Tim Day wrote:
I have an old dual-P3 Intel STL2 motherboard has been running Etch no
problem (2.6.18 kernel) for ages.
It has an IDE drive (root filesystem and swap, and it boots off it)
(/dev/hda on Etch) and a CD-ROM on the single IDE connector on the
motherboard, and a couple of big SATA drives hanging of some PCI-X card
(/dev/sda and /dev/sdb on Etch).
I upgraded it to lenny following the instructions (yes, setting
LABEL=rootfilesys on /dev/dha1 and changing /boot/grub/menu.lst
appropriately etc) but the 2.6.26 kernel seems to be completely ignorant
of the IDE devices and I just get the "Waiting for root filesystem..."
message. (It can clearly see the SATA drives though).
I can boot back into 2.6.18 no problem (and now via the
LABEL=rootfilesys mechanism).
Alternatively, you can try the UUID=<filesystem-uuid> for mounting the
drive. Another option is to specify the names as sda, sdb, etc.
You can check the output of `tune2fs -l' to determine the necessary
parameters like label, UUID, etc.
In 2.6.18,
dmesg | grep -i ide
lists (edited for relevance):
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus...
SvrWks OSB4: IDE controller at PCI slot 0000:00:0f.1
ide0: BM-DMA at 0x14c0-0x14c7, BIOS settings: hda:DMA, hdb: DMA
ide0: BM-DMA at 0x14c0-0x14c7, BIOS settings: hda:DMA, hdb: DMA
Probing IDE interface ide0...
id0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
But 2.6.26 only says
Uniform Multi-Platform E-IDE driver
ide: Assuming 33MHz system bus...
SvrWks OSB4: IDE controller (0x1166,0x0211 rev 0x00) at PCI slow
0000:00:0f.1
Serverworks_IDE: probe of 0000:00:0f.1 failed with error -16
And once it drops me to the prompt, all I see is the SATA drives.
I'm a bit out of my depth here....
My original assumption was that I'd somehow run foul of the hd*/sd*
renaming issue the release notes make a big deal out of, but the fact my
old 2.6.18 kernel is booting just fine via the new kopts
root=LABLEL=rootfilesys stuff seems to indicate this isn't the case.
Now I'm thinking that the new kernel simply doesn't like my IDE
hardware. Can anything be done about this ? I tried adding
ide0=0x1f0,0x3f6,14
on the kernel command line (based on where 2.6.18 found it); it didn't
make any difference but I later found something at kerneltrap.org
suggesting ide*=... options had been removed by 2.6.26.
Please, any suggestions for how to get the system onto 2.6.26 gratefully
received!
Thanks
Tim
--
If you can't explain it simply, you don't understand it well enough.
-- Albert Einstein
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
