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.
This is my first time try Slackware (before is Red Hat,Mandrake, Mandriva, Suse). The default kernel of Slackware is 2.4.x, I updated to 2.6.21.1, still got the errors as belows.
When I booting I got this message
Code:
"Warning: The DMA on your harddisc id turned off
This may realy slow down fsck process."
But why when I #hdparm -d 1 /dev/hda:
Code:
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
My IDE:
Code:
# lspci
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
here is my kernel messages
Code:
#dmesg
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
Could someone explain me why and how to solve this problem?
Is "hda: no DRQ after issuing MULTWRITE_EXT" related to "DMA"? Because I wonder why my LED hard drive light indicator "get on" by itself so many times even I my computer is on idle. I guess my hard disc light indicator "get on" even my computer is idle and still everytime I got those kernel messages.
Code:
"hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success"
Is this the reason why when I my Slackware "Hang" / CRASH. ??? My thought is, my computer crash because I got a bunch full of those messages:
Linux supposed to be a stable OS, even Slackware. How come my computer crash ???
My kernel version is 2.6.21.1
WHat type of computer and hard-disk is that? You can Google the error messages and come up with lots of reading about it. It isn't Slackware's fault, and it likely isn't the kernel's fault either.
I just replaced an already brand new hard disk because it apparently was defective. It gave me loads of similar messages, and also DMA_IRQ Drive-seek blah blah errors, and my drive light would stay on for 15 or 20 minutes without doing anything, and my system would crash sometimes... My thread is here: http://www.linuxquestions.org/questi...d.php?t=550842 for your perusal.
Might be unrelated to my issue, but mine was related to DMA, but DMA itself wasn't the problem, atleast not alone. Between the drive being defective, poor memory timings/clock speeds, and/or crappy or non-DMA enabled IDE cables, you could get errors such as those..
I have a new hard drive installed now, same model, and everything is running perfectly again.
Here's something for you to try -- you should have the 'smartmon' tool kit in your slackware.Run this in a console:
smartctl --all /dev/hda
and your hard drive (if it is SMART enabled) will show you a bunch of stuff, among which will be a table of results from any/all SMART-self diagnostic tests it has done on itself. Look for failed or incompleted tests as an indicator of drive problems.
You can type 'smartctl -h' for help or 'man smartd' or 'man smartctl' for more info on this.
Last edited by GrapefruiTgirl; 05-06-2007 at 09:00 PM.
If it still works in other OS'es like Debian, I can't see why it shouldn't work in Slack. If there are some problems using them too, so it's not Slack but most probably your hard drive problems.
Can you check the bios settings? Any special settings there?
What is your adressing mode (chs, lba, auto)? If it is auto, try changing it to chs (and lba later).
If that kernel messages is somewhat "normal". Every time my hard disc light is on, I got that message, so the "dmesg" is full of that messages, it is really annoying me, even when my computer is idle.
But still I want to get my DMA working, I would like to ask whether my buffered disk reads is normal or not.
Code:
# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 4564 MB in 2.00 seconds = 2282.73 MB/sec
Timing buffered disk reads: 4 MB in 3.07 seconds = 1.30 MB/sec
If that kernel messages is somewhat "normal". Every time my hard disc light is on, I got that message, so the "dmesg" is full of that messages, it is really annoying me, even when my computer is idle.
But still I want to get my DMA working, I would like to ask whether my buffered disk reads is normal or not.
Code:
# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 4564 MB in 2.00 seconds = 2282.73 MB/sec
Timing buffered disk reads: 4 MB in 3.07 seconds = 1.30 MB/sec
And, btw, could you add 2.4 kernel from Slackware to the list of choices in your lilo menu and boot it. Maybe all the errors will be gone? Then we will know that something in 2.6 kernel doesn't get along with your hdd.
Last edited by Alien_Hominid; 05-07-2007 at 03:06 AM.
Here's something to try, for curiosity sake:
The only reliable way I could get my light to turn off and the IDE devices return to 'acting normal' was to run the command 'lshw'. Slackware doesn't have this command by default, but you can get lshw from Sourceforge.net and other places.
Sometimes it would hang when reading the IDE section (hit CTRL-C to kill it) and usually it would complete, and then the HDD light would be off. --NOTE - I really don't know what this proves, but I found it a good way to get the HDD light to go off before I finally had to replace my HD.
Another thing to consider, if you HAVE had this problem with other OS's, is the Master/Slave settings of your devices, and their relative locations on the IDE bus. What I mean is that some machine/HD/CD combinations don't like having an HD on the same cable as an ATAPI CD player/burner.
I've had some issues with that in the past, however this time, for me, my HD was actually defective.
And, btw, could you add 2.4 kernel from Slackware to the list of choices in your lilo menu and boot it. Maybe all the errors will be gone? Then we will know that something in 2.6 kernel doesn't get along with your hdd.
Well I am re-installing my Slackware and I would start from zero again.
I got a new weird problem, I couldn't format my hard disk to ext3. Well, I found one or two posts from another forums said that changing the file system solved the problem. But when I tried to format my hard drive to ext3, it takes forever, I left it 3 hours but still haven't finish.
I desperate and go back to reiserfs.
I will update to you whether that error will come out again or not with the default slackware 2.4 kernel
Perhaps consider Ext2 if you haven't ? It's simple, reliable, and has worked trouble-free for me for Slackware.
Good luck with the reinstall -- let us know what bacomes of it!
And, btw, could you add 2.4 kernel from Slackware to the list of choices in your lilo menu and boot it. Maybe all the errors will be gone? Then we will know that something in 2.6 kernel doesn't get along with your hdd.
Well, a little bit different. But basically the same.
When I use kernel 2.6.21.1
Code:
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
kernel 2.4.33.3 (Slackware's default)
Code:
hda: no DRQ after issuing WRITE
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
Now, I backup the 2.4.33.3 kernel, backup xorg.conf ( only these thing I know to backup, I am not Linux guru )
Now, trying again compile 2.6.21.1 ... I got another solution for DMA problem from another forum. Hope that solution helps me..
Perhaps consider Ext2 if you haven't ? It's simple, reliable, and has worked trouble-free for me for Slackware.
Good luck with the reinstall -- let us know what bacomes of it!
any good points that able to change my mind and think about Ext2? compare to Ext3?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.