LILO hangs on "Loading Linux....."
Hi, I am booting from a floppy (/dev/fd0). My Slackware partition is /dev/hdb3. I am using the vmlinuz kernal.
Here is my custom-made lilo.conf (which is in /etc/lilo.conf) I have LILO on a floppy so I can boot Linux immediately, so when I don't have it in it just goes straight to Vista (I know, I'm stupid.) Code:
disk=/dev/hdb Code:
boot: Code:
mkinitrd -c -f reiserfs -r /dev/hdb3 Thanks, David |
I have never used the disk= option, but if you're booting to /dev/hdb, should you be specifying bios=0x81? (My reference book says the first disk is usually 0x80 and the second disk is usually 0x81.) Do you even need the disk= and bios= statements at all? I've never used them, but then I've never used LILO from a floppy either. (BTW, I do a similar thing you are trying using a GRUB floppy to choose a different OS than default on a box I run headless. However you want to boot your machine is up to you. Let freedom ring!)
|
Yeah, I just assummed 80 said to treat that drive as the primary, but I really didn't know the meaning behind it all. I think I remember trying it w/o those statments and it would give me an error, but I'll try it again when I get back to that computer (won't be till after Spring break, woooo!)
Thanks, David P.S. what is the best way to create a initrd.gz file? I really think that is the best reason as to why this isn't working, because like I said, it will load all the way past that line, which makes me think it is loading the kernal, then just waiting on commands, that they never get. |
Quote:
Loading Linux .................. Uncompressing Linux .............. Then it rapidly spits out a bunch of messages as the kernel itself boots. If the kernel was booting OK and your problem was initrd.gz, I think it would give you a message to that effect, or at least you would see more than you do. But like I say, I could be wrong. And I don't have a convenient way to test this right now. P.S. I have a machine that uses LILO to multiboot with one of the choices being Damn Small Linux, which I have on a FAT32 partition which mainly holds an old win95 installation. One time w/o thinking, I "defragged" that partition w/o rerunning lilo aftewards. The next time I went to boot DSL I observed what you have described. The defragging had moved things around and LILO didn't know where they were until I ran lilo again. |
Well I just recently reinstalled LILO, so I don't think it is that. If you say initrd.gz starts after
Code:
Uncompressing Linux.............. |
Quote:
By recently reinstalling, do you mean running the lilo command? If so, did you try changing or removing that bios = line? |
Yes I ran the LILO command. I don't remember the last time I didn't use the BIOS, but when I don't, it will give me an error when I start up with an error code (error 4 I believe).
I am thinking, however, that I may need to put Code:
bios=0x81 Code:
bios=0x80 So what should I see if it were to boot up correctly? Something like: Code:
Loading Linux......................... |
Quote:
Quote:
If you can't get the last 2/3, have you thought about trying to use GRUB from a floppy instead? I have done it, but my grasp of GRUB is shaky enough I don't know if I am the best person to advise. |
Ok, I'll give that a try when I get back to town (gotta love figuring out a problem with a computer while not even being in the same area code lol)
|
Hallelujah! Just had to switch disk to 0x81, Thanks a lot yall!
|
All times are GMT -5. The time now is 09:15 AM. |