Have just installed Ubuntu Lucid Lynx (10.04) and unsurprisingly FN
brightness keys didn't work. Just to remind that I have Sony FE31HR with
Nvidia 7400 on board. Solution #112 leads exactly to benste's problems
(#113). Also I tried the following solution (it is one solution in forum
posts):
** Branch linked: lp:ubuntu/hal
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It seems that devicekit-power won't support the backlight, so I revert to HAL
use even if it's depreciated.
For those who wants backlight support in Karmic, here are the 3 modified files
(work in xubuntu 9.10).
Reference :
Hi,
firstly, sorry for not debbugging the issue in Karmic (sony laptop used for
work), so this post is purely informative, but may help the debbuging
process.
To better understand we the bug should be here is some technical infos :
1- sony_laptop (module): handle the Hardware-software FN keys
** Bug watch added: GNOME Bug Tracker #593933
https://bugzilla.gnome.org/show_bug.cgi?id=593933
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Sun, Nov 08, 2009 at 09:54:52AM -, yleetiny wrote:
So maybe, we should install udev-extras, test it, if it doesn't work : get
the source and modify it to match the HAL file
(30-keymap-module-sony-laptop.fdi)
udev-extras is no longer a separate package; all of these keymaps are
included
Hi,
I can confirm that the bug is still present on Karmic stable - HAL 0.5.13
(fresh install on FE31M).
I fixed it changing the file /usr/share/hal/fdi/policy/10osvendor/10
-sony-laptop-brightness.fdi at line #160:
from
remove key=info.addons type=strlist/remove
to
remove key=info.addons
Hi Steven, ylethiy and co, Ive just upgraded to karmic Beta/ RC, and the
original bug is still present, although FN key feautures has been
significantly improving (e.g. S1 key now has an own event)
But as brightness diming with and without your nvidia driver still
doesn't work I've tried your 0.4
Hi simram, I'm sry to say, but I have to inform you that you picked the
wrong report, as the topic is already saying this thread is not about
Nvidia Grafic Cards in 8 or 9 series it's only about 7 and older
Binary package hint: hotkey-setup
seperatred bug from:
Sony + Intel --
This bug was fixed in the package hal - 0.5.13-1ubuntu2
---
hal (0.5.13-1ubuntu2) karmic; urgency=low
[ Steve Langasek ]
* debian/patches/series: add debian/patches/04_nvidia_brightness.patch so
it actually gets applied.
* debian/patches/04_nvidia_brightness.patch: copy
I guess someone tested in Karmic ?
Could so explain me what exactly happened now?
Does debian/patches/series: mean that it was fixed within debian and
now imported, or does it mean that it is a debian based system and
yleetiny's patch which is working for me now has been applied ?
--
sony
Actually, it's not fixed at all. The hal upload includes my previous
attempt at fixing this, which feedback says doesn't fix it after all.
Sorry, resetting the bug state.
** Changed in: hal (Ubuntu)
Status: Fix Released = In Progress
--
sony brighness on a geforce series older than 8
ahh im glad i found this thread, I installed jaunty on my sony AW series vaio
(nvidia 9300m GS) - and the built in gnome brightness control had a cross over
it and was ineffective -
so i have been using smartdimmer (preinstalled) to change it manually - but
this gets tedious to use terminal
maybe also another post you may want to look at
http://ubuntuforums.org/showpost.php?p=3553350postcount=8
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs,
Hello,
I have a Sony Vaio VGN-AR41E, which has an NVidia GeForce 8400M GT graphics
card.
Smartdimmer works for me, and the Fn keys work now too (as of Karmic Alpha 4).
Will your fix work for me? I do not see my card in the .fdi file.
--
sony brighness on a geforce series older than 8 (nvclock
Sorry, I didn't realise this wasn't for my card.
Still, 8400M GT doesn't work either.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@yleetiny,
first solution to move /usr/share/hal/fdi/policy/10osvendor/10-sony-
laptop-brightness.fdi to /usr/share/hal/fdi/preprobe/20thirdparty
does not work.
But the second (to move 10-sony-laptop-brightness.fdi to
/usr/share/hal/fdi/preprobe/10osvendor/) WORKS!
Also I've found out that
Can people please test whether the attached file written to
/usr/share/hal/fdi/policy/10osvendor/10-sony-laptop-brightness.fdi,
together with an otherwise unmodified set of hal fdi files, also works?
I believe this is what the earlier hal upload was aiming for, and fell
just short of.
If it
** Branch linked: lp:~ubuntu-core-dev/hal/ubuntu
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Sun, Aug 02, 2009 at 04:49:27PM -, Alex wrote:
According to the rules it should match the second udi (the
backlight),and as the udi does not contain linux.sysfs_path then
necessary attributes should be added. But on my (and most likely
benste's) config it does not. May be there is a bug
@Steve,
I have completely reinstalled hal package (previously removed all *.fdi
files) and saved 10-sony-laptop-brightness.fdi to
/usr/share/hal/fdi/policy/10osvendor/ and it does not work for me.
Here is the output:
de...@defue-laptop:~$ hal-find-by-property --key info.category --string
Alex,
Did you restart hal after adding the new fdi file?
What is the output of lshal -u /org/freedesktop/Hal/devices/computer on
this system? I haven't seen a reference yet showing which Sony chip you
have.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
Yes I restarted hal.
here is the out:
de...@defue-laptop:~$ lshal -u /org/freedesktop/Hal/devices/computer
udi = '/org/freedesktop/Hal/devices/computer'
info.addons = {'hald-addon-cpufreq', 'hald-addon-acpi'} (string list)
info.callouts.add = {'hal-acl-tool --remove-all',
@ Steve,
It should a good thing to leave the sysfs path, but the thing is that nearly
everything vaio specific rely on the sony-laptop module. The issue here is
that the backlight device is created with a sysfs path for every viao (see
Here is a new version of
/usr/share/hal/fdi/policy/10osvendor/10-sony-laptop-brightness.fdi which
should work.
I just removed the linux.sysfs_path for all model to do the trick.
Can somebody test it ?
@Alex : Thanks a lot for your highlights
@benste :
I did not try on Karmic. Since I do not
@yleetiny: It didn't work for me. linux.sysfs_path was still presented
in lshal and brightness changing didn't not work.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of
On Sat, Aug 01, 2009 at 09:17:54AM -, Alex wrote:
* and looked through my output of the following command:
de...@defue-laptop:~$ hal-find-by-property --key info.category --string
laptop_panel | xargs lshal -u
udi = '/org/freedesktop/Hal/devices/computer_backlight'
info.addons =
Steve, I tried to change brightness with this solution in a guest session and
it worked perfectly.
So what do you mean by It will also break backlight handling for all other
users, so this isn't a
patch that we can include in the archive. ?
+ do you know which date would be deadline for karmic
@Steve,
You are absolutely right on all your points.
I have 2 related to the bug udi:
1) Nvidia card pci
udi = '/org/freedesktop/Hal/devices/pci_10de_1d8'
info.linux.driver = 'nvidia' (string)
info.parent = '/org/freedesktop/Hal/devices/pci_8086_27a1' (string)
info.product = 'G72M
I was hoping that I've done the trick. The issue is that the
10-laptop-panel-mgmt-policy.fdi is loaded before
10-sony-laptop-brightness.fdi (which delete the wrong sysfspath).
Thus There is two solutions :
1- force the evaluation of 10-sony-laptop-brightness.fdi before the other
by changing its
Maybe solution 1 : Could somebody try to move
/usr/share/hal/fdi/policy/10osvendor/10-sony-laptop-brightness.fdi
into /usr/share/hal/fdi/preprobe/20thirdparty or if it is not working
/usr/share/hal/fdi/preprobe/10osvendor/ ?
(obviously after moving it restart HAL or the computer)
2009/8/3 yohan
* Thanks a lot Alex for your help, I think that I now understand what is wrong.
* On my computer HAL workaround is working, here is the infos on my device.
yleet...@vaio-vgnc2zb-yohan:~$ hal-find-by-property --key info.category
--string laptop_panel | xargs lshal -u
udi =
I got it working!!!
So, here is my investigation:
1) I have exactly the same
/usr/share/hal/fdi/policy/10osvendor/10-laptop-panel-mgmt-policy.fdi as you
attached, so renaming it has no effect.
2) I've carefully looked through the 10-laptop-panel-mgmt-policy.fdi file:
?xml version=1.0
Hi, I'm not sure what's my problem whether it's the same or not, so I
attached output of the fdi file, and the hal output.
I guess yleetiny your working on smartdimmer 0.5 as far as you know the bug ?
---
2nd part:
I installed sonysmartdimmer 0.4 again, and now I can change the value up to
thx a lot alex, tried some combinations of values in the above named
file and ended up with the folling working configuration:
START - WORKAROUND
/usr/share/hal/fdi/policy/10osvendor/10-laptop-panel-mgmt-policy.fdi
[...]
!-- for the generic sysfs interfaces --
match
sry again, i just messed up your text, the config is the same in your
uploaded fdi file.
@yleetiny: I don't know what this change affected, but is it possible to
modify your package so that the workaround is applied, and the sony-
smartdimmer package may be inserted in main release for karmic?
+
@benste,
you did all right. I messed up values in the last line. Ofcource it should be
1: exists=false, 2: exists=true as it is in the attachment.
@yleetiny
To summarize the bug. Sony-smartdimmer_0.4.deb doesn't work for benste and me
because in
Hi! I am experiencing the same behaviour/problem as benste has. My
laptop is VGN-FE31HR on Jaunty 64bit. I've installed sony-
smartdimmer_0.4.deb (#67) and here is outputs:
de...@defue-laptop:~$ hal-find-by-property --key info.category --string
laptop_panel | xargs lshal -u
udi =
Today the keys change from fully dimmed to not dimed but there are only
2 steps - I need the 21 steps back (or has this been caused by compiz
shortcuts?)
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug
No workaround yet?
I thought you're aware of the exact failure :-)
Does the case that HAL will be dropped for 9.10 (for
https://fedoraproject.org/wiki/Features/DeviceKit#How_To_Test) take
affect on all this resaerach?
--
sony brighness on a geforce series older than 8 (nvclock works fine)
I noticed that lshal | grep primary_video.product returned :
system.hardware.primary_video.product = 472 (0x1d8) (int)
for my NVidia 7400 GO (sony viao VGN-C2Z_B)
but in the 10-sony-laptop-brightness.fdi file the 7400 GO is referenced as
0x01d8
Does this difference (0x1d8 vs 0x01d8) has any
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
Sorry guys,
I don't really understand why it is not working, but you have to uninstall
the previous version of the package first, or maybe the paths I use are only
for 64bits.
I'm sorry, but I don't have a lot of time to help you for now.
So, could you extract the package, and try to install
yleetiny,
It would help us to get this integrated into Ubuntu 9.04 as an SRU if
you would provide a diff against the hal package, rather than a stand-
alone .deb; we need to be able to integrate this into the hal package,
instead of having a separate nvidia-specific package.
--
sony brighness
I'll give it a try asap maybe this evening.
The 64bit path only is the most appropriate in my opinion.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which
The first deb worked on my system - which is not a 64-bit system. I
have not had an opportunity to test the second.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of
I guess I could be a lot more specific. My system is:
Sony VGN-S480
Centrino 2.0Ghz
nVidia GeForece Go 6200
The deb sony-smartdimmer_0.3.deb worked, except the limitations I
noted earlier. I have not tried 0.4 yet.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
Yes, you're right .diff files are better.
It's just that I forgot to backup the previous files, so I cannot generate
them asap.
You'll here find there the 3 files that I modified.
their paths are /usr/lib/hal/scripts/linux and
/usr/share/hal/fdi/policy/10osvendor
Just diff them for me.
2009/5/5
Hi yleetiny,
As for Benste your latest fix (0.4) didn't work for me neither...
Fn + F5/F6 have no effect...
The command smartdimmer -s 20 works well.
Thanks again for your work.
O-p
--
sony brighness on a geforce series older than 8 (nvclock works fine)
smartdimmer -s 15 is the minimum :-)
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Sorry, I didn't test my package, there was wrong path and name for the fdi
file.
Here is a new one.
2009/5/3 jcialdea j...@jimbodude.net
That package fixes the main issue for me - the hotkeys now control the
brightness. Thanks yleetiny.
However - I do not have 18 brightness levels when
Hi yleetiny, thanx for your latest fix but V 0.4 didn't work for me
The status bar is now able to be moved, but only until half of the size
And there is no influence on the actual brighness.
You're using smartdimmer and not nvclock aren't you?
--
sony brighness on a geforce series older than 8
Strangely 0.3 doesn't work for me at all.
Does I have to reinstall hal first?
(using 7600go on a vaio)
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs,
Sorry guys, I thought the bug was already solved.
I made a quick fix. What differs from original distribution version is :
1- I only make 18 levels since for me smartdimmer goes from 15 to 100 with a
step of 5.
2- I removed the sysfspath of the backlight card (that sony-laptop wrongly
creates).
That package fixes the main issue for me - the hotkeys now control the
brightness. Thanks yleetiny.
However - I do not have 18 brightness levels when using the hotkeys - I
have 5 - but the 5 levels seem to cover the full brightness range.
Also, the brightness notification pop-up does not show
The case where the panel does not exist at all in lshal is handled in
bug 345531. The original issue was fixed in hal (see comment 38), thus I
close this again.
** Changed in: hal (Ubuntu Jaunty)
Status: Triaged = Fix Released
** Changed in: hal
Status: New = Invalid
--
sony
No, this is *not* fixed.
** Changed in: hal (Ubuntu Jaunty)
Status: Fix Released = Triaged
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So if it's fixed, do know when this willl be updated to default jaunty?
cause I want to use my battery live :-)
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
I agree - comment 38 does not provide a fix to this issue. See the
duplicate #355984 for a more concise description of the issue.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a
did you read this thread???
pls try
smartdimmer -s 15
and
acpi_listen clicking an fn key afterwards.
If both works you've got the same bug FN keys are working ! brightness
changeing is working BUT HAL doesn't handle it right so that gpm and you
FN keys doesn't trigger the smartdimmer ewvent
Hi everyone,
In Ubuntu 8.10 I could see the brightness bar but without any effect
but, at least, I could see it. I've just upgraded to 9.04 and now I can
change the brightness through the terminal with smartdimmer but,
curiously I can't see the brightness bar. So is it working in the right
Please hold on, for 8.10 the patch is attached. thx to ylethy
for 9.04 (like me) the bug is known and will be fixed asap thx to Steve
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are
Today I've installed kubuntu 9.04 Beta on my Sony VAIO FE31Z laptop and
I've updated to the latest packages to April, 15 2009 and I can't change
the brightnes on it, Fn keys are not doing anything.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
Steven, is there anything new? Jaunty release is close and it would be nice to
see this fixed.
You just wait for Martin or?
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member
if your laptop panel doesn't show up at all in lshal output, then that's
another wrinkle entirely - you may have a completely separate bug than
benste. I'm going to un-dupe bug #345531, please follow up to that bug
for your case.
--
sony brighness on a geforce series older than 8 (nvclock works
Schmirrwurst, try xev or acpi_listen in a terminal to look whether
keys are working for you.
@ Steven:
ben...@vaio-fe31m:~$ apt-cache show smartdimmer
Package: smartdimmer
Priority: optional
Section: utils
Installed-Size: 132
Maintainer: Ubuntu MOTU Developers ubuntu-m...@lists.ubuntu.com
Ok, I've confirmed the problem here. The following setting:
info.addons = {'hald-addon-generic-backlight'} (string list)
is not what we wanted, we wanted
org.freedesktop.Hal.Device.LaptopPanel.method_names =
{'SetBrightness','GetBrightness'} (string list)
and I can see how the patch that
$ acpi_listen
((bright down))
sony/hotkey SNC 0001 0010
sony/hotkey SNC 0001 003b
((bright up))
sony/hotkey SNC 0001 0011
sony/hotkey SNC 0001 003b
the command hal-find-by-property --key info.category --string laptop_panel |
xargs lshal -u
udi =
You've got different output to mine, maybe the keys are not recognized
by HAL ?I've got the exact same output on my system,
sony/hotkey SNC 0001 0010
sony/hotkey SNC 0001 003b
sony/hotkey SNC 0001 0011
sony/hotkey SNC 0001 003b
which Ubuntu version do you use?
I use jaunty, it is an update version from alpha 4
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
benste,
Which version of smartdimmer do you have installed? The patch applied
to hal expects smartdimmer 0.8b4-1ubuntu2 or newer.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a
I've the following versions :
hal 0.5.12~rc1+git20090204-0ubuntu4
smartdimmer 0.8b4-1ubuntu2
There is still no reaction on fn keys...
--
sony brighness on a geforce series older than 8 (nvclock works fine)
I've also tried smartdimmer on command line, and it is working
properly...
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On Sun, Mar 29, 2009 at 05:35:55PM -, Schmirrwurst wrote:
I've the following versions :
hal 0.5.12~rc1+git20090204-0ubuntu4
smartdimmer 0.8b4-1ubuntu2
There is still no reaction on fn keys...
Please post the output of the following
Hi, as the original reporter :-) I'm back again,
Today I installed Jaunty on my FE 31 m, using the geforce 7600go
As you've read before Ylethies patch solved this issue during 8.10, but
in jaunty it doesn't work.
smartdimmer is preinstalled on my system, and works fine using -s -g -d and -i
so
If the new release from smartdimmer is not released for jaunty, could it be
possible to make hal use the nvclock binary for geforce8+ cards ?
The working nvclock binary is now released and working. So user could install
nvclock pkg and have fn keys working... better than nothing...
--
sony
the new smartdimmer is already in jaunty.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
What do you mean with after beta ?
Will it be ready for jaunty ?
Is there somewhere where I could check the state from the MIR Team work ?
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you
Thus far no version of the nvclock package in Ubuntu has provided
smartdimmer. This will be implemented after beta, with the permission
of the MIR team; the hal implementation expects the smartdimmer from
nvclock, which has different semantics than the one currently in the
archive (in addition to
I merged Steve's branch. The patch needs to be sent upstream, and most
likely the fdi file will go to hal-info, but that's not urgent.
** Changed in: hal (Ubuntu Jaunty)
Status: Confirmed = Fix Committed
--
sony brighness on a geforce series older than 8 (nvclock works fine)
We'll pursue the forward route and not revive the acpi-support bits.
** Changed in: acpi-support (Ubuntu Jaunty)
Status: Confirmed = Won't Fix
** Changed in: acpi-support (Ubuntu Jaunty)
Assignee: Steve Langasek (vorlon) = (unassigned)
** Changed in: acpi-support (Ubuntu)
This bug was fixed in the package hal - 0.5.12~rc1+git20090204-0ubuntu4
---
hal (0.5.12~rc1+git20090204-0ubuntu4) jaunty; urgency=low
[ Steve Langasek ]
* debian/control: Recommend: smartdimmer for sony backlight support.
* 88_nvidia_brightness.patch: add a new sony-nvidia
I've updated today the hal version mentioned above, and try fn keys
first with the latest nvclock b4 that has now been released, and because
it didn't work, I tried then with smartdimmer after uninstalling
nvclock, doesn't work...
--
sony brighness on a geforce series older than 8 (nvclock works
Ok, I think I've undersand, the new nvclock b4 package is not providing
smartdimmer anymore, and the smartdimmer package has not yet been update
(0.1-2build1), is that right ?
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You
yleetiny, thank you *very* much for your work on this bug! I've
reviewed the package you prepared, and converted this into a patch
against the hal package which is now published in the bzr branch linked
from the top of this report. I'm waiting for Martin Pitt (hal guru) to
review this before we
This bug properly belongs to hal, not to nvclock; the issue is hal not
having a correct method for setting the backlight brightness on these
systems, which requires either nvclock or smartdimmer. Reassigning.
Since nvclock is in universe (and at least the binary is likely to stay
there for
per duplicate bug #345531, if hal is not going to be fixed in time for
jaunty, the sony brightness script should be re-adde to acpi-support.
** Also affects: acpi-support (Ubuntu)
Importance: Undecided
Status: New
** Changed in: acpi-support (Ubuntu Jaunty)
Importance: Undecided =
Note: *complete* resolution is dependent on bug #95444, but smartdimmer
is already present in main and I expect will be the preferred interface
in main for jaunty whether or not we update to the version from the
nvclock source, so the hal side of this can be worked on in parallel.
--
sony
There is no need to a file to increase backlight since you only need to know
how to get and set the correct value.
Since you made a script on for sony vaio geforce 8, it seems to me that your
last post is solved.
The problem in the script above is the sudo use, it seems you need to use the
I can confirm it unfortunately doesn't work for the Vaio VGN FZ31M.
Furthermore, fn+F5 or fn+F6 doesn't even bring up the brightness OSD
anymore when it did before (even though it didn't do anything obviously,
which is the problem that brings us together here).
--
sony brighness on a geforce
To renato neves and axx
Sony Vaio VGN FZ31M have a Geforce 8400 series, this bug report only treats the
geforce 6/7 series.
You should report on the bug 95444
Some workaround exists there using the cvs version of nvclock
--
sony brighness on a geforce series older than 8 (nvclock works fine)
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
HI
mine doesn't work too. my model is :
system.hardware.product = 'VGN-FZ31M' (string)
Cheers
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of
My debian file only work for a listed vaio models,
could you please give me the result of
lshal | grep -i vgn
please?
I will add your model asap
PS: I'm searching for a way to better match all geforce 6/7 series, but
i don't know how i can make it. Until this math isn't done only a few
Here is a new deb file.
I change the matching method so that it should work for every vaio using a
Geforce 6/7 Go .
** Attachment added: sony-smartdimmer_0.2.deb
http://launchpadlibrarian.net/18694638/sony-smartdimmer_0.2.deb
--
sony brighness on a geforce series older than 8 (nvclock
Could someone assign this bug to hal and hal-info, please?
I made a .deb to make the different modifications necessary to have both FN
hotkeys and brightness control possible.
It will relies on smartdimmer instead of nvclock, since i cannot nvclock
though hal
The use of hal is better than the
** Also affects: hal
Importance: Undecided
Status: New
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've installed the .deb file on Intrepid on a Vaio FE31Z but still I
can't change the brightness with the Fn keys.
--
sony brighness on a geforce series older than 8 (nvclock works fine)
https://bugs.launchpad.net/bugs/277589
You received this bug notification because you are a member of Ubuntu
I make some diff files for the scripts, you should just reinstall hal
and hal-info ( sudo aptitude reinstall hal hal-info )
then patch them with the commands :
sudo
patch /usr/lib/hal/scripts/linux/hal-system-lcd-get-brightness-linux
hal-system-lcd-get-brightness-linux.diff
sudo
patch
First of all thank you again for your ideas and actiosn,
but sadly again it doesn't work.
I realized after last patch from your site brightness window on key press
dissappeared, but after the next update - including lot of acpi data! it was
back but now my maximum is about 2/5 of the full size
1 - 100 of 121 matches
Mail list logo
