dmidecode=SQ45S70S

[saulus]

Hi,

your tools are just great. I didnt knew about them for the last two years and wasted a lot of time trying to fix the issues by myself.

Sadly the brightness-up and brightness-down key do not do anything since I installed the packages samsung-backlight samsung-tools and samsung-wireless. Before I saw the notice from gnome about the keypress, which now has disappeared.

Im running ubuntu lucid x-64 on a Samsung Q70. My exact hardware specification:

$ uname -a
Linux subb 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux

$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port [8086:2a01] (rev 03)
00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03)
00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03)
00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03)
00:1f.2 IDE interface [0101]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller [8086:2828] (rev 03)
00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 03)
01:00.0 VGA compatible controller [0300]: nVidia Corporation G86 [GeForce 8400M G] [10de:0428] (rev a1)
02:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)
03:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8039 PCI-E Fast Ethernet Controller [11ab:4353] (rev 15)
04:09.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b4)
04:09.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 09)
04:09.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 18)
04:09.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 09)
04:09.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev 04)

$ sudo dmidecode -s system-product-name
SQ45S70S

Do you have any suggestions?

Kind regards,
SauLus

[voria]

Your model is already supported by the packages on the repository, so everything should work good...
Please attach here your dmesg, maybe there are useful informations to find where is the problem.

[saulus]

I must add I have a "special" Q70. On the sticker on the backside only NP-Q70 is written, which made the samsung support wonder, once. This is because I ordered this laptop 2 weeks before it was sold for the first time. Maybe it has some other hardware, I dont know.

[saulus]

Sadly the brightness-up and brightness-down key do not do anything since I installed the packages samsung-backlight samsung-tools and samsung-wireless. Before I saw the notice from gnome about the keypress, which now has disappeared.

The problem has changed a bit and is given with more details as follows:

Every key I have tested so far works great (suspend, energy, shutdown screen backlight, mute, fan speed, bluetooth, wireless lan, touchpad, and the volume keys), except for the brightness keys. FN+up and FN+down are recognized and I again see the notification of the screen is getting darker/brighter but nothing happens.

My Bios 11ST, as it is recommended very often to make the function keys work.

[voria]

Looking at your dmesg everything seems ok.
Please try to add the option 'acpi_backlight=vendor' to the grub kernel command line (for instructions on how to do this, take a look here).

[saulus]

I added the option to grub but nothing changed:

$ grep vendor /boot/grub/grub.cfg
linux /boot/vmlinuz-2.6.32-22-generic root=UUID=89587b4e-e061-457b-941f-1380f668864d ro crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_backlight=vendor

Using FN+up/down still shows the display brightness change notification but actually the brightness does not change. The only possibility to change the brightness still is by using smartdimmer.

I added a new dmesg output. The packages are updated, including your new packet from today.

Thank you in advance,
SauLus

[voria]

Other users have had the same problem on a N510 netbook, shipped with a nvidia card.
It turns out the problem was in the BIOS and the problem was fixed by upgrading it to latest version.
The only suggestion I can give you is to update your BIOS if a newer version is available... if you are already using the latest version, then I'm afraid there is not much we can do...

[saulus]

It turns out the problem was in the BIOS and the problem was fixed by upgrading it to latest version.
The only suggestion I can give you is to update your BIOS if a newer version is available

Yes, there are newer bios' available. As I said I'm using the bios 11ST but there is at least 17ST available. I often have read it is not good to uprade the bios since the function keys then do not work at all. I also had the 17ST running a while ago and the function keys had to be corrected by a call like

setkeycodes e008 225 e009 224

However, there maybe hope as I can see from these posts:

http://www.doof.me.uk/2010/02/20/samsun ... ux-2-6-32/
http://what-ho.posterous.com/linux-hotk ... ng-laptops

I will try the bios update and the 2.6.32-tweaks soon.

What for packages do I really need for the function keys and your packages to work? I installed hal and acpi*. I'd like to remove them if they are of no need.

Tyia,
SauLus

[voria]

I often have read it is not good to uprade the bios since the function keys then do not work at all. I also had the 17ST running a while ago and the function keys had to be corrected by a call like

setkeycodes e008 225 e009 224

However, there maybe hope as I can see from these posts:

http://www.doof.me.uk/2010/02/20/samsun ... ux-2-6-32/
http://what-ho.posterous.com/linux-hotk ... ng-laptops

I will try the bios update and the 2.6.32-tweaks soon.

The setup of the keys is now correctly handed by udev packages available on my repository, so you don't need to edit udev files as described in the link you posted.

What for packages do I really need for the function keys and your packages to work? I installed hal and acpi*. I'd like to remove them if they are of no need.

You don't need to install anything by hand, when you install packages from my repository, if there is any other package needed as dependency it will be automatically installed.
Anyway, hal support has completely been dropped and it's no more needed in lucid, so you should remove it.

[saulus]

I had time to try the latest bios 17ST but it did not change anything compared to 11ST. It took me several hours to downgrade and then I tried 05ST, the most erly bios I got and the 09ST, which is often refered to as the best bios version. 10ST and 11ST are said to have a bug regarding the brightness keys.

see https://wiki.edubuntu.org/LaptopTesting ... SamsungQ45

My brightness keys now change the brightness from the early beginning of the bios, over grub, and during the boot sequence of linux. But this stops at the time when gdm starts.

Using acpi_backlight=vendor then the situation does not get better and the notification area does not appear by each keystroke.

I removed hal and the acpi_support (except acpid), since it wasnt a dependency.

Do you have any further suggestions?

Thank you,
SauLus

[voria]

Please try to temporary remove the closedsource nvidia driver and use the nouveau driver, and check if the brightness control works with it.
If this is the case, then the problem is definitely with the nvidia driver, and I suggest to search more information on the nvnews.net forum.

I removed hal and the acpi_support (except acpid), since it wasnt a dependency.

I suggest you to reinstall acpi-support, since it's installed by default in ubuntu and it's needed for acpi to work properly.

[saulus]

Hi,

first I re-added the package acpi_support. The I opened System>Administration>Hardware Drivers and tried the alternative nvidia driver, i.e. nvidia-173, rebooted but nothing changed. So I removed all nvidia-belongings hoping that the nouveau driver automatically gets initiated (package xserver-xorg-video-nouveau is installed). After the reboot the screen remained black.

So, after one hour of chrooting and manually copying the packages because of a missing internet connection in the chrooted environment, I finally got my system running again.

Was it the correct way to enable the nouveau driver?
Just a footnote, I dont know if it is related and it doesnt bother me at all: My splash screen looks very primitive: Plain-colored with 4 squares nearly in pixelsize where the live-cd splash screen has nice dots. I reinstalled xsplash, but it didnt help.

[voria]

As far as I know, just the removal the nvidia driver should be enough to get nouveau up and running in its place. If this is not the case, then perhaps a configuration file for the X server exists as /etc/X11/xorg.conf, which forces the use of the nvidia driver. If so, try to remove or rename the config file and restart.

the nvidia driver specified in the X server configuration file ('/etc/X11/xorg.conf') which disable drivers autodetection.

Concerning the spash screen, it requires that the video driver in use has support for Kernel Mode Setting (KMS) in order to work and show up properly. The liveCD uses the nouveau driver which has this support, while the nvidia driver misses it.
Anyway just for the record, the splash screen in lucid is plymouth, not xsplash.

[saulus]

Ok,

the "Problem" with the splash screen was easily fixed, since only plymouth-theme-ubuntu-text got installed during the upgrade and not plymouth-theme-ubuntu-logo.

First I removed nvidia again and deleted the /etc/X11/xorg.conf.
After a rebooting the brightness keys worked fine (the other behaved strage but I didnt have time to test them).

Then I got back to the newer Bios 11ST, since 09ST has some small problems (dmesg reports hardware issues and videos and sounds stutter and are bucking). Then I noticed that the brightness keys do not work from the end of grub=the beginning of the kernel until gdm. Then (I suppose when your brightness module gets loaded) everything is fine with the brightness-module installed and everything stays bad without it.

Since we now know that its related to nvidia I suggest its out of topic Sadly I need the nvidia driver, since I am developing on openGL ...


Thank you very much for your time and work,

SauLus

[saulus]

Since the command smartdimmer works, I found a gnome-pannel
applet that manages adjusting the brightness with the smartdimmer/nvclock. It can be found here:

http://ppa.launchpad.net/intuitivenippl ... artdimmer/

It would be nice, though, to make this, or the smartdimmer/nvclock tool accessible using the keys. What do you think, would it be difficult and/or have a bad impact on the design of your package?


Another question: Do you know abount any samsung with an nvidia chipset on which the brightness can be adjusted using your module?

SauLus