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
, 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
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
: 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
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
> 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.
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
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
> 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
NTER 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_tune_drive pio == 255
> 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
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
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:
> 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
=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
Mikael Pettersson wrote:
I was looking briefly at the port mapping issue on 4-port Promise controllers
yesterday and noticed a bit of programming magic in Promise's driver that
Linux doesn't do, and which affects two of the four ports. That _could_
explain your issues.
/Mikael
Just as a note,
or status: 0x50
> > Oct 25 13:57:18 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI
> > SK/ASC/ASCQ 0xb/00/00
> > Oct 25 13:57:18 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete }
> > Oct 25 13:57:26 gleep kernel: ata1: no sense translation for status:
very few seconds during
i/o:
Oct 25 13:57:18 gleep kernel: ata3: no sense translation for status: 0x50
Oct 25 13:57:18 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Oct 25 13:57:18 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete }
Oct 25 13:57:26 gleep
Jeff Garzik wrote::
>Johannes Resch wrote:
>> Hi,
>>
>> [please CC me on replies]
>>
>> I've got a box running 2.6.10 (with the patch[0] needed to support the
>> Promise SATAII 150 TX4 controller).
>> This box has three software raid1 partitions mirrored on a SATA disk on
>> the Promise control
Johannes Resch wrote:
Hi,
[please CC me on replies]
I've got a box running 2.6.10 (with the patch[0] needed to support the
Promise SATAII 150 TX4 controller).
This box has three software raid1 partitions mirrored on a SATA disk on
the Promise controller and a disk on the mainboard IDE controller
could look at to resolve this problem?
The SATA drive is a new Seagate ST3250823AS.
Feb 6 04:49:04 mars kernel: ata4: status=0x51 { DriveReady SeekComplete
Error }
Feb 6 04:49:04 mars kernel: SCSI error : <3 0 0 0> return code = 0x802
Feb 6 04:49:04 mars kernel: FMK Current sda: sen
Hello,
Just got a message:
hda: status error: status=0x50 { DriveReady SeekComplete }
hda: no DRQ after issuing MULTWRITE
hda is: QUANTUM FIREBALL CX10.2A, 9787MB w/418kB Cache, CHS=19885/16/63, UDMA(33)
Promise Ultra100 controller.
# hdparm /dev/hda
/dev/hda:
multcount= 8 (on)
I/O
>
> > (This is from the 2.4.1-pre10 btw.)
> >
> > hdd: CD-ROM TW 120D, ATAPI CD/DVD-ROM drive
> > hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> > hdd: set_drive_speed_status: error=0x04
>
> Means your device did not like that
23 matches
Mail list logo
