Fn brightness keys on Toshiba Satellite A300 don't work at all

[Jano]

Description: Ubuntu 8.10
Release: 8.10
Hardware: Toshiba Satellite A300 with Phoenix BIOS

The LCD display of my notebook always remains on highest possible level and cannot be dimmed down by any means, especially by the Fn brightness keys, which do nothing at all. Please note that my machine is a Toshiba computer with a PHOENIX bios, which means i cannot use tools such as toshset, fn-fx and so on. Those tools only work for machines with a genuine Toshiba bios. I also upgraded my bios to version 1.50 (from 1.40), provided by the manufacturer, but it didn't help the slightiest bit. As a result, both Ubuntu 8.04 and 8.10 remain inoperable by night or anywhere in insufficiently lit premises. Needless to say, it drains the battery extremely quickly. Thanks in advance for any solution.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Jano (jkotuc)]

No problem.

1.) uname -a: Linux bodhisattwa 2.6.27-7-generic #1 SMP Tue Nov 4
19:33:20 UTC 2008 i686 GNU/Linux

2.) attached

3.) attached

Many thanks in advance for any help

Jan

On Thu, Nov 13, 2008 at 4:04 PM, IanW <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately we can't fix it without more information.
>
> Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
> 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
> 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
> 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
>
> For your reference, the full description of procedures for kernel-
> related bug reports is available at
> https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux
> Status: New => Incomplete
>
> --
> Can't adjust display brightness on Toshiba Satellite A300
> https://bugs.launchpad.net/bugs/297658
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jano (jkotuc)]

UPDATE: I performed the recent kernel upgrade; now i'm running version 2.6.27-8-generic, but the display brightness problem still persists... Should i post another set of logs with the newer kernel?

[Jano (jkotuc)]

ANOTHER UPDATE: After a recent kernel update, the computer behaves a bit erratically. Sometimes the brightness adjusting works right after a boot, but doesn't work after a restart. Approximately 1 in 5 boots is okay, in 4 boots out of 5 i still cannot adjust display brightness... Seems really strange to me.

[Aesaert Wim (wim-aesaert)]

I'm on a Toshiba Satellite L350D-10i

system-manufacturer: TOSHIBA
system-product-name: Satellite L350D
system-version: PSLE0E-00E004BT

I have a problem that looks a lot like your latest post. Normally I can't switch my screen brightness with the Fn-Hotkeys. When I install KDE-guidance-powermanager and reboot, I can change brightness levels of the LCD screen with Fn-keys. The second time I reboot (and all following reboots) I can't change-brightness levels anymore via Fn-keys. Changing brightness level manually with the slider in guidance powermanager works any time.
Sometimes switching brightness also works first reboot after I uninstall guidance-powermanager. Second and all following rebootes disables switching brightness again.

I don't know if this is an FN-Hotkey, guidance-powermanager or other problem.

I did a dmesg when the brightness worked and also one when i doesn't work, compared both and they were almost exactly the same. I can post both if you want. If you want more information or you me to test something, feel free to ask. I'll help as much as I can.

[Aesaert Wim (wim-aesaert)]

In my previous post I forgot to mention that I use a vanilla kernel because my laptop kept on crashing because the fan wasn't running properly. Following options were enabled:

Symbol: ACPI_TOSHIBA [=y]
  │ Prompt: Toshiba Laptop Extras
  │ Defined at drivers/acpi/Kconfig:260
  │ Depends on: !X86_VOYAGER && ACPI && X86
  │ Location:
  │ -> Power management options
  │ -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
  │ Selects: BACKLIGHT_CLASS_DEVICE

Symbol: TOSHIBA [=y]
  │ Prompt: Toshiba Laptop support
  │ Defined at arch/x86/Kconfig:724
  │ Depends on: X86_32
  │ Location:
  │ -> Processor type and features

I probably also enabled a lot of other options that had something to do with ACPI and powermanagement.

[Aesaert Wim (wim-aesaert)]

uname -a: Linux denplatten 2.6.27.2-met-toshiba-ondersteuning #2 SMP Sat Nov 29 22:53:53 CET 2008 i686 GNU/Linux

version: Linux version 2.6.27.2-met-toshiba-ondersteuning (root@denplatten) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #2 SMP Sat Nov 29 22:53:53 CET 2008

P.S. Can someone explain how to attach multiple items in one post. I'm growing a grey beard here while adding attachments.

Greetz and thanks in advance :)

[Jano (jkotuc)]

Hello, breaking news: I discovered a certain pattern in my laptop's behavior regarding this brightness issue. Whenever a kernel upgrade (from official packages) is performed, the first boot with the new kernel is always good (i.e. i can adjust brightness), while all subsequent boots are NOT. Any ideas why this might be happening?? I'm really puzzled. TIA.

[Jano (jkotuc)]

Hello, back to normal. With the last three kernel updates, I wasn't able to adjust the brightness, not even in the first boot with the new kernel. I wonder if anything is beign done with this bug... :-/

[Aesaert Wim (wim-aesaert)]

 Jano wrote on 2008-12-09: (permalink)
Hello, breaking news: I discovered a certain pattern in my laptop's behavior regarding this brightness issue. Whenever a kernel upgrade (from official packages) is performed, the first boot with the new kernel is always good (i.e. i can adjust brightness), while all subsequent boots are NOT. Any ideas why this might be happening?? I'm really puzzled. TIA.

__________________

There recently was an update of an acpi package. I can't remember the name exactly. I remember that the brightness up and down key worked and also that the power detection (removing or connecting power cable) was working good at the first reboot after I upgraded the acpi package. The problem is that it didn't work 'again' from the second boot or all following reboots.

I don't know how this acpi stuff works, but could the following be possible?

bootsession 1 = power detection and hotkeys working
bootsession 2+x = power detection and hotkeys NOT working
1) acpi reads some settings from a certain settings file when the pc boots (bootsession 1).
2) some other piece of power-hotkey-software (which starts after acpi is started) writes some wrong settings to this settings file. (bootsession 1)
3) Kubuntu starts and acpi works. (bootsession 1)
4) Reboot the pc
5) Acpi reads some WRONG settings from a certain settings file when the pc boots (bootsession 2+x)
6) Some other piece of power-hotkey-software (which starts after acpi is started) writes some wrong settings to this settings file. (bootsession 2+x)
7) Kubuntu starts and acpi doesn't work.(bootsession 2+x)
8) Reboot the pc
9) All following reboots are equal to point 5 to 8.

10) When you reïnstall acpi, it writes the good settings to this settings file.
11) Reboot the pc.
We can start again from point 1) acpi reads.....

[kernel-janitor (kernel-janitor)]

Hi Jano,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 297658

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jano (jkotuc)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
Uname: Linux 2.6.28-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Leann Ogasawara (leannogasawara)]

Hi Jano,

Could you actually re-test with the latest Karmic 9.10 Alpha release and re-run the apport-collect command while running Karmic. Thanks.

http://cdimage.ubuntu.com/releases/karmic

[Jano (jkotuc)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
Uname: Linux 2.6.28-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Jano (jkotuc)]

Allright, i'll do the testing tomorrow, but the apport-collect output i posted now was from the most recent kernel upgrade on Ubuntu 9.04, which completely hosed the ACPI management of my machine, or so it seems...

[Jano (jkotuc)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3838 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x96500000 irq 22'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1179ff1c,00100003 HDA:11c11040,11790001,00100200'
   Controls : 22
   Simple ctrls : 13
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090902.1)
MachineType: TOSHIBA Satellite A300
Package: linux (not installed)
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-9-generic N/A
 linux-firmware 1.16
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/27/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.50
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd06/27/2008:svnTOSHIBA:pnSatelliteA300:pvrPSAG0E-02J027CZ:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Satellite A300
dmi.product.version: PSAG0E-02J027CZ
dmi.sys.vendor: TOSHIBA

[Jano (jkotuc)]

The above is an output of apport-collect from the newest Karmic live CD. The ACPI and brightness controls finally work 100% !! The funny thing is, that the apport-collect itself froze during the process, and the entire system froze with it. Too bad, I had to do the hard restart...

[Leann Ogasawara (leannogasawara)]

Marking this particular issue Fix Released against Karmic per the previous comment. Thanks.

[Jano (jkotuc)]

This bug is still not fixed (as of Maverick Meerkat). I tried the both the Ubuntu live CD and the Kubuntu installation, and in both cases the brightness keys don't work. Should I post all the lspci and other logs all over again?

[Jano (jkotuc)]

uname -a: Linux tatranka 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:24:00 UTC 2010 i686 GNU/Linux

[Jano (jkotuc)]

UPDATE: I edited /etc/default/grub and added "acpi_osi=" like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset acpi_osi="

Now everything works!