Dell latitude e6400 intel code 2 duo running opensuse 11.2 64 bit Installing the card, I get this error message. --------------------------------------------------------------------- An error occurred during the installation of SB0400 Audigy2 value The kernel module snd-emu-10k1 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters. -------------------------------- Running the opensuse hardware probe, a truncated version of the output indicates Bus ID : 4 Bus: PCI (I don’t have email on the notebook installation, but could provided more data if needed). -------------------------------------------------- ALSA driver version 1.0.23-gti20100614 compiled on Jun 13 2010 for kernel 2.6.31.12-0.2-desktop (SMP) Suggestions?
My appologies for that unreadable message. I did a cut and paste from another forum. Here is the message in a more readable format
kde desktop
Dell latitude e6400 intel code 2 duo running opensuse 11.2 64 bit
Installing the card, I get this error message.
An error occurred during the installation of SB0400 Audigy2 value
The kernel module snd-emu-10k1 for sound support could not be loaded.
This can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
Running the opensuse hardware probe, a truncated version of the
output indicates
Bus ID : 4 Bus: PCI
(I don’t have email on the notebook installation, but could provided more
data if needed).
ALSA driver version 1.0.23-gti20100614
compiled on Jun 13 2010 for kernel 2.6.31.12-0.2-desktop (SMP)
For those of us (like me) who are a bit slow in understanding things, could you be a bit more “simple” as to describing your actual PC symptoms wrt sound?
Do you have any sound at all with openSUSE-11.2 Linux?
provide the URLs (of a summary webpage) that are created by running the diagnostic script noted here: SDB:AudioTroubleshooting - openSUSE - Script to run to obtain detailed information. On openSUSE-11.1 and newer that will ask you to run the script /usr/sbin/alsa-info.sh and after the script finishes it will give you a URL to pass to the support personnel. Please post here the output URL. Just the URL. You may need to run that script twice (the first time with root permissions to update in the /usr/sbin directory, and the second time to get the URL).
in a terminal, or xterm, or konsole, type: rpm -qa ‘alsa’ #and post output here
in a terminal, or xterm, or konsole, type: rpm -qa ‘pulse’ #and post output here
in a terminal, or xterm, or konsole, type: rpm -q libasound2 #and post output here
in a terminal, or xterm, or konsole, type: uname -a #and post output here
…
for openSUSE-11.2 or later, in a terminal, or xterm, or konsole, type: cat /etc/modprobe.d/50-sound.conf #and post output here
u1Nb.0_TCV1hO821:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
+u4I.LT3Ovshg5NE:iMic USB audio system
alias snd-card-1 snd-usb-audio
gariac@linux-bsd3:~>
Now the funny thing is the card NOW plays audio after a fresh boot. Kmix shows a console (controls?) for the card. Alsamixer shows the card as well. But after trying to install the card, it has now disappeared from alsamixer. The output for the modprob was after I tried to install via yast.
I will do a fresh boot and see if things change. I should also point out that I just did an install of the card under windows 7, so maybe it changed the card.
Here is a “fresh” output from the modprobe right after booting. Yast was not run.
options snd slots=snd-hda-intel,snd-usb-audio
u1Nb.0_TCV1hO821:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
+u4I.LT3Ovshg5NE:iMic USB audio system
alias snd-card-1 snd-usb-audio
gariac@linux-bsd3:~>
I’m not sure if this is of any value, but Alsamixer shows the card as SB0530.
Kmix indicates SB Audigy 2 ZS Notebook [SB0530
Amrock sees the card in two manners. The first is:
SB Audigy 2 ZS Notebook [SB0530](rev.0 serial 0x20011102) (ADC Capture/Standard PCM Playback)
The second is:
SB Audigy 2 ZS Notebook SB0530, ADC Capture/Standard PCM Playback (side speakers)
provide the URLs (of a summary webpage) that are created by running the diagnostic script noted here: SDB:AudioTroubleshooting - openSUSE - Script to run to obtain detailed information. On openSUSE-11.1 and newer that will ask you to run the script /usr/sbin/alsa-info.sh and after the script finishes it will give you a URL to pass to the support personnel. Please post here the output URL. Just the URL. You may need to run that script twice (the first time with root permissions to update in the /usr/sbin directory, and the second time to get the URL).
in a terminal, or xterm, or konsole, type: rpm -qa ‘alsa’ #and post output here
in a terminal, or xterm, or konsole, type: rpm -qa ‘pulse’ #and post output here
in a terminal, or xterm, or konsole, type: rpm -q libasound2 #and post output here
in a terminal, or xterm, or konsole, type: uname -a #and post output here
…
for openSUSE-11.2 or later, in a terminal, or xterm, or konsole, type: cat /etc/modprobe.d/50-sound.conf #and post output here
Can you please also run the diagnostic script that I twice requested above? You can do that from openSUSE-11.2 with your PC connected to the internet by typing as a regular user in a terminal:
/usr/sbin/alsa-info.sh
select the share/upload option, and that should provide you a website/URL address where the information is posted. Please post here the URL address.
If for some reason it does NOT give you a website/url address, then run the script again with the no-upload option:
/usr/sbin/alsa-info.sh --no-upload
and that will create a /tmp/alsa-info.txt file. Please open that alsa-info.txt file with a text editor, copy the contents, and then paste the contents on the web site : New - Pastie and press paste on that web site. That will post the contents to a new website and please then take the new website/url address and post that here. JUST the URL address.
That diagnostic script provides a LOT of information.
where sound card 0 using HD-Intel. Later on this script is see this:
!!PCI Soundcards installed in the system
!!--------------------------------------
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
04:00.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
and finally the Intel Audio device is noted to be a “Codec: IDT 92HD71B7X”
I then compared it to the 50-sound.conf file content you provided:
and its a bit more clear to me.
Those two are inconsistent! the 50-sound.conf files has a sound card 0 and a sound card 1. The script indicates a sound card 0 and a sound card 2 (with no sound card 1). Did you change the configuration between the two?
What sound device are you trying to get sound out of ?
Reading this:
suggests to me you are trying to hot plug the USB creative sound device ??
And perhaps then the problem you are encountering is hot plugging that device does not work well?
There is small guidance here given for hot plugging USB audio devices (it says headphones but it applies to speakers): USB headphones - openSUSE
Note also the order of sound devices in KDE’s configure destkop > multimedia should also match the order of sound devices in YaST’s > hardware > sound in order for things to work well.
For background, I have some software that isn’t working with Intel HDA. [On desktop systems, I put in a Diamond XS71 and be done with the software problems. Better to spend $20 on a card rather than beating your head to make the software work.]
I have tried USB audio as an alternative. At the time I ran all those diagnostics, the Griffin imic was not plugged in. However, it works fine with your basic linux programs (Audacity, aplay, etc.), just not the oddball software I’m trying to run. In the past I had a bit of trouble with USB audio, but the current alsa usb seems to work just fine for most programs.
The Audigy card is simply another attempt to get a card running that might work with this software. [This software does run on my desktop PC with the Diamond XS71 card.]
Regarding this guestion:
"Those two are inconsistent! the 50-sound.conf files has a sound card 0 and a sound card 1. The script indicates a sound card 0 and a sound card 2 (with no sound card 1). Did you change the configuration between the two?
What sound device are you trying to get sound out of ?"
I’m not sure I understand the question. Would it simplify things for me to simply delete the usb sound. It take no effort to install usb sound again should I want to use it later.
I don’t follow the “change configuration between the two.” I haven’t edited any system files. I make it a point when possible just to use the opensuse tools like yast to set up the PC.
I was trying to get sound out of the Audigy card. Since it hasn’t installed correctly via yast, I really don’t know how aplay and other programs manage to use the card. It is like the installation worked halfway.
Maybe I can explain a bit how I understand some sound aspects work, and you can read it and see if it helps?
In openSUSE’s YaST > Hardware > Sound it is possible to save the priority order of the sound devices (for cases where there are more than one devices). In fact, if you look under YaST > Hardware > Sound > Other, you sound see an entry for changing the order of the sound device. Selecting that, will change the entry in the /etc/modprobe.d/50-sound.conf file, so that next time your restart alsa, it will use the order of sound devices in the 50-sound.conf file. Alsa is restarted during every reboot, and it is possible to restart alsa with a specific command (with root permissions).
In KDE-4, under the Menu > Configure Desktop > Multimedia, the flexibility was provided to have KDE select different sound devices. However experience has indicated to me, that for many users if the order of sound devices in Menu > Configure Desktop > Multimedia does not match the order of devices in YaST > Hardware > Sound, then sound may not work. Plus, when one changes the order in YaST, it is NOT automatically changed in KDE, and hence there can be problems.
If one plugs in a USB audio device (such as headphones or speakers) and then removes in, plugs it back in, etc … there is a chance it could because of some autodection software cause the order of devices to change, impacting the sound.
Now I do NOT have a USB sound device (such as USB headphones nor USB speakers) so I can not provide specific advice, other than to provide the above caution.
I deleted the Griffin imic and the Audigy loaded. It doesn’t record, but this might be pilot error. The Audigy shows up as two different devices, which appears to be playback and capture, so perhaps some more hacking will get it to record.