Trying to activate a bluetooth mouse

Help on all MX Re-spins
Message
Author
User avatar
MAYBL8
MX Packager
Posts: 599
Joined: Thu Dec 31, 2009 2:48 pm

Trying to activate a bluetooth mouse

#1 Post by MAYBL8 »

System Specs Below:

I get no bluetooth adapters available

Code: Select all

Snaphot created on: 20200413_2353
System:    Host: mx-kde Kernel: 5.4.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.4.0-3-amd64 root=UUID=2697ae54-f9f7-488c-a6dd-11828dcb8e57 ro 
           quiet 
           Desktop: KDE Plasma 5.14.5 tk: Qt 5.11.3 info: cairo-dock wm: kwin_x11 dm: LightDM 1.26.0 
           Distro: MX-19.1_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Convertible System: HP product: HP Spectre x360 Convertible 15-df1xxx v: N/A serial: <filter> 
           Chassis: type: 31 serial: <filter> 
           Mobo: HP model: 863F v: 54.14 serial: <filter> UEFI: AMI v: F.11 date: 10/14/2019 
Battery:   ID-1: BAT0 charge: 78.5 Wh condition: 78.5/78.5 Wh (100%) volts: 13.1/11.6 model: HP Primary 
           type: Li-ion serial: <filter> status: Full cycles: 31 
           Device-1: hid-0018:04F3:2992.0001-battery model: ELAN2514:00 04F3:2992 serial: N/A charge: N/A 
           status: N/A 
CPU:       Topology: Quad Core model: Intel Core i7-10510U bits: 64 type: MT MCP arch: Kaby Lake family: 6 
           model-id: 8E (142) stepping: C (12) microcode: CA L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36799 
           Speed: 800 MHz min/max: 400/4900 MHz Core speeds (MHz): 1: 1471 2: 1458 3: 1413 4: 1566 5: 1258 
           6: 1448 7: 1469 8: 1600 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:9b41 
           Device-2: NVIDIA GP108M [GeForce MX250] driver: N/A bus ID: 3b:00.0 chip ID: 10de:1d13 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics (Comet Lake 3x8 GT2) v: 4.6 Mesa 19.3.3 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:02c8 
           Sound Server: ALSA v: k5.4.0-3-amd64 
Network:   Device-1: Intel driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 chip ID: 8086:02f0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 504.19 GiB used: 28.75 GiB (5.7%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: HBRPEKNX0202AH size: 476.94 GiB block size: physical: 512 B 
           logical: 512 B speed: 15.8 Gb/s lanes: 2 serial: <filter> rev: HPS1 scheme: GPT 
           ID-2: /dev/nvme1n1 vendor: Intel model: HBRPEKNX0202AHO size: 27.25 GiB block size: physical: 512 B 
           logical: 512 B speed: 15.8 Gb/s lanes: 2 serial: <filter> rev: HPS2 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: 4060 
           bus ID: 00:17.0 chip ID: 8086.282a rev: N/A 
Partition: ID-1: / raw size: 40.00 GiB size: 39.12 GiB (97.81%) used: 10.80 GiB (27.6%) fs: ext4 
           dev: /dev/nvme0n1p5 
           ID-2: /home raw size: 200.00 GiB size: 195.86 GiB (97.93%) used: 17.93 GiB (9.2%) fs: ext4 
           dev: /dev/nvme0n1p6 
           ID-3: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/nvme0n1p7 
Sensors:   System Temperatures: cpu: 49.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.osuosl.org/pub/mxlinux/mx/repo/ buster main non-free
           2: deb http://ftp.osuosl.org/pub/mxlinux/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 290 Uptime: 16m Memory: 15.28 GiB used: 1.58 GiB (10.3%) Init: SysVinit v: 2.93 
           runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: quick-system-in 
           inxi: 3.0.36 

User avatar
JayM
Qualified MX Guide
Posts: 6793
Joined: Tue Jan 08, 2019 4:47 am

Re: Trying to activate a bluetooth mouse

#2 Post by JayM »

MAYBL8 wrote: Thu Apr 23, 2020 7:06 pm get no bluetooth adapters available
1. Search the manual for bluetooth.
2. Search the wiki for bluetooth.
3. Search the Arch wiki for bluetooth.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
MAYBL8
MX Packager
Posts: 599
Joined: Thu Dec 31, 2009 2:48 pm

Re: Trying to activate a bluetooth mouse

#3 Post by MAYBL8 »

Ok I will and I will document everything I do. I hope all of that finds the answer to my problem.

User avatar
MAYBL8
MX Packager
Posts: 599
Joined: Thu Dec 31, 2009 2:48 pm

Re: Trying to activate a bluetooth mouse

#4 Post by MAYBL8 »

Troubleshooting

Some recent BT dongles may not yet have drivers in the kernel and thus will not be recognized. The most likely solution is to upgrade the kernel.
Command-line tools can be helpful when problems arise.

To check if bluez daemon is running:

/etc/init.d/bluetooth status

Is this kernel new enough?

Code: Select all

$ uname -a
Linux mx-kde 5.4.0-3-amd64 #1 SMP Debian 5.4.13-1~mx19+1 (2020-01-19) x86_64 GNU/Linux

Code: Select all

$ /etc/init.d/bluetooth status
[ ok ] bluetooth is running.
More to come from the manual.

To check that your BT device is present and working:

hcitool dev

Code: Select all

$ hcitool dev
Devices:

Code: Select all

 lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root 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 06cb:00bb Synaptics, Inc. 
Bus 001 Device 003: ID 062a:5918 MosArt Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Not sure what this means but this is what the Debian Linux page said to run:

Code: Select all

$ hcitool scan
Device is not available: No such device
All of this is over my head:

Code: Select all

(blueman-assistant:31722): dbind-WARNING **: 21:04:45.099: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
/usr/bin/blueman-assistant:80: DeprecationWarning: Gtk.Assistant.set_page_header_image is deprecated
  self.assistant.set_page_header_image(pages[PAGE_INTRO], get_icon("blueman", 32))
/usr/bin/blueman-assistant:117: PyGTKDeprecationWarning: The keyword(s) "type" have been deprecated in favor of "message_type" respectively. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  d = Gtk.MessageDialog(type=Gtk.MessageType.ERROR, )
The wiki is the same info that is in the Manual.

Here is some more info from the Arch Wiki page:

Code: Select all

root@mx-kde:~# bluetoothctl
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# power on
No default controller available

Code: Select all

$ sudo /usr/lib/bluetooth/bluetoothd -n -d
bluetoothd[4797]: Bluetooth daemon 5.50
bluetoothd[4797]: Unknown key Discoverable for group General in /etc/bluetooth/main.conf
bluetoothd[4797]: src/main.c:parse_config() parsing /etc/bluetooth/main.conf
bluetoothd[4797]: src/main.c:parse_config() discovto=0
bluetoothd[4797]: src/main.c:parse_config() Key file does not have key “PairableTimeout” in group “General”
bluetoothd[4797]: src/main.c:parse_config() Key file does not have key “Privacy” in group “General”
bluetoothd[4797]: src/main.c:parse_config() Key file does not have key “Name” in group “General”
bluetoothd[4797]: src/main.c:parse_config() Key file does not have key “Class” in group “General”
bluetoothd[4797]: src/main.c:parse_config() Key file does not have key “DeviceID” in group “General”
bluetoothd[4797]: src/main.c:parse_config() Key file does not have key “ReverseServiceDiscovery” in group “General”
bluetoothd[4797]: src/main.c:parse_config() Key file does not have key “MinEncKeySize” in group “GATT”
bluetoothd[4797]: src/adapter.c:adapter_init() sending read version command
bluetoothd[4797]: Starting SDP server
bluetoothd[4797]: src/sdpd-service.c:register_device_id() Adding device id record for 0002:1d6b:0246:0532
bluetoothd[4797]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[4797]: src/plugin.c:add_plugin() Loading hostname plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading autopair plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading policy plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading neard plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading sap plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading a2dp plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading avrcp plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading hog plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading health plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading gap plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading scanparam plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading deviceinfo plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading midi plugin
bluetoothd[4797]: src/plugin.c:add_plugin() Loading battery plugin
bluetoothd[4797]: src/plugin.c:plugin_init() Loading plugins /usr/lib/x86_64-linux-gnu/bluetooth/plugins
bluetoothd[4797]: src/plugin.c:add_plugin() Loading sixaxis plugin
bluetoothd[4797]: profiles/health/hdp.c:hdp_manager_start() Starting Health manager
bluetoothd[4797]: profiles/input/suspend-none.c:suspend_init() 
bluetoothd[4797]: profiles/network/manager.c:read_config() /etc/bluetooth/network.conf: Key file does not have key “DisableSecurity” in group “General”
bluetoothd[4797]: profiles/network/manager.c:read_config() Config options: Security=true
bluetoothd[4797]: plugins/neard.c:neard_init() Setup neard plugin
bluetoothd[4797]: plugins/sixaxis.c:sixaxis_init() 
bluetoothd[4797]: src/main.c:main() Entering main loop
bluetoothd[4797]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[4797]: Bluetooth management interface 1.14 initialized
bluetoothd[4797]: src/adapter.c:read_version_complete() sending read supported commands command
bluetoothd[4797]: src/adapter.c:read_version_complete() sending read index list command
bluetoothd[4797]: src/adapter.c:read_commands_complete() Number of commands: 65
bluetoothd[4797]: src/adapter.c:read_commands_complete() Number of events: 35
bluetoothd[4797]: src/adapter.c:read_commands_complete() enabling kernel-side connection control
bluetoothd[4797]: src/adapter.c:read_index_list_complete() Number of controllers: 0
bluetoothd[4797]: src/profile.c:register_profile() sender :1.73
bluetoothd[4797]: src/profile.c:create_ext() Created "Message Notification"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.73
bluetoothd[4797]: src/profile.c:create_ext() Created "Message Access"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.73
bluetoothd[4797]: src/profile.c:create_ext() Created "Phone Book Access"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.73
bluetoothd[4797]: src/profile.c:create_ext() Created "Synchronization"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.73
bluetoothd[4797]: src/profile.c:create_ext() Created "File Transfer"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.73
bluetoothd[4797]: src/profile.c:create_ext() Created "Object Push"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.73
bluetoothd[4797]: src/profile.c:create_ext() Created ":1.73/org/bluez/obex/00005005_0000_1000_8000_0002ee000001/00005005-0000-1000-8000-0002ee000001"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.72
bluetoothd[4797]: src/profile.c:create_ext() Created "Headset Voice gateway"
bluetoothd[4797]: src/profile.c:register_profile() sender :1.72
bluetoothd[4797]: src/profile.c:create_ext() Created ":1.72/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb"
bluetoothd[4797]: plugins/hostname.c:property_changed() static hostname: mx-kde
bluetoothd[4797]: plugins/hostname.c:property_changed() pretty hostname: 
bluetoothd[4797]: plugins/hostname.c:property_changed() chassis: convertible
I have no idea what any of this means. All I know it still isn't working.

Code: Select all

root@mx-kde:~# dmesg | grep -i blue
[    5.746038] Bluetooth: Core ver 2.22
[    5.746049] Bluetooth: HCI device and connection manager initialized
[    5.746052] Bluetooth: HCI socket layer initialized
[    5.746053] Bluetooth: L2CAP socket layer initialized
[    5.746055] Bluetooth: SCO socket layer initialized
[    5.751565] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.751567] Bluetooth: BNEP filters: protocol multicast
[    5.751569] Bluetooth: BNEP socket layer initialized
More info:

Code: Select all

$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
Linux mx-kde 5.4.0-3-amd64 #1 SMP Debian 5.4.13-1~mx19+1 (2020-01-19) x86_64 GNU/Linux
00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
        Subsystem: Intel Corporation Device [8086:0074]
        Kernel driver in use: iwlwifi
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root 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 06cb:00bb Synaptics, Inc. 
Bus 001 Device 003: ID 062a:5918 MosArt Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[    6.771261] Bluetooth: Core ver 2.22
[    6.771294] Bluetooth: HCI device and connection manager initialized
[    6.771318] Bluetooth: HCI socket layer initialized
[    6.771328] Bluetooth: L2CAP socket layer initialized
[    6.771341] Bluetooth: SCO socket layer initialized
[    6.783486] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.783488] Bluetooth: BNEP filters: protocol multicast
[    6.783495] Bluetooth: BNEP socket layer initialized
[    2.397425] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[    2.512923] iwlwifi 0000:00:14.3: firmware: failed to load iwlwifi-QuZ-a0-hr-b0-50.ucode (-2)
[    2.513911] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[    2.513912] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
[    2.513923] iwlwifi 0000:00:14.3: firmware: failed to load iwlwifi-QuZ-a0-hr-b0-49.ucode (-2)
[    2.513924] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
[    2.516232] iwlwifi 0000:00:14.3: firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[    2.516589] iwlwifi 0000:00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
[    2.542531] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[    2.543534] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    2.590987] iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor.
[ 1400.388635] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[ 1400.388858] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[24812.492823] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[24812.493024] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[29675.293559] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[29675.293842] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[29713.647148] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[29713.647408] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[30097.204486] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[30097.204878] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[30427.806697] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[30427.806935] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[30472.912386] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[30472.912734] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[30511.194246] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[30511.194413] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[30847.231377] (NULL device *): firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-48.ucode
[30847.231415] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
bluetooth             659456  7 bnep
ecdh_generic           16384  1 bluetooth
rfkill                 28672  9 hp_wmi,bluetooth,cfg80211
crc16                  16384  2 bluetooth,ext4
Doing my own research I think this might be a kernel issue. I could be completely wrong.
Tried 5.4.0-4 Did not change anything.
Tried 5.5.0-1 Did not change anything.
Tried 5.6.0 Did not change anything.

User avatar
JayM
Qualified MX Guide
Posts: 6793
Joined: Tue Jan 08, 2019 4:47 am

Re: Trying to activate a bluetooth mouse

#5 Post by JayM »

Can you post the results of lsusb when it's plugged in so perhaps we can get its brand and model?

Is the problem with the mouse not working, or Bluetooth on the computer not working? Can you tell us what Bluetooth dongle you have (I assume it's a USB dongle as this is a desktop computer and those normally don't have built-in Bluetooth.)

(For everyone's info, OP is running KDE not Xfce per their QSI.)
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
MAYBL8
MX Packager
Posts: 599
Joined: Thu Dec 31, 2009 2:48 pm

Re: Trying to activate a bluetooth mouse

#6 Post by MAYBL8 »

Bluetooth is part of the internal wifi card.
It doesn't seem to recognize there is bluetooth there. I have confirmed it works in Windows 10. This laptop is dual boot.

This is from the spec sheet in the manual:

Wireless Integrated wireless local area network (WLAN) options by way of wireless module Dual PCIe WLAN antennas built into display assembly Support for the Intel 9560 ac 2×2 MU-MIMO + Bluetooth 5 M.2 1216 non-vPro MIPI+BRI WW WLAN module

User avatar
JayM
Qualified MX Guide
Posts: 6793
Joined: Tue Jan 08, 2019 4:47 am

Re: Trying to activate a bluetooth mouse

#7 Post by JayM »

If you boot from a standard MX-19.1 live USB (with Xfce) is your Bluetooth card detected?
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
MAYBL8
MX Packager
Posts: 599
Joined: Thu Dec 31, 2009 2:48 pm

Re: Trying to activate a bluetooth mouse

#8 Post by MAYBL8 »

I can only boot from an AHS version because the laptop is a Gen 10 CPU.
Will that work for your test?

Edit,
Looking back I might be able to boot to live usb but not install.
I'll give that a try and post back here.

User avatar
MAYBL8
MX Packager
Posts: 599
Joined: Thu Dec 31, 2009 2:48 pm

Re: Trying to activate a bluetooth mouse

#9 Post by MAYBL8 »

I used the AHS usb I had that has kernel 5.3.0-2 on it and bluetooth adapter not found on it either.

User avatar
MAYBL8
MX Packager
Posts: 599
Joined: Thu Dec 31, 2009 2:48 pm

Re: Trying to activate a bluetooth mouse

#10 Post by MAYBL8 »

My research has discovered that this laptop must be to new to get everything working depending on the kernel.
I went from 5.4 to 5.5 and sound quit working. Bluetooth doesn't work on any kernel.
Is there a place to go to see the development of kernels ?
What I found on the intel website was my laptop has a Comet lake CPU and Linux describes it as a
CPU: Topology: Quad Core model: Intel Core i7-10510U bits: 64 type: MT MCP arch: Kaby Lake family: 6

This is from intel website:

Code: Select all

Essentials

    Product Collection 10th Generation Intel® Core™ i7 Processors
    Code Name Products formerly Comet Lake
    Vertical Segment Mobile
    Processor Number i7-10510U

Post Reply

Return to “MX Respins”