Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › Dell 370 Bluetooth and Arch
New Posts  All Forums:Forum Nav:

Dell 370 Bluetooth and Arch

post #1 of 8
Thread Starter 
Ok so when I was setting up my Arch install I didn't have a bluetooth card installed but I had one on order. It got here last last week and I installed it but it's not recognized. I've tried all the different bluez (4,5,Git) to no avail. In my reading on trying to get this card initiated I people say to install windows and the Windows driver and that will initiate the card. That really doesn't make sense because it should initiate via the bios but this is Dell.

Bus 005 Device 002: ID 8086:0182 Intel Corp. WiMAX Connection 2400m
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick
Bus 001 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I really, REALLY don't want a bare metal Widows install 1. because I don't want Windows installed. 2. Becase something will happed to wonderfully functional Linux install and I'm many hours away from my now out of date clone and have things that need done.

If installing Windows is the only way to do this then I'll get it done but advice on setting up syslinux would be great would be great keeping in mind that the partition that windows is on will be deleted as soon as the one driver is installed.

There has to be a better way to make this broadcom card work, I'm just not finding it.

Currently Bluez4 is installed

[chris@my****tydell ~]$ hcitool scan
Device is not available: No such device

I've enabled bluetooth service in systemd

[chris@my****tydell ~]$ hciconfig
[chris@my****tydell ~]$

I've read the Wiki and the forums and still need some help
 
DD Portable
(12 items)
 
 
CPUMotherboardGraphicsRAM
i5 5675C Gigabyte GA-Z97X Gaming 5 XFX RX 480 GTR 32GB Corsair Vengeance 1600 
Hard DriveHard DriveHard DriveCooling
Samsung 840 Evo Western Digital Black RE4 2TB Western Digital Green 2TB bequiet! Silent Wings 2 140mm PWM 
CoolingCoolingCoolingOS
bequiet! Silent Wings 2 140mm PWM bequiet! Shadow Wings SW1 120mm PWM bequiet! Dark Rock Pro 3 Arch X64 / Gnome and OSX 10.11 
MonitorKeyboardPowerCase
Dell U2414H KBC Poker II be quiet! Straight Power 10 400W bequiet! Silent Base 800 
MouseAudioAudio
Speedlink Omni VI  Sound Blaster Z  Bose Companion 2  
CPUMotherboardGraphicsRAM
i5 3427U The Googs HD4000 4GB DDR3 
Hard DriveOSMonitorKeyboard
32GB Flash / 128GB SanDisk Extreme SD card ChromeOS / Ubuntu 14.04 12" 2560x1700 bad 
PowerCaseMouseAudio
not much  Aluminium  Trackpad it makes noise I think  
  hide details  
Reply
 
DD Portable
(12 items)
 
 
CPUMotherboardGraphicsRAM
i5 5675C Gigabyte GA-Z97X Gaming 5 XFX RX 480 GTR 32GB Corsair Vengeance 1600 
Hard DriveHard DriveHard DriveCooling
Samsung 840 Evo Western Digital Black RE4 2TB Western Digital Green 2TB bequiet! Silent Wings 2 140mm PWM 
CoolingCoolingCoolingOS
bequiet! Silent Wings 2 140mm PWM bequiet! Shadow Wings SW1 120mm PWM bequiet! Dark Rock Pro 3 Arch X64 / Gnome and OSX 10.11 
MonitorKeyboardPowerCase
Dell U2414H KBC Poker II be quiet! Straight Power 10 400W bequiet! Silent Base 800 
MouseAudioAudio
Speedlink Omni VI  Sound Blaster Z  Bose Companion 2  
CPUMotherboardGraphicsRAM
i5 3427U The Googs HD4000 4GB DDR3 
Hard DriveOSMonitorKeyboard
32GB Flash / 128GB SanDisk Extreme SD card ChromeOS / Ubuntu 14.04 12" 2560x1700 bad 
PowerCaseMouseAudio
not much  Aluminium  Trackpad it makes noise I think  
  hide details  
Reply
post #2 of 8
I had the very same Problem with my Dell Studio 1557 running Arch.
The thing is, your BCM2046 bluetooth adapter is in HID mode when you boot linux. This means, it presents itself as a Mouse/Touchepad device.
To be able to use it you have to switch it to HCI mode. This is done by the hid2hci tool, part of 'bluez-utils'.
There is a udev rule for this which used to work flawlessly on my DELL for the last couple of years.
However, a couple of weeks ago the problem reappeared. The only way to make the bluetooth chip visible in linux is for me to boot Windows inside VirtualBox and connect the USB Touchpad to the VM and let windows switch it to HCI mode.
After that linux sees the bluetooth adapter...until the next reboot/resume.

I'm not sure which package is responsible for this regression...

If you're able to find a solution I'd be happy to hear it smile.gif

So long,

rev
post #3 of 8
Quote:
Originally Posted by revinary View Post

I had the very same Problem with my Dell Studio 1557 running Arch.
The thing is, your BCM2046 bluetooth adapter is in HID mode when you boot linux. This means, it presents itself as a Mouse/Touchepad device.
To be able to use it you have to switch it to HCI mode. This is done by the hid2hci tool, part of 'bluez-utils'.
There is a udev rule for this which used to work flawlessly on my DELL for the last couple of years.
However, a couple of weeks ago the problem reappeared. The only way to make the bluetooth chip visible in linux is for me to boot Windows inside VirtualBox and connect the USB Touchpad to the VM and let windows switch it to HCI mode.
After that linux sees the bluetooth adapter...until the next reboot/resume.

I'm not sure which package is responsible for this regression...
systemd? Since Arch doesn't support udev any longer
post #4 of 8
Udev's source tree has been merged into systemd.
Therefore, it is not packaged separately but that doesn't mean it's not supported anymore - udev is essential for running Arch.

That being said, it may very well be true that a change in udev/systemd caused the regression.
I'll see if I can downgrade systemd and post the results -

So long,

rev
post #5 of 8
I hadn't realised parts of udev still lives in systemd. I thought it was a complete replacement. Makes sense now you say it though.

Learn something new every day. smile.gif
post #6 of 8
Quote:
Originally Posted by revinary View Post

Udev's source tree has been merged into systemd.
Therefore, it is not packaged separately but that doesn't mean it's not supported anymore - udev is essential for running Arch.

That being said, it may very well be true that a change in udev/systemd caused the regression.
I'll see if I can downgrade systemd and post the results -

So long,

rev

Did you ever get time to do your testing?
post #7 of 8
Hi there,

I did some debugging and ran over this bug.
The proposed patch has already been merged upstream, but the fix hasn't reached arch yet.

Also note: I was debugging bluez5 which will probably be fixed by one of the next package upgrades.
I'm not sure if bluez4 will be patched, too, though.

The next step would be to build hid2hci from git and see if it fixes the issue.

Unfortunately I'm quite busy these days writing my Master's Thesis so I don't have too much time looking into it.

I'll let you know if I make any progress.

Thanks for your interest,

rev
post #8 of 8
OK, so I compiled hid2hci from the bluez git repo and it works.
For now, I simply made a copy of the relevant udev rule (/usr/lib/udev/rules.d/97-hid2hci.rules) and made it call
the git build of hid2hci.

Another problem, however, remains:

when resuming from standby the adapter is again in HID mode and the udev rule is not triggered -
the regression is discussed here.

As a workaround, I created a script in /lib/systemd/system-sleep/ which calls hid2hci on resume.

This is all quite annoying and in the end it boils down to this:

Devs are aware of the regression and the fix is on it's way downstream.

So either you wait until the problem fixes itself (in the next couple of weeks/months)
or you use the mentioned workarounds.

Note: since recently, hid2hci is packaged seperately and is based on bluez5 so you should be fine,
even if your bluetooth GUI of choice still uses bluez4

- rev
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › Dell 370 Bluetooth and Arch