Laptop fan freaks out on boot

[Tomas]

On Fri, Jun 14, 2024 at 10:00:26PM +0200, ***@tutanota.com wrote:

[Setting Mail-Followup-To to debian-user, as Felipe pointed out]

[My question was, for those confused by top posting: at
which point at boot the fan speeds up]

Yes, I am using Debian 12.5. It's a new install on a Dell laptop, which previously ran Windows, and it never had any cooling issues.
The fan runs at very high RPM (probably on maximum) for a couple of seconds on boot.
[OK] Reached target sound.target - Sound card.
The fan otherwise behaves normally, and sound plays fine, except XFCE event sounds don't work (log in/out, emptying trash, etc).

OK, the Linux kernel has definitely taken over at that point.

I asked the question because I've observed a similar behaviour
(mainly on desktops), but this happens much earlier, while
the BIOS is still in charge, before the the kernel has taken
over.

I'm not very knowledgeable on what happens when (especially
if systemd is involved, but you could try to look into your
boot log with "journalctl -b". Perhaps you find out what is
happening around the start of sound.target.

Cheers

[j***@tutanota.com]

Hello Tomas,

I looked at the boot.log files, as well as the output from your command, and didn't see any errors or warnings.

I'm going to report this issue to ***@bugs.debian.org.

The laptop is ten years old, but this behavior is definitely abnormal.

Best regards,

Jeff

Post by Tomas
[Setting Mail-Followup-To to debian-user, as Felipe pointed out]
[My question was, for those confused by top posting: at
which point at boot the fan speeds up]

Yes, I am using Debian 12.5. It's a new install on a Dell laptop, which previously ran Windows, and it never had any cooling issues.
The fan runs at very high RPM (probably on maximum) for a couple of seconds on boot.
[OK] Reached target sound.target - Sound card.
The fan otherwise behaves normally, and sound plays fine, except XFCE event sounds don't work (log in/out, emptying trash, etc).

OK, the Linux kernel has definitely taken over at that point.
I asked the question because I've observed a similar behaviour
(mainly on desktops), but this happens much earlier, while
the BIOS is still in charge, before the the kernel has taken
over.
I'm not very knowledgeable on what happens when (especially
if systemd is involved, but you could try to look into your
boot log with "journalctl -b". Perhaps you find out what is
happening around the start of sound.target.
Cheers
--
t

[Tomas]

Post by j***@tutanota.com
Hello Tomas,
I looked at the boot.log files, as well as the output from your command, and didn't see any errors or warnings.

Hm. I hope someone around here has a better idea.
Hope you get it fixed :-)

Cheers

[Hans]

Am Sonntag, 16. Juni 2024, 04:03:49 CEST schrieb ***@tutanota.com:
Just a shot:

Take a look, if you have the packaget "fancontrol" installed.

Then as root start the command "fancontrol" and see, if the vents are
recognized. Normally they should stop, then start again. Just follow the
instructions.

This command is creating the file /etc/fancontrol, which you can later fine
tune (i.e. tell, at which temperature the fans will start).

On Asus laptops (especiially older laptops like eepc), I had to decide, which
kernel module shoulds be used. One is "wmi" (the other one I forgot the neame
of (too long ago!). Modern kernels are using wmi, but maybe your cpu does not
support it and needs the older one (maybe someone else knows more).

There are kernel options, which decide, which module is used. However, this is
mostly on my EEEPC, but maybe other older laptops may alos depend on it.

Just some ideas, hope this is helping though....

Best regards

Hans

Post by j***@tutanota.com
Hello Tomas,
I looked at the boot.log files, as well as the output from your command, and
didn't see any errors or warnings.
The laptop is ten years old, but this behavior is definitely abnormal.
Best regards,
Jeff