there's no difference between 0x1d8 and 0x01d8 in hexadecimal. This is
like 10 and 010 : leading 0 are not significant (0x is a prefix to
notice hexadecimal number).
472 = 4 x 100 + 7 x 10 + 2 = 1 x 16^2 + 13 x 16 + 8 = 0x1d8 = 0x01d8
--
sony brighness on a geforce series older than 8 (nvclock w
Same question.
My little update on this point :
- the gnome-power-manager bug talked about here is corrected (and was not
related to my patch)
- my patches are still valid : I currently use them on a feisty install
regularly updated.
'/usr/share/hal/fdi/policy/20thirdparty/10-laptop-panel-mgmt
New packages (thanks yleetiny) :
http://data.likide.homelinux.org/hal-sony-lcd-wa_0.5-1_i386.deb
http://data.likide.homelinux.org/hal-sony-lcd-wa_0.5-1_amd64.deb
The num_levels bug affects gnome-power-manager because when it
encounters out of range value at starting, it doesn't set desired
bright
yleetiny : thanks for the new bug report. I agree to help you for your
scripts (tests, packages). You can contact me directly via jabber or
mail to lalmeras %at% gmail.com
Sebastian : very good french. I also have problems with brightness
applet, but I run a beta release so the problem is maybe no
I can't reproduce this problem. I currently use v0.5-1 package.
You can try to remove my package (dpkg -r hal-sony-lcd-wa), verify that
/etc/hal/fdi/policy/10osvendor no longer contains 10-sony-laptop-panel-
mgmt-policy.fdi.
Then see if your HAL initialization error still occurs.
You can also ch
yleetiny : I'm french too. I updated my package with your system name so
the package should work for you (but I don't comment out the exit line
in the panel scripts because it works perfectly here).
Sebastian : I added amd64 package, so you can try it :
http://data.likide.homelinux.org/hal-sony-l
I updated my packages.
- your computer id (VGN-FE48E) is used to enable the smartdimmer use
- I integrate the suggestion of yleetiny to comment out the two exit. They are
harmful because your computers (and not mine) provide a standard and not
working method which disables smartdimmer
Try these
I'm currently running hardy and it works for me (minus new bugs).
Do you try to use the smartdimmer -s command ? Does it work ?
For me Fn key works quite well since a long time (because they are
binded via acpi event scripts to smartdimmer). The fix presented here is
for the hal subsystem (used
1. "And how can I... bind Fn keys... via ...acpi" :
If this doesn't work out of the box for you, I am pessimistic about make it
work. But we can try :
- in a terminal window, run the 'acpi_listen' command
- press your brightness up and brightness up key
- copy the lines printed (here it is :
so
My packages updated :
http://data.likide.homelinux.org/hal-sony-lcd-wa_0.4-1_amd64.deb
http://data.likide.homelinux.org/hal-sony-lcd-wa_0.4-1_i386.deb
(for the persons who use hardy, it seems there's at the moment a problem
with policykit which breaks gnome-power-management lcd brightness
setting
I made a package from my patch, hal-sony-lcd-wa available at :
deb http://deb.likide.homelinux.org/ gutsy/
--
LCD brightness setting doesn't work with Sony Vaio VGN-S5M
https://bugs.launchpad.net/bugs/77739
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
Public bug reported:
Binary package hint: hal
LCD brightness setting doesn't work currently with hal in feisty and
dapper release.
It doesn't work because the scripts hal-system-lcd-{get,set}-brightness-
linux relies on acpi methods. But this computer doesn't support
brightness setting with acpi
Here are the patches.
** Attachment added: "hal-system-lcd brighness patches"
http://librarian.launchpad.net/5579379/hal-system-lcd.patch
--
LCD brightness setting doesn't work with Sony Vaio VGN-S5M
https://launchpad.net/bugs/77739
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Here are :
- a hald fdi policy script
(/usr/share/hal/fdi/policy/20thirdparty/10-laptop-panel-mgmt-policy.fdi) which :
* modifies the hal "laptop_panel.num_levels" property provided by buggy acpi
to replace it with 21 (the correct value for my computer)
* changes the laptop_panel.access_meth
smartdimmer comes from smartdimmer package from main.
It seems to be a good idea to set smartdimmer as a dependency of the hal
package if my solution is accepted. smartdimmer is also a dependency of
acpi-support.
--
apt-cache show smartdimmer
Package: smartdimmer
Priority: optional
Secti
fdi policy file is right. I download it and it is the same I keep here.
The only problem I have is that if I click on the link, Firefox try to
open the file (because it is xml) and only displays text nodes. So I
need to right click and download.
You're right for the shift on brightness value. So t
Filtering on GPU is a bad idea because I think there is also computers
with nvidia chip and correct acpi implementation.
You're right for num_levels.
I have the same problem of brighness going to 0 then going to the right
brightness. It seems to be a gnome-power-manager bug (I don't have this bu
17 matches
Mail list logo
