OK, I'm lost...
After spending the better part of a week getting Linux up and running, X
configured decently and LILO working on my NEC Versa notebook, I slam the
machine into the docking station and fire it up. Left-Shift at the LILO prompt
and type Linux....
Loading............. (etc etc)
that a hang on partition check. Remove the notebook from the docking station
and it boots right into Linux.
Here's the config details:
NEC Versa 486-25dx4 (75Mhx)
20 M RAM
340m HDD - 200m FAT on /dev/hda1, 140m Linux Native on /dev/hda2
1M WD90C24 VGA
Active Matrix Display
IBM PCMCIA Token-Ring adapter in slot 0
IBM 16-bit 16/4 Token-Ring adapter
Conner 3034 340m IDE, 100% FAT
Now, I realize when docking the notebook, the drive in the docking station will become the 2nd partition and the Linux Partition becomes the third partition, while when "mobile", the Linux partition is the 2nd one.
With Linux on /dev/hda2, why would the system hang when it comes to the
partition check? The thing boots the kernel from /dev/hda2 just fine.
Does the existance of the 2nd drive (/dev/hdb??) make a difference? (Obviously, it does or the machine wouldn't hang)
What happens if I change my FSTAB entries to show the existance of the 2nd disk?Will it blow up when I'm "mobile"?
Is anyone else runing a similar setup and made it work? I'd really like to
be able to take Linux with me when I'm out in the field...
Hmmm.. I'd been booting from floppy until this morning... Would the kernel on
the HDD possibly be different? In clearer terms, when doing a make zdisk,
is the new kernel put on the floppy? If I were to re-compile the kernel
and do a make zImage instead, would it fly?? :)