You are not logged in.
Hi all,
I'm a newbie just getting used to running Arch and so far loving it. I have Alienware X51R2 which has broadcom onboard wifi & bluetooth
$ lspci -nnv
...
02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
Subsystem: Dell Device [1028:0017]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f7a00000 (64-bit, non-prefetchable) [size=32K]
Memory at f7800000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [68] Vendor Specific Information: Len=44 <?>
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 24-fd-00-ff-ff-00-00-01
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Capabilities: [1b0] Latency Tolerance Reporting
Capabilities: [220] #15
Kernel driver in use: wl
Kernel modules: bcma, wl
...
when I load btusb
$ modprobe btusb
bluetooth doesn't immediately work and lsusb only shows
$ lsusb
...
Bus 001 Device 002: ID 413c:8143 Dell Computer Corp.
...
I've been searching for information on support forums for a couple of days and came to suspect that "413c:8143 Dell Computer Corp." might actually be a bluetooth device. So I did:
$ echo '413c 8143' > /sys/bus/usb/drivers/btusb/new_id
$ hciconfig hci0 up
and voila now the bluetooth device gets loaded. My question is:
1. where should I put these commands so that it will be executed at a reasonable time when booting the system
2. more fundamentally, though, is there a device source code somewhere that I can patch so that "413c:8143" device will get recognized as a bluetooth device? I've googled the id and there are several patches being submitted to device driver. can this be the case that something has been lost in translation while doing merge or refactoring a device driver?
Thanks!
Offline