From: The Source <thesourcehim@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [REGRESSION] SB X-Fi Notebook stopped working in 1.0.23
Date: Wed, 21 Apr 2010 13:00:32 +0400 [thread overview]
Message-ID: <4BCEBEB0.2080702@gmail.com> (raw)
In-Reply-To: <4BCEBCDE.8030207@gmail.com>
21.04.2010 12:52, The Source пишет:
> 21.04.2010 12:49, The Source пишет:
>> 21.04.2010 10:53, Clemens Ladisch пишет:
>>> The Source wrote:
>>>
>>>> This device works fine with 1.0.22.1 driver, but doesn't with 1.0.23.
>>>> snd-usb-audio& Ko are loaded but to no good. alsamixer doesn't
>>>> list the
>>>> device and no device files in /dev/snd.
>>>>
>>> When the driver doesn't attach, it should log some error message(s) to
>>> the system log.
>>>
>>>
>>> Regards,
>>> Clemens
>>>
>>>
>>
>> usb 8-2: new full speed USB device using uhci_hcd and address 2
>> usb 8-2: New USB device found, idVendor=041e, idProduct=30d2
>> usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>> usb 8-2: Product: SB X-Fi Notebook
>> usb 8-2: Manufacturer: Creative Technology Ltd
>> usb 8-2: configuration #1 chosen from 1 choice
>> input: Creative Technology Ltd SB X-Fi Notebook as
>> /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2:1.3/input/input11
>> generic-usb 0003:041E:30D2.0002: input,hidraw1: USB HID v1.11 Device
>> [Creative Technology Ltd SB X-Fi Notebook] on usb-0000:00:1d.2-2/input3
>> input: Creative Technology Ltd SB X-Fi Notebook as
>> /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2:1.4/input/input12
>> generic-usb 0003:041E:30D2.0003: input,hidraw2: USB HID v1.11
>> Keyboard [Creative Technology Ltd SB X-Fi Notebook] on
>> usb-0000:00:1d.2-2/input4
>> ALSA pcm.c:174: 2:1:1: endpoint lacks sample rate attribute bit,
>> cannot set.
>> ALSA pcm.c:174: 2:2:1: endpoint lacks sample rate attribute bit,
>> cannot set.
>>
>> P.S. Another strange glitch - with 1.0.23 strange things start to
>> happen, for example, bash hust hangs on exit and system becomes slow.
> Ok, the glitch happens because after inserting the card and getting
> those dmesg messages modprobe never exits and eats 100% CPU.
And that's what dmesg says with 1.0.22.1 when the card works fine:
usb 8-2: Product: SB X-Fi Notebook
usb 8-2: Manufacturer: Creative Technology Ltd
usb 8-2: configuration #1 chosen from 1 choice
input: Creative Technology Ltd SB X-Fi Notebook as
/devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2:1.3/input/input11
generic-usb 0003:041E:30D2.0002: input,hidraw1: USB HID v1.11 Device
[Creative Technology Ltd SB X-Fi Notebook] on usb-0000:00:1d.2-2/input3
input: Creative Technology Ltd SB X-Fi Notebook as
/devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2:1.4/input/input12
generic-usb 0003:041E:30D2.0003: input,hidraw2: USB HID v1.11 Keyboard
[Creative Technology Ltd SB X-Fi Notebook] on usb-0000:00:1d.2-2/input4
usbcore: registered new interface driver snd-usb-audio
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2010-04-21 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 20:17 [REGRESSION] SB X-Fi Notebook stopped working in 1.0.23 The Source
2010-04-21 6:53 ` Clemens Ladisch
2010-04-21 8:49 ` The Source
2010-04-21 8:52 ` The Source
2010-04-21 9:00 ` The Source [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BCEBEB0.2080702@gmail.com \
--to=thesourcehim@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.