Christos Zoulas wrote:
This is the script I use [1]. As you can see I cannot put this into any static configuration as mixerctlIn article <48FEC745.7000104%yazzy.org@localhost>, Marcin M. Jessa <lists%yazzy.org@localhost> wrote:Roy Marples wrote:On Tue, 2008-10-21 at 17:52 -0400, Jared D. McNeill wrote:Marcin M. Jessa wrote:What doesn't work nicely about azalia on Eee PC? I confirmed that both playback and capture work, and the volume buttons (Fn+whatever) work as well.Swift Griggs wrote:the native 1024x600 resolution. Sound works, also. Oddly, I've found that I can turn the volume up using mixerctl to much higher levels than are available when running XP. It's the first time the Azailia drivers have worked so well for me.I don't really understand why we need to use mixerctl to be able to adjust the volume level when the same device works nicely with linux drivers...Well, on my ThinkPad z60m, I have to manually adjust channels to +248 from the default as it's too low. With the default I jack all available sliders in GNOME volume control and/or equivalent in KDE and XFCE to max and still can't here anything until I manually adjust in mixerctl AND get it to save state on shutdown. Whilst it "works", it's hardly "optimal"Exactly, I had to write a shell script to use mixerctl to set up sound for my internal speakers or to send output to the head phones.Each time I need to change the sound level I have to type mixerctl -w outputs.lineout=xyz,xyzThis sucks big time...Why don't you stick it in /etc/sysctl.conf
requires diffent input for internal speakers and for headphones.Not to mention the fact that it's not an optional way of adjusting the sound level of my azalia device...
#!/bin/sh
case ${1} in
s)
mixerctl -w outputs.lineout.eapd=on
mixerctl -w outputs.lineout=200,200
;;
h)
mixerctl -w outputs.lineout.eapd=on
mixerctl -w outputs.headphones=255,255
mixerctl -w outputs.lineout=0,0
;;
"")
echo "Please use one of following: h(eadphones) or
s(peakers)"
esac