Arch Linux

Nanthiel

Member

From: Slovenia

Registered: 2009-09-20

Posts: 148

[Solved] Alsamixer bad behaviour!

Hello everyone, I have the following problem with Alsamixer:

I can control the volume levels only with the numpad and number keys on the keyboard (thus - I can't set 100% Volume, clicking 5 is 50%, 6 is 60% etc.), left/right buttons work to select between various options (PCM, Master, ...). Also the "End" key works to get volume levels to 0%. Up/down keys aren't doing anything!

So what's wrong with alsamixer? =/

Note, I'm using the Creative X-Fi drivers. Could this be the fault?

Thanks for the answers!

— Nanthiel

Last edited by Nanthiel (2009-11-04 22:52:43)

SIGTERM

Member

Registered: 2009-09-19

Posts: 67

Website

Re: [Solved] Alsamixer bad behaviour!

Maybe try OSS?
http://wiki.archlinux.org/index.php/OSS … r_users.29
"Better support for some sound card models, for example for the Creative X-Fi."

Nanthiel

Member

From: Slovenia

Registered: 2009-09-20

Posts: 148

Re: [Solved] Alsamixer bad behaviour!

Oh, interesting. Thank you! I will definitely try this!

EDIT/ADDITION: Thank you again! OSS owns for my audio card, it has never worked better!

Last edited by Nanthiel (2009-09-28 21:29:59)

Nanthiel

Member

From: Slovenia

Registered: 2009-09-20

Posts: 148

Re: [Solved] Alsamixer bad behaviour!

But a problem appeared!

My tv card doesn't have sound anymore. How would I go about configuring this?

(the driver is bt878; it says:
WARNING: /etc/modprobe.d/modprobe.conf line 4: ignoring bad line starting with 'bt878'
three times when loading OSS, and once each time I try to do anything with 'modprobe')

Please help!

SIGTERM

Member

Registered: 2009-09-19

Posts: 67

Website

Re: [Solved] Alsamixer bad behaviour!

Nice to hear your sound card is working .
For your TV-card, I don't know. I'll try and do some searching when I've got some spare time.

Last edited by SIGTERM (2009-09-29 20:11:08)

Nanthiel

Member

From: Slovenia

Registered: 2009-09-20

Posts: 148

Re: [Solved] Alsamixer bad behaviour!

Okay this has now been solved! An update just made it work seamlessly with ALSA!