Skip navigation.
Home
The QNX Community Portal

View topic - New Intel motherboards

New Intel motherboards

Read-only archive of qnx.development_tools (Self-hosted graphical development with the Eclipse IDE and cross-hosted development on Solaris, Linux, or Windows) at inn.qnx.com

Re: New Intel motherboards

Postby Robert Craig » Tue Aug 01, 2006 7:23 pm

Hmmmm... That I don't know. The patch has been posted so I'm not sure
why you wouldn't be seeing it. Do you have an up to date maintenance
plan in place? I'm not sure under what conditions the patch wouldn't
appear...

R.


Robert Kindred wrote:
I tried your number 11903, and at
http://www.qnx.com/download/group.html?programid=11903



I see



USB Patch [Patch ID 189]

qconfig Patch for QNX Momentics 6.3.0 SP1 or SP2 [Patch ID 205]

Debug Malloc Library Patch for QNX Momentics 6.3.0 SP2 [Patch ID 155]

QNX® Momentics® 6.3.0 Graphics Driver Patch [Patch ID 171]

Maintenance Patch [Patch ID 97] for Momentics 6.3.0 SP1 Full TCP/IP Stack



Do I need to do something to turn on more stuff?



"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:e98hor$nqn$1@inn.qnx.com...

Hmmmm... It's possible that I've got some sort of magic access (although
I thought that I'd turned that off). I see those patches towards the
end of the list as well, but before it there are quite a few other ones.
The URL says "programid=11903" when I get to the appropriate download
area...


R.

Robert Kindred wrote:

Hey, sounds great! For some reason, though I don't see it. All I see
are:

USB Patch [Patch ID 189]

qconfig Patch for QNX Momentics 6.3.0 SP1 or SP2 [Patch ID 205]

Debug Malloc Library Patch for QNX Momentics 6.3.0 SP2 [Patch ID 155]

QNX® Momentics® 6.3.0 Graphics Driver Patch [Patch ID 171]

Maintenance Patch [Patch ID 97] for Momentics 6.3.0 SP1 Full TCP/IP Stack

Maybe I'm looking in the wrong place.

Robert Kindred


"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:e93o9b$dof$1@inn.qnx.com...


The recently released patch ID 214 (available from the download section
of
MyQNX under Momentics 6.3.x : ... Service Pack 2 and related downloads :
... Patches and Updates) contains a variety of updated drivers including
a
new devn-i82544.

R.


Robert Craig wrote:



I'm not sure how we go about announcing availability of driver updates,
but they'll become available through your MyQNX account. I'll try and
post a message here when the patch is put out as well.

R.

Robert Kindred wrote:



"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:dtksn4$age$1@inn.qnx.com...



Hi Robert:

I just looked at the specs for the board and it has the 82573 GigE
controller on board. Interestingly enough, this SHOULD work with our
i82544 driver (we're going to be releasing a new version RSN :->).
That being said, I believe that we've had a couple of bug reports
filed
specifically with that chipset that will have to be fixed.

The good news is that this chip is a priority for us and we already
have driver infrastructure in place for it so it will be fully
supported in the very near future.



That's great! How will I know when it is available?




Robert.


[]






Robert Craig
 

Re: New Intel motherboards

Postby Steve Reid » Tue Aug 01, 2006 9:04 pm

Robert Craig <rcraig_at_qnx@nowhere.com> wrote:
Hmmmm... That I don't know. The patch has been posted so I'm not sure
why you wouldn't be seeing it. Do you have an up to date maintenance
plan in place? I'm not sure under what conditions the patch wouldn't
appear...

I think the patch has been posted but hasn't yet been made available to
the outside world.

------------------------------------------
Steve Reid stever@qnx.com
Technical Editor
QNX Software Systems
------------------------------------------
Steve Reid
 

Re: New Intel motherboards

Postby Robert Craig » Mon Aug 14, 2006 7:17 pm

I've just received notice from the powers that be that this patch is now
available externally. Sorry for the confusion...

Rob

Steve Reid wrote:

Robert Craig <rcraig_at_qnx@nowhere.com> wrote:

Hmmmm... That I don't know. The patch has been posted so I'm not sure
why you wouldn't be seeing it. Do you have an up to date maintenance
plan in place? I'm not sure under what conditions the patch wouldn't
appear...


I think the patch has been posted but hasn't yet been made available to
the outside world.

------------------------------------------
Steve Reid stever@qnx.com
Technical Editor
QNX Software Systems
------------------------------------------
Robert Craig
 

Re: New Intel motherboards

Postby Robert Kindred » Mon Oct 02, 2006 2:14 pm

Well, I downloaded this and ran the patch instructions. Then I tried the
io-net and the "wait" something trick. This causes the "Devices" tab to
appear on the network configuration form, but I still cannot ping out. Can
anyone give me some tips on manually installing and troubleshooting a
network driver?

Robert Kindred

"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:ebqi0g$i5l$1@inn.qnx.com...
I've just received notice from the powers that be that this patch is now
available externally. Sorry for the confusion...

Rob

Steve Reid wrote:

Robert Craig <rcraig_at_qnx@nowhere.com> wrote:

Hmmmm... That I don't know. The patch has been posted so I'm not sure
why you wouldn't be seeing it. Do you have an up to date maintenance
plan in place? I'm not sure under what conditions the patch wouldn't
appear...


I think the patch has been posted but hasn't yet been made available to
the outside world.

------------------------------------------
Steve Reid stever@qnx.com
Technical Editor
QNX Software Systems
------------------------------------------
Robert Kindred
 

Re: New Intel motherboards

Postby Robert Craig » Mon Oct 02, 2006 9:15 pm

As root:

slay io-net
io-net -di82544 verbose -ptcpip

ifconfig (etc.) (or use phlip if you'd like)

You can then use "sloginfo" to get the debug information that io-net
prints out.

To make sure that you're using the right version of the driver, you can
also specify the fully qualified pathname for the driver name.

For general debugging, "ping" and "nicinfo" are useful utilities.

Robet.

Robert Kindred wrote:
Well, I downloaded this and ran the patch instructions. Then I tried the
io-net and the "wait" something trick. This causes the "Devices" tab to
appear on the network configuration form, but I still cannot ping out. Can
anyone give me some tips on manually installing and troubleshooting a
network driver?

Robert Kindred

"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:ebqi0g$i5l$1@inn.qnx.com...

I've just received notice from the powers that be that this patch is now
available externally. Sorry for the confusion...

Rob

Steve Reid wrote:


Robert Craig <rcraig_at_qnx@nowhere.com> wrote:


Hmmmm... That I don't know. The patch has been posted so I'm not sure
why you wouldn't be seeing it. Do you have an up to date maintenance
plan in place? I'm not sure under what conditions the patch wouldn't
appear...


I think the patch has been posted but hasn't yet been made available to
the outside world.

------------------------------------------
Steve Reid stever@qnx.com
Technical Editor
QNX Software Systems
------------------------------------------


Robert Craig
 

Re: New Intel motherboards

Postby Robert Kindred » Tue Oct 24, 2006 8:59 pm

"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:efruua$nq4$1@inn.qnx.com...
As root:

slay io-net
io-net -di82544 verbose -ptcpip

ifconfig (etc.) (or use phlip if you'd like)

You can then use "sloginfo" to get the debug information that io-net
prints out.

To make sure that you're using the right version of the driver, you can
also specify the fully qualified pathname for the driver name.

For general debugging, "ping" and "nicinfo" are useful utilities.

Robet.

[]


OK, I loaded the driver up. The ping gives me "Host is down", but certain
places on Google tell me that this is a rather nebulous error message. The
stack does not really know what the problem is. When I run nicinfo after
ping, I get:

INTEL 82544 Gigabit (Copper) Ethernet Controller

Link is DOWN

Physical Node ID ........................... 001676 32A557
Current Physical Node ID ................... 001676 32A557
Current Operation Rate ..................... 0 kb/s half-duplex
Active Interface Type ...................... MII
Active PHY address ....................... 0
Maximum Transmittable data Unit ............ 1514
Maximum Receivable data Unit ............... 0
Hardware Interrupt ......................... 0xb
Memory Aperture ............................ 0x90100000 - 0x9011ffff
Promiscuous Mode ........................... Off
Multicast Support .......................... Enabled

Packets Transmitted OK ..................... 10
Bytes Transmitted OK ....................... 640
Broadcast Packets Transmitted OK ........... 10
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
Deferred Transmits ......................... 0
Late Collision on Transmit errors .......... 0
Transmits aborted (excessive collisions) ... 0
No Carrier on Transmit ..................... 0
Receive Alignment errors ................... 0
Received packets with CRC errors ........... 0
Packets Dropped on receive ................. 0


Because I see transmits with no receives, I suspect that there is an
interrupt problem.

Robert Kindred
Robert Kindred
 

Re: New Intel motherboards

Postby Mario Charest » Wed Oct 25, 2006 12:35 pm

"Robert Kindred" <RKindred@SwRI.edu> wrote in message
news:ehlun7$10f$1@inn.qnx.com...
"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:efruua$nq4$1@inn.qnx.com...
As root:

slay io-net
io-net -di82544 verbose -ptcpip

ifconfig (etc.) (or use phlip if you'd like)

You can then use "sloginfo" to get the debug information that io-net
prints out.

To make sure that you're using the right version of the driver, you can
also specify the fully qualified pathname for the driver name.

For general debugging, "ping" and "nicinfo" are useful utilities.

Robet.

[]

OK, I loaded the driver up. The ping gives me "Host is down", but certain
places on Google tell me that this is a rather nebulous error message.
The stack does not really know what the problem is. When I run nicinfo
after ping, I get:

INTEL 82544 Gigabit (Copper) Ethernet Controller

Link is DOWN

Physical Node ID ........................... 001676 32A557
Current Physical Node ID ................... 001676 32A557
Current Operation Rate ..................... 0 kb/s half-duplex

0K for speed. That means the driver was not able to detect the
connection speed, as if the cable was unplugged.

Active Interface Type ...................... MII
Active PHY address ....................... 0
Maximum Transmittable data Unit ............ 1514
Maximum Receivable data Unit ............... 0
Hardware Interrupt ......................... 0xb
Memory Aperture ............................ 0x90100000 - 0x9011ffff
Promiscuous Mode ........................... Off
Multicast Support .......................... Enabled

Packets Transmitted OK ..................... 10
Bytes Transmitted OK ....................... 640
Broadcast Packets Transmitted OK ........... 10
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
Deferred Transmits ......................... 0
Late Collision on Transmit errors .......... 0
Transmits aborted (excessive collisions) ... 0
No Carrier on Transmit ..................... 0
Receive Alignment errors ................... 0
Received packets with CRC errors ........... 0
Packets Dropped on receive ................. 0


Because I see transmits with no receives, I suspect that there is an
interrupt problem.

Robert Kindred

Mario Charest
 

Re: New Intel motherboards

Postby Robert Kindred » Wed Oct 25, 2006 3:07 pm

"Mario Charest" <root@127.0.0.1> wrote in message
news:ehnlh4$6oc$1@inn.qnx.com...
"Robert Kindred" <RKindred@SwRI.edu> wrote in message
news:ehlun7$10f$1@inn.qnx.com...

"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:efruua$nq4$1@inn.qnx.com...
As root:

slay io-net
io-net -di82544 verbose -ptcpip

ifconfig (etc.) (or use phlip if you'd like)

You can then use "sloginfo" to get the debug information that io-net
prints out.

To make sure that you're using the right version of the driver, you can
also specify the fully qualified pathname for the driver name.

For general debugging, "ping" and "nicinfo" are useful utilities.

Robet.

[]

INTEL 82544 Gigabit (Copper) Ethernet Controller

Link is DOWN

Physical Node ID ........................... 001676 32A557
Current Physical Node ID ................... 001676 32A557
Current Operation Rate ..................... 0 kb/s half-duplex

0K for speed. That means the driver was not able to detect the
connection speed, as if the cable was unplugged.

Active Interface Type ...................... MII
Active PHY address ....................... 0
Maximum Transmittable data Unit ............ 1514
Maximum Receivable data Unit ............... 0
Hardware Interrupt ......................... 0xb
Memory Aperture ............................ 0x90100000 - 0x9011ffff
Promiscuous Mode ........................... Off
Multicast Support .......................... Enabled

Packets Transmitted OK ..................... 10
Bytes Transmitted OK ....................... 640
Broadcast Packets Transmitted OK ........... 10
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
Deferred Transmits ......................... 0
Late Collision on Transmit errors .......... 0
Transmits aborted (excessive collisions) ... 0
No Carrier on Transmit ..................... 0
Receive Alignment errors ................... 0
Received packets with CRC errors ........... 0
Packets Dropped on receive ................. 0

Well, I am not sure, but the lights come on when the cable is plugged in,
and one of them blinks once per second when ping is running. Here is the
tail end of sloginfo:

Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 8
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 4
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 8
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 4
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27df, class 1018a rev 1, busno 0, dfunc f9
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr 3f4, irq e, chnl 0, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_display_devices: ST340016A tid
0, cable 80, max udma 5, cur udma 5, max mdma 2, cur mdma 0, max sdma -1,
cur sdma -1, pio 4, mblk 16
Oct 25 09:35:56 2 19 0 eide_init_devices: ST340016A path 0,
tid 0, udma -1, mdma -1, sdma -1, pio 4, mblk 16
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27df, class 1018a rev 1, busno 0, dfunc f9
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr 374, irq f, chnl 1, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27c0, class 1018f rev 1, busno 0, dfunc fa
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 30c8,
cntl_addr 30ec, irq a, chnl 0, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27c0, class 1018f rev 1, busno 0, dfunc fa
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 30c0,
cntl_addr 30e8, irq a, chnl 1, udma -1, mdma -1, sdma -1, pio 0
Oct 25 14:36:13 5 14 0 tcpip starting
Oct 25 14:36:13 3 14 0 Using pseudo random generator. See
"random" option
Oct 25 14:36:15 1 8 0 phfont_init
Oct 25 14:36:15 1 8 0 phfontXX started OK
Oct 25 14:36:17 5 8 0 Process fontsleuth initialized.
Oct 25 14:36:18 1 8 0 phfont_init
Oct 25 14:36:18 1 8 0 phfontXX started OK
Oct 25 14:36:18 5 9 0 Start: /usr/photon/bin/devi-hirun kbd
fd -d/dev/kbd ps2 mousedev

Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 5 8 0 Attached /dev/io-graphics/vesabios0, id = 0
Oct 25 14:44:09 5 10 0 devn-i82544: Bus width is 32 bits
Oct 25 14:44:09 5 10 0 devn-i82544: *not* running in PCI-X mode
Oct 25 14:44:09 5 10 0 devn-i82544: found internal Copper PHY at
address 1
Oct 25 14:44:09 5 10 0 INTEL 82544 Gigabit (Copper)
Oct 25 14:44:09 5 10 0 Vendor .............. 0x8086
Oct 25 14:44:09 5 10 0 Device .............. 0x108b
Oct 25 14:44:09 5 10 0 Revision ............ 0x0
Oct 25 14:44:09 5 10 0 Memory base ......... 0x90100000
Oct 25 14:44:09 5 10 0 Interrupt ........... 0xb
Oct 25 14:44:09 5 10 0 MAC address ......... 001676 32a557
Oct 25 14:44:09 5 14 0 tcpip starting
Oct 25 14:44:09 3 14 0 Using pseudo random generator. See
"random" option


Robert Kindred
Robert Kindred
 

Re: New Intel motherboards

Postby Robert Kindred » Fri Oct 27, 2006 1:31 pm

I wonder if anyone can tell how I can get source code so that I can
troubleshoot this at the grass roots level.

Robert Kindred

"Robert Kindred" <RKindred@SwRI.edu> wrote in message
news:ehnuec$cvn$1@inn.qnx.com...
"Mario Charest" <root@127.0.0.1> wrote in message
news:ehnlh4$6oc$1@inn.qnx.com...

"Robert Kindred" <RKindred@SwRI.edu> wrote in message
news:ehlun7$10f$1@inn.qnx.com...

"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:efruua$nq4$1@inn.qnx.com...
As root:

slay io-net
io-net -di82544 verbose -ptcpip

ifconfig (etc.) (or use phlip if you'd like)

You can then use "sloginfo" to get the debug information that io-net
prints out.

To make sure that you're using the right version of the driver, you can
also specify the fully qualified pathname for the driver name.

For general debugging, "ping" and "nicinfo" are useful utilities.

Robet.

[]

INTEL 82544 Gigabit (Copper) Ethernet Controller

Link is DOWN

Physical Node ID ........................... 001676 32A557
Current Physical Node ID ................... 001676 32A557
Current Operation Rate ..................... 0 kb/s half-duplex

0K for speed. That means the driver was not able to detect the
connection speed, as if the cable was unplugged.

Active Interface Type ...................... MII
Active PHY address ....................... 0
Maximum Transmittable data Unit ............ 1514
Maximum Receivable data Unit ............... 0
Hardware Interrupt ......................... 0xb
Memory Aperture ............................ 0x90100000 - 0x9011ffff
Promiscuous Mode ........................... Off
Multicast Support .......................... Enabled

Packets Transmitted OK ..................... 10
Bytes Transmitted OK ....................... 640
Broadcast Packets Transmitted OK ........... 10
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
Deferred Transmits ......................... 0
Late Collision on Transmit errors .......... 0
Transmits aborted (excessive collisions) ... 0
No Carrier on Transmit ..................... 0
Receive Alignment errors ................... 0
Received packets with CRC errors ........... 0
Packets Dropped on receive ................. 0

Well, I am not sure, but the lights come on when the cable is plugged in,
and one of them blinks once per second when ping is running. Here is the
tail end of sloginfo:

Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 8
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 4
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 8
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 4
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27df, class 1018a rev 1, busno 0, dfunc f9
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr 3f4, irq e, chnl 0, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_display_devices: ST340016A
tid 0, cable 80, max udma 5, cur udma 5, max mdma 2, cur mdma 0, max
sdma -1, cur sdma -1, pio 4, mblk 16
Oct 25 09:35:56 2 19 0 eide_init_devices: ST340016A path
0, tid 0, udma -1, mdma -1, sdma -1, pio 4, mblk 16
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27df, class 1018a rev 1, busno 0, dfunc f9
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr 374, irq f, chnl 1, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27c0, class 1018f rev 1, busno 0, dfunc fa
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 30c8,
cntl_addr 30ec, irq a, chnl 0, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27c0, class 1018f rev 1, busno 0, dfunc fa
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 30c0,
cntl_addr 30e8, irq a, chnl 1, udma -1, mdma -1, sdma -1, pio 0
Oct 25 14:36:13 5 14 0 tcpip starting
Oct 25 14:36:13 3 14 0 Using pseudo random generator. See
"random" option
Oct 25 14:36:15 1 8 0 phfont_init
Oct 25 14:36:15 1 8 0 phfontXX started OK
Oct 25 14:36:17 5 8 0 Process fontsleuth initialized.
Oct 25 14:36:18 1 8 0 phfont_init
Oct 25 14:36:18 1 8 0 phfontXX started OK
Oct 25 14:36:18 5 9 0 Start: /usr/photon/bin/devi-hirun kbd
fd -d/dev/kbd ps2 mousedev

Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 5 8 0 Attached /dev/io-graphics/vesabios0, id =
0
Oct 25 14:44:09 5 10 0 devn-i82544: Bus width is 32 bits
Oct 25 14:44:09 5 10 0 devn-i82544: *not* running in PCI-X mode
Oct 25 14:44:09 5 10 0 devn-i82544: found internal Copper PHY at
address 1
Oct 25 14:44:09 5 10 0 INTEL 82544 Gigabit (Copper)
Oct 25 14:44:09 5 10 0 Vendor .............. 0x8086
Oct 25 14:44:09 5 10 0 Device .............. 0x108b
Oct 25 14:44:09 5 10 0 Revision ............ 0x0
Oct 25 14:44:09 5 10 0 Memory base ......... 0x90100000
Oct 25 14:44:09 5 10 0 Interrupt ........... 0xb
Oct 25 14:44:09 5 10 0 MAC address ......... 001676 32a557
Oct 25 14:44:09 5 14 0 tcpip starting
Oct 25 14:44:09 3 14 0 Using pseudo random generator. See
"random" option


Robert Kindred
Robert Kindred
 

Re: New Intel motherboards

Postby Robert Craig » Fri Oct 27, 2006 6:12 pm

Can you try inserting and removing the cable and looking at the sloginfo
output? I'm not seeing any link up notifications and the fact that the
operation rate is 0 is definitely a problem.

Can you post the output from pci -v?


R.

Robert Kindred wrote:

"Mario Charest" <root@127.0.0.1> wrote in message
news:ehnlh4$6oc$1@inn.qnx.com...

"Robert Kindred" <RKindred@SwRI.edu> wrote in message
news:ehlun7$10f$1@inn.qnx.com...

"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:efruua$nq4$1@inn.qnx.com...

As root:

slay io-net
io-net -di82544 verbose -ptcpip

ifconfig (etc.) (or use phlip if you'd like)

You can then use "sloginfo" to get the debug information that io-net
prints out.

To make sure that you're using the right version of the driver, you can
also specify the fully qualified pathname for the driver name.

For general debugging, "ping" and "nicinfo" are useful utilities.

Robet.


[]

INTEL 82544 Gigabit (Copper) Ethernet Controller

Link is DOWN

Physical Node ID ........................... 001676 32A557
Current Physical Node ID ................... 001676 32A557
Current Operation Rate ..................... 0 kb/s half-duplex

0K for speed. That means the driver was not able to detect the
connection speed, as if the cable was unplugged.


Active Interface Type ...................... MII
Active PHY address ....................... 0
Maximum Transmittable data Unit ............ 1514
Maximum Receivable data Unit ............... 0
Hardware Interrupt ......................... 0xb
Memory Aperture ............................ 0x90100000 - 0x9011ffff
Promiscuous Mode ........................... Off
Multicast Support .......................... Enabled

Packets Transmitted OK ..................... 10
Bytes Transmitted OK ....................... 640
Broadcast Packets Transmitted OK ........... 10
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
Deferred Transmits ......................... 0
Late Collision on Transmit errors .......... 0
Transmits aborted (excessive collisions) ... 0
No Carrier on Transmit ..................... 0
Receive Alignment errors ................... 0
Received packets with CRC errors ........... 0
Packets Dropped on receive ................. 0


Well, I am not sure, but the lights come on when the cable is plugged in,
and one of them blinks once per second when ping is running. Here is the
tail end of sloginfo:

Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 8
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 4
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 8
Oct 25 09:35:56 3 17 0 Range check failed (IO) - Dev 27df - Vend
8086 - Class 1018a - Addr 0 - Size 4
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27df, class 1018a rev 1, busno 0, dfunc f9
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 1f0,
cntl_addr 3f4, irq e, chnl 0, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_display_devices: ST340016A tid
0, cable 80, max udma 5, cur udma 5, max mdma 2, cur mdma 0, max sdma -1,
cur sdma -1, pio 4, mblk 16
Oct 25 09:35:56 2 19 0 eide_init_devices: ST340016A path 0,
tid 0, udma -1, mdma -1, sdma -1, pio 4, mblk 16
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27df, class 1018a rev 1, busno 0, dfunc f9
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 170,
cntl_addr 374, irq f, chnl 1, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27c0, class 1018f rev 1, busno 0, dfunc fa
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 30c8,
cntl_addr 30ec, irq a, chnl 0, udma -1, mdma -1, sdma -1, pio 0
Oct 25 09:35:56 2 19 0 eide_identify_devices: Generic IDE vid
8086, did 27c0, class 1018f rev 1, busno 0, dfunc fa
Oct 25 09:35:56 2 19 0 eide_identify_devices: cmd_addr 30c0,
cntl_addr 30e8, irq a, chnl 1, udma -1, mdma -1, sdma -1, pio 0
Oct 25 14:36:13 5 14 0 tcpip starting
Oct 25 14:36:13 3 14 0 Using pseudo random generator. See
"random" option
Oct 25 14:36:15 1 8 0 phfont_init
Oct 25 14:36:15 1 8 0 phfontXX started OK
Oct 25 14:36:17 5 8 0 Process fontsleuth initialized.
Oct 25 14:36:18 1 8 0 phfont_init
Oct 25 14:36:18 1 8 0 phfontXX started OK
Oct 25 14:36:18 5 9 0 Start: /usr/photon/bin/devi-hirun kbd
fd -d/dev/kbd ps2 mousedev

Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 6 8 0 SetDisplayOffset pos: 0 0
Oct 25 14:36:18 5 8 0 Attached /dev/io-graphics/vesabios0, id = 0
Oct 25 14:44:09 5 10 0 devn-i82544: Bus width is 32 bits
Oct 25 14:44:09 5 10 0 devn-i82544: *not* running in PCI-X mode
Oct 25 14:44:09 5 10 0 devn-i82544: found internal Copper PHY at
address 1
Oct 25 14:44:09 5 10 0 INTEL 82544 Gigabit (Copper)
Oct 25 14:44:09 5 10 0 Vendor .............. 0x8086
Oct 25 14:44:09 5 10 0 Device .............. 0x108b
Oct 25 14:44:09 5 10 0 Revision ............ 0x0
Oct 25 14:44:09 5 10 0 Memory base ......... 0x90100000
Oct 25 14:44:09 5 10 0 Interrupt ........... 0xb
Oct 25 14:44:09 5 10 0 MAC address ......... 001676 32a557
Oct 25 14:44:09 5 14 0 tcpip starting
Oct 25 14:44:09 3 14 0 Using pseudo random generator. See
"random" option


Robert Kindred

Robert Craig
 

Re: New Intel motherboards

Postby Robert Kindred » Thu Nov 02, 2006 8:20 pm

"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:ehthue$8qr$1@inn.qnx.com...
Can you try inserting and removing the cable and looking at the sloginfo
output? I'm not seeing any link up notifications and the fact that the
operation rate is 0 is definitely a problem.

Can you post the output from pci -v?

I did make a log of pci -v, and you are welcome to it, but I am slipping. I
should have thought to unplug the UEI PowerDaq cards and the counter-timer
card. When I do, the network works just fine. I guess I'll have to play
juggle with card slots and interrupts now.

I think there are gentlemen's rules for sharing an interrupt, aren't there?
If you snag an interrupt and someone else is using it, you should do your
work on the interrupt and then trigger them to run in daisy-chain fashion.
I don't know if everyone plays by these rules.

Robert Kindred


R.

[]
Robert Kindred
 

Previous

Return to qnx.development_tools

Who is online

Users browsing this forum: No registered users and 1 guest