[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: hm... doesn't work + can't find mgnokiidev
From: |
marcell mars |
Subject: |
Re: hm... doesn't work + can't find mgnokiidev |
Date: |
Wed, 25 Jun 2003 21:00:22 +0200 |
User-agent: |
Mutt/1.4.1i |
:> > Can't create socket: No such file or directory
:> > Couldn't open PHONET device: Illegal seek
:> > GSM/FBUS init failed!
:> > Xlib: unexpected async reply (sequence 0x38a6)!
:>
:> So this is with xgnokii?
yep...
:> > # gnokii --getnetworkinfo
:> > GNOKII Version 0.5.2
:> > Can't create socket: No such file or directory
:> > Couldn't open PHONET device: No such file or directory
:> > Telephone interface init failed: Command failed.
:> > Quitting.
:>
:> What about gnokii --identify?
the same...
:> Do you have hcid daemon running?
root 6851 0.0 0.2 1404 540 ? S Jun24 0:00 hcid: processing
events
it just says the same no matter if i'm connected to phone through
rfcomm or not... i'm not sure if it reads the .gnokiirc at all....
i even did this:
-rwxrwxrwx 1 root gnokii 3911 Jun 25 20:42 .gnokiirc
no change :(
now i'm not sure i'm doing that right.. so:
* i load all usb bluetooth stuff:
hci_usb, l2cap, bluez (lsmod gives me good info about that)
* run:
# hcid -f /etc/bluetooth/hcid.conf
* plug usb toggle
* check with hcitool scan what is the device in da hood (when there is a new
one
8) )
* put things like this 00:02:EE:C2:79:FA in .gnokiirc (port =
00:02:EE:C2:79:FA)
* # modprobe ussp
* # rfcomm 0 00:02:EE:C2:79:FA 1
* getting this as a result:
Connected /dev/ttyU0 to 00:02:EE:C2:79:FA on channel 1
* # gnokii --identify
* getting this as a result:
GNOKII Version 0.5.2
Can't create socket: No such file or directory
Couldn't open PHONET device: No such file or directory
Telephone interface init failed: Command failed.
Quitting.
is it something that i'm doing wrong.. (i even put BD address instead
of phone address in .gnokiirc in depression :( )... as expected no
results... i'm glad that you tried to help me... hope that we will
find the solution soon....
address@hidden