Quote:
Originally posted by equinox
I recently gave Slack 10 a bash, booted from the scsi.i kernel because I have a SATA hdd (giga-byte mainboard).
Under CFDISK it lists my hdd as hda / hda1 etc... instead of sda / sda1...
Note that this is under the 2.4.26 kernel.
The install goes fine and I reboot into slackware and all is good. I then want to install the 2.6.7 kernel and do everything as instructed under the README and once I rebooted I get a kernel panic, I have a suspicion that this is because of my /etc/fstab still showing my hdd is hdax instead of sdax, and under the 2.6.7 kernel it wants to load the scsi modules... am I correct?
|
What does dmesg look like in your kernel panic? I had a few before
I got 2.6.7 to work, but how did you get 2.4.26 to boot without a sata
kernel? You're the first I heard to get it working - must be using generic
scsi module.
In 2.6.7 it should load as /dev/sda - you're correct. You need the right
modules for your mobo chipset and hd, then your /etc/lilo.conf should
look something like this.
NB: You don't need an initrd if you have your filesystem built-in
Code:
mingdao@james:~$ cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="apm=power-off"
boot = /dev/hda <- /dev/sda if lilo is in your sata drive
message = /boot/boot_message.txt
prompt
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x64k
vga=791
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Slack-2.6.7
read-only
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windoze
table = /dev/hda
# Windows bootable partition config ends
The problem I had was getting lilo to accept "root = /dev/sda1"
when I had it booting as /dev/hde so don't forget that /etc/fstab
will have to match up with lilo...
