Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #270106 > unrolled thread

Re: Laptop fan freaks out on boot

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Laptop fan freaks out on boot Tomas <tomas@tuxteam.de> - 2024-06-15 07:10 +0200
    Re: Laptop fan freaks out on boot jpeter17359549@tutanota.com - 2024-06-16 04:30 +0200
      Re: Laptop fan freaks out on boot Tomas <tomas@tuxteam.de> - 2024-06-16 06:50 +0200
      Re: Laptop fan freaks out on boot Hans <hans.ullrich@loop.de> - 2024-06-16 17:20 +0200

#270106 — Re: Laptop fan freaks out on boot

[Multipart message — attachments visible in raw view] — view raw

On Fri, Jun 14, 2024 at 10:00:26PM +0200, jpeter17359549@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.
> 
> It seems to happen at the point where it reaches this line:
> [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

[toc] | [next] | [standalone]

#270111

[Multipart message — attachments visible in raw view] — view raw

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 submit@bugs.debian.org.

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

Best regards,

Jeff


Jun 15, 2024, 05:02 by tomas@tuxteam.de:

> On Fri, Jun 14, 2024 at 10:00:26PM +0200, jpeter17359549@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.
>>
>> It seems to happen at the point where it reaches this line:
>> [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
>

[toc] | [prev] | [next] | [standalone]

#270112

[Multipart message — attachments visible in raw view] — view raw

On Sun, Jun 16, 2024 at 04:03:49AM +0200, jpeter17359549@tutanota.com wrote:
> 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.

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

Hope you get it fixed :-)

Cheers
-- 
tomás

[toc] | [prev] | [next] | [standalone]

#270123

Am Sonntag, 16. Juni 2024, 04:03:49 CEST schrieb jpeter17359549@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

> 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 submit@bugs.debian.org.
> 
> The laptop is ten years old, but this behavior is definitely abnormal.
> 
> Best regards,
> 
> Jeff
> 

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web