Talk:Sony Vaio VGN-AR41E
From The Unknown
Contents |
Read me first
Due to constant spamming I have no other option but to restrict edits to logged in users.
So if you have something to add, please register an account.
sony-laptop feedback
> > For now all sony-laptop can do is enable the Fn keys, I'll add your > > model to the DMI list asap. > > Any chances of getting the rest of the controls working? (like turning > on bluetooth and so on) well, not until somebody is able to trace which SNC device methods (if any at all) are called to control the extra features. Unfortunately there are no specs available for it.
Questions
I have the VGN-AR21S which is more or less similar and i am trying to sort out the spdif out... What makes you think that it uses the ALC ? and how i am able to try and see if it works ... I am also running gentoo by the way.
Well, there are (somehow) two codecs, the ALC is for SPDIF and the SigmaTel is for internal speakers, headphones and microphone.
Haven't figured out how to use both, and since I do not have any equipment with SPDIF... I can't really test it out.
Another question is if you managed to work out the backlight dimming somehow !
Nope, not yet. Apparently nobody else either. My solutions: dark/gray themes and/or nvidia-settings and adjusting the brightness control (not the same as backlight dimming)
Last is about the special keys such as S1 ,S2 AV mode , eject etc ... that do not produce any event at least for me :D
They produce acpi events if the source file for the driver is modified a little (in the kernel) or if you wait until the patch shall be in-kernel.
Once you have acpi events, they can be configured in /etc/acpi/, you need to know the format of the event that it produces (you can find it out in /var/log/messages) and then you can make a script to bind it to a specific action.
--Ragsu 02:55, 14 February 2011 (EET) I have VGN-AR41L which is quite identical to AR41E, except L has more memory. Do you have problems with the 3d-acceleration? No matter which drivers I tried in Ubuntu at least, no driver was compatible with the GF 8400M GT.
Soundcard
I do have the equipment to do the tests but i am trying to understand how this is possible ... 2 codecs mean 2 soundcards and then the alsa configuration can be done like this ... Multiple cards this is ok .. but 2 codecs 1 card i cannot get it :/
As far as i can see i got 2 codecs ! the sigmatel one and the conexant which is the for the modem
cat /proc/asound/card0/codec#0 | grep Codec
Codec: SigmaTel CXD9872AKD
cat /proc/asound/card0/codec#1 |grep Codec
Codec: Conexant ID 2bfa
Maybe it's because you have model=vaio or model=vaio-ar somewhere in your alsa config files.
If I remove any and all configuration, I have a total of three codecs. One realtek, one sigmatel, and one conexant (which, as you said, is probably a modem).
And regarding two codecs but one soundcard... well... no idea really :)
But since you have the equipment, maybe you could try contacting the alsa team for some guidance.
P.S.: We really should switch to e-mail or something, time is limited sometimes and I forget to check this page. My contact info is here.
--eaglex 19:45, 15 May 2008 (EEST)
Fix suggestions
you should edit alsa-base with sudo gedit /etc/modprobe.d/alsa-base add the line options snd-hda-intel model=vaio
Sorry, but that doesn't really work with this model. --eaglex 17:09, 10 May 2008 (EEST)
Strange, I have exactly the same model and it works. It's important to have the last ALSA that's from Ubuntu 7.10 on
What exactly should this fix? both output to headphones and SPDIF or just heaphones? Or? --eaglex 08:30, 7 September 2008 (EEST)
I have headphone/speaker muting working with the following command...
"options snd-hda-intel model=vaio enable=1 index=0 position_fix=1"
Don't ask me what it does, because I really don't know. However, after appending it to “/etc/modprobe.d/alsa-base”, I found that the headphones worked! What's more, the damned things muted the main speakers.
Only issues are, I can't get the mic to work and the 'optical out' isn't working either.
I found this at: http://multidisciplinary.wordpress.com/2009/01/15/sound-headphones-fix-in-linux-on-sony-vaio-vgn-ar51su-laptop/
I am, overall, happy with Ubuntu 8.10 on my Vaio VGN-AR41E, but the Fn key problem and the poor audio support is starting to annoy:)
Cyberkilla 02:13, 14 February 2009 (EET)
How about trying this: First, open up a terminal and run amixer contents
You should get something like so:
numid=2,iface=MIXER,name='Master Playback Switch' ; type=BOOLEAN,access=rw------,values=2 : values=on,on numid=1,iface=MIXER,name='Master Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0 : values=127,127 | dBscale-min=-95.25dB,step=0.75dB,mute=0 numid=6,iface=MIXER,name='PCM Playback Volume' ; type=INTEGER,access=rw---RW-,values=2,min=0,max=255,step=0 : values=180,180 | dBscale-min=-51.00dB,step=0.20dB,mute=0 numid=5,iface=MIXER,name='Capture Source' ; type=ENUMERATED,access=rw------,values=1,items=3 ; Item #0 'Mic Jack' ; Item #1 'Internal Mic' ; Item #2 'PCM' : values=1 numid=4,iface=MIXER,name='Capture Switch' ; type=BOOLEAN,access=rw------,values=2 : values=on,on numid=3,iface=MIXER,name='Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=15,step=0 : values=0,0 | dBscale-min=0.00dB,step=1.50dB,mute=0 numid=7,iface=MIXER,name='Digital Capture Volume' ; type=INTEGER,access=rw---RW-,values=2,min=0,max=120,step=0 : values=60,60 | dBscale-min=-30.00dB,step=0.50dB,mute=0
What we care about is the bold stuff, yours will probably be off and set to a different input source. To set it like mine, do these:
amixer cset numid=5,iface=MIXER,name='Capture Source' 1
^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^
| | +--- Item #1 (which is internal mic, your index number may vary)
| +-------------------------- Just copy/paste this part from amixer contents above
+---------------------------------------------------- Utility and set mode
amixer cset numid=4,iface=MIXER,name='Capture Switch' on -- pretty much the same as above
And this should hopefully get your mic working. Hope it does. Good luck.
--eaglex 23:00, 17 February 2009 (EET)
Forgot something: no idea/progress with SPDIF over here either. The Fn keys can be made to produce acpi events, but it requires messing with the driver, adding some code, compiling, so on, so forth. Not recommended if you haven't done this before.
--eaglex 23:04, 17 February 2009 (EET)
Wow, it works. Thanks again.
It's not the easiest thing to configure though. I hope it's better supported in the next release of Ubuntu, but for now I'm happy:)
With regards to the Fn keys, would I need to recompile this driver every time there was an update to the kernel?
If I only had to do it once, I'd go for it.
Cyberkilla 18:02, 19 February 2009 (EET)
By the way, I tried "options snd-hda-intel probe_mask=3 model=vaio" and it added switches (but removed a few volume controls). I then installed ALSA version 1.0.0.19 by following the instructions here: http://ubuntuforums.org/showpost.php?p=6834674&postcount=75 After a restart, I was in much better condition. I now have:
- Playback
- Master Volume
- Headphone Volume
- PCM Volume
- Speaker Volume - controls internal speaker volume.
- Recording
- Capture - always muted, never works.
- Digital - always muted, never works (btw, I only have optical out, don't I?)
- Switches
- PCM Capture
- Mic Jack
- Internal Mic
I still can't get the mics to work through the proper graphical interface. I don't know whether it's worth anyone upgrading to the latest ALSA, unless you want the Headphone and Speaker controls back. It's still not quite working properly. The overall volume curve is still too steep too. You only start to hear sound after 50% master volume. It is outputting sound under 50%, but it's really, really quiet. --Cyberkilla 13:57, 5 March 2009 (EET)
With regards to the Fn keys, would I need to recompile this driver every time there was an update to the kernel? If I only had to do it once, I'd go for it.
Sorry, missed that line before. I'm afraid yes, you would have to patch/recompile every kernel you upgrade to, until it's added officially.
If you need any help, I'm happy to.
--eaglex 21:24, 5 March 2009 (EET)
terrainvista
Hello, I have the headphone working with only "options snd-hda-intel model=vaio" (it works with adding "enable=1 index=0 position_fix=1 as well). The problem now is the mic. I have the following result that doesn't include 'Capture Source'.
amixer contents numid=0,iface=MIXER,name='Master Playback Switch' ; type=BOOLEAN,access=rw------,values=1 : values=on numid=0,iface=MIXER,name='Master Playback Volume' ; type=INTEGER,access=rw------,values=2,min=0,max=65536,step=1 : values=65536,65536 numid=0,iface=MIXER,name='Capture Switch' ; type=BOOLEAN,access=rw------,values=1 : values=on numid=0,iface=MIXER,name='Capture Volume' ; type=INTEGER,access=rw------,values=2,min=0,max=65536,step=1 : values=65536,65536
It seems there is some difference in my AR41E model. Any suggestion?
I found an easy solution for dimming and I post there now.
That's pretty odd. I don't know about Cyberkilla, but I have
options snd-hda-intel probe_mask=3 model=vaio
Maybe you have an older kernel? What does uname -r say?
--eaglex 11:49, 28 February 2009 (EET)
I use Ubuntu 8.10 and have 2.6.27-11-generic I'll try with your setting on alsa-base
Great! the option with "probe_mask" you suggest works also for me! Thanks a lot. It changes to Sigma Tel codec and also alsa-mixer works now. The only thing it is that it doesn't work with ekiga (also the webcam doesn't work with ekiga...)
Hard Disk APM Modes
Through trial and error, I have found APM 192 to be the best hard drive power mode at the moment.
I can't cite anything specific. Having read the specs for the hard drive on this model, it has a mode where head parking happens and above that is a mode where the drive will conserve power but not park heads. This seems to be the best option for Ubuntu at the moment.
I've tried to guess when these modes change. With the APM mode to anything below 192, hard parking eventually occurs. At APM 192, head parking stops happening.
I have also monitored the temperate of the drive.
- My Findings
APM 192 peaks at ~33C for me, and no head parking occurs.
APM 254 peaks at ~39C.
Clearly, the most energy efficient APM setting without head parking *appears* to be 192.
In addition, the specs claim that the hard disk can deal with internal temperatures of at least 60C. It does not work in ambient temperatures of 60C, but then, neither does your body so it's not a problem:)
Power modes Heads Spindle Buffer Active (operating) Tracking Rotating Full power Idle, performance Tracking Rotating Self refresh—low power Idle, active Floating Rotating Self refresh—low power Idle, low power Parked Rotating Self refresh—low power Standby Parked Stopped Self refresh—low power Sleep Parked Stopped Self refresh—low power
The Specs - as far as I know, this is the right specs. I found it on their site.
Data Sheet
--Cyberkilla 16:18, 23 February 2009 (EET)
Wow, did a lot of research and testing there. Thanks for all the info.
If you want, you can add it to the main page, otherwise I'll do it when I eventually get time.
--eaglex 17:57, 24 February 2009 (EET)
Just wondering, by comparision, don't you get a lot more activity (LED flashing) with it at 192 than at 255?
--eaglex 18:01, 28 February 2009 (EET)
On the contrary, the opposite is true for me. Setting it to mode 192 _stops_ the drive from making noises and disk access was unaffected. As far as I know, you should have the exact same hard drive as me, so it should behave the same. I don't know why you would experience extra noises.
I'll keep an eye open over the next few days and let you know if the LED flashes more often for me. Thanks for trying the 192 setting yourself.
--Cyberkilla 15:14, 4 March 2009 (EET)
