SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello!
I am running Slackware Linux-12.1 with kernel-generic-smp-2.6.24.5-smp, a fresh new installation. Recently I started getting the following messaged during booting. Earlier they appeared at some boots only but now they appear whenever I boot up the machine. Here they are:
Warning: The dma on your hard drive is turned off.
This may really slow down the fsck process.
I never got these messages in Slackware-12.0.
Here is some info:
dmesg | grep ide
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdcMA, hddMA
Probing IDE interface ide0...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33
ide1 at 0x170-0x177,0x376 on irq 15
ide-floppy driver 0.99.newide
ide: failed opcode was: unknown
ide0: reset: success
If I try to manualy hdparm -d1 /dev/hda, the command succeeds and there is dma on both hard drives.
My question is whether there is a hardware problem on my system, how to check whether it indeed is a hardware problem. Or what I could do to turn dma on at boot so that these messages do not appear. My system seems to run appreciably slower.
If you notice extremely long wait times when formatting partitions in the
installer, and you're installing on a Thinkpad that has a SATA drive, it's
possible that the wrong driver is being used, which disables DMA on the drive
(and could happen on other machines). A bit more detail about it is here: http://www.thinkwiki.org/wiki/Proble...stem_hard_disk
Try passing "hda=noprobe" to the kernel when booting the installer, and it
should use the correct libata driver.
Are your drives SATA drives, and being recognized as /dev/hda instead of /dev/sda? Does passing the "hda=noprobe" option to LILO fix the problem?
Are your drives SATA drives, and being recognized as /dev/hda instead of /dev/sda? Does passing the "hda=noprobe" option to LILO fix the problem?
My drives are hda (at least this setting has always worked so far, I have been using Slackware since 10.2 with the same hardware). Passing "hda=noprobe" makes the hard drive invisible for the system. I resinstalled twice afresh as I made a complete mess trying to solve this issue. I also booted into windows to make sure that the hardware is ok. Now I booted into Linux and there seems to be no problem, no kernel parameters are passed to lilo. Odd. If the issue is solved I do not know what actually solved it. After other clean reinstallations dma was still disabled. Maybe booting into windows did the trick? Actually windows is on the older hard drive, /dev/hda and when I passed hda=noprobe to the kernel, dma was ok. I have no idea.
I reinstalled the system several times so far to make sure that this is not due to some so. My final conclusion is that probably after a power failure something went wring with my windows drive (/dev/hda). After booting into windows, the message disappeared while booting Linux.
Now I no more get these messages during boot. The problem is that "hdparm -d /dev/hda" and "hdparm -d /dev/hdb" both say that dma is off. My system runs fairly slowly until I issue "/hdparm -d 1 /dev/hda" and "hdparm -d 1 /dev/hdb". Then hdparm reports that dma is on (dma=1) for both hard drives. Isn't dma supposed to be enabled by default? Should I add these commands to rc.local or some other more appropriate place?
Here is some info from my syslog:
May 30 14:55:25 marto kernel: hdb: ST3160812A, ATA DISK drive
May 30 14:55:25 marto kernel: hda: Maxtor 6E040L0, ATA DISK drive
May 30 14:55:25 marto kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
May 30 14:55:25 marto kernel: hdd: TEAC CD-W552E, ATAPI CD/DVD-ROM drive
May 30 14:55:25 marto kernel: hdc: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive
May 30 14:55:25 marto kernel: hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33
May 30 14:55:25 marto kernel: ide1 at 0x170-0x177,0x376 on irq 15
May 30 14:55:25 marto kernel: ide-floppy driver 0.99.newide
May 30 14:55:25 marto kernel: Driver 'sd' needs updating - please use bus_type methods
May 30 14:55:25 marto kernel: Driver 'sr' needs updating - please use bus_type methods
May 30 14:55:25 marto kernel: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
May 30 14:55:25 marto kernel: raid6: int32x1 473 MB/s
May 30 14:55:25 marto kernel: raid6: int32x2 645 MB/s
May 30 14:55:25 marto kernel: raid6: int32x4 752 MB/s
May 30 14:55:25 marto kernel: raid6: int32x8 455 MB/s
May 30 14:55:25 marto kernel: raid6: mmxx1 1665 MB/s
May 30 14:55:25 marto kernel: raid6: mmxx2 2109 MB/s
May 30 14:55:25 marto kernel: raid6: sse1x1 966 MB/s
May 30 14:55:25 marto kernel: raid6: sse1x2 1833 MB/s
May 30 14:55:25 marto kernel: raid6: sse2x1 2129 MB/s
May 30 14:55:25 marto kernel: raid6: sse2x2 2256 MB/s
May 30 14:55:25 marto kernel: raid6: using algorithm sse2x2 (2256 MB/s)
May 30 14:55:25 marto kernel: Using IPI No-Shortcut mode
May 30 14:55:25 marto kernel: intel_rng: Firmware space is locked read-only. If you can't or
May 30 14:55:25 marto kernel: intel_rng: don't want to disable this in firmware setup, and if
May 30 14:55:25 marto kernel: intel_rng: you are certain that your system has a functional
May 30 14:55:25 marto kernel: intel_rng: RNG, try using the 'no_fwh_detect' option.
May 30 14:55:25 marto kernel: rtc_cmos: probe of 00:02 failed with error -16
May 30 14:55:25 marto kernel: ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
May 30 14:55:25 marto kernel: videodev: "QCM USB Camera" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
May 30 14:55:25 marto kernel: fuse init (API version 7.9)
May 30 14:55:25 marto kernel: lm85 0-002e: Client (0,0x2e) config is locked.
May 30 14:55:48 marto kernel: hdb: dma_intr: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
May 30 14:55:48 marto kernel: hdb: dma_intr: error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound AddrMarkNotFound }, LBAsect=1647103278975, high=98175, low=98175, sector=301759
May 30 14:55:48 marto kernel: ide: failed opcode was: unknown
May 30 14:55:50 marto kernel: ide0: reset: success
Both drives are correctly recognized. However, there are some error messages that I do not know what to think of.
Thank you for your responsiveness. Regards, Martin
Sorry for cross-posting. I didn't notice that in my previous post the second sentence is unfinished. It should read:"I reinstalled the system several times so far to make sure that this is not due to something that I messed up after the installation."
I would also ask if I should suspect a hardware problem and consult a computer service? What would you recommend?
What does 'hdparm -i /dev/hda' & '/hdparm -i /dev/hdb' show? The 'i' flag is for boot time information.
After that issue the 'hdparm -I /dev/hda' & 'hdparm -I /dev/hdb'. The 'I' flag is direct from the HDD.
Do you have the newer '80 conductor' cable for your HDD?
Edit: It is easier to read a post when long list or data is placed within the vbcode tags. These tags are at the top of the reply window; Quote or Code tag.
Last edited by onebuck; 05-30-2008 at 09:10 AM.
Reason: request vbcode tags
What does 'hdparm -i /dev/hda' & '/hdparm -i /dev/hdb' show? The 'i' flag is for boot time information.
After that issue the 'hdparm -I /dev/hda' & 'hdparm -I /dev/hdb'. The 'I' flag is direct from the HDD.
I turns out that after some boots dma is on, and after others it is off. Sometimes even during the boot up process I get the warning that dma is disabled and of course at these times it is off and booting is slow. At other times booting seems fast, no dma warnings, but hdparm says that dma is off. This time after I booted dma was on, so everything was ok. I will now post you the result of the above commands and later when after booting I have no dma, I will also post the results.
Quote:
Originally Posted by onebuck
Do you have the newer '80 conductor' cable for your HDD?
I do not know that (probabbly I will have to open my PC box to check). However I can say that the Maxtor drive (/dev/hda, where Windows is) is since 2003. The ST3160812A drive is newer - since 2006.
Code:
root@marto:~# hdparm -i /dev/hda
/dev/hda:
Model=Maxtor 6E040L0, FwRev=NAR61590, SerialNo=E1600PPE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, 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: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
root@marto:~# hdparm -I /dev/hda
/dev/hda:
ATA device, with non-removable media
Model Number: Maxtor 6E040L0
Serial Number: E1600PPE
Firmware Revision: NAR61590
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 0
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 80293248
device size with M = 1024*1024: 39205 MBytes
device size with M = 1000*1000: 41110 MBytes (41 GB)
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 0
Advanced power management level: disabled
Recommended acoustic management value: 192, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_VERIFY command
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
Advanced Power Management feature set
SET_MAX security extension
* Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
Checksum: correct
root@marto:~# hdparm -i /dev/hdb
/dev/hdb:
Model=ST3160812A, FwRev=3.AAJ, SerialNo=5LS4GJAM
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=312581808
IORDY=on/off, tPIO={min:240,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
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
root@marto:~# hdparm -I /dev/hdb
/dev/hdb:
ATA device, with non-removable media
Model Number: ST3160812A
Serial Number: 5LS4GJAM
Firmware Revision: 3.AAJ
Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 312581808
device size with M = 1024*1024: 152627 MBytes
device size with M = 1000*1000: 160041 MBytes (160 GB)
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = ?
Recommended acoustic management value: 208, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 1 determined by the jumper
Checksum: correct
I googled the Internet and seems that other guys have the same problem: dma is randomly on or off after booting, and sometimes is off during boot up as well. In my case however, I can ALWAYS successfully turn dma on manually after booting, if it has been off.
As well as the good info posted above by others, some BIOSs have options for turning DMA [on|off|auto|PIO[123]|UDMA[12345]} when booting the system.
I'd guess that an "auto" setting *could* result in random on or off settings at boot, but that's a guess.
Do check for that 80-wire cable too, and that the master drive is at the END of the cable, and any slave drive is in the MIDDLE plug.
Finally, if you were wondering (I think I saw mention of it above) a great place for hdparm commands to be executed at startup is in the /etc/rc.local script.
Sasha
PS - for the record, AFAIK from reading, SATA drives have DMA enabled automatically by default, I suppose provided that the correct driver is in use too.
Last edited by GrapefruiTgirl; 05-30-2008 at 11:42 AM.
Finally, if you were wondering (I think I saw mention of it above) a great place for hdparm commands to be executed at startup is in the /etc/rc.local script.
I'm assuming you mean /etc/rc.d/rc.local in Slackware.
Do check for that 80-wire cable too, and that the master drive is at the END of the cable, and any slave drive is in the MIDDLE plug.
Thank you very much for your reply. Actually the hard drive supposed to be master was at the middle (gray) slot of my 80-conductor cable (though its jumper was set to master) and the slave one was at the end of the cable (the black slot) and its jumper was not set at all. What I did is put the master at black slot and the slave at the grey slot. I also set the slave's jumper to "cable select". I rebooted twice and it seems that everything is ok, dma was on. BIOS also correctly recognizes the two hard drives and says that ULTRA DMA is enabled on both of them. The 80 conductor cable is also detected. Time will show if the problem is ultimately solved.
Thank you very much for your responsiveness.
Regards,
Martin
PS It might be a dull question, but I would also like to ask if there is any sense in reinstalling the operating system not that the hardware setting have changed.
Well, if all is working, I see no reason at all to reinstall the OS. If anything happens to be slightly misconfigged (which I doubt) by rearranging the drives, I would just watch for that and fix it. Reinstalling seems at this point to be needless.
Also, if you do a bit of research about the ATA/IDE standards over the years, you will read that CS (cable select) is an invention/idea that did not really take off, and that has not been standardized nor implemented as intended by most HW and SW vendors. If anything, it has potential to give you grief at some point, if it does anything at all. If it were me, I would change that jumper from CS to Slave.
Also, if you do a bit of research about the ATA/IDE standards over the years, you will read that CS (cable select) is an invention/idea that did not really take off, and that has not been standardized nor implemented as intended by most HW and SW vendors. If anything, it has potential to give you grief at some point, if it does anything at all. If it were me, I would change that jumper from CS to Slave.
Sasha
Actually I set the jumper to "cable select" because I did not see how to set it to "slave". At the instructions at the hard drive there is a specification for "master=on, slave=off" and "cable select". I did not see an option for "master=off,slave=on" or something like that. Probably I will ask a friend of mine to solve this.
If you look closely at the drive housing, there is often the settings of the jumpers stamped or engraved into the metal. Alternately, many have a sticker on the drive showing the settings.
If I remember right, a drive with NO jumper at all will default to Slave, if there is a master present. Don't quote me here though.
Above all, if it works, go with it and leave it on CS unless you learn otherwise.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
MA, hdb
Sasha
