Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a relatively simple question. When my SuSE box starts I see 3 instances of via82xx initiated - and consequently no sound from my machine. I guess this is due to some duplication in a configuration file being read by /etc/init.d/alsasound - but which one? How should I go about fixing this?
lspci:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge (rev 80)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc.: Unknown device 3149 (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB (rev 81)
0000:00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3227
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 60)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
Hello, I had the same problem on my machine too, I have via8235 and suse 9.1. The sound card was configured, but no sound output. But I have fixed it last night following the instruction given on
after running modprobe. I then restarted my machine, and open Kmixer, in the advanced mod, I turned on PCM, and it works. I can even listen to the radio online now.
I thought this might help you, but don't ask me if there is any other problems as I am not a linux expert. :-)
However, I can't even get alsa to compile on a fully patched clean installation. I have downloaded the latest version (1.0.5) and attempted to follow the instructions on the alsa-sound page, to no avail. I have the relevant kernel sources installed - is there some gotcha that I've missed?
I have a Via 8235 soundcard and had some troubles with it, the way I got mine to work was to use YaST to set it up and in the options set it so that DXS channels were disabled, now my sound is crystal clear.
Yeh, I have done the same thing dave_starsky, using yast to install the sound card first. Then when I typed "modinfo soundcore", I have output. I didn't try to compile the source at all. Maybe give that a try and see, good luck.
Right after a lot of head scratching, frustration at being unable to compile the 2.6.5-75 kernel without the ALSA driver built in - so I could then attempt to compile ALSA 1.0.5 .........I finally have the bloody obvious solution.
Sound stopped working when SuSE's online updater installed the bug fixed kernel 2.6.5-75, so it's broken right? Well sort of, if you add "pci=noacpi" to the boot command, then sound miraculously springs back in to life. This is consistent with my observation that when sound was screwed, it would start to play a sample then immediately get stuck playing a single note indefinitely.....unless I moved my USB mouse around - which allowed the sample to play out.
So IRQ problem right? The VIA 8235 sound chip was on IRQ11 as was one of the UHCI USB controllers - and whilst I thought kernel 2.6.x was going to be much better at acpi stuff, it aint - or at least it isn't in the kernel SuSE chucked out. So if you take IRQ routing out of acpi's hands things will be back to normal.
I have an identical machine, that I didn't allow SuSE to patch to the latest recommended kernel - and sound works fine. So to repeat, add: pci=noacpi (and possibly) noapic
to the boot command line (type it into the box at the bottom of the SuSE splash screen before pressing return) and off you go.
Just reinstalled SuSE 9.1 from scratch on one of my machines, and sound still doesn't work. It seems a bit stupid to be using a 2.6 kernel when one of the fundamental things going for it was supposed to be the great ACPI support. I did report this as a bug to SuSE and they never got back to me, things had better improve......
Follow up to previous email: you don't have to type pci=noacpi in each time, just edit menu.lst in /boot/grub to include the pci=noacpi in the linux load line.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.