[SOLVED] Bluetooth (Dell Wireless 365) on Dell E4300
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
ERROR: Vendor ID, Product ID, and Switching Method must all be defined.
-h, --help Display help
-q, --quiet Don't display any messages
-r, --mode= Mode to switch to [hid, hci]
-v, --vendor= Vendor ID to act upon
-p, --product= Product ID to act upon
-m, --method= Method to use to switch [csr, logitech, dell]
You must have bluez-utils and bluez-libs tou also must have bluez-hcidump and bluez-firmaware installed. Make sure all of those packages are installed.
Then you have to add a code snippet to get passkey agent working. Without this you will not be able to do anything. You need to go to your etc>dbus-1>system.d and edit the bluetooth.conf file. Here is the code you must place in there.
<!-- 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"
<!-- ../system.conf have denied everything, so we just punch some holes -->
I greatly appreciate your help but seem I had a strange problem with this BT 365 device of Dell.
Today, I partition my harddisk to dual boot with Windows 7. Then, I install BT driver from Dell official site. After installing and configuring, I turn on BT adapter using function of the software, and the BT LED is suddenly on.
Now, I log on to Slackware, the BT light is still on, I try lsusb and find it out
Bus 003 Device 005: ID 413c:8160 Dell Computer Corp.
Yes that is exactly what happens. I guess I did not read this thread well enough. My HP wireless is the same way until the driver started to support turning it off and on. That most likely is the problem they have not built a driver as of yet to turn your bluetooth on and off.