I switched from Lubuntu to Linux Lite 5.2 about 6 months ago and, barring one minor hiccup, it has been working perfectly for me. I read here about the improvements and additions in 5.4, but none of them seem important to me. Since all is well with my 5.2, is there any real reason to upgrade to 5.4?

And, am I correct in thinking that all the updates that I have done since starting with LL 5.2 still has me on 5.2, NOT 5.4?

I recently tried reviving an Old PC that we hadn't used before by installing Linux Lite on it. It's been functioning alright, but the wifi stability is absolutely bogus. There are times were it just gives up searching for other networks, disabling the use of wifi until I decide to reboot the PC, making it a huge pain in the neck. I am aware my computer's capabilities are limited, but I want to at least make it so It can maintain a healthy signal when connecting to the internet. The router doesn't appear to be the problem, as other devices from the same room as the PC can access it too? Is it the driver? The wifi card? The pc was from a long time ago, 2009 I think, so could this be a factor?

My Old PC specs:
Powered by Dual-Core Intel Pentium E5300
2GB Ram
HP Pavilion Slimline
Running Linux 5.4

lshw -C network output:

Having a great number rsynch images in timeshift seems to prevent lite tweaks from locating kernels safely removable. After trimming down the saved snapshot list in timeshift old kernels can removed with no problem.
TC

I recently noticed a quirk with post update wifi connections which I believe is connected to timeshift and I think some users are attempting to solve it via network settings which have nothing to do with the quirk. I have three/four different LL 5.x installations and only one exhibits the loss of and inability to re-connect to a saved wifi connection after rebooting after updates and it is the one where timeshift is auto-scheduled. I don't use timeshift at all on the others. Also none of my connections are set to auto-connect. The quirk exhibits itself in the following ways:
The user runs updates normally and reboots the machine. The user selects the previous wifi connection that worked before and attempts to connect. The connection fails and after failing is no longer displayed in nm's connection list. Logging out and back in again does not make it reappear in the list. Editing the connection manually and saving it has no effect. All that works, I have discovered after experimenting a bit, is to log out to the login screen and then select shutdown and shut down the system. When booting again all will be normal. I do believe this is related to timeshift auto-scheduling usage and maybe a case where normal reboot code and systemd network management settings are not allowed to reset because of timeshift. As I have explained, logging out and shutting the system down after a normal update reboot alleviates the quirk.
TC   

I have been a Mint user for some years, but i found I could not use it on my original  Toshiba laptop of some age, as it's cpu and ram was far too small.  I read that Lite had had some success for those small laptops so, I downloaded it and Wow, My old Toshiba is working like a song. I'll be perusing the forum and will no doubt be in contact. C G

1) Along with the "system freezing" problem I have been having with 5.4, I also sometimes can't connect to the wifi I have been using for years.  I have a modem in the room next to my office and I also have a hot spot on my desk, and sometimes LL will simply not connect to them.

(and occasionally LL will connect to the modem but still will not work)

2) Also - I have a TP-Link TL-WN725N usb adapter, and I don't think LL recognizes it.

This is a dual boot system, and Windows still connects to both easily and they both work well.

suggestions?

Hi there,

I need some help to set up my Epson et-2750 inkjet printer. It is connected to by PC via a usb cable.
I downloaded and installed the EPSON drivers and utility - the scanner works perfectly, but the printer doesn't.

When I use the menu setup, it sees the printer but I can't print the test page.
Wen I use the CUPS web interface - same problem.

Kernel & Operating System Information
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
Kernel 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

USB Information
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 04b8:112a Seiko Epson Corp. ET-2750 Series  <== that's the one!
Bus 001 Device 005: ID 8087:0026 Intel Corp.
Bus 001 Device 007: ID 045e:0812 Microsoft Corp.
Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

usblp kernel module is loaded.

ls -l /dev/bus/usb/*/*
crw-rw-r--  1 root root 189,  0 May 13 17:07 /dev/bus/usb/001/001
crw-rw-r--  1 root root 189,  1 May 13 17:07 /dev/bus/usb/001/002
crw-rw-r--  1 root root 189,  3 May 13 17:07 /dev/bus/usb/001/004
crw-rw-r--  1 root root 189,  4 May 13 17:07 /dev/bus/usb/001/005
crw-rw-r--  1 root root 189,  5 May 13 17:07 /dev/bus/usb/001/006
crw-rw-r--  1 root root 189,  6 May 13 17:07 /dev/bus/usb/001/007
crw-rw-r--+ 1 root lp  189,  7 May 13 17:21 /dev/bus/usb/001/008
crw-rw-r--  1 root root 189, 128 May 13 17:07 /dev/bus/usb/002/001
crw-rw-r--  1 root root 189, 256 May 13 17:07 /dev/bus/usb/003/001
crw-rw-r--  1 root root 189, 384 May 13 17:07 /dev/bus/usb/004/001

ls -l /dev/usb/lp*
ls: cannot access '/dev/usb/lp*': No such file or directory

Is this the problem? If so, how do I create lp0?

Regards
Hagen

Hi

I install linux lite in my old computer and I am very happy with it .. but I can't succes to connect to my wifi network .. I no see the wifi network list
I try using my internal network (atheros AR5007EG wireless) .. and I test a external USB wifi (realtek 802.11n WLAN USB Adapter) .. but I have the same problem

I need help

Thanks

Sorry guys to ask but can you help me fix linux lite slow boot times.

Terminal:

systemd-analyze
Startup finished in 5.747s (kernel) + 31.859s (userspace) = 37.606s
graphical.target reached after 31.809s in userspace


systemd-analyze blame
15.113s networking.service                                 
11.583s blueman-mechanism.service                           
9.372s NetworkManager-wait-online.service                 
8.641s accounts-daemon.service                             
8.518s networkd-dispatcher.service                         
6.577s udisks2.service                                     
5.933s grub-common.service                                 
5.321s dev-sda2.device                                     
4.941s systemd-udev-settle.service                         
4.906s gpu-manager.service                                 
4.845s NetworkManager.service                             
4.645s polkit.service                                     
4.215s thermald.service                                   
4.115s systemd-journal-flush.service                       
3.732s systemd-resolved.service                           
3.693s lightdm.service                                     
3.679s plymouth-quit-wait.service                         
3.161s systemd-logind.service                             
2.965s ModemManager.service                               
2.732s avahi-daemon.service                               
2.397s wpa_supplicant.service                             
2.280s zfs-load-module.service                             
2.062s nmbd.service                                       
1.754s apparmor.service                                   
1.631s systemd-tmpfiles-setup.service                     
1.456s rsyslog.service                                     
1.323s systemd-networkd.service                           
1.161s systemd-udevd.service                               
  933ms systemd-modules-load.service                       
  863ms smbd.service                                       
  683ms lm-sensors.service                                 
  657ms ubiquity.service                                   
  588ms e2scrub_reap.service                               
  557ms systemd-tmpfiles-setup-dev.service                 
  532ms grub-initrd-fallback.service                       
  495ms systemd-udev-trigger.service                       
  491ms keyboard-setup.service                             
  483ms systemd-random-seed.service                         
  463ms systemd-sysctl.service                             
  418ms systemd-fsck@dev-disk-by\x2duuid-58C4\x2dFA1E.service
  366ms alsa-restore.service                               
  364ms upower.service                                     
  332ms systemd-sysusers.service                           
  317ms swapfile.swap                                       
  251ms ntp.service                                         
  236ms boot-efi.mount                                     
  224ms systemd-journald.service                           
  200ms dev-hugepages.mount                                 
  199ms dev-mqueue.mount                                   
  199ms sys-kernel-debug.mount                             
  198ms sys-kernel-tracing.mount                           
  196ms blk-availability.service                           
  194ms kmod-static-nodes.service                           
  194ms lvm2-monitor.service                               
  165ms zfs-volume-wait.service                             
  141ms [email protected]                                   
  138ms zfs-mount.service                                   
  124ms systemd-remount-fs.service                         
  70ms systemd-tmpfiles-clean.service                     
  57ms setvtrgb.service                                   
  47ms dns-clean.service                                   
  46ms pppd-dns.service                                   
  43ms ifupdown-pre.service                               
  40ms rtkit-daemon.service                               
  39ms console-setup.service                               
  38ms zfs-share.service                                   
  37ms systemd-user-sessions.service                       
  36ms hddtemp.service                                     
  25ms systemd-networkd-wait-online.service               
  21ms [email protected]                       
  20ms resolvconf-pull-resolved.service                   
  17ms finalrd.service                                     
  15ms plymouth-start.service                             
  12ms plymouth-read-write.service                         
    9ms systemd-update-utmp.service                         
    7ms openvpn.service                                     
    7ms systemd-update-utmp-runlevel.service               
    4ms sys-kernel-config.mount                             
    3ms sys-fs-fuse-connections.mount 

plz help.