You are not logged in.

#1 2014-06-04 13:05:31

agent0
Member
From: Russia
Registered: 2014-05-04
Posts: 74
Website

[REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

Hello.
I have a lenovo yoga 13 laptop with 8723 wireless card.
Wifi is working bacause of dkms-8723au-git package. As I know, in 3.15 kernel it will work out of the box and lwfinger will no longer maintain this source code.

Bluetooth is not working and there is no bluetooth driver in aur. It is required to install another package from here https://github.com/lwfinger/rtl8723au_bt.
I cannot build this package, because when I run make command it ends with error make[1]: *** /lib/modules/3.14.4-1-ARCH/build: No such file or directory. Also there was written about no dkms support in code. But I cannot fix it, because I am still noob in Archlinux. And for some reason it is written "Support kernel version 2.6.32~3.13.0" in readme.txt. I have already 3.14.4-1-ARCH kernel.

Could anyone help me to fix that and make aur package for other people to get  bluetooth work on lenovo yoga 13?

Offline

#2 2014-06-05 12:28:53

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,893

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

Install linux-headers from [core], then try again

Last edited by Lone_Wolf (2014-06-05 12:29:27)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2014-06-05 14:50:56

agent0
Member
From: Russia
Registered: 2014-05-04
Posts: 74
Website

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

I have already executed sudo pacman -Suy. And version of installed linux-headers is 3.14.5-1. When I cd to the source for bluetooth folder and execute make command, it stops with error. Here is output:

$ make
make -C /lib/modules/3.14.4-1-ARCH/build M=/home/ndr/8723au_bt/rtl8723au_bt modules
make[1]: *** /lib/modules/3.14.4-1-ARCH/build: No such file or directory.  Stop.
Makefile:15: recipe for target 'all' failed
make: *** [all] Error 2

What does it want? Maybe Linux headers 3.14.4 is needed instead of 3.14.5 ? I do not know what to do next and how to compile bluetooth driver.

Offline

#4 2014-06-05 15:03:15

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,893

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

run uname -r & pacman -Qi linux | grep Version

It those 2 don't match, you probably have forgotten to reboot after updating the kernel.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#5 2014-06-05 15:21:13

agent0
Member
From: Russia
Registered: 2014-05-04
Posts: 74
Website

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

I have rebooted and then executed

$ uname -r & pacman -Qi linux | grep Version
[1] 8209
3.14.5-1-ARCH
[1]+  Done                    uname -r

Now I execute make in source folder and it ends with success. You are right, perhaps I just needed to reboot.
Then I ran sudo make install

[ndr@yoga rtl8723au_bt]$ make
make -C /lib/modules/3.14.5-1-ARCH/build M=/home/ndr/8723au_bt/rtl8723au_bt modules
make[1]: вход в каталог «/usr/lib/modules/3.14.5-1-ARCH/build»
  CC [M]  /home/ndr/8723au_bt/rtl8723au_bt/rtk_btusb.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/ndr/8723au_bt/rtl8723au_bt/rtk_btusb.mod.o
  LD [M]  /home/ndr/8723au_bt/rtl8723au_bt/rtk_btusb.ko
make[1]: выход из каталога «/usr/lib/modules/3.14.5-1-ARCH/build»

[ndr@yoga rtl8723au_bt]$ sudo make install
[sudo] password for ndr: 
mkdir -p /lib/firmware/rtk_bt
cp -f rlt8723a_chip_b_cut_bt40_fw_asic_rom_patch-svn8511-0x0020342E-20121105-LINUX_USB.bin /lib/firmware/rtk_bt/rtk8723a.bin
cp -f rtk_btusb.ko /lib/modules/3.14.5-1-ARCH/kernel/drivers/bluetooth/rtk_btusb.ko
depmod -a /lib/modules/3.14.5-1-ARCH
echo "install rtk_btusb success!"
install rtk_btusb success!

Then I reboot again. But I get error window at startup with the following text:
Cannot accept network settings (russian: Не удалось применить сетевые настройки)
org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process org.blueman.Mechanism received signal 5

You will not be able to connect to bluetooth network via this computer (Вы можете не соединиться с сетью Bluetooth через этот компьютер)

Last edited by agent0 (2014-06-05 15:26:43)

Offline

#6 2014-06-06 13:16:49

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,893

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

It could be related to the bluez 5 used on archlinux.
I think it's worth a try to install bluez4 from AUR to see if it works with that.

If switching to bluez4 doesn't solve it, you should take it up with lwfinger.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#7 2014-06-07 09:13:52

agent0
Member
From: Russia
Registered: 2014-05-04
Posts: 74
Website

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

I think bluez5 is ok, because when I run bluetoothctl it can detect my cluetooth controller now. However, I cannot start working with it

[ndr@yoga ~]$ sudo bluetoothctl 
[sudo] password for ndr: 
[NEW] Controller 2C:D0:5A:DF:60:07 yoga [default]
[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
  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
  version                    Display version
  quit                       Quit program
[bluetooth]# version
Version 5.19
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Blocked
[bluetooth]# list
Controller 2C:D0:5A:DF:60:07 yoga [default]
[bluetooth]# devices 
[bluetooth]# show
Controller 2C:D0:5A:DF:60:07
	Name: yoga
	Alias: yoga
	Class: 0x000000
	Powered: no
	Discoverable: no
	Pairable: yes
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0513
	Discovering: no
[bluetooth]# select 2C:D0:5A:DF:60:07
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Blocked
[DEL ] Controller 2C:D0:5A:DF:60:07 yoga [default]
[NEW] Controller 2C:D0:5A:DF:60:07 yoga [default]
[bluetooth]#

Ok, it is not powered on. In troubleshooting section in wiki there are some instructions about such situation. I do all as described in wiki:

[ndr@yoga ~]$ hciconfig -a
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 2C:D0:5A:DF:60:07  ACL MTU: 820:8  SCO MTU: 255:16
	[b]DOWN[/b]
	RX bytes:558 acl:0 sco:0 events:28 errors:0
	TX bytes:355 acl:0 sco:0 commands:28 errors:0
	Features: 0xff 0xfb 0xff 0xfe 0xdb 0xff 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF PARK 
	Link mode: SLAVE ACCEPT 

[ndr@yoga ~]$ hciconfig -a hci0 up
Can't init device hci0: Operation not permitted (1)
[ndr@yoga ~]$ sudo hciconfig -a hci0 up
[sudo] password for ndr: 
Can't init device hci0: Operation not possible due to RF-kill (132)
[ndr@yoga ~]$ rfkill unblock all
bash: rfkill: command not found

Could you please tell me where to dig next. Why there is not rfkill command?

Offline

#8 2014-06-07 15:05:08

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,893

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

$ pkgfile rfkill
core/netctl
core/rfkill
extra/bash-completion
$

in this case you want to install the rfkill pacakge.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#9 2014-06-08 15:56:18

agent0
Member
From: Russia
Registered: 2014-05-04
Posts: 74
Website

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

Yes. You are right. I needed to install pkgfile and rfkill. Thanks for your help. I will learn how to work with bluetooth via terminal.

Lone_Wolf, do you have access to discussion of AUR packages? Maybe ianonavy (author of wifi aur pkg for rtl8723) will make aur bluetooth package?

Offline

#10 2014-06-09 02:04:09

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,893

Re: [REQUEST] rtl8723au_bt bluetooth driver for lenovo yoga 13

Yes, i am registered on aur general mailing list, but iaonavy may not be following that.

Most aur maintainers list their email in the PKGBUILD, and ianonavy did that.

Look at the first line of pkgbuild for dkms-8723au-git and try contacting him directly through mail.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB