Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-05-29 at 00:35 +1000, Basil Chupin wrote:
DEVICES_FORCE_IDE_DMA="/dev/hda:-c1:-m16:-u1 /dev/hdb:-c1:-m16:-u1 /dev/hdd:-c1:-m16:-u1 /dev/hdc:on" Yeah, but we are talking here about v10.1 which is an animal of a different kind...
True.
OK, this is what I tried and the results.
Firstly, the comment that the params you show above are not the same as you gave in an earlier response so I'll ignore the above and use what you gave
Well, my first one I created for you, taking my real line and leaving only the parameters I thought you needed. Posibly I misstyped something. The second one is the one that I'm actually using.
On both occasions the above statements in /ide were ALTERED to read:
..._DMA=""
Oh, my! :-(
I then used the approach which Silviu provided which was to use /etc/init.d/boot.local.
Yes, that one must work. Time ago, I created my own "/etc/init.d/boot.localhw" service script instead. I'm not using it now, but I might use it again when I install 10.1. Basicly, I run hdparm.
Use a text editor to directly edit the file. Doesn't appear that using anything will stop from something in SuSE amending ../ide to whatever it is "programmed" to do (against your will in fact).
It must be something in hald/devfs/subfs/whatever.
All these things above I found after much time in typing/rebooting/typing/rebooting/typing/ad finitum :-) . I'll never be same...
You sure have saved a lot of time for many of us ;-)
A bit off the mark I am afraid, sorry :-( . I just spent the last 3 days re-installing and re-installing and re-installing 10.1 trying to get that *STUPID* new (or even the old!) software updater to work. It stuffed my system each time so I had to re-install. (And PLEASE, Andreas, don't ask me to put in a bug report 'cause I don't remember all the things I had to do and not do and what worked up to a point - which point? - and what didn't.) Anyway, I am now in a situation where I have got the system running again but without all that crap updating thingie so thta I can at least get back online and "talk" to people. Which now leads me to the comment I just made above.... The setting of DMA now does NOT work. Period. No matter what I do - either what Silviu said or what you said (re using /etc/sysconfig/ide - just doesn't work. It did after the first install of 10.1 and when I wrote the comments earlier in this thread but now, when I went to view a DVD earlier today, I discovered that nothing that I do in putting parameters in control files sets the DMA for the one device that needs the setting to be able to view DVDs correctly - namely, HDB. The ONLY way to have DMA set and working correctly is to to use hdparm on a command line (as root) and only then will the DMA be set and show up as being set in Control Centre/Harware/IDE DMA Mode. The wackiest thing about all this is that even if using 'hdparm -I /dev/hdb' shows that the DMA *is* set (to udma2 in my cse) but unless the DMA is shown as being set in CC/Harware/DAM Mode then the device behaves as a device without DMA. ONLY when CC/Hardware/IDE DMA Mode shows that the DMA is set *then* the device works correctly with DMA set. I have a DVD which starts with a man walking slowly and the camera pans slowly as he is walking and I use this to test whether the DMA is working or not: if the panning/walking is jerky then I know that the DMA is not set. During the re-installation of 10.1 over the past 3 days something did get updated during the first call to the "home base" server so something now has been corrupted, and DMA for hdb cannot be set using /etc/sysconfig/ide or /etc/init.d/boot.local. Command line use of hdparm is only way I can do it - just like I had to do in 10.0. So, we are making progress..... backwards. Cheers. -- Ignorance can be corrected. Stupidity is permanent. -- 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