Sound card(?) not found Asus MB M2N-MX SE Plus, MCP61

English Hardware
#1

alsaconf won’t find the sound card. I installed the sound drivers that
came with MB and modified the modprobe.conf file per instructions. When
that failed I removed the drivers and installed the drivers with one
click at webpin. Alsaconf still fails. Lspci identifies the sound device
as 00:05. There must be something I’ve missed. I can’t find anything to
define what alsaconf is looking for. Here’s the insert I put in
modprobe.conf;

#############################################################################

CvwD.RCKed0PPX+4:MCP61 High Definition Audio

alias snd-card-0 snd-hda-intel

snd-xxxx is the card ID.

ALSA portion

alias char-major-116 snd
alias snd-card-0 snd-5

OSS/Free portion

alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

card #1

alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
############################################################################

Larry

#2

I recommend you remove what you put in modprobe.conf. Its not necessary and it could cause problems later.

If you can avoid using the driver that comes with the MB, then I would recommend avoiding it. The reason I give this recommendation is you are unlikely to get much support using that driver. Instead if you use the alsa driver that comes with openSUSE , a number of us will attempt to help you on this forum. Plus if you write a bug report on openSUSE (to attempt to get a bug fixed in the audio) you are more likely to get the bug addressed if you are using the alsa driver, than you are if you are using the MB supplied driver.

The exception to that would be if your motherboard comes with an X-Fi . In which case, just ignore my post. That hardware is NOT supported well under alsa yet (although slow advances are being made). If using X-Fi I can not help.

I do not know how new you are to openSUSE Linux. If new, it might help first if you read some openSUSE concepts: Concepts - openSUSE

Then after reading that, try working your way through the openSUSE audio troubleshooting guide:
SDB:AudioTroubleshooting - openSUSE

Note, when testing if you have sound, please copy and paste the following speaker-test into a Gnome terminal or a kde konsole:

speaker-test -Dplug:front -c2 -l5 -twav
Note Linux is case sensitive, and “D” is not the same as “d”. To stop the above test, while the konsole/xterm has the mouse focus, press <CTRL><C> on the keyboard. Note you should check your mixer settings (kmix if using KDE, and alsamixer if using Gnome) to ensure that PCM and Master Volume are set around 75%. Note the test for surround sound is different.

If that test yields errors (and its not uncommon to get errors there), try instead this more simple test: speaker-test -c2 -l5 -twavYou should hear a female voice saying ‘FRONT LEFT’, ‘FRONT RIGHT’ five times. Its quite common that one of those speaker tests will work and one will NOT work, so don’t be distressed if that is the case. IF that test gives sound, stop now, post that the sound test gives sound, and we will look at other possible causes for your applications not giving you the sound you want (such as missing codecs, using the wrong packaged version … etc … ).

Try those speaker-tests as both a regular user, and with root permissions. If you have a headset, try with your headset plugged in, and also with your headset not plugged in (for speakers).

Assuming no sound, can you provide more very detailed information so a good recommendation can be given? If using openSUSE-11.1, you can do that, with your laptop connected to the internet, by opening a gnome-terminal or a kde konsole and typing “su” (no quotes - enter root password) and then and typing and executing twice :
/usr/sbin/alsa-info.shthe first time it will ask to update. Select YES for the update. The second time that will run a diagnostic script and post the output to a web site on the Internet. It will give you the URL of the web site. Please post that URL here. JUST the URL.

Also, please copy and paste the following commands one line at a time into a gnome-terminal or a konsole and post here the output: rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound

#3

oldcpu wrote:
> lggriffin;1967531 Wrote:
>> alsaconf won’t find the sound card. I installed the sound drivers that
>> came with MB and modified the modprobe.conf file per instructions.
>> When
>> that failed I removed the drivers and installed the drivers with one
>> click at webpin. Alsaconf still fails. Lspci identifies the sound
>> device
>> as 00:05. There must be something I’ve missed. I can’t find anything
>> to
>> define what alsaconf is looking for. Here’s the insert I put in
>> modprobe.conf;I recommend you remove what you put in modprobe.conf. Its not necessary
> and it could cause problems later.
>
Removed insert from modprobe.conf

> If you can avoid using the driver that comes with the MB, then I would
> recommend avoiding it. The reason I give this recommendation is you are
> unlikely to get much support using that driver. Instead if you use the
> alsa driver that comes with openSUSE , a number of us will attempt to
> help you on this forum. Plus if you write a bug report on openSUSE (to
> attempt to get a bug fixed in the audio) you are more likely to get the
> bug addressed if you are using the alsa driver, than you are if you are
> using the MB supplied driver.
>
I removed the MB drivers after they didn’t work

> The exception to that would be if your motherboard comes with an X-Fi .
> In which case, just ignore my post. That hardware is NOT supported well
> under alsa yet (although slow advances are being made). If using X-Fi I
> can not help.
>
NOT using X-Fi. This is MCP61, which was supported a couple of kernel
releases back by ALSA.

> I do not know how new you are to openSUSE Linux. If new, it might help
> first if you read some openSUSE concepts: ‘Concepts - openSUSE’
> (http://en.opensuse.org/Concepts)
>
The first time I worked with Linux was about 10 years ago. I gave up
when I couldn’t get X_86 to run on a Toshiba satellite.

This experience started about a month ago with 11.1 64 bit. I installed
10.3 as sugggested after 11.1 changed the drive IDs when trying to get
more space for the root partition. I now have 20GB for /root and /home.

I’ve been using the Administrators guide at;
http://tldp.org/LDP/sag/html/index.html
I’m seem to find what I want there. Though trying to find the right
command is going to be a PITA for some time to come. I’ve subscribed to
to the Forums via News Groups, and have spent a lot of time reading
through them.

> Then after reading that, try working your way through the openSUSE
> audio troubleshooting guide:
> ‘SDB:AudioTroubleshooting - openSUSE’
> (http://en.opensuse.org/SDB:AudioTroubleshooting)
>
Been there a half dozen times.

> Note, when testing if you have sound, please copy and paste the
> following speaker-test into a Gnome terminal or a kde konsole:
>
> :: speaker-test -Dplug:front -c2 -l5 -twav::

Here is the error I get.
Linux:/home/Larry # speaker-test -Dplug:front -c2 -l5 -twav

speaker-test 1.0.19

Playback device is plug:front
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
ALSA lib pcm.c:2014:(snd_pcm_open_conf) Invalid type for PCM front
definition (id: front, value: cards.pcm.front)
Playback open error: -22,Invalid argument

> Note Linux is case sensitive, and “D” is not the same as “d”. To stop
> the above test, while the konsole/xterm has the mouse focus, press
> <CTRL><C> on the keyboard. Note you should check your mixer settings
> (kmix if using KDE, and alsamixer if using Gnome) to ensure that PCM and
> Master Volume are set around 75%. Note the test for surround sound is
> different.

Here is the error I get.
Linux:/home/Larry # alsamixer

alsamixer: function snd_ctl_open failed for default: No such device

I got a similar error from kmix. but I can’t reproduce it.

>
> If that test yields errors (and its not uncommon to get errors there),
> try instead this more simple test: ::speaker-test -c2 -l5
> -twav::You should hear a female voice saying ‘FRONT LEFT’,
> ‘FRONT RIGHT’ five times. Its quite common that one of those speaker
> tests will work and one will NOT work, so don’t be distressed if that is
> the case. IF that test gives sound, stop now, post that the sound test
> gives sound, and we will look at other possible causes for your
> applications not giving you the sound you want (such as missing codecs,
> using the wrong packaged version … etc … ).
>
> Try those speaker-tests as both a regular user, and with root
> permissions. If you have a headset, try with your headset plugged in,
> and also with your headset not plugged in (for speakers).
>
I’ve posted the results of one the speaker test above. The problem seems
to be MCP61 is not being found. I’ve enabled it in the BIOS and set it
to PNP.

> Assuming no sound, can you provide more very detailed information so a
> good recommendation can be given? If using openSUSE-11.1, you can do
> that, with your laptop connected to the internet, by opening a
> gnome-terminal or a kde konsole and typing “su” (no quotes - enter root
> password) and then and typing and executing twice :
> ::/usr/sbin/alsa-info.sh::the first time it will ask
> to update. Select YES for the update. The second time that will run a
> diagnostic script and post the output to a web site on the Internet. It
> will give you the URL of the web site. Please post that URL here. JUST
> the URL.
>
I’ve posted the alsa info with the other info on the bottom, including
the output from lspci. I believe the audio device 00:05 is what needs to
be found by alsa.

> Also, please copy and paste the following commands one line at a time
> into a gnome-terminal or a konsole and post here the output:
> ::rpm -qa | grep alsa
> rpm -qa | grep pulse
> rpm -q libasound2
> uname -a
> cat /etc/modprobe.d/sound::
>
>

Linux:/home/Larry # lspci
00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio
(rev a2)
00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2)
00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0d.0 VGA compatible controller: nVidia Corporation GeForce 6100
nForce 430 (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
Linux:/home/Larry #

Your ALSA information is located at
http://www.alsa-project.org/db/?f=a3c3c44bf739a5a5ad3436404636405f66fa217d

Please inform the person helping you.

Linux:/home/Larry # rpm -qa | grep alsa
alsa-plugins-1.0.19.git20090303-1.8
alsa-tools-debuginfo-1.0.14-38
alsa-tools-1.0.14-38
alsa-oss-1.0.14-23
alsa-utils-1.0.19.git20090319-1.2
alsa-firmware-1.0.14-24
alsa-tools-gui-1.0.14-38
alsa-1.0.14-31.2

Linux:/home/Larry # rpm -qa | grep pulse
(no output)

Linux:/home/Larry # rpm -qa | grep libasound2
libasound2-32bit-1.0.14-31.2
libasound2-1.0.14-31.2

Linux:/home/Larry # uname -a
Linux Linux 2.6.22.19-0.2-default #1 SMP 2008-12-18 10:17:03 +0100
x86_64 x86_64 x86_64 GNU/Linux

Linux:/home/Larry # cat /etc/modprobe.d/sound
options snd-hda-intel enable_msi=1
options snd-hda-intel enable=1 index=0

CvwD.RCKed0PPX+4:MCP61 High Definition Audio

alias snd-card-0 snd-hda-intel

#4

Thanks! I think I can help.

I note this from the script:

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

Driver version:     
Library version:    
Utilities version:  1.0.19

that typically means your driver is not being recognized. I note your alsa rpms are a mix of 1.0.14 and 1.0.19 git versions. In my experience that will cause problems. I recommend you bring all your alsa versions up to the latest git. Also, once you go down the “git path” (pardon the expression) you pretty much need to install alsa-driver-kmp-yourkernelversion rpm. You can do the necessary update, by opening a konsole/terminal, and with root permissions, and with your PC connected to the internet, and send the following six zypper commands (that I tuned specifically for your setup) in the exact sequence below, executing one at a time:

zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_10.3/ multimedia

zypper install alsa alsa-plugins alsa-tools-gui alsa-utils alsa-tools alsa-firmware alsa-tools-debuginfo libasound2

zypper rr multimedia

zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_10.3_Update/ multimedia

zypper install alsa-driver-kmp-default

zypper rr multimedia

I do not believe you need alsa-tools-debuginfo, although I included it in the above update command. Do you actually know of any specific benefit you get from that rpm ?

After doing that update, restart your PC and test your sound. Its possible the “enable_msi=1” is no longer needed in your /etc/modprobe.d/sound file (I don’t know). I think enable_msi=0 is the default.

#5

Thank You! That appears to have solved the problem. Good responses now
from kmix and the speaker test. I can think about doing something else
besides banging on the computer today. :slight_smile:

I probably don’t need the GIT and debuginfo, but I’ll leave well enough
alone for the time being.

Thanks again,
Larry

oldcpu wrote:
> !!ALSA Version
> !!------------
>
> Driver version:
> Library version:
> Utilities version: 1.0.19
> --------------------
> that typically means your driver is not being recognized. I note your
> alsa rpms are a mix of 1.0.14 and 1.0.19 git versions. In my experience
> that will cause problems. I recommend you bring all your alsa versions
> up to the latest git. Also, once you go down the “git path” (pardon the
> expression) you pretty much need to install
> alsa-driver-kmp-yourkernelversion rpm. You can do the necessary update,
> by opening a konsole/terminal, and with root permissions, and with your
> PC connected to the internet, and send the following six zypper commands
> (that I tuned specifically for your setup) in the exact sequence below,
> executing one at a time:
> Code:
> --------------------
> zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_10.3/ multimedia
> --------------------
>
> Code:
> --------------------
> zypper install alsa alsa-plugins alsa-tools-gui alsa-utils alsa-tools alsa-firmware alsa-tools-debuginfo libasound2
> --------------------
>
> Code:
> --------------------
> zypper rr multimedia
> --------------------
>
> Code:
> --------------------
> zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_10.3_Update/ multimedia
> --------------------
>
> Code:
> --------------------
> zypper install alsa-driver-kmp-default
> --------------------
>
> Code:
> --------------------
> zypper rr multimedia
> --------------------
>
>
> I do not believe you need alsa-tools-debuginfo, although I included it
> in the above update command. Do you actually know of any specific
> benefit you get from that rpm ?
>
> After doing that update, restart your PC and test your sound. Its
> possible the “enable_msi=1” is no longer needed in your
> /etc/modprobe.d/sound file (I don’t know). I think enable_msi=0 is the
> default.
>
>

#6

Great, glad to read its working now !

I also started around 10 years ago (closer to 11). I was fortunate in that I had better luck.

Reference openSUSE today … and on a related (but slightly different note), my recommendation is you next spend some time setting up your multimedia applications. Note openSUSE as installed typically is very limited in its multimedia, but if one knows how it is quick and easy to update to first rate multimedia via 3rd party software packages. The way to do that easily is to update your openSUSE’s Software Package Manager’s repositories.

I recommend you add 4 and only 4 repositories to your software package manager. Repositories (as you may remember from reading the concepts page link I provided) are in essence file servers on the internet that have applications, drivers, and codecs. The 4 repositories I recommend are OSS, Non-OSS, Update and Pacman. Just those 4. No others. None. Adding others can cause problems that require slightly above average to advanced knowledge to sort, and IMHO you probably do not want those complications now when you are just starting out again.

So go here for openSUSE 10.3: Repositories/10.3 - openSUSE-Community and follow those instructions to setup OSS, Non-OSS, Update and Packman. No others. If others are enabled then remove them. It is possible the 1st three (OSS, Non-OSS, Update) are already enabled, in which case you only need to add and enable Packman. In particular, do not add videolan repository, as it requires above average openSUSE knowledge to prevent applications/codecs from that repository causing problem with those of Packman.

Once those 4 repositories (OSS, Non-OSS, Update, Packman) are added, with your PC connected to the Internet, go to YaST > Software > Software Management, and change “filter” setting to “search” and search for libxine1 from Novell/SuSE. That is likely installed. Mark it for removal (as it is crippled) but don’t remove it yet … instead search for libxine1 from Packman, and mark it for installation. Note you can tell the packman packaged versions of applications by the “pm” in the version number. Then apply both removal and installation.

Once that is successful, then install the Packman packaged version of amarok, amarok-xine, amarok-packman, xine-ui, smplayer, mplayerplug-in, vlc, libffmpeg0, w32codec-all, libquicktime0, xvidcore, libxvidcore4. The last 5 will help install useful codecs. If there are Novell/SuSE-GmbH versions, replace them with the Packman packaged versions.

When you start amarok, change its sound engine to xine.

Good luck.

#7

oldcpu wrote:

>
> Reference openSUSE today … and on a related (but slightly different
> note), my recommendation is you next spend some time setting up your
> multimedia applications. Note openSUSE as installed typically is very
> limited in its multimedia, but if one knows how it is quick and easy to
> update to first rate multimedia via 3rd party software packages. The
> way to do that easily is to update your openSUSE’s Software Package
> Manager’s repositories.
>
I saw that in your post to Wags79, so I checked mine. I had 8-9
repositories. I deleted them and then added or readded the 4 recommended.

One of the things I need to look into is how Linux handles files,
deleted, not used, defrag.

> I recommend you add 4 and only 4 repositories to your software package
> manager. Repositories (as you may remember from reading the concepts
> page link I provided) are in essence file servers on the internet that
> have applications, drivers, and codecs. The 4 repositories I recommend
> are OSS, Non-OSS, Update and Pacman. Just those 4. No others. None.
> Adding others can cause problems that require slightly above average to
> advanced knowledge to sort, and IMHO you probably do not want those
> complications now when you are just starting out again.
>
> So go here for openSUSE 10.3: ‘Repositories/10.3 - openSUSE-Community’
> (http://opensuse-community.org/Repositories/10.3) and follow those
> instructions to setup OSS, Non-OSS, Update and Packman. No others. If
> others are enabled then remove them. It is possible the 1st three (OSS,
> Non-OSS, Update) are already enabled, in which case you only need to add
> and enable Packman. In particular, do not add videolan repository, as
> it requires above average openSUSE knowledge to prevent
> applications/codecs from that repository causing problem with those of
> Packman.
>
> Once those 4 repositories (OSS, Non-OSS, Update, Packman) are added,
> with your PC connected to the Internet, go to YaST > Software > Software
> Management, and change “filter” setting to “search” and search for
> libxine1 from Novell/SuSE. That is likely installed. Mark it for removal
> (as it is crippled) but don’t remove it yet … instead search for
> libxine1 from Packman, and mark it for installation. Note you can tell
> the packman packaged versions of applications by the “pm” in the version
> number. Then apply both removal and installation.
>
?? What is the reason for “apply both removal and installation”, I’m
learning.

> Once that is successful, then install the Packman packaged version of
> amarok, amarok-xine, amarok-packman, xine-ui, smplayer, mplayerplug-in,
> vlc, libffmpeg0, w32codec-all, libquicktime0, xvidcore, libxvidcore4.
> The last 5 will help install useful codecs. If there are
> Novell/SuSE-GmbH versions, replace them with the Packman packaged
> versions.
>
> When you start amarok, change its sound engine to xine.
>
Thank you again. Right now I want this machine to do photo work, and
musical library.

> Good luck.
>
I’m in that mode, I chose SUSE. :slight_smile:
>

#8

Good point ! My mistake. In 10.3 you need to mark xine-lib (I think its that - from Novell/SuSE) for removal and then mark libxine1 (from packman) for installation.

I messed up the name of the Novell/SuSE-GmbH library for xine in 10.3 (and also in 11.0).

In openSUSE-11.0 and older, the library for xine as packged by Novell/SuSE-GmbH used to be called xine-lib (or something like that) but it was not called libxine1. That Novell/SuSE-GmbH library was crippled and needed to be replaced by the Packman packaged library for xine, which is called libxine1.

If one just tried to install the Packman packaged libxine1 (in openSUSE-11.0 or earlier) the install would fail because of dependency (or some other) problems with the Novell/SuSE-GmbH xine library (called xine-lib or something like that). If one tried to first remove the Novell xine-lib, one would get many other apps also being removed, which would be disastrous.

So for openSUSE-11.0 and earlier, the way to work around this problem was to mark the Novell/SuSE-GmbH xine-lib for removal, but not remove it. Then mark the packman libxine1 for install. Then apply both, and everything worked.

In the case of openSUSE-11.1, Novell/SuSE-GmbH changed the name of the xine library to be libxine1, which is the same as the name that Packman assign to that library. So in the case of openSUSE-11.1, one can simply ask to update libxine1 to the Packman version, and it all works smoothly.

The problem on 11.0 and earlier is something to do with the way libraries in rpms with different names are handled (ie warnings given and no update made). I don’t know the specifics well enough to go beyond what I noted above, but I do know that work around works well.

#9

What sort of photo work?

For my home / family pix, I use digkam to import the videos from my old Canon Ixus camera. And I use gimp to edit my pictures. Typically users either like or hate gimp. Most ex-windows users hate gimp with a passion, but those of us who have learned to use it think its ok. :slight_smile:

For home movies (from still pix) I use kdenlive (which is sort of overkill) to create movies from the ixus still pix and from the ixus 640x480 @ 30fps video clips.

For making panoramic images from many still pictures (successively taken of one piece of scenery) I am bad. I say bad because I run autostitch (an MS-Windows program) under wine. Once I have panoramic images, I use stills2dv to create panning movie clips from the panoramic video.

#10

oldcpu wrote:
> lggriffin;1967845 Wrote:
>> Thank you again. Right now I want this machine to do photo work, and
>> musical library.
> What sort of photo work?
>
Photography is something I’ve been interested in for many years.
Currently most of what I do is product photos for Ebay. I’m only about
60 miles from Yosemite and hope to buy an RV by the end of the month to
spend some time there before I move to Oregon.

> For my home / family pix, I use digkam to import the videos from my old
> Canon Ixus camera. And I use gimp to edit my pictures. Typically users
> either like or hate gimp. Most ex-windows users hate gimp with a
> passion, but those of us who have learned to use it think its ok. :slight_smile:
>
I’m not familar Canon. I have Olmpus some film, some digital, and a Sony
Handicam, I just inherited. You can get adapters for the newer DSLR
cameras and use the old film lenses on them of course you lose the auto
focus and aperture control. Digital SLR cameras are like computers every
2 years there is a better model and deals to be had. That’s were I’m at
with mine.

I’m going to try Gimp again, it’s on par with Photoshop, but there are
some programs beyond Windows Photoeditor, that will do about 80% of what
needs to be done, FastStone, Irfanview, and RawTherapee. RT has gotten
good words on the Olympus mailing list I subscribe to and look to see if
there is a Linux version.

> For home movies (from still pix) I use kdenlive (which is sort of
> overkill) to create movies from the ixus still pix and from the ixus
> 640x480 @ 30fps video clips.
>
That’s good info. I’ve got about a dozen Handicam cassettes to edit. My
Dad for some reason had the Handicam going as he drove down the road.

> For making panoramic images from many still pictures (successively
> taken of one piece of scenery) I am bad. I say bad because I run
> autostitch (an MS-Windows program) under wine. Once I have panoramic
> images, I use stills2dv to create panning movie clips from the panoramic
> video.
>
There is a member of the list that does panoramics. I don’t remember
what he uses to stitch.
>

#11

oldcpu wrote:
> Once that is successful, then install the Packman packaged version of
> amarok, amarok-xine, amarok-packman, xine-ui, smplayer, mplayerplug-in,
> vlc, libffmpeg0, w32codec-all, libquicktime0, xvidcore, libxvidcore4.
> The last 5 will help install useful codecs. If there are
> Novell/SuSE-GmbH versions, replace them with the Packman packaged
> versions.
>
I’m working my way through these and there to some great stuff here.
Yast2 for some reason has gotten really slow downloading the packages.

> When you start amarok, change its sound engine to xine.
>
> Good luck.
>
>

#12

If you have not done so yet, give some thought to disabling ipv6 and removing beagle. That should help performance improve significantly.

#13

New problem YaST2 is crashing when I try to install libxvidore4. I’ve
rebooted, run yast form a terminal, I’m not getting any error message.
I’m wondering if I should start another post for this.

oldcpu wrote:
> lggriffin;1968023 Wrote:
>> Yast2 for some reason has gotten really slow downloading the packages.
> If you have not done so yet, give some thought to disabling ipv6 and
> removing beagle. That should help performance improve significantly.
>
>

#14

You mean libxvidcore4 ?

What happens if you try to install from zypper? ie :

su
zypper install libxvidcore4

#15

My fault, I thought yast had defaulted to a check mark to install, it
was already installed. Have to add zypper to my list of things to learn.

Right now looks like I’ve got my hands full with the audio. Everything
is going great. I’ve got the sound plugged into a spare receiver. I need
to find a good news group for audio on Linux system.

Thanks for all your help. If you need something camers. old chevy
trucks, what ever let me know.

Larry

oldcpu wrote:
> lggriffin;1968253 Wrote:
>> New problem YaST2 is crashing when I try to install libxvidore4. I’ve
>> rebooted, run yast form a terminal, I’m not getting any error message.
>> I’m wondering if I should start another post for this.
> You mean libxvidcore4 ?
>
> What happens if you try to install from zypper? ie :
>
> ::su
> zypper install libxvidcore4::
>
>

#16

If one likes command line, then zypper is pretty good. Here is a guide on zypper use: Zypper/Usage/11.1 - openSUSE

The best multimedia technical forum I have found for both MS-Windows and Linux is doom9 (although it is predominantly MS-Windows). The Linux/Mac subforum area is here: Linux, Mac OS X, & Co - Doom9’s Forum

However it is more video orientated than still photo.

The gimp forum is here: GimpTalk • Index page

Best of luck in your efforts.