One question: is Barry really needed if you have blackberry_charge enabled in the kernel? It recognizes and charges my blackberry at full charge without a problem. I don't have barry installed btw.

As for xmblackberry, I have version 0.3.0 installed and with backup/restore (tested) and sync (not tested yet) working. The sync has options that shows and all I need to do is configure what options/programs I want to sync to. The only thing I can't seem to get working is the modem part.

I copied your scripts, the modem is recognized and it initializes but returns with a bunch of sent and receive handshaking that repeats forever, it doesn't complete the script to give me an ip address, gateway, and dns so I can browse online. I'm with t-mobile btw.

One question: is Barry really needed if you have blackberry_charge enabled in the kernel? It recognizes and charges my blackberry at full charge without a problem. I don't have barry installed btw.

bcharge does an additional reset of the USB port with a magic value that exposes the BB functionality on newer devices (8100 and up, SD cards). Your 7100T might just work without needing the bcharge tool out of Barry, as it doesn't have USB Mass Storage and everything is on channel 1 already. Because you can use xmblackberry successfully to backup/restore my gut instinct says you don't need bcharge like newer devices - skip the Barry needs.

It looks like the devel files for libXpm are not installed on your system; if using a Fedora system you want 'libXpm-devel' RPM file, for Ubuntu I'm sure it's very similar. Install the appropriate package and you're off and rocking - be prepared for others maybe, since one was not installed you never know.

Running Ubuntu 7.10 with Pearl 8100 Tmobile. I believe I installed everything you said, went through step by step. I get to part of running XmBlackBerry and i get this:
ztrane@laptop:~/XmBlackBerry$ XmBlackBerry
sync.c:sync_init(296) - rim-sync plugin not available. Unable to find plugin "rim-sync". This can be caused by unresolved symbols Sync disabled.

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

I got this to work as well. I compiled xmblackberry 0.30.0 and barry 0.9. The only thing I would add is that xmblackberry expected a libXm.so.3 -- just make a link from libXm.so.4.0.0 to libXm.so.3 and you're set!

Thanks a lot for this guide, I would have had a much harder time of it without this. I'm not going to use my BB as internet access at this point, but I'm not going to boot into windows just to mess around with the filesystem either!

I have a 7105t unlocked with Cingular (AT&T) service on an Ubuntu 7.10 Gusty OS. I can't get this thing to work...I am pretty sure it should work because I got it to work in windoze, doing a tethered modem. I got everything to compile fine and Barry and XmBlackberry both seem to be working (they reconize and connect to the device). What's funny is the very first time I ran it, it dialed an the whole bit but never connected...I messed around with that for a while and now no matter what I do I only get this output when running the call command:

sudo pppd call blackberry
Initializing
ATE
Connect script failed

I've tried messing around with putting in as the username and CINGULAR1 as the password but none of that works. I have also tried many diffrerent scripts from google but again nothing.

So I'm trying to make this work on Xandros (advanced mode) with no luck.
I've isntalled and pinned just about every possible repository I can, and seem to have all the required packages installed.
No errors when I'm installing anything, but when I sudo bcharge & sudo bcharge -o, I get: