Yet another after effect of compile

[windoze killa]

Hopefully the last problem from my kernel compile. After reinstalling the alsa sound drivers for my sound card, VIA8233, both aumix and kmix crash. They can be run and I see the speaker icon in the system tray but when I click on it to open it so I can make adjustments it crashes. I will try and post the error O/P tonight when I get home. Just hoping someone might know what may be causing this.

[edit]

I don't think this is really related to the kernel compile because I think it may have been a problem since installing the new motherboard.

[bwkaz]

Can you post the errors that you get when you run them from a terminal?

[windoze killa]

Will try to get to it tonight. Have top battle with the minister for home affairs.

[windoze killa]

Here are the error messages when kmix crashes.

This one is from the debug screen of kcrash.

(no debugging symbols found)...(no debugging symbols found)...
0x40b6b999 in __wait4 () from /lib/libc.so.6
#0 0x40b6b999 in __wait4 () from /lib/libc.so.6
#1 0x40be7c90 in __DTOR_END__ () from /lib/libc.so.6
#2 0x40323838 in KCrash::defaultCrashHandler () at eval.c:41
#3 <signal handler called>
#4 0x08056d4d in KDialog::marginHint () at eval.c:41
#5 0x080de390 in ?? () at eval.c:41
#6 0x40629f71 in QWidget::event () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#7 0x40592891 in QApplication::notify () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#8 0x4028ac89 in KApplication::notify () at eval.c:41
#9 0x40560d5f in QETWidget::translateMouseEvent ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#10 0x4055e248 in QApplication::x11ProcessEvent ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#11 0x4055d21a in QApplication::processNextEvent ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#12 0x4059474c in QApplication::enter_loop ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#13 0x4055d197 in QApplication::exec () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#14 0x08052508 in KDialog::marginHint () at eval.c:41
#15 0x40ad41f6 in __libc_start_main (
main=0x8052390 <KDialog::marginHint(void)+276>, argc=7, ubp_av=0xbffffb84,
init=0x8050454 <_init>, fini=0x8063710 <_fini>,
rtld_fini=0x4000cfe8 <_dl_fini>, stack_end=0xbffffb7c)
at ../sysdeps/generic/libc-start.c:129


This one is what is displayed in the terminal window after the crash.

KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kmix path = <unknown> pid = 1942


The only thing I can make from it is a problem with qt. Any other guesses appreciated.

[bwkaz]

It's a problem in the KDialog::marginHint function (the one before the <signal handler called> line), although I have no idea what the problem would be.

Does aumix give some similar error?

[windoze killa]

From memory yes it does. I didn't get a chance to play much last night. I will have another go tonight.

[windoze killa]

aumix when run from a terminal says

aumix: error opening mixer

I also did an lsdev to see what devices were running and there was no mixer.

I don't know if this means much but any help would be appreciated.

[bwkaz]

Yeah, that does help. Does modprobe snd-pcm-oss fix the problem?

The mixer device is handled by the snd-mixer-oss module, which snd-pcm-oss depends on (and adding in snd-pcm-oss will also give you a /dev/dsp device, OSS-emulation style).

[windoze killa]

I will give it a try tonight. From memory I can't remember seeing anything about oss.

[windoze killa]

Well, that modprobe worked to an extent. It no longer crashes. Not having a lot of time and rushing through this and not rebooting yet. Will this need to be done each time or does modprobe fix it for good?

I still don't have sound and I know /var/log/messages says there are some other things modprobe couldn't find but I will post those on sunday.

Thank for your help so far.

[bwkaz]

No, modprobe doesn't fix it for good, but editing /etc/modules.conf should.

Add a couple lines:

alias /dev/dsp snd-pcm-oss
alias /dev/mixer snd-pcm-oss

This assumes you're using devfs, but I think that's the case because it looks like /dev/mixer didn't even exist before, and the only way that can happen is with devfs.

[windoze killa]

How do I know if I am using devfs?