Fan only works after suspend toshiba M500

[nyjetshead]

F12 x64

Fan won't start working until it put into suspend.
I tried acpi.power_nocheck =1 in the kernel line doesn't work.

Any suggestions?

Satellite M500-ST5401 Intel

[nyjetshead]

Bump

Anyone having the same problem?

[BugRocks1]

http://www.thinkwiki.org/wiki/How_to_control_fan_speed

Have you tried looking at /proc to see if there is any fan files to play with?

---------- Post added at 06:08 AM CDT ---------- Previous post was at 06:03 AM CDT ----------

http://wiki.archlinux.org/index.php/Fan_Speed_Control

---------- Post added at 06:11 AM CDT ---------- Previous post was at 06:08 AM CDT ----------

pwmconfig may be usefull also and it comes with the package lm_sensors.

---------- Post added at 06:14 AM CDT ---------- Previous post was at 06:11 AM CDT ----------

Also in /sys/bus/acpi/devices somewhere there should be the files for the fans I just don't know how to get the address for them, but if you find them is just and "echo" away from it.

I think those address can be found in /var/log/Xorg.0.log when you suspend and come back they should show up as an event and show you the address.

---------- Post added at 06:35 AM CDT ---------- Previous post was at 06:14 AM CDT ----------

Possible path to the fan objects:

/sys/class/thermal/cooling_device0

---------- Post added at 06:37 AM CDT ---------- Previous post was at 06:35 AM CDT ----------

There is also the BIOS fan control system.

http://en.gentoo-wiki.com/wiki/Asus_Eee_PC_901

[nyjetshead]

Thanks for the info.

I'm a bit hesitant to go playing around because it works fine once it's suspended and then returned to normal operation.

There must be something that is getting reset when it comes out of suspend that isn't getting set when it boots.

I did locate the fan files and they are all set to ON

[BugRocks1]

I have no clue about why it is happening.

But if it was me, I would be looking at the log files in:

/var/log/messages
/var/log/Xorg.0.log

before and after the suspend mode to see if there is any differences that make shed some light on it.

---------- Post added at 08:43 AM CDT ---------- Previous post was at 08:33 AM CDT ----------

There are some scripts that define how the computer should wake up, the FDI files for HAL, the udev hardware definitions somewhere.

/etc/udev/rules.d
/etc/rc.d

[nyjetshead]

I didn't see anything that looked unusual in the logs

The only thing I found that seemed interesting was:

From Dmesg

ACPI: Thermal Zone [THRM] (71 C) ( This is what I get when I rebooted my ASUS laptop)

But the Toshiba gives me:
ACPI: Thermal Zone [TZO] (0 C)

I have no idea what to do with this info and if it means anything.

[BugRocks1]

Research material:

Information about low level access to the toshiba ACPI controls
http://www.buzzard.me.uk/toshiba/docs.html

---------- Post added at 11:41 AM CDT ---------- Previous post was at 10:09 AM CDT ----------

Using "locate acpi" this configuration files come up

/etc/acpi
/etc/acpi/actions
/etc/acpi/events
/etc/acpi/actions/power.sh
/etc/acpi/events/power.conf
/etc/acpi/events/video.conf
/etc/rc.d/init.d/acpid
/etc/rc.d/rc0.d/K74acpid
/etc/rc.d/rc1.d/K74acpid
/etc/rc.d/rc2.d/S26acpid
/etc/rc.d/rc3.d/S26acpid
/etc/rc.d/rc4.d/S26acpid
/etc/rc.d/rc5.d/S26acpid
/etc/rc.d/rc6.d/K74acpid

Is ACPID running?

ps -A | grep -i acpi

Do you have the toshiba module for acpi?

lsmod | grep -i toshiba

path to the driver:
/lib/modules/2.6.32.9-70.fc12.i686.PAE/kernel/drivers/platform/x86/toshiba_acpi.ko

ps: your kernel number and plataform may differ from mine.

Hunting for ACPI messages on DMESG.

cat /var/log/dmesg

$ grep -i acpi /var/log/dmesg

_SB and _TZ are related to the fans you will see one or the other but not both according to the ACPI specification.
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P8._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]

[nyjetshead]

I installed lm-sensors and installed the config file it created.
This was prior to my posting the issue here.

The Toshiba kmod is installed but when loaded I receive an error, apparently doesn't apply to this model.
From what I found on this the toshiba kmod is not up todate. Too bad Toshiba doesn't supply this and keep it up to date like some of the other manufacturers.

Probably should have considered a different machine.

I tried the omnibook kernel mod and that to didn't apply to this model.
This is also out of date.

Some of the function keys work and some don't.
I also cant activate the internal Bluetooth, its recognized but I can't enable it.
It's said to have something to do with the function keys.

[root@localhost ~]# ps -A | grep -i acpi
   22 ?        00:00:00 kacpid
   23 ?        00:00:00 kacpi_notify
   24 ?        00:00:00 kacpi_hotplug
 1342 ?        00:00:00 acpid
 1466 ?        00:00:00 hald-addon-acpi

[root@localhost ~]#  grep -i acpi /var/log/dmesg
 BIOS-e820: 00000000bdb90000 - 00000000bdb9e000 (ACPI data)
 BIOS-e820: 00000000bdb9e000 - 00000000bdde0000 (ACPI NVS)
ACPI: RSDP 00000000000fa200 00024 (v02 TOSASU)
ACPI: XSDT 00000000bdb90100 00064 (v01 TOSASU TOSASU00 20100205 MSFT 00000097)
ACPI: FACP 00000000bdb90290 000F4 (v04 TOSASU T0SASU00 20100205 MSFT 00000097)
ACPI: DSDT 00000000bdb905c0 0D76C (v02 TOSASU      A00 00000001 MSFT 03000001)
ACPI: FACS 00000000bdb9e000 00040
ACPI: APIC 00000000bdb90390 0006C (v02 TOSASU APIC1200 20100205 MSFT 00000097)
ACPI: MCFG 00000000bdb90400 0003C (v01 TOSASU OEMMCFG  20100205 MSFT 00000097)
ACPI: SLIC 00000000bdb90440 00176 (v01 TOSASU TOSASU00 20100205 MSFT 00000097)
ACPI: OEMB 00000000bdb9e040 000B6 (v01 TOSASU OEMB1200 20100205 MSFT 00000097)
ACPI: HPET 00000000bdb9dfc0 00038 (v01 TOSASU OEMHPET  20100205 MSFT 00000097)
ACPI: GSCI 00000000bdb9e100 02024 (v01 TOSASU GMCHSCI  20100205 MSFT 00000097)
ACPI: SSDT 00000000bdba0cb0 004F0 (v01  PmRef    CpuPm 00003000 INTL 20051117)
ACPI: Local APIC address 0xfee00000
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a301 base: 0xfed00000
ACPI: Core revision 20090903
ACPI: bus type pci registered
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
ACPI: Power Resource [PF0] (on)
ACPI: Power Resource [PF1] (on)
ACPI: Power Resource [PF2] (on)
ACPI: Power Resource [PF3] (on)
ACPI: Power Resource [PF4] (on)
ACPI: Power Resource [PF5] (on)
ACPI Warning: Incorrect checksum in table [OEMB] - ED, should be A8 (20090903/tbutils-314)
ACPI Warning: Incorrect checksum in table [GSCI] - 90, should be F2 (20090903/tbutils-314)
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP1_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP2_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP4_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP6_._PRT]
ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PILC] (IRQs 3 4 5 6 7 9 10 11 12 *14 15)
ACPI: PCI Interrupt Link [PILD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [PILF] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PILG] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PILH] (IRQs 3 4 5 6 7 9 10 11 12 14 *15)
PCI: Using ACPI for IRQ routing
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 11 devices
ACPI: ACPI bus type pnp unregistered
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
acpiphp: Slot [1] registered
ACPI: AC Adapter [AC] (on-line)
ACPI: Lid Switch [LID]
ACPI: Power Button [PWRB]
ACPI: Power Button [PWRF]
ACPI: Fan [FAN0] (on)
ACPI: Fan [FAN1] (on)
ACPI: Fan [FAN2] (on)
ACPI: Fan [FAN3] (on)
ACPI: Fan [FAN4] (on)
ACPI: Fan [FAN5] (on)
ACPI: SSDT 00000000bdba0440 0023D (v01  PmRef  Cpu0Ist 00003000 INTL 20051117)
ACPI: SSDT 00000000bdba0710 00594 (v01  PmRef  Cpu0Cst 00003001 INTL 20051117)
ACPI: SSDT 00000000bdba0330 0010F (v01  PmRef  Cpu1Ist 00003000 INTL 20051117)
ACPI: SSDT 00000000bdba0680 00085 (v01  PmRef  Cpu1Cst 00003000 INTL 20051117)
ACPI: Thermal Zone [TZ0] (0 C)
ACPI: Battery Slot [BAT] (battery present)
acpi device:02: registered as cooling_device8
ACPI: Video Device [IGD] (multi-head: yes  rom: no  post: no)

[BugRocks1]

There are ways to fix that but none are easy, well at least the ones I found

http://www.unix.privat.t-online.de/acpi.html

http://sourceforge.net/projects/fnfx/

For the Portege M300
http://en.opensuse.org/Upgrading_Tos...h/fnfx/toshset

Site with utilities and information specifically for the toshiba laptops.
http://www.buzzard.me.uk/toshiba/index.html

Apparent toshiba linux support:
http://linux.toshiba-dme.co.jp/linux/

The latest acpi drivers from toshiba(2004)
http://linux.toshiba-dme.co.jp/linux/eng/download.htm

You are not alone others are complaining about the issue too:
http://linux.toshiba-dme.co.jp/piper...er/000468.html

That post there have some things.

Overrriding ACPI methods.
http://www.mjmwired.net/kernel/Docum...ustomizing.txt

---------- Post added at 03:21 PM CDT ---------- Previous post was at 03:19 PM CDT ----------

Using kernel options to override DSDT's
http://www.lesswatts.org/projects/ac...ridingDSDT.php

---------- Post added at 03:24 PM CDT ---------- Previous post was at 03:21 PM CDT ----------

ACPI: DSDT 00000000bdb905c0 0D76C (v02 TOSASU A00 00000001 MSFT 03000001)

MSFT = Microsoft table compiler = buggy DSDT from what I read.

---------- Post added at 03:52 PM CDT ---------- Previous post was at 03:24 PM CDT ----------

Found a newer driver for the toshiba laptops:

http://memebeam.org/toys/RecentChanges

---------- Post added at 03:53 PM CDT ---------- Previous post was at 03:52 PM CDT ----------

how to install the driver:
http://memebeam.org/toys/ToshibaAcpiDriver

[nyjetshead]

Thanks for the reply.

I visited almost all of those links previously... unfortunately a lot of that stuff is stale and applicable to models that are 5 years old.

Toshiba's Linux site is a joke everything there is outdated short of the posts by others who are adding their laptop info, none of which applies to the model or series I have.

I neglected to mention that I tried the Fn stuff, it didn't help it actually made it worse Fn key wise.

Since this is my sons laptop, I'm looking for a solution that doesn't involve hacking and support on my end. In the interim, he will have to watch the cpu temps and put it into suspend right after booting.

I filed a bug report on this hopefully it will get addressed.

Toshiba is supposed to be making gains in market share so maybe things will change in the future.

[nightmarcus]

Toshiba Satellite L355D-S7829. My fan has never operated above a very minimal speed in any Linux distro except Ubuntu, and I'm not worried enough about it to go messing around with my kernel and stuff. It runs fast enough to keep me cool unless I'm just doing some really CPU intensive stuff, but then I just plug in my USB chill pad, still, it'd be nice if it adjusted the fan speed on its own. During bootup though I noticed a new error message saying make sure the toshiba_acpi option is marked in the kernel, so maybe newer kernel versions have better support for Toshiba ACPI options because this error message didn't used to appear. Anyway, I've posted my issue on so many different forums I can't see straight, and I have never received a really cut and dry answer on how to fix it without it getting broken the next time you install an automatic update.