-
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
Tweaks for Toshiba Satellite L15W-B (Radius) #40
Comments
Thanks for sharing your experience. I have a different laptop (Yoga 13) with different config: Bus 003 Device 004: ID 0bda:1724 Realtek Semiconductor Corp. RTL8723AU 802.11n WLAN Adapter I read your post and thought I'd try that - instead of adding new entry 0bda:1724 to the blacklist, I moved the generic realtek line from blacklist to the btusb_table[] array { USB_VENDOR_AND_INTERFACE_INFO(0x0bda, 0xe0, 0x01, 0x01), .driver_info = BTUSB_REALTEK }, I've used lwfinger's modules for years, but after upgraded Ubuntu to 15.10 "new" branch no longer compile and I had to use the "kernel" branch and the above modification to make it work. There appear to be some differences between "kernel" and "new" branchs' btusb.c. If you device used to work by "new" branch, it doesn't hurt to cross-reference the old/new code. Good luck. |
BTW, once bluetooth is up, under 15.10 I was able to pair and use my Bluetooth 4.0 (low-energy profile) micosoft designer mouse right from standard UI. Cool.. And both wifi/bluetooth works fine simultaneously with lwfinger's drivers (there was a question about that in another thread) |
Hello! I'm having the same problem you did. Is there any way this can be passed upstream, to be included in future updates? Having to patch this file every time it's updated would be a real bummer. I'm thinking of just plugging a BT dongle into my Toshiba, as I don't have any experience with compiling things from source... |
The patch has been sent upstream, but I have heard nothing since. |
Hello! I finally found what I needed on the Ubuntu forums. Bless the soul who created a PPA to handle this issue as new kernels arrive! 73 DE N4RPS On December 15, 2015 10:30:53 AM EST, lwfinger notifications@github.com wrote: The patch has been sent upstream, but I have heard nothing since. — Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Sorry for commenting on an old issue. But I wonder if the line Any suggestions of what should I do? |
The USB vendor ID of 0x0930 belongs to Atheros, not Realtek. Are you sure that your BT device is made by Realtek? |
@lwfinger I did not do any replacement to the bluetooth/WiFi hardware since I bought it, and one of my |
I'm so glad your post from 2015 was still up. Your solution worked perfectly! On the other hand, doing my first kernel recompile was, let's just say "a learning experience". I hope you see this post and feel my wireless gratitude. |
I remember my first kernel build, but the kernel was a lot smaller. You are welcome. |
Compiling now. Is there any possibility for this change to be included in future linux kernels? |
Been fooling with these drivers trying to get them working on my (newish) laptop. bluetooth device always showed up as:
and poking it with lsusb showed the device as
prodding it for more info returned the following. Nowhere did it mention realtek chipset so I figured maybe it wasn't being recognized properly and maybe Toshiba had a custom version made for this line of laptops:
Anyway, after scratching my head I figured I'd just throw caution of the wind and poke at the btusb source. I changed the following starting at about line 309 (from the latest -kernel git branch)
Original:
New:
After recompiling and re-inserting the module, dmesg showed:
So I assume that means it's loading the firmware now. And bluetooth works. So yay!
Anyway, thought I'd share my success and hope someone else finds this useful.
The text was updated successfully, but these errors were encountered: