Hi there!
I have a problem with my network access under qnx(wot surprise). under windows everything works perfect, so there isn’t nor a hardware problem neither a problem with the access itself.
I have a K75SA board with a network sis900 on board.
I had installed qnx 6.2.0 and tried a lot of things to get the network running. but there was no success. then I found out, that there is a new driver(sis900.so). So, i got qnx 6.2.1. nc and installed it completely new. but the network still isn’t running. I can ping myself(my IP), can ping others in my intranet and can ping the default gateway. but I can’t ping anyone outside the intranet. the nameserver seems to work, cos I get an IP when I try to ping www.qnx.com for instance.
wots funny, is that nicinfo gives for the first two entries series of 0s. and the bit rate is 0 as well!
so, wot can I do?
how can I configure the access manually step by step?
how can I find the source of error?
thanks a lot for any help!!!
Did you setup the gateway “route add default x.x.x.x”, are you using dhcp? Bit rate 0 hum that’s odd cause if you can ping other machine it means the interface is up and running. You could try forcing a bit rate in case there is a problem with auto-detect.
I don’t use dhcp. I just configure all data manually with phlip and restart afterwards. then all the ping stuff works as described above. >route show< shows also the correct gateway.
I tried to force the bit rate by means of >io-net<. the followings shows what I’ve done:
slay io-net<
pci -vvv<
OUTPUT:
…[
Class = Network (Ethernet)
Vendor ID = 1039h, Silicon Integrated System
Device ID = 900h, SiS900 Fast Ethernet/Home Networking Ctrlr
PCI index = 0h
Class Codes = 020000h
Revision ID = 90h
Bus number = 0
Device number = 3
Function num = 0
Status Reg = 290h
Command Reg = 107h
I/O space access enabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents enabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
PCI IO Address = d400h length 256 enabled
PCI Mem Address = cffff000h 32bit length 4096 enabled
Subsystem Vendor ID = 1019h
Subsystem ID = a14h
PCI Expansion ROM = cffc0000h length 131072 disabled
Max Lat = 11ns
Min Gnt = 52ns
PCI Int Pin = INT A
Interrupt line = 5
Capabilities Pointer = 40h
Capability ID = 1h
Capabilities = fe02h - 100h
Device Dependent Registers:
0x40: 01 00 02 fe 00 01 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
]…
<# io-net -dsis9 did=0x900,vid=0x1039,duplex=1,speed=100,mtu=1,verbose=4 -ptcpip &>
OUTPUT:
[
[2] 1064978
SiS900
Vendor … 0x1039
Device … 0x900
Revision … 0x0
I/O port base … 0xd400
Interrupt … 0x5
MAC address … 000000 000000
]
hope, you could follow my steps! I’ve no idea, but this line from doesn’t look healthy:
Jan 15 16:58:18 2 10 0 devn-sis9: Can’t Access EEPROM Contents.
maybe that’s the problem?
BTW the info from hasn’t change at all after the steps!
let’s say your default gateway is 192.168.1.1
first, ping 192.168.1.1 and make sure it works.
then, run “route add default 192.168.1.1” to add the default gateway. now “netstat -rn” should show the default route going to your gateway 192.168.1.1
you should be able to ping yahoo now.
You may also try doing an ‘arp -a’ on another machine and see if you are actually using 00:00:00:00:00:00 as your mac address. If so, your gateway may have problems with that (or any computer or switch for that matter). You can set the mac address by hand in the io-net command I believe.
Fix: This is an updated version of the Sis900 Ethernet driver, to work on the latest revision of the chipset that doesn’t have the MAC address in EEPROM. The revisions concerned are 0x90 and 9x91. You will need to use (provided below) a new nicinfo utility with this driver.
ok, I made a few steps further!
Now, I’m able to ping for instance www.yahoo.com. but I can’t access that page with a browser(voyager, mozilla). neither can I load other pages. after I started once a browser I’m not able anymore to ping any host even when the browser is closed again. It needs a complete restart!
what have I done so far:
I got the patches for devn-sis9.so and nicinfo and “installed” them be just swapping the originals with the patches in /usr/sbin resp. /lib/dll Is that correct?
At least the nicinfo shows now logical entries!
I still can’t use the DHCP by means of PhLIP: after a while it says “Could not reach DHCP server on interface en0”
I got a 2 entries from SLOGINFO which may have to deal with the problem:
- devn-sis9.so MORE bit not clean
and after starting a browser: - Service cmd 0x22 returned errno 22
still hoping anybody can help me!!!
primel - are you using pppoe?
No, I don’t use pppoe!
Does nobody have an idea? 
Can I try something elso, so that I know the browser is “guilty”?
I had similar problems with D-Link aka Realtek… I had to dig around in;
etc/system/enum/devices/
On restart the configuration gets reset by the auto detect. I also found two spurious characters on the mount command…once i removed them then the card auto detected properly. However the card only runs at half duplex. I have to slay the io-net and redo manually to get full duplex.
I used -p tcpip and when I set to dhcp on devices Tab it loaded pppoe automatically on any attempt to connect to internet. If I had the settings wrong for the card I got an error message that pppoe could not connect because of invalid sockets …or some informative message.
- Try disable enum devices on restart.
- Check for proper config startup in the etc/system/enum/devices/
- I hope this applies to ur problem too.
ss