lkml.org 
[lkml]   [1999]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Booting process Linux with NOVELL RPL
Well, I came along these problems half a year ago - but the bad
news is that I havnt got it work. My setup is quite different, but
the problem is probably the same. I tried to load the image with
a tftp capable boot-rom, but for strange reasons the tftp code
fills the image downwards from the place where the initial loader
(i.e. the kernel one that reads from the "floppy") copies itself,
so after some bytes of loading the image it gets itself... whoops.

To address this problem, you should look into making the whole
load/decompress thing more configurable (i.e. configurable buffer
addresses, even loading a non-compressed image would be working
if using bzImages).

Richard.

btw. H. P. Anvin was quite helpful in tracking down/commenting
my thoughts about this. You may also ask the lilo/syslinux authors
about this.

On Mon, 8 Feb 1999, Ard van Breemen wrote:

> Hi,
> I got a minor problem with booting the kernel.
> I've got a Network Computer that boots using NOVELL RPL over 802.3.
> With mars I am able to feed this computer any disk I want, although it is
> up to the programs to be able to work. (Normal freedos disk images work)
> I've found that booting freedos is no problem, but running loadlin is,
> running lilo does not work either.
> So I thought about feeding the NC just a plain Linux Kernel. Tadah! It is
> accepted! (loadlin and lilo don't come that far for loading the kernel.)
> The kernel is really able to download itself. But then the stage of
> uncompressing:
> invalid compressed format (err=2).
> This message is issued in lib/inflate.c. after examening the kernel image
> header, using the get_byte function call.
> I guess this is an issue of the starting address of the kernel, since it
> is loaded by RPL, which itself occupies some space.
> So my question is, is this a logic conclussion, and most important: has
> anybody seen this behaviour already, knows what is going on, and
> (hopefully) has a fix, or at least a suggestion?
>
> If not, I will find it out myself, but I'd rather do not something that
> someone else has already done.
>
> Thanx!
> --
> intel1: 11:49am up 13 days, 10:02, 12 users, load average: 0.15, 0.12, 0.07
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>

--
Richard Guenther <richard.guenther@student.uni-tuebingen.de>
PGP: 2E829319 - 2F 83 FC 93 E9 E4 19 E2 93 7A 32 42 45 37 23 57
WWW: http://www.anatom.uni-tuebingen.de/~richi/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:2.114 / U:0.000 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site