You are not logged in.
Pages: 1
Hi,
I used Bluetooth in my laptop a couple of times before, but now the system doesn't show any device.
Someone have a clue to detect the device?
$ lsmod | grep btusb
btusb 53248 0
btrtl 16384 1 btusb
btbcm 16384 1 btusb
btintel 24576 1 btusb
bluetooth 638976 11 btrtl,btintel,btbcm,bnep,btusb
usbcore 294912 8 usbserial,xhci_hcd,ehci_pci,cp210x,uvcvideo,ehci_hcd,btusb,xhci_pci$ systemctl status bluetooth
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2018-07-14 18:20:23 -03; 2h 33min ago
Docs: man:bluetoothd(8)
Main PID: 1308 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
Memory: 2.1M
CGroup: /system.slice/bluetooth.service
└─1308 /usr/lib/bluetooth/bluetoothd
jul 14 18:20:23 gpc systemd[1]: Starting Bluetooth service...
jul 14 18:20:23 gpc bluetoothd[1308]: Bluetooth daemon 5.50
jul 14 18:20:23 gpc systemd[1]: Started Bluetooth service.
jul 14 18:20:23 gpc bluetoothd[1308]: Starting SDP server
jul 14 18:20:23 gpc bluetoothd[1308]: Bluetooth management interface 1.14 initialized# dmesg | grep -i 'blue'
[ 2.329817] Bluetooth: Core ver 2.22
[ 2.329845] Bluetooth: HCI device and connection manager initialized
[ 2.329849] Bluetooth: HCI socket layer initialized
[ 2.329853] Bluetooth: L2CAP socket layer initialized
[ 2.329863] Bluetooth: SCO socket layer initialized
[ 35.564933] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 35.564937] Bluetooth: BNEP filters: protocol multicast
[ 35.564941] Bluetooth: BNEP socket layer initialized# journalctl -b | grep -i 'blue'
jul 14 18:19:50 gpc kernel: Bluetooth: Core ver 2.22
jul 14 18:19:50 gpc kernel: Bluetooth: HCI device and connection manager initialized
jul 14 18:19:50 gpc kernel: Bluetooth: HCI socket layer initialized
jul 14 18:19:50 gpc kernel: Bluetooth: L2CAP socket layer initialized
jul 14 18:19:50 gpc kernel: Bluetooth: SCO socket layer initialized
jul 14 18:20:23 gpc dbus-daemon[351]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.35' (uid=1000 pid=1260 comm="/usr/bin/pulseaudio --daemonize=no ")
jul 14 18:20:23 gpc systemd[1]: Starting Bluetooth service...
jul 14 18:20:23 gpc bluetoothd[1308]: Bluetooth daemon 5.50
jul 14 18:20:23 gpc dbus-daemon[351]: [system] Successfully activated service 'org.bluez'
jul 14 18:20:23 gpc systemd[1]: Started Bluetooth service.
jul 14 18:20:23 gpc bluetoothd[1308]: Starting SDP server
jul 14 18:20:23 gpc dbus-daemon[351]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.36' (uid=0 pid=1308 comm="/usr/lib/bluetooth/bluetoothd ")
jul 14 18:20:23 gpc bluetoothd[1308]: Bluetooth management interface 1.14 initialized
jul 14 18:20:23 gpc kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
jul 14 18:20:23 gpc kernel: Bluetooth: BNEP filters: protocol multicast
jul 14 18:20:23 gpc kernel: Bluetooth: BNEP socket layer initialized# hciconfig list
Can't get device info: No such device$ lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 058f:3822 Alcor Micro Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub$ lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
03:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)$ rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: noThanks!
Last edited by Spiral (2018-07-15 00:21:03)
Offline
You may think this procedure sounds silly, but it's worth a try.
For the first method it helps if your BIOS is capable of enable/disable of network adapters. If your BIOS doesn't have this ability, then simply omit the steps relating to the BIOS in this method. Boot into the BIOS settings utility and disable all network adapters temporarily. Save the BIOS settings, and then power down completely. Remove the battery and power plug, and let the laptop sit without power briefly. Reboot again, go into BIOS settings again, now enable it your network adapters. Save the BIOS settings, then continue booting.
If the above method did not work, then you may want to try the next method.
Resetting the BIOS back to the factory default settings may help with adapter detection. This also sometimes helps to remove a hard block. Boot into the BIOS settings utility and reset the BIOS back to the factory default settings. Save the default settings, then power down the laptop. Remove the battery and power plug, and let the laptop sit without power briefly. Then, hold down the power button for approximately 30 seconds. Then restart the laptop, and see if it will boot with the factory default settings. If not, you may have to change some settings in the BIOS (such as secure boot) to get Linux to boot up. Hopefully, after a successful reboot your adapter has been detected.
Good luck.
Offline
You may think this procedure sounds silly, but it's worth a try.
For the first method it helps if your BIOS is capable of enable/disable of network adapters. If your BIOS doesn't have this ability, then simply omit the steps relating to the BIOS in this method. Boot into the BIOS settings utility and disable all network adapters temporarily. Save the BIOS settings, and then power down completely. Remove the battery and power plug, and let the laptop sit without power briefly. Reboot again, go into BIOS settings again, now enable it your network adapters. Save the BIOS settings, then continue booting.
If the above method did not work, then you may want to try the next method.
Resetting the BIOS back to the factory default settings may help with adapter detection. This also sometimes helps to remove a hard block. Boot into the BIOS settings utility and reset the BIOS back to the factory default settings. Save the default settings, then power down the laptop. Remove the battery and power plug, and let the laptop sit without power briefly. Then, hold down the power button for approximately 30 seconds. Then restart the laptop, and see if it will boot with the factory default settings. If not, you may have to change some settings in the BIOS (such as secure boot) to get Linux to boot up. Hopefully, after a successful reboot your adapter has been detected.
Good luck.
Thanks! I will try
Offline
Pages: 1