Hello from Gregg C Levine normally with Jedi Knight Computers "Um okay, Richard, I'll find it in my sent messages folders, and quote it here: "Well, I have to hand it to you, Richard, this time it works. I applied the patch to a "clean tar ball of Release 2.4.2, (following your instructions from 12/11/01 Tuesday, "naturally.), and did the usual things to create a bootable image. And after the system "finished booting with the messaging that I believe is normal on Slackware based "systems, (dmesg output available on request.), and ran things this way, "./kexec "kernel.elf". The end result? The dmesg output that I associate with the kernel release "that I have turned into an elf image using the program that Eric wrote for the job. In "the environment that I am running, a Pentium Classic system with a commodity "BIOS, is that normal a response? Ideally, I'd like to try this one on for size on a Linux "BIOS equipped system, of similar vintage, the board is a 430FX based one, from "Tyan. Once again, thanks, your work in creating those patches, well this one, and the "other stuff turned out to be the tiger's PJs. And I have two such cats here, they are the "company mascots Okay, in that series of events, it, (the kexec'd kernel, a 2.2.19 one) goes through the standard sequence of events, and promptly runs down to the end with it, it's complaining that it can not mount the root file system, on the hard drive, root device 00:00, and then it stops. This elf image was made up using version 1.7. I'll try out the other ones, I have all of them here. Note, that version 1.90 does not work as advertised. Part of my investigations was to see exactly what happens during the whole process, so this is what I expected. Now how did you, create your initial root device? I can create one, using tools suggested for doing so, on a system that will be booted using loadlinux, instead of GRUB, or lilo. ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner- > [EMAIL PROTECTED]] On Behalf Of Richard A. Smith > Sent: Thursday, December 13, 2001 12:36 PM > To: Gregg C Levine > Cc: Linuxbios > Subject: Re: kexec -- has anyone take it any further? > > On 12 Dec 2001 22:04:03 -0700, Eric W. Biederman wrote: > > >> function does work as advertised, but since my system, is running with a > >> commodity bios, my setup, gets locked in a kernel panic, and I have to > >> reset the system, I do not think I am getting anywhere. This does not > >> mean I shall be discouraged. Just that I'd like to take this concept > >> onto a matching Linux BIOS configured motherboard. It is wearing a 430FX > >> based motherboard, with a Pentium, if that is any help. > > > >Hmm. I am distured that you have issues. And that Rich has issues. > >I will export the stability and apply ability of this shortly. I am > > Gregg, > > I missed in your (off-list) e-mail that you were getting a kernel > panic. Where exactly is the panic at? I was _not_ using LinuxBios > at the time I set up the kexec stuff because LB didn't have general > purpose 440bx support back then. I was using a semi-commodity BIOS > designed for embedded systems. > > I also was kexecing a 2.2.19 kernel rather than another 2.4.x. > > My problem was that if I used any version of mkelfImage other than > v1.0 to build the kexeced kernel image it would some how corrupt the > initrd when it loaded it. As long as I stuck to v1.0 it worked > great. > > Then the project died so I never investigated it any further. > > -- > Richard A. Smith Bitworks, Inc. > [EMAIL PROTECTED] 501.846.5777 > Sr. Design Engineer http://www.bitworks.com > > >
