Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
11-30-2007, 10:14 AM
|
#1
|
|
Member
Registered: Jan 2006
Location: Australia
Distribution: Slackware 12.1
Posts: 173
Rep:
|
Bluetooth startup issue
Hello all,
I have a bluetooth mouse and keyboard which I would like to start up when my slack machine boots. I chmod +x to /etc/rc.d/rc.bluetooth and started hcid, sdpd, and hidd. The others, rfcomm, pand and dund I left off (as I have no use for them).
The problem is rc.bluetooth start spits out an error: Can't listen on HID control channel: Address already in use. If I restart it after boot (or use rc.local to do it) it works fine. If I start it and then start it again, the same error is displayed.
Does anyone know how I can fix this, without having to start, stop, then restart my bluetooth control?
|
|
|
|
11-30-2007, 12:05 PM
|
#2
|
|
Guru
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,818
|
When you make rc.bluetooth executable it will start up during bootup, ff you then login and try to start it manually, you will get an error (because it is already running).
If you need to restart the service to get your hardware working for some reason, then you could put a restart command in rc.local. But if memory serves, BlueTooth is started pretty close to rc.local anyway, so it might not give things enough time to settle down.
|
|
|
|
11-30-2007, 03:34 PM
|
#3
|
|
Member
Registered: Jan 2006
Location: Australia
Distribution: Slackware 12.1
Posts: 173
Original Poster
Rep:
|
I'm not trying to start it manually after startup, I was saying the same error occurs if I do that.
I have the restart command in my rc.local, and that works, but I am wanting to fix the problem, not just cover it up
I had it working before I reinstalled (new hard drive) 
|
|
|
|
11-30-2007, 09:27 PM
|
#4
|
|
Member
Registered: Jan 2006
Location: Australia
Distribution: Slackware 12.1
Posts: 173
Original Poster
Rep:
|
I turned off starting of sdpd by rc.bluetooth and this stops the error, and my mouse and keyboard are working fine now.
Does anyone know why this error happened? Could sdpd be starting up elsewhere perhaps??
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:43 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|