[gnome-bluetooth] [gnome-phone-manager] "Can't get device list"

Thorsten Ball mrnugget at gmail.com
Wed Nov 10 09:13:38 GMT 2004


Thanks for helping. I got it to work. I recompiled the kernel
and could use phone-manager as root. But as normal user
i could not access it, so i searched in the Gentoo Forums
and found the right udev rules. 
Maybe they are interessting for someone.

Rule:
KERNEL="rfcomm[0-9]*", NAME="rfcomm/%n", SYMLINK="%k phone"

Permissions:
rfcomm/[0-9]*:root:dialout:0666

Hope that helps someone.

Thanks and regards,
   Thorsten


On Wed, 10 Nov 2004 09:59:03 +0100, Jens Geiregat
<jens.geiregat at gmail.com> wrote:
> I had the same problem on gentoo ;-) . I solved it like this:
> 
> I quote myself:
> --------------------------------------------------------------------
> I got it working!
> 
> First, I recompiled my kernel with:
> <M>   L2CAP protocol support
> < >   SCO links support
> <M>   RFCOMM protocol support
> [*]     RFCOMM TTY support
> 
> (the RFCOMM TTY support wasn't switched on before)
> 
> But it still didn't work like it should, but the errors were always
> about RFCOMM.
> Google gave me this:
> http://www.linuxquestions.org/questions/answers/194
> 
> execute this command:
> cd /dev && mknod --mode 666 /dev/rfcomm0 c 216 0
> 
> and it should work.
> --------------------------------------------------------
> 
> Dunno if it will help you out, but that did the trick for me (don't
> forget to recompile your kernel and reboot :-D ). You do have the same
> error as I had:
> ------------------------------------------------------
> > > > ** (gnome-phone-manager:11522): WARNING **: Unable to obtain RFCOMM
> > > > connection (-1)
> ------------------------------------------------------
> So, when I changed my kernel and added the device, it worked
> (gnome-phone-manager was able to find the device, and connect to it).
> 
> Good luck!
> 
> 
> 
> 
> Jens Geiregat
> 
> On Wed, 10 Nov 2004 09:36:34 +0100, Thorsten Ball <mrnugget at gmail.com> wrote:
> > I looked through the whole archive (because i was not able to find the
> > search-function, is there something like that?) but didn't find a solution
> > to my problem. But maybe, the T610 doesn't work with the gnome-phone-manager
> > as it seems, right?
> >
> > Regards,
> >  Thorsten
> >
> > PS: Am i handling this mailing-list-stuff right? I'm new to this, sorry.
> >
> > On Wed, 10 Nov 2004 08:53:25 +0100, Jens Geiregat
> >
> >
> > <jens.geiregat at gmail.com> wrote:
> > > Search the mailing list archive. This problem has been mentioned before.
> > >
> > > Jens Geiregat
> > >
> > >
> > >
> > >
> > > On Wed, 10 Nov 2004 07:00:35 +0100, Thorsten Ball <mrnugget at gmail.com> wrote:
> > > > Hello,
> > > >
> > > > i got a problem with getting gnome-phone-manager to work. I'm using Gentoo
> > > > with the newest version of gnome-bluetooth (which works great) and now
> > > > i just tried the gnome-phone-manager. But whenever i start it and it wants
> > > > to connect to the selected mobile phone (Sony Ericsson T610) i'm getting
> > > > this error in the shell:
> > > >
> > > > ---
> > > > $ gnome-phone-manager
> > > > conn_complete:  status 0x00
> > > > Browsing 00:0E:07:1D:99:A7 ...
> > > > Service Name: Dial-up Networking
> > > > Service RecHandle: 0x10000
> > > > Protocol Descriptor List:
> > > >   "L2CAP" (0x0100)
> > > >   "RFCOMM" (0x0003)
> > > >     Channel: 1
> > > > Service Class ID List:
> > > >   "Dialup Networking" (0x1103)
> > > >   "Generic Networking" (0x1201)
> > > > ** Message: device 00:0E:07:1D:99:A7 (Dialup Networking) port 1
> > > >
> > > > ** Message: device 00:0E:07:1D:99:A7 (Generic Networking) port 1
> > > >
> > > > ** (gnome-phone-manager:11522): WARNING **: Can't get device list
> > > > Browsing 00:0E:07:1D:99:A7 ...
> > > > Service Name: Dial-up Networking
> > > > Service RecHandle: 0x10000
> > > > Protocol Descriptor List:
> > > >   "L2CAP" (0x0100)
> > > >   "RFCOMM" (0x0003)
> > > >     Channel: 1
> > > > Service Class ID List:
> > > >   "Dialup Networking" (0x1103)
> > > >   "Generic Networking" (0x1201)
> > > > ** Message: device 00:0E:07:1D:99:A7 (Dialup Networking) port 1
> > > >
> > > > ** Message: device 00:0E:07:1D:99:A7 (Generic Networking) port 1
> > > >
> > > > ** (gnome-phone-manager:11522): WARNING **: Can't get device list
> > > >
> > > > ** (gnome-phone-manager:11522): WARNING **: Can't get device list
> > > > ** Message: rfcomm attempting to connect 00:0E:07:1D:99:A7 chan 1, got -1
> > > >
> > > > ** (gnome-phone-manager:11522): WARNING **: Unable to obtain RFCOMM
> > > > connection (-1)
> > > > ** Message: New connection device is (null)
> > > > ** Message: No device!
> > > > ** Message: Exiting connect thread
> > > > ---
> > > >
> > > > I don't know where the problem is, because sending and receiving files
> > > > over bluetooth works
> > > > very good.
> > > >
> > > > Maybe someone has an idea.
> > > >
> > > > Regards,
> > > > Thorsten
> > > >
> > > > _______________________________________________
> > > > gnome-bluetooth mailing list
> > > > gnome-bluetooth at usefulinc.com
> > > > http://lists.usefulinc.com/mailman/listinfo/gnome-bluetooth
> > > >
> > >
> > > _______________________________________________
> > > gnome-bluetooth mailing list
> > > gnome-bluetooth at usefulinc.com
> > > http://lists.usefulinc.com/mailman/listinfo/gnome-bluetooth
> > >
> >
> > _______________________________________________
> >
> >
> > gnome-bluetooth mailing list
> > gnome-bluetooth at usefulinc.com
> > http://lists.usefulinc.com/mailman/listinfo/gnome-bluetooth
> >
>



More information about the gnome-bluetooth mailing list