RE: [expert] LILO Problem - Loading Linux EBDA too big
On Tue, 2002-02-19 at 12:45, Jorge A. Pichardo wrote: > Yep. I updated the kernel through the Mandrake wizard and it burped > until the machine was booted. Anyway, thanks for the clues Braian and > BillK! It is up and running again! By the way when I run the boot CD and > going to the process of the expert mode choosing the update I got the > error "fsck failed with exit code 4 or signal 0" when it reaches the > security check. I tried to run a series of switches in the LILO in > rescue mode to rebuild the device and I didn't work telling me > "Fatal:open /boot/vmlinuz: no such file or directory". I looked into the > "/boot" and I had to rebuild the symbolic link pointing to the right > file for the vmlinuz file and that was it. It worked charmy. > > Thanks folks yeah...see updating the kernel through Software manager is a definate no..no. That's been a rule of thumb since 8.0 came out. Not quite sure why, but I know, as do you now too, that it does bad things. And yes, I did it too and didn't remember Civileme's warning about doing so until after I'd done it. By then it was too late. the deed had been done. the best way to handle the kernel updates is to just download the packages to your drive and do them that way. -- daRcmaTTeR Registered Linux User 182496 Mandrake 8.2beta1 - 3:05pm up 2:39, 2 users, load average: 0.03, 0.10, 0.05 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
RE: [expert] LILO Problem - Loading Linux EBDA too big
Yep. I updated the kernel through the Mandrake wizard and it burped until the machine was booted. Anyway, thanks for the clues Braian and BillK! It is up and running again! By the way when I run the boot CD and going to the process of the expert mode choosing the update I got the error "fsck failed with exit code 4 or signal 0" when it reaches the security check. I tried to run a series of switches in the LILO in rescue mode to rebuild the device and I didn't work telling me "Fatal:open /boot/vmlinuz: no such file or directory". I looked into the "/boot" and I had to rebuild the symbolic link pointing to the right file for the vmlinuz file and that was it. It worked charmy. Thanks folks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of William Kenworthy Sent: Monday, February 18, 2002 5:23 PM To: Mandrake Expert Subject: Re: [expert] LILO Problem - Loading Linux EBDA too big To add a bit more: when you changed the kernel, lilo is trying to load the kernel using the old boot info and what the obtuse error message is saying is that it doesnt match what it thinks it should be loading. The cure is to read "man lilo" and use the chroot option to to write the new kernel information to the boot sector whilst mounted in rescue mode. BillK On Tue, 2002-02-19 at 09:04, Brian Parish wrote: > Have you upgraded the kernel by any chance? This is usually the > scenario that causes this. Anyway, the easiest way out is to boot > from the install CD, choose expert mode, choose update, choose no > packages to install, then just run through a standard install (very > quickly). This should straighten on the chaos in your /boot and get > you running again. > > If it was a kernel upgrade that caused it, note for the future that > even though the kernel appears in the security updates list, it should > NEVER be installed that way. Instead, download it and do "rpm -ivh > kernel..." so that it gets installed alongside your existing kernel. > > HTH > Brian > > On Tue, 2002-02-19 at 11:34, Jorge A. Pichardo wrote: > > Hi all, > > > > I posted my problem in the newbies group and didn't get no answer > > yet. So I posted it here. For some reason this morning appeared a > > message in my linux box: "Loading Linux EBDA too big" and the system > > halts. It is the same everytime I boot it. > > > > I tried to rescue it with the mandrake install CD and tried "chroot > > /mnt" and all my directory structure seems ok (boot, dev, home,...) > > now in "/" then I tried to mount /boot but I had this error "can't > > find boot in /etc/fstab or /etc/mtab" I looked into those files and > > I saw nothing about the "/boot" and I can't get it booted yet. I > > read somewhere else that I need to remount the /boot and run "sync" > > a couple of times followed by a lilo -v -v as commands. But I have > > no luck yet. > > > > At this point I don't know how to proceed. Any thoughts, > > recommendations > > > > Regards, > > Jorge Pichardo > > > > Victoria - Vancouver British Columbia, Canada > > Tel: +250-370-5250 > > > > > > > > > > > > > > > > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://www.mandrakestore.com > > > > > > This message has been 'sanitized'. This means that potentially > dangerous content has been rewritten or removed. The following log > describes which actions were taken. > > Sanitizer (start="1014081124"): > Part (pos="2727"): > SanitizeFile (filename="unnamed.txt", mimetype="text/plain"): > Match (rule="2"): > Enforced policy: accept > > Part (pos="4603"): > SanitizeFile (filename="message.footer", mimetype="text/plain"): > Match (rule="default"): > Enforced policy: defang > > Replaced mime type with: application/DEFANGED-8988 > Replaced file name with: message_footer.DEFANGED-8988 > > Total modifications so far: 1 > > > Anomy 0.0.0 : Sanitizer.pm > $Id: Sanitizer.pm,v 1.32 2001/10/11 19:27:15 bre Exp $ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO Problem - Loading Linux EBDA too big
To add a bit more: when you changed the kernel, lilo is trying to load the kernel using the old boot info and what the obtuse error message is saying is that it doesnt match what it thinks it should be loading. The cure is to read "man lilo" and use the chroot option to to write the new kernel information to the boot sector whilst mounted in rescue mode. BillK On Tue, 2002-02-19 at 09:04, Brian Parish wrote: > Have you upgraded the kernel by any chance? This is usually the > scenario that causes this. Anyway, the easiest way out is to boot from > the install CD, choose expert mode, choose update, choose no packages to > install, then just run through a standard install (very quickly). This > should straighten on the chaos in your /boot and get you running again. > > If it was a kernel upgrade that caused it, note for the future that even > though the kernel appears in the security updates list, it should NEVER > be installed that way. Instead, download it and do "rpm -ivh kernel..." > so that it gets installed alongside your existing kernel. > > HTH > Brian > > On Tue, 2002-02-19 at 11:34, Jorge A. Pichardo wrote: > > Hi all, > > > > I posted my problem in the newbies group and didn't get no answer yet. > > So I posted it here. > > For some reason this morning appeared a message in my linux box: > > "Loading Linux EBDA too big" and the system halts. It is the same > > everytime I boot it. > > > > I tried to rescue it with the mandrake install CD and tried "chroot > > /mnt" and all my directory structure seems ok (boot, dev, home,...) now > > in "/" then I tried to mount /boot but I had this error "can't find > > boot in /etc/fstab or /etc/mtab" I looked into those files and I saw > > nothing about the "/boot" and I can't get it booted yet. > > I read somewhere else that I need to remount the /boot and run "sync" a > > couple of times followed by a lilo -v -v as commands. But I have no luck > > yet. > > > > At this point I don't know how to proceed. Any thoughts, > > recommendations > > > > Regards, > > Jorge Pichardo > > > > Victoria - Vancouver British Columbia, Canada > > Tel: +250-370-5250 > > > > > > > > > > > > > > > > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://www.mandrakestore.com > > > > > > This message has been 'sanitized'. This means that potentially > dangerous content has been rewritten or removed. The following > log describes which actions were taken. > > Sanitizer (start="1014081124"): > Part (pos="2727"): > SanitizeFile (filename="unnamed.txt", mimetype="text/plain"): > Match (rule="2"): > Enforced policy: accept > > Part (pos="4603"): > SanitizeFile (filename="message.footer", mimetype="text/plain"): > Match (rule="default"): > Enforced policy: defang > > Replaced mime type with: application/DEFANGED-8988 > Replaced file name with: message_footer.DEFANGED-8988 > > Total modifications so far: 1 > > > Anomy 0.0.0 : Sanitizer.pm > $Id: Sanitizer.pm,v 1.32 2001/10/11 19:27:15 bre Exp $ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] LILO Problem - Loading Linux EBDA too big
Have you upgraded the kernel by any chance? This is usually the scenario that causes this. Anyway, the easiest way out is to boot from the install CD, choose expert mode, choose update, choose no packages to install, then just run through a standard install (very quickly). This should straighten on the chaos in your /boot and get you running again. If it was a kernel upgrade that caused it, note for the future that even though the kernel appears in the security updates list, it should NEVER be installed that way. Instead, download it and do "rpm -ivh kernel..." so that it gets installed alongside your existing kernel. HTH Brian On Tue, 2002-02-19 at 11:34, Jorge A. Pichardo wrote: > Hi all, > > I posted my problem in the newbies group and didn't get no answer yet. > So I posted it here. > For some reason this morning appeared a message in my linux box: > "Loading Linux EBDA too big" and the system halts. It is the same > everytime I boot it. > > I tried to rescue it with the mandrake install CD and tried "chroot > /mnt" and all my directory structure seems ok (boot, dev, home,...) now > in "/" then I tried to mount /boot but I had this error "can't find > boot in /etc/fstab or /etc/mtab" I looked into those files and I saw > nothing about the "/boot" and I can't get it booted yet. > I read somewhere else that I need to remount the /boot and run "sync" a > couple of times followed by a lilo -v -v as commands. But I have no luck > yet. > > At this point I don't know how to proceed. Any thoughts, > recommendations > > Regards, > Jorge Pichardo > > Victoria - Vancouver British Columbia, Canada > Tel: +250-370-5250 > > > > > > > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[expert] LILO Problem - Loading Linux EBDA too big
Hi all, I posted my problem in the newbies group and didn't get no answer yet. So I posted it here. For some reason this morning appeared a message in my linux box: "Loading Linux EBDA too big" and the system halts. It is the same everytime I boot it. I tried to rescue it with the mandrake install CD and tried "chroot /mnt" and all my directory structure seems ok (boot, dev, home,...) now in "/" then I tried to mount /boot but I had this error "can't find boot in /etc/fstab or /etc/mtab" I looked into those files and I saw nothing about the "/boot" and I can't get it booted yet. I read somewhere else that I need to remount the /boot and run "sync" a couple of times followed by a lilo -v -v as commands. But I have no luck yet. At this point I don't know how to proceed. Any thoughts, recommendations Regards, Jorge Pichardo Victoria - Vancouver British Columbia, Canada Tel: +250-370-5250 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lilo problem?
--- Lonnie Cumberland <[EMAIL PROTECTED]> wrote: > lilo.conf > --- > boot=/dev/sda > map=/boot/map > install=/boot/boot.b > vga=normal > default=linux > keytable=/boot/us.klt > lba32 > prompt > timeout=50 > message=/boot/message > menu-scheme=wb:bw:wb:bw > image=/boot/vmlinuz <-- this and > label=linux > root=/dev/sda5 > initrd=/boot/initrd.img > append=" hdc=ide-scsi ide0=noautotune > ide1=noautotune ide2=noautotune > ide3=noautotune mem=128M" > read-only > image=/boot/vmlinuz > label=failsafe > root=/dev/sda5 > initrd=/boot/initrd.img > append=" hdc=ide-scsi failsafe" > read-only > other=/dev/fd0 > label=floppy > unsafe > image=/boot/vmlinuz <--- thiis causing the problem > label=ic-linux > root=/dev/hde6 > initrd=/boot/initrd.img > append="hdc=ide-scsi ide0=noautotune > ide1=noautotune ide2=noautotune ide3=noautotune" > read-only > - > copy the MDK8 kernel (vmlinuz-2.4.3-20mdk) from /dev/hde6's /boot directory to the /boot dir of /dev/sda5, then change image=/boot/vmlinuz (with 2nd arrow) to image=/boot/vmlinuz-2.4.3-20mdk. run /sbin/lilo ... make sure no errors encountered, then reboot using image ic-linux. hope that works. > does anyone have any ideas? > > Cheers, > Lonnie > > Lonnie Cumberland > OutStep Technologies Incorporated > > URL: http://www.outstep.com > EMAIL: [EMAIL PROTECTED] > : [EMAIL PROTECTED] > > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://.mandrakestore.com > __ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com
Re: [expert] lilo problem?
Ok, you have /boot/vmlinuz as the image for both kernels. You should have the two different images listed separately. Try putting a different image e.g. image=/boot/vmlinuz-new in your /etc/lilo.conf file where /boot/vmlinuz-new is a link to your new kernel image. -sen On Mon, 13 Aug 2001, Lonnie Cumberland wrote: > > > > > > lilo.conf > > > > > --- > > > boot=/dev/sda > > > map=/boot/map > > > install=/boot/boot.b > > > vga=normal > > > default=linux > > > keytable=/boot/us.klt > > > lba32 > > > prompt > > > timeout=50 > > > message=/boot/message > > > menu-scheme=wb:bw:wb:bw > > > image=/boot/vmlinuz > > > label=linux > > > root=/dev/sda5 > > > initrd=/boot/initrd.img > > > append=" hdc=ide-scsi ide0=noautotune ide1=noautotune > > ide2=noautotune > > > ide3=noautotune mem=128M" > > > read-only > > > image=/boot/vmlinuz > > > label=failsafe > > > root=/dev/sda5 > > > initrd=/boot/initrd.img > > > append=" hdc=ide-scsi failsafe" > > > read-only > > > other=/dev/fd0 > > > label=floppy > > > unsafe > > > image=/boot/vmlinuz > > > label=ic-linux > > > root=/dev/hde6 > > > initrd=/boot/initrd.img > > > append="hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune > > ide3=noautotune" > > > read-only > > > > > - Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com
Re: [expert] lilo problem?
Hello, I can select the proper image to boot in the LILO selections, but the problem is that the incorrect "vmlinuz" is being booted. The "vmlinuz" pointed to on the SCSI /dev/sda5 is being booted instead of the "vmlinuz" pointed to on the /dev/hde6 UltraDMA 66 controller. The correct "root" filesystem is being loaded and setup, but the incorrect kernel. -- Lonnie Quoting "Sheldon E. Newhouse" <[EMAIL PROTECTED]>: > On Mon, 13 Aug 2001, Lonnie Cumberland wrote: > > > Hello All, > > > > How are you doing today? Good I hope. > > > > I have an interesting problem with my Lilo that I hope someone might > have a > > solution for. > > > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have > an > > UltraDMA 66 drive installed and is accessible as well. Currently my > Mandrake 7.2 > > runs just fine and I have made a clean partition on my /dev/hde6 to > install a > > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > > > The install had gone just fine onto the /dev/hde6 partition for the > Mandrake > > 8.0, and I then added the entries to my lilo.conf on my Mandrake > 7.2. > > > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry > from lilo, > > it appears that my old 2.2.17 kernel is booted (even though there is > NONE in the > > /dev/hde6 partition) and then it tries to use the files located on the > /dev/hde6 > > > Hello All, > > > > How are you doing today? Good I hope. > > > > I have an interesting problem with my Lilo that I hope someone might > have a > > solution for. > > > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have > an > > UltraDMA 66 drive installed and is accessible as well. Currently my > Mandrake 7.2 > > runs just fine and I have made a clean partition on my /dev/hde6 to > install a > > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > > > The install had gone just fine onto the /dev/hde6 partition for the > Mandrake > > 8.0, and I then added the entries to my lilo.conf on my Mandrake > 7.2. > > > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry > from lilo, > > it appears that my old 2.2.17 kernel is booted (even though there is > NONE in the > > /dev/hde6 partition) and then it tries to use the files located on the > /dev/hde6 > > > Hello All, > > > > How are you doing today? Good I hope. > > > > I have an interesting problem with my Lilo that I hope someone might > have a > > solution for. > > > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have > an > > UltraDMA 66 drive installed and is accessible as well. Currently my > Mandrake 7.2 > > runs just fine and I have made a clean partition on my /dev/hde6 to > install a > > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > > > The install had gone just fine onto the /dev/hde6 partition for the > Mandrake > > 8.0, and I then added the entries to my lilo.conf on my Mandrake > 7.2. > > > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry > from lilo, > > it appears that my old 2.2.17 kernel is booted (even though there is > NONE in the > > /dev/hde6 partition) and then it tries to use the files located on the > /dev/hde6 > > > Hello All, > > > > How are you doing today? Good I hope. > > > > I have an interesting problem with my Lilo that I hope someone might > have a > > solution for. > > > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have > an > > UltraDMA 66 drive installed and is accessible as well. Currently my > Mandrake 7.2 > > runs just fine and I have made a clean partition on my /dev/hde6 to > install a > > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > > > The install had gone just fine onto the /dev/hde6 partition for the > Mandrake > > 8.0, and I then added the entries to my lilo.conf on my Mandrake > 7.2. > > > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry > from lilo, > > it appears that my old 2.2.17 kernel is booted (even though there is > NONE in the > > /dev/hde6 partition) and then it tries to use the files located on the > /dev/hde6 > > > Hello All, > > > > How are you doing today? Good I hope. > > > > I have an interesting problem with my Lilo that I hope someone might > have a > > solution for. > > > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have > an > > UltraDMA 66 drive installed and is accessible as well. Currently my > Mandrake 7.2 > > runs just fine and I have made a clean partition on my /dev/hde6 to > install a > > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > > > The install had gone just fine onto the /dev/hde6 partition for the > Mandrake > > 8.0, and I then added the entries to my lilo.conf on my Mandrake > 7.2. > > > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry > from lilo, > > it appears that my old 2.2.17 kernel is booted (even though there is > NONE in the > > /dev/hde6 partition) and then it tries to use the files located on the > /dev/hde6 > > partitio
Re: [expert] lilo problem?
On Mon, 13 Aug 2001, Lonnie Cumberland wrote: > Hello All, > > How are you doing today? Good I hope. > > I have an interesting problem with my Lilo that I hope someone might have a > solution for. > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an > UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 > runs just fine and I have made a clean partition on my /dev/hde6 to install a > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > The install had gone just fine onto the /dev/hde6 partition for the Mandrake > 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry from lilo, > it appears that my old 2.2.17 kernel is booted (even though there is NONE in the > /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 > Hello All, > > How are you doing today? Good I hope. > > I have an interesting problem with my Lilo that I hope someone might have a > solution for. > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an > UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 > runs just fine and I have made a clean partition on my /dev/hde6 to install a > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > The install had gone just fine onto the /dev/hde6 partition for the Mandrake > 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry from lilo, > it appears that my old 2.2.17 kernel is booted (even though there is NONE in the > /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 > Hello All, > > How are you doing today? Good I hope. > > I have an interesting problem with my Lilo that I hope someone might have a > solution for. > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an > UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 > runs just fine and I have made a clean partition on my /dev/hde6 to install a > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > The install had gone just fine onto the /dev/hde6 partition for the Mandrake > 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry from lilo, > it appears that my old 2.2.17 kernel is booted (even though there is NONE in the > /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 > Hello All, > > How are you doing today? Good I hope. > > I have an interesting problem with my Lilo that I hope someone might have a > solution for. > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an > UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 > runs just fine and I have made a clean partition on my /dev/hde6 to install a > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > The install had gone just fine onto the /dev/hde6 partition for the Mandrake > 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry from lilo, > it appears that my old 2.2.17 kernel is booted (even though there is NONE in the > /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 > Hello All, > > How are you doing today? Good I hope. > > I have an interesting problem with my Lilo that I hope someone might have a > solution for. > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an > UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 > runs just fine and I have made a clean partition on my /dev/hde6 to install a > test copy of Mandrake 8.0 to run the 2.4.x kernel. > > The install had gone just fine onto the /dev/hde6 partition for the Mandrake > 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry from lilo, > it appears that my old 2.2.17 kernel is booted (even though there is NONE in the > /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 > partition from which the kernel cannot locate the required 2.2.17 kernel modules. > > My confusion is that when I boot "IC", lilo hould be trying to boot the 2.4.x > kernel from /dev/hde6 and NOT the kernel 2.2.17 from the /dev/sda5 partition. Your first image in the /etc/lilo.conf file is the default that the system will try to boot. In order to choose another image you have to manually use the "tab" key when the lilo: prompt appears. After you decide which image you want to actually be the default, simply edit the /etc/lilo.conf file to put the corresponding lines in the proper position. -sen > I have included a copy of the LILO.CONF from my Mnadrake 7.2 so that you can > take a look at, ok.
Re: [expert] lilo problem?
I'm wondering if you might have to do some drive mapping. My windows install is on hdb, so to get it to boot, I do: other=/dev/hdb1 label=windows table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 This is just a guess, but maybe you can do: image=/boot/vmlinuz label=ic-linux map-drive=0x84 to=0x80 root=/dev/hde6 initrd=/boot/initrd.img append="hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune It might have to do with restrictions on booting from hde, but I could very well be wrong. :( -- Stephen On Monday 13 August 2001 08:31 am, Lonnie Cumberland wrote: > Hello All, > > How are you doing today? Good I hope. > > I have an interesting problem with my Lilo that I hope someone might have a > solution for. > > I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an > UltraDMA 66 drive installed and is accessible as well. Currently my > Mandrake 7.2 runs just fine and I have made a clean partition on my > /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. > > The install had gone just fine onto the /dev/hde6 partition for the > Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake > 7.2. > > The problem is that when I try to boot the "IC" (Mandrake 8.0) entry from > lilo, it appears that my old 2.2.17 kernel is booted (even though there is > NONE in the /dev/hde6 partition) and then it tries to use the files located > on the /dev/hde6 partition from which the kernel cannot locate the required > 2.2.17 kernel modules. > > My confusion is that when I boot "IC", lilo hould be trying to boot the > 2.4.x kernel from /dev/hde6 and NOT the kernel 2.2.17 from the /dev/sda5 > partition. > > I have included a copy of the LILO.CONF from my Mnadrake 7.2 so that you > can take a look at, ok. > > lilo.conf > --- > boot=/dev/sda > map=/boot/map > install=/boot/boot.b > vga=normal > default=linux > keytable=/boot/us.klt > lba32 > prompt > timeout=50 > message=/boot/message > menu-scheme=wb:bw:wb:bw > image=/boot/vmlinuz > label=linux > root=/dev/sda5 > initrd=/boot/initrd.img > append=" hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune > ide3=noautotune mem=128M" > read-only > image=/boot/vmlinuz > label=failsafe > root=/dev/sda5 > initrd=/boot/initrd.img > append=" hdc=ide-scsi failsafe" > read-only > other=/dev/fd0 > label=floppy > unsafe > image=/boot/vmlinuz > label=ic-linux > root=/dev/hde6 > initrd=/boot/initrd.img > append="hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune > ide3=noautotune" read-only > - > > does anyone have any ideas? Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com
[expert] lilo problem?
Hello All, How are you doing today? Good I hope. I have an interesting problem with my Lilo that I hope someone might have a solution for. I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2 runs just fine and I have made a clean partition on my /dev/hde6 to install a test copy of Mandrake 8.0 to run the 2.4.x kernel. The install had gone just fine onto the /dev/hde6 partition for the Mandrake 8.0, and I then added the entries to my lilo.conf on my Mandrake 7.2. The problem is that when I try to boot the "IC" (Mandrake 8.0) entry from lilo, it appears that my old 2.2.17 kernel is booted (even though there is NONE in the /dev/hde6 partition) and then it tries to use the files located on the /dev/hde6 partition from which the kernel cannot locate the required 2.2.17 kernel modules. My confusion is that when I boot "IC", lilo hould be trying to boot the 2.4.x kernel from /dev/hde6 and NOT the kernel 2.2.17 from the /dev/sda5 partition. I have included a copy of the LILO.CONF from my Mnadrake 7.2 so that you can take a look at, ok. lilo.conf --- boot=/dev/sda map=/boot/map install=/boot/boot.b vga=normal default=linux keytable=/boot/us.klt lba32 prompt timeout=50 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label=linux root=/dev/sda5 initrd=/boot/initrd.img append=" hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune mem=128M" read-only image=/boot/vmlinuz label=failsafe root=/dev/sda5 initrd=/boot/initrd.img append=" hdc=ide-scsi failsafe" read-only other=/dev/fd0 label=floppy unsafe image=/boot/vmlinuz label=ic-linux root=/dev/hde6 initrd=/boot/initrd.img append="hdc=ide-scsi ide0=noautotune ide1=noautotune ide2=noautotune ide3=noautotune" read-only - does anyone have any ideas? Cheers, Lonnie Lonnie Cumberland OutStep Technologies Incorporated URL: http://www.outstep.com EMAIL: [EMAIL PROTECTED] : [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://.mandrakestore.com
Re: [expert] LILO problem with LM7.2
[EMAIL PROTECTED] wrote: > > I just istalled LM7.2 on my new drive (20GB). It's got a 13GB Win98 > partition and the rest for LM7.2. The install goes fine, but LILO doesn't > install. I tried with every distro I own and the same thing happens, LILO > refuses to install. In order to get the thing to boot, I installed FreeBSD > 4.0, and it's bootloader installed. I re-installed LM7.2 over BSD, but > again, LILO won't install. The BSD loader is still there. > > Any clues why? As Al Baker mentioned, Windows systems install on the first available partition on the first hard drive. This is cast in stone. In addition, MS FDISK will only create one Primary partition and an Extended partition (with multiple logical drives) whereas the Linux system can create up to 4 primary partitions (the limit for a hard drive). Lilo must be installed within the first 1024 cylinders of the drive being booted, or it will not boot/install properly. A workaround is to create a small primary partition (10 MB) at the start of the drive which will be mounted as /boot. This will ensure that LILO is within the first 1024 cylinders. This works even if it is being installed on a second or third drive. If it is on the first drive, it will be labeled as C. I am using Norton's GDISK to do this. Next, a primary partition of a suitable size is defined for Windows. This partition will be labeled as D. The first primary must then be marked as hidden. This will force the second partition to be labeled as C so Windows can be installed on it. It should be also set to active. You can then define a partition for swap (128 MB?) and one for the balance of the Linux system which will be mounted as root. Install Windows first. It will automatically go to the default C partition. Once Windows is configured, you can proceed to install Mandrake Linux. When the install gets to the disk partitioning question, choose diskdrake. It will display the various partitions including the hidden one. Click on EXT2 and then on the first small partition, and set its mount point as /boot. On a second or third drive, there should be only 3 partitions. The first at the drive start will be the small one which will be mounted as /boot. In either case, the remaining partitions can be set to swap or / as required. Note that GDISK leaves the default format of these partitions a FAT, so you will have to click either SWAP or EXT2 before clicking on a partition to set a mount point. Diskdrake also will detect the Windows partition, and will set its mount point as /mnt/windows. When the install gets to the question of installing LILO, (or GRUB), have it installed on the master boot record (MBR) of the first drive - hda. Mandrake automatically detects Windows and includes it in its menu. I am currently configuring a system to use Win98, LM7.2 and BeOS. I used Nortons GDISK running on a Win98 system floppy to configure a 10 GB hard drive as follows: P1 - 13 MB mount as /boot P2 - 2 GB Windows 98 EXT2 L1 - 2 GB for BeOS L2 - 133 MB Swap L3 - 5.1 GB mount as root I can start either Windows or LM7.2 at boot time, and am going to install BeOS next. BeOS has a nice boot loader and I may use it to control the system startup. Hope this helps... Tom. Tom Cada Great Lakes Systems
Re: [expert] LILO problem with LM7.2
I believe Windows likes to be the first partition on the drive, and then you have to set LILO to the MBR (master boot record). I think FreeBSD defaults it's loader to the master boot record as well. --- [EMAIL PROTECTED] wrote: > I just istalled LM7.2 on my new drive (20GB). It's > got a 13GB Win98 > partition and the rest for LM7.2. The install goes > fine, but LILO doesn't > install. I tried with every distro I own and the > same thing happens, LILO > refuses to install. In order to get the thing to > boot, I installed FreeBSD > 4.0, and it's bootloader installed. I re-installed > LM7.2 over BSD, but > again, LILO won't install. The BSD loader is still > there. > > Any clues why? > > > __ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/
[expert] LILO problem with LM7.2
I just istalled LM7.2 on my new drive (20GB). It's got a 13GB Win98 partition and the rest for LM7.2. The install goes fine, but LILO doesn't install. I tried with every distro I own and the same thing happens, LILO refuses to install. In order to get the thing to boot, I installed FreeBSD 4.0, and it's bootloader installed. I re-installed LM7.2 over BSD, but again, LILO won't install. The BSD loader is still there. Any clues why?
Re: [expert] lilo problem
I'm only guessing what you are asking here . . . If you mean that your LILO on the hard disk went away, but you can still boot from floppy, then . . . Just boot from floppy, the log in as root, and run lilo, by typing lilo . If you mean somthihng else, please ask the question more coherently: What doesn't work? How doesn't it work? What is the *precise* command you are issuing? What is the *precise* error message you are getting? "webug :-)" wrote: > > hi ! > > my lilo does not work anymore > how do i restore the fd0 to the lilo ? > is there a short way to do that ? > please help !! -- "Brian, the man from babble-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com.
[expert] lilo problem
hi ! my lilo does not work anymore how do i restore the fd0 to the lilo ? is there a short way to do that ? please help !!
Re: [expert] LILO problem
On Mon, 17 Apr 2000, Kirk McElhearn wrote: > I just tried something - I have a Mandrake boot floppy, and I figured > that maybe I could just copy it and change some config in the floppy to > get the other distro to boot. But when trying to access the floppy, I > get a message Could not list directory contents. Is this floppy some > format that cannot be read by Mandrake? How are you trying to read the floppy? -Matt Stegman <[EMAIL PROTECTED]>
Re: [expert] LILO problem
Kirk McElhearn wrote: > On 16/04/00 23:11, Andrew George [EMAIL PROTECTED] is reported to > have said: > > >/boot/vmlinuz is a symlink to the real kernel file, I noticed both your linux > >distributons in LILO.conf pointed to it so I was wondering if the symlink had > >been removed somehow so lilo didn't know where to find the real Kernel > > Isn't it checking for this symlink in the HD that is specified for each > boot setup? > > In any case, it still tells me No images have been defined > > Kirk If the /boot/vmlinuz symlink doesn't work with Lilo, then simply enter the full name of the kernel to boot with, e.g., /boot/vmlinuz-2.2.2-x Besides, even if the plain, general, vmlinuz, symlink worked, it'ld still be better to specify the entire kernel image name, because, then, when you work on reconfiguring the lilo.conf file using some tool, or even directly, you explicitly know what you're dealing with. Hence, regardless of whether a symlink like this did work, it shouldn't be used for this purpose, imo. mike
Re: [expert] LILO problem
Kirk McElhearn wrote: > I'm really getting fed up with this problem. So many people said it was > so easy to use a big HD and boot more than one distribution, I wish there > were some way to figure out why it won't work for me > > I just tried something - I have a Mandrake boot floppy, and I figured > that maybe I could just copy it and change some config in the floppy to > get the other distro to boot. But when trying to access the floppy, I > get a message Could not list directory contents. Is this floppy some > format that cannot be read by Mandrake? I don't think that Mandrake should have any problems listing the contents of the disk. Have you tried listing the contents from a dos boot, like into Win9x or NT? If you can list the contents there, then you can definitely list the contents with Linux, but the mount definition may need to be changed to specify the correct filesystem type. To check the latter, you can try mounting the floppy to ext2 and to vfat, if ext2 fails. If both of these fail, then haven't a clue. mount -vt vfat /dev/fd0H1440 /mnt/floppy mount -vt ext2 /dev/fd0 /mnt/floppy mount -vt vfat /dev/fd0 /mnt/floppy You could use /mnt/a:, instead of /mnt/floppy. Doesn't matter, as long as the /mnt mount point isn't already mounted. The only time this can otherwise matter is if you try to mount without specifying the -t option and argument. If none of these mounts works, then haven't a clue. If any of these mounts works and you can't list the contents of the floppy disk, then haven't a clue. On the other hand, the above is based on the assumption that you're trying to list the contents of a Linux boot floppy, which should be listable. As for large disks, you might find some useful information through the LDP http://www.linuxdoc.org Check through the list of HOWTOs. You should find one on using Large Disks. Don't know if it'll contain the answer to your problems, but you should read the howto anyway. mike
Re: [expert] LILO problem
I'm really getting fed up with this problem. So many people said it was so easy to use a big HD and boot more than one distribution, I wish there were some way to figure out why it won't work for me I just tried something - I have a Mandrake boot floppy, and I figured that maybe I could just copy it and change some config in the floppy to get the other distro to boot. But when trying to access the floppy, I get a message Could not list directory contents. Is this floppy some format that cannot be read by Mandrake? Kirk vice versa Translations - French to English, English to French | Technical Writing Traductions francais-anglais, anglais-francais | Redaction technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [EMAIL PROTECTED]http://www.mcelhearn.com Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] LILO problem
On 16/04/00 23:11, Andrew George [EMAIL PROTECTED] is reported to have said: >/boot/vmlinuz is a symlink to the real kernel file, I noticed both your linux >distributons in LILO.conf pointed to it so I was wondering if the symlink had >been removed somehow so lilo didn't know where to find the real Kernel Isn't it checking for this symlink in the HD that is specified for each boot setup? In any case, it still tells me No images have been defined Kirk vice versa Translations - French to English, English to French | Technical Writing Traductions francais-anglais, anglais-francais | Redaction technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [EMAIL PROTECTED]http://www.mcelhearn.com Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] LILO problem
On Mon, 17 Apr 2000, you wrote: > On 16/04/00 0:58, Andrew George [EMAIL PROTECTED] is reported to > have said: > > >1) Are you running lilo -R ? (the lilo doc says running lilo -R gives you > >that > >error) > > No. > > > 2) Is the symlink for vmlinuz still there? > > Where is there? > > Kirk > /boot/vmlinuz is a symlink to the real kernel file, I noticed both your linux distributons in LILO.conf pointed to it so I was wondering if the symlink had been removed somehow so lilo didn't know where to find the real Kernel
Re: [expert] LILO problem
On 16/04/00 0:58, Andrew George [EMAIL PROTECTED] is reported to have said: >1) Are you running lilo -R ? (the lilo doc says running lilo -R gives you >that >error) No. > 2) Is the symlink for vmlinuz still there? Where is there? Kirk vice versa Translations - French to English, English to French | Technical Writing Traductions francais-anglais, anglais-francais | Redaction technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [EMAIL PROTECTED]http://www.mcelhearn.com Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] LILO problem
On Sun, 16 Apr 2000, Kirk McElhearn wrote: > On 14/04/00 19:45, Stephen F. Bosch [EMAIL PROTECTED] is reported to > have said: > > >> OK, I have finally managed to get two distributions installed, and to get > >> lilo to work. But when I try to tweek the lilo.conf, I get a message > >> that each of my choices is added, but then it says No images have been > >> defined. It does not update my changes in the mbr. What could I be > >> doing wrong? > > > >Show us your /etc/lilo.conf, man. > > boot = /dev/fd0 > timeout = 100 > prompt > message = /boot/message > default = dos > vga = normal > read-only > map=/boot/map > install=/boot/boot.b > keytable=/boot/pc-dvorak-latin1.klt > image = /boot/vmlinuz > label = mdk2 > root = /dev/hdb11 > image = /boot/vmlinuz > label = mdk > root = /dev/hda6 > other = /dev/hda1 > label = win > table=/dev/hda > other = /dev/fd0 > label = floppy > unsafe > > Kirk Errtwo questions 1) Are you running lilo -R ? (the lilo doc says running lilo -R gives you that error) 2) Is the symlink for vmlinuz still there? Andrew
Re: [expert] LILO problem
On 15/04/00 19:54, Mike Corbeil [EMAIL PROTECTED] is reported to have said: >> >Show us your /etc/lilo.conf, man. >> >> boot = /dev/fd0 > >If you want your changes to go to the mbr, then the above line must be >changed >to /dev/hda, which is where the mbr is located. > >The way you have it, it'ld used /dev/fd0, which is the floppy. Yeah, sorry about that. I had tried both to the MBR and to a floppy, and neither worked. I should have sent it with /hda... Kirk vice versa Translations - French to English, English to French | Technical Writing Traductions francais-anglais, anglais-francais | Redaction technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [EMAIL PROTECTED]http://www.mcelhearn.com Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] LILO problem
Kirk McElhearn wrote: > On 14/04/00 19:45, Stephen F. Bosch [EMAIL PROTECTED] is reported to > have said: > > >> OK, I have finally managed to get two distributions installed, and to get > >> lilo to work. But when I try to tweek the lilo.conf, I get a message > >> that each of my choices is added, but then it says No images have been > >> defined. It does not update my changes in the mbr. What could I be > >> doing wrong? > > > >Show us your /etc/lilo.conf, man. > > boot = /dev/fd0 If you want your changes to go to the mbr, then the above line must be changed to /dev/hda, which is where the mbr is located. The way you have it, it'ld used /dev/fd0, which is the floppy. > timeout = 100 > prompt > message = /boot/message > default = dos > vga = normal > read-only > map=/boot/map > install=/boot/boot.b > keytable=/boot/pc-dvorak-latin1.klt > image = /boot/vmlinuz > label = mdk2 > root = /dev/hdb11 > image = /boot/vmlinuz > label = mdk > root = /dev/hda6 > other = /dev/hda1 > label = win > table=/dev/hda > other = /dev/fd0 > label = floppy > unsafe > > Kirk > >vice versa > Translations - French to English, English to French | Technical Writing > Traductions francais-anglais, anglais-francais | Redaction technique > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > [EMAIL PROTECTED]http://www.mcelhearn.com > Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] LILO problem
Kirk McElhearn wrote: > Actually, I figured this question would not get many answers on the > newbie list... You may be correct, but it would be useful to other newbies, because many or all newbies will need deal with that kind of question. On the other hand, asking in the expert mailing list also isn't a crime. I've only been using these mailing lists since this past week and kind of like the idea, personally, that at least some more seasoned people pay some attention to questions asked in the newbie list. Maybe I have too much of a bleeding heart for newbies. Of course no one is obligated to do so, and it'ld make more emails to delete, but I don't have a problem doing that. If I see a question or thread I'm not interested in or can't answer, then Delete is quickly clicked. Some people, however, get annoyed by overwhelming amounts of email, but if subjects are sufficiently clear, then more email is less of a problem or nuissance. Clear subjects, though, are therefore important. You say LILO and I know what you mean. If you said , then I wouldn't have a clue, but might read just to find out what is about. If, however, you say the name of an application which I have no experience with and no interest in, then Delete, and zap it's gone. This is one reason why I'm following both threads, however won't be for long if I don't get this cdrom installed. Definitely not a rich man, and I'm not prepared to swap the drives. Laziness is part of the reason, but it's mostly because I'm not interested in dealing with the hassles swapping will bring, at least not now. The rest is merely a story I'm not going to bla blab about. I apologize for being too harsh, though, even if you don't seem too bothered. My global perspective "got the better" of me (I think that's the correct expression). mike
Re: [expert] LILO problem
On 15/04/00 0:28, Marcos Dione [EMAIL PROTECTED] is reported to have said: >> Lastly, this is truly a newbie question and should be asked in the newbie >> mailing list. > > don't mean to start a flamewar here... but don't try to >discriminate... I mean, I don't think he's a newbie if he's trying to boot >another kernel. I think a newbie would not know what the hell is a >kernel... anyway, he made the question, so, don't complain about he MUST >ask it somewhere else. Actually, I figured this question would not get many answers on the newbie list... Kirk vice versa Translations - French to English, English to French | Technical Writing Traductions francais-anglais, anglais-francais | Redaction technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [EMAIL PROTECTED]http://www.mcelhearn.com Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] LILO problem
On 14/04/00 19:45, Stephen F. Bosch [EMAIL PROTECTED] is reported to have said: >> OK, I have finally managed to get two distributions installed, and to get >> lilo to work. But when I try to tweek the lilo.conf, I get a message >> that each of my choices is added, but then it says No images have been >> defined. It does not update my changes in the mbr. What could I be >> doing wrong? > >Show us your /etc/lilo.conf, man. boot = /dev/fd0 timeout = 100 prompt message = /boot/message default = dos vga = normal read-only map=/boot/map install=/boot/boot.b keytable=/boot/pc-dvorak-latin1.klt image = /boot/vmlinuz label = mdk2 root = /dev/hdb11 image = /boot/vmlinuz label = mdk root = /dev/hda6 other = /dev/hda1 label = win table=/dev/hda other = /dev/fd0 label = floppy unsafe Kirk vice versa Translations - French to English, English to French | Technical Writing Traductions francais-anglais, anglais-francais | Redaction technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [EMAIL PROTECTED]http://www.mcelhearn.com Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] LILO problem
Marcos Dione wrote: > On Fri, 14 Apr 2000, Mike Corbeil wrote: > > > Lastly, this is truly a newbie question and should be asked in the newbie > > mailing list. > > don't mean to start a flamewar here... but don't try to > discriminate... I mean, I don't think he's a newbie if he's trying to boot > another kernel. I think a newbie would not know what the hell is a > kernel... anyway, he made the question, so, don't complain about he MUST > ask it somewhere else. The crucial underlying point is that many newbies are using the newbie list and in asking there, the answer will be made there, which means that many more newbies will benefit. I like thinking in global manners. I've subscribed to both lists and if a newbie question is more than basic, then I suggest they post to the expert list and therefore to subscribe to both. The question was newbie, but t'was not a crime committed. I'll refrain from proving the newbie part of the point and retract my harsh attitude. mike > > > -- > "No tire sus colillas en el mingitorio, las humedece y > las hace dificil de encender" > "Do not dump butts in the wc. They dampen and it makes > them difficult to light." > --Tom Sharpe, "Wilt on high"
Re: [expert] LILO problem
On Fri, 14 Apr 2000, Mike Corbeil wrote: > Lastly, this is truly a newbie question and should be asked in the newbie > mailing list. don't mean to start a flamewar here... but don't try to discriminate... I mean, I don't think he's a newbie if he's trying to boot another kernel. I think a newbie would not know what the hell is a kernel... anyway, he made the question, so, don't complain about he MUST ask it somewhere else. -- "No tire sus colillas en el mingitorio, las humedece y las hace dificil de encender" "Do not dump butts in the wc. They dampen and it makes them difficult to light." --Tom Sharpe, "Wilt on high"
Re: [expert] LILO problem
Kirk McElhearn wrote: > > OK, I have finally managed to get two distributions installed, and to get > lilo to work. But when I try to tweek the lilo.conf, I get a message > that each of my choices is added, but then it says No images have been > defined. It does not update my changes in the mbr. What could I be > doing wrong? Show us your /etc/lilo.conf, man. -Stephen-
Re: [expert] LILO problem
Kirk McElhearn wrote: > OK, I have finally managed to get two distributions installed, and to get > lilo to work. But when I try to tweek the lilo.conf, I get a message > that each of my choices is added, but then it says No images have been > defined. It does not update my changes in the mbr. What could I be > doing wrong? > > Kirk Provide the contents of the lilo.conf file you're trying to use, and the contents of the /boot directories of the Linux configurations that lilo is supposed to be able to boot. For the /boot listing, you only need to include the name of the kernel image file and symlinks, if there are symlinks. These are typically /boot/vmlinuz... Also: - give the or list the /dev/hd??? files mapped to /, and - what tool are you using to tweek the lilo.conf file? There are at least a couple capable tools; therefore, it may be helpful to know which (I only know linuxconf, whereas others apparently use other tools). Lastly, this is truly a newbie question and should be asked in the newbie mailing list. My hd.img question would resemble a newbie question, except that I'm also asking how the hd.img file for the cdrom I have can be modified or made to work with the second hdd, which it's not permitting to use, currently. This goes beyond what newbies can easily or quickly find worthwhile and authoritative documentation for, particularly because I don't have the sources to create the hd.img file and would prefer avoiding this (will probably just trash the cdrom, instead, albeit maybe not). Am "simultaneously" working on upgrading RH 5.1 to 5.2 and beyond, as well as trying to find a way to install this cdrom for Mdk 7.0v2 (probably or perhaps not worthwhile, but will see); and, of course, there are many other things to do; therefore, am seeking what these mailing lists are supposedly for, i.e., assistance. You should read the documentation on lilo, lilo.conf, and the tool you're using to configure or define the lilo.conf file. You could edit it directly and then simply run lilo, but the gui tools available are certainly adequate and easy to use. Plus if there's anything else which needs to be done related to lilo configuration, then these tools will take care of this business, permitting the user to get on with other more useful things to learn. I never had to ask anyone how to configure and install lilo, albeit would be interested in knowing if it would work for this hd.img problem I'm having. Some reading might turn up the answer, but I already went through the lilo man pages and this wasn't fruitful for this particular task. Don't really like the idea that lilo configuration requires visibility of kernel images, though. Always someone to tell you can't do something which shouldn't hurt anyone except novices and experienced people who are asleep when doing their work. Anyway, if you want help, then you need to provide more information. mike
[expert] LILO problem
OK, I have finally managed to get two distributions installed, and to get lilo to work. But when I try to tweek the lilo.conf, I get a message that each of my choices is added, but then it says No images have been defined. It does not update my changes in the mbr. What could I be doing wrong? Kirk vice versa Translations - French to English, English to French | Technical Writing Traductions francais-anglais, anglais-francais | Redaction technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [EMAIL PROTECTED]http://www.mcelhearn.com Kirk McElhearn | Chemin de la Lauze | 05600 Guillestre | France
Re: [expert] lilo problem with 7.0 air
Tom Berkley wrote: > Larry > > Suspect a lilo.conf line length limitation. Try using the \ character at > the end of a line > and continue the append command on the following line. Make absolute > certain that no spaces follow the \ character or is will not escape the > newline character. > > Tom Sorry but I should have mentioned that I've read all the documentation and the character limitation is not stated or I missed that part. I have previously tried the line warp procedure but it still chops off and will not execute the remainder of the append statement. I can however type the idea and idea statement at the lilo prompt and then it will be accepted and also the append statement will be correct as to the ide-scsi items. This way everything will load fine, but not if I place it all into the lilo append. Seems like it worked for me some time back but this may just be wishfully thinking Thank You Larry > > Larry Sword wrote: > > > > Tom Berkley wrote: > > > > > In append major items are separated with spaces and minor (within an > > > option) items are separated with commas. Not sure if this is a > > > convention for viewing or if lilo actually pays attention to this. But > > > it works, notheless. > > > > > > Tom > > > > Speaking of the append statement. I've run into [problems when the total > > number of characters and spaces number in excess of 42. After the 42nd > > character the remainder of the line is ignored. > > Example: append="hdc=ide-scsi hdd=ide-scsi ide2=0xd400,0xd802,18 > > ide3=0xe000,0xe402,18" > > Anything after ,0xe402, is cut off and ignored, and the ide2 and ide3 are > > not loaded. > > > > And yes placing the "," after a major item will cause the append statement to > > ignore anything after, at least it did to me > > > > Larry > > > > > > > > > > > Larry Sword wrote: > > > > > > > > Fabrice SERVANT wrote: > > > > > > > > > Hello, > > > > > As my linux won't recognize my 128M RAM > > > > > I'm trying to put append="mem=128M" in my > > > > > lilo.conf. But when I type lilo to update the config > > > > > I get the following message: > > > > > > > > > > Added li > > > > > Added win > > > > > Added floppy > > > > > No images have been defined. > > > > > > > > > > HERE IS MY LILO.CONF > > > > > > > > > > boot=/dev/hde > > > > > map=/boot/map > > > > > install=/boot/boot.b > > > > > vga=normal > > > > > default=windows > > > > > keytable=/boot/fr-latin1.klt > > > > > prompt > > > > > timeout=100 > > > > > message=/boot/message > > > > > root=/dev/hdf6 > > > > > read-only > > > > > image=/boot/vmlinuz-2.2.14-15mdk > > > > > label=linux > > > > > initrd=/boot/initrd-2.2.14-15mdk.img > > > > > append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" > > > > > > > > One other item. Remove the "," after "mem=128M. Items are separated only > > > > by a space. > > > > > > > > > > > > > > other=/dev/hde1 > > > > > label=win > > > > > table=/dev/hde > > > > > other=/dev/fd0 > > > > > label=floppy > > > > > unsafe > > > > > > > > > > Anyone speaks "lilo.conf" ? > > > > > bye > > > > > > > > > > __ > > > > > Get Your Private, Free Email at http://www.hotmail.com
Re: [expert] lilo problem with 7.0 air
Larry Suspect a lilo.conf line length limitation. Try using the \ character at the end of a line and continue the append command on the following line. Make absolute certain that no spaces follow the \ character or is will not escape the newline character. Tom Larry Sword wrote: > > Tom Berkley wrote: > > > In append major items are separated with spaces and minor (within an > > option) items are separated with commas. Not sure if this is a > > convention for viewing or if lilo actually pays attention to this. But > > it works, notheless. > > > > Tom > > Speaking of the append statement. I've run into [problems when the total > number of characters and spaces number in excess of 42. After the 42nd > character the remainder of the line is ignored. > Example: append="hdc=ide-scsi hdd=ide-scsi ide2=0xd400,0xd802,18 > ide3=0xe000,0xe402,18" > Anything after ,0xe402, is cut off and ignored, and the ide2 and ide3 are > not loaded. > > And yes placing the "," after a major item will cause the append statement to > ignore anything after, at least it did to me > > Larry > > > > > > > Larry Sword wrote: > > > > > > Fabrice SERVANT wrote: > > > > > > > Hello, > > > > As my linux won't recognize my 128M RAM > > > > I'm trying to put append="mem=128M" in my > > > > lilo.conf. But when I type lilo to update the config > > > > I get the following message: > > > > > > > > Added li > > > > Added win > > > > Added floppy > > > > No images have been defined. > > > > > > > > HERE IS MY LILO.CONF > > > > > > > > boot=/dev/hde > > > > map=/boot/map > > > > install=/boot/boot.b > > > > vga=normal > > > > default=windows > > > > keytable=/boot/fr-latin1.klt > > > > prompt > > > > timeout=100 > > > > message=/boot/message > > > > root=/dev/hdf6 > > > > read-only > > > > image=/boot/vmlinuz-2.2.14-15mdk > > > > label=linux > > > > initrd=/boot/initrd-2.2.14-15mdk.img > > > > append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" > > > > > > One other item. Remove the "," after "mem=128M. Items are separated only > > > by a space. > > > > > > > > > > > other=/dev/hde1 > > > > label=win > > > > table=/dev/hde > > > > other=/dev/fd0 > > > > label=floppy > > > > unsafe > > > > > > > > Anyone speaks "lilo.conf" ? > > > > bye > > > > > > > > __ > > > > Get Your Private, Free Email at http://www.hotmail.com
Re: [expert] lilo problem with 7.0 air
Tom Berkley wrote: > In append major items are separated with spaces and minor (within an > option) items are separated with commas. Not sure if this is a > convention for viewing or if lilo actually pays attention to this. But > it works, notheless. > > Tom Speaking of the append statement. I've run into [problems when the total number of characters and spaces number in excess of 42. After the 42nd character the remainder of the line is ignored. Example: append="hdc=ide-scsi hdd=ide-scsi ide2=0xd400,0xd802,18 ide3=0xe000,0xe402,18" Anything after ,0xe402, is cut off and ignored, and the ide2 and ide3 are not loaded. And yes placing the "," after a major item will cause the append statement to ignore anything after, at least it did to me Larry > > > Larry Sword wrote: > > > > Fabrice SERVANT wrote: > > > > > Hello, > > > As my linux won't recognize my 128M RAM > > > I'm trying to put append="mem=128M" in my > > > lilo.conf. But when I type lilo to update the config > > > I get the following message: > > > > > > Added li > > > Added win > > > Added floppy > > > No images have been defined. > > > > > > HERE IS MY LILO.CONF > > > > > > boot=/dev/hde > > > map=/boot/map > > > install=/boot/boot.b > > > vga=normal > > > default=windows > > > keytable=/boot/fr-latin1.klt > > > prompt > > > timeout=100 > > > message=/boot/message > > > root=/dev/hdf6 > > > read-only > > > image=/boot/vmlinuz-2.2.14-15mdk > > > label=linux > > > initrd=/boot/initrd-2.2.14-15mdk.img > > > append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" > > > > One other item. Remove the "," after "mem=128M. Items are separated only > > by a space. > > > > > > > > other=/dev/hde1 > > > label=win > > > table=/dev/hde > > > other=/dev/fd0 > > > label=floppy > > > unsafe > > > > > > Anyone speaks "lilo.conf" ? > > > bye > > > > > > __ > > > Get Your Private, Free Email at http://www.hotmail.com
Re: [expert] lilo problem with 7.0 air
On Sun, 09 Apr 2000, you wrote: > Hello, > As my linux won't recognize my 128M RAM > I'm trying to put append="mem=128M" in my > lilo.conf. But when I type lilo to update the config > I get the following message: > HmmFirst of all, does that first image (/boot/vmlinuz-2.2.14-15mdk) exist in the /boot directory? Second, does your system share some of the ram for video purposes? If so, you'll need to take that account in your "append" statement. Thirdly, does it work OK if you take out the "mem=128M"? Fourthly, do you have BIOS set to OS/2??? If so, I'm told you'll NEVER see anything above about 50 or 60 megs of RAM! John
Re: [expert] lilo problem with 7.0 air
In append major items are separated with spaces and minor (within an option) items are separated with commas. Not sure if this is a convention for viewing or if lilo actually pays attention to this. But it works, notheless. Tom Larry Sword wrote: > > Fabrice SERVANT wrote: > > > Hello, > > As my linux won't recognize my 128M RAM > > I'm trying to put append="mem=128M" in my > > lilo.conf. But when I type lilo to update the config > > I get the following message: > > > > Added li > > Added win > > Added floppy > > No images have been defined. > > > > HERE IS MY LILO.CONF > > > > boot=/dev/hde > > map=/boot/map > > install=/boot/boot.b > > vga=normal > > default=windows > > keytable=/boot/fr-latin1.klt > > prompt > > timeout=100 > > message=/boot/message > > root=/dev/hdf6 > > read-only > > image=/boot/vmlinuz-2.2.14-15mdk > > label=linux > > initrd=/boot/initrd-2.2.14-15mdk.img > > append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" > > One other item. Remove the "," after "mem=128M. Items are separated only > by a space. > > > > > other=/dev/hde1 > > label=win > > table=/dev/hde > > other=/dev/fd0 > > label=floppy > > unsafe > > > > Anyone speaks "lilo.conf" ? > > bye > > > > __ > > Get Your Private, Free Email at http://www.hotmail.com
Re: [expert] lilo problem with 7.0 air
Fabrice SERVANT wrote: > Hello, > As my linux won't recognize my 128M RAM > I'm trying to put append="mem=128M" in my > lilo.conf. But when I type lilo to update the config > I get the following message: > > Added li > Added win > Added floppy > No images have been defined. > > HERE IS MY LILO.CONF > > boot=/dev/hde > map=/boot/map > install=/boot/boot.b > vga=normal > default=windows > keytable=/boot/fr-latin1.klt > prompt > timeout=100 > message=/boot/message > root=/dev/hdf6 > read-only > image=/boot/vmlinuz-2.2.14-15mdk > label=linux > initrd=/boot/initrd-2.2.14-15mdk.img > append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" One other item. Remove the "," after "mem=128M. Items are separated only by a space. > > other=/dev/hde1 > label=win > table=/dev/hde > other=/dev/fd0 > label=floppy > unsafe > > Anyone speaks "lilo.conf" ? > bye > > __ > Get Your Private, Free Email at http://www.hotmail.com
Re: [expert] lilo problem with 7.0 air
win instead of windows That was my mistake Thanks Fabrice U allways need someone to look after you, so do I __ Get Your Private, Free Email at http://www.hotmail.com
Re: [expert] lilo problem with 7.0 air
Fabrice SERVANT wrote: > > Hello, > As my linux won't recognize my 128M RAM > I'm trying to put append="mem=128M" in my > lilo.conf. But when I type lilo to update the config > I get the following message: > > Added li > Added win > Added floppy > No images have been defined. > > HERE IS MY LILO.CONF > > boot=/dev/hde > map=/boot/map > install=/boot/boot.b > vga=normal > default=windows > keytable=/boot/fr-latin1.klt > prompt > timeout=100 > message=/boot/message > root=/dev/hdf6 > read-only > image=/boot/vmlinuz-2.2.14-15mdk > label=linux > initrd=/boot/initrd-2.2.14-15mdk.img > append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" > other=/dev/hde1 > label=win > table=/dev/hde > other=/dev/fd0 > label=floppy > unsafe > > Anyone speaks "lilo.conf" ? > bye > Whoops noticed that label=win and default=windows do not appear to be in sync. It might cause problems when booting default. Civileme
Re: [expert] lilo problem with 7.0 air
Fabrice SERVANT wrote: > > Hello, > As my linux won't recognize my 128M RAM > I'm trying to put append="mem=128M" in my > lilo.conf. But when I type lilo to update the config > I get the following message: > > Added li > Added win > Added floppy > No images have been defined. > > HERE IS MY LILO.CONF > > boot=/dev/hde > map=/boot/map > install=/boot/boot.b > vga=normal > default=windows > keytable=/boot/fr-latin1.klt > prompt > timeout=100 > message=/boot/message > root=/dev/hdf6 > read-only > image=/boot/vmlinuz-2.2.14-15mdk > label=linux > initrd=/boot/initrd-2.2.14-15mdk.img > append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" > other=/dev/hde1 > label=win > table=/dev/hde > other=/dev/fd0 > label=floppy > unsafe > > Anyone speaks "lilo.conf" ? > bye MOVE the line root=/dev/hdf6 to follow image=/boot/vmlinuz-2.2.14-15mdk An image is not complete without a root directory to mount The rest looks ok Civileme
[expert] lilo problem with 7.0 air
Hello, As my linux won't recognize my 128M RAM I'm trying to put append="mem=128M" in my lilo.conf. But when I type lilo to update the config I get the following message: Added li Added win Added floppy No images have been defined. HERE IS MY LILO.CONF boot=/dev/hde map=/boot/map install=/boot/boot.b vga=normal default=windows keytable=/boot/fr-latin1.klt prompt timeout=100 message=/boot/message root=/dev/hdf6 read-only image=/boot/vmlinuz-2.2.14-15mdk label=linux initrd=/boot/initrd-2.2.14-15mdk.img append="mem=128M, ide2=0xcc00,0xd002 ide3=0xd800,0xdc02" other=/dev/hde1 label=win table=/dev/hde other=/dev/fd0 label=floppy unsafe Anyone speaks "lilo.conf" ? bye __ Get Your Private, Free Email at http://www.hotmail.com
Re: [expert] Lilo problem after kernel recompile
On Thu, 10 Jun 1999, Sheldon Lee Wen wrote: > It seems that on dual processor > systems that lilo can hang the kernel because it ends up overwriting > some of it's memory space. Lilo therefore needs to be compiled with > the LARGE_EDBA option. Thanks - I've put a new lilo in the updates directory. LLaP bero
Re: [expert] Lilo problem after kernel recompile
Just to let everyone know... I downloaded and built the lilo SRPM. It seems that on dual processor systems that lilo can hang the kernel because it ends up overwriting some of it's memory space. Lilo therefore needs to be compiled with the LARGE_EDBA option. Just thought that this might increase your knowledge base :) Cheers. Sheldon. -- == Sheldon Lee Wen [EMAIL PROTECTED], Nortelnetworks Ottawa Canada Skyeast CSA x55800 "Superstition is a word the ignorant use to describe their ignorance." -- Sifu. ==
[expert] Lilo problem after kernel recompile
Hi, I recompiled and installed my kernel. After rebooting lilo comes up as normal. However, after I type in linux I get the starting linux message and it hangs. I thought it may be my kernel so I reinstalled the rpm's for the old one and rebooted. Same problem. I can boot off of a boot disk fine but this is annoying. I tried editing my lilo.conf file and ran lilo -c, didn't work, I then added linear to the configuration didn't work. I boot to the os2 boot manager from hda which then loads lilo from a second hard drive hdc lilo then should be pointing to my boot directory on hda5. Here's my fstab file: /dev/hda6 / ext2defaults1 1 /dev/hdc1 /boot ext2defaults1 2 /dev/hdc5 Swap001 swapdefaults0 0 /dev/hda7 Swap002 swapdefaults0 0 /dev/hdc6 /optext2defaults1 3 /dev/fd0/mnt/floppy ext2noauto 0 0 none/proc procdefaults0 0 none/dev/ptsdevpts mode=0622 0 0 heres my lilo.conf file: boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 image=/boot/vmlinuz-2.2.9-19mdksmp label=linux root=/dev/hda6 read-only image=/boot/vmlinuz-2.2.9-19mdk label=linux-up root=/dev/hda6 read-only other=/dev/hda1 label=dos table=/dev/hda Anyone please give me some suggestions or point me in the right direction. Thanks, Sheldon.
