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
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div dir="auto">Hello Tomas,<br></div><div dir="auto"><br></div><div dir="auto">I looked at the boot.log files, as well as the output from your command, and didn't see any errors or warnings.<br></div><div dir="auto"><br></div><div dir="auto">I'm going
to report this issue to <a href="mailto:
submit@bugs.debian.org" rel="noopener noreferrer" target="_blank">
submit@bugs.debian.org</a>.<br></div><div dir="auto"><br></div><div dir="auto">The laptop is ten years old, but this behavior is definitely abnormal.
<br></div><div dir="auto"><br></div><div dir="auto">Best regards,<br></div><div dir="auto"><br></div><div dir="auto">Jeff<br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Jun 15, 2024, 05:02 by
tomas@tuxteam.de:<br></div><
blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto">On Fri, Jun 14, 2024 at 10:00:26PM +0200,
jpeter17359549@tutanota.com wrote:<br></div><div dir="auto"><br></div><div dir="auto"
[Setting Mail-Followup-To to debian-user, as Felipe pointed out]<br></div><div dir="auto"><br></div><div dir="auto">[My question was, for those confused by top posting: at<br></div><div dir="auto">which point at boot the fan speeds up]<br></div><
blockquote><div dir="auto">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.<br></div><div dir="auto"><br></div><div dir="auto">The fan runs at very high RPM (probably on
maximum) for a couple of seconds on boot.<br></div><div dir="auto"><br></div><div dir="auto">It seems to happen at the point where it reaches this line:<br></div><div dir="auto">[OK] Reached target sound.target - Sound card.<br></div><div dir="auto"><br><
/div><div dir="auto">The fan otherwise behaves normally, and sound plays fine, except XFCE event sounds don't work (log in/out, emptying trash, etc).<br></div></blockquote><div dir="auto"><br></div><div dir="auto">OK, the Linux kernel has definitely
taken over at that point.<br></div><div dir="auto"><br></div><div dir="auto">I asked the question because I've observed a similar behaviour<br></div><div dir="auto">(mainly on desktops), but this happens much earlier, while<br></div><div dir="auto">the
BIOS is still in charge, before the the kernel has taken<br></div><div dir="auto">over.<br></div><div dir="auto"><br></div><div dir="auto">I'm not very knowledgeable on what happens when (especially<br></div><div dir="auto">if systemd is involved, but
you could try to look into your<br></div><div dir="auto">boot log with "journalctl -b". Perhaps you find out what is<br></div><div dir="auto">happening around the start of sound.target.<br></div><div dir="auto"><br></div><div dir="auto">Cheers<br></div><
div dir="auto">-- <br></div><div dir="auto">t<br></div></blockquote><div dir="auto"><br></div> </body>
</html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)