Re: Bill Lowther, USA, Ubuntu 9.04 kenal 2.6.28-15-generic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



RE, Do I have to run $ sudo modprobe agrserial prior to the initial
fax transmission following every bootup?
-----------
Yes
Not autoloading any winmodem driver on bootup is a safety measure.
Part of the code is closed source, and hence cannot be checked with
routine debug tools, during changes/upgrades in other System
components.
Should some incompatibility cause a Crash on bootup,
it would require skilled use of a Rescue Disk, to enable a clean
bootup of the System.
Again,
$ sudo modprobe agrserial
which is a component in agrsm-test,
does suffice for modem setup.

RE: Also, where is the "efax list"  that you referred to below? Do a
Google search with "efax Linux"

MarvS

On Mon, Oct 26, 2009 at 4:20 PM, Bill <donnabill22@xxxxxxxxxxx> wrote:
> Marvin:
>     I did $ sudo modprobe agrserial, launched Efax-gtk, and
> successfully sent a fax.  However, I did a restart on my computer, tried
> to send a fax and got the following messages:
>
> efax-0.9a: 15:54:03 Error: can't open serial port /dev/ttySAGR: No such
> file or directory
> efax-0.9a: 15:54:03 failed page (path to file)
> efax-0.9a: 15:54:03 finished - unrecoverable error
>
> So I did $ sudo modprobe agrserial again, followed by $ sudo agrsm-test
> and got the following messages:
>
> Found drivers for boot kernel 2.6.28-16-generic at:
> /lib/modules/2.6.28-16-generic/updates/dkms/agrserial.ko
> /lib/modules/2.6.28-16-generic/updates/dkms/agrmodem.ko
>
>
>
> Loading drivers:
>
> Drivers loaded:
> agrserial              19808  0
> agrmodem             1340932  1
>
> and symbolic link created:
> lrwxrwxrwx 1 root root 12 2009-10-26 16:00 /dev/ttySAGR -> /dev/ttyAGS3
>
> Checking for utility wvdialconf
> Found /usr/bin/wvdialconf, preparing to run:
> wvdialconf /etc/wvdial.conf
> A file /etc/wvdial.conf already exists, first renaming
> to /etc/wvdial.200910260010
>
> Modem Port Scan<*1>: S0   S1   S2   S3
> ttySAGR<*1>: ATQ0 V1 E1 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 Z -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
> ttySAGR<*1>: Modem Identifier: ATI -- Agere SoftModem Version 2.1.80.0
> ttySAGR<*1>: Speed 4800: AT -- OK
> ttySAGR<*1>: Speed 9600: AT -- OK
> ttySAGR<*1>: Speed 19200: AT -- OK
> ttySAGR<*1>: Speed 38400: AT -- OK
> ttySAGR<*1>: Speed 57600: AT -- OK
> ttySAGR<*1>: Speed 115200: AT -- OK
> ttySAGR<*1>: Max speed is 115200; that should be safe.
> ttySAGR<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
> /etc/wvdial.conf<Warn>: Can't open '/etc/wvdial.conf' for reading: No
> such file or directory
> /etc/wvdial.conf<Warn>: ...starting with blank configuration.
> ttySAGR<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
> Found a modem on /dev/ttySAGR.
>
> Modem detection successful
> Read wdial.txt
> Then edit /etc/wvdial.conf  with:
>  sudo gedit /etc/wvdial.conf
> at the lines beginning with ; and deleting the ; < >  "
> Then try a dialout with:
>   sudo wvdial
>
> The installation record has been written to ./agrsm-test.txt
> *************************************************************
>
> Do I have to run $ sudo modprobe agrserial prior to the initial fax
> transmission following every bootup?
>
> Also, where is the "efax list"  that you referred to below?
>
> TIA,
> Bill
>
>
>
>
> -----Original Message-----
> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
> To: A4Skyhawk <donnabill22@xxxxxxxxxxx>
> Cc: discuss@xxxxxxxxxxxxx
> Subject: Re: Bill Lowther, USA, Ubuntu 9.04 kenal 2.6.28-15-generic
> Date: Mon, 26 Oct 2009 15:19:19 -0400
>
> A4,
>
> You needn't run my agrsm-test, once it has been shown to be effective.
>  Rather it should suffice to:
> $ sudo modprobe agrserial
> which will suffice to load agrmodem+agrserial and dynamically create
> the port, with the symbolic to it:
>   /dev/ttySAGR -->  /dev/ttyAGS3
>
> This provides the access to the modem, and all else is an efax issue,
> better addressed to the efax list.
>
> MarvS
>
>
> On Mon, Oct 26, 2009 at 3:10 PM, A4Skyhawk <donnabill22@xxxxxxxxxxx> wrote:
>>
>> I am now able to fax out successfully after receiving help here
>> (http://www.nabble.com/ScanModem-report-to25518870.html).  Thank you very
>> much for your support.
>> A couple of issues remain:
>> 1) When I first launch Efax-gtk and try to send a fax, I get an error
>> message - "unrecoverable error".  I then open terminal and execute $ sudo
>> agrsm-test, after which I can send a fax.  Is this the required first step
>> to using efax-gtk, or am I missing something in the setup of efax-gtk?
>> 2) I have not been able to receive a fax.  Here are the messages following a
>> few of my attempts:
>>
>> efax-0.9a: 12:21:27 waiting for activity
>> efax-0.9a: 12:22:20 activity detected
>> efax-0.9a: 12:22:33 fax call answered
>> efax-0.9a: 12:23:03 Warning: 577 reception errors
>> efax-0.9a: 12:23:04 Warning: reception errors
>> efax-0.9a: 12:22:33 remote ID ->          16103884447
>> efax-0.9a: 12:22:33 session  98lpi 14.4kbps 8.5"/215mm  any   1D    -     -
>> 20ms
>> efax-0.9a: 12:22:35 session  98lpi 14.4kbps 8.5"/215mm  any   1D    -     -
>> 20ms
>> efax-0.9a: 12:23:03 received 578 lines with 577 errors
>> efax-0.9a: 12:23:09 finished - success
>>
>> another :
>>
>> efax-0.9a: 12:23:10 opened /dev/ttySAGR
>> efax-0.9a: 12:23:11 using Agere SoftModem Version 2.1.80.0Agere
>> SystemsData/Fax2.1.80.0 in class 2.0
>> efax-0.9a: 12:23:12 waiting for activity
>> efax-0.9a: 12:25:28 activity detected
>> Too many failed attempts
>> efax-0.9a: 12:25:42 fax call answered
>> *** buffer overflow detected ***: efix-0.9a terminated
>> ======= Backtrace: =========
>> /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7df2da8]
>> /lib/tls/i686/cmov/libc.so.6[0xb7df0eb0]
>> efix-0.9a[0x804c3ae]
>> efix-0.9a[0x804c80e]
>> efix-0.9a[0x8049dae]
>> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7d0b775]
>> efix-0.9a[0x8048f61]
>> ======= Memory map: ========
>> 08048000-08052000 r-xp 00000000 08:02 57318      /usr/bin/efix-0.9a
>> 08052000-08055000 rw-p 00009000 08:02 57318      /usr/bin/efix-0.9a
>> 08055000-08069000 rw-p 08055000 00:00 0
>> 085ec000-0860d000 rw-p 085ec000 00:00 0          [heap]
>> b7b76000-b7b83000 r-xp 00000000 08:02 2599       /lib/libgcc_s.so.1
>> b7b83000-b7b84000 r--p 0000c000 08:02 2599       /lib/libgcc_s.so.1
>> b7b84000-b7b85000 rw-p 0000d000 08:02 2599       /lib/libgcc_s.so.1
>> b7b94000-b7b95000 rw-p b7b94000 00:00 0
>> b7b95000-b7bd4000 r--p 00000000 08:02 13369
>> /usr/lib/locale/en_US.utf8/LC_CTYPE
>> b7bd4000-b7bd5000 r--p 00000000 08:02 13374
>> /usr/lib/locale/en_US.utf8/LC_NUMERIC
>> b7bd5000-b7bd6000 r--p 00000000 08:02 13377
>> /usr/lib/locale/en_US.utf8/LC_TIME
>> b7bd6000-b7cc1000 r--p 00000000 08:02 13368
>> /usr/lib/locale/en_US.utf8/LC_COLLATE
>> b7cc1000-b7cc2000 rw-p b7cc1000 00:00 0
>> b7cc2000-b7cf2000 r-xp 00000000 08:02 2649       /lib/libpcre.so.3.12.1
>> b7cf2000-b7cf3000 r--p 0002f000 08:02 2649       /lib/libpcre.so.3.12.1
>> b7cf3000-b7cf4000 rw-p 00030000 08:02 2649       /lib/libpcre.so.3.12.1
>> b7cf4000-b7cf5000 rw-p b7cf4000 00:00 0
>> b7cf5000-b7e51000 r-xp 00000000 08:02 2659
>> /lib/tls/i686/cmov/libc-2.9.so
>> b7e51000-b7e52000 ---p 0015c000 08:02 2659
>> /lib/tls/i686/cmov/libc-2.9.so
>> b7e52000-b7e54000 r--p 0015c000 08:02 2659
>> /lib/tls/i686/cmov/libc-2.9.so
>> b7e54000-b7e55000 rw-p 0015e000 08:02 2659
>> /lib/tls/i686/cmov/libc-2.9.so
>> b7e55000-b7e58000 rw-p b7e55000 00:00 0
>> b7e58000-b7f0e000 r-xp 00000000 08:02 12548
>> /usr/lib/libglib-2.0.so.0.2000.1
>> b7f0e000-b7f0f000 r--p 000b5000 08:02 12548
>> /usr/lib/libglib-2.0.so.0.2000.1
>> b7f0f000-b7f10000 rw-p 000b6000 08:02 12548
>> /usr/lib/libglib-2.0.so.0.2000.1
>> b7f10000-b7f11000 r--p 00000000 08:02 13372
>> /usr/lib/locale/en_US.utf8/LC_MONETARY
>> b7f11000-b7f12000 r--p 00000000 08:02 13378
>> /usr/lib/locale/en_US.utf8/LC_MESSAGES/SYS_LC_MESSAGES
>> b7f12000-b7f13000 r--p 00000000 08:02 13375
>> /usr/lib/locale/en_US.utf8/LC_PAPER
>> b7f13000-b7f14000 r--p 00000000 08:02 13373
>> /usr/lib/locale/en_US.utf8/LC_NAME
>> b7f14000-b7f15000 r--p 00000000 08:02 13367
>> /usr/lib/locale/en_US.utf8/LC_ADDRESS
>> b7f15000-b7f16000 r--p 00000000 08:02 13376
>> /usr/lib/locale/en_US.utf8/LC_TELEPHONE
>> b7f16000-b7f17000 r--p 00000000 08:02 13371
>> /usr/lib/locale/en_US.utf8/LC_MEASUREMENT
>> b7f17000-b7f1e000 r--s 00000000 08:02 2619
>> /usr/lib/gconv/gconv-modules.cache
>> b7f1e000-b7f1f000 r--p 00000000 08:02 13370
>> /usr/lib/locale/en_US.utf8/LC_IDENTIFICATION
>> b7f1f000-b7f21000 rw-p b7f1f000 00:00 0
>> b7f21000-b7f22000 r-xp b7f21000 00:00 0          [vdso]
>> b7f22000-b7f3e000 r-xp 00000000 08:02 7999       /lib/ld-2.9.so
>> b7f3e000-b7f3f000 r--p 0001b000 08:02 7999       /lib/ld-2.9.so
>> b7f3f000-b7f40000 rw-p 0001c000 08:02 7999       /lib/ld-2.9.so
>> bf821000-bf840000 rw-p bffe1000 00:00 0          [stack]
>> rangecheck -15
>> rangecheck -15
>>
>> ** (evince:11549): WARNING **: Error rendering thumbnail
>> rangecheck -15
>> efax-0.9a: 12:26:24 Warning: 593 reception errors
>> rangecheck -15
>> efax-0.9a: 12:26:40 Error: timed out after waiting
>> efax-0.9a: 12:26:40 Warning: wrong response after command: +FKS
>> efax-0.9a: 12:25:42 remote ID ->          16103884447
>> efax-0.9a: 12:25:42 session  98lpi 14.4kbps 8.5"/215mm  any   1D    -     -
>> 20ms
>> efax-0.9a: 12:25:44 session  98lpi 14.4kbps 8.5"/215mm  any   1D    -     -
>> 20ms
>> efax-0.9a: 12:26:24 received 593 lines with 593 errors
>> efax-0.9a: 12:26:40 finished - invalid modem response
>>
>> another:
>>
>> efax-0.9a: 14:18:38 opened /dev/ttySAGR
>> efax-0.9a: 14:18:40 using Agere SoftModem Version 2.1.80.0Agere
>> SystemsData/Fax2.1.80.0 in class 2.0
>> efax-0.9a: 14:18:55 fax call answered
>> efax-0.9a: 14:19:37 Warning: 588 reception errors
>> efax-0.9a: 14:19:53 Error: timed out after waiting
>> efax-0.9a: 14:19:53 Warning: wrong response after command: +FKS
>> efax-0.9a: 14:18:55 remote ID ->          16103884447
>> efax-0.9a: 14:18:55 session  98lpi 14.4kbps 8.5"/215mm  any   1D    -     -
>> 20ms
>> efax-0.9a: 14:18:57 session  98lpi 14.4kbps 8.5"/215mm  any   1D    -     -
>> 20ms
>> efax-0.9a: 14:19:37 received 588 lines with 588 errors
>> efax-0.9a: 14:19:53 finished - invalid modem response
>>
>> When I open "List received faxes", and double click on the date/time title
>> for that attempted fax receipt, nothing opens in document viewer, it just
>> displays "Loading" and no other text.
>>
>> Thank you for your support,
>> Bill
>>
>> --
>> View this message in context: http://www.nabble.com/Bill-Lowther%2C-USA%2C-Ubuntu-9.04-kenal-2.6.28-15-generic-tp26065637p26065637.html
>> Sent from the Linux Winmodem Support - Discussion mailing list archive at Nabble.com.
>>
>>
>
>


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux