Mailinglist Archive: opensuse (5130 mails)

< Previous Next >
Re: [SLE] DMA Nightlmare on SuSE 10.x Revisited
  • From: Basil Chupin <blchupin@xxxxxxxxxx>
  • Date: Mon, 29 May 2006 00:57:20 +1000
  • Message-id: <4479BA50.7050909@xxxxxxxxxx>
Per Jessen wrote:
Basil Chupin wrote:

supposed to. If the setting does not survive a reboot, your BIOS is
resetting it. But you also said FORCE_DMA is not working - which is
probably worth reporting as hdparm is ok.
The setting survives reboots so it is now OK.

The FORCE_DMA didn't work as per my original post and since receiving
the advice from you, Silviu and Carlos, and fiddling with different
settings, I have found that doing anything in /etc/sysconfig/ide does
NOT work.

/etc/sysconfig/ide will set the variable DEVICES_FORCE_IDE_DMA, which in
10.0 was used by the boot.idedma init-script. This functionality has
been moved to a udev script.
It seems to have happened in 10.1, probably as a result of

I've looked at that bugzilla listing. Methinks that it wasn't done correctly - a on-the-run fix which did not produce the right result for the majority of people, only for those which have a CD ROM which is /dev/hdg :-( .

What am I comparing the results to?
Firstly, both HDs are identical.

Yes, but that is a matter of specifications, not current settings. Of
course, if YaST shows a drive set to an unsupported DMA-mode, something
isn't quite right :-)

I now have a bit more knowldge about hdparm and now know that there are 2 options for it which happen to produce 2 different results. These options are -i and -I.

I used on all the 4 devices I have (just to review: hda=Maxtor 250GB; hdb=CD ROM; hdc=Maxtor 250GB; hdd=Pioneer 110) and ran hdparm -i and then hdparm -I on all 4 devices. I won't bother with giving results for hdb and hdd but for hda and hdc are shown below because as I said they are identical HDs but are treated differently by SuSE.

hdarm -i hdparm -I

hda mdma0 to mdma2 mdma0 to mdma2
udma0 to udma2 udma0 to udma6 (5 set) <=============

hdc mdma0 to mdam2 mdma0 to mdma2
udma0 to udma6 (6 set) <===== udma0 to udma6 (6 set) <============

Whatever all this means I don't know, but something is not kosher somewhere especially when Windows recognises everything correctly :-) .


Ignorance can be corrected. Stupidity is permanent.

< Previous Next >