I’m using a PCMCIA ATA flash card on my x86 system with QNX 6.2 and
I’m having some troubles with (I suppose) pccard-launch utility or devb-eide
driver.
pccard-launch -vvv ‘0x0400, devb-eide eide ioport=0x0200,irq=3’ &
I get a message:
iotype=401 l->type=400
couldn’t lock socket 1 (16)
and after that nothing happens.
If I kill enum-pccard process and run pccard-lunch, devb-eide is spawned. It
takes about 1 minute
to see a new device in dev directory and additional 20 sec to see
/dev/hd1t77 device. I can mount
/dev/hd1t77 but access time is extreamly slow.
The same hardware configuration was working very well and fast with QNX 6.0
and patch B.
Any work around or existing solutions?
Janusz Ruszel.
“Janusz Ruszel” <janusz_ruszel@baxter.com> wrote in message
news:aipfrt$d92$1@inn.qnx.com…
I’m using a PCMCIA ATA flash card on my x86 system with QNX 6.2 and
I’m having some troubles with (I suppose) pccard-launch utility or
devb-eide
driver.
pccard-launch -vvv ‘0x0400, devb-eide eide ioport=0x0200,irq=3’ &
Try
pccard-launch -vvv ‘0x0400, devb-eide eide ioport=0x0200:0x20c,irq=3’ &
AFAIK the devb-eide driver has undergone major modification for 6.2.
I get a message:
iotype=401 l->type=400
couldn’t lock socket 1 (16)
and after that nothing happens.
If I kill enum-pccard process and run pccard-lunch, devb-eide is spawned.
It
takes about 1 minute
to see a new device in dev directory and additional 20 sec to see
/dev/hd1t77 device. I can mount
/dev/hd1t77 but access time is extreamly slow.
The same hardware configuration was working very well and fast with QNX
6.0
and patch B.
Any work around or existing solutions?
Janusz Ruszel.
Thank you Jim!
It works. I would blame on poor documentation again.
Janusz Ruszel.
“Jim Douglas” <jim@dramatec.co.uk> wrote in message
news:aiqhut$772$1@inn.qnx.com…
“Janusz Ruszel” <> janusz_ruszel@baxter.com> > wrote in message
news:aipfrt$d92$> 1@inn.qnx.com> …
I’m using a PCMCIA ATA flash card on my x86 system with QNX 6.2 and
I’m having some troubles with (I suppose) pccard-launch utility or
devb-eide
driver.
pccard-launch -vvv ‘0x0400, devb-eide eide ioport=0x0200,irq=3’ &
Try
pccard-launch -vvv ‘0x0400, devb-eide eide ioport=0x0200:0x20c,irq=3’ &
AFAIK the devb-eide driver has undergone major modification for 6.2.
I get a message:
iotype=401 l->type=400
couldn’t lock socket 1 (16)
and after that nothing happens.
If I kill enum-pccard process and run pccard-lunch, devb-eide is
spawned.
It
takes about 1 minute
to see a new device in dev directory and additional 20 sec to see
/dev/hd1t77 device. I can mount
/dev/hd1t77 but access time is extreamly slow.
The same hardware configuration was working very well and fast with QNX
6.0
and patch B.
Any work around or existing solutions?
Janusz Ruszel.
\
Janusz Ruszel <janusz_ruszel@baxter.com> wrote:
: Thank you Jim!
: It works. I would blame on poor documentation again.
Did you have a problem with our documentation or someone else’s?
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems