[opensuse] arts, alsa and oss
Maybe someone here can point me in the right direction... I'm running SUSE 10.2 and bumping into a problem with sound in a specific application... Cedega and World of Warcraft. Basically I have no sound at all in Cedega/WoW. I've tinkered around a fair bit and searched... posted on the Cedega forums etc etc.. and no solutions yet. As best as I can figure, the problem is with how ALSA and OSS are handled in SUSE. For whatever reason Cedega cannot see any OSS capabilities in SUSE. I've got the ALSA OSS emulation stuff installed... I've checked that. If I run the Cedega tests it fails the OSS support test. If I force it to use OSS in the Cedega setup, I'm met with silence. (As an experiment, I've also tried telling KDE to use OSS instead of ALSA, and it does not work) As a comparison, I've also got Kubuntu (6.10) installed, and under Kubuntu, and sound works perfectly... if I'm using the OSS option in the audio tab (in the setup in Cedega). Also, when I run the Cedega tests, it passes the OSS test. So... the hardware supports whatever is needed, the application works... the game works... just not in SUSE. Does anyone have any suggestions or ideas on this... what can be done to convince Cedega (or anything else for that matter - eg KDE) to use OSS on SUSE? C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 03 January 2007 06:06, Clayton wrote:
Maybe someone here can point me in the right direction...
I'm running SUSE 10.2 and bumping into a problem with sound in a specific application... Cedega and World of Warcraft. Basically I have no sound at all in Cedega/WoW.
I've tinkered around a fair bit and searched... posted on the Cedega forums etc etc.. and no solutions yet.
As best as I can figure, the problem is with how ALSA and OSS are handled in SUSE. For whatever reason Cedega cannot see any OSS capabilities in SUSE. I've got the ALSA OSS emulation stuff installed... I've checked that.
If I run the Cedega tests it fails the OSS support test. If I force it to use OSS in the Cedega setup, I'm met with silence. (As an experiment, I've also tried telling KDE to use OSS instead of ALSA, and it does not work)
As a comparison, I've also got Kubuntu (6.10) installed, and under Kubuntu, and sound works perfectly... if I'm using the OSS option in the audio tab (in the setup in Cedega). Also, when I run the Cedega tests, it passes the OSS test.
So... the hardware supports whatever is needed, the application works... the game works... just not in SUSE.
Does anyone have any suggestions or ideas on this... what can be done to convince Cedega (or anything else for that matter - eg KDE) to use OSS on SUSE?
C.
Run the program from the konsole/console and post the output it prints. Also check the premissions of the /dev/<oss specific> files and make sure they have read access for the users or approp group (e.g. audio, etc). Just for those not in the know to run your program for wine in the console: wine/Cedega <Point2play or whatever it is now><.wine>/c_drive<or whatever>/<you program dir>/<so forth and so on>/<program executable> Then back out/kill program and look at the console data it printed. It may be a config issue with wine/Cedega. Or it may be the permissions as well. Also If you're running AppArmor - Don't! It can interfer with apps and /dev access - it's designed for Enterprise/network servers with access to the outside world - generally overkill for home users and non-servers. I used WineX/Cedega for years and IMHO the state of the generic Wine program is much easier to use (and you don't have to fork out $5 every month). I tried to support the WineX/Cedega project for about 3 years and gave up because I had far better luck running the games I wanted in plain old Wine rather than Cedega - I just don't get what their trying to accomplish (other than making money). Game support is hit or miss and as I said - I can get the old fashioned Wine to do the same and more. HTH, Curtis. -- Spammers Beware: Trespassers will be shot, survivors will be shot again! I don't want a politician I can believe in. I simply want a politician I can believe!
Run the program from the konsole/console and post the output it prints.
Did that, and the output isn't really all that helpful.... ------------ /usr/lib/transgaming_cedega/gddb.py:19: RuntimeWarning: Python C API version mismatch for module gddb_parser: This Python has API version 1013, module gddb_parser has version 1012. import gddb_parser ----------- The gddb parser is the Games Database parser... basically it is used to preconfigure some of the settings to be optimal for the game you've installed. Nothing that should affect the game sound problem I'm having.
check the premissions of the /dev/<oss specific> files and make sure they have read access for the users or approp group (e.g. audio, etc).
Looked in /dev and all audio related things seem to have the right rw permissions.
If you're running AppArmor - Don't! It can interfer with apps and /dev access
Disabled AppArmor... it did not correct the OSS sound related problem, but... but it did speed things up a LOT to have that disabled (was enabled by default from the install). This goes beyond game support in Cedega (I was just twigged to the issue by the sound issues in Cedega), and seems to be a general problem I'm having with OSS support in SUSE 10.2. Anything I want to run and use OSS will not work. MPlayer for example... I usually run that using OSS for my sound because if I use ALSA, I get a very rapidly repeating error "Unable to find simple control 'PCM' 0" that I've never been able to resolve... except for changing over to OSS... which doesn't work in my 10.2 install since OSS (I assume it's alsa-oss) doesn't work at all. Any other suggestions would be more than welcome here. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05-01-2007 at 14:15, Clayton <smaug42@gmail.com> wrote: check the premissions of the /dev/<oss specific> files and make sure they have read access for the users or approp group (e.g. audio, etc).
Looked in /dev and all audio related things seem to have the right rw permissions.
As the poster said you should verify the rights for the group audio, one more thing to remember: in openSUSE 10.2, users are by default NOT in the audio group anymore. Rights to the Sound Device is handled different. Maybe for OSS the group Membership is still required?? I just don't have anything around to test it. Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
As the poster said you should verify the rights for the group audio, one more thing to remember: in openSUSE 10.2, users are by default NOT in the audio group anymore. Rights to the Sound Device is handled different. Maybe for OSS the group Membership is still required?? I just don't have anything around to test it.
Well.... the only way I could get any sound working at all in 10.2 was to add myself to the Audio group. Once I did that, I could get sound via ALSA... but nothing at all via OSS. c -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 05 January 2007 04:39, Clayton wrote:
As the poster said you should verify the rights for the group audio, one more thing to remember: in openSUSE 10.2, users are by default NOT in the audio group anymore. Rights to the Sound Device is handled different. Maybe for OSS the group Membership is still required?? I just don't have anything around to test it.
Well.... the only way I could get any sound working at all in 10.2 was to add myself to the Audio group. Once I did that, I could get sound via ALSA... but nothing at all via OSS.
c
crw-rw----+ 1 root audio 14, 3 2007-01-05 15:34 /dev/dsp Might wanna do a "chmod ugo+r /dev/dsp* The same might hold for the other sound devices. From the print out only the root and audio groups have read access. Depending on the protocol Cedega uses, it might help to give the "o" (other) read access. Also check the dmesg print out after starting Cedega. HTH, Curits. -- Spammers Beware: Trespassers will be shot, survivors will be shot again! I don't want a politician I can believe in. I simply want a politician I can believe!
crw-rw----+ 1 root audio 14, 3 2007-01-05 15:34 /dev/dsp
Might wanna do a "chmod ugo+r /dev/dsp*
The same might hold for the other sound devices. From the print out only the root and audio groups have read access. Depending on the protocol Cedega uses, it might help to give the "o" (other) read access. Also check the dmesg print out after starting Cedega.
Nothing new from dmesg after launching the game - or doing anything with OSS. If I force something like Amarok to use OSS, it plays the music through my USB headset (which is on dsp2 I think). crw-rw---- 1 root audio 14, 3 2007-01-06 12:13 dsp crw-rw----+ 1 root audio 14, 35 2007-01-06 12:13 dsp2 If I use an application like... Skype and tell it to use ALSA, it sees 3 devices - The Logitech USB headset, CA0106 (my SB Live! 24), and MPU-401 (also on the SB card). If I change it to OSS, it sees 2 devices.. dsp and dsp2. If I set it all to use dsp2, it works using OSS in Skype. If I set it to use dsp (which I assume is my SB card), I just get errors about the sound device not working. I set Cedega to use dsp2 and mixer2 (under OSS) and I have sound... but only through my headset, not my main speakers. So.... OSS is actually working (ie it's not an application problem)... just not working through my main sound card. So... how to fix is the question. And.. what is the + at the end of the permissions on dsp2? Is that an indication of where the problem might be? C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 06 January 2007 03:55, Clayton wrote:
crw-rw----+ 1 root audio 14, 3 2007-01-05 15:34 /dev/dsp
Might wanna do a "chmod ugo+r /dev/dsp*
The same might hold for the other sound devices. From the print out only the root and audio groups have read access. Depending on the protocol Cedega uses, it might help to give the "o" (other) read access. Also check the dmesg print out after starting Cedega.
Nothing new from dmesg after launching the game - or doing anything with OSS.
If I force something like Amarok to use OSS, it plays the music through my USB headset (which is on dsp2 I think).
crw-rw---- 1 root audio 14, 3 2007-01-06 12:13 dsp crw-rw----+ 1 root audio 14, 35 2007-01-06 12:13 dsp2
If I use an application like... Skype and tell it to use ALSA, it sees 3 devices - The Logitech USB headset, CA0106 (my SB Live! 24), and MPU-401 (also on the SB card). If I change it to OSS, it sees 2 devices.. dsp and dsp2. If I set it all to use dsp2, it works using OSS in Skype. If I set it to use dsp (which I assume is my SB card), I just get errors about the sound device not working.
I set Cedega to use dsp2 and mixer2 (under OSS) and I have sound... but only through my headset, not my main speakers.
So.... OSS is actually working (ie it's not an application problem)... just not working through my main sound card.
So... how to fix is the question. And.. what is the + at the end of the permissions on dsp2? Is that an indication of where the problem might be?
C.
Ok, so what sound card are you using? Also explain a little about you speaker setup - such as you have external speakers and headphones at the same time? Or, is it that you're switching between the two (also a bit of a mystery why you have 3 dsp devices with skype)? Could be something to do with the sound cards output ports on the device or the software config that is routing the signals. Cheers, Curtis. -- Spammers Beware: Trespassers will be shot, survivors will be shot again! I don't want a politician I can believe in. I simply want a politician I can believe!
Ok, so what sound card are you using? Also explain a little about you speaker setup - such as you have external speakers and headphones at the same time? Or, is it that you're switching between the two (also a bit of a mystery why you have 3 dsp devices with skype)? Could be something to do with the sound cards output ports on the device or the software config that is routing the signals.
I mentioned the setup in my previous email.. but probably not clearly.... :-) The main sound card is a Sound Blaster Live! 24 connected to external speakers (uses ca0106 driver). The only other sound device I have is my Logitech USB headset. Both devices are connected at the same time (I am not switching between the two - both remain connected at all times). The sound card is on /dev/dsp, and the headset on /dev/dsp2. There is no device on /dev/dsp1 - it's not even there in the /dev directory. The "third" device is the MIDI part of the SoundBlaster, and shows up as MPU-401... the same as it's always done in Linux. As a comparison, if I boot to Kubuntu (6.10), and check the same hardware, the /dev devices are exactly the same (ie the SB is on /dev/dsp, the headset on /dev/dsp2, and no /dev/dsp1 device). OSS works fine through the SoundBlaster in all applications I set to use it.... meaning that Cedega works with sound, as well as something like Skype (if I set it to use OSS). Permissions on the /dev devices are the same... except in SUSE /dev/dsp2 has a + at the end of the permissions. On SUSE, I am using the same hardware, drivers, and software (other than that one is installed from RPM and the other from DEB). I am using the exact same software/application specific configuration as well. Also, on SUSE, if I play a movie with MPlayer, I have to use ALSA as my sound (the only output that currently produces any sound at all via the SB). The whole time there is an error flashing (too fast to read) on the desktop that says (when you stop/pause the movie) "Unable to find simple control 'PCM' 0". I cannot play the movie with this error strobing (this also happens on Kubuntu). My solution in the past was to simply switch over to OSS (in MPlayer options). If I do that now, the OSS sound starts playing on /dev/dsp2 (my headset). There is no sound at all if I direct the output to the SoundBlaster (on /dev/dsp). In Kubuntu it works fine via the SoundBlaster if I set MPlayer to use OSS and direct the sound to /dev/dsp. It's got to be something in SUSE (configuration? kernel compilation?) that's the problem. But what it is, is a mystery. It's keeping me from using 10.2 as my main desktop though :-( Could this be linked to the problem I have with SUSE 10.2 where all users have no sound at all until I manually add them to the Audio group? https://bugzilla.novell.com/show_bug.cgi?id=227420 C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 06 January 2007 23:30, Clayton wrote:
Ok, so what sound card are you using? Also explain a little about you speaker setup - such as you have external speakers and headphones at the same time? Or, is it that you're switching between the two (also a bit of a mystery why you have 3 dsp devices with skype)? Could be something to do with the sound cards output ports on the device or the software config that is routing the signals.
I mentioned the setup in my previous email.. but probably not clearly.... :-)
The main sound card is a Sound Blaster Live! 24 connected to external speakers (uses ca0106 driver). The only other sound device I have is my Logitech USB headset. Both devices are connected at the same time (I am not switching between the two - both remain connected at all times). The sound card is on /dev/dsp, and the headset on /dev/dsp2.
There is no device on /dev/dsp1 - it's not even there in the /dev directory. The "third" device is the MIDI part of the SoundBlaster, and shows up as MPU-401... the same as it's always done in Linux.
As a comparison, if I boot to Kubuntu (6.10), and check the same hardware, the /dev devices are exactly the same (ie the SB is on /dev/dsp, the headset on /dev/dsp2, and no /dev/dsp1 device). OSS works fine through the SoundBlaster in all applications I set to use it.... meaning that Cedega works with sound, as well as something like Skype (if I set it to use OSS). Permissions on the /dev devices are the same... except in SUSE /dev/dsp2 has a + at the end of the permissions.
On SUSE, I am using the same hardware, drivers, and software (other than that one is installed from RPM and the other from DEB). I am using the exact same software/application specific configuration as well.
Also, on SUSE, if I play a movie with MPlayer, I have to use ALSA as my sound (the only output that currently produces any sound at all via the SB). The whole time there is an error flashing (too fast to read) on the desktop that says (when you stop/pause the movie) "Unable to find simple control 'PCM' 0". I cannot play the movie with this error strobing (this also happens on Kubuntu). My solution in the past was to simply switch over to OSS (in MPlayer options). If I do that now, the OSS sound starts playing on /dev/dsp2 (my headset). There is no sound at all if I direct the output to the SoundBlaster (on /dev/dsp). In Kubuntu it works fine via the SoundBlaster if I set MPlayer to use OSS and direct the sound to /dev/dsp.
It's got to be something in SUSE (configuration? kernel compilation?) that's the problem. But what it is, is a mystery. It's keeping me from using 10.2 as my main desktop though :-(
Could this be linked to the problem I have with SUSE 10.2 where all
users have no sound at all until I manually add them to the Audio group? https://bugzilla.novell.com/show_bug.cgi?id=227420
C.
Why aren't you using the snd-emu10k1 driver? The ALSA wki page has the following; This is the wiki page about Creative Labs Audigy LS alsa driver. It's called snd-ca0106 - formerly known as snd-audigyls... SB Live 24bit - capture from analog inputs does't work and the 1st entry for supported cards is SB Audigy LS Check out these 2 pages; http://alsa.opensrc.org/Emu10k1 http://alsa.opensrc.org/Ca0106 Module for EMU10K1/EMU10k2 based PCI soundcards. * Sound Blaster Live! * Sound Blaster PCI 512 * Emu APS (partially supported) * Sound Blaster Audigy * Sound Blaster Audigy 2 extin - bitmap of available external inputs for FX8010 (see below, not needed for Audigy, Audigy 2) extout - bitmap of available external outputs for FX8010 (see below, not needed for Audigy, Audigy 2) seq_ports - allocated sequencer ports (4 by default) max_synth_voices - limit of voices used for wavetable (64 by default) max_buffer_size - specifies the maximum size of wavetable/pcm buffers given in MB unit. Default value is 128. enable_ir - enable IR Module supports up to 8 cards and autoprobe. Input & Output configurations............................[extin/extout] * Creative Card wo/Digital out......................[0x0003/0x1f03] * Creative Card w/Digital out.......................[0x0003/0x1f0f] * Creative Card w/Digital CD in.....................[0x000f/0x1f0f] * Creative Card wo/Digital out + LiveDrive..........[0x3fc3/0x1fc3] * Creative Card w/Digital out + LiveDrive...........[0x3fc3/0x1fcf] * Creative Card w/Digital CD in + LiveDrive.........[0x3fcf/0x1fcf] * Creative Card wo/Digital out + Digital I/O 2......[0x0fc3/0x1f0f] * Creative Card w/Digital out + Digital I/O 2.......[0x0fc3/0x1f0f] * Creative Card w/Digital CD in + Digital I/O 2.....[0x0fcf/0x1f0f] * Creative Card 5.1/w Digital out + LiveDrive.......[0x3fc3/0x1fff] * Creative Card 5.1 (c) 2003........................[0x3fc3/0x7cff] * Creative Card all ins and outs....................[0x3fff/0x7fff] The ca0106 drivers are far more rudimentary and far less feature rich AFAICT. I strongly suspect this is the primary cause for your problems especially the point about the analog being non-functional. Though I would suspect that Cedega is spitting out the audio in digital form, it may confuse the drivers do to the fact that it may be trying to push the signal via the ADC component and therefore kludges from the start. I could be wrong though. Try to load the drivers for snd-emu10k1, not the old OSS EMU10k1 drivers - lacking the "snd-" prefix. These have yet another separate set of features and utilities for them - namely a few tools to load SFX and Effects params. The ALSA snd-emu10k1 drivers are far less problematic overall IMHO. HTH, Curtis. -- Spammers Beware: Trespassers will be shot, survivors will be shot again! I don't want a politician I can believe in. I simply want a politician I can believe!
Why aren't you using the snd-emu10k1 driver?
Simple answer.... the default install from SUSE uses ca0106. I haven't changed anything from what the install gave me. It is also the exact same driver that Kubuntu 6.10 uses. I'll give the snd-emu10k1 drivers a whirl and see what happens. Interesting though that other distros are using the ca0106 driver... and that this driver is working fine with the various apps onmy hardware... it's only SUSE (so far) that chokes on it. Puzzling. Anyway... I'll try the other drivers and see what happens. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I'll give the snd-emu10k1 drivers a whirl and see what happens.
OK, now I'm VERY confused... I started up YAST, and went to Hardware > Sound. I deleted the existing sound card setup. As soon as I did that, my desktop went black - the wallpaper and all icons disappeared. I added the sound card back in - still using the ca0106 drivers because there is no way to change that in YAST. The desktop is still... broken (for lack of a better word)... ie, no wallpaper, and no desktop icons... cannot right click on the desktop. But... if I test ANY application and tell it to use OSS, it works via the SoundBlaster. If I log out, and back in again, OSS no longer works - and my desktop is back to normal. I start up YAST again, delete the sound card, and poof.. desktop is broken. Add the sound card back in using ca0106 as the driver (like I said, you cannot choose a different driver with YAST) Save and exit. Desktop is still broken, but... OSS works. The only way I've found to fix the broken desktop is to log out and back in again. Why in the world would changing a sound card - ie removing it break my desktop? If it makes any difference, this is on a clean SUSE 10.2 install... no carry over from a previous version. Updates applied (but this was an issue before any updates were applied) The messages log has this in it when I delete and reconfigure the sound card: ----------- Jan 7 10:20:49 smaug42 kernel: ACPI: PCI interrupt for device 0000:04:06.0 disabled Jan 7 10:20:52 smaug42 kernel: PCI: Enabling device 0000:04:06.0 (0100 -> 0101) Jan 7 10:20:52 smaug42 kernel: ACPI: PCI Interrupt 0000:04:06.0[A] -> GSI 21 (level, low) -> IRQ 233 Jan 7 10:20:52 smaug42 kernel: Model 1006 Rev 00000000 Serial 10061102 Jan 7 10:20:58 smaug42 kernel: ACPI: PCI interrupt for device 0000:04:06.0 disabled Jan 7 10:20:58 smaug42 kernel: PCI: Enabling device 0000:04:06.0 (0100 -> 0101) Jan 7 10:20:58 smaug42 kernel: ACPI: PCI Interrupt 0000:04:06.0[A] -> GSI 21 (level, low) -> IRQ 233 Jan 7 10:20:58 smaug42 kernel: Model 1006 Rev 00000000 Serial 10061102 ------------ C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I added the sound card back in - still using the ca0106 drivers because there is no way to change that in YAST.
I should clarify what I meant here... I see no way in YAST to change the driver on the autodetected hardware. If I add a new device (ignoring the autodetected one) I can select specific drivers etc. If I select the emu10k1 driver it fails to load, complaining about incorrect addresses and interrupts. A little more experimenting... if I delete the soundcard (using YAST), it breaks the desktop. I log out and back in. The desktop is working correctly again. I go in to YAST and add the autodetected sound card using the ca0106 drivers (if I force it to emu10k1 it errors on address/irq). I save and exit and test any application using OSS (Cedega, MPlayer etc) and all work fine via the SoundBlaster. Log out, and back in... and everything stops working with OSS. I wouldn't care so much that OSS wasn't working but it seems to be the only way I can get sound to work correctly with Cedega and MPlayer... C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 07 January 2007 01:23, Clayton wrote:
I'll give the snd-emu10k1 drivers a whirl and see what happens.
OK, now I'm VERY confused... I started up YAST, and went to Hardware > Sound. I deleted the existing sound card setup. As soon as I did that, my desktop went black - the wallpaper and all icons disappeared. I added the sound card back in - still using the ca0106 drivers because there is no way to change that in YAST. The desktop is still... broken (for lack of a better word)... ie, no wallpaper, and no desktop icons... cannot right click on the desktop. But... if I test ANY application and tell it to use OSS, it works via the SoundBlaster.
If I log out, and back in again, OSS no longer works - and my desktop is back to normal. I start up YAST again, delete the sound card, and poof.. desktop is broken. Add the sound card back in using ca0106 as the driver (like I said, you cannot choose a different driver with YAST) Save and exit. Desktop is still broken, but... OSS works.
The only way I've found to fix the broken desktop is to log out and back in again. Why in the world would changing a sound card - ie removing it break my desktop?
If it makes any difference, this is on a clean SUSE 10.2 install... no carry over from a previous version. Updates applied (but this was an issue before any updates were applied)
Ok, that is a bit strange. I wonder if the USB snd stuff isn't behind this. Try unpluging the usb headphones then reboot into init 3, bring up yast as root, delete any sound card (unless it shows the snd-emu10k1 drivers). The thing that might be happening is that between the usb headphones and the sound card yast/SuSE/ALSA is getting confused and think that the two devices equat to the ca0106 device or some kludge that is caused by the combo of the two. I wonder when you did the install did you have the headphones plugged in? So, d/c the headphones for now, check the driver setup (probably still ca0106) - delete old sound card drivers if they remain the same. Manually install via yast selection the snd-emu10k1 and see if the sound card behaves better. But if that fails then you can manually load the snd-emu10k1 drivers. Just to give you a look at my mod setup I'll post here. Mind you I have an audigy1 card. But the setup is pretty much exactly what it was with my old SB-Live 24 sound card. lsmod | grep snd snd_pcm_oss 53376 0 snd_mixer_oss 21248 1 snd_pcm_oss snd_seq_midi 13824 0 snd_emu10k1_synth 12544 0 snd_emux_synth 41984 1 snd_emu10k1_synth snd_seq_virmidi 11392 1 snd_emux_synth snd_seq_midi_event 11520 2 snd_seq_midi,snd_seq_virmidi snd_seq_midi_emul 10624 1 snd_emux_synth snd_seq 60272 5 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_ seq_midi_event,snd_seq_midi_emul snd_emu10k1 125728 1 snd_emu10k1_synth snd_rawmidi 29824 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1 snd_ac97_codec 95648 1 snd_emu10k1 snd_ac97_bus 6400 1 snd_ac97_codec snd_pcm 86916 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec snd_seq_device 12812 6 snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,sn d_seq,snd_emu10k1,snd_rawmidi snd_timer 27908 3 snd_seq,snd_emu10k1,snd_pcm snd_page_alloc 14472 2 snd_emu10k1,snd_pcm snd_util_mem 9472 2 snd_emux_synth,snd_emu10k1 snd_hwdep 13956 2 snd_emux_synth,snd_emu10k1 snd 61188 16 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_emu1 0k1_synth,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq,snd_emu10k1,s nd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_util_mem,snd_hwde p I have had the same setup with the SuSE JACKlab project using the pre-emptive kernel with almost zero latency (about 10 to 20 ms - for a Creative sound card that ain't bad). I have a home studio setup with a Tascam 1884FW console and get the same - but much more! I also loaded an EMU-0404 with 2 to 10ms latency (unfortunately only on Windblows systems). Sound in Linux is improved alot, but has a lot more to tacke. Eitherway, there's no reason you should be getting a dead dsp0 setup - hence I think it might be about the snd-usb component. The only other thing that comes to mind right now is that you have a variant of the SB-Live card that is causing the ca0106 driver to be selected. As I said earlier in the post - you can setup the drivers manually if need be. Then again the USB sound mods/setup is very much known to go kludge bigtime here and there. In the same kernel dir for usbaudio is another file called usbquirks (hint hint?). HTH, Curtis. -- Spammers Beware: Trespassers will be shot, survivors will be shot again! I don't want a politician I can believe in. I simply want a politician I can believe!
Ok, that is a bit strange. I wonder if the USB snd stuff isn't behind this. Try unpluging the usb headphones then reboot into init 3, bring up yast as root, delete any sound card (unless it shows the snd-emu10k1 drivers).
I tried many variations of this in the past few days. Yesterday I even went so far as to reformat my root partition and re-install 10.2 from the master disk (the retail version this time, not the downloaded version - just in case that would make a difference). On install I had the usual 10.2 no sound problem... solved by adding the Audio group to $USER. (sep issue, and I wish someone could tell me why this is a problem on some systems, and not on others). No USB headset was plugged in.... and exactly the same /dev/dsp setup as before. And... still no OSS sound in any apps that need/use OSS sound. I cannot under any circumstances convince my sound card to work with the emu10k1 drivers. It will not work at all unless i swap over to the ca0106 driver - this is consistent with pretty much everything I've read on the web.. the SB Live!24 is supposed to used the ca0106 drivers not the emu10k1 drivers (which seem to be targeted at the Audigy chipset).
lsmod | grep snd
This is my current lsmod | grep snd snd_pcm_oss 53376 0 snd_mixer_oss 21248 1 snd_pcm_oss snd_seq_midi 13824 0 snd_seq_midi_event 11520 1 snd_seq_midi snd_seq 60272 2 snd_seq_midi,snd_seq_midi_event snd_usb_audio 81024 2 snd_usb_lib 20992 1 snd_usb_audio snd_hwdep 13956 1 snd_usb_audio snd_ca0106 37636 6 snd_ac97_codec 95648 1 snd_ca0106 snd_pcm 86916 6 snd_pcm_oss,snd_usb_audio,snd_ca0106,snd_ac97_codec snd_timer 27908 4 snd_seq,snd_pcm snd_ac97_bus 6400 1 snd_ac97_codec snd_mpu401 12712 1 snd_mpu401_uart 13056 1 snd_mpu401 snd_rawmidi 29824 4 snd_seq_midi,snd_usb_lib,snd_ca0106,snd_mpu401_uart snd_seq_device 12812 3 snd_seq_midi,snd_seq,snd_rawmidi snd 61188 29 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_seq,snd_usb_audio,snd_usb_lib,snd_hwdep,snd_ca0106,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore 13792 1 snd snd_page_alloc 14472 2 snd_ca0106,snd_pcm usbcore 114896 6 usbhid,snd_usb_audio,snd_usb_lib,uhci_hcd,ehci_hcd,ohci_hcd The next option... maybe replacing the old Live24 card with an Audigy? They are only 30-some Euro at the local computer shop... if they still have any. Seems like everyone is pushing the shiny new SoundBlaster XFi (or something)... that are 300 Euro. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
More on this sound thing... done a lot of digging, and found out that the SoundBlaster Live! series all use the emu10k1 driver EXCEPT the Live! 24 (the card I have). That one only works with the ca0106 driver. So SUSE is using the correct driver for this card. Loads more tinkering, and I can get the OSS sound working.. sort of. If I open YAST, Delete the sound card config, save and exit the YAST sound module, restart it.. add the sound card back in, I get full support for OSS (and ALSA) in all applications, But...but.. if I log out, I loose the OSS capability and I'm back where I started... no OSS support for any application that needs/uses it. repeat the delete, add thing with the sound card drivers, and it starts working again. This is so stupid... and frustrating... so VERY frustrating. Is this a dumb bug? Is it my hardware? It works perfectly in 10.1 and in Ubuntu 6.10 (on the same hardware)... it's only 10.2 that's giving me this grief. My /dev lineup is exactly the same in 10.1 and in Ubuntu 6.10... lsmod shows the exact same thing across the OSes. The only thing I haven't checked is the ca0106 driver I'm using.... I might try downgrading the driver to a previous version.... I'm open to any and all suggestions :-( C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Jan 03, 2007 at 12:08:52PM -0800, Curtis Rey wrote:
a config issue with wine/Cedega. Or it may be the permissions as well. Also If you're running AppArmor - Don't! It can interfer with apps and /dev
AppArmor only mediates confined programs, and the default set of profiles we provide is pretty slim. (Check /etc/apparmor.d/ to see what is confined by default. Check ps auxZ output to see what is currently confined. Check unconfined(8) to see a list of what network services are confined.) If AppArmor _is_ denying access to your files for one of your programs, you can easily resolve the problem by running either YaST's "Update Profile Wizard" or the terminal-friendly aa-logprof(8) and answering the questions.
access - it's designed for Enterprise/network servers with access to the outside world - generally overkill for home users and non-servers.
Depends on your applications. :) If you run clamav, apache2-mod_php4, MozillaFirefox, opera, ethereal, phpMyAdmin, squid, apache2, squirrelmail, mailman, MozillaThunderbird, gaim, gpg, mozilla, mysql, or postgresql, you may wish to run AppArmor and write profiles for those applications, to try to protect yourself from the buggiest applications. (This list compiled from programs that required five or more updates during the support lifetime of SuSE Linux 9.2. I'm sure this list will change over time, and it isn't meant to be exhaustive -- just giving guidelines of the worst offenders. :) Thanks
participants (4)
-
Clayton -
Curtis Rey -
Dominique Leuenberger -
Seth Arnold