I figured out a workaround... oke it's more sort of a hackaround :P
I created a systemd service which fires of a script that sets the brightness level once on startup. Technicaly the service systemd-backlight@backlight:intel_backlight should take care of saving and setting the backlight levels on shutdown/startup, but this seems to be broken at the moment. According to some recent archlinux forum posts there has been quite a deal of hacking going on in the kernel code handling this.
Here are the two files i created
/usr/lib/systemd/scripts/set_brithness (remember to make this executable with chmod 750
#!/bin/bash
echo "250" > /sys/class/backlight/intel_backlight/brightness
And
/usr/lib/systemd/system/set_brithness
[Unit]
Description= Set brightness to a reasonable level on start-up, since systemd backlight@backlicht:intel_backlight is broken for the moment.
[Service]
Type=oneshot
ExecStart=/usr/lib/systemd/scripts/set_brightness
[Install]
WantedBy=multi-user.target
I have ttestedit with a simple reboot but do not know how it behaves on hibernate/suspend. Also, thisas a little glitch Gonme Settings do not keepttrackof this change. If you open monitor cconfiguration it will set bthebrightnessto the last value it knew about. Same thing with Functionkeys. But I can live with this for now. I will also hit the Arch Forums with this, to further investigate this and maybe file a bug.
On my T410, this changes gamma, not brightness. They are not the same thing. – Laszlo Valko – 2014-09-06T22:36:13.737
I can confirm this. It does not change brightness, it changes gamma, what results in a change of brighness in the displayed image but not in backlight brightness. – paradoxon – 2014-09-07T12:08:42.207
Sorry, I didn't know there was difference. How about using redshift? It changes your screen color temperature during the day so your eyes don't hurt. Also you can set up your prefered brightness and additionally correct gamma. – ioku – 2014-09-07T15:35:39.227