Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - devn-i82544 not able to auto negotiate: (22 Items)
   
devn-i82544 not able to auto negotiate  
I am facing a strange problem

When I am launching the driver with the below command:

#io-net -i1 -d i82544 mac=id,speed=100,duplex=0x1 -ptcpip prefix=/sock1

The connection seems to be proper.

But when i don't mention speed and duplex i.e. when i give the following command

#io-net -i1 -d i82544 mac=id -ptcpip prefix=/sock1 (command used for auto negotiation)

The other nic card is unable to see network connection (says network cable unplug) 

Network configuration (82544 Nic direclty connect to laptop via straight cable).

The obervations sloginfo looks same for both commands and io-net does't show any error.

Please suggest what may be te issue
Re: devn-i82544 not able to auto negotiate  
> I am facing a strange problem using QNX 6.3.2 io-net driver 82544 
> 
> When I am launching the driver with the below command:
> 
> #io-net -i1 -d i82544 mac=id,speed=100,duplex=0x1 -ptcpip prefix=/sock1
> 
> The connection seems to be proper.
> 
> But when i don't mention speed and duplex i.e. when i give the following 
> command
> 
> #io-net -i1 -d i82544 mac=id -ptcpip prefix=/sock1 (command used for auto 
> negotiation)
> 
> The other nic card is unable to see network connection (says network cable 
> unplug) 
> 
> Network configuration (82544 Nic direclty connect to laptop via straight cable
> ).
> 
> The obervations sloginfo looks same for both commands and io-net does't show 
> any error.
> 
> Please suggest what may be te issue


Re: devn-i82544 not able to auto negotiate  
What version of the O/S are you running? There is a newer driver under
6.5.0 for the Intel gigabit chipsets - devnp-e1000.so.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-19 5:11 AM, "nishant mishra" <community-noreply@qnx.com> wrote:

>I am facing a strange problem
>
>When I am launching the driver with the below command:
>
>#io-net -i1 -d i82544 mac=id,speed=100,duplex=0x1 -ptcpip prefix=/sock1
>
>The connection seems to be proper.
>
>But when i don't mention speed and duplex i.e. when i give the following
>command
>
>#io-net -i1 -d i82544 mac=id -ptcpip prefix=/sock1 (command used for auto
>negotiation)
>
>The other nic card is unable to see network connection (says network
>cable unplug) 
>
>Network configuration (82544 Nic direclty connect to laptop via straight
>cable).
>
>The obervations sloginfo looks same for both commands and io-net does't
>show any error.
>
>Please suggest what may be te issue
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89442
>
Re: devn-i82544 not able to auto negotiate  
I am trying to launch devn-i82455 on 6.3.2
commands
#io-net -d i82455 mac=001ff448f185 -ptcpip (auto negitiatation not working network cable unplugged)

#io-net -d i82455 mac=001ff448f185,speed=100,duplex=0x1 -ptcpip
(works goos at 100 mbps) 
Re: devn-i82544 not able to auto negotiate  
Here is the latest version of the 6.3.2 driver for you to try. It is now
called devn-e1000.so.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-20 1:33 AM, "nishant mishra" <community-noreply@qnx.com> wrote:

>I am trying to launch devn-i82455 on 6.3.2
>commands
>#io-net -d i82455 mac=001ff448f185 -ptcpip (auto negitiatation not
>working network cable unplugged)
>
>#io-net -d i82455 mac=001ff448f185,speed=100,duplex=0x1 -ptcpip
>(works goos at 100 mbps)
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89471
>

Attachment: Text devn-e1000.so.632 222.38 KB
Re: devn-i82544 not able to auto negotiate  
Can you also suggest the arguments I am unable to pass it says 

# io-net -d e1000 mac=001ff0448818 -ptcpip
# unable to load dll devn-e1000: Shared library is corrupted
Re: devn-i82544 not able to auto negotiate  
Its a power PPC qnx6.3.2 io-net will the driver which you sent will still work
Re: devn-i82544 not able to auto negotiate  
Here is the 6.3.2 PPC version.

Hugh.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-20 8:50 AM, "nishant mishra" <community-noreply@qnx.com> wrote:

>Its a power PPC qnx6.3.2 io-net will the driver which you sent will still
>work
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89477
>

Attachment: Text devn-e1000.so.632.ppc 284.21 KB
Re: devn-i82544 not able to auto negotiate  
See i got the following error:
# io-net -d e1000 mac=001ff0448f18,verbose=4 -ptcpip
# unable to init dll devn-e1000: No error

# sloginfo
Time             Sev Major Minor Args
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
Jan 01 01:56:50    6    10     0 e1000_standby_nvm
Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_stop_nvm
Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
Jan 01 01:56:50    6    10     0 e1000_standby_nvm
Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_stop_nvm
Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
Jan 01 01:56:50    6    10     0 e1000_standby_nvm
Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_stop_nvm
Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
Jan 01 01:56:50    6    10     0 e1000_standby_nvm
Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_stop_nvm
Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
Jan 01 01:56:50    6    10     0 e1000_standby_nvm
Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_stop_nvm
Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
Jan 01 01:56:50    6    10     0 e1000_standby_nvm
Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_stop_nvm
Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
Jan 01 01:56:50    6    10     0 e1000_standby_nvm
Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_stop_nvm
Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
Jan 01 01:56:50    6    10     0...
View Full Message
Re: devn-i82544 not able to auto negotiate  
Please try this version.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-20 11:01 AM, "nishant mishra" <community-noreply@qnx.com> wrote:

>See i got the following error:
># io-net -d e1000 mac=001ff0448f18,verbose=4 -ptcpip
># unable to init dll devn-e1000: No error
>
># sloginfo
>Time             Sev Major Minor Args
>Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_standby_nvm
>Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_stop_nvm
>Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
>Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_standby_nvm
>Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_stop_nvm
>Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
>Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_standby_nvm
>Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_stop_nvm
>Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
>Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_standby_nvm
>Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_stop_nvm
>Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
>Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_standby_nvm
>Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_stop_nvm
>Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
>Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_in_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_standby_nvm
>Jan 01 01:56:50    6    10     0 e1000_release_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_stop_nvm
>Jan 01 01:56:50    6    10     0 e1000_read_nvm_microwire
>Jan 01 01:56:50    6    10     0 e1000_acquire_nvm_generic
>Jan 01 01:56:50    6    10     0 e1000_ready_nvm_eeprom
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0 e1000_shift_out_eec_bits
>Jan 01 01:56:50    6    10     0...
View Full Message
Attachment: Text devn-e1000.so.632.ppc 284.21 KB
Re: devn-i82544 not able to auto negotiate  
Do you feel any issues with the logs see the attachement too
# nicinfo
INTEL PRO/1000 Gigabit (Copper) Ethernet Controller

  Physical Node ID ........................... 000000 000000
  Current Physical Node ID ................... 001FF0 448F18
  Current Operation Rate ..................... Unknown
  Active Interface Type ...................... MII
    Active PHY address ....................... 1
  Maximum Transmittable data Unit ............ 1514
  Maximum Receivable data Unit ............... 1514
  Hardware Interrupt ......................... 0x15
  Memory Aperture ............................ 0xcefc0000 - 0xcefdffff
  Promiscuous Mode ........................... Off
  Multicast Support .......................... Enabled

  Packets Transmitted OK ..................... 0
  Bytes Transmitted OK ....................... 0
  Broadcast Packets Transmitted OK ........... 0
  Multicast Packets Transmitted OK ........... 0
  Memory Allocation Failures on Transmit ..... 0

  Packets Received OK ........................ 0
  Bytes Received OK .......................... 0
  Broadcast Packets Received OK .............. 0
  Multicast Packets Received OK .............. 0
  Memory Allocation Failures on Receive ...... 0

  Single Collisions on Transmit .............. 0
  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
#
Attachment: Text cfd_6.3.2.TXT 50.14 KB
Re: devn-i82544 not able to auto negotiate  
and still there are no signals at laptop side it says network connection unplugged
Re: devn-i82544 not able to auto negotiate  
What is the device ID of the Ethernet device? The output from 'pci -v'
would also help.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-20 12:20 PM, "nishant mishra" <community-noreply@qnx.com> wrote:

>and still there are no signals at laptop side it says network connection
>unplugged
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89500
>
Re: devn-i82544 not able to auto negotiate  
# pci A

PCI version    = 2.10

Class          = Network (Ethernet)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 100eh,  82540EM Gigabit Ethernet Controller
PCI index      = 0h
PCI Mem Address = cefc0000h enabled
PCI Mem Address = cefe0000h enabled
PCI IO Address  = fff00h enabled
CPU IO Address  = d00fff00h
PCI Expansion ROM = 0h disabled
PCI Int Pin    = INT A
Interrupt line = 21
CPU Interrupt  = 15h

Class          = Display (VGA)
Vendor ID      = 126fh, Silicon Motion, Inc.
Device ID      = 712h,  SM712 LynxEM+
PCI index      = 0h
PCI Mem Address = cf000000h enabled
PCI Int Pin    = INT A
Interrupt line = 21
CPU Interrupt  = 15h

#
Re: devn-i82544 not able to auto negotiate  
Looks to me as though interrupts aren't working. The link up will only be
detected with a link interrupt. Can you plug the machine into a switch
rather than a laptop? You can also try starting the driver with a
different irq on the command line.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-20 12:27 PM, "nishant mishra" <community-noreply@qnx.com> wrote:

># pci A
>
>PCI version    = 2.10
>
>Class          = Network (Ethernet)
>Vendor ID      = 8086h, Intel Corporation
>Device ID      = 100eh,  82540EM Gigabit Ethernet Controller
>PCI index      = 0h
>PCI Mem Address = cefc0000h enabled
>PCI Mem Address = cefe0000h enabled
>PCI IO Address  = fff00h enabled
>CPU IO Address  = d00fff00h
>PCI Expansion ROM = 0h disabled
>PCI Int Pin    = INT A
>Interrupt line = 21
>CPU Interrupt  = 15h
>
>Class          = Display (VGA)
>Vendor ID      = 126fh, Silicon Motion, Inc.
>Device ID      = 712h,  SM712 LynxEM+
>PCI index      = 0h
>PCI Mem Address = cf000000h enabled
>PCI Int Pin    = INT A
>Interrupt line = 21
>CPU Interrupt  = 15h
>
>#
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89502
>
Re: devn-i82544 not able to auto negotiate  
I tried using a switch but was not able to ping to and fro
Re: devn-i82544 not able to auto negotiate  
Well before you can ping you need to get a link up, so connect the machine
to the switch and see if you get a link light.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-20 1:16 PM, "nishant mishra" <community-noreply@qnx.com> wrote:

>I tried using a switch but was not able to ping to and fro
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89504
>
Re: devn-i82544 not able to auto negotiate  
We're having a similar problem on 6.3.2-x86 between our system and a switch. The attached driver seems to correct our 
issue. Is this an 'official' release? If so, is there an associated patch number? I'd like to propose it as a solution 
but management is asking what kind of testing has been done. Are there regression tests that drivers are put through? 
Thanks.

Mark
Re: devn-i82544 not able to auto negotiate  
No, this is not an official release - there haven't been any for 6.3.2 for
a long time. If you require an official driver, you will have to request
it via the correct channels.

-- 
Hugh Brown
QNX Software Systems Limited
1001 Farrar Rd.,
Ottawa. ON. K2K 0B3.
Telephone: 613-591-0931







On 12-05-23 5:14 PM, "Mark Dowdy" <community-noreply@qnx.com> wrote:

>We're having a similar problem on 6.3.2-x86 between our system and a
>switch. The attached driver seems to correct our issue. Is this an
>'official' release? If so, is there an associated patch number? I'd like
>to propose it as a solution but management is asking what kind of testing
>has been done. Are there regression tests that drivers are put through?
>Thanks.
>
>Mark
>
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post93275
>To cancel your subscription to this discussion, please e-mail
>drivers-networking-unsubscribe@community.qnx.com

Re: devn-i82544 not able to auto negotiate  
Its working after using a switch
But not when connected directly through a straight cable 
Would you be able to point out what is the exact reason for it
Do you also suspect hardware or it only driver
Re: devn-i82544 not able to auto negotiate  
I have had a lot of problems connecting gigabit devices via crossover
cables to another host - don't ask me why! I suspect that it is something
to do with the hardware.

-- 
Hugh Brown
QNX Software Systems Limited
175 Terence Matthews Crescent,
Ottawa. ON. K2M 1W8.
Telephone: 613-591-0931







On 11-10-21 5:21 AM, "nishant mishra" <community-noreply@qnx.com> wrote:

>Its working after using a switch
>But not when connected directly through a straight cable
>Would you be able to point out what is the exact reason for it
>Do you also suspect hardware or it only driver
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post89519
>
RE: devn-i82544 not able to auto negotiate  
A straight cable will not work -- you need a cross-over to work back to back.

-----Original Message-----
From: nishant mishra [mailto:community-noreply@qnx.com] 
Sent: October-21-11 5:21 AM
To: drivers-networking
Subject: Re: devn-i82544 not able to auto negotiate

Its working after using a switch
But not when connected directly through a straight cable 
Would you be able to point out what is the exact reason for it
Do you also suspect hardware or it only driver



_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post89519