1

I have ubuntu 18.04 LTS installed in my machine. Since the last update (kernel 4.15.0-176-generic) the machine is very slow to boot (login) and there are problems after the login (slow and laggy). At the login screen the keyboard, touch-pad and mouse do not respond for more than 3 minutes. Once the keyboard,touch-pad and mouse are responding and I am able to login the computer is slow and laggy. Sometimes the wifi is not working because the driver wasn't loaded during the boot process (I can manualy load the driver with the modprobe command without errors and the wifi works fine) .

This problem is not always present, in some cases after rebooting the system boots and works without any problem (it is not slow neither laggy), and I don't have to wait the 3 minutes for the keyboard, touch-pad and mouse to became responsive.

Laptop is Lenovo V330-15IKB CPU Intel i5-8250U 12GB RAM with only a SSD 256GB only Ubuntu OS (no dual boot).

When the problem is present I see that dmesg shows a jump in time (about 190sec equal to more than 3 minutes)

dmesg

[    4.355662] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    4.359659] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    4.362007] proc_thermal 0000:00:04.0: Creating sysfs group for PROC_THERMAL_PCI
[    4.365280] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[    4.414071] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[    4.470665] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    4.476281] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    4.501241] media: Linux media interface: v0.10
[    4.514681] Bluetooth: Core ver 2.22
[    4.514715] NET: Registered protocol family 31
[    4.514715] Bluetooth: HCI device and connection manager initialized
[    4.514718] Bluetooth: HCI socket layer initialized
[    4.514720] Bluetooth: L2CAP socket layer initialized
[    4.514728] Bluetooth: SCO socket layer initialized
[    4.568449] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
[    4.568450] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[    4.568451] RAPL PMU: hw unit of domain package 2^-14 Joules
[    4.568451] RAPL PMU: hw unit of domain dram 2^-14 Joules
[    4.568452] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[    4.568452] RAPL PMU: hw unit of domain psys 2^-14 Joules
[    4.755297] AVX2 version of gcm_enc/dec engaged.
[    4.755298] AES CTR mode by8 optimization enabled
[    4.787951] random: crng init done
[    4.787952] random: 7 urandom warning(s) missed due to ratelimiting
[    5.224511] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[    5.282583] r8169 0000:03:00.0 enp3s0: link down
[    5.282683] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[    6.480097] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.480098] Bluetooth: BNEP filters: protocol multicast
[    6.480101] Bluetooth: BNEP socket layer initialized
[  184.421868] i2c_hid i2c-SYNA2B42:00: i2c-SYNA2B42:00 supply vdd not found, using dummy regulator
[  184.494360] input: SYNA2B42:00 06CB:8252 as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA2B42:00/0018:06CB:8252.0003/input/input6
[  184.494687] hid-generic 0018:06CB:8252.0003: input,hidraw2: I2C HID v1.00 Mouse [SYNA2B42:00 06CB:8252] on i2c-SYNA2B42:00
[  184.500071] mei_me 0000:00:16.0: enabling device (0004 -> 0006)
[  184.520724] idma64 idma64.0: Found Intel integrated DMA 64-bit
[  184.542324] asus_wmi: Asus Management GUID not found
[  184.560287] kvm: disabled by bios
[  184.638732] kvm: disabled by bios
[  184.639522] Linux video capture interface: v2.00
[  184.642685] intel_rapl: Found RAPL domain package
[  184.642686] intel_rapl: Found RAPL domain core
[  184.642687] intel_rapl: Found RAPL domain uncore
[  184.642688] intel_rapl: Found RAPL domain dram
[  184.697656] kvm: disabled by bios
[  184.733371] kvm: disabled by bios
[  184.855831] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: TM3336-002, fw id: 2654938
[  184.962083] input: Synaptics TM3336-002 as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA2B42:00/0018:06CB:8252.0003/input/input7
[  184.962800] hid-rmi 0018:06CB:8252.0003: input,hidraw2: I2C HID v1.00 Mouse [SYNA2B42:00 06CB:8252] on i2c-SYNA2B42:00
[  209.717367] rfkill: input handler disabled

I have restarted many time the machine, and in some case I can see in the output of the dmesg command the following lines related to the loading the wifi driver/firmware:

[    9.527848] iwlwifi 0000:02:00.0: loaded firmware version 29.1044073957.0 op_mode iwlmvm
[    9.588579] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210

I don't know why sometime the driver is not loaded during the boot up process. Even that, when the driver is loaded at the boot up process the main problem is still present (touch pad, mouse and keyboard not responding at login screen and slow and laggy behavior after login).

I don't know what is causing the problem so far. How can I troubleshoot and solve this problem?

cactus
  • 21
  • Are you dual-booting with Windows? – ChanganAuto Jun 12 '22 at 19:48
  • No. No dual boot. I only have Ubuntu on my notebook installed on a SSD. – cactus Jun 12 '22 at 20:06
  • If so it's an hardware and/or firmware issue. So... (1) update UEFI ("BIOS") and (2) disable fast boot in UEFI. – ChanganAuto Jun 12 '22 at 20:09
  • The BIOS is configured in "legacy mode" (UEFI disable), I haven't seen any fastboot option. Is it posible that the last update caused some firmware or driver compatibily problems? – cactus Jun 12 '22 at 20:34
  • If you installed in Legacy mode then that was a dumb move and likely the root of the problem. And, of course, regardless of the mode you should update the firmware. Now, keep in mind that Legacy mode was designed ONLY for OSes that don't support UEFI mode. The last one being Windows XP, out of support since 2014, the reason to be of the Legacy/CSM support died right there and then. Do the smart thing: ALWAYS install in UEFI mode if the machine has UEFI. – ChanganAuto Jun 12 '22 at 20:38
  • 1
    Just to clarify, I had Ubuntu 18.04 LTS installed in my machine since 2018 and it was working well. The problem I describe in the original post started three week ago after I accepted a software update. I don't think that the problem is related to the UEFI or BIOS mode. Even that I will take your advice, and next time I will install next OS in the UEFI mode. But for now I want to troubleshoot and repair the OS as it is installed at the moment. – cactus Jun 13 '22 at 17:05
  • Does this answer your question? How to decrease the boot time – Raffa Jul 01 '22 at 06:34
  • @Raffa I tried to disable NetworkManager-wait-online.service as it is suggested in the post you metion but it didn't solved my problem. I suspect that the cause of the problem is related to bluetooth or wifi firmware/drivers or maybe snap applications. – cactus Jul 02 '22 at 19:05

2 Answers2

0

I've the same problem and no fix, but as workaround: I boot with an older kernel version (4.15.0-176), that I've managed to keep during system updates.

As help for further troubleshooting: My machine is a HP laptop (bought in 2018) with dual boot for Windows; Ubuntu (actually: xubuntu) installation was in UEFI mode; I've tried to update the BIOS(UEFI) but no results. I guess there is some change in latest kernel versions that triggers the problem.

Marco
  • 1
  • Do you know how can I boot with kernel version 4.15.0-176? Does the new updates erase old kernels version? Which wireless/bluethooth card do you have? – cactus Jul 16 '22 at 23:00
0

The problem was solved by updating the wifi card driver/firmware. I downloaded the last driver from: https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html

The driver I download is named as "iwlwifi-7265D-29.ucode".

Even when I already have the version 29 of the driver in my machine, the downloaded driver seems to be different:

sum and sha256 for the iwlwifi-7265D-29.ucode that I already had installed (original diver):

cactus@ssa:~$ sum /lib/firmware/iwlwifi-7265D-29.ucode
54500  1013
cactus@ssa:~$ sha256sum /lib/firmware/iwlwifi-7265D-29.ucode
cf3856c1eb5db22d9aafd8e2a0cf1794d4c3a442a9eaf11ccc1a53391a0a12fa  /lib/firmware/iwlwifi-7265D-29.ucode

sum and sha256 for the iwlwifi-7265D-29.ucode downloaded:

cactus@ssa:~$ sum /home/cactus/Downloads/iwlwifi-7265D-29.ucode
15972  1013
cactus@ssa:~$ sha256sum /home/cactus/Downloads/iwlwifi-7265D-29.ucode
f6776a50107cba4f68362b5cf8455f5a0db6a4e8d1e34f4ede6f26803458e25e  /home/cactus/Downloads/iwlwifi-7265D-29.ucode

After updating the driver and rebooting the initial problem (slow boot, touch pad and keyboard not responding for more than 3 minutes at login screen, slow and laggy behavior after login) disappeared.

I did a final test: I to switch back to the original driver version, and I could see that the problem was not present any more (even when I was using the original driver).

cactus
  • 21