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 :
http://www.mail-archive.com/devkit-de...@lists.freedesktop.org/msg00219.
** 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 su
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 dect
@ 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
"http://www.linux.it/~malattia/wiki/index.php/Sony-lapt
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 y
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
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
* 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 = '/org/freedesktop/Hal/d
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/
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 manual
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
> 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
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
I reproduced this symptom with debug symbols installed but there is no
files generated in "/var/crash" so I don't think that a report from
apport was made.
--
Pulseaudio and gnome-power-manager crash when unplugging ac power while playing
on a bluetooth headset
https://bugs.launchpad.net/bugs/30
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
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
@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
** Attachment added: "pulseaudio.strace"
http://launchpadlibrarian.net/20326207/pulseaudio.strace
--
Pulseaudio and gnome-power-manager crash when unplugging ac power while playing
on a bluetooth headset
https://bugs.launchpad.net/bugs/306614
You received this bug notification because you ar
here is both strace file of : gnome-power-manager and pulseaudio
NB : I manually killed gnome-power-manager
** Attachment added: "gnome-power-manager.strace"
http://launchpadlibrarian.net/20326182/gnome-power-manager.strace
--
Pulseaudio and gnome-power-manager crash when unplugging ac power
Public bug reported:
This bug appears in Ubuntu 8.10, previous version didn't have this bug.
# my linux version
uname -r
2.6.27-10-generic
# How to produce the bug ? :
1- configure your bluetooth heaset for alsa in ~/.asoundrc :
mine is:
pcm.bluetooth {
type bluetooth
device "00:13:A
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
"HO
I will make my comments on each models :
*** VGN-BZ12XN ***
1- you have 2 backlights interfaces : one from sony-laptop, the other from
acpi, you may have backlight control for it through acpi, or an applet.
2- you have the "sony-laptop" module, correctly associated in hal : "sony vaio
jogdial"
** Description changed:
I have a Sony VAIO VGN-NR230AE. It's a Brazilian VAIO model, not sure
whether it's available in America but in Brazil it's very popular. Right
from the start after installing Ubuntu 8.04 I noticed that only the
volume up, volume down, mute, Pause, Break and Scroll L
Could you please, attach the result of lshal?
I'm going to verify what goes wrong...
For others helpfull informations are available at :
http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-modules.html
Eventually if somebody can try the latest sony-laptop module.
PS : I can confirm that
the use of fn-keys on vaio models depends on the module "sony-laptop"
previously named "sonypi".
so first, verify that the module is correctly loaded.
"lsmod | grep -i sony"
then, the link beetween the fn-keys module and traditionnal keycodes are made
through HAL (Hardware Abstraction Layer ). If
** 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 foun
I have modified my small package to use the full pathbut 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... sinc
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)
htt
this is a duplicate of bug 294667
--
error inserting iwl3945
https://bugs.launchpad.net/bugs/295028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
I have the same bug, same hardware. So I confirm that it is
reproductible
--
error inserting iwl3945
https://bugs.launchpad.net/bugs/295028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
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 workaro
would change, but nothing happend. After I
> installed hal-sony-lcd-wa_0.5-1_i386.deb it still doesnt work. But then I
> change the
>
> /usr/share/hal/fdi/information/10freedesktop/10-sony-laptop-panel-mgmt-policy.fdi
> file and insert my Vaio model like yleetiny above tells and now i
Sorry I said a small mistake in my previous post : if the sony-laptop
module work correctly and your HAL is well configured , you should be
able to see acpi events, since HAL will add the neccessary FN-keys to
your keyboard.
--
Fn keys on VAIO don't produce keystrokes nor ACPI events
https://bugs
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 wor
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
mo
The FN-keys for sony vaios are not linked to acpi, but linked to the
module sony-laptop. As its developper wrote on his wiki, the Fn-keys are
now mapped through HAL (Hardware Abstraction Layer). So it is normal
that there is no acpi event at all. Concerning the brigthness support
see bug 277589, th
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 t
Here is a package to install the new method "sony-smartdimmer" in hal and
hal-info.
It will allows the sony vaio user who can use smartdimmer to change their
brightness, to change their brightness though the gnome-applet, and also have a
functionnal FN-keys.
NB: only a few model will have the F
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 /usr/lib
As I said it is very likely that the files on your computer and mine aren't at
the same place,
but are you using an Ubuntu distribution, because it doesn't seem so, i just
check the differents files in the x86 packages, and they should work.
1- So firstly we need to fix your hal, then reinstall
Sorry,
1rstly, For the backup, and the cp I think the paths are all mixed up,
since i'm using a 64bits version.
to find the files : find /usr -iname
"hal-system-lcd-*et-brightness-linux", backup, and replace them with my
files.
2ndly, I also mess up with the name of your sony-laptop model, you n
Sorry,
1rstly, For the backup, and the cp I think the paths are all mixed up,
since i'm using a 64bits version.
to find the files : find /usr -iname
"hal-system-lcd-*et-brightness-linux", backup, and replace them with my
files.
2ndly, I also mess up with the name of your sony-laptop model, you n
You should do what i wrote in a.sh, then reboot your computer.
you also have to install smartdimmer : " sudo apt-get install
smartdimmer "
if there is any problem, could you post the result of :
lshal | grep -i vgn -B 20 -A 20
please,
Thanks
2008/10/13 benste <[EMAIL PROTECTED]>
> sounds ni
The problem lies in "hal", since the backlight method is wrongly done.
In fact, for every sony laptop, it say to use "echo {1..8} >
/proc/acpi/sony/brightness" instead of using smartdimmer or xbacklight.
Laurent Almeras and I modified some "hal" configuration files to make it work
with smartdimm
The problem lies in "hal", since the backlight method is wrongly done.
In fact, for every sony laptop, it say to use "echo {1..8} >
/proc/acpi/sony/brightness" instead of using smartdimmer or xbacklight.
Laurent Almeras and I modified some "hal" configuration files to make it work
with smartdimm
I can't reproduce this problem too...
Could you please give me the results of this command ?:
grep -i hald /var/log/* > ~/hald_errors.log
which will create a file hald_errors.log in your HOME directory...
Please send us it...
--
LCD brightness setting doesn't work with Sony Vaio VGN-S5M
https:/
@Sebastian
is your issue reproductible after a complete reboot of your PC?
(maybe, there is an issue about hal, if you restart/start it manually when you
are in an X session, i don't know)
If it is reproductible that will means that is a real issue
take us inform!
(sorry for my english i'm sur
Laurent Almeras :
There is a really small bug in your file when I checked them its in your fdi
file :
If you say "laptop_panel.num_levels = 20 (0x15) (int)"
that means the levels will begin from "0" to "19" ( 19-0+1= 20 =num_levels,
that is the difference between the number of levels, and the m
Sebastian Gaul:
My script is not perfect : it overides the applet (in fact it does exactly what
the applet does in a different language).
But i think it still a good thing because :
1- it better respect the security
2- with it Gnome brightness preferences works (when you swith form
sector/battery
Hello, i just make a topic on the developpement on the french ubuntu forum :
here is the link (you'll find other people that uses smartdimmer too, and
maybe test your solution on KDE)
http://forum.ubuntu-fr.org/viewtopic.php?id=185566
2008/1/25, LaurentAlmeras <[EMAIL PROTECTED]>:
>
> My packages
I know where the bug come from :
it's a range issue :
smartdimmer level goes from 1 to 21
hal laptop_panel level goes from 0 to 20 ( the one we want ).
but there is a small bug when you get / set the brightness :
so the lines :
"`smartdimmer -g| awk '{print $3;}`" should become "$(( `smartdimmer -g
Yes it should work on Gusty...
It works for me (VAIO VGN-C2Z_B)
Have you tried the new package of LaurentAlmeras?
I made a small script to set/test your brightness...
Could you try it? (to see what is wrong, the getbrightness/the set Brightness)
** Attachment added: "Little script to set/test t
s to detect correctly de keys...
I hope this will solve your problem
2008/1/24, Sebastian Gaul <[EMAIL PROTECTED]>:
>
> Thank you yleetiny, but nothing changed...
> What I did was installing the package
> http://data.likide.homelinux.org/hal-sony-lcd-wa_0.2-2_amd64.deb, then
>
Sebastian Gaul:
Thanks, i have edited the fdi file to make it work, but i don't know how to
create packages...
but if you want to make it work you can :
1- install the package
2- move the file attached here to :
"/usr/share/hal/fdi/policy/10osvendor/10-sony-laptop-panel-mgmt-policy.fdi "
** Atta
Sebastian : could you post here the result of the command "lshal".
Laurent : I think that commenting out the exit line, will be necessary for some
VAIO model, because the laptop_panel is partially detected as a sony's panel
("linux.sysfs_path"). And thus, it uses it's behaviour ( the "echo" way
Hello, there is a partial solution that you can find here...
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/77739/
Neithertheless, you may need to add your notebook model in the fdi file
to make it works...
PS: Sorry for my poor English, i'm new on launchpad and don't speak very well
englis
Hello LaurentAlmeras!
I just would like to say thanks for your solution...I used it on my Sony Laptop
VGN-C2Z_B...
Indeed I had to modify your file just a little bit...that is to say
1- Add my sony laptop model in the .fdi file by
2- Comment two exits in the other files...
I attach the "diff"
56 matches
Mail list logo
