Backlight on Samsung Q430

[cvfreak]

I have tried every single suggestion to get my backlight working on this laptop. I'm not an expert on linux, but I know a little bit. I have searched the internet for several weeks and have come up with nothing useful.

I have Fedora 14
a Nvidia 310m gpu
latest nvidia driver (260.19.29)

If anyone could help me, I would really appreciate it, because currently I'm only getting about a 2 hour battery life, where I know I can sqeeze about 20-30minutes more if I could decrease the backlight.

Thanks in advance.

[cvfreak]

nobody knows?

[DukeNukem]

http://linuxtweaking.blogspot.com/20...amsung-fn.html

This is a guide I wrote for the Samsung R510/P510 laptop. It should work for you but you need to replace R510/P510 with your laptop model, which is the following,

Q430/Q530

Let me know how you get on.

**Please update your system fully before trying the guide.

[cvfreak]

Thank you for your guide, however its still not working.


When I boot, I can change the brightness at grub and it will stay, however when I try to use the function keys at the desktop, the brightness popup stays at 0 brightness, regardless of what setting I use at grub, or If I boot without touching anything.

[DukeNukem]

I have noticed an error in my guide,

su -c 'cp samsung-backlight.ko /lib/modules/$(uname -r)

it should be,

su -c 'cp samsung-backlight.ko /lib/modules/$(uname -r)/kernel/

Sorry :-)

Its not too hard to fix, open a terminal

cd lib/modules/$(uname -r)

dir

you should see a list of files, confirm that samsung-backlight.ko is in that list

su -c 'mv samsung-backlight.ko kernel/
su -c 'depmod -a'
su -c 'modprobe samsung-backlight'

[cvfreak]

ok. I'll try it as soon as I get home

[cvfreak]

Ugh. I'm at school again, and they updated the network to wpa2 enterprise, so fedora is finicky. It might be a couple weeks before I get to try your fix.

Thank you sooooooo much though. I'm sure your guide will be perfect once i get the chance

Thanks again!

[cvfreak]

ok, got my networking trouble fixed. hopefully. so i run through your tut from scratch, and it outputs the error " No rule to make target `modules' " after downloading. it previously said there was not a /lib/modules/2.6.35.6-45.fc14.x86_64/build so i added that manually and it out put this error. any ideas?

[DukeNukem]

This is why I said update your fedora before running the guide

su -c 'yum -y update'

Reboot if necessary

su -c 'yum install kernel-devel gcc'

now try the make command again

[DukeNukem]

Your grub is fine.

Lets see you 95-keyboard-force-release.rules file.

[cvfreak]

# Set model specific atkbd force_release quirk
#
# Several laptops have hotkeys which don't generate release events,
# which can cause problems with software key repeat.
# The atkbd driver has a quirk handler for generating synthetic
# release events, which can be configured via sysfs since 2.6.32.
# Simply add a file with a list of scancodes for your laptop model
# in /lib/udev/keymaps, and add a rule here.
# If the hotkeys also need a keymap assignment you can copy the
# scancodes from the keymap file, otherwise you can run
# /lib/udev/keymap -i /dev/input/eventX
# on a Linux vt to find out.

ACTION=="remove", GOTO="force_release_end"
SUBSYSTEM!="serio", GOTO="force_release_end"
KERNEL!="serio*", GOTO="force_release_end"
DRIVER!="atkbd", GOTO="force_release_end"

ENV{DMI_VENDOR}="$attr{[dmi/id]sys_vendor}"


ENV{DMI_VENDOR}=="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}=="*Q430/Q530*|*E252*|*N120*|*N128*|*N130*|*N140*|*N148/N208*|*N150*|*N150/N210/N220*|*N220*|*N308*|*N310*|*N510*|*NB30*|*NC10/N110*|*ND10*|*Q210/P210*|*R410P*|*R425/R525*|*R428/P428*|*R460*|*R463*|*R468/R418*|*R480/R431/R481*|*R509*|*R518*|*R519/R719*|*R520/R522/R620*|*R528/R728*|*R530/R730*|*R530/R730/P590*|*R560*|*R580*|*R580/R590*|*R59/R60/R61*|*R59P/R60P/R61P*|*R710*|*R720*|*R780/R778*|*SR58P*|*SR700*|*SR70S/SR71S*|*SX22S*|*X118*|*X120*|*X460*", RUN+="keyboard-force-release.sh $devpath samsung-other"

ENV{DMI_VENDOR}=="Dell Inc.", ATTR{[dmi/id]product_name}=="Studio 1557|Studio 1558", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

ENV{DMI_VENDOR}=="FUJITSU SIEMENS", ATTR{[dmi/id]product_name}=="AMILO Si 1848+u", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

ENV{DMI_VENDOR}=="FOXCONN", ATTR{[dmi/id]product_name}=="QBOOK", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

ENV{DMI_VENDOR}=="MTC", ATTR{[dmi/id]product_version}=="A0", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

ENV{DMI_VENDOR}=="PEGATRON CORP.", ATTR{[dmi/id]product_name}=="Spring Peak", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

ENV{DMI_VENDOR}=="TOSHIBA", ATTR{[dmi/id]product_name}=="Satellite U300|Satellite Pro U300|Satellite U305", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

ENV{DMI_VENDOR}=="Viooo Corporation", ATTR{[dmi/id]product_name}=="PT17", RUN+="keyboard-force-release.sh $devpath common-volume-keys"

# These are all the HP laptops that setup a touchpad toggle key
ENV{DMI_VENDOR}=="Hewlett-Packard*", ATTR{[dmi/id]product_name}=="*[pP][aA][vV][iI][lL][iI][oO][nN]*", RUN+="keyboard-force-release.sh $devpath hp-other"
ENV{DMI_VENDOR}=="Hewlett-Packard*", ATTR{[dmi/id]product_name}=="*[tT][xX]2*", RUN+="keyboard-force-release.sh $devpath hp-other"
ENV{DMI_VENDOR}=="Hewlett-Packard*", ATTR{[dmi/id]product_name}=="*2510p*|*2530p*|HP G60 Notebook PC", RUN+="keyboard-force-release.sh $devpath hp-other"

LABEL="force_release_end"

[DukeNukem]

Looks all good too

I am thinking maybe the samsung-backlight.ko module does not support the Q430/Q530, or we got the wrong product name.

In a console, as root type

dmidecode -s system-product-name

See if it matches Q430/Q530

[cvfreak]

You had it right. it is Q430/Q530.

I searched to see if it worked on ubuntu, but I couldn't find anything on it

[DukeNukem]

http://www.voria.org/forum/

The samsung-backlight.c driver is modded and maintained by Voria, try posting on his forum, ask for your laptop to be added to samsung-backlight module.

Good luck

[cvfreak]

Ok, thank you for your help anyway. I appreciate it very much.