I’ve just downloaded the USB 2.0 drivers for QNX4
io-usb immediately ends with the message “Error Initializing Stack”
(exectly the same if I execute “io-usb -v”)
My system is QNX 4.25 G
Any hints?
Thank you
Joan Baucells <“Joan Baucells”@nospam.es> wrote:
I’ve just downloaded the USB 2.0 drivers for QNX4
io-usb immediately ends with the message “Error Initializing Stack”
(exectly the same if I execute “io-usb -v”)My system is QNX 4.25 G
Any hints?
Please post the output from “show_pci -v”
This is my “show_pci -v” output:
PCI version = 2.10
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 1250h
PCI index = 0h
Class Code = 60000h Bridge (Host/PCI) ProgIF=0
Revision ID = 3h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2200h
Command Reg = 106h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0
PCI Int Pin = NC
Interrupt line = 0
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7000h
PCI index = 0h
Class Code = 60100h Bridge (PCI/ISA) ProgIF=0
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 0
Status Reg = 280h
Command Reg = fh
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0
PCI Int Pin = NC
Interrupt line = 0
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7010h
PCI index = 0h
Class Code = 10180h Mass Storage (IDE) ProgIF=128
Revision ID = 0h
Bus number = 0
Device number = 7
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
IO@ffa0h length 16 bytes
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0
PCI Int Pin = NC
Interrupt line = 0
Vendor ID = 5333h, S3 Inc.
Device ID = 8811h, Trio32/Trio64
PCI index = 0h
Class Code = 30000h Display (VGA) ProgIF=0
Revision ID = 54h
Bus number = 0
Device number = 13
Function num = 0
Status Reg = 200h
Command Reg = 3h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Base Address = MEM@f8000000h,32bit length 67108864
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = no connection
IRQ Routing = bus=0 slot=128 device=8
No card configured in slot
INTA=3,4,5,7,9,10,11 Slot1:INTD Slot2:INTC Slot3:INTB
Slot4:INTA Slot134:INTD
IRQ Routing = bus=0 slot=1 device=13
Vendor ID = 5333h, S3 Inc.
Device ID = 8811h, Trio32/Trio64
INTA=3,4,5,7,9,10,11 Slot2:INTD Slot3:INTC Slot4:INTB
INTB=3,4,5,7,9,10,11 Slot2:INTA Slot3:INTD Slot4:INTC
INTC=3,4,5,7,9,10,11 Slot2:INTB Slot3:INTA Slot4:INTD
INTD=3,4,5,7,9,10,11 Slot128:INTA Slot2:INTC Slot3:INTB
Slot4:INTA Slot134:INTD
IRQ Routing = bus=0 slot=2 device=14
No card configured in slot
INTA=3,4,5,7,9,10,11 Slot1:INTB Slot3:INTD Slot4:INTC
INTB=3,4,5,7,9,10,11 Slot1:INTC Slot3:INTA Slot4:INTD
INTC=3,4,5,7,9,10,11 Slot128:INTA Slot1:INTD Slot3:INTB
Slot4:INTA Slot134:INTD
INTD=3,4,5,7,9,10,11 Slot1:INTA Slot3:INTC Slot4:INTB
IRQ Routing = bus=0 slot=3 device=15
No card configured in slot
INTA=3,4,5,7,9,10,11 Slot1:INTC Slot2:INTB Slot4:INTD
INTB=3,4,5,7,9,10,11 Slot128:INTA Slot1:INTD Slot2:INTC
Slot4:INTA Slot134:INTD
INTC=3,4,5,7,9,10,11 Slot1:INTA Slot2:INTD Slot4:INTB
INTD=3,4,5,7,9,10,11 Slot1:INTB Slot2:INTA Slot4:INTC
IRQ Routing = bus=0 slot=4 device=16
No card configured in slot
INTA=3,4,5,7,9,10,11 Slot128:INTA Slot1:INTD Slot2:INTC
Slot3:INTB Slot134:INTD
INTB=3,4,5,7,9,10,11 Slot1:INTA Slot2:INTD Slot3:INTC
INTC=3,4,5,7,9,10,11 Slot1:INTB Slot2:INTA Slot3:INTD
INTD=3,4,5,7,9,10,11 Slot1:INTC Slot2:INTB Slot3:INTA
IRQ Routing = bus=0 slot=133 device=7 func=1
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7000h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7010h
INTA=14
INTB=15
IRQ Routing = bus=0 slot=134 device=7 func=2
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7000h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 7010h
INTD=3,4,5,7,9,10,11 Slot128:INTA Slot1:INTD Slot2:INTC Slot3:INTB
Slot4:INTA
Thank you for your time!
Kevin Chiles wrote:
Joan Baucells <“Joan Baucells”@nospam.es> wrote:
I’ve just downloaded the USB 2.0 drivers for QNX4io-usb immediately ends with the message “Error Initializing Stack”
(exectly the same if I execute “io-usb -v”)My system is QNX 4.25 G
Any hints?
Please post the output from “show_pci -v”
Joan Baucells <“Joan Baucells”@nospam.es> wrote:
This is my “show_pci -v” output:
It looks like the USB chip isn’t enabled in the BIOS.
Ooops!!
You’re right, they works now.
Thanks
Kevin Chiles wrote:
Joan Baucells <“Joan Baucells”@nospam.es> wrote:
This is my “show_pci -v” output:It looks like the USB chip isn’t enabled in the BIOS.
This is very useful topic for me.
I found “/dev/usb” after executing “io-usb” command, but I cannot mount it
yet.
Please show me how to use usb mass storage device.
Thank you.
“Joan Baucells” <“Joan Baucells”@NoSpam.es> wrote in message
news:438566BF.BC55AF3A@NoSpam.es…
Ooops!!
You’re right, they works now.
Thanks
Kevin Chiles wrote:
Joan Baucells <“Joan Baucells”@nospam.es> wrote:
This is my “show_pci -v” output:It looks like the USB chip isn’t enabled in the BIOS.
Insert an USB memory device.
Execute io-usb.
After thst execute Fsys.umass &
You will found a new disk “/dev/hd2” or something like taht.
You will need to initialize the new device executing dinit -h /dev/hd2
After that you can mount the device mount /dev/hs2 /yourUSBlocation
Tony wrote:
This is very useful topic for me.
I found “/dev/usb” after executing “io-usb” command, but I cannot mount it
yet.
Please show me how to use usb mass storage device.Thank you.
“Joan Baucells” <“Joan Baucells”@NoSpam.es> wrote in message
news:> 438566BF.BC55AF3A@NoSpam.es> …
Ooops!!You’re right, they works now.
Thanks
Kevin Chiles wrote:
Joan Baucells <“Joan Baucells”@nospam.es> wrote:
This is my “show_pci -v” output:It looks like the USB chip isn’t enabled in the BIOS.
On Mon, 28 Nov 2005 11:19:08 +0300, Joan Baucells <“Joan
Baucells”@NoSpam.es> wrote:
Insert an USB memory device.
Execute io-usb.
After thst execute Fsys.umass &
You will found a new disk “/dev/hd2” or something like taht.You will need to initialize the new device executing dinit -h /dev/hd2
Do this only if the FLASH-disk is not initialized already!
Normally they are ready to use (i.e FAT32 formatted).
After that you can mount the device mount /dev/hs2 /yourUSBlocation
Tony.
I downloaded the USB driver as well and am trying to use it. When I connect
a memory stick to my USB drive and give the following commands:
io-usb &
Fsys.umass &
“/dev/hd1” gets created.
Then I give the command
“mount -p /dev/hd1”. This creates “/dev/hd1t6”.
Then, I mount /dev/hd1t6 as follows:
“mount -t dos /dev/hd1t6 /dos/c”
and it seems to work. When I am not using the flash disk, I can unmount
“/dos/c”.
However, If I disconnect the flash disk , it doesn’t remove “/dev/hd1” or
for that matter “/dev/hd1t6”. Even after I kill io-usb and Fsys.umass,
these block-special devices exist.
Shouldn’t it remove “/dev/hd1” and “/dev/hd1t6” when i disconnect the memory
stick?
I appreciate your suggestions.
Shashank
“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:op.s0x8n301o93ri4@mobile.wst.quantum.ru…
On Mon, 28 Nov 2005 11:19:08 +0300, Joan Baucells <“Joan
Baucells”@NoSpam.es> wrote:
Insert an USB memory device.
Execute io-usb.
After thst execute Fsys.umass &
You will found a new disk “/dev/hd2” or something like taht.You will need to initialize the new device executing dinit -h /dev/hd2
Do this only if the FLASH-disk is not initialized already!
Normally they are ready to use (i.e FAT32 formatted).
After that you can mount the device mount /dev/hs2 /yourUSBlocationTony.
On Mon, 28 Nov 2005 17:16:07 +0300, Shashank <sbalijepalli@precitech.com>
wrote:
…and give the following commands:
io-usb &
Fsys.umass &“/dev/hd1” gets created.
Then I give the command
“mount -p /dev/hd1”. This creates “/dev/hd1t6”.
So far you’ve did everything OK
Then, I mount /dev/hd1t6 as follows:
“mount -t dos /dev/hd1t6 /dos/c”
I do it this way:
mount /dev/hd1t6
Fatfsys
Tony.
“Shashank” <sbalijepalli@precitech.com> wrote in message
news:dmf3jl$ri3$7@inn.qnx.com…
I downloaded the USB driver as well and am trying to use it. When I
connect
a memory stick to my USB drive and give the following commands:
io-usb &
Fsys.umass &“/dev/hd1” gets created.
Then I give the command
“mount -p /dev/hd1”. This creates “/dev/hd1t6”.Then, I mount /dev/hd1t6 as follows:
“mount -t dos /dev/hd1t6 /dos/c”and it seems to work. When I am not using the flash disk, I can unmount
“/dos/c”.However, If I disconnect the flash disk , it doesn’t remove “/dev/hd1” or
for that matter “/dev/hd1t6”. Even after I kill io-usb and Fsys.umass,
these block-special devices exist.
Read the doc that came with the USB kit, it explains how to cleanly (and
manualy) deal with removal of devices.
Shouldn’t it remove “/dev/hd1” and “/dev/hd1t6” when i disconnect the
memory
stick?I appreciate your suggestions.
Shashank
“Tony” <> mts.spb.suxx@mail.ru> > wrote in message
news:> op.s0x8n301o93ri4@mobile.wst.quantum.ru> …
On Mon, 28 Nov 2005 11:19:08 +0300, Joan Baucells <“Joan
Baucells”@NoSpam.es> wrote:
Insert an USB memory device.
Execute io-usb.
After thst execute Fsys.umass &
You will found a new disk “/dev/hd2” or something like taht.You will need to initialize the new device executing dinit -h /dev/hd2
Do this only if the FLASH-disk is not initialized already!
Normally they are ready to use (i.e FAT32 formatted).
After that you can mount the device mount /dev/hs2 /yourUSBlocationTony.