Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-09-03 Thread Sergei Shtylyov
eed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } That means that you've managed to fi

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-09-03 Thread John Sigler
, hdd:pio Probing IDE interface ide0... hda: PQI IDE DiskOnModule, ATA DISK drive hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-09-01 Thread Sergei Shtylyov
hda: PQI IDE DiskOnModule, ATA DISK drive ENTER via82cxxx_tune_drive ENTER via_set_drive ENTER ide_config_drive_speed hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error ENTER via_set_speed

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-09-01 Thread Sergei Shtylyov
: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } That means that you've managed to fin

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-31 Thread Sergei Shtylyov
Alan Cox wrote: Standards: Likely used: 1 Prehistory LBA, IORDY not likely No DMA, nothing above PIO2 Cool! :-) Buffer type: 0002: dual port, multi-sector Buffer size: 1.0kB bytes avail on r/w long: 4 Cannot perform double-word IO Ca

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-31 Thread Alan Cox
> When a DMA operation is enabled, CS0- and CS1- shall not be asserted and > transfers shall be 16-bits wide. > > I took the above to mean the device was designed to support DMA. > Where did I err? The bus is specified for DMA, not the device. > > > The data sheet says the media can only do 4.

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-31 Thread John Sigler
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 as

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-31 Thread John Sigler
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) This si

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-30 Thread Alan Cox
> 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. The data sheet says the media can only do 4.1MB/second which is consistent with only needing PIO2 (actually its far slower than PIO2) - To

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-30 Thread John Sigler
ENTER via82cxxx_ide_dma_check ENTER via_set_drive ENTER ide_config_drive_speed hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error ENTER via_set_speed EXIT via_set_speed EXIT via_set_drive EX

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-30 Thread Alan Cox
> Buffer size: 1.0kB bytes avail on r/w long: 4 > > (Assuming an 8-bit byte, 4 bytes = 32 bits) R/W Long is a different thing. > When you say "the current libata IDE" do you mean PATA_VIA (in my case)? > I've avoided this driver because it is marked EXPERIMENTAL. Would there > be

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-30 Thread John Sigler
ck ENTER via_set_drive ENTER ide_config_drive_speed hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error ENTER via_set_speed EXIT via_set_speed EXIT via_set_drive EXIT via82cxxx_ide_dm

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-30 Thread John Sigler
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:

Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-29 Thread Alan Cox
> Standards: > Likely used: 1 Prehistory > LBA, IORDY not likely No DMA, nothing above PIO2 > Buffer type: 0002: dual port, multi-sector > Buffer size: 1.0kB bytes avail on r/w long: 4 > Cannot perform double-word IO Can't even do double word

hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

2007-08-29 Thread John Sigler
=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hda: set_drive_speed_status: error=0x04 { DriveStatusError } ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1