HD Install :: wrong drive geometry when not booted with dma
Matt-
I experienced the same problem as you. I ended up doing a frugal install, using the following steps:
1) from the live CD: boot dsl dma
2) partition disk as you desire
3) copy the /usr/sbin/frugal_instal.sh to /home/dsl. The lilo.conf file it makes has nodma set, so search for nodma, and chnage it to dma.
4) run the modified frugal_instal.sh
Let us know if it works!
MarkMark, thanks for the tip....sure enough, the frugal install worked......strange though...and here's why: I modified the mkliloboot script to add dma to the append line in lilo.conf (same as the frugal script) but it didn't work.......
I'm glad i have it booting off the hdd, but i don't want it running out of a ramdisk...and asking for config options every boot. does anyone know the difference between the hdinstall and frugal kernel/lilo options off hand? I'm going to look into this myself, and post whatever i find.
+mattGOT IT!!!!
looks like 0.8.4 fixed this issue. simply booted the cd (without the dma boot option) ran standard hdinstall script, and mkliloboot
no problems booting anymore
thanks to everyone for their help +mattCORRECTION: don't got it....
funny thing is it works if there is a slave on the bus, but if you remove the slave, the kernel panics again.....
here are some errors i noticed earlier in the boot process:
Does the drive, running as a single item on the bus, require a jumper to be set for "single" use, rather than a simple CS setting for the cable in use ?