You are not logged in.
Hi, I'm havig trouble with making the integratod bluetooth work in my Dell Studio 15 (1555)
Bus 003 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
rfkill reports that the bluetooth device is not blocked:
# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
but hcitool finds no device at all:
# hcitool scan
Device is not available: No such device
# hcitool dev
Devices:
neither do hciconfig:
# hciconfig -a
The wiki mentions that I need to run hid2hci. This is outdated because hid2hci is not in the $PATH anymore and better yet, hid2hci tool itself has changed and now it requires the exact place of the bluetooth device in the sysfs added in the as --devpath parameter.
This is the point where I'm stuck, I have no idea where it should be.
It tried to find files in and directories in /sys/ containing broadcom, dell, bluetooth, 0a5c:4500 and 413c, but had no luck.
How can I can found out which device node belongs to which actual device in the sysfs?
I think maybe /lib/udev/rules.d/97-bluetooth-hid2hci.rules should automatically swtich the device to hci mode, but apperantly this not happens.
ps: the other Studio 15 topics were not ontopic or old and I did not want to necrobump.
Last edited by ijanos (2011-08-10 19:47:31)
Offline
I have same laptop as yours and bluetooth work very well with kde&bluedevil (up to date x86_64).
Did you have bluez installed and bluetooth daemon running?
Offline
I have same laptop as yours and bluetooth work very well with kde&bluedevil (up to date x86_64).
Did you have bluez installed and bluetooth daemon running?
Bluez is installed and bluetooth deamon is up and running. GUI frotends cannot find the device.
This is the dmesg output when I start the bluetooth service.
[ 671.630306] Bluetooth: Core ver 2.16
[ 671.630328] NET: Registered protocol family 31
[ 671.630330] Bluetooth: HCI device and connection manager initialized
[ 671.630332] Bluetooth: HCI socket layer initialized
[ 671.630333] Bluetooth: L2CAP socket layer initialized
[ 671.630381] Bluetooth: SCO socket layer initialized
[ 7478.493785] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
but still there is no sign of the device with hcitool dev
And no, the hardware is fine, it works when I boot windows.
Offline
What DE are you using?
Dbus daemon is runing? (not backgrounded).
If yes, try to uninstall/reinstall all bluetooth packages and then restart.
In the past bluetooth was working (did you make a recent update)?
Read carefully https://wiki.archlinux.org/index.php/Bluetooth, mabe you missed something.
Here my /etc/dbus-1/system.d/bluetooth.conf:
<!-- This configuration file specifies the required security policies
for Bluetooth core daemon to work. -->
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<!-- ../system.conf have denied everything, so we just punch some holes -->
<policy user="root">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent"/>
<allow send_interface="org.bluez.HandsfreeAgent"/>
<allow send_interface="org.bluez.MediaEndpoint"/>
<allow send_interface="org.bluez.Watcher"/>
</policy>
<policy at_console="true">
<allow send_destination="org.bluez"/>
</policy>
<!-- allow users of lp group (printing subsystem) to
communicate with bluetoothd -->
<policy group="lp">
<allow send_destination="org.bluez"/>
</policy>
<policy context="default">
<deny send_destination="org.bluez"/>
</policy>
</busconfig>
Last edited by mits (2011-08-10 11:00:00)
Offline
What DE are you using?
Dbus daemon is runing? (not backgrounded).
openbox, and dbus is running.
If yes, try to uninstall/reinstall all bluetooth packages and then restart.
In the past bluetooth was working (did you make a recent update)?
This is a few days old fresh install of arch x86_64, so I could have missed a package, but I've read the bluetooth wiki page a few times and I think everything should be ok.
Or this could be a bug in fresh installs and maybe you have something from and older package that make your bluetooth work. (I had an x86 arch in this machine and it worked, but I configured it ~1,5 years ago)
Anyways, thanks for the dbus config, I will play with that.
EDIT: I have the exact same bluetooth.conf so that shoul be ok.
Last edited by ijanos (2011-08-10 11:22:56)
Offline
Ok. I re-checked everything and still no luck. There are no errors in syslog or dmesg, and they both report the successful start of the bluetooth daemon, but still no device show up for hcitool dev.
The only thing in the wiki I was not able to try is to run the hid2hci tool, because I can not figure out the right value for the required devpath parameter.
Offline
I am wondering if my system not loads the right module. Could you send me list of your loaded kernel modules? (the output of the lsmod command)
Offline
My lsmod:
How you start your DE (startx, slim etc)?
Mabe is consolekit/polkit related.
Why didn't try to install kde to see it works.
rfcomm 34845 8
bnep 9213 2
ext4 369556 2
mbcache 5817 1 ext4
jbd2 71074 1 ext4
btusb 11577 2
bluetooth 138465 23 rfcomm,bnep,btusb
crc16 1297 2 ext4,bluetooth
usbhid 35256 0
hid 81635 1 usbhid
uvcvideo 64931 0
videodev 78006 1 uvcvideo
media 10437 2 uvcvideo,videodev
v4l2_compat_ioctl32 8292 1 videodev
wl 2527080 0
joydev 9895 0
lib80211_crypt_tkip 8506 0
snd_hda_codec_idt 55175 1
snd_hda_intel 22122 2
snd_hda_codec 77927 2 snd_hda_codec_idt,snd_hda_intel
cpufreq_ondemand 6132 2
dell_laptop 7947 0
snd_hwdep 6325 1 snd_hda_codec
tg3 131006 0
acpi_cpufreq 5877 1
snd_pcm 73856 2 snd_hda_intel,snd_hda_codec
uhci_hcd 23084 0
freq_table 2451 2 cpufreq_ondemand,acpi_cpufreq
rfkill 15402 3 bluetooth,dell_laptop
ehci_hcd 39511 0
intel_agp 10904 0
snd_timer 19416 1 snd_pcm
serio_raw 4294 0
snd 57786 10 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6146 1 snd
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
psmouse 55224 0
dell_wmi 1517 0
sdhci_pci 8530 0
sdhci 22194 1 sdhci_pci
iTCO_wdt 12717 0
mmc_core 73353 1 sdhci
iTCO_vendor_support 1929 1 iTCO_wdt
lib80211 4158 2 wl,lib80211_crypt_tkip
mperf 1275 1 acpi_cpufreq
usbcore 142544 6 btusb,usbhid,uvcvideo,uhci_hcd,ehci_hcd
intel_gtt 14423 1 intel_agp
dcdbas 5488 1 dell_laptop
sparse_keymap 3088 1 dell_wmi
i2c_i801 8187 0
evdev 9530 10
i2c_core 20133 2 videodev,i2c_i801
libphy 16665 1 tg3
r592 12011 0
crc_itu_t 1297 0
memstick 6846 1 r592
thermal 7863 0
wmi 8411 1 dell_wmi
processor 24256 3 acpi_cpufreq
video 11228 0
ac 3265 0
battery 10905 0
fglrx 2815966 69
button 4470 1 fglrx
jfs 173430 1
sg 25557 0
sr_mod 14951 0
cdrom 36329 1 sr_mod
sd_mod 28307 5
ahci 20865 4
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
scsi_mod 131482 4 sg,sr_mod,sd_mod,libata
Last edited by mits (2011-08-10 13:49:23)
Offline
Hah! Windows managed to shut down the adapter in a way that I could not enable it from linux. Rebooted the machine to windows, turned on the adapter, rebooted again and there it is.
Thanks for all the helpful replies!
Offline