Results 1 to 6 of 6

Thread: bluetooth device not reachable

  1. #1
    Join Date
    Apr 2009
    Location
    somewhere in Europe...
    Beans
    173
    Distro
    Ubuntu 10.04 Lucid Lynx

    bluetooth device not reachable

    I've tried several of the solutions proposed in the forum (all that I could find at least) but none of them work for me, I am on an asus with kubuntu 20.04, I installed and uninstalled bluez, blueman but nothing is happening....my earplugs are simply not connecting (NB I was able to connected to another device that has ubuntu 20.04 on it)

  2. #2
    Join Date
    May 2014
    Location
    /home
    Beans
    9,194
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: bluetooth device not reachable

    Post results from terminal for
    Code:
    lsusb; dmesg | egrep -i 'blue|firm'

  3. #3
    Join Date
    Apr 2009
    Location
    somewhere in Europe...
    Beans
    173
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: bluetooth device not reachable

    thank you, here we go (I uninstalled all bluetooth software because there was a chance they were conflicting with something)

    $ lsusb; dmesg | egrep -i 'blue|firm'
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 011: ID 8087:0a2a Intel Corp.
    Bus 001 Device 006: ID 145f:01c8 Trust Trust Wireless Mouse
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    [ 0.000000] [Firmware Bug]: TPM Final Events table missing or invalid
    [ 0.169538] Spectre V2 : Enabling Restricted Speculation for firmware calls
    [ 0.333423] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
    [ 1.088711] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
    [ 1.088732] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
    [ 1.588537] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
    [ 15.306307] elan_i2c i2c-ELAN1000:00: Elan Touchpad: Module ID: 0x0005, Firmware: 0x0004, Sample: 0x000d, IAP: 0x000e
    [ 15.323592] iwlwifi 0000:01:00.0: loaded firmware version 29.1654887522.0 op_mode iwlmvm
    [ 15.395752] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
    [ 711.898695] audit: type=1107 audit(1610884275.455:51): pid=800 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=
    "org.bluez" pid=22997 label="snap.chromium.chromium"


  4. #4
    Join Date
    May 2014
    Location
    /home
    Beans
    9,194
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: bluetooth device not reachable

    The 8087:0a2a device is Intel Bluetooth but there is no sign of the bluetooth firmware loading

  5. #5
    Join Date
    Apr 2009
    Location
    somewhere in Europe...
    Beans
    173
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: bluetooth device not reachable

    so you're saying my laptop has no bluetooth capacity? or that I should install some to gain the capacity to use bluetooth?
    Last edited by abelito8; January 21st, 2021 at 01:28 AM.

  6. #6
    Join Date
    Apr 2009
    Location
    somewhere in Europe...
    Beans
    173
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: bluetooth device not reachable

    I followed this thread
    https://itectec.com/ubuntu/ubuntu-ub...h-not-working/

    and I can connect, I can even listen to some sound...but it's completely scattered and keeps on getting disconnected....

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •