Before switching to udev, I could use the built-in bluetooth dongle (connected via usb) in my dell inspiron 8600 without problems (like this: http://forums.gentoo.org/viewtopic.php?t=205860). After switching to udev, the "bluetooth enabled"-LED blinks on every 5 seconds for about half a second. When I try to access it, it says it isn't there... root@notebook / # hcitool -i hci0 Invalid device: No such device root@notebook / # hciconfig hci0 Can't get device info: No such device root@notebook / # I have no clue, perhaps I did something wrong, but some dev in #gentoo on freenode told me to write a bug here ;-)
*** Bug 64363 has been marked as a duplicate of this bug. ***
udev doesn't "switch" anything. Perhaps it's not creating your device nodes properly. What /dev nodes does the hcitool and hciconfig tools need to operate on?
need info
I don't know which device hciconfig tries to access, it's hci0 (just like eth0). From stracing hciconfig it looks like its accessing a socket... socket(PF_BLUETOOTH, SOCK_RAW, 1)
Again, I don't think this is a udev issue. If you are opening a socket, that doesn't touch udev at all. Did you try asking the bluez authors?
It is indeed not a udev problem, but a conflict with a different kernelmodule. Sorry. udev is a great piece of software.
changing from NEEDINFO to INVALID
indeed not a udev problem
