dma turned off
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
Signature · 9 lines
Peter - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 15 lines · 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.dif that is the place do I put this command?However, giving the command from the console as root after booting I get:
Quoted 7 lines
setting
using_dmato 1 (on)
HDIO_SET_DMAfailed: 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 8 lines · 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. *
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.
Signature · 13 lines
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 [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Thanks Jim!
Quoted 20 lines · On Wed, 10 Nov 2004 23:30:16 -0500 Jim Nelson <[email protected]> wrote:
Quoted 19 lines · 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.dif that is the place do I put this command?However, giving the command from the console as root after booting I get:
setting
using_dmato 1 (on)
HDIO_SET_DMAfailed: Operation not permitted
using_dma= 0 (off)
Quoted 9 lines
Quoted 3 lines
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
Signature · 6 lines
Peter - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 8 lines · 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. *
Quoted 6 lines · [email protected] 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)
Quoted 2 lines
Quoted 2 lines
HDIO_SET_DMAfailed: 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
Signature · 7 lines
Peter - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 4 lines · Richard Adams
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.
Signature · 13 lines
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 [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs