|
Steffen B.(deleted)
01/27/2011 9:41 AM
post82679
|
Does Intel 82579LM ethernet controller work with QNX 6.5.0?
Best regards,
Steffen
|
|
|
|
|
|
Hugh Brown
01/27/2011 9:56 AM
post82681
|
From what I can tell, the 82579 is a PHY. What is the PCI device ID?
On 11-01-27 9:41 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> Does Intel 82579LM ethernet controller work with QNX 6.5.0?
>
> Best regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post82679
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
01/28/2011 4:09 AM
post82708
|
Vendor ID: 0x8086
Device ID: 0x1502
|
|
|
|
|
|
Hugh Brown
01/28/2011 8:14 AM
post82710
|
No, this device ID is not currently in our driver. I will have to add it
some time and send you an update.
On 11-01-28 4:09 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> Vendor ID: 0x8086
> Device ID: 0x1502
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post82708
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
01/28/2011 9:01 AM
post82715
|
What do you think about the time schedule to add this?
|
|
|
|
|
|
Hugh Brown
01/28/2011 9:43 AM
post82726
|
I¹ll try for today, but I can¹t promise anything. You will have to do the
testing, as I don¹t have that chipset here.
On 11-01-28 9:01 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> What do you think about the time schedule to add this?
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post82715
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Hugh Brown
01/28/2011 3:09 PM
post82749
|
Here is an experimental driver for you to test. Please let me know how it
goes.
Thanks, Hugh.
On 11-01-28 9:01 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> What do you think about the time schedule to add this?
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post82715
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Hugh Brown
02/01/2011 8:31 AM
post82813
|
Have you had a chance to test this driver? Please let me know.
Thanks, Hugh.
On 11-01-28 9:01 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> What do you think about the time schedule to add this?
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post82715
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
02/01/2011 9:57 AM
post82823
|
Thank you very much for the driver. As soon I have the new mainboard I will test the driver and update you.
Regards,
Steffen
|
|
|
|
|
|
Matthias Ecker
05/17/2011 11:12 AM
post85788
|
Hello Hugh,
got an SlotCPU with a Q67 Chipset and a vid=0x8086,did=0x1502 Network Interface (Intel 82579 PHY) and tested your posted
driver. Unfortunately it does not work )-:
here are the steps I tried, to get it working:
Renamed it to devnp_e1000_2.so and put it into /lib/dll
sloginfo -c
io-pkt-v4-hc -i2 -ptcpip prefix=/alt -de1000_2 verbose=10,pci=0,did=0x1502
sloginfo
Time Sev Major Minor Args
May 17 19:07:06 5 14 0 tcpip starting
May 17 19:07:06 3 14 0 Using pseudo random generator. See "random" option
May 17 19:07:06 5 14 0 initializing IPsec... done
May 17 19:07:06 5 14 0 IPsec: Initialized Security Association Processing.
May 17 19:07:06 6 10 0 e1000_set_mac_type
May 17 19:07:06 6 10 0 e1000_set_mac_type
May 17 19:07:06 6 10 0 e1000_init_mac_ops_generic
May 17 19:07:06 6 10 0 e1000_init_phy_ops_generic
May 17 19:07:06 6 10 0 e1000_init_nvm_ops_generic
May 17 19:07:06 6 10 0 e1000_init_mac_ops_generic
May 17 19:07:06 6 10 0 e1000_init_nvm_ops_generic
May 17 19:07:06 6 10 0 ERROR: Flash registers not mapped
May 17 19:07:06 6 10 0 NVM Initialization Error
May 17 19:07:06 6 10 0 Hardware Initialization Failure
May 17 19:07:06 2 14 0 Unable to init devnp-e1000_2.so: No such device
as far as pci -vv tells me, the parameter should be ok:
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1502h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 5h
Bus number = 0
Device number = 25
Function num = 0
Status Reg = 10h
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 Error Response disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
PCI INTx enabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
BAR - 0 [Mem] = fe600000h 32bit length 131072 enabled
BAR - 1 [Mem] = fe624000h 32bit length 4096 enabled
BAR - 2 [I/O] = f080h length 32 enabled
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT A
Interrupt line = 10
CPU Interrupt = ah
Capabilities Pointer = c8h
Capability ID = 1h - Power Management
Capabilities = c822h - 7002000h
Capability ID = 5h - Message Signaled Interrupts
Capabilities = 80h - 0h
Capability ID = 13h - Unknown
Capabilities = 306h - 0h
Device Dependent Registers:
0x040: 0000 0000 0000 0000 0000 0000 0000 0000
...
0x0c0: 0000 0000 0000 0000 01d0 22c8 0020 0007
0x0d0: 05e0 8000 0000 0000 0000 0000 0000 0000
0x0e0: 1300 0603 0000 0000 0000 0000 0000 0000
0x0f0: 0000 0000 0000 0000 0000 0000 0000 0000
Is there something wrong with the io-pkt call?
Thanks,
Matthias
|
|
|
|
|
|
Hugh Brown
05/17/2011 11:26 AM
post85791
|
Please try the attached driver and let me know if it solves the problem.
Thanks, Hugh.
On 11-05-17 11:12 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Hello Hugh,
>
> got an SlotCPU with a Q67 Chipset and a vid=0x8086,did=0x1502 Network
> Interface (Intel 82579 PHY) and tested your posted driver. Unfortunately it
> does not work )-:
>
> here are the steps I tried, to get it working:
>
> Renamed it to devnp_e1000_2.so and put it into /lib/dll
>
> sloginfo -c
> io-pkt-v4-hc -i2 -ptcpip prefix=/alt -de1000_2 verbose=10,pci=0,did=0x1502
> sloginfo
> Time Sev Major Minor Args
> May 17 19:07:06 5 14 0 tcpip starting
> May 17 19:07:06 3 14 0 Using pseudo random generator. See "random"
> option
> May 17 19:07:06 5 14 0 initializing IPsec... done
> May 17 19:07:06 5 14 0 IPsec: Initialized Security Association
> Processing.
> May 17 19:07:06 6 10 0 e1000_set_mac_type
> May 17 19:07:06 6 10 0 e1000_set_mac_type
> May 17 19:07:06 6 10 0 e1000_init_mac_ops_generic
> May 17 19:07:06 6 10 0 e1000_init_phy_ops_generic
> May 17 19:07:06 6 10 0 e1000_init_nvm_ops_generic
> May 17 19:07:06 6 10 0 e1000_init_mac_ops_generic
> May 17 19:07:06 6 10 0 e1000_init_nvm_ops_generic
> May 17 19:07:06 6 10 0 ERROR: Flash registers not mapped
>
> May 17 19:07:06 6 10 0 NVM Initialization Error
>
> May 17 19:07:06 6 10 0 Hardware Initialization Failure
> May 17 19:07:06 2 14 0 Unable to init devnp-e1000_2.so: No such
> device
>
>
>
> as far as pci -vv tells me, the parameter should be ok:
>
> Class = Network (Ethernet)
> Vendor ID = 8086h, Intel Corporation
> Device ID = 1502h, Unknown Unknown
> PCI index = 0h
> Class Codes = 020000h
> Revision ID = 5h
> Bus number = 0
> Device number = 25
> Function num = 0
> Status Reg = 10h
> 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 Error Response disabled
> Data/Address stepping disabled
> SERR# driver disabled
> Fast back-to-back transactions to different agents disabled
> PCI INTx enabled
> Header type = 0h Single-function
> BIST = 0h Build-in-self-test not supported
> Latency Timer = 0h
> Cache Line Size= 0h
> BAR - 0 [Mem] = fe600000h 32bit length 131072 enabled
> BAR - 1 [Mem] = fe624000h 32bit length 4096 enabled
> BAR - 2 [I/O] = f080h length 32 enabled
> Max Lat = 0ns
> Min Gnt = 0ns
> PCI Int Pin = INT A
> Interrupt line = 10
> CPU Interrupt = ah
> Capabilities Pointer = c8h
> Capability ID = 1h - Power Management
> Capabilities = c822h - 7002000h
> Capability ID = 5h - Message Signaled Interrupts
> Capabilities = 80h - 0h
> Capability ID = 13h - Unknown
> Capabilities = 306h - 0h
> Device Dependent Registers:
> 0x040: 0000 0000 0000 0000 0000 0000 0000 0000
> ...
> 0x0c0: 0000 0000 0000 0000 01d0 22c8 0020 0007
> 0x0d0: 05e0 8000 0000 0000 0000 0000 0000 0000
> 0x0e0: 1300 0603 0000 0000 0000 0000 0000 0000
> 0x0f0: 0000 0000 0000 0000 0000 0000 0000 0000
>
> Is there something wrong with the io-pkt call?
>
> Thanks,
> Matthias
>
>
>
>
>
>
>
> _______________________________________________
>
> Networking...
|
|
|
|
|
|
Matthias Ecker
05/17/2011 11:45 AM
post85794
|
this one is better, though not perfect. There is a wm0 device and sloginfo shows, that it is the device with did 0x1502.
But there seems to be a problem with the link detection. I connected a cable, did SOCK=/alt ifconfig wm0 up and ...
ifconfig wm0 ip.
->
SOCK=/alt ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities rx=1f<IP4CSUM,TCP4CSUM,UDP4CSUM,TCP6CSUM,UDP6CSUM>
capabilities tx=7f<IP4CSUM,TCP4CSUM,UDP4CSUM,TCP6CSUM,UDP6CSUM,TSO4,TSO6>
enabled=0
address: 88:88:88:88:87:88
media: Ethernet none
inet 192.168.70.20 netmask 0xffffff00 broadcast 192.168.70.255
SOCK=/alt nicinfo
wm0:
INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
Link is DOWN
Physical Node ID ........................... 888888 888788
Current Physical Node ID ................... 888888 888788
Current Operation Rate ..................... 0 kb/s half-duplex
Active Interface Type ...................... MII
Active PHY address ....................... 2
Maximum Transmittable data Unit ............ 1500
Maximum Receivable data Unit ............... 1500
Hardware Interrupt ......................... 0xa
Memory Aperture ............................ 0xfe600000 - 0xfe61ffff
Promiscuous Mode ........................... Off
Multicast Support .......................... Enabled
Packets Transmitted OK ..................... 0
Bytes Transmitted OK ....................... 0
Broadcast Packets Transmitted OK ........... 0
Multicast Packets Transmitted OK ........... 0
Memory Allocation Failures on Transmit ..... 0
Packets Received OK ........................ 0
Bytes Received OK .......................... 0
Broadcast Packets Received OK .............. 0
Multicast Packets Received OK .............. 0
Memory Allocation Failures on Receive ...... 0
Single Collisions on Transmit .............. 0
Multiple Collisions on Transmit ............ 0
Deferred Transmits ......................... 0
Late Collision on Transmit errors .......... 0
Transmits aborted (excessive collisions) ... 0
Jabber detected ............................ 0
Receive Alignment errors ................... 0
Received packets with CRC errors ........... 0
Packets Dropped on receive ................. 0
Oversized Packets received ................. 0
Short packets .............................. 0
Squelch Test errors ........................ 0
Invalid Symbol Errors ...................... 0
Regards,
Matthias
|
|
|
|
|
|
Hugh Brown
05/17/2011 1:21 PM
post85805
|
Please will you run the attached driver as before and send me the sloginfo
output. I have added some debug code.
Thanks, Hugh.
On 11-05-17 11:45 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
>
>
> this one is better, though not perfect. There is a wm0 device and sloginfo
> shows, that it is the device with did 0x1502.
>
> But there seems to be a problem with the link detection. I connected a cable,
> did SOCK=/alt ifconfig wm0 up and ... ifconfig wm0 ip.
>
> ->
> SOCK=/alt ifconfig
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
> inet 127.0.0.1 netmask 0xff000000
> wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> capabilities rx=1f<IP4CSUM,TCP4CSUM,UDP4CSUM,TCP6CSUM,UDP6CSUM>
> capabilities
> tx=7f<IP4CSUM,TCP4CSUM,UDP4CSUM,TCP6CSUM,UDP6CSUM,TSO4,TSO6>
> enabled=0
> address: 88:88:88:88:87:88
> media: Ethernet none
> inet 192.168.70.20 netmask 0xffffff00 broadcast 192.168.70.255
>
>
> SOCK=/alt nicinfo
> wm0:
> INTEL PRO/1000 Gigabit (Copper) Ethernet Controller
>
> Link is DOWN
>
> Physical Node ID ........................... 888888 888788
> Current Physical Node ID ................... 888888 888788
> Current Operation Rate ..................... 0 kb/s half-duplex
> Active Interface Type ...................... MII
> Active PHY address ....................... 2
> Maximum Transmittable data Unit ............ 1500
> Maximum Receivable data Unit ............... 1500
> Hardware Interrupt ......................... 0xa
> Memory Aperture ............................ 0xfe600000 - 0xfe61ffff
> Promiscuous Mode ........................... Off
> Multicast Support .......................... Enabled
>
> Packets Transmitted OK ..................... 0
> Bytes Transmitted OK ....................... 0
> Broadcast Packets Transmitted OK ........... 0
> Multicast Packets Transmitted OK ........... 0
> Memory Allocation Failures on Transmit ..... 0
>
> Packets Received OK ........................ 0
> Bytes Received OK .......................... 0
> Broadcast Packets Received OK .............. 0
> Multicast Packets Received OK .............. 0
> Memory Allocation Failures on Receive ...... 0
>
> Single Collisions on Transmit .............. 0
> Multiple Collisions on Transmit ............ 0
> Deferred Transmits ......................... 0
> Late Collision on Transmit errors .......... 0
> Transmits aborted (excessive collisions) ... 0
> Jabber detected ............................ 0
> Receive Alignment errors ................... 0
> Received packets with CRC errors ........... 0
> Packets Dropped on receive ................. 0
> Oversized Packets received ................. 0
> Short packets .............................. 0
> Squelch Test errors ........................ 0
> Invalid Symbol Errors ...................... 0
>
> Regards,
> Matthias
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85794
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Matthias Ecker
05/18/2011 4:00 AM
post85828
|
no worries... I've attached the sloginfo output.
Regards,
Matthias
|
|
|
|
|
|
Hugh Brown
05/18/2011 8:13 AM
post85837
|
Matthias,
Have you tried another O/S on this board and if so, does the Ethernet
interface work correctly with a valid MAC address?
Thanks, Hugh.
On 11-05-18 4:00 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> no worries... I've attached the sloginfo output.
>
> Regards,
> Matthias
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85828
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Matthias Ecker
05/18/2011 11:04 AM
post85857
|
Dear Hugh,
tested ubuntu 11.04 and both network interfaces are ok. Even the one, that qnx doesn't support "out of the box" is
working (ifconfig, ping, telnet)
Regards,
Matthias
|
|
|
|
|
|
Hugh Brown
05/18/2011 11:10 AM
post85858
|
OK, I¹ll have to investigate further. Does Ubuntu get a valid MAC address
from the 1502 interface?
Thanks, Hugh.
On 11-05-18 11:04 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Dear Hugh,
>
> tested ubuntu 11.04 and both network interfaces are ok. Even the one, that qnx
> doesn't support "out of the box" is working (ifconfig, ping, telnet)
>
> Regards,
> Matthias
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85857
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Matthias Ecker
05/18/2011 11:14 AM
post85860
|
cant't tell.
is 88:88:88:88:87:88 a valid mac? didn't expect such a continuity...
|
|
|
|
|
|
Hugh Brown
05/18/2011 11:15 AM
post85861
|
No, that MAC address is invalid, so if Ubuntu is getting the same MAC
address, then there is a problem with the flash on that board.
On 11-05-18 11:14 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> cant't tell.
> is 88:88:88:88:87:88 a valid mac? didn't expect such a continuity...
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85860
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Hugh Brown
05/18/2011 3:33 PM
post85876
|
Matthias,
Please will you try the attached driver and see if it makes any difference.
Please send me the sloginfo output once you have tried it.
Many thanks, Hugh.
On 11-05-18 11:14 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> cant't tell.
> is 88:88:88:88:87:88 a valid mac? didn't expect such a continuity...
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85860
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Matthias Ecker
05/19/2011 2:36 AM
post85907
|
Dear Hugh,
no worries! tried it, but it does not make any difference (at least for me): no link detection and no way to ping the
outside.
Thank you for your effort!!
Regards,
Matthias
|
|
|
|
|
|
Hugh Brown
05/19/2011 7:53 AM
post85924
|
Matthias,
I didn¹t get the full sloginfo output. Please can you start slogger s128k¹
and then restart the driver and send me the sloginfo output? Please can you
also attach the full pci vv¹ output?
Many thanks, Hugh.
On 11-05-19 2:36 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Dear Hugh,
>
> no worries! tried it, but it does not make any difference (at least for me):
> no link detection and no way to ping the outside.
>
> Thank you for your effort!!
>
> Regards,
> Matthias
>
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85907
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Matthias Ecker
05/19/2011 9:09 AM
post85931
|
Dear Hugh,
you'll find the requested information attached to this reply. Please let me know if you need any further information.
Regards,
Matthias
196 slay slogger
197 use slogger
198 slogger -s 1024
199 io-pkt-v4-hc -i2 -ptcpip prefix=/alt -de1000_5 verbose=10,pci=0,did=0x1502
200 SOCK=/alt ifconfig wm0 up
201 SOCK=/alt ifconfig wm0 192.168.70.20
202 SOCK=/alt ifconfig
203 sloginfo > sloginfo.out4
204 pci -vv > pcivv.txt
205 tar -cvf info.tar sloginfo.out4 pcivv.txt
206 history
|
|
|
|
|
|
Hugh Brown
05/19/2011 12:39 PM
post85949
|
I have found a Sandy Bridge board, so will let you know when I have the
network driver working.
Hugh.
On 11-05-19 9:09 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Dear Hugh,
>
> you'll find the requested information attached to this reply. Please let me
> know if you need any further information.
>
> Regards,
> Matthias
>
> 196 slay slogger
> 197 use slogger
> 198 slogger -s 1024
> 199 io-pkt-v4-hc -i2 -ptcpip prefix=/alt -de1000_5
> verbose=10,pci=0,did=0x1502
> 200 SOCK=/alt ifconfig wm0 up
> 201 SOCK=/alt ifconfig wm0 192.168.70.20
> 202 SOCK=/alt ifconfig
> 203 sloginfo > sloginfo.out4
> 204 pci -vv > pcivv.txt
> 205 tar -cvf info.tar sloginfo.out4 pcivv.txt
> 206 history
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85931
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Hugh Brown
05/27/2011 3:00 PM
post86214
|
Matthias,
You will have to speak to Kontron about re-programming the EEPROM on your
board with a correct MAC address. I have been in contact with Intel and the
MAC address that you have on your machine is the default address if no MAC
address is programmed.
I should have an experimental driver ready for you to test either later
today or on Monday.
Thanks, Hugh.
On 11-05-19 9:09 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Dear Hugh,
>
> you'll find the requested information attached to this reply. Please let me
> know if you need any further information.
>
> Regards,
> Matthias
>
> 196 slay slogger
> 197 use slogger
> 198 slogger -s 1024
> 199 io-pkt-v4-hc -i2 -ptcpip prefix=/alt -de1000_5
> verbose=10,pci=0,did=0x1502
> 200 SOCK=/alt ifconfig wm0 up
> 201 SOCK=/alt ifconfig wm0 192.168.70.20
> 202 SOCK=/alt ifconfig
> 203 sloginfo > sloginfo.out4
> 204 pci -vv > pcivv.txt
> 205 tar -cvf info.tar sloginfo.out4 pcivv.txt
> 206 history
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85931
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
06/29/2011 8:58 AM
post86938
|
I tested the latest driver you posted here and it works.
But in general I have timing problems with the e1000 driver.
I solved the problems using APIC (see also http://community.qnx.com/sf/discussion/do/listPosts/projects.networking/
discussion.drivers.topc20387)
Regards,
Steffen
|
|
|
|
|
|
Hugh Brown
05/27/2011 3:50 PM
post86218
|
Here is the experimental driver for you to test. You can override the MAC
address by specifying ³mac=001122334455² on the command line.
Please let me know how it goes.
Thanks, Hugh.
On 11-05-19 9:09 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Dear Hugh,
>
> you'll find the requested information attached to this reply. Please let me
> know if you need any further information.
>
> Regards,
> Matthias
>
> 196 slay slogger
> 197 use slogger
> 198 slogger -s 1024
> 199 io-pkt-v4-hc -i2 -ptcpip prefix=/alt -de1000_5
> verbose=10,pci=0,did=0x1502
> 200 SOCK=/alt ifconfig wm0 up
> 201 SOCK=/alt ifconfig wm0 192.168.70.20
> 202 SOCK=/alt ifconfig
> 203 sloginfo > sloginfo.out4
> 204 pci -vv > pcivv.txt
> 205 tar -cvf info.tar sloginfo.out4 pcivv.txt
> 206 history
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post85931
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Matthias Ecker
05/30/2011 3:31 AM
post86239
|
Dear Hugh,
this one is working! media detection worked and I could ping and telnet other hosts in the net. Great work!
It is a adlink nu-pro-e340 test slot cpu (not the final version). I'm in contact with our sales director and told him
the problems with the mac address. He forwarded the information the board developer.
Do you need further tests? sloginfo output?
May I use this driver for testing purposes, or is it too "experimental"?
Thanks,
Matthias
|
|
|
|
|
|
Hugh Brown
05/30/2011 8:18 AM
post86249
|
Hi Matthias,
Good news! You can use this driver for testing purposes. I have run some
basic tests with the driver, but I think that it should be pretty stable.
I don¹t need any further output.
Thanks, Hugh.
On 11-05-30 3:31 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Dear Hugh,
>
> this one is working! media detection worked and I could ping and telnet other
> hosts in the net. Great work!
>
> It is a adlink nu-pro-e340 test slot cpu (not the final version). I'm in
> contact with our sales director and told him the problems with the mac
> address. He forwarded the information the board developer.
>
> Do you need further tests? sloginfo output?
>
> May I use this driver for testing purposes, or is it too "experimental"?
>
> Thanks,
> Matthias
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post86239
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Hugh Brown
05/31/2011 8:55 AM
post86288
|
Matthias,
Here is the updated enumeration file, so that the driver will start
automatically at boot time. You can copy this file to
/etc/system/enum/devices.
Hugh.
On 11-05-30 3:31 AM, "Matthias Ecker" <community-noreply@qnx.com> wrote:
> Dear Hugh,
>
> this one is working! media detection worked and I could ping and telnet other
> hosts in the net. Great work!
>
> It is a adlink nu-pro-e340 test slot cpu (not the final version). I'm in
> contact with our sales director and told him the problems with the mac
> address. He forwarded the information the board developer.
>
> Do you need further tests? sloginfo output?
>
> May I use this driver for testing purposes, or is it too "experimental"?
>
> Thanks,
> Matthias
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post86239
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
| Attachment: |
net
27.05 KB
|
|
|
|
|
Steffen B.(deleted)
06/30/2011 9:47 AM
post86982
|
Unfortunately I still have timing problems with the driver although I use APIC.
The original driver which was delivered with QNX 6.5.0 runs with Intel 82574L with real telegram traffic very well
(without APIC).
The driver posted here disrupts or delays traffic.
Regards,
Steffen
|
|
|
|
|
|
Hugh Brown
06/30/2011 10:16 AM
post86986
|
Please can you explain what you mean by ³disrupts or delays traffic²? How
are you measuring this? What hardware is this running on?
Thanks, Hugh.
On 11-06-30 9:47 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> Unfortunately I still have timing problems with the driver although I use
> APIC.
>
> The original driver which was delivered with QNX 6.5.0 runs with Intel 82574L
> with real telegram traffic very well (without APIC).
>
> The driver posted here disrupts or delays traffic.
>
> Regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post86982
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
06/30/2011 10:45 AM
post86988
|
I use the following hardware:
Fujitsu D3076 mainboard with Q67 chipset, i7-2600K Sandy Bridge processor, Ethernet Intel 82574L and 82579LM.
I have a connection to another PC and I send and receive every 100ms about 2MB Data with 40ms timeout.
Normally this data transfer needs less than 1ms but sometimes the transfer stops and I run into my 40ms timeout.
As I mentioned before, with the released driver I do not have any problems.
Best regards,
Steffen
|
|
|
|
|
|
Hugh Brown
06/30/2011 11:06 AM
post86989
|
Please will you run the attached ttcp program and let me know what type of
throughput you get. I have tested this on our Sandy Bridge platform (Intel
reference) and consistently get 70MB/s throughput. I am running the test via
a gigabit switch to another x86 PC. Please run the program as follows:
On server:
ttcp s r
On client:
ttcp s t n100000 ip.address
Thanks, Hugh.
On 11-06-30 10:45 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> I use the following hardware:
> Fujitsu D3076 mainboard with Q67 chipset, i7-2600K Sandy Bridge processor,
> Ethernet Intel 82574L and 82579LM.
>
> I have a connection to another PC and I send and receive every 100ms about 2MB
> Data with 40ms timeout.
>
> Normally this data transfer needs less than 1ms but sometimes the transfer
> stops and I run into my 40ms timeout.
>
> As I mentioned before, with the released driver I do not have any problems.
>
> Best regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post86988
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
| Attachment: |
ttcp
25.81 KB
|
|
|
|
|
Hugh Brown
06/30/2011 11:20 AM
post86990
|
I should add that I am also running this in APIC mode and have also tested
with another e1000 adapter plugged into a PCIe socket, with the same
results.
On 11-06-30 10:45 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> I use the following hardware:
> Fujitsu D3076 mainboard with Q67 chipset, i7-2600K Sandy Bridge processor,
> Ethernet Intel 82574L and 82579LM.
>
> I have a connection to another PC and I send and receive every 100ms about 2MB
> Data with 40ms timeout.
>
> Normally this data transfer needs less than 1ms but sometimes the transfer
> stops and I run into my 40ms timeout.
>
> As I mentioned before, with the released driver I do not have any problems.
>
> Best regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post86988
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
07/01/2011 2:50 AM
post87011
|
I started the program as follows, but nothing happens:
Server:
# SOCK=/dev/socket2 ttcp -s -r
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
Client:
# SOCK=/dev/socket2 ttcp -s -t -n100000 172.16.205.4
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
What is wrong?
I tested the new driver on an older system (Core 2 Quad with G41 chipset, ICH7 and PCI express eth), too. I had the same
problems. But the released driver works very well.
Best regards,
Steffen
|
|
|
|
|
|
Hugh Brown
07/01/2011 9:11 AM
post87018
|
There should only be one ‘-’ for each of the options. I see that you have 2.
On 11-07-01 2:50 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> I started the program as follows, but nothing happens:
>
> Server:
> # SOCK=/dev/socket2 ttcp -s -r
> ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
> ttcp-r: socket
>
> Client:
> # SOCK=/dev/socket2 ttcp -s -t -n100000 172.16.205.4
> ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
> ttcp-r: socket
>
> What is wrong?
>
> I tested the new driver on an older system (Core 2 Quad with G41 chipset, ICH7
> and PCI express eth), too. I had the same problems. But the released driver
> works very well.
>
> Best regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post87011
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
07/01/2011 9:31 AM
post87019
|
I used only one "-". If you look directly in the forum, there is only displayed one "-" .
Best regards,
Steffen
|
|
|
|
|
|
Hugh Brown
07/04/2011 7:43 AM
post87033
|
Can you try with just one interface running? Start ‘io-pkt-v4 –de1000
did=0x1502’ then ifconfig the interface and run ttcp.
If you started io-pkt with the prefix command (prefix=/alt), then you should
start ttcp as “SOCK=/alt ttcp ...”.
On 11-07-01 2:50 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> I started the program as follows, but nothing happens:
>
> Server:
> # SOCK=/dev/socket2 ttcp -s -r
> ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
> ttcp-r: socket
>
> Client:
> # SOCK=/dev/socket2 ttcp -s -t -n100000 172.16.205.4
> ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
> ttcp-r: socket
>
> What is wrong?
>
> I tested the new driver on an older system (Core 2 Quad with G41 chipset, ICH7
> and PCI express eth), too. I had the same problems. But the released driver
> works very well.
>
> Best regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post87011
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
07/04/2011 11:21 AM
post87042
|
Sorry, but I still don't get any output. I started the program as follows:
Server:
io-pkt-v4 -drtl8169 verbose=4,pci=0x0,vid=0x10ec,did=0x8168 -ptcpip
waitfor /dev/socket
ifconfig en0 172.16.205.4 netmask 255.255.0.0
ttcp s r
Client:
io-pkt-v4 -de1000 verbose=1,pci=0x0,vid=0x8086,did=0x1502 -ptcpip
waitfor /dev/socket
ifconfig en0 172.16.205.3 netmask 255.255.0.0
ttcp -s -t -n100000 172.16.205.4
Best regards,
Steffen
|
|
|
|
|
|
Hugh Brown
07/04/2011 11:38 AM
post87045
|
Can you ping from one node to another? Also can you do a ‘cksum ttcp’. The
output from mine is below.
1944084984 26431 ttcp
Thanks, Hugh.
On 11-07-04 11:21 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> Sorry, but I still don't get any output. I started the program as follows:
>
> Server:
> io-pkt-v4 -drtl8169 verbose=4,pci=0x0,vid=0x10ec,did=0x8168 -ptcpip
> waitfor /dev/socket
> ifconfig en0 172.16.205.4 netmask 255.255.0.0
> ttcp s r
>
> Client:
> io-pkt-v4 -de1000 verbose=1,pci=0x0,vid=0x8086,did=0x1502 -ptcpip
> waitfor /dev/socket
> ifconfig en0 172.16.205.3 netmask 255.255.0.0
> ttcp -s -t -n100000 172.16.205.4
>
> Best regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post87042
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
07/05/2011 2:31 AM
post87050
|
I can ping and the checksum is the same.
Regards,
Steffen
|
|
|
|
|
|
Hugh Brown
07/05/2011 7:43 AM
post87064
|
Steffen,
Are you starting the programs in a script? Looking at your previous post, I
see that you have a waitfor /dev/socket, so that is why I am assuming you
are running a script. You should have a ³sleep 3² between the ifconfig and
starting the ttcp, as the link auto-negotiation takes about 3 seconds.
Hugh.
On 11-07-05 2:31 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> I can ping and the checksum is the same.
>
> Regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post87050
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Hugh Brown
07/05/2011 7:57 AM
post87066
|
Further to my last e-mail, do you have a sample program that you are using
to detect the delay? If so, could I have a copy to do some testing here?
Thanks, Hugh.
On 11-07-05 2:31 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> I can ping and the checksum is the same.
>
> Regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post87050
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
07/06/2011 4:26 AM
post87114
|
Sorry, but the delay didn't help, too. But I wrote my own application and I have about 10MB/s with a 100Mb/s-switch.
Then I wrote a test application (see atachment). Every 100ms 8002 bytes are transfered to a server and back. This should
normally need about 1600us. That means for one way 800us and I detected about 850us. If the time is bigger than 1000us
I print out the time value.
The first transfer in my systems always needs about 200ms. I don't know why. And then you shouldn't have any output if
the transfer works properly.
The server you should start without any parameters. The client needs the ip address of the server system: EthClient ip.
address
Best regards,
Steffen
|
|
|
|
|
|
Steffen B.(deleted)
07/06/2011 4:28 AM
post87115
|
|
|
|
|
|
|
Hugh Brown
07/06/2011 2:22 PM
post87153
|
Steffen,
Thank you very much for the test programs they enabled me to find the
problem and fix it. I have attached an updated driver for you to test, so
please let me know if everything is working OK now.
Thanks, Hugh.
On 11-07-06 4:28 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> The client comes here.
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post87115
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Limited. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
07/11/2011 8:55 AM
post87239
|
Thank you very much for the driver. In general the driver works now. I don't have these long delays any more.
But I still have problems:
- With 82579LM device the transmission needs more than 1000us (this can be reproduced with my test programs). Normally I
tested with 82574L device and transmission needs only about 850us.
- With 82574L device my system runs about 2 hours. Then a timeout occurs to a third network device. With my old Core 2
Quad system and PCI Express ethernet adapter with 82574L controller and the new driver the system runs very well.
Best regards,
Steffen
|
|
|
|
|
|
Hugh Brown
07/11/2011 9:12 AM
post87241
|
The transmit routine is the same for all the chipsets, so I don¹t see how I
can change the time required for transmission. When I tested the new driver
with your test program, I didn¹t see any timeout messages at all.
Hugh.
On 11-07-11 8:55 AM, "Steffen Brühl" <community-noreply@qnx.com> wrote:
> Thank you very much for the driver. In general the driver works now. I don't
> have these long delays any more.
>
> But I still have problems:
> - With 82579LM device the transmission needs more than 1000us (this can be
> reproduced with my test programs). Normally I tested with 82574L device and
> transmission needs only about 850us.
>
> - With 82574L device my system runs about 2 hours. Then a timeout occurs to a
> third network device. With my old Core 2 Quad system and PCI Express ethernet
> adapter with 82574L controller and the new driver the system runs very well.
>
> Best regards,
>
> Steffen
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post87239
>
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Limited. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Steffen B.(deleted)
07/12/2011 5:55 AM
post87264
|
I changed my EthClient (see attachment) to print out every transmission time. Here are the results:
82574L:
0: 196086 us for 8002 bytes
1: 895 us for 8002 bytes
2: 874 us for 8002 bytes
3: 914 us for 8002 bytes
4: 893 us for 8002 bytes
5: 934 us for 8002 bytes
6: 915 us for 8002 bytes
7: 893 us for 8002 bytes
8: 872 us for 8002 bytes
9: 913 us for 8002 bytes
10: 892 us for 8002 bytes
11: 871 us for 8002 bytes
12: 913 us for 8002 bytes
13: 892 us for 8002 bytes
14: 888 us for 8002 bytes
15: 911 us for 8002 bytes
16: 891 us for 8002 bytes
17: 869 us for 8002 bytes
18: 909 us for 8002 bytes
19: 887 us for 8002 bytes
82579LM:
0: 206610 us for 8002 bytes
1: 1015 us for 8002 bytes
2: 1014 us for 8002 bytes
3: 1014 us for 8002 bytes
4: 1014 us for 8002 bytes
5: 1014 us for 8002 bytes
6: 1014 us for 8002 bytes
7: 1013 us for 8002 bytes
8: 1012 us for 8002 bytes
9: 1013 us for 8002 bytes
10: 1012 us for 8002 bytes
11: 1014 us for 8002 bytes
12: 1014 us for 8002 bytes
13: 1013 us for 8002 bytes
14: 1014 us for 8002 bytes
15: 1013 us for 8002 bytes
16: 1014 us for 8002 bytes
17: 1013 us for 8002 bytes
18: 1013 us for 8002 bytes
19: 1012 us for 8002 bytes
Maybe the transmission time is different bacause one is a controller and the other a PHY?
I also don't understand, why the first transmission needs so much time.
Best regards,
Steffen
|
|
|
|
|
|
