[opus]

I have a 20G, 7200 rpm, UDMA100 HD. Why do I see this:

$dmesg
ad0: 19092MB <ST320011A> [38792/16/63] at ata0-master UDMA33

How do I change the UDMA from 33 to 100. It should be 100...correct?

Thanks,

Pete

[soup4you2]

I have a 20G, 7200 rpm, UDMA100 HD. Why do I see this:

$dmesg
ad0: 19092MB <ST320011A> [38792/16/63] at ata0-master UDMA33

How do I change the UDMA from 33 to 100. It should be 100...correct?

Thanks,

Pete

What Release 4x or 5x

[opus]

Sorry......FreeBSD 4.8-STABLE #0: Mon Jul 7 14:14:43 MDT 2003

[elmore]

What kind of controller do you have?

Is it supported?

[opus]

Not sure of the controller. I can tell you that is is a Dell 4550 which is about a year old. How can I get you the controller type?

[soup4you2]

you might also want to check your IDE cables to be sure their ata100 cables

some manufactures only use 66 cables...

[elmore]

A dmesg should do it, Your looking for your ata device driver.

Here's a link to supported controllers.

http://www.freebsd.org/releases/4.8R/hardware-i386.html#AEN33

Is this a laptop or desktop or a server. I went to go look on dell's site and couldn't find info on a 4550

[opus]

atapci0: <Intel ICH4 ATA100 controller> port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0

It is a desktop...only about a year or so old. Go figure why they dont show it at Dell.

[elmore]

I'm gonna go out on a limb here and guess that it's either an unsupported acrd or if supported it's not compiled into your kernel, in which case you'll need to recompile your kernel to add support for it.

There's a couple of FreeBSD kernel compiling threads around here that'll point you in the right direction.

ANyone else have any ideas? :idea:

[opus]

Sorry,

This is the controller. It must have cut it out last time thinking it was HTML.

Intel ICH4 ATA100 controller

I believe this is supported.

[Kernel_Killer]

I had the same speed drop from ATA133, and it was just the cable. Probably your best bet. It wouldn't surprise me if they used a ATA66 cable.

[elmore]

so this device is covered under the generic ata device.

Here's the ata (4) manpage link:

http://www.freebsd.org/cgi/man.cgi?query=ata&amp;apropos=0&amp;sektion=0&amp;manpath=Free BSD+4.8-RELEASE&amp;format=html

Here's a quote from the manpage that seems relevent to you:


The ata driver also allows for changes to the transfer mode of the
devices at a later time when the system is up and running, see
atacontrol(8).

The driver attempts to set the maximum performance transfer mode on your
disk drives by selecting the highest possible DMA mode. However the ata
driver sometimes issue the message "DMA limited to UDMA33, non-ATA66
cable or device", if the cable is ATA66 (or above) compliant, it is
because the other device on this channel states it can only accept upto
UDMA2/ATA33 signals. ATAPI devices are left in PIO mode because DMA
problems are common despite the device specifications. You can always
try to set DMA mode on an ATAPI device using atacontrol(8), but be aware
that your hardware might not support it and can hang the system.


So try atacontrol and see what happens, make sure you have an ata100 cable as soup mentioned earlier, make sure all device on the ide bus are ata100 compliant. Let us know what happens!

Hope that helps! :)

[opus]

dwarf# atacontrol mode 0 udma100 udma100
Master = UDMA33
Slave = UDMA33
dwarf#

It doesnt seem to do anything....

Would that be the proper command?

[soup4you2]

the man page tells all... really simple actually

atacontrol mode 0 will show you what your devices are set at..

i ran it and was supprised about something

Master = UDMA100
Slave = ???


was my return results.. dunno what the ??? is but i'll look into it.. probbibly cd-rom

but say my cdrom was a hard drive and the master was PIOX

you would give the command

[code:1:212fdbde12]
atacontrol mode 0 UDMA4 UDMA4
&lt;master&gt; &lt;slave&gt;
[/code:1:212fdbde12]

try checkin out the man page there's some cool stuff you can do w/ it.. create raid stripes.. i didnt know that...

[elmore]

Are both the master and the slave ata100 devices?

I've never used the atacontrol command before so...
Assuming I know nothing about it cause I don't! I'd probably do

[code:1:1682b1c668]

atacontrol mode 0

[/code:1:1682b1c668]

To see what the bus is seeing. Then I'd do

[code:1:1682b1c668]

atacontrol mode UDMA5 UDMA5

[/code:1:1682b1c668]

of course I could be wrong like I stated before. Other things I'd look at are, the disk drive jumper settings, the cable, the BIOS settings, make sure the slave is also an ata100 device. etc. etc.

[elmore]

HAHA! Soup you posted the same thing I did while I was reading the manpage for goold 'ole petie. Funny! :D

[soup4you2]

mode 0 is primary IDE
mode 1 is secondary IDE

before you do it i would check those cables,,,

and if you do run it run the command sync right afterwards...

[opus]

Both HD's are UDMA100s. I will have to check BIOS. I am just assuming that a 2.4GHz machine from Dell would be UDMA100 compliant....yeah, I know 'assuming'.

[soup4you2]

HAHA! Soup you posted the same thing I did while I was reading the manpage for goold 'ole petie. Funny! :D

hehehe......

btw you check the cable yet petie? it completely would not supprise me that you have a non-100 cable in there

[opus]

Here is what happened:

I had 2 hd's, 1 being master and the other slave...on the same ribbon of course. I dont need the 2nd drive, was just to lazy top open the case and take it out. I uplugged the 2nd and rebooted. I now have:

Master = UDMA100
Slave = ???

I am happy. Not sure why with the other drive plugged in I was getting udma33. It is the same type HD.

[soup4you2]

well glad to see you were able to get it resolved....

[elmore]

check the jumper settings on the second hdd perhaps it was set in UDMA33 mode.

I know some of mine are that way

[opus]

That means I will have to uplug all and open the case again. :o

Lets not and say we did....LOL!!


Pete