Re: nm doesn't notice usb enet connect
On Thursday 09 November 2006 7:49 pm, Dan Williams wrote: > On Thu, 2006-11-09 at 06:40 -0500, Neal Becker wrote: > > Dan Williams wrote: > > > On Wed, 2006-11-08 at 21:44 -0500, Neal Becker wrote: > > >> My wired enet has a bad connection, so I bought a usb2 enet adapter. > > >> It works fine, but I think it points out a problem with nm. It seems > > >> nm doesn't notice the new adapter on eth2 if I plug it in after > > >> startup, unless I restart nm. > > > > > > Does your adapter use the ne2k driver or something? Does the driver do > > > link detection? NM certainly isn't going to use your adapter unless > > > the driver can do carrier detect. Try 'mii-tool eth0' when a cable is > > > plugged in, or or 'ethtool eth0' and look for the "Link detected: " > > > line. If your cable is in, but neither of those report a link, then > > > the driver likely needs fixing. > > > > > > For example, NM won't work automatically in QEMU because the ne2k_pci > > > driver that suports the NE2000 hardware that qemu emulates doesn't > > > support carrier detect. > > > > sudo /sbin/ethtool eth2 > > Settings for eth2: > > Supported ports: [ TP MII ] > > Supported link modes: 10baseT/Half 10baseT/Full > > 100baseT/Half 100baseT/Full > > Supports auto-negotiation: Yes > > Advertised link modes: 10baseT/Half 10baseT/Full > > 100baseT/Half 100baseT/Full > > Advertised auto-negotiation: Yes > > Speed: 100Mb/s > > Duplex: Full > > Port: MII > > PHYAD: 3 > > Transceiver: internal > > Auto-negotiation: on > > Supports Wake-on: pg > > Wake-on: d > > Current message level: 0x0007 (7) > > Link detected: yes > > > > Driver is asix > > device is d-link EUB-E100 > > Found a few these lying around, and got the problem in a quick test. > > One more thing to check; plug in a cable and do: > > cat /sys/class/net/eth2/carrier > > and see what that returns > OK, so you're saying you duplicated the problem? cat /sys/class/net/eth2/carrier 1 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm doesn't notice usb enet connect
On Thu, 2006-11-09 at 06:40 -0500, Neal Becker wrote: > Dan Williams wrote: > > > On Wed, 2006-11-08 at 21:44 -0500, Neal Becker wrote: > >> My wired enet has a bad connection, so I bought a usb2 enet adapter. It > >> works fine, but I think it points out a problem with nm. It seems nm > >> doesn't notice the new adapter on eth2 if I plug it in after startup, > >> unless I restart nm. > > > > Does your adapter use the ne2k driver or something? Does the driver do > > link detection? NM certainly isn't going to use your adapter unless the > > driver can do carrier detect. Try 'mii-tool eth0' when a cable is > > plugged in, or or 'ethtool eth0' and look for the "Link detected: " > > line. If your cable is in, but neither of those report a link, then the > > driver likely needs fixing. > > > > For example, NM won't work automatically in QEMU because the ne2k_pci > > driver that suports the NE2000 hardware that qemu emulates doesn't > > support carrier detect. > > > > sudo /sbin/ethtool eth2 > Settings for eth2: > Supported ports: [ TP MII ] > Supported link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > Supports auto-negotiation: Yes > Advertised link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > Advertised auto-negotiation: Yes > Speed: 100Mb/s > Duplex: Full > Port: MII > PHYAD: 3 > Transceiver: internal > Auto-negotiation: on > Supports Wake-on: pg > Wake-on: d > Current message level: 0x0007 (7) > Link detected: yes > > Driver is asix > device is d-link EUB-E100 Found a few these lying around, and got the problem in a quick test. One more thing to check; plug in a cable and do: cat /sys/class/net/eth2/carrier and see what that returns dan > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm doesn't notice usb enet connect
Dan Williams wrote: > On Wed, 2006-11-08 at 21:44 -0500, Neal Becker wrote: >> My wired enet has a bad connection, so I bought a usb2 enet adapter. It >> works fine, but I think it points out a problem with nm. It seems nm >> doesn't notice the new adapter on eth2 if I plug it in after startup, >> unless I restart nm. > > Does your adapter use the ne2k driver or something? Does the driver do > link detection? NM certainly isn't going to use your adapter unless the > driver can do carrier detect. Try 'mii-tool eth0' when a cable is > plugged in, or or 'ethtool eth0' and look for the "Link detected: " > line. If your cable is in, but neither of those report a link, then the > driver likely needs fixing. > > For example, NM won't work automatically in QEMU because the ne2k_pci > driver that suports the NE2000 hardware that qemu emulates doesn't > support carrier detect. > sudo /sbin/ethtool eth2 Settings for eth2: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 3 Transceiver: internal Auto-negotiation: on Supports Wake-on: pg Wake-on: d Current message level: 0x0007 (7) Link detected: yes Driver is asix device is d-link EUB-E100 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm doesn't notice usb enet connect
On Wed, 2006-11-08 at 21:44 -0500, Neal Becker wrote: > My wired enet has a bad connection, so I bought a usb2 enet adapter. It > works fine, but I think it points out a problem with nm. It seems nm > doesn't notice the new adapter on eth2 if I plug it in after startup, > unless I restart nm. Does your adapter use the ne2k driver or something? Does the driver do link detection? NM certainly isn't going to use your adapter unless the driver can do carrier detect. Try 'mii-tool eth0' when a cable is plugged in, or or 'ethtool eth0' and look for the "Link detected: " line. If your cable is in, but neither of those report a link, then the driver likely needs fixing. For example, NM won't work automatically in QEMU because the ne2k_pci driver that suports the NE2000 hardware that qemu emulates doesn't support carrier detect. Dan > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
nm doesn't notice usb enet connect
My wired enet has a bad connection, so I bought a usb2 enet adapter. It works fine, but I think it points out a problem with nm. It seems nm doesn't notice the new adapter on eth2 if I plug it in after startup, unless I restart nm. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
