Momentics NC’s install doesn’t auto-detect my enet card, an ISA 3Com
Etherlink III. (I have a PCI NIC, a Linksys ‘Network Everywhere’ Fast
Ethernet adapater, that QNX detected but doesn’t seem to support; I
need to leave this card in for when I boot into WinXP.)
QNX loads the tulip driver for the PCI NIC (which doesn’t work) and
ignores the ISA card. I found I can get it to work manually by doing:
slay io-net
io-net -d el509 -p tcpip
In order to have the box boot with enet working, I created an
/etc/rc.local file and put those two commands in it. This works, but
seems like a pretty clumsy hack, i.e., let QNX start io-net with the
‘wrong’ driver, then kill/restart it with the right one.
Is there some file I can edit to override QNX’s default behavior?
Momentics NC’s install doesn’t auto-detect my enet card, an ISA 3Com
Etherlink III. (I have a PCI NIC, a Linksys ‘Network Everywhere’ Fast
Ethernet adapater, that QNX detected but doesn’t seem to support; I
need to leave this card in for when I boot into WinXP.)
QNX loads the tulip driver for the PCI NIC (which doesn’t work) and
ignores the ISA card. I found I can get it to work manually by doing:
slay io-net
io-net -d el509 -p tcpip
In order to have the box boot with enet working, I created an
/etc/rc.local file and put those two commands in it. This works, but
seems like a pretty clumsy hack, i.e., let QNX start io-net with the
‘wrong’ driver, then kill/restart it with the right one.
Is there some file I can edit to override QNX’s default behavior?
I agree. I don’t care for the philosophy of starting everything you
can find with default parameters and then having to restart them again
later on correctly.
Can you build a custom OS image?
This gives you many more options.
I agree. I don’t care for the philosophy of starting everything you
can find with default parameters and then having to restart them again
later on correctly.
Can you build a custom OS image?
This gives you many more options.
BTW, this also gives you a much faster startup. It doesn’t have to detect what hardware you’re using if you just tell it what you’re
using and how to use it.
Momentics NC’s install doesn’t auto-detect my enet card, an ISA 3Com
Etherlink III. (I have a PCI NIC, a Linksys ‘Network Everywhere’ Fast
QNX loads the tulip driver for the PCI NIC (which doesn’t work) and
ignores the ISA card. I found I can get it to work manually by doing:
slay io-net
io-net -d el509 -p tcpip
In order to have the box boot with enet working, I created an
/etc/rc.local file and put those two commands in it. This works, but
seems like a pretty clumsy hack, i.e., let QNX start io-net with the
‘wrong’ driver, then kill/restart it with the right one.
I thought EtherLinkIII was supported but
wht isn’t it in default enumurateors, QSSL?
(cuz it’s ISA card? maybe…)
You can modify /etc/system/enum/devices/net to
erase “unwanted” devices, or add new devices.
For new devices, adding /etc/system/enum/oem/ should be neater tho.
Momentics NC’s install doesn’t auto-detect my enet card, an ISA 3Com
Etherlink III. (I have a PCI NIC, a Linksys ‘Network Everywhere’ Fast
QNX loads the tulip driver for the PCI NIC (which doesn’t work) and
ignores the ISA card. I found I can get it to work manually by doing:
slay io-net
io-net -d el509 -p tcpip
In order to have the box boot with enet working, I created an
/etc/rc.local file and put those two commands in it. This works, but
seems like a pretty clumsy hack, i.e., let QNX start io-net with the
‘wrong’ driver, then kill/restart it with the right one.
I thought EtherLinkIII was supported but
wht isn’t it in default enumurateors, QSSL?
(cuz it’s ISA card? maybe…)
If enumurators find a PCI card, we intentionally stopped the ISA scan,
cause it is dangrous. (There is an option to enumurator to force scan
ISA though)
Note in this perticular case, even if ISA is scaned, he will end up have
2 nics, which is still not what he wanted.
You can modify /etc/system/enum/devices/net to
erase “unwanted” devices, or add new devices.
Use the rc.local approch, modify thse file could get you in trouble next
time you do a update or something.
You can modify /etc/system/enum/devices/net to
erase “unwanted” devices, or add new devices.
Use the rc.local approch, modify thse file could get you in trouble next
time you do a update or something.
Well mods for new devices can be avoided by /etc/system/enum/oem/, but
is there any clean way to DISABLE particular device’s enumuration?
Mucking with rc.local afterwards isn’t neat.
You can modify /etc/system/enum/devices/net to
erase “unwanted” devices, or add new devices.
Use the rc.local approch, modify thse file could get you in trouble next
time you do a update or something.
Well mods for new devices can be avoided by /etc/system/enum/oem/, but
is there any clean way to DISABLE particular device’s enumuration?
Mucking with rc.local afterwards isn’t neat.
Sure. Create a new entry in an /etc/system/enum/oem/ file
(or in /etc/system/enum/overrides) that has the device that you
want to disable and have no actions associated with it. E.g.:
David Wolfe <> da5id@luvspamwolfe.name> > wrote:
Momentics NC’s install doesn’t auto-detect my enet card, an ISA 3Com
Etherlink III. (I have a PCI NIC, a Linksys ‘Network Everywhere’ Fast
In order to have the box boot with enet working, I created an
/etc/rc.local file and put those two commands in it. This works,
but seems like a pretty clumsy hack…
You can modify /etc/system/enum/devices/net to
erase “unwanted” devices, or add new devices.
Use the rc.local approch, modify thse file could get you in trouble
next time you do a update or something.
Hmm. Okay. But it turns out I lied above. The rc.local hack I tried
doesn’t quite work. (I swear it worked once, but I haven’t been able
to repeat it.) Slaying io-net seems to dislodge the DNS and gateway
settings, and I’ve had to reset them manually using phlip. I tried
editing /etc/net.cfg to specify nameservers, routing and ‘mode dhcp’,
but this doesn’t seem to do the trick.
It still comes up with a ‘Manual’ config in phlip when I boot. It’s
like the PCI scan says, “Oh, okay I’ve got this PCI tulip chip, and no
DHCP server is answering the phone, so I’ll just set it to manual.”
(I’m actually using DHCP, but this particular card doesn’t work with
QNX.) Then, when I kill io-net and restart it with the 3COM driver, it
fails. Perhaps I need to manually run a DHCP client as well?
Hmm. Okay. But it turns out I lied above. The rc.local hack I tried
doesn’t quite work. (I swear it worked once, but I haven’t been able
to repeat it.) Slaying io-net seems to dislodge the DNS and gateway
settings, and I’ve had to reset them manually using phlip. I tried
editing /etc/net.cfg to specify nameservers, routing and ‘mode dhcp’,
but this doesn’t seem to do the trick.
It still comes up with a ‘Manual’ config in phlip when I boot. It’s
like the PCI scan says, “Oh, okay I’ve got this PCI tulip chip, and no
DHCP server is answering the phone, so I’ll just set it to manual.”
(I’m actually using DHCP, but this particular card doesn’t work with
QNX.) Then, when I kill io-net and restart it with the 3COM driver, it
fails. Perhaps I need to manually run a DHCP client as well?
I’m not surprised. Anytime you slay off a process, other processes
that had connections to it will need to re-establish their connections.
A select few may detect that the server they were conencted to has
gone away and do a reconnect themselves. But more often, you will
have to slay off any client processes of io-net and restart them too.
In order to have the box boot with enet working, I created an
/etc/rc.local file and put those two commands in it. This works,
but seems like a pretty clumsy hack…
You can modify /etc/system/enum/devices/net to
erase “unwanted” devices, or add new devices.
Use the rc.local approch, modify thse file could get you in trouble
next time you do a update or something.
Hmm. Okay. But it turns out I lied above. The rc.local hack I tried
doesn’t quite work. (I swear it worked once, but I haven’t been able
to repeat it.) Slaying io-net seems to dislodge the DNS and gateway
settings, and I’ve had to reset them manually using phlip. I tried
editing /etc/net.cfg to specify nameservers, routing and ‘mode dhcp’,
but this doesn’t seem to do the trick.
It still comes up with a ‘Manual’ config in phlip when I boot. It’s
like the PCI scan says, “Oh, okay I’ve got this PCI tulip chip, and no
DHCP server is answering the phone, so I’ll just set it to manual.”
(I’m actually using DHCP, but this particular card doesn’t work with
QNX.) Then, when I kill io-net and restart it with the 3COM driver, it
fails. Perhaps I need to manually run a DHCP client as well?
As other suggest, you just need to manuly invoke “netmanager”.
Try this:
rename your /etc/rc.d/rc.local to something else
boot the machine, slay io-net, restart it with proper driver
start phlip, config the interface in dhcp mode.
restore your /etc/rc.d/rc.local with like:
slay io-net
io-net -d el900 -p tcpip
netmanager