Panic42 said:
Quote:
With Code:
ps -A | grep hidd With hidd --show he doesn't show at startup a connection, but after i have run hidd --connect, he shows: Quote:
|
Quote:
Anyway, this is the place to continue your bug search. Your problem is clearly that the hidd server has NOT started; you will have to find out why---perhaps by looking in your system log. A few possibly interesting points from my log: Code:
kernel: usbcore: registered new driver hiddev Code:
alias net-pf-31 bluetooth should produce something like Code:
root 1813 1 0 08:58 ? 00:00:00 /usr/bin/hidd --server -- Arne |
Holly Crap it worked. Thanks for the help Arne.
|
Quote:
have done different now that makes it work? -- Arne |
The problem was exactly as you stated. The man page says that you have to have "--" infront of your hidd option. So I followed your directions to the tee.
hidd --search hidd --connnect device<hex> Hit the pair botton on the bottom of my mouse. |
Quote:
commands; the top one searches for your mouse and connects it, while you manually indicate the BT address to connect in the bottom one. And now you should never need them again! Just make sure hidd --server is started, and waggle your mouse. -- Arne |
I added now: alias net-pf-31 bluetooth to my /etc/modprobe.conf file. But this didn't help.
My log file contains only these lines: Quote:
|
Hmmm...it seems as if the hid kernel modules haven't been
loaded. Strange. I am running FC4 kernel 2.6.12 which apparently has them built into the kernel. Perhaps you should do a 'locate hiddev' or similar. -- Arne |
Despite my mouse working I find that my mouse is also not reconnecting and I need to reconnect after a long period of not being used or on bootup. I actually have to manually reconnect each time I want to use it after not using it for a bit of time. I created a script that helps me to do this a little faster but its still annoying. I am going to back track through this particular thread and see if I can find some other things that may help.
|
with locate hiddev, I receive the message:
Quote:
My computer also disconnects after a long period, my problem is the same as lmcilwain's |
Quote:
I intended that you yourself would think of relevant things to look for. Relevant things might be hid.ko or hid-core or usbhid or... As I said, your problem seems to be that the hidd server does not start (or perhaps crashes immediately), because running hidd --server and then ps -A | grep hidd should result in something like root 1801 1 0 08:01 ? 00:00:00 /usr/bin/hidd --server Question: are you running hidd --server as root? Another point: You should consider editing /etc/updatedb.conf to avoid the error message from locate. -- Arne |
When I run hidd --server as root, is works.
I added this now to my /etc/rc.d/rc.local file. Thank you for your help! |
Quote:
a file which I believe you have. Then enable hidd at the runlevel you are running -- this can typically be done using some gui runlevel editor (e.g., Server Settings->Services in Gnome). By the way, could you please tell me whether you see any difference in your log file when running hidd as root and as non-root? -- Arne |
I don't know how to enable hidd at the runlevel I'm running.
When I run hidd --server as root in log file is written: Quote:
Quote:
Quote:
Quote:
|
Quote:
Quote:
tail -f /var/log/messages Quote:
This contradicts your post#16 . It is hard to perform collaborative debugging when suggestions are silently ignored and information cannot be trusted. -- Arne |
All times are GMT -5. The time now is 12:13 AM. |