You are not logged in.
Since I updated the nvidia driver I can't control my brightness.
My laptop is a Samsung RV520 with a Geforce 520M.
The xorg config is the same .
Anyone has the same problem?
EDIT:
Even after I resume from a suspend.
Last edited by archel (2012-10-22 11:47:40)
Offline
I forced the acpi_osi=Linux and acpi_backlight=vendor in the grub2 config and I still have the problem BUT now I can use properly the command "echo 8 > /sys/class/backlight/samsung/brightness" to restore the brightness.
I remember that I couldnìt do it in the previous version, great
Now I need a way to automatically restore the brightness from the suspend/standby.
I'm using samsung-tools-bzr to control the FN-keys but I can't use fn+up and fn+down for the brightness.
Offline
So I did this(well, I just recheked everything):
1.Checked the Xorg file for brightness control (NVIDIA WIKI)
2. Enabled the acpi_backlight=vendor
3. While looking for clues I noticed that I forgot to add to my .xinitrc "xbindkeys" in order to get samsung-tools config load when X starts.
And after I've done step 3, brightness works fine after suspend/standby.
Wonder why it worked fine with the previous driver..maybe because in this realease there is a fix on brightness control for some laptop (like mine I noticed )
Well, I think this is SOLVED
Offline
I don't see how this can be considered a proper solution
I had the same problem with Sony Vaio VPCEH2L1R. After my eyes began to ache because of 100% display brightness, I downgraded xorg-server to 1.12.4 and nvidia to 304.51 and now everything works - without suspicious kernel hacks and weird .xinitrs options. What's with that 'xbindkeys' anyway? Could you please explain?
PS: though I'm a dedicated archlinux user, I've always disliked this thing about rolling release model: shit just breaks without end. Kind of discouraging, considering my mother's been using Samsung laptop with OpenSUSE without any problems.
Last edited by ajaxas (2012-10-21 08:52:50)
Offline
I know this is not a proper solution, that's why I wrote "Well, I think this is SOLVED"
The xbindkeys is used by samsung-tools (bzr version for me from AUR) for the fn-keys (which includes fn+up/down for brightness.. so "something is related").
But really before upgrading the nvidia drivers, everything worked fine.
Now that you mentioned xorg-server.. there was an updated two(?) days ago. So maybe is also xorg fault.
Offline
I see. My Sony Vaio Fn keys work without xbindkeys, except for touchpad on/off key.
Okay, I'll try to find out whether it's nvidia or xorg-server thing.
EDIT: yes, it's nvidia all right. Dunno if I should file a bug report or whatever...
Last edited by ajaxas (2012-10-21 14:01:02)
Offline
Don't know either I kinda solved my problem.
Offline
It's a bug, so file report.
Offline
I don't think it's an archlinux related bug. Nvidia driver is a proprietary blob, and I don't want to write *there*.
I could relate to the package maintainer, of course.
Or I could've bought a laptop without Nvidia graphics card -___- Intel HD3000 is more than enough, really. Bullocks.
Offline
Ok, I have the same problem today... So there's something wrong in this driver version
Bug reported
Last edited by archel (2012-10-22 12:16:03)
Offline
Ok, I have the same problem today... So there's something wrong in this driver version
Bug reported
It's quiet over there. And old nvidia module doesn't work with linux-3.6.3 for me -_-
Was there a reply from our own Evil Inc.?
Offline
Look at the wiki:
https://wiki.archlinux.org/index.php/NV … on_laptops
Offline
Look at the wiki:
https://wiki.archlinux.org/index.php/NV … on_laptops
You don't say?
[ajaxas@r2d2 ~]$ cat /etc/X11/xorg.conf.d/10-display.conf
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "1"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
Option "NoLogo" "1"
Option "ConnectedMonitor" "DFP"
#Option "RegistryDwords" "EnableBrightnessControl=1"
Option "RegistryDwords" "EnableBrightnessControl=1; PowerMizerEnable=0x1; PowerMizerLevelAC=0x3; PowerMizerLevel=0x3"
Option "OnDemandVBlankInterrupts" "1"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
Option "MetaModes" "1366x768_60 +0+0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
The thing is: it works with 304.51, but doesn't work with 304.60. I consider such behavior wrong.
Offline
That's strange. I have a Samsung RV511 laptop and brightness setting has never worked for me with the official nvidia driver. Nvidiabl from AUR solved the problem.
Last edited by zxz (2012-10-27 09:44:55)
Offline
That's strange. I have a Samsung RV511 laptop and brightness setting has never worked for me with the official nvidia driver. Nvidiabl from AUR solved the problem.
Dunno. I've got Sony, and it just works.
On the other hand, that depends. It didn't work with XFCE (i.e. it worked and then it didn't work and worked again another day with no apparent reason - I consider this as "didn't work"), but worked with KDE without a single problem till now.
Offline
Did anyone try the new nvidia driver 304.64?
http://www.geforce.com/drivers/results/51453
I can't test it on my system because I'm out of my town for a few days, but I think they fixed the brightness issue.
Offline
Did anyone try the new nvidia driver 304.64?
http://www.geforce.com/drivers/results/51453
I can't test it on my system because I'm out of my town for a few days, but I think they fixed the brightness issue.
Same shit
Responds to 'echo X > /sys/class/backlight/acpi_vendor0/brightness', but KDE hotkeys and applets don't work.
Sorry to disappoint you.
Offline
Same here. 304.64 didn't fix the problem, broken since 304.51
Offline
archel wrote:Did anyone try the new nvidia driver 304.64?
http://www.geforce.com/drivers/results/51453
I can't test it on my system because I'm out of my town for a few days, but I think they fixed the brightness issue.
Same shit
Responds to 'echo X > /sys/class/backlight/acpi_vendor0/brightness', but KDE hotkeys and applets don't work.
Sorry to disappoint you.
Oh gosh.. sad to hear that
I hope they fixed my notebook
Selo what's your pc spec?
Offline
I am using Ideapad Y530
Offline
This whole situation makes me wonder: just how does udev handle brightness control? If not via /sys interface?
Or is it not udev at all? As (I think) I've mentioned earlier here, my laptop's brightness Fn combinations hadn't worked with XFCE, but they do work with KDE. So it is possible KDE handles Fn keys independently of udev.
And if so, could it be not a nvidia driver bug per se (since brightness can be adjusted via /sys), but an issue of KDE/nvidia interaction caused by some changes in nvidia?
Can anyone comment, please?
Offline
an issue of KDE/nvidia interaction caused by some changes in nvidia?
That would be my guess. The changes in nvidia are documented even - from the 304.60 changelog:
Added support for the "Backlight" RandR output property for configuring the brightness of some notebook internal panels.
Offline
@Gusar
Nvidia even claimed to have fixed something similar in 304.64:
Fixed a regression in backlight control functionality on some notebook configurations.
but not for me.
Btw, people all over the Internet are weeping as well, example: http://www.nvnews.net/vbulletin/showthr … ?p=2579087
Offline
Yeah there was a genuine regression, but it's now fixed. You said it yourself that the problem is only in KDE. So the driver is now fine, it's KDE that got tripped up by the change in the 304.60 driver, and it's KDE that will need to adapt to it.
Last edited by Gusar (2012-11-10 16:32:48)
Offline
Yeah there was a genuine regression, but it's now fixed. You said it yourself that the problem is only in KDE. So the driver is now fine, it's KDE that got tripped up by the change in the 304.60 driver, and it's KDE that will need to adapt to it.
This sounds sane.
Unfortunately, this doesn't make things easier at all.
EDIT:
Okay, I updated this bug: https://bugs.kde.org/show_bug.cgi?id=308757 and hope people in KDE will do something.
It's so sad to be totally unqualified.
Last edited by ajaxas (2012-11-10 17:40:35)
Offline