Project Home
Project Home		 Trackers
Trackers		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Community/Discussion/QNX4 Community Support (EOL)/Intel i82546GB / i82540 / e1000/List of Posts
Forum Topic - Intel i82546GB / i82540 / e1000: (6 Items)
   
Update
Walt Wimer
09/17/2009 2:08 PM
post38199
Intel i82546GB / i82540 / e1000   
Hi!

I have an Interphase 454G Quad-Port Gigabit Ethernet PMC card ( http://www.interphase.com/products/product.cfm/PMC/376 )
 that I'm trying to use with a Dynatem "DMC" (Pentium III-based) VME board ( http://www.dynatem.com/products/dmc.php ) 
running QNX 4.25 (ca. 1999-2000).  The Interphase card has two Intel i82546GB chips connected to the PCI bus via an 
Intel PCI-to-PCI bridge chip (on the PMC card).  The i82546GB chips show up as PCI Device ID 1079h in the output from "
show_pci".

I've tried both the Net.i82540 driver dated July 26, 2007 from the official QNX4 driver patches, as well as an 
experimental Net.e1000 driver posted to this forum by Hugh Brown.  Both drivers give me INITIALIZATION ERROR 4 and exit 
immediately.

We have Net loaded, and a pair of i82559 Fast Ethernet interfaces built onto the CPU board work fine with the Net.
ether82557 driver.

I have attached the output from "show_pci -v".

Any suggestions?


Thanks!

Walt Wimer
Attachment: Text show_pci-v.txt 13.65 KB
Hugh Brown
09/17/2009 2:18 PM
post38200
RE: Intel i82546GB / i82540 / e1000   
How are you starting Net? You should start 'Net-d4 &'.


-----Original Message-----
From: Walt Wimer [mailto:community-noreply@qnx.com] 
Sent: Thursday, September 17, 2009 2:09 PM
To: qnx4-community
Subject: Intel i82546GB / i82540 / e1000

Hi!

I have an Interphase 454G Quad-Port Gigabit Ethernet PMC card (
http://www.interphase.com/products/product.cfm/PMC/376 ) that I'm trying
to use with a Dynatem "DMC" (Pentium III-based) VME board (
http://www.dynatem.com/products/dmc.php ) running QNX 4.25 (ca.
1999-2000).  The Interphase card has two Intel i82546GB chips connected
to the PCI bus via an Intel PCI-to-PCI bridge chip (on the PMC card).
The i82546GB chips show up as PCI Device ID 1079h in the output from
"show_pci".

I've tried both the Net.i82540 driver dated July 26, 2007 from the
official QNX4 driver patches, as well as an experimental Net.e1000
driver posted to this forum by Hugh Brown.  Both drivers give me
INITIALIZATION ERROR 4 and exit immediately.

We have Net loaded, and a pair of i82559 Fast Ethernet interfaces built
onto the CPU board work fine with the Net.ether82557 driver.

I have attached the output from "show_pci -v".

Any suggestions?


Thanks!

Walt Wimer




_______________________________________________

QNX4 Community Support
http://community.qnx.com/sf/go/post38199
Walt Wimer
09/17/2009 2:25 PM
post38203
Re: RE: Intel i82546GB / i82540 / e1000   
Hi Hugh,

Thanks for your suggestion!  That looks like a very promising lead.  We are indeed starting Net with no options, so 
(according to "use Net") it defaults to 2 drivers (which are consumed by our i82559 interfaces).

I'll try starting Net with -d4 (or -d6 ?) as soon as I can get access to our test system again (a collegue is using it 
now...).


Thanks for the lightning-quick response!!!

Walt
Walt Wimer
09/17/2009 5:41 PM
post38226
Re: RE: Intel i82546GB / i82540 / e1000   
Hi Hugh,

Well, starting Net with -d6 definitely helped, along with some further experimenation with command line parameters for 
the Net.i82540/e1000 driver.  Each driver now remains running and correctly reports link status, speed, etc.  Watching 
the -v output, they properly detect the cable being disconnected and then reconnected.  The 'ifconfig' command can 
initialize the en1, en2, en3, etc. interfaces, and the output from 'netstat -rn' looks like what I expect.  Everything 
_looks_ fine.

Unfortunately, I can't ping anything.

If I kill the Net.i82540/e1000 driver, start up the Net.ether82557 driver, and move my cable to the built-in ethernet 
interface, ping works fine.

At the moment, I'm out of ideas.

I might try to boot a Linux liveCD or something on our system, just to make sure the hardware is working properly.  (I'm
 not sure how difficult that will be on our equipment, however...)

Thanks again for your earlier help, and thanks in advance for any additional ideas!


Walt
Hugh Brown
09/18/2009 7:39 AM
post38255
RE: RE: Intel i82546GB / i82540 / e1000   
Hi Walt,

What network addresses are you assigning to the interfaces? They all
have to be on different subnets. The output from 'netstat -in' would
help. Do you see any receive activity reported in netinfo for all of the
interfaces? If you could also post the output from 'show_pci -v' that
would also be helpful.

Hugh.

-----Original Message-----
From: Walt Wimer [mailto:community-noreply@qnx.com] 
Sent: Thursday, September 17, 2009 5:41 PM
To: qnx4-community
Subject: Re: RE: Intel i82546GB / i82540 / e1000

Hi Hugh,

Well, starting Net with -d6 definitely helped, along with some further
experimenation with command line parameters for the Net.i82540/e1000
driver.  Each driver now remains running and correctly reports link
status, speed, etc.  Watching the -v output, they properly detect the
cable being disconnected and then reconnected.  The 'ifconfig' command
can initialize the en1, en2, en3, etc. interfaces, and the output from
'netstat -rn' looks like what I expect.  Everything _looks_ fine.

Unfortunately, I can't ping anything.

If I kill the Net.i82540/e1000 driver, start up the Net.ether82557
driver, and move my cable to the built-in ethernet interface, ping works
fine.

At the moment, I'm out of ideas.

I might try to boot a Linux liveCD or something on our system, just to
make sure the hardware is working properly.  (I'm not sure how difficult
that will be on our equipment, however...)

Thanks again for your earlier help, and thanks in advance for any
additional ideas!


Walt




_______________________________________________

QNX4 Community Support
http://community.qnx.com/sf/go/post38226
Walt Wimer
09/18/2009 3:13 PM
post38358
Re: RE: RE: Intel i82546GB / i82540 / e1000   
Hi Hugh,

Thanks for the additional suggestions!

I found the problem!  I connected up a PC running Wireshark and discovered something I didn't expect.  I'm an old IP guy
, so my first instinct was to get IP working.  I didn't immediately care about QNX networking.  Looking at packet traces
, I discovered that the MAC addresses in the 'netmap' file interact in strange ways with the IP stack.  For example, I 
saw ARP replies from QNX that had the source MAC address (in the actual ethernet header) set to the card's native MAC 
address (from the card's ROM), but ARP data fields with the MAC address from the 'netmap' file.  Thus other hosts on my 
network were trying to send IP datagrams to the old MAC address listed in the 'netmap' file, but nothing was listening 
on that MAC address.

Once I edited the 'netmap' file to match reality (and reloaded it), things started working correctly.

Another problem bites the dust!


Thanks for all your help!

Walt

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems