[yocto] USB Ethernet problems
Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? Hans ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
Hello, Do you use connman as the network manager? From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Hans Beckérus Sent: Friday, April 05, 2013 12:08 PM To: yocto@yoctoproject.org Subject: [yocto] USB Ethernet problems Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? Hans ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
On 2013-04-05 03:08, Hans Beckérus wrote: Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? I run exactly this setup on many different platforms with no issues so it can definitely be done with Poky/Yocto. What system (target) are you using? What version of the metadata (Poky/Yocto) are you using? master? danny? etc How is your network device configured? -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
On Fri, Apr 5, 2013 at 12:08 PM, Iorga, Cristian cristian.io...@intel.comwrote: Hello, ** ** Do you use connman as the network manager? ** Since I do not know what that is, then I would say the answer is no ;) This is a very slimmed down ARM system, with a simple init.d script that brings up the networking. The other devices/buses are probed through the flattened device tree. What probably is needed is a networking script that either waits for the eth0 to become available or it must be started later. But I am not too sure starting it later will help though. Hans ** *From:* yocto-boun...@yoctoproject.org [mailto: yocto-boun...@yoctoproject.org] *On Behalf Of *Hans Beckérus *Sent:* Friday, April 05, 2013 12:08 PM *To:* yocto@yoctoproject.org *Subject:* [yocto] USB Ethernet problems ** ** Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? Hans ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas g...@mlbassoc.com wrote: On 2013-04-05 03:08, Hans Beckérus wrote: Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? I run exactly this setup on many different platforms with no issues so it can definitely be done with Poky/Yocto. What system (target) are you using? What version of the metadata (Poky/Yocto) are you using? master? danny? etc How is your network device configured? I am on branch master. My network device is *not* configured. That is the whole point/?problem?. The kernel knowns nothing about the NIC at boot. It is not detected until it first detects the USB 2.0 host adapter. Then after a few moments the NIC is probed and eth0 becomes available through the ASIX driver. But its too late, the /etc/init.d/networking is already done trying ifup :( Is there some configuration on network level I can do to fix this? Right now I have an ugly patch in /etc/init.d/networking that spins until eth0 comes up. It solves the sync issue, but also requires some sort of timeout to not get stuck forever if the device is never inserted :( Hans -- --**-- Gary Thomas | Consulting for the MLB Associates |Embedded world --**-- __**_ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
On 2013-04-05 06:38, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2013-04-05 03:08, Hans Beckérus wrote: Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? I run exactly this setup on many different platforms with no issues so it can definitely be done with Poky/Yocto. What system (target) are you using? What version of the metadata (Poky/Yocto) are you using? master? danny? etc How is your network device configured? I am on branch master. My network device is *not* configured. That is the whole point/?problem?. The kernel knowns nothing about the NIC at boot. It is not detected until it first detects the USB 2.0 host adapter. Then after a few moments the NIC is probed and eth0 becomes available through the ASIX driver. But its too late, the /etc/init.d/networking is already done trying ifup :( Is there some configuration on network level I can do to fix this? Right now I have an ugly patch in /etc/init.d/networking that spins until eth0 comes up. It solves the sync issue, but also requires some sort of timeout to not get stuck forever if the device is never inserted :( Is your ethernet driver compiled in or a kernel module? I'm using a compiled in driver (the same one BTW) and it works fine. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
On Fri, Apr 5, 2013 at 2:48 PM, Gary Thomas g...@mlbassoc.com wrote: On 2013-04-05 06:38, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas g...@mlbassoc.com mailto: g...@mlbassoc.com wrote: On 2013-04-05 03:08, Hans Beckérus wrote: Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? I run exactly this setup on many different platforms with no issues so it can definitely be done with Poky/Yocto. What system (target) are you using? What version of the metadata (Poky/Yocto) are you using? master? danny? etc How is your network device configured? I am on branch master. My network device is *not* configured. That is the whole point/?problem?. The kernel knowns nothing about the NIC at boot. It is not detected until it first detects the USB 2.0 host adapter. Then after a few moments the NIC is probed and eth0 becomes available through the ASIX driver. But its too late, the /etc/init.d/networking is already done trying ifup :( Is there some configuration on network level I can do to fix this? Right now I have an ugly patch in /etc/init.d/networking that spins until eth0 comes up. It solves the sync issue, but also requires some sort of timeout to not get stuck forever if the device is never inserted :( Is your ethernet driver compiled in or a kernel module? I'm using a compiled in driver (the same one BTW) and it works fine. It is compiled into the kernel. If you look at boot log I sent in the initial mail you can see that the actual ASIX device (D-Link DUB-E100) is detected much later than the host adapter :( How is it in your case? Maybe it is the actual device that is not responding quickly enough? Are you pre-configuring anything in your bootargs prepared from U-Boot for eth? Hans ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
On 2013-04-05 06:57, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 2:48 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2013-04-05 06:38, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2013-04-05 03:08, Hans Beckérus wrote: Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? I run exactly this setup on many different platforms with no issues so it can definitely be done with Poky/Yocto. What system (target) are you using? What version of the metadata (Poky/Yocto) are you using? master? danny? etc How is your network device configured? I am on branch master. My network device is *not* configured. That is the whole point/?problem?. The kernel knowns nothing about the NIC at boot. It is not detected until it first detects the USB 2.0 host adapter. Then after a few moments the NIC is probed and eth0 becomes available through the ASIX driver. But its too late, the /etc/init.d/networking is already done trying ifup :( Is there some configuration on network level I can do to fix this? Right now I have an ugly patch in /etc/init.d/networking that spins until eth0 comes up. It solves the sync issue, but also requires some sort of timeout to not get stuck forever if the device is never inserted :( Is your ethernet driver compiled in or a kernel module? I'm using a compiled in driver (the same one BTW) and it works fine. It is compiled into the kernel. If you look at boot log I sent in the initial mail you can see that the actual ASIX device (D-Link DUB-E100) is detected much later than the host adapter :( How is it in your case? Maybe it is the actual device that is not responding quickly enough? Are you pre-configuring anything in your bootargs prepared from U-Boot for eth? No, I don't do anything special at all. My boot log is attached. You can see that the interface (on the USB) is found quite early. That said, the system works fine even if I plug it in later on. You still did not show us your '/etc/network/interfaces' file. Mine contains these lines which make it handle the network device coming and going: # Wired interface (on optional board) auto eth0 iface eth0 inet dhcp -- Gary Thomas | Consulting for the MLB Associates |Embedded world SPL 2012.07-rc1-dirty (Mar 13 2013 - 13:26:04) OMAP4430 ES2.3 OMAP SD/MMC: 0 mmc_send_cmd : timeout: No status update U-Boot 2012.07-rc1-dirty (Mar 13 2013 - 13:26:04) CPU : OMAP4430 ES2.3 Board: OMAP4 Cobra4430p82 I2C: ready DRAM: 1 GiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment In:serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 mmc_send_cmd : timeout: No status update Card did not respond to voltage select! mmc1(part 0) is current device SD/MMC found on device 1 MMC: block number 0x1 exceeds max(0x0) ** Unable to use mmc 1:1 for fatload ** MMC: block number 0x1 exceeds max(0x0) ** Unable to use mmc 1:1 for fatload ** mmc_send_cmd : timeout: No status update mmc0(part 0) is current device SD/MMC found on device 0 reading uEnv.txt **
Re: [yocto] USB Ethernet problems
On Fri, Apr 5, 2013 at 3:27 PM, Gary Thomas g...@mlbassoc.com wrote: On 2013-04-05 07:23, Gary Thomas wrote: On 2013-04-05 06:57, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 2:48 PM, Gary Thomas g...@mlbassoc.com mailto: g...@mlbassoc.com wrote: On 2013-04-05 06:38, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas g...@mlbassoc.commailto: g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2013-04-05 03:08, Hans Beckérus wrote: Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? I run exactly this setup on many different platforms with no issues so it can definitely be done with Poky/Yocto. What system (target) are you using? What version of the metadata (Poky/Yocto) are you using? master? danny? etc How is your network device configured? I am on branch master. My network device is *not* configured. That is the whole point/?problem?. The kernel knowns nothing about the NIC at boot. It is not detected until it first detects the USB 2.0 host adapter. Then after a few moments the NIC is probed and eth0 becomes available through the ASIX driver. But its too late, the /etc/init.d/networking is already done trying ifup :( Is there some configuration on network level I can do to fix this? Right now I have an ugly patch in /etc/init.d/networking that spins until eth0 comes up. It solves the sync issue, but also requires some sort of timeout to not get stuck forever if the device is never inserted :( Is your ethernet driver compiled in or a kernel module? I'm using a compiled in driver (the same one BTW) and it works fine. It is compiled into the kernel. If you look at boot log I sent in the initial mail you can see that the actual ASIX device (D-Link DUB-E100) is detected much later than the host adapter :( How is it in your case? Maybe it is the actual device that is not responding quickly enough? Are you pre-configuring anything in your bootargs prepared from U-Boot for eth? No, I don't do anything special at all. My boot log is attached. You can see that the interface (on the USB) is found quite early. That said, the system works fine even if I plug it in later on. You still did not show us your '/etc/network/interfaces' file. Mine contains these lines which make it handle the network device coming and going: # Wired interface (on optional board) auto eth0 iface eth0 inet dhcp That is what I have. I use whatever default poky gave me ;) But looking at your log makes me wonder if your system simply are running a lot more other stuff causing networking to be delayed enough for the ASIX device to be probed before /etc/init.d/networking is executed? Also, this [1.999420] gadget: Ethernet Gadget, version: Memorial Day 2008 [2.005798] gadget: g_ether ready I have not added USB gadget interface support for Ethernet in my kernel. Do I really need it? I don't think that the ASIX is using that interface, is it not using the old classic USB device modell? Sorry for the extra noise in the log - I didn't realize that it was still on while I was checking the /etc/network/interfaces file... No problem ;) Hans ___ yocto mailing list yocto@yoctoproject.org
Re: [yocto] USB Ethernet problems
On 2013-04-05 07:50, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 3:27 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2013-04-05 07:23, Gary Thomas wrote: On 2013-04-05 06:57, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 2:48 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2013-04-05 06:38, Hans Beckérus wrote: On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: On 2013-04-05 03:08, Hans Beckérus wrote: Hi. In our configuration we do not have an on-board Ethernet device. It connected to the USB-host adapter. It seems that probing of such devices are done very late in the kernel boot-up which means it gets out of sync with the network init script(s) and the NIC thus has to be brought up manually after boot. ... usb 1-1: new high-speed USB device number 2 using xusbps-ehci hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected VFS: Mounted root (ext2 filesystem) on device 1:0. devtmpfs: mounted Freeing init memory: 152K INIT: version 2.88 booting usb 1-1.4: new high-speed USB device number 3 using xusbps-ehci Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device INIT: Entering runlevel: 5 Starting Dropbear SSH server: NET: Registered protocol family 10 dropbear. Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. asix 1-1.4:1.0: eth0: register 'asix' at usb-xusbps-ehci.0-1.4, ASIX AX88772 USB 2.0 Ethernet, fc:75:16:cf:6a:86 ... Is there some way to configure a system through Yocto to handle this scenario? I run exactly this setup on many different platforms with no issues so it can definitely be done with Poky/Yocto. What system (target) are you using? What version of the metadata (Poky/Yocto) are you using? master? danny? etc How is your network device configured? I am on branch master. My network device is *not* configured. That is the whole point/?problem?. The kernel knowns nothing about the NIC at boot. It is not detected until it first detects the USB 2.0 host adapter. Then after a few moments the NIC is probed and eth0 becomes available through the ASIX driver. But its too late, the /etc/init.d/networking is already done trying ifup :( Is there some configuration on network level I can do to fix this? Right now I have an ugly patch in /etc/init.d/networking that spins until eth0 comes up. It solves the sync issue, but also requires some sort of timeout to not get stuck forever if the device is never inserted :( Is your ethernet driver compiled in or a kernel module? I'm using a compiled in driver (the same one BTW) and it works fine. It is compiled into the kernel. If you look at boot log I sent in the initial mail you can see that the actual ASIX device (D-Link DUB-E100) is detected much later than the host adapter :( How is it in your case? Maybe it is the actual device that is not responding quickly enough? Are you pre-configuring anything in your bootargs prepared from U-Boot for eth? No, I don't do anything special at all. My boot log is attached. You can see that the interface (on the USB) is found quite early. That said, the system works fine even if I plug it in later on. You still did not show us your '/etc/network/interfaces' file. Mine contains these lines which make it handle the network device coming and going: # Wired interface (on optional board) auto eth0 iface eth0 inet
Re: [yocto] USB Ethernet problems
On Friday 05 April 2013 16:13:32 Hans Beckérus wrote: On Fri, Apr 5, 2013 at 3:59 PM, Gary Thomas g...@mlbassoc.com wrote: As for the timing, maybe I've just been very lucky :-) I can see that if the device isn't present when the system runs 'ifup eth0' (or the equivalent) you'll have a problem. That's what connman is for - I don't use it, but it might help you out. I should take a look at it. But it already sounds like something much bigger than this simple system should really need. Thanks for all the help so far. If anything else comes to your mind, please tell me. I guess I will have to live with my QD patch for now ;) One other possibility I can think of would be using a udev rule to run a script when the actual hardware detection/insertion event happens. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] USB Ethernet problems
On Fri, Apr 5, 2013 at 5:51 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Friday 05 April 2013 16:13:32 Hans Beckérus wrote: On Fri, Apr 5, 2013 at 3:59 PM, Gary Thomas g...@mlbassoc.com wrote: As for the timing, maybe I've just been very lucky :-) I can see that if the device isn't present when the system runs 'ifup eth0' (or the equivalent) you'll have a problem. That's what connman is for - I don't use it, but it might help you out. I should take a look at it. But it already sounds like something much bigger than this simple system should really need. Thanks for all the help so far. If anything else comes to your mind, please tell me. I guess I will have to live with my QD patch for now ;) One other possibility I can think of would be using a udev rule to run a script when the actual hardware detection/insertion event happens. Cheers, Paul Yea. In this case mdev. But I guess mdev as provided by poky/busybox should provide this facility too? But I can no see any mdev configuration files :( Hans ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
