Bluetooth adapter not found [Solved]

[harmon]

Hi!
As I wrote in my first post, I had a similar problem in other Linux distris (I tried about 10) - in most of them I could solve this by using

Code: Select all

hid2hci --method=dell --vendor=413c --product=8156

SL: "command not found".
I suppose it must be possible to switch from HID to HCI mode (and back) - but how?
BTW: At the moment I do not make any changes, although I had no problem with the "old" kernel.

[Fitzcarraldo]

Courtesy of Google: Gentoo Bugzilla Bug Report No. 315749 - net-wireless/bluez-4.63 - Dell bluetooth doesn't get initialized.

[harmon]

Hi Fitzcarraldo!
Thank you very much, again.
I keep my promise: http://forum.sabayon.org/viewtopic.php?f=81&t=24845
To write that "Anleitung" (guidance) I first downloaded SL-Gnome and installed it on USB
(as usually with PartedMagic/ UNetbootin).
I was not surprised to see that BT is working fine (Gnome!). But as I don't like Gnome 3, I don't know what to do.
I suppose, each Linux with Gnome edition will come with Gnome 3 some day.
First I will vacation (a month or so).
harmon

[Fitzcarraldo]

In Comment 30 - Gentoo Bugzilla Bug Report No. 315749, Pacho Ramos states that you must have udev built with the extras USE flag. I don't have access to a machine with Entropy installed at the moment, so I am unable to check. Have you checked that the udev package in Entropy was built with that USE flag enabled?:

Code: Select all

# eix -I udev

Also, according to that Gentoo bug report (Status: RESOLVED FIXED), you need to have the following udev rule configured on your machine in /lib64/udev/rules.d/97-bluetooth-hid2hci.rules:

Code: Select all

ACTION=="add", ENV{ID_VENDOR}=="413c", ENV{ID_CLASS}=="mouse", ATTRS{bmAttributes}=="e0", KERNEL=="mouse*", RUN+="/usr/sbin/hid2hci --method dell -v $env{ID_VENDOR} -p $env{ID_MODEL} --mode hci"

And, until you next reboot, you need to do:

Code: Select all

hid2hci --method dell -v 413c -p 8158 --mode hci

(You quoted a product code of 8156 rather than 8158, so try that.)

Did you try all that?

[harmon]

Hi!
Terminal output:

Code: Select all

sabayon harmon # eix -I udev
[U] dev-python/pyudev
     Available versions:  (~)0.10 (~)0.11 {pygobject pyqt4 pyside test}
     Installed versions:  0.10(10:48:35 AM 06/27/2011)(pyqt4 -pygobject -pyside -test)
     Homepage:            http://packages.python.org/pyudev/ http://pypi.python.org/pypi/pyudev
     Description:         Python binding to libudev
[D] sys-fs/udev
     Available versions:  114 115-r1 119 124-r1 124-r2 141 (~)141-r1 146-r1!t 149 151-r4 164-r2 (~)167-r1[1] [m](~)168-r2[1] [m](~)171-r1 [m](~)171-r1[1] [m]**9999 {acl action_modeswitch build debug (+)devfs-compat edd (-)extras floppy gudev hwdb introspection keymap old-hd-rules +rule_generator selinux test}
     Installed versions:  171-r1[1](11:32:50 AM 07/04/2011)(acl extras gudev hwdb keymap rule_generator -action_modeswitch -debug -edd -floppy -introspection -selinux -test)
     Homepage:            http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
     Description:         Linux dynamic and persistent device naming support (aka userspace devfs)
[1] "sabayon" /var/lib/layman/sabayon
Found 2 matches.


I was searching in the net, but i didn't find a solution how to enable USE flag.

I created the file 97-bluetooth-hid2hci.rules, but after rebooting: same results.

[popsUlfr]

Hi!
I was searching in the net, but i didn't find a solution how to enable USE flag.

There are 2 ways to do that:
1) The quick way by adding USE="extras" in front of the emerge command:

Code: Select all

USE="extras" emerge -av udev


2) The persistent way so it remembers the flag by adding it to

Code: Select all

/etc/portage/package.use

like that

Code: Select all

sys-fs/udev extras

I see that portage wants to downgrade the udev version because the one used in entropy is masked in portage. So you may need to add

Code: Select all

=sys-fs/udev-171-r1

to

Code: Select all

/etc/portage/package.unmask

Now try to emerge that specific version with

Code: Select all

USE="extras" emerge -av =sys-fs/udev-171-r1

or just

Code: Select all

emerge -av =sys-fs/udev-171-r1

if you used the persistent method.

[harmon]

Hi!
Persistent mode -> no success.
I had to update config files and did (see man emerge, line 800+ )

Code: Select all

You can disable this feature by setting CONFIG_PROTECT="-*"  in  /etc/make.conf.

[Fitzcarraldo]

According to the output of eix that you posted, you already have the extras USE flag enabled for udev:

Installed versions: 171-r1[1](11:32:50 AM 07/04/2011)(acl extras gudev hwdb keymap rule_generator -action_modeswitch -debug -edd -floppy -introspection -selinux -test)

[harmon]

Hi!

Code: Select all

sabayon harmon # hcitool scan
Device is not available: No such device
sabayon harmon # hidd --search
bash: hidd: command not found
sabayon harmon # hid2hci --method dell -v 413c -p 8158 --mode hci
bash: hid2hci: command not found


Until next month!
harmon

[popsUlfr]

According to the output of eix that you posted, you already have the extras USE flag enabled for udev:

Installed versions: 171-r1[1](11:32:50 AM 07/04/2011)(acl extras gudev hwdb keymap rule_generator -action_modeswitch -debug -edd -floppy -introspection -selinux -test)

Whoops! Good catch I totally missed that.
Might also be a case of missing firmware. Did you try blueman to manage anything bluetooth?

Code: Select all

equo install blueman

I doubt this will improve the situation since this is an issue on driver level but you never know.