That's great news Sharon. :D
I don't know much about the US phone system - but I would imagine that
sending a fax long distance is similar to making a long distance phone
call - so you simply dial the number of the recipient in the same way
that you would to make a telephone call by hand. If you need to enter
access codes etc, then you would need to put these into the dial string,
possibly with pauses in between. This can't be the first time someone
has tried it. ;-)
BTW the reason my message apparently took 4 days to send is because I
have been travelling, and I could connect to the ISP for that account to
send the email - so it has been sat in my unsent messages folder for a
few days - it's a real pain in the butt - I guess I will just have to
endure their webmail service to send replies.
Best regards,
Robert
Sharon or Dan Donegan wrote:
>
> Omigosh, I'm so excited. My fax is working - at least for local
> numbers. If you know of any special protocol for long distance numbers
> I would appreciate it.
>
> The best thing was that I could Google error messages prefaced by
> Lindmodem and there was tons of info. And I have kept a file of the
> commands and what I did if that is of interest.
>
> Really appreciate that you both helped me so much.
>
> Sharon
>
>
> Robert Thornburrow wrote:
>> Hi Sharon (and Marv),
>>
>> Unfortunately, I am away from home at the moment, so my email
>> access isn't the best, and my Linux dev machine is located at home.
>>
>> The GCC version check is there for a reason, but I can relax this a
>> little in the next version of the driver. If the versions don't match,
>> then I will see if I can get it to check just the major versions and if
>> they do match issue a warning rather than bail out with an error.
>>
>> If Marv's fix works, then we will use that in the interim. I will supply
>> an updated driver when I can, as I have had one other report of this
>> issue. It is an annoying problem as any distro worth its salt normally
>> ships the same exact version of compiler with the distro that they built
>> the kernel with. (Sharon, I see that fix was attached a second email)
>>
>> I'm afraid I don't know much about setting up fax software with Linux,
>> but somewhere at the back of my mind, I seem to remember someone
>> reporting that they had got this working with the PCTel driver, so it
>> is worth persisting.
>>
>> Note that the device used by the driver is normally /dev/ttyS_PCTEL0,
>> but that this should get symlinked to /dev/modem automatically.
>>
>> Best regards,
>>
>> Robert
>>
>> ========================================
>> Message Received: Nov 28 2008, 04:48 PM
>> From: "Marvin Stodolsky"
>> To: "Sharon or Dan Donegan" , "Linmodems"
>> Cc:
>> Subject: Re: Sharon Donegan U.S.A. PCTEL-0.9.7-9-RHT-9
>>
>>
>> Sharon,
>>
>> First rename the old pctel-0.9.7-9-rht-10.tar.gz
>> $ mv pctel-0.9.7-9-rht-10.tar.gz pctel-0.9.7-9-rht-10_old.tar.gz
>> so it won't be confused with the new one I sent.
>> Assuming you have copied the new package to the Desktop:
>> $ cd Desktop
>> unpack the one I sent with the fix to the gcc matching
>> $ tar zxf pctel*.tar.gz
>> Move into the new folder
>> $ cd pctel-0.9.7-9-rht-10
>> Start the compile and install with:
>> $ sudo ./setup
>> The rest of the installation part is automagic.
>>
>> Aptitude is not used.
>> Please send queries to the List, not direct to me as I'm not on line
>> much.
>>
>> MarvS
>>
>>
>> On Fri, Nov 28, 2008 at 10:27 AM, Sharon or Dan Donegan
>> wrote:
>> > Hi Marv and Robert,
>> >
>> > I did what you said (I think) but I already knew that my modem
>> was a
>> > 134d:7897. Is that what I was supposed to get?
>> >
>> > Not sure what the purpose of the change of file to "old"? Is that
>> so we can
>> > work with it without touching the original?
>> >
>> > Also, on doing "gcc", I got this:
>> > sharon@sharon-dan:~/Desktop$ cd pctel-0.9.7-9-rht-10.old
>> > sharon@sharon-dan:~/Desktop/pctel-0.9.7-9-rht-10.old$ gcc
>> > gcc: no input files
>> >
>> > Does this mean I have no "gcc" files or I didn't look in the
>> right place?
>> >
>> > Thanks,
>> >
>> > Sharon
>> >
>> >
>> > Marvin Stodolsky wrote:
>> >
>> > Robert,
>> >
>> > Please check my proposed fix. I'm not erudite with sed
>> >
>> > Sharon,
>> >
>> > Rename your current folder pctel-0.9.7-9-rht-10/ by
>> > $ mv pctel-0.9.7-9-rht-10 pctel-0.9.7-9-rht-10.old
>> > Then try using the attached.
>> >
>> > The pctel.txt is in the Modem/ folder output by scanModem
>> >
>> > MarvS
>> >
>> >
>> >
>> > On Thu, Nov 27, 2008 at 10:23 PM, Marvin Stodolsky
>> > wrote:
>> >
>> >
>> > Robert,
>> >
>> > RE: > installed gcc version 4.2.4 does not match kernel gcc
>> version 4.2.3
>> > Best fix this too severe restriction in the configure script.
>> > Does it not suffice to have a version match at the 4.2 level?
>> >
>> > Marvin
>> >
>> > On Thu, Nov 27, 2008 at 5:57 PM, Sharon or Dan Donegan
>> > wrote:
>> >
>> >
>> > Hi Marv,
>> > I got this far but it seems it wants kernel gcc version...4.2.3.
>> Tried a
>> > search in Synaptic but I don't know the prefix (will try to
>> find it).
>> > Thanks, Sharon
>> >
>> >
>> > sharon@sharon-dan:~/Desktop$ cd pctel-0.9.7-9-rht-10/
>> > sharon@sharon-dan:~/Desktop/pctel-0.9.7-9-rht-10$ ./setup
>> > checking for running kernel version...2.6.24
>> > checking for ptserial...ptserial-2.6.c
>> > checking for gcc...4.2.4
>> > checking for kernel gcc version...4.2.3
>> > ** error
>> > installed gcc version 4.2.4 does not match kernel gcc version
>> 4.2.3
>> > installing the kernel driver module is not possible
>> > installing a different version of gcc, or your kernel, is
>> necessary
>> > ** compilation error
>> > please read the FAQ about reporting compilation problems
>> > and report this problem. A transcript of the build process
>> > has been saved in src/make.log. When reporting problems to
>> > the development team, please send us this file.
>> > sharon@sharon-dan:~/Desktop/pctel-0.9.7-9-rht-10$
>> >
>> >
>> >
>> > Marvin Stodolsky wrote:
>> >
>> > Sharon,
>> >
>> > Nothing will work until you compile and then install the drivers.
>> Follow
>> > At http://linmodems.technion.ac.il/pctel-linux
>> > Get the pctel-0.9.7-9-rht-10.tar.gz
>> > Unpack under Linux with:
>> > tar zxf pctel*.tar.gz
>> > and read instuctions in the new folder unpacked.
>> > Read DOCs/Pctel.txt and Modem/DOCs/YourSystem.txt for follow
>> through
>> > guidance.
>> >
>> > MarvS
>> >
>> > On Thu, Nov 27, 2008 at 3:13 PM, Sharon or Dan Donegan
>> > wrote:
>> >
>> >
>> > Hi Robert,
>> >
>> > Actually I'm not knowledgeable at all. I did try with wvdial
>> and with
>> > eFax-Gtk to dial my cellphone (as though it were a "provider").
>> Had used
>> > this 56K modem when I just had Dial-Up but now have an ethercard
>> with DSL.
>> >
>> > I don't think I have installed PCTEL-0.9.7-9-rht-9 as I can't
>> find it in the
>> > Terminal. Nor can I find PCTEL.
>> >
>> > Also, I just removed "sl-modem-daemon" in Synaptic. From reading
>> other help
>> > chats I thought it wasn't necessary and/or was for 688 something.
>> >
>> > Thank you,
>> >
>> > Sharon
>> >
>> >
>> >
>> > Marvin Stodolsky wrote:
>> >
>> >
>> > On Thu, Nov 27, 2008 at 2:07 PM, Marvin Stodolsky
>> > wrote:
>> >
>> >
>> >
>> > Sharon
>> >
>> > Please verify that you can achieve an ordinary dialout to some
>> > Internet provider, so that it is clear that the drivers are
>> achieving
>> > that functionalty.
>> >
>> > I'll separately send you a package of scripts that are
>> effective for
>> > fax function with Smartlink modem hardware, using port
>> /dev/ttySL0.
>> >
>> > Changing the port designation to that used by your Pctel hardware
>> > should be simple. Beyond that queries should go to some eFax List.
>> >
>> > Maintainer Robert,
>> > Are you knowledeagble of the level of Fax support embedded in the
>> > PCtel code.
>> >
>> > MarvS
>> >
>> > On Thu, Nov 27, 2008 at 10:37 AM, Sharon or Dan Donegan
>> > wrote:
>> >
>> >
>> >
>> > Hello,
>> >
>> > I am using Ubuntu Hardy, am trying to use eFax-Gtk and receive the
>> > message
>> > "No Response from Modem".
>> >
>> > I downloaded
>> >
>>
>> http://linmodems.technion.ac.il/pctel-linux/pctel-0.9.7-9-rht-9.tar.gz ,
>> > Extract Here and tried Run, Display in Terminal but my fax still
>> doesn't
>> > work.
>> >
>> > Have really done tons of stuff over the last few months and not
>> sure
>> > what to
>> > do now.
>> >
>> > Below is the printout from ModemData prior to "installing"
>> > pctel-0.9.7-9-rht-9.tar.gz (if that actually happened by
>> clicking on
>> > "Run).
>> >
>> > Any help you can give would be appreciated. Thank you.
>> >
>> > Sharon
>> >
>> > -------------------------- System information
>> > ----------------------------
>> > CPU=i686, Linux version 2.6.24-21-generic (buildd@palmer) (gcc
>> version
>> > 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Tue Oct 21 23:43:45 UTC 2008
>> > scanModem update of: 2008_11_06
>> > The modem symbolic link is /dev/modem -> ttySL0
>> > There are no blacklisted modem drivers in /etc/modprobe* files
>> Attached
>> > USB
>> > devices are:
>> > ID 1668:6010 Actiontec Electronics, Inc. [hex] ID 04b8:0820 Seiko
>> Epson
>> > Corp. ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0
>> > "TetraHub"
>> > ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
>> >
>> > USB modems not recognized
>> >
>> > For candidate card in slot 01:0a.0, firmware information and
>> bootup
>> > diagnostics are:
>> > PCI slot PCI ID SubsystemID Name
>> > ---------- --------- --------- --------------
>> > 01:0a.0 134d:7897 134d:0001 Modem: PCTel Inc HSP MicroModem
>> > 56
>> > Modem interrupt assignment and sharing: 11: 302206 XT-PIC-XT
>> > uhci_hcd:usb1
>> > --- Bootup diagnostics for card in PCI slot 01:0a.0 ----
>> > [ 24.966284] PCI: Enabling device 0000:01:0a.0 (0000 -> 0001)
>> > [ 24.966913] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [LNKC]
>> -> GSI
>> > 11
>> > (level, low) -> IRQ 11
>> >
>> > === Finished firmware and bootup diagnostics, next deducing cogent
>> > software.
>> > ===
>> >
>> > Predictive diagnostics for card in bus 01:0a.0:
>> > Modem chipset detected on
>> > NAME="Modem: PCTel Inc HSP MicroModem 56 "
>> > CLASS=0703
>> > PCIDEV=134d:7897
>> > SUBSYS=134d:0001
>> > IRQ=11
>> > IDENT=PCTEL
>> >
>> > For candidate modem in: 01:0a.0
>> > 0703 Modem: PCTel Inc HSP MicroModem 56 Primary device ID:
>> > 134d:7897
>> > Support type needed or chipset: PCTEL
>> >
>> >
>> > ----------------end Softmodem section --------------
>> > At http://linmodems.technion.ac.il/pctel-linux
>> > Get the pctel-0.9.7-9-rht-9.tar.gz
>> > Unpack under Linux with:
>> > tar zxf pctel*.tar.gz
>> > and read instuctions therein.
>> > Read DOCs/Pctel.txt and Modem/DOCs/YourSystem.txt for follow
>> through
>> > guidance.
>> >
>> > Writing DOCs/Pctel.txt
>> >
>> > Completed candidate modem analyses.
>> >
>> > The base of the UDEV device file system is: /dev/.udev
>> >
>> > Versions adequately match for the compiler installed: 4.2.3
>> > and the compiler used in kernel assembly: 4.2.4
>> >
>> >
>> >
>> > Minimal compiling resources appear complete:
>> > make utility - /usr/bin/make
>> > Compiler version 4.2
>> > linuc_headers base folder /lib/modules/2.6.24-21-generic/build
>> >
>> > However some compilations and executable functions may need
>> additional
>> > files,
>> > in the FileNames.h (so called kernel "h"eaders) collection
>> installed in
>> > /usr/include/ .
>> > For martian_modem, additional required packages are needed. The
>> also
>> > required headers of package libc6 are commonly installed by
>> default.
>> > Compiling hsfmodem drivers does require linux-libc-dev and
>> libc6-dev
>> > packages, for kernels 2.6.24 and later versions.
>> > In not included on your install CD, search for them at
>> > http://packages.ubuntu.com
>> > or comparable Repository for other Linux distros.
>> > When compiling ALSA drivers, the utility "patch" will also be
>> needed.
>> >
>> >
>> > Compressed files at: /usr/src/sl-modem.tar.bz2
>> >
>> >
>> > If a driver compilation fails, with message including some lack
>> of some
>> > FileName.h (stdio.h for example), then
>> > Some additional kernel-header files need installation to
>> /usr/include.
>> > The
>> > minimal additional packages are libc6-dev
>> > and any of its dependents, under Ubuntu linux-libc-dev
>> >
>> > If an alternate ethernet connection is available,
>> > $ apt-get update
>> > $ apt-get -s install linux-kernel-devel
>> > will install needed packages.
>> > For Debian/Ubuntu related distributions, run the following
>> command to
>> > display the needed package list:
>> >
>> > Otherwise packages have to be found through
>> http://packages.ubuntu.com
>> > Once downloaded and transferred into a Linux partition,
>> > they can be installed alltogether with:
>> > $ sudo dpkg -i *.deb
>> >
>> >
>> > Checking pppd properties:
>> > -rwsr-xr-- 1 root dip 269256 2007-10-04 12:57 /usr/sbin/pppd
>> >
>> > In case of an "error 17" "serial loopback" problem, see:
>> >
>> http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
>> >
>> > To enable dialout without Root permission do:
>> > $ su - root (not for Ubuntu)
>> > sudo chmod a+x /usr/sbin/pppd
>> > or under Ubuntu related Linuxes
>> > sudo chmod a+x /usr/sbin/pppd
>> >
>> > Checking settings of: /etc/ppp/options
>> > asyncmap 0
>> > noauth
>> > crtscts
>> > lock
>> > hide-password
>> > modem
>> > proxyarp
>> > lcp-echo-interval 30
>> > lcp-echo-failure 4
>> > noipx
>> >
>> > In case of a message like:
>> > Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
>> > see
>> http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
>> >
>> > Read Modem/DOCs/YourSystem.txt concerning other COMM channels:
>> eth0
>> > Which can interfere with Browser naviagation.
>> >
>> > Don't worry about the following, it is for experts should trouble
>> > shooting
>> > be necessary.
>> > ==========================================================
>> >
>> > # start/stop the daemon when the USB modem is connected
>> > KERNEL=="slusb[0-9]*", GROUP="dialout",
>> > RUN+="/etc/init.d/sl-modem-daemon"
>> > Checking for modem support lines:
>> > --------------------------------------
>> > /device/modem symbolic link: lrwxrwxrwx 1 root root 6 2008-11-25
>> > 10:00
>> > /dev/modem -> ttySL0
>> > slmodemd created symbolic link /dev/ttySL0: Within /etc/udev/
>> > files:
>> > /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the
>> daemon when
>> > the
>> > USB modem is connected
>> > /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
>> > GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
>> > /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when
>> the USB
>> > modem
>> > is connected
>> > /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
>> GROUP="dialout",
>> > RUN+="/etc/init.d/sl-modem-daemon"
>> > Within /etc/modprobe.conf files:
>> > /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
>> > /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
>> > /etc/modprobe.d/blacklist-modem:# Uncomment these entries in
>> order to
>> > blacklist unwanted modem drivers
>> > /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
>> > /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
>> > /etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe
>> > --ignore-install ungrab-winmodem ; modprobe --ignore-install
>> slamr;
>> > test -e
>> > /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0
>> 2>/dev/null &&
>> > chgrp
>> > dialout /dev/slamr0) Within any ancient /etc/devfs files:
>> >
>> > Within ancient kernel 2.4.n /etc/module.conf files:
>> >
>> > --------- end modem support lines --------
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>
>
>
>
