[To Heck With It] Getting Bluetooth to work at boot

Questions about hardware, drivers and peripherals
Forum rules
Before you post please read how to get help
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

[To Heck With It] Getting Bluetooth to work at boot

Post by Arch_Enemy »

I bought a KB thinking I could use it to run my computer, my table, and my Samsung phone using DeX, but then I realized I bought a BT only model.
So, I got a BT dongle. It was almost plug and play, so searching here and elsewhere I actually had it working at boot, 2 times. Digging deeper I tried a few more things, it started at boot one more time and that was it. I have to use another KB to sign in, then re-pair the KB. Once it came up automatically, and once I had to click the "ON" button in BT.

Reading through this, I ran a command that gave me this output:

Code: Select all

[code]System:    Host: TimeWarp Kernel: 4.15.0-193-generic x86_64
           bits: 64 gcc: 7.5.0
           Desktop: MATE 1.20.1 (Gtk 3.22.30) info: mate-panel dm: lightdm
           Distro: Linux Mint 19 Tara
Machine:   Device: desktop Mobo: Intel model: DX58OG v: AAG10926-203 serial: N/A
           BIOS: Intel v: SOX5820J.86A.0920.2013.0729.0042 date: 07/29/2013
CPU:       Quad core Intel Xeon E5640 (-MT-MCP-)
           arch: Nehalem rev.2 cache: 12288 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 26584
           clock speeds: max: 3327 MHz 1: 2778 MHz 2: 3101 MHz 3: 2834 MHz
           4: 3212 MHz 5: 2888 MHz 6: 2176 MHz 7: 2739 MHz 8: 3327 MHz
Memory:    Using dmidecode: root required for dmidecode
Graphics:  Card: NVIDIA GK104 [GeForce GTX 660 OEM]
           bus-ID: 03:00.0 chip-ID: 10de:1185
           Display Server: x11 (X.Org 1.19.6 )
           drivers: (unloaded: modesetting,nvidia,fbdev,vesa,nouveau)
           Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
           OpenGL: renderer: llvmpipe (LLVM 10.0.0, 128 bits)
           version: 3.3 Mesa 20.0.8 (compat-v: 3.1) Direct Render: Yes
Audio:     Card-1 NVIDIA GK104 HDMI Audio Controller
           driver: snd_hda_intel bus-ID: 03:00.1 chip-ID: 10de:0e0a
           Card-2 Intel 82801JI (ICH10 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:3a3e
           Sound: Advanced Linux Sound Architecture v: k4.15.0-193-generic
Network:   Card: Intel 82567LF-2 Gigabit Network Connection
           driver: e1000e v: 3.2.6-k port: 4100
           bus-ID: 00:19.0 chip-ID: 8086:10cd
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1000.2GB (51.8% used)
           ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB serial: <filter>
Partition: ID-1: / size: 42G used: 28G (70%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 566G used: 456G (85%) fs: ext4 dev: /dev/sda2
RAID:      System: supported: N/A
           No RAID devices: /proc/mdstat, md_mod kernel module present
           Unused Devices: none
Sensors:   System Temperatures: cpu: 45.5C mobo: N/A gpu: 0.0:50C
           Fan Speeds (in rpm): cpu: N/A
Repos:     Active apt sources in file: /etc/apt/sources.list.d/dhor-myway-bionic.list
           deb http://ppa.launchpad.net/dhor/myway/ubuntu bionic main
           deb-src http://ppa.launchpad.net/dhor/myway/ubuntu bionic main
           Active apt sources in file: /etc/apt/sources.list.d/graphics-drivers-ppa-bionic.list
           deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic main
           deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic main
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://mirror.metrocast.net/linuxmint-packages tara main upstream import backport
           deb http://mirror.its.dal.ca/ubuntu bionic main restricted universe multiverse
           deb http://mirror.its.dal.ca/ubuntu bionic-updates main restricted universe multiverse
           deb http://mirror.its.dal.ca/ubuntu bionic-backports main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           deb http://archive.canonical.com/ubuntu/ bionic partner
           Active apt sources in file: /etc/apt/sources.list.d/protonvpn-stable.list
           deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
Info:      Processes: 269 Uptime: 10 min Memory: 1533.8/16028.4MB
           Init: systemd v: 237 runlevel: 5 Gcc sys: 7.5.0
           Client: Shell (bash 4.4.201 running in bash) inxi: 2.3.56
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 25a7:fa10  
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 04f9:0402 Brother Industries, Ltd 
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 005: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 003 Device 004: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 003 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 003 Device 002: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 009 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
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
NAME FSTYPE LABEL UUID MOUNTPOINT
loop0 squashfs   /snap/core18/2566
loop1 squashfs   /snap/snapd/16778
loop2 squashfs   /snap/snapd/17029
loop3 squashfs   /snap/bluetooth-autostart/10
sda    
sda1 ext4  77dd11c1-219f-45c1-9d19-c66dbeca4f06 /
sda2 ext4  e3946cdf-ae08-4f74-a5de-46acb556a644 /home
sda3 ntfs  19DCC2C263A54B11 
sr0    
sr1    
00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:3405] (rev 13)
	Subsystem: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:5332]
00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:02.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 2 [8086:3409] (rev 13)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 13)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 13)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:10.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 Physical and Link Layer Registers Port 0 [8086:3425] (rev 13)
00:10.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 Routing and Protocol Layer Registers Port 0 [8086:3426] (rev 13)
00:14.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 13)
	Kernel driver in use: i7core_edac
	Kernel modules: i7core_edac
00:14.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 13)
00:14.2 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 13)
00:14.3 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 13)
	Kernel driver in use: i5500_temp
	Kernel modules: i5500_temp
00:19.0 Ethernet controller [0200]: Intel Corporation 82567LF-2 Gigabit Network Connection [8086:10cd]
	Subsystem: Intel Corporation 82567LF-2 Gigabit Network Connection [8086:5332]
	Kernel driver in use: e1000e
	Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller [8086:5332]
	Kernel driver in use: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller [8086:5332]
	Kernel driver in use: uhci_hcd
00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller [8086:5332]
	Kernel driver in use: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller [8086:5332]
	Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:0042]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a40]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 2 [8086:3a42]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 [8086:3a48]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a34]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller [8086:5332]
	Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a35]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller [8086:5332]
	Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a36]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller [8086:5332]
	Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 [8086:3a3a]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller [8086:5332]
	Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 90)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:3a16]
	Subsystem: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:5332]
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller [8086:3a22]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller [8086:5332]
	Kernel driver in use: ahci
	Kernel modules: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 82801JI (ICH10 Family) SMBus Controller [8086:3a30]
	Subsystem: Intel Corporation 82801JI (ICH10 Family) SMBus Controller [8086:5332]
	Kernel modules: i2c_i801
01:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 03)
	Subsystem: Intel Corporation uPD720200 USB 3.0 Host Controller [8086:5332]
	Kernel driver in use: xhci_hcd
02:00.0 IDE interface [0101]: Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller [1b4b:9123] (rev 10)
	Subsystem: Intel Corporation 88SE9123 PCIe SATA 6.0 Gb/s controller [8086:5332]
	Kernel modules: pata_acpi
02:00.1 IDE interface [0101]: Marvell Technology Group Ltd. 88SE912x IDE Controller [1b4b:91a4] (rev 11)
	Subsystem: Intel Corporation 88SE912x IDE Controller [8086:5332]
	Kernel driver in use: pata_marvell
	Kernel modules: pata_marvell, pata_acpi
03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 660 OEM] [10de:1185] (rev a1)
	Subsystem: NVIDIA Corporation GK104 [GeForce GTX 760 OEM] [10de:106f]
	Kernel driver in use: nvidia
	Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
03:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio Controller [10de:0e0a] (rev a1)
	Subsystem: NVIDIA Corporation GK104 HDMI Audio Controller [10de:106f]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. Device [1b4b:9215] (rev 11)
	Subsystem: Marvell Technology Group Ltd. Device [1b4b:9215]
	Kernel driver in use: ahci
	Kernel modules: ahci
ff:00.0 Host bridge [0600]: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers [8086:2c70] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers [8086:8086]
ff:00.1 Host bridge [0600]: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder [8086:2d81] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series QuickPath Architecture System Address Decoder [8086:8086]
ff:02.0 Host bridge [0600]: Intel Corporation Xeon 5600 Series QPI Link 0 [8086:2d90] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series QPI Link 0 [8086:8086]
ff:02.1 Host bridge [0600]: Intel Corporation Xeon 5600 Series QPI Physical 0 [8086:2d91] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series QPI Physical 0 [8086:8086]
ff:02.2 Host bridge [0600]: Intel Corporation Xeon 5600 Series Mirror Port Link 0 [8086:2d92] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Mirror Port Link 0 [8086:8086]
ff:02.3 Host bridge [0600]: Intel Corporation Xeon 5600 Series Mirror Port Link 1 [8086:2d93] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Mirror Port Link 1 [8086:8086]
ff:02.4 Host bridge [0600]: Intel Corporation Xeon 5600 Series QPI Link 1 [8086:2d94] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series QPI Link 1 [8086:8086]
ff:02.5 Host bridge [0600]: Intel Corporation Xeon 5600 Series QPI Physical 1 [8086:2d95] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series QPI Physical 1 [8086:8086]
ff:03.0 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers [8086:2d98] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Registers [8086:8086]
ff:03.1 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder [8086:2d99] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Target Address Decoder [8086:8086]
ff:03.2 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers [8086:2d9a] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller RAS Registers [8086:8086]
ff:03.4 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers [8086:2d9c] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Test Registers [8086:8086]
ff:04.0 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control [8086:2da0] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Control [8086:8086]
ff:04.1 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address [8086:2da1] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Address [8086:8086]
ff:04.2 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank [8086:2da2] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Rank [8086:8086]
ff:04.3 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control [8086:2da3] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 0 Thermal Control [8086:8086]
ff:05.0 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control [8086:2da8] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Control [8086:8086]
ff:05.1 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address [8086:2da9] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Address [8086:8086]
ff:05.2 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank [8086:2daa] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Rank [8086:8086]
ff:05.3 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control [8086:2dab] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 1 Thermal Control [8086:8086]
ff:06.0 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control [8086:2db0] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Control [8086:8086]
ff:06.1 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address [8086:2db1] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Address [8086:8086]
ff:06.2 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank [8086:2db2] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Rank [8086:8086]
ff:06.3 Host bridge [0600]: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control [8086:2db3] (rev 02)
	Subsystem: Intel Corporation Xeon 5600 Series Integrated Memory Controller Channel 2 Thermal Control [8086:8086]
BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic root=UUID=77dd11c1-219f-45c1-9d19-c66dbeca4f06 ro quiet splash vt.handoff=1
nvidia, 410.104, 4.15.0-167-generic, x86_64: installed
nvidia, 410.104, 4.15.0-169-generic, x86_64: installed
nvidia, 410.104, 4.15.0-171-generic, x86_64: installed
nvidia, 410.104, 4.15.0-173-generic, x86_64: installed
nvidia, 410.104, 4.15.0-175-generic, x86_64: installed
nvidia, 410.104, 4.15.0-176-generic, x86_64: installed
nvidia, 410.104, 4.15.0-177-generic, x86_64: installed
nvidia, 410.104, 4.15.0-180-generic, x86_64: installed
nvidia, 410.104, 4.15.0-184-generic, x86_64: installed
nvidia, 410.104, 4.15.0-189-generic, x86_64: installed
nvidia, 410.104, 4.15.0-191-generic, x86_64: installed
nvidia, 410.104, 4.15.0-192-generic, x86_64: installed
nvidia, 410.104, 4.15.0-193-generic, x86_64: installed
nvidia, 410.104, 4.15.0-42-generic, x86_64: installed
btusb                  45056  0
btrtl                  16384  1 btusb
btbcm                  16384  1 btusb
btintel                16384  1 btusb
bluetooth             524288  45 btrtl,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           24576  2 bluetooth
btrfs                1159168  0
xor                    24576  1 btrfs
zstd_compress         163840  1 btrfs
raid6_pq              114688  1 btrfs
[    0.000000] Reserved but unavailable: 131 pages
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] e820: [mem 0xd0000000-0xdfffffff] available for PCI devices
[    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[    0.000000] Memory: 16342332K/16766664K available (12300K kernel code, 2484K rwdata, 4324K rodata, 2468K init, 2724K bss, 424332K reserved, 0K cma-reserved)
[    0.000000] DMAR-IR: This system BIOS has enabled interrupt remapping
               on a chipset that contains an erratum making that
               interrupt remapping is being disabled.  Please
[    0.030286] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.146143] core: CPUID marked event: 'bus cycles' unavailable
[    0.158491] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.184819] ACPI: Using IOAPIC for interrupt routing
[    0.220517] pci 0000:00:1e.0: PCI bridge to [bus 08] (subtractive decode)
[    0.220525] pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7 window] (subtractive decode)
[    0.220526] pci 0000:00:1e.0:   bridge window [io  0x0d00-0xffff window] (subtractive decode)
[    0.220527] pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
[    0.220528] pci 0000:00:1e.0:   bridge window [mem 0x000c4000-0x000cbfff window] (subtractive decode)
[    0.220529] pci 0000:00:1e.0:   bridge window [mem 0xfed40000-0xfedfffff window] (subtractive decode)
[    0.220529] pci 0000:00:1e.0:   bridge window [mem 0xd0000000-0xdfffffff window] (subtractive decode)
[    0.220648] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    0.220720] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    0.220790] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[    0.220861] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    0.220931] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[    0.221001] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    0.221072] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    0.221142] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    1.051957] pciehp 0000:00:1c.0:pcie004: Slot #5 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl- LLActRep+
[    1.051978] pciehp 0000:00:1c.1:pcie004: Slot #1 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl- LLActRep+
[    1.051995] pciehp 0000:00:1c.4:pcie004: Slot #2 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl- LLActRep+
[    1.114773] RAS: Correctable Errors collector initialized.
[    1.127372] EDD information not available.
[    2.174436] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    5.130327] Btrfs loaded, crc32c=crc32c-intel
[    9.349174] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   20.622947] EDAC MC0: Giving out device to module i7core_edac.c controller i7 core #0: DEV 0000:ff:03.0 (INTERRUPT)
[   21.681350] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[   21.790121] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  410.104  Tue Feb  5 22:58:30 CST 2019 (using threaded interrupts)
[   22.467606] Bluetooth: Core ver 2.22
[   22.467628] Bluetooth: HCI device and connection manager initialized
[   22.467631] Bluetooth: HCI socket layer initialized
[   22.467632] Bluetooth: L2CAP socket layer initialized
[   22.467635] Bluetooth: SCO socket layer initialized
[   23.246326] usbcore: registered new interface driver btusb
[   27.777819] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   27.777819] Bluetooth: BNEP filters: protocol multicast
[   27.777822] Bluetooth: BNEP socket layer initialized
[   39.117069] audit: type=1400 audit(1664498027.485:37): apparmor="DENIED" operation="create" profile="snap.bluetooth-autostart.autostart-bluetooth" pid=1426 comm="hciconfig" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
[   71.080229] Bluetooth: RFCOMM TTY layer initialized
[   71.080233] Bluetooth: RFCOMM socket layer initialized
[   71.080237] Bluetooth: RFCOMM ver 1.11
[  187.648655] input: Bluetooth Keyboard as /devices/virtual/misc/uhid/0005:1915:0040.0008/input/input16
[  187.649043] hid-generic 0005:1915:0040.0008: input,hidraw7: BLUETOOTH HID v0.01 Keyboard [Bluetooth Keyboard] on 00:1A:7D:DA:71:13
[/code]

I don't have a lot more hair left to tear out. One person said it worked well with Mint, and it does, but not from boot. If needed, I'll try to track down the steps I took getting it to work the first time.

Some of what I have tried:

Code: Select all

 systemctl restart bluetooth.service
 systemctl daemon-reload
 systemctl enable bluetooth.service
 sudo xed /etc/systemd/system/bluetooth.service
 nano /etc/bluetooth/main.conf (changes here did make a difference)
 snap install bluetooth-autostart 
 
Any assistance greatly appreciated!
Last edited by Arch_Enemy on Tue Oct 04, 2022 12:42 am, edited 2 times in total.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

BTW, I know I'm running kernel 4.15.

As I said, it did work from boot twice on this machine, and three times on an identical machine.

Also:

Code: Select all

hciconfig hci0 version
hci0:	Type: Primary  Bus: USB
	BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
	HCI Version: 4.0 (0x6)  Revision: 0x22bb
	LMP Version: 4.0 (0x6)  Subversion: 0x22bb
	Manufacturer: Cambridge Silicon Radio (10)
and from dmesg:

Code: Select all

[   39.117069] audit: type=1400 audit(1664498027.485:37): apparmor="DENIED" operation="create" profile="snap.bluetooth-autostart.autostart-bluetooth" pid=1426 comm="hciconfig" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
[   71.080229] Bluetooth: RFCOMM TTY layer initialized
[   71.080233] Bluetooth: RFCOMM socket layer initialized
[   71.080237] Bluetooth: RFCOMM ver 1.11
[  182.030541] NET: Registered protocol family 38
[  187.648655] input: Bluetooth Keyboard as /devices/virtual/misc/uhid/0005:1915:0040.0008/input/input16
[  187.649043] hid-generic 0005:1915:0040.0008: input,hidraw7: BLUETOOTH HID v0.01 Keyboard [Bluetooth Keyboard] on 00:1A:7D:DA:71:13
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Joe2Shoe
Level 5
Level 5
Posts: 776
Joined: Wed Oct 18, 2017 8:12 pm
Location: Ozone

Re: Getting Bluetooth to work at boot

Post by Joe2Shoe »

Go to Menu/Preferences/Startup Applications. Left-click on Blueman Applet, set the switch to ON (to the right), then click on the "pencil" icon (bottom of window), then under "Startup delay", set the timeout to 5 seconds, click Save, exit window. Reboot.
"Tolerance is the refuge of men without conviction."
"Common sense is not so common" - Voltaire
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

I use MATE and I don't have that option :(
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Joe2Shoe
Level 5
Level 5
Posts: 776
Joined: Wed Oct 18, 2017 8:12 pm
Location: Ozone

Re: Getting Bluetooth to work at boot

Post by Joe2Shoe »

That's strange, as I ran MATE for 5 years on 2 laptops, I'm sure the "Startup Applications" was there.
Go to Menu and type "Startup Applications" in the search box at the top.
"Tolerance is the refuge of men without conviction."
"Common sense is not so common" - Voltaire
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: Getting Bluetooth to work at boot

Post by hglee »

Arch_Enemy wrote:
Fri Sep 30, 2022 3:33 pm
I use MATE and I don't have that option :(

Seeing that you're at Level 6+: There's a system file that you can modify for Bluetooth configuration -- /etc/bluetooth/main.conf


First, make a date/time-stamped backup copy of that file (you can run this command multiple times, to make multiple backups):

Code: Select all

sudo cp -v /etc/bluetooth/main.conf{,--`date +%F--%Hh%Mm%Ss`} && echo && ls -al /etc/bluetooth/main.conf*
The backup file(s) look something like this: main.conf--2022-10-01--11h43m44s (that's YYYY-MM-DD).


To restore the original from a backup, in the following line change the date/time in the DT="2022-10-01--11h43m44s" parameter to match your backup:

Code: Select all

DT="2022-10-01--11h43m44s" && sudo cp -vf /etc/bluetooth/main.conf{"--$DT",}
Change only what's between the first double quotes. If you make a typo (mismatch) in the date/time then no change (restoration) will be made.


Now you can safely modify that file using the xed text editor, e.g. to set the AutoConnectTimeout parameter:

Code: Select all

sudo -iH xed /etc/bluetooth/main.conf
Any line that starts with # is ignored, so to activate #AutoConnectTimeout = 60 you first remove the #, then set the desired timeout value (seconds).

Save & reboot.

Last edited by hglee on Sun Oct 02, 2022 11:31 pm, edited 1 time in total.
Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

Hi.

Yeah, I had tried that as well I turned it on, then thinking that may cause the issue turned it off.

I turned it back on. I also have AutoEnable on as well, and that is what's supposed to start BT at boot.
We'll try again! ;)

I actually use a Samsung Galaxy S9 as my main "computer" for browsing the net, email, etc. It uses a lot less
electricity than the Monster I have. That's what started this little project in the first place. I want on KB for that,
the computer, and a tablet. I had one that was 2 BT and 1 2.4G connection, but in a short while it started dropping
strokes and doubling others.

Let's see what happens when I reboot the Beast!
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

I should mention I'm running Mint 19.3, MATE desktop, and yeah, I found the Startup Apps the first time.
There's no option to right click and change setting.

What I do get is a command-line like dialog box. I'll have to look up the man page for the BT command and modify it in the dialog box.

I've heard of people having issues in 20+ as well. I have another box running 20.1 I'll try it on.

I'm reluctant to mess with the Beast, because it's my work machine.

Thanks for suggestions, guys!
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

After a review of everything, all these suggestions take place after I login.

I need something that starts bluetooth before X starts. Need to have it at login.

I tried a couple things on my own, and that's when I realized everything happens after login.
I have to use another KB to sign in, and then BT starts.

Need it to start before X starts.

I'm smart enough, but, apparently, not THAT smart enough! :D
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

Help me, Obe Wan Kenobe.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Joe2Shoe
Level 5
Level 5
Posts: 776
Joined: Wed Oct 18, 2017 8:12 pm
Location: Ozone

Re: Getting Bluetooth to work at boot

Post by Joe2Shoe »

"I should mention I'm running Mint 19.3, MATE desktop, and yeah, I found the Startup Apps the first time.
There's no option to right click and change setting."

There is no right-click option to change settings.
In Startup Applications, left-click on Blueman Applet, set the switch to ON (top right), then click on the "pencil" icon (bottom of window), then under "Startup delay", set the timeout to 5 seconds, click Save, exit window. Reboot.
Good luck.
"Tolerance is the refuge of men without conviction."
"Common sense is not so common" - Voltaire
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

UGH! Something from a website got pasted in main.conf in /etc/bluetooth:

Code: Select all

bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2022-10-02 17:53:12 EDT; 6min ago
     Docs: man:bluetoothd(8)
 Main PID: 1175 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─1175 /usr/lib/bluetooth/bluetoothd

Oct 02 17:53:12 TimeWarp bluetoothd[1175]: Parsing /etc/bluetooth/main.conf failed: Key file contains line “Source: https://frameboxxindore.com/apple/you-asked-how-do-i-enable-bluetooth.com
Now to reboot and try again.

I've noticed 2 sites autoinsert their URLs in text documents.

Not Nice.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: Getting Bluetooth to work at boot

Post by hglee »

Joe2Shoe wrote:
Sun Oct 02, 2022 10:38 am
Arch_Enemy wrote:
Thu Sep 29, 2022 8:57 pm

Code: Select all

System:    Host: TimeWarp Kernel: 4.15.0-193-generic x86_64
           bits: 64 gcc: 7.5.0
           Desktop: MATE 1.20.1 (Gtk 3.22.30) info: mate-panel dm: lightdm
           Distro: Linux Mint 19 Tara

In Startup Applications, left-click on Blueman Applet, ...

Mint started using Blueman only with Vanessa. It isn't installed in either Tara (LM19) or Una (LM20).

Dropping Blueberry to adopt Blueman was headline news for LM21. "The biggest difference between Blueman and Blueberry is that the former uses BlueZ as a Bluetooth backend while the latter relies on the gnome-bluetooth backend."

Hence the onslaught of Bluetooth issues for LM21.


EDIT: For some reason, this forum censors a 9to5Linux dot com link as blog spam.

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

Uninstalled blueman and installed bluemon, bluetooth starts before X, KB available at login.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: [To Heck With It] Getting Bluetooth to work at boot

Post by Arch_Enemy »

After 5 reboots, on 2 different 19.3 installations, it stopped working again.

I'll just buy a 2.4G/BT keyboard that works with Mint.

I've had it. Spent the whole day on it.

I'm retired, but i still have better things to do.

I guess Bluetooth on Linux just isn't ready for Prime Time.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: Getting Bluetooth to work at boot

Post by hglee »

Arch_Enemy wrote:
Tue Oct 04, 2022 12:16 am
Uninstalled blueman and installed bluemon, bluetooth starts before X, KB available at login.

Blueman isn't installed with LM19 by default. Did you subsequently install Blueman because it replaces Blueberry in LM21?

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: Getting Bluetooth to work at boot

Post by Arch_Enemy »

hglee wrote:
Tue Oct 04, 2022 12:54 am
Arch_Enemy wrote:
Tue Oct 04, 2022 12:16 am
Uninstalled blueman and installed bluemon, bluetooth starts before X, KB available at login.

Blueman isn't installed with LM19 by default. Did you subsequently install Blueman because it replaces Blueberry in LM21?

Yes, i did. I uninstalled it on both installations.

it was working fine all day, both installations, then quit again.

I found a KB exactly like the one I have, with 2.4G instead of BT1. I've reached my rope's end dealing with this.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: [To Heck With It] Getting Bluetooth to work at boot

Post by Arch_Enemy »

Addendum:

Of the 2 installations, one is for work, one is for play. I don't care a lot of the play installation. I rolled an ISO on a USB key I can reinstall at any time.
That's the beauty of my signature. I've done it a couple times already. home is always there.
I could update that one to 20+, and if it blows out, Meh. No big deal.

But I don't like messing with the one for work. They both do just what I want them to.

I've already ordered the new KB, so I'm throwing in the towel. The fight is over. I can still send the one I have back.

If it were headphones, or powered speakers, I wouldn't care. I'd just reconnect. it's only a couple of clicks.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
User avatar
hglee
Level 6
Level 6
Posts: 1423
Joined: Fri Jun 22, 2018 4:31 pm

Re: [To Heck With It] Getting Bluetooth to work at boot

Post by hglee »

Arch_Enemy wrote:
Tue Oct 04, 2022 1:17 am
That's the beauty of my signature. I've done it a couple times already. home is always there.
Agreed, I've done it that way for years.

I also keep a partition (/xdata) that never gets reformatted. It has stuff I'd otherwise need to restore from backups, such as videos & music.


A richer BT front-end is Bluetuith, a Terminal app in mouse-friendly ASCII menus. It can also transfer files via BT, and control media playback.


It wouldn't run in my LM19 VM, but you've got LM20 somewhere. The most recent bluetuith is at github as source code and as a ready-to-run binary.


wget won't properly handle some github URLs, so install the multi-talented aria2 downloader, then fetch the bluetuith v0.1.3 tarball into ~/Downloads:

Code: Select all

sudo apt install -y aria2 bluez && cd ~/Downloads # Mint has BlueZ by default, but just to be sure
aria2c https://github.com/darkhz/bluetuith/releases/download/v0.1.3/bluetuith_0.1.3_Linux_x86_64.tar.gz
Download and run the SHA256SUM checksum file:

Code: Select all

aria2c https://github.com/darkhz/bluetuith/releases/download/v0.1.3/checksums.txt && sha256sum -c --ignore-missing checksums.txt
Extract the bluetuith executable binary, directly from the tarball into your /usr/local/bin subdirectory:

Code: Select all

sudo tar -xf bluetuith_*_Linux_x86_64.tar.gz -C /usr/local/bin/
View the bluetuith --help output:

Code: Select all

bluetuith --help

Now run the colourful & mouse-friendly bluetuith "TUI" (Terminal User Interface):

Code: Select all

bluetuith --set-theme-config='Adapter=red,Device=purple,MenuBar=blue'

Bluetuith can effectively replace bluetoothctl.

Bluetuith READ ME at Open Source Agenda.

Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
User avatar
Arch_Enemy
Level 7
Level 7
Posts: 1508
Joined: Tue Apr 26, 2016 3:28 pm

Re: [To Heck With It] Getting Bluetooth to work at boot

Post by Arch_Enemy »

I got it to work on all three disk installations, rolled a USB version, and got that to start too.
Multiple reboots.

Then it quit on all four.

I guess Linux just doesn't get along with bluetooth.

Wake me up when they get it figured out.

Seems I get 4-5 reboots, then it blows its brains out.

I've put far too much time into this. I'm not a quitter, and can usually get anything to work,
but I have met my Waterloo.
I have travelled 37629424162.9 miles in my lifetime

One thing I would suggest, create a partition as a 50G partition as /. Partition the rest as /Home. IF the system fails, reinstall and use the exact same username and all your 'stuff' comes back to you.
Post Reply

Return to “Hardware Support”