Announcement

**Schwarzer Kater** · May 14, 2024, 04:13 AM

Bluetooth can be e.g. connected to USB internally or externally (is it an internal daughterboard or is it an external Bluetooth adapter?).

What is the output of lsusb -tv ?

**bill-lancaster** · May 14, 2024, 04:20 AM

Thank you Schwarzer, its an internal usb device

:~$ lsusb -tv

Code:

[FONT=monospace][COLOR=#000000]:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M [/COLOR]
   ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   ID 1d6b:0002 Linux Foundation 2.0 root hub
   |__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
       ID 248a:8367 Maxxter Telink Wireless Receiver
   |__ Port 2: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 12M
       ID 248a:8367 Maxxter Telink Wireless Receiver
   |__ Port 7: Dev 3, If 0, Class=Mass Storage, Driver=uas, 480M
       ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
   |__ Port 8: Dev 4, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
       ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
   |__ Port 9: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M
       ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
   |__ Port 9: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
       ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
   |__ Port 9: Dev 5, If 2, Class=Audio, Driver=snd-usb-audio, 480M
       ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
   |__ Port 9: Dev 5, If 3, Class=Audio, Driver=snd-usb-audio, 480M
       ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
[COLOR=#54ff54][B]bil[/B][/COLOR][/FONT]

**bill-lancaster** · May 14, 2024, 04:30 AM

Thank you, I see what you mean.

Code:

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 248a:8367 Maxxter Telink Wireless Receiver
    |__ Port 2: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 248a:8367 Maxxter Telink Wireless Receiver
    |__ Port 7: Dev 3, If 0, Class=Mass Storage, Driver=uas, 480M
        ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
    |__ Port 8: Dev 4, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
        ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    |__ Port 9: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M
        ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
    |__ Port 9: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
        ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
    |__ Port 9: Dev 5, If 2, Class=Audio, Driver=snd-usb-audio, 480M
        ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
    |__ Port 9: Dev 5, If 3, Class=Audio, Driver=snd-usb-audio, 480M
        ID 046d:0990 Logitech, Inc. QuickCam Pro 9000

**Schwarzer Kater** · May 14, 2024, 04:48 AM

Hm, I don't see Bluetooth in your lsusb output (but sometimes I am blind

)…

What do sudo service bluetooth status and rfkill say?

You can also enter bluetoothctl then show to get informations and to quit this program just enter exit afterwards.

PS: There was a kernel update recently for 22.04 LTS - did Bluetooth work before this? Does Bluetooth work when you boot from a live USB stick with Kubuntu 22.04.4 LTS?

**bill-lancaster** · May 14, 2024, 04:56 AM

Code:

~$ sudo service bluetooth status
[sudo] password for bill:
○ bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

May 14 09:47:29 bill-Vostro-3470 systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 14 09:48:15 bill-Vostro-3470 systemd[1]: Condition check resulted in Bluetooth service being skipped.

and

Code:

:~$ rfkill
ID TYPE DEVICE      SOFT      HARD
 0 wlan phy0   unblocked unblocked

**Schwarzer Kater** · May 14, 2024, 05:05 AM

So it seems your Bluetooth hardware is not recognized at all anymore…

Did you try booting from a live USB with Kubuntu 22.04.4 LTS?
--> On second thought: you could also try to boot with the previous kernel from the GRUB boot menu to test if it is a kernel issue.

**oshunluvr** · May 14, 2024, 05:09 AM

It's probable your blue tooth device died or has come loose. Most Dell laptops I have messed with over the years have a small device card that usually has wifi and bluetooth on one card. If it was working at all, you would have seen this:

Code:

stuart@office:~$ rfkill
ID TYPE      DEVICE      SOFT      HARD
0 bluetooth hci0   unblocked unblocked
1 wlan      phy0     blocked unblocked

If you're handy enough, you can flip that thing over and remove the battery and any service panels with a small screwdriver and look for a plug-in circuit board about the size of a half-dollar (but not round, lol). It will have a couple small wires connected directly to the card that are for the antennae. It will either have a couple screws or a spring clip holding it in place. It's possible that it just wiggled loose and re-seating it will bring it back to life.

Also possible it just died. Good news is you could replace it through Dell. Alternately, a Bluetooth USB thingy will work and not cost more than a few dollars.

**Schwarzer Kater** · May 14, 2024, 05:14 AM

Hardware failure or a loose/bad connection is also a possibilty, of course.

If you follow oshunluvr's suggestion: Please don't forget to take appropriate measures to avoid static electricity charge whenever working inside of a computer!

**oshunluvr** · May 14, 2024, 05:15 AM

FYI, this is your wifi/bluetooth device:

Code:

 |__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 248a:8367 Maxxter Telink Wireless Receiver
|__ Port 2: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 12M
ID 248a:8367 Maxxter Telink Wireless Receiver

Curious what kernel you're using and have you changed anything system related lately? Seems highly unlikely that a kernel change would make a difference, but you never know. Try booting to an earlier kernel. There are bugs occasionally. That device is widely supported.

**bill-lancaster** · May 14, 2024, 05:45 AM

Actually its a Dell Vostro PC. I'll look at the Bluetooth card etc and report back.
Tried booting from a 22.04 DVD, Bluetooth still missing.

**Schwarzer Kater** · May 14, 2024, 05:53 AM

Slightly OT:
oshunluvr: I can't comment on a comment, so.

We have had several incidents (and destroyed hardware components) presumably involving static electricity charge over the years when I worked as a computer technician (it were mostly apprentices who caused this)… I also participated in a few trainings where we tested static electricity charge (both provoked situations by e.g. dragging one's feet across a carpet or handling synthetic clothes and unprovoked situations) - you could see the effects quite clearly in the dark during these tests.
I know that in 99% nothing happens when working inside of a computer - but better to be safe than sorry.

For working in a laptop you could first touch something metal within reach like a radiator if you don't have an antistatic mat and to be safe then additionally touch something inside the laptop like a shielding.

**bill-lancaster** · May 14, 2024, 06:51 AM

Couldn't see a Bluetooth/wifi card in the PC.
Figured out the 'boot from earlier grub' thing and I now have a working Bluetooth.
What should I do now?

**Schwarzer Kater** · May 14, 2024, 07:40 AM

Well, presumably the latest kernel update in (K)ubuntu 22.04 LTS (to 6.5.0-35) has caused this then.

I would keep booting into the previous kernel via the GRUB boot menu until there is a new kernel update that resolves this.
This would involve several steps for me:

Make sure that the working kernel is not removed by the next kernel update (*Ubuntu normally keeps the current kernel and the one before and removes any older - automatically installed - ones).

So I would set the working kernel to "manually installed" - then it won't get removed. After you have booted with the working kernel (in your case this should be 6.5.0-28-generic) you can do this in Konsole with
sudo apt-mark manual linux-image-$(uname -r) .

If a newer kernel works in the future, to revert the changes start with the "old" working kernel and in Konsole enter sudo apt-mark auto linux-image-$(uname -r) .
.
Alter the GRUB boot menu so it will always show, wait for your input and have your last choice preselected.

You can do this e.g. with the Kate text editor.
Please sudo cp /etc/default/grub /etc/default/grub.orig in Konsole first before altering the GRUB settings with Kate, so you have a backup of the file if anything goes wrong or you want to return to the original settings later on.

After this start Kate, open /etc/default/grub with it and
a) replace the line
GRUB_DEFAULT=0
with the two lines
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
and
b) replace the line
GRUB_TIMEOUT_STYLE=hidden
with
GRUB_TIMEOUT_STYLE=menu
and
c) replace the line
GRUB_TIMEOUT=0
with
GRUB_TIMEOUT=-1
and
d) add the line
GRUB_DISABLE_SUBMENU=true

Now save the file in Kate (you will have to enter your password to do so) and in Konsole
sudo update-grub .

You will see the effect with the next reboot .

In the future if you want or need to you can revert the changes either manually with Kate again or simply by sudo cp /etc/default/grub.orig /etc/default/grub in Konsole.

**bill-lancaster** · May 14, 2024, 07:45 AM

Well thank you so much, In fact I found 3 versions of grub and I booted from the 2nd one. I'll follow you advice and hopefully all will be well.

Announcement

Bluetooth stopped working

Bluetooth stopped working

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment