Using OpenSUSE 12.2 with opensuse kernel 3.6.2 from kernel repo.
Latest Gnome from Opensuse.
On boot, kernel sets volume level on default sound device to 50%.
This is too low for normal use, I set it to 100%.
On reboot, volume is back at 50%.
This does not happen on kernel 3.4.2, so it seems to rule out intermediate software layers.
Anyone get the same?
(PS also getting failure to resume from hibernate
and downloading problems with fixed IP with this kernel, so abandoning.)
I have kernel 3.6.2 loaded on a couple of PC’s, but I am not seeing this behavior. I do have Creative Sound cards in each, so perhaps you need to tell us about your audio hardware as it could be that specific kernel module that has the problem. You can check out your loaded Linux kernel modules with this bash script, recently updated and hot off of the presses:
Thank You,
Good suggestion. Do you need the entire list from skim or just the snd entries?
The whole list would be best. Make sure to place it in Code # tags, using the advanced message editor or place it in SUSE Paste, making sure to select to never delete and leaving us the page link. If you use skim, use the terminal command:
skim -r
To prevent the color escape codes from being in the text listing. You can quiz each kernel module you think does sound for more information in the bash script.
Thank You,
This is by no means a solution but you could try this to get suitable defaults. Set the audio the way you want in alsamixer or pavucontrol, and then open a terminal as root and run:
alsactl store
Though I am unsure if this will actually work or not. If it helps a tiny bit though I will be glad.
Here is my skim listing:
Num Name Size Ins Requires
1) 8139cp 31931 0 -
2) 8139too 33503 0 -
3) asus_atk0110 18657 0 -
4) ata_generic 12899 0 -
5) ata_piix 34991 3 -
6) atl1c 45452 0 -
7) autofs4 42753 2 -
8) bluetooth 321927 24 rfcomm,bnep,btusb,
9) bnep 19584 2 -
10) btusb 23835 0 -
11) button 13906 1 i915,
12) cdrom 46687 1 sr_mod,
13) coretemp 13444 0 -
14) drm 272508 4 i915,drm_kms_helper,
15) drm_kms_helper 51052 1 i915,
16) fuse 86852 3 -
17) i2c_algo_bit 13413 1 i915,
18) i915 505525 3 -
19) ip6table_filter 12815 1 -
20) ip6table_mangle 12700 0 -
21) ip6table_raw 12683 1 -
22) ip6_tables 27207 3 ip6table_raw,ip6table_mangle,ip6table_filter,
23) ip6t_REJECT 12939 3 -
24) iptable_filter 12810 1 -
25) iptable_raw 12678 1 -
26) ip_tables 27239 2 iptable_raw,iptable_filter,
27) ipt_REJECT 12541 3 -
28) iTCO_vendor_support 13718 1 iTCO_wdt,
29) iTCO_wdt 17948 0 -
30) microcode 35772 0 -
31) mperf 12667 0 -
32) nf_conntrack 97545 6 nf_conntrack_ipv6,xt_NOTRACK,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ipv4,xt_conntrack,
33) nf_conntrack_broadcast 12589 1 nf_conntrack_netbios_ns,
34) nf_conntrack_ipv4 15005 3 -
35) nf_conntrack_ipv6 14497 3 -
36) nf_conntrack_netbios_ns 12665 0 -
37) nf_defrag_ipv4 12729 1 nf_conntrack_ipv4,
38) nf_defrag_ipv6 18107 1 nf_conntrack_ipv6,
39) parport 46310 2 ppdev,parport_pc,
40) parport_pc 37265 0 -
41) pcspkr 12718 0 -
42) ppdev 17678 0 -
43) processor 44907 0 -
44) rfcomm 72935 4 -
45) rfkill 26009 3 bluetooth,
46) scsi_dh 14554 4 scsi_dh_rdac,scsi_dh_alua,scsi_dh_hp_sw,scsi_dh_emc,
47) scsi_dh_alua 17121 0 -
48) scsi_dh_emc 17258 0 -
49) scsi_dh_hp_sw 12894 0 -
50) scsi_dh_rdac 17408 0 -
51) sg 36394 0 -
52) snd 87206 17 snd_hda_codec_realtek,snd_usb_audio,snd_usbmidi_lib,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device,
53) snd_hda_codec 136135 2 snd_hda_codec_realtek,snd_hda_intel,
54) snd_hda_codec_realtek 81862 1 -
55) snd_hda_intel 33312 2 -
56) snd_hwdep 13602 2 snd_usb_audio,snd_hda_codec,
57) snd_page_alloc 18484 2 snd_hda_intel,snd_pcm,
58) snd_pcm 109282 3 snd_usb_audio,snd_hda_intel,snd_hda_codec,
59) snd_rawmidi 34608 1 snd_usbmidi_lib,
60) snd_seq 69746 0 -
61) snd_seq_device 14497 2 snd_rawmidi,snd_seq,
62) snd_timer 29370 2 snd_pcm,snd_seq,
63) snd_usb_audio 129661 1 -
64) snd_usbmidi_lib 24906 1 snd_usb_audio,
65) soundcore 15047 1 snd,
66) sr_mod 22295 0 -
67) thermal_sys 24703 2 video,processor,
68) usb_storage 57741 0 -
69) uvcvideo 76392 0 -
70) video 19345 1 i915,
71) videobuf2_core 32851 1 uvcvideo,
72) videobuf2_memops 13608 1 videobuf2_vmalloc,
73) videobuf2_vmalloc 13020 1 uvcvideo,
74) videodev 111306 1 uvcvideo,
75) x_tables 33967 15 xt_LOG,xt_limit,xt_tcpudp,xt_pkttype,ip6t_REJECT,ipt_REJECT,ip6table_raw,xt_NOTRACK,iptable_raw,iptable_filter,ip6table_mangle,ip_tables,xt_conntrack,ip6table_filter,ip6_tables,
76) xt_conntrack 12760 6 -
77) xt_limit 12711 10 -
78) xt_LOG 17471 10 -
79) xt_NOTRACK 12504 4 -
80) xt_pkttype 12504 3 -
81) xt_tcpudp 12884 6 -
Pulseaudio reports 3 audio devices, a USB webcam, a bluetooth adapter and the onboard audio.
The module for the onboard device appears to be snd_hda_intel (according to Yast hardware listing.)
So I am using KDE, but you can still look at YaST / Hardware / Sound:
http://paste.opensuse.org/view/download/1282347
And tell me how many sound devices does it find? It looks like you have more than one.
Thank You,
Yes indeed there are 3 devices as noted in previous message
Pulseaudio reports 3 audio devices, a USB webcam, a bluetooth adapter and the onboard audio.
The module for the onboard device appears to be snd_hda_intel (according to Yast hardware listing.)
The bluetooth device is there and functions as an audio device but only when a BT device is paired.
So, do you have the correct sound device set to 0 for default? Have you went into PulseAudio and set the profile for the other sound devices to off? Its possible with three sound devices that Pulse is getting confused. Normally you only use the one sound device and so the others can be disabled of at least not set as the default. I have an nVIDIA video card with sound on one PC and I make sure in Pulse its profile is set to off and that it is not the default in YaST / Hardware / Sound.
Thank You,
Yes, the different devices behave correctly when selected as the active device. However when I change from kernel 3.6.2 to kernel 3.4.2 and back PA and Gnome version remains fixed, the default device remains unchanged. BT is inactive, and the webcam has no audio output, so the only output device can be the onboard device.
However this sound device issue is a minor inconvenience. The failure to recover from hibernation is more of a concern, but the real killer is the download behaviour. When I have time I will investigate the 3.7 release. Otherwise I am stuck with the 3.4.2 (or 3.5.x which works) for the duration.
This issue and the hibernation issue have gone away in the 3.6.3 kernel just published.
This just leaves the download stalls, but if I stay on dynamic IP then the new kernel is workable.