Sergei Shtylyov wrote:
John Sigler wrote:
When my system boots, I get several set_drive_speed_status errors.
(Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
IDE code attempts to autotune PIO mode and fails at that because your
device
Alan Cox wrote:
John Sigler wrote:
http://www.pqimemory.com/documents/domdata.pdf
PIO mode 2 is mentioned. Even DMA seems to be supported.
Or am I mistaken?
Could there be a bug in my south bridge?
Nothing there about DMA support.
cf. document's page 12.
DMACK- (DMA acknowledge
Eric wrote:
John Sigler wrote:
According to my supplier, herre is the data sheet for the DOMs:
http://www.pqimemory.com/documents/domdata.pdf
PIO mode 2 is mentioned. Even DMA seems to be supported.
Or am I mistaken?
Page 3 states max interface burst speed is 8.3MB/s in PIO2. I
wouldn't
Alan Cox wrote:
John Sigler wrote:
Standards:
Likely used: 1
Prehistory
The tragic bit is that we were sold similar DOMs in 2007...
(It's probably time to change suppliers?)
LBA, IORDY not likely
No DMA, nothing above PIO2
OK. (Grumble)
Buffer type: 0002
Petr Vandrovec wrote:
John Sigler wrote:
Alan Cox wrote:
Basically your dinosaur is working correctly.
What do the warnings mean? :-)
That your drive does not support set transfer mode/speed command at all,
or that value which kernel tried is not supported by the drive...
I would
John Sigler wrote:
Petr Vandrovec wrote:
John Sigler wrote:
Alan Cox wrote:
Basically your dinosaur is working correctly.
What do the warnings mean? :-)
That your drive does not support set transfer mode/speed command at
all, or that value which kernel tried is not supported
Hello,
When my system boots, I get several set_drive_speed_status errors.
(Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
Is there something I need to set in the config? or something I should
not have set?
Bonus question: is there some way
