Realtek 8139 Based Netcards

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

Is it possible to use a Realtek 8139 based netcard even if it is not
detected by nettrap?

Thanks, Ryan

2

Yes. Just try running it:

slay -f io-net
io-net -d rtl verbose -p tcpip

Also, nettrap is deprecated.

chris


Ryan <ryan@western.wave.ca> wrote:

Is it possible to use a Realtek 8139 based netcard even if it is not
detected by nettrap?

Thanks, Ryan

3

I ran it according to your suggestion, but it stated that the device was
not found. I know that under FreeBSD the identification string in the device
driver had to be updated for this newer card in order to be detected. Could
this be a similar problem?

“Chris McKillop” <hw@qnx.com> wrote in message
news:9h6o9p$pkh$2@nntp.qnx.com…

Yes. Just try running it:

slay -f io-net
io-net -d rtl verbose -p tcpip

Also, nettrap is deprecated.

chris


Ryan <> ryan@western.wave.ca> > wrote:

Is it possible to use a Realtek 8139 based netcard even if it is not
detected by nettrap?

Thanks, Ryan

4

Ryan <ryan@western.wave.ca> wrote:

I ran it according to your suggestion, but it stated that the device was
not found. I know that under FreeBSD the identification string in the device
driver had to be updated for this newer card in order to be detected. Could
this be a similar problem?

Perhaps. Want to post the output of “pci” here for us?

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

5

Sure. Here goes:

PCI version = 2.10

Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
IO Address = d000h enabled
Mem Address = e3000000h enabled
PCI Int Pin = INT A
Interrupt line = 4



“Chris McKillop” <hw@qnx.com> wrote in message
news:9h93pd$a6d$2@nntp.qnx.com…

Ryan <> ryan@western.wave.ca> > wrote:

I ran it according to your suggestion, but it stated that the device
was
not found. I know that under FreeBSD the identification string in the
device
driver had to be updated for this newer card in order to be detected.
Could
this be a similar problem?


Perhaps. Want to post the output of “pci” here for us?

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL

6

Hi Ryan,

Try running the driver specifying the device and vendor ids.

example:

io-net -drtl did=1300,vid=1186 -pttcpip

Regards,

Joe

Ryan <ryan@western.wave.ca> wrote:

Sure. Here goes:

PCI version = 2.10

Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
IO Address = d000h enabled
Mem Address = e3000000h enabled
PCI Int Pin = INT A
Interrupt line = 4



“Chris McKillop” <> hw@qnx.com> > wrote in message
news:9h93pd$a6d$> 2@nntp.qnx.com> …
Ryan <> ryan@western.wave.ca> > wrote:

I ran it according to your suggestion, but it stated that the device
was
not found. I know that under FreeBSD the identification string in the
device
driver had to be updated for this newer card in order to be detected.
Could
this be a similar problem?


Perhaps. Want to post the output of “pci” here for us?

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL

7

Hardware Support Account <hw@qnx.com> wrote:

Hi Ryan,

Try running the driver specifying the device and vendor ids.

example:

io-net -drtl did=1300,vid=1186 -pttcpip

Don’t forget the 0x’s…

… did=0x1300,vid=0x1186 …


chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

8

I have a SureCom PC CARD that uses the 8139. It is not autodetected, but
when I entered the commands (from earlier in this thread), then the
network card appears in the Network setup.

But it still doesn’t work. I’ve got networking going on my desktops, but
it won’t work for my laptop. The link is there (both ends have green
link leds), but I can’t communicate on the network. Won’t work with DHCP
(desktops worked fine) nor setting things up manually.

Note that the yellow activity led does blink when doing Ping, but there
is no response on the network. Other devices can’t see the laptop
either.

Any ideas?

BTW, this is also the behavior for my older LinkSys 10M card – it is
auto detected by QNX, but it won’t actually communicate on the network.

–
Brad Aisa <baisa@NOSPAMbrad-aisa.com>
http://www.brad-aisa.com/ – PGP public key available at:
http://pgp.mit.edu:11371/pks/lookup?search=Brad+Aisa&op=index

“Laissez faire.”

9

That probably means TCP/IP has not been configured properly. I’m not sure
why DHCP does not work, perhaps because it was started before network
interface was made available (since it is not autodetected). You might try
to kill and restart DHCP client after loading network driver (you don’t
really have to restart io-net). Also make sure driver gets proper irq and
ioport values (use ‘pin’ utility to find out what are right values), you can
supply them along with did/vid. In rare cases you might have to supply MAC
address to the driver as well.

slay -f io-net
io-net -d rtl did=0x1300,vid=0x1186,irq=xxx,ioport=0xXXX,mac=XXXXXXXXXXXX -p
tcpip &

OR

mount -T io-net -o
“did=0x1300,vid=0x1186,irq=xxx,ioport=0xXXX,mac=XXXXXXXXXXXX”
/lib/dll/devn-rtl.so

Then

slay -f dhcp.client
dhcp.client &

If you can’t get DHCP working try using manual configuration. You can do it
in the GUI tool or from command line (which I prefer):

ifconfig en0 <ip_address_here> netmask <network_mask_here>
route add default <gateway_address_here>

If you can not ping hosts on the same subnet after ‘ifconfig’ command,
something must be incompatible in the card. Might be using some custom PHY
…

  • igor

“Brad Aisa” <baisa@brad-aisa.com> wrote in message
news:3B3F7647.F25838FD@brad-aisa.com…

I have a SureCom PC CARD that uses the 8139. It is not autodetected, but
when I entered the commands (from earlier in this thread), then the
network card appears in the Network setup.

But it still doesn’t work. I’ve got networking going on my desktops, but
it won’t work for my laptop. The link is there (both ends have green
link leds), but I can’t communicate on the network. Won’t work with DHCP
(desktops worked fine) nor setting things up manually.

Note that the yellow activity led does blink when doing Ping, but there
is no response on the network. Other devices can’t see the laptop
either.

Any ideas?

BTW, this is also the behavior for my older LinkSys 10M card – it is
auto detected by QNX, but it won’t actually communicate on the network.

–
Brad Aisa <> baisa@NOSPAMbrad-aisa.com
http://www.brad-aisa.com/ > – PGP public key available at:
http://pgp.mit.edu:11371/pks/lookup?search=Brad+Aisa&op=index

“Laissez faire.”

10

I tried your suggestion ad verbum, but still its not detecting the card:

io-net -drtl did=0x1300,vid=0x1186 -pttcpip

unable to init dll devn-rtl: No such device

Thanks for the patience…

Ryan



“Chris McKillop” <cdm@qnx.com> wrote in message
news:9hjt99$3v7$1@nntp.qnx.com…

Hardware Support Account <> hw@qnx.com> > wrote:

Hi Ryan,

Try running the driver specifying the device and vendor ids.

example:

io-net -drtl did=1300,vid=1186 -pttcpip


Don’t forget the 0x’s…

… did=0x1300,vid=0x1186 …


chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL

11

Ryan <ryan@western.wave.ca> wrote:

I tried your suggestion ad verbum, but still its not detecting the card:

io-net -drtl did=0x1300,vid=0x1186 -pttcpip

unable to init dll devn-rtl: No such device

Thanks for the patience…

Did you recently buy this card? If so, what is the model number of the
card and where did you buy it?

chris

\

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

12

Yes, it’s a newer card. D-Link DFE-538TX. Apparently its a Canada only
release. I ran into a problem with it being detected in FreeBSD also, but
there were some patches available that updated the device driver to
recognize the card.

Ryan

Did you recently buy this card? If so, what is the model number of the
card and where did you buy it?

chris