Here is what I get with the new chat script. log file is attached $ sudo pppd call barry-verizon usb_set_debug: Setting debugging level to 9 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Skipping non bus directory devices usb_os_find_busses: Found 007 usb_os_find_busses: Found 001 usb_os_find_busses: Found 002 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 003 usb_os_find_busses: Found 004 usb_os_find_devices: Found 001 on 007 usb_os_find_devices: Found 001 on 001 usb_os_find_devices: Found 002 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 006 on 006 usb_os_find_devices: Found 004 on 006 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 003 on 006 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 006 usb_os_find_devices: Found 001 on 006 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 001 on 004 usb_os_find_busses: Skipping non bus directory devices usb_os_find_busses: Found 007 usb_os_find_busses: Found 001 usb_os_find_busses: Found 002 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 003 usb_os_find_busses: Found 004 usb_os_find_devices: Found 001 on 007 usb_os_find_devices: Found 001 on 001 usb_os_find_devices: Found 002 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 006 on 006 usb_os_find_devices: Found 004 on 006 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 003 on 006 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 006 usb_os_find_devices: Found 001 on 006 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 001 on 004 usb_os_find_busses: Skipping non bus directory devices usb_os_find_busses: Found 007 usb_os_find_busses: Found 001 usb_os_find_busses: Found 002 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 003 usb_os_find_busses: Found 004 usb_os_find_devices: Found 001 on 007 usb_os_find_devices: Found 001 on 001 usb_os_find_devices: Found 002 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 006 on 006 usb_os_find_devices: Found 004 on 006 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 003 on 006 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 006 usb_os_find_devices: Found 001 on 006 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 001 on 004 Connect script failed Waiting for 1 child processes... script /usr/local/sbin/pppob -l /tmp/pppod.log -v, pid 20311 sending SIGTERM to process 20311
On Thu, Aug 7, 2008 at 3:30 PM, Andy Herkey <[EMAIL PROTECTED]> wrote: > Graham Smith wrote: >> Thanks Chris >> >> I don't use Windows, so I can't try that. >> >> I tried dialing #777 directly from the phone and I get the error >> message "can't connect as dialed". The phone has data service. Do I >> need to modify the scripts? >> >> Graham >> >> On Thu, Aug 7, 2008 at 1:12 PM, Chris Frey <[EMAIL PROTECTED]> wrote: >> >>> On Wed, Aug 06, 2008 at 08:55:53PM -0700, Graham Smith wrote: >>> >>>> I'm running 64bit Ubuntu 8.04. I've installed barry 0.13 (from source) >>>> and edited the options and chat file to match the ubuntu file >>>> locations (Attached). >>>> >>> Hi Graham, >>> >>> Thanks for the report. >>> >>> >>> >>>> When I try pppd I get the following >>>> >>>> $ pppd call barry-verizon >>>> Initializing >>>> Connect script failed >>>> Waiting for 1 child processes... >>>> script /usr/local/sbin/pppob, pid 28678 >>>> sending SIGTERM to process 28678 >>>> >>>> btool output is >>>> Blackberry devices found: >>>> Device ID: 0x6296d0. PIN: 31a74b1c, Description: RIM 8800 Series >>>> Colour CDMA Handheld >>>> Using device (PIN): 31a74b1c >>>> >>>> >>>> any help is greatly appreciated. >>>> >>> I looked at the pppob log you attached, and my first guess is that the >>> chat script may not match your provider exactly. I'm assuming you're >>> using Verizon, since you picked that script. >>> >>> Have you tried using the modem from Windows? Does the #777 phone >>> number work there? >>> >>> Thanks, >>> - Chris >>> >>> >>> ------------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >>> Build the coolest Linux based applications with Moblin SDK & win great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> Barry-devel mailing list >>> Barry-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/barry-devel >>> >>> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Barry-devel mailing list >> Barry-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/barry-devel >> > Graham, > It looks to me that the AT commands aren't responding properly. > Create a new chat script with the following lines and send the output. > > ABORT ERROR > '' AT&F > OK ATZ > OK AT > OK ATE0 > OK ATE0V1 > OK ATS0=0 > OK AT > OK ATE0V1 > OK ATI > OK AT > OK ATDT#777 > CONNECT > > --Andy > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel >
pppod.log
Description: Binary data
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
