Quote:
Originally posted by amosf
The riva and sound modules are not conected so you must have changed something else during the compile - make sure you compile support for the sound card. And just check permissions on the /dev/dsp
BTW, do you see the saound card module load? Check dmesg... Any errors if it is loading?
Hold on... you reinstalled? Oops. Overkill 
|
Hey amosf,
I'm not sure whom you're replying to - but in Slack 10.0 ALSA is
the default sound. With an install of everything except Games:
Code:
bash-2.05b$ find /var/log/packages -iname "*alsa*" -exec ls -l {} \;
-rw-r--r-- 1 root root 3685 2004-09-02 03:06 /var/log/packages/alsa-lib-1.0.5-i486-1
-rw-r--r-- 1 root root 1090 2004-09-02 03:07 /var/log/packages/alsa-oss-1.0.5-i486-1
-rw-r--r-- 1 root root 14511 2004-09-02 03:06 /var/log/packages/alsa-driver-1.0.5a-i486-2
-rw-r--r-- 1 root root 1769 2004-09-02 03:04 /var/log/packages/alsa-utils-1.0.5-i486-1
and this is my soundcard
Code:
bash-2.05b# lspci
omit other devices
02:0b.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
02:0b.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 03)
and this is what's in the kernel for sound, omitting cards I don't have
Code:
# Sound
#
CONFIG_SOUND=m
...
CONFIG_SOUND_EMU10K1=m
CONFIG_MIDI_EMU10K1=y
...
CONFIG_SOUND_OSS=m
...
and sound is working. I did compile xmms-cdread-0.11d.tar.gz so XMMS would
read audio CDs. Other than that, it's "straight out of the box."
My board has a BroadCom Gigabit Ethernet nic, and in Slack-10.0 the kernel
has to be recompiled to use it (no module - tigon3 or tg3). When I recompile,
the first time I leave sound just as it is - and it doesn't work. I've also tried
several other options. But I never can get sound back. Probably just me, as
I'll be recompiling again in the next few days and will try the way I did it in
Slack-9.1; that is, leave CONFIG_SOUND=m and nothing else under sound,
then compile alsa-driver, alsa-lib, and alsa-utils from source. Then insmod
the modules according to the instructions at ALSA's site.
As far as the rivafb, there is a module in the 2.4.26 kernel for the riva framebuffer,
and the message appears when you install the Nvidia driver, but I've not had a
problem by just pressing OK and ignoring it. But I've only installed Slack-10.0
and the Nvidia driver on about 5 - 8 comps, so that's not a lot of examples.
Thanks for your help. Btw - didn't your sig used to say you run Slack?
Edit: Excuse me, for I wasn't intending to hijack this thread. I think
the discussion will benefit the thread starter, since his hardware, distro,
and kernel are similar. All Creative Labs SB cards use the same module,
except one Audigy which isn't supported at all.
