On Sun, Nov 3, 2013 at 11:34 AM, Daniel Mack <zonque@xxxxxxxxx> wrote: > If it's not listen in lsusb, it's not an ALSA problem. Are you > completely sure about that? Can you double-check with another machine maybe? > > Are there any dmesg messages added when the device is plugged in? Well, it works with this machine with ubuntu 12.04 :) I do have a spare laptop, but it does not boot from cd (broken) nor from usb stick (too old machine...) :) Anyway, jsaarela@Paranoid:~$ dmesg | tail; lsusb [ 15.309813] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 18.152299] wlan0: authenticate with ac:22:0b:ba:44:e8 [ 18.167515] wlan0: send auth to ac:22:0b:ba:44:e8 (try 1/3) [ 18.169063] wlan0: authenticated [ 18.171753] wlan0: associate with ac:22:0b:ba:44:e8 (try 1/3) [ 18.175848] wlan0: RX AssocResp from ac:22:0b:ba:44:e8 (capab=0x411 status=0 aid=2) [ 18.176020] wlan0: associated [ 18.176075] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 18.254434] init: plymouth-stop pre-start process (1446) terminated with status 1 [ 19.810168] init: cups-browsed main process ended, respawning Bus 002 Device 002: ID 064e:e263 Suyin Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub plug in the keyboard: jsaarela@Paranoid:~$ dmesg | tail; lsusb [ 15.309813] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 18.152299] wlan0: authenticate with ac:22:0b:ba:44:e8 [ 18.167515] wlan0: send auth to ac:22:0b:ba:44:e8 (try 1/3) [ 18.169063] wlan0: authenticated [ 18.171753] wlan0: associate with ac:22:0b:ba:44:e8 (try 1/3) [ 18.175848] wlan0: RX AssocResp from ac:22:0b:ba:44:e8 (capab=0x411 status=0 aid=2) [ 18.176020] wlan0: associated [ 18.176075] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 18.254434] init: plymouth-stop pre-start process (1446) terminated with status 1 [ 19.810168] init: cups-browsed main process ended, respawning Bus 002 Device 002: ID 064e:e263 Suyin Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub jsaarela@Paranoid:~$ Modprobing snd-usb-audio manually does not help either. Nor plugging kbd in and turning it on after plugging, or leaving kbd on and just plugging it in. Plugging a usb memory stick to same port produces expected results, stick is visible at dmesg and lsusb, and it can be mounted, so the port itself should be quite ok. So something is clearly broken somewhere, but as I don't have slightest idea how the current usb subsystem should work I really don't know where to start looking. - Jyrki ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
