Just installed QNX 6.2.1. I am having problems getting my network card to work properly.
I start with
slay -f io-net
then
io-net -d el900 verbose=10 -p tcpip
sloginfo reveals an error, “Cannot find an active PHY”:
Time Sev Major Minor Args
Jan 20 16:43:36 5 10 0 devn-el900: Vendor Id.=0x10b7 Device Id.=0x9001 pci index=0x0000 Irq=0x0005
Jan 20 16:43:36 5 10 0 Caps (a6). Card is a 90X
Jan 20 16:43:36 5 10 0 media_options: e138
Jan 20 16:43:36 2 10 0 devn-el900: Cannot find an active PHY
Jan 20 16:43:36 5 10 0 Media Options: e138
Jan 20 16:43:36 5 10 0 Internal Config: 10302d8
Jan 20 16:43:36 3 14 0 Using pseudo random generator. See “random” option
I ask about this error because when I execute dhcp.client, nothing happens. If I use the GUI network settings tool, I get an “unable to reach DHCP server” error when I select DHCP and click “apply”.
Here is the info on my network card:
Class = Network (Ethernet)
Vendor ID = 10b7h, 3Com Corporation
Device ID = 9001h, 3C900-COMBO Fast Etherlink XL PCI Combo NIC
PCI index = 0h
Class Codes = 020000h
Revision ID = 0h
Bus number = 0
Device number = 20
Function num = 0
Status Reg = 200h
Command Reg = 107h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = ee80h length 64 enabled
PCI Expansion ROM = ffac0000h length 65536 disabled
Max Lat = 8ns
Min Gnt = 3ns
PCI Int Pin = INT A
Interrupt line = 5
What does “nicinfo” say ? I have a feeling your “media rate” will be 0
cdm identified this problem with 3C900 years ago, don’t know if it is fixed.
Or maybe your problem is different.
It indeed has a Media Rate of 0.
Apparently, the QNX el900 driver doesn’t work with 3C900. It has a problem to detect the correct media rate.
What kind/speed of ethernet switch/hub do you have? Are you using CAT5 twisted pair cable?
Don’t know the brand of hub since it’s locked away in the network hardware rack in our building. We are wired for 10/100 MB ethernet, and I am connected to the wall with twisted-pair cable. This board works fine under Linux and Windows, so I figure it’s the driver. Too bad. I’ve got an ISA bus NE2000 compatible board as well, so I guess I’ll switch to that.
Seems like this is the case; sloginfo output posted in my original question mentions something about PHY. I have no idea what that is, but I figure it’s bad to have an error. I’ll try again with the NE2000 board.