Hi,
I'm playing around with the daily snapshots. Currently I'm using the snapshot from 20100929 on an EBVBeagle C2.
In order to see home exactly I'm cooking it you can look here: http://ebvbeagle.blogspot.com/2010/09/linaro-on-beagle.html
It comes up more or less happily, but as soon as I connect either my mcs7830 based USB to ethernet adapter, my USB mouse, or my USB keyboard to the USB hub I don't see anything happening.
No logs from the kernel buffer and no udev events with udevadm monitor.
With some old Angstrom image I have lying around I can see the events.
With Linaro it looks like udev is running.
Either me or the image is missing something.
Is it time to recompile the kernel and/or write some udev rules, or does this image try to use some other mechanism for hot plugging I'm not aware of?
Regards,
Robert
On Wed, Sep 29, 2010 at 10:21:54PM +0300, Robert Berger wrote:
In order to see home exactly I'm cooking it you can look here: http://ebvbeagle.blogspot.com/2010/09/linaro-on-beagle.html
Oh, this is pretty neat. Thanks for the post!
It comes up more or less happily, but as soon as I connect either my mcs7830 based USB to ethernet adapter, my USB mouse, or my USB keyboard to the USB hub I don't see anything happening.
What does lsusb tell you?
I have a similar problem, but ironically with Angstrom on my IGEPv2. It says this when nothing is plugged in:
root@igep0020:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Bus 002 Device 001: ID 1d6b:0002
If I plug in a keyboard, I get:
[ 130.771484] hub 1-0:1.0: unable to enumerate USB device on 1
on the serial console, and of course it doesn't work.
With some old Angstrom image I have lying around I can see the events.
I suspect you will also get different lsusb results, though. And does the keyboard work ?
On Wed, Sep 29, 2010, Christian Robottom Reis wrote:
What does lsusb tell you?
I have a similar problem, but ironically with Angstrom on my IGEPv2. It says this when nothing is plugged in:
root@igep0020:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Bus 002 Device 001: ID 1d6b:0002If I plug in a keyboard, I get:
[ 130.771484] hub 1-0:1.0: unable to enumerate USB device on 1on the serial console, and of course it doesn't work.
Isn't the EHCI port USB 2 only?
Hi,
Le 30/09/2010 02:42, Christian Robottom Reis a écrit :
I have a similar problem, but ironically with Angstrom on my IGEPv2. It says this when nothing is plugged in:
root@igep0020:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Bus 002 Device 001: ID 1d6b:0002If I plug in a keyboard, I get:
[ 130.771484] hub 1-0:1.0: unable to enumerate USB device on 1
if that's like on the Beagleboard, you need a USB hub to be able to use Low/Full speed USB devices : http://elinux.org/BeagleBoard#EHCI
Eric
Hi,
On 09/30/2010 04:03 AM, Eric Bénard wrote:
Hi,
Le 30/09/2010 02:42, Christian Robottom Reis a écrit :
I have a similar problem, but ironically with Angstrom on my IGEPv2. It says this when nothing is plugged in:
root@igep0020:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Bus 002 Device 001: ID 1d6b:0002If I plug in a keyboard, I get:
[ 130.771484] hub 1-0:1.0: unable to enumerate USB device on 1if that's like on the Beagleboard, you need a USB hub to be able to use Low/Full speed USB devices : http://elinux.org/BeagleBoard#EHCI
Just for completeness. I do use a (powered) USB hub and my setup works under Angstrom.
That's my output from Angstrom before and after plugging a keyboard:
beagleboard login: root root@beagleboard:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Bus 002 Device 001: ID 1d6b:0002 Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB root@beagleboard:~# usb 2-1: reset high speed USB device using musb_hdrc and address 2 usb 2-1.2: new low speed USB device using musb_hdrc and address 3 usb 2-1.2: device v0603 p00f2 is not supported usb 2-1.2: configuration #1 chosen from 1 choice input: NOVATEK USB Keyboard as /class/input/input2 generic-usb 0003:0603:00F2.0001: input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-musb_hdrc-1.2/input0 input: NOVATEK USB Keyboard as /class/input/input3 generic-usb 0003:0603:00F2.0002: input: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-musb_hdrc-1.2/input1
root@beagleboard:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Bus 002 Device 001: ID 1d6b:0002 Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 002 Device 003: ID 0603:00f2 Novatek Microelectronics Corp. root@beagleboard:~#
So the hardware setup should not be the problem in my case.
Regards,
Robert
Eric
..."Arguing that Java is better than C++ is like arguing that grasshoppers taste better than tree bark." - Thant Tessman
My public pgp key is available at: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
Hi,
On 09/30/2010 03:42 AM, Christian Robottom Reis wrote:
On Wed, Sep 29, 2010 at 10:21:54PM +0300, Robert Berger wrote:
In order to see home exactly I'm cooking it you can look here: http://ebvbeagle.blogspot.com/2010/09/linaro-on-beagle.html
Oh, this is pretty neat. Thanks for the post!
You're welcome.
It comes up more or less happily, but as soon as I connect either my mcs7830 based USB to ethernet adapter, my USB mouse, or my USB keyboard to the USB hub I don't see anything happening.
What does lsusb tell you?
No much either;)
Last login: Sat Jan 1 00:00:06 UTC 2000 on ttyS2 Linux localhost.localdomain 2.6.35-1006-linaro-omap #12-Ubuntu Tue Sep 21 20:09:17 UTC 2010 armv7l GNU/Linux Linaro M (development branch)
Welcome to Linaro! * Documentation: https://wiki.linaro.org/ root@localhost:~# lsusb -bash: lsusb: command not found root@localhost:~#
Regards,
Robert...Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining.
My public pgp key is available at: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
On Thu, Sep 30, 2010 at 06:46:47AM +0300, Robert Berger wrote:
Welcome to Linaro!
- Documentation: https://wiki.linaro.org/
root@localhost:~# lsusb -bash: lsusb: command not found root@localhost:~#
Oh that's annoying. I'll file a bug on linaro-images to get usbutils included. Can you find a way to get that package installed into the image meanwhile to see what output it shows?
Alternatively, you could look inside /proc and /sys to find out if the kernel is picking up the device at all.
-
Christian Robottom Reis -
Eric Bénard -
Loïc Minier -
Robert Berger