2

I updated my Ubuntu 12.04 last night to the latest packages.

When I tried to change brightness using Fn Key this morning, brightness went all the way to either min or max brightness. I was not able to set brightness to anywhere in between.

I thought the update may have broken Fn Key, then I tried using the slide in Brightness and Lock screen in system settings. But when I have Brightness and Lock opened, brightness is locked to min brightness no matter I use the slide or Fn key.

P.S. I had no problem with brightness before yesterday.

My hardware is Samsung NP350 Laptop with Intel HD3000.

Thanks

Suhaib
  • 4,171
David
  • 23

8 Answers8

3

I had the same issue, and was able to solve it as follows. In a Terminal (Ctrl+Alt+T) I ran:

cd /etc/modprobe.d

I looked to see what files the /etc/modprobe.d directory contained:

porsche@porsche-300V3A-300V4A-300V5A-200A4B-200A5B:/etc/modprobe.d$ ls -la
total 52
drwxr-xr-x   2 root root  4096 Aug  4 00:33 .
drwxr-xr-x 131 root root 12288 Aug  4 00:54 ..
-rw-r--r--   1 root root  2507 Feb 15 21:03 alsa-base.conf
-rw-r--r--   1 root root   325 Mar 18  2011 blacklist-ath_pci.conf
-rw-r--r--   1 root root  1656 Aug  4 00:33 blacklist.conf
-rw-r--r--   1 root root   210 Mar 18  2011 blacklist-firewire.conf
-rw-r--r--   1 root root   661 Nov 20  2011 blacklist-framebuffer.conf
-rw-r--r--   1 root root   156 Feb 15 21:03 blacklist-modem.conf
lrwxrwxrwx   1 root root    41 Jul 31 13:04 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.conf
-rw-r--r--   1 root root   583 Mar 18  2011 blacklist-rare-network.conf
-rw-r--r--   1 root root  1077 Mar 18  2011 blacklist-watchdog.conf
-rw-r--r--   1 root root    30 May 18 03:03 vmwgfx-fbdev.conf
porsche@porsche-300V3A-300V4A-300V5A-200A4B-200A5B:/etc/modprobe.d$ 
porsche@porsche-300V3A-300V4A-300V5A-200A4B-200A5B:/etc/modprobe.d$

So I edited blacklist.conf by running sudo vi blacklist.conf. (You can also use sudo nano -w blacklist.conf or gksu gedit blacklist.conf.)

I added the following lines to blacklist.conf:

blacklist samsung_laptop
blacklist samsung_backlight

Then I saved the file, and quit the text editor. Afterwards, I applied:

sudo apt-get update

I restarted my laptop and everything is OK right now.

Eliah Kagan
  • 119,640
Jorge Avila
  • 46
0

Try Running Update Manager. Install any and all packages. THEN REBOOT! If this does not work, Try again in a week. If that does not fix it wait for a few weeks and try again. If still this does not fix it I do not know what to say. This is why I do not recommend upgrades. Instead you should re install, start from scratch.

Braiden Hayes
  • 1
0

Im facing the same issue after the system update in a samsung Laptop with the same video adapter. I notice when you reduce the bright with the fn key or through the configuration, the problem appear and the X session crash. Looking forward for a solution. As temporal solution, remove the Dim screen to save power from Brightness and Lock.

Alex
  • 1
0

I had the same problem and fixed it easily as follows:

  1. Restart your machine and press "shift" until the "grub" menu appears
  2. Choose previous linux installation
  3. Choose the kernel version which was just before the last update.

When ubuntu boots, everything should be OK. You need to do this everytime you restart your machine until the bug is fixed in future kernel versions. It seems the latest kernel update had an issue!

Eliah Kagan
  • 119,640
Good Knight
  • 1
0

Notebook NP530U3B:

cat /etc/madprobe.d/blacklist-samsung.conf
blacklist samsung_laptop
blacklist samsung_backlight  #if you have
Eliah Kagan
  • 119,640
Ilya
  • 1
0

The problem is in the new kernel that was installed after you update your system. Just open a terminal window (Ctrl+Alt+T) and type:

gksu gedit /boot/grub/grub.cfg

In the newly opened text editor window you need to comment lines to refer the new kernel (I guess is the 3.2.0.29 version) and stil uncommmented the old version (3.2.0.23). Just save the file and reboot your system, that worked for me and probaly will work for you too!

Eliah Kagan
  • 119,640
Willian Santos
  • 1
0

This Solution is working for me. I hope it would help you.

Mohamed
  • 329
0

I had the same problem on my samsung (QX410, different model). This was fixed by the 3.2.0-31 kernel, so you may want to update again and see if it's gone away.

Here's the bug report:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042311

roadmr
  • 34,802