Hi List, been chasing my tail for the last two hours and getting nowhere on my wifes laptop. I only do updates monthly on her machine, as it is safely behind firewalls and only does email and browser stuff. I have never had audio problems on this laptop, Centos just worked from day one - even the wireless.
It appears that the 5.5 kernels and related audio driver snd-hda-intel do not function. If I reboot into 2.6.18-164.15.1.el5.centos.plus all is well. $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0x80000000 irq 169 1 [U0x46d0x804 ]: USB-Audio - USB Device 0x46d:0x804 USB Device 0x46d:0x804 at usb-0000:00:1d.7-3, high speed
Neither 2.6.18-194.3.1.el5.centos.plus or 2.6.18-194.8.1.el5.centos.plus have functioning sound. on these kernels I get $ cat /proc/asound/cards 0 [U0x46d0x804 ]: USB-Audio - USB Device 0x46d:0x804 USB Device 0x46d:0x804 at usb-0000:00:1d.7-3, high speed
yet lsmod shows <snip> snd_hda_intel 472337 0 snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_pcm_oss 42817 0 snd_usb_audio 77761 2 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72133 3 snd_hda_intel,snd_pcm_oss,snd_usb_audio snd_usb_lib 19137 1 snd_usb_audio snd_rawmidi 26561 1 snd_usb_lib snd_timer 24517 2 snd_seq,snd_pcm snd_page_alloc 14281 2 snd_hda_intel,snd_pcm snd_seq_device 11725 4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi snd_hwdep 12869 2 snd_hda_intel,snd_usb_audio snd 55749 15 snd_hda_intel,snd_seq_oss,snd_seq,snd_pcm_oss,snd_usb_audio,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_timer,snd_seq_device,snd_hwdep soundcore 11553 1 snd
So I remembered the bug rh introduced with the 194 kernels and nvidia chipsets (not my case but I'm desperate) and added the enable_msi=0 so that my modprobe.conf is now <snip> options snd cards_limit=8 alias snd-card-0 snd-hda-intel options snd-hda-intel index=0 enable_msi=0
but it still will not work. <rant> I am getting frustrated at the retrograde steps that seem to be hitting kernel and 5.x upgrades lately. yum update used to just work, get me the latest patches and all was well - after all that is why I use Centos. </rant> I have tried modprobe -r to remove and reload module but to no avail. Anyone have any ideas as to what I try next? Google has not given me any ideas yet. TIA
Rob Kampen wrote:
Hi List, been chasing my tail for the last two hours and getting nowhere on my wifes laptop. I only do updates monthly on her machine, as it is safely behind firewalls and only does email and browser stuff. I have never had audio problems on this laptop, Centos just worked from day one - even the wireless.
It appears that the 5.5 kernels and related audio driver snd-hda-intel do not function. If I reboot into 2.6.18-164.15.1.el5.centos.plus all is well. $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0x80000000 irq 169 1 [U0x46d0x804 ]: USB-Audio - USB Device 0x46d:0x804 USB Device 0x46d:0x804 at usb-0000:00:1d.7-3, high speed
Neither 2.6.18-194.3.1.el5.centos.plus or 2.6.18-194.8.1.el5.centos.plus have functioning sound. on these kernels I get $ cat /proc/asound/cards 0 [U0x46d0x804 ]: USB-Audio - USB Device 0x46d:0x804 USB Device 0x46d:0x804 at usb-0000:00:1d.7-3, high speed
yet lsmod shows
<snip> snd_hda_intel 472337 0 snd_seq_dummy 7877 0 snd_seq_oss 32577 0 snd_seq_midi_event 11073 1 snd_seq_oss snd_seq 49585 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_pcm_oss 42817 0 snd_usb_audio 77761 2 snd_mixer_oss 19009 1 snd_pcm_oss snd_pcm 72133 3 snd_hda_intel,snd_pcm_oss,snd_usb_audio snd_usb_lib 19137 1 snd_usb_audio snd_rawmidi 26561 1 snd_usb_lib snd_timer 24517 2 snd_seq,snd_pcm snd_page_alloc 14281 2 snd_hda_intel,snd_pcm snd_seq_device 11725 4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi snd_hwdep 12869 2 snd_hda_intel,snd_usb_audio snd 55749 15 snd_hda_intel,snd_seq_oss,snd_seq,snd_pcm_oss,snd_usb_audio,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_timer,snd_seq_device,snd_hwdep
soundcore 11553 1 snd
So I remembered the bug rh introduced with the 194 kernels and nvidia chipsets (not my case but I'm desperate) and added the enable_msi=0 so that my modprobe.conf is now
<snip> options snd cards_limit=8 alias snd-card-0 snd-hda-intel options snd-hda-intel index=0 enable_msi=0
but it still will not work.
<rant> I am getting frustrated at the retrograde steps that seem to be hitting kernel and 5.x upgrades lately. yum update used to just work, get me the latest patches and all was well - after all that is why I use Centos. </rant> I have tried modprobe -r to remove and reload module but to no avail. Anyone have any ideas as to what I try next? Google has not given me any ideas yet. TIA
Still no joy - I am at a loss to know what to check - if I boot a 194 kernel no sound, 164 kernel is fine - why the regression? Same configs, same modules loaded but now no sound - what can I check to determine problem and find a solution? no errors in logs or dmesg
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 20/07/10 03:08, Rob Kampen wrote:
Still no joy - I am at a loss to know what to check - if I boot a 194 kernel no sound, 164 kernel is fine - why the regression? Same configs, same modules loaded but now no sound - what can I check to determine problem and find a solution? no errors in logs or dmesg
I would suggest you start checking back through the changelogs between kernel-2.6.18-194.el5 and kernel-2.6.18-164.el5, find likely candidates that may have caused your issue and then rebuild a testing kernel with that patch reverted. If that testing kernel fixes your issue then you've identified the issue and can file a bug report upstream.
To start you on your way, this patch looks like a likely candidate for you to investigate further:
* Mon Dec 21 2009 Jarod Wilson jarod@redhat.com [2.6.18-183.el5] - [sound] alsa hda driver update for rhel5.5 (Jaroslav Kysela) [525390]
On Tue, Jul 20, 2010 at 2:55 AM, Ned Slider ned@unixmail.co.uk wrote:
On 20/07/10 03:08, Rob Kampen wrote:
Still no joy - I am at a loss to know what to check - if I boot a 194 kernel no sound, 164 kernel is fine - why the regression? Same configs, same modules loaded but now no sound - what can I check to determine problem and find a solution? no errors in logs or dmesg
I would suggest you start checking back through the changelogs between kernel-2.6.18-194.el5 and kernel-2.6.18-164.el5, find likely candidates that may have caused your issue and then rebuild a testing kernel with that patch reverted. If that testing kernel fixes your issue then you've identified the issue and can file a bug report upstream.
To start you on your way, this patch looks like a likely candidate for you to investigate further:
- Mon Dec 21 2009 Jarod Wilson jarod@redhat.com [2.6.18-183.el5]
- [sound] alsa hda driver update for rhel5.5 (Jaroslav Kysela) [525390]
Rob,
I understand you have already tried a workaround reported in:
https://bugzilla.redhat.com/show_bug.cgi?id=586532
According to comment #10 in there, Gary Gatling built a test kernel with the above alsa patch removed. You might want to try asking him for the kernel he built if you do not feel like building it yourself.
Akemi
On Wed, Jul 21, 2010 at 3:20 PM, Rob Kampen rkampen@kampensonline.com wrote:
Rob Kampen wrote:
I have started to setup an rpmbuild environment but need to read some more instructions, as when I followed the wiki I got different results - not sure if this is due to using the centosplus SRPM, as that is what all my workstations use, or due to my error in following instructions. When I tried the make oldconfig after copying the config file as indicated I ended up having to respond to lots of option questions that I have no idea about, thus I'm likely to select an option that causes problems. I thought make oldconfig was a process to dump out the current config settings so they could be used as a template for the new build......confused.
Because you are starting with a centosplus kernel and cplus kernels are already customized, you do not have to go through the customization part of the wiki instruction. In your case, all you have to do it to remove one patch.
I see the patch to be removed is this one:
Patch24883: linux-2.6-sound-alsa-hda-driver-update-for-rhel5-5.patch
Therefore, look for the line:
%patch24883 -p1
and delete it (it is line 9753 in the current kernel). If you had already modified the .spec file, I suggest you start fresh. The only other change you would want to make is "buildid" to provide a unique name for your new kernel.
Good luck!
Akemi
Akemi Yagi wrote:
On Wed, Jul 21, 2010 at 3:20 PM, Rob Kampen rkampen@kampensonline.com wrote:
Rob Kampen wrote:
I have started to setup an rpmbuild environment but need to read some more instructions, as when I followed the wiki I got different results - not sure if this is due to using the centosplus SRPM, as that is what all my workstations use, or due to my error in following instructions. When I tried the make oldconfig after copying the config file as indicated I ended up having to respond to lots of option questions that I have no idea about, thus I'm likely to select an option that causes problems. I thought make oldconfig was a process to dump out the current config settings so they could be used as a template for the new build......confused.
Because you are starting with a centosplus kernel and cplus kernels are already customized, you do not have to go through the customization part of the wiki instruction. In your case, all you have to do it to remove one patch.
I see the patch to be removed is this one:
Patch24883: linux-2.6-sound-alsa-hda-driver-update-for-rhel5-5.patch
Therefore, look for the line:
%patch24883 -p1
and delete it (it is line 9753 in the current kernel). If you had already modified the .spec file, I suggest you start fresh. The only other change you would want to make is "buildid" to provide a unique name for your new kernel.
Good luck!
Well firstly let me thank all those who have done such an excellent job with Centos, and the wiki. I have managed to rpmbuild my first ever kernel minus the patch - and it installed and booted just fine. A real tribute to all the centos team and particularly those that have taken the time to document the howto pages.
Unfortunately that particular patch is not the issue - sound still didn't work. So I went back and looked at dmesg and found that snd-usb-audio is loading first and as modprobe.conf had no specific instructions about this device driver it installed it as card 0 - thus when it subsequently tried to load snd-hda-intel as card 0 it failed. My initial fix was to edit modprobe.conf and make the snd-hda-intel as card 1. Reboot and now the card shows up okay and sound worked. Using the System > Administration > Soundcard Detection configurator showed both devices as it did for the 164 and earlier kernels. The settings tab allows one to change the order of devices. Looking at the modprobe.conf produced by this procedure yielded the following :- <snip> options snd cards_limit=8 alias snd-card-0 snd-hda-intel options snd-hda-intel index=0 alias snd-card-1 snd-usb-audio options snd-usb-audio index=1
thus now I have specific instruction to load the snd-usb-audio as device 1 and thus snd-hda-intel can load as device 0. why this worked okay without the two lines for snd-usb-audio on 164 (5.4) kernels is a mystery to me. I hope this may be of help to others that suddenly find sound devices failing to perform as expected.
All in all a learning experience. Thanks to Ned and Akemi for getting me headed in the right direction.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Jul 22, 2010 at 7:43 PM, Rob Kampen rkampen@kampensonline.com wrote:
The settings tab allows one to change the order of devices. Looking at the modprobe.conf produced by this procedure yielded the following :-
<snip> options snd cards_limit=8 alias snd-card-0 snd-hda-intel options snd-hda-intel index=0 alias snd-card-1 snd-usb-audio options snd-usb-audio index=1
thus now I have specific instruction to load the snd-usb-audio as device 1 and thus snd-hda-intel can load as device 0. why this worked okay without the two lines for snd-usb-audio on 164 (5.4) kernels is a mystery to me. I hope this may be of help to others that suddenly find sound devices failing to perform as expected.
All in all a learning experience. Thanks to Ned and Akemi for getting me headed in the right direction.
You are quite welcome. Glad to learn you've got things sorted out. I'm sure your solution would help future searchers having the same problem.
Akemi
Rob Kampen wrote:
Still no joy - I am at a loss to know what to check - if I boot a 194 kernel no sound, 164 kernel is fine - why the regression? Same configs, same modules loaded but now no sound - what can I check to determine problem and find a solution? no errors in logs or dmesg
Is there anything in /var/log/messages or dmesg about the soundcard (with both the 164 and 194 kernels)?
James Pearson
James Pearson wrote:
Rob Kampen wrote:
Still no joy - I am at a loss to know what to check - if I boot a 194 kernel no sound, 164 kernel is fine - why the regression? Same configs, same modules loaded but now no sound - what can I check to determine problem and find a solution? no errors in logs or dmesg
Is there anything in /var/log/messages or dmesg about the soundcard (with both the 164 and 194 kernels)?
Sorry - I somehow failed to read the previous posts about this issue being resolved - so ignore this ...
James Pearson