|
Klaus Pantleon(deleted)
|
Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/10/2013 10:38 AM
post107346
|
Net.e1000 with i210 and i217
Hello to all QNX4 supporters!
I have here a new test PC with intel network cards inside.
The PCI device IDs are 0x1533 and 0x153a. This devive IDs are supported from the e1000 driver in linux and on the intel
page they are described as "i210" and "i217" devices.
with the Net.e1000 I have no success using "-d" or "-p -i" and will get always:
No device found
loc_e1000 failed
Is there a posiibility to extend the Net.e1000 for this cards?
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/10/2013 10:42 AM
post107347
|
Re: Net.e1000 with i210 and i217
Driver attached.
On 2013/12/10, 10:38 AM, "Klaus Pantleon" <community-noreply@qnx.com>
wrote:
>Hello to all QNX4 supporters!
>
>I have here a new test PC with intel network cards inside.
>The PCI device IDs are 0x1533 and 0x153a. This devive IDs are supported
>from the e1000 driver in linux and on the intel page they are described
>as "i210" and "i217" devices.
>with the Net.e1000 I have no success using "-d" or "-p -i" and will get
>always:
>No device found
>loc_e1000 failed
>
>Is there a posiibility to extend the Net.e1000 for this cards?
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107346
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/10/2013 10:58 AM
post107348
|
Re: Net.e1000 with i210 and i217
No success.
FTP+chmod OK
starting the driver no success. Still got:
Net.e1000: proc_fun =e0:0a69
Net.e1000: vidbus_inuse = e8:4bf0
No devices found
loc_e1000 failed
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/10/2013 11:03 AM
post107349
|
Re: Net.e1000 with i210 and i217
If you start the diver with Œ-v¹ command line option, is there any more
output?
On 2013/12/10, 10:58 AM, "Klaus Pantleon" <community-noreply@qnx.com>
wrote:
>No success.
>FTP+chmod OK
>starting the driver no success. Still got:
>Net.e1000: proc_fun =e0:0a69
>Net.e1000: vidbus_inuse = e8:4bf0
>No devices found
>loc_e1000 failed
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107348
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/10/2013 11:24 AM
post107351
|
Re: Net.e1000 with i210 and i217
I already used "-vv". There is no difference in ouptut even if I use "-vvvv".
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/10/2013 11:29 AM
post107352
|
Re: Net.e1000 with i210 and i217
Please can you post the output from Œshow_pci -v¹?
On 2013/12/10, 11:24 AM, "Klaus Pantleon" <community-noreply@qnx.com>
wrote:
>I already used "-vv". There is no difference in ouptut even if I use
>"-vvvv".
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107351
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/11/2013 1:59 AM
post107391
|
Re: Net.e1000 with i210 and i217
Hi Hugh,
I attached the show_pci -v output. Please be aware that I use a changed show_pci because of a problem in libraries. If
you have to many PCI devices the origin show_pci crashes. As I removed the gathering of the IRQ routing stuff at the end
of normal show_pci it was working properly for me.
If you need the IRQ routing stuff at the end of the 'normal' show_pci please let me know.
BR, Klaus
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/11/2013 10:11 AM
post107404
|
Re: Net.e1000 with i210 and i217
This is really weird, as I have a 1533 device in my QNX4 machine and it
works fine. Does the 0x10d3 device on your machine work?
On 2013/12/11, 1:59 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:
>Hi Hugh,
>
>I attached the show_pci -v output. Please be aware that I use a changed
>show_pci because of a problem in libraries. If you have to many PCI
>devices the origin show_pci crashes. As I removed the gathering of the
>IRQ routing stuff at the end of normal show_pci it was working properly
>for me.
>If you need the IRQ routing stuff at the end of the 'normal' show_pci
>please let me know.
>
>BR, Klaus
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107391
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/11/2013 10:18 AM
post107407
|
Re: Net.e1000 with i210 and i217
Yes, the 0x10d3 is a PCIe network card I added to make my tests easier. Now I can reach the QNX node using fleet.
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/11/2013 11:06 AM
post107409
|
Re: Net.e1000 with i210 and i217
Please run the attached driver on a text mode console and see if it finds
the device. It will spew a whole lot of device IDs to the screen, but
0x1533 and 0x153c should be near the end. If it doesn¹t find your device,
please let me know what the lines read for the 2 devices.
On 2013/12/11, 10:18 AM, "Klaus Pantleon" <community-noreply@qnx.com>
wrote:
>Yes, the 0x10d3 is a PCIe network card I added to make my tests easier.
>Now I can reach the QNX node using fleet.
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107407
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/12/2013 2:46 AM
post107461
|
Re: Net.e1000 with i210 and i217
I get following output:
(root)//185/root>./Net.e1000 -d1533 -I1 -l2 -v
Find device 0x1533 - status 0x86
No devices found
loc_e1000 failed
(root)//185/root>./Net.e1000 -d153c -I1 -l2 -v
Find device 0x153c - status 0x86
No devices found
loc_e1000 failed
(root)//185/root>
(root)//185/root>./Net.e1000 -I1 -l2 -v
...
Find device 0x1522 - status 0x86
Find device 0x1523 - status 0x86
Find device 0x1524 - status 0x86
Find device 0x1525 - status 0x86
Find device 0x1526 - status 0x86
Find device 0x1527 - status 0x86
Find device 0x1531 - status 0x86
Find device 0x1533 - status 0x86
Find device 0x1534 - status 0x86
Find device 0x1535 - status 0x86
Find device 0x1536 - status 0x86
Find device 0x1537 - status 0x86
Find device 0x1538 - status 0x86
Find device 0x1539 - status 0x86
Find device 0x153a - status 0x86
Find device 0x153b - status 0x86
Find device 0x155a - status 0x86
Find device 0x1559 - status 0x86
Find device 0x1546 - status 0x86
Find device 0x294c - status 0x86
Find device 0xf0fe - status 0x86
No devices found
loc_e1000 failed
(root)//185/root>
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/12/2013 8:48 AM
post107467
|
Re: Net.e1000 with i210 and i217
Please run the attached driver and let me have the output. I have added
some more debug. Please run it as you did before, with the -d command line
option.
On 2013/12/12, 2:46 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:
>I get following output:
>
>(root)//185/root>./Net.e1000 -d1533 -I1 -l2 -v
>Find device 0x1533 - status 0x86
>No devices found
>loc_e1000 failed
>(root)//185/root>./Net.e1000 -d153c -I1 -l2 -v
>Find device 0x153c - status 0x86
>No devices found
>loc_e1000 failed
>(root)//185/root>
>
>(root)//185/root>./Net.e1000 -I1 -l2 -v
>...
>Find device 0x1522 - status 0x86
>Find device 0x1523 - status 0x86
>Find device 0x1524 - status 0x86
>Find device 0x1525 - status 0x86
>Find device 0x1526 - status 0x86
>Find device 0x1527 - status 0x86
>Find device 0x1531 - status 0x86
>Find device 0x1533 - status 0x86
>Find device 0x1534 - status 0x86
>Find device 0x1535 - status 0x86
>Find device 0x1536 - status 0x86
>Find device 0x1537 - status 0x86
>Find device 0x1538 - status 0x86
>Find device 0x1539 - status 0x86
>Find device 0x153a - status 0x86
>Find device 0x153b - status 0x86
>Find device 0x155a - status 0x86
>Find device 0x1559 - status 0x86
>Find device 0x1546 - status 0x86
>Find device 0x294c - status 0x86
>Find device 0xf0fe - status 0x86
>No devices found
>loc_e1000 failed
>(root)//185/root>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107461
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/11/2013 11:06 AM
post107410
|
Re: Net.e1000 with i210 and i217
Can I give you more info using debian, freebsd or qnx6?
The first I'm familiar with. QNX6 I have tested years ago.
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/11/2013 11:47 AM
post107415
|
Re: Net.e1000 with i210 and i217
No, just run the driver I sent you and let me know the results.
On 2013/12/11, 11:06 AM, "Klaus Pantleon" <community-noreply@qnx.com>
wrote:
>Can I give you more info using debian, freebsd or qnx6?
>The first I'm familiar with. QNX6 I have tested years ago.
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107410
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/12/2013 9:23 AM
post107469
|
Re: Net.e1000 with i210 and i217
I used the previously send driver and got following:
(root)//185/root>./Net.e1000 -d153c -I1 -l2 -vvv
Net.e1000: proc_fun = e0:0a69
Net.e1000: vidbuf_inuse = e8:4bf0
Find device 0x153c - status 0x86
No devices found
loc_e1000 failed
(root)//185/root>cksum ./Net.e1000
3195832594 302571 ./Net.e1000
(root)//185/root>
(root)//185/root>./Net.e1000 -d1533 -I1 -l2 -v
...
Vendor 8086 - Device c08 - bus 0 - devfn 0
Vendor 8086 - Device c01 - bus 0 - devfn 8
Vendor 8086 - Device 41a - bus 0 - devfn 10
Vendor 8086 - Device c0c - bus 0 - devfn 18
Vendor 8086 - Device 8c31 - bus 0 - devfn a0
Vendor 8086 - Device 8c3a - bus 0 - devfn b0
Vendor 8086 - Device 153a - bus 0 - devfn c8
Vendor 8086 - Device 8c2d - bus 0 - devfn d0
Vendor 8086 - Device 8c20 - bus 0 - devfn d8
Vendor 8086 - Device 8c12 - bus 0 - devfn e0
Vendor 8086 - Device 8c16 - bus 0 - devfn e3
Vendor 8086 - Device 8c26 - bus 0 - devfn e8
Vendor 8086 - Device 8c56 - bus 0 - devfn f8
Vendor 8086 - Device 8c00 - bus 0 - devfn fa
Vendor 8086 - Device 8c22 - bus 0 - devfn fb
Vendor 8086 - Device 8c08 - bus 0 - devfn fd
Vendor 8086 - Device 8c24 - bus 0 - devfn fe
Vendor 8086 - Device 10d3 - bus 1 - devfn 0
Vendor 104c - Device 8240 - bus 2 - devfn 0
Vendor 8086 - Device 1533 - bus 4 - devfn 0
Find device 0x1533 - status 0x86
No devices found
loc_e1000 failed
(root)//185/root>
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/12/2013 2:59 PM
post107495
|
Re: Net.e1000 with i210 and i217
I¹ve added some more debug, so please run this one as before and let me
have the output.
On 2013/12/12, 9:23 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:
>I used the previously send driver and got following:
>
>(root)//185/root>./Net.e1000 -d153c -I1 -l2 -vvv
>
>Net.e1000: proc_fun = e0:0a69
>Net.e1000: vidbuf_inuse = e8:4bf0
>Find device 0x153c - status 0x86
>No devices found
>loc_e1000 failed
>(root)//185/root>cksum ./Net.e1000
>3195832594 302571 ./Net.e1000
>(root)//185/root>
>
>
>(root)//185/root>./Net.e1000 -d1533 -I1 -l2 -v
>...
>Vendor 8086 - Device c08 - bus 0 - devfn 0
>Vendor 8086 - Device c01 - bus 0 - devfn 8
>Vendor 8086 - Device 41a - bus 0 - devfn 10
>Vendor 8086 - Device c0c - bus 0 - devfn 18
>Vendor 8086 - Device 8c31 - bus 0 - devfn a0
>Vendor 8086 - Device 8c3a - bus 0 - devfn b0
>Vendor 8086 - Device 153a - bus 0 - devfn c8
>Vendor 8086 - Device 8c2d - bus 0 - devfn d0
>Vendor 8086 - Device 8c20 - bus 0 - devfn d8
>Vendor 8086 - Device 8c12 - bus 0 - devfn e0
>Vendor 8086 - Device 8c16 - bus 0 - devfn e3
>Vendor 8086 - Device 8c26 - bus 0 - devfn e8
>Vendor 8086 - Device 8c56 - bus 0 - devfn f8
>Vendor 8086 - Device 8c00 - bus 0 - devfn fa
>Vendor 8086 - Device 8c22 - bus 0 - devfn fb
>Vendor 8086 - Device 8c08 - bus 0 - devfn fd
>Vendor 8086 - Device 8c24 - bus 0 - devfn fe
>Vendor 8086 - Device 10d3 - bus 1 - devfn 0
>Vendor 104c - Device 8240 - bus 2 - devfn 0
>Vendor 8086 - Device 1533 - bus 4 - devfn 0
>Find device 0x1533 - status 0x86
>No devices found
>loc_e1000 failed
>(root)//185/root>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107469
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/13/2013 4:03 AM
post107523
|
Re: Net.e1000 with i210 and i217
I tested the new Net.e1000 and got the following:
(Sorry, in my last post there was the address 0x153c used but it must be 0x153a)
(root)//185/root>cksum ./Net.e1000
3603596395 302649 ./Net.e1000
(root)//185/root>./Net.e1000 -d1533 -I1 -l2 -v
..
vend 8086 - devc 8c16 - bus 0 - devfn e3
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 8c26 - bus 0 - devfn e8
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 8c56 - bus 0 - devfn f8
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 8c00 - bus 0 - devfn fa
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 8c22 - bus 0 - devfn fb
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 8c08 - bus 0 - devfn fd
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 8c24 - bus 0 - devfn fe
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 10d3 - bus 1 - devfn 0
vendor 8086 - device 1533 - idx 0 - index 1
vend 104c - devc 8240 - bus 2 - devfn 0
vendor 8086 - device 1533 - idx 0 - index 1
vend 8086 - devc 1533 - bus 4 - devfn 0
vendor 8086 - device 1533 - idx 0 - index 1
Find device 0x1533 - status 0x86
No devices found
loc_e1000 failed
(root)//185/root>
(root)//185/root>./Net.e1000 -d153a -I1 -l2 -v
...
vend 8086 - devc 8c16 - bus 0 - devfn e3
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 8c26 - bus 0 - devfn e8
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 8c56 - bus 0 - devfn f8
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 8c00 - bus 0 - devfn fa
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 8c22 - bus 0 - devfn fb
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 8c08 - bus 0 - devfn fd
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 8c24 - bus 0 - devfn fe
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 10d3 - bus 1 - devfn 0
vendor 8086 - device 153a - idx 1 - index 1
vend 104c - devc 8240 - bus 2 - devfn 0
vendor 8086 - device 153a - idx 1 - index 1
vend 8086 - devc 1533 - bus 4 - devfn 0
vendor 8086 - device 153a - idx 1 - index 1
Find device 0x153a - status 0x86
No devices found
loc_e1000 failed
(root)//185/root>
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/13/2013 8:13 AM
post107525
|
Re: Net.e1000 with i210 and i217
Why are you using ³-I1²? That is for the second device of the same device
ID. You should just use ³-d1533².
On 2013/12/13, 4:03 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:
>I tested the new Net.e1000 and got the following:
>(Sorry, in my last post there was the address 0x153c used but it must be
>0x153a)
>
>(root)//185/root>cksum ./Net.e1000
>3603596395 302649 ./Net.e1000
>
>(root)//185/root>./Net.e1000 -d1533 -I1 -l2 -v
>..
>vend 8086 - devc 8c16 - bus 0 - devfn e3
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 8c26 - bus 0 - devfn e8
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 8c56 - bus 0 - devfn f8
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 8c00 - bus 0 - devfn fa
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 8c22 - bus 0 - devfn fb
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 8c08 - bus 0 - devfn fd
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 8c24 - bus 0 - devfn fe
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 10d3 - bus 1 - devfn 0
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 104c - devc 8240 - bus 2 - devfn 0
>vendor 8086 - device 1533 - idx 0 - index 1
>vend 8086 - devc 1533 - bus 4 - devfn 0
>vendor 8086 - device 1533 - idx 0 - index 1
>Find device 0x1533 - status 0x86
>No devices found
>loc_e1000 failed
>(root)//185/root>
>
>
>(root)//185/root>./Net.e1000 -d153a -I1 -l2 -v
>...
>vend 8086 - devc 8c16 - bus 0 - devfn e3
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 8c26 - bus 0 - devfn e8
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 8c56 - bus 0 - devfn f8
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 8c00 - bus 0 - devfn fa
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 8c22 - bus 0 - devfn fb
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 8c08 - bus 0 - devfn fd
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 8c24 - bus 0 - devfn fe
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 10d3 - bus 1 - devfn 0
>vendor 8086 - device 153a - idx 1 - index 1
>vend 104c - devc 8240 - bus 2 - devfn 0
>vendor 8086 - device 153a - idx 1 - index 1
>vend 8086 - devc 1533 - bus 4 - devfn 0
>vendor 8086 - device 153a - idx 1 - index 1
>Find device 0x153a - status 0x86
>No devices found
>loc_e1000 failed
>(root)//185/root>
>
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107523
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/13/2013 9:54 AM
post107534
|
Re: Net.e1000 with i210 and i217
Because I'm, stupid :(
That was my fault. I had to use the "-I" flag everytime I was using the same network card type twice.
Now the Net.e1000 -d1533 -l2 works. I get the MAC for "netmap" and
For the device "153a" i still have no success even if this device ID is in the Net.e1000. I searched for "1533" using
spatch and found there also the "153a".
If I use the "Net.e1000 -p5060 -i5 -l3 " I receive the MAC for my local netmap but the device itselves doesn'r lokk OK.
Using netinfo -l3 I see no link or speed info.
The "Net.e1000 -d1533 -l2" will start sufficently and I receive a MAC for my local netmap but there is no incoming
traffic I can see in "netinfo -L2". Only outgoing packet number is increasing. And there are several other nodes on the
switch generating ethernet broadcast traffic.
Thanks a lot a have a nice WE!!!!
(root)//185/root>Net.e1000 -d153a -l3 -vvv
Net.e1000: proc_fun = e0:0a69
Net.e1000: vidbuf_inuse = e8:4bf0
e1000_set_mac_type
find_mac_type failed
loc_e1000 failed
(root)//185/root>
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/13/2013 10:26 AM
post107541
|
Re: Net.e1000 with i210 and i217
Please can you post the output from the debug driver for the 0x153a device?
On 2013/12/13, 9:54 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:
>Because I'm, stupid :(
>That was my fault. I had to use the "-I" flag everytime I was using the
>same network card type twice.
>
>Now the Net.e1000 -d1533 -l2 works. I get the MAC for "netmap" and
>
>For the device "153a" i still have no success even if this device ID is
>in the Net.e1000. I searched for "1533" using spatch and found there also
>the "153a".
>If I use the "Net.e1000 -p5060 -i5 -l3 " I receive the MAC for my local
>netmap but the device itselves doesn'r lokk OK. Using netinfo -l3 I see
>no link or speed info.
>The "Net.e1000 -d1533 -l2" will start sufficently and I receive a MAC for
>my local netmap but there is no incoming traffic I can see in "netinfo
>-L2". Only outgoing packet number is increasing. And there are several
>other nodes on the switch generating ethernet broadcast traffic.
>
>Thanks a lot a have a nice WE!!!!
>
>(root)//185/root>Net.e1000 -d153a -l3 -vvv
>Net.e1000: proc_fun = e0:0a69
>Net.e1000: vidbuf_inuse = e8:4bf0
>e1000_set_mac_type
>find_mac_type failed
>loc_e1000 failed
>(root)//185/root>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107534
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/16/2013 7:19 AM
post107575
|
Re: Net.e1000 with i210 and i217
The Device "1533" is now working properly!
(root)//185/root>/root/Net.e1000 -d153a -l2
vend 8086 - devc c08 - bus 0 - devfn 0
vendor 8086 - device 153a - idx 0 - index 0
vend 8086 - devc c01 - bus 0 - devfn 8
vendor 8086 - device 153a - idx 0 - index 0
vend 8086 - devc 41a - bus 0 - devfn 10
vendor 8086 - device 153a - idx 0 - index 0
vend 8086 - devc c0c - bus 0 - devfn 18
vendor 8086 - device 153a - idx 0 - index 0
vend 8086 - devc 8c31 - bus 0 - devfn a0
vendor 8086 - device 153a - idx 0 - index 0
vend 8086 - devc 8c3a - bus 0 - devfn b0
vendor 8086 - device 153a - idx 0 - index 0
vend 8086 - devc 153a - bus 0 - devfn c8
vendor 8086 - device 153a - idx 0 - index 0
Find device 0x153a - status 0x0
Read status 0x0
setup_init_funcs failed
Net.e1000: INITIALIZATION ERROR 4
net_reg failed
(root)//185/root>
(root)//185/root>/root/Net.e1000 -d153a -l2 -v
...
vend 8086 - devc 153a - bus 0 - devfn c8
vendor 8086 - device 153a - idx 0 - index 0
Find device 0x153a - status 0x0
Read status 0x0
Device 153a - Revision 4
reading PHY page 0 (or 0x0 shifted) reg 0x2
reading PHY page 0 (or 0x0 shifted) reg 0x3
EEPROM not present
PHY Initialization Error
setup_init_funcs failed
Net.e1000: INITIALIZATION ERROR 4
net_reg failed
(root)//185/root>
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/16/2013 8:54 AM
post107576
|
Re: Net.e1000 with i210 and i217
Does the QNX 6.5 driver work with the 0x153a device? If so, I¹ll have to
debug the QNX4 driver further.
On 2013/12/16, 7:19 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:
>The Device "1533" is now working properly!
>
>(root)//185/root>/root/Net.e1000 -d153a -l2
>vend 8086 - devc c08 - bus 0 - devfn 0
>vendor 8086 - device 153a - idx 0 - index 0
>vend 8086 - devc c01 - bus 0 - devfn 8
>vendor 8086 - device 153a - idx 0 - index 0
>vend 8086 - devc 41a - bus 0 - devfn 10
>vendor 8086 - device 153a - idx 0 - index 0
>vend 8086 - devc c0c - bus 0 - devfn 18
>vendor 8086 - device 153a - idx 0 - index 0
>vend 8086 - devc 8c31 - bus 0 - devfn a0
>vendor 8086 - device 153a - idx 0 - index 0
>vend 8086 - devc 8c3a - bus 0 - devfn b0
>vendor 8086 - device 153a - idx 0 - index 0
>vend 8086 - devc 153a - bus 0 - devfn c8
>vendor 8086 - device 153a - idx 0 - index 0
>Find device 0x153a - status 0x0
>Read status 0x0
>setup_init_funcs failed
>Net.e1000: INITIALIZATION ERROR 4
>net_reg failed
>(root)//185/root>
>
>
>(root)//185/root>/root/Net.e1000 -d153a -l2 -v
>...
>vend 8086 - devc 153a - bus 0 - devfn c8
>vendor 8086 - device 153a - idx 0 - index 0
>Find device 0x153a - status 0x0
>Read status 0x0
>Device 153a - Revision 4
>reading PHY page 0 (or 0x0 shifted) reg 0x2
>reading PHY page 0 (or 0x0 shifted) reg 0x3
>EEPROM not present
>
>PHY Initialization Error
>
>setup_init_funcs failed
>Net.e1000: INITIALIZATION ERROR 4
>net_reg failed
>(root)//185/root>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107575
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/16/2013 10:37 AM
post107581
|
Re: Net.e1000 with i210 and i217
I havent checked it with QNX6.
I will do so tomorrow.
Thanks a lot!!
|
|
|
|
|
|
Klaus Pantleon(deleted)
|
Re: Net.e1000 with i210 and i217
|
|
Klaus Pantleon(deleted)
12/17/2013 9:58 AM
post107602
|
Re: Net.e1000 with i210 and i217
I have no QNX6 running on that machine and one network card is working properly (0x10d3).
But with the others I have problems. How I must start the aditional drivers?
I used
io-pkt -d e1000 did=0x1533
but after entering that command the nicinfo will not show any info any more.
Sorry but I'm only familiar wirh QNX4.
# cksum /lib/dll/devnp-e1000.so
1938313566 276366 /lib/dll/devnp-e1000.so
# ls -l /lib/dll/devnp-e1000.so
-rwxr-xr-x 1 root root 276366 Jun 20 2012 /lib/dll/devnp-e1000.so
|
|
|
|
|
|
Hugh Brown
|
Re: Net.e1000 with i210 and i217
|
|
Hugh Brown
12/17/2013 10:05 AM
post107603
|
Re: Net.e1000 with i210 and i217
Please run the attached devnp-e1000.so after copying it to /lib/dll. Just
run ³io-pkt-v4 -de1000². If you run ³ifconfig², you should see three
interfaces (wm0, wm1 & wm2) if all the devices are working properly. If
not, please run ³sloginfo² and send me the output.
On 2013/12/17, 9:58 AM, "Klaus Pantleon" <community-noreply@qnx.com> wrote:
>I have no QNX6 running on that machine and one network card is working
>properly (0x10d3).
>But with the others I have problems. How I must start the aditional
>drivers?
>I used
>io-pkt -d e1000 did=0x1533
>but after entering that command the nicinfo will not show any info any
>more.
>Sorry but I'm only familiar wirh QNX4.
>
># cksum /lib/dll/devnp-e1000.so
>1938313566 276366 /lib/dll/devnp-e1000.so
># ls -l /lib/dll/devnp-e1000.so
>-rwxr-xr-x 1 root root 276366 Jun 20 2012
>/lib/dll/devnp-e1000.so
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post107602
>To cancel your subscription to this discussion, please e-mail
>general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
