USB Ethernet problems

USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1270 bytes --]

Re: USB Ethernet problems

[Iorga, Cristian]

[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]

Hello,

Do you use connman as the network manager?

From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@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


[-- Attachment #2: Type: text/html, Size: 4268 bytes --]

Re: USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]

On Fri, Apr 5, 2013 at 12:08 PM, Iorga, Cristian
<cristian.iorga@intel.com>wrote:

>  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-bounces@yoctoproject.org [mailto:
> yocto-bounces@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
>
> ****
>

[-- Attachment #2: Type: text/html, Size: 4212 bytes --]

Re: USB Ethernet problems

[Gary Thomas]

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
------------------------------------------------------------

Re: USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 2832 bytes --]

On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas <gary@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/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>

[-- Attachment #2: Type: text/html, Size: 3709 bytes --]

Re: USB Ethernet problems

[Gary Thomas]

On 2013-04-05 06:38, Hans Beckérus wrote:
>
>
> On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@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
------------------------------------------------------------

Re: USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 3325 bytes --]

On Fri, Apr 5, 2013 at 2:48 PM, Gary Thomas <gary@mlbassoc.com> wrote:

> On 2013-04-05 06:38, Hans Beckérus wrote:
>
>
>>
>> On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas <gary@mlbassoc.com <mailto:
>> gary@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

[-- Attachment #2: Type: text/html, Size: 3929 bytes --]

Re: USB Ethernet problems

[Gary Thomas]

[-- Attachment #1: Type: text/plain, Size: 4352 bytes --]

On 2013-04-05 06:57, Hans Beckérus wrote:
>
>
> On Fri, Apr 5, 2013 at 2:48 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
>     On 2013-04-05 06:38, Hans Beckérus wrote:
>
>
>
>         On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com <mailto:gary@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
------------------------------------------------------------

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: p82.log --]
[-- Type: text/x-log; name="p82.log", Size: 28175 bytes --]

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

** Unable to read "uEnv.txt" from mmc 0:1 **
reading uImage

3402352 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 84000000 ...
   Image Name:   Linux-3.4.27
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3402288 Bytes = 3.2 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Linux version 3.4.27 (gthomas@titan) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Wed Mar 20 11:05:55 MDT 2013
[    0.000000] CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: OMAP4 Cobra4430p82 board
[    0.000000] cma: CMA: reserved 8 MiB at 98800000
[    0.000000] cma: CMA: reserved 112 MiB at 99000000
[    0.000000] cma: CMA: reserved 32 MiB at ad800000
[    0.000000] cma: CMA: reserved 64 MiB at a9000000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] omap2_set_globals_tap
[    0.000000] OMAP4: Map 0xad600000 to 0xfe600000 for dram barrier
[    0.000000] omap2_set_globals_tap
[    0.000000] OMAP4430 ES2.3
[    0.000000] PERCPU: Embedded 8 pages/cpu @c0f6b000 s11008 r8192 d13568 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 259584
[    0.000000] Kernel command line: console=ttyO2,115200n8 mpurate=auto smsc95xx.macaddr=00:1d:11:95:42:c8 mem=1G@0x80000000 sierra.nmea=1 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 726MB 296MB = 1022MB total
[    0.000000] Memory: 808264k/808264k available, 240312k reserved, 270336K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0653000   (6444 kB)
[    0.000000]       .init : 0xc0653000 - 0xc06a5b00   ( 331 kB)
[    0.000000]       .data : 0xc06a6000 - 0xc070ffc8   ( 424 kB)
[    0.000000]        .bss : 0xc070ffec - 0xc0761980   ( 327 kB)
[    0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:524
[    0.000000] omap_sr_disable: omap_sr struct for sr_wakeup not found
[    0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[    0.000000] Console: colour dummy device 80x30
[    0.000213] Calibrating delay loop... 1590.23 BogoMIPS (lpj=6213632)
[    0.070343] pid_max: default: 32768 minimum: 301
[    0.070709] Mount-cache hash table entries: 512
[    0.072082] CPU: Testing write buffer coherency: ok
[    0.072174] ftrace: allocating 19474 entries in 58 pages
[    0.114959] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.115264] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.115386] Setting up static identity map for 0x804b1f18 - 0x804b1f70
[    0.115417] L310 cache controller enabled
[    0.115447] l2x0: 16 ways, CACHE_ID 0x410000c4, AUX_CTRL 0x5e470000, Cache size: 1048576 B
[    0.115447] omap_sar_ram_init
[    0.115692] generating sar_ram layout...
[    0.115905] sar ram layout created
[    0.193847] CPU1: Booted secondary processor
[    0.263702] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.263732] CPU1: Unknown IPI message 0x1
[    0.263732] Brought up 2 CPUs
[    0.263763] SMP: Total of 2 processors activated (3188.82 BogoMIPS).
[    0.264465] devtmpfs: initialized
[    0.269104] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269134] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269165] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269195] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269226] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269226] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269256] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.269287] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269317] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269348] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.269378] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269409] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.269470] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269500] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269531] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269561] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269622] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269653] omap_sr_disable: omap_sr struct for sr_core not found
[    0.269683] omap_sr_disable: omap_sr struct for sr_core not found
[    0.270507] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.270538] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.270660] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.270690] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.270721] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.273406] omap_hwmod: mcpdm: _wait_target_ready error: -16
[    0.273437] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.273437] omap_hwmod: mcpdm: cannot be enabled (3)
[    0.273712] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.273742] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.273773] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.273803] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.275085] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.276123] dummy: 
[    0.286163] NET: Registered protocol family 16
[    0.289672] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.290161] GPMC revision 6.0
[    0.293304] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.293365] OMAP GPIO hardware version 0.1
[    0.293609] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.293914] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.294219] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.294494] gpiochip_add: registered GPIOs 128 to 159 on device: gpio
[    0.294799] gpiochip_add: registered GPIOs 160 to 191 on device: gpio
[    0.296813] omap_mux_init: Add partition: #1: core, flags: 2
[    0.297790] omap_mux_init: Add partition: #2: wkup, flags: 2
[    0.298156] omap_mux_get_by_name: Could not find signal uart1_cts.uart1_cts
[    0.298187] omap_hwmod_mux_init: Could not allocate device mux entry
[    0.304534] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.304534] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.308685] Updated GPU clock source to be dpll_per_m7x2_ck
[    0.311401]  omap-mcbsp.1: alias pad_fck already exists
[    0.311645]  omap-mcbsp.2: alias pad_fck already exists
[    0.311920]  omap-mcbsp.3: alias pad_fck already exists
[    0.312164]  omap-mcbsp.4: alias pad_fck already exists
[    0.313385] OMAP DMA hardware revision 0.0
[    0.332427] bio: create slab <bio-0> at 0
[    0.334228] SCSI subsystem initialized
[    0.334655] omap2_mcspi omap2_mcspi.1: master is unqueued, this is deprecated
[    0.335327] omap2_mcspi omap2_mcspi.2: master is unqueued, this is deprecated
[    0.335662] omap2_mcspi omap2_mcspi.3: master is unqueued, this is deprecated
[    0.335998] omap2_mcspi omap2_mcspi.4: master is unqueued, this is deprecated
[    0.336456] usbcore: registered new interface driver usbfs
[    0.336639] usbcore: registered new interface driver hub
[    0.336822] usbcore: registered new device driver usb
[    0.337982] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 400 kHz
[    0.338775] Skipping twl internal clock init and using bootloader value (unknown osc rate)
[    0.339263] twl 1-0048: PIH (irq 39) chaining IRQs 416..436
[    0.339996] VUSB: 3300 mV normal standby
[    0.342895] twl6030_usb twl6030_usb: Initialized TWL6030 USB module
[    0.344329] V1V8: 1800 mV normal standby
[    0.344757] V2V1: 2100 mV normal standby
[    0.345336] VMMC: 1200 <--> 3000 mV at 3000 mV normal standby
[    0.346038] VPP: 1800 <--> 2500 mV at 1900 mV normal standby
[    0.346862] VCXIO: 1800 mV normal standby
[    0.346862] VCXIO: supplied by V2V1
[    0.347839] VDAC: 1800 mV normal standby
[    0.347869] VDAC: supplied by V2V1
[    0.348724] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal standby
[    0.349426] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal standby
[    0.350219] CLK32KG: 
[    0.350616] VANA: 2100 mV normal standby
[    0.351013] omap_i2c omap_i2c.2: bus 2 rev2.4.0 at 400 kHz
[    0.351287] omap_i2c omap_i2c.3: bus 3 rev2.4.0 at 400 kHz
[    0.351593] omap_i2c omap_i2c.4: bus 4 rev2.4.0 at 400 kHz
[    0.352020] Linux media interface: v0.10
[    0.352142] Linux video capture interface: v2.00
[    0.353057] omap-iommu omap-iommu.0: dsp registered
[    0.353118] omap-iommu omap-iommu.1: ipu registered
[    0.353668] Advanced Linux Sound Architecture Driver Version 1.0.25.
[    0.354705] Switching to clocksource 32k_counter
[    0.387817] NET: Registered protocol family 2
[    0.388061] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.388580] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.390472] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
[    0.391906] TCP: Hash tables configured (established 131072 bind 65536)
[    0.391906] TCP: reno registered
[    0.391906] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.391967] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.392242] NET: Registered protocol family 1
[    0.392547] RPC: Registered named UNIX socket transport module.
[    0.392578] RPC: Registered udp transport module.
[    0.392578] RPC: Registered tcp transport module.
[    0.392578] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.392730] usbhs_omap usbhs_omap: ehci_logic_fck failed:-2
[    0.426086]  omap-rproc.1: alias fck already exists
[    0.427032] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.427093] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.427185] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.427246] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.430053] highmem bounce pool size: 64 pages
[    0.440093] VFS: Disk quotas dquot_6.5.2
[    0.440490] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.444000] NFS: Registering the id_resolver key type
[    0.444732] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.444793] msgmni has been set to 1482
[    0.445678] io scheduler noop registered
[    0.445709] io scheduler deadline registered
[    0.445983] io scheduler cfq registered (default)
[    0.447265] OMAP DSS rev 4.0
[    0.449584] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.451202] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0
[    0.451629] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1
[    0.452026] omap_uart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2
[    1.521392] console [ttyO2] enabled
[    1.525482] omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3
[    1.533752] [drm] Initialized drm 1.1.0 20060810
[    1.548583] brd: module loaded
[    1.557037] loop: module loaded
[    1.563476] tun: Universal TUN/TAP device driver, 1.6
[    1.568847] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.575836] usbcore: registered new interface driver asix
[    1.581695] usbcore: registered new interface driver smsc75xx
[    1.587921] usbcore: registered new interface driver smsc95xx
[    1.594207] usbcore: registered new interface driver sierra_net
[    1.600463] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.607543] ehci-omap.0 supply hsusb0 not found, using dummy regulator
[    1.614654] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[    1.620666] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
[    1.630615] ehci-omap ehci-omap.0: irq 109, io mem 0x4a064c00
[    1.651672] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[    1.657897] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.665100] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.672729] usb usb1: Product: OMAP-EHCI Host Controller
[    1.678344] usb usb1: Manufacturer: Linux 3.4.27 ehci_hcd
[    1.684051] usb usb1: SerialNumber: ehci-omap.0
[    1.689605] hub 1-0:1.0: USB hub found
[    1.693603] hub 1-0:1.0: 3 ports detected
[    1.722106] Initializing USB Mass Storage driver...
[    1.727447] usbcore: registered new interface driver usb-storage
[    1.733825] USB Mass Storage support registered.
[    1.739013] usbcore: registered new interface driver usbserial
[    1.745178] usbserial: USB Serial Driver core
[    1.749938] usbcore: registered new interface driver sierra
[    1.755981] USB Serial support registered for Sierra USB modem
[    1.762176] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    1.970153] musb-hdrc musb-hdrc: USB OTG mode controller at fc0ab000 using DMA, IRQ 124
[    1.978973]  gadget: using random self ethernet address
[    1.984527]  gadget: using random host ethernet address
[    1.990783] usb0: MAC de:b4:b4:a3:fc:33
[    1.994842] usb0: HOST MAC b6:b3:47:dc:4c:ed
[    1.999420]  gadget: Ethernet Gadget, version: Memorial Day 2008
[    2.005798]  gadget: g_ether ready
[    2.026672] usb 1-1: new high-speed USB device number 2 using ehci-omap
[    2.183258] usb 1-1: New USB device found, idVendor=2001, idProduct=f103
[    2.190338] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.198638] hub 1-1:1.0: USB hub found
[    2.202728] hub 1-1:1.0: 7 ports detected
[    2.209960] musb-hdrc musb-hdrc: MUSB HDRC host driver
[    2.215423] musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 2
[    2.223175] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    2.230377] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.238006] usb usb2: Product: MUSB HDRC host driver
[    2.243255] usb usb2: Manufacturer: Linux 3.4.27 musb-hcd
[    2.248962] usb usb2: SerialNumber: musb-hdrc
[    2.254272] hub 2-0:1.0: USB hub found
[    2.258239] hub 2-0:1.0: 1 port detected
[    2.292846] mousedev: PS/2 mouse device common for all mice
[    2.298828] spi1.0 supply vcc not found, using dummy regulator
[    2.305450] ads7846 spi1.0: touchscreen, irq 221
[    2.311035] input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi_master/spi1/spi1.0/input/input0
[    2.322296] twl6030_pwrbutton_probe: Enter
[    2.327026] input: twl6030_pwrbutton as /devices/platform/omap_i2c.1/i2c-1/1-0049/twl6030_pwrbutton/input/input1
[    2.339172] twl_rtc twl_rtc: Power up reset detected.
[    2.345336] twl_rtc twl_rtc: Enabling TWL-RTC
[    2.353118] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
[    2.359832] i2c /dev entries driver
[    2.365631] omap_hsmmc.1 supply vmmc not found, using dummy regulator
[    2.372497] omap_hsmmc.1 supply vmmc_aux not found, using dummy regulator
[    2.488800] omap_hsmmc omap_hsmmc.1: could not set regulator OCR (-22)
[    2.497924] omap_hsmmc.0 supply vmmc_aux not found, using dummy regulator
[    2.505371] usb 1-1.2: new high-speed USB device number 3 using ehci-omap
[    2.623901] usbcore: registered new interface driver usbhid
[    2.630096] usbhid: USB HID core driver
[    2.634521] OMAPRPC: Registration of OMAPRPC rpmsg service returned 0! debug=0
[    2.642242] thermal_governor_dev_register:Adding omap_ondie_governor governor
[    2.649841] usb 1-1.2: config 1 has an invalid interface number: 7 but max is 5
[    2.657592] thermal_get_slope:Getting slope is not supported for domain cpu
[    2.665161] usb 1-1.2: config 1 has no interface number 5
[    2.671936] thermal_get_offset:Getting offset is not supported for domain cpu
[    2.681579] thermal_governor_dev_register:Adding omap_ongpu_governor governor
[    2.689270] thermal_get_slope:Getting slope is not supported for domain gpu
[    2.696777] thermal_get_offset:Getting offset is not supported for domain gpu
[    2.705078] usb 1-1.2: New USB device found, idVendor=1199, idProduct=68a3
[    2.712402] rproc remoteproc0: dsp_c0 is available
[    2.714172] usb 1-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[    2.714202] usb 1-1.2: Product: MC7710
[    2.714202] usb 1-1.2: Manufacturer: Sierra Wireless, Incorporated
[    2.714202] usb 1-1.2: SerialNumber: 358178040038889
[    2.741027] rproc remoteproc0: Note: remoteproc is still under development and considered experimental.
[    2.751037] rproc remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    2.751434] sierra 1-1.2:1.0: Sierra USB modem converter detected
[    2.769287] rproc remoteproc1: ipu_c0 is available
[    2.774414] rproc remoteproc1: Note: remoteproc is still under development and considered experimental.
[    2.774810] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB0
[    2.775329] sierra 1-1.2:1.1: Sierra USB modem converter detected
[    2.798004] rproc remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    2.812164] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB1
[    2.820007] sierra 1-1.2:1.2: Sierra USB modem converter detected
[    2.822540] OMAP4/5 SoC init
[    2.822540] omap_pcm_dummy() init
[    2.822540] omap_mcpdm_dummy() init
[    2.823242] aess aess: ABE Firmware version 9560
[    2.825439] omap_sr_disable: omap_sr struct for sr_iva not found
[    2.849456] omap_sr_disable: omap_sr struct for sr_iva not found
[    2.856414] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB2
[    2.867950] asoc: snd-soc-dummy-dai <-> MultiMedia1 mapping ok
[    2.874389] sierra 1-1.2:1.3: Sierra USB modem converter detected
[    2.882049] asoc: snd-soc-dummy-dai <-> MultiMedia2 mapping ok
[    2.888702] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB3
[    2.896850] sierra 1-1.2:1.4: Sierra USB modem converter detected
[    2.904937] asoc: snd-soc-dummy-dai <-> Voice mapping ok
[    2.910614] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB4
[    2.919311] asoc: snd-soc-dummy-dai <-> Tones mapping ok
[    2.925659] sierra_net 1-1.2:1.7: wwan0: register 'sierra_net' at usb-ehci-omap.0-1.2, Sierra Wireless USB-to-WWAN Modem, 12:5f:ef:c7:01:07
[    2.926544] asoc: snd-soc-dummy-dai <-> Vibra mapping ok
[    2.926940] asoc: snd-soc-dummy-dai <-> MODEM mapping ok
[    2.927215] asoc: snd-soc-dummy-dai <-> MultiMedia1 LP mapping ok
[    2.927429] asoc: snd-soc-dummy-dai <-> omap-mcbsp.2 mapping ok
[    2.965270] asoc: twl6040-legacy <-> mcpdm-legacy mapping ok
[    2.969085] mmc0: new high speed MMC card at address 0001
[    2.977050] mmcblk0: mmc0:0001 SEM32G 29.7 GiB 
[    2.977661] asoc: twl6040-dl1 <-> mcpdm-dl1 mapping ok
[    2.977874] asoc: twl6040-ul <-> mcpdm-ul1 mapping ok
[    2.978088] asoc: twl6040-dl2 <-> mcpdm-dl2 mapping ok
[    2.978271] asoc: twl6040-vib <-> mcpdm-vib mapping ok
[    2.978515] asoc: snd-soc-dummy-dai <-> omap-mcbsp.1 mapping ok
[    2.978698] asoc: snd-soc-dummy-dai <-> omap-mcbsp.1 mapping ok
[    2.978881] asoc: snd-soc-dummy-dai <-> omap-mcbsp.2 mapping ok
[    2.979095] asoc: snd-soc-dummy-dai <-> omap-mcbsp.2 mapping ok
[    2.980255] input: Cobra4430p82 Headset Jack as /devices/platform/omap-abe-twl6040/sound/card0/input2
[    2.984527] oprofile: using arm/armv7-ca9
[    2.984771] IPv4 over IPv4 tunneling driver
[    2.985595] TCP: cubic registered
[    2.985626] NET: Registered protocol family 17
[    2.985687] NET: Registered protocol family 40
[    3.059570] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    3.062713] mmcblk0boot0: mmc0:0001 SEM32G partition 1 2.00 MiB
[    3.074279] mmcblk0boot1: mmc0:0001 SEM32G partition 2 2.00 MiB
[    3.074371] ThumbEE CPU extension supported.
[    3.074401] Registering SWP/SWPB emulation handler
[    3.091430]  mmcblk0: p1 p2 p3 p4
[    3.092346] omap_sr_disable: omap_sr struct for sr_mpu not found
[    3.092376] omap_sr_disable: omap_sr struct for sr_core not found
[    3.108062] Power Management for TI OMAP4XX/OMAP5XXX devices.
[    3.114440] hwmod gpmc not found
[    3.117980] sr_init: No PMIC hook to init smartreflex
[    3.120544] usb 1-1.4: new high-speed USB device number 4 using ehci-omap
[    3.130798] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
[    3.139282] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
[    3.147705] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized
[    3.156127] SmartReflex Class3 initialized
[    3.161773] omap4iss omap4iss: Revision 40000101 found
[    3.163848]  mmcblk0boot1: unknown partition table
[    3.172393] omap4iss omap4iss: ISP Revision 40000100 found
[    3.174011]  mmcblk0boot0: unknown partition table
[    3.184631] ov5640 3-003c: XVCLK set to rounded aproximate (19200000 Hz)
[    3.193878] ov5640 3-003c: Detected a OV5640 chip, revision 0
[    3.232604] tvp5150 3-005c: chip found @ 0xb8 (OMAP I2C adapter)
[    3.253082] usb 1-1.4: New USB device found, idVendor=2001, idProduct=3c05
[    3.260375] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.268157] usb 1-1.4: Product: DUB-E100
[    3.272399] usb 1-1.4: Manufacturer: D-Link Corporation
[    3.277954] usb 1-1.4: SerialNumber: 000001
[    3.347167] tvp5150 3-005c: tvp5150am1 detected.
[    3.354492] cma: CMA: reserved 64 MiB at a5000000
[    3.363861] clock: disabling unused clocks to save power
[    3.370483] registered taskstats version 1
[    3.375244] VANA: incomplete constraints, leaving on
[    3.381561] VDAC: incomplete constraints, leaving on
[    3.387573] VMMC: incomplete constraints, leaving on
[    3.393188] VUSB: incomplete constraints, leaving on
[    3.399139] input: gpio-keys as /devices/platform/gpio-keys/input/input3
[    3.407501] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
[    3.422454] dmm dmm: initialized all PAT entries
[    3.433654] [drm] Enabling DMM ywrap scrolling
[    3.442932] Console: switching to colour frame buffer device 40x30
[    3.450561] fb0: omapdrm frame buffer device
[    3.455108] drm: registered panic notifier
[    3.459472] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    3.466552] [drm] No driver support for vblank timestamp query.
[    3.472808] [drm] Initialized omapdrm 1.0.0 20110917 on minor 0
[    3.479309] ALSA device list:
[    3.482482]   #0: Cobra4430p82
[    3.760314] asix 1-1.4:1.0: eth0: register 'asix' at usb-ehci-omap.0-1.4, ASIX AX88772 USB 2.0 Ethernet, 00:80:c8:3b:76:ab
[    4.049285] kjournald starting.  Commit interval 5 seconds
[    4.051849] EXT3-fs (mmcblk0p2): using internal journal
[    4.054168] EXT3-fs (mmcblk0p2): recovery complete
[    4.054168] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
[    4.054199] VFS: Mounted root (ext3 filesystem) on device 179:2.
[    4.054931] devtmpfs: mounted
[    4.055175] Freeing init memory: 328K
INIT: version 2.88 booting
Starting udev
[    4.354034] udevd[856]: starting version 182
Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory
bootlogd.
[    7.069366] Adding 2096476k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 across:2096476k SS
Configuring network interfaces... [    7.639373] rproc remoteproc1: powering up ipu_c0
[    7.677124] rproc remoteproc1: Booting fw image ducati-m3-core0.xem3, size 3595847
[    7.685577] omap-iommu omap-iommu.1: ipu: version 2.1
[    7.994873] rproc remoteproc1: remote processor ipu_c0 is now up
[    8.004333] virtio_rpmsg_bus virtio0: rpmsg host is online
[    8.010162] rproc remoteproc1: registered virtio0 (type 7)
udhcpc (v1.20.2) started
Sending discover...
[    8.458435] omap-rproc omap-rproc.1: received echo reply from ipu_c0
[    8.465301] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x32
[    8.474121] virtio_rpmsg_bus virtio0: creating channel rpmsg-dce addr 0x2a
[    8.482360] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x33
[    9.961395] asix 1-1.4:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
Sending discover...
Sending select for 10.0.0.213...
Lease of 10.0.0.213 obtained, lease time 600
/etc/udhcpc.d/50default: Adding DNS 192.168.12.1
/etc/udhcpc.d/50default: Adding DNS 10.0.0.1
done.
Starting DHCP server: .
Thu Apr  4 20:34:00 UTC 2013
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting Xserver
Starting Dropbear SSH server: 
cat /etc/netroot@cobra4430p82:~# cat /etc/network/inroot@cobra4430p82:~# cat /etc/network/interfaces 
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
 
# The loopback interface
auto lo
iface lo inet loopback

# Wired interface (on optional board)
auto eth0
face eth0 inet dhcp

# Wireless via Sierra Wireless 3G Modem
iface wwan0 inet dhcp
    pre-up /etc/modem.py IP on

# USB ethernet
auto usb0
iface usb0 inet static
      address 192.168.211.1
      netmask 255.255.255.0


root@cobra4430p82:~# vi /etc/netroot@cobra4430p82:~# vi /etc/network/inroot@cobra4430p82:~# vi /etc/network/interfaces 
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# Wired interface (on optional board)
auto eth0
face eth0 inet dhcp

# Wireless via Sierra Wireless 3G Modem
iface wwan0 inet dhcp
    pre-up /etc/modem.py IP on

# USB ethernet
auto usb0
iface usb0 inet staticaddress 192.168.211.1netmask 255.255.255.0


~
~- /etc/network/interfaces 1/21 4%
- /etc/network/interfaces 2/21 9%
- /etc/network/interfaces 3/21 14%
- /etc/network/interfaces 4/21 19%
- /etc/network/interfaces 5/21 23%
- /etc/network/interfaces 6/21 28%
- /etc/network/interfaces 7/21 33%
- /etc/network/interfaces 8/21 38%face eth0 inet dhcp
                   
# Wireless via Sierra Wireless 3G Modem
iface wwan0 inet dhcp                  
    pre-up /etc/modem.py IP on
                              
# USB ethernet
auto usb0     
iface usb0 inet static
      address 192.168.211.1netmask 255.255.255.0                     

~Delete 1 lines (10 chars) using [D]- /etc/network/interfaces [Modified] 8/20 40%I /etc/network/interfaces [Modified] 8/20 40%iface eth0 inet dhcpi- /etc/network/interfaces [Modified] 8/20 40%root@cobra4430p82:~# 

Re: USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 5320 bytes --]

On Fri, Apr 5, 2013 at 3:27 PM, Gary Thomas <gary@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 <gary@mlbassoc.com <mailto:
>>> gary@mlbassoc.com>> wrote:
>>>
>>>     On 2013-04-05 06:38, Hans Beckérus wrote:
>>>
>>>
>>>
>>>         On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas <gary@mlbassoc.com<mailto:
>>> gary@mlbassoc.com> <mailto:gary@mlbassoc.com <mailto:gary@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

[-- Attachment #2: Type: text/html, Size: 6618 bytes --]

Re: USB Ethernet problems

[Gary Thomas]

On 2013-04-05 07:50, Hans Beckérus wrote:
>
>
> On Fri, Apr 5, 2013 at 3:27 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@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 <gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com <mailto:gary@mlbassoc.com>>> wrote:
>
>                  On 2013-04-05 06:38, Hans Beckérus wrote:
>
>
>
>                      On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com <mailto:gary@mlbassoc.com>>
>             <mailto:gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com <mailto:gary@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?

No, this is only for OTG support which is not needed for you to use
the ASIX device.

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.

>
>
>     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
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 6927 bytes --]

On Fri, Apr 5, 2013 at 3:59 PM, Gary Thomas <gary@mlbassoc.com> wrote:

> On 2013-04-05 07:50, Hans Beckérus wrote:
>
>>
>>
>> On Fri, Apr 5, 2013 at 3:27 PM, Gary Thomas <gary@mlbassoc.com <mailto:
>> gary@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 <
>> gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com<mailto:
>> gary@mlbassoc.com>>> wrote:
>>
>>                  On 2013-04-05 06:38, Hans Beckérus wrote:
>>
>>
>>
>>                      On Fri, Apr 5, 2013 at 12:16 PM, Gary Thomas <
>> gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:gary@mlbassoc.com<mailto:
>> gary@mlbassoc.com>>
>>             <mailto:gary@mlbassoc.com <mailto:gary@mlbassoc.com> <mailto:
>> gary@mlbassoc.com <mailto:gary@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?
>>
>
> No, this is only for OTG support which is not needed for you to use
> the ASIX device.
>
> Correct. I have no use for ever leaving host mode on this system so OTG is
most likely overkill.


> 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 Q&D patch for now ;)

Hans

[-- Attachment #2: Type: text/html, Size: 8498 bytes --]

Re: USB Ethernet problems

[Paul Eggleton]

On Friday 05 April 2013 16:13:32 Hans Beckérus wrote:
> On Fri, Apr 5, 2013 at 3:59 PM, Gary Thomas <gary@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 Q&D 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

Re: USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On Fri, Apr 5, 2013 at 5:51 PM, Paul Eggleton <paul.eggleton@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 <gary@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 Q&D 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

[-- Attachment #2: Type: text/html, Size: 1669 bytes --]

Re: USB Ethernet problems

[Hans Beckérus]

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

On Fri, Apr 5, 2013 at 6:16 PM, Hans Beckérus <hans.beckerus@gmail.com>wrote:

>
>
> On Fri, Apr 5, 2013 at 5:51 PM, Paul Eggleton <
> paul.eggleton@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 <gary@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 Q&D 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 :(
>
> Ah. Found it in busybox config.
CONFIG_FEATURE_MDEV_CONF=y should do the trick.
Also CONFIG_FEATURE_MDEV_EXEC is needed to run a script I think.

Hans

[-- Attachment #2: Type: text/html, Size: 2283 bytes --]