John D Lamb wrote:
Basil Chupin wrote:
Per Jessen wrote:
Basil Chupin wrote:
The setting of DMA now does NOT work. Period. https://bugzilla.novell.com/show_bug.cgi?id=177959 https://bugzilla.novell.com/show_bug.cgi?id=182885 Thanks for these links. I've read them now but putting thru the suggested fix (ie the symlink) does not solve the problem- the DMA for /dev/hdb still remains OFF. Only way to get it set is to use hdparm -d1c1u1 /dev/hdb as root from a command line.
Just on the off chance that it's some use, I had one disk refusing to set DMA when booting after I installed 10.1. It turns out DMA had been switched off for /dev/hdb in the system BIOS. After hitting DEL on a reboot and changing the detect DMA setting to auto, everything worked fine.
Thanks for this John. I'll check this out at the next boot. The problem with this is that Windows recognises all the devices correctly. When I do 'hdparm -I /dev/hdx' all the 4 devices have the correct udma set - except that hda is set to udma5 when it should be the same as for hdc - udma6 - because both are identical HDs. When one looks at Control Centre/Hardware/IDE DMA Mode, udma is shown as set for hda, hdc and hdd but not for hdb and unless the udma is shown as set here then the device operates with no udma. That is, SuSE depends on what is shown in CC/Hdware/IDE DMA for the dma to be applied to the device. And the only way I can get the dma/udma set for hdb is to use 'hdparm -d1c1u1 /dev/hdb' from a command line. There is a bug report about dma not working correctly on a device hdg I think which Per pointed me at but doing the 'fix' suggested there doesn't do anything. Only the command line approach works (for me). Cheers. -- Indecision is the key to flexibility. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com