|
Mark Dowdy(deleted)
|
Activating a '2nd' Network Adapter
|
|
Mark Dowdy(deleted)
09/04/2008 9:58 PM
post12895
|
Activating a '2nd' Network Adapter
Our system, running 6.3.0 SP2, has a hard-wired Intel 82546GB dual-port
network adapter. Our application requires the addition of a third
ethernet interface so I added an Intel Pro/1000 GT adapter board. The
Pro/1000 has an Intel 82541PI. The pci command lists the newly added
device (see below, the PCI ID is 0x107c) but io-net doesn't find it
(i.e. /dev/io-net only contains two en's 0 and 1). Not surprisingly,
ifconfig doesn't know about the new adapter either. PCI device ID 0x107c
is in the Intel network adapter section of /etc/system/enum/devices/net
file (I applied patch 214). Any ideas why the ethernet interface on the
new adapter isn't starting? Thanks.
# pci
PCI version = 2.10
Class = Mass Storage (IDE)
Vendor ID = 8086h, Intel Corporation
Device ID = 24d1h, Unknown Unknown
PCI index = 0h
PCI IO Address = 0h enabled
PCI IO Address = 0h enabled
PCI IO Address = 0h enabled
PCI IO Address = 0h enabled
PCI IO Address = 14b0h enabled
PCI Int Pin = INT A
Interrupt line = no connection
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1079h, Unknown Unknown
PCI index = 0h
PCI Mem Address = dd200000h enabled
PCI IO Address = 2000h enabled
PCI Int Pin = INT A
Interrupt line = 10
CPU Interrupt = ah
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1079h, Unknown Unknown
PCI index = 1h
PCI Mem Address = dd220000h enabled
PCI IO Address = 2040h enabled
PCI Int Pin = INT B
Interrupt line = 11
CPU Interrupt = bh
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 107ch, Unknown Unknown
PCI index = 0h
PCI Mem Address = dd320000h enabled
PCI Mem Address = dd300000h enabled
PCI IO Address = 3000h enabled
PCI Int Pin = INT A
Interrupt line = 10
CPU Interrupt = ah
Class = Display (VGA)
Vendor ID = 1002h, ATI Technologies
Device ID = 4752h, Rage XL PCI
PCI index = 0h
PCI Mem Address = de000000h enabled
PCI IO Address = 4000h disabled
PCI Mem Address = dd400000h enabled
PCI Int Pin = INT A
Interrupt line = 10
CPU Interrupt = ah
# ls /dev/io-net
en0 en1 ip0 ip_en
#
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: Activating a '2nd' Network Adapter
|
|
Andrew Boyd(deleted)
09/05/2008 8:29 AM
post12903
|
RE: Activating a '2nd' Network Adapter
Try specifying "did=0x107c" to devn-i82544.so
--
aboyd
|
|
|
|
|
|
Robert Craig
|
RE: Activating a '2nd' Network Adapter
|
|
Robert Craig
09/05/2008 12:27 PM
post12951
|
RE: Activating a '2nd' Network Adapter
From the command line,
slay io-net
sloginfo -c
io-net -di82544 verbose -ptcpip
sloginfo
And send us the output from the last sloginfo.
Just to make sure that the right driver is installed, could you also
send us the output from
use -i /lib/dll/devn-i82544.so
Thanks,
Robert.
-----Original Message-----
From: Mark Dowdy [mailto:community-noreply@qnx.com]
Sent: Thursday, September 04, 2008 9:59 PM
To: general-networking
Subject: Activating a '2nd' Network Adapter
Our system, running 6.3.0 SP2, has a hard-wired Intel 82546GB dual-port
network adapter. Our application requires the addition of a third
ethernet interface so I added an Intel Pro/1000 GT adapter board. The
Pro/1000 has an Intel 82541PI. The pci command lists the newly added
device (see below, the PCI ID is 0x107c) but io-net doesn't find it
(i.e. /dev/io-net only contains two en's 0 and 1). Not surprisingly,
ifconfig doesn't know about the new adapter either. PCI device ID 0x107c
is in the Intel network adapter section of /etc/system/enum/devices/net
file (I applied patch 214). Any ideas why the ethernet interface on the
new adapter isn't starting? Thanks.
# pci
PCI version = 2.10
Class = Mass Storage (IDE)
Vendor ID = 8086h, Intel Corporation
Device ID = 24d1h, Unknown Unknown
PCI index = 0h
PCI IO Address = 0h enabled
PCI IO Address = 0h enabled
PCI IO Address = 0h enabled
PCI IO Address = 0h enabled
PCI IO Address = 14b0h enabled
PCI Int Pin = INT A
Interrupt line = no connection
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1079h, Unknown Unknown
PCI index = 0h
PCI Mem Address = dd200000h enabled
PCI IO Address = 2000h enabled
PCI Int Pin = INT A
Interrupt line = 10
CPU Interrupt = ah
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1079h, Unknown Unknown
PCI index = 1h
PCI Mem Address = dd220000h enabled
PCI IO Address = 2040h enabled
PCI Int Pin = INT B
Interrupt line = 11
CPU Interrupt = bh
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 107ch, Unknown Unknown
PCI index = 0h
PCI Mem Address = dd320000h enabled
PCI Mem Address = dd300000h enabled
PCI IO Address = 3000h enabled
PCI Int Pin = INT A
Interrupt line = 10
CPU Interrupt = ah
Class = Display (VGA)
Vendor ID = 1002h, ATI Technologies
Device ID = 4752h, Rage XL PCI
PCI index = 0h
PCI Mem Address = de000000h enabled
PCI IO Address = 4000h disabled
PCI Mem Address = dd400000h enabled
PCI Int Pin = INT A
Interrupt line = 10
CPU Interrupt = ah
# ls /dev/io-net
en0 en1 ip0 ip_en
#
_______________________________________________
General
http://community.qnx.com/sf/go/post12895
|
|
|
|
|
|
Mark Dowdy(deleted)
|
Re: Activating a '2nd' Network Adapter
|
|
Mark Dowdy(deleted)
09/08/2008 3:47 PM
post13022
|
Re: Activating a '2nd' Network Adapter
# slay io-net
# sloginfo -c
Time Sev Major Minor Args
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086
- Class 1018a - Addr 0 - Size 8
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086
- Class 1018a - Addr 0 - Size 4
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086
- Class 1018a - Addr 0 - Size 8
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086
- Class 1018a - Addr 0 - Size 4
Sep 08 12:34:26 2 19 0 eide_identify_devices: Intel 82801EB SATA vid 8
086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 08 12:34:26 2 19 0 eide_identify_devices: cmd_addr 1f0, cntl_addr
3f4, irq e, chnl 0, udma 5, mdma 2, sdma 0, pio 4
Sep 08 12:34:26 2 19 0 eide_display_devices: ST380817AS tid 0, c
able 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1, cur sdma -
1, pio 4, mblk 16
Sep 08 12:34:26 2 19 0 eide_init_devices: ST380817AS path 0, tid
0, udma 2, mdma 2, sdma -1, pio 4, mblk 16
Sep 08 12:34:26 2 19 0 eide_identify_devices: Intel 82801EB SATA vid 8
086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 08 12:34:26 2 19 0 eide_identify_devices: cmd_addr 170, cntl_addr
374, irq f, chnl 1, udma 5, mdma 2, sdma 0, pio 4
Sep 08 12:34:26 2 19 0 eide_display_devices: CD-224E tid 0, c
able 40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max sdma 2, cur sdma 0,
pio 4, mblk 0
Sep 08 12:34:26 2 19 0 eide_init_devices: CD-224E path 0, tid
0, udma 2, mdma 2, sdma 0, pio 4, mblk 0
Sep 08 12:34:34 5 6 200 Installing /dev/par port 378
Sep 08 12:34:34 5 14 0 tcpip starting
Sep 08 12:34:34 3 14 0 Using pseudo random generator. See "random" op
tion
Sep 08 12:34:37 1 8 0 phfont_init
Sep 08 12:34:37 1 8 0 phfontXX started OK
Sep 08 12:34:38 5 8 0 Process fontsleuth initialized.
Sep 08 12:34:39 1 8 0 phfont_init
Sep 08 12:34:39 1 8 0 phfontXX started OK
Sep 08 12:34:39 6 8 0 VGA primary : bus 0x9 dev/func 0x8
Sep 08 12:34:39 6 8 0 Found 1 PCI/AGP display devices
Sep 08 12:34:39 6 8 0 pci_init: found PCI device 1002:4752
Sep 08 12:34:39 5 8 0 Attached /dev/io-graphics/rage0, id = 0
Sep 08 12:34:42 5 9 0 Start: /usr/photon/bin/devi-hirun kbd fd -d/dev
/kbd ps2 mousedev
# io-net -di82544 verbose -ptcpip
# sloginfo
Time Sev Major Minor Args
Sep 08 12:42:51 5 10 0 devn-i82544: Bus width is 64 bits
Sep 08 12:42:51 5 10 0 devn-i82544: *may* be running at 66Mhz
Sep 08 12:42:51 5 10 0 devn-i82544: PCI-X bus speed estimation is 100-
133
Sep 08 12:42:51 5 10 0 devn-i82544: found internal Copper PHY at addre
ss 1
Sep 08 12:42:51 5 10 0 INTEL 82544 Gigabit (Copper)
Sep 08 12:42:51 5 10 0 Vendor .............. 0x8086
Sep 08 12:42:51 5 10 0 Device .............. 0x1079
Sep 08 12:42:51 5 10 0 Revision ............ 0x0
Sep 08 12:42:51 5 10 0 Memory base ......... 0xdd200000
Sep 08 12:42:51 5 10 0 Interrupt ........... 0xa
Sep 08 12:42:51 5 10 0 MAC address ......... 003048 2de0c0
Sep 08 12:42:51 5 10 0 devn-i82544: Bus width is 64 bits
Sep 08 12:42:51 5 10 0 devn-i82544: *may* be running at 66Mhz
Sep 08 12:42:51 5 10 0 devn-i82544: PCI-X bus speed estimation is 100-
133
Sep 08 12:42:51 5 10 0 devn-i82544: found internal Copper PHY at addre
ss 1
Sep 08 12:42:51 5 10 0 INTEL 82544 Gigabit (Copper)
Sep 08 12:42:51 5 10 0 Vendor .............. 0x8086
Sep 08 12:42:51 5 10 0 Device .............. 0x1079
Sep 08 12:42:51 5 10 0 Revision ............ 0x0
Sep 08 12:42:51 5 10 0 Memory base ............
View Full Message
|
|
|
|
|
|
Robert Craig
|
RE: Activating a '2nd' Network Adapter
|
|
Robert Craig
09/08/2008 4:00 PM
post13023
|
RE: Activating a '2nd' Network Adapter
So it's definitely not finding the third interface.
The two 1079's show up but not the third one.
The reason why you lose connectivity is because there's no IP address
assigned to the interfaces after re-starting io-net. You'd need to run
dhcp.client -i en0
dhcp.client -i en1
to get the IP addresses assigned.
Another thing to try...
Right after boot up with the two interfaces showing up:
mount -Tio-net -o did=0x107c,vid=0x8086 /lib/dll/devn-i82544.so
and see if a third interface appears.
Robert.
-----Original Message-----
From: Mark Dowdy [mailto:community-noreply@qnx.com]
Sent: Monday, September 08, 2008 3:48 PM
To: general-networking
Subject: Re: Activating a '2nd' Network Adapter
# slay io-net
# sloginfo -c
Time Sev Major Minor Args
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 8
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 4
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 8
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 4
Sep 08 12:34:26 2 19 0 eide_identify_devices: Intel 82801EB
SATA vid 8
086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 08 12:34:26 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr
3f4, irq e, chnl 0, udma 5, mdma 2, sdma 0, pio 4
Sep 08 12:34:26 2 19 0 eide_display_devices: ST380817AS
tid 0, c
able 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1,
cur sdma -
1, pio 4, mblk 16
Sep 08 12:34:26 2 19 0 eide_init_devices: ST380817AS
path 0, tid
0, udma 2, mdma 2, sdma -1, pio 4, mblk 16
Sep 08 12:34:26 2 19 0 eide_identify_devices: Intel 82801EB
SATA vid 8
086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 08 12:34:26 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr
374, irq f, chnl 1, udma 5, mdma 2, sdma 0, pio 4
Sep 08 12:34:26 2 19 0 eide_display_devices: CD-224E
tid 0, c
able 40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max sdma 2, cur
sdma 0,
pio 4, mblk 0
Sep 08 12:34:26 2 19 0 eide_init_devices: CD-224E
path 0, tid
0, udma 2, mdma 2, sdma 0, pio 4, mblk 0
Sep 08 12:34:34 5 6 200 Installing /dev/par port 378
Sep 08 12:34:34 5 14 0 tcpip starting
Sep 08 12:34:34 3 14 0 Using pseudo random generator. See
"random" op
tion
Sep 08 12:34:37 1 8 0 phfont_init
Sep 08 12:34:37 1 8 0 phfontXX started OK
Sep 08 12:34:38 5 8 0 Process fontsleuth initialized.
Sep 08 12:34:39 1 8 0 phfont_init
Sep 08 12:34:39 1 8 0 phfontXX started OK
Sep 08 12:34:39 6 8 0 VGA primary : bus 0x9 dev/func 0x8
Sep 08 12:34:39 6 8 0 Found 1 PCI/AGP display devices
Sep 08 12:34:39 6 8 0 pci_init: found PCI device 1002:4752
Sep 08 12:34:39 5 8 0 Attached /dev/io-graphics/rage0, id = 0
Sep 08 12:34:42 5 9 0 Start: /usr/photon/bin/devi-hirun kbd
fd -d/dev
/kbd ps2 mousedev
# io-net -di82544 verbose -ptcpip
# sloginfo
Time Sev Major Minor Args
Sep 08 12:42:51 5 10 0 devn-i82544: Bus width is 64 bits
Sep 08 12:42:51 5 10 0 devn-i82544: *may* be running at 66Mhz
Sep 08 12:42:51 5 10 0 devn-i82544: PCI-X bus speed estimation
is 100-
133
Sep 08 12:42:51 5 10 0 devn-i82544: found internal Copper PHY
at addre
ss 1
Sep 08 12:42:51 5 10 0 INTEL 82544 Gigabit (Copper)
Sep 08 12:42:51 5 10 0 Vendor .............. 0x8086
Sep 08 12:42:51 5 10 0 Device .............. 0x1079
Sep 08 12:42:51 5 10 0 Revision ............ 0x0
Sep 08 12:42:51 5 10 0 Memory base ......... 0xdd200000
Sep 08 12:42:51 5 ...
View Full Message
|
|
|
|
|
|
Mark Dowdy(deleted)
|
Re: Activating a '2nd' Network Adapter
|
|
Mark Dowdy(deleted)
09/08/2008 5:16 PM
post13026
|
Re: Activating a '2nd' Network Adapter
> Another thing to try...
>
> Right after boot up with the two interfaces showing up:
>
> mount -Tio-net -o did=0x107c,vid=0x8086 /lib/dll/devn-i82544.so
>
> and see if a third interface appears.
Indeed it does.
Isn't this what the following lines from /etc/systems/enum/devices/net are supposed to do?
<snip>
device(pci, ven=$(PCI_VEND_INTEL), dev=107c) # Intel 82541PI Gigabit
<snip>
mount(-Tio-net "-opci=$(index),vid=0x$(ven),did=0x$(dev)" /lib/dll/devn-i82544.so, "/dev/io-net/en$(netnum)")
Now that we've established that there is a way to find the third interface, what is the 'correct' way to automatically
start this interface?
Mark
|
|
|
|
|
|
Robert Craig
|
RE: Activating a '2nd' Network Adapter
|
|
Robert Craig
09/08/2008 5:34 PM
post13028
|
RE: Activating a '2nd' Network Adapter
Hi Mark:
Hmmmm... You know, it should work.
How about changing the enumerator file
mount(-Tio-net "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-i82544.so, "/dev/io-net/en$(netnum)")
to add a verbose option "-overbose,pci= (etc)" and then sending us the
output from sloginfo after a reboot. At least it looks like the driver
is capable of picking up on that device now.
Robert.
-----Original Message-----
From: Mark Dowdy [mailto:community-noreply@qnx.com]
Sent: Monday, September 08, 2008 5:17 PM
To: general-networking
Subject: Re: Activating a '2nd' Network Adapter
> Another thing to try...
>
> Right after boot up with the two interfaces showing up:
>
> mount -Tio-net -o did=0x107c,vid=0x8086 /lib/dll/devn-i82544.so
>
> and see if a third interface appears.
Indeed it does.
Isn't this what the following lines from /etc/systems/enum/devices/net
are supposed to do?
<snip>
device(pci, ven=$(PCI_VEND_INTEL), dev=107c) # Intel 82541PI Gigabit
<snip>
mount(-Tio-net "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-i82544.so, "/dev/io-net/en$(netnum)")
Now that we've established that there is a way to find the third
interface, what is the 'correct' way to automatically start this
interface?
Mark
_______________________________________________
General
http://community.qnx.com/sf/go/post13026
|
|
|
|
|
|
Mark Dowdy(deleted)
|
Re: RE: Activating a '2nd' Network Adapter
|
|
Mark Dowdy(deleted)
09/09/2008 1:02 PM
post13075
|
Re: RE: Activating a '2nd' Network Adapter
> Hmmmm... You know, it should work.
> How about changing the enumerator file
>
> mount(-Tio-net "-opci=$(index),vid=0x$(ven),did=0x$(dev)" /lib/dll/devn-i82544.so, "/dev/io-net/en$(netnum)")
>
> to add a verbose option "-overbose,pci= (etc)" and then sending us the
> output from sloginfo after a reboot. At least it looks like the driver
> is capable of picking up on that device now.
Here's the output from sloginfo following the addition of the verbose option. Interestingly, the interface is now
automatically recognized following a reboot.
Time Sev Major Minor Args
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086 - Class 1018a - Addr 0 - Size 8
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086 - Class 1018a - Addr 0 - Size 4
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086 - Class 1018a - Addr 0 - Size 8
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 - Vend 8086 - Class 1018a - Addr 0 - Size 4
Sep 09 09:08:46 2 19 0 eide_identify_devices: Intel 82801EB SATA vid 8086, did 24d1, class 1018a rev 2, busno
0, dfunc fa
Sep 09 09:08:46 2 19 0 eide_identify_devices: cmd_addr 1f0, cntl_addr 3f4, irq e, chnl 0, udma 5, mdma 2, sdma
0, pio 4
Sep 09 09:08:46 2 19 0 eide_display_devices: ST380817AS 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
Sep 09 09:08:46 2 19 0 eide_init_devices: ST380817AS path 0, tid 0, udma 2, mdma 2, sdma -1, pio 4, mblk
16
Sep 09 09:08:46 2 19 0 eide_identify_devices: Intel 82801EB SATA vid 8086, did 24d1, class 1018a rev 2, busno
0, dfunc fa
Sep 09 09:08:46 2 19 0 eide_identify_devices: cmd_addr 170, cntl_addr 374, irq f, chnl 1, udma 5, mdma 2, sdma
0, pio 4
Sep 09 09:08:46 2 19 0 eide_display_devices: CD-224E tid 0, cable 40, max udma 2, cur udma 2, max
mdma 2, cur mdma 0, max sdma 2, cur sdma 0, pio 4, mblk 0
Sep 09 09:08:46 2 19 0 eide_init_devices: CD-224E path 0, tid 0, udma 2, mdma 2, sdma 0, pio 4, mblk
0
Sep 09 09:08:54 5 6 200 Installing /dev/par port 378
Sep 09 09:08:54 5 14 0 tcpip starting
Sep 09 09:08:54 3 14 0 Using pseudo random generator. See "random" option
Sep 09 09:08:57 1 8 0 phfont_init
Sep 09 09:08:57 1 8 0 phfontXX started OK
Sep 09 09:08:58 5 8 0 Process fontsleuth initialized.
Sep 09 09:08:59 1 8 0 phfont_init
Sep 09 09:08:59 1 8 0 phfontXX started OK
Sep 09 09:08:59 6 8 0 VGA primary : bus 0x9 dev/func 0x8
Sep 09 09:08:59 6 8 0 Found 1 PCI/AGP display devices
Sep 09 09:08:59 6 8 0 pci_init: found PCI device 1002:4752
Sep 09 09:08:59 5 8 0 Attached /dev/io-graphics/rage0, id = 0
Sep 09 09:09:02 5 9 0 Start: /usr/photon/bin/devi-hirun kbd fd -d/dev/kbd ps2 mousedev
|
|
|
|
|
|
Robert Craig
|
RE: RE: Activating a '2nd' Network Adapter
|
|
Robert Craig
09/09/2008 1:16 PM
post13082
|
RE: RE: Activating a '2nd' Network Adapter
Very strange. I don't see any output from networking at all as a result
of the verbose option being passed. Can you cut and paste the relevant
lines from the enumerator for us to take a look at?
Glad to hear that things are working, but it would be good to know
why...
Robert.
-----Original Message-----
From: Mark Dowdy [mailto:community-noreply@qnx.com]
Sent: Tuesday, September 09, 2008 1:03 PM
To: general-networking
Subject: Re: RE: Activating a '2nd' Network Adapter
> Hmmmm... You know, it should work.
> How about changing the enumerator file
>
> mount(-Tio-net "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-i82544.so, "/dev/io-net/en$(netnum)")
>
> to add a verbose option "-overbose,pci= (etc)" and then sending us the
> output from sloginfo after a reboot. At least it looks like the
driver
> is capable of picking up on that device now.
Here's the output from sloginfo following the addition of the verbose
option. Interestingly, the interface is now automatically recognized
following a reboot.
Time Sev Major Minor Args
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086 - Class 1018a - Addr 0 - Size 8
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086 - Class 1018a - Addr 0 - Size 4
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086 - Class 1018a - Addr 0 - Size 8
Sep 09 09:08:46 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086 - Class 1018a - Addr 0 - Size 4
Sep 09 09:08:46 2 19 0 eide_identify_devices: Intel 82801EB
SATA vid 8086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 09 09:08:46 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr 3f4, irq e, chnl 0, udma 5, mdma 2, sdma 0, pio 4
Sep 09 09:08:46 2 19 0 eide_display_devices: ST380817AS
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
Sep 09 09:08:46 2 19 0 eide_init_devices: ST380817AS
path 0, tid 0, udma 2, mdma 2, sdma -1, pio 4, mblk 16
Sep 09 09:08:46 2 19 0 eide_identify_devices: Intel 82801EB
SATA vid 8086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 09 09:08:46 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr 374, irq f, chnl 1, udma 5, mdma 2, sdma 0, pio 4
Sep 09 09:08:46 2 19 0 eide_display_devices: CD-224E
tid 0, cable 40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max
sdma 2, cur sdma 0, pio 4, mblk 0
Sep 09 09:08:46 2 19 0 eide_init_devices: CD-224E
path 0, tid 0, udma 2, mdma 2, sdma 0, pio 4, mblk 0
Sep 09 09:08:54 5 6 200 Installing /dev/par port 378
Sep 09 09:08:54 5 14 0 tcpip starting
Sep 09 09:08:54 3 14 0 Using pseudo random generator. See
"random" option
Sep 09 09:08:57 1 8 0 phfont_init
Sep 09 09:08:57 1 8 0 phfontXX started OK
Sep 09 09:08:58 5 8 0 Process fontsleuth initialized.
Sep 09 09:08:59 1 8 0 phfont_init
Sep 09 09:08:59 1 8 0 phfontXX started OK
Sep 09 09:08:59 6 8 0 VGA primary : bus 0x9 dev/func 0x8
Sep 09 09:08:59 6 8 0 Found 1 PCI/AGP display devices
Sep 09 09:08:59 6 8 0 pci_init: found PCI device 1002:4752
Sep 09 09:08:59 5 8 0 Attached /dev/io-graphics/rage0, id = 0
Sep 09 09:09:02 5 9 0 Start: /usr/photon/bin/devi-hirun kbd
fd -d/dev/kbd ps2 mousedev
_______________________________________________
General
http://community.qnx.com/sf/go/post13075
|
|
|
|
|
|
Mark Dowdy(deleted)
|
Re: RE: RE: Activating a '2nd' Network Adapter
|
|
Mark Dowdy(deleted)
09/09/2008 3:01 PM
post13094
|
Re: RE: RE: Activating a '2nd' Network Adapter
Here are the lines for the Intel network adapters
device(pci, ven=$(PCI_VEND_INTEL), dev=1008) # Intel 82544EI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1009) # Intel 82544EI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=100c) # Intel 82544GC Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=100d) # Intel 82544GC Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=100e) # Intel 82540EM Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=100f) # Intel 82545EM Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1010) # Intel 82546EB Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1011) # Intel 82545EM Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1012) # Intel 82546EB Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1013) # Intel 82541EI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1015) # Intel 82540EM Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1016) # Intel 82540EP Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1017) # Intel 82540EP Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1018) # Intel 82541EI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1019) # Intel 82541EI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=101d) # Intel 82546EB Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=101e) # Intel 82540EP Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1026) # Intel 82545GM Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1027) # Intel 82545GM Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1028) # Intel 82545GM Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1075) # Intel 82541GI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1076) # Intel 82541GI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1077) # Intel 82541GI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1078) # Intel 82541ER Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=1079) # Intel 82546GB Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=107a) # Intel 82546GB Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=107b) # Intel 82546GB Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=107c) # Intel 82541PI Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=108a) # Intel 82546EB Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=108b) # Intel 82573V Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=108c) # Intel 82573E Gigabit
device(pci, ven=$(PCI_VEND_INTEL), dev=109a) # Intel 82573L Gigabit
tag(devn)
append(legacy, ",nonet")
requires($(IONET_CMD),)
uniq(netnum, devn-en, 0)
mount(-Tio-net "-overbose,pci=$(index),vid=0x$(ven),did=0x$(dev)" /lib/d
ll/devn-i82544.so, "/dev/io-net/en$(netnum)")
use(symbolic=netmgr)
|
|
|
|
|
|
Mark Dowdy(deleted)
|
Re: RE: RE: Activating a '2nd' Network Adapter
|
|
Mark Dowdy(deleted)
09/12/2008 1:11 PM
post13354
|
Re: RE: RE: Activating a '2nd' Network Adapter
> Very strange. I don't see any output from networking at all as a result
> of the verbose option being passed. Can you cut and paste the relevant
> lines from the enumerator for us to take a look at?
> Glad to hear that things are working, but it would be good to know
> why...
Indeed it would be good to know why. Now that I have verified that the adapter is working, I actually want to use a
different driver. I tried commenting out the
device(pci, ven=$(PCI_VEND_INTEL), dev=107c) # Intel 82541PI Gigabit
line in the devices file but according to nicinfo and ifconfig, it looks like the driver is running. Where else could
the system be starting the driver for this interface?
Mark
|
|
|
|
|
|
Robert Craig
|
RE: RE: RE: Activating a '2nd' Network Adapter
|
|
Robert Craig
09/12/2008 1:19 PM
post13356
|
RE: RE: RE: Activating a '2nd' Network Adapter
Hi Mark:
Could you post this question in the Drivers forum? There are
different people monitoring that forum that may be of help as well.
Robert.
-----Original Message-----
From: Mark Dowdy [mailto:community-noreply@qnx.com]
Sent: Friday, September 12, 2008 1:12 PM
To: general-networking
Subject: Re: RE: RE: Activating a '2nd' Network Adapter
> Very strange. I don't see any output from networking at all as a
result
> of the verbose option being passed. Can you cut and paste the
relevant
> lines from the enumerator for us to take a look at?
> Glad to hear that things are working, but it would be good to know
> why...
Indeed it would be good to know why. Now that I have verified that the
adapter is working, I actually want to use a different driver. I tried
commenting out the
device(pci, ven=$(PCI_VEND_INTEL), dev=107c) # Intel 82541PI Gigabit
line in the devices file but according to nicinfo and ifconfig, it looks
like the driver is running. Where else could the system be starting the
driver for this interface?
Mark
_______________________________________________
General
http://community.qnx.com/sf/go/post13354
|
|
|
|
|
|
Robert Craig
|
RE: Activating a '2nd' Network Adapter
|
|
Robert Craig
09/09/2008 11:07 AM
post13055
|
RE: Activating a '2nd' Network Adapter
Hi Mark:
Apparently there's also a newer driver patch available which
should work with that card.
http://www.qnx.com/download/feature.html?programid=17094
Robert.
-----Original Message-----
From: Mark Dowdy [mailto:community-noreply@qnx.com]
Sent: Monday, September 08, 2008 5:17 PM
To: general-networking
Subject: Re: Activating a '2nd' Network Adapter
> Another thing to try...
>
> Right after boot up with the two interfaces showing up:
>
> mount -Tio-net -o did=0x107c,vid=0x8086 /lib/dll/devn-i82544.so
>
> and see if a third interface appears.
Indeed it does.
Isn't this what the following lines from /etc/systems/enum/devices/net
are supposed to do?
<snip>
device(pci, ven=$(PCI_VEND_INTEL), dev=107c) # Intel 82541PI Gigabit
<snip>
mount(-Tio-net "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-i82544.so, "/dev/io-net/en$(netnum)")
Now that we've established that there is a way to find the third
interface, what is the 'correct' way to automatically start this
interface?
Mark
_______________________________________________
General
http://community.qnx.com/sf/go/post13026
|
|
|
|
|
|
Mark Dowdy(deleted)
|
Re: RE: Activating a '2nd' Network Adapter
|
|
Mark Dowdy(deleted)
09/09/2008 1:05 PM
post13077
|
Re: RE: Activating a '2nd' Network Adapter
That looks like a SP3 patch so I'm going to hold off for now. If the situation requires the installation of SP3, I'll do
that and try the newer patch. Thanks for the link.
Mark
|
|
|
|
|
|
Hugh Brown
|
RE: Activating a '2nd' Network Adapter
|
|
Hugh Brown
09/08/2008 4:26 PM
post13025
|
RE: Activating a '2nd' Network Adapter
That is because the driver doesn't have the device ID for the 0x107c
device. I doubt whether placing the vendor and device IDs on the command
line will get the driver to work as the driver has to perform different
setups for different adapters. I can send you an un-released version of
our new driver which does support this chipset, if you are interested.
-----Original Message-----
From: Robert Craig
Sent: Monday, September 08, 2008 4:01 PM
To: 'post13022@community.qnx.com'
Cc: Hugh Brown
Subject: RE: Activating a '2nd' Network Adapter
So it's definitely not finding the third interface.
The two 1079's show up but not the third one.
The reason why you lose connectivity is because there's no IP address
assigned to the interfaces after re-starting io-net. You'd need to run
dhcp.client -i en0
dhcp.client -i en1
to get the IP addresses assigned.
Another thing to try...
Right after boot up with the two interfaces showing up:
mount -Tio-net -o did=0x107c,vid=0x8086 /lib/dll/devn-i82544.so
and see if a third interface appears.
Robert.
-----Original Message-----
From: Mark Dowdy [mailto:community-noreply@qnx.com]
Sent: Monday, September 08, 2008 3:48 PM
To: general-networking
Subject: Re: Activating a '2nd' Network Adapter
# slay io-net
# sloginfo -c
Time Sev Major Minor Args
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 8
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 4
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 8
Sep 08 12:34:26 3 17 0 Range check failed (IO) - Dev 24d1 -
Vend 8086
- Class 1018a - Addr 0 - Size 4
Sep 08 12:34:26 2 19 0 eide_identify_devices: Intel 82801EB
SATA vid 8
086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 08 12:34:26 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr
3f4, irq e, chnl 0, udma 5, mdma 2, sdma 0, pio 4
Sep 08 12:34:26 2 19 0 eide_display_devices: ST380817AS
tid 0, c
able 40, max udma 6, cur udma 5, max mdma 2, cur mdma 0, max sdma -1,
cur sdma -
1, pio 4, mblk 16
Sep 08 12:34:26 2 19 0 eide_init_devices: ST380817AS
path 0, tid
0, udma 2, mdma 2, sdma -1, pio 4, mblk 16
Sep 08 12:34:26 2 19 0 eide_identify_devices: Intel 82801EB
SATA vid 8
086, did 24d1, class 1018a rev 2, busno 0, dfunc fa
Sep 08 12:34:26 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr
374, irq f, chnl 1, udma 5, mdma 2, sdma 0, pio 4
Sep 08 12:34:26 2 19 0 eide_display_devices: CD-224E
tid 0, c
able 40, max udma 2, cur udma 2, max mdma 2, cur mdma 0, max sdma 2, cur
sdma 0,
pio 4, mblk 0
Sep 08 12:34:26 2 19 0 eide_init_devices: CD-224E
path 0, tid
0, udma 2, mdma 2, sdma 0, pio 4, mblk 0
Sep 08 12:34:34 5 6 200 Installing /dev/par port 378
Sep 08 12:34:34 5 14 0 tcpip starting
Sep 08 12:34:34 3 14 0 Using pseudo random generator. See
"random" op
tion
Sep 08 12:34:37 1 8 0 phfont_init
Sep 08 12:34:37 1 8 0 phfontXX started OK
Sep 08 12:34:38 5 8 0 Process fontsleuth initialized.
Sep 08 12:34:39 1 8 0 phfont_init
Sep 08 12:34:39 1 8 0 phfontXX started OK
Sep 08 12:34:39 6 8 0 VGA primary : bus 0x9 dev/func 0x8
Sep 08 12:34:39 6 8 0 Found 1 PCI/AGP display devices
Sep 08 12:34:39 6 8 0 pci_init: found PCI device 1002:4752
Sep 08 12:34:39 5 8 0 Attached /dev/io-graphics/rage0, id = 0
Sep 08 12:34:42 5 9 0 Start: /usr/photon/bin/devi-hirun kbd
fd -d/dev
/kbd ps2 mousedev
# io-net -di82544 verbose -ptcpip
# sloginfo
Time Sev Major Minor Args
Sep 08 12:42:51 5 10 0 devn-i82544: Bus width is 64 bits
Sep 08 12:42:51 5 10 ...
View Full Message
|
|
|
|
|
|
