hi people
I'm running debian on an AUSUS P4C800 mainboard, and recently purchased a maxtor SATA drive.
with the kernel that came with the install (2.4.25-1-386) I can access my drive at /dev/hde. transfer rate is as good as with the IDE / Dual ATA drive, say around 60MB/sec
I tried compiling a 2.6.8.1 kernel, and when I use this one I can't see my hd anywhere, neither on /dev/hde, nor on /dev/sd
when I try to compile 2.6.8.1 with /boot/
config-2.4.25-1-386 I get this at boot:
Code:
VFS: Cannot open root device "hda5" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
/ is on a reiserfs partition (hda5), reiserfs support is built hard in the kernel (and 2.4.25- still manages to boot on it while it's built as a module)
I've tried using a config file from someone who apparently managed to get his SATA drive on the intel ICH5 controler, and that didn't work out.
I've tried adding all options to my kernel, but compiling crashes due to errors
the config I use now for my 2.6.8.1 is
here, it works great except for the lack of support of my sata drive and i2c hardware sensors (why?)
does some-one out here have anymore ideas of things I could try, or tests I could run to see JUST HOW my 2.4 kernel manages to access my SATA drive?
---------------------------[ editing post after continuing my experiments ]--------------------
so.. after palying around with it a little more, I tried a few things: I thought "if my 2.4 kernel can't boot straight off the SATA drive, maybe it's because it's loaded as a module. so I checked the outpu of lsmod, mounted the SATA drive, and checked again: no difference.
before I continue, I must say this:
2.4 kernel:
-----------------
no network
no audigy2
SATA available
2.6.8.1 kernel:
-----------------------
network is fine
audigy is fine
no SATA
that's it. now for the weird bit. when loading on the 2.4 kernel, at some point I get this (pulled out from /var/log/dmesg) [#1]
Code:
ICH5: IDE controller at PCI slot 00:1f.1
PCI: Enabling device 00:1f.1 (0005 -> 0007)
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio
ICH5-SATA: IDE controller at PCI slot 00:1f.2
ICH5-SATA: chipset revision 2
ICH5-SATA: 100% native mode on irq 18
ide2: BM-DMA at 0xef60-0xef67, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xef68-0xef6f, BIOS settings: hdg:pio, hdh:pio
with the 2.6.8.1, I only see that: [#2]
Code:
ICH5: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio
(I must say something else: for test purposes the two hard drives have about the same contents)
now, according to #1 (see "code" above); set my setting my /boot/grub/menu.lst to
Code:
title Debian GNU/Linux, kernel 2.6.8.1 (on SATA?)
root (hd2,0)
kernel /vmlinuz-2.6.8.1 root=/dev/hde5 ro
boot
that got me something like "disk doesn't exist"
so I set it to
Code:
title Debian GNU/Linux, kernel 2.6.8.1
root (hd1,0)
kernel /vmlinuz-2.6.8.1 root=/dev/hdc5 ro
boot
that boots, but then I get a kernel panic.
with root=/dev/hde5 I get a kernel panic too.
with
Code:
title Debian GNU/Linux, kernel 2.6.8.1
root (hd1,0)
kernel /vmlinuz-2.6.8.1 root=/dev/hda5 ro
boot
it boots alright, but I still don't have access to my SATA drive. now how strange is that ???
if there's something that seems unclear to you, please ask me for details... I'm starting to get real worried about my mental sanity ;-) so I'll be pleased to explain and try whatever you may think of
