On Wednesday April 18 2007 10:14 am, Sunny wrote: > On 4/18/07, Jess Jackson <[EMAIL PROTECTED]> wrote: > > Hi Sonny: > > > > I guess it is good not to be alone. Are you having trouble with any > > other settings besides the DMA becoming disabled? > > > > Jess > > Not so far. And actually this is not the setting itself. I would guess > that YaST just uses hdparm behind the scenes - so when you set it, it > executes the command and sets it, but then when you open YaST again, > it reads the real drive status and displays that DMA is not enabled. I > may be wrong, of course. > > -- > Sunny
I've seen this happen also with version 1.x of k3b. Never had a problem with DMA being disabled like that before. I did not note exact versions of software at the time because I was making several system wide changes. I will be building the system back up to the latest versions from a base openSUSE 10.2 install so I'll pay attention this time... Stan -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
