> The ATA adapter is embedded into the motherboard. Looking at the board, > the chipset reads Cyrix Cx5530. There is some contradictory information > about whether this chip supports DMA or not. Regarding the CF, i am The CS5530 supports UDMA, the CF card may well support UDMA but there is a third ingredient in the CF cases - whatever connects the two must support UDMA. A lot of (especially older) CF convertors, CF cards slots on boards and the like do not even have the required wiring present, others don't have to to the standard needed for UDMA. > ata1.00: ATA-5: SILICON POWER, 2.0, mas UDMA/66 Your CF card reports that it supports UDMA so I am quite sure it does. > sd 0:0:0:0: [sda] 2000880 512-byte hardware sectors (1024 MB) > sd 0:0:0:0: [sda] Write Protect is off > sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't > support DPO or FUA So PIO works and DMA doesn't. > Does this give any interesting info to the problem? It matches the other driver behaviour which is very helpful. > PS: Since i cannot provide parameters to the kernel, i don't know how > the kernel i have completely working (2.6.22.15) figure out that he > should continue boot from root=/dev/hda1. This kernel does not seem to > get to that conclusion. It would be /dev/sda1. I've no idea how the firmware bootloader passes information to the kernel on your netvista. You could see if the old rdev stuff is used (rdev /vmlinuz /dev/sda1) For the PIO find static int libata_dma_mask = .... In drivers/ata/libata-core.c and change it to = 0; -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
