FS#5296 - beyond kernel is breaking my usb audio device

Attached to Project: Arch Linux
Opened by Greg Meyer (oggb4mp3) - Sunday, 27 August 2006, 17:27 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 01 September 2006, 08:16 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To James Rayner (iphitus)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My usb-audio device does not work with the beyond kernel (2.6.17.beyond3-1). The snd-usb-audio module loads properly and the device is recognized as an alsa device in /proc/asound/cards, but all apps report the device as busy. using the stock Arch kernel (2.6.17.11-1) it works fine. The alsa guys won't help because it works fine in the stock kernel.
This task depends upon

Closed by  James Rayner (iphitus)
Sunday, 03 December 2006, 09:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.6.19-beyond1... should be fixed now.
Comment by Greg Meyer (oggb4mp3) - Sunday, 27 August 2006, 17:52 GMT
I have reviewed the beyond patchset, and I don't see anything applied directly to snd-usb-audio, but since I am not really good at mucking around in kernel sources, I don't know where to look next or what additional info I could provide to help debug this. I will say that at one point I did have trouble with the vanilla kernel, but this was fixed at some point. I had posted a bug over at alsa-project bugtracker, but it was closed because it was working in the mainline kernel. Here is the link to the alsa bug https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1874
Comment by James Rayner (iphitus) - Friday, 01 September 2006, 22:54 GMT
you sure it's beyond kernel? was it a once off or is it repeatable every boot?

sounds like theres just a program hogging the sound card.
Comment by Greg Meyer (oggb4mp3) - Saturday, 02 September 2006, 00:36 GMT
Well, it happens every boot, and it works fine with the standard kernel and no other cnfiguration change. If I simply reboot with the current kernel26 it works fine.
Comment by Dawid Wróbel (cromo) - Thursday, 26 October 2006, 14:51 GMT
Could be that stock kernel26 was newer (2.6.17.11) than beyond3, which is 2.6.17.7 in fact?
Comment by Greg Meyer (oggb4mp3) - Thursday, 26 October 2006, 15:14 GMT
Well, this has been going on for awhile now, the same problem occurred with the ck kernel before beyond became part of the kernel family. I see that beyond is now stale and ck has made a reappearance, so it's probably a good time to test it again.
Comment by Dawid Wróbel (cromo) - Thursday, 26 October 2006, 15:24 GMT
Since beyond includes ck patchset as well, I guess this is not directly related to beyond patchset itself. Try to test other kernels and than write the results here.
Comment by Greg Meyer (oggb4mp3) - Friday, 27 October 2006, 12:31 GMT
I tried 2.6.18.1-ck and it works again. I hesitate to close this though, because although beyond has not been updated for 2.6.18.1, it hasn't been dropped from the distro yet. If we get a future update to the beyond kernel, I'll be sure to test again.

Loading...