|
Bugzilla – Full Text Bug Listing |
| Summary: | SIS sound fails - looped | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Alexey Eremenko <al4321> |
| Component: | Kernel | Assignee: | Thomas Renninger <trenn> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Alexey Eremenko
2005-09-13 19:15:44 UTC
It's a typical behavior of the wrong irq routing. Try to boot with pci=noacpi option or acpi=off option. OK, thanks! This seems to work for now - throught system is still unstable. This is due to the fact I have changed many config files with alsaconfig and manually. It seems that I will need to reinstall. However the problem still remains - new users will be unable to setup sound on many configurations - I have tested SuSE in 3 systems - in none of them sound worked out-of-the-box. After tweaking & configuration all 3 were working. 1 failed due to the ACPI (maybe we can take noacpi by default on problematic systems) 1 failed due to ISA (SUSE Linux doesn't autodetect ISA Sound Blasters) 1 failed die to other unknown reason Can we take steps to ensure that all of SuSE users get sound out of the box ? another problem with ALSA sound configuration & Yast- After using "alsaconf" it generates a file named "/etc/modprobe.d/sound" which is OK by itself, buy SuSE's Yast "Sound Card" editor can't edit the sound card configured this way, until that file manually removed. Should I open a new bug for that? OK, the files were reconfigured back to working state, so now I hope no need to reinstall. Overall: What's another intereting point about those 3 failed sound systems - all were made by different manufacturers, Creative, SIS, and VIA. Taking that into consideration, , and the fact all 3 systems were running sound OK after manual configuration, it really shows me that it's something wrong with SuSE's sound detection. 1. The problem of SIS is the kernel problem. Not the sound configuration. 2. The non-PnP ISA isn't detected, and will be very unlikely supported in future, too. If it's a PnP-ISA, it should be possible to detect. Please file another bug report. 3. No idea what is wrong with VIA, but if it works with some module options, it's a bug of the driver, not the sound configurator. YaST and alsaconf change two files: /etc/modprobe.d/sound and /etc/sysconfig/hardware/*. It's possible that YaST doesn't handle the config files generated by alsaconf properly, though. (Meanwhile, alsaconf always overwrite the configuration.) In this bug report, please concentrate only on the issue 1. The others are totally different problems. Please don't mix up. Consequently, do you need ACPI tune up to get SIS working, or did you find any other workaround? Instead of turning off ACPI totally, you can try another pci=xxx option, e.g. pci=routeirq. I'm sorry, but I don't know very much the Linux kernel options. So what kernel options exist ? Can you drop me a link, that explains kernel boot options? For example, how to force my kernel to boot into runlevel 3, instead of 5 with kernel bootoptions? =========================================== I have tried: 1) acpi=off (works) 2) pci=noacpi (doesn't work) 3) pci=routeirq (doesn't work) I haven't found workaround. If acpi=off works for sound, it's indeed an ACPI issue. Changed to Kernel component. Hubert, please pass it to an appropriate person who understands ACPI better than I... Please attach dmesg and acpidmp output when booting without acpi=off. No input for three months... Please also test on Open Suse 10.1 and reopen if the problem still exists. |