Anyone have any luck getting this NIC working under QNX 6.1? Its a realtek
based NIC (8139C), yet the rtl driver wont load for it.
8139 drivers under every other OS work flawlessly. (win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
Could you post the output from pci -vvv?
Regards,
Dave B.
Chad Fewer wrote:
Anyone have any luck getting this NIC working under QNX 6.1? Its a realtek
based NIC (8139C), yet the rtl driver wont load for it.8139 drivers under every other OS work flawlessly. (win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
Dave,
The system is using an ASUS A7V Motherboard, with a VIA Tech chipset.
(VT8363). I’ve pulled the card, swapped it around available PCI slots,
still nothing. I’ve also tried Enabling/Disabling PNP OS settings in the
BIOS with no effect.
Thanx for any help.
Chad.
pci -vvv follows for network device …
Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 0
Device number = 12
Function num = 0
Status Reg = 290h
Command Reg = 7h
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 disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = ah
Cache Line Size= 0h
PCI IO Address = a400h length 256 enabled
PCI Mem Address = d4800000h 32bit length 256 enabled
Subsystem Vendor ID = 1186h
Subsystem ID = 1300h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = f7c2h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 c2 f7 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Applications Support Account wrote:
Could you post the output from pci -vvv?
Regards,
Dave B.
Chad Fewer wrote:
Anyone have any luck getting this NIC working under QNX 6.1? Its a
realtek based NIC (8139C), yet the rtl driver wont load for it.8139 drivers under every other OS work flawlessly. (win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
I got the same problem with that card
under linux I use the via-rhine driver and it’s work fine but the QNX
via-rhine driver isn’t working
Jeff
“Chad Fewer” <cfewer1@cogeco.ca> wrote in message
news:abh0ss$ppu$1@inn.qnx.com…
Dave,
The system is using an ASUS A7V Motherboard, with a VIA Tech chipset.
(VT8363). I’ve pulled the card, swapped it around available PCI slots,
still nothing. I’ve also tried Enabling/Disabling PNP OS settings in the
BIOS with no effect.Thanx for any help.
Chad.
pci -vvv follows for network device …
Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 0
Device number = 12
Function num = 0
Status Reg = 290h
Command Reg = 7h
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 disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = ah
Cache Line Size= 0h
PCI IO Address = a400h length 256 enabled
PCI Mem Address = d4800000h 32bit length 256 enabled
Subsystem Vendor ID = 1186h
Subsystem ID = 1300h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = f7c2h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 c2 f7 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Applications Support Account wrote:Could you post the output from pci -vvv?
Regards,
Dave B.
Chad Fewer wrote:
Anyone have any luck getting this NIC working under QNX 6.1? Its a
realtek based NIC (8139C), yet the rtl driver wont load for it.8139 drivers under every other OS work flawlessly.
(win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
\
Hi
If you download the Unix driver from Dlink for the 530TX+ (which is what
the PCI ID comes out as if you look here:
http://www.yourvote.com/pci/vendors.txt)
then you’ll see that the chip is a Realtek 8139 clone.
So, I suggest that you try using our Realtek driver using the ‘did’ and
‘vid’ arguments to explicitly pass the vendor and device IDs that you
show below i.e. did=0x1300 vid=0x1186
There are so many clones that our drivers usually have this mechanism as
an override.
Hope that helps
Dave
Jeff wrote:
I got the same problem with that card
under linux I use the via-rhine driver and it’s work fine but the QNX
via-rhine driver isn’t working
Jeff“Chad Fewer” <> cfewer1@cogeco.ca> > wrote in message
news:abh0ss$ppu$> 1@inn.qnx.com> …Dave,
The system is using an ASUS A7V Motherboard, with a VIA Tech chipset.
(VT8363). I’ve pulled the card, swapped it around available PCI slots,
still nothing. I’ve also tried Enabling/Disabling PNP OS settings in the
BIOS with no effect.Thanx for any help.
Chad.
pci -vvv follows for network device …
Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 0
Device number = 12
Function num = 0
Status Reg = 290h
Command Reg = 7h
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 disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = ah
Cache Line Size= 0h
PCI IO Address = a400h length 256 enabled
PCI Mem Address = d4800000h 32bit length 256 enabled
Subsystem Vendor ID = 1186h
Subsystem ID = 1300h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = f7c2h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 c2 f7 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Applications Support Account wrote:
Could you post the output from pci -vvv?Regards,
Dave B.
Chad Fewer wrote:Anyone have any luck getting this NIC working under QNX 6.1? Its a
realtek based NIC (8139C), yet the rtl driver wont load for it.8139 drivers under every other OS work flawlessly.
(win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
I try
#io-net -d rtl did=0x1300 vid=0x1186
and I got
unable to init dll devn-rtl: No such device
I also try with
io-net -d rtl did=0x1300 vid=0x1186 pci=0x0 irq=5
and I still got
unable to init dll devn-rtl: No such device
Jeff
“Dave Bott” <dbott@qnx.com> wrote in message
news:3CED5545.8050406@qnx.com…
Hi
If you download the Unix driver from Dlink for the 530TX+ (which is what
the PCI ID comes out as if you look here:
http://www.yourvote.com/pci/vendors.txt> )
then you’ll see that the chip is a Realtek 8139 clone.So, I suggest that you try using our Realtek driver using the ‘did’ and
‘vid’ arguments to explicitly pass the vendor and device IDs that you
show below i.e. did=0x1300 vid=0x1186There are so many clones that our drivers usually have this mechanism as
an override.Hope that helps
Dave
Jeff wrote:
I got the same problem with that card
under linux I use the via-rhine driver and it’s work fine but the QNX
via-rhine driver isn’t working
Jeff“Chad Fewer” <> cfewer1@cogeco.ca> > wrote in message
news:abh0ss$ppu$> 1@inn.qnx.com> …Dave,
The system is using an ASUS A7V Motherboard, with a VIA Tech chipset.
(VT8363). I’ve pulled the card, swapped it around available PCI slots,
still nothing. I’ve also tried Enabling/Disabling PNP OS settings in the
BIOS with no effect.Thanx for any help.
Chad.
pci -vvv follows for network device …
Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 0
Device number = 12
Function num = 0
Status Reg = 290h
Command Reg = 7h
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 disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = ah
Cache Line Size= 0h
PCI IO Address = a400h length 256 enabled
PCI Mem Address = d4800000h 32bit length 256 enabled
Subsystem Vendor ID = 1186h
Subsystem ID = 1300h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = f7c2h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 c2 f7 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Applications Support Account wrote:
Could you post the output from pci -vvv?Regards,
Dave B.
Chad Fewer wrote:Anyone have any luck getting this NIC working under QNX 6.1? Its a
realtek based NIC (8139C), yet the rtl driver wont load for it.8139 drivers under every other OS work flawlessly.
(win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
it is…
io-net -d rtl did=0x1300,vid=0x1186
…no space allowed.
chris
Jeff <cyberlogik@hotmail.com> wrote:
I try
#io-net -d rtl did=0x1300 vid=0x1186
and I got
unable to init dll devn-rtl: No such device
I also try withio-net -d rtl did=0x1300 vid=0x1186 pci=0x0 irq=5
and I still got
unable to init dll devn-rtl: No such deviceJeff
“Dave Bott” <> dbott@qnx.com> > wrote in message
news:> 3CED5545.8050406@qnx.com> …
HiIf you download the Unix driver from Dlink for the 530TX+ (which is what
the PCI ID comes out as if you look here:
http://www.yourvote.com/pci/vendors.txt> )
then you’ll see that the chip is a Realtek 8139 clone.So, I suggest that you try using our Realtek driver using the ‘did’ and
‘vid’ arguments to explicitly pass the vendor and device IDs that you
show below i.e. did=0x1300 vid=0x1186There are so many clones that our drivers usually have this mechanism as
an override.Hope that helps
Dave
Jeff wrote:
I got the same problem with that card
under linux I use the via-rhine driver and it’s work fine but the QNX
via-rhine driver isn’t working
Jeff“Chad Fewer” <> cfewer1@cogeco.ca> > wrote in message
news:abh0ss$ppu$> 1@inn.qnx.com> …Dave,
The system is using an ASUS A7V Motherboard, with a VIA Tech chipset.
(VT8363). I’ve pulled the card, swapped it around available PCI slots,
still nothing. I’ve also tried Enabling/Disabling PNP OS settings in the
BIOS with no effect.Thanx for any help.
Chad.
pci -vvv follows for network device …
Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 0
Device number = 12
Function num = 0
Status Reg = 290h
Command Reg = 7h
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 disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = ah
Cache Line Size= 0h
PCI IO Address = a400h length 256 enabled
PCI Mem Address = d4800000h 32bit length 256 enabled
Subsystem Vendor ID = 1186h
Subsystem ID = 1300h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = f7c2h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 c2 f7 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Applications Support Account wrote:
Could you post the output from pci -vvv?Regards,
Dave B.
Chad Fewer wrote:Anyone have any luck getting this NIC working under QNX 6.1? Its a
realtek based NIC (8139C), yet the rtl driver wont load for it.8139 drivers under every other OS work flawlessly.
(win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
\
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
“Chris McKillop” <cdm@qnx.com> wrote in message
news:acuu8f$8ea$1@nntp.qnx.com…
it is…
io-net -d rtl did=0x1300,vid=0x1186
…no space allowed.
chris
I still got
unable to init dll devn-rtl: No such device
The card work fine under linux and windows 2000.
I have the QNX 6.1 distribution
Jeff
Jeff <> cyberlogik@hotmail.com> > wrote:
I try#io-net -d rtl did=0x1300 vid=0x1186
and I got
unable to init dll devn-rtl: No such device
I also try withio-net -d rtl did=0x1300 vid=0x1186 pci=0x0 irq=5
and I still got
unable to init dll devn-rtl: No such deviceJeff
“Dave Bott” <> dbott@qnx.com> > wrote in message
news:> 3CED5545.8050406@qnx.com> …
HiIf you download the Unix driver from Dlink for the 530TX+ (which is
what
the PCI ID comes out as if you look here:
http://www.yourvote.com/pci/vendors.txt> )
then you’ll see that the chip is a Realtek 8139 clone.So, I suggest that you try using our Realtek driver using the ‘did’ and
‘vid’ arguments to explicitly pass the vendor and device IDs that you
show below i.e. did=0x1300 vid=0x1186There are so many clones that our drivers usually have this mechanism
as
an override.Hope that helps
Dave
Jeff wrote:
I got the same problem with that card
under linux I use the via-rhine driver and it’s work fine but the QNX
via-rhine driver isn’t working
Jeff“Chad Fewer” <> cfewer1@cogeco.ca> > wrote in message
news:abh0ss$ppu$> 1@inn.qnx.com> …Dave,
The system is using an ASUS A7V Motherboard, with a VIA Tech chipset.
(VT8363). I’ve pulled the card, swapped it around available PCI
slots,
still nothing. I’ve also tried Enabling/Disabling PNP OS settings in
the
BIOS with no effect.Thanx for any help.
Chad.
pci -vvv follows for network device …
Class = Network (Ethernet)
Vendor ID = 1186h, D-Link System Inc
Device ID = 1300h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 0
Device number = 12
Function num = 0
Status Reg = 290h
Command Reg = 7h
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 disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = ah
Cache Line Size= 0h
PCI IO Address = a400h length 256 enabled
PCI Mem Address = d4800000h 32bit length 256 enabled
Subsystem Vendor ID = 1186h
Subsystem ID = 1300h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = f7c2h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 c2 f7 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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Applications Support Account wrote:
Could you post the output from pci -vvv?Regards,
Dave B.
Chad Fewer wrote:Anyone have any luck getting this NIC working under QNX 6.1? Its a
realtek based NIC (8139C), yet the rtl driver wont load for it.8139 drivers under every other OS work flawlessly.
(win2kpro,linux,beos)
any help is appreciated, thanx.
Chad Fewer
\Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
I followed Chris’s suggestion for io-net, which works with my D-Link
DFE-530TX+. I can configure the network with the philip tool, and can ping
and access the internet.
I still have a problem after rebooting, the file /etc/net.cfg gets reset
(loses all of my network confiurations like IP address, gateway,
nameservers, manual vs DHCP, etc. I have to reenter them each time I reboot.
I have tried making a file /etc/rc.d/rc.local per the QNX Knowledge base,
and chmod it to 775:
#!bin/sh
/bin/slay io-net
/sbin/io-net -d rtl -did=0x1300,vid=0x1186 -ptcpip
/bin/netmanager
Any ideas how to keep the system from resetting /etc/net.cfg and losing my
network information each time I reboot?
Thanks,
Dale Pischke
drpischke@cox.net
“Chris McKillop” <cdm@qnx.com> wrote in message
news:acuu8f$8ea$1@nntp.qnx.com…
it is…
io-net -d rtl did=0x1300,vid=0x1186
…no space allowed.
chris
I found that adding ‘sleep 1’ before the /bin/netmanager command worked, so
that my /etc/net.cfg file stays intact with my settings.
Thanks,
Dale Pischke
drpischke@cox.net
“Dale R. Pischke” <drpischke@cox.net> wrote in message
news:ag2e43$eau$1@inn.qnx.com…
I followed Chris’s suggestion for io-net, which works with my D-Link
DFE-530TX+. I can configure the network with the philip tool, and can ping
and access the internet.I still have a problem after rebooting, the file /etc/net.cfg gets reset
(loses all of my network confiurations like IP address, gateway,
nameservers, manual vs DHCP, etc. I have to reenter them each time I
reboot.I have tried making a file /etc/rc.d/rc.local per the QNX Knowledge base,
and chmod it to 775:
#!bin/sh
/bin/slay io-net
/sbin/io-net -d rtl -did=0x1300,vid=0x1186 -ptcpip
/bin/netmanagerAny ideas how to keep the system from resetting /etc/net.cfg and losing my
network information each time I reboot?Thanks,
Dale Pischke
drpischke@cox.net
“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:acuu8f$8ea$> 1@nntp.qnx.com> …it is…
io-net -d rtl did=0x1300,vid=0x1186
…no space allowed.
chris
\
Perhaps /etc/rc.d/rc.setup-info is somehow getting invoked after each reboot
(it can rewrite /etc/net.cfg).
dB
“Dale R. Pischke” <drpischke@cox.net> wrote in message
news:ag2e43$eau$1@inn.qnx.com…
I followed Chris’s suggestion for io-net, which works with my D-Link
DFE-530TX+. I can configure the network with the philip tool, and can ping
and access the internet.I still have a problem after rebooting, the file /etc/net.cfg gets reset
(loses all of my network confiurations like IP address, gateway,
nameservers, manual vs DHCP, etc. I have to reenter them each time I
reboot.I have tried making a file /etc/rc.d/rc.local per the QNX Knowledge base,
and chmod it to 775:
#!bin/sh
/bin/slay io-net
/sbin/io-net -d rtl -did=0x1300,vid=0x1186 -ptcpip
/bin/netmanagerAny ideas how to keep the system from resetting /etc/net.cfg and losing my
network information each time I reboot?Thanks,
Dale Pischke
drpischke@cox.net
“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:acuu8f$8ea$> 1@nntp.qnx.com> …it is…
io-net -d rtl did=0x1300,vid=0x1186
…no space allowed.
chris
\