OpenSuSE 11.1 No sound after recent updates - Page 2

oldcpu · #11 (**permalink**) 31-Oct-2009, 21:15

Quote:

Originally Posted by oldcpu

You should be sending commands from the 11.1 section (1st 3 commands) and then send commands from the 11.1's kernel 2.6.27.37-0.1-pae section. NOT from the 11.0 section.

If you sent the 1st 3 commands from the 11.0 section, you will need to send them again from the 11.1 section, as it goes to a different software repository. You will then have to send the next 3 commands from the section specific to your kernel version, which is a 2.6.27.37.

Ensure you REMOVE the repository "multimedia" from the failed effort, before you try again.

My guess is the commands you should be sending are the following. Note you may wish to modify the second command to add the extra alsa apps you have (in addition to alsa, alsa-docs, and libasound2).

Code:

zypper rr multimedia

Code:

zypper ar http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_11.1/ multimedia

Code:

zypper install alsa alsa-docs libasound2

Code:

zypper rr multimedia

Code:

zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.1_Update/ multimedia

Code:

zypper install alsa-driver-kmp-pae

Code:

zypper rr multimedia

... again, I do not know how well the above format will render in NNTP. I added a 7th command (at the start) to ensure you did not still have "multimedia" as a repos label.

#12 (**permalink**) 01-Nov-2009, 00:59

On Sun, 01 Nov 2009 00:54:38 +0000, Jim Henderson wrote:

> On Sat, 31 Oct 2009 22:59:29 +0000, David Gersic wrote:
>
>> but reinstalling Pulse
>
> I wouldn't even reinstall it, based on my own experience - many people
> have reported having problems with pulseaudio, I'd remove that from the
> picture and diagnose from there.

I could do that, except that in removing it, things got worse. Or at
least they seem worse without it.

> When you don't get any input, do you get a sort of clicking noise at all
> (might have to listen with headphones)? That was the symptom I had.

Nope. Nothing at all.

--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

#13 (**permalink**) 01-Nov-2009, 00:59

On Sun, 01 Nov 2009 02:16:01 +0000, oldcpu wrote:

> Its looking for an alsa-driver-kmp-pae for the 2.6.25.20 kernel. I
> think you went and sent the zypper commands for openSUSE-11.0 instead of
> openSUSE-11.1.

Argh. Looks like you're right. Sorry about that. Now following the
directions correctly, I've installed the new alsa driver. No change in
symptoms, though. I reran the alsa-info.sh script to update the output:

http://www.alsa-project.org/db/?f=16...2c70d3cca26e04

--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

oldcpu · #14 (**permalink**) 01-Nov-2009, 03:33

Quote:

Originally Posted by David Gersic

On Sun, 01 Nov 2009 02:16:01 +0000, oldcpu wrote:

> Its looking for an alsa-driver-kmp-pae for the 2.6.25.20 kernel. I
> think you went and sent the zypper commands for openSUSE-11.0 instead of
> openSUSE-11.1.

Argh. Looks like you're right. Sorry about that. Now following the
directions correctly, I've installed the new alsa driver. No change in
symptoms, though. I reran the alsa-info.sh script to update the output:

http://www.alsa-project.org/db/?f=16...2c70d3cca26e04

OK, now I note this:

Code:

!!ALSA Version
!!------------

Driver version:     1.0.21-git20091031
Library version:    1.0.18
Utilities version:  1.0.18

This tells me the last 3 (of the six commands) worked, but the two 1.0.18 entries suggests to me your PC still has the old alsa, alsa-docs, ... etc ... and hence the 2nd command: "zypper install alsa alsa-docs libasound2 .... < what ever else you added > " failed to work/update your alsa versions.

You could confirm that by typing:

rpm -qa '*alsa*'

...
I suspect with the exception of alsa-driver-kmp-pae (which will be 1.0.21) the rest of your alsa apps will be 1.0.18.

I have seen this problem happen before where users still have the installation CD/DVD selected as a repository in YaST/zypper, with a higher priority than any new adhoc repository. Hence in the second command only resulted in the alsa versions from the CD/DVD be re-installed and it ignored the updated alsa rpms available in the multimedia directory.

I recommend you go to YaST > Software > Software Repositories and disable your CD/DVD as a repository. It should look something like "cd:///?devices=/dev/sr0" or something like that.

While you are there, check and ensure you have OSS, Non-OSS, and openSUSE-11.1-Update enabled. This is also a good time to click on the "add" button and add "Packman" as a repository. Typically I recommend ONLY 4 repositories be left enabled: OSS, Non-OSS, Update and Packman. Others should be disabled. Others can then be added/enabled as required and disabled after.

Anyway, after you have disabled the CD/DVD, send the follow commands again with root permissions and your PC connected to the Internet:

Code:

zypper rr multimedia

Code:

zypper ar http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_11.1/ multimedia

Code:

zypper install alsa alsa-docs libasound2

Code:

zypper rr multimedia

and again, for the command "zypper install alsa alsa-docs libasound2" expand that command so as to update your alsa apps. For example I have alsa-oss-32bit, alsa-plugins-pulse, alsa-plugins-pulse-32bit, alsa-utils, alsa-oss, alsa-docs, alsa, alsa-plugins, alsa-devel, alsa-plugins-32bit installed on my 64-bit openSUSE, so in my case that command would be:

Code:

zypper install alsa-oss-32bit alsa-plugins-pulse alsa-plugins-pulse-32bit alsa-utils alsa-oss alsa-docs alsa alsa-plugins alsa-devel alsa-plugins-32bit libasound2

you have a 32-bit PC, so you should have less alsa applications than I have. Don't forget libasound2.

Again, you can tell what alsa apps you have installed by typing:

rpm -qa '*alsa*'

... the intent here is to update them to 1.0.21 of alsa.

#15 (**permalink**) 01-Nov-2009, 08:59

On Sun, 01 Nov 2009 09:36:03 +0000, oldcpu wrote:

> Code:
> --------------------
> !!ALSA Version
> !!------------
>
> Driver version: 1.0.21-git20091031 Library version: 1.0.18
> Utilities version: 1.0.18
> --------------------
>
> This tells me the last 3 (of the six commands) worked, but the two
> 1.0.18 entries suggests to me your PC still has the old alsa, alsa-docs,
> .. etc ... and hence the 2nd command: "zypper install alsa alsa-docs
> libasound2 .... < what ever else you added > " failed to work/update
> your alsa versions.

I didn't add anything else to the list. The original attempt installed
alsa-docs but told me that alsa and libasound2 were already installed.
Now that alsa-docs is there, all I get from zypper is:

Code:
--------------------
linux:/home/dgersic # zypper ar http://download.opensuse.org/repositories/
multimedia:/libs/openSUSE_11.1/ multimedia
Adding repository 'multimedia' [done]
Repository 'multimedia' successfully added
Enabled: Yes
Autorefresh: No
URI: http://download.opensuse.org/reposit...timedia:/libs/
openSUSE_11.1/

linux:/home/dgersic # zypper install alsa alsa-docs libasound2
New repository or package signing key received:
Key ID: DD5EB0F5E1BF12F6
Key Name: multimedia:libs OBS Project <multimedia:libs@build.opensuse.org>
Key Fingerprint: 1AA7393A01D3446EE2CB3183DD5EB0F5E1BF12F6
Repository: multimedia

Do you want to reject the key, trust temporarily, or trust always? [R/t/
a/?]: t
Building repository 'multimedia' cache [done]
Loading repository data...
Reading installed packages...
'alsa' is already installed.
'alsa-docs' is already installed.
'libasound2' is already installed.
Resolving package dependencies...
Nothing to do.
linux:/home/dgersic # zypper rr multimedia
Removing repository 'multimedia' [done]
Repository 'multimedia' has been removed.
--------------------

> You could confirm that by typing:
> *::rpm -qa '*alsa*'::*

Code:
--------------------
linux:/home/dgersic # rpm -qa '*alsa*'
alsa-devel-1.0.18-8.12.1
alsa-utils-1.0.18-6.4
alsa-plugins-pulse-1.0.18-6.12
alsa-docs-1.0.21-43.1
alsa-plugins-1.0.18-6.12
alsa-1.0.18-8.12.1
alsa-driver-kmp-pae-1.0.21.20091031_2.6.27.37_0.1-1.1
alsa-oss-1.0.17-1.37
--------------------

> I suspect with the exception of alsa-driver-kmp-pae (which will be
> 1.0.21) the rest of your alsa apps will be 1.0.18.

Yep, they are.

> I have seen this problem happen before where users still have the
> installation CD/DVD selected as a repository in YaST/zypper, with a
> higher priority than any new adhoc repository.

The DVD repo is disabled by the simple expediency of the DVD being in a
case on my desk. So it's not hitting the DVD source. Just to see if it
would help, I disabled everything but opensuse/opensuse-update/oss/non-oss
then tried zypper again with the same results. Then I disabled everything
that wasn't the 'multimedia' repo and tried again, with the same results.

Code:
--------------------
linux:/home/dgersic # zypper lr
# | Alias | Name | Enabled |
Refresh
---+--------------------------+--------------------------+---------
+--------
1 | GNOME:STABLE:2.26 | GNOME:STABLE:2.26 | No |
Yes
2 | KDE:KDE4:Factory

esktop | KDE:KDE4:Factory

esktop | No |
Yes
3 | Libdvdcss repository | Libdvdcss repository | No |
Yes
4 | Packman Repository | Packman Repository | No |
Yes
5 | X11

GL | X11

GL | No |
Yes
6 | devel:tools:building | devel:tools:building | No |
Yes
7 | multimedia | multimedia | Yes |
No
8 | openSUSE 11.1-0 | openSUSE 11.1-0 | No |
No
9 | repo | NVIDIA Repository | No |
Yes
10 | repo-debug | openSUSE-11.1-Debug | No |
Yes
11 | repo-non-oss | openSUSE-11.1-Non-Oss | No |
Yes
12 | repo-oss | openSUSE-11.1-Oss | No |
Yes
13 | repo-source | openSUSE-11.1-Source | No |
Yes
14 | repo-update | openSUSE-11.1-Update | No |
Yes
--------------------

Looking at the above URL with a web browser, I can see that newer alsa
and libasound2 packages are actually available. Should I just download
the rpms and install them myself, bypassing zypper here?

> and again, for the command "zypper install alsa alsa-docs libasound2"
> expand that command so as to update your alsa apps.

Using the output from rpm -qa *alsa*, I went with:

Code:
--------------------
linux:/home/dgersic # zypper install alsa alsa-docs libasound2 alsa-devel
alsa-utils alsa-plugins-pulse alsa-plugins alsa-oss
Loading repository data...
Reading installed packages...
'alsa' is already installed.
'alsa-docs' is already installed.
'libasound2' is already installed.
'alsa-devel' is already installed.
'alsa-utils' is already installed.
'alsa-plugins-pulse' is already installed.
'alsa-plugins' is already installed.
'alsa-oss' is already installed.
Resolving package dependencies...
Nothing to do.
--------------------

--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

oldcpu · #16 (**permalink**) 01-Nov-2009, 09:21

Quote:

Originally Posted by David Gersic

Code:

linux:/home/dgersic # rpm -qa '*alsa*'
alsa-devel-1.0.18-8.12.1
alsa-utils-1.0.18-6.4
alsa-plugins-pulse-1.0.18-6.12
alsa-docs-1.0.21-43.1
alsa-plugins-1.0.18-6.12
alsa-1.0.18-8.12.1
alsa-driver-kmp-pae-1.0.21.20091031_2.6.27.37_0.1-1.1
alsa-oss-1.0.17-1.37

Ok, that confirms the assessment I made based on the diagnostic script, that the alsa versions were not updated.

Quote:

Originally Posted by David Gersic

Code:

linux:/home/dgersic # zypper lr
#  | Alias                    | Name                     | Enabled |
Refresh
---+--------------------------+--------------------------+---------
+--------
1  | GNOME:STABLE:2.26        | GNOME:STABLE:2.26        | No      | Yes
2  | KDE:KDE4:Factory:Desktop | KDE:KDE4:Factory:Desktop | No      | Yes
3  | Libdvdcss repository     | Libdvdcss repository     | No      | Yes
4  | Packman Repository       | Packman Repository       | No      | Yes
5  | X11:XGL                  | X11:XGL                  | No      | Yes
6  | devel:tools:building     | devel:tools:building     | No      | Yes
7  | multimedia               | multimedia               | Yes     | No
8  | openSUSE 11.1-0          | openSUSE 11.1-0          | No      | No
9  | repo                     | NVIDIA Repository        | No      | Yes
10 | repo-debug               | openSUSE-11.1-Debug      | No      | Yes
11 | repo-non-oss             | openSUSE-11.1-Non-Oss    | No      | Yes
12 | repo-oss                 | openSUSE-11.1-Oss        | No      | Yes
13 | repo-source              | openSUSE-11.1-Source     | No      | Yes
14 | repo-update              | openSUSE-11.1-Update     | No      | Yes
--------------------

What I can not tell from that is the relative priority of the repositories, nor what URL is associated with which label. The command:

zypper lr -d

yields more useful information.

Quote:

Originally Posted by David Gersic

Code:

linux:/home/dgersic # zypper install alsa alsa-docs libasound2 alsa-devel
alsa-utils alsa-plugins-pulse alsa-plugins alsa-oss

That looks good.

For the zypper command to work, the repository "multimedia" needs a higher priority (ie a lower priority number) than the OS and then the update directories. For the software manager to say the application is "already installed" means it can get the application from a repository whose priority is higher (lower number) than the multimedia.

That can easily be addressed by going to YaST > Software > Software Repositories and ensure that OSS and Update priority is higher than that of the multimedia.

I can NOT replicate this on my PC without DELIBERATELY changing the OSS and Update repos priority to some high number (ie it does not happen with their default priorities on my PC) so I can not explain why it has happened. But I know it is easy to fix if you follow my advice above.

hendersj · #17 (**permalink**) 01-Nov-2009, 13:36

On Sun, 01 Nov 2009 05:59:28 +0000, David Gersic wrote:

>> I wouldn't even reinstall it, based on my own experience - many people
>> have reported having problems with pulseaudio, I'd remove that from the
>> picture and diagnose from there.
>
> I could do that, except that in removing it, things got worse. Or at
> least they seem worse without it.

How so? You may need to restart the X session and make sure the
processes are not running, but the system definitely should be able to
operate without pulse - it's a layer between applications and the sound
hardware, and from everything I've read, there aren't applications that
depend on it. (Most consider it an unnecessary layer because it just
adds more layers to diagnose).

>> When you don't get any input, do you get a sort of clicking noise at
>> all (might have to listen with headphones)? That was the symptom I
>> had.
>
> Nope. Nothing at all.

Sounds like a different problem then - oldcpu has much more experience
than I do with sound issues in general....you're in good hands with
him. :-)

Jim

--
Jim Henderson
openSUSE Forums Moderator

oldcpu · #18 (**permalink**) 01-Nov-2009, 13:49

Quote:

Originally Posted by oldcpu

That can easily be addressed by going to YaST > Software > Software Repositories and ensure that OSS and Update priority is higher than that of the multimedia.

I meant to say there that OSS and Non-OSS have a higher priority "number" but in fact are LOWER in priority than multimedia. Say give multimedia a priority of 20 and OSS and Non-OSS a priority of 100.

oldcpu · #19 (**permalink**) 01-Nov-2009, 15:07

Quote:

Originally Posted by oldcpu

I meant to say there that OSS and Non-OSS have a higher priority "number" but in fact are LOWER in priority than multimedia. Say give multimedia a priority of 20 and OSS and Non-OSS a priority of 100.

I should have included "Update" with OSS and Non-OSS. ... ie ensure the multimedia repos has a higher priority (lower priority #) than those 3 repos ... ie say those 3 with 100 and multimedia with 20.

Then update the alsa to 1.0.21.

#20 (**permalink**) 01-Nov-2009, 19:59

esktop | KDE:KDE4:Factory

esktop | No |
Yes | 99 | rpm-md | http://download.opensuse.org/repositories/
KDE:/KDE4:/Factory:/Desktop/openSUSE_11.1/ |
3 | Libdvdcss repository | Libdvdcss repository | No |
Yes | 99 | rpm-md | http://suse.linuxin.dk/
repo/11.1/ |
4 | Packman Repository | Packman Repository | No |
Yes | 99 | rpm-md | http://ftp.skynet.be/pub/packman/
suse/11.1/ |
5 | X11

GL | X11

GL | No |
Yes | 99 | rpm-md | http://download.opensuse.org/repositories/
X11:/XGL/openSUSE_11.1_GNOME_Factory/ |
6 | devel:tools:building | devel:tools:building | No |
Yes | 99 | rpm-md | http://download.opensuse.org/repositories/
devel:/tools:/building/openSUSE_11.1/ |
7 | multimedia | multimedia | Yes |
No | 20 | NONE | http://download.opensuse.org/repositories/
multimedia:/libs/openSUSE_11.1/ |
8 | openSUSE 11.1-0 | openSUSE 11.1-0 | No |
No | 99 | yast2 | cd:///?devices=/dev/
sr0 |
9 | repo | NVIDIA Repository | No |
Yes | 99 | rpm-md | http://download.nvidia.com/
opensuse/11.1 |
10 | repo-debug | openSUSE-11.1-Debug | No |
Yes | 100 | NONE | http://download.opensuse.org/debug/
distribution/11.1/repo/oss/ |
11 | repo-non-oss | openSUSE-11.1-Non-Oss | Yes |
Yes | 100 | yast2 | http://download.opensuse.org/
distribution/11.1/repo/non-oss/ |
12 | repo-oss | openSUSE-11.1-Oss | Yes |
Yes | 100 | yast2 | http://download.opensuse.org/
distribution/11.1/repo/oss/ |
13 | repo-source | openSUSE-11.1-Source | No |
Yes | 100 | NONE | http://download.opensuse.org/source/
distribution/11.1/repo/oss/ |
14 | repo-update | openSUSE-11.1-Update | Yes |
Yes | 99 | rpm-md | http://download.opensuse.org/
update/11.1/
--------------------

> For the zypper command to work, the repository "multimedia" needs a
> higher priority (ie a lower priority number) than the OS and then the
> update directories. For the software manager to say the application is
> "already installed" means it can get the application from a repository
> whose priority is higher (lower number) than the multimedia.

So I changed the 'multimedia' temporary repo to priority 20 as you can
see. The results were less than spectacular:

Code:
--------------------
linux:/home/dgersic # zypper install alsa alsa-docs libasound2 alsa-devel
alsa-utils alsa-plugins-pulse alsa-plugins alsa-oss
New repository or package signing key received:
Key ID: DD5EB0F5E1BF12F6
Key Name: multimedia:libs OBS Project <multimedia:libs@build.opensuse.org>
Key Fingerprint: 1AA7393A01D3446EE2CB3183DD5EB0F5E1BF12F6
Repository: multimedia

Do you want to reject the key, trust temporarily, or trust always? [R/t/
a/?]: t
Building repository 'multimedia' cache [done]
Loading repository data...
Reading installed packages...
'alsa' is already installed.
'alsa-docs' is already installed.
'libasound2' is already installed.
'alsa-devel' is already installed.
'alsa-utils' is already installed.
'alsa-plugins-pulse' is already installed.
'alsa-plugins' is already installed.
'alsa-oss' is already installed.
Resolving package dependencies...
Nothing to do.
--------------------

> I can NOT replicate this on my PC without DELIBERATELY changing the OSS
> and Update repos priority to some high number

The priorities on the other repos are all defaults. As far as I know, I
haven't changed them.

> (ie it does not happen
> with their default priorities on my PC) so I can not explain why it has
> happened. But I know it is easy to fix if you follow my advice above.

Is there a way to tell zypper to just "shut up and do it anyway"? In
looking over its various options, I'm not seeing one.

--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode