|
Mohammad Dadashzadeh(deleted)
|
QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/07/2009 10:49 AM
post35468
|
QNX does not detect the third network card
Hi all,
I added a new network card which is "Intel 82572EI_COPPER 0x107D devnp-e1000.so ARM, MIPS, PPC, SH4, X86
driver support for Intel gigabit " to my target PC (x86) which has already one built in network card and one intel PRO
1000 GT network card.
Unfortunately QNX does not detect the new network card and I see just two devices in TCP/IP configuration. what should I
do to solve this problem?
Thanks,
Mohammad
|
|
|
|
|
|
Hugh Brown
|
RE: QNX does not detect the third network card
|
|
Hugh Brown
08/07/2009 10:55 AM
post35470
|
RE: QNX does not detect the third network card
What version of the O/S are you running? The devnp-* drivers only work
with io-pkt.
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Friday, August 07, 2009 10:49 AM
To: drivers-networking
Subject: QNX does not detect the third network card
Hi all,
I added a new network card which is "Intel 82572EI_COPPER
0x107D devnp-e1000.so ARM, MIPS, PPC, SH4, X86
driver support for Intel gigabit " to my target PC (x86) which has
already one built in network card and one intel PRO 1000 GT network
card.
Unfortunately QNX does not detect the new network card and I see just
two devices in TCP/IP configuration. what should I do to solve this
problem?
Thanks,
Mohammad
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post35468
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/07/2009 10:57 AM
post35471
|
Re: RE: QNX does not detect the third network card
QNX 6.4.1 and io-pkt-v4-hc
|
|
|
|
|
|
Hugh Brown
|
RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/07/2009 11:02 AM
post35472
|
RE: RE: QNX does not detect the third network card
If you do the following, does the driver work?
slay io-pkt-v4-hc
io-pkt-v4-hc -de1000
nicinfo
Does nicinfo show a device or are there any error messages when you
start io-pkt?
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Friday, August 07, 2009 10:57 AM
To: drivers-networking
Subject: Re: RE: QNX does not detect the third network card
QNX 6.4.1 and io-pkt-v4-hc
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post35471
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/07/2009 11:07 AM
post35474
|
Re: RE: RE: QNX does not detect the third network card
I did it, no error. but it does not recognize any network card anymore.
Regards,
Mohammad
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/07/2009 11:12 AM
post35475
|
RE: RE: RE: QNX does not detect the third network card
Please do the following:
sloginfo -c
slay io-pkt-v4-hc
io-pkt-v4-hc -de1000 verbose
Please can you post the output from 'pci -v' as well as the output from
'sloginfo'.
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Friday, August 07, 2009 11:08 AM
To: drivers-networking
Subject: Re: RE: RE: QNX does not detect the third network card
I did it, no error. but it does not recognize any network card anymore.
Regards,
Mohammad
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post35474
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/07/2009 11:33 AM
post35479
|
Re: RE: RE: RE: QNX does not detect the third network card
Sloginfo -c results
Time Sev Major Minor Args
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x5e)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x54)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:26:23 2 19 1500 devb-ahci 1.00A (Oct 20 2008 23:23:51)
Aug 07 11:26:23 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver 6040001
Aug 07 11:26:23 2 5 0 xpt_configure: ahci SIM attach failure
Aug 07 11:26:23 2 19 0 devb-eide 1.00A (Oct 20 2008 23:27:28)
Aug 07 11:26:23 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver 6040001
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB vid 8086, did 266f, class 1018a rev 3,
busno 0, dfunc f9
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr 1f0, cntl_addr 3f4, irq e, chnl 0, udma 5, m
dma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0
Aug 07 11:26:23 2 19 0 eide_identify: chk 4 cmd ec, tid 0, status 51, astatus 51, error 4
Aug 07 11:26:23 2 19 0 eide_display_devices: mdl HL-DT-ST DVDRAM GSA-4163B sn K3151CI1252 fw A102 t
id 0, cable 40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 0
Aug 07 11:26:23 2 19 0 eide_init_devices: HL-DT-ST DVDRAM GSA-4163B path 0, tid 0, udma 2, mdma 2,
sdma -1, pio 4, mblk 0
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB vid 8086, did 266f, class 1018a rev 3,
busno 0, dfunc f9
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr 170, cntl_addr 374, irq f, chnl 1, udma 5, m
dma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB/W SATA vid 8086, did 2651, class 1018f
rev 3, busno 0, dfunc fa
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr e800, cntl_addr e400, irq a, chnl 0, udma 5,
mdma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0
Aug 07 11:26:23 2 19 0 eide_parse_identify: IDENTIFY DRIVE CMD cksum failure 192
Aug 07 11:26:23 2 19 0 eide_display_devices: mdl WDC WD1600JD-22HBB0 sn WD-WCAL9266037 fw 08.02D08
tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 16
Aug 07 11:26:23 2 19 0 eide_init_devices: WDC WD1600JD-22HBB0 path 1, tid 0, udma 5, mdma 2, sdma -
1, pio 4, mblk 16
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB/W SATA vid 8086, did 2651, class 1018f
rev 3, busno 0, dfunc fa
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr e000, cntl_addr dc00, irq a, chnl 1, udma 5,
mdma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0
Aug 07 11:26:23 2 19 0 eide_parse_identify: IDENTIFY DRIVE CMD cksum failure 192
Aug 07 11:26:23 2 19 0 eide_display_devices: mdl WDC WD1600JD-22HBB0 sn WD-WCAL9266037 fw 08.02D08
tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 16
Aug 07 11:26:23 2 19 0 eide_init_devices: WDC WD1600JD-22HBB0...
View Full Message
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/07/2009 11:40 AM
post35482
|
RE: RE: RE: RE: QNX does not detect the third network card
I don't want the sloginfo -c results. I want you to do the following:
slay io-pkt-v4-hc
io-pkt-v4-hc -de1000 verbose
sloginfo > file
Post the output 'file'.
Thanks.
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Friday, August 07, 2009 11:33 AM
To: drivers-networking
Subject: Re: RE: RE: RE: QNX does not detect the third network card
Sloginfo -c results
Time Sev Major Minor Args
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x5e)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x54)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:26:22 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:26:23 2 19 1500 devb-ahci 1.00A (Oct 20 2008 23:23:51)
Aug 07 11:26:23 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver
6040001
Aug 07 11:26:23 2 5 0 xpt_configure: ahci SIM attach failure
Aug 07 11:26:23 2 19 0 devb-eide 1.00A (Oct 20 2008 23:27:28)
Aug 07 11:26:23 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver
6040001
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB
vid 8086, did 266f, class 1018a rev 3,
busno 0, dfunc f9
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr 3f4, irq e, chnl 0, udma 5, m
dma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0
status 50, error 0
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 1
status 0, error 0
Aug 07 11:26:23 2 19 0 eide_identify: chk 4 cmd ec, tid 0,
status 51, astatus 51, error 4
Aug 07 11:26:23 2 19 0 eide_display_devices: mdl HL-DT-ST
DVDRAM GSA-4163B sn K3151CI1252 fw A102 t
id 0, cable 40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max sdma
-1, cur sdma -1, pio 4, mblk 0
Aug 07 11:26:23 2 19 0 eide_init_devices: HL-DT-ST DVDRAM
GSA-4163B path 0, tid 0, udma 2, mdma 2,
sdma -1, pio 4, mblk 0
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB
vid 8086, did 266f, class 1018a rev 3,
busno 0, dfunc f9
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr 374, irq f, chnl 1, udma 5, m
dma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0
status 7f, error 7f
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 1
status 7f, error 7f
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB/W
SATA vid 8086, did 2651, class 1018f
rev 3, busno 0, dfunc fa
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr e800,
cntl_addr e400, irq a, chnl 0, udma 5,
mdma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0
status 50, error 0
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 1
status 0, error 0
Aug 07 11:26:23 2 19 0 eide_parse_identify: IDENTIFY DRIVE
CMD cksum failure 192
Aug 07 11:26:23 2 19 0 eide_display_devices: mdl WDC
WD1600JD-22HBB0 sn WD-WCAL9266037 fw 08.02D08
tid 0, cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max
sdma -1, cur sdma -1, pio 4, mblk 16
Aug 07 11:26:23 2 19 0 eide_init_devices: WDC WD1600JD-22HBB0
path 1, tid 0, udma 5, mdma 2, sdma -
1, pio 4, mblk 16
Aug 07 11:26:23 2 19 0 eide_identify_devices: Intel 82801FB/W
SATA vid 8086, did 2651, class 1018f
rev 3, busno 0, dfunc fa
Aug 07 11:26:23 2 19 0 eide_identify_devices: cmd_addr e000,
cntl_addr dc00, irq a, chnl 1, udma 5,
mdma 2, sdma 0, pio 4
Aug 07 11:26:23 2 19 0 eide_identify_devices: probing dev 0
status 50, error 0
Aug 07 11:26:23 2 19 0...
View Full Message
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/07/2009 12:02 PM
post35488
|
Re: RE: RE: RE: RE: QNX does not detect the third network card
I figure out there is no devnp-e1000.so in x86\lib\dll so I copied from Momentics machine to target machine after that I
run
slay io-pkt-v4-hc
io-pkt-v4-hc -de1000 verbose
sloginfo > file
and below is the result. Now my target machine recognizes new network card but it removed the built in network card. I
guess there is a limitation of two network cards somewhere?
Thanks
Time Sev Major Minor Args
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x5e)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x54)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:30 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:30 2 19 1500 devb-ahci 1.00A (Oct 20 2008 23:23:51)
Aug 07 11:55:30 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver 6040001
Aug 07 11:55:30 2 5 0 xpt_configure: ahci SIM attach failure
Aug 07 11:55:30 2 19 0 devb-eide 1.00A (Oct 20 2008 23:27:28)
Aug 07 11:55:30 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver 6040001
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel 82801FB vid 8086, did 266f, class 1018a rev 3, busno 0,
dfunc f9
Aug 07 11:55:30 2 19 0 eide_identify_devices: cmd_addr 1f0, cntl_addr 3f4, irq e, chnl 0, udma 5, mdma 2, sdma
0, pio 4
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0
Aug 07 11:55:30 2 19 0 eide_identify: chk 4 cmd ec, tid 0, status 51, astatus 51, error 4
Aug 07 11:55:30 2 19 0 eide_display_devices: mdl HL-DT-ST DVDRAM GSA-4163B sn K3151CI1252 fw A102 tid 0, cable
40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 0
Aug 07 11:55:30 2 19 0 eide_init_devices: HL-DT-ST DVDRAM GSA-4163B path 0, tid 0, udma 2, mdma 2, sdma -1,
pio 4, mblk 0
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel 82801FB vid 8086, did 266f, class 1018a rev 3, busno 0,
dfunc f9
Aug 07 11:55:30 2 19 0 eide_identify_devices: cmd_addr 170, cntl_addr 374, irq f, chnl 1, udma 5, mdma 2, sdma
0, pio 4
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 0 status 7f, error 7f
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 1 status 7f, error 7f
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel 82801FB/W SATA vid 8086, did 2651, class 1018f rev 3,
busno 0, dfunc fa
Aug 07 11:55:30 2 19 0 eide_identify_devices: cmd_addr e800, cntl_addr e400, irq a, chnl 0, udma 5, mdma 2,
sdma 0, pio 4
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 0 status 50, error 0
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 1 status 0, error 0
Aug 07 11:55:30 2 19 0 eide_parse_identify: IDENTIFY DRIVE CMD cksum failure 192
Aug 07 11:55:30 2 19 0 eide_display_devices: mdl WDC WD1600JD-22HBB0 sn WD-WCAL9266037 fw 08.02D08 tid 0,
cable 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 16
Aug 07 11:55:30 2 19 0 eide_init_devices: WDC WD1600JD-22HBB0 path 1, tid 0, udma 5, mdma 2, sdma -1, pio 4,
mblk 16
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel 82801FB/W SATA vid 8086, did 2651, class 1018f rev 3,
busno 0, dfunc fa
Aug 07 11:55:30 2 19 0 eide_identify_devices: cmd_addr e000, cntl_addr dc00, irq a, chnl 1, udma 5, mdma 2,
sdma 0, pio 4
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 0 status 7f, error ff
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 1 status 7f, error ff
Aug 07 11:55:30 2 5 ...
View Full Message
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/07/2009 1:01 PM
post35494
|
RE: RE: RE: RE: RE: QNX does not detect the third network card
No, there is no limitation of 2 network cards. If you reboot your
machine, now that you have the driver in /lib/dll, you should see all 3
interfaces.
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Friday, August 07, 2009 12:02 PM
To: drivers-networking
Subject: Re: RE: RE: RE: RE: QNX does not detect the third network card
I figure out there is no devnp-e1000.so in x86\lib\dll so I copied from
Momentics machine to target machine after that I run
slay io-pkt-v4-hc
io-pkt-v4-hc -de1000 verbose
sloginfo > file
and below is the result. Now my target machine recognizes new network
card but it removed the built in network card. I guess there is a
limitation of two network cards somewhere?
Thanks
Time Sev Major Minor Args
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x5e)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x54)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x52)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:29 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:30 2 12 0 ps2 - Device Timeout (0x56)
Aug 07 11:55:30 2 19 1500 devb-ahci 1.00A (Oct 20 2008 23:23:51)
Aug 07 11:55:30 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver
6040001
Aug 07 11:55:30 2 5 0 xpt_configure: ahci SIM attach failure
Aug 07 11:55:30 2 19 0 devb-eide 1.00A (Oct 20 2008 23:27:28)
Aug 07 11:55:30 2 5 0 libcam.so (Oct 20 2008 23:22:34) bver
6040001
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel 82801FB
vid 8086, did 266f, class 1018a rev 3, busno 0, dfunc f9
Aug 07 11:55:30 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr 3f4, irq e, chnl 0, udma 5, mdma 2, sdma 0, pio 4
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 0
status 50, error 0
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 1
status 0, error 0
Aug 07 11:55:30 2 19 0 eide_identify: chk 4 cmd ec, tid 0,
status 51, astatus 51, error 4
Aug 07 11:55:30 2 19 0 eide_display_devices: mdl HL-DT-ST
DVDRAM GSA-4163B sn K3151CI1252 fw A102 tid 0, cable 40, max udma 2, cur
udma 2, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4, mblk 0
Aug 07 11:55:30 2 19 0 eide_init_devices: HL-DT-ST DVDRAM
GSA-4163B path 0, tid 0, udma 2, mdma 2, sdma -1, pio 4, mblk 0
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel 82801FB
vid 8086, did 266f, class 1018a rev 3, busno 0, dfunc f9
Aug 07 11:55:30 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr 374, irq f, chnl 1, udma 5, mdma 2, sdma 0, pio 4
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 0
status 7f, error 7f
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 1
status 7f, error 7f
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel 82801FB/W
SATA vid 8086, did 2651, class 1018f rev 3, busno 0, dfunc fa
Aug 07 11:55:30 2 19 0 eide_identify_devices: cmd_addr e800,
cntl_addr e400, irq a, chnl 0, udma 5, mdma 2, sdma 0, pio 4
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 0
status 50, error 0
Aug 07 11:55:30 2 19 0 eide_identify_devices: probing dev 1
status 0, error 0
Aug 07 11:55:30 2 19 0 eide_parse_identify: IDENTIFY DRIVE
CMD cksum failure 192
Aug 07 11:55:30 2 19 0 eide_display_devices: mdl WDC
WD1600JD-22HBB0 sn WD-WCAL9266037 fw 08.02D08 tid 0, cable 40, max udma
6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -1, pio 4,
mblk 16
Aug 07 11:55:30 2 19 0 eide_init_devices: WDC WD1600JD-22HBB0
path 1, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 16
Aug 07 11:55:30 2 19 0 eide_identify_devices: Intel...
View Full Message
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Andrew Boyd(deleted)
08/07/2009 1:03 PM
post35495
|
RE: RE: RE: RE: RE: QNX does not detect the third network card
> there is no limitation of 2 network cards
I had four i82544 interfaces up yesterday
with a single driver.
--
aboyd
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/10/2009 8:32 AM
post35537
|
Re: RE: RE: RE: RE: RE: QNX does not detect the third network card
I reboot my system. Now it recognizes just the two network cards (Intel Pro 100 and intel Pro 1000 GT) same as before.
It does not recognize the third network card (Intel Pro 1000 PT) which is connected to PCI express slot. if I run below
code, it removes the first network card from the list and adds the third network card to the list. If I reboot the
system I will get back to the default configuration with the first and second network cards.
slay io-pkt-v4-hc
io-pkt-v4-hc -de1000 verbose
Regards,
Mohammad
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/10/2009 8:47 AM
post35540
|
RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
Please look at you /etc/system/enum/devices/net file and see if both of
the device IDs for your gigabit adapters are in the file. If not, you
can copy one of the lines and add the device ID. Then reboot your
system.
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Monday, August 10, 2009 8:32 AM
To: drivers-networking
Subject: Re: RE: RE: RE: RE: RE: QNX does not detect the third network
card
I reboot my system. Now it recognizes just the two network cards (Intel
Pro 100 and intel Pro 1000 GT) same as before. It does not recognize the
third network card (Intel Pro 1000 PT) which is connected to PCI express
slot. if I run below code, it removes the first network card from the
list and adds the third network card to the list. If I reboot the system
I will get back to the default configuration with the first and second
network cards.
slay io-pkt-v4-hc
io-pkt-v4-hc -de1000 verbose
Regards,
Mohammad
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post35537
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/10/2009 9:01 AM
post35542
|
Re: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
Hi Hugh,
Thanks a lot. It solved the problem.
Regards,
Mohammad
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/10/2009 9:23 AM
post35546
|
Re: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
Hi,
QNX recognizes the third network card also I can set the IP address. However, when I ping another PC in the same network
or vise versa , ping does not work. Should I do something else after adding the device ID to the net file and rebooting
. I am sure that I have set the IP address correctly as the other network cards work perfectly.
Regards,
Mohammad
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/10/2009 9:33 AM
post35549
|
RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
Have you configured the network addresses using the Photon network setup
or are you doing it manually? If you are doing it manually, make sure
that you slay dhcp.client and netmanager before configuring the
interfaces.
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Monday, August 10, 2009 9:23 AM
To: drivers-networking
Subject: Re: RE: RE: RE: RE: RE: RE: QNX does not detect the third
network card
Hi,
QNX recognizes the third network card also I can set the IP address.
However, when I ping another PC in the same network or vise versa , ping
does not work. Should I do something else after adding the device ID to
the net file and rebooting. I am sure that I have set the IP address
correctly as the other network cards work perfectly.
Regards,
Mohammad
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post35546
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Andrew Boyd(deleted)
08/10/2009 9:49 AM
post35556
|
RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
>> ping does not work
> configured the network addresses
A simple way to check to see if the driver is
functioning with the nic is with the
# nicinfo -r enX
utility, where X is a small positive integer.
Ensure that for each interface, it has negotiated
to a valid link speed and duplex, and check the
"Packets Received Ok" count - it should be non-zero
on almost any network, which indicates that the nic
interrupt is functioning.
Once you think the hardware and driver are functioning
then you can go on to the protocols.
--
aboyd
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/10/2009 10:04 AM
post35565
|
Re: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
Packet Received is non-zero however packet transmit is zero even though I pinged its IP address from the other computer
in the network. I think this is the reason ping does not work.
Regards,
Mohammad
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/10/2009 10:11 AM
post35571
|
RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
What is the output from 'netstat -in' after the interfaces have been
configured?
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Monday, August 10, 2009 10:04 AM
To: drivers-networking
Subject: Re: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third
network card
Packet Received is non-zero however packet transmit is zero even though
I pinged its IP address from the other computer in the network. I think
this is the reason ping does not work.
Regards,
Mohammad
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post35565
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/10/2009 10:14 AM
post35574
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Colls
lo0 33192 <Link> 18 0 18 0 0
lo0 33192 127/8 127.0.0.1 18 0 18 0 0
fxp0 1500 <Link> 00:11:11:6e:07:2e 1259 0 348 0 0
fxp0 1500 129.100.227/2 129.100.227.188 1259 0 348 0 0
wm0 1500 <Link> 00:15:17:b9:5f:13 584 0 520 0 0
wm0 1500 192.168.1/24 192.168.1.5 584 0 520 0 0
wm1 1500 <Link> 00:1b:21:3b:59:42 75 0 1 0 0
wm1 1500 192.168.1/24 192.168.1.6 75 0 1 0 0
|
|
|
|
|
|
Sean Boudreau(deleted)
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third
network card
|
|
Sean Boudreau(deleted)
08/10/2009 10:18 AM
post35575
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third
network card
On Mon, Aug 10, 2009 at 10:14:24AM -0400, Mohammad Dadashzadeh wrote:
> # netstat -in
> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Colls
> lo0 33192 <Link> 18 0 18 0 0
> lo0 33192 127/8 127.0.0.1 18 0 18 0 0
> fxp0 1500 <Link> 00:11:11:6e:07:2e 1259 0 348 0 0
> fxp0 1500 129.100.227/2 129.100.227.188 1259 0 348 0 0
> wm0 1500 <Link> 00:15:17:b9:5f:13 584 0 520 0 0
> wm0 1500 192.168.1/24 192.168.1.5 584 0 520 0 0
> wm1 1500 <Link> 00:1b:21:3b:59:42 75 0 1 0 0
> wm1 1500 192.168.1/24 192.168.1.6 75 0 1 0 0
>
wm0 and wm1 are on the same subnet. All packets
routed to 192.168.1/24 will go out one or the other
(check your routing table). In your case it seems
to be wm0.
-seanb
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Hugh Brown
08/10/2009 10:18 AM
post35576
|
RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
You have 2 links on the same subnet. You can't do that!
Wm0 and wm1 have the same subnet.
-----Original Message-----
From: Mohammad Dadashzadeh [mailto:community-noreply@qnx.com]
Sent: Monday, August 10, 2009 10:14 AM
To: drivers-networking
Subject: Re: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the
third network card
# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts
Oerrs Colls
lo0 33192 <Link> 18 0 18
0 0
lo0 33192 127/8 127.0.0.1 18 0 18
0 0
fxp0 1500 <Link> 00:11:11:6e:07:2e 1259 0 348
0 0
fxp0 1500 129.100.227/2 129.100.227.188 1259 0 348
0 0
wm0 1500 <Link> 00:15:17:b9:5f:13 584 0 520
0 0
wm0 1500 192.168.1/24 192.168.1.5 584 0 520
0 0
wm1 1500 <Link> 00:1b:21:3b:59:42 75 0 1
0 0
wm1 1500 192.168.1/24 192.168.1.6 75 0 1
0 0
_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post35574
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/10/2009 10:26 AM
post35579
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
Is this the case in QNX since in my windows machine I have two network cards with
the same subnet mask.
Windows IP Configuration
Ethernet adapter Local Area Connection 5:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : uwo.ca
IP Address. . . . . . . . . . . . : 129.100.227.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 129.100.227.1
Thanks,
Mohammad
|
|
|
|
|
|
Sean Boudreau(deleted)
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the
third network card
|
|
Sean Boudreau(deleted)
08/10/2009 10:30 AM
post35581
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the
third network card
On Mon, Aug 10, 2009 at 10:26:43AM -0400, Mohammad Dadashzadeh wrote:
> Is this the case in QNX since in my windows machine I have two network cards with
> the same subnet mask.
>
> Windows IP Configuration
>
>
> Ethernet adapter Local Area Connection 5:
>
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 192.168.1.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : uwo.ca
> IP Address. . . . . . . . . . . . : 129.100.227.15
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 129.100.227.1
>
Those have the same subnet masks but when applied
against the ip addresses they result in different
subnets. On your QNX box they're the same:
On windows:
(192.168.1.3 & 255.255.255.0) = 192.168.1.0
(129.100.227.15 & 255.255.255.0) = 129.100.227.0
On QNX:
(192.168.1.5 & 255.255.255.0) = 192.168.1.0
(192.168.1.6 & 255.255.255.0) = 192.168.1.0
-seanb
|
|
|
|
|
|
Mohammad Dadashzadeh(deleted)
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
|
|
Mohammad Dadashzadeh(deleted)
08/10/2009 10:49 AM
post35584
|
Re: RE: RE: RE: RE: RE: RE: RE: RE: RE: QNX does not detect the third network card
You are right I even checked it in windows, the same problem. I guess I have a conceptual problem. I have a private
network with the ip addresses 192.168.1.1-254 and subnet mask 255.255.255.0. Is it possible to have multiple network
cards in one PC connected to the same network. If I want that I have to set all the network cards IP address in this
range 192.168.1.1-254 and subnet 255.255.255.255. It seems that it is impossible. I am totally confused.
Regards,
Mohammad
|
|
|
|
|
|
