Asus X540L bluetooth

New to Debian (Or Linux in general)? Ask your questions here!

Asus X540L bluetooth

Postby sjsj » 2019-01-27 17:07

Hello,

Sorry, I speak a little English.

My new notebook: Asus X540L

Installed: debian-9.7.0-amd64-netinst.iso

Edit the /etc/apt/sources.list and add contrib and non-free

Code: Select all
apt-get update
apt-get upgrade
apt-get install firmware-realtek


My head/earphone is connected when I try repeatedly, but few seconds or minutes disconnected. Please help me.

Code: Select all
dmesg | grep -i blue
[    1.488237] usb 1-4: Product: Bluetooth Radio
[    8.692946] Bluetooth: Core ver 2.22
[    8.692962] Bluetooth: HCI device and connection manager initialized
[    8.692965] Bluetooth: HCI socket layer initialized
[    8.692967] Bluetooth: L2CAP socket layer initialized
[    8.692975] Bluetooth: SCO socket layer initialized
[    9.523921] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
[    9.523923] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_config.bin
[    9.690909] bluetooth hci0: firmware: failed to load rtl_bt/rtl8723b_config.bin (-2)
[    9.690914] bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2
[    9.690919] Bluetooth: hci0: Failed to load rtl_bt/rtl8723b_config.bin
[    9.690922] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
[    9.716512] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8723b_fw.bin
[    9.717390] Bluetooth: hci0: rom_version status=0 version=1
[    9.717397] Bluetooth: cfg_sz 0, total size 22496
[   14.853487] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.853488] Bluetooth: BNEP filters: protocol multicast
[   14.853492] Bluetooth: BNEP socket layer initialized
[   27.304145] Bluetooth: RFCOMM TTY layer initialized
[   27.304151] Bluetooth: RFCOMM socket layer initialized
[   27.304158] Bluetooth: RFCOMM ver 1.11


Please help me. Thanks!
User avatar
sjsj
 
Posts: 82
Joined: 2016-10-22 16:26

Re: Asus X540L bluetooth

Postby pylkko » 2019-01-27 17:27

Maybe you are missing the correct firmware package as your dmesg is saying "failed to load firmware". Do you know what device you have? Can you see it in lspci for example? Did you check the firmware folder if the config file is there or anywhere else?

The firmware package you mention does seems to say it supports the card seen by the kernel.

This is probably new hardware? Perhaps you need a newer version of the package.
User avatar
pylkko
 
Posts: 1392
Joined: 2014-11-06 19:02

Re: Asus X540L bluetooth

Postby sjsj » 2019-01-27 18:43

pylkko wrote:Can you see it in lspci for example?


Code: Select all
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:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (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: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)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5286 PCI Express Card Reader (rev 01)
02:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 06)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter


pylkko wrote:Did you check the firmware folder if the config file is there or anywhere else?


How to?
User avatar
sjsj
 
Posts: 82
Joined: 2016-10-22 16:26

Re: Asus X540L bluetooth

Postby Head_on_a_Stick » 2019-01-27 19:04

https://github.com/lwfinger/rtlwifi_new claims that the new driver is included in kernel v4.17+ so perhaps try the version from stretch-backports?

viewtopic.php?f=16&t=139003

For the firmware, the sid version was just updated and should be "safe" to install (as a .deb) in a stable system.

http://deb.debian.org/debian/pool/non-f ... -1_all.deb

EDIT: just read the OP again, an intermittent failure would suggest a hardware problem.

Or perhaps powersaving:
Code: Select all
/sbin/iwconfig wlp3s0

Check the "Power Management" line.

I've predicted the interface name from the bus address but it may be wrong, use `ip link` to list the interfaces.
"The trouble with the world is that the stupid are cocksure and the intelligent full of doubt." — Bertrand Russell
User avatar
Head_on_a_Stick
 
Posts: 8842
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Asus X540L bluetooth

Postby sjsj » 2019-01-27 19:50

Head_on_a_Stick wrote:http://deb.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-realtek_20190114-1_all.deb


Code: Select all
dpkg -i firmware-realtek_20190114-1_all.deb


The problem is not solved.

Head_on_a_Stick wrote:Check the "Power Management" line.


Code: Select all
Power Management:off
User avatar
sjsj
 
Posts: 82
Joined: 2016-10-22 16:26

Re: Asus X540L bluetooth

Postby Head_on_a_Stick » 2019-01-27 19:51

sjsj wrote:The problem is not solved

Have you tried a newer kernel as well?

Remember: drivers != firmware :wink:
"The trouble with the world is that the stupid are cocksure and the intelligent full of doubt." — Bertrand Russell
User avatar
Head_on_a_Stick
 
Posts: 8842
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Asus X540L bluetooth

Postby sjsj » 2019-01-28 19:09

Head_on_a_Stick wrote:Have you tried a newer kernel?


Is it not dangerous? I need a stable system.
User avatar
sjsj
 
Posts: 82
Joined: 2016-10-22 16:26

Re: Asus X540L bluetooth

Postby pylkko » 2019-01-28 19:53

sjsj wrote:
Head_on_a_Stick wrote:Have you tried a newer kernel?


Is it not dangerous? I need a stable system.


if you use the backported one, it is relatively safe, since the backporting team attempts to make newer packages that are compatible with the old packages on Debian 9. Your alternative is to wait for Debian 10 to come out (in a few months). You can also have both the old kernel from Debian 9 and the the backported one installed at the same time (in Debian 9). Then you can select which one to use from grub on boot (if you test it and see that it works but are not willing to go fully with the new kernel).
User avatar
pylkko
 
Posts: 1392
Joined: 2014-11-06 19:02

Re: Asus X540L bluetooth

Postby sjsj » 2019-02-01 11:55

I want to solve the problem without upgrading the kernel. Is it possible?

Code: Select all
ls /etc/bluetooth
input.conf  main.conf  network.conf  proximity.conf


Connected and disconnected:

Code: Select all
bluetoothctl
[NEW] Controller 30:D1:6B:4B:5C:95 sos [default]
[NEW] Device DB:F4:69:58:DB:CE DJ1200BT
[bluetooth]# help
Available commands:
  list                       List available controllers
  show [ctrl]                Controller information
  select <ctrl>              Select default controller
  devices                    List available devices
  paired-devices             List paired devices
  power <on/off>             Set controller power
  pairable <on/off>          Set controller pairable mode
  discoverable <on/off>      Set controller discoverable mode
  agent <on/off/capability>  Enable/disable agent with given capability
  default-agent              Set agent as the default one
  advertise <on/off/type>    Enable/disable advertising with given type
  set-advertise-uuids [uuid1 uuid2 ...] Set advertise uuids
  set-advertise-service [uuid][data=[xx xx ...] Set advertise service data
  set-advertise-manufacturer [id][data=[xx xx ...] Set advertise manufacturer data
  set-advertise-tx-power <on/off> Enable/disable TX power to be advertised
  set-scan-filter-uuids [uuid1 uuid2 ...] Set scan filter uuids
  set-scan-filter-rssi [rssi] Set scan filter rssi, and clears pathloss
  set-scan-filter-pathloss [pathloss] Set scan filter pathloss, and clears rssi
  set-scan-filter-transport [transport] Set scan filter transport
  set-scan-filter-clear      Clears discovery filter.
  scan <on/off>              Scan for devices
  info [dev]                 Device information
  pair [dev]                 Pair with device
  trust [dev]                Trust device
  untrust [dev]              Untrust device
  block [dev]                Block device
  unblock [dev]              Unblock device
  remove <dev>               Remove device
  connect <dev>              Connect device
  disconnect [dev]           Disconnect device
  list-attributes [dev]      List attributes
  set-alias <alias>          Set device alias
  select-attribute <attribute> Select attribute
  attribute-info [attribute] Select attribute
  read                       Read attribute value
  write <data=[xx xx ...]>   Write attribute value
  notify <on/off>            Notify attribute value
  register-profile <UUID ...> Register profile to connect
  unregister-profile         Unregister profile
  version                    Display version
  quit                       Quit program
[bluetooth]# exit
[DEL] Controller 30:D1:6B:4B:5C:95 sos [default]


Code: Select all
bluetoothctl
[NEW] Controller 30:D1:6B:4B:5C:95 sos [default]
[NEW] Device DB:F4:69:58:DB:CE DJ1200BT
[bluetooth]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
[CHG] Device DB:F4:69:58:DB:CE Connected: yes
[CHG] Device DB:F4:69:58:DB:CE UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device DB:F4:69:58:DB:CE UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device DB:F4:69:58:DB:CE UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device DB:F4:69:58:DB:CE UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device DB:F4:69:58:DB:CE ServicesResolved: yes
[CHG] Device DB:F4:69:58:DB:CE Paired: yes
Connection successful
[CHG] Device DB:F4:69:58:DB:CE ServicesResolved: no
[CHG] Device DB:F4:69:58:DB:CE Connected: no
[CHG] Device DB:F4:69:58:DB:CE Connected: yes
[DJ1200BT]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
[CHG] Device DB:F4:69:58:DB:CE Connected: no
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
[CHG] Device DB:F4:69:58:DB:CE Connected: yes
[CHG] Device DB:F4:69:58:DB:CE ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device DB:F4:69:58:DB:CE ServicesResolved: no
[CHG] Device DB:F4:69:58:DB:CE Connected: no
[bluetooth]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
[CHG] Device DB:F4:69:58:DB:CE Connected: yes
Connection successful
[CHG] Device DB:F4:69:58:DB:CE Connected: no
[bluetooth]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect DB:F4:69:58:DB:CE
Attempting to connect to DB:F4:69:58:DB:CE
Failed to connect: org.bluez.Error.Failed
[bluetooth]#


Why disconnected?

Code: Select all
/etc/init.d/bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-02-01 08:06:18 CET; 5h 35min ago
     Docs: man:bluetoothd(8)
 Main PID: 521 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─521 /usr/lib/bluetooth/bluetoothd

febr 01 08:06:18 sos bluetoothd[521]: Starting SDP server
febr 01 08:06:19 sos bluetoothd[521]: Bluetooth management interface 1.14 i…ized
febr 01 08:06:19 sos bluetoothd[521]: Failed to obtain handles for "Service…stic
febr 01 08:06:19 sos bluetoothd[521]: Sap driver initialization failed.
febr 01 08:06:19 sos bluetoothd[521]: sap-server: Operation not permitted (1)
febr 01 08:06:34 sos bluetoothd[521]: Endpoint registered: sender=:1.44 pat…urce
febr 01 08:06:34 sos bluetoothd[521]: Endpoint registered: sender=:1.44 pat…Sink
febr 01 08:06:59 sos bluetoothd[521]: Endpoint registered: sender=:1.66 pat…urce
febr 01 08:06:59 sos bluetoothd[521]: Endpoint registered: sender=:1.66 pat…Sink
febr 01 08:06:59 sos bluetoothd[521]: RFCOMM server failed for Headset Voic…(98)
Hint: Some lines were ellipsized, use -l to show in full.


Code: Select all
/etc/init.d/bluetooth start
[ ok ] Starting bluetooth (via systemctl): bluetooth.service.


Code: Select all
systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-02-01 08:06:18 CET; 5h 38min ago
     Docs: man:bluetoothd(8)
 Main PID: 521 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─521 /usr/lib/bluetooth/bluetoothd

febr 01 08:06:18 sos bluetoothd[521]: Starting SDP server
febr 01 08:06:19 sos bluetoothd[521]: Bluetooth management interface 1.14 initialized
febr 01 08:06:19 sos bluetoothd[521]: Failed to obtain handles for "Service Changed" characteristic
febr 01 08:06:19 sos bluetoothd[521]: Sap driver initialization failed.
febr 01 08:06:19 sos bluetoothd[521]: sap-server: Operation not permitted (1)
febr 01 08:06:34 sos bluetoothd[521]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2DPSource
febr 01 08:06:34 sos bluetoothd[521]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2DPSink
febr 01 08:06:59 sos bluetoothd[521]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSource
febr 01 08:06:59 sos bluetoothd[521]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSink
febr 01 08:06:59 sos bluetoothd[521]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use


Code: Select all
apt-get install blueman


Code: Select all
hcitool dev
Devices:
   hci0   30:D1:6B:4B:5C:95


Code: Select all
hcitool scan
Scanning ...


Code: Select all
rfcomm connect hci0 DB:F4:69:58:DB:CE
Can't connect RFCOMM socket: Host is down


Source: wiki.debian.org
User avatar
sjsj
 
Posts: 82
Joined: 2016-10-22 16:26

Re: Asus X540L bluetooth

Postby sjsj » 2019-02-02 08:43



Code: Select all
apt edit-sources
deb http://deb.debian.org/debian stretch-backports main contrib non-free
apt-get update
apt-get install -t stretch-backports linux-image-amd64


Restart.

Code: Select all
uname -a
Linux sos 4.19.0-0.bpo.1-amd64 #1 SMP Debian 4.19.12-1~bpo9+1 (2018-12-30) x86_64 GNU/Linux


Is it a new kernel? How to continue or not continue? The bluetooth is works. Thanks.
User avatar
sjsj
 
Posts: 82
Joined: 2016-10-22 16:26

Re: Asus X540L bluetooth

Postby pylkko » 2019-02-02 09:11

Yes. The kernel in Debian 9 is 4.9, so if you have 4.19 then it is a 'new kernel'. And notice also the "bpo" in your output which stands for backport.
User avatar
pylkko
 
Posts: 1392
Joined: 2014-11-06 19:02


Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 6 guests

fashionable