Bruce Ferrell wrote:

Also check the permissions on /dev/snd. for some reason, on my installation, the perms/ownership is root.root 744 and this does not allow soud to work for anyone other than root

$ ls /dev/snd -l total 0 drwxr-xr-x 2 root root 60 Sep 18 10:37 by-path crw-rw---- 1 root audio 116, 8 Sep 18 10:37 controlC0 crw-rw---- 1 root audio 116, 3 Sep 18 10:37 controlC1 crw-rw---- 1 root audio 116, 2 Sep 18 10:37 midiC1D0 crw-rw---- 1 root audio 116, 7 Sep 18 10:37 pcmC0D0c crw-rw---- 1 root audio 116, 6 Sep 18 10:37 pcmC0D0p crw-rw---- 1 root audio 116, 5 Sep 18 10:37 pcmC0D1c crw-rw---- 1 root audio 116, 4 Sep 18 10:37 pcmC0D2p crw-rw---- 1 root audio 116, 1 Sep 18 10:37 seq crw-rw---- 1 root audio 116, 33 Sep 18 10:37 timer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On September 19, 2012 14:08:18 James Knott wrote:

indigenis wrote:

...

On September 19, 2012 12:50:10 James Knott wrote:

...

I no longer have sound on my computer, since upgrading to openSUSE 12.2. According to Yast Sound Configuration, I have the sound built in on my Asus motherboard and it uses the snd-intel8x0 driver. However, according to the mixer Sound and Video Configuration, there is no sound card. Lsmod shows "snd_pcm 109282 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss".

Any idea how I can get sound going? This is the first time in many years that I haven't had sound working.

tnx jk

What channels do you see in kmix?

Click on the sound icon in the bottom right of your screen and click Mixer. Go up to Settings and click Configure Channels.

There is no "Configure Channels". Under "Select Master Channel", it shows "Dummy Channel". In contrast, the same setting on my notebook computer shows "Internal Audio Analog Stereo".

...

On the left hand pane, look for PCM and drag it to the right hand pane, then turn it up to 100%.

Turn the Master channel to low and slowly turn it up checking to see if audio can be heard.

Does that work?

I had this same issue and found that my PCM channel would not output audio unless I turned it up.

As I mentioned, it doesn't even show a sound card as available.

What happens if you add your user to the "audio" group then restart or logout/login. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wednesday, September 19, 2012 04:28 PM James Knott wrote:

I have 2 computers here. One is a desktop and one a notebook. Neither has users as members of audio group, but the sound works fine on the notebook. It also shows a real device and not "Dummy Output". This looks more like 12.2 is not recognizing the hardware than anything else.

Didn't you post that YaST sees the device? And the kernel is seeing it and loading modules? I seem to recall a somewhat recent thread where the problem was the module configuration, and once the correct parameter was supplied in YaST, it worked. The OP had to research to find that (maybe the ALSA site?). Sorry I don't remember more. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/19/2012 01:50 PM, James Knott wrote:

Dennis Gallien wrote:

...

Didn't you post that YaST sees the device? And the kernel is seeing it and loading modules?

I seem to recall a somewhat recent thread where the problem was the module configuration, and once the correct parameter was supplied in YaST, it worked. The OP had to research to find that (maybe the ALSA site?).

Yes, as far as I can tell, Yast sees it and the module is loaded. But wasn't Alsa in previous openSUSE versions and dropped for PulseAudio in 12.2? Yast able to see the device and play the test sound (you didn't mention that but I'm presuming that works) is an indication the device is present and that root is able to access it/them... Leading back to permissions. I *think* udev is responsible for setting up device permissions as they are added and users log in and out... Probably wrong about that last part.

I'm seeing quite a few "issues" with device permissions in 12.2 /dev/sr0 not accessible by normal users etc, and now sound -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wednesday, September 19, 2012 04:50 PM James Knott wrote:

Dennis Gallien wrote:

...

Didn't you post that YaST sees the device? And the kernel is seeing it and loading modules?

I seem to recall a somewhat recent thread where the problem was the module configuration, and once the correct parameter was supplied in YaST, it worked. The OP had to research to find that (maybe the ALSA site?).

Yes, as far as I can tell, Yast sees it and the module is loaded. But wasn't Alsa in previous openSUSE versions and dropped for PulseAudio in 12.2?

I am a lightweight in this area, but I had thought that ALSA provides the drivers and that PA was an interface layer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, 19 Sep 2012 16:50:58 -0400, James Knott wrote:

wasn't Alsa in previous openSUSE versions and dropped for PulseAudio in 12.2?

Had you read the desciption on http://www.alsa-project.org/main/index.php/Main_Page you would have seen that ALSA is still needed. ALSA provides the sound architecture , i.e. drivers and a user space library while PA provides application specific mixers that allow you to configure per application where the sound is output and so on. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/19/2012 05:25 PM, Dennis Gallien wrote:

On Wednesday, September 19, 2012 06:14 PM Philipp Thomas wrote:

...

On Wed, 19 Sep 2012 16:50:58 -0400, James Knott

wrote:

...

wasn't Alsa in previous openSUSE versions and dropped for PulseAudio in 12.2? Had you read the desciption on http://www.alsa-project.org/main/index.php/Main_Page you would have seen that ALSA is still needed. ALSA provides the sound architecture , i.e. drivers and a user space library while PA provides application specific mixers that allow you to configure per application where the sound is output and so on.

Philipp So can PA be disabled in 12.2 as in previous versions?

James, if so, then that may be your solution. In order to get my Intel driver (snd-hda-intel) to consistently work under 12.1, was to force define a "model".

The card defaulted to reading the BIOS and setting the model to "auto" - I had to hard code the model=3stack-6ch-dig - as well as uninstall PA. This could be the key to getting 12.2 to work. ALC882/883/885/888/889 ====================== *Used = model = 3stack-6ch-dig (3-jack 6-channel with SPDIF I/O)* ---------------------------------------- 3stack-dig 3-jack with SPDIF I/O 6stack-dig 6-jack digital with SPDIF I/O arima Arima W820Di1 targa Targa T8, MSI-1049 T8 asus-a7j ASUS A7J asus-a7m ASUS A7M macpro MacPro support mb5 Macbook 5,1 macmini3 Macmini 3,1 mba21 Macbook Air 2,1 mbp3 Macbook Pro rev3 imac24 iMac 24'' with jack detection imac91 iMac 9,1 w2jc ASUS W2JC 3stack-2ch-dig 3-jack with SPDIF I/O (ALC883) alc883-6stack-dig 6-jack digital with SPDIF I/O (ALC883) 3stack-6ch 3-jack 6-channel 3stack-6ch-dig 3-jack 6-channel with SPDIF I/O 6stack-dig-demo 6-jack digital for Intel demo board acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc) acer-aspire Acer Aspire 9810 acer-aspire-4930g Acer Aspire 4930G acer-aspire-6530g Acer Aspire 6530G acer-aspire-7730g Acer Aspire 7730G acer-aspire-8930g Acer Aspire 8930G medion Medion Laptops targa-dig Targa/MSI targa-2ch-dig Targa/MSI with 2-channel targa-8ch-dig Targa/MSI with 8-channel (MSI GX620) laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE) lenovo-101e Lenovo 101E lenovo-nb0763 Lenovo NB0763 lenovo-ms7195-dig Lenovo MS7195 lenovo-sky Lenovo Sky haier-w66 Haier W66 3stack-hp HP machines with 3stack (Lucknow, Samba boards) 6stack-dell Dell machines with 6stack (Inspiron 530) mitac Mitac 8252D clevo-m540r Clevo M540R (6ch + digital) clevo-m720 Clevo M720 laptop series fujitsu-pi2515 Fujitsu AMILO Pi2515 fujitsu-xa3530 Fujitsu AMILO XA3530 3stack-6ch-intel Intel DG33* boards intel-alc889a Intel IbexPeak with ALC889A intel-x58 Intel DX58 with ALC889 asus-p5q ASUS P5Q-EM boards mb31 MacBook 3,1 sony-vaio-tt Sony VAIO TT auto auto-config reading BIOS (default) -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing & Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home & Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 20/09/12 10:25, Dennis Gallien wrote:

So can PA be disabled in 12.2 as in previous versions?

James, if so, then that may be your solution.

I've had endless and inconsistent difficulties with Pulse Audio on this machine, over several generations of openSUSE. This was so both with the onboard Intel sound chip and, latterly, a SoundBlaster X-Fi Titanium PCI card. In frustration in 12.1 I uninstalled everything to do with Pulse Audio that I could find; and in installing 12.2 a couple of weeks ago I deselected every instance of it. In both cases the fallback to alsa works just fine. Having said that, an rpm grep on pulse reveals that there are still four remnants in the system that can't be got rid of because of dependencies. They are libxine2-pulse-1.2.2-78.1.x86_64 libpulse-mainloop-glib0-1.1-6.1.2.x86_64 libpulse0-1.1-6.1.2.x86_64 libpulse0-32bit-1.1-6.1.2.x86_64 but, functionally at least, they don't seem to matter. -- Robin K Wellington "Harbour City" New Zealand -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thursday, September 20, 2012 12:13 AM Philipp Thomas wrote:

On Wed, 19 Sep 2012 18:25:02 -0400, Dennis Gallien

wrote:

...

So can PA be disabled in 12.2 as in previous versions?

Why, in most cases I encountered PA wasn't realy the culprit. And without PA you loose things like application specific volume.

Philipp

But there have been *many* reports from users having problems with PA, at least in past releases. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Addendum to the list of pulseaudio packages that I have installed: paman-0.9.4-144.1.x86_64 (PulseAudio Manager) pavucontrol-0.9.10-9.1.x86_64 (PulseAudio Volume Control) pavumeter-0.9.3-181.1.x86_64 (PulseAudio VU Meters) padevchooser-0.9.4-143.1.x86_64 (PulseAudio Device Chooser) paprefs-0.9.9-12.1.x86_64 (PulseAudio Preferences) Sorry for not properly checking the list before I clicked 'send' last time! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Vadym Krevs wrote:

If you're using sysvinit instead of systemd, then you probably hit this issue: https://bugzilla.novell.com/show_bug.cgi?id=769570

Yes, I was running sysvinit. When I run systemd, sound works as it should. However, this brings me back to the reason I switched to sysvinit in 12.1. I run an imap server and use fetchmail to download the email. I started fetchmail with a script launched by /etc/init.d/after.local. This method does not work with systemd. Is there anyway of running after.local on a systemd system? This is critical, as I have another computer, currently running 11.4, where after.local is used to start a 6in4 IPv6 tunnel. If these two items cannot be started in systemd, then, as far as I'm concerned, systemd is broken and useless. Is there any equivalent to after.local in systemd? After.local is an extremely useful feature, which I have used many times over the years. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

why don't you start fetchmail on user login (~/.profile or ~/.bashrc )?

Fetchmail is run by a user that never logs on. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan wrote:

* James Knott [09-20-12 20:47]:

...

...

Patrick Shanahan wrote:

...

...

why don't you start fetchmail on user login (~/.profile or ~/.bashrc )?

Fetchmail is run by a user that never logs on. Then write a script that starts or checks for a fetchmail instance on successful network connection.

ping yahoo.com && fetchmail -d 300

I found a way to run after.local here: http://forums.opensuse.org/blogs/comments/comment547.html It appears to work. However, given the number of people who rely on after.local, why wasn't it included in systemd in the same manner as boot.local is? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ken Schneider - openSUSE wrote:

...

It appears to work. However, given the number of people who rely on after.local, why wasn't it included in systemd in the same manner as boot.local is?

Because systemd doesn't support "runlevels" in the way sysvinit does. Everything is a "service" that runs as needed. Supposedly the functionality can be duplicated in a systemd service file. Oh, and the devs would rather 100's of thousands of people write their own then one dev write it and supply it to the masses.

After.local is a bit different than runlevels. It runs only after the system is up and running. It's a convienient way to lauch things that are not part of the boot process, but should start shortly after boot. It's similar in concept to the start up folders that people often use. So why couldn't systemd simply run such a script when it's done everything else required in booting? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward wrote:

...

After.local is a bit different than runlevels. It runs only after the system is up and running. It's a convienient way to lauch things that are not part of the boot process, but should start shortly after boot. It's similar in concept to the start up folders that people often use. So why couldn't systemd simply run such a script when it's done everything else required in booting? So its doing something like CRON does with @reboot. That's what I use to fire off fetchmail in the background when I start

James Knott said the following on 09/21/2012 08:07 AM: the system.

I had looked at that earlier but there was some reason, at the time, which made after.local better. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, 2012-09-21 at 08:00 -0400, James Knott wrote:

Patrick Shanahan wrote:

...

ping yahoo.com && fetchmail -d 300

If systemd is so great, why should it be necessary to do something like that to replace lost functionality?

There is no lost functionality. Do not do what you are doing there. Use crond, what you are running is not really a well behaved service. Cron offers @reboot for this purpose.

While systemd may have advantages, the developers should have had better support for existing sysv software. That includes support for after.local and I would suggest also anything in the various rcx.d directories.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org