-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have been trying to access my Nokia 6230 using a DKU-2 data cable from CentOS, with some weird results.
Interesting thing is that I have VMWare installed on this machine and, if I install the Nokia Suite inside it, it can access the phone without problems. So all hardware related parts are working.
Anyway, kernel load the cdc_acm module, and gives me /dev/ttyACM0. Accessing this tty (cu -l, minicom, take your pick), I can issue AT commands and get responses. So far so good.
But then I try to access it using some software (gnokii, obex, gammu), it simply won't work.
Trying to use usbserial instead of cdc_acm gives exactly the same result.
Does anyone has any better experience with this setup ?
TIA,
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Aug 18, 2006 at 10:52:36PM -0300, Rodrigo Barbosa wrote:
I have been trying to access my Nokia 6230 using a DKU-2 data cable from CentOS, with some weird results.
(...)
Does anyone has any better experience with this setup ?
I just found the answer here. It takes a combination of obexftp (recompiled, Dag's won't work, because it has no dku2libusb support) for file transfer and gnokii (using a nonstandard nokia_sku2) driver for information.
Freaking 6230 doesn't provide FBUS support, so things get a bit complicated.
Anyway, I'm now able to upload and download files.
For historical reference, this is the best place to start when researching this:
http://wiki.gnokii.org/index.php/DKU2
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Sat, 19 Aug 2006, Rodrigo Barbosa wrote:
On Fri, Aug 18, 2006 at 10:52:36PM -0300, Rodrigo Barbosa wrote:
I have been trying to access my Nokia 6230 using a DKU-2 data cable from CentOS, with some weird results.
(...)
Does anyone has any better experience with this setup ?
I just found the answer here. It takes a combination of obexftp (recompiled, Dag's won't work, because it has no dku2libusb support) for file transfer and gnokii (using a nonstandard nokia_sku2) driver for information.
Freaking 6230 doesn't provide FBUS support, so things get a bit complicated.
Anyway, I'm now able to upload and download files.
For historical reference, this is the best place to start when researching this:
Hi Rodrigo,
Thanks for answering your own question and making a difference ! This mail caused me to rethink the current openobex support.
The problem is that Red Hat is still at openobex 1.1 in FC5, while the latest release is 1.3. So I am sticking to openobex 1.1 for now.
openobex 1.1 has a problem with older libusb (undefined reference to `usb_get_string_simple') so I have to disable usb support in openobex from EL3 and lower otherwise obexftp get these undefined references.
So thanks to your mail I looked again to obexftp, updated openobex to 1.1 (with usb support on EL4, but please do check!) and upped obexftp to 0.19. (obexftp 0.20 has problems with openobex 1.1, likely needs an openobex update)
Let me know if this improves the experience.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Aug 19, 2006 at 04:15:41PM +0200, Dag Wieers wrote:
Thanks for answering your own question and making a difference ! This mail caused me to rethink the current openobex support.
The problem is that Red Hat is still at openobex 1.1 in FC5, while the latest release is 1.3. So I am sticking to openobex 1.1 for now.
Humm, that would be a problem for me, because:
==quote== http://openobex.triq.net/devices/nokia#nokia_6230
Nokia 6230
Works with openobex-1.2 & ObexFTP-0.19. ==quote==
Anyway, I didn't know you followed FC5 versions. I thought that was more like Karan's repo. Then again, at least your repository is not spin-crazy like atrpms (I very afraid to use packages from there).
So thanks to your mail I looked again to obexftp, updated openobex to 1.1 (with usb support on EL4, but please do check!) and upped obexftp to 0.19. (obexftp 0.20 has problems with openobex 1.1, likely needs an openobex update)
Actually, I wasn't able to compile obexftp 0.20 even with openobex 1.3. So I'm using 1.3 and 0.19 here.
Let me know if this improves the experience.
Unfortunatelly my phone is not supported by openobex 1.1, so I really can't test. But it should work ok for plenty of other phones now.
Great work as usual, Dag.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Sat, 19 Aug 2006, Rodrigo Barbosa wrote:
On Sat, Aug 19, 2006 at 04:15:41PM +0200, Dag Wieers wrote:
Thanks for answering your own question and making a difference ! This mail caused me to rethink the current openobex support.
The problem is that Red Hat is still at openobex 1.1 in FC5, while the latest release is 1.3. So I am sticking to openobex 1.1 for now.
Humm, that would be a problem for me, because:
==quote== http://openobex.triq.net/devices/nokia#nokia_6230
Nokia 6230
Works with openobex-1.2 & ObexFTP-0.19. ==quote==
That's a pitty.
Anyway, I didn't know you followed FC5 versions. I thought that was more like Karan's repo. Then again, at least your repository is not spin-crazy like atrpms (I very afraid to use packages from there).
Dries is building for FC4 and FC5. We don't exactly follow FC5 except that EL5 is based on FC5 and I used FC5 to make expectations about library versions.
FC1 was the first distribution that had openobex (1.0.1). FC5 only has 1.1. So I expect EL5 to have openobex 1.1. I cannot add a higher rpmforge openobex in EL4 than will ship with EL5. (In fact, technically I can, but I will not)
I have been shipping libraries before Red Hat did and in some cases my versions in eg. EL3 exceeded was what then suddenly supported in EL4 and this makes it much harder to support both EL3 and EL4 applications that depend on these libraries. So whenever I can, I try to make sure that whatever I ship in EL4 does not exceed what is released with the latest Red Hat release (currently FC5).
Currently that means shipping openobex 1.1 in order not to break gnome-bluetooth or other stuff that will ship with EL5 and to maintain the lineair path between EL2.1, EL3, EL4 and EL5.
If I have evidence that EL5 ships with something newer, I can proceed upgrading openobex and obexftp.
So thanks to your mail I looked again to obexftp, updated openobex to 1.1 (with usb support on EL4, but please do check!) and upped obexftp to 0.19. (obexftp 0.20 has problems with openobex 1.1, likely needs an openobex update)
Actually, I wasn't able to compile obexftp 0.20 even with openobex 1.3. So I'm using 1.3 and 0.19 here.
I tried it as well on my FC5 and failed equally. But I did not look into the problem because I couldn't release them anyway.
Let me know if this improves the experience.
Unfortunatelly my phone is not supported by openobex 1.1, so I really can't test. But it should work ok for plenty of other phones now.
I have a nokia 6230i and that one worked with openobex 1.0.1 and obexftp 0.10.3 and is now working with openobex 1.1 and obexftp 0.19. But I am using bluetooth, not USB.
If the problem is a particular USB problem you might be right. But the OBEX implementation has no problem with my Nokia 6230i. Unless there is a very big difference between an 6230 and a 6230i from the obex point of view.
So I would urge you to try it nevertheless and update the website. It is possible that the person who committed this just entered what he conveniently had available, not the minimum requirements.
Great work as usual, Dag.
You're welcome. Now if only there was a better tool to download files in bulk (or sync the filesystem with phone). I always intended to use python-obexftp for this purpose.
Maybe obexfs (a fuse module) is the way to go with EL5. (I've been waiting to properly use infrared and bluetooth since at least RH7)
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Aug 19, 2006 at 06:08:08PM +0200, Dag Wieers wrote:
FC1 was the first distribution that had openobex (1.0.1). FC5 only has 1.1. So I expect EL5 to have openobex 1.1. I cannot add a higher rpmforge openobex in EL4 than will ship with EL5. (In fact, technically I can, but I will not)
Makes sense.
Actually, I wasn't able to compile obexftp 0.20 even with openobex 1.3. So I'm using 1.3 and 0.19 here.
I tried it as well on my FC5 and failed equally. But I did not look into the problem because I couldn't release them anyway.
Me neither. If 0.19 didn't work, I would but, hey, I'm lazy :)
Let me know if this improves the experience.
Unfortunatelly my phone is not supported by openobex 1.1, so I really can't test. But it should work ok for plenty of other phones now.
I have a nokia 6230i and that one worked with openobex 1.0.1 and obexftp 0.10.3 and is now working with openobex 1.1 and obexftp 0.19. But I am using bluetooth, not USB.
If the problem is a particular USB problem you might be right. But the OBEX implementation has no problem with my Nokia 6230i. Unless there is a very big difference between an 6230 and a 6230i from the obex point of view.
There some some very big differences between 6230 and 6230i in several other aspects, but I don't think OBEX itself is one of them.
USB seems to be pretty different. 6230 uses a DKU-2 cable, while 6230i uses one called CA-53.
So probably I would have no problem with BlueTooth or IR, but with USB it seems to be a no go.
So I would urge you to try it nevertheless and update the website. It is possible that the person who committed this just entered what he conveniently had available, not the minimum requirements.
I actually tried that, and didn't work. Real pitty.
Maybe obexfs (a fuse module) is the way to go with EL5. (I've been waiting to properly use infrared and bluetooth since at least RH7)
I tried it a few moments ago without success, mostly because of USB limitations on the package. Might work for BT or IR.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
Rodrigo Barbosa wrote:
I have been trying to access my Nokia 6230 using a DKU-2 data cable from CentOS, with some weird results.
I fought this battle on a Fedora Core system (even to the point of making a standalone kernel module out of gnokii's DKU2 support), and let me tell you -- in the end, it's not worth it and you don't get a lot of features.(*)
My personal recommendation is to buy a cheap Bluetooth USB dongle ($15 Belkin works great) and use that instead, along with "gammu":
http://www.gammu.org/wiki/index.php?title=Main_Page
My 6230(b) works perfectly over BT with gammu, full filesystem management, contacts/sms/etc. backup and restore, modem use - all that and a bag of chips. I use a Symbian device these days, but I can't imagine the 6230 support has been broken.
$0.02 USD -te
(*) The beginnings of some of my (mis)adventures of DKU2: http://thread.gmane.org/gmane.linux.drivers.gammu/2114/focus=2114
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, Aug 19, 2006 at 11:44:47AM -0700, Troy Engel wrote:
Rodrigo Barbosa wrote:
I have been trying to access my Nokia 6230 using a DKU-2 data cable from CentOS, with some weird results.
I fought this battle on a Fedora Core system (even to the point of making a standalone kernel module out of gnokii's DKU2 support), and let me tell you -- in the end, it's not worth it and you don't get a lot of features.(*)
Yeah, I ended up finding all that out through some pain myself. But the only thing I need is to transfer files, so obexftp is doing the job fine.
And yes, I'm looking to get a cheap BT adapter. Problem is, they are pretty expensive around here (US$150+).
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-
Dag Wieers -
Rodrigo Barbosa -
Troy Engel