eth1 on netDUO not working
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
eth1 on netDUO not working
by gordu
::
Rate this Message:
I just got a connex400, netduo card and a console-st. the problem I am having is I cannot get eth1 to come up. I have un-commented the lines in /etc/network/interfaces for eth1, the interface is detected at boot time
<3>gumstix_smc91x_init: smc91x chip found <3>gumstix_smc91x_init: found 2 smc91x chip(s) <4>smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org> <4>eth0: SMC91C11xFD (rev 2) at c4870300 IRQ 59 DMA 8 [nowait] <4>eth0: Ethernet addr: 06:45:69:b9:8e:90 <7>eth0: PHY LAN83C183 (LAN91C111 Internal) <4>eth1: SMC91C11xFD (rev 2) at c4872300 IRQ 50 DMA 9 [nowait] <4>eth1: Ethernet addr: 06:45:69:b9:8e:91 <7>eth1: PHY LAN83C183 (LAN91C111 Internal) Then later eth0 comes up ok udhcpc (v1.2.1) started> udhcpc[576]: udhcpc (v1.2.1) started Sending discover... udhcpc[576]: Sending discover... eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 Sending discover... udhcpc[576]: Sending discover... Sending select for 172.23.6.167... udhcpc[576]: Sending select for 172.23.6.167... Lease of 172.23.6.167 obtained, lease time 604800 udhcpc[576]: Lease of 172.23.6.167 obtained, lease time 604800 adding dns 172.23.0.200 adding dns 172.23.0.235 adding dns 172.23.0.239 Auto negotiation NOT supported However eth1 is another story... eth1 no wireless extensions. udhcpc (v1.2.1) started udhcpc[612]: udhcpc (v1.2.1) started Sending discover... udhcpc[612]: Sending discover... NETDEV WATCHDOG: eth1: transmit timed out Auto negotiation NOT supported Sending discover... udhcpc[612]: Sending discover... NETDEV WATCHDOG: eth1: transmit timed out Auto negotiation NOT supported Sending discover... udhcpc[612]: Sending discover... NETDEV WATCHDOG: eth1: transmit timed out Auto negotiation NOT supported No lease, failing. udhcpc[612]: No lease, failing. done. Nothing to be done I get no link light, nothing. I've swapped the cable from eth0 with eth1 (so I know the cable etc is fine) and still no link light. ifconfig shows eth0 Link encap:Ethernet HWaddr 06:45:69:B9:8E:90 inet addr:172.23.6.167 Bcast:172.23.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2306 errors:0 dropped:0 overruns:0 frame:0 TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:198278 (193.6 KiB) TX bytes:7897 (7.7 KiB) Interrupt:59 Base address:0x300 DMA chan:8 eth1 Link encap:Ethernet HWaddr 06:45:69:B9:8E:91 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:3 dropped:0 overruns:0 carrier:3 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:50 Base address:0x2300 DMA chan:9 The NETDEV WATCHDOG timeouts I'm guessing are coming because the SMC is not responding to a TX, but other than that I'm out of ideas. A final note, eth1 has not worked since I received the card. |
|
|
Re: eth1 on netDUO not working
by Chuck Randall
::
Rate this Message:
gordu,
I was in the same boat a few weeks ago, but resolved it. Can you post the contents of your /etc/network/interfaces file? Chuck On Jul 15, 2008, at 1:55 PM, gordu wrote: > > I just got a connex400, netduo card and a console-st. the problem > I am > having is I cannot get eth1 to come up. I have un-commented the > lines in > /etc/network/interfaces for eth1, the interface is detected at boot > time > > <3>gumstix_smc91x_init: smc91x chip found > <3>gumstix_smc91x_init: found 2 smc91x chip(s) > <4>smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@...> > <4>eth0: SMC91C11xFD (rev 2) at c4870300 IRQ 59 DMA 8 [nowait] > <4>eth0: Ethernet addr: 06:45:69:b9:8e:90 > <7>eth0: PHY LAN83C183 (LAN91C111 Internal) > <4>eth1: SMC91C11xFD (rev 2) at c4872300 IRQ 50 DMA 9 [nowait] > <4>eth1: Ethernet addr: 06:45:69:b9:8e:91 > <7>eth1: PHY LAN83C183 (LAN91C111 Internal) > > Then later eth0 comes up ok > > udhcpc (v1.2.1) started> > udhcpc[576]: udhcpc (v1.2.1) started > Sending discover... > udhcpc[576]: Sending discover... > eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 > Sending discover... > udhcpc[576]: Sending discover... > Sending select for 172.23.6.167... > udhcpc[576]: Sending select for 172.23.6.167... > Lease of 172.23.6.167 obtained, lease time 604800 > udhcpc[576]: Lease of 172.23.6.167 obtained, lease time 604800 > adding dns 172.23.0.200 > adding dns 172.23.0.235 > adding dns 172.23.0.239 > Auto negotiation NOT supported > > However eth1 is another story... > > > eth1 no wireless extensions. > udhcpc (v1.2.1) started > udhcpc[612]: udhcpc (v1.2.1) started > Sending discover... > udhcpc[612]: Sending discover... > NETDEV WATCHDOG: eth1: transmit timed out > Auto negotiation NOT supported > Sending discover... > udhcpc[612]: Sending discover... > NETDEV WATCHDOG: eth1: transmit timed out > Auto negotiation NOT supported > Sending discover... > udhcpc[612]: Sending discover... > NETDEV WATCHDOG: eth1: transmit timed out > Auto negotiation NOT supported > No lease, failing. > udhcpc[612]: No lease, failing. > done. > Nothing to be done > > > I get no link light, nothing. I've swapped the cable from eth0 with > eth1 > (so I know the cable etc is fine) and still no link light. ifconfig > shows > > eth0 Link encap:Ethernet HWaddr 06:45:69:B9:8E:90 > inet addr:172.23.6.167 Bcast:172.23.255.255 Mask: > 255.255.0.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2306 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:198278 (193.6 KiB) TX bytes:7897 (7.7 KiB) > Interrupt:59 Base address:0x300 DMA chan:8 > > eth1 Link encap:Ethernet HWaddr 06:45:69:B9:8E:91 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:3 dropped:0 overruns:0 carrier:3 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:50 Base address:0x2300 DMA chan:9 > > The NETDEV WATCHDOG timeouts I'm guessing are coming because the SMC > is not > responding to a TX, but other than that I'm out of ideas. A final > note, eth1 > has not worked since I received the card. > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
|
Re: eth1 on netDUO not working
by gordu
::
Rate this Message:
Chuck
I saw your post but it seemed like you were having issues with your startup scripts, anyhow here is my interfaces file. Also I have tried configuring the interface manually after boot again with no success. I'm inclined to believe this is a hardware issue since I can manually configure eth0 and it works but the same manual config for eth1 does not. Also as far as the system is concerned the interface is up and configured, it just never detects link. Also /proc/net/dev shows nothing other than 3 errors on the transmit side of eth1 and /proc/interrupts shows 0 interrupts for eth1. gord u # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # auto lo iface lo inet loopback # # Wired interfaces # auto eth0 iface eth0 inet dhcp # if netduo attached uncomment lines below auto eth1 iface eth1 inet dhcp # # Wireless interfaces # # Example of an unencrypted (no WEP or WPA) wireless connection # that connects to any available access point: # ##auto wlan0 ##iface wlan0 inet dhcp ## wireless_mode managed ## wireless_essid any # Example of an unencrypted (no WEP or WPA) wireless connection # that is locked to a specific access point: # #iface wlan0 inet dhcp # wireless_mode managed # wireless-essid some-essid # Example of a WEP encrypted connection locked to a specific access point: # #iface wlan0 inet dhcp # pre-up /sbin/iwconfig $IFACE key 03AB30A4EF8A71A4781DA1CB84 key open essid gumstixnet txpower 100mW # Example of a WPA1 or WPA2 encrypted connection locked to a specific access point. # # You will also need to create a /etc/wpa_supplicant.conf file: # Copy / paste the results of this command into that file : # wpa_passphrase myssid mypasswordhere # #iface wlan0 inet dhcp # pre-up wpa_supplicant -Dmarvell -iwlan0 -c/etc/wpa_supplicant.conf -Bw # down killall wpa_supplicant # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr ##iface usb0 inet static ## address 192.168.0.202 ## netmask 255.255.255.0 ## network 192.168.0.0 ## gateway 192.168.0.200 # Bluetooth networking ##iface bnep0 inet dhcp On Tue, Jul 15, 2008 at 2:43 PM, Chuck Randall <shibboleth@...> wrote: gordu, ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
|
Re: eth1 on netDUO not working
by Chuck Randall
::
Rate this Message:
You say it appears the interface is up and configured. What does the
output of ifconfig look like when it is in this state? When you configure them with DHCP, you need to be connected to a DHCP server to set the ports and have them become active. Chuck On Jul 15, 2008, at 3:11 PM, Gord Urquhart wrote: > Chuck > I saw your post but it seemed like you were having issues with > your startup scripts, anyhow here is my interfaces file. Also I have > tried configuring the interface manually after boot again with no > success. I'm inclined to believe this is a hardware issue since I > can manually configure eth0 and it works but the same manual config > for eth1 does not. Also as far as the system is concerned the > interface is up and configured, it just never detects link. > > Also /proc/net/dev shows nothing other than 3 errors on the transmit > side of eth1 and /proc/interrupts shows 0 interrupts for eth1. > > gord u > > > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) > > # The loopback interface > # > auto lo > iface lo inet loopback > > # > # Wired interfaces > # > > auto eth0 > iface eth0 inet dhcp > > # if netduo attached uncomment lines below > auto eth1 > iface eth1 inet dhcp > > # > # Wireless interfaces > # > > # Example of an unencrypted (no WEP or WPA) wireless connection > # that connects to any available access point: > # > ##auto wlan0 > ##iface wlan0 inet dhcp > ## wireless_mode managed > ## wireless_essid any > > # Example of an unencrypted (no WEP or WPA) wireless connection > # that is locked to a specific access point: > # > #iface wlan0 inet dhcp > # wireless_mode managed > # wireless-essid some-essid > > # Example of a WEP encrypted connection locked to a specific access > point: > # > #iface wlan0 inet dhcp > # pre-up /sbin/iwconfig $IFACE key 03AB30A4EF8A71A4781DA1CB84 key > open essid gumstixnet txpower 100mW > > # Example of a WPA1 or WPA2 encrypted connection locked to a > specific access point. > # > # You will also need to create a /etc/wpa_supplicant.conf file: > # Copy / paste the results of this command into that file : > # wpa_passphrase myssid mypasswordhere > # > #iface wlan0 inet dhcp > # pre-up wpa_supplicant -Dmarvell -iwlan0 -c/etc/ > wpa_supplicant.conf -Bw > # down killall wpa_supplicant > > # Ethernet/RNDIS gadget (g_ether) > # ... or on host side, usbnet and random hwaddr > ##iface usb0 inet static > ## address 192.168.0.202 > ## netmask 255.255.255.0 > ## network 192.168.0.0 > ## gateway 192.168.0.200 > > # Bluetooth networking > ##iface bnep0 inet dhcp > > > > > > > On Tue, Jul 15, 2008 at 2:43 PM, Chuck Randall <shibboleth@... > > wrote: > gordu, > > I was in the same boat a few weeks ago, but resolved it. > Can you post the contents of your /etc/network/interfaces file? > > Chuck > > > On Jul 15, 2008, at 1:55 PM, gordu wrote: > > > > > I just got a connex400, netduo card and a console-st. the problem > > I am > > having is I cannot get eth1 to come up. I have un-commented the > > lines in > > /etc/network/interfaces for eth1, the interface is detected at boot > > time > > > > <3>gumstix_smc91x_init: smc91x chip found > > <3>gumstix_smc91x_init: found 2 smc91x chip(s) > > <4>smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@...> > > <4>eth0: SMC91C11xFD (rev 2) at c4870300 IRQ 59 DMA 8 [nowait] > > <4>eth0: Ethernet addr: 06:45:69:b9:8e:90 > > <7>eth0: PHY LAN83C183 (LAN91C111 Internal) > > <4>eth1: SMC91C11xFD (rev 2) at c4872300 IRQ 50 DMA 9 [nowait] > > <4>eth1: Ethernet addr: 06:45:69:b9:8e:91 > > <7>eth1: PHY LAN83C183 (LAN91C111 Internal) > > > > Then later eth0 comes up ok > > > > udhcpc (v1.2.1) started> > > udhcpc[576]: udhcpc (v1.2.1) started > > Sending discover... > > udhcpc[576]: Sending discover... > > eth0: link up, 100Mbps, half-duplex, lpa 0x40A1 > > Sending discover... > > udhcpc[576]: Sending discover... > > Sending select for 172.23.6.167... > > udhcpc[576]: Sending select for 172.23.6.167... > > Lease of 172.23.6.167 obtained, lease time 604800 > > udhcpc[576]: Lease of 172.23.6.167 obtained, lease time 604800 > > adding dns 172.23.0.200 > > adding dns 172.23.0.235 > > adding dns 172.23.0.239 > > Auto negotiation NOT supported > > > > However eth1 is another story... > > > > > > eth1 no wireless extensions. > > udhcpc (v1.2.1) started > > udhcpc[612]: udhcpc (v1.2.1) started > > Sending discover... > > udhcpc[612]: Sending discover... > > NETDEV WATCHDOG: eth1: transmit timed out > > Auto negotiation NOT supported > > Sending discover... > > udhcpc[612]: Sending discover... > > NETDEV WATCHDOG: eth1: transmit timed out > > Auto negotiation NOT supported > > Sending discover... > > udhcpc[612]: Sending discover... > > NETDEV WATCHDOG: eth1: transmit timed out > > Auto negotiation NOT supported > > No lease, failing. > > udhcpc[612]: No lease, failing. > > done. > > Nothing to be done > > > > > > I get no link light, nothing. I've swapped the cable from > eth0 with > > eth1 > > (so I know the cable etc is fine) and still no link light. ifconfig > > shows > > > > eth0 Link encap:Ethernet HWaddr 06:45:69:B9:8E:90 > > inet addr:172.23.6.167 Bcast:172.23.255.255 Mask: > > 255.255.0.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:2306 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:198278 (193.6 KiB) TX bytes:7897 (7.7 KiB) > > Interrupt:59 Base address:0x300 DMA chan:8 > > > > eth1 Link encap:Ethernet HWaddr 06:45:69:B9:8E:91 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:3 dropped:0 overruns:0 carrier:3 > > collisions:0 txqueuelen:1000 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > Interrupt:50 Base address:0x2300 DMA chan:9 > > > > The NETDEV WATCHDOG timeouts I'm guessing are coming because the SMC > > is not > > responding to a TX, but other than that I'm out of ideas. A final > > note, eth1 > > has not worked since I received the card. > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
|
Re: eth1 on netDUO not working
by gordu
::
Rate this Message:
Chuck
You actually don't need to have a valid ip address for the ports to become active, otherwise you would never be able to get an address from DHCP. Here are my ifconfig outputs (In this case I have manually configured eth0 to have no address (but it is up and working) and eth1 to have a static address not working eth0 Link encap:Ethernet HWaddr 06:45:69:B9:8E:90 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:89103 errors:67 dropped:0 overruns:67 frame:0 TX packets:223 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7344824 (7.0 MiB) TX bytes:21463 (20.9 KiB) Interrupt:59 Base address:0x300 DMA chan:8 eth1 Link encap:Ethernet HWaddr 06:45:69:B9:8E:91 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:3 dropped:0 overruns:0 carrier:3 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:50 Base address:0x2300 DMA chan:9 gord u On Tue, Jul 15, 2008 at 4:01 PM, Chuck Randall <shibboleth@...> wrote: You say it appears the interface is up and configured. What does the ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
|
Re: eth1 on netDUO not working
by gordu
::
Rate this Message:
Well I've figured it out sorta...doing a
modprobe -r smc91x followed by reinstalling the module modprobe smc91x fixes things. Now the question is why is the module getting hooped in the first place. gord u On Tue, Jul 15, 2008 at 4:26 PM, Gord Urquhart <gordurq@...> wrote:
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
| Free Forum Powered by Nabble | Forum Help |