Skip navigation.
Home
The QNX Community Portal

View topic - Fsys.atapi

Fsys.atapi

Read-only archive of qnx.qnx4 (General QNX4 Discussion Group) at inn.qnx.com

Fsys.atapi

Postby Pavel Kycina » Mon Aug 28, 2006 11:40 am

Hello,

is there any information available about the mode disks are accessed at the
given time?

In QNX6 there are entries in sloginfo genereted during devb-eide startup, is
there something similiar in QNX4?

Thank you,

PK
Pavel Kycina
 

RE: Fsys.atapi

Postby maschoen » Mon Aug 28, 2006 6:40 pm

Do you mean like, PIO mode, or DMA_MODE=3????
Unless you can get this from the driver when it starts up, probably not.
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Re: Fsys.atapi

Postby Pavel Kycina » Wed Aug 30, 2006 5:42 am

"maschoen" <maschoen@pobox-dot-com.no-spam.invalid> wrote in message
news:ecvhkk$nb9$1@inn.qnx.com...
Do you mean like, PIO mode, or DMA_MODE=3????
Unless you can get this from the driver when it starts up, probably
not.


I start Fsys.atapi with several "-v", but even during startup it doesn't
display any additional info about this.

I have a new motherboard with VIA 8251 chipset, but EIDE part has the same
PCI ID as older board (1106, 571), which should be supported by Fsys.atapi.

But throughput on old board is approx. 17MB/s, on new one approx. 8MB/s. So
there is some problem there. Any ideas?

Thanks, PK
Pavel Kycina
 

RE: Re: Fsys.atapi

Postby maschoen » Wed Aug 30, 2006 8:14 pm

Now speaking about something I know nothing about, The latest version of EIDE seems have an optional special ribbon cable with 80 wires. I think its all about noise reduction. The computer I'm writing this on seems to know whether this special high density cable is being used or no, because it complains that it is missing at boot time. Could it be that one of your systems has the special cable, and the other doesn't?
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Re: Re: Fsys.atapi

Postby Pavel Kycina » Thu Aug 31, 2006 5:22 am

Both have 80pin cable.

PK


"maschoen" <maschoen@pobox-dot-com.no-spam.invalid> wrote in message
news:ed51d2$hme$1@inn.qnx.com...
Now speaking about something I know nothing about, The latest version
of EIDE seems have an optional special ribbon cable with 80 wires. I
think its all about noise reduction. The computer I'm writing this
on seems to know whether this special high density cable is being
used or no, because it complains that it is missing at boot time.
Could it be that one of your systems has the special cable, and the
other doesn't?
Pavel Kycina
 

Re: Fsys.atapi

Postby Kevin Chiles » Thu Sep 07, 2006 6:00 pm

Pavel Kycina <xkycina@microstep-hdo.sk> wrote:
Hello,

is there any information available about the mode disks are accessed at the
given time?

In QNX6 there are entries in sloginfo genereted during devb-eide startup, is
there something similiar in QNX4?

Yes.

Increase the trace severity to 6. ie Proc -T50,6
create a file with the following entries:

#major 0x00005
0xB40 %s

run traceinfo -e file
Kevin Chiles
 

Re: Fsys.atapi

Postby Pavel Kycina » Fri Sep 08, 2006 6:33 am

Hello,

this is the output from traceinfo on that computer.

PK
------------
Jan 01 01:00:00 6 00005b40 eide_identify_devices: Generic IDE vid 1106, did
3349, class 1018f rev 0, busno 0, dfunc 78

Jan 01 01:00:00 6 00005b40 eide_identify_devices: cmd_addr ff00, cntl_addr
fe00, irq b, chnl 0, udma -1, mdma -1, sdma -1, pio 0

Jan 01 01:00:00 6 00005b40 eide_identify_devices: probing dev 0 7f

Jan 01 01:00:00 6 00005b40 eide_identify_devices: probing dev 1 7f

Jan 01 01:00:00 6 00005b40 eide_command: BSY/DRQ set: 7f

Jan 01 01:00:00 6 00005b40 eide_identify: IDENTIFY failed: cmd ec, tid 0,
status 7f, error ff

Jan 01 01:00:04 6 00005b40 eide_command: BSY/DRQ set: ff

Jan 01 01:00:04 6 00005b40 eide_identify: IDENTIFY failed: cmd a1, tid 0,
status ff, error ff

Jan 01 01:00:05 6 00005b40 eide_command: BSY/DRQ set: 7f

Jan 01 01:00:05 6 00005b40 eide_identify: IDENTIFY failed: cmd ec, tid 1,
status 7f, error ff

Jan 01 01:00:09 6 00005b40 eide_command: BSY/DRQ set: ff

Jan 01 01:00:09 6 00005b40 eide_identify: IDENTIFY failed: cmd a1, tid 1,
status ff, error ff

Jan 01 01:00:09 6 00005b40 eide_identify_devices: Generic IDE vid 1106, did
3349, class 1018f rev 0, busno 0, dfunc 78

Jan 01 01:00:09 6 00005b40 eide_identify_devices: cmd_addr fd00, cntl_addr
fc00, irq b, chnl 1, udma -1, mdma -1, sdma -1, pio 0

Jan 01 01:00:09 6 00005b40 eide_identify_devices: probing dev 0 7f

Jan 01 01:00:09 6 00005b40 eide_identify_devices: probing dev 1 7f

Jan 01 01:00:09 6 00005b40 eide_command: BSY/DRQ set: 7f

Jan 01 01:00:09 6 00005b40 eide_identify: IDENTIFY failed: cmd ec, tid 0,
status 7f, error ff

Jan 01 01:00:13 6 00005b40 eide_command: BSY/DRQ set: ff

Jan 01 01:00:13 6 00005b40 eide_identify: IDENTIFY failed: cmd a1, tid 0,
status ff, error ff

Jan 01 01:00:14 6 00005b40 eide_command: BSY/DRQ set: 7f

Jan 01 01:00:14 6 00005b40 eide_identify: IDENTIFY failed: cmd ec, tid 1,
status 7f, error ff

Jan 01 01:00:18 6 00005b40 eide_command: BSY/DRQ set: ff

Jan 01 01:00:18 6 00005b40 eide_identify: IDENTIFY failed: cmd a1, tid 1,
status ff, error ff

Jan 01 01:00:18 6 00005b40 eide_identify_devices: VIA 82C586A/B vid 1106,
did 571, class 1018a rev 7, busno 0, dfunc 79

Jan 01 01:00:18 6 00005b40 eide_identify_devices: cmd_addr 1f0, cntl_addr
3f4, irq e, chnl 0, udma -1, mdma 2, sdma 0, pio 4

Jan 01 01:00:18 6 00005b40 eide_identify_devices: probing dev 0 50

Jan 01 01:00:18 6 00005b40 eide_identify_devices: probing dev 1 0

Jan 01 01:00:20 6 00005b40 eide_display_devices: ST380011A config c5a,tid 0,
cable 80, max udma 5, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur
sdma -1, pio 4, mblk 16

Jan 01 01:00:22 6 00005b40 eide_identify: chk 4 cmd ec, tid 1, status 0,
error 0

Jan 01 01:00:22 6 00005b40 eide_identify_devices: VIA 82C586A/B vid 1106,
did 571, class 1018a rev 7, busno 0, dfunc 79

Jan 01 01:00:22 6 00005b40 eide_identify_devices: cmd_addr 170, cntl_addr
374, irq f, chnl 1, udma -1, mdma 2, sdma 0, pio 4

Jan 01 01:00:22 6 00005b40 eide_identify_devices: probing dev 0 20

Jan 01 01:00:22 6 00005b40 eide_identify_devices: probing dev 1 30

Jan 01 01:00:24 6 00005b40 eide_identify: chk 4 cmd ec, tid 0, status 7f,
error 7f

Jan 01 01:00:24 6 00005b40 eide_command: BSY/DRQ set: 8

Jan 01 01:00:24 6 00005b40 eide_identify: IDENTIFY failed: cmd a1, tid 0,
status 8, error 8

Jan 01 01:00:25 6 00005b40 eide_identify: chk 4 cmd ec, tid 1, status 7f,
error 7f

Jan 01 01:00:25 6 00005b40 eide_command: BSY/DRQ set: 8

Jan 01 01:00:25 6 00005b40 eide_identify: IDENTIFY failed: cmd a1, tid 1,
status 8, error 8

Jan 01 01:00:26 6 00005b40 eide_init_devices: ST380011A path 0, tid 0,
udma -1, mdma 2, sdma -1, pio 4, mblk 16

Jan 01 01:00:26 5 00005109 Scsi sense (unit=0 scsi=2 err=70h sense=5h
asc=24h ascq=0h)

Jan 01 01:00:26 5 00005109 Scsi sense (unit=0 scsi=2 err=70h sense=5h
asc=24h ascq=0h)

Jan 01 01:00:26 5 00005109 Scsi sense (unit=0 scsi=2 err=70h sense=5h
asc=24h ascq=0h)

Jan 01 01:00:26 5 00005109 Scsi sense (unit=0 scsi=2 err=70h sense=5h
asc=24h ascq=0h)

Jan 01 01:00:26 5 00005109 Scsi sense (unit=0 scsi=2 err=70h sense=5h
asc=24h ascq=0h)

------------
Pavel Kycina
 


Return to qnx.qnx4

Who is online

Users browsing this forum: No registered users and 2 guests