Kernel Bug Tracker – Bug 5975
No Function keys -- Toshiba Satellite M45-S359
Last modified: 2013-04-09 06:13:59 UTC
This model's function keys and other toshiba models (such as the m45-s331, see
page http://www.fedoraforum.org/forum/showthread.php?p=223328) do not work.
The LCD is shut down when the lid is closed, however the dimming using the
function keys does not work. Attempts to load the toshiba_acpi module also do
I'm running a vanilla 2.6.16-rc1 kernel on fedora core 4, with the following
kernel options: acpi=on pci=routeirq
Created attachment 7172 [details]
output from the acpidump tool
Created attachment 7173 [details]
Created attachment 7174 [details]
Created attachment 7175 [details]
Created attachment 7176 [details]
Created attachment 7177 [details]
The problem is that we do not have support for Phoenix Bios.
The toshiba_acpi module is only for toshiba bios..
Does the problem still exist in the latest kernel with a newer bios?
can the toshiba_acpi driver be loaded?
can you change the brightness level by manually writing to /sys/class/backlight/acpi_video0/brightness?
Due to this problem and other little integration and compatibility
things that Linux could never address, I will be changing soon to a
Mac. I do not have Linux installed anymore on my PC, however the last
time I checked the problem was still there. I believe it had a kernel
version 2.6.20 or 2.6.21.
On 9/20/07, firstname.lastname@example.org
> email@example.com changed:
> What |Removed |Added
> AssignedTofirstname.lastname@example.org |email@example.com
> Status|NEW |ASSIGNED
> ------- Comment #8 from firstname.lastname@example.org 2007-09-19 23:08 -------
> Hi, Daniel,
> Does the problem still exist in the latest kernel with a newer bios?
> can the toshiba_acpi driver be loaded?
> can you change the brightness level by manually writing to
> Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
Oh, bad news :(
I'll reject this bug and mark it as unreproducible.
Please reopen it if you want to try Linux again. :)