Problem Description:
I was doing a massive copy (88 GB or so) from a network device to an external SSD. It took 2 or 3 hours. It apparently completed successfully. But now I find myself in the following situation.
My MX Mechanical Keyboard is no longer talking to my Laptop (Lenovo ThinkPad P16). Though the Kubuntu System Settings Bluetooth sees the keyboard, I can no longer connect to it or pair to it.
My BenQ RD240Q external monitor is no longer recognized by System Settings Displays tab. If I unplug it from my laptopâs HDMI port and then plug it back in I get a display like this:
Relevant System Information:
The laptop does have a NVidia RTX3500 GPU which has sometimes proved problematic but I am reluctant to suspect that here since there is also the issue of the keyboard not functioning. The one thing that unites these two issues besides when they happened is that both go through the KDE Plasma settings app.
Screenshots or Error Messages:
see above
What Iâve Tried:
Tried rebooting and power off, no luck there.
What Iâm looking for from the community:
Command line ways of investigating these issues.
What to look for in logs, journalctl, for both of these problems, the bluetooth keyboard problem and the second monitor problem.
$ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
I have had such difficulties before. The driver was installed and was running and now we get this. I think the driver is the reason for the monitor non-recognition. How can I tell if it is running?
$ journalctl -b -p 3 dmesg | grep -iE "nvidia|bluetooth|usb|pcie|error|fail" Feb 05 14:59:07 aigas kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) Feb 05 14:59:07 aigas kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) Feb 05 14:59:07 aigas kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) Feb 05 14:59:07 aigas kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) Feb 05 14:59:07 aigas systemd-udevd[738]: /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14 Invalid key 'SYSFS'. Feb 05 14:59:07 aigas systemd-udevd[738]: /etc/udev/rules.d/60-brother-mfp-brscan5-1.0.2-2.rules:17 Invalid key 'SYSFS'. Feb 05 14:59:07 aigas kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) Feb 05 14:59:07 aigas kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) Feb 05 14:59:07 aigas kernel: spi-nor spi0.0: unrecognized JEDEC id bytes: f7 f0 30 09 03 00 Feb 05 14:59:09 aigas bluetoothd[1589]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Feb 05 14:59:09 aigas bluetoothd[1589]: sap-server: Operation not permitted (1) Feb 05 14:59:09 aigas bluetoothd[1589]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters Feb 05 14:59:09 aigas bluetoothd[1589]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters Feb 05 14:59:10 aigas systemd-udevd[738]: /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14 Invalid key 'SYSFS'. Feb 05 14:59:10 aigas systemd-udevd[738]: /etc/udev/rules.d/60-brother-mfp-brscan5-1.0.2-2.rules:17 Invalid key 'SYSFS'. Feb 05 14:59:13 aigas systemd-udevd[738]: /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14 Invalid key 'SYSFS'. Feb 05 14:59:13 aigas systemd-udevd[738]: /etc/udev/rules.d/60-brother-mfp-brscan5-1.0.2-2.rules:17 Invalid key 'SYSFS'. Feb 05 14:59:30 aigas sddm-helper[2730]: gkr-pam: unable to locate daemon control file Feb 05 15:03:17 aigas kernel: Bluetooth: hci0: Unknown advertising packet type: 0x40 Feb 05 15:34:17 aigas kernel: scsi 0:0:0:1: Failed to get diagnostic page 0x1 Feb 05 15:34:17 aigas kernel: scsi 0:0:0:1: Failed to bind enclosure -19 Feb 05 15:54:59 aigas kernel: Bluetooth: hci0: Hardware error 0x0c Feb 05 15:54:59 aigas kernel: Bluetooth: hci0: Retrieving Intel exception info failed (-16) Feb 05 16:00:00 aigas systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. Feb 05 17:44:47 aigas kernel: Bluetooth: hci0: Unknown advertising packet type: 0x40 Feb 05 18:47:22 aigas kernel: Bluetooth: hci0: Hardware error 0x0c Feb 05 18:47:22 aigas kernel: Bluetooth: hci0: Retrieving Intel exception info failed (-16) Feb 05 18:47:44 aigas kernel: Bluetooth: hci0: Hardware error 0x0c Feb 05 18:47:44 aigas kernel: Bluetooth: hci0: Retrieving Intel exception info failed (-16) Feb 05 19:17:27 aigas kernel: audit: backlog limit exceeded Feb 05 19:17:27 aigas kernel: audit: backlog limit exceeded dmesg: read kernel buffer failed: Operation not permitted
I was using the machine to flash an SSD that is used in a Raspberry Pi-like device. I had to flash a new OS onto the deviceâs SSD. I was told to use something called rpi-imager. (https://github.com/raspberrypi/rpi-imager). This required a lengthy build which included several installations of stuff that probably fouled up my dependencies.
I tried reinstalling my nvidia driver but it wouldnât because depencencies.
And then it turned out I didnât need this d****d program at all. The new image came with its own imager.
So now I have to figure out how to uninstall this piece of crap and get my machine back to the correct dependencies.
For next time, there is a very well maintained snap of rpi-imager that the Canonical Rpi maintainer actually keeps up to date ⊠that will definitely not mess up your system
Nice to know, thanks, but can anyone tell me how to remove the bad one and restore my system to what it should be? My screenshot above tells me everything I need to install to get the driver working that the system wonât install. Is there some sort of âapt downgradeâ command that would revert the system to what it was?
The link to the github page shows more than one method to install the rpi-imager
Did you install the imager_2.0.6_amd64.AppImage?
Did you build your own AppImage?
Or something else?
I would suggest that you work in reverse order to the GitHub instructions:-
Youâll need elevated privileges (sudo) to remove some files if they are not stored in your user directory.
Remove the Appimage
Remove build-qt.sh (should be in opt/Qt according to GitHub)
You need to be careful here because you have Plasma which is built using QT framework
Delete the source code (from wherever you stored it)
Doing what you suggested did help. I removed all the things you said I should remove, except I donât do sudo apt autoremove after a bad experience with that. Additionally I got rid of /opt/Qt entirely based on your suggestion of looking at the directory.
Then I did a sudo apt remove of the driver, after which I could reinstall it and everything works again. Thanks.
sudo apt autoremove will first list the packages to be considered for removal.
It offers a Yes/No prompt - nothing is removed without user approval.
Anyway, if the topic is now solved, please mark the relevant post as the solution.
The platform software will automatically close the thread to prevent the discussion meandering off-topic in the future.
Look for kernel / driver errors
Check if Bluetooth service is healthy
Check display / GPU state
