Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You may want to try adding the device address in the /etc/bluetooth/rfcomm.conf file, and setting bind to yes. This does work on my workstation. However, on my dell laptop, I also need to toggle FN+F2, and then restart bluetooth service for it to work.
in /etc/init.d/bluetooth or /etc/init.d/hidd, where
When the hidd server is started succesfully, you should only need
to move your mouse, wait a few seconds, and then it should work.
Also, if you have not used it for some time, you need to reconnect
by moving and waiting.
If you have bluetooth in your PC, you don't need to connect the
cradle USB stuff at all---but simply use it for recharging the
I actually can't get my bluetooth mouse to work at all with my laptop running FC4. I did the following:
[root@Whistler ~]# hcitool scan
[root@Whistler ~]# hidd server
[root@Whistler ~]# hidd connect 00:50:F2:E2:A5:A2
I tap my button at the bottom
I was still not able to get my mouse working. I also tried doing this in the bluetooth manager and it discovers my mouse but I can't double click no it or right click on it or get to the poperties of it to try and connect it.
My messages log states the following when trying this:
Jul 22 13:53:41 Whistler pam_timestamp_check: pam_timestamp: `/' owner UID != 0
Jul 22 13:54:16 Whistler last message repeated 7 times
Jul 22 13:54:21 Whistler pam_timestamp_check: pam_timestamp: `/' owner UID != 0
Jul 22 13:54:23 Whistler kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Jul 22 13:54:26 Whistler pam_timestamp_check: pam_timestamp: `/' owner UID != 0
Jul 22 13:55:01 Whistler last message repeated 7 times
bluetooth 56133 8 hidp,rfcomm,l2cap,hci_usb
hcitool dev shows:
hcitool con shows:
hctool scan shows:
00:50:F2:E2:A5:A2 Microsoft Mouse
After I push the connect button and type hidd --connect 00:07:61:0d:f6:1d, my mouse works. Then he writes as connection:
< ACL 00:07:61:0D:F6:1D handle 41 state 1 lm MASTER
When I start my computer and move my mouse, the little bluetooth light on my IBM laptop is blinking, but the cursor doesn't move. So he sees that there is a bluetooth device, but he doesn't connect to him automaticaly.