<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Linux Lite Forums - Start up and Shutdown]]></title>
		<link>https://www.linuxliteos.com/forums/</link>
		<description><![CDATA[Linux Lite Forums - https://www.linuxliteos.com/forums]]></description>
		<pubDate>Thu, 30 Apr 2026 16:21:00 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Annoying behaviour on wake from sleep LL 4.8]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9810</link>
			<pubDate>Mon, 26 Jan 2026 22:43:38 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=8000">ShaunR</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9810</guid>
			<description><![CDATA[Hello All,<br />
<br />
I have installed Linux Lite 4.8 on an HP 350 G2.  Everything seems to work fine except for waking from the suspended state.<br />
I have set the computer to blank the screen after 5 minutes of inactivity and suspend after 30 minutes on both power and battery.<br />
The screen goes blank as it should after 5 minutes, then after 30 minutes it suspends and the power light starts flashing.<br />
If I now try to wake it up by touching the mouse pad, what happens is that the power light stops flashing, but the screen stays dark.  I have to touch the mouse pad again to make the screen turn on.<br />
<br />
So I have to touch the mouse twice to wake it up every time.<br />
<br />
This may seem like a small thing, but it is still annoying.  I would like the computer to wake from sleep and turn the screen back on with a single touch of the mouse.<br />
<br />
Can anyone please suggest a fix, or at least a way of finding out why the screen doesn't turn on when the mouse is first touched?<br />
<br />
I have already tried to fix it by putting:<br />
ExecStart=/usr/bin/bash -c "xrandr -d :0 --output eDP-1 --auto"<br />
in a systemd service file "After=suspend.target", which seemed like a good idea, but soon discovered that the command was not being executed on wake after suspend.<br />
<br />
UPDATE<br />
I have now discovered that if I put startx in the systemd service file, the screen turns on after suspend unconditionally.  So it's fixed!  The only problem is that startx fails with a lot of error messages in syslog, so this isn't a very satisfactory solution.<br />
<br />
(The command wasn't being executed before because the bash path was wrong, it should be /bin/bash.)]]></description>
			<content:encoded><![CDATA[Hello All,<br />
<br />
I have installed Linux Lite 4.8 on an HP 350 G2.  Everything seems to work fine except for waking from the suspended state.<br />
I have set the computer to blank the screen after 5 minutes of inactivity and suspend after 30 minutes on both power and battery.<br />
The screen goes blank as it should after 5 minutes, then after 30 minutes it suspends and the power light starts flashing.<br />
If I now try to wake it up by touching the mouse pad, what happens is that the power light stops flashing, but the screen stays dark.  I have to touch the mouse pad again to make the screen turn on.<br />
<br />
So I have to touch the mouse twice to wake it up every time.<br />
<br />
This may seem like a small thing, but it is still annoying.  I would like the computer to wake from sleep and turn the screen back on with a single touch of the mouse.<br />
<br />
Can anyone please suggest a fix, or at least a way of finding out why the screen doesn't turn on when the mouse is first touched?<br />
<br />
I have already tried to fix it by putting:<br />
ExecStart=/usr/bin/bash -c "xrandr -d :0 --output eDP-1 --auto"<br />
in a systemd service file "After=suspend.target", which seemed like a good idea, but soon discovered that the command was not being executed on wake after suspend.<br />
<br />
UPDATE<br />
I have now discovered that if I put startx in the systemd service file, the screen turns on after suspend unconditionally.  So it's fixed!  The only problem is that startx fails with a lot of error messages in syslog, so this isn't a very satisfactory solution.<br />
<br />
(The command wasn't being executed before because the bash path was wrong, it should be /bin/bash.)]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[5 Minute Boot]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9702</link>
			<pubDate>Mon, 17 Nov 2025 05:05:19 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=1363">frank4360</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9702</guid>
			<description><![CDATA[Booting LinuxLite now takes up to 5 minutes!<br />
<br />
Here is the output from "systemd-analyze blame"<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>5min 53ms networking.service<br />
  5.527s NetworkManager-wait-online.service<br />
  5.019s systemd-networkd-wait-online.service<br />
  3.390s hddtemp.service<br />
  3.347s lightdm.service<br />
  3.336s plymouth-quit-wait.service<br />
  1.555s snapd.seeded.service<br />
  1.511s systemd-udev-settle.service<br />
  1.362s snapd.service<br />
    994ms blueman-mechanism.service</blockquote>
<br />
I already have the mod <br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="color: #55FF55;" class="mycode_color"><span style="font-weight: bold;" class="mycode_b">[Service]</span></span><br />
Type=oneshot<br />
ExecStart=/lib/systemd/systemd-networkd-wait-online --timeout=5<br />
RemainAfterExit=yes</blockquote>
<br />
Any ideas greatly appreciated.]]></description>
			<content:encoded><![CDATA[Booting LinuxLite now takes up to 5 minutes!<br />
<br />
Here is the output from "systemd-analyze blame"<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>5min 53ms networking.service<br />
  5.527s NetworkManager-wait-online.service<br />
  5.019s systemd-networkd-wait-online.service<br />
  3.390s hddtemp.service<br />
  3.347s lightdm.service<br />
  3.336s plymouth-quit-wait.service<br />
  1.555s snapd.seeded.service<br />
  1.511s systemd-udev-settle.service<br />
  1.362s snapd.service<br />
    994ms blueman-mechanism.service</blockquote>
<br />
I already have the mod <br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="color: #55FF55;" class="mycode_color"><span style="font-weight: bold;" class="mycode_b">[Service]</span></span><br />
Type=oneshot<br />
ExecStart=/lib/systemd/systemd-networkd-wait-online --timeout=5<br />
RemainAfterExit=yes</blockquote>
<br />
Any ideas greatly appreciated.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[No authentication when i reopen my laptops lid]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9701</link>
			<pubDate>Sat, 15 Nov 2025 12:52:19 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=7820">Samuelo</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9701</guid>
			<description><![CDATA[Hello, i noticed that when i close my laptop's lid for one reason or another and then re-open it again later LL don't ask for my password like windows does.<br />
For me that's a serious security flaw as anyone could just open the lid and then get access to laptop, how can i prevent this?<br />
The box "Lock screen when system is going to sleep" was already checked and re-doing it changed nothing.]]></description>
			<content:encoded><![CDATA[Hello, i noticed that when i close my laptop's lid for one reason or another and then re-open it again later LL don't ask for my password like windows does.<br />
For me that's a serious security flaw as anyone could just open the lid and then get access to laptop, how can i prevent this?<br />
The box "Lock screen when system is going to sleep" was already checked and re-doing it changed nothing.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Dell Latitude E6220 Laptop boot time too long]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9638</link>
			<pubDate>Tue, 16 Sep 2025 21:03:27 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=7445">CountFoxx</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9638</guid>
			<description><![CDATA[My Dell Latitude E6220 Laptop takes too long to boot up—3.15 minutes, which I think is too long. I unchecked some and then all the applications from 'Session and Startup, ' but there is no difference in boot time, whatsoever.  I have no third-party software installed.<br />
<br />
Any helpful suggestions or remedies, please <img src="https://www.linuxliteos.com/forums/images/smilies/huh.png" alt="Huh" title="Huh" class="smilie smilie_17" />  <br />
<br />
<span style="font-weight: bold;" class="mycode_b">-Processors-</span><br />
Package Information <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 0 0:0 3200.00 MHz <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 1 0:1 3200.00 MHz <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 2 0:0 3200.00 MHz <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 3 0:1 3200.00 MHz<br />
<br />
<span style="font-weight: bold;" class="mycode_b">-Memory-</span><br />
MemTotal Total Memory 3883788 KiB <br />
MemFree Free Memory 496216 KiB <br />
MemAvailable 1754864 KiB <br />
Buffers 78876 KiB <br />
Cached 1539512 KiB <br />
SwapCached Cached Swap 0 KiB <br />
Active 2074168 KiB <br />
Inactive 806616 KiB <br />
Active(anon) 1448912 KiB <br />
Inactive(anon) 0 KiB <br />
Active(file) 625256 KiB <br />
Inactive(file) 806616 KiB <br />
Unevictable 120616 KiB <br />
Mlocked 20340 KiB <br />
SwapTotal Virtual Memory 6060416 KiB <br />
SwapFree Free Virtual Memory 6060416 KiB <br />
Zswap 0 KiB <br />
Zswapped 0 KiB <br />
Dirty 316 KiB <br />
Writeback 0 KiB <br />
AnonPages 1383104 KiB <br />
Mapped 490320 KiB <br />
Shmem 176856 KiB <br />
KReclaimable 60144 KiB <br />
Slab 179108 KiB <br />
SReclaimable 60144 KiB <br />
SUnreclaim 118964 KiB <br />
KernelStack 10696 KiB <br />
PageTables 31968 KiB <br />
SecPageTables 0 KiB <br />
NFS_Unstable 0 KiB <br />
Bounce 0 KiB <br />
WritebackTmp 0 KiB <br />
CommitLimit 8002308 KiB <br />
Committed_AS 12772768 KiB <br />
VmallocTotal -1 KiB <br />
VmallocUsed 73352 KiB <br />
VmallocChunk 0 KiB <br />
Percpu 12352 KiB <br />
HardwareCorrupted 0 KiB <br />
AnonHugePages 0 KiB <br />
ShmemHugePages 47104 KiB <br />
ShmemPmdMapped 0 KiB <br />
FileHugePages 0 KiB <br />
FilePmdMapped 0 KiB <br />
Unaccepted 0 KiB <br />
HugePages_Total 0 <br />
HugePages_Free 0 <br />
HugePages_Rsvd 0 <br />
HugePages_Surp 0 <br />
Hugepagesize 2048 KiB <br />
Hugetlb 0 KiB <br />
DirectMap4k 202192 KiB <br />
DirectMap2M 3870720 KiB <br />
<br />
<span style="font-weight: bold;" class="mycode_b">-PCI Devices-</span><br />
Host bridge : Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)<br />
VGA compatible controller : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])<br />
Communication controller : Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)<br />
Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)<br />
USB controller : Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])<br />
Audio device : Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) (prog-if 00 [Normal decode])<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) (prog-if 00 [Normal decode])<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4) (prog-if 00 [Normal decode])<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4) (prog-if 00 [Normal decode])<br />
USB controller : Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])<br />
ISA bridge : Intel Corporation QM67 Express Chipset LPC Controller (rev 04)<br />
RAID bus controller : Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)<br />
SMBus : Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)<br />
Network controller : Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)<br />
SD Host controller : O2 Micro, Inc. OZ600FJ0/OZ900FJ0/OZ600FJS SD/MMC Card Reader Controller (rev 05) (prog-if 01)<br />
Mass storage controller : O2 Micro, Inc. Device 8231 (rev 03)]]></description>
			<content:encoded><![CDATA[My Dell Latitude E6220 Laptop takes too long to boot up—3.15 minutes, which I think is too long. I unchecked some and then all the applications from 'Session and Startup, ' but there is no difference in boot time, whatsoever.  I have no third-party software installed.<br />
<br />
Any helpful suggestions or remedies, please <img src="https://www.linuxliteos.com/forums/images/smilies/huh.png" alt="Huh" title="Huh" class="smilie smilie_17" />  <br />
<br />
<span style="font-weight: bold;" class="mycode_b">-Processors-</span><br />
Package Information <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 0 0:0 3200.00 MHz <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 1 0:1 3200.00 MHz <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 2 0:0 3200.00 MHz <br />
Intel&reg; Core&#153; i5-2520M CPU @ 2.50GHz 3 0:1 3200.00 MHz<br />
<br />
<span style="font-weight: bold;" class="mycode_b">-Memory-</span><br />
MemTotal Total Memory 3883788 KiB <br />
MemFree Free Memory 496216 KiB <br />
MemAvailable 1754864 KiB <br />
Buffers 78876 KiB <br />
Cached 1539512 KiB <br />
SwapCached Cached Swap 0 KiB <br />
Active 2074168 KiB <br />
Inactive 806616 KiB <br />
Active(anon) 1448912 KiB <br />
Inactive(anon) 0 KiB <br />
Active(file) 625256 KiB <br />
Inactive(file) 806616 KiB <br />
Unevictable 120616 KiB <br />
Mlocked 20340 KiB <br />
SwapTotal Virtual Memory 6060416 KiB <br />
SwapFree Free Virtual Memory 6060416 KiB <br />
Zswap 0 KiB <br />
Zswapped 0 KiB <br />
Dirty 316 KiB <br />
Writeback 0 KiB <br />
AnonPages 1383104 KiB <br />
Mapped 490320 KiB <br />
Shmem 176856 KiB <br />
KReclaimable 60144 KiB <br />
Slab 179108 KiB <br />
SReclaimable 60144 KiB <br />
SUnreclaim 118964 KiB <br />
KernelStack 10696 KiB <br />
PageTables 31968 KiB <br />
SecPageTables 0 KiB <br />
NFS_Unstable 0 KiB <br />
Bounce 0 KiB <br />
WritebackTmp 0 KiB <br />
CommitLimit 8002308 KiB <br />
Committed_AS 12772768 KiB <br />
VmallocTotal -1 KiB <br />
VmallocUsed 73352 KiB <br />
VmallocChunk 0 KiB <br />
Percpu 12352 KiB <br />
HardwareCorrupted 0 KiB <br />
AnonHugePages 0 KiB <br />
ShmemHugePages 47104 KiB <br />
ShmemPmdMapped 0 KiB <br />
FileHugePages 0 KiB <br />
FilePmdMapped 0 KiB <br />
Unaccepted 0 KiB <br />
HugePages_Total 0 <br />
HugePages_Free 0 <br />
HugePages_Rsvd 0 <br />
HugePages_Surp 0 <br />
Hugepagesize 2048 KiB <br />
Hugetlb 0 KiB <br />
DirectMap4k 202192 KiB <br />
DirectMap2M 3870720 KiB <br />
<br />
<span style="font-weight: bold;" class="mycode_b">-PCI Devices-</span><br />
Host bridge : Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)<br />
VGA compatible controller : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])<br />
Communication controller : Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)<br />
Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)<br />
USB controller : Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])<br />
Audio device : Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) (prog-if 00 [Normal decode])<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) (prog-if 00 [Normal decode])<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4) (prog-if 00 [Normal decode])<br />
PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4) (prog-if 00 [Normal decode])<br />
USB controller : Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])<br />
ISA bridge : Intel Corporation QM67 Express Chipset LPC Controller (rev 04)<br />
RAID bus controller : Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)<br />
SMBus : Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)<br />
Network controller : Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)<br />
SD Host controller : O2 Micro, Inc. OZ600FJ0/OZ900FJ0/OZ600FJS SD/MMC Card Reader Controller (rev 05) (prog-if 01)<br />
Mass storage controller : O2 Micro, Inc. Device 8231 (rev 03)]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Netbook boot screen before loading]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9434</link>
			<pubDate>Sat, 24 May 2025 18:20:46 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=7182">LLfan</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9434</guid>
			<description><![CDATA[I have installed Linux Lite on an Asus eee PC (Netbook) and it works fine.<br />
The only issue is when booting.<br />
I always get the following screen.<br />
<a href="https://ibb.co/LD0qvkQ9" target="_blank" rel="noopener" class="mycode_url"><img src="https://i.ibb.co/BHf7wz4T/linux-lite.jpg" loading="lazy"  alt="[Image: linux-lite.jpg]" class="mycode_img" /></a><br />
When I press F2 it goes into BIOS then I just press ESC and it loads and all is well.<br />
Does anyone know why I'm getting this screen when I boot?<br />
Thanks.]]></description>
			<content:encoded><![CDATA[I have installed Linux Lite on an Asus eee PC (Netbook) and it works fine.<br />
The only issue is when booting.<br />
I always get the following screen.<br />
<a href="https://ibb.co/LD0qvkQ9" target="_blank" rel="noopener" class="mycode_url"><img src="https://i.ibb.co/BHf7wz4T/linux-lite.jpg" loading="lazy"  alt="[Image: linux-lite.jpg]" class="mycode_img" /></a><br />
When I press F2 it goes into BIOS then I just press ESC and it loads and all is well.<br />
Does anyone know why I'm getting this screen when I boot?<br />
Thanks.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Slow start up on SDD after clean install]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9430</link>
			<pubDate>Thu, 22 May 2025 03:39:23 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=7171">vaspatt3</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9430</guid>
			<description><![CDATA[Using HP Compaq Presario CQ57.  Runs smooth but boot time is slow.  The grub menu does not appear on startup it just goes straihjt to booting process unless shift key is held at power on.  Any suggestions to help it boot quicker?  Presently clocks anywhere between 2.5 to 3.5 minutes.  Suggestions? Comments?]]></description>
			<content:encoded><![CDATA[Using HP Compaq Presario CQ57.  Runs smooth but boot time is slow.  The grub menu does not appear on startup it just goes straihjt to booting process unless shift key is held at power on.  Any suggestions to help it boot quicker?  Presently clocks anywhere between 2.5 to 3.5 minutes.  Suggestions? Comments?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Apple MacBook Air on 7.2 has strange wake from suspend]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9258</link>
			<pubDate>Wed, 06 Nov 2024 11:43:15 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=6497">Uncle Jimmy Bob</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9258</guid>
			<description><![CDATA[I installed Linux Lite 7.2 on an  Apple MacBook Air mid 2011 with 4GB RAM.  I formatted drive and used the ZFS file system and note that the kernel is 6.8.0-48-generic.  Not a dual-boot system; Linux Lite is only OS present on machine. <br />
<br />
I used Power Manager to set the option <span style="font-style: italic;" class="mycode_i">When Laptop lid is closed:</span> Suspend<br />
<br />
The laptop boots fine, I can log in, and everything works.   When I close the lid, it immediately turns off the screen and suspends.<br />
<br />
After a delay, say a few minutes, when I open lid the machine wakes up.  No lock screen or password is presented, but I see the desktop rendered correctly with clock in status bar showing time accurate as of moment of waking up.  Mouse pointer moves fine, but clicking button on touchpad does nothing and keyboard is unresponsive.  Clock does not advance and I see a static display of time of resume.  If I leave it for ~60 seconds the mouse pointer disappears (rest of display, with frozen clock is unchanged; displayed time does not advance).  Now if I click the touchpad the pointer returns and the clock immediately updates to display current time but does not revert to a running clock -- it's a static display of time, but the time is updated to moment of touchpad click.  Still no ability to use mouse to manipulate icons/controls on the screen even though pointer moves fine, and keyboard continues to have no effects. The laptop will move mouse pointer, but nothing more.<br />
<br />
Power button works fine and I can restart the machine if I hold it down for like 4 seconds.<br />
Either Ctrl-F2 does nothing, or I don't know how to do that on this Mac keyboard.<br />
<br />
I changed Power Manager option to Hibernate on lid close.  When I close lid the screen turns off, and when I reopen the laptop it does not awaken and appears to be off.  A single press of the power button will cause it to reboot.<br />
<br />
I tried a couple of commands in the terminal.<br />
<span style="font-style: italic;" class="mycode_i">systemctl suspend</span> sends laptop to sleep, upon wake (keyboard press) I see the lock screen where I given the opportunity to present my password, and it comes back to full function and everything works. <br />
<span style="font-style: italic;" class="mycode_i">systemctl hibernate </span> goes to lock screen, but never goes to sleep.  I can enter password and everything works fine, but again, it never goes in to hibernate state.<br />
<br />
I get different behavior by closing lid, which causes Power Manager to initiate Suspend mode, than I do with <span style="font-style: italic;" class="mycode_i">systemctl suspend </span>at the command line. <br />
<br />
Any thoughts on how I can "fix" the closing lid / Power Manager path so that it will resume correctly?<br />
It functions fine when I use terminal and <span style="font-style: italic;" class="mycode_i">systemctl suspend, </span>but that's a bit tedious to do every time I want to put the laptop to sleep.]]></description>
			<content:encoded><![CDATA[I installed Linux Lite 7.2 on an  Apple MacBook Air mid 2011 with 4GB RAM.  I formatted drive and used the ZFS file system and note that the kernel is 6.8.0-48-generic.  Not a dual-boot system; Linux Lite is only OS present on machine. <br />
<br />
I used Power Manager to set the option <span style="font-style: italic;" class="mycode_i">When Laptop lid is closed:</span> Suspend<br />
<br />
The laptop boots fine, I can log in, and everything works.   When I close the lid, it immediately turns off the screen and suspends.<br />
<br />
After a delay, say a few minutes, when I open lid the machine wakes up.  No lock screen or password is presented, but I see the desktop rendered correctly with clock in status bar showing time accurate as of moment of waking up.  Mouse pointer moves fine, but clicking button on touchpad does nothing and keyboard is unresponsive.  Clock does not advance and I see a static display of time of resume.  If I leave it for ~60 seconds the mouse pointer disappears (rest of display, with frozen clock is unchanged; displayed time does not advance).  Now if I click the touchpad the pointer returns and the clock immediately updates to display current time but does not revert to a running clock -- it's a static display of time, but the time is updated to moment of touchpad click.  Still no ability to use mouse to manipulate icons/controls on the screen even though pointer moves fine, and keyboard continues to have no effects. The laptop will move mouse pointer, but nothing more.<br />
<br />
Power button works fine and I can restart the machine if I hold it down for like 4 seconds.<br />
Either Ctrl-F2 does nothing, or I don't know how to do that on this Mac keyboard.<br />
<br />
I changed Power Manager option to Hibernate on lid close.  When I close lid the screen turns off, and when I reopen the laptop it does not awaken and appears to be off.  A single press of the power button will cause it to reboot.<br />
<br />
I tried a couple of commands in the terminal.<br />
<span style="font-style: italic;" class="mycode_i">systemctl suspend</span> sends laptop to sleep, upon wake (keyboard press) I see the lock screen where I given the opportunity to present my password, and it comes back to full function and everything works. <br />
<span style="font-style: italic;" class="mycode_i">systemctl hibernate </span> goes to lock screen, but never goes to sleep.  I can enter password and everything works fine, but again, it never goes in to hibernate state.<br />
<br />
I get different behavior by closing lid, which causes Power Manager to initiate Suspend mode, than I do with <span style="font-style: italic;" class="mycode_i">systemctl suspend </span>at the command line. <br />
<br />
Any thoughts on how I can "fix" the closing lid / Power Manager path so that it will resume correctly?<br />
It functions fine when I use terminal and <span style="font-style: italic;" class="mycode_i">systemctl suspend, </span>but that's a bit tedious to do every time I want to put the laptop to sleep.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Fail to resume after suspend using lid and other issues]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9241</link>
			<pubDate>Wed, 18 Sep 2024 04:51:44 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=6406">majuamst</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9241</guid>
			<description><![CDATA[I am a brand new user of Linux on a 10 year old laptop with a C-60 AMD GPU. Immediately upon booting, there is a brief message, "0.004051 Common interrupt 1.55 No IRQ handler for vector" that flashes for 10-15 seconds. The computer continues to boot into LinuxLite. I am a longtime Windows user and a brand new Linux user. I am learning to like LinuxLite and have set up this old laptop to do everything the way I want, but I have one very big problem. It will not wake up from suspend. It flashes "no IRQ handler for vector" on several lines of a black screen. The error message disappears too quickly for me to copy and post it accurately for you to see. After the error message, the screen stays blank and never loads my desktop. I have tried to use hibernate instead, but I get another error message indicating that hibernate is not possible. It appears that some IRQs are not being assigned upon boot and after suspend.<br />
<br />
I did some internet research and found that this is a known issue with AMD processors. It has something to do with IOMMU. The suggestions include turning IOMMU off in the BIOS, but that option is not provided in the rudimentary BIOS screens of this ACER Aspire One 722. Apparently there is a Linux software solution as well, but they all suggest the BIOS change first.<br />
<br />
Sorry for the long post, but I am wondering if someone has experienced this issue and knows how to fix it. I really want to learn Linux on this old laptop and have started tutorials to navigate my way around. As we get closer to Microsoft abandoning Windows 10, I would like to convert all of my networked computers to Linux, but not if I cannot solve these types of problems.<br />
<br />
Thank you for being here for beginners like me.]]></description>
			<content:encoded><![CDATA[I am a brand new user of Linux on a 10 year old laptop with a C-60 AMD GPU. Immediately upon booting, there is a brief message, "0.004051 Common interrupt 1.55 No IRQ handler for vector" that flashes for 10-15 seconds. The computer continues to boot into LinuxLite. I am a longtime Windows user and a brand new Linux user. I am learning to like LinuxLite and have set up this old laptop to do everything the way I want, but I have one very big problem. It will not wake up from suspend. It flashes "no IRQ handler for vector" on several lines of a black screen. The error message disappears too quickly for me to copy and post it accurately for you to see. After the error message, the screen stays blank and never loads my desktop. I have tried to use hibernate instead, but I get another error message indicating that hibernate is not possible. It appears that some IRQs are not being assigned upon boot and after suspend.<br />
<br />
I did some internet research and found that this is a known issue with AMD processors. It has something to do with IOMMU. The suggestions include turning IOMMU off in the BIOS, but that option is not provided in the rudimentary BIOS screens of this ACER Aspire One 722. Apparently there is a Linux software solution as well, but they all suggest the BIOS change first.<br />
<br />
Sorry for the long post, but I am wondering if someone has experienced this issue and knows how to fix it. I really want to learn Linux on this old laptop and have started tutorials to navigate my way around. As we get closer to Microsoft abandoning Windows 10, I would like to convert all of my networked computers to Linux, but not if I cannot solve these types of problems.<br />
<br />
Thank you for being here for beginners like me.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Problem restoring laptop state after lid re-opened]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=9203</link>
			<pubDate>Tue, 02 Jul 2024 18:36:43 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=6284">g40</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=9203</guid>
			<description><![CDATA[The desktop appears to freeze once the lid is re-opened. The mouse still works but keyboard appears disabled. The only solution so far is power-cycle.<br />
<br />
Using power manager I have tried each option, all end up with the same result. Screen locking is off. <br />
<br />
[edit] The 'switch off display' option *does* work, but suspend/hibernate/lock all seem to skewer the desktop.<br />
<br />
Any thoughts? Machine in question is an Intel i5 Dell Vostro w/ 16GB RAM, Samsung 512GB SSD. Please let me know if more info required.<br />
]]></description>
			<content:encoded><![CDATA[The desktop appears to freeze once the lid is re-opened. The mouse still works but keyboard appears disabled. The only solution so far is power-cycle.<br />
<br />
Using power manager I have tried each option, all end up with the same result. Screen locking is off. <br />
<br />
[edit] The 'switch off display' option *does* work, but suspend/hibernate/lock all seem to skewer the desktop.<br />
<br />
Any thoughts? Machine in question is an Intel i5 Dell Vostro w/ 16GB RAM, Samsung 512GB SSD. Please let me know if more info required.<br />
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Error, Busybox INTRANFS]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=8962</link>
			<pubDate>Sat, 28 Oct 2023 00:23:08 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=3475">LarryB1607</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=8962</guid>
			<description><![CDATA[Sorry if posting in the wrong spot.  Received some updates Wed and now I cannot get into my system.  Even an older package does not work as well as a recovery one which goes on forever.   Typing in help brings up a long line of cryptic to mestuff that I cannot copy to post.  Using LLOS 4.8???  I have an old backup, but not sure how to get to it and it would be way to old anyway.  I will run Gparted and find out the drive.  I have  a system and a user partition.  If I need to reinstall, will my user partition remain usable?  This happened once before from an update, but I was able to use an older package , but not this time.  thanks for any help]]></description>
			<content:encoded><![CDATA[Sorry if posting in the wrong spot.  Received some updates Wed and now I cannot get into my system.  Even an older package does not work as well as a recovery one which goes on forever.   Typing in help brings up a long line of cryptic to mestuff that I cannot copy to post.  Using LLOS 4.8???  I have an old backup, but not sure how to get to it and it would be way to old anyway.  I will run Gparted and find out the drive.  I have  a system and a user partition.  If I need to reinstall, will my user partition remain usable?  This happened once before from an update, but I was able to use an older package , but not this time.  thanks for any help]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Hibernation in LL]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=8947</link>
			<pubDate>Sat, 07 Oct 2023 04:53:02 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=5986">wofoo</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=8947</guid>
			<description><![CDATA[I tried 'systemctl hibernate' on LL, and it fails. This is having a swap partition larger than ram. It kills networking, the screen goes blank, but rather than going to sleep it goes back to desktop.<br />
<br />
Any ideas? Thanks]]></description>
			<content:encoded><![CDATA[I tried 'systemctl hibernate' on LL, and it fails. This is having a swap partition larger than ram. It kills networking, the screen goes blank, but rather than going to sleep it goes back to desktop.<br />
<br />
Any ideas? Thanks]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Slow shutdown systemd]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=8936</link>
			<pubDate>Fri, 29 Sep 2023 11:50:26 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=2">valtam</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=8936</guid>
			<description><![CDATA[I resolved my slow shutdown with this generic fix:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo mousepad /etc/systemd/system.conf</code></div></div><br />
change:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>#DefaultTimeoutStopSec=90s</code></div></div><br />
to:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>DefaultTimeoutStopSec=10s</code></div></div><br />
My personal root causes were: <span style="font-weight: bold;" class="mycode_b">Session c2</span> and <span style="font-weight: bold;" class="mycode_b">User Login Management</span> both hanging. Now shutdown is almost instant.]]></description>
			<content:encoded><![CDATA[I resolved my slow shutdown with this generic fix:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo mousepad /etc/systemd/system.conf</code></div></div><br />
change:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>#DefaultTimeoutStopSec=90s</code></div></div><br />
to:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>DefaultTimeoutStopSec=10s</code></div></div><br />
My personal root causes were: <span style="font-weight: bold;" class="mycode_b">Session c2</span> and <span style="font-weight: bold;" class="mycode_b">User Login Management</span> both hanging. Now shutdown is almost instant.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Slow boot fix for systemd-networkd-wait-online.service]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=8935</link>
			<pubDate>Fri, 29 Sep 2023 11:33:29 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=2">valtam</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=8935</guid>
			<description><![CDATA[Made my boot times from 1 minute, to a few seconds:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo systemctl edit --full systemd-networkd-wait-online.service</code></div></div><br />
change:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ExecStart=/lib/systemd/systemd-networkd-wait-online</code></div></div><br />
to:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ExecStart=/lib/systemd/systemd-networkd-wait-online --timeout=5</code></div></div><br />
reboot.<br />
<br />
Fix is specific ONLY to this systemd service.]]></description>
			<content:encoded><![CDATA[Made my boot times from 1 minute, to a few seconds:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo systemctl edit --full systemd-networkd-wait-online.service</code></div></div><br />
change:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ExecStart=/lib/systemd/systemd-networkd-wait-online</code></div></div><br />
to:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ExecStart=/lib/systemd/systemd-networkd-wait-online --timeout=5</code></div></div><br />
reboot.<br />
<br />
Fix is specific ONLY to this systemd service.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Wrong keyboard on logscreen]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=8929</link>
			<pubDate>Mon, 25 Sep 2023 16:04:18 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=5642">Jean-Marc B</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=8929</guid>
			<description><![CDATA[Hi folks !<br />
<br />
First some context : installed LL on an old Samsung Netbook N150 a few months back. I move a lot, and I much prefer a small laptop than a tablet. Don't need somehting powerful, using it just to take notes, browse the web and watch a video. So far, so good.<br />
<br />
But since the end of August, after an update, I've discovered that on the login screen, the keyboard is all wrong, it's impossible to put in my pass word without the virtual keyboard.<br />
<br />
What is weird :<br />
<br />
- fr (for Fench azerty) is displayed in the right corner of the screen as usual,<br />
- when I invoque the virtual keyboard, it's displayed as azerty, put when I use it, it changes to qwerty,<br />
- moreover, when I acces to desktop after logging in, the keyboard is correctly set to French azerty again,<br />
<br />
So far, I've only be able to by pass the problem by setting the computer to auto log in at startup. It's not really a problem, but I don't like it very much.<br />
<br />
Any idea to resolve the problem ?]]></description>
			<content:encoded><![CDATA[Hi folks !<br />
<br />
First some context : installed LL on an old Samsung Netbook N150 a few months back. I move a lot, and I much prefer a small laptop than a tablet. Don't need somehting powerful, using it just to take notes, browse the web and watch a video. So far, so good.<br />
<br />
But since the end of August, after an update, I've discovered that on the login screen, the keyboard is all wrong, it's impossible to put in my pass word without the virtual keyboard.<br />
<br />
What is weird :<br />
<br />
- fr (for Fench azerty) is displayed in the right corner of the screen as usual,<br />
- when I invoque the virtual keyboard, it's displayed as azerty, put when I use it, it changes to qwerty,<br />
- moreover, when I acces to desktop after logging in, the keyboard is correctly set to French azerty again,<br />
<br />
So far, I've only be able to by pass the problem by setting the computer to auto log in at startup. It's not really a problem, but I don't like it very much.<br />
<br />
Any idea to resolve the problem ?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[I want to make it boot faster]]></title>
			<link>https://www.linuxliteos.com/forums/showthread.php?tid=8868</link>
			<pubDate>Wed, 12 Jul 2023 21:05:54 +0800</pubDate>
			<dc:creator><![CDATA[<a href="https://www.linuxliteos.com/forums/member.php?action=profile&uid=5869">shuantsu</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.linuxliteos.com/forums/showthread.php?tid=8868</guid>
			<description><![CDATA[My linux lite is taking a while to boot. Can I make it faster?<br />
<br />
<span style="font-weight: bold;" class="mycode_b">My pc specifications:</span><br />
<br />
System:    Host: OptiPlex-360 Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.16.0 <br />
           Distro: Linux Lite 6.4 LTS base: Ubuntu 22.04.2 LTS (Jammy Jellyfish) <br />
Machine:   Type: Desktop System: Dell product: OptiPlex 360 v: N/A serial: &lt;superuser/root required&gt; <br />
           Mobo: Dell model: 0T656F v: A01 serial: &lt;superuser/root required&gt; BIOS: Dell v: A07 date: 06/18/2012 <br />
CPU:       Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 6144 KiB <br />
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11970 <br />
           Speed: 2237 MHz min/max: 2000/3000 MHz Core speeds (MHz): 1: 2397 2: 2274 <br />
Graphics:  Device-1: NVIDIA GF119 [GeForce GT 610] vendor: ZOTAC driver: nouveau v: kernel bus ID: 01:00.0 <br />
           Display: x11 server: X.Org 1.21.1.4 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz <br />
           OpenGL: renderer: NVD9 v: 4.3 Mesa 22.2.5-0ubuntu0.1~22.04.3 direct render: Yes <br />
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 <br />
           Device-2: NVIDIA GF119 HDMI Audio vendor: ZOTAC driver: snd_hda_intel v: kernel bus ID: 01:00.1 <br />
           Sound Server: ALSA v: k5.15.0-76-generic <br />
Network:   Device-1: Broadcom and subsidiaries NetLink BCM5784M Gigabit Ethernet PCIe vendor: Dell driver: tg3 v: kernel <br />
           port: dc80 bus ID: 02:00.0 <br />
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:23:ae:b7:14:10 <br />
           IF-ID-1: lxcbr0 state: down mac: 00:16:3e:00:00:00 <br />
Drives:    Local Storage: total: 111.79 GiB used: 25.75 GiB (23.0%) <br />
           ID-1: /dev/sda model: SSD 120GB size: 111.79 GiB temp: 39 C <br />
Partition: ID-1: / size: 108.98 GiB used: 25.74 GiB (23.6%) fs: ext4 dev: /dev/sda3 <br />
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: nouveau temp: 46 C <br />
           Fan Speeds (RPM): N/A <br />
Info:      Processes: 197 Uptime: 9m Memory: 3.75 GiB used: 1.18 GiB (31.4%) Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 <br />
           Shell: bash v: 5.1.16 inxi: 3.0.38<br />
<br />
This is the <span style="font-weight: bold;" class="mycode_b">systemd-analyze time</span> output:<br />
<br />
Startup finished in 4.138s (kernel) + 18.051s (userspace) = 22.190s <br />
graphical.target reached after 18.007s in userspace<br />
<br />
This is the <span style="font-weight: bold;" class="mycode_b">systemd-analyze blame</span> output:<br />
<br />
11.849s logrotate.service<br />
11.793s networking.service<br />
10.493s gpu-manager.service<br />
 8.212s NetworkManager-wait-online.service<br />
 2.524s lightdm.service<br />
 2.523s plymouth-quit-wait.service<br />
 2.123s snapd.service<br />
 1.896s systemd-random-seed.service<br />
 1.616s systemd-udev-settle.service<br />
 1.575s dev-sda3.device<br />
 1.512s blueman-mechanism.service<br />
 1.200s networkd-dispatcher.service<br />
 1.008s snapd.seeded.service<br />
  986ms udisks2.service<br />
  772ms accounts-daemon.service<br />
  549ms polkit.service<br />
  535ms NetworkManager.service<br />
  532ms avahi-daemon.service<br />
  459ms thermald.service<br />
  457ms ModemManager.service<br />
  453ms wpa_supplicant.service<br />
  452ms systemd-logind.service<br />
  421ms lxc-net.service<br />
  416ms nmbd.service<br />
  413ms apparmor.service<br />
  406ms virtualbox.service<br />
  335ms rsyslog.service<br />
  315ms keyboard-setup.service<br />
  314ms zfs-load-module.service<br />
  311ms cups.service<br />
  298ms systemd-journald.service<br />
  277ms systemd-udev-trigger.service<br />
  277ms systemd-udevd.service<br />
  242ms systemd-modules-load.service<br />
  238ms systemd-journal-flush.service<br />
  237ms user@1000.service<br />
  212ms resolvconf-pull-resolved.service<br />
  211ms ubiquity.service<br />
  204ms smbd.service<br />
  202ms snapd.apparmor.service<br />
  188ms systemd-resolved.service<br />
  179ms grub-common.service<br />
  177ms e2scrub_reap.service<br />
  164ms alsa-restore.service<br />
  156ms ntp.service<br />
  140ms update-notifier-download.service<br />
  121ms hddtemp.service<br />
  113ms lvm2-monitor.service<br />
  112ms lm-sensors.service<br />
  101ms lxc.service<br />
   99ms modprobe@fuse.service<br />
   96ms systemd-networkd.service<br />
   85ms packagekit.service<br />
   83ms systemd-tmpfiles-setup.service<br />
   81ms grub-initrd-fallback.service<br />
   72ms upower.service<br />
   54ms systemd-sysusers.service<br />
   49ms modprobe@chromeos_pstore.service<br />
   48ms systemd-fsck@dev-disk-by\x2duuid-78F1\x2d468B.service<br />
   43ms zfs-share.service<br />
   43ms dev-loop0.device<br />
   43ms dev-mqueue.mount<br />
   41ms sys-kernel-debug.mount<br />
   41ms dev-hugepages.mount<br />
   40ms sys-kernel-tracing.mount<br />
   37ms kmod-static-nodes.service<br />
   34ms modprobe@configfs.service<br />
   33ms dns-clean.service<br />
   30ms modprobe@drm.service<br />
   30ms plymouth-start.service<br />
   29ms plymouth-read-write.service<br />
   29ms systemd-networkd-wait-online.service<br />
   28ms systemd-sysctl.service<br />
   27ms swapfile.swap<br />
   26ms systemd-remount-fs.service<br />
   25ms zfs-mount.service<br />
   24ms zfs-volume-wait.service<br />
   22ms modprobe@pstore_blk.service<br />
   21ms systemd-tmpfiles-setup-dev.service<br />
   20ms user-runtime-dir@1000.service<br />
   20ms modprobe@ramoops.service<br />
   17ms boot-efi.mount<br />
   15ms modprobe@efi_pstore.service<br />
   15ms openvpn.service<br />
   14ms console-setup.service<br />
   13ms systemd-update-utmp.service<br />
   12ms finalrd.service<br />
   12ms ifupdown-pre.service<br />
   11ms sys-fs-fuse-connections.mount<br />
   11ms rtkit-daemon.service<br />
   10ms systemd-user-sessions.service<br />
    9ms sys-kernel-config.mount<br />
    9ms casper-md5check.service<br />
    9ms systemd-update-utmp-runlevel.service<br />
    8ms snap-core-15511.mount<br />
    8ms proc-sys-fs-binfmt_misc.mount<br />
    8ms modprobe@pstore_zone.service<br />
    5ms setvtrgb.service<br />
  969us snapd.socket<br />
   51us blk-availability.service<br />
<br />
Sometimes the networking.service is taking almost 20sec.<br />
I wanted it to boot faster, what can I do?]]></description>
			<content:encoded><![CDATA[My linux lite is taking a while to boot. Can I make it faster?<br />
<br />
<span style="font-weight: bold;" class="mycode_b">My pc specifications:</span><br />
<br />
System:    Host: OptiPlex-360 Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.16.0 <br />
           Distro: Linux Lite 6.4 LTS base: Ubuntu 22.04.2 LTS (Jammy Jellyfish) <br />
Machine:   Type: Desktop System: Dell product: OptiPlex 360 v: N/A serial: &lt;superuser/root required&gt; <br />
           Mobo: Dell model: 0T656F v: A01 serial: &lt;superuser/root required&gt; BIOS: Dell v: A07 date: 06/18/2012 <br />
CPU:       Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 6144 KiB <br />
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11970 <br />
           Speed: 2237 MHz min/max: 2000/3000 MHz Core speeds (MHz): 1: 2397 2: 2274 <br />
Graphics:  Device-1: NVIDIA GF119 [GeForce GT 610] vendor: ZOTAC driver: nouveau v: kernel bus ID: 01:00.0 <br />
           Display: x11 server: X.Org 1.21.1.4 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz <br />
           OpenGL: renderer: NVD9 v: 4.3 Mesa 22.2.5-0ubuntu0.1~22.04.3 direct render: Yes <br />
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 <br />
           Device-2: NVIDIA GF119 HDMI Audio vendor: ZOTAC driver: snd_hda_intel v: kernel bus ID: 01:00.1 <br />
           Sound Server: ALSA v: k5.15.0-76-generic <br />
Network:   Device-1: Broadcom and subsidiaries NetLink BCM5784M Gigabit Ethernet PCIe vendor: Dell driver: tg3 v: kernel <br />
           port: dc80 bus ID: 02:00.0 <br />
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:23:ae:b7:14:10 <br />
           IF-ID-1: lxcbr0 state: down mac: 00:16:3e:00:00:00 <br />
Drives:    Local Storage: total: 111.79 GiB used: 25.75 GiB (23.0%) <br />
           ID-1: /dev/sda model: SSD 120GB size: 111.79 GiB temp: 39 C <br />
Partition: ID-1: / size: 108.98 GiB used: 25.74 GiB (23.6%) fs: ext4 dev: /dev/sda3 <br />
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: nouveau temp: 46 C <br />
           Fan Speeds (RPM): N/A <br />
Info:      Processes: 197 Uptime: 9m Memory: 3.75 GiB used: 1.18 GiB (31.4%) Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 <br />
           Shell: bash v: 5.1.16 inxi: 3.0.38<br />
<br />
This is the <span style="font-weight: bold;" class="mycode_b">systemd-analyze time</span> output:<br />
<br />
Startup finished in 4.138s (kernel) + 18.051s (userspace) = 22.190s <br />
graphical.target reached after 18.007s in userspace<br />
<br />
This is the <span style="font-weight: bold;" class="mycode_b">systemd-analyze blame</span> output:<br />
<br />
11.849s logrotate.service<br />
11.793s networking.service<br />
10.493s gpu-manager.service<br />
 8.212s NetworkManager-wait-online.service<br />
 2.524s lightdm.service<br />
 2.523s plymouth-quit-wait.service<br />
 2.123s snapd.service<br />
 1.896s systemd-random-seed.service<br />
 1.616s systemd-udev-settle.service<br />
 1.575s dev-sda3.device<br />
 1.512s blueman-mechanism.service<br />
 1.200s networkd-dispatcher.service<br />
 1.008s snapd.seeded.service<br />
  986ms udisks2.service<br />
  772ms accounts-daemon.service<br />
  549ms polkit.service<br />
  535ms NetworkManager.service<br />
  532ms avahi-daemon.service<br />
  459ms thermald.service<br />
  457ms ModemManager.service<br />
  453ms wpa_supplicant.service<br />
  452ms systemd-logind.service<br />
  421ms lxc-net.service<br />
  416ms nmbd.service<br />
  413ms apparmor.service<br />
  406ms virtualbox.service<br />
  335ms rsyslog.service<br />
  315ms keyboard-setup.service<br />
  314ms zfs-load-module.service<br />
  311ms cups.service<br />
  298ms systemd-journald.service<br />
  277ms systemd-udev-trigger.service<br />
  277ms systemd-udevd.service<br />
  242ms systemd-modules-load.service<br />
  238ms systemd-journal-flush.service<br />
  237ms user@1000.service<br />
  212ms resolvconf-pull-resolved.service<br />
  211ms ubiquity.service<br />
  204ms smbd.service<br />
  202ms snapd.apparmor.service<br />
  188ms systemd-resolved.service<br />
  179ms grub-common.service<br />
  177ms e2scrub_reap.service<br />
  164ms alsa-restore.service<br />
  156ms ntp.service<br />
  140ms update-notifier-download.service<br />
  121ms hddtemp.service<br />
  113ms lvm2-monitor.service<br />
  112ms lm-sensors.service<br />
  101ms lxc.service<br />
   99ms modprobe@fuse.service<br />
   96ms systemd-networkd.service<br />
   85ms packagekit.service<br />
   83ms systemd-tmpfiles-setup.service<br />
   81ms grub-initrd-fallback.service<br />
   72ms upower.service<br />
   54ms systemd-sysusers.service<br />
   49ms modprobe@chromeos_pstore.service<br />
   48ms systemd-fsck@dev-disk-by\x2duuid-78F1\x2d468B.service<br />
   43ms zfs-share.service<br />
   43ms dev-loop0.device<br />
   43ms dev-mqueue.mount<br />
   41ms sys-kernel-debug.mount<br />
   41ms dev-hugepages.mount<br />
   40ms sys-kernel-tracing.mount<br />
   37ms kmod-static-nodes.service<br />
   34ms modprobe@configfs.service<br />
   33ms dns-clean.service<br />
   30ms modprobe@drm.service<br />
   30ms plymouth-start.service<br />
   29ms plymouth-read-write.service<br />
   29ms systemd-networkd-wait-online.service<br />
   28ms systemd-sysctl.service<br />
   27ms swapfile.swap<br />
   26ms systemd-remount-fs.service<br />
   25ms zfs-mount.service<br />
   24ms zfs-volume-wait.service<br />
   22ms modprobe@pstore_blk.service<br />
   21ms systemd-tmpfiles-setup-dev.service<br />
   20ms user-runtime-dir@1000.service<br />
   20ms modprobe@ramoops.service<br />
   17ms boot-efi.mount<br />
   15ms modprobe@efi_pstore.service<br />
   15ms openvpn.service<br />
   14ms console-setup.service<br />
   13ms systemd-update-utmp.service<br />
   12ms finalrd.service<br />
   12ms ifupdown-pre.service<br />
   11ms sys-fs-fuse-connections.mount<br />
   11ms rtkit-daemon.service<br />
   10ms systemd-user-sessions.service<br />
    9ms sys-kernel-config.mount<br />
    9ms casper-md5check.service<br />
    9ms systemd-update-utmp-runlevel.service<br />
    8ms snap-core-15511.mount<br />
    8ms proc-sys-fs-binfmt_misc.mount<br />
    8ms modprobe@pstore_zone.service<br />
    5ms setvtrgb.service<br />
  969us snapd.socket<br />
   51us blk-availability.service<br />
<br />
Sometimes the networking.service is taking almost 20sec.<br />
I wanted it to boot faster, what can I do?]]></content:encoded>
		</item>
	</channel>
</rss>