Re: [Bluez-users] Can't connect RFCOMM channel: Resource temporarily unavailable

[Swathi Mathur80 <swathi_mathur80@yahoo.com>]

Hello Marcel,
Yes, i am running btsco module on Fedora Core 4. What
do you mean by your statement "if nothing else works
try to switch it off".
Warm Regards,
Swathi

--- Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Swathi,
> 
> > As per your request i have pasted the result of
> > “hciconfig -a” and “hcidump -X -V”. Along
> with it
> > someother information which i thought might be
> helpful
> > in debugging.
> > 
> > When i first started my pc if found that hcid
> demon
> > was not running. So i re-started the bluetooth
> > services and made the hcid to run
> >
>
-------------------------------------------------------
> > [root@localhost bluetooth]# /etc/init.d/bluetooth
> > status
> > hcid is stopped
> > sdpd (pid 1729) is running...
> > [root@localhost bluetooth]# /etc/init.d/bluetooth
> > restart
> > Stopping Bluetooth services:                      
>    
> >     [FAILED]
> > Starting Bluetooth services:                      
>    
> >     [  OK  ]
> > [root@localhost bluetooth]# /etc/init.d/bluetooth
> > restart
> > Stopping Bluetooth services:                      
>    
> >     [  OK  ]
> > Starting Bluetooth services:                      
>    
> >     [  OK  ]
> >
>
-------------------------------------------------------
> > 
> > The headset is being put in the pairing mode.
> Hcidump
> > -X -V is running in the background. I execute the
> > btsco command
> >
>
-------------------------------------------------------
> > [root@localhost /]# btsco 00:08:C6:3E:54:2C -v -r
> > btsco v0.4c
> > Device is 1:0
> > Error: Failed to connect to SDP server: Function
> not
> > implemented
> > Assuming channel 2
> > 
> > Voice setting: 0x0060
> > Can't connect RFCOMM channel: Resource temporarily
> > unavailable
> >
>
-------------------------------------------------------
> > 
> > output of hcidump -X -V is as below
> >
>
-------------------------------------------------------
> > < HCI Command: Create Connection (0x01|0x0005)
> plen 13
> >     bdaddr 00:08:C6:3E:54:2C ptype 0xcc18 rswitch
> 0x01
> > clkoffset 0x0000
> >     Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> > > HCI Event: Command Status (0x0f) plen 4
> >     Create Connection (0x01|0x0005) status 0x00
> ncmd 1
> > > HCI Event: PIN Code Request (0x16) plen 6
> >     bdaddr 00:08:C6:3E:54:2C
> > > HCI Event: Connect Complete (0x03) plen 11
> >     status 0x22 handle 41 bdaddr 00:08:C6:3E:54:2C
> > type ACL encrypt 0x00
> >     Error: LMP Response Timeout
> > < HCI Command: Read Voice Setting (0x03|0x0025)
> plen 0
> > > HCI Event: Command Complete (0x0e) plen 6
> >     Read Voice Setting (0x03|0x0025) ncmd 1
> >     status 0x00 voice setting 0x0060
> > < HCI Command: Create Connection (0x01|0x0005)
> plen 13
> >     bdaddr 00:08:C6:3E:54:2C ptype 0xcc18 rswitch
> 0x01
> > clkoffset 0x0000
> >     Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> > > HCI Event: Command Status (0x0f) plen 4
> >     Create Connection (0x01|0x0005) status 0x00
> ncmd 1
> > > HCI Event: PIN Code Request (0x16) plen 6
> >     bdaddr 00:08:C6:3E:54:2C
> > > HCI Event: Connect Complete (0x03) plen 11
> >     status 0x22 handle 42 bdaddr 00:08:C6:3E:54:2C
> > type ACL encrypt 0x00
> >     Error: LMP Response Timeout
> >
>
-------------------------------------------------------
> 
> run the next one with "hcidump -X -V -t" to get the
> timestamps, but I am
> quite sure that the hcid is not running.
> 
> >
>
-------------------------------------------------------
> > [root@localhost mail]# /etc/init.d/bluetooth
> status
> > hcid (pid 3136) is running...
> > sdpd (pid 3140) is running...
> >
>
-------------------------------------------------------
> > output of “ps x”
> >  2714 ?        Ss     0:00 hcid: processing events
> >  2716 ?        Ss     0:00 sdpd
> >
>
-------------------------------------------------------
> 
> Are you 100% sure that these are running as root.
> You might better check
> with "ps -u root | grep hcid". The non-matching PIDs
> make it a little
> but suspicious.
> 
> Check /var/log/messages for any syslog output.
> However since this looks
> like a RedHat or Fedora distribution, it might be a
> SELinux problem. If
> nothing else works, try to switch it off.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do
> you grep through log files
> for problems?  Stop!  Download the new AJAX search
> engine that makes
> searching your log files as easy as surfing the 
> web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/bluez-users
> 



	
		
__________________________________ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users