LinuxQuestions.org - No sound after KDE 3.2 upgrade (and not using alsa)

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - No sound after KDE 3.2 upgrade (and not using alsa) (https://www.linuxquestions.org/questions/linux-software-2/no-sound-after-kde-3-2-upgrade-and-not-using-alsa-146802/)

I just upgraded to the current stable KDE 3.2. After starting KDE, KMixCtrl crashes. It seems to be looking for an ALSA configuration, which I removed a while back. I've gone into the Control center and turned off autoloading the mixer when starting KDE. I've also tried the different hardware configurations (it was on autodetect) without success.

Anyone tell me what I've missed or know of a workaround to get the sound to work in KDE 3.2 without using ALSA?

AFAIK, everything else seems to be in order. Here's some of my info, along with the backtrace:

Code:

lspci

----------------------------------------------------------------------------

00:11.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)

        Subsystem: Creative Labs: Unknown device 8071

        Flags: bus master, medium devsel, latency 32, IRQ 11

        I/O ports at 1040 [size=32]

        Capabilities: [dc] Power Management version 1





        

lsmod

--------------------------------------------------

emu10k1                61960  1

sound                  57492  0  [emu10k1]

ac97_codec            13480  0  [emu10k1]

soundcore              3652  7  [emu10k1 sound]

emu10k1-gp              1480  0  (unused)

gameport                1484  0  [emu10k1-gp]







dmesg

----------------------------------------------------------------------

emu10k1: EMU10K1 rev 7 model 0x8071 found, IO at 0x1040-0x105f, IRQ 11

ac97_codec: AC97  codec, id: TRA35 (TriTech TR A5)







KMixCtrl backtrace

----------------------------------------------------------------------------

(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 14783)]



0x411cf5c9 in waitpid () from /lib/libpthread.so.0

#0  0x411cf5c9 in waitpid () from /lib/libpthread.so.0

#1  0x4072dccd in KCrash::defaultCrashHandler(int) ()

  from /opt/kde/lib/libkdecore.so.4

#2  0x411cdc45 in __pthread_sighandler () from /lib/libpthread.so.0

#3  <signal handler called>

#4  0x41332ac1 in kill () from /lib/libc.so.6

#5  0x411ca9ed in pthread_kill () from /lib/libpthread.so.0

#6  0x411cad0b in raise () from /lib/libpthread.so.0

#7  0x413326fa in raise () from /lib/libc.so.6

#8  0x41334127 in abort () from /lib/libc.so.6

#9  0x4132bd6a in __assert_fail () from /lib/libc.so.6

#10 0x4152f58e in snd_config_update_free () from /usr/lib/./libasound.so.2

#11 0x4152f016 in snd_config_update_r () from /usr/lib/./libasound.so.2

#12 0x4152f4b8 in snd_config_update () from /usr/lib/./libasound.so.2

#13 0x41537d7d in snd_ctl_open () from /usr/lib/./libasound.so.2

#14 0x40831adc in Mixer_ALSA:: openMixer() ()

  from /opt/kde/lib/libkdeinit_kmixctrl.so

#15 0x40834a5b in Mixer::grab() () from /opt/kde/lib/libkdeinit_kmixctrl.so

#16 0x40830a24 in kdemain () from /opt/kde/lib/libkdeinit_kmixctrl.so

#17 0x408268a6 in kdeinitmain () from /opt/kde/lib/kde3/kmixctrl.so

#18 0x0804cfd8 in strcpy ()

#19 0x0804df39 in strcpy ()

#20 0x0804e47c in strcpy ()

#21 0x0804f42a in strcpy ()

#22 0x4131ed06 in __libc_start_main () from /lib/libc.so.6

Thanx :)
---thegeekster

------------
Edit: typos

I had to un-install KDE 3.2 from both my Slack boxes, the aRTS sound server would not work properly without AlSA, and ALSA make my SB Live Card sound like crap. Without ALSA installed the aRTS hog ties the /dev/dsp and /dev/mixer so I was not able to use the emu10k1 driver, So I put KDE 3.14 back in and all is well.......my SB live card works like it's supposed to......with the emu10k1 driver.

Try changing Control Center -> Sound & Multimedia -> Sound System -> hardware -> audio device to Threaded Open Sound System. I did that and it worked fine.
Just make sure that you compiled in OSS emulation.

Quote:

Originally posted by ghostwalker
Try changing Control Center -> Sound & Multimedia -> Sound System -> hardware -> audio device to Threaded Open Sound System. I did that and it worked fine.
Just make sure that you compiled in OSS emulation.

I tried that in Control Center, but then I don't remember if I used OSS emulation............I don't think so since my card was listed before the section for OSS emulation...........hmmmm...........I'll have to double check that. Thanx :)

I'll let you know how it turns out :D

---thegeekster

Hey ghostwalker,

One question..................should I disable the driver in the kernel config and use strictly OSS emulation, or just go ahead and use the emulation on top of the driver?.........I'm thinking about possible confilicts happening ;)

Use emulation on to with you driver loaded.

Quote:

Originally posted by ghostwalker
Use emulation on to with you driver loaded.

Great, thanx...............:)

I'll have to try this out tomorrow, since it's past my sleepy time ;)

Well, it seems that I already compiled the OSS modules for the SoundBlaster compatible (sb.o) besides the emu10k1 driver, so I'm at a loss............................after looking at the kernel config (v2.4.24), I didn't see any "OSS emulation", only "OSS modules" in the Sound section, which is what I thought was being referred to................Is there an emulation option located somewhere else besides the Sound section? :confused:

--------------------
PS: I also tried to modprobe the sb driver, but it didn't work. Here's the output:

Code:

 # modprobe sb

/lib/modules/2.4.24/kernel/drivers/sound/sb.o: init_module: No such device

/lib/modules/2.4.24/kernel/drivers/sound/sb.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

      You may find more information in syslog or the output from dmesg

/lib/modules/2.4.24/kernel/drivers/sound/sb.o: insmod /lib/modules/2.4.24/kernel/drivers/sound/sb.o failed

/lib/modules/2.4.24/kernel/drivers/sound/sb.o: insmod sb failed

And yes, there _is_ a sb.o driver located in the drivers/sound directory......... ;)

Ummmm.............................hehehe, it seems that it was pilot error as the reason the sound wasn't working......................After messing around inside my computer, I had plugged the speakers back into the wrong plugin.......*slaps forehead*...........anyway, the sound is now working. I have the hardware settings on autodetect and it works just fine.............................Thanx anyway and sorry for all the trouble :)

---thegeekster

Hi

some thoughts on kmixctrl and alsa and sound not using alsa.

1) Plse check your /etc/hotplug/blacklist file.....you may need to remove some files that hotplug are ignoring for me they are
sb sb_lib uart401 sound soundcore etc

2) In your home directory is a file called dot xsession-errors (for slackware 10) and I have had errors.You may need to see "hidden" files.
This file when I had kmixctrl errors alerted me to the
/tmp/mcop-your name/ file (I can't remember) but after I deleted the lot from here my warning disappeared.

3) And other posts suggest there is an issue with kde sound server not releasing after running an arts (sound ) file, so I disable sound server for kde in the control centre area.

4) Some people may not have UNcommented there card stuff in /etc/rd.d/rc.modules......which is where I enable my sb card.

hope that helps