Forum Home
Press F1
Thread ID: 24044	2002-09-02 06:41:00	Booting to Linux	Mike (15)	Press F1

Post ID	Timestamp	Content	User
75734	2002-09-05 10:14:00	> this HOWTO ( . lug . net . nz/docs/ldp/HOWTO/mini/Loa" target="_blank">dunedin . lug . net . nz > lin+Win95-98-ME/) about how to do > it . I would if I could get past the contents page :( > There is something wrong with your lilo . . . it > prints a letter as it gets to each stage L . . . I . . . > L . . . O, so if you get LI, it is crapping out . yeah, it freezes at LI - but only when booting off the second drive . If I boot off the main drive it loads fine (doesn't now cause I removed it) and off the floppy it loads fine (which is what I'm using now) . Mike .	Mike (15)
75735	2002-09-05 11:13:00	LILO does this sometimes - one solution is to install something like XOSL in the master boot record and LILO in the root partition of Linux.	JohnD (509)
75736	2002-09-06 04:43:00	Mike ... that Howto has a "Next" at the bottom left corner of each page ... that gets you to the next page B-) BTW your pasting of the link put a > in the middle of it ...	Graham L (2)
75737	2002-09-06 04:53:00	and just thought of something ... the LILO problem might be that you installed it to that second HDD when it was the second HDD, and you are trying to use it as the first HDD with your BIOS boot order changing. That would foul up in a baaaad way because it will be referring to the disk as "/dev/hdb" when it is actually being "/dev/hda". That is enough to confuse the very best boot manager. (And of course, it is the best boot manager ;-)). You don't fix something like this by adding boot managers. You fix it by finding the cause. I'm not sure how we can fix this, without accidentally zapping the MS disk's MBR. I think that the safest way will be to stick with the floppy boot.	Graham L (2)
75738	2002-09-06 05:36:00	> Mike ... that Howto has a "Next" at the bottom left > corner of each page ... that gets you to the next > page B-) I may be thick, but I'm not stupid :) actually every link I clicked on on the page, including the Next link just sent me to another copy of the same page... no matter what link I clicked on. Maybe I should try again today :) > BTW your pasting of the link put a > in the > middle of it ... who cares :) it's the forum's fault - I just clicked on "Quote original", so if there was a in the middle of it, then the forum created it by itself :) Mike.	Mike (15)
75739	2002-09-06 05:39:00	I was wondering if that might have been the problem, although I also wonder whether it would have been considered /dev/hda rather than /dev/hdb, as all I did was change the boot order, not which disk it was (my bios is stupid gateway that doesn't let you actually change what the computer thinks of each disk - just lets you change what order to boot in). For example if I set it to boot IDE2 after IDE1, but both after ATAPI CDROM, it wouldn't know that IDE2 was the first booting HDD as I'd booted (for the install) off the CD. (does that make sense?) Mike.	Mike (15)
75740	2002-09-06 05:48:00	Opps, sorry, that happens to me too. Odd. ?:| The document is there and it's readable when not accessed directly from here. After being caught a few times, I always click on any link I make here, but didn't go further than checking the first page. Try going in through the directory of all the miniHOWTOs (dunedin.lug.net.nz) for "Loadlin+Win95+98+ME". Or use a browser on your Linux documentation CD. Should have all the HOWTOS.	Graham L (2)
75741	2002-09-06 08:43:00	Graham - if you can get the thing to go by adding another boot loader, why not? Surely the aim is to get the OS going and do some things with it? I have never been able to get LILO to boot Linux from /dev/hdd (not that I need to now since I have past my dual booting days with Windows).	JohnD (509)
75742	2002-09-07 04:12:00	I don't know ... but you are probably right. /dev/hda *should* indeed be IDE1, and /dev/hdb IDE2. You can probably tell by watching the screen as it boots (though that goes too fast now). It tells you what disks it knows about. You can see those boot messages by using dmesg. the df ("disk free space" command) will tell you. But But multibooting is a bit fragile at the best of times. There are too many things which can go wrong. The only box I have win (95) and linux on has a straight DOS boot. I then use loadlin to get Linux, because it is a Compaq Deskpro, with the odd maintenance partition which causes problems with LILO. There is a work around, but I have never bothered. My old server setup had Novell NW4.1 on one partition and that was the standard boot. I used a floppy for Linux on that one.	Graham L (2)
75743	2002-09-07 05:03:00	> I don't know ... but you are probably right. :) I think I'll just stick with booting linux from a floppy. It works, and I think I'll just leave it that way until I can get some more 72pin ram for my other computer and move the HDD over into that and run it as my Linux machine. Mike.	Mike (15)
1 2