SiS645 and SiS961 chipset

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:

I was referring to the orinoco driver: now that works for me, and that’s
great! > :slight_smile:

But my SiS ethernet card don’t, even though everything seems ok.

Please can you post the output from nicinfo after you have started the
driver and done an ifconfig and tried to ping it from another machine.
Unfortunately we don’t have the exact chipset that you have, so you
are going to have to help me on this one!

This is the output of the commands:

io-net -dsis9 verbose=4 -ptcpip

963_read_macaddr returned:
MAC Address … 047804 08a073
635_read_macaddr returned:
MAC Address … 00e018 eb402a
read_macaddr returned:
MAC Address … 00e018 eb402a

And the system log:

Time Sev Major Minor Args
Apr 21 14:33:41 5 10 0 devn-sis9: Vendor Id.=0x1039 Device
Id.=0x0900 pci index=0x0000 Irq=0x000b

Apr 21 14:33:47 2 10 0 devn-sis9: Can’t Access EEPROM Contents.
Apr 21 14:33:47 5 10 0 SiS900
Apr 21 14:33:47 5 10 0 Vendor … 0x1039
Apr 21 14:33:47 5 10 0 Device … 0x900
Apr 21 14:33:47 5 10 0 Revision … 0x0
Apr 21 14:33:47 5 10 0 I/O port base … 0xa000
Apr 21 14:33:47 5 10 0 Interrupt … 0xb
Apr 21 14:33:47 5 10 0 MAC address … 00e018 eb402a
Apr 21 14:33:48 5 14 0 tcpip starting
Apr 21 14:33:48 3 14 0 Using pseudo random generator. See
“random” option
Apr 21 14:33:50 5 10 0 sis9 (lan: 0): Link Up. (10bT)
Apr 21 14:33:53 5 10 0 sis9 (lan: 0): Link Up. (10bT)

As I told you before, nicinfo does not report transmission errors when I
ping from my machine, but I get “host unreachable”. I don’t know if that
depends on the driver or it’s just a normal TCP/IP configuration issue. I
guess my IP config is fine. I tried to use DHCP for the network card IP, but
I get an error from dhcp.client (old and updated version), like “can’t reach
DHCP server on interface en0”. So I try a static IP in my subnet, but other
machines in the same subnet can’t ping to me, and I can’t see any Rx packet
in nicinfo output. And that’s strange because I received many packets with
the MORE bit error.
So I don’t know what to think anymore. It should be an IP config problem,
but everything is set correctly and it doesn’t work. Any thoughts?

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030421145046.25854A@node90.ott.qnx.com> …
Sorry, but I’m confused! You said below that you were able to get an
adhoc connection to a Linux box. Now you say that networking is not
working?

Please do the following:

  1. slay io-net
  2. sloginfo -c
  3. io-net -dsis9 verbose=4 -ptcpip
  4. slay io-net
  5. sloginfo > file

Post the output ‘file’ from step 5.

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Unfortunately, networking doesn’t work yet.
I don’t think it’s because of the MORE bit error message… even when I
don’t get the error PING doesn’t work, either from or to my machine. And
nicinfo does not show Tx packet errors when I ping from my machine,
while
when I ping from another machine to mine no Rx packets are logged.

Btw, the exact error was: MORE bit not clear

I also have troubles with USB and SoundCard, both by SiS, but I’d be
happy
if at least the network worked.
Anyway, I try to use devu-ohci for USB - I get no errors, but also no
peripherals, and if I try to enable usb mouse no usbmouse device is
created
(which seems reasonable, since it’s not detected).
For the soundocard I saw there’s a reference to some deva-ctrl-sis.so
driver
in /etc/system/enum/audio - I wanted to try that, but I haven’t on my HD
and
I installed both QNX Neutrino and the Momentics suite.

Paolo


“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030421080233.24773A@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Thanks, I was able to get an adhoc connection working, even with a
Linux
machine.

As for my SiS network card I get this error in the system log:
devn-sis9.so: Bit MORE clear (or similar)

What is it?


This means that the receive logic found a descriptor with the MORE bit
clear, when it was expecting the MORE bit to be set. Otherwise, is the
driver working OK? Do you get this status in the sloginfo often?

Btw, now nicinfo shows that my card has a non-zero MAC address, so the
fix
is working.

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030415075502.28523A@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
We also hope to see the updated orinoco driver soon…


Take a look, the orinoco driver is there already!

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030411141242.10475L@node90.ott.qnx.com> …
Previously, Jir Kristek wrote in qdn.public.qnxrtp.os:
Please, will you get out the driver to the experimental section.


I will have the updated driver posted at > http://developers.qnx.com
in the next few days.


[snip]






\

Well, I’m going mad with that…
I tried once again and I was able to ping from another Windows machine to my
laptop, but not back to the other machine. I’m not sure, however, that this
Windows machine didn’t have some AntiVirus firewall or similar.
As soon as I find a crossed cable I’m going to try with a direct connection,
so far I was using a hub and I was connected to a LAN.
I guess those packets I receive with the MORE bit error are generated when I
first announce my presence to the LAN, and maybe they’re some Windows
machine that tries to connect with NetBIOS to my laptop, as they do when I
boot with Windows.
I also tried again with DHCP, activating the debug option, but I don’t get
any error message in the syslog. The strange thing is that the number of
sent packets in nicinfo does not increase. Is this normal with DHCP?

Paolo

“Hugh Brown” <hsbrown@qnx.com> ha scritto nel messaggio
news:Voyager.030422094207.19912A@node90.ott.qnx.com

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
I was referring to the orinoco driver: now that works for me, and that’s
great! > :slight_smile:

But my SiS ethernet card don’t, even though everything seems ok.


Please can you post the output from nicinfo after you have started the
driver and done an ifconfig and tried to ping it from another machine.
Unfortunately we don’t have the exact chipset that you have, so you
are going to have to help me on this one!

This is the output of the commands:

io-net -dsis9 verbose=4 -ptcpip

963_read_macaddr returned:
MAC Address … 047804 08a073
635_read_macaddr returned:
MAC Address … 00e018 eb402a
read_macaddr returned:
MAC Address … 00e018 eb402a

And the system log:

Time Sev Major Minor Args
Apr 21 14:33:41 5 10 0 devn-sis9: Vendor Id.=0x1039 Device
Id.=0x0900 pci index=0x0000 Irq=0x000b

Apr 21 14:33:47 2 10 0 devn-sis9: Can’t Access EEPROM
Contents.
Apr 21 14:33:47 5 10 0 SiS900
Apr 21 14:33:47 5 10 0 Vendor … 0x1039
Apr 21 14:33:47 5 10 0 Device … 0x900
Apr 21 14:33:47 5 10 0 Revision … 0x0
Apr 21 14:33:47 5 10 0 I/O port base … 0xa000
Apr 21 14:33:47 5 10 0 Interrupt … 0xb
Apr 21 14:33:47 5 10 0 MAC address … 00e018 eb402a
Apr 21 14:33:48 5 14 0 tcpip starting
Apr 21 14:33:48 3 14 0 Using pseudo random generator. See
“random” option
Apr 21 14:33:50 5 10 0 sis9 (lan: 0): Link Up. (10bT)
Apr 21 14:33:53 5 10 0 sis9 (lan: 0): Link Up. (10bT)

As I told you before, nicinfo does not report transmission errors when I
ping from my machine, but I get “host unreachable”. I don’t know if that
depends on the driver or it’s just a normal TCP/IP configuration issue.
I
guess my IP config is fine. I tried to use DHCP for the network card IP,
but
I get an error from dhcp.client (old and updated version), like “can’t
reach
DHCP server on interface en0”. So I try a static IP in my subnet, but
other
machines in the same subnet can’t ping to me, and I can’t see any Rx
packet
in nicinfo output. And that’s strange because I received many packets
with
the MORE bit error.
So I don’t know what to think anymore. It should be an IP config
problem,
but everything is set correctly and it doesn’t work. Any thoughts?

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030421145046.25854A@node90.ott.qnx.com> …
Sorry, but I’m confused! You said below that you were able to get an
adhoc connection to a Linux box. Now you say that networking is not
working?

Please do the following:

  1. slay io-net
  2. sloginfo -c
  3. io-net -dsis9 verbose=4 -ptcpip
  4. slay io-net
  5. sloginfo > file

Post the output ‘file’ from step 5.

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Unfortunately, networking doesn’t work yet.
I don’t think it’s because of the MORE bit error message… even
when I
don’t get the error PING doesn’t work, either from or to my machine.
And
nicinfo does not show Tx packet errors when I ping from my machine,
while
when I ping from another machine to mine no Rx packets are logged.

Btw, the exact error was: MORE bit not clear

I also have troubles with USB and SoundCard, both by SiS, but I’d be
happy
if at least the network worked.
Anyway, I try to use devu-ohci for USB - I get no errors, but also
no
peripherals, and if I try to enable usb mouse no usbmouse device is
created
(which seems reasonable, since it’s not detected).
For the soundocard I saw there’s a reference to some
deva-ctrl-sis.so
driver
in /etc/system/enum/audio - I wanted to try that, but I haven’t on
my HD
and
I installed both QNX Neutrino and the Momentics suite.

Paolo


“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030421080233.24773A@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Thanks, I was able to get an adhoc connection working, even with a
Linux
machine.

As for my SiS network card I get this error in the system log:
devn-sis9.so: Bit MORE clear (or similar)

What is it?


This means that the receive logic found a descriptor with the MORE
bit
clear, when it was expecting the MORE bit to be set. Otherwise, is
the
driver working OK? Do you get this status in the sloginfo often?

Btw, now nicinfo shows that my card has a non-zero MAC address, so
the
fix
is working.

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030415075502.28523A@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
We also hope to see the updated orinoco driver soon…


Take a look, the orinoco driver is there already!

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030411141242.10475L@node90.ott.qnx.com> …
Previously, Jir Kristek wrote in qdn.public.qnxrtp.os:
Please, will you get out the driver to the experimental
section.


I will have the updated driver posted at
http://developers.qnx.com
in the next few days.


[snip]







\

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:

Well, I’m going mad with that…
I tried once again and I was able to ping from another Windows machine to my
laptop, but not back to the other machine. I’m not sure, however, that this
Windows machine didn’t have some AntiVirus firewall or similar.
As soon as I find a crossed cable I’m going to try with a direct connection,
so far I was using a hub and I was connected to a LAN.
I guess those packets I receive with the MORE bit error are generated when I
first announce my presence to the LAN, and maybe they’re some Windows
machine that tries to connect with NetBIOS to my laptop, as they do when I
boot with Windows.
I also tried again with DHCP, activating the debug option, but I don’t get
any error message in the syslog. The strange thing is that the number of
sent packets in nicinfo does not increase. Is this normal with DHCP?

No, you should see the sent packets as well as the sent bytes counters
incrementing if the driver is working correctly. What make and model laptop
is this?

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030422094207.19912A@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
I was referring to the orinoco driver: now that works for me, and that’s
great! > :slight_smile:

But my SiS ethernet card don’t, even though everything seems ok.


Please can you post the output from nicinfo after you have started the
driver and done an ifconfig and tried to ping it from another machine.
Unfortunately we don’t have the exact chipset that you have, so you
are going to have to help me on this one!

This is the output of the commands:

io-net -dsis9 verbose=4 -ptcpip

963_read_macaddr returned:
MAC Address … 047804 08a073
635_read_macaddr returned:
MAC Address … 00e018 eb402a
read_macaddr returned:
MAC Address … 00e018 eb402a

And the system log:

Time Sev Major Minor Args
Apr 21 14:33:41 5 10 0 devn-sis9: Vendor Id.=0x1039 Device
Id.=0x0900 pci index=0x0000 Irq=0x000b

Apr 21 14:33:47 2 10 0 devn-sis9: Can’t Access EEPROM
Contents.
Apr 21 14:33:47 5 10 0 SiS900
Apr 21 14:33:47 5 10 0 Vendor … 0x1039
Apr 21 14:33:47 5 10 0 Device … 0x900
Apr 21 14:33:47 5 10 0 Revision … 0x0
Apr 21 14:33:47 5 10 0 I/O port base … 0xa000
Apr 21 14:33:47 5 10 0 Interrupt … 0xb
Apr 21 14:33:47 5 10 0 MAC address … 00e018 eb402a
Apr 21 14:33:48 5 14 0 tcpip starting
Apr 21 14:33:48 3 14 0 Using pseudo random generator. See
“random” option
Apr 21 14:33:50 5 10 0 sis9 (lan: 0): Link Up. (10bT)
Apr 21 14:33:53 5 10 0 sis9 (lan: 0): Link Up. (10bT)

As I told you before, nicinfo does not report transmission errors when I
ping from my machine, but I get “host unreachable”. I don’t know if that
depends on the driver or it’s just a normal TCP/IP configuration issue.
I
guess my IP config is fine. I tried to use DHCP for the network card IP,
but
I get an error from dhcp.client (old and updated version), like “can’t
reach
DHCP server on interface en0”. So I try a static IP in my subnet, but
other
machines in the same subnet can’t ping to me, and I can’t see any Rx
packet
in nicinfo output. And that’s strange because I received many packets
with
the MORE bit error.
So I don’t know what to think anymore. It should be an IP config
problem,
but everything is set correctly and it doesn’t work. Any thoughts?

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030421145046.25854A@node90.ott.qnx.com> …
Sorry, but I’m confused! You said below that you were able to get an
adhoc connection to a Linux box. Now you say that networking is not
working?

Please do the following:

  1. slay io-net
  2. sloginfo -c
  3. io-net -dsis9 verbose=4 -ptcpip
  4. slay io-net
  5. sloginfo > file

Post the output ‘file’ from step 5.

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Unfortunately, networking doesn’t work yet.
I don’t think it’s because of the MORE bit error message… even
when I
don’t get the error PING doesn’t work, either from or to my machine.
And
nicinfo does not show Tx packet errors when I ping from my machine,
while
when I ping from another machine to mine no Rx packets are logged.

Btw, the exact error was: MORE bit not clear

I also have troubles with USB and SoundCard, both by SiS, but I’d be
happy
if at least the network worked.
Anyway, I try to use devu-ohci for USB - I get no errors, but also
no
peripherals, and if I try to enable usb mouse no usbmouse device is
created
(which seems reasonable, since it’s not detected).
For the soundocard I saw there’s a reference to some
deva-ctrl-sis.so
driver
in /etc/system/enum/audio - I wanted to try that, but I haven’t on
my HD
and
I installed both QNX Neutrino and the Momentics suite.

Paolo


“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030421080233.24773A@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Thanks, I was able to get an adhoc connection working, even with a
Linux
machine.

As for my SiS network card I get this error in the system log:
devn-sis9.so: Bit MORE clear (or similar)

What is it?


This means that the receive logic found a descriptor with the MORE
bit
clear, when it was expecting the MORE bit to be set. Otherwise, is
the
driver working OK? Do you get this status in the sloginfo often?

Btw, now nicinfo shows that my card has a non-zero MAC address, so
the
fix
is working.

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030415075502.28523A@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
We also hope to see the updated orinoco driver soon…


Take a look, the orinoco driver is there already!

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030411141242.10475L@node90.ott.qnx.com> …
Previously, Jir Kristek wrote in qdn.public.qnxrtp.os:
Please, will you get out the driver to the experimental
section.


I will have the updated driver posted at
http://developers.qnx.com
in the next few days.


[snip]










\

I have an ASUS Notebook, model L3180M, with SiS 740 chipset, SiS 900
Ethernet card, SiS 7012 Audio card, SiS 7013 modem that identifies itself as
“PCtel HSP56 MR Data/Fax”.

I tried a cross-over connection, and after choosing a private IP network
(10.0.0.1/16) I got ping working on both sides. But yet dhcp doesn’t work,
as I described.

Paolo

“Hugh Brown” <hsbrown@qnx.com> ha scritto nel messaggio
news:Voyager.030423125016.31025C@node90.ott.qnx.com

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Well, I’m going mad with that…
I tried once again and I was able to ping from another Windows machine
to my
laptop, but not back to the other machine. I’m not sure, however, that
this
Windows machine didn’t have some AntiVirus firewall or similar.
As soon as I find a crossed cable I’m going to try with a direct
connection,
so far I was using a hub and I was connected to a LAN.
I guess those packets I receive with the MORE bit error are generated
when I
first announce my presence to the LAN, and maybe they’re some Windows
machine that tries to connect with NetBIOS to my laptop, as they do when
I
boot with Windows.
I also tried again with DHCP, activating the debug option, but I don’t
get
any error message in the syslog. The strange thing is that the number of
sent packets in nicinfo does not increase. Is this normal with DHCP?


No, you should see the sent packets as well as the sent bytes counters
incrementing if the driver is working correctly. What make and model
laptop
is this?

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:

I have an ASUS Notebook, model L3180M, with SiS 740 chipset, SiS 900
Ethernet card, SiS 7012 Audio card, SiS 7013 modem that identifies itself as
“PCtel HSP56 MR Data/Fax”.

I tried a cross-over connection, and after choosing a private IP network
(10.0.0.1/16) I got ping working on both sides. But yet dhcp doesn’t work,
as I described.

Well, if ping is working, then the network driver must be working. As far
as the dhcp side is concerned, you will have to check the setup of your
dhcp server.

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030423125016.31025C@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Well, I’m going mad with that…
I tried once again and I was able to ping from another Windows machine
to my
laptop, but not back to the other machine. I’m not sure, however, that
this
Windows machine didn’t have some AntiVirus firewall or similar.
As soon as I find a crossed cable I’m going to try with a direct
connection,
so far I was using a hub and I was connected to a LAN.
I guess those packets I receive with the MORE bit error are generated
when I
first announce my presence to the LAN, and maybe they’re some Windows
machine that tries to connect with NetBIOS to my laptop, as they do when
I
boot with Windows.
I also tried again with DHCP, activating the debug option, but I don’t
get
any error message in the syslog. The strange thing is that the number of
sent packets in nicinfo does not increase. Is this normal with DHCP?


No, you should see the sent packets as well as the sent bytes counters
incrementing if the driver is working correctly. What make and model
laptop
is this?

Previously, Hugh Brown wrote in qdn.public.qnxrtp.os:

Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
I have an ASUS Notebook, model L3180M, with SiS 740 chipset, SiS 900
Ethernet card, SiS 7012 Audio card, SiS 7013 modem that identifies itself as
“PCtel HSP56 MR Data/Fax”.

I tried a cross-over connection, and after choosing a private IP network
(10.0.0.1/16) I got ping working on both sides. But yet dhcp doesn’t work,
as I described.


Well, if ping is working, then the network driver must be working. As far
as the dhcp side is concerned, you will have to check the setup of your
dhcp server.

When you talk about dhcp, are you trying to run dhcp.client under QNX6, or
are you trying to dhcp boot the machine?

Paolo

“Hugh Brown” <> hsbrown@qnx.com> > ha scritto nel messaggio
news:> Voyager.030423125016.31025C@node90.ott.qnx.com> …
Previously, Paolo Messina wrote in qdn.public.qnxrtp.os:
Well, I’m going mad with that…
I tried once again and I was able to ping from another Windows machine
to my
laptop, but not back to the other machine. I’m not sure, however, that
this
Windows machine didn’t have some AntiVirus firewall or similar.
As soon as I find a crossed cable I’m going to try with a direct
connection,
so far I was using a hub and I was connected to a LAN.
I guess those packets I receive with the MORE bit error are generated
when I
first announce my presence to the LAN, and maybe they’re some Windows
machine that tries to connect with NetBIOS to my laptop, as they do when
I
boot with Windows.
I also tried again with DHCP, activating the debug option, but I don’t
get
any error message in the syslog. The strange thing is that the number of
sent packets in nicinfo does not increase. Is this normal with DHCP?


No, you should see the sent packets as well as the sent bytes counters
incrementing if the driver is working correctly. What make and model
laptop
is this?

\

When you talk about dhcp, are you trying to run dhcp.client under QNX6, or
are you trying to dhcp boot the machine?

No, I just tried to use dhcp.client to configure my IP address. I will try
again using the dhcp server address.

Paolo