-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Driver don't seem to work on kernel 3.19.8-100.fc20.x86_64 #32
Comments
Reboot and run two commands: lsmod | grep btusb Post the output of the two commands. |
Hello, [root@admin-riker-deltanews-bg ~]# uptime The module doesn't seem to be loaded on boot. But even if I load it manually it would still not work. Thanks. |
When a module is not loaded on boot, that means the device is not in its tables. Forcing a load won't help either. That said, I do not understand your problem. The USB ID 0bda:1724 is in the version of the driver in the kernel branch. Are you sure you are using that branch? The command 'git branch' will tell you that. |
What I did was Then download zip file. I suppose this means it's a kernel branch? Thanks |
@mehanzhi yes, it is kernel branch archive. |
Thanks zhukovra, lwfinger, would you like ssh access, logs, or something else in order to debug? Thanks. |
As said earlier, you have the kernel branch, and it should work. Send ssh access info to [email protected]. |
I have a similar issue. Is there is progress on this, I'd appreciate an update on this thread. |
Hello, |
I finally got a chance to work on this, and pushed a trial fix onto the GitHub site. Unfortunately, I was unable to log into the test box. Until we fix my connection problem, please try this code. |
So, I see progress. Now, it seems that the bluetooth is being detected, and hci0 shows up in hciconfig. However, `hciconfig hci0 up' outputs "Can't init device hci0: Invalid argument (22)". Also, dmesg shows an error: "Bluetooth: RTL8723A: unexpected EPATCH signature!" |
That is progress. I just pushed new BT firmware for the rtl8723au. Please pull, do a 'sudo make install' and try again. |
Cheers @lwfinger, it works again. Thanks for everything! |
Hello, I was at work and I had to take my laptop with me, however it's now available for testing if you like. I'll try the code too and see if it will work for me. |
Hmm, the module is loaded, but still can't find my phone when searching for devices I can't see any available devices :( |
I logged in, and updated the driver and firmware to the latest versions. I do not know if the correct firmware is loaded or not. The system will need to be rebooted. Unfortunately, the following messages are back: atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Those messages overrun all the useful stuff. |
@mehanzhi that issue is an annoyance with the yoga 13. Basically, it's due to the one of the screen modes notifications not being understood by the kernel. The way I "fix" it is to go into windows and click the "lock mode" button (the small one on the front right side) and log back into linux and see if it leaves. |
If you run 'sudo crontab -e' and add a line with "@Onboot /usr/bin/setkeycodes e03e", that should fix it. |
Sorry, that crontab change will not help. |
Hello, I fix it with the script #!/bin/sh sudo setkeycodes e00d 255 But I have throubles make the /etc/rc.local run so the script can be started on boot and I have to run it manually every time. This time I forgot to run it, sorry about that :( And about the solution with windows, I don't have windows on my box. And the little button for screen rotation is nothing else than keys Supr+O and it sets a setting on/off in the gconf so you can use it to enable/disable screen rotation, I have a custom script for this too :) |
Rebooted, driver is loaded and bluetooth device is available but still I can't find any bluetooth devices. |
Using "sudo crontab -e", add a line that says "@Onboot " You should remove the "sudo" from the commands, and use the full path of /usr/bin/setketcodes. Also make sure that the script is executable. I am unable to connect to the box. |
Hello, Issue with the bluetooth seems to be solved for me too. Thanks for the help. |
Hello, I have updated on opensuse tumbleweed to Kernel 4.1.1, I understood that should have the bluetooth driver on it, but it seems that is not there. I have installed rtl8723au_bt-kernel. Now, it seems that the bluetooth is being detected, and hci0 shows up in hciconfig. However, `hciconfig hci0 up' outputs "Can't init device hci0: Invalid argument (22)". Also, dmesg shows an error: "Bluetooth: RTL8723A: unexpected EPATCH signature!" Any sugestion? |
The new driver will be in kernel 4.2. It is not in 4.1. There is new firmware that was pushed yesterday. Did you pull again? |
I have download and install again just in case, still not working here some information: linux-g7rn:/home/jordi # rfkill list linux-g7rn:/home/jordi # lsusb linux-g7rn:/home/jordi # lsmod | grep btusb linux-g7rn:/home/jordi # hciconfig hci0 up linux-g7rn:/home/jordi # hciconfig list Thankyou for your help |
Just I mix up |
I just update to Kernel 4.1.2 and still the same problems |
root@tobor:~/rtl8723au_bt-kernel# hciconfig root@tobor:~/rtl8723au_bt-kernel# hcitool scan [ Never finds a device !! ] root@tobor:~/rtl8723au_bt-kernel# bluetoothctl root@tobor:~/rtl8723au_bt-kernel# uname -a With a Debian Jessie 3.16.0-4-amd64 it works perfectly. |
Hello,
I'll just give you output, it's not that long and it has all I did.
[root@localhost rtl8723au_bt-kernel]# make
make -C /lib/modules/3.19.8-100.fc20.x86_64/build M=/home/k_georgiev/work/rtl8723au_bt-kernel modules
make[1]: Entering directory
/usr/src/kernels/3.19.8-100.fc20.x86_64' Building modules, stage 2. MODPOST 1 modules make[1]: Leaving directory
/usr/src/kernels/3.19.8-100.fc20.x86_64'[root@localhost rtl8723au_bt-kernel]# make install
depmod -a /lib/modules/3.19.8-100.fc20.x86_64
installed revised btusb
[root@localhost rtl8723au_bt-kernel]# modprobe -rv btusb
rmmod btusb
[root@localhost rtl8723au_bt-kernel]# modprobe -v btusb
insmod /lib/modules/3.19.8-100.fc20.x86_64/kernel/drivers/bluetooth/btusb.ko
[root@localhost rtl8723au_bt-kernel]# lsmod |grep -i btusb.
btusb 45899 0
[root@localhost rtl8723au_bt-kernel]# rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
[root@localhost rtl8723au_bt-kernel]#
And on the user interface on gnome I see no bluetooth functioning.
I saw issue 'bluetooth not working while wifi is on' so I stopped the wifi but got same result.
Thanks
The text was updated successfully, but these errors were encountered: