No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics

[getaceres]

Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:

On various laptops from Sony, HP, Samsung and others there is no way to control backlight brightness. In case of Sony e.g. on Vaios with 8-series adapters, e.g.
nVidia Corporation GeForce 8400M GS
nVidia Corporation GeForce 8600M GT (rev a1)

The registers have been found (kudos to mikes!) and incorporated into
nvclock, which you can check out by anonymous cvs and install:

]$ sudo apt-get install cvs
]$ cvs -d:pserver:<email address hidden>:/cvsroot/nvclock login
]$ cvs -z3 -d:pserver:<email address hidden>:/cvsroot/nvclock co -P nvclock
]$ cd nvclock
]$ ./autogen.sh
]$ ./configure
]$ make
]$ sudo make install

To test, make sure you are using nVidia's proprietary driver, then:
]$ sudo nvclock -S 100
]$ sudo nvclock -S 15
]$ sudo nvclock -S +10

So far mikes' registers have been found to work on:

Apple laptops
{
Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
}

HP/Compaq laptops
{
8510W (Quadro FX 570M, MXM)
8710P (Quadro NVS 320M, MXM)
}

Samsung laptops:
{
Q210 (Geforce 9200M)
Q310 (Geforce 9200M)
R510 (Geforce 9200M)
}

Sony laptops:
{
8400M GS:
VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E SZ95S, SZ6RMN

8400M GT:
VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E, FZ21M, FZ21S, FZ470E, FZ340E, FZ190N, FZ18M, FZ31E, FZ18E, FZ260E NR21Z, NR38S, NR21S,FZ280E

8600M GS:
VGN FZ31Z, FZ21Z, FZ31S

8600M GT:
VGN AR51SU, AR71S
}

Zepto laptops
{
Geforce 9600GT based laptops using MXM cards
}

Add your model to the list by clicking on the "Update description / tags" link, NOT by asking in a bug comment for someone else to do it.

To get hotkeys to work, follow the instructions in this comment:
https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/75
or install the package at :
https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/111

Dual-adapter models (SZ6 among others) can get backlight control with the Intel adapter using xbacklight, and can get hotkey functionality as per bug #173652.

[unggnu (unggnu)]

If it still doesn't work try sudo modprobe sony-acpi . Sometimes the module isn't loaded. Maybe this is your problem.

[getaceres (getaceres)]

It's loaded and still Fn doesn't work and brightness is only adjustable through smartdimmer.

jose@ubuntu-vaio:~$ lsmod | grep sony
sonypi 23196 0
sony_acpi 6284 0
jose@ubuntu-vaio:~$

[unggnu (unggnu)]

Could you please recheck it with latest Ubuntu Gutsy Gibbon 7.10 or the Live CD? I guess the problem was the change from sony-acpi to sony-laptop.

[Leann Ogasawara (leannogasawara)]

This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks again!

[getaceres (getaceres)]

Sorry for the delay. I've tried with both, the Live CD and my up to date Gutsy installation and they don't work (Fn is not responding and brightness cannot be changed in the gnome power manager preferences).

[getaceres (getaceres)]

Tried with Hardy Alpha 6 Live CD and still brightness and FN keys don't work.

[Leann Ogasawara (leannogasawara)]

Hi getaceres,

On the latest Hardy Alpha release, please provide the information outlined here: https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch . Thanks.

[getaceres (getaceres)]

Volume keys work, but not the two laptop hotkey shortcuts:

By Method 3: For every key press I get two numbers, everyone with a received and completed message.

Shortcut S1:
[Mon Mar 17 21:44:00 2008] received event "sony/hotkey SNC 00000001 00000090"
[Mon Mar 17 21:44:00 2008] received event "sony/hotkey SNC 00000001 00000010"

Shorcut S2:
[Mon Mar 17 21:45:14 2008] received event "sony/hotkey SNC 00000001 00000091"
[Mon Mar 17 21:45:14 2008] received event "sony/hotkey SNC 00000001 00000011"

Brightness Down (Fn+F5):
[Mon Mar 17 21:46:58 2008] received event "sony/hotkey SNC 00000001 00000010"
[Mon Mar 17 21:46:58 2008] received event "sony/hotkey SNC 00000001 0000003b"

Brightness Up (Fn+F6):
[Mon Mar 17 21:47:59 2008] received event "sony/hotkey SNC 00000001 00000011"
[Mon Mar 17 21:47:59 2008] received event "sony/hotkey SNC 00000001 0000003b"

Display change between LCD/External/Both (Fn+F7):
[Mon Mar 17 21:49:55 2008] received event "sony/hotkey SNC 00000001 00000012"
[Mon Mar 17 21:49:55 2008] received event "sony/hotkey SNC 00000001 0000003b"

Suspend (Fn+F12):
[Mon Mar 17 21:51:11 2008] received event "sony/hotkey SNC 00000001 00000017"
[Mon Mar 17 21:51:11 2008] received event "sony/hotkey SNC 00000001 0000003b"

These are the main Fn functions although there are more like the numeric keypad and block despl.

The model:

sudo dmidecode -s system-manufacturer
Sony Corporation

sudo dmidecode -s system-product-name
VGN-FE31Z

sudo dmidecode -s system-version
C3LN0NJF

Also, brightness don't work even changing the slider in the gnome power management screen and only works using the smartdimmer command.

[for1dev (afor1ner)]

I'm having the same problem with my Vaio FZ280E. Too bad it didn't ship with a pair of sunglasses.

Been watching this thread very closely:
http://www.nvnews.net/vbulletin/showthread.php?t=100494&page=4

yaayyy open source on proprietary hardware :)

[Bram (brvdpu)]

I think my hotkey doesn't word because i use the nvidia drivers (v 173.14.12), which take care of the brightness too. Any idea how to set my system up to still be able to use the hotkeys?

[getaceres (getaceres)]

Tried with 2.6.27 kernel but still not working. Not only the brightness keys (which may be due to nvida) but I can't get to work any of the fn+<something> keys.

[Schmirrwurst (schmirrwurst)]

I'm experiencing the same problems on FZ21E and Intrepid A6
Changing the brightness from the nvidia driver panel is working well, but it doesn't work from the keys, so I wonder if it is realy a nvidia driver issue ??

[Schmirrwurst (schmirrwurst)]

I'm currently using the 177 driver
ii nvidia-177-kernel-source 177.76-0ubuntu1 NVIDIA binary kernel module source
ii nvidia-177-modaliases 177.76-0ubuntu1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-glx-177 177.76-0ubuntu1 NVIDIA binary Xorg driver

kernel : 2.6.27-3-generic #1 SMP Wed Sep 10 16:18:52 UTC 2008 x86_64 GNU/Linux

$ modinfo sony_laptop
filename: /lib/modules/2.6.27-3-generic/kernel/drivers/misc/sony-laptop.ko
version: 0.6
license: GPL
description: Sony laptop extras driver (SPIC and SNC ACPI device)
author: Stelian Pop, Mattia Dongili
srcversion: E48E3D714530434ADDC399C
alias: acpi*:SNY6001:*
alias: acpi*:SNY5001:*
depends:
vermagic: 2.6.27-3-generic SMP mod_unload modversions
parm: debug:set this to 1 (and RTFM) if you want to help the development of this driver (int)
parm: no_spic:set this if you don't want to enable the SPIC device (int)
parm: compat:set this if you want to enable backward compatibility mode (int)
parm: mask:set this to the mask of event you want to enable (see doc) (ulong)
parm: camera:set this to 1 to enable Motion Eye camera controls (only use it if you have a C1VE or C1VN model) (int)
parm: minor:minor number of the misc device for the SPIC compatibility code, default is -1 (automatic) (int)

[Schmirrwurst (schmirrwurst)]

following bug is already about this subject, but as it is treating to problems at a time (two different cards) I believe it is better to hold them seperate.
https://bugs.launchpad.net/ubuntu/+source/xbacklight/+bug/173652, there for it is not a duplicate..

[Michael Doube (michael-doube)]

I agree - I've sent nVidia problems from bug #173652 to this bug. As I understand it, sony-laptop generates ACPI events for the key-presses but the script that it calls doesn't do anything to affect backlight brightness. I'm not sure who's responsible for setting LED backlight: sony-laptop or nvidia driver? Possibly the backlight is an SNC method http://tjworld.net/snc/ or a CMOS register http://tjworld.net/wiki/Sony/Vaio/FE41Z/HackingBiosNvram (please note, I am clueless here...)

And for those who set their 'brightness' with the nVidia tool, you are only changing LCD values, not LED values, i.e. you are changing the colours of the screen not the intensity of the backlight so there is no power saving (only eye saving!).

[benste (benste)]

Hy,
I'm not shure why I've been subscribed to this thread by __
but, in my opinion it's not resbonsibilty of nvidia, because brightness should not only work with the GLX driver also with the standard nv one.
I tried my things today on interpid again with the following result:
ACPI Events are recocnized - but nothing happens BUT from time to time NVclock seems to cause a "report this bug message". The keys on a european FE31m are like folowed:
benste@vaiofe31m:~$ acpi_listen
S1
sony/hotkey SNC 00000001 00000090
sony/hotkey SNC 00000001 00000010
s2
sony/hotkey SNC 00000001 00000091
sony/hotkey SNC 00000001 00000011
FN+ F5 (brightn down)
sony/hotkey SNC 00000001 00000010
sony/hotkey SNC 00000001 0000003b
FN + F6 (up)
sony/hotkey SNC 00000001 00000011
sony/hotkey SNC 00000001 0000003b
FN + F7 (external display change)
sony/hotkey SNC 00000001 00000012
sony/hotkey SNC 00000001 0000003b
FN + F10 (zoom display)
sony/hotkey SNC 00000001 00000015
sony/hotkey SNC 00000001 0000003b
FN + F12 (suspend to disk)
sony/hotkey SNC 00000001 00000017
sony/hotkey SNC 00000001 0000003b

And that's it,
I'm not shure what is going on in the last time, but it would be easier for me if I would know who does what since at minimum one year it seems for me that no one does anything but all are just reporting the same bug.

PS: if Nvidia should develop a brightness support via Nvclock, what a bout those who aren't using the proprate driver?

[Alberto Milone (albertomilone)]

Can you post the output of this command?
smartdimmer -g

[Michael Doube (michael-doube)]

mdoube@doris:~$ smartdimmer -g
init_nvclock() failed!

Alberto Milone wrote:
> Can you post the output of this command?
> smartdimmer -g
>
>

[benste (benste)]

three times:

benste@vaiofe31m:~$ smartdimmer -g
SmartDimmer level: 21
benste@vaiofe31m:~$ smartdimmer -g
SmartDimmer level: 21
benste@vaiofe31m:~$ smartdimmer -g
SmartDimmer level: 21
seems to work or?

even -m and -i for dimming works including the wanted effect but Fn woun't work :-)

@ Michael:
you've got a 8 or 7 series?? did you install restricted driver?

[Warren Seine (warren-seine)]

I'm in the same case as Michael. I use a Vaio VGN-AR41E with a GeForce
8400M and its restricted driver.

Brightness is really a problem. It works by changing the value in the
nvidia-settings panel, but it doesn't look like it's *screen*
brightness (and still burn my eyes !).
--
Warren Seine

[benste (benste)]

We may seperate this bug for 7- series and 8+ series or?

because in 7 and lower series nvclock works and in 8+ not

[Michael Doube (michael-doube)]

Benste:

nVidia 8400M GS, restricted driver.

Yes, I think we should make it clear that smartdimmer supports the 7
series but not the 8 series at this point.

[loxan (5-launchpad-loxley-se)]

Brightness keys doesn't work on Sony Vaio AR71S either.

nVidia Corporation GeForce 8600M GT (rev a1)

uses the sony-laptop module.

Have to use nvidia-settings, but it's really crappy way of doing it.

[benste (benste)]

Should I open a new one for 7series '?
I'm just a user so I wouldn't be able to find solutions :-)

[Michael Doube (michael-doube)]

Benste

Please do. There must be some problem in sonybright.sh if your backlight adjustment is not working from hotkeys, either it not being called, or its actions aren't being interpreted or the script itself is just wrong. Have you tried running

]~$ sudo /etc/init.d/acpid restart

After logging in to Ubuntu, then trying hotkeys again? This is necessary to make the script work as per bug #173652

[benste (benste)]

yes it probably muste be ther :-)

benste@vaiofe31m:/etc/acpi/events$ sh sony-brightness-down
sony-brightness-down: 3: Syntax error: "(" unexpected

[benste (benste)]

Michael, would you be so pleasant to post my z series bug problem ?
I'm not able to create - and link it to all the related branches.

thx.

You may better write a summary than me :-)

[benste (benste)]

Opened here:

https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589

[asino89 (asino89)]

I'm writing from a live session (so whitout nvidia rstricted drivers) of ubuntu intrepid ibex beta version (downloaded yesterday)...
No way of changing the brightness of my sony vaio vgn-nr31S...

I report some of the trials i did:

ubuntu@ubuntu:/etc/acpi/events$ sh sony-brightness-down
sony-brightness-down: 3: SPIC: not found
sony-brightness-down: 4: down: not found

xbacklight -set 50
No outputs have backlight property

 /etc/acpi/sonybright.sh down
cat: /sys/class/backlight/sony/brightness: No such file or directory
/etc/acpi/sonybright.sh: line 8: [: : integer expression expected
/etc/acpi/sonybright.sh: line 15: /sys/class/backlight/sony/brightness: No such file or directory

Hope this will help somebody to fix this bug...

[Schmirrwurst (schmirrwurst)]

Same keys for my vgn-fz21E

On Wednesday 24 September 2008 18:30:56 benste wrote:
> Hy,
> I'm not shure why I've been subscribed to this thread by __
> but, in my opinion it's not resbonsibilty of nvidia, because brightness
> should not only work with the GLX driver also with the standard nv one. I
> tried my things today on interpid again with the following result: ACPI
> Events are recocnized - but nothing happens BUT from time to time NVclock
> seems to cause a "report this bug message". The keys on a european FE31m
> are like folowed: benste@vaiofe31m:~$ acpi_listen
> S1
> sony/hotkey SNC 00000001 00000090
> sony/hotkey SNC 00000001 00000010
> s2
> sony/hotkey SNC 00000001 00000091
> sony/hotkey SNC 00000001 00000011
> FN+ F5 (brightn down)
> sony/hotkey SNC 00000001 00000010
> sony/hotkey SNC 00000001 0000003b
> FN + F6 (up)
> sony/hotkey SNC 00000001 00000011
> sony/hotkey SNC 00000001 0000003b
> FN + F7 (external display change)
> sony/hotkey SNC 00000001 00000012
> sony/hotkey SNC 00000001 0000003b
> FN + F10 (zoom display)
> sony/hotkey SNC 00000001 00000015
> sony/hotkey SNC 00000001 0000003b
> FN + F12 (suspend to disk)
> sony/hotkey SNC 00000001 00000017
> sony/hotkey SNC 00000001 0000003b
>
> And that's it,
> I'm not shure what is going on in the last time, but it would be easier for
> me if I would know who does what since at minimum one year it seems for me
> that no one does anything but all are just reporting the same bug.
>
> PS: if Nvidia should develop a brightness support via Nvclock, what a
> bout those who aren't using the proprate driver?
>
>
> ** Changed in: hotkey-setup (Ubuntu)
> Status: New => Confirmed
>
> ** Changed in: hotkey-setup (Ubuntu)
> Status: Confirmed => In Progress
>
> ** Changed in: nvidia-graphics-drivers-177 (Ubuntu)
> Status: New => In Progress
>
> ** Changed in: linux (Ubuntu)
> Status: New => In Progress

[mikes (mikevas)]

Any news? I managed to fix the sony_laptop module to work with the Vaio VGN-NR31 and register the Fn keypresses as ACPI events. If anyone wants the fixed module please contact me.

But the serious problem is the lack of knowledge about the nvidia 8 series smartdimmer internals. Any luck with this? Can I help with anything? I got a 8400M GT (G86)

[mikes (mikevas)]

Could we please at least raise the "importance" of this task? It is really critical since a) laptop is unusable when on batery, and b) picture is too bright and washed out when on full brightness. I understand that it has to do with nvidia and/or sony, but this does not make it any less important.

Thanks

[benste (benste)]

@mikes,
could you fix my file?

https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589

[Michael Lustfield (michaellustfield)]

I just want to add that nothing works until I do 'xrandr --output LVDS --set BACKLIGHT_CONTROL native'. After that, xbacklight and function keys work to set screen brightness.

I also get this:
michael@panther:~$ smartdimmer -g
init_nvclock() failed!

As far as this error goes...
michael@panther:~$ /etc/acpi/sonybright.sh down
cat: /sys/class/backlight/sony/brightness: No such file or directory
/etc/acpi/sonybright.sh: line 8: [: : integer expression expected
/etc/acpi/sonybright.sh: line 15: /sys/class/backlight/sony/brightness: No such file or directory

The reason is because the file has moved to /sys/class/backlight/acpi_videoX/brightness where X is either 0 or 1. However, changing this value doesn't seem to make a difference in the screen brightness.

I don't know if any of this was useful to anybody else, but I hope so.

[Hans (hans-eichbaum)]

I have a Vaio VGN-SZ71MN/B. This Vaio has 2 graphic cards, controlable with a switch that says stamina / speed.
When I select 'stamina' the Intel G965 is used and I have nicely brightness control with xbacklight after using the xrandr trick. When I select 'speed' the Nvidia Geforce 8 card is used and I have no brightness control.

I have read lots about the Nvidia brightness control problems with Vaio's and wondering now the following. If the brightness control is just controllable via a register, why is it any different for the Nvidia? Or in other words, is it really just a register?
Like others I have observed occasionally flickering when using the Nvidia card, might this be related to the brightness control? has it been deliberately disabled due to this flickering problem (it might be worse when controlling the brightness leds)??

[mikes (mikevas)]

Any progress/ideas on this?

[kiloxxx (kiloxxx)]

Only a little progress with hotkeys, not with backlight.

I have a VGN-FZ11Z, after the last kernel upgrade (2.6.24-21-generic i686) it finally recognizes the brightness keys correctly. Not only acpi_listen gives responses when the key are pressed, but also kde open a little pop-up referring to the increase and the decrease of brightness.
Unfortunately the actual brightness is still fixed to 100%.

[benste (benste)]

fyi,
yohan Lee-tin-yien developed a .deb file exaktly for this situation (keypresses are converted into actions but nothing happens.)
BUT it woun't work until you've got a working smartdimmer which is maybe a bit triggy or not possible yet with 8 or 9 series.
The debb file will be uploaded asap.

[mikes (mikevas)]

I had some progress here. I attached Vista to WinDbg and traced inside the kernel and drivers. I found what it does to change the backlight, but I need some more work in order to port this to Linux. The actual change happens with a call to WRITE_REGISTER_ULONG in a kernel virtual address (9XXXXXXX) with values from 800000f0 (low) to 80000401(full). It seems prety straighforward. There is no port IO as in the pommed driver, and I dont know how this address (9XXXXXXX) is translated to nvidia register addresses and/or physical bus addresses. There are calls to HalTranslateBusAddress and mmMapIoSpace at the initialization of the driver, I'll have to trace those and see where they map the used address spaces. I will work some more on it and post the results.

If anyone is experienced with memory mapped I/O stuff in both Win and Linux, please help!

[mikes (mikevas)]

BINGO! As I am writing to you, my LCD brightness is set to a comfortable low level and my battery time is 2+ hours! The physical address for the register is 0xCE61C084 for the 8400M, if it means anything to you. I did a quick and dirty hack on nvclock to set the register and it worked. Possible values are from 0x0 to 0x401. To set the brightness you have to bitwise-OR the value with 0x80000000. The max value for my panel is 0x401. This means that you have to write 0x80000401 to 0xCE61C084 in order to set the brightness to full. 0x80000100 is ok for something relatively low. All values in-between are working. Implementing the nice backlight fade-in and fade-out effect from Vista should be easily doable.

Have in mind that when you are reading the value of the register the leading 8 does not appear. It is needed when you set the brightness though. The register eats it and is left with the least significant part which is the real value (i.e. 0x00000401).

For those that are going to incorporate this to smartdimmer and/or nvclock, have in mind that this physical address is outside of the ranges that are mmap-ped in the backend code, so you possibly need to add a new pointer member in the NVCard struct.

[Warren Seine (warren-seine)]

Great news! Let's hope things will improve quickly now :)
I'm on a 8400M too and would be glad to test your hack.
--
Warren Seine

[Sérgio Almeida (mephx-x)]

On Tuesday 21 October 2008 03:22:28 SooW wrote:
> Great news! Let's hope things will improve quickly now :)
> I'm on a 8400M too and would be glad to test your hack.
> --
> Warren Seine

Mikes sent me the hack of nvclock some minutes ago.

To adjust, near line 1060 +/- you will see: *(nv_card->PDIMMER) = 0x80000100;

Change this from 0x80000030 (minimum until failure) to 0x80000400 /maximum
until failure).

Hope this helps.

Cheers,
mephx

[Warren Seine (warren-seine)]

On Mon, Oct 20, 2008 at 10:37 PM, mephx <email address hidden> wrote:
> On Tuesday 21 October 2008 03:22:28 SooW wrote:
>> Great news! Let's hope things will improve quickly now :)
>> I'm on a 8400M too and would be glad to test your hack.
>
> Mikes sent me the hack of nvclock some minutes ago.
>
> To adjust, near line 1060 +/- you will see: *(nv_card->PDIMMER) =
> 0x80000100;
>
> Change this from 0x80000030 (minimum until failure) to 0x80000400 /maximum
> until failure).
>
> Hope this helps.
>
> Cheers,
> mephx

I comfirm that it works on a VAIO VGN-AR41E with 8400M.
My eyes and my battery say thank you, mikes.

--
Warren Seine

[Niels Slot (nielsslot)]

I can confirm this work on a Sony Vaio FZ38M with a 8400M GT. Mikes: thank
you very much :).

2008/10/21 mephx <email address hidden>

> On Tuesday 21 October 2008 03:22:28 SooW wrote:
> > Great news! Let's hope things will improve quickly now :)
> > I'm on a 8400M too and would be glad to test your hack.
> > --
> > Warren Seine
>
> Mikes sent me the hack of nvclock some minutes ago.
>
> To adjust, near line 1060 +/- you will see: *(nv_card->PDIMMER) =
> 0x80000100;
>
> Change this from 0x80000030 (minimum until failure) to 0x80000400 /maximum
> until failure).
>
> Hope this helps.
>
> Cheers,
> mephx
>
>
>
> ** Attachment added: "nvclock_hacked.tgz"
> http://launchpadlibrarian.net/18755253/nvclock_hacked.tgz
>
> --
> No Screen Backlight Control; Sony Vaio with nvidia 8 series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[kiloxxx (kiloxxx)]

Really a great news!!!
I've just installed the hacked version of nvclock and after "nvclock -S 50" the brightness in now set to 50%!
Unfortunately it worked just one time, if I try to change again the brightness it gives to me:

Error!
Smartdimmer is only supported on certain laptops using a Geforce 6200/7x00Go. If you want support on your laptop contact the author.

and it doesn't change nothing (I don't think the error message is related because I could see it also the first time).
The only way to restore brightness is to reboot my laptop, then "nvclock -S 50" works again, but just for one time.
Any idea?

[seek (seek-matrixcode)]

I am test it too.

Same problem.

works ed just one time.

i am using a Vaio VGN-FZ31Z

-- General info --
Card: nVidia Geforce 8600M GS
Architecture: G86 A2
PCI id: 0x425

after the work i will to more tests.

[seek (seek-matrixcode)]

Ok. Forget my last comment.

It works.

The value is hard coded.

great job mikes

[kiloxxx (kiloxxx)]

I think that my error would be related to the use of "nvclock -S 50".
But, where have I to write the value?
Thank you.

[seek (seek-matrixcode)]

here is my changed source.

change the code at: *(nv_card->PDIMMER) = 0x80000100;

printf("br: %i\n", brightness);
printf("wmask: %08x\n", 0x80000000 | brightness);
if(brightness >= 0 && brightness < 1024) {
  (nv_card->PDIMMER) = 0x80000000 | brightness; //0x0 to 0x401
} else {
  printf("value must be between 0 and 1024\n");
}
printf("DIMMER: %08x\n", *nv_card->PDIMMER);·

[Michael Doube (michael-doube)]

Could you please post a tarball here so we can test your hack?

Many thanks for your work, mikes.

[seek (seek-matrixcode)]

here is my version for testing:
http://stud.matrixcode.de/nvclock_hacked_seek.tgz

> ./nvclock -S 256
br: 256
wmask: 80000100
DIMMER: 00000100

>./nvclock -S 1024
br: 1024
wmask: 80000400
value must be between 0 and 1024
DIMMER: 00000100

[kiloxxx (kiloxxx)]

Ok, I will try to change the source, but which file?

[Michael Doube (michael-doube)]

Woops, sorry, now I see it!

[seek (seek-matrixcode)]

i changed only src/nvclock.c

near line 1060 +/-: *(nv_card->PDIMMER) = 0x80000100;

and again. great job mikes :D

[kiloxxx (kiloxxx)]

Excuse me too, I hadn't see the file.
Now it works, on a FZ11Z with 8400M GT.
After more than one year I finally could manage the brightness!
Great job, really.

[Michael Doube (michael-doube)]

seek - thanks, I have your version of nvclock working on Intrepid amd64 on a Vaio SZ650

[Michael Doube (michael-doube)]

mikes: could you please detail the method that you used to discover the registers so that others may do this on future iterations and possibly other manufacturers' implementations of nVidia devices? The basic problem here was that no-one had a clue how to get the information that you have discovered.

[mikes (mikevas)]

I did not do something streamlined like using a tool or something. I just
reversed the nvidia driver in vista. I am not sure if there is any point in
describing the process here. There are tons of info on reverse engineering
on the net, but here is a general description.

After failing to spot any changes in the documented registers that are
dumped by RivaTuner (after even extending the ranges) I had to take it more
seriously. I attached WinDbg (the Windows kernel debugger) from a remote pc
via firewire and traced through the windows kernel and nvidia driver, by
examining the dissasembled code (using IDA Pro) and the memory and by
putting breakpoints here and there. I found the address that is modified and
caused the backlight level to change. After that you need to convert this
virtual address to a physical bus address in order to use it from another
operating system (or even the same system under different circumstances). I
booted linux, modified the nvclock backend to write values to the new video
memory location and voila!

Have in mind that reversing commercial software like the Nvidia drivers is
illegal.

Michael

On Tue, Oct 21, 2008 at 1:29 PM, Michael Doube <email address hidden> wrote:

> mikes: could you please detail the method that you used to discover the
> registers so that others may do this on future iterations and possibly
> other manufacturers' implementations of nVidia devices? The basic
> problem here was that no-one had a clue how to get the information that
> you have discovered.
>
> --
> No Screen Backlight Control; Sony Vaio with nvidia 8 series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "hotkey-setup" source package in Ubuntu: In Progress
> Status in "linux" source package in Ubuntu: In Progress
> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: In
> Progress
>
> Bug description:
> Using Ubuntu on Sony Vaio laptop with Nvidia 8 vga card:
>
> There is no way to control backlight brightness on Sony Vaios with 8-series
> adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!). See these hacked nvclock
> sources for fixed versions which can set backlight on Sony Vaios:
>
> http://stud.matrixcode.de/nvclock_hacked_seek.tgz
> http://launchpadlibrarian.net/18755253/nvclock_hacked.tgz
>
> So far mikes' registers have been found to work on:
> 8400M GS on Vaio SZ650
> 8400M GT on Vaio FZ38M, FZ11Z
> 8600M GS on Vaio FZ31Z
>
> Invoking sonybright.sh with hotkeys will do nothing until the script calls
> new versions either SmartDimmer or nvclock properly.
>
> Dual-adapter models (SZ6 among others) can get backlight control with the
> Intel adapter using xbacklight, and can get hotkey functionality as per bug
> #173652.
>

[mikes (mikevas)]

My Vaio is VGN-NR31. Can someone add it to the description?

[Alberto Milone (albertomilone)]

I have added VGN-NR31 to the description.

[Sérgio Almeida (mephx-x)]

On Tuesday 21 October 2008 12:48:04 Alberto Milone wrote:
> I have added VGN-NR31 to the description.
>
> ** Description changed:
>
> Using Ubuntu on Sony Vaio laptop with Nvidia 8 vga card:
>
> There is no way to control backlight brightness on Sony Vaios with
> 8-series adapters, e.g. nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!). See these hacked
> nvclock sources for fixed versions which can set backlight on Sony
> Vaios:
>
> http://stud.matrixcode.de/nvclock_hacked_seek.tgz
> http://launchpadlibrarian.net/18755253/nvclock_hacked.tgz
>
> So far mikes' registers have been found to work on:
> 8400M GS on Vaio SZ650
> - 8400M GT on Vaio FZ38M, FZ11Z
> + 8400M GT on Vaio FZ38M, FZ11Z, VGN-NR31
> 8600M GS on Vaio FZ31Z
>
> Invoking sonybright.sh with hotkeys will do nothing until the script
> calls new versions either SmartDimmer or nvclock properly.
>
> Dual-adapter models (SZ6 among others) can get backlight control with
> the Intel adapter using xbacklight, and can get hotkey functionality as
> per bug #173652.

Oh, Add the VGN-FZ11-S 8400M GT.

x

[asino89 (asino89)]

Great work!!!
But I have a stupid question...
I've tried to install nvclock on my system following the istructions described in the file s"readme" and "install" (which are the usual procedures for installing), but when i get to "make install" i have this output:
mkdir -p /usr/local/man/man1
mkdir: not able to create the directory `/usr/local/man': the file is existing
make: *** [install-man] Error 1

I know that this is just a stupid problem, but I don't know how to solve it...
Many thaks!

[ikooki (kenn-net)]

Mikes rocks! please add VNG FZ290 8400M GT to the list.

[loxan (5-launchpad-loxley-se)]

Woho! Great work guys, now it works on AR71S also! Please add it to the list of working models aswell.

[asino89 (asino89)]

I repeated the procedure described in the description of the bug. But it's stopping me with the same error that i reported before...
If i try to launch nvclock it says:
sudo: nvclock: command not found

I have a VGN NR31, so i don't understand what's the matter...
Probabily i'm ust making some errors while isntalling, but i can't understand what i didn't do correctly...

I have tried both with mikes' file that with seek's one... Both with the same results...

Help plz!

[loxan (5-launchpad-loxley-se)]

asino89: are you installing it as root ? as in "sudo make install" ? and get the build-dep for nvclock aswell.

[asino89 (asino89)]

I did just the commands described in the description. So i'm installing it as root (more precisely i'm giving the command "sudo make isntall".
I did even:
sudo apt-get build-dep nvclock
and retried.
But the error is always the same.
I don't know how to solve it...
Thanks!

[Niels Slot (nielsslot)]

Hi guys,

I've made a patch using code from Mikes and seek. My patch makes more use of code already in NVClock. It therefore works, for the user, the same as with older GeForce 7xxx cards. This means that you have to supply a percentage instead of just a value. Because of this I had to choose a 0% value. Right now it's at 256 or 0x80000100. This might be to high, feel free to change :).

You can apply the patch on a clean NVClock 0.8b3 tarball, which you can find on the NVClock homepage.

I had to add the device id of my graphics card in the soure code. If your graphics card is not recognized as a NV5X card, add your device id in the code.

[mikes (mikevas)]

Nice work man.

On Tue, Oct 21, 2008 at 10:11 PM, nielsslot <email address hidden> wrote:

> Hi guys,
>
> I've made a patch using code from Mikes and seek. My patch makes more
> use of code already in NVClock. It therefore works, for the user, the
> same as with older GeForce 7xxx cards. This means that you have to
> supply a percentage instead of just a value. Because of this I had to
> choose a 0% value. Right now it's at 256 or 0x80000100. This might be to
> high, feel free to change :).
>
> You can apply the patch on a clean NVClock 0.8b3 tarball, which you can
> find on the NVClock homepage.
>
> I had to add the device id of my graphics card in the soure code. If
> your graphics card is not recognized as a NV5X card, add your device id
> in the code.
>
> ** Attachment added: "Patch for nvclock 0.8b3 with smartdimmer support for
> GeForce 8"
> http://launchpadlibrarian.net/18778823/nvclock-8400M-smartdimmer.patch
>
> --
> No Screen Backlight Control; Sony Vaio with nvidia 8 series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "hotkey-setup" source package in Ubuntu: In Progress
> Status in "linux" source package in Ubuntu: In Progress
> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: In
> Progress
>
> Bug description:
> Using Ubuntu on Sony Vaio laptop with Nvidia 8 vga card:
>
> There is no way to control backlight brightness on Sony Vaios with 8-series
> adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!). See these hacked nvclock
> sources for fixed versions which can set backlight on Sony Vaios:
>
> http://stud.matrixcode.de/nvclock_hacked_seek.tgz
> http://launchpadlibrarian.net/18755253/nvclock_hacked.tgz
>
> To install nvclock, download one of the tgz files above (these instructions
> assume you use seek's version), then:
> ]$ tar -zxvf nvclock_hacked_seek.tgz
> ]$ cd nvclock0.8b3a
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 128
>
> So far mikes' registers have been found to work on:
> 8400M GS on VGN SZ650N
> 8400M GT on VGN FZ38M, FZ11Z, NR31, AR41E, FZ11S, FZ290
> 8600M GS on VGN FZ31Z
>
> Add your model to the list by clicking on the "Update description / tags"
> link, NOT by asking in a bug comment for someone else to do it.
>
> Invoking sonybright.sh with hotkeys will do nothing until the script calls
> new versions of either SmartDimmer or nvclock properly. I have opened bug
> #286978 against smartdimmer to encourage support for nVidia 8 series on Sony
> Vaios. Please feel free to visit that bug and click on the 'me too' link at
> the top.
>
> Dual-adapter models (SZ6 among others) can get backlight control with the
> Intel adapter using xbacklight, and can get hotkey functionality as per bug
> #173652.
>

[Sérgio Almeida (mephx-x)]

Can anyone explain me why nvclock does not work when ran
inside /etc/acpi/power.sh ? Does it run in a different environment?

This would be nice for automation until the fix is permanent...

cheers,
x

[seek (seek-matrixcode)]

seek@gcode:~$ cat /etc/default/acpi-support | grep -B2 ENABLE_LAPTOP_MODE
# Switch to laptop-mode on battery power - off by default as it causes odd
# hangs on some machines
ENABLE_LAPTOP_MODE=true

seek@gcode:~$ cat /etc/acpi/battery.d/90-brightness.sh
#! /bin/bash

/bin/nvclock -S 5

seek@gcode:~$ cat /etc/acpi/ac.d/90-brightness.sh
#! /bin/bash

/bin/nvclock -S 100

---

this scripts running, but i have following in the log
seek@gcode:~$ dmesg | tail -5
[ 369.915130] nvclock[10871]: segfault at 00000000 eip b7de3283 esp bfe2f11c error 4
[ 400.605804] nvclock[11305]: segfault at 00000000 eip b7d36283 esp bfe2410c error 4
[ 403.662667] nvclock[11365]: segfault at 00000000 eip b7df5283 esp bf8f0bdc error 4
[ 419.213568] nvclock[11905]: segfault at 00000000 eip b7d47283 esp bfed99cc error 4
[ 428.282101] nvclock[12223]: segfault at 00000000 eip b7d9c283 esp bf8d13bc error 4

why that? it is running as normal user and root

[Niels Slot (nielsslot)]

NVClock crashes in Acpi.d events because no HOME environment variable has
been set. See src/backend/config.c line 273. As a workaround I have this:

#!/bin/bash
HOME=/root nvclock -S 5

I also had to copy the ~/.nvclock directory to /root/.nvclock.

Now I've got it working perfectly. When I unplug my laptop, the brightness
goes down :).

2008/10/22 seek <email address hidden>

> seek@gcode:~$ cat /etc/default/acpi-support | grep -B2 ENABLE_LAPTOP_MODE
> # Switch to laptop-mode on battery power - off by default as it causes odd
> # hangs on some machines
> ENABLE_LAPTOP_MODE=true
>
> seek@gcode:~$ cat /etc/acpi/battery.d/90-brightness.sh
> #! /bin/bash
>
> /bin/nvclock -S 5
>
> seek@gcode:~$ cat /etc/acpi/ac.d/90-brightness.sh
> #! /bin/bash
>
> /bin/nvclock -S 100
>
> ---
>
> this scripts running, but i have following in the log
> seek@gcode:~$ dmesg | tail -5
> [ 369.915130] nvclock[10871]: segfault at 00000000 eip b7de3283 esp
> bfe2f11c error 4
> [ 400.605804] nvclock[11305]: segfault at 00000000 eip b7d36283 esp
> bfe2410c error 4
> [ 403.662667] nvclock[11365]: segfault at 00000000 eip b7df5283 esp
> bf8f0bdc error 4
> [ 419.213568] nvclock[11905]: segfault at 00000000 eip b7d47283 esp
> bfed99cc error 4
> [ 428.282101] nvclock[12223]: segfault at 00000000 eip b7d9c283 esp
> bf8d13bc error 4
>
> why that? it is running as normal user and root
>
> --
> No Screen Backlight Control; Sony Vaio with nvidia 8 series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[piike (pedrocbs)]

lol

almost a year to get my backlight control working, nice work guys. I've patched the original code from the nvclock because the nvclock-hacked worked only once, my vaio is a VGN-FZ250AE(brasilian model) with a geforce 8400M GT. I've build a deb package to help ubuntu user to test. Someone could tell me if the Sony provides help to the guys that are working on it?

PS- sorry about my english.

[Andreas Behnke (ab-andreasbehnke)]

Hey, great work from Mike!

For my Sony FZ 11 S the command
sudo nvclock -S ??
is working. Which script ( sonybright.sh?) must be adjusted to call this command?

If have not much experience with shell scripting but will try to implement this for
getting the FN Keys working.

[Niels Slot (nielsslot)]

I've already got FN keys to work. It's pretty easy. In /etc/acpi/events
there are a number of files. You can copy or change the sony brightness
files.

First change the key event. To find out which key code you need run
'acpi_listen' and press the brightness up and down keys. For me it was
'sony/hotkey SNC 00000001 00000011' and 'sony/hotkey SPIC 00000001 00000010'
(if I remember correctly..). Put these codes on the 'event=' line in the
sony-brightness-up and sony-brightness-down files.

Secondly, you need to change the commands. Since nvclock segfault if no
homedir is set, use 'HOME=/root nvclock -S +10' or 'HOME=/root nvclock -S
-10' as the 'action='.

I hope this helps, if not, please say so. I don't have my laptop with me
right now so I can't upload my configuration files. (But i'm willing to do
that later.)

2008/10/24 aprogram <email address hidden>

> Hey, great work from Mike!
>
> For my Sony FZ 11 S the command
> sudo nvclock -S ??
> is working. Which script ( sonybright.sh?) must be adjusted to call this
> command?
>
> If have not much experience with shell scripting but will try to implement
> this for
> getting the FN Keys working.
>
> --
> No Screen Backlight Control; Sony Vaio with nvidia 8 series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Michael Doube (michael-doube)]

I notified the nvclock developer (Roderick / thunderbird) of this bug report and he has replied:

"I have added some very experimental code to nvclock cvs. I don't know if it works but if you can please test it."

http://sourceforge.net/cvs/?group_id=21335

[Patrick (patrick-voegeli)]

Yeah! It works on my girlfriend laptop, thank you.

I used the patch provided by nielssot and I can do nvclock as many times as I wan't. I've also done the keys hack. After it was done, I restart acpid and it began working, great. However, when I restarted, the keys wouldn't work: gnome displays ness changes but the actual brightness won't change. If I restart acpid, it begins working again.

any thoughts?

[Michael Doube (michael-doube)]

I have an SZ6 with an Intel card as well as the nVidia one; for brightness to change on both I've done this:

# /etc/acpi/events/sony-brightness-up

event=sony/hotkey SPIC 00000001 00000011
action=/etc/acpi/sonybright.sh up; HOME=/root nvclock -S +10

----------------------------------------------------
# /etc/acpi/sonybright.sh

#!/bin/bash
if [ "x$1" = "xdown" ]; then
   xbacklight -time 100 -steps 10 -dec 10 2>/tmp/sonybright.log
elif [ "x$1" = "xup" ]; then
   xbacklight -time 100 -steps 10 -inc 10 2>/tmp/sonybright.log
else
   echo >&2 Unknown argument $1
fi

[Niels Slot (nielsslot)]

Current CVS version of NVClock works fine for me. I tested it today and gave some feedback to Roderick / Thunderbird. I would like to ask everyone here to test the CVS version. See http://sourceforge.net/cvs/?group_id=21335 for instructions on how to get it. See the description of the bug on how to compile and install it.

NVClock CVS also has an experimental Smartdimmer utility. It's a copy of the old smartdimmer utility. It work exactly the same, but it supports GeForce 8 cards. (This should fix bug #286978)

[seek (seek-matrixcode)]

Yes. I reviewed the code and tested it on my device.
Now this version should work with GeForce 8 cards.

[Michael Doube (michael-doube)]

Does anyone know how to fix the on-screen display so that it reports actual brightness instead of some made-up, wrong value when you change brightness with hotkeys? I suspect that it will require a new bug, against gnome-power-manager or HAL but I'm not sure what to aim at.

[kiloxxx (kiloxxx)]

I used the patch provided by nielsslot that allows to use a percentage instead of a numeric value and I also changed "sony-brightness-down" and "sony-brightness-up" and now when I adjust brightness via fn keys my display reports the actual brightness. I'm using kde, I don't know if it works also in gnome.

I created the two files "/etc/acpi/battery.d/90-brightness.sh" and "/etc/acpi/ac.d/90-brightness.sh" in order to use nvclock inside "/etc/acpi/power.sh", as suggested by seek, and it works too.

Like Patrick I had to restart acpid in order to have nvclock working, but when I rebooted it stopped to work till I restarted acpid again. To avoid the continuous manual restart of acpid I used this workaround:

1) I created an executable file, "acpirestart.sh", that restarts acpid when kde is loaded. I placed it in "/home/~/.kde/Autostart/" (I don't know the path to gnome autostart):

vim /home/~/.kde/Autostart/

#!/bin/sh
sudo /etc/init.d/acpid restart

2) I changed "etc/sudoers" in order to allow to my user to restart acpid without providing a password:

sudo EDITOR=vim visudo

# Cmnd alias specification
Cmnd_Alias ACPID = /etc/init.d/acpid

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
[username] ALL = NOPASSWD : ACPID

[yleetiny (yleetiny)]

Does somebody have tried to patch smartdimmer too?

I was originally working on HAL configuration to make the FN-keys & the gnome brightness applet & the on-screen display work with smartdimmer. I made a .deb for it like somebody said.

I am actually trying to use "nvclock" instead with the workaround ( sudo cp -r ~/.nvclock /root ) . It works but there is a significant cpu consumption that i didn't found in smartdimmer.

So if somebody can make something like smartdimmer or patch it for the nvidia 8 cards. It will be great.

Here is a testing package to use nvclock.

PS: you need to have the nvclock cvs version working, install the package and do :
sudo cp -r ~/.nvclock /root
sudo /etc/init.d/hal restart

[Niels Slot (nielsslot)]

yleetiny: current NVClock CVS includes a Smartdimmer utility. The code of
this utility is based on the old smartdimmer code and uses the new NVClock
backend (with Geforce 8 support).

2008/10/28 yleetiny <email address hidden>

> Does somebody have tried to patch smartdimmer too?
>
> I was originally working on HAL configuration to make the FN-keys & the
> gnome brightness applet & the on-screen display work with smartdimmer. I
> made a .deb for it like somebody said.
>
> I am actually trying to use "nvclock" instead with the workaround ( sudo
> cp -r ~/.nvclock /root ) . It works but there is a significant cpu
> consumption that i didn't found in smartdimmer.
>
> So if somebody can make something like smartdimmer or patch it for the
> nvidia 8 cards. It will be great.
>
> Here is a testing package to use nvclock.
>
> PS: you need to have the nvclock cvs version working, install the package
> and do :
> sudo cp -r ~/.nvclock /root
> sudo /etc/init.d/hal restart
>
>
> ** Attachment added: "deb file"
> http://launchpadlibrarian.net/18963808/sony-nvclock_0.3.beta.deb
>
> --
> No Screen Backlight Control; Sony Vaio with nvidia 8 series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[renato neves (trigun666)]

thanks for all :)
What do i need to do to use HAL with NVClock, and so the FN-keys & the gnome brightness applet & the on-screen display work ?
I tried the patch that alters the config files from yleetiny but doesn't work.

[Thomas Lété (bistory)]

I've quickly made a 64bits packages with checkinstall, I share it with you :)

[Sérgio Almeida (mephx-x)]

On Sunday 02 November 2008 17:59:59 bistory wrote:
> I've quickly made a 64bits packages with checkinstall, I share it with
> you :)
>
> ** Attachment added: "nvclock_0.80b3-1_amd64.deb"
> http://launchpadlibrarian.net/19240869/nvclock_0.80b3-1_amd64.deb

Can you please change the minimum to 5%? I'll have to revert to the other
version.

Cheers,
x

[Sérgio Almeida (mephx-x)]

oops, my bad. Nevermind...

[Bram (brvdpu)]

Press the following keys:

    * ctrl+alt+f1 (to get a bash session
    * Fn+f9 (to lower brightness)
    * ctrl+alt+f7 (to return to your x-session)

[Thomas Lété (bistory)]

I don't know if it relies on ACPI Daemon or other but I've a problem with Hotkeys setup...
I followed what nielsslot said, I restart acpid and mes keys work. But when I restart my computer, I must restart acpid once when I want to use my keys...

Do you have this problem too ?

[Niels Slot (nielsslot)]

I've got the same problem here.

Does anyone know if letting acpid dealing with this is the correct way?
Shouldn't HAL expose this to higher level applications, like for example
gnome's power manager or KDE4's Powerdevil?

2008/11/6 bistory <email address hidden>

> I don't know if it relies on ACPI Daemon or other but I've a problem with
> Hotkeys setup...
> I followed what nielsslot said, I restart acpid and mes keys work. But when
> I restart my computer, I must restart acpid once when I want to use my
> keys...
>
> Do you have this problem too ?
>
> --
> No Screen Backlight Control; Sony Vaio with nvidia 8 series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Zaur Nasibov (basicwolf)]

Guys, thank you very much!
Works on Sony VAIO FZ21Z NVidia 8600 GS

[renato neves (trigun666)]

hi to all , it looks that executing nvclock in "hal-system-lcd-set-brightness-linux" doesn't work, but maybe smartdimmer can!
Can someone pleassse put a .deb(i386) :P of nvlock hacked and with the smartdimmer utility ?

[ToTo (mrtoto)]

I have a Sony Vaio VGN-FZ190N with Nvidia GeForce 8400M GT
I've tried Smartdimmer but it says Smartdimmer is only supported on certain laptops using a Geforce 6200/7x00Go. If you want support on your laptop contact the author.
Is there any solution for 8400M GT ? or not yet ?

[Warren Seine (warren-seine)]

On Fri, Nov 7, 2008 at 4:31 AM, ToTo <email address hidden> wrote:
> I have a Sony Vaio VGN-FZ190N with Nvidia GeForce 8400M GT
> I've tried Smartdimmer but it says Smartdimmer is only supported on certain laptops using a Geforce 6200/7x00Go. If you want support on your laptop contact the author.
> Is there any solution for 8400M GT ? or not yet ?

Toto, are you sure you're using nvclock built from CVS? I had this
problem with the v3 of the .deb (while the v3a1 works immediately).
--
Warren Seine

[Shawe Ewahs (shawe-ewahs)]

http://launchpadlibrarian.net/19240869/nvclock_0.80b3-1_amd64.deb

Works perfectly in a FZ38M with:

sudo nvclock -S +10
sudo nvclock -S -10

How can I add with Fn+F5 and FN+F6 this keys works, but they don't apply the changes. With console command it works.

[benste (benste)]

same problem like I had :-)

look into :
https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589

at the end of the page there is a deb file which applys changes to gnome-power for using smartdimmer / nvclock :-)

[ToTo (mrtoto)]

Dudeeeeeeeeeee thank you !!!!!!!!!!!!
That was the problemmmmmmmmmm !!!! now it works !!!
I couldn't make function keys work so far! I followed the instructions and made all changes to sony-brightness-up and down, but still doesn't work !
anyway I'm so happy that I can change brightness from now on ! :D
doesn't matter how :D

[Michael Doube (michael-doube)]

Backlight setting is not restored when resuming from suspend to RAM. It's a minor point I know, though is not an issue on the other (Intel) card on this laptop.

[ToTo (mrtoto)]

I confirm that it works on Sony VAIO FZ-190N NVidia Geforce 8400M GT

[Kasper Meerts (kasperm-deactivatedaccount)]

It works for me on a Sony VAIO FZ31E with a NVidia GeForce 8400M GT.

Thanks a bunch.
I presume this will make it really quick in the Ubuntu repositories? It's a pretty bad bug.

[Shawe Ewahs (shawe-ewahs)]

I say it also on: https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589/comments/30

If anyone can say me what files are needed for adjust the brightness with the fn-keys, I think that I know how correct it.

I was watching the files and do this:

In /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi
    And I add my model

In /usr/lib/hal/scripts/hal-system-lcd-get-brightness-linux
    I change vaio-nvidia for this, smartdimmer don't work with sony-nvidia:
    elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
            # smartdimmer -g
            # value=$(( `smartdimmer -g | awk '{print $3;}'` -1 ))
            value=$((`sudo nvclock -i | awk '/Backlight/ {print $3;}' | tr -d '%'` -10))

/usr/lib/hal/scripts/hal-system-lcd-set-brightness-linux
    I change vaio-nvidia for this, smartdimmer don't work with sony-nvidia:
    elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
            # smartdimmer -s 21
            # smartdimmer -s "$(( $value + 1 ))"
            # value=$((`sudo nvclock -i | awk '/Backlight/ {print $3;}' | tr -d '%'`))
            nvclock -S "$((value + 10))"

What file need to edit also? I don't found the file for increase the blacklight :S

[renato neves (trigun666)]

Shawe Ewahs

I think the files set and get that we need to change are in this directory.

/usr/lib/hal/scripts/linux

tell me if it works

Cheers

[Shawe Ewahs (shawe-ewahs)]

renato neves: I do this, but I also need edit any thing more, but I don't found it.

[renato neves (trigun666)]

Then i don't know either. If you find tell me because i have the same problem

[Shawe Ewahs (shawe-ewahs)]

On /usr/lib/hal/scripts/linux/hal-system-lcd-get-brightness-linux

change the original elif for this:

elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
        # smartdimmer -g
        # value=$(( `smartdimmer -g | awk '{print $3;}'` -2 ))
        value=$(( `nvclock -S +0 | grep level: | awk '{print $4;}' | sed -e 's:%::'` / 5 -3 ))

On nano /usr/lib/hal/scripts/linux/hal-system-lcd-set-brightness-linux

change the original elif for this:

elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
        # smartdimmer -s 21
        #smartdimmer -s "$(( $value + 2 ))"
        nvclock -S "$(( $value * 5 + 15 ))"

On /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi
add your model, like this:
        <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" string="VGN-FZ38M">
          <merge key="laptop_panel.num_levels" type="int">20</merge>
          <merge key="laptop_panel.access_method" type="string">sony-nvidia</merge>
        </match>

I think that it works better with this sentences, but also didn't work correctly. I go to restart for tryit again with this config.

[Shawe Ewahs (shawe-ewahs)]

More information:

/etc/acpi/events/sony-brightness-down

With this:

# /etc/acpi/events/sony-brightness-down
event=sony/hotkey SNC 00000001 00000010
action=/etc/acpi/sonybright.sh down

/etc/acpi/events/sony-brightness-up

With this:

# /etc/acpi/events/sony-brightness-up
event=sony/hotkey SNC 00000001 00000011
action=/etc/acpi/sonybright.sh up

/etc/acpi/sonybright.sh

With this:

#!/bin/bash
if [ "x$1" = "xdown" ]; then
# xbacklight -time 100 -steps 10 -dec 10 2>/tmp/sonybright.log
        nvclock -S -10
elif [ "x$1" = "xup" ]; then
# xbacklight -time 100 -steps 10 -inc 10 2>/tmp/sonybright.log
        nvclock -S +10
else
   echo >&2 Unknown argument $1
fi

sudo /etc/init.d/acpid restart
sudo /etc/init.d/hal restart

And Fn+F5 and Fn+F6 works, only fail that don't show the correct % in graph.
I think that graphical % fails because:
/usr/lib/hal/scripts/linux/hal-system-lcd-set-brightness-linux
and
/usr/lib/hal/scripts/linux/hal-system-lcd-get-brightness-linux
aren't working correctly. Only this fault.

[Shawe Ewahs (shawe-ewahs)]

I don't know why, but acpid need restarted every time that I power on the laptop, if I don't do that, the brightness don't work :S

I'm trying and I see that Ubuntu don't use:
/usr/lib/hal/scripts/linux/hal-system-lcd-set-brightness-linux
and
/usr/lib/hal/scripts/linux/hal-system-lcd-get-brightness-linux
For nothing in sony-nvidia
Only use:
/etc/acpi/events/sony-brightness-down
/etc/acpi/events/sony-brightness-up
That are the only files that apply changes to brightness.

If any one know why, please tell me why ubuntu don't use this /usr/lib/hal/scripts/linux/hal-system-lcd-*-brightness-linux with vaio-nvidia config.

And one more thing, in my comment https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/106 I correct one thing:

change:

elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
        # smartdimmer -g
        # value=$(( `smartdimmer -g | awk '{print $3;}'` -2 ))
        value=$(( `nvclock -S +0 | grep level: | awk '{print $4;}' | sed -e 's:%::'` / 5 -3 ))

to

elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
        # smartdimmer -g
        # value=$(( `smartdimmer -g | awk '{print $3;}'` -2 ))
        value=$(( `nvclock -S +0 | grep level: | awk '{print $4;}' | sed -e 's:%::'` / 5 - 2 ))

Brightness change 2 to 2 from scale max 20 (100/5), and decrease a real 10% to this way. With value 3, increase a 15%. I don't know how is the default in it, but value 2 .
NVClock accept minimum brightness to 15%, in decreasing 10% you can decrease up to 20%, in 15% decreasing you can decrease up to 25%. Anyway for also solve this little feature? Or aren't interesting change it?

[Shawe Ewahs (shawe-ewahs)]

Now all work :D :

In:
/usr/lib/hal/scripts/linux/hal-system-lcd-get-brightness-linux

elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
        # smartdimmer -g
        # value=$(( `smartdimmer -g | awk '{print $3;}'` -2 ))
        value=$((`/usr/local/bin/nvclock -S +0 | grep level: | awk '{print $4;}' | sed -e 's:%::'` / 5 - 2 ))

I don't know why, but nvclock is not loaded from here path, putting here absolute path, it work well.

and I do the same for /usr/lib/hal/scripts/linux/hal-system-lcd-set-brightness-linux, it seems that not have this problem, but I change it also:

elif [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "sony-nvidia" ]; then
        # smartdimmer -s 21
        # smartdimmer -s "$(( $value + 2 ))"
        /usr/local/bin/nvclock -S "$(( $value * 5 + 10 ))"

[Shawe Ewahs (shawe-ewahs)]

I can confirm that now, works wells, also after reboot the system, including the progress bar that appears when press Fn keys. Anyone can try it?

Can anyone explain me how to do a deb package for these files for have an easy installation? I can add all Vaio's specified in the description for the deb file.

[yleetiny (yleetiny)]

I have modified my small package to use the full path....but it will break the compatibility with the other models.
( /usr/bin/nvclock ) . I also remove the nvclock package dependency your nvclock version is not linked to the package.
NB: I also use the "HOME=/root" environement before it... since i read that it is a way to make nvclock work in a script.

In my package i don't use the vaio model... but the pci id of the main graphic card. I tend to think it is a better way since some model have 2 graphics cards. Even if the "match" file it is quite long...

You can just extract the package to see the different files...

[Shawe Ewahs (shawe-ewahs)]

Decompress the file and then run "sudo install-sony-nvidia.sh" it will be save your original files, and copy the configured files, also download a copy of NVClock from CVS and compile and install it automatically.

Try and share your opinion please for report to Ubuntu.

[axx (axx)]

Shawe, thanks for your nice work.
Unfortunately the tarball you attached is mostly empty, save for the script itself.
The etc/ and usr/ folders in the archive are empty, so it fails.

Looking forward to trying again!

Using FZ31M / 8400M GT on ubuntu 8.10

[axx (axx)]

Oh, and for people having problems trying to get nvclock to install, you need the following:
automake and xorg-server-dev, both are available in the repositories.

The nvclock command works on the Vaio FZ-31M with a 8400M GT.

Thanks everyone, especially mikes! Am looking forward for the rest of the integration via Shawe's script :)

[Shawe Ewahs (shawe-ewahs)]

Try it here:
http://shawe.ewahs.googlepages.com/install-FnKeys-sony-nvidia.sh

[renato neves (trigun666)]

great work :D
too bad that brigthness, once changed, can't pass the 30%.Maybe the conversion of brightness isn't perfect.

[Shawe Ewahs (shawe-ewahs)]

renato neves is my first time that I try to help to correct a problem. I don't know how it works and I'm trying from ignorance :P.
My script works for you? In my laptop yesterday work well (also after reboot), but now it doesn't work :S

Anyone can do a .deb file with my little changes for people can try it?

[renato neves (trigun666)]

For the first time is pretty good :)....it works but only with that little problem of conversion.
I also have a nvidia 8400m gt

[Shawe Ewahs (shawe-ewahs)]

renato neves, can you explain more detailed what is your "little problem of conversion"? For my it hasn't any little problem :S if you can explain to me what happened, I can try to correct it again :P.

[Shawe Ewahs (shawe-ewahs)]

Partial corrected, try apply this: https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/115

[renato neves (trigun666)]

When i dim the brightness it goes from 100% to 20% , then if i increase it goes from 20% to 30%, after that brightness can't be changed anymore.

This is the conversion :

in set brightness : "$(( $value * 5 + 15 ))"

in get brightness : value=$(( ${value//%/ } /5 -3 ))

i changed it into this : "$(( $value * 33 ))"

and this : value=$(( ${value//%/ } / 33 ))

It's not better but i prefer it. :P

[Kasper Meerts (kasperm-deactivatedaccount)]

I have the same problem. The brightness doesn't go over 30%.

[Shawe Ewahs (shawe-ewahs)]

On /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi, there are a number, for Vaio is 20, with my conversion $value/5 value is 100, 100/5=20, also the number for the conversion must be modified.

        <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" string="VGN-FZ38M">
          <merge key="laptop_panel.num_levels" type="int">20</merge>
          <merge key="laptop_panel.access_method" type="string">sony-nvidia</merge>
        </match>

If you change:
in set brightness : "$(( $value * 5 + 15 ))"
in get brightness : value=$(( ${value//%/ } /5 -3 ))
to
in set brightness : "$(( $value * 5 + 10 ))"
in get brightness : value=$(( ${value//%/ } / 5 - 2 ))
You also can go over to 20% and, brightness increase/decrease 10%

Value is original brightness, it you /5 you pass 100% to 20, if you do -2, you are decreasing -10% in real scale. Because the nvclock are limited to 15%, we only can decrease up to 20% with this.

If you see all my comments, you can read that I change it in my most newests comments for this reason :P

For the moment, my laptop, renato reves laptop and Kasper Meerts laptop, are working "correctly". We only need found a better formulation for change the brightness.

[acid-r4in (rpeternella)]

See if this works with you (it's ok with my FZ340E/B):

- install nvclock and insert the /local/usr/bin (or the path where nvclock was installed) in the $PATH variable at /etc/profile
- chmod 777 nvclock so it can be executed as normal user
- Map the fn+f5 and fn+f6 keys (brightness up and down) with xev. This way you can actually know the keycode for them. In my case they are 101 and 212.
- install xbindkeys package.
- create a file in your home directory name .xbindkeyrc
- add the following lines to .xbindkeysrc:

#adjust the brightness up -> keep the double quotes as they are part of the script
"nvclock -S +10%"
  c:101

#adjust the brightness down -> keep the double quotes as they are part of the script
"nvclock -S -10%"
  c:212

- make sure following command runs every time you start X (via startx, or kdm, whatever):
  xbindkeys -f ~/.xbindkeysrc

- give it a try :)

hope this works, it's perfect here, but the only problem is that there is no visual feedback indicating the current level. Altough, it's a minor problem in my opinion.

[Shawe Ewahs (shawe-ewahs)]

acid-r4in thanks for your comment, we are trying to found the solution for also integrate with Ubuntu control events, the visual feedback that you say. Are you try my "solution"?

Please, if your laptop work, add it to the initial list. In description you can read:

"Add your model to the list by clicking on the "Update description / tags" link, NOT by asking in a bug comment for someone else to do it."

[acid-r4in (rpeternella)]

Shawe,

Already added it up there :)
I will try installing Ubuntu 8.10 someday when I have time, so I can test it :)
Right now I'm under Archlinux, and most of the files and places listed there don't even exist in my system.

[Schmirrwurst (schmirrwurst)]

I've tested your solution ewah, nvclock works (I had already added my laptop in the description), but I can't bring the fn keys to work !
I've also tried to add my PC in the fdi policy file, without effet !

[Shawe Ewahs (shawe-ewahs)]

<email address hidden> when I try it, it works only after reboot the system (not only restarting acpid), I don't know why, but actually it doesn't work and I don't what are occurred for this strange change.

Anybody now to who we can send this information for solve more fast this problem with the actually information? To hal project?

[axx (axx)]

I may be wrong, but I have the feeling that the newest Nvidia drivers (177.80, which is only the latest ubuntu packaged version in fact) may have changed something and made your modifications ineffective. The fn+F5-6 don't work anymore, I have to enter the nvclock commands manually. (which is still usable of course)

The fn shortcuts now segfault, as seen in dmesg output:
nvclock[5526]: segfault at 0 ip b7dde2c3 sp bf9f4cfc error 4 in libc-2.8.90.so[b7d67000+158000]

The only other segfault I could find via google with error 4 in libc-2.8.90.so was also an nvidia driver bug report, so that's that.

I'll try removing your mods to see if it changes anything Shawe.

Also, it would be good if we could have someone in charge, be it of Nvidia integration or of acpi, to give us some heads up as to what to do to get this bugfix working and taken in consideration (and pardon my lack of knowledge concerning linux bug squishing).

[Shawe Ewahs (shawe-ewahs)]

Anyone can try the new version of my script? (Is the same link, but code is diferent than my other comment)

http://shawe.ewahs.googlepages.com/install-FnKeys-sony-nvidia.sh

Actually it use smartdimmer, it is included in cvs repository from nvclock, and use this for correct work (no more nvclock for change brightness). Try and report it please, thanks.

Now it work correctly and without problems for my, from 15% up to 100%.

[Michael Doube (michael-doube)]

Shawe, your script doesn't work here: Hardy on an SZ650N. I had to chmod +x /etc/acpi/events/sonybright.sh to make that script executable. My keys are recognised and logged by acpid.

[Shawe Ewahs (shawe-ewahs)]

Michael Double, I only tested on Intrepid. Also, my script must put the correct permitions to respective files, don't do it?

[axx (axx)]

Hey I tried the new script.
It's a lot better, not perfect, but much much better, so thanks a lot for your work!

Here are the problems:
– changing the brightness is not super responsive, totally usable, but not as quick as your previous version
– the visual feedback doesn't quite work… it doesn't update quite right
– gnome power manager doesn't seem to be aware of the brightness capability as the screen does not dim when the AC adapter is unplugged.

Other than that, as far as I can tell, it's great, so thanks again Shawe! :)

[Shawe Ewahs (shawe-ewahs)]

axx:

- smartimmer and nvclock have a little pause for apply the new brightness (also manually), is normal that it don't do it fast. Previous version also have this inconvenient.
- Visual feedback work well for up and down, not fast, but work correctly.
- Gnome Power Manager, can control brightness when plug or unplug the AC Adapter.

You can see the points 2 and 3 with this video (poor quality, but you can see that all work):

http://www.youtube.com/watch?v=XWKoPfH6WtA

axx what Vaio do you have? I'm testing it with Sony Vaio FZ38M but I don't think that this solution is only applicable to me.

[marcomerucci (marco-merucci)]

Hello all.
I've a VGN-fz18m with 8400M GT card. I've tried to follow your advice but i haven't benn able to solve the problem.
It is possible to resume the several solution until now?
I'de be very glade to use the brightness, is one year that i've the notebook without this regulation... I was hoping in intrepid... but nothing done.

[Jordi2019 (jordi2019)]

Hi Everyone,

I've got a VGN-NR21S Sony Vaio. I've installed the package: “nvclock_0.80b3-1_amd64.deb” and it works fine. If I want to change the brightness level I can only do it using the console. Also I've installed “install-FnKeys-sony-nvidia.sh” but, unfortunately this doesn't work at all. Before install it I was able to see the progress bar, but without any result. If I can help for example testing new packages, I'll be glad!

[yleetiny (yleetiny)]

@Everybody
Hum why nobody is trying my package for the FN-keys?
You can find it in the description.
It should work after a reboot.
I admit that the "install-FnKeys-sony-nvidia" also install FN-keys through acpi. Mine only use, HAL.
Maybe i will try to make a package for the whole thing.
But since my package does not rely on the vaio model but instead on the video card itself + manufacturer = sony, it should be great if people try it, and give us feedbacks.

@Shawe Ewahs
Could you recompile the .deb file to install nvclock in "/usr/bin" instead of "/usr/local/bin" for amd64 and 32bits, please?
This thing should make "nvclock" cvs compatible with the actual ubuntu install.
So there will be a common "hal-sony-nvclock.deb" to correct FN-keys for all nvclock users.

[Shawe Ewahs (shawe-ewahs)]

@yleetiny: For me works better my partial solution. that yours.
I don't do any .deb file, in my script it compile it from cvs, in here normal way. I think that it can be possible give a destination location in ./configure command for do that.
Please, can you put in a comment all links that you say that works better please? I try it all in this bug and they don't work for me, I think that I do anything different than you.

[Schmirrwurst (schmirrwurst)]

I have partially solved my problem with fn keys, with shawe's install script, in fact there are working, but only after a restart from the acpid daemon. So after each startup I have to restart the acpid...
Any Idea why ?
Dec 10 10:20:23 briza acpid: client connected from 7198[108:115]
Dec 10 10:23:32 briza acpid: client has disconnected
Dec 10 10:29:57 briza kernel: [ 0.000000] ACPI: If "acpi_apic_instance=2" works better, notify <email address hidden>
Dec 10 10:29:57 briza kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Dec 10 10:29:57 briza kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Dec 10 10:29:57 briza kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Dec 10 10:29:57 briza kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Dec 10 10:29:57 briza kernel: [ 12.814635] acpi device:09: registered as cooling_device2
Dec 10 10:29:59 briza acpid: client connected from 4888[108:115]
Dec 10 10:30:01 briza acpid: client connected from 5053[0:0]
Dec 10 10:35:03 briza acpid: client has disconnected
Dec 10 12:53:02 briza kernel: [ 0.000000] ACPI: If "acpi_apic_instance=2" works better, notify <email address hidden>
Dec 10 12:53:02 briza kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Dec 10 12:53:02 briza kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Dec 10 12:53:02 briza kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Dec 10 12:53:02 briza kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Dec 10 12:53:02 briza kernel: [ 10.662121] acpi device:09: registered as cooling_device2
Dec 10 12:53:04 briza acpid: client connected from 4872[108:115]

[Schmirrwurst (schmirrwurst)]

I've installed kubuntu by a friend on a fz31z and also shiwas script, fn keys are working (no need to restart acpid), but kde power manager is not working (it is on my fz21e)...
I've found no configuration file for kde guidance power manager... ?!

[yleetiny (yleetiny)]

To Shawe Ewahs :
Hum, how can I say it?
Your script is a great workaround, it compiles cvs, etc.. etc.. and it is really great.
But I tend to think that we need to go on the next step : DEB packages.

Why?
Simply because it is easier for people to install, it is somehow cleaner. The other reason is that the small tweaks for HAL will never be taken in the main stream since it depends on a program ( "nvclock" or "smartdimmer") whereas it should be simple "echo"s .
So I think in the current situation, the best thing would be a ppa where you can find the differents packages :
 1- nvclock, cvs version for geforce8 users ( with the correct paths, because it is needed for "2**" )
 2**- hal-sony-nvclock, to get brightness support through HAL, it will give you the small OSD when you change brightness, the applet compatibility too, in short it will give GNOME or KDE or whatsoever the capability to dimm your brightness. Which will work for Geforce 6,7 and 8
 3- acpi-sony-nvclock, to give acpi the possibility to dimm the brightness. Those things should go to the main stream.

Why did I say mine is better for the HAL part?
The only issue that there is in your hal configuration is that is not "out of the box" since you need to give your model. I actually made the script you use for HAL(I can recognise my comments) for geforce6 and 7 users using smartdimmer, and the first reaction was : it does'nt work, since their model wasn't listed. So I developped another approach which is to identify that the manufacturer is "Sony" and that your main card is a listed nvidia geforce 6,7 or 8. This approach will avoid two cases : the unlisted vaio model and the fact that if you use 2 graphic cards, it won't try to dimm something not active as your main card.
The thing now, is that I do not have 2 graphics card on my laptop and my package haven't been tested enough to be sure that everything works flawless. That's why I asked people to try my package.

In short, Workarounds are great but being able to find a durable solution is even better.

[Shawe Ewahs (shawe-ewahs)]

To yleetiny:
- I don't know how do a DEB packages with it, I don't found info explainning how to do it.
- I know that HAL tweak is better with HAL info from graphic card, but also I don't know how to do it, for this reason I use model laptop. If you do it, try to remake my script using your tweaks. I also think the same as you, but I can't do nothing because I don't know it.
- It's better solution identify the graphic card (only put in the list the 8 series), not manufacturer or model.

If you know how to do it, try it to implemment it and do a little script like mine for easy install for others users (I know that isn't the better way for test it, but is the easy way available for us). When we found a really solution, the admin for this bug can try to implement a finnally .deb for add it to Ubuntu repos.

If you want, we can try to work together with this problem. Now, I don't know how to more things because I don't know how HAL info work. Please, try to do a complete script with your actual solution, and I try it, and can see what do yoy do in it.

[Warren Seine (warren-seine)]

May I remind you that this is not a feature, but a *bug*. So this
shouldn't be in an archive or a shell script, this should just be
fixed within the packages that are affected (whether it's nvclock or
an ubuntu core package).

Tell me if I'm wrong, but there is neither new feature nor new program
attached to this bug. So why do you want to make a package? The
current .deb that can be found in the topic are just here to allow
experimented users to test the fixes. Hope the bug will be fixed in
the default Jaunty distribution without having to "aptitude install"
anything.
--
Warren Seine

[Shawe Ewahs (shawe-ewahs)]

SooW, is really, isn't needed like a feature, but is needed for get full support for this graphic card. Also isn't a bug, only has partial support for it with nvclock and hal.
The DEB packages is needed, not for nvclock, nvclock from CVS has "good" support for it, but HAL hasn't know what it mas do with this graphic card, for this we want do a deb file for add support for it.
The .deb file that you say, is nvclock only, it doesn't do work FN Keys, only give you support for brightness. I don't want to wait for Jaunty, I want use it now because, now it works, and I thing that other people think the same.

[darylb (darylblanc)]

Perhaps the proper way to get the hal changes in is by submitting a patch to the hal and hal-info packages, or indeed upstream. The hal-info package is definitely where the /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi file lives, I'm not sure about the other ones in the package. I don't think a new separate package is the best answer.

[yleetiny (yleetiny)]

I agree that submitting patches are the best way to solve a bug, and I was my goal when I try to dig into the issue.
But in our case, I don't really think that is a bug of nvclock nor HAL, but more likely an experimental support.

I made the idea of packages since the issue is long well known but do not have an easy solution. Indeed, the solutions proposed cannot be made into patches of the main packages. The long term solution is in fact a patch of sony-laptop module, but it is unlikely that this module will be updated soon since there is a lack of data and it is now shipped within the default kernel.

== Nvclock ==
It is a developpement version, so it cannot go into the proposed packages. But we can make an experimental package of nvclock cvs since it introduce an experimental support of geforce 8

== hal-info, nvclock==
I cannot propose a patch since it will add a depedency on hal-info to nvclock. When I analysed the traditionnal way to dim backlight, I saw that they are just echo to a device (linked to a proper module). That is why I propose an extra package.
There should not need to make different packages for geforce6,7 or 8 users, if nvclock-cvs-experimental is correctly packaged.

@Shawe Ewahs
To detect the card, I use pci-ids, but I also need to check that the manufacturer is sony. Why?
If geforce6 and 7 for laptop are called Geforce Go series and I can found their pci-ids, for Geforce8, I do not know what exact model are laptop graphics card with dimming functionabilities. So I listed all the Geforce8 cards + sony = sony laptop that have a geforce8 series card. I attached the fdi file which is in : "/usr/share/hal/fdi/information/10freedesktop".
I think that I can remove the "sony" manufacturer match if I know all the geforce8 models for laptop.
NB : I am also a begginer in packaging files. My package is just a package which will copy some files and execute some scripts. I read some documents to make them but they are in French, but you should be able to find some documents over the internet.

== acpi ==
This one, can be considered as a real bug which can be solved by a patch, but I don't know if today is a correct configuration file for all sony-vaio users.

[huiii (a00ps)]

@all,

first thanks for putting so much energy into this,
i got a sony VAIO fz31m with brightness working now on ubuntu intrepid.
I recently wrote such an "how-to" here:
http://ubuntuforums.org/showthread.php?p=6325299#post6325299
but just today i found this bug report with other solutions by coincidence...

i have a request though:
the procedure displayed here is quite confusing,
after reading the whole page, i do not know for sure what i should do and why i am doing it?!

so i think it would be a very good idea to put this down on a "how-to".
would somebody be willing to help me implement the solutions from here into that "how-to"?

thx again

[huiii (a00ps)]

ok, nevertheless i tried the script of Shawe Ewahs and the one of yleetiny on a VAIO FZ31M.
unfortunately i do not know exactly what both solutions where supposed to do, but apart from the weird effect i got now when changing brightness with the FN-keys, the gnome-osd will not go over the middel, instead stucks there shivering, nothing else did work:
no gnome-power-manager-support
no dim when switching to battery...

in that case i would recommend everyone who got the same result to follow this how-to here:
http://ubuntuforums.org/showthread.php?p=6325299#post6325299
it works

[Shawe Ewahs (shawe-ewahs)]

huiii thanks for this link, for me work exactly than with this tutorial link. All do exactly the same, except CPU than now go to 100% when I press the FN-Keys, and brightness changes 15% to 15%, I suposed because is using 2 configuracion, mine (5%) and your link (10%). No more speed for change it, and nothing new for me :P

Maybe you need to do "cp -R $HOME/.nvclock /root" for use correctly my script, I don't know why but nvclock needed itself in /root folder.

A question, it's possible than smartdimer/nvclock increase the live of battery?? Now it only work for 15min without AC Adapter. And after that I test any "partial solution" it works for 1h30. :S

[Thunderbird (thunderbird-linuxhardware)]

Hi,

Since a lot of users are asking me about backlight control in NVClock I decided to post here myself. Since the discovery of the register on a Sony laptop I have added support for various other laptops from different vendors. Next to Sony models the code appears to work on a HP/Compaq 8510W, Samsung Q210/Q310/R600 and a Zepto 9600M laptop. The HP and Zepto model use MXM ('mobile pci-express card which can be replaced') which could mean that more MXM boards use this register.

I plan to release a new version of NVClock soon. What sort of issues are you guys still seeing? I'll see if I can do something about flckering (caused by bios dumping) and the need for a home directory. The bios info is needed in a lot of cases for instance for proper temperature reading and other features but I'll see what I can do about it. Most likely I will try to read the bios from a copy inside videoram instead of the rom when it is in videoram.

What other issues are you guys seeing?

Thanks,
Thunderbird

[Jordi2019 (jordi2019)]

@Shawe

Before executing your script I was able to see the brightness progress bar, but without any result. Now I can’t see it and the brightness also continues without work. My laptop is vgn-nr21S. If you need further information about my bug, please contact with me. I’ll be glad to help you.

[Shawe Ewahs (shawe-ewahs)]

@Jordi2019 my script give you any error in the process? Is probably that give you any error on cvs or make.

[Jordi2019 (jordi2019)]

@Shawe

You had reason, I have some errors:

checking for gtk+-2.0 >= 2.4.0... checking for x11... configure: error: "X11 required for nvcontrol support"

make: *** No targets specified and no makefile found. Stop.

make: *** No rule to make target `install'. Stop.

cp: cannot stat `smartdimmer': No such file or directory

Copying /etc/acpi/sonybright.sh

--2008-12-30 20:55:47-- http://shawe.ewahs.googlepages.com/sonybright.sh

Resolving shawe.ewahs.googlepages.com... 74.125.47.118

Connecting to shawe.ewahs.googlepages.com|74.125.47.118|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 244 [application/octet-stream]

Saving to: `sonybright.sh.1'

Thanks,

[BoZ (ba-serge)]

For those who is interested in setting Fn keys with acpid.

As it has been already mentioned above in this thread, if you simply write
   nvclock -S -5
in your sonybright.sh it won't work unless you restart the daemon after login. Of course you can do this restart automatically on every startup. But to my opinion this does not smell to be the right way.

The actual problem is a weird user rights and home directory settings, since acpid runs as root. So to overcome that I propose just to put something like
    sudo -H -u YOURUSERNAME /usr/local/bin/nvclock -S -5
here after -u you put your user name (it is of course possible to find out that name in script. But if you are the only one it is obviously not worth spending time on that). -H option sets environment HOME to that of the target user.

It works for me. And there is no need to restart acpid...

[Thunderbird (thunderbird-linuxhardware)]

I made changes to nvclock recently which make a HOME directory unneeded I think. Those changes were made for this purpose. Could you check if a recent cvs copy works?

Roderick

[Thunderbird (thunderbird-linuxhardware)]

NVClock 0.8 (beta4) is now online.

[Shawe Ewahs (shawe-ewahs)]

Thunderbird, this beta version solve the problems from this bug #95444?

[Thunderbird (thunderbird-linuxhardware)]

The new beta contains backlight control for all the laptops which where mentioned in this thread. If nvclock 0.8b4 would be added to the new ubuntu it would solve this bug.

[Schmirrwurst (schmirrwurst)]

My fn keys are still working only on acpid restart after reboot, can so help me to solve that problem ?
Is it really necessary to make acpid restart at kde startup, it sound strange ? why do acpid need restart ?

I've also seen there is a version 177.82 from the driver on nvidia, supposing resolving some bug, does so already test it ?

[blks303 (blks303)]

Installing the new nvclock 0.8b4 and editing

1) /etc/acpi/events/sony-brightness-down

event=sony/hotkey SNC 00000001 00000010
action=/usr/local/bin/nvclock -S -10

2)/etc/acpi/events/sony-brightness-up

event=sony/hotkey SNC 00000001 00000011
action=/usr/local/bin/nvclock -S +10

made the fn keys working on my FZ18M.
P.S. I also installed the last available nvidia drivers 177.82 but I don't now if that affects the result.

Thanks a lot guys!! perfect work!!

[Shawe Ewahs (shawe-ewahs)]

For people who tested my script, I found a BIG error, for this reason, it don't work (the script are correct, but not the permissions assigned :P).

http://shawe.ewahs.googlepages.com/install-FnKeys-sony-nvidia.sh

I change only lines with chmod, I see that I don't give to files permission for execute :P, only read and write, for this reason it don't show and don't do it anything.

If anyone want to try it now, you're comments are welcoming.

I found this error reinstalling Ubuntu, and when I try it I see that people are saying me, do absolutely nothing. I think that know is correctly solved and ¿without more errors?

I think that only need a more clean way for recognize laptops with graphical cards affected, better than specify laptop to laptop in /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fd file (my actually way), but at least now works. Anyone knows how to do better implementation for this recognition?

[Jordi2019 (jordi2019)]

@Shawe

Since you modified your script I can use my FN keys to up/down the brightness.

Just a comment: Before installing your script I was able to see my brightness bar without any result. After executing it I can’t see the bar, but it really works now!

Thank you so much!

[Shawe Ewahs (shawe-ewahs)]

@Jordi2019

What laptop are you using? Maybe can be that my script hasn't your laptop in the list of supported models, but nvclock also works. That can be your problem.

Can you re-execute my script and sendme to my mail all code that it generate in a console?
My mail is shawe(dot)ewahs(at)gmail(dot).com , if I see what is wrong in your execution I can try to correct it. I do a little changes for my Ubuntu installation base system and don't have more problems, but is possible that I install manually any dependency that I don't added to the script.

Thanks for try it!

[Bem Jones-Bey (ajani)]

First off thanks to everyone contributing to this bug, I've found the information very helpful, especially to Shawe since without those scripts, I wouldn't even have had the foggiest idea how to get the hotkeys working. =]

My laptop is a HP 8510w, so Shawe's scripts don't work out of the box for me. I ended up adding my model to the FDI file, and things pretty much work. In the process, I also made the HAL scripts less Sony specific.

I've packaged up my modified files here: http://testing.pyen.com/~ajani/nvidia8-fnkeys.tar.bz2

Shawe, I'm especially interested in what you think of my changes, and if other could tell me if this works for them, that would be great, too.

I do have one question: I didn't make any changes to the acpid scripts; my model uses /etc/acpi/video_brightness{down,up}.sh. Do those only need to be changed so that the brightness keys will work when not in Gnome?

Here's a list of the changes that I've made:

* replaced 'sony' with nvidia8, to make it more obvious that it's not sony specific
* changed the access method name to nvidia8 because it now supports non-sony models
* moved the check for the nvidia8 laptop panel access method to the top of the hal get and set scripts so that the check fot /sys/class/backlight doesn't have to be commented out. This should make it easier to incorporate these changes into the hal packages.
* install script:
  - changed script to use dpkg-divert to make backups of replaced files so that upgrades of the packages for those files won't break the setup
  - removed 'make install' step, since it isn't needed
  - changed chmods on scripts to be 755, so that other and group get executable bit
  - change chmod on the fdi to be 644, since it doesn't need to be executable
  - added a 'sudo' in front of every command that needs root priviledges so that I can run the script as my normal user
  - All of the files except nvclock source are included in the tarball, so it doesn't download anything except nvclock
* Added an uninstall script

[Shawe Ewahs (shawe-ewahs)]

Don't work for my, seems that it is a recursively tar file: http://testing.pyen.com/~ajani/nvidia8-fnkeys.tar.bz2
Can you redo it again?

* replaced 'sony' with nvidia8, to make it more obvious that it's not sony specific
* changed the access method name to nvidia8 because it now supports non-sony models
I propose this in a comment on this thread, but I don't know how to solve it, very good work :D

* moved the check for the nvidia8 laptop panel access method to the top of the hal get and set scripts so that the check fot /sys/class/backlight doesn't have to be commented out. This should make it easier to incorporate these changes into the hal packages.
I don't understand well what it do.

* install script:
  - changed script to use dpkg-divert to make backups of replaced files so that upgrades of the packages for those files won't break the setup
  - removed 'make install' step, since it isn't needed
  - changed chmods on scripts to be 755, so that other and group get executable bit
  - change chmod on the fdi to be 644, since it doesn't need to be executable
Little important changes, i've a big error with this that don't show the progressbar, that I see that it is problem with permitions :D

  - added a 'sudo' in front of every command that needs root priviledges so that I can run the script as my normal user
Is it based on my script? I can't try your.
  - All of the files except nvclock source are included in the tarball, so it doesn't download anything except nvclock
I put separate files from my initial script for have the possibility for update any separate file without change the result of initial script.
* Added an uninstall script
Interesting for undo any changes without good results :D

Only with all I read that you do, I think that you do a big important change from try to solve this bug, the second most important from nvclock support correctly 8series.
I think that it only need better recognition on .fdi, only compare the series from nvidia graphic card, it's the important think, not the model of laptop that we now that are using it.

[Shawe Ewahs (shawe-ewahs)]

I send a petition to hal lists for help to try recognize only the graphic cards that are affected, not the laptop that include this graphic cards on .fdi file.

Anyone have more ideas for try to solve this "bug"?

[Bem Jones-Bey (ajani)]

@Shawe

All of the scripts in my tarball are based on yours. I'm not sure why you have trouble opening it, I can open it fine with tar on the command line and with Archive Manager. I did remake it and reuploaded it, just in case. I've also made just a tar: http://testing.pyen.com/~ajani/nvidia8-fnkeys.tar, since it doesn't really need to be zipped. Do one of those work for you?

You know, having the fdi do the recognition on the card type is a really good idea, and since I'm rather new to this whole HAL thing, I didn't realize that it would be possible to do that. If I manage to figure out how to do that, I'll post here, but hopefully the HAL folks will be able to say immediately what needs to be done to do it that way.

[Thunderbird (thunderbird-linuxhardware)]

I have no good method of detecting which cards are supported. Right now the detection mechanism is a crappy whitelist for some vendors and it doesn't mean all models of a vendor are supported. The best way is to make a list of pci device ids in combination with the vendor id of a board.

This information can be obtained in different ways. In case of nvclock 0.8b4 run nvclock -D:
NV_PBUS_PCI_0 (0x1800): 014f10de
NV_PBUS_PCI_0 (0x182c): 00000000

Here 0x014f is the pci device id (geforce 6200 in this case) and the pci subvendor id is 0 (to be exact the pci subvendor id is 16-bit and it at pci header offset 0x2c).

Another way is using lspci -x:
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6200] (rev a2)
00: de 10 4f 01 07 00 10 00 a2 00 00 03 00 00 00 00
10: 00 00 00 d4 0c 00 00 c8 00 00 00 00 04 00 00 da
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 05 01 00 00

In this case byte 3 and 4 contain the device id. Just reading 3 (0x4f) and 4 (0x01) might make you think the device id is 0x4f01 but it is little endian, so they need to be swapped to become '0x14f'. At 0x2c and 0x2d you would see the subvendor but in my case it is 0.

Because my subvendor is 0, here another example:
02:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
00: ec 10 69 81 17 00 b0 02 10 00 00 02 10 20 00 00
10: 01 de 00 00 00 f0 ef df 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 14 0a 24
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 20 40

At 0x2c and 0x2d you see 0x7b and 0x14, the subvendor id is 0x147b which means Abit (the vendor of my motherboard).

[Shawe Ewahs (shawe-ewahs)]

Bem, Is possible that the problem is "WinRAR", when I read your message I'm using Windows :P With the new file, I can see it.

Thunderbird, I propose to hal project that help us to do a detection of this 3 graphic cards, for change the "whitelist" with the correct 3 detected grapich cards affected, but I thing that I don't speak very well english for that they understand me :P Can you try explain to hal lists?

[Shawe Ewahs (shawe-ewahs)]

Bem, I'm watching your changes and I want to know want thing: "nvidia8" detection on your files, works also with "nvidia9" and "quadro" series? It's also important for try to generalise the solution.

Or we need to add also similar to this?

if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia8" ]; then
    value=$((`smartdimmer -g | awk '{print $3;}'`))
    value=$((($value /5)-1))
    exit ${value}
fi

if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia9" ]; then
    value=$((`smartdimmer -g | awk '{print $3;}'`))
    value=$((($value /5)-1))
    exit ${value}
fi

if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "quadro" ]; then
    value=$((`smartdimmer -g | awk '{print $3;}'`))
    value=$((($value /5)-1))
    exit ${value}
fi

I don't know if it is correct, but also similar to this must be added for a generalised solution.

And for .fdi file, I think that we need change:

<match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" string="MODEL_NAME">

for anything similar to:

    <match key=”pci.vendor_id” int=”0×8086″> <!– Intel Corporation –>
      <match key=”pci.product_id” int=”0×3582″> <!– 82852/855GM Integrated Graphics Device –>
        <match key=”pci.subsys_vendor_id” int=”0×1179″> <!– Toshiba America Info Systems –>
          <match key=”pci.subsys_product_id” int=”0×2″> <!– Unknown (0×0002) –>

I found it on: http://blogs.gnome.org/hughsie/2006/06/

In Device Manager, it must have any key that help to us to detect this information, no?

[Thunderbird (thunderbird-linuxhardware)]

You could rely on nvclock/smartdimmer for detecting the capability but
I would also like a list of supported cards. It just doesn't mean that
when a laptop uses lets say a geforce8 that it uses nvclock's
smartdimmer will work, nor does it mean that all laptops from sony
work. For that reason I want to have a list. Perhaps there is some
pattern in it or so. In the end I might find a better way based on
e.g. the video bios.

Further why re you dividing the value by 5? All users should update to
the smartdimmer version shipped with nvclock 0.8b4. It only supports
values between 0 and 100%. The old geforce6/7 smartdimmer used values
between 0 and 20 or whatever and those directly mapped to gpu
registers. On modern cards the value can be between 0 and a few
thousand.

Roderick

Quoting Shawe Ewahs <email address hidden>:

> Bem, I'm watching your changes and I want to know want thing: "nvidia8"
> detection on your files, works also with "nvidia9" and "quadro" series?
> It's also important for try to generalise the solution.
>
> Or we need to add also similar to this?
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia8" ]; then
> value=$((`smartdimmer -g | awk '{print $3;}'`))
> value=$((($value /5)-1))
> exit ${value}
> fi
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia9" ]; then
> value=$((`smartdimmer -g | awk '{print $3;}'`))
> value=$((($value /5)-1))
> exit ${value}
> fi
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "quadro" ]; then
> value=$((`smartdimmer -g | awk '{print $3;}'`))
> value=$((($value /5)-1))
> exit ${value}
> fi
>
> I don't know if it is correct, but also similar to this must be added
> for a generalised solution.
>
>
> And for .fdi file, I think that we need change:
>
> <match
> key="/org/freedesktop/Hal/devices/computer:system.hardware.product"
> string="MODEL_NAME">
>
> for anything similar to:
>
> <match key=”pci.vendor_id” int=”0×8086″> <!– Intel Corporation –>
> <match key=”pci.product_id” int=”0×3582″> <!– 82852/855GM
> Integrated Graphics Device –>
> <match key=”pci.subsys_vendor_id” int=”0×1179″> <!– Toshiba
> America Info Systems –>
> <match key=”pci.subsys_product_id” int=”0×2″> <!– Unknown
> (0×0002) –>
>
> I found it on: http://blogs.gnome.org/hughsie/2006/06/
>
> In Device Manager, it must have any key that help to us to detect this
> information, no?
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no w...

[Shawe Ewahs (shawe-ewahs)]

Thunderbird, this value divided by 5 is for show the progressbar with the brightness. This progressbar works with value specified on list of laptops on /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi file, if you watch on it, you can see the reason, smartdimmer works with 100 value, this progressbar works in 20 value, here differences is 5 times. This "value=$((($value /5)-1))" is only a convertion for show the progressbar decreasing depending of the value of the brightness.

If you decrease 1 point of brightness with FN keys, you are using it, doing this: (100/5)-1= 19, 19*5=95, you are changing brightness to 95% and progressbar give value 19 from total of 20, for show you the progressbar with new nevel of brightness corresponding to it.

You understand it better now?

I don't understand for what reason you say that you preferred a whitelist of laptops, I think that people in HAL project, can help us for only detect the graphics cards affected more easily and more tiny and efficiently.

You say:

"It just doesn't mean that when a laptop uses lets say a geforce8 that it uses nvclock's smartdimmer will work, nor does it mean that all laptops from sony work."

Of course, only laptopts with GeForce8/GeForce9/Quadro are affected with this problem (all? I don't know, but I think yes for this moment), not depending with here manufacturer. Only depend of if the laptop have a graphic card from this series.

"For that reason I want to have a list. Perhaps there is some pattern in it or so. In the end I might find a better way based on e.g. the video bios."

Is probably, that not alls are correctly detected with this method, but I thing that the whitelist can decrease more trying to reduce to graphical card detected, and adding support for laptops that don't work with this method.
Reducing to a list that have this characteristics:
- It use nvidia8,nvidia9 or quadro for nvclock
- It's a laptop with graphic card manufactured by "nVidia Corporation", (implemente with this or video bios, ... I don't know the better way for this, but this is the important)
For this moment, we now that it's really, you can confirm with the list on the description. That confirm that don't need a whitelist with ALL laptops with this graphic cards.

[Thunderbird (thunderbird-linuxhardware)]

> Is probably, that not alls are correctly detected with this method,
> but I thing that the whitelist can decrease more trying to reduce to
> graphical card detected, and adding support for laptops that don't
> work with this method.
> Reducing to a list that have this characteristics:
> - It use nvidia8,nvidia9 or quadro for nvclock
> - It's a laptop with graphic card manufactured by "nVidia
> Corporation", (implemente with this or video bios, ... I don't know
> the better way for this, but this is the important)
> For this moment, we now that it's really, you can confirm with the
> list on the description. That confirm that don't need a whitelist
> with ALL laptops with this graphic cards.
>

Only a small fraction of the nvidia based laptops works using this
method. I think that less than 50% of the laptops use this method
likely even less lets say 25% or so. For instance no Dell, Lenovo and
Acer laptops have been reported to use this method. Further the HP
models which use it upto now are some business orientated models and I
doubt the the normal consumer line uses this method. On a lot of
nvidia laptops the buttons actually work fine by default. For that
reason I want a whitelist for or else a good detection method. I might
have found something in the video bios but I don't have time to
implement all the code for it. What I saw in the nouveau bios code is
that the lvds table contains some pwm fields which are likely meant
for smartdimmer.

Roderick

[Shawe Ewahs (shawe-ewahs)]

Thunderbird, my laptop need a driver distributed by Sony, not for nVidia, is possible that others laptops affecteds have the same "problem"? nVidia don't give drivers for Vaio directly, it website say to you that you need to download the driver for Sony Vaio website.
It's possible that manufacturer change a little part from the original hardware and driver.

I don't knew this that you explain to me, I think that all laptops with this 3 graphic cards are affected.

[Bem Jones-Bey (ajani)]

On 01/25/2009 05:13 AM, Shawe Ewahs wrote:
> Bem, I'm watching your changes and I want to know want thing: "nvidia8"
> detection on your files, works also with "nvidia9" and "quadro" series?
> It's also important for try to generalise the solution.
>
I just chose nvidia8 as a generic name for all cards that are affected
by this regardless if they are 8, 9, or quadro. It seemed to me that
since the solution was the same for all of them, we might as well have
one name. (Also, realize that Quadro is the name of an entire product
line, like GeForce, and thus just "Quadro" wouldn't be sufficient) If
you can come up with a better name, I'm perfectly fine with that.
> Or we need to add also similar to this?
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia8" ]; then
> value=$((`smartdimmer -g | awk '{print $3;}'`))
> value=$((($value /5)-1))
> exit ${value}
> fi
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia9" ]; then
> value=$((`smartdimmer -g | awk '{print $3;}'`))
> value=$((($value /5)-1))
> exit ${value}
> fi
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "quadro" ]; then
> value=$((`smartdimmer -g | awk '{print $3;}'`))
> value=$((($value /5)-1))
> exit ${value}
> fi
>
> I don't know if it is correct, but also similar to this must be added
> for a generalised solution.
>
If we do have different names that do the same thing, I'd suggest using
a shell case statement, like so:

case $HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD in
nvidia8|nvidia9|quadro)
     value=$((`smartdimmer -g | awk '{print $3;}'`))
     value=$((($value /5)-1))
     exit ${value}
esac
> And for .fdi file, I think that we need change:
>
> <match
> key="/org/freedesktop/Hal/devices/computer:system.hardware.product"
> string="MODEL_NAME">
>
> for anything similar to:
>
> <match key=”pci.vendor_id” int=”0×8086″> <!– Intel Corporation –>
> <match key=”pci.product_id” int=”0×3582″> <!– 82852/855GM Integrated Graphics Device –>
> <match key=”pci.subsys_vendor_id” int=”0×1179″> <!– Toshiba America Info Systems –>
> <match key=”pci.subsys_product_id” int=”0×2″> <!– Unknown (0×0002) –>
>
> I found it on: http://blogs.gnome.org/hughsie/2006/06/
>
> In Device Manager, it must have any key that help to us to detect this
> information, no?
>
If I do the following on my laptop, I can dump all of the useful
information about my graphics card. Perhaps it would be useful to
collect this information from everyone that is affected by this so that
we can see what commonalities that we see. We may find that there are
only a couple of pci product ids that are affected, and that would be an
easy to maintain list.

[hup:Desktop]% hal-find-by-property --key info.linux.driver --string
'nvidia'
/org/freedesktop/Hal/devices/pci_10de_40c
[hup:Desktop]% hal-device /org/freedesktop/Hal/devices/pci_10de_40c
udi = '/org/freedesktop/Hal/devices/pci_10de_40c'
   pci.device_protocol = 0 (0x0) (int)
   info.linux.driver = 'nvidia' (string)
   pci.vendor = 'nVidia Corporation' (string)
   linux.sysfs_path =
'/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0' (string)
   info.vendor = 'nVidia Corporat...

[Shawe Ewahs (shawe-ewahs)]

Yes, any information from hal-device can be the solution for detect the products affects. This is mine:

$ hal-find-by-property --key info.linux.driver --string 'nvidia'
/org/freedesktop/Hal/devices/pci_10de_426
shawe@Vaio:~$ hal-device /org/freedesktop/Hal/devices/pci_10de_426
udi = '/org/freedesktop/Hal/devices/pci_10de_426'
  pci.device_protocol = 0 (0x0) (int)
  info.linux.driver = 'nvidia' (string)
  pci.vendor = 'nVidia Corporation' (string)
  linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0' (string)
  info.vendor = 'nVidia Corporation' (string)
  info.subsystem = 'pci' (string)
  info.parent = '/org/freedesktop/Hal/devices/pci_8086_2a01' (string)
  pci.product = 'G86M [GeForce 8400M GT]' (string)
  info.product = 'G86M [GeForce 8400M GT]' (string)
  pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0' (string)
  pci.subsys_vendor = 'Sony Corporation' (string)
  info.udi = '/org/freedesktop/Hal/devices/pci_10de_426' (string)
  pci.product_id = 1062 (0x426) (int)
  linux.hotplug_type = 2 (0x2) (int)
  pci.vendor_id = 4318 (0x10de) (int)
  linux.subsystem = 'pci' (string)
  pci.subsys_product_id = 36869 (0x9005) (int)
  pci.subsys_vendor_id = 4173 (0x104d) (int)
  pci.device_class = 3 (0x3) (int)
  pci.device_subclass = 0 (0x0) (int)

Yes, maybe is posible collecting this information, I don't know how hal works, for this reason I only propose ideas.

I say to you if nvidia8, nvidia9 and quadro are different, because I don't know if nvidia8 works for the three. If you say that yes, no problem.

[Thunderbird (thunderbird-linuxhardware)]

Geforce8/9/quadro cards are the same. Further the thing you just
showed is a basic pci id check. For that again a list of capable cards
is needed. For the record there are dozens of different mobile
geforce8/9/quadro cards.

Roderick

Quoting Shawe Ewahs <email address hidden>:

> Yes, any information from hal-device can be the solution for detect the
> products affects. This is mine:
>
> $ hal-find-by-property --key info.linux.driver --string 'nvidia'
> /org/freedesktop/Hal/devices/pci_10de_426
> shawe@Vaio:~$ hal-device /org/freedesktop/Hal/devices/pci_10de_426
> udi = '/org/freedesktop/Hal/devices/pci_10de_426'
> pci.device_protocol = 0 (0x0) (int)
> info.linux.driver = 'nvidia' (string)
> pci.vendor = 'nVidia Corporation' (string)
> linux.sysfs_path =
> '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0' (string)
> info.vendor = 'nVidia Corporation' (string)
> info.subsystem = 'pci' (string)
> info.parent = '/org/freedesktop/Hal/devices/pci_8086_2a01' (string)
> pci.product = 'G86M [GeForce 8400M GT]' (string)
> info.product = 'G86M [GeForce 8400M GT]' (string)
> pci.linux.sysfs_path =
> '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0' (string)
> pci.subsys_vendor = 'Sony Corporation' (string)
> info.udi = '/org/freedesktop/Hal/devices/pci_10de_426' (string)
> pci.product_id = 1062 (0x426) (int)
> linux.hotplug_type = 2 (0x2) (int)
> pci.vendor_id = 4318 (0x10de) (int)
> linux.subsystem = 'pci' (string)
> pci.subsys_product_id = 36869 (0x9005) (int)
> pci.subsys_vendor_id = 4173 (0x104d) (int)
> pci.device_class = 3 (0x3) (int)
> pci.device_subclass = 0 (0x0) (int)
>
> Yes, maybe is posible collecting this information, I don't know how hal
> works, for this reason I only propose ideas.
>
> I say to you if nvidia8, nvidia9 and quadro are different, because I
> don't know if nvidia8 works for the three. If you say that yes, no
> problem.
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:ano...

[Bem Jones-Bey (ajani)]

On 01/26/2009 12:24 AM, Thunderbird wrote:
> Geforce8/9/quadro cards are the same. Further the thing you just
> showed is a basic pci id check. For that again a list of capable cards
> is needed. For the record there are dozens of different mobile
> geforce8/9/quadro cards.
>
So are you saying that you think making a list of the pci ids of all of
the cards isn't a good idea? Were you suggesting earlier that instead of
making a list, we attempt to discover if there is some way we can probe
the card and find out if it needs to be supported by nvclock instead of
through the standard kernel interfaces? (If so, do you have a way we
could do that? I'm not much of a hardware hacker, I'm afraid.)

--
Bem Jones-Bey (<email address hidden>)

[getaceres (getaceres)]

What about older Geforce cards (6 and 7)?. They also are controlled by smartdimmer, so once the patch has been applied to HAL, these cards have to be included in the list as well.

[Thunderbird (thunderbird-linuxhardware)]

For geforce6/7 cards the detection in nvclock is quite good and it can
be relied on.

Quoting getaceres <email address hidden>:

> What about older Geforce cards (6 and 7)?. They also are controlled by
> smartdimmer, so once the patch has been applied to HAL, these cards have
> to be included in the list as well.
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E,
> FZ21M, FZ21S, FZ470E, FZ340E, FZ190N, FZ18M, FZ31E, FZ18E, FZ260E
> NR21Z, NR38S, NR21S
>
> 8600M GS:
> VGN FZ31Z, FZ21Z, FZ31S
>
> 8600M GT:
> VGN AR51SU, AR71S
> }
>
> Zepto laptops
> {
> Geforce 9600GT based laptops using MXM cards
> }
>
> Add your model to the list by clicking on the "Update description /
> tags" link, NOT by asking in a bug comment for someone else to do it.
>
> To get hotkeys to work, follow the instructions in this comment:
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/75
> or install the package at :
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/111
>
> Dual-adapter models (SZ6 among others) can get backlight control
> with the Intel adapter using xbacklight, and can get hotkey
> functionality as per bug #173652.
>

[Thunderbird (thunderbird-linuxhardware)]

We explicitly need a list right now of the device id of the card and
the subvendor id. Further some studying of the gpu bios needs to be
done for geforce8/9 models which are supported by nvclock and types
which aren't. I need several bioses of both models for that. Though I
can't say when I have time to analyze them.

Quoting Bem Jones-Bey <email address hidden>:

> On 01/26/2009 12:24 AM, Thunderbird wrote:
>> Geforce8/9/quadro cards are the same. Further the thing you just
>> showed is a basic pci id check. For that again a list of capable cards
>> is needed. For the record there are dozens of different mobile
>> geforce8/9/quadro cards.
>>
> So are you saying that you think making a list of the pci ids of all of
> the cards isn't a good idea? Were you suggesting earlier that instead of
> making a list, we attempt to discover if there is some way we can probe
> the card and find out if it needs to be supported by nvclock instead of
> through the standard kernel interfaces? (If so, do you have a way we
> could do that? I'm not much of a hardware hacker, I'm afraid.)
>
> --
> Bem Jones-Bey (<email address hidden>)
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E,
> FZ21M, FZ21S, FZ470E, FZ340...

[Shawe Ewahs (shawe-ewahs)]

Thunderbird is possible do a little script that generate a .txt file with the info that you think that can be useful? This can be a easy way for people report this to here.

If you can explain more accurately what we can do for do your idea, I must to try do it in my free time, and more people can contribute to do a solution that work for all, if we know how can do for it.

Example list:

Product: pci.product = 'G86M [GeForce 8400M GT]' (string)
Info Product: info.product = 'G86M [GeForce 8400M GT]' (string)
Device ID: info.udi = '/org/freedesktop/Hal/devices/pci_10de_426' (string)
Device ID: pci.product_id = 1062 (0x426) (int)
Vendor ID: pci.vendor_id = 4318 (0x10de) (int)
Subsys ID: pci.subsys_product_id = 36869 (0x9005) (int)
Subsys Vendor ID: pci.subsys_vendor_id = 4173 (0x104d) (int)

Can be sufficient with this? If yes, I can do a little script that extract this info (more or less also).

[Thunderbird (thunderbird-linuxhardware)]

Only the following three lines are needed:
> Device ID: pci.product_id = 1062 (0x426) (int) => Geforce 8400M
> Vendor ID: pci.vendor_id = 4318 (0x10de) (int) => Nvidia
> Subsys Vendor ID: pci.subsys_vendor_id = 4173 (0x104d) (int) => Sony

Quoting Shawe Ewahs <email address hidden>:

> Thunderbird is possible do a little script that generate a .txt file
> with the info that you think that can be useful? This can be a easy way
> for people report this to here.
>
> If you can explain more accurately what we can do for do your idea, I
> must to try do it in my free time, and more people can contribute to do
> a solution that work for all, if we know how can do for it.
>
> Example list:
>
> Product: pci.product = 'G86M [GeForce 8400M GT]' (string)
> Info Product: info.product = 'G86M [GeForce 8400M GT]' (string)
> Device ID: info.udi =
> '/org/freedesktop/Hal/devices/pci_10de_426' (string)
> Device ID: pci.product_id = 1062 (0x426) (int)
> Vendor ID: pci.vendor_id = 4318 (0x10de) (int)
> Subsys ID: pci.subsys_product_id = 36869 (0x9005) (int)
> Subsys Vendor ID: pci.subsys_vendor_id = 4173 (0x104d) (int)
>
> Can be sufficient with this? If yes, I can do a little script that
> extract this info (more or less also).
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> So...

[Thunderbird (thunderbird-linuxhardware)]

Further I'd like some additional info. Could you some people try to
run nvclock -D BEFORE the nvidia kernel module and X are loaded, so
directly after logging into a VT? I'm interested in the line which
contains 'NV_PDISPLAY_SOR0_REGS_BRIGHTNESS'. If it contains the proper
value then it means the video bios is setting some interesting values
from the video bios. Second I like a few copies of video bios from
cards which work using nvclock's smartdimmer and from ones which
aren't supported. The video bios is dumped by nvclock into ~/.nvclock.

[Bem Jones-Bey (ajani)]

On 01/26/2009 11:45 AM, Thunderbird wrote:
> Only the following three lines are needed:
>
>> Device ID: pci.product_id = 1062 (0x426) (int) => Geforce 8400M
>> Vendor ID: pci.vendor_id = 4318 (0x10de) (int) => Nvidia
>> Subsys Vendor ID: pci.subsys_vendor_id = 4173 (0x104d) (int) => Sony
>>
Ok, I've thrown together a quick script to dump this info as well as the
text versions of the product and vendor:
[hup:acpi]% ./dump_info.sh
== Properties for /org/freedesktop/Hal/devices/pci_10de_40c ==
   pci.vendor = 'nVidia Corporation' (string)
   pci.product = 'Quadro FX 570M' (string)
   pci.product_id = 1036 (0x40c) (int)
   pci.vendor_id = 4318 (0x10de) (int)
   pci.subsys_vendor_id = 4156 (0x103c) (int)

People can grab it from:
http://testing.pyen.com/~ajani/dump_info.sh

I've also made it an attachment to this email, we'll see if Launchpad
does the right thing with it.

Thunderbird, I'll look into getting you that other info later when I can
reboot.

[Shawe Ewahs (shawe-ewahs)]

A little script like this, can extrat the first info that you say me.

mkdir nvidia-info
cd nvidia-info
hal-device $(hal-find-by-property --key info.linux.driver --string 'nvidia')
| grep pci.product >> nvidia-info.txt
hal-device $(hal-find-by-property --key info.linux.driver --string 'nvidia')
| grep pci.vendor_id >> nvidia-info.txt
hal-device $(hal-find-by-property --key info.linux.driver --string 'nvidia')
| grep pci.subsys_vendor_id >> nvidia-info.txt
cp $HOME/.nvclock/bios*.rom .
cd ..
zip nvidia-info.zip nvidia-info

The second info I don't know where I can found it and how consult it
correctly, any idea?

By §h@wæ
http://www.islatux.es

2009/1/26 Thunderbird <email address hidden>

> Further I'd like some additional info. Could you some people try to
> run nvclock -D BEFORE the nvidia kernel module and X are loaded, so
> directly after logging into a VT? I'm interested in the line which
> contains 'NV_PDISPLAY_SOR0_REGS_BRIGHTNESS'. If it contains the proper
> value then it means the video bios is setting some interesting values
> from the video bios. Second I like a few copies of video bios from
> cards which work using nvclock's smartdimmer and from ones which
> aren't supported. The video bios is dumped by nvclock into ~/.nvclock.
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung,
> Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Bem Jones-Bey (ajani)]

On 01/26/2009 12:09 PM, Thunderbird wrote:
> Further I'd like some additional info. Could you some people try to
> run nvclock -D BEFORE the nvidia kernel module and X are loaded, so
> directly after logging into a VT? I'm interested in the line which
> contains 'NV_PDISPLAY_SOR0_REGS_BRIGHTNESS'. If it contains the proper
> value then it means the video bios is setting some interesting values
> from the video bios. Second I like a few copies of video bios from
> cards which work using nvclock's smartdimmer and from ones which
> aren't supported. The video bios is dumped by nvclock into ~/.nvclock.
>
I've attached the entire output of nvclock -D (in single user mode) on
my HP 8510w, as well as the bios dump. I've also put them up here:
http://testing.pyen.com/~ajani/nvidia/

[Shawe Ewahs (shawe-ewahs)]

Thunderbird can you try if this collect information that you want?

#/bin/bash
mkdir nvidia-info
cd nvidia-info
hal-device $(hal-find-by-property --key info.linux.driver --string 'nvidia')
| grep pci.product >> nvidia-info.txt
hal-device $(hal-find-by-property --key info.linux.driver --string 'nvidia')
| grep pci.vendor_id >> nvidia-info.txt
hal-device $(hal-find-by-property --key info.linux.driver --string 'nvidia')
| grep pci.subsys_vendor_id >> nvidia-info.txt
nvclock -D | grep NV_PDISPLAY_SOR0_REGS_BRIGHTNESS >> nvidia-info.txt
cp $HOME/.nvclock/bios*.rom .
cd ..
zip nvidia-info.zip nvidia-info

But I think that can be better collect to this way:

#/bin/bash
mkdir nvidia-info
cd nvidia-info
hal-device $(hal-find-by-property --key info.linux.driver --string 'nvidia')
>> nvidia-info.txt
nvclock -D >> nvidia-info.txt
cp $HOME/.nvclock/bios*.rom .
cd ..
zip nvidia-info.zip nvidia-info

If people report here information, is better that send all related
information, I know that exist a command line to compare and extract the
most repeated lines and in this case, can be an automated way for found the
coincidences of the different graphics cards affected.

By §h@wæ
http://www.islatux.es

[Shawe Ewahs (shawe-ewahs)]

If we decided for only one script, we can "automatize" the detection of coincident key in more files.

[Bem Jones-Bey (ajani)]

Just to be sure, you guys did run that script in singe user mode, right
(boot in "recovery mode", then choose root shell)? Thunderbird asked for
the nvclock -D to be run before X is started. (All of the other dumps
can be gotten normally, but the nvclock -D is special)

[Peter_h (forum-horners)]

Sony Vaio FZ11S Nvidia 8400M GT

[Thunderbird (thunderbird-linuxhardware)]

I think this log is made using 0.8b3 and not using 0.8b4 as the
brightness register is missing.

Quoting Peter_h <email address hidden>:

> Sony Vaio FZ11S Nvidia 8400M GT
>
> ** Attachment added: "NV 8400M GT FZ11S"
> http://launchpadlibrarian.net/21685357/nvidia-info.zip
>
> --

[Peter_h (forum-horners)]

root@peter-laptop:/home/peter/install/Nvidia/nvclock0.8b4# nvclock
NVClock v0.8 (Beta4)

Using NVClock you can overclock your Nvidia videocard under Linux and FreeBSD.
Use this program at your own risk, because it can damage your system!

Usage: ./nvclock [options]

Overclock options:
   -b --backend backend Backend to use: coolbits/coolbits2d/coolbits3d/lowlevel (NV3X/NV4X/NV5X only)
   -m --memclk speed Memory clock in MHz
...

I tray ist again - but beta4 ist installed?!

[loxan (5-launchpad-loxley-se)]

Ok, latest nvclock binary and output both before X and after X has started.

[Thunderbird (thunderbird-linuxhardware)]

What might be useful is the following on a fresh boot of your system
without using the nvidia driver and also without a framebuffer driver
(a framebuffer driver could prevent an image restore).

Download vbtracetool (git clone
git://anongit.freedesktop.org/~stuart/vbtracetool/), compile it and
then it like mentioned in the QUICKSTART file bundled with it. It will
take 30-60s and then bzip2 the resulting file. The file contains the
boot log of your video bios and might show me where the info I need in
the bios is located.

[Bem Jones-Bey (ajani)]

On 01/28/2009 11:29 AM, Thunderbird wrote:
> What might be useful is the following on a fresh boot of your system
> without using the nvidia driver and also without a framebuffer driver
> (a framebuffer driver could prevent an image restore).
>
>
Does Ubuntu have a kernel that doesn't have a framebuffer driver, or
would I have to compile my own? (Or does it not load the framebuffer
driver when I boot single user?) And I guess the other option would be
to boot with one of the minimal Linux distros.

[Thunderbird (thunderbird-linuxhardware)]

You can also use a framebuffer driver (vesafb) but then the display
might not get restored and then you would need to guess when to
reboot. I would wait lets say 2 minutes when doing it this method and
then reboot (just by typing it into another VT)

Quoting Bem Jones-Bey <email address hidden>:

> On 01/28/2009 11:29 AM, Thunderbird wrote:
>> What might be useful is the following on a fresh boot of your system
>> without using the nvidia driver and also without a framebuffer driver
>> (a framebuffer driver could prevent an image restore).
>>
>>
> Does Ubuntu have a kernel that doesn't have a framebuffer driver, or
> would I have to compile my own? (Or does it not load the framebuffer
> driver when I boot single user?) And I guess the other option would be
> to boot with one of the minimal Linux distros.
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E,
> FZ21M, FZ21S, FZ470E, FZ340E, FZ190N, FZ18M, FZ31E, FZ18E, FZ260E
> NR21Z, NR38S, NR21S
>
> 8600M GS:
> VGN FZ31Z, FZ21Z, FZ31S
>
> 8600M GT:
> VGN AR51SU, AR71S
> }
>
> Zepto laptops
> {
> Geforce 9600GT based laptops using MXM cards
> }
>
> Add your model to the list by clicking on the "Update description /
> tags" link, NOT by as...

[Schmirrwurst (schmirrwurst)]

I've asked the package maintainer if so can package nvclock0.8b4, it seems that there is a working package at http://www.kanotix.com/files/thorhammer/updates/nvclock/ , it is a 386 version, I have not tested yet if it works on amd64

[Bem Jones-Bey (ajani)]

Ok, to make sure I fully understand: the only reason the framebuffer
driver might cause a problem is because after the app is run, the
display might be broken: the data that comes out would still be fine. I
thought you were saying that the tool wouldn't give good data if the
framebuffer driver existed in the kernel. So in this case, booting
single user should be just fine.

Thanks for the clarification. I'll run the vbtracetool as soon as I get
a chance.

On 01/28/2009 12:08 PM, Thunderbird wrote:
> You can also use a framebuffer driver (vesafb) but then the display
> might not get restored and then you would need to guess when to
> reboot. I would wait lets say 2 minutes when doing it this method and
> then reboot (just by typing it into another VT)
>
> Quoting Bem Jones-Bey<email address hidden>:
>
>
>> On 01/28/2009 11:29 AM, Thunderbird wrote:
>>
>>> What might be useful is the following on a fresh boot of your system
>>> without using the nvidia driver and also without a framebuffer driver
>>> (a framebuffer driver could prevent an image restore).
>>>
>>>
>>>
>> Does Ubuntu have a kernel that doesn't have a framebuffer driver, or
>> would I have to compile my own? (Or does it not load the framebuffer
>> driver when I boot single user?) And I guess the other option would be
>> to boot with one of the minimal Linux distros.
>>
>> --
>> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
>> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
>> graphics
>> https://bugs.launchpad.net/bugs/95444
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in Hardware Abstraction Layer (HAL): Invalid
>> Status in “hal” source package in Ubuntu: New
>> Status in “hotkey-setup” source package in Ubuntu: In Progress
>> Status in “linux” source package in Ubuntu: In Progress
>> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>>
>> Bug description:
>> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>>
>> On various laptops from Sony, HP, Samsung and others there is no way
>> to control backlight brightness. In case of Sony e.g. on Vaios with
>> 8-series adapters, e.g.
>> nVidia Corporation GeForce 8400M GS
>> nVidia Corporation GeForce 8600M GT (rev a1)
>>
>> The registers have been found (kudos to mikes!) and incorporated into
>> nvclock, which you can check out by anonymous cvs and install:
>>
>> ]$ sudo apt-get install cvs
>> ]$ cvs
>> -d:pserver:<email address hidden>:/cvsroot/nvclock
>> login
>> ]$ cvs -z3
>> -d:pserver:<email address hidden>:/cvsroot/nvclock co
>> -P nvclock
>> ]$ cd nvclock
>> ]$ ./autogen.sh
>> ]$ ./configure
>> ]$ make
>> ]$ sudo make install
>>
>> To test, make sure you are using nVidia's proprietary driver, then:
>> ]$ sudo nvclock -S 100
>> ]$ sudo nvclock -S 15
>> ]$ sudo nvclock -S +10
>>
>> So far mikes' registers have been found to work on:
>>
>> Apple laptops
>> {
>> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
>> }
>>
>> HP/Compaq laptops
>> {
>> 8510W (Quadro FX 570M, MXM)
>> 8710P (Quadro NVS 320M, MXM)
>> }
>>
>> Samsung laptops:
>> {...

[Shawe Ewahs (shawe-ewahs)]

Is normal a logfile with 4,2GB? I test this tool and generate for me a log
toooooo big, using nvidia driver in this moment, and yes, closing de output
image, also SSH or RemoteDesktop don't work in this moment.

I must to try it yesterday in rescue-mode.

By §h@wæ
http://www.islatux.es

2009/1/28 Bem Jones-Bey <email address hidden>

> Ok, to make sure I fully understand: the only reason the framebuffer
> driver might cause a problem is because after the app is run, the
> display might be broken: the data that comes out would still be fine. I
> thought you were saying that the tool wouldn't give good data if the
> framebuffer driver existed in the kernel. So in this case, booting
> single user should be just fine.
>
> Thanks for the clarification. I'll run the vbtracetool as soon as I get
> a chance.
>
> On 01/28/2009 12:08 PM, Thunderbird wrote:
> > You can also use a framebuffer driver (vesafb) but then the display
> > might not get restored and then you would need to guess when to
> > reboot. I would wait lets say 2 minutes when doing it this method and
> > then reboot (just by typing it into another VT)
> >
> > Quoting Bem Jones-Bey<email address hidden>:
> >
> >
> >> On 01/28/2009 11:29 AM, Thunderbird wrote:
> >>
> >>> What might be useful is the following on a fresh boot of your system
> >>> without using the nvidia driver and also without a framebuffer driver
> >>> (a framebuffer driver could prevent an image restore).
> >>>
> >>>
> >>>
> >> Does Ubuntu have a kernel that doesn't have a framebuffer driver, or
> >> would I have to compile my own? (Or does it not load the framebuffer
> >> driver when I boot single user?) And I guess the other option would be
> >> to boot with one of the minimal Linux distros.
> >>
> >> --
> >> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> >> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> >> graphics
> >> https://bugs.launchpad.net/bugs/95444
> >> You received this bug notification because you are a direct subscriber
> >> of the bug.
> >>
> >> Status in Hardware Abstraction Layer (HAL): Invalid
> >> Status in "hal" source package in Ubuntu: New
> >> Status in "hotkey-setup" source package in Ubuntu: In Progress
> >> Status in "linux" source package in Ubuntu: In Progress
> >> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: In
> Progress
> >>
> >> Bug description:
> >> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
> >>
> >> On various laptops from Sony, HP, Samsung and others there is no way
> >> to control backlight brightness. In case of Sony e.g. on Vaios with
> >> 8-series adapters, e.g.
> >> nVidia Corporation GeForce 8400M GS
> >> nVidia Corporation GeForce 8600M GT (rev a1)
> >>
> >> The registers have been found (kudos to mikes!) and incorporated into
> >> nvclock, which you can check out by anonymous cvs and install:
> >>
> >> ]$ sudo apt-get install cvs
> >> ]$ cvs
> >> -d:pserver:<email address hidden>:/cvsroot/nvclock
> >> login
> >> ]$ cvs -z3
> >> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> >> -P nvclock
> >> ]$ cd nvclock
> >> ]$ ./autogen.sh
> >> ]$ ./configur...

[Schmirrwurst (schmirrwurst)]

I've tried to package the latest beta release from nvclock, that include the modifications we needed for our card, try to test it, it could be a better alternative as cvs install...
I don't know if I manage to meet the requierements to upload it in the official repositories..., for now it is in my ppa...

 http://ppa.launchpad.net/brennion/ppa/ubuntu

[Bem Jones-Bey (ajani)]

On 01/28/2009 11:29 AM, Thunderbird wrote:
> What might be useful is the following on a fresh boot of your system
> without using the nvidia driver and also without a framebuffer driver
> (a framebuffer driver could prevent an image restore).
>
> Download vbtracetool (git clone
> git://anongit.freedesktop.org/~stuart/vbtracetool/), compile it and
> then it like mentioned in the QUICKSTART file bundled with it. It will
> take 30-60s and then bzip2 the resulting file. The file contains the
> boot log of your video bios and might show me where the info I need in
> the bios is located.
>
I ran all 3 steps in the QUICKSTART file. I attempted to attach them to
my email, but launchpad didn't like that, perhaps because the delooped
bzipped logfile is 13MB. (It's like 500 MB expanded) So I've put them up
here:

http://testing.pyen.com/~ajani/nvidia/8510w-logfile-deloopd.bz2
http://testing.pyen.com/~ajani/nvidia/8510w-io-logfile.bz2
http://testing.pyen.com/~ajani/nvidia/8510w.rom

Hope that does end up being useful.

--
Bem Jones-Bey (<email address hidden>)

[Thunderbird (thunderbird-linuxhardware)]

There is some code in the bios which loads the smartdimmer register but I haven't had time to fully understand it yet.

[Thunderbird (thunderbird-linuxhardware)]

Could some more people post their bios file (~/.nvclock/bios0.rom). I might have found something in it.

[Michael Doube (michael-doube)]

This is a Sony Vaio SZ650N/C with nVidia GeForce 8400M

[Thunderbird (thunderbird-linuxhardware)]

Michael what version of nvclock are you using? For some reason your bios file is empty. If you aren't using b4 try to update to it and also try to remove ~/.nvclock and run nvclock again to recreate it. NVClock should be showing some bios info using -i.

[Michael Doube (michael-doube)]

Thunderbird:

with nvclock 0.8b4

]$ nvclock -i
-- General info --
Card: nVidia Geforce 8400M GS
Architecture: G86 A2
PCI id: 0x427
GPU clock: 182.248 MHz
Bustype: PCI-Express

-- Shader info --
Clock: 432.000 MHz
Stream units: 16 (1b)
ROP units: 4 (1b)
-- Memory info --
Amount: 64 MB
Type: 128 bit DDR3
Clock: 601.712 MHz

-- PCI-Express info --
Current Rate: 16X
Maximum rate: 16X

-- Smartdimmer info --
Backlight level: 40%

-- Sensor info --
Sensor: GPU Internal Sensor
GPU temperature: 60C

-- VideoBios information --
Version: 60.86.57.00.18
Signon message: Sony S58MGT02 VBIOS
Performance level 0: gpu 275MHz/shader 550MHz/memory 301MHz/1.15V/100%
Performance level 1: gpu 400MHz/shader 800MHz/memory 600MHz/1.15V/100%
VID mask: 3
Voltage level 0: 1.15V, VID: 0
Voltage level 1: 1.20V, VID: 1
Voltage level 2: 1.25V, VID: 2
Voltage level 3: 1.32V, VID: 3

[xor59 (xor59)]

This is a Fujitsu Siemens XA2528 with nVidia Geforce 8600M GS

 nvclock -i
-- General info --
Card: nVidia Geforce 8600M GS
Architecture: G86 A2
PCI id: 0x425
GPU clock: 182.248 MHz
Bustype: PCI-Express

-- Shader info --
Clock: 594.000 MHz
Stream units: 16 (1b)
ROP units: 8 (1b)
-- Memory info --
Amount: 256 MB
Type: 128 bit DDR2
Clock: 799.200 MHz

-- PCI-Express info --
Current Rate: 16X
Maximum rate: 16X

-- Sensor info --
Sensor: GPU Internal Sensor
GPU temperature: 51C

-- VideoBios information --
Version: 60.86.4c.00.15
Signon message: G86 e416 SKU 0001 VGA BIOS
Performance level 0: gpu 275MHz/shader 550MHz/memory 200MHz/1.20V/100%
Performance level 1: gpu 500MHz/shader 1000MHz/memory 400MHz/1.25V/100%
VID mask: 3
Voltage level 0: 1.15V, VID: 0
Voltage level 1: 1.20V, VID: 1
Voltage level 2: 1.25V, VID: 2
Voltage level 3: 1.32V, VID: 3

[Thunderbird (thunderbird-linuxhardware)]

Right now the info I expected is present in your bios and in the HP and other Sony bioses I have seen. The info which is there is a line of code which sets the smartdimmer register to '100%'. There might be more info but I have no idea where that is. This might be enough for some basic detection.

If people are using a Mac, Samsung laptop or some other supported model I'm also interested in bios dumps for those to see if the detection can also be used on those.

[Schmirrwurst (schmirrwurst)]

debdiff for new version 0.8b4 which solve a part of the issue

[Shawe Ewahs (shawe-ewahs)]

Thunderbird what coincidencies are you found on the current bios shared?

[Schmirrwurst (schmirrwurst)]

As I've just learn the diff.gz is needed by upstream version... here it is...
I hope it is going to be included in jaunty, I would make it easyer, hope my sponsoring will work...

Just a question about smartdimmer, I've seen the nvclock has its one, the smartdimmer pkg from the repository should be deleted ? Do I need to provide the smartdimmer binary in the nvclock package and setting smartdimmer pkg as conflict ?

For those who wan't to try, the packages are available here :
https://launchpad.net/~brennion/+archive/ppa

[Steve Langasek (vorlon)]

Sebastien, why have you opened tasks against all of these different packages? I see no information that would explain that this is a bug in linux, hal, or acpi-support.

The patches you've submitted for sponsorship are against the nvclock package, which is one package for which a task has *not* been opened here. Your first patch, as you noted, appears to include the upstream diff relative to the current Ubuntu version; that's not much of a problem, but you also appear to have repackaged nvclock from scratch, discarding all of the package history. Is there a reason for this?

[Thunderbird (thunderbird-linuxhardware)]

I haven't studied the packages posted here but I would recommend to
use the kanotix package as a base. The kanotix packager updated some
portions based on my input. Debian might receive new packages soon
too. I contacted Randy about it a while ago but I didn't hear anything
back from him. (I'm the author of nvclock)

Quoting Steve Langasek <email address hidden>:

> Sebastien, why have you opened tasks against all of these different
> packages? I see no information that would explain that this is a bug in
> linux, hal, or acpi-support.
>
> The patches you've submitted for sponsorship are against the nvclock
> package, which is one package for which a task has *not* been opened
> here. Your first patch, as you noted, appears to include the upstream
> diff relative to the current Ubuntu version; that's not much of a
> problem, but you also appear to have repackaged nvclock from scratch,
> discarding all of the package history. Is there a reason for this?
>
> ** Changed in: nvclock (Ubuntu)
> Sourcepackagename: acpi-support => nvclock
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvclock” source package in Ubuntu: New
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E,
> FZ21M, FZ21S, FZ470E, FZ340E, FZ190N, FZ...

[Steve Langasek (vorlon)]

This is definitely not a hotkey-setup issue; the hotkey-setup package only handles setting kernel keymaps for hotkeys, and is deprecated in favor of hal-info besides.

I had the opportunity this week to test out hotkey mappings on a variety of laptops, including one Sony Vaio, and the brightness keys appear to be recognized correctly as keys - and the brightness was adjusted as well. I don't know if this was an nvidia-based system, but at least I didn't see any evidence that the keypresses themselves were not recognized correctly.

If you have reason to think that the keypresses are not being recognized on your system (as opposed to us just not having a good way to *handle* those keypresses on Ubuntu), please follow https://wiki.ubuntu.com/Hotkeys/Troubleshooting and report back with your results.

[Thunderbird (thunderbird-linuxhardware)]

I verified what I was looking for in bioses from sony, hp and apple. I
expect others to use the same way, so I have added some experimental
code to nvclock cvs. It should be tested to see if it works well and I
still need to know if it works on samsung laptops.

Roderick

Quoting Shawe Ewahs <email address hidden>:

> Thunderbird what coincidencies are you found on the current bios shared?
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: New
> Status in “hotkey-setup” source package in Ubuntu: In Progress
> Status in “linux” source package in Ubuntu: In Progress
> Status in “nvidia-graphics-drivers-177” source package in Ubuntu: In Progress
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E,
> FZ21M, FZ21S, FZ470E, FZ340E, FZ190N, FZ18M, FZ31E, FZ18E, FZ260E
> NR21Z, NR38S, NR21S
>
> 8600M GS:
> VGN FZ31Z, FZ21Z, FZ31S
>
> 8600M GT:
> VGN AR51SU, AR71S
> }
>
> Zepto laptops
> {
> Geforce 9600GT based laptops using MXM cards
> }
>
> Add your model to the list by clicking on the "Update description /
> tags" link, NOT by asking in a bug comment for someone else to do it.
>
> To get hotkeys to work, follow the instructions in this comment:
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/75
> or install the package at :
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/111
>
> Dual-adapter models (SZ6 among others) can get backlight control
> with the Intel adapter using xbackli...

[Thunderbird (thunderbird-linuxhardware)]

This issue is specific to various nvidia based laptops including some
sony models. It is a real issue.

Quoting Steve Langasek <email address hidden>:

> This is definitely not a hotkey-setup issue; the hotkey-setup package
> only handles setting kernel keymaps for hotkeys, and is deprecated in
> favor of hal-info besides.
>
> I had the opportunity this week to test out hotkey mappings on a variety
> of laptops, including one Sony Vaio, and the brightness keys appear to
> be recognized correctly as keys - and the brightness was adjusted as
> well. I don't know if this was an nvidia-based system, but at least I
> didn't see any evidence that the keypresses themselves were not
> recognized correctly.
>
> If you have reason to think that the keypresses are not being recognized
> on your system (as opposed to us just not having a good way to *handle*
> those keypresses on Ubuntu), please follow
> https://wiki.ubuntu.com/Hotkeys/Troubleshooting and report back with
> your results.
>
> ** Changed in: hotkey-setup (Ubuntu)
> Status: In Progress => Invalid
>
> ** Changed in: hal (Ubuntu)
> Status: New => Invalid
>
> ** Changed in: nvidia-graphics-drivers-177 (Ubuntu)
> Status: In Progress => New
>
> ** Changed in: linux (Ubuntu)
> Status: In Progress => New
>

[Steve Langasek (vorlon)]

> It is a real issue.

I never said otherwise; I only said that it doesn't appear to be a question of hotkey mappings.

[Schmirrwurst (schmirrwurst)]

For the new package :
I packaged from the scratch the b4 release, because it is out now, and I though it might be easyer for jaunty to upload directly a version working with nvidia8/9... and to have it directly included in the distribution.
Patching the b3 version for intrepid, is too complicated for me...

Thunderbird, perhaps you can tell me about your modification (that are in the kanotix pkg) so I can include them. Or you mind the debian one will be ready for jaunty ?

For the bug report, I've seen acpi event scripts for sony, are removed from jaunty, for the moment, and the workaround to have the fnkey was to modify the sonybright... and so on. So I though acpi-support is concerned. Sorry if that was wrong...

That all reports turned to new, was not planed.

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.

  http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180

To transition your bug into the new package, we need your help. Please do the following:

 a. Verify the bug occurs in Jaunty with the -180 driver
     (ISOs: http://cdimage.ubuntu.com/releases/jaunty/)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * Your /etc/X11/xorg.conf
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Under Affects, click the down arrow to the left of 'nvidia-graphics-drivers-177'
 d. Edit the Package to change 'nvidia-graphics-drivers-177' to 'nvidia-graphics-drivers-180'
 e. Click Save Changes

Thank you!

[We'll expire the remaining -177 bugs in a month or so.]

[Icapa (ivan-olea)]

HI everyone !

I was looking for how to change brightness in my Vaio VGN-CS11S and found this thread, congratulations it's very good !

You're modified version of nvclock works with my GeForce 9300 perfectly, but I can't do it with Fn Keys.

Volume keys work ok, but brighness don't. With acpi_listen I can't see any Fn key event altough in my gnome desktop I can change volume and mute ok.

Can you help me please?

[Shawe Ewahs (shawe-ewahs)]

Icapa try this comments:

https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/161
https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/164

On it's it have a little scripts for change files, but is possible that your model of laptop are not included on /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi, it your isn't on list add your model, like this:
        <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" string="VGN-FZ38M">
          <merge key="laptop_panel.num_levels" type="int">20</merge>
          <merge key="laptop_panel.access_method" type="string">sony-nvidia</merge>
        </match>

Changing VGN-FZ38M for your model. It's the one thing that I can help you.

[Icapa (ivan-olea)]

Thanks Shawe

I have tried with "showkey" to see if the laptop "understand" these keys and
It doesn't, with nvclock I can change brightness manually but it's a bit
tedious. I run your script..but it seems it doesn't work for me... I'm going
to try the modifications yo said

Thank you very much

2009/2/15 Shawe Ewahs <email address hidden>

> Icapa try this comments:
>
>
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/161
>
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/164
>
> On it's it have a little scripts for change files, but is possible that
> your model of laptop are not included on
> /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi,
> it your isn't on list add your model, like this:
> <match
> key="/org/freedesktop/Hal/devices/computer:system.hardware.product"
> string="VGN-FZ38M">
> <merge key="laptop_panel.num_levels" type="int">20</merge>
> <merge key="laptop_panel.access_method"
> type="string">sony-nvidia</merge>
> </match>
>
> Changing VGN-FZ38M for your model. It's the one thing that I can help
> you.
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung,
> Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in "hal" source package in Ubuntu: Invalid
> Status in "hotkey-setup" source package in Ubuntu: Invalid
> Status in "linux" source package in Ubuntu: New
> Status in "nvclock" source package in Ubuntu: New
> Status in "nvidia-graphics-drivers-180" source package in Ubuntu: New
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way to
> control backlight brightness. In case of Sony e.g. on Vaios with 8-series
> adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3 -d:pserver:<email address hidden>:/cvsroot/nvclock
> co -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E SZ95S
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, ...

[Shawe Ewahs (shawe-ewahs)]

Icapa, if works manually, works with this scripts adding your model in the file that I say you. Not work perfectly, but works.

[Icapa (ivan-olea)]

I'm sure your script is good, nvclock works perfectly but my Fn5 and Fn6
couldn't be detected, is there any test reading directly from keyboard
driver to see if keys are detected?

2009/2/15 Shawe Ewahs <email address hidden>

> Icapa, if works manually, works with this scripts adding your model in
> the file that I say you. Not work perfectly, but works.
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung,
> Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in "hal" source package in Ubuntu: Invalid
> Status in "hotkey-setup" source package in Ubuntu: Invalid
> Status in "linux" source package in Ubuntu: New
> Status in "nvclock" source package in Ubuntu: New
> Status in "nvidia-graphics-drivers-180" source package in Ubuntu: New
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way to
> control backlight brightness. In case of Sony e.g. on Vaios with 8-series
> adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3 -d:pserver:<email address hidden>:/cvsroot/nvclock
> co -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E SZ95S
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E, FZ21M,
> FZ21S, FZ470E, FZ340E, FZ190N, FZ18M, FZ31E, FZ18E, FZ260E NR21Z, NR38S,
> NR21S,FZ280E
>
> 8600M GS:
> VGN FZ31Z, FZ21Z, FZ31S
>
> 8600M GT:
> VGN AR51SU, AR71S
> }
>
> Zepto laptops
> {
> Geforce 9600GT based laptops using MXM cards
> }
>
> Add your model to the list by clicking on the "Update description / tags"
> link, NOT by asking in a bug comment for someone else to do it.
>
> To get hotkeys to work, follow the instructions in this comment:
>
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/75
> or install the package at :
>
> https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/95444/comments/111
>
> Dual-adapter models (SZ6 among others) can get backlight control with the
> Intel adapter using xbacklight, and can get hotkey funct...

[Shawe Ewahs (shawe-ewahs)]

Read all comments on this pages, people say thinks that you can try for try
to solve.

By §h@wæ
http://www.islatux.es

2009/2/15 Icapa <email address hidden>

> I'm sure your script is good, nvclock works perfectly but my Fn5 and Fn6
> couldn't be detected, is there any test reading directly from keyboard
> driver to see if keys are detected?
>
>
> 2009/2/15 Shawe Ewahs <email address hidden>
>
> > Icapa, if works manually, works with this scripts adding your model in
> > the file that I say you. Not work perfectly, but works.
> >
> > --
> > No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung,
> > Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> > https://bugs.launchpad.net/bugs/95444
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in Hardware Abstraction Layer (HAL): Invalid
> > Status in "hal" source package in Ubuntu: Invalid
> > Status in "hotkey-setup" source package in Ubuntu: Invalid
> > Status in "linux" source package in Ubuntu: New
> > Status in "nvclock" source package in Ubuntu: New
> > Status in "nvidia-graphics-drivers-180" source package in Ubuntu: New
> >
> > Bug description:
> > Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
> >
> > On various laptops from Sony, HP, Samsung and others there is no way to
> > control backlight brightness. In case of Sony e.g. on Vaios with 8-series
> > adapters, e.g.
> > nVidia Corporation GeForce 8400M GS
> > nVidia Corporation GeForce 8600M GT (rev a1)
> >
> > The registers have been found (kudos to mikes!) and incorporated into
> > nvclock, which you can check out by anonymous cvs and install:
> >
> > ]$ sudo apt-get install cvs
> > ]$ cvs -d:pserver:<email address hidden>:/cvsroot/nvclock
> > login
> > ]$ cvs -z3 -d:pserver:<email address hidden>:
> /cvsroot/nvclock
> > co -P nvclock
> > ]$ cd nvclock
> > ]$ ./autogen.sh
> > ]$ ./configure
> > ]$ make
> > ]$ sudo make install
> >
> > To test, make sure you are using nVidia's proprietary driver, then:
> > ]$ sudo nvclock -S 100
> > ]$ sudo nvclock -S 15
> > ]$ sudo nvclock -S +10
> >
> > So far mikes' registers have been found to work on:
> >
> > Apple laptops
> > {
> > Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> > }
> >
> > HP/Compaq laptops
> > {
> > 8510W (Quadro FX 570M, MXM)
> > 8710P (Quadro NVS 320M, MXM)
> > }
> >
> > Samsung laptops:
> > {
> > Q210 (Geforce 9200M)
> > Q310 (Geforce 9200M)
> > R510 (Geforce 9200M)
> > }
> >
> > Sony laptops:
> > {
> > 8400M GS:
> > VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E SZ95S
> >
> > 8400M GT:
> > VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E,
> FZ21M,
> > FZ21S, FZ470E, FZ340E, FZ190N, FZ18M, FZ31E, FZ18E, FZ260E NR21Z, NR38S,
> > NR21S,FZ280E
> >
> > 8600M GS:
> > VGN FZ31Z, FZ21Z, FZ31S
> >
> > 8600M GT:
> > VGN AR51SU, AR71S
> > }
> >
> > Zepto laptops
> > {
> > Geforce 9600GT based laptops using MXM cards
> > }
> >
> > Add your model to the list by clicking on the "Update description / tags"
> > link, NOT by asking in a bug comment for someone else to do it.
> >
> > To get hotkeys to work, follow the in...

[Thunderbird (thunderbird-linuxhardware)]

Could some people try the latest nvclock cvs? Some time ago I added
proper smartdimmer detection but I still don't know if it works for
everyone.

Thanks,
Roderick

[Schmirrwurst (schmirrwurst)]

Hi thunderbird,

If I've the previous cvs version installed, could you describe the steps to properly uninstall and install, and what to test ? There so many posts now, that it's pretty confusing...
Can I test it also under jaunty ? So far as I know, the sonybright.sh ... and other scripts aren't yet available ?

[Thunderbird (thunderbird-linuxhardware)]

Hi,

The steps are the same as before, so:

]$ sudo apt-get install cvs
]$ cvs -d:pserver:<email address hidden>:/cvsroot/nvclock login
]$ cvs -z3
-d:pserver:<email address hidden>:/cvsroot/nvclock co
-P nvclock
]$ cd nvclock
]$ ./autogen.sh
]$ ./configure
]$ make
]$ sudo make install

Thanks,
Roderick

Quoting Schmirrwurst <email address hidden>:

> Hi thunderbird,
>
> If I've the previous cvs version installed, could you describe the
> steps to properly uninstall and install, and what to test ? There so
> many posts now, that it's pretty confusing...
> Can I test it also under jaunty ? So far as I know, the
> sonybright.sh ... and other scripts aren't yet available ?
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: Invalid
> Status in “hotkey-setup” source package in Ubuntu: Invalid
> Status in “linux” source package in Ubuntu: New
> Status in “nvclock” source package in Ubuntu: New
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: New
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight brightness. In case of Sony e.g. on Vaios with
> 8-series adapters, e.g.
> nVidia Corporation GeForce 8400M GS
> nVidia Corporation GeForce 8600M GT (rev a1)
>
> The registers have been found (kudos to mikes!) and incorporated into
> nvclock, which you can check out by anonymous cvs and install:
>
> ]$ sudo apt-get install cvs
> ]$ cvs
> -d:pserver:<email address hidden>:/cvsroot/nvclock
> login
> ]$ cvs -z3
> -d:pserver:<email address hidden>:/cvsroot/nvclock co
> -P nvclock
> ]$ cd nvclock
> ]$ ./autogen.sh
> ]$ ./configure
> ]$ make
> ]$ sudo make install
>
> To test, make sure you are using nVidia's proprietary driver, then:
> ]$ sudo nvclock -S 100
> ]$ sudo nvclock -S 15
> ]$ sudo nvclock -S +10
>
> So far mikes' registers have been found to work on:
>
> Apple laptops
> {
> Macbook 5,1 Aluminum 13.3" (Geforce 9400M)
> }
>
> HP/Compaq laptops
> {
> 8510W (Quadro FX 570M, MXM)
> 8710P (Quadro NVS 320M, MXM)
> }
>
> Samsung laptops:
> {
> Q210 (Geforce 9200M)
> Q310 (Geforce 9200M)
> R510 (Geforce 9200M)
> }
>
> Sony laptops:
> {
> 8400M GS:
> VGN SZ650N, SZ61MN/B, SZ730E, SZ750N, SZ71MN/B, SZ71E SZ95S
>
> 8400M GT:
> VGN FZ38M, FZ31M, FZ11Z, NR31, AR41E, FZ11S, FZ290, FZ250AE, FZ21E,
> FZ21M, FZ21S, FZ470E, FZ340E, FZ190N, FZ18M, FZ31E, FZ18E, FZ260E
> NR21Z, NR38S, NR21S,FZ280E
>
> 8600M GS:
> VGN FZ31Z, FZ21Z, FZ31S
>
> 8600M GT:
> VGN AR51SU, AR71S
> }
>
> Zepto laptops
> {
> Geforce 9600GT based laptops using MXM cards
> }
>
> Add your model to the list by clicking on the "Update description /
> tags" link, NOT by asking in a bug comment for someone else to do it.
...

[Bem Jones-Bey (ajani)]

On 02/18/2009 10:38 AM, Thunderbird wrote:
> Could some people try the latest nvclock cvs? Some time ago I added
> proper smartdimmer detection but I still don't know if it works for
> everyone.

Sorry it took me so long, I've been rather busy lately. I did get to
compile the latest CVS, and while it works fine if I run it as myself
from the commandline, hald fails to run it (for my brightness keys) with
the following error:

[28671]: 14:45:47.158 [D] addon-acpi.c:195: event is 'video C160
00000086 00000000
'
14:45:47.159 [I] hald_dbus.c:5127: OK for method 'GetBrightness' with
signature '' on interface 'org.freedesktop.Hal.Device.LaptopPanel' for
UDI '/org/freedesktop/Hal/devices/computer_backlight' and execpath
'hal-system-lcd-get-brightness'
14:45:47.159 [I] hald_dbus.c:4018: no need to enqueue
14:45:47.550 [I] hald_dbus.c:4042: No more methods in queue
14:45:47.550 [I] hald_dbus.c:4105: failed with 'Error!' 'Smartdimmer is
only supported on certain (HP/SamsungSony/Zepto) laptops using a Geforce
6200/7x00Go/8x00Go. If you want support on your laptop contact the author.'
14:45:47.551 [I] hald_dbus.c:5127: OK for method 'SetBrightness' with
signature 'i' on interface 'org.freedesktop.Hal.Device.LaptopPanel' for
UDI '/org/freedesktop/Hal/devices/computer_backlight' and execpath
'hal-system-lcd-set-brightness'
14:45:47.551 [I] hald_dbus.c:4018: no need to enqueue
14:45:47.916 [I] hald_dbus.c:4042: No more methods in queue
14:45:47.917 [I] hald_dbus.c:4105: failed with 'Error!' 'Smartdimmer is
only supported on certain (HP/SamsungSony/Zepto) laptops using a Geforce
6200/7x00Go/8x00Go. If you want support on your laptop contact the author.'

While hald does claim to be running as root, I don't know what
privileges it runs the scripts with.

If I put the old smartdimmer 0.8b4 (without the detection logic), my
brightness keys work fine.

--
Bem Jones-Bey (<email address hidden>)

[Thunderbird (thunderbird-linuxhardware)]

What is different when you run it as a user and at startup? In both
cases the nvidia drivers aren't loaded yet? You are certain that you
use the same binary in both cases?

Perhaps it failed to report bios info when running from a startup
script. Could you check if the output of 'nvclock -i' shows bios info
in both situations?

Thanks,
Roderick

Quoting Bem Jones-Bey <email address hidden>:

> On 02/18/2009 10:38 AM, Thunderbird wrote:
>> Could some people try the latest nvclock cvs? Some time ago I added
>> proper smartdimmer detection but I still don't know if it works for
>> everyone.
>
> Sorry it took me so long, I've been rather busy lately. I did get to
> compile the latest CVS, and while it works fine if I run it as myself
> from the commandline, hald fails to run it (for my brightness keys) with
> the following error:
>
> [28671]: 14:45:47.158 [D] addon-acpi.c:195: event is 'video C160
> 00000086 00000000
> '
> 14:45:47.159 [I] hald_dbus.c:5127: OK for method 'GetBrightness' with
> signature '' on interface 'org.freedesktop.Hal.Device.LaptopPanel' for
> UDI '/org/freedesktop/Hal/devices/computer_backlight' and execpath
> 'hal-system-lcd-get-brightness'
> 14:45:47.159 [I] hald_dbus.c:4018: no need to enqueue
> 14:45:47.550 [I] hald_dbus.c:4042: No more methods in queue
> 14:45:47.550 [I] hald_dbus.c:4105: failed with 'Error!' 'Smartdimmer is
> only supported on certain (HP/SamsungSony/Zepto) laptops using a Geforce
> 6200/7x00Go/8x00Go. If you want support on your laptop contact the author.'
> 14:45:47.551 [I] hald_dbus.c:5127: OK for method 'SetBrightness' with
> signature 'i' on interface 'org.freedesktop.Hal.Device.LaptopPanel' for
> UDI '/org/freedesktop/Hal/devices/computer_backlight' and execpath
> 'hal-system-lcd-set-brightness'
> 14:45:47.551 [I] hald_dbus.c:4018: no need to enqueue
> 14:45:47.916 [I] hald_dbus.c:4042: No more methods in queue
> 14:45:47.917 [I] hald_dbus.c:4105: failed with 'Error!' 'Smartdimmer is
> only supported on certain (HP/SamsungSony/Zepto) laptops using a Geforce
> 6200/7x00Go/8x00Go. If you want support on your laptop contact the author.'
>
> While hald does claim to be running as root, I don't know what
> privileges it runs the scripts with.
>
> If I put the old smartdimmer 0.8b4 (without the detection logic), my
> brightness keys work fine.
>
> --
> Bem Jones-Bey (<email address hidden>)
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq,
> Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series
> graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Hardware Abstraction Layer (HAL): Invalid
> Status in “hal” source package in Ubuntu: Invalid
> Status in “hotkey-setup” source package in Ubuntu: Invalid
> Status in “linux” source package in Ubuntu: New
> Status in “nvclock” source package in Ubuntu: New
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: New
>
> Bug description:
> Using Ubuntu on laptops with Nvidia Geforce8/Geforce9/Quadro vga card:
>
> On various laptops from Sony, HP, Samsung and others there is no way
> to control backlight b...

[Bem Jones-Bey (ajani)]

On 02/22/2009 01:53 AM, Thunderbird wrote:
> What is different when you run it as a user and at startup? In both
> cases the nvidia drivers aren't loaded yet? You are certain that you
> use the same binary in both cases?

I think you misunderstand: smartdimmer gives me that error every time
hald tries to run it. hald runs it in response to me pressing the
brightness up and down keys.

It runs the following to set the brightness: ($value is passed into the
script)

if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia8" ]; then
     smartdimmer -s $((($value +1)*5))
     exit 0
fi

And it runs the following to get the brightness:

if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia8" ]; then
     value=$((`smartdimmer -g | awk '{print $3;}'`))
     value=$((($value /5)-1))
     exit ${value}
fi

I am sure that it is running the same binary there that I am running by
hand, as the only smartdimmer on my system is /usr/bin/smartdimmer, and
it reliably stops working when I copy in the new binary, and works again
when I copy in the old one. Both binaries work fine from the command
line. I just checked, and hald seems to be running the script as root
(according to 'id' and 'whoami'), so I'm completely not sure why I'm
seeing different behavior.

In all these cases, X is up and running with the nvidia drivers.

>
> Perhaps it failed to report bios info when running from a startup
> script. Could you check if the output of 'nvclock -i' shows bios info
> in both situations?

Here's nvclock -i run from a gnome-terminal, as my normal user:
-- General info --
Card: nVidia QuadroFX 570M
Architecture: G84 A2
PCI id: 0x40c
GPU clock: 182.248 MHz
Bustype: PCI-Express

-- Shader info --
Clock: 594.000 MHz
Stream units: 32 (11b)
ROP units: 8 (11b)
-- Memory info --
Amount: 256 MB
Type: 128 bit DDR3
Clock: 601.712 MHz

-- PCI-Express info --
Current Rate: 16X
Maximum rate: 16X

-- Smartdimmer info --
Backlight level: 85%

-- Sensor info --
Sensor: GPU Internal Sensor
GPU temperature: 68C

-- VideoBios information --
Version: 60.84.56.01.02
Signon message: HP VB10 Mobile NB8P-GLM VGA BIOS
Performance level 0: gpu 275MHz/shader 550MHz/memory 301MHz/1.15V/100%
Performance level 1: gpu 475MHz/shader 950MHz/memory 702MHz/1.20V/100%
VID mask: 3
Voltage level 0: 1.15V, VID: 3
Voltage level 1: 1.20V, VID: 3

And here's what it looks like when HAL runs it:

-- General info --
Card: nVidia QuadroFX 570M
Architecture: G84 A2
PCI id: 0x40c
GPU clock: 182.248 MHz
Bustype: PCI-Express

-- Shader info --
Clock: 594.000 MHz
Stream units: 32 (11b)
ROP units: 8 (11b)
-- Memory info --
Amount: 256 MB
Type: 128 bit DDR3
Clock: 601.712 MHz

-- PCI-Express info --
Current Rate: 16X
Maximum rate: 16X

-- Sensor info --
Sensor: GPU Internal Sensor
GPU temperature: 71C

It does indeed look like it's missing BIOS info. Interestingly enough, I
get the same behavior if I use the 0.8b4 version of nvclock, but its
smartdimmer works from hald because it ignores the fact that it can't
look it up.

--
Bem Jones-Bey (<email address hidden>)

[Thunderbird (thunderbird-linuxhardware)]

There must be a bug somewhere in my bios dumping code. I'll take a
look at it. Note smartdimmer and nvclock are internally the same. Only
from the outside smartdimmer looks different.

Roderick

Quoting Bem Jones-Bey <email address hidden>:

> On 02/22/2009 01:53 AM, Thunderbird wrote:
>> What is different when you run it as a user and at startup? In both
>> cases the nvidia drivers aren't loaded yet? You are certain that you
>> use the same binary in both cases?
>
> I think you misunderstand: smartdimmer gives me that error every time
> hald tries to run it. hald runs it in response to me pressing the
> brightness up and down keys.
>
> It runs the following to set the brightness: ($value is passed into the
> script)
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia8" ]; then
> smartdimmer -s $((($value +1)*5))
> exit 0
> fi
>
> And it runs the following to get the brightness:
>
> if [ "$HAL_PROP_LAPTOP_PANEL_ACCESS_METHOD" = "nvidia8" ]; then
> value=$((`smartdimmer -g | awk '{print $3;}'`))
> value=$((($value /5)-1))
> exit ${value}
> fi
>
> I am sure that it is running the same binary there that I am running by
> hand, as the only smartdimmer on my system is /usr/bin/smartdimmer, and
> it reliably stops working when I copy in the new binary, and works again
> when I copy in the old one. Both binaries work fine from the command
> line. I just checked, and hald seems to be running the script as root
> (according to 'id' and 'whoami'), so I'm completely not sure why I'm
> seeing different behavior.
>
> In all these cases, X is up and running with the nvidia drivers.
>
>>
>> Perhaps it failed to report bios info when running from a startup
>> script. Could you check if the output of 'nvclock -i' shows bios info
>> in both situations?
>
> Here's nvclock -i run from a gnome-terminal, as my normal user:
> -- General info --
> Card: nVidia QuadroFX 570M
> Architecture: G84 A2
> PCI id: 0x40c
> GPU clock: 182.248 MHz
> Bustype: PCI-Express
>
> -- Shader info --
> Clock: 594.000 MHz
> Stream units: 32 (11b)
> ROP units: 8 (11b)
> -- Memory info --
> Amount: 256 MB
> Type: 128 bit DDR3
> Clock: 601.712 MHz
>
> -- PCI-Express info --
> Current Rate: 16X
> Maximum rate: 16X
>
> -- Smartdimmer info --
> Backlight level: 85%
>
> -- Sensor info --
> Sensor: GPU Internal Sensor
> GPU temperature: 68C
>
> -- VideoBios information --
> Version: 60.84.56.01.02
> Signon message: HP VB10 Mobile NB8P-GLM VGA BIOS
> Performance level 0: gpu 275MHz/shader 550MHz/memory 301MHz/1.15V/100%
> Performance level 1: gpu 475MHz/shader 950MHz/memory 702MHz/1.20V/100%
> VID mask: 3
> Voltage level 0: 1.15V, VID: 3
> Voltage level 1: 1.20V, VID: 3
>
> And here's what it looks like when HAL runs it:
>
> -- General info --
> Card: nVidia QuadroFX 570M
> Architecture: G84 A2
> PCI id: 0x40c
> GPU clock: 182.248 MHz
> Bustype: PCI-Express
>
> -- Shader info --
> Clock: 594.000 MHz
> Stream units: 32 (11b)
> ROP units: 8 (11b)
> -- Memory info --
> Amount: 256 MB
> Type: 128 bit DDR3
> Clock: 601.712 MHz
>
> -- PCI-Express info --
> Current Rate: 16X
> Maximum rate: 16X
>
> -- Sensor info --
> Sensor: GPU Internal Sensor...

[Schmirrwurst (schmirrwurst)]

For me on FZ21E, nvclock command line seems to work, see log file...

[Schmirrwurst (schmirrwurst)]

FN keys are still working only after /etc/acpid restart, I don't know why, and could not find any infos in the logs...
Do the changes in the latest nvclock cvs are supposed to solve fnkeys pb ?

[Bryce Harrington (bryce)]

This seems to be an nvclock issue rather than -nvidia. Even if it was an -nvidia issue, it is not likely anything could be done about it since it's a proprietary binary driver. Dropping task.

[Schmirrwurst (schmirrwurst)]

I think if we need nvclock to manage brightness to work with nvidia cards, then nvclock should be at least added to depedency from nvidia-driver, so that the average user, have it work directly... ?

[Shawe Ewahs (shawe-ewahs)]

Schmirrwurst, if in Ubuntu scripts add support for this laptops yes, is
possible add the actually partial solution for the next release? I know that
isn't the best way to do it, but is better than nothing in this moment.

My scripts added in comments works, only need add support for all laptops
listed on this thread, maybe can need add a new model of laptop that isn't
when I do the script.
My script only copy a modifieds fdi file for add support for laptops
affecteds withs this problem.

By §h@wæ
http://www.islatux.es

2009/3/13 Schmirrwurst <email address hidden>

> I think if we need nvclock to manage brightness to work with nvidia
> cards, then nvclock should be at least added to depedency from nvidia-
> driver, so that the average user, have it work directly... ?
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung,
> Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Schmirrwurst (schmirrwurst)]

shawe, are your changed on fdi related with acpi ?

Do you know why there no more sony scripts on jaunty for now ?

Is someone able here to release the b4 version from nvclock, I'm afraid that jaunty will come out with the b3 version which is not working with gforce 8/9 card...that would make more complicated for normal user to use a workaround...
I've already proposed a nvclock package, and I've now find out, nvclock b4 has already been released for debian sid :
http://packages.debian.org/fr/sid/nvclock, how can we do to have it also for jaunty ?

[Shawe Ewahs (shawe-ewahs)]

Schmirrwurst why no more sony scripts on jaunty? It's the way that partial
works in this moment without big problems.
nvclock b4 works well without this scripts? I can't tested in this moment, I
haven't got my laptop.

By §h@wæ
http://www.islatux.es

2009/3/14 Schmirrwurst <email address hidden>

> shawe, are your changed on fdi related with acpi ?
>
> Do you know why there no more sony scripts on jaunty for now ?
>
> Is someone able here to release the b4 version from nvclock, I'm afraid
> that jaunty will come out with the b3 version which is not working with
> gforce 8/9 card...that would make more complicated for normal user to use a
> workaround...
> I've already proposed a nvclock package, and I've now find out, nvclock b4
> has already been released for debian sid :
> http://packages.debian.org/fr/sid/nvclock, how can we do to have it also
> for jaunty ?
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung,
> Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Schmirrwurst (schmirrwurst)]

for the moment there are no more "sonybright.sh" and other file related to sony/nvidia in the acpi folder, they have been removed on jaunty, and I'm wondering that one month for release, there is still nothing in vue ! So I asked you if you know if something is in progress... It would be very bad, if jaunty comes out without any acpi support for gforce users !

[Shawe Ewahs (shawe-ewahs)]

Schmirrwurst I only know that appears on this thread, some users send his
graphic card info for try to found a common value for recognize it, but it
hasn't any result for the moment.

By §h@wæ
http://www.islatux.es

2009/3/14 Schmirrwurst <email address hidden>

> for the moment there are no more "sonybright.sh" and other file related
> to sony/nvidia in the acpi folder, they have been removed on jaunty, and
> I'm wondering that one month for release, there is still nothing in vue
> ! So I asked you if you know if something is in progress... It would be
> very bad, if jaunty comes out without any acpi support for gforce users
> !
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung,
> Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Steve Langasek (vorlon)]

The sony scripts were dropped from acpi-support because based on testing, these events were believed to now be handled in the kernel input layer. If your brightness hotkeys on sony work when you downgrade to the intrepid version of acpi-support, but stop working when upgrading to the jaunty version, then please open a new bug report against acpi-support with information about your model and include the output of both 'showkeys' and 'acpi_listen' when pressing these keys.

If it's a bug, it's an entirely separate bug from the one this bug report is about, so closing the acpi-support task.

[Schmirrwurst (schmirrwurst)]

as suggested from steve, I've opened a new but concerning acpi-support :
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/345531

Maybe you can confirm that bug, so that acpi-support team can work on it as quick as possible...

[Steve Langasek (vorlon)]

Nominally, this bug can be fixed with a trivial merge of nvclock 0.8b4 from Debian. I've attached the (filtered for autogenerated content) debdiff for this relative to the version currently in jaunty.

There are some practical issues with doing this merge right now, though:
- The reason the new version of nvclock fixes this bug is specifically because it begins to ship smartdimmer, which was previously in a separate package; I understand that the nvclock smartdimmer fixes the issue for GeForce8/9, but I don't know what the risk of regression is for other hardware supported by the previous package, which we will now be Conflicting/Replacing/Providing.
- I have no hardware on which I can test this package.
- We have to replace the current 'smartdimmer' package in main with the new one from nvclock, which requires a review by the ubuntu-mir team. Initial response from the ubuntu-mir team is that they would like to see the Debian merge done first, and only afterwards evaluate it for inclusion in main.

I'm subscribing motu-release for a second opinion on whether this is ok to upload for jaunty. It would be nice to close out this long-standing bug, I just don't know that the risk of regression is appropriate at this point in the release cycle.

[Schmirrwurst (schmirrwurst)]

Steve you said "Initial response from the ubuntu-mir team is that they would like to see the Debian merge done first, and only afterwards evaluate it for inclusion in main", I don't know if i've understand this, but I found out Debian has already packaged nvclock b4 for sid : http://packages.debian.org/fr/sid/x11/nvclock

[StefanPotyra (sistpoty)]

Steve, I think if you intent to include it into main, I guess ubuntu-release should handle this instead of motu-release.

Personally, I'd be in favor for better hardware support.

The diff doesn't look too big, but it sadly also doesn't give me any info about possible regressions (dealing with hardware without docs is a little bit opaque). *shrug*

[Steve Langasek (vorlon)]

On Sun, Mar 22, 2009 at 11:29:34PM -0000, StefanPotyra wrote:
> Steve, I think if you intent to include it into main, I guess ubuntu-
> release should handle this instead of motu-release.

Well, that can be done of course, but since the first step is to get a
universe-only update in, I figured I would ask motu-release. :)

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[Martin Pitt (pitti)]

I reviewed the merge. While you are at cleaning up the package anyway, you should also drop the Encoding= line from the .desktop file (these are obsolete).

Otherwise the merge looks alright to me.

[Steve Langasek (vorlon)]

punted on the Encoding= issue because the .desktop file isn't shipped in the package.

[Shawe Ewahs (shawe-ewahs)]

It is fixed yer for Ubuntu Jaunty:

https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589/comments/38

By §h@wæ
http://www.islatux.es

2009/3/23 Steve Langasek <email address hidden>

> punted on the Encoding= issue because the .desktop file isn't shipped in
> the package.
>
> ** Changed in: nvclock (Ubuntu)
> Assignee: (unassigned) => Steve Langasek (vorlon)
>
> --
> No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung,
> Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
> https://bugs.launchpad.net/bugs/95444
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Launchpad Janitor (janitor)]

This bug was fixed in the package nvclock - 0.8b4-1ubuntu2

---------------
nvclock (0.8b4-1ubuntu2) jaunty; urgency=low

  * Take over the smartdimmer binary package, shipping only the
    smartdimmer tool. LP: #347813, #95444.

 -- Steve Langasek <email address hidden> Thu, 26 Mar 2009 00:01:09 +0000

[Thomas Lété (bistory)]

This bug isn't fixed for me, hal recommends smartdimmer (>= 0.8b4) but it's wrong...
It must recommend nvclock (>= 0.8b4) instead of smartdimmer. I think it's a mistake :)
But nvclock from ubuntu isn't provided with the smartdimmer command... nvclock should superseed smartdimmer (which is now legacy).

[Thomas Lété (bistory)]

Just ignore my message, the smartdimmer utility has been updated recently, my apologises
My hotkeys aren't recognized by gnome...

[Michael Lustfield (michaellustfield)]

Invalidating against package "linux" because this has been fixed in package "nvclock".

[sijk (simo-kivimaki-fi)]

I updated nVidia proprietary driver to version 185.18.36 and now backlight brightness control works. I suppose that the new driver listens backlight ACPI events properly.

Setup:
Ubuntu Jaunty
HP 8530w
nVidia Quadro FX 770M

[Schmirrwurst (schmirrwurst)]

Could you post the output from :
ls /sys/class/backlight/
and
ls /proc/acpi/video/
?

[sijk (simo-kivimaki-fi)]

$ ls /sys/class/backlight/
acpi_video0

$ ls /proc/acpi/video/
DGFX

[Charalampos Serenis (chserenis)]

Not working with sony vaio VPCZ1, with an nvidia GT 330M graphics card

~/local/nvclock$ sudo /usr/local/bin/nvclock -f -S 15
Unable to shadow the video bios
Error!
Smartdimmer is only supported on certain (HP/Samsung/Sony/Zepto) laptops using a Geforce 6200/7x00Go/8x00Go. If you want support on your laptop contact the author.

[Ibrahim Karahan (ibrahimkarahan)]

Please see http://www.nvnews.net/vbulletin/showthread.php?t=143025 for a working driver on some laptops.

[asino89 (asino89)]

After latest updates to nvidia driver, the backlight control isn't working.
I was using the modified nvclock (procedure suggested for this bug).
Does anyone have the same troubles?

[asino89 (asino89)]

I'll better explain my troubles.

When I try to use nvclock (eg I launch "sudo nvclock -S 50") i get a "Segmentation fault".
I'm sure this problem came out after the updates to my nvidia graphic card drivers, that I did (through update manager) on 2012-04-12.

I've tried even drivers #173, but it isn't working all the same.

I've tried to reinstall nvclock (even on a brand new installation of ubuntu), but when I launch "make" i get an error like this: "undefined reference to `XextFindDisplay'".

I have no ideas of why this is happening!
Any help will be appreciated!

[TJ (tj)]

The SIGSEGV is being tracked in bug #1039916 "Nvidia driver causing SIGSEGV in nvclock and smartdimmer".

That bug affects the "Fix released" status of this bug since this work-around no longer functions. I've nominated this bug for Precise and Quantal, but any fix of the SIGSEGV issue will be done in bug #1039916.