USB, Bluetooth and wifi don't start at boot

English Hardware
21

Thanks for posting a good and bad log, that makes diffing things possible and that often gives you a clue.

This time not however and that is because the log is not detailed enough, it looks to me what you see being printed on the screen when you boot the machine with “quiet=no”. Both logs are only about 270 lines.

Please use sudo journalctl -b -1/-2/-3/… to get the more detailed logs and post these. For me that starts with:

Jun 25 08:23:21 grondagame kernel: microcode: updated early: 0x19 → 0x28, date = 2019-11-12
Jun 25 08:23:21 grondagame kernel: Linux version 6.3.7-1-default (geeko@buildhost) (gcc (SUSE Linux) 13.1.1 20230522 [revision dd36656ada05731c069ecd5b1878380294fb1f3e], GNU ld (GNU Binutils; openSUSE Tumble>
Jun 25 08:23:21 grondagame kernel: Command line: BOOT_IMAGE=/vmlinuz-6.3.7-1-default root=UUID=95cde02d-4818-4ba3-a3ff-de690f5f1d56 splash=silent quiet security=apparmor
Jun 25 08:23:21 grondagame kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Jun 25 08:23:21 grondagame kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Jun 25 08:23:21 grondagame kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
Jun 25 08:23:21 grondagame kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jun 25 08:23:21 grondagame kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using ‘standard’ format.
Jun 25 08:23:21 grondagame kernel: signal: max sigframe size: 1776
Jun 25 08:23:21 grondagame kernel: BIOS-provided physical RAM map:
Jun 25 08:23:21 grondagame kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Jun 25 08:23:21 grondagame kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Jun 25 08:23:21 grondagame kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Jun 25 08:23:21 grondagame kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved

22

This is what I got:

sudo journalctl -b -1/-2/-3/
journalctl: invalid option -- '1'

I then started the creation of the log file without options, you can find it here: Boot.log Hope this helps more.

23

This is what “man journalctl” says about -1/-2/-3/… :wink:

 -b [[ID][±offset]|all], --boot[=[ID][±offset]|all]
     Show messages from a specific boot. This will add a match for "_BOOT_ID=".

     The argument may be empty, in which case logs for the current boot will be shown.

     If the boot ID is omitted, a positive offset will look up the boots starting from the beginning of
     the journal, and an equal-or-less-than zero offset will look up boots starting from the  end of the
     journal. Thus, 1 means the first boot found in the journal in chronological order, 2 the second 
     and so on; while -0 is the last boot, -1 the boot before last, and so on. An  empty offset is 
     equivalent to specifying -0, except when the current boot is not the last boot (e.g. because 
     --directory was specified to look at logs from a different machine).

Did you have a look at the log yourself? It starts good but after some lines there is “lines 1-17…skipping…” and the same text is repeated and repeated, so no useful information.

Try to find the a successful boot, for example -3 and a failing boot, for example -2

Then do “sudo journalctl -b -X > [good/bad].log” (replace X with the correct negative boot number). This will write the log to good.log/bad.log; post these files.

24

boot -b -3: boot -b -3
boot -b -2: boot -b -2

Is this what you need? Sorry, but I have never used these commands before and I didn’t understand the man page so it was guessing.
Again thank you for the effort and time you put into helping me, it is greatly appreciated.

25

Yes, that is what is helpful, I guess the boot-b3 the good log, boot-b2 the bad log.

What I did is strip of the timestamps and them diff the files and that shows (left b2, right b3):

Screenshot_20230625_225932
Screenshot_20230625_2259321398×955 179 KB

Also noted some USB errors in the b2 log but not in the b3 log:

$ grep 'kernel: usb.*error' ~/Downloads/boot-b2.log
Jun 25 12:17:55 openSUSE kernel: usb 3-3: device descriptor read/64, error -110
Jun 25 12:18:11 openSUSE kernel: usb 3-3: device descriptor read/64, error -110
Jun 25 12:18:16 openSUSE kernel: usb 3-3: device descriptor read/64, error -110
Jun 25 12:18:32 openSUSE kernel: usb 3-3: device descriptor read/64, error -110
Jun 25 12:18:43 openSUSE kernel: usb 3-3: device not accepting address 6, error -62
Jun 25 12:18:54 openSUSE kernel: usb 3-3: device not accepting address 7, error -62
$ grep 'kernel: usb.*error' ~/Downloads/boot-b3.log

$ errno 110
ETIMEDOUT 110 Connection timed out
$ errno 62
ETIME 62 Timer expired

So the problem is with USB 3-3. On that bus there are in the good case:

  • MediaTek Inc. Wireless_Device
  • OKLIC USB Mouse

Also the Logitech USB Receiver on USB 3-2 is not loaded.

The problem is likely that either the MediaTek or OKLIC device is behaving bad or that some cables are bad.

Try:

  • moving these devices to another port
  • remove the device from the system
  • replace the device with a alternative device
  • replace the cable where possible
26

Wow, you have been busy.

I did post this before but I do it again here:

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

Bus 3 Device 3 is: Foxconn / Hon Hai Wireless_Device.

inxi -Fxxxrz gives me this, just a small part of the output:
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: **btusb** v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 3-3:3 chip-ID: 0489:e0d8
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends

The correct bootlog mentions Mediatek Wireless device: could it be a different name for the same product? In the output of lsusb I don’t see the name Mediatek, just Foxconn / Hon Hai Wireless
I found this website: Bluetooth
They mention the name Mediatek in the first (and only answer) so I really believe you are on to something. I thought the error was caused by USB and that it influenced BT as well, but it seems it is the other way around. They also say a patch is in kernel 5.19, I use 6.3.7, so if things went well I shouldn’t have this error. But …

OKLIC USB Mouse: I have 1 mouse, the Logitech M220 wireless mouse and the K295 wireless keyboard combo. I use a USB dongle (receiver) for them which is connected to a KVM switch because, unfortunately, I do have to share Keyboard, Video and Mouse with a Windows laptop from the office when I work from home. As an alternatif I could switch cables but selecting the right laptop with a push on a button is much easier to do.
The dongle is a true Logitech device, I found this: Dongle On my dongle I see the code C-U0010 as is used on this website.

I found this: Oklic Turns out it is made by Areson Technology which still doesn’t ring a bell here. No idea what that can be, as said I have 1 mouse: a Logitech M220.

I wonder, both the devices which are not entirely working well are connected to USB Bus 3. Logitech receiver on device 6, Foxconn Bluetooth on device 3. Is it possible when one doesn’t work (doesn’t start or whatever) does that influence the entire bus 3, meaning one depends on another?

That’s all I found so far. Again many thanks Marel.

27

The errors you get “usb 3-3: device descriptor read/64, error -110” do not point to a driver missing functionality but to a hardware problem. I Would replace the device.

28

That will probably be difficult since it is a built-in device, plus as I wrote before I had the same trouble with my previous laptop which was a complete different brand.
I know I should not write this, but the last 5 or so boots were all without trouble. I know, I will jinx it but I had to write it. Yesterday I had updates again and maybe one of them helped.

30

@JanMussche

When you first installed Tumbleweed, did you encounter these issues? You mentioned “new problems” at the beginning of your post. At what point did you encounter these problems? Can you revert your system to before the problems and see which updated packages might be causing the issue?

Did you try a live distro on DVD or USB (openSUSE, Ubuntu, etc.) and see if you are having the same issues with Bluetooth, USB, and login? That might confirm that it is not a software issue (i.e. something got borked on your Tumbleweed operating system during an update for example) and might be a hardware issue. Granted though, a live distro won’t load the Nvidia drivers for your system. If you find your hardware working with the live distro, I’d venture that something went wrong with your installed Tumbleweed. Searching for the reason may be difficult but as someone previously mentioned, maybe a data backup, OS reinstall, and data restoration might be easier and in order.

To download a live version of openSUSE on a USB stick; would be curious to know if you have the same issues. See the link “Alternative Downloads” on the Download pages for:

Tumbleweed: openSUSE Tumbleweed - Get openSUSE
Leap: openSUSE Leap - Get openSUSE

As for me, I found rolling releases, while more exciting with much more recent packages, eventually created some instability in other packages or in the system. I have a “newer” gaming laptop with dual GPUs (Intel and Nvidia GeoForce RTX 3050Ti). Tumbleweed was great but I ended up reverting back to Leap. My laptop still works great with the older kernel, no issues with the hardware, even with dual GPUs (though admittedly I had to work through some other hardware issues). For using newer packages in openSUSE Leap (apps like Firefox, LibreOffice, etc.), flatpak came to the rescue!

All the best,
Dad4Linux

31

In the mean time I have switched to Fedora Linux and until now I am enjoying it so very much. With my new laptop I had a couple of problems when I was using Tumbleweed, and now they disappeared, although I have to say I got one new issue in return.
The things I had with Tumbleweed were:

  • Tearing pictures when using Nvidia (Tearing). I needed to use the Nvidia GPU cause he built-in AMD could not manage 2 monitors on X11. I could not make Wayland work so it was either AMD with 1 monitor or Nvidia on 2 but with tearing.
  • In KDE display settings the vertical position of 1 monitor in relation to the other automatically changed. Since the external is a 1920x1080 and the built in is 2560x1600, it means there is a place on the builtin monitor where you can’t cross over to the external one with the mouse. I want the bottom parts of both monitors to be at the same place so only at the top of the built-in monitor I can’t move over to the external monitor. This was changed constantly which was very annoying.
  • Bluetooth and USB had problems. Sometimes they both worked fine, sometimes they started later (after a minute or so) and sometimes Bluetooth did not start at all.

Now all of these issues (problems?) are gone. Every time when I boot it just works.
I boot into a Wayland session with the AMD GPU and I have perfect pictures on 2 monitors without tearing.
The monitors stay at the correct place in the settings so moving over to the other screen is easy.
Bluetooth and USB start up fine without problems.

The one problem I have now, which did not exist on Tumbleweed, is that I can’t control the brightness of the built-in monitor. In TW I could just place my mouse over the battery icon on the lower panel and use the mouse wheel to adjust the brightness, this does not work now. Have to find a way for that. (should anyone have an idea please let me know)

I do want to thank everyone for taking the time to help me, this is amazing what people do for others who need help. Thank you so much for that.

32

Enjoy your “journey” with RH … :slight_smile:
.

.

Screenshot_20230701_233120_Google
Screenshot_20230701_233120_Google540×499 56.4 KB

2 Likes