* Re2: loadlin with 2.5.?? kernels [not found] <1c6.531124.2ae44a91@aol.com> @ 2002-10-20 18:22 ` Mike Galbraith 2002-10-20 19:26 ` Rene Blokland 0 siblings, 1 reply; 3+ messages in thread From: Mike Galbraith @ 2002-10-20 18:22 UTC (permalink / raw) To: Floydsmith, linux-kernel; +Cc: Floydsmith At 02:06 PM 10/20/2002 -0400, Floydsmith@aol.com wrote: >Subj: Re: loadlin with 2.5.?? kernels >Date: 10/20/2002 1:43:50 PM Eastern Daylight Time >gmx.de >vger.kernel.org >aol.com >Sent from the Internet (Details) > > > >aol.com wrote: > >In a message dated 10/20/2002 9:03:34 AM Eastern Daylight Time, >gmx.de writes: > > > > > >>Subj:loadlin with 2.5.?? kernels > >>Date:10/20/2002 9:03:34 AM Eastern Daylight Time >gmx.de >vger.kernel.org > >>Sent from the Internet > >> > >> > >> > >>Greetings, > >> > >>I hadn't had time to build/test kernels since 2.5.8-pre3. I now find that > >>loadlin doesn't work on my box any more. Is this a known problem? If so, > >>when did it quit working? (loadlin obsolete? other?) > >> > >>At the moment, the only way I have to boot is via floppy. > > > > > >loadlin will not work with any kernel that is 1024k or greater in size. > >There is a replacement named "linld" at: > >http://www.tux.org/pub/people/kent-robotti/looplinux/index.html > >which help you. > >Yeah, that's always been a pain, but that's not what I'm hitting (violent >reboot). I'll give linld (thanks!) a shot, but mostly, I want my dearly >beloved loadlin back ;-) > >Reply: >Yes I have seen that one to (but only with certain large kernels and when >certain large initrd images are used). >The only solution I have found (so far) is to reduce the size of the >initrd - again, a pain. >If linld works for you, please reply; this would be usefull info. What was the last version that booted for you no problem? (other than size) -Mike ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Re2: loadlin with 2.5.?? kernels 2002-10-20 18:22 ` Re2: loadlin with 2.5.?? kernels Mike Galbraith @ 2002-10-20 19:26 ` Rene Blokland 2002-10-21 5:29 ` Eric W. Biederman 0 siblings, 1 reply; 3+ messages in thread From: Rene Blokland @ 2002-10-20 19:26 UTC (permalink / raw) To: linux-kernel In article <5.1.0.14.2.20021020202108.00b890f8@pop.gmx.net>, Mike Galbraith wrote: > What was the last version that booted for you no problem? (other than size) > > -Mike In my case x.38 that is the last, I don't no anymore why not .39 (did it compile?) But sure .40 didn't boot with loadlin and an image dd'd to a floppy -- Groeten / Regards, Rene J. Blokland ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Re2: loadlin with 2.5.?? kernels 2002-10-20 19:26 ` Rene Blokland @ 2002-10-21 5:29 ` Eric W. Biederman 0 siblings, 0 replies; 3+ messages in thread From: Eric W. Biederman @ 2002-10-21 5:29 UTC (permalink / raw) To: reneb; +Cc: linux-kernel Rene Blokland <reneb@orac.aais.org> writes: > In article <5.1.0.14.2.20021020202108.00b890f8@pop.gmx.net>, Mike Galbraith > wrote: > > > > What was the last version that booted for you no problem? (other than size) > > > > -Mike > > In my case x.38 that is the last, I don't no anymore why not .39 (did it > compile?) > But sure .40 didn't boot with loadlin and an image dd'd to a floppy Hmm. Are you certain the last working version wasn't at .30 that just before Ingos gdt changes. And changing the gdt is quite likely to have broken loadlin, as it uses the segments in the gdt from setup.S I will see if I can build a test patch for this. Except for the recent EDD work and the GDT change there really haven't been changes to setup.S so this failure report is very strange. Eric ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-10-21 5:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1c6.531124.2ae44a91@aol.com>
2002-10-20 18:22 ` Re2: loadlin with 2.5.?? kernels Mike Galbraith
2002-10-20 19:26 ` Rene Blokland
2002-10-21 5:29 ` Eric W. Biederman
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox
Powered by JetHome