Graham Smith wrote:
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
Graham, Sorry it took so long to get back to you.We had a major power outage in our data center last night. Nothing but system problems all night and day. What ever happened it took out both of the UPs with it. :(
I want to make sure that you have tried the new chat script multiple times since I only saw one try in the logs and there wasn't a close by pppob. I have seen this before when the modem isn't getting initialized properly and the device sometimes needs to be re-cycled. First try re-pluging the usb. I don't like these next options and never had to do them myself; try powering off and last remove the battery.
I am attaching a ruby script that uses pppob to send commands to the modem to see how it responds. You may need install ruby and modify the $PPP variable in the modemtest.rb script to point to where pppob is installed.
Please run this script and send me the screen output and the /tmp/modemtest.log it creates.
Thanks, Andy
modemtest.rb
Description: application/ruby
begin:vcard fn:Andy Herkey n:Herkey;Andy email;internet:[EMAIL PROTECTED] version:2.1 end:vcard
------------------------------------------------------------------------- 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
