Am I in DMA HD mode or not?
Greetings: If I do: # hdparm -d /dev/hda /dev/hda: using_dma = 0 (off) But if I do: # hdparm -i /dev/hda ATA device, with non-removable media powers-up in standby; SET FEATURES subcmd spins-up. Model Number: IBM-DTLA-307030 Serial Number: YKEYKM70956 Firmware Revision: TX4OA60A [output snipped] DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5 [output snipped] * READ/WRITE DMA QUEUED [output snipped] The asterisks in the info output indicate what, that the feature is enabled, or just available? Available doesn't make sense, because they are all available in the drive. The asterisks seem to indicate what is enabled. There appears to be a contradiction. What is really goind on? Note that if I do: # hdparm -d1 /dev/hda the system locks. My read timings look like: # hdparm -t /dev/hda /dev/hda: Timing buffered disk reads: 64 MB in 7.73 seconds = 8.28 MB/sec # hdparm -T /dev/hda /dev/hda: Timing buffer-cache reads: 128 MB in 0.86 seconds =148.84 MB/sec -- ____________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarle@sandia.gov
* S.R.Glasoe
On Friday 12 March 2004 12:32 pm, Chris Carlen wrote:
Greetings: snip Note that if I do:
# hdparm -d1 /dev/hda snip Christopher R. Carlen
Put a space between the d and 1 in -d1.
Even better, use yast to have it make the change on the next reboot.
Switching/forcing a HD from no-DMA to DMA *while data is being written to
it* ,which given that the drive is hda and therefore liekly holds both / and
swap is 100% likely to eb the case, will result at best in data loss, will
result most likely in a crash and can result in a completely corrupted
filesystem.
Been there, done that, did the reinstall. A large section of /etc had
gotten corrupted .. no fun at all
Using yest you tell the system to switch to hda mode on the next reboot.
and it does that when the drivbe is staill in readonly mode.
if that hardhangs your machine (because your IDE controller is not properly
supported) you can boot from rescue CD to installed system, and unset
it again, with no more lost then 15 minutes and a few grey hairs
Currently listening to: pj1994-03-10d2t02
Gerhard,
On Friday 12 March 2004 01:39 pm, Gerhard den Hollander wrote:
Even better, use yast to have it make the change on the next reboot.
Switching/forcing a HD from no-DMA to DMA *while data is being written to it* ,which given that the drive is hda and therefore liekly holds both / and swap is 100% likely to eb the case, will result at best in data loss, will result most likely in a crash and can result in a completely corrupted filesystem.
snip
Using yest you tell the system to switch to hda mode on the next reboot. and it does that when the drivbe is staill in readonly mode.
if that hardhangs your machine (because your IDE controller is not properly supported) you can boot from rescue CD to installed system, and unset it again, with no more lost then 15 minutes and a few grey hairs
Gerhard,
== The Acoustic Motorbiker ==
Better option. Forgot about this. But I don't think it existed under SUSE 8.1. It is in 8.2 and even better in 9.0. Our OP is using SUSE 8.1... Even better under the newer YaST is the ability to see what level of DMA support each device provides. Under the list of IDE DMA devices there is a scroller that lists everything from No Change, DMA Off, DMA On (Default Mode), DMA/16 through UltraDMA/100 and probably higher but thats all my system will do. Works like a charm. Stan
Gerhard den Hollander wrote:
* S.R.Glasoe
(Fri, Mar 12, 2004 at 01:02:46PM -0600) On Friday 12 March 2004 12:32 pm, Chris Carlen wrote:
Greetings:
snip
Note that if I do:
# hdparm -d1 /dev/hda
snip
Christopher R. Carlen
Put a space between the d and 1 in -d1.
Even better, use yast to have it make the change on the next reboot.
Switching/forcing a HD from no-DMA to DMA *while data is being written to it* ,which given that the drive is hda and therefore liekly holds both / and swap is 100% likely to eb the case, will result at best in data loss, will result most likely in a crash and can result in a completely corrupted filesystem.
Been there, done that, did the reinstall. A large section of /etc had gotten corrupted .. no fun at all
Using yest you tell the system to switch to hda mode on the next reboot. and it does that when the drivbe is staill in readonly mode.
if that hardhangs your machine (because your IDE controller is not properly supported) you can boot from rescue CD to installed system, and unset it again, with no more lost then 15 minutes and a few grey hairs
Thanks for the reply. I tried Yast as well and the machine locked. I am convinced the VIA UDMA controller on this mobo is unsupported. Good day! -- ____________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarle@sandia.gov
participants (3)
-
Chris Carlen
-
Gerhard den Hollander
-
S.R.Glasoe