Hello,
New problems, apart form the Nvidia problems I had already: Nvidia
Symptoms:
When I boot I can’t use my mouse for over a minute. The cursor is located on the boarder between the 2 monitors, but it’s frozen.
Bluetooth is not started (correctly). When I ask for the status it is: inactive (dead)
I see a window asking for my root password to start the wifi connection, something normally happens automatically at boot.
Things have worked fine before, I could use the mouse straight away, I did get an enabled Bluetooth and the wifi connected automatically. It’s just that this happens sometimes, although at the moment it is with every boot.
Even now, after several minutes, when I type this:
sudo systemctl enable bluetooth
[sudo] password for root:
[User: jan] @ [Server: openSUSE] - [Directory: ~]
$ sudo systemctl start bluetooth
[User: jan] @ [Server: openSUSE] - [Directory: ~]
$ sudo systemctl status bluetooth
○ bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: inactive (dead)
Docs: man:bluetoothd(8)
Bluetooth is still dead. Mouse and keyboard are working though, meaning USB is working.
For much info about my laptop please have a look at this website: Hardware probe, or checkout the info below.
I have no idea what to do now. Is it something hardware and Linux related, is it Tumbleweed which causes these problems? I don’t know.
Please help. Thank you.
You talk about the boot process. Then you talk about a window popping up to ask for the root password. Is that then on the Display Managers login page?
I’m not sure if I understand what you mean with the Display managers login page, but it is just a window on my desktop asking for my password so the wifi can be enabled.
The description in this thread only describes problems during boot. And as the boot (visually) ends with the appearance of the login screen (which is don by the Display Manager (dm, in the form of e.g. kdm, sddm, lightdm, gdm, …) and thus is the only place that such GUI thing as popup window is possible, I assumed that it is there and then.
But now you talk about a desktop, which is only started after login and way after the boot has finished. And even now you do not tell us which Desktop Environment you are using.
I am afraid you should have some more imagination about what other people then you yourself know about what you see and do without having a chance to look over your shoulder.
Not a bad idea to consider reinstalling everything, if you have things backed up correctly that might be the fastest way to get the machine in nicely working state.
No, I don’t. I had the same problems with my previous laptop so that is why I think it is not hardware related.
Well, I could do that, I do have backups of everything but I have re-installed the OS several times before, including other OS’es, and it doesn’t really help. It can work fine for weeks and then suddenly the error returns, stays for several boots and then it is gone again. No idea what is causing it.
Nobody else having problems with Bluetooth, and/or USB not starting?
What does journalctl tell you with regards to USB and Bluetooth. If it fails some fhints would be there I guess. I know that some laptops have a function key to disable Bluetooth. It is not triggered by accident?
Bluetooth is more troublesome but that is almost never due to starting up the service and USB not starting is pretty rare I would say.
I saw the thread about your Nvidia problems, I would think it is not strange to think that the problems you experience are related to experiments you did getting that to work, is that an option?
That is not a bad thought, but as I wrote I had the same problems (USB and Bluetooth) on my previous laptop and there I was not experimenting with Nvidia simply because it wasn’t there. I had 1 Intel GPU and that was it, no need to tinker. Why did I buy another laptop??? :=(
If you had the exact same problem on your old laptop I think there is good chance the problem comes back with a fresh reinstall so likely better to find out what is causing the problem.
What kind of USB devices are connected to the laptop and did you have them connected also at your old laptop? I once had a “cheap” mouse that triggered problems so you could try replacing your USB devices to see if that makes a difference.
Well, here it is. After a reboot I saw this in journalctl:
Jun 25 12:17:01 openSUSE systemd[1]: Stopped target Bluetooth Support.
Jun 25 12:17:01 openSUSE systemd[1]: Stopping Bluetooth service...
Jun 25 12:17:01 openSUSE systemd[1]: Stopped Bluetooth service.
Jun 25 12:17:54 openSUSE NetworkManager[1462]: <info> [1687688274.3807] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.42.6/libnm-device-plugin-bluetooth.so)
Jun 25 12:19:08 openSUSE systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
12:17:01 was the time the system was going down ( I guess ), starting at 12:17:54 it came back up
The folder /sys/class/bluetooth does not exist
Does this tell you something? One more thing, I first had to wait over a minute to have my USB keyboard and mouse before I could login.
ps:
This is the outcome of the same command after the next boot where it all worked from the start:
Jun 25 12:30:08 openSUSE NetworkManager[1403]: <info> [1687689008.5651] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.42.6/libnm-device-plugin-bluetooth.so)
Jun 25 12:30:09 openSUSE kernel: Bluetooth: Core ver 2.22
Jun 25 12:30:09 openSUSE kernel: Bluetooth: HCI device and connection manager initialized
Jun 25 12:30:09 openSUSE kernel: Bluetooth: HCI socket layer initialized
Jun 25 12:30:09 openSUSE kernel: Bluetooth: L2CAP socket layer initialized
Jun 25 12:30:09 openSUSE kernel: Bluetooth: SCO socket layer initialized
Jun 25 12:30:09 openSUSE systemd[1]: Starting Bluetooth service...
Jun 25 12:30:09 openSUSE bluetoothd[1843]: Bluetooth daemon 5.66
Jun 25 12:30:09 openSUSE bluetoothd[1843]: Bluetooth management interface 1.22 initialized
Jun 25 12:30:09 openSUSE kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jun 25 12:30:09 openSUSE kernel: Bluetooth: BNEP filters: protocol multicast
Jun 25 12:30:09 openSUSE kernel: Bluetooth: BNEP socket layer initialized
Jun 25 12:30:09 openSUSE systemd[1]: Started Bluetooth service.
Jun 25 12:30:09 openSUSE systemd[1]: Reached target Bluetooth Support.
Jun 25 12:30:11 openSUSE kernel: Bluetooth: hci0: Device setup in 2176453 usecs
Jun 25 12:30:11 openSUSE kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Jun 25 12:30:11 openSUSE kernel: Bluetooth: hci0: AOSP extensions version v1.00
Jun 25 12:30:11 openSUSE kernel: Bluetooth: hci0: AOSP quality report is supported
Jun 25 12:30:11 openSUSE kernel: Bluetooth: MGMT ver 1.22
Jun 25 12:30:20 openSUSE kernel: Bluetooth: hci0: Device setup in 138384 usecs
Jun 25 12:30:20 openSUSE kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Jun 25 12:30:20 openSUSE kernel: Bluetooth: hci0: AOSP extensions version v1.00
Jun 25 12:30:20 openSUSE kernel: Bluetooth: hci0: AOSP quality report is supported
Jun 25 12:30:22 openSUSE kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 25 12:30:22 openSUSE kernel: Bluetooth: RFCOMM socket layer initialized
Jun 25 12:30:22 openSUSE kernel: Bluetooth: RFCOMM ver 1.11
The fact that /sys/class/bluetooth does not exist suggests that the driver cannot be loaded. Since the driver is usb dependent the problems seem to be connected.
Your grub file contains several boot options which I am now unable to find because the hardware probe has gone. It dealt with AMD/ATI options. They probably are there to make sure the Nvidia works? Since the USB controller seems to be of the same make I suspect the cause lies with those options.
Hello Natasha,
Thank you for answering and trying to help me. Much appreciated.
I have read your answer a few times and still don’t know what it is you wrote.
The first line sounds pretty straight forward. Now that both USB and Bluetooth work I do see the directory /sys/class.
But then.
I found 2 files which I will append here. I hope this is what you wrote about. If not, let me know and I will send other info.
/boot/grub2/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set btrfs_relative_path="n"
export btrfs_relative_path
if [ -f ${config_directory}/grubenv ]; then
load_env -f ${config_directory}/grubenv
elif [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${env_block}" ] ; then
set env_block="(${root})${env_block}"
export env_block
load_env -f "${env_block}"
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
if [ "${env_block}" ] ; then
save_env -f "${env_block}" next_entry
fi
set boot_once=true
else
set default="${saved_entry}"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
if [ "${env_block}" ] ; then
save_env -f "${env_block}" saved_entry
else
save_env saved_entry
fi
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 3f18177c-4786-4467-8f6f-d0966f017851
font="/usr/share/grub2/unicode.pf2"
fi
if loadfont $font ; then
if [ "${grub_platform}" = "efi" ]; then
echo "Please press 't' to show the boot menu on this console"
fi
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
for i in gfxterm; do
if [ x${use_append} = xtrue ]; then
terminal_output --append $i
elif terminal_output $i; then
use_append=true;
fi
done
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root ba70d786-2ade-46f6-963d-832d1f07382c
insmod gfxmenu
loadfont ($root)/grub2/themes/openSUSE/DejaVuSans-Bold14.pf2
loadfont ($root)/grub2/themes/openSUSE/DejaVuSans10.pf2
loadfont ($root)/grub2/themes/openSUSE/DejaVuSans12.pf2
loadfont ($root)/grub2/themes/openSUSE/ascii.pf2
insmod png
set theme=($root)/grub2/themes/openSUSE/theme.txt
export theme
if [ x${boot_once} = xtrue ]; then
set timeout=0
elif [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=2
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=2
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/00_tuned ###
set tuned_params=""
set tuned_initrd=""
### END /etc/grub.d/00_tuned ###
### BEGIN /etc/grub.d/05_crypttab ###
### END /etc/grub.d/05_crypttab ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'openSUSE Tumbleweed' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3f18177c-4786-4467-8f6f-d0966f017851' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root ba70d786-2ade-46f6-963d-832d1f07382c
echo 'Loading Linux 6.3.7-1-default ...'
linux /vmlinuz-6.3.7-1-default root=UUID=3f18177c-4786-4467-8f6f-d0966f017851 splash=silent resume=/dev/disk/by-uuid/aa88641b-3ca5-4cb2-863b-675f01e7a045 mitigations=auto quiet security=apparmor nosimplefb=1
echo 'Loading initial ramdisk ...'
initrd /initrd-6.3.7-1-default
}
submenu 'Advanced options for openSUSE Tumbleweed' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-3f18177c-4786-4467-8f6f-d0966f017851' {
menuentry 'openSUSE Tumbleweed, with Linux 6.3.7-1-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.3.7-1-default-advanced-3f18177c-4786-4467-8f6f-d0966f017851' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root ba70d786-2ade-46f6-963d-832d1f07382c
echo 'Loading Linux 6.3.7-1-default ...'
linux /vmlinuz-6.3.7-1-default root=UUID=3f18177c-4786-4467-8f6f-d0966f017851 splash=silent resume=/dev/disk/by-uuid/aa88641b-3ca5-4cb2-863b-675f01e7a045 mitigations=auto quiet security=apparmor nosimplefb=1
echo 'Loading initial ramdisk ...'
initrd /initrd-6.3.7-1-default
}
menuentry 'openSUSE Tumbleweed, with Linux 6.3.7-1-default (recovery mode)' --hotkey=3 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.3.7-1-default-recovery-3f18177c-4786-4467-8f6f-d0966f017851' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root ba70d786-2ade-46f6-963d-832d1f07382c
echo 'Loading Linux 6.3.7-1-default ...'
linux /vmlinuz-6.3.7-1-default root=UUID=3f18177c-4786-4467-8f6f-d0966f017851
echo 'Loading initial ramdisk ...'
initrd /initrd-6.3.7-1-default
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/35_fwupd ###
### END /etc/grub.d/35_fwupd ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ###
### END /etc/grub.d/80_suse_btrfs_snapshot ###
### BEGIN /etc/grub.d/90_persistent ###
### END /etc/grub.d/90_persistent ###
### BEGIN /etc/grub.d/95_textmode ###
if [ "${grub_platform}" = "efi" ]; then
# On EFI systems we can only have graphics *or* serial, so allow the user
# to switch between the two
hiddenentry 'Text mode' --hotkey 't' {
set textmode=true
terminal_output console
}
fi
### END /etc/grub.d/95_textmode ###
/etc/default/grub
# If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update
# /boot/grub2/grub.cfg.
# Uncomment to set your own custom distributor. If you leave it unset or empty, the default
# policy is to determine the value from /etc/os-release
GRUB_DISTRIBUTOR=
GRUB_DEFAULT=saved
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=2
GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=/dev/disk/by-uuid/aa88641b-3ca5-4cb2-863b-675f01e7a045 mitigations=auto quiet security=apparmor nosimplefb=1"
GRUB_CMDLINE_LINUX=""
# Uncomment to automatically save last booted menu entry in GRUB2 environment
# variable `saved_entry'
# GRUB_SAVEDEFAULT="true"
#Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
# GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
#Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL="gfxterm"
# The resolution used on graphical terminal
#note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE="auto"
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
# GRUB_DISABLE_LINUX_UUID=true
#Uncomment to disable generation of recovery mode menu entries
# GRUB_DISABLE_RECOVERY="true"
#Uncomment to get a beep at grub start
# GRUB_INIT_TUNE="480 440 1"
GRUB_BACKGROUND=
GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt
SUSE_BTRFS_SNAPSHOT_BOOTING="true"
GRUB_USE_LINUXEFI="true"
GRUB_DISABLE_OS_PROBER="false"
GRUB_ENABLE_CRYPTODISK="n"
GRUB_CMDLINE_XEN_DEFAULT="vga=gfx-1024x768x16"
Sorry I’m afraid I must have seen it wrong. If you use the failsafe boot does the also occur there?
On another note I went through the bugzilla.o.o and that didn’t tell me much, however the kernel bugzilla did come up with something, which might seem related: https://bugzilla.kernel.org/show_bug.cgi?id=217475
Yes, /sys/class/bluetooth not present is likely what is the problem but are those 5 lines everything you get between 12:17:01 and 12:19:08? I pretty sure there is more.
Please post the output of "sudo journalctl --since=“2023-05-25 12:17:01” --until “2023-05-25 12:19:09"” using susepaste and post the link here.
Jun 25 12:10:49 openSUSE kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Jun 25 12:17:01 openSUSE systemd[1]: Stopped target Bluetooth Support.
Jun 25 12:17:01 openSUSE systemd[1]: Stopping Bluetooth service...
Jun 25 12:17:01 openSUSE systemd[1]: Stopped Bluetooth service.
Jun 25 12:17:54 openSUSE NetworkManager[1462]: <info> [1687688274.3807] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.42.6/libnm-device-plugin-bluetooth.so)
Jun 25 12:19:08 openSUSE systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jun 25 12:22:06 openSUSE systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
I added a line in front and one in the back of the 5 lines I sent earlier to show these 5 lines were all I got. Mind you, this is the situation where things didn’t work.
lsusb
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0489:e0d8 Foxconn / Hon Hai Wireless_Device
Bus 003 Device 006: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 005: ID 25a7:6672 Areson Technology Corp OKLIC
Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 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 002: ID 048d:c102 Integrated Technology Express, Inc. ITE Device(8910)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I did assume going down meant “the system was powered down” and with came back up I thought it was after booted up again and then I expect a lot more messages, but this not not given too much information and I think you mean something different with “going down”.
In your start post you indicated:
Better post the boot log for this, I expect it to be more than 1000 lines.
I took 2 parts of the complete boot.log, one in which the laptop booted as it should always do (Correct) and one in which USB made me wait 1 minute and I had no Bluetooth at all. (incorrect)
Have fun. I am very grateful that you want to do this, I have read the files but it doesn’t mean anything to me. I mean, I don’t see what goes wrong and what not.
