Comment 0 for bug 222322

Binary package hint: file-roller

The addressing of IDE devices is screwed. Rather than address as hda hdb hdc hdd they are being addressed in Hardy as sda sdb. This works if you only have one IDE drive on hda. It gets misinterpreted as sda, but is functional.

The problem becomes clearly apparent when you start putting hard drives on the secondary IDE controller. For example when you have one drive as master on hda and another as master on the secondary controller on hdc. Only hda is picked up and converted to sda. Unfortunately hdc is not visible. Doing 'fdisk -l' only reports on drives on the primary controller.

Furthermore, in other configurations, I have had only drives on the secondary controller being picked up, with drives on the primary controller invisible.

My hardware is under two years old.

Gutsy works fine. Gutsy correctly addresses my IDE devices.

I have for much of yesterday and today been attempting to install Hardy. But without success. I tried a fresh install of Dapper, and upgrade to Hardy, but that failed with unresolvable dependencies, that did not resolve when instructions to -f install were followed.

So I did a fresh install of Gutsy and upgrade to Hardy. This correctly addressed my IDE devices in Gutsy, but were screwed after the upgrade (otherwise successful) to Hardy.

Being totally disillusioned with Hardy, I installed Fedora Core 8 (just released). Interestingly, the same screwup in IDE addressing occurred there also. So this leads me to believe the source of this show stopper bug, is somewhere upstream.

I am forced to abandon Hardy, and will make do with Gutsy, until a resolution to this bug is made available.

Maybe related to this. On another machine that has no IDE devices connected, the grub bootloader in Hardy failed, and gave the option of LILO during the install. It now is fully functional using the LILO bootloader.