Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Net.e1000 problem: (17 Items)
   
Net.e1000 problem  
Hello QNX masters,
I have a SIEMENS nanobox V2 indutrial railmounted PC and wiant to get both internal network cards to run.
Both cards have the PCI device ID 0x1533 and normaly this isfor an i210 intel gigabit network adapter supported using 
QNX4.
The first network card is working OK and I get for "Net.e1000 -I0 -l1 -vvv &":

  e1000_put_hw_semaphore_i210
  e1000_write_phy_reg_mdic
  e1000_read_phy_reg_mdic
  e1000_release_phy_82575
  e1000_release_swfw_sync_i210
  e1000_get_hw_semaphore_i210
  e1000_put_hw_semaphore_i210
  Flow Control = FULL.

  e1000_get_link_up_info_82575
  e1000_get_speed_and_duplex_copper_generic
  100 Mbs,
  Full Duplex

  e1000_force_mac_fc_generic
  hw->fc.current_mode = 3
  e1000_get_link_up_info_82575
  e1000_get_speed_and_duplex_copper_generic
  100 Mbs,
  Full Duplex

  Link up speed 100 Mbps - duplex Full


The second network card is not working OK and I get for "Net.e1000 -I1 -l2 -vvv &":

  e1000_get_hw_semaphore_i210
  e1000_put_hw_semaphore_i210
  e1000_write_phy_reg_mdic
  e1000_read_phy_reg_mdic
  e1000_release_phy_82575
  e1000_release_swfw_sync_i210
  e1000_get_hw_semaphore_i210
  e1000_put_hw_semaphore_i210
  e1000_read_phy_reg_gs40g
  e1000_acquire_phy_82575
  e1000_acquire_swfw_sync_i210
  e1000_get_hw_semaphore_i210
  e1000_put_hw_semaphore_i210
  e1000_write_phy_reg_mdic
  e1000_read_phy_reg_mdic
  e1000_release_phy_82575
  e1000_release_swfw_sync_i210
  e1000_get_hw_semaphore_i210
  e1000_put_hw_semaphore_i210
  Link down
  e1000_null_mng_mode
  e1000_clear_hw_cntrs_base_generic

With "netinfo -L2" I can see that the network controller receives packages but is not sending out something.
All this checks are only possible as long as I connect only one network cable. As soon as I connect two network cables 
and try to start the first network adpater and afterwards the 2nd network adpater the system freezes.
Eben if there is no IRQ confilct in the "show_pci -v"

Can you apapt the Net.e1000 to the new network card? (even if the 0x1533 should already work)
Can I bring more information about the Net.e1000 output?

BR, Klaus

Re: Net.e1000 problem  
If you just start the second interface (Net.e1000 -I1 -l2 -vvv &) does it
work?



On 2015/5/29, 8:23 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>Hello QNX masters,
>I have a SIEMENS nanobox V2 indutrial railmounted PC and wiant to get
>both internal network cards to run.
>Both cards have the PCI device ID 0x1533 and normaly this isfor an i210
>intel gigabit network adapter supported using QNX4.
>The first network card is working OK and I get for "Net.e1000 -I0 -l1
>-vvv &":
>
>  e1000_put_hw_semaphore_i210
>  e1000_write_phy_reg_mdic
>  e1000_read_phy_reg_mdic
>  e1000_release_phy_82575
>  e1000_release_swfw_sync_i210
>  e1000_get_hw_semaphore_i210
>  e1000_put_hw_semaphore_i210
>  Flow Control = FULL.
>
>  e1000_get_link_up_info_82575
>  e1000_get_speed_and_duplex_copper_generic
>  100 Mbs,
>  Full Duplex
>
>  e1000_force_mac_fc_generic
>  hw->fc.current_mode = 3
>  e1000_get_link_up_info_82575
>  e1000_get_speed_and_duplex_copper_generic
>  100 Mbs,
>  Full Duplex
>
>  Link up speed 100 Mbps - duplex Full
>
>
>The second network card is not working OK and I get for "Net.e1000 -I1
>-l2 -vvv &":
>
>  e1000_get_hw_semaphore_i210
>  e1000_put_hw_semaphore_i210
>  e1000_write_phy_reg_mdic
>  e1000_read_phy_reg_mdic
>  e1000_release_phy_82575
>  e1000_release_swfw_sync_i210
>  e1000_get_hw_semaphore_i210
>  e1000_put_hw_semaphore_i210
>  e1000_read_phy_reg_gs40g
>  e1000_acquire_phy_82575
>  e1000_acquire_swfw_sync_i210
>  e1000_get_hw_semaphore_i210
>  e1000_put_hw_semaphore_i210
>  e1000_write_phy_reg_mdic
>  e1000_read_phy_reg_mdic
>  e1000_release_phy_82575
>  e1000_release_swfw_sync_i210
>  e1000_get_hw_semaphore_i210
>  e1000_put_hw_semaphore_i210
>  Link down
>  e1000_null_mng_mode
>  e1000_clear_hw_cntrs_base_generic
>
>With "netinfo -L2" I can see that the network controller receives
>packages but is not sending out something.
>All this checks are only possible as long as I connect only one network
>cable. As soon as I connect two network cables and try to start the first
>network adpater and afterwards the 2nd network adpater the system freezes.
>Eben if there is no IRQ confilct in the "show_pci -v"
>
>Can you apapt the Net.e1000 to the new network card? (even if the 0x1533
>should already work)
>Can I bring more information about the Net.e1000 output?
>
>BR, Klaus
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post113872
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com

Re: Net.e1000 problem  
If I start the second network card as the only one ("Net.e1000 -I1 -l1") the system will continue to work. But I only 
receive packages (netinfo -L1). No packages are going out. I checked the incoming and outgoing of packages with a direct
 connection to another PC running wireshark. The incoming count is OK but no package is going out. 
Re: Net.e1000 problem  
Well is the first adapter is working and it has the same device ID as the
second interface, this means that the driver is working, so I would look
at why the second adapter isn¹t working. Are you running TCP/IP, and if
so, what IP addresses are you using for each network adapter? Can you also
please post the output from ³show_pci -v², as well as ³sin² and ³sin irq².




On 2015/6/1, 4:05 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>If I start the second network card as the only one ("Net.e1000 -I1 -l1")
>the system will continue to work. But I only receive packages (netinfo
>-L1). No packages are going out. I checked the incoming and outgoing of
>packages with a direct connection to another PC running wireshark. The
>incoming count is OK but no package is going out.
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post113879
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com

Re: Net.e1000 problem  
Hello Hugh,

the requested output is following:


Welcome to QNX 4.25
Copyright (c) QNX Software Systems Ltd. 1982,1998
login: root
password:
Last login: Mon Jun 01 13:16:07 2015 on not a tty
Mon Jun 01 13:18:59 2015
(root)//138/root>on -f 1 login -f root
Last login: Wed Dec 31 19:00:16 1969 on //1/dev/con1
Thu Jan 01 00:01:41 1970


(root)//1/root>show_pci -v

PCI version    = 3.00

Vendor ID      = 8086h, INTEL CORPORATION
Device ID      = f00h,
PCI index      = 0h
Class Code     = 060000h Bridge (Host/PCI) ProgIF=0
Revision ID    = eh
Bus number     = 0
Device number  = 0
Function num   = 0
Status Reg     = 0h
Command Reg    = 7h
Header type    = 0h Single-function
BIST           = 0h Build-in-self-test not supported
Latency Timer  = 0h
Cache Line Size= 0h

Subsystem Vendor ID = 8086h
Subsystem ID        = 7270h
Max Lat        = 0ns
Min Gnt        = 0ns
PCI Int Pin    = 0, NC
Interrupt line = 0

Vendor ID      = 8086h, INTEL CORPORATION
Device ID      = f31h,
PCI index      = 0h
Class Code     = 030000h Display (VGA) ProgIF=0
Revision ID    = eh
Bus number     = 0
Device number  = 2
Function num   = 0
Status Reg     = 10h
Command Reg    = 7h
Header type    = 0h Single-function
BIST           = 0h Build-in-self-test not supported
Latency Timer  = 0h
Cache Line Size= 0h
Base Address   = MEM@90000000h,32bit length 4194304 MEM@80000000h,Prefetchable,32bit length 268435456 IO@7050h length 8 
bytes
Subsystem Vendor ID = 8086h
Subsystem ID        = 7270h
Max Lat        = 0ns
Min Gnt        = 0ns
PCI Int Pin    = 1, INT A
Interrupt line = 7
Capabilities Pointer = d0h
Capability ID        = 1h
Capabilities         = 22h - 0h
Capability ID        = 5h
Capabilities         = 0h - 0h
Capability ID        = 9h
Capabilities         = 107h - 0h

Vendor ID      = 8086h, INTEL CORPORATION
Device ID      = f21h,
PCI index      = 0h
Class Code     = 01018ah Mass Storage (IDE) ProgIF=138
Revision ID    = eh
Bus number     = 0
Device number  = 19
Function num   = 0
Status Reg     = 2b0h
Command Reg    = 7h
Header type    = 0h Single-function
BIST           = 0h Build-in-self-test not supported
Latency Timer  = 0h
Cache Line Size= 0h
Base Address   = IO@0h length 8 bytes IO@0h length 4 bytes IO@0h length 8 bytes IO@0h length 4 bytes IO@7030h length 16 
bytes IO@7020h length 16 bytes
Subsystem Vendor ID = 8086h
Subsystem ID        = 7270h
Max Lat        = 0ns
Min Gnt        = 0ns
PCI Int Pin    = 1, INT A
Interrupt line = 10
Capabilities Pointer = 70h
Capability ID        = 1h
Capabilities         = 3h - 8h

Vendor ID      = 8086h, INTEL CORPORATION
Device ID      = f18h,
PCI index      = 0h
Class Code     = 108000h Encryption (Other 128) ProgIF=0
Revision ID    = eh
Bus number     = 0
Device number  = 26
Function num   = 0
Status Reg     = 10h
Command Reg    = 106h
Header type    = 0h Single-function
BIST           = 0h Build-in-self-test not supported
Latency Timer  = 0h
Cache Line Size= 10h un-cacheable
Base Address   = MEM@90800000h,32bit length 1048576 MEM@90700000h,32bit length 1048576
Subsystem Vendor ID = 8086h
Subsystem ID        = 7270h
Max Lat        = 0ns
Min Gnt        = 0ns
PCI Int Pin    = 1, INT A
Interrupt line = 11
Capabilities Pointer = 80h
Capability ID        = 1h
Capabilities         = 4803h - 8h
Capability ID        = 5h
Capabilities         = 0h - 0h

Vendor ID      = 8086h, INTEL CORPORATION
Device ID      = f04h,
PCI index      = 0h
Class Code     = 040300h Multimedia (RAM) ProgIF=0
Revision ID    = eh
Bus number     = 0
Device number  = 27
Function num   = 0
Status Reg     = 10h
Command Reg    = 6h
Header type    = 0h Single-function
BIST           = 0h Build-in-self-test not supported
Latency Timer  = 0h
Cache Line Size= 10h un-cacheable
Base Address   = MEM@90900000h,64bit length 16384
Subsystem Vendor ID = 8086h
Subsystem ID        = 7270h
Max Lat        = 0ns
Min Gnt       ...
View Full Message
Re: Net.e1000 problem  
Hello Klaus,

I can only imagine that your problem has something to do with the
hardware. I have setup a machine here with 2 I210 adapters (ID 0x1533) and
both of them are working just fine. Is there an option in your BIOS setup
to turn off Plug ¹n Play? On my system, the network adapters are using
IRQs 10 and 11. On your system, one of the adapters is using IRQ 7, which
is normally reserved for printers. If your BIOS doesn¹t have a Plug ¹n
Play option, there might be a setup where you can change the IRQs of PCI
devices, so you can try that.

Hugh.



On 2015/6/1, 9:22 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>Hello Hugh,
>
>the requested output is following:
>
>
>Welcome to QNX 4.25
>Copyright (c) QNX Software Systems Ltd. 1982,1998
>login: root
>password:
>Last login: Mon Jun 01 13:16:07 2015 on not a tty
>Mon Jun 01 13:18:59 2015
>(root)//138/root>on -f 1 login -f root
>Last login: Wed Dec 31 19:00:16 1969 on //1/dev/con1
>Thu Jan 01 00:01:41 1970
>
>
>(root)//1/root>show_pci -v
>
>PCI version    = 3.00
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f00h,
>PCI index      = 0h
>Class Code     = 060000h Bridge (Host/PCI) ProgIF=0
>Revision ID    = eh
>Bus number     = 0
>Device number  = 0
>Function num   = 0
>Status Reg     = 0h
>Command Reg    = 7h
>Header type    = 0h Single-function
>BIST           = 0h Build-in-self-test not supported
>Latency Timer  = 0h
>Cache Line Size= 0h
>
>Subsystem Vendor ID = 8086h
>Subsystem ID        = 7270h
>Max Lat        = 0ns
>Min Gnt        = 0ns
>PCI Int Pin    = 0, NC
>Interrupt line = 0
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f31h,
>PCI index      = 0h
>Class Code     = 030000h Display (VGA) ProgIF=0
>Revision ID    = eh
>Bus number     = 0
>Device number  = 2
>Function num   = 0
>Status Reg     = 10h
>Command Reg    = 7h
>Header type    = 0h Single-function
>BIST           = 0h Build-in-self-test not supported
>Latency Timer  = 0h
>Cache Line Size= 0h
>Base Address   = MEM@90000000h,32bit length 4194304
>MEM@80000000h,Prefetchable,32bit length 268435456 IO@7050h length 8 bytes
>Subsystem Vendor ID = 8086h
>Subsystem ID        = 7270h
>Max Lat        = 0ns
>Min Gnt        = 0ns
>PCI Int Pin    = 1, INT A
>Interrupt line = 7
>Capabilities Pointer = d0h
>Capability ID        = 1h
>Capabilities         = 22h - 0h
>Capability ID        = 5h
>Capabilities         = 0h - 0h
>Capability ID        = 9h
>Capabilities         = 107h - 0h
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f21h,
>PCI index      = 0h
>Class Code     = 01018ah Mass Storage (IDE) ProgIF=138
>Revision ID    = eh
>Bus number     = 0
>Device number  = 19
>Function num   = 0
>Status Reg     = 2b0h
>Command Reg    = 7h
>Header type    = 0h Single-function
>BIST           = 0h Build-in-self-test not supported
>Latency Timer  = 0h
>Cache Line Size= 0h
>Base Address   = IO@0h length 8 bytes IO@0h length 4 bytes IO@0h length 8
>bytes IO@0h length 4 bytes IO@7030h length 16 bytes IO@7020h length 16
>bytes
>Subsystem Vendor ID = 8086h
>Subsystem ID        = 7270h
>Max Lat        = 0ns
>Min Gnt        = 0ns
>PCI Int Pin    = 1, INT A
>Interrupt line = 10
>Capabilities Pointer = 70h
>Capability ID        = 1h
>Capabilities         = 3h - 8h
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f18h,
>PCI index      = 0h
>Class Code     = 108000h Encryption (Other 128) ProgIF=0
>Revision ID    = eh
>Bus number     = 0
>Device number  = 26
>Function num   = 0
>Status Reg     = 10h
>Command Reg    =...
View Full Message
Re: Net.e1000 problem  
Further to my last posting, I have my adapters running on 2 separate
networks. You cannot have 2 adapters on the same subnet.




On 2015/6/1, 9:22 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>Hello Hugh,
>
>the requested output is following:
>
>
>Welcome to QNX 4.25
>Copyright (c) QNX Software Systems Ltd. 1982,1998
>login: root
>password:
>Last login: Mon Jun 01 13:16:07 2015 on not a tty
>Mon Jun 01 13:18:59 2015
>(root)//138/root>on -f 1 login -f root
>Last login: Wed Dec 31 19:00:16 1969 on //1/dev/con1
>Thu Jan 01 00:01:41 1970
>
>
>(root)//1/root>show_pci -v
>
>PCI version    = 3.00
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f00h,
>PCI index      = 0h
>Class Code     = 060000h Bridge (Host/PCI) ProgIF=0
>Revision ID    = eh
>Bus number     = 0
>Device number  = 0
>Function num   = 0
>Status Reg     = 0h
>Command Reg    = 7h
>Header type    = 0h Single-function
>BIST           = 0h Build-in-self-test not supported
>Latency Timer  = 0h
>Cache Line Size= 0h
>
>Subsystem Vendor ID = 8086h
>Subsystem ID        = 7270h
>Max Lat        = 0ns
>Min Gnt        = 0ns
>PCI Int Pin    = 0, NC
>Interrupt line = 0
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f31h,
>PCI index      = 0h
>Class Code     = 030000h Display (VGA) ProgIF=0
>Revision ID    = eh
>Bus number     = 0
>Device number  = 2
>Function num   = 0
>Status Reg     = 10h
>Command Reg    = 7h
>Header type    = 0h Single-function
>BIST           = 0h Build-in-self-test not supported
>Latency Timer  = 0h
>Cache Line Size= 0h
>Base Address   = MEM@90000000h,32bit length 4194304
>MEM@80000000h,Prefetchable,32bit length 268435456 IO@7050h length 8 bytes
>Subsystem Vendor ID = 8086h
>Subsystem ID        = 7270h
>Max Lat        = 0ns
>Min Gnt        = 0ns
>PCI Int Pin    = 1, INT A
>Interrupt line = 7
>Capabilities Pointer = d0h
>Capability ID        = 1h
>Capabilities         = 22h - 0h
>Capability ID        = 5h
>Capabilities         = 0h - 0h
>Capability ID        = 9h
>Capabilities         = 107h - 0h
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f21h,
>PCI index      = 0h
>Class Code     = 01018ah Mass Storage (IDE) ProgIF=138
>Revision ID    = eh
>Bus number     = 0
>Device number  = 19
>Function num   = 0
>Status Reg     = 2b0h
>Command Reg    = 7h
>Header type    = 0h Single-function
>BIST           = 0h Build-in-self-test not supported
>Latency Timer  = 0h
>Cache Line Size= 0h
>Base Address   = IO@0h length 8 bytes IO@0h length 4 bytes IO@0h length 8
>bytes IO@0h length 4 bytes IO@7030h length 16 bytes IO@7020h length 16
>bytes
>Subsystem Vendor ID = 8086h
>Subsystem ID        = 7270h
>Max Lat        = 0ns
>Min Gnt        = 0ns
>PCI Int Pin    = 1, INT A
>Interrupt line = 10
>Capabilities Pointer = 70h
>Capability ID        = 1h
>Capabilities         = 3h - 8h
>
>Vendor ID      = 8086h, INTEL CORPORATION
>Device ID      = f18h,
>PCI index      = 0h
>Class Code     = 108000h Encryption (Other 128) ProgIF=0
>Revision ID    = eh
>Bus number     = 0
>Device number  = 26
>Function num   = 0
>Status Reg     = 10h
>Command Reg    = 106h
>Header type    = 0h Single-function
>BIST           = 0h Build-in-self-test not supported
>Latency Timer  = 0h
>Cache Line Size= 10h un-cacheable
>Base Address   = MEM@90800000h,32bit length 1048576 MEM@90700000h,32bit
>length 1048576
>Subsystem Vendor ID = 8086h
>Subsystem ID        = 7270h
>Max Lat        = 0ns
>Min Gnt        = 0ns
>PCI Int Pin    = 1, INT A
>Interrupt line =...
View Full Message
Re: Net.e1000 problem  
Of course I let run the send network card only if I start "Net.e1000 -I1 -l1".
If I let run both network cards and connect only the first to a network this card will work. As soon as I connect a 
netwoark cable with trafiic to the second card the system will stop. If I let run only the driver for the second card 
and connect it to a network cable I see that there are only packages coming out but nothing will be received.
Re: Net.e1000 problem  
Please can you post the exact commands that you are using to start the
network drivers as well as your TCP/IP setup.
In a previous posting you said that the second interface was only
receiving packets, but not transmitting packets. Now you say that it is
the other way around!
Have you tried changing the IRQs in the BIOS?



On 2015/6/2, 8:36 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>Of course I let run the send network card only if I start "Net.e1000 -I1
>-l1".
>If I let run both network cards and connect only the first to a network
>this card will work. As soon as I connect a netwoark cable with trafiic
>to the second card the system will stop. If I let run only the driver for
>the second card and connect it to a network cable I see that there are
>only packages coming out but nothing will be received.
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post113894
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com

Re: Net.e1000 problem  
Sorry for the wrong info in my last mail.

If I start both network cards:
"Net.e1000 -I0 -l1 -vvv &"
"Net.e1000 -I1 -l2 -vvv &"

If I start only the second network card:
"Net.e1000 -I1 -l1 -vvv &"

No IP stack  (Socket, Tcpip) is running only QNX4 protocol.

The second network card will receive packets only if it is running alone. As soon as the first network card is started 
too, the system will freeze if the second network card is connected.  I can see no packets coming out of the 2nd network
 card using wireshark on a direct connected PC.
Re: Net.e1000 problem  
OK, if you are just running Fleet, can you please post the output from
³netinfo -L1² and ³netinfo -L2² and also your /etc/config/netmap file.



On 2015/6/2, 9:02 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>Sorry for the wrong info in my last mail.
>
>If I start both network cards:
>"Net.e1000 -I0 -l1 -vvv &"
>"Net.e1000 -I1 -l2 -vvv &"
>
>If I start only the second network card:
>"Net.e1000 -I1 -l1 -vvv &"
>
>No IP stack  (Socket, Tcpip) is running only QNX4 protocol.
>
>The second network card will receive packets only if it is running alone.
>As soon as the first network card is started too, the system will freeze
>if the second network card is connected.  I can see no packets coming out
>of the 2nd network card using wireshark on a direct connected PC.
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post113896
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com

Re: Net.e1000 problem  
I'm sitting with putty and telnet on node 138 and make the request over the network.
The netmap file is only needed on 138 because I know the node number of the target node "1" and its MAC address.

For running both network adapters I get the following:

(root)//138/root>cat /etc/config/netmap
1 1 001B1B A32EB2

(root)//138/root>netinfo -n1 -L1

Driver Slot 0:  Driver Pid 77  Logical Net 1  Network Card: Ethernet/
INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
    Vendor ID ........................ 0x8086
    Device ID ........................ 0x1533
    Revision ......................... 0x3
    Physical Node ID ................. 001B1B A32EB2
    Media Rate ....................... 100Mb/s FDX
    Mtu .............................. 1514
    I/O Port Range ................... 0x90500000 -> 0x9050FFFE
    Hardware Interrupt ............... 7

    Total Packets Txd OK ............. 109
    Total Packets Txd Bad ............ 0
    Tx Collision Errors .............. 0
    Tx Collision Errors (aborted) .... 0
    Carrier Sense Lost on Tx ......... 0
    FIFO Underruns During Tx ......... 0
    Tx deferred ...................... 0
    Out of Window Collisions ......... 0

    Total Packets Rxd OK ............. 245
    Total Rx Errors .................. 0
    Multicast Packets Received ....... 0
    Broadcast Packets Received ....... 135
    FIFO Overruns During Rx .......... 0
    Alignment errors ................. 0
    CRC errors ....................... 0

(root)//138/root>netinfo -n1 -L2

Driver Slot 1:  Driver Pid 87  Logical Net 2  Network Card: Ethernet/
INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
    Vendor ID ........................ 0x8086
    Device ID ........................ 0x1533
    Revision ......................... 0x3
    Physical Node ID ................. 001B1B A32EAE
    Media Rate ....................... 0Mb/s HDX
    Mtu .............................. 1514
    I/O Port Range ................... 0x90400000 -> 0x9040FFFE
    Hardware Interrupt ............... 10

    Total Packets Txd OK ............. 0
    Total Packets Txd Bad ............ 0
    Tx Collision Errors .............. 0
    Tx Collision Errors (aborted) .... 0
    Carrier Sense Lost on Tx ......... 0
    FIFO Underruns During Tx ......... 0
    Tx deferred ...................... 0
    Out of Window Collisions ......... 0

    Total Packets Rxd OK ............. 0
    Total Rx Errors .................. 0
    Multicast Packets Received ....... 0
    Broadcast Packets Received ....... 0
    FIFO Overruns During Rx .......... 0
    Alignment errors ................. 0
    CRC errors ....................... 0


For running only the second network adapter I have to use a serial login to the device

Re: Net.e1000 problem  
I still think that you have an interrupt problem with the second adapter.
Are the network adapters on plug-in adapters, or are they fixed on the
motherboard? If they are on plug-in adapters, you can always try another
slot. If they are on the motherboard, you can try changing the IRQs in the
BIOS.



On 2015/6/2, 9:42 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>I'm sitting with putty and telnet on node 138 and make the request over
>the network.
>The netmap file is only needed on 138 because I know the node number of
>the target node "1" and its MAC address.
>
>For running both network adapters I get the following:
>
>(root)//138/root>cat /etc/config/netmap
>1 1 001B1B A32EB2
>
>(root)//138/root>netinfo -n1 -L1
>
>Driver Slot 0:  Driver Pid 77  Logical Net 1  Network Card: Ethernet/
>INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
>    Vendor ID ........................ 0x8086
>    Device ID ........................ 0x1533
>    Revision ......................... 0x3
>    Physical Node ID ................. 001B1B A32EB2
>    Media Rate ....................... 100Mb/s FDX
>    Mtu .............................. 1514
>    I/O Port Range ................... 0x90500000 -> 0x9050FFFE
>    Hardware Interrupt ............... 7
>
>    Total Packets Txd OK ............. 109
>    Total Packets Txd Bad ............ 0
>    Tx Collision Errors .............. 0
>    Tx Collision Errors (aborted) .... 0
>    Carrier Sense Lost on Tx ......... 0
>    FIFO Underruns During Tx ......... 0
>    Tx deferred ...................... 0
>    Out of Window Collisions ......... 0
>
>    Total Packets Rxd OK ............. 245
>    Total Rx Errors .................. 0
>    Multicast Packets Received ....... 0
>    Broadcast Packets Received ....... 135
>    FIFO Overruns During Rx .......... 0
>    Alignment errors ................. 0
>    CRC errors ....................... 0
>
>(root)//138/root>netinfo -n1 -L2
>
>Driver Slot 1:  Driver Pid 87  Logical Net 2  Network Card: Ethernet/
>INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
>    Vendor ID ........................ 0x8086
>    Device ID ........................ 0x1533
>    Revision ......................... 0x3
>    Physical Node ID ................. 001B1B A32EAE
>    Media Rate ....................... 0Mb/s HDX
>    Mtu .............................. 1514
>    I/O Port Range ................... 0x90400000 -> 0x9040FFFE
>    Hardware Interrupt ............... 10
>
>    Total Packets Txd OK ............. 0
>    Total Packets Txd Bad ............ 0
>    Tx Collision Errors .............. 0
>    Tx Collision Errors (aborted) .... 0
>    Carrier Sense Lost on Tx ......... 0
>    FIFO Underruns During Tx ......... 0
>    Tx deferred ...................... 0
>    Out of Window Collisions ......... 0
>
>    Total Packets Rxd OK ............. 0
>    Total Rx Errors .................. 0
>    Multicast Packets Received ....... 0
>    Broadcast Packets Received ....... 0
>    FIFO Overruns During Rx .......... 0
>    Alignment errors ................. 0
>    CRC errors ....................... 0
>
>
>For running only the second network adapter I have to use a serial login
>to the device
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post113899
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com

Re: Net.e1000 problem  
I'm using the latest driver on foundry27.
You extended it the last time for me.
Re: Net.e1000 problem  
I have also attached the Net.e1000 driver that I¹m using.



On 2015/6/2, 9:42 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>I'm sitting with putty and telnet on node 138 and make the request over
>the network.
>The netmap file is only needed on 138 because I know the node number of
>the target node "1" and its MAC address.
>
>For running both network adapters I get the following:
>
>(root)//138/root>cat /etc/config/netmap
>1 1 001B1B A32EB2
>
>(root)//138/root>netinfo -n1 -L1
>
>Driver Slot 0:  Driver Pid 77  Logical Net 1  Network Card: Ethernet/
>INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
>    Vendor ID ........................ 0x8086
>    Device ID ........................ 0x1533
>    Revision ......................... 0x3
>    Physical Node ID ................. 001B1B A32EB2
>    Media Rate ....................... 100Mb/s FDX
>    Mtu .............................. 1514
>    I/O Port Range ................... 0x90500000 -> 0x9050FFFE
>    Hardware Interrupt ............... 7
>
>    Total Packets Txd OK ............. 109
>    Total Packets Txd Bad ............ 0
>    Tx Collision Errors .............. 0
>    Tx Collision Errors (aborted) .... 0
>    Carrier Sense Lost on Tx ......... 0
>    FIFO Underruns During Tx ......... 0
>    Tx deferred ...................... 0
>    Out of Window Collisions ......... 0
>
>    Total Packets Rxd OK ............. 245
>    Total Rx Errors .................. 0
>    Multicast Packets Received ....... 0
>    Broadcast Packets Received ....... 135
>    FIFO Overruns During Rx .......... 0
>    Alignment errors ................. 0
>    CRC errors ....................... 0
>
>(root)//138/root>netinfo -n1 -L2
>
>Driver Slot 1:  Driver Pid 87  Logical Net 2  Network Card: Ethernet/
>INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
>    Vendor ID ........................ 0x8086
>    Device ID ........................ 0x1533
>    Revision ......................... 0x3
>    Physical Node ID ................. 001B1B A32EAE
>    Media Rate ....................... 0Mb/s HDX
>    Mtu .............................. 1514
>    I/O Port Range ................... 0x90400000 -> 0x9040FFFE
>    Hardware Interrupt ............... 10
>
>    Total Packets Txd OK ............. 0
>    Total Packets Txd Bad ............ 0
>    Tx Collision Errors .............. 0
>    Tx Collision Errors (aborted) .... 0
>    Carrier Sense Lost on Tx ......... 0
>    FIFO Underruns During Tx ......... 0
>    Tx deferred ...................... 0
>    Out of Window Collisions ......... 0
>
>    Total Packets Rxd OK ............. 0
>    Total Rx Errors .................. 0
>    Multicast Packets Received ....... 0
>    Broadcast Packets Received ....... 0
>    FIFO Overruns During Rx .......... 0
>    Alignment errors ................. 0
>    CRC errors ....................... 0
>
>
>For running only the second network adapter I have to use a serial login
>to the device
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post113899
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com

Attachment: Text Net.e1000 297.29 KB
Re: Net.e1000 problem  
Using "sysmon m=int" I can only see interrupts for line 7 and never for line 10.  Of course I will start the drivers 
always alone now.
On line 7 is the 1st controller
On line 10 is the 2nd controller.
Is there more output possible beside "-vvv" at Net.e1000 ?
Re: Net.e1000 problem  
You can try ³-vvvvvvv². This should give you lots of output.



On 2015/6/2, 10:12 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:

>Using "sysmon m=int" I can only see interrupts for line 7 and never for
>line 10.  Of course I will start the drivers always alone now.
>On line 7 is the 1st controller
>On line 10 is the 2nd controller.
>Is there more output possible beside "-vvv" at Net.e1000 ?
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post113904
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com