dma turned off

dma turned off

[Peter H.]

Hi,

Slackware 10

When I switch to kernel 2.6.7 I get the following error message on boot:

 * Warning: The dma on your hard drive is turned off. *
 * This may really slow down the fsck process. *

Apparently with the command "hdparm -d /dev/hda" dma is turned on.

Where in /etc/rc.d if that is the place do I put this command?

However, giving the command from the console as root after booting I get:

setting using_dma to 1 (on)
 HDIO_SET_DMA failed: Operation not permitted
 using_dma    =  0 (off)

How to resolve?

Thanks & regards
-- 
Peter



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: dma turned off

[Jim Nelson]

Peter H. wrote:
> Hi,
> 
> Slackware 10
> 
> When I switch to kernel 2.6.7 I get the following error message on boot:
> 
>  * Warning: The dma on your hard drive is turned off. *
>  * This may really slow down the fsck process. *
> 
> Apparently with the command "hdparm -d /dev/hda" dma is turned on.
> 
> Where in /etc/rc.d if that is the place do I put this command?
> 
> However, giving the command from the console as root after booting I get:
> 
> setting using_dma to 1 (on)
>  HDIO_SET_DMA failed: Operation not permitted
>  using_dma    =  0 (off)
> 
> How to resolve?
> 
> Thanks & regards

What kind of hard drive and IDE chipset does it have?  I know some drives were 
recently added to a no-DMA blacklist for behaving badly.  Normally, dma is 
supposed to be enabled by default, and only disabled when a known-bad hard drive 
or IDE controller is found.


On my Slack 10.0 server, I put hdparm in rc.local.  My rc.local:

(most of the disk storage is on SCSI drives, /dev/hda is just the boot drive due 
to a POS BIOS that can't boot off of expansion cards)

#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local setup commands in here:
 

# enable 32-bit mode, turn on APM, set spindown for 1 hour,
# unmask IRQ's, nd set the keep-settings flag for /dev/hda
hdparm -c 1 -B 128 -S 242 -u 1 -k -q /dev/hda
 

# get the date from VT's NTP server and start the local time server
ntpdate ntp-1.vt.edu
ntpd &
 

#start the SMART monitoring tools
smartd &

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: dma turned off

[Peter]

Thanks Jim!

On Wed, 10 Nov 2004 23:30:16 -0500
Jim Nelson <james4765@verizon.net> wrote:

> Peter H. wrote:
> > Hi,
> > 
> > Slackware 10
> > 
> > When I switch to kernel 2.6.7 I get the following error message on boot:
> > 
> >  * Warning: The dma on your hard drive is turned off. *
> >  * This may really slow down the fsck process. *
> > 
> > Apparently with the command "hdparm -d /dev/hda" dma is turned on.
> > 
> > Where in /etc/rc.d if that is the place do I put this command?
> > 
> > However, giving the command from the console as root after booting I get:
> > 
> > setting using_dma to 1 (on)
> >  HDIO_SET_DMA failed: Operation not permitted
> >  using_dma    =  0 (off)
> > 
> > How to resolve?
> > 
> > Thanks & regards
> 
> What kind of hard drive and IDE chipset does it have?  I know some drives were 
> recently added to a no-DMA blacklist for behaving badly.  Normally, dma is 
> supposed to be enabled by default, and only disabled when a known-bad hard drive 
> or IDE controller is found.
> 
hdparm -i /dev/hda

 Model=Maxtor 2F040L0, FwRev=VAM51JJ0, SerialNo=F1J91XNE
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=4047/16/255, CurSects=16511760, LBA=yes, LBAsects=80293248
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: (null): 

I think it is kernel related since with kernel 2.4.26 in slackware I do not get those error messages neither in Fedora Core2 with kernel 2.6.5.... on the same HD.

Regards

-- 
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: dma turned off

[Richard Adams]

On Thursday 11 November 2004 04:13, Peter H. wrote:
> Hi,
>
> Slackware 10
>
> When I switch to kernel 2.6.7 I get the following error message on boot:
>
>  * Warning: The dma on your hard drive is turned off. *
>  * This may really slow down the fsck process. *

I suggest you use www.google.com/linux and type in "2.6.7 DMA" (without 
quotes), lots of hints there on 2.6.x kernels and DMA.

I would go as far as saying its NOT you or your hardware at fault,many have 
problems with DMA and friends at the minute.
One draw back of using an up to date kernel which has not been widely tested.

-- 
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: dma turned off

[Peter]

On Thursday 11 November 2004 04:13, Peter H. wrote:
> Hi,
>
> Slackware 10
>
> When I switch to kernel 2.6.7 I get the following error message on boot:
>
>  * Warning: The dma on your hard drive is turned off. *
>  * This may really slow down the fsck process. *


pa3gcu@zeelandnet.nl said:
> I suggest you use www.google.com/linux and type in "2.6.7 DMA" (without
> quotes), lots of hints there on 2.6.x kernels and DMA.

> I would go as far as saying its NOT you or your hardware at fault,many have
> problems with DMA and friends at the minute. One draw back of using an up to
> date kernel which has not been widely tested. 

That's what I did before posting on the subject. That's why I asked where to 
put hdparm -d 1 /dev/hda in /etc/rc.d since the error message comes early on 
booting and putting it into rc.local it will be executed at the end of boot. I 
put it into rc.S and still get the error message:

 setting using_dma to 1 (on)
> >  HDIO_SET_DMA failed: Operation not permitted
> >  using_dma    =  0 (off)

Further when booted with 2.6.7 kppp takes again 22 seconds to come up against 
11 with 2.4.26. Therefore I resign from the idea of using kernel 2.6.7.

Signing off. Thanks everybody for the help, much appreciated.

Regards
-- 
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: dma turned off

[Richard Adams]

On Thursday 11 November 2004 16:58, Richard Adams wrote:
> I would go as far as saying its NOT you or your hardware at fault,many have
> problems with DMA and friends at the minute.
> One draw back of using an up to date kernel which has not been widely
> tested.

Sorry it took me a long while to reply and i must admit i seem to have lost 
your reply to this mail and the other mails of this thread, so i am now 
talking blind as i cant seem to find the archives anymore anywhere.

I seem to remember you mentioning that you had compiled a new kernel.???
If that is true then maybe you did not define your IDE chipset, if that is the 
case then that is your problem as the kernel will fall back onto, "slow but 
works on anything" sort of arrangement.
The command 'lspci' should say what the chipset is, then 
checkout /usr/src/linux/config and make sure you have defined support for 
that chipset.

-- 
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: dma turned off

[Richard Adams]

On Tuesday 16 November 2004 05:01, Peter wrote:
> Thank you so much Richard!
>
> pa3gcu@zeelandnet.nl said:
> > I seem to remember you mentioning that you had compiled a new kernel.???
> > If that is true then maybe you did not define your IDE chipset, if that
> > is the case then that is your problem as the kernel will fall back onto,
> > "slow but works on anything" sort of arrangement. The command 'lspci'
> > should say what the chipset is, then  checkout /usr/src/linux/config and
> > make sure you have defined support for that chipset.
>
> In my last mail I said I give up on the idea of installing kernel 2.6.7 in
> Slackware10 since I could not produce any sound and programs like kppp took
> twice as long to load than with 2.4.26 and dma could not be turned on.
>
> Now as per your advice I had one last try and behold there is now sound and
> same loading speed for kppp as in 2.4.26 and dma is turned on.
>
> My chipset is of VIA Technologies. Since make xconfig gives an error with
> 2.6.7 I am using menuconfig in which I have a hard time finding things like
> VIA. So I went into .../linux/.config searched for VIA82xxx set them to =y
> then
> make, cat bzImage > vmliz, lilo and there it was.

I'm old fashioned about things, i always use 'make config' but i also cheat a 
lot and edit .config and then use 'make oldconfig' that way one only gets to 
answer newly found changed configuration.

> Except the sound is very faint and I have to make aumix -L first to have
> full sound. No problem I put that into .profile. Apparently the setting is
> lost when shutting down unlike in 2.4.26.

Use  alsa's programs to set your sound 'alsactl' 'alsamixer' etc etc.

> On boot I still get the error meassge:
>
> FATAL: Module snd_pcm_oss not found.
> FATAL: Module snd_mixer_oss not found.

Could be old entries in /etc/modules.conf confusing module loading.

A good place to get hints is;
http://www.djcj.org/LAU/guide/index.php
Has many links as well.

>
> Regards

-- 
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: dma turned off

[lindax newbie]

2.6.7 was an "odd" numbered kernel...:-)
I found it to be too unstable to use though 2.6.5 (odd as well, shoots 
my theory)
seemed stable.  Linus is trying to get lots of bug fixes into the 
current kernel
and release a "stable" kernel again.  I guess even he realized that the 
2.6 series
had evolved into a 2.7-type kernel (developer/unstable) kernel as to make it
unusable for so many as to potentially start hurting their "test" base.

The idea, before, was that only stable things were tried or back ported 
into the
stable kernel, but Linus in his genius, declared that those who wanted 
stable
kernels would henceforth get them from "distros", and he didn't need no 
testbase
for an even number series...  Some of us had hoped that the 2.6 series 
wouldn't evolve
into an unstable 2.7 series named 2.6.x so we could continue to be 2nd 
line testers
for stable releases, but that has not proved to be the case (noticably 
for 2.6.7).
I used to only use vanilla even release kernels, but have been forced 
back to vendor
kernels for newer installs.  Hopefully the current stable release, when 
it comes out,
will be more stable.  Haven't been following it that closely now and 
they don't
get announced regularly on "/." (or I'm missing some "/.-age").

Of course the last stable release from my vendor wouldn't boot or update 
any of
my systems since XFS was broken in the vendor (SuSE's) stable 
release....so much
for vendor stability.  :-(  Yeah, they had a patch, but that didn't help 
if you
needed to be online to download the patch -- their CD/DVD-installer 
doesn't handle
proxies. :-(

-l

Peter wrote:

>Thank you so much Richard!
>
>pa3gcu@zeelandnet.nl said:
>  
>
>>I seem to remember you mentioning that you had compiled a new kernel.??? If
>>that is true then maybe you did not define your IDE chipset, if that is the
>>case then that is your problem as the kernel will fall back onto, "slow but
>>works on anything" sort of arrangement. The command 'lspci' should say what
>>the chipset is, then  checkout /usr/src/linux/config and make sure you have
>>defined support for that chipset.
>>    
>>
>
>In my last mail I said I give up on the idea of installing kernel 2.6.7 in 
>Slackware10 since I could not produce any sound and programs like kppp took 
>twice as long to load than with 2.4.26 and dma could not be turned on.
>
>Now as per your advice I had one last try and behold there is now sound and 
>same loading speed for kppp as in 2.4.26 and dma is turned on.
>
>My chipset is of VIA Technologies. Since make xconfig gives an error with 
>2.6.7 I am using menuconfig in which I have a hard time finding things like 
>VIA. So I went into .../linux/.config searched for VIA82xxx set them to =y 
>then
>make, cat bzImage > vmliz, lilo and there it was.
>
>Except the sound is very faint and I have to make aumix -L first to have full 
>sound. No problem I put that into .profile. Apparently the setting is lost 
>when shutting down unlike in 2.4.26.
>
>On boot I still get the error meassge:
>
>FATAL: Module snd_pcm_oss not found.
>FATAL: Module snd_mixer_oss not found.
>
>Regards
>
>  
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs