-
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
rtl8723au bt driver not working 4.4.0-36-generic #53
Comments
thanks for sharing . this is solved then.screens shot are txt mode than better as easier to copy paste and search. here is another rtl driver for https://github.com/vincent-t/rt8192cu_dkms device -http://plugable.com/drivers/usb-wifint/ |
@bajbijendra Thanks will try this out and let you know |
@bajbijendra My wifi driver works fine Bluetooth on the other hand doesn't these above drivers are for wifi only |
@lwfinger, sorry If I'm causing any trouble, I was on 4.4 generic kernel I moved to 4.5 stable and I get the error in systemctl status bluetooth :: After building the rtl8723au kernel branch Sep 15 01:25:23 afro-coder systemd[1]: Starting Bluetooth service... If I move back to bluez 5.23 Sep 15 01:29:23 afro-coder systemd[1]: Starting Bluetooth service... Still no connections nor can any device detect |
it works for me 4.4.0-131-generic |
generic details:
kernel-4.4.0-36-generic
Linux mint 18 sarah.
wifi driver rtl8723be
bluetooth driver: rtl8723au
Things attached: Dmesg log, journalctl log, systemctl log.
Things that get the bluetooth device started are modprobe -rv btusb, modprobe -v btusb.
Module installed from kernel branch rest all throw errors.
boot-Config:: http://pastebin.com/6xnXMByS
Problem: I have installed rtlwifi .
My phone scans the laptop after updating bluez to the latest version, unable to pair/connect and hcitool scan fails.
After modprobe commands the bluetooth is visible for a rough 30 secs.
I've read all the issues on your kernel thread alspo still couldn't find a way to keep this stable
could you guide me on how to fix this.
I know you're very busy but a little help would be sufficient for me.
dmesg log and journalctl log
.
.
.
.
.
.
.
systemctl log
lsusb and insmod
EDIT: after following this thread #39 I got the device up and running and stable but it doesn't find any devices but still this persists.
Edit1 : downgraded bluez to .23 Still can't find devices
The text was updated successfully, but these errors were encountered: