On Sat, 29 Dec 2001, guy keren wrote: > > On Sat, 29 Dec 2001, Shlomi Fish wrote: > > > I installed kernel 2.4.16.11mdk (from Mandrake Cooker) on my Linux > > installation. It did not replace the old kernel but rather I have both > > version installed. I'd like to boot it instead. > > > > My father would kill me if I'll replace the Win98's MBR boot loader with > > LILO, so I'm using loadlin. > > why? just set up LILO to time-out after 3 seconds, and boot into windows > by default - your father won't notice any difference - just tell him to > press ENTER if he sees 'LILO:' on the screen for more then 3 seconds. > > but lets not get into paranoyaland now. >
I'm not going to install LILO - period. Since the rest of my family uses Windows, there's no point in booting Linux not through it. > > Unfortunately, loadlin reboots the computer > > instead of booting the Linux with the kernel and initrd file that Mandrake > > have placed on the hard-disk. > > did you make sure you have a version of LILO capable of using the 32 bit > BIOS interface, to handle large disk drives? i haven't followed on loadlin > for a long time, so i don't know how it handles large drivers (i.e. > 1024 > cylinders, for example). > > however, the fct that it worked for you until now, implies you did > something wrong with the new kernel, or that mandrake changed something, > and you need to look for info from them. > I'll try. > > I decided to try and install LILO on a floppy which will boot the kernel > > from there. I used the following lilo.conf file: > > > > boot=/dev/fd0 > > map=/boot/map > > install=/boot/boot.b > > vga=normal > > default=linux-2.4.16-11 > > #keytable=/boot/us.klt > > #lba32 > > prompt > > timeout=50 > > #message=/boot/message > > image=/boot/vmlinuz-2.4.16-11mdk > > label=linux-2.4.16-11 > > root=/dev/hdc5 > > initrd=/boot/initrd-2.4.16-11mdk.img > > append=" devfs=mount" > > read-only > > the file itself looks ok. > > > However, when I place the floppy in the floppy drive and reboot the > > machine an "L" is displayed" and then the number "01" consecutively. I > > checked the LILO documentation, but I'm not sure what I'm doing wrong. > > because you haven't realy read it carefully. please point your browser to > http://linuxclub.il.eu.org/lectures/12/ (slides of a lecture whose title > is 'Linux startup process - from boot till SysV init') and look at the > 'LILO error codes' section - it might enlighten you. > I looked at it and in other places and it did not help me. > > My Linux hard disk has been disabled from the BIOS, so this may be a > > problem. > > what do you mean 'disabled'? meaning that the BIOS does would not > recognize it as a valid drive? then ofcourse it won't work - LILO depends > on some bios interfaces to access the hard disk and read data from it. > Bingo! Apparently, when I set up the BIOS to detect my secondary master (the Linux disk) to AUTO instead of NONE, LILO booted the system fine. Thanks. Regards, Shlomi Fish ---------------------------------------------------------------------- Shlomi Fish [EMAIL PROTECTED] Home Page: http://t2.technion.ac.il/~shlomif/ Home E-mail: [EMAIL PROTECTED] "Let's suppose you have a table with 2^n cups..." "Wait a second - is n a natural number?" ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
