I have a network interface on my laptop which was working (don't know when it stopped cause I mainly use WIFI) and now fails to connect. I have NM for network and when I plug the UTP cable (doesn't matter where I do this, it's always the same) I get this on /var/log/messages:
Mar 25 15:51:05 xxx kernel: [ 570.065930] TCP: lp registered Mar 25 15:51:07 xxx kernel: [ 571.722755] forcedeth 0000:00:0a.0: eth1: link up Mar 25 15:51:07 xxx kernel: [ 571.723094] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Mar 25 15:51:07 xxx NetworkManager[871]: <info> (eth1): carrier now ON (device state 20) Mar 25 15:51:07 xxx NetworkManager[871]: <info> (eth1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
NM says "Not connected".
At boot time I have these relevant lines.
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): carrier is OFF Mar 25 15:41:57 xxx kernel: [ 22.397119] 8021q: 802.1Q VLAN Support v1.8 Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): new Ethernet device (driver: 'forcedeth' ifindex: 2) Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0 Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): now managed Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): bringing up device. Mar 25 15:41:57 xxx kernel: [ 22.402806] forcedeth 0000:00:0a.0: eth1: MSI enabled Mar 25 15:41:57 xxx kernel: [ 22.403016] forcedeth 0000:00:0a.0: eth1: no link during initialization Mar 25 15:41:57 xxx kernel: [ 22.403741] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Mar 25 15:41:57 xxx dbus-daemon[884]: modem-manager[951]: <info> ModemManager (version 0.5.3.96-1.fc16) starting... Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): preparing device. Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): deactivating device (reason 'managed') [2]
What can the problem be?
Martín Marqués writes:
I have a network interface on my laptop which was working (don't know when it stopped cause I mainly use WIFI) and now fails to connect. I have NM for network and when I plug the UTP cable (doesn't matter where I do this, it's always the same) I get this on /var/log/messages:
Mar 25 15:41:57 xxx kernel: [ 22.403016] forcedeth 0000:00:0a.0: eth1: no link during initialization
Some googling around suggests that you might have some luck by:
1) Plugging into a different port on your router, or 2) Trying a different cable.
Both ends of a CAT cable are not really "identical", and that's why most routers have a single "upstream" or "uplink" ports, where some pins are switcherooed. Adding to the confusion is that some CAT cables might be crossover, rather than straight through. I also have the impression that most hardware, at least GigE, might not really care, and autonegotiate who is what, with its peer, when they connect to each other.
Try plugging the cable into your hub/router's "uplink" or "upstream" port, if it's not connected to anything.
2013/3/26 Sam Varshavchik mrsam@courier-mta.com:
Martín Marqués writes:
I have a network interface on my laptop which was working (don't know when it stopped cause I mainly use WIFI) and now fails to connect. I have NM for network and when I plug the UTP cable (doesn't matter where I do this, it's always the same) I get this on /var/log/messages:
Mar 25 15:41:57 xxx kernel: [ 22.403016] forcedeth 0000:00:0a.0: eth1: no link during initialization
Some googling around suggests that you might have some luck by:
- Plugging into a different port on your router, or
- Trying a different cable.
Both ends of a CAT cable are not really "identical", and that's why most routers have a single "upstream" or "uplink" ports, where some pins are switcherooed. Adding to the confusion is that some CAT cables might be crossover, rather than straight through. I also have the impression that most hardware, at least GigE, might not really care, and autonegotiate who is what, with its peer, when they connect to each other.
Try plugging the cable into your hub/router's "uplink" or "upstream" port, if it's not connected to anything.
Nop, nothing. Connection doesn't come up, not even at connections where I used to connect without any trouble (tried at home, at work and at College)
OK, just tested something:
Plugged the ethernet cable, ethernet device came up (ifconfig shows it, but with no IP address) so I dhclient it and the IP comes up and eth1 is now connected and configured.
So the problem is with NM not doing it's work. Any ideas?
2013/3/26 Martín Marqués martin.marques@gmail.com:
2013/3/26 Sam Varshavchik mrsam@courier-mta.com:
Martín Marqués writes:
I have a network interface on my laptop which was working (don't know when it stopped cause I mainly use WIFI) and now fails to connect. I have NM for network and when I plug the UTP cable (doesn't matter where I do this, it's always the same) I get this on /var/log/messages:
Mar 25 15:41:57 xxx kernel: [ 22.403016] forcedeth 0000:00:0a.0: eth1: no link during initialization
Some googling around suggests that you might have some luck by:
- Plugging into a different port on your router, or
- Trying a different cable.
Both ends of a CAT cable are not really "identical", and that's why most routers have a single "upstream" or "uplink" ports, where some pins are switcherooed. Adding to the confusion is that some CAT cables might be crossover, rather than straight through. I also have the impression that most hardware, at least GigE, might not really care, and autonegotiate who is what, with its peer, when they connect to each other.
Try plugging the cable into your hub/router's "uplink" or "upstream" port, if it's not connected to anything.
Nop, nothing. Connection doesn't come up, not even at connections where I used to connect without any trouble (tried at home, at work and at College)
-- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador
martin.
I don't know enough to speak about NM, as well as dhclient and how each app works with each other. I thought NM was supposed to auto handle dhclient issues.
What version of Fed, what version of NM, and dhclient?
On Tue, Mar 26, 2013 at 1:22 PM, Martín Marqués martin.marques@gmail.com wrote:
OK, just tested something:
Plugged the ethernet cable, ethernet device came up (ifconfig shows it, but with no IP address) so I dhclient it and the IP comes up and eth1 is now connected and configured.
So the problem is with NM not doing it's work. Any ideas?
2013/3/26 Martín Marqués martin.marques@gmail.com:
2013/3/26 Sam Varshavchik mrsam@courier-mta.com:
Martín Marqués writes:
I have a network interface on my laptop which was working (don't know when it stopped cause I mainly use WIFI) and now fails to connect. I have NM for network and when I plug the UTP cable (doesn't matter where I do this, it's always the same) I get this on /var/log/messages:
Mar 25 15:41:57 xxx kernel: [ 22.403016] forcedeth 0000:00:0a.0: eth1: no link during initialization
Some googling around suggests that you might have some luck by:
- Plugging into a different port on your router, or
- Trying a different cable.
Both ends of a CAT cable are not really "identical", and that's why most routers have a single "upstream" or "uplink" ports, where some pins are switcherooed. Adding to the confusion is that some CAT cables might be crossover, rather than straight through. I also have the impression that most hardware, at least GigE, might not really care, and autonegotiate who is what, with its peer, when they connect to each other.
Try plugging the cable into your hub/router's "uplink" or "upstream" port, if it's not connected to anything.
Nop, nothing. Connection doesn't come up, not even at connections where I used to connect without any trouble (tried at home, at work and at College)
-- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador
-- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
2013/3/26 bruce badouglas@gmail.com:
martin.
I don't know enough to speak about NM, as well as dhclient and how each app works with each other. I thought NM was supposed to auto handle dhclient issues.
What version of Fed, what version of NM, and dhclient?
All is the latest versions of Fedora 16 (yes, I know it's gonna die sone)
On 3/26/2013 2:17 PM, Martín Marqués wrote:
2013/3/26 bruce badouglas@gmail.com:
martin.
I don't know enough to speak about NM, as well as dhclient and how each app works with each other. I thought NM was supposed to auto handle dhclient issues.
What version of Fed, what version of NM, and dhclient?
All is the latest versions of Fedora 16 (yes, I know it's gonna die sone)
Already did.
https://lists.fedoraproject.org/pipermail/announce/2013-February/003144.html
2013/3/26 David dgboles@gmail.com:
On 3/26/2013 2:17 PM, Martín Marqués wrote:
2013/3/26 bruce badouglas@gmail.com:
martin.
I don't know enough to speak about NM, as well as dhclient and how each app works with each other. I thought NM was supposed to auto handle dhclient issues.
What version of Fed, what version of NM, and dhclient?
All is the latest versions of Fedora 16 (yes, I know it's gonna die sone)
Already did.
https://lists.fedoraproject.org/pipermail/announce/2013-February/003144.html
OK, I'm running preupgrade right now, but I want to know why NM isn't calling dhclient.
Else, I might upgrade and end up with the same problem, + some new ones.
-
bruce -
David -
Martín Marqués -
Sam Varshavchik