The problem I reported once, still exist in 2.4.19. See my previous emails
for the reference:
http://marc.theaimsgroup.com/?l=linux-kernel&m=102495067602135&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=102277249800423&w=2
It is fixed in -ac series though.
As Bartek Zolnierkiewicz pointed me, the problem was introduced by two
factors:
- checking the return value of pci_enable_device(dev)
- some settings problem with PCI resources -- BIOS/controller does
prepare them for XP
(these are more-less Bartek's words).
What helped me was using fixup_device_piix() from -ac in
ide_scan_pcidev(). My controler's ID is DEVID_ICH3M.
It is used in a different, more generic way in -ac, so I don't post the
patch.
Alan, Marcelo: is there any chance that this change will be ported from
-ac in 2.4.20?
many thanks to Bartek,
pkot
-- mailto:pkot@linuxnews.pl :: mailto:pkot@slackware.pl http://kt.linuxnews.pl/ :: Kernel Traffic po polsku
- 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/