New S and Y models: Brightness and Fn Keys

I'm using Debian Squeeze testing mode with KDE 4 in a new Vaio S model. (Intel HD Graphics)

I have installed sony-laptop module using Synaptic.

- Wifi and network installed and working. Using Wicd.
- Camera works (checked with Cheese).

However, I have these pendent issues:

- No brightness control by Fn keys or software, despite the sound Fn keys is working. This is specially annoying.
- No sound despite Fn keys shows the progress bar .
- No light keyboard control: no control of time for keys light off. Now light is on/off in an default automatic way.

Some idea to solve this?. Other people with this model?.

 

use google and search for sony_acpi.tgz download and make.It will compile a kernel module, you should simply load when your system is booting. you can use it to adjust display-brightness

as far as the fn-keys...umm..if sonypid is activated in the kernel ( Device Drivers > Character Devices >Sony Vaio Programmable I/O Control Device support). the system should recognize the events by the fn keys

you can also try xbindkeys
http://packages.debian.org/search?keywords=xbindkeys

hope this helps

 

Last time i compiled kernel (2.6.32.7) i saw there somewhere the options to compile it with modules for Sony laptops Fn keys ...

 

yes, now I'm checking just that.
All is quite confusing... there is one sonypi module but it seems obsolete for a new sony_laptop. But it doesn't work to me. Also there are some options for Sony in the kernel, and the sony_acpi.tgz cited by 1ceBlu3.
I'm investigating all that before making more installations. I'm not very expert in uninstalling them in case of failure.

Problem is the new Vaio S series still doesn't have many users.

thanks for any information

 

Sound works following this advice: http://ubuntuforums.org/showpost.php?p=8830993&postcount=2.
Check if some channel is inactive (or set to a low volume) using alsamixer, too.

 

For troubleshooting hotkey problems try running xev to see if the scancodes are even being picked up. If they aren't, it's likely that the sony kernel module needs to be modified.

https://wiki.ubuntu.com/Hotkeys/Troubleshooting
https://wiki.ubuntu.com/Hotkeys/Architecture

Good luck!

 

It's quite funny because KDE's Systemsettings actually recognizes Fn+F5 as "Monitor Brightness Down", and if I set Fn+F5 to, say, maximize window size, it DOES work, but it doesn't work if you set it to dim the monitor. Consider that the brightness slider in Battery Monitor widget DOES work, and brightness settings in KDE's power profiles are applied correctly.

Quite funny indeed

 

not my case. slider in battery widget doesn't work using AC instead battery. (I cannot try battery at this moment). Have you try with AC?

well, to me brightness and sound it's quite a nightmare... Sony_acpi cannot be compiled due to errors, although it seems the keys are recognized

sony-latop module apparently is charged:

Code:

root@debian:/var/log# cat dmesg |grep sony
[    7.004848] sony-laptop: Sony Notebook Control Driver v0.6.
[    7.040033] sony-laptop: brightness ignored, must be controlled by ACPI video driver
[   16.388921] sonypi: Sony Programmable I/O Controller Driver v1.26.

root@debian:/var/log# cat messages |grep sony
Mar  1 01:27:40 debian kernel: [    6.959307] sony-laptop: Sony Notebook Control Driver v0.6.
Mar  1 01:27:40 debian kernel: [    6.998517] sony-laptop: brightness ignored, must be controlled by ACPI video driver
Mar  1 01:27:43 debian kernel: [   16.387412] sonypi: Sony Programmable I/O Controller Driver v1.26.

and testing with xev, the Fn+f5 and Fn+f6 keys are working:

Code:

root@debian:/var/log#xev
KeyRelease event, serial 35, synthetic NO, window 0x3600001,
    root 0x112, subw 0x0, time 3391620, (407,459), root:(408,484),
    state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 35, synthetic NO, window 0x3600001,
    root 0x112, subw 0x0, time 3395772, (407,459), root:(408,484),
    state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

and in Xorg.0.log:

Code:

(II) config/udev: Adding input device "Sony Vaio Keys" (/dev/input/event6)
(**) "Sony Vaio Keys": always reports core events
(**) "Sony Vaio Keys": Device: "/dev/input/event6"
(II) "Sony Vaio Keys": Found keys
(II) "Sony Vaio Keys": Configuring as keyboard
(II) XINPUT: Adding extended input device ""Sony Vaio Keys"" (type: KEYBOARD)

about alsa, no success with these lines inside /etc/modprobe.d/alsa-base.conf:

Code:

# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2

options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel enable_msi=1
options snd-hda-intel model=sony-assamd


# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2

Some help?

 

Have you done an lspci | grep -i audio and then try the options for your chipset in http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio-Models.txt

Sometimes you need to try a few before it works, even if they aren't sony ones.

If you are getting errors compiling the sony acpi module it could be because you don't have the required dependencies (it should compile with the build-essential virtual package), or your glibc is too old for the newer kernel stuff. But if you post the actual errors maybe someone can help with that.

 

using this little program it's possibile to disable the bluetooth antenna without turning off all the radios. it made me gain a bit more battery life.

 

hi guys,
just wanted to share my experience with ubuntu 10.4 Beta 1.
The first problem was that I simply got a black screen after installing, this is because of a bug in the nvidia driver that causes the graphic card not to realize that there is an internal display connected.
At first I had to boot with the grub-option "nomodeset". In the grub boot loader press e and then add "nomodeset" at the end of the boot command, then press Ctrl+X to boot (I don't remember where I read this and I don't even now what this actually does ).
You should then be able to boot up and install the proprietary Nvidia drivers in System -> Hardware Drivers.
After a reboot you should see a black screen once again. Now boot in recovery mode to get a console and follow these instructions:
http://www.nvnews.net/vbulletin/showpost.php?p=2118873&postcount=22

To make your HDMI port work as well you have to add DFP-1 to the "ConnectedMonitor option in the xorg.conf. It should look like this:
Option "ConnectedMonitor" "DFP-0,DFP-1"

After that, everything should be working.


W-LAN, LAN, Bluetooth work out of the Box on 10.4, this is how you get your internal sound card working:

Download the latest ALSA driver from http://www.alsa-project.org/main/index.php/Main_Page

Unpack it:
tar xfj alsa-driver-1.0.22.1.tar.bz2
cd alsa-driver-1.0.22.1

Now we have to compile and install the driver:
./configure
make
sudo make install

After that, add this line to /etc/modprobe.d/alsa-base.conf :

options snd-hda-intel model=sony-assamd

After a reboot, sound should be working.

The only thing that I still didn't get working is the HDMI audio, the ALSA driver does not seem to support it yet. See also here (should be the same sound chip):
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-December/023858.html

edit:
btw, brightnes keys don't work for me as well, I have the same problem as zvo, I can't compile it.

 

thanks for sharing that! i'm sure it will come in handy for someone somewhere along the way

 

Seems like I got HDMI audio working as well, I can't test it at the moment, but at least I see the device in the sound settings.

Just download the latest snapshot of the ALSA driver from here:
http://ftp.kernel.org/pub/linux/kernel/people/tiwai/alsa/alsa-driver/

Please keep in mind that these are unstable builds and could screw up your system (I guess )!

tar xfvz alsa-driver-snapshot.tar.gz
cd alsa-driver
./configure
make
sudo make install
sudo reboot

done.

 

the brightness keys problem is solved in kubuntu lucid following the advice here: https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/461524, precisely the post #11

Standard Ubuntu Lucid should have no problem since they got rid of hal

 

Finally got HDMI sound working with my NVidia card!
Install the latest ALSA-Driver (1.0.23) and add the following to /etc/modprobe.d/alsa-base.conf :

Code:

options snd-hda-intel enable_msi=0 probe_mask=0xffff,0xfff2

 

Hehe, Geez, this is like some sorcery spell, where u sure sacrifice your very linux soul to some very 'evilest' soundserver? !! The word 'intel' detect some real foul magicks!! :-DDD