Orinoco WiFi gold on PC-104

Hi, I try to install a orinoco WiFi card on a PCMCIA module on a PC104 and it is not working!

this is what I try, I also got a ethernet adaptor and the drivers works fine:

#PCMCIA DEVICE
pci-bios
waitfor /dev/pci
devp-pccard -a 0x400 -l10,10
waitfor /dev/pccard
sleep 1
slay pci-bios
sleep 1
pci-bios
waitfor /dev/pci
sleep 1
devc-con -e -n4 &
#ETHARNET ET WIRELESS CARDS
io-net -d rtl -p ttcpip if=en0:192.168.2.13
pin
io-net -d orinoco ioport=0x400,irq=10 -v -p ttcpip if=en1:192.168.2.15
waitfor /dev/socket

Someone have try this before?


Charles-Etienne Lemay
TEAMSAT
Université de Sherbrooke
Tel: (819) 821-8000 ext. 1215
Fax: (819) 821-7937

On Fri, 21 Mar 2003 11:25:43 -0500, “Bernard Biron” <bb2@hermes.usherb.ca> wrote:

C’est un message de format MIME en plusieurs parties.

------=_NextPart_000_00E3_01C2EF9C.9C357180
Content-Type: text/plain;
charset=“iso-8859-1”
Content-Transfer-Encoding: quoted-printable

Hi, I try to install a orinoco WiFi card on a PCMCIA module on a PC104 =
and it is not working!

this is what I try, I also got a ethernet adaptor and the drivers works =
fine:

Are you sure your PC/104 board supports 3.3V?
This has been a problem for a customer of mine before…

<acellarius@yahoo.com> a écrit dans le message news:
1103_1048273685@192.168.0.5

On Fri, 21 Mar 2003 11:25:43 -0500, “Bernard Biron” <> bb2@hermes.usherb.ca
wrote:
C’est un message de format MIME en plusieurs parties.

------=_NextPart_000_00E3_01C2EF9C.9C357180
Content-Type: text/plain;
charset=“iso-8859-1”
Content-Transfer-Encoding: quoted-printable

Hi, I try to install a orinoco WiFi card on a PCMCIA module on a PC104 =
and it is not working!

this is what I try, I also got a ethernet adaptor and the drivers works

fine:

Are you sure your PC/104 board supports 3.3V?
This has been a problem for a customer of mine before…

My PC-104 is : Eurotech CPU-1432, on the PCI bus and I/O, there is 3.3V

This is my power input :

Table 16. J11 Auxiliary Power Connector

Pin Signal Description

1 GND Ground

2 VDD (+5VDC) +5VDC signal

3 N.C. Not connected

4 +12VDC +12VDC signal

5 N.C. Not connected

6 -12VDC -12VDC signal

7 GND Ground

8 VDD (+5VDC) +5VDC signal

9 WDTL WDT Toggled Status

10 PWR_BTN Power Button

11 +5VSB Always high (ATX only)

12 ATX ON ATX Power on signal

“Bernard Biron” <bb2@hermes.usherb.ca> wrote in message news:b5fdl9$9qt$1@inn.qnx.com
Hi, I try to install a orinoco WiFi card on a PCMCIA module on a PC104 and it is not working!

this is what I try, I also got a ethernet adaptor and the drivers works fine:

#PCMCIA DEVICE
pci-bios
waitfor /dev/pci
devp-pccard -a 0x400 -l10,10
waitfor /dev/pccard
sleep 1
slay pci-bios
sleep 1
pci-bios
waitfor /dev/pci
sleep 1
devc-con -e -n4 &
#ETHARNET ET WIRELESS CARDS
io-net -d rtl -p ttcpip if=en0:192.168.2.13
pin
io-net -d orinoco ioport=0x400,irq=10 -v -p ttcpip if=en1:192.168.2.15
waitfor /dev/socket


Why are you restarting pci-bios? That odd.

Starting two io-net doesn’t look like a good idea here. (what happens to /dev/socket when two stacks are running). Plus I don’t beleive you can have two interfaces assigned an IP address in the same class.

Can you be a little more elaborte when you say “doesn’t work”.

\

  • Mario
    Boisbriand, Quebec, Canada

“Mario Charest” postmaster@127.0.0.1 a écrit dans le message news: b5h0lb$2qe$1@inn.qnx.com

“Bernard Biron” <bb2@hermes.usherb.ca> wrote in message news:b5fdl9$9qt$1@inn.qnx.com
Hi, I try to install a orinoco WiFi card on a PCMCIA module on a PC104 and it is not working!

this is what I try, I also got a ethernet adaptor and the drivers works fine:

#PCMCIA DEVICE
pci-bios
waitfor /dev/pci
devp-pccard -a 0x400 -l10,10
waitfor /dev/pccard
sleep 1
slay pci-bios
sleep 1
pci-bios
waitfor /dev/pci
sleep 1
devc-con -e -n4 &
#ETHARNET ET WIRELESS CARDS
io-net -d rtl -p ttcpip if=en0:192.168.2.13
pin
io-net -d orinoco ioport=0x400,irq=10 -v -p ttcpip if=en1:192.168.2.15
waitfor /dev/socket


Why are you restarting pci-bios? That odd.

Starting two io-net doesn’t look like a good idea here. (what happens to /dev/socket when two stacks are running). Plus I don’t beleive you can have two interfaces assigned an IP address in the same class.

Can you be a little more elaborte when you say “doesn’t work”.

\

  • Mario
    Boisbriand, Quebec, Canada


    I start the pci-bios because it need to be start tu use devp-pccard and got some warning if it start before devp-pccard, so I start it after and is ok.

By doesn’t work I meen that the first networks adaptor work and le second(orinoco) don’t start.
It say : unable the start dll devn-orinoco.so : Library cannot be found

But I have include the .so and it’s in the /proc/boot/

So you think it’s possible to start the 2 networks adaptor with the same io-net?

“Charles-Etienne Lemay” <charlesetienne@hermes.usherb.ca> a écrit dans le message news: b5n06a$mh2$1@inn.qnx.com

“Mario Charest” postmaster@127.0.0.1 a écrit dans le message news: b5h0lb$2qe$1@inn.qnx.com

“Bernard Biron” <bb2@hermes.usherb.ca> wrote in message news:b5fdl9$9qt$1@inn.qnx.com
Hi, I try to install a orinoco WiFi card on a PCMCIA module on a PC104 and it is not working!

this is what I try, I also got a ethernet adaptor and the drivers works fine:

#PCMCIA DEVICE
pci-bios
waitfor /dev/pci
devp-pccard -a 0x400 -l10,10
waitfor /dev/pccard
sleep 1
slay pci-bios
sleep 1
pci-bios
waitfor /dev/pci
sleep 1
devc-con -e -n4 &
#ETHARNET ET WIRELESS CARDS
io-net -d rtl -p ttcpip if=en0:192.168.2.13
pin
io-net -d orinoco ioport=0x400,irq=10 -v -p ttcpip if=en1:192.168.2.15
waitfor /dev/socket


Why are you restarting pci-bios? That odd.

Starting two io-net doesn’t look like a good idea here. (what happens to /dev/socket when two stacks are running). Plus I don’t beleive you can have two interfaces assigned an IP address in the same class.

Can you be a little more elaborte when you say “doesn’t work”.

\

  • Mario
    Boisbriand, Quebec, Canada


    I start the pci-bios because it need to be start tu use devp-pccard and got some warning if it start before devp-pccard, so I start it after and is ok.

By doesn’t work I meen that the first networks adaptor work and le second(orinoco) don’t start.
It say : unable the start dll devn-orinoco.so : Library cannot be found

But I have include the .so and it’s in the /proc/boot/

So you think it’s possible to start the 2 networks adaptor with the same io-net?


sorry, the error is more la this! : unable the start dll devn-orinoco.so : Device unable to start

So you think it’s possible to start the 2 networks adaptor with the same
io-net?

It’s not only possible, that’s usually the way to do it :wink:

sorry, the error is more la this! : unable the start dll devn-orinoco.so :
Device unable to start

What is the output of pin?

“Mario Charest” postmaster@127.0.0.1 a écrit dans le message news:
b5nm65$hr3$1@inn.qnx.com

So you think it’s possible to start the 2 networks adaptor with the same
io-net?

It’s not only possible, that’s usually the way to do it > :wink:

I have try something else et it work for the first card ( realtek) and not
for the orinoco

io-net &
mount -T io-net devn-rtl.so
mount -T io-net -o if=en0:192.168.2.13 npm-ttcpip.so
mount -T io-net devn.orinoco.so
mount -T io-net -o if=en1:192.168.2.15 npm-ttcpip.so

Display messages :

Mount : Can’t mount / (type io-net)
Mount : Possible reason : Nosuch device or address
Mount : Can’t mount / (type io-net)
Mount : Possible reason : Ressource busy


So en en0 is ok ( I ping it! )

sorry, the error is more la this! : unable the start dll devn-orinoco.so
:
Device unable to start

What is the output of pin?

Yesterday I a put mais 3com pcicia card and the base was 0x400 and woth the
orinoco I don’t got anything.

sock Func Type Flags PID Base
Size IRQ
1 Empty ----MF----------
1 Empty ----MF----------
2 0 Network C–NIF----------
10
2 Empty ----MF----------

Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:

“Mario Charest” postmaster@127.0.0.1 a écrit dans le message news:
b5nm65$hr3$> 1@inn.qnx.com> …



So you think it’s possible to start the 2 networks adaptor with the same
io-net?

It’s not only possible, that’s usually the way to do it > :wink:

I have try something else et it work for the first card ( realtek) and not
for the orinoco

io-net &
mount -T io-net devn-rtl.so
mount -T io-net -o if=en0:192.168.2.13 npm-ttcpip.so
mount -T io-net devn.orinoco.so
mount -T io-net -o if=en1:192.168.2.15 npm-ttcpip.so

Display messages :

Mount : Can’t mount / (type io-net)
Mount : Possible reason : Nosuch device or address
Mount : Can’t mount / (type io-net)
Mount : Possible reason : Ressource busy

Do all messages spill from the same mount command?

I see one obvious problem – you can’t mount npm-ttcpip.so twice
the way your are doing.

The resource busy probably comes from that. The other message,
no such device or address, might be a ‘hardware not found’, or
might also be related.

Maybe try:

io-net &
mount -T io-net devn-rtl.so
mount -T io-net devn.orinoco.so
mount -T io-net -o if=en0:192.168.2.13 if=en1:192.168.2.15 npm-ttcpip.so

(Also, are you using npm-ttcpip.so instead of npm-tcpip.so for a
particular reason?)

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

“David Gibbs” <dagibbs@qnx.com> a écrit dans le message news:
b5nr4m$bm2$1@nntp.qnx.com
Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:

“Mario Charest” postmaster@127.0.0.1 a écrit dans le message news:
b5nm65$hr3$> 1@inn.qnx.com> …



So you think it’s possible to start the 2 networks adaptor with the same
io-net?

It’s not only possible, that’s usually the way to do it > :wink:

I have try something else et it work for the first card ( realtek) and not
for the orinoco

io-net &
mount -T io-net devn-rtl.so
mount -T io-net -o if=en0:192.168.2.13 npm-ttcpip.so
mount -T io-net devn.orinoco.so
mount -T io-net -o if=en1:192.168.2.15 npm-ttcpip.so

Display messages :

Mount : Can’t mount / (type io-net)
Mount : Possible reason : Nosuch device or address
Mount : Can’t mount / (type io-net)
Mount : Possible reason : Ressource busy

Do all messages spill from the same mount command?

Yes.

I see one obvious problem – you can’t mount npm-ttcpip.so twice
the way your are doing.

The resource busy probably comes from that. The other message,
no such device or address, might be a ‘hardware not found’, or
might also be related.

Maybe try:

io-net &
mount -T io-net devn-rtl.so
mount -T io-net devn.orinoco.so
mount -T io-net -o if=en0:192.168.2.13 if=en1:192.168.2.15 npm-ttcpip.so

with that this is what I got :

Mount : Can’t mount / (type io-net)
Mount : Possible reason : Nosuch device or address


(Also, are you using npm-ttcpip.so instead of npm-tcpip.so for a
particular reason?)

I boot on a floppy disk with some firewire library and I don’t have enought
place!
I can try with the npm-tcpip.so but the error is before in the mount.


-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:

“David Gibbs” <> dagibbs@qnx.com> > a écrit dans le message news:
b5nr4m$bm2$> 1@nntp.qnx.com> …
Charles-Etienne Lemay <> charlesetienne@hermes.usherb.ca> > wrote:



Maybe try:

io-net &
mount -T io-net devn-rtl.so
mount -T io-net devn.orinoco.so
mount -T io-net -o if=en0:192.168.2.13 if=en1:192.168.2.15 npm-ttcpip.so

with that this is what I got :

Mount : Can’t mount / (type io-net)
Mount : Possible reason : Nosuch device or address

Ok, that’s back to the hardware side – not detecting the
orinoco card. I think there had been some conversation about
this already, but I haven’t been following it as closely (not
so much my area of expertise.)

Have you been asked for, and posted, the output of “pci -v”,
“pin” and “pin cis”?

(Also, are you using npm-ttcpip.so instead of npm-tcpip.so for a
particular reason?)

I boot on a floppy disk with some firewire library and I don’t have enought
place!

That makes perfect sense.

I can try with the npm-tcpip.so but the error is before in the mount.

I don’t think it will make any difference – that was a side question,
rather than a particular to this issue question.

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

“David Gibbs” <dagibbs@qnx.com> a écrit dans le message news:
b5ntj1$d3f$2@nntp.qnx.com
Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:

“David Gibbs” <> dagibbs@qnx.com> > a écrit dans le message news:
b5nr4m$bm2$> 1@nntp.qnx.com> …
Charles-Etienne Lemay <> charlesetienne@hermes.usherb.ca> > wrote:



Maybe try:

io-net &
mount -T io-net devn-rtl.so
mount -T io-net devn.orinoco.so
mount -T io-net -o if=en0:192.168.2.13 if=en1:192.168.2.15 npm-ttcpip.so

with that this is what I got :

Mount : Can’t mount / (type io-net)
Mount : Possible reason : Nosuch device or address

Ok, that’s back to the hardware side – not detecting the
orinoco card. I think there had been some conversation about
this already, but I haven’t been following it as closely (not
so much my area of expertise.)

Have you been asked for, and posted, the output of “pci -v”,
“pin” and “pin cis”?

pin -v : illégal option!

pin :
sock Func Type Flags PID Base Size
IRQ
1 Empty ----MF----------
1 Empty ----MF----------
2 0 Network C–NIF----------
10
2 Empty ----MF----------

pin cis : is kind of long!(but if you want if, I can tipe it!) I give you
the pin config

pin config 2 :
;socket 2¨
[device]
Manufacturer=“Lucent Technologies”
Product=“WaveLAN/IEEE”
info1=“Version 01.01”
info2=" "
Regbase=0x3e0
config=0x1,0x0600,irq any, io any+64 (width =16)
register=0,0x40,0x40 ; level mode interrupts









-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

here is a update of what I try this morning…

I have found the detail of the devn.orinoco.so on this web page : http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/utilities/d/devn-orinoco.so.html

My linksys wireless bridge is configure like this :

IP:192.168.2.71
OP:Infrastructure
SSID:Linksys
Channel:6
WEP:Disable

And here is the command to start the io-net

io-net -drtl
-dorinoco channel=6,irq=5,networks=Linksys
-pttcpip if=en0:10.63,if=en1:10.65

My ip address are configure in the net.cfg file.

The detail of the pin is that :

sock Func Type Flags PID Base Size IRQ
1 Empty ----MF----------
1 Empty ----MF----------
2 0 Network C–NIF---------- 5
2 Empty ----MF----------

The detail of the pin config 2 :

;socket 2¨
[device]
Manufacturer=“Lucent Technologies”
Product=“WaveLAN/IEEE”
info1=“Version 01.01”
info2=" "
Regbase=0x3e0
config=0x1,0x0600,irq any, io any+64 (width =16)
register=0,0x40,0x40 ; level mode interrupts


My error message are :

Unable to start “-dorinoco” (2)
Unable to start “-pttcpip” (2)
Unable to access “/dev/Socket” (2)
netmanager error ( ok this is normal because my en1 is not correct!)



Someone see something wrong?

Thanks


Charles-Etienne Lemay
TEAMSAT
Université de Sherbrooke
Tel: (819) 821-8000 ext. 1215
Fax: (819) 821-7937

Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:


Have you been asked for, and posted, the output of “pci -v”,
“pin” and “pin cis”?

pin -v : illégal option!

“pci -v” not “pin -v”

pin :
sock Func Type Flags PID Base Size
IRQ
1 Empty ----MF----------
1 Empty ----MF----------
2 0 Network C–NIF----------
10
2 Empty ----MF----------

pin cis : is kind of long!(but if you want if, I can tipe it!) I give you
the pin config

pin config 2 :
;socket 2¨
[device]
Manufacturer=“Lucent Technologies”
Product=“WaveLAN/IEEE”
info1=“Version 01.01”
info2=" "
Regbase=0x3e0
config=0x1,0x0600,irq any, io any+64 (width =16)
register=0,0x40,0x40 ; level mode interrupts






-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.


QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:



“David Gibbs” <> dagibbs@qnx.com> > a crit dans le message news:
b5q37s$p9l$> 1@nntp.qnx.com> …
Charles-Etienne Lemay <> charlesetienne@hermes.usherb.ca> > wrote:



Have you been asked for, and posted, the output of “pci -v”,
“pin” and “pin cis”?

pin -v : illgal option!

“pci -v” not “pin -v”

it’s to long, I can’t see the first sentences.
All a see is the vga adaptor!

Try:

pci -v > /tmp/pci.out

then post /tmp/pci.out here.

“David Gibbs” <dagibbs@qnx.com> a écrit dans le message news:
b5q37s$p9l$1@nntp.qnx.com
Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:


Have you been asked for, and posted, the output of “pci -v”,
“pin” and “pin cis”?

pin -v : illégal option!

“pci -v” not “pin -v”

it’s to long, I can’t see the first sentences.
All a see is the vga adaptor!

pin :
sock Func Type Flags PID Base Size
IRQ
1 Empty ----MF----------
1 Empty ----MF----------
2 0 Network C–NIF----------
10
2 Empty ----MF----------

pin cis : is kind of long!(but if you want if, I can tipe it!) I give you
the pin config

pin config 2 :
;socket 2¨
[device]
Manufacturer=“Lucent Technologies”
Product=“WaveLAN/IEEE”
info1=“Version 01.01”
info2=" "
Regbase=0x3e0
config=0x1,0x0600,irq any, io any+64 (width =16)
register=0,0x40,0x40 ; level mode interrupts






-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.


QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Have you been asked for, and posted, the output of “pci -v”,
“pin” and “pin cis”?

pin -v : illgal option!

“pci -v” not “pin -v”

it’s to long, I can’t see the first sentences.
All a see is the vga adaptor!

Try:

pci -v > /tmp/pci.out

then post /tmp/pci.out here.

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 1078h, Cyrix Corporation
Device ID = 1h, MediaGXm MMX Cyrix Integrated CPU
PCI index = 0h
Class Codes = 060000h
Revision ID = 0h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 280h
Command Reg = 7h
Header type = 0h Single-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 = NC
Interrupt line = 0

Class = Bridge (CardBus)
Vendor ID = 1180h, Ricoh Co Ltd
Device ID = 478h, RLc478 CardBus Controller
PCI index = 0h
Class Codes = 060700h
Revision ID = 80h
Bus number = 0
Device number = 10
Function num = 0
Status Reg = 210h
Command Reg = 7h
Header type = 2h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
ExCA Base Address = ffeff000h
Capabilities Pointer = ffh
Secondary Status = ffffh
Primary Bus Number = 0
Secondary Bus Number = 1
Subordinate Bus Number = 1
Secondary Latency Timer = 20h
Memory Base 0 = 0h
Memory Limit 0 = 0h
Memory Base 1 = 0h
Memory Limit 1 = 0h
I/O Base 0 = 0h
I/O Limit 0 = 0h
I/O Base 1 = 0h
I/O Limit 1 = 0h
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 9
Bridge Control = 700h
Subsystem Vendor ID = 0h
Subsystem ID = 0h
Legacy Mode Base Address = 0h
System Control = 0h
Retry Status = 0h
Card Control = 0h
Device Control = 0h
Buffer Control = 0h
Socket DMA Register 0 = 0h
Socket DMA Register 1 = 0h

Class = Bridge (CardBus)
Vendor ID = 1180h, Ricoh Co Ltd
Device ID = 478h, RLc478 CardBus Controller
PCI index = 1h
Class Codes = 060700h
Revision ID = 80h
Bus number = 0
Device number = 10
Function num = 1
Status Reg = 210h
Command Reg = 7h
Header type = 2h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
ExCA Base Address = ffefe000h
Capabilities Pointer = ffh
Secondary Status = ffffh
Primary Bus Number = 0
Secondary Bus Number = 2
Subordinate Bus Number = 2
Secondary Latency Timer = 20h
Memory Base 0 = 0h
Memory Limit 0 = 0h
Memory Base 1 = 0h
Memory Limit 1 = 0h
I/O Base 0 = 0h
I/O Limit 0 = 0h
I/O Base 1 = 0h
I/O Limit 1 = 0h
PCI Int Pin = 2
PCI Int Pin = INT B
Interrupt line = 9
Bridge Control = 700h
Subsystem Vendor ID = 0h
Subsystem ID = 0h
Legacy Mode Base Address = 0h
System Control = 0h
Retry Status = 0h
Card Control = 0h
Device Control = 0h
Buffer Control = 0h
Socket DMA Register 0 = 0h
Socket DMA Register 1 = 0h

Class = Network (Ethernet)
Vendor ID = 10ech, Realtek Semiconductor
Device ID = 8139h, RT8139A/B/C Fast Ethernet Adapter
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 0
Device number = 14
Function num = 0
Status Reg = 280h
Command Reg = 7h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
PCI IO Address = fc00h length 256 enabled
PCI Mem Address = 80001000h 32bit length 256 enabled
Subsystem Vendor ID = 10ech
Subsystem ID = 8139h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = 9

Class = Bridge (PCI/ISA)
Vendor ID = 1078h, Cyrix Corporation
Device ID = 100h, Cx5530 ISA bridge
PCI index = 0h
Class Codes = 060100h
Revision ID = 30h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 280h
Command Reg = 1fh
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 4h un-cacheable
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (Unknown)
Vendor ID = 1078h, Cyrix Corporation
Device ID = 101h, Cx5530 SMI status and ACPI timer
PCI index = 0h
Class Codes = 068000h
Revision ID = 0h
Bus number = 0
Device number = 18
Function num = 1
Status Reg = 280h
Command Reg = 2h
Header type = 0h Single-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 = NC
Interrupt line = 0

Class = Mass Storage (IDE)
Vendor ID = 1078h, Cyrix Corporation
Device ID = 102h, Cx5530 IDE Controller
PCI index = 0h
Class Codes = 010100h
Revision ID = 0h
Bus number = 0
Device number = 18
Function num = 2
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI IO Address = f800h length 16 enabled
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Multimedia (Audio)
Vendor ID = 1078h, Cyrix Corporation
Device ID = 103h, Cx5530 XpressAUDIO
PCI index = 0h
Class Codes = 040100h
Revision ID = 0h
Bus number = 0
Device number = 18
Function num = 3
Status Reg = 280h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI Mem Address = 40011000h 32bit length 128 enabled
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Display (VGA)
Vendor ID = 1078h, Cyrix Corporation
Device ID = 104h, Cx5530 Video Controller
PCI index = 0h
Class Codes = 030000h
Revision ID = 0h
Bus number = 0
Device number = 18
Function num = 4
Status Reg = 280h
Command Reg = 3h
Header type = 0h Multi-function
BIST = 2h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
PCI Mem Address = 40800000h 32bit length 8388608 enabled
Subsystem Vendor ID = 1078h
Subsystem ID = 1h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0



Has I see, mais card is not detect!

Charles-Etienne Lemay <charlesetienne@hermes.usherb.ca> wrote:

PCI version = 2.10

[Lots-O-Stuff deleted]

Has I see, mais card is not detect!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

My advice. If your going to add a comment like this, put it before
a long listing like the pci output. Not everyone will read to the
very end. When they get to the pci output they may be looking for
something very specific, making them blind to other comments like this.

Dam! That was the PCI bus that was not working, I have try with another and it works fine!

Thanks for your help
“Bernard Biron” <bb2@hermes.usherb.ca> a écrit dans le message news: b5fdl9$9qt$1@inn.qnx.com
Hi, I try to install a orinoco WiFi card on a PCMCIA module on a PC104 and it is not working!

this is what I try, I also got a ethernet adaptor and the drivers works fine:

#PCMCIA DEVICE
pci-bios
waitfor /dev/pci
devp-pccard -a 0x400 -l10,10
waitfor /dev/pccard
sleep 1
slay pci-bios
sleep 1
pci-bios
waitfor /dev/pci
sleep 1
devc-con -e -n4 &
#ETHARNET ET WIRELESS CARDS
io-net -d rtl -p ttcpip if=en0:192.168.2.13
pin
io-net -d orinoco ioport=0x400,irq=10 -v -p ttcpip if=en1:192.168.2.15
waitfor /dev/socket

Someone have try this before?


Charles-Etienne Lemay
TEAMSAT
Université de Sherbrooke
Tel: (819) 821-8000 ext. 1215
Fax: (819) 821-7937