2.4.18 (and maybe earlier versions) can't see my IDE disks where 2.2 can

Nix (nix@esperi.demon.co.uk)
30 Jun 2002 20:22:34 +0100


I'm using a ten year old 486 as a firewall, with an aged transparent
2.5Mb Promise caching IDE controller managing a couple of fairly
bog-standard IDE disks (one a 420Mb 1989-vintage Western Digital of some
kind, the other a 1994-vintage 1Gb IBM disk). I can't find out the model
numbers without taking the machine to pieces, because even with 2.2.20
the (new) ide driver says

Jun 30 00:33:50 esperi kernel: hda: non-IDE drive, CHS=2047/16/63
Jun 30 00:33:50 esperi kernel: hdb: non-IDE drive, CHS=895/15/62
Jun 30 00:33:50 esperi kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

but then it finds the partitions OK:

Jun 30 00:33:50 esperi kernel: Partition check:
Jun 30 00:33:50 esperi kernel: hda: hda1 hda2 hda3 < hda5 hda6 hda7 > hda4
Jun 30 00:33:50 esperi kernel: hdb: hdb1 < hdb5 hdb6 hdb7 >

2.4 doesn't get anywhere near this far. It finds the IDE controller but
fails to find any of the attached drives, and panics because it can't
mount /.

When I try to force it with kernel parameters, viz `hda=2047,16,63
hdb=895,15,62', it says

hda6: bad access: block=2, count=2
end_request: I/O error, dev 03:06 (hda), sector 2

and then panics because it can't mount root.

I must admit to not knowing where to start debugging this one.

The old disk-only driver works OK with this machine, but it doesn't
support IRQ-based transfer that I can see, with the result that my
16450 UART is dropping incoming packets like confetti :((((

(log from the old driver starting up in 2.4:

Jun 30 13:00:44 esperi kernel: hda: 1007MB, CHS=2047/16/63
Jun 30 13:00:44 esperi kernel: hdb: 406MB, CHS=895/15/62
Jun 30 13:00:44 esperi kernel: Partition check:
Jun 30 13:00:44 esperi kernel: hda: hda1 hda2 hda3 < hda5 hda6 hda7 > hda4
Jun 30 13:00:44 esperi kernel: hdb: hdb1 < hdb5 hdb6 hdb7 >

pretty uninformative, really.)

Anyone got any idea how I could start to debug this? I could really do
with a driver that supports IRQ on this machine...

-- 
`What happened?'
                 `Nick shipped buggy code!'
                                             `Oh, no dinner for him...'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/