I upgraded to 2.6.26-r3 and my sound doesn't work. Deleting /var/lib/alsa/asound.state does not solve the issue. The following is observation. Apologies if it does not help to diagnose this problem: I noticed some difference between what RTC-related support you are permitted to select in menuconfig for 2.6.25-r7 and 2.6.26-r3. I would have used the same .config ('same' being the closest I can get to the config for the former kernel version by running 'make oldconfig' on it in the source directory for the latter kernel version) with 2.6.26-r3 as I used with 2.6.25-r7 but this was not possible: grep -i rtc /boot/config-2.6.25-gentoo-r7 | grep -v ^# CONFIG_HPET_EMULATE_RTC=y CONFIG_RTC=y CONFIG_SND_RTCTIMER=m CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y CONFIG_RTC_LIB=m CONFIG_RTC_CLASS=m CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y grep -i rtc /boot/config-2.6.26-gentoo-r3 | grep -v ^# CONFIG_HPET_EMULATE_RTC=y CONFIG_RTC=y CONFIG_SND_RTCTIMER=m CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y I can set 'CONFIG_RTC_LIB=m' and 'CONFIG_RTC_CLASS=m' in the menuconfig for 2.6.26-r3, but doing so causes 'CONFIG_SND_RTCTIMER' and 'CONFIG_SND_SEQ_RTCTIMER_DEFAULT' to disappear from the resulting config file. Conversely, I could have 'CONFIG_RTC_LIB=m', 'CONFIG_RTC_CLASS=m', 'CONFIG_SND_RTCTIMER=m' and 'CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y' set in the config resulting from running make menuconfig in 2.6.25-r7. After testing with 2.6.26-r4: (I haven't tested with gentoo-sources > 2.6.26-r4 since I'm only running stable (amd64). The logic is definitely different concerning RTC options in the menuconfig for 2.6.26. Setting, for example, 'CONFIG_RTC_CLASS' to yes causes 'CONFIG_RTC' to be set to no. This in turn disables 'CONFIG_SND_RTCTIMER', which I believe is necessary (along with 'CONFIG_RTC'=yes) in order for my setup to have sound. 'CONFIG_RTC' and 'CONFIG_SNDRTCTIMER' (and 'CONFIG_SND_SEQ_RTCTIMER_DEFAULT') were not mutually exclusive in 2.6.25-r7 or indeed in any of the following, which I have used with this same hardware: config-2.6.19-gentoo-r5 config-2.6.22-gentoo-r2 config-2.6.22-gentoo-r5 config-2.6.22-gentoo-r8 config-2.6.22-gentoo-r9 config-2.6.23-gentoo-r3 config-2.6.23-gentoo-r6 config-2.6.23-gentoo-r8 config-2.6.23-gentoo-r9 config-2.6.24-gentoo-r4 config-2.6.24-gentoo-r7 config-2.6.25-gentoo-r6 config-2.6.25-gentoo-r7 This is the first kernel release I've used which has stopped my sound working. Now alsa-utils-1.0.17 has gone stable on amd64, I've installed it (as part of my usual emerge -uDN world). I can confirm that I'm still without sound in 2.6.26-r4 Perhaps if I attach my 2.6.25-r7 config and two configs I've tried with 2.6.26-r4 you could look at them and tell me if there is anything visibly wrong. 'config-2.6.26-r4' is the result of a 'make oldconfig' on the 2.6.25-r7 config file. Booting up the resulting 2.6.26-r4 kernel I'm told that the RTC cannot be accessed. Looking at the kernel config file I can see that some RTC options have been disabled(!!) So, running 'make menuconfig' and re-enabling SND_RTCTIMER support (and some other RTC options which had been disabled) gives me the file 'config-2.6.26-r4rtc'. Rebuilding the 2.6.26-r4 kernel with this resolves the missing RTC access problem but I still get no sound. There really weren't any manual changes between my 2.6.25-r7 config and the first 2.6.26-r4 config. Please compare those two files (attached). Again, this is the first kernel since 2.6.19 in which I have had any sound issues. I'm really stuck with this problem. I was pinning my hopes on alsa-utils-1.0.17 but it has not helped me.
Created attachment 176062 [details] My 2.6.25 config, with which there are no sound or RTC issues.
Created attachment 176064 [details] The direct result of 'make oldconfig' on the 2.6.25-r7 kernel config - where's my RTC support?
Created attachment 176066 [details] I put RTC support back in and there are no RTC issues, but still no sound.
Created attachment 176067 [details] lspci output (from 2.6.25-gentoo-r7)
Created attachment 176069 [details] dmesg output (2.6.25-gentoo-r7)
(In reply to comment #5) > Created an attachment (id=176069) [edit] > dmesg output (2.6.25-gentoo-r7) That's not your entire dmesg output. Did you run alsaconf after you emerged alsa-*-1.0.17 and booting with the new kernel? Did you run alsamixer to set proper volume settings? Do you get any failure messages running apps that use sound? Or do the apps run fine but no sound output actually reaches the speakers?
Jeroen, I ran alsaconf after reading your comment and now my sound works. Thank you. Last time I upgraded alsa-utils (1.0.14 > 1.0.16) was on 30th May 2008. I did not run alsaconf on that occasion either, yet sound worked post-upgrade. This is my only excuse for not running it this time, which is fairly poor, admittedly. Thanks again, Richard P.S. > That's not your entire dmesg output. I used the output of the program 'dmesg' for my 'dmesg' attachment when I should have attached /var/log/dmesg. Well, I know for next time :)
Looks like this problem is fixed, closing...
