I’ve got two QNX machines–after shipping them to the customer site, they
quit talking to each other. One of them complains during boot up:
“Net: nm_load(): brg_tbl_autoload() failed”
The network adapter is integrated into the motherboard. Anybody have an idea
what’s going on here?
Thanks,
John
Previously, Elderbear wrote in qdn.public.qnx4:
I’ve got two QNX machines–after shipping them to the customer site, they
quit talking to each other. One of them complains during boot up:“Net: nm_load(): brg_tbl_autoload() failed”
The network adapter is integrated into the motherboard. Anybody have an idea
what’s going on here?
The output from ‘show_pci -v’ should tell me what type of chip you have on
the motherboard. If its one of the newer 82557’s, you might need a driver
update. The output from ‘sin ver’ would also help.
Thanks,
John
\
Elderbear <john@jelder.com> wrote:
I’ve got two QNX machines–after shipping them to the customer site, they
quit talking to each other. One of them complains during boot up:“Net: nm_load(): brg_tbl_autoload() failed”
The network adapter is integrated into the motherboard. Anybody have an idea
what’s going on here?
Did you configure them any differently? What do you give as -l options
to the Net.driver on each machine? What do your netmaps look like?
The nm_load() stuff has to do with the bridging code in Net – only
usually wandered through if you have nodes on more than one lan, and
Net is trying to figure out how to route packets from one logical lan
to another.
QNX Training Services
dagibbs@qnx.com
I’ve got two QNX machines–after shipping them to the customer site,
they
quit talking to each other. One of them complains during boot up:“Net: nm_load(): brg_tbl_autoload() failed”
The network adapter is integrated into the motherboard. Anybody have an
idea
what’s going on here?Did you configure them any differently?
Turns out I had an interupt switch on the other machine–once I compensated
for that, everything works OK. But the error is still there. I’m merely
curious now.
What do you give as -l options
to the Net.driver on each machine?
I didn’t specify–I assume it defaults to 1?
What do your netmaps look like?
They’re real simple. Two entries, one for each machine.
The nm_load() stuff has to do with the bridging code in Net – only
usually wandered through if you have nodes on more than one lan, and
Net is trying to figure out how to route packets from one logical lan
to another.
Wow! Perhaps I need to specify that I only have 1 net & that it’s net 1?
I’ll try that. Nope, Net.ether82557 -l1 still gives the same error.
Curiouser & curiouser.
Thanks,
John