|
Bugzilla – Full Text Bug Listing |
| Summary: | Sound system fails (autoconfigured improperly) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Alexey Eremenko <al4321> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | My y2logs - dated 28.8.2005. | ||
|
Description
Alexey Eremenko
2005-08-26 13:35:47 UTC
does playing a wav file with aplay work ? aplay /opt/kde3/share/sounds/KDE_Window_UnSticky.wav does "alsamixer" work on command line ? Here are the results: alexey@linux:~> aplay /opt/kde3/share/sounds/KDE_Window_UnSticky.wav ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:955:(snd_func_refer) error evaluating name ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2094:(snd_pcm_open_noupdate) Unknown PCM default aplay: main:540: audio open error: No such device I might try to give you a VNC access to my PC. Will this help you? You won't probably hear sound over VNC (as far as I know-Only Microsoft Remote Desktop allows Sound-on Windows XP) ========================================================= alexey@linux:~> alsamixer alsamixer: function snd_ctl_open failed for default: No such device it is an general alsa/permission issue .... Now, it is solved after reinstalling the driver. (i.e. Yast->Sound->Delete->Edit->Quick Install) So now the only problem remains in question - why it wasn't working from the beginning ? Reducing severity to normal. It's no "general" problem :) Does user login via kdm? user autologined. probably via kdm. This kind of bug happens when either /dev/snd/* device files really don't exist, or the permission is set to another user. Try to reboot and check whether the problem remains. If it occurs again, check /dev/snd/pcmC0* and /dev/snd/controlC0 files. Hell and Thunder !!! After rebooting I'we lost my audio device once again! linux:/dev # ll s* crw-r--r-- 1 root root 36, 1 2005-08-26 17:37 skip crw------- 1 alexey root 10, 250 2005-08-26 17:37 sonypi lrwxrwxrwx 1 root root 4 2005-08-26 20:37 stderr -> fd/2 lrwxrwxrwx 1 root root 4 2005-08-26 20:37 stdin -> fd/0 lrwxrwxrwx 1 root root 4 2005-08-26 20:37 stdout -> fd/1 In fact, there is *no* snd device or directory exists in "/dev" KMix returned to it's stupid mode, where it can't find any sound device. Probably this problem lies deep. Together with KMix, Severity returned to blocker. (Blocker severity, because Suse on my Primary Home Desktop is useless without sound) Also, there was NO such problem in BETA2. Strange, what the hell changed since???? Check /proc/asound/cards whether the driver is loaded properly. If yes, it should be a udev problem. Unfortunately, now the sound also fails under root. Also, there is no "asound" directory in /proc: linux:/proc # ll a* total 0 dr-xr-xr-x 10 root root 0 2005-08-26 17:37 . dr-xr-xr-x 118 root root 0 2005-08-26 20:37 .. dr-xr-xr-x 2 root root 0 2005-08-26 18:08 ac_adapter -rw-r--r-- 1 root root 0 2005-08-26 18:08 alarm dr-xr-xr-x 2 root root 0 2005-08-26 18:08 battery dr-xr-xr-x 3 root root 0 2005-08-26 18:08 button -rw-r--r-- 1 root root 0 2005-08-26 18:08 debug_layer -rw-r--r-- 1 root root 0 2005-08-26 18:08 debug_level -r-------- 1 root root 0 2005-08-26 18:08 dsdt dr-xr-xr-x 2 root root 0 2005-08-26 18:08 embedded_controller -r-------- 1 root root 0 2005-08-26 17:37 event -r-------- 1 root root 0 2005-08-26 18:08 fadt dr-xr-xr-x 2 root root 0 2005-08-26 18:08 fan -r--r--r-- 1 root root 0 2005-08-26 18:08 info dr-xr-xr-x 2 root root 0 2005-08-26 18:08 power_resource dr-xr-xr-x 3 root root 0 2005-08-26 18:08 processor -rw-r--r-- 1 root root 0 2005-08-26 18:08 sleep dr-xr-xr-x 2 root root 0 2005-08-26 18:08 thermal_zone -rw-r--r-- 1 root root 0 2005-08-26 18:08 wakeup linux:/proc # pwd /proc linux:/proc # cd /proc/asound bash: cd: /proc/asound: No such file or directory Also, for some unknown reason after doing a* it showed me all virtual files not starting from "a"... Try to access my pc via VNC, port 5900 at IP: 82.80.214.219 If, I have configured the Router, and SuSE 10 right, it should work! I hope that doing this is much more effectively, than thinking in the air. It means that the sound driver is not loaded. Check /etc/sysconfig/hardware/hwcfg-* file includes snd-via82xx, e.g. grep snd /etc/sysconfig/hardware/hwcfg-* If it exists, the system isn't in the sane state. Reconfiguring the sound device via yast would be required. alexey@linux:~> grep snd /etc/sysconfig/hardware/hwcfg-* /etc/sysconfig/hardware/hwcfg-static-1:# YaST configured sound card snd-card-0 /etc/sysconfig/hardware/hwcfg-static-1:MODULE='snd-via82xx' grep: /etc/sysconfig/hardware/hwcfg-static-printer: Permission denied alexey@linux:~> alexey@linux:~> alexey@linux:~> su - root Password: linux:~ # grep snd /etc/sysconfig/hardware/hwcfg-* /etc/sysconfig/hardware/hwcfg-static-1:# YaST configured sound card snd-card-0 /etc/sysconfig/hardware/hwcfg-static-1:MODULE='snd-via82xx' linux:~ # Well, yes, some files seem to be exist. It's strange that the setting is saved to hwcfg-static-*. It should be like hwcfg-bus-pci-xxxx. There is a know bug on beta3 that static configuration isn't loaded at all (#113158). That's the reason why it doesn't work on beta3. Did you configure it yast (or installer did it automatically)? If yes, the yast did set up wrong... To be sure, try to set up with yast, and check hwcfg file again. The problems begun after the setup. Then I have tried to solve them with Yast Control Center. After long, trying, I finally had some sound from both root and users, but after restart all has gone !!! After using Yast it became OK. Now I have sound... for some time... linux:~ # grep snd /etc/sysconfig/hardware/hwcfg-* /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.5:# YaST configured sound card snd-card-0 /etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:11.5:MODULE='snd-via82xx' /etc/sysconfig/hardware/hwcfg-static-1:# YaST configured sound card snd-card-0 /etc/sysconfig/hardware/hwcfg-static-1:MODULE='snd-via82xx' linux:~ # ===================== As for VNC: I don't know which ports it uses, so I'm having trouble to configure my router to forward VNC packets. Hmm, then it's mysterious how yast created hwcfg-static-*. Reassigned to yast2-maintainer. Most likely we need yast2 log files to analyze, so please attach y2log files. (Also lower the severity since it's a yast configuration issue.) OK, OK, I will add those yast2 logs. Question to developers: Are they always enought to reconstruct what happened ? If not, how often they are enough ? (from 0-100%) Created attachment 47909 [details]
My y2logs - dated 28.8.2005.
The log contains these hwcfg files used by yast: y2log-2:2005-08-26 19:19:40 <1> linux(6440) [YCP] sound/write_routines.ycp:188 using hwcfg file: hwcfg-bus-pci-0000:00:11.5 y2log-4:2005-08-26 15:21:13 <1> linux(13587) [YCP] sound/write_routines.ycp:188 using hwcfg file: hwcfg-bus-pci-0000:00:11.5 y2log-4:2005-08-26 16:07:15 <1> linux(5734) [YCP] sound/write_routines.ycp:188 using hwcfg file: hwcfg-static-1 y2log-4:2005-08-26 16:51:47 <1> linux(5746) [YCP] sound/write_routines.ycp:188 using hwcfg file: hwcfg-bus-pci-0000:00:11.5 y2log-5:2005-08-26 14:07:28 <1> linux(4939) [YCP] sound/write_routines.ycp:188 using hwcfg file: hwcfg-bus-pci-0000:00:11.5 The one static case is there because user pressed Add (adds a new/unknown sound card) instead of Edit (configures the selected card). So the static config was OK -> resolving as INVALID |