A problem with BlueZ-PAN connection: "Connection failed. Inappropriate ioctl for device(25)"
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 1075575743.2720.71.camel@pegasus
Quoted 6 lines · ext Marcel Holtmann
Hi Tuomo,
Quoted 2 lines
This is an rather old thread (from end of November 2003) to which I am here answering, but because I guess some-one will sooner or later have similar problems I'd like to give a short report how to solve the problem.
Quoted 9 lines
Quoted 3 lines
We even tried to debug the kernel but never found the real reason why above error occurs. Clearly though some module was missing or misloaded. However the solution to the problem was rather simple -- just start all the bluez-daemons manually using a simple script. Our earlier configuration was such that these daemons were started from hotplug-system (
/etc/hotplug/bluetooth.agent) which seemed to work otherwise OK, but as now later we can tell pand seems to be somehow incompatible with hotplugging.I don't know why it now works from the bluetooth.agent script, but the daemons are designed to run from an init script. The hotplug script is for bringing the device up and/or restoring some specific settings.
I was perhaps not too clear in my words, namely I was trying to say that we have never managed to get system working with bluetooth.agent and that we had earlier tried only with bluetooth.agent. Now we have a init script and it working like supposed. I can't anymore remember from where we copied the instructions to use bluetooth.agent, but to use it was definely not our own invention ;-).
Signature · 16 lines
<< Tuomo-Markus Tikkanen <> [email protected] >> << Nokia Research Center <> Phone: +358 71 803 6480 >> << P.O. Box 407 <> Mobile: +358 50 483 6480 >> << FIN-00045 NOKIA GROUP <> FAX: +358 71 803 6210 >> ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Bluez-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bluez-users
Marcel Holtmann
maintainerHi Tuomo,
Quoted 1 line
Quoted 1 line
I don't know why it now works from the bluetooth.agent script, but the
---
sorry, this was a typo. I meant "not".
Quoted 9 lines
Quoted 2 lines
daemons are designed to run from an init script. The hotplug script is for bringing the device up and/or restoring some specific settings.
I was perhaps not too clear in my words, namely I was trying to say that we have never managed to get system working with bluetooth.agent and that we had earlier tried only with bluetooth.agent. Now we have a init script and it working like supposed. I can't anymore remember from where we copied the instructions to use bluetooth.agent, but to use it was definely not our own invention ;-).
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users