[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-linux-e
Subject:    Re: [SLE] DMA Nightlmare on SuSE 10.x Revisited
From:       Per Jessen <per () computer ! org>
Date:       2006-05-27 10:38:52
Message-ID: e59a7s$2bj$1 () saturn ! local ! net
[Download RAW message or body]

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
https://bugzilla.novell.com/show_bug.cgi?id=117683

> 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 :-)


/Per Jessen, Zürich


-- 
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


[prev in list] [next in list] [prev in thread] [next in thread]