Re: Sharon Donegan U.S.A. PCTEL-9.7-9-RHT-10

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

 



Sharon,

Don't take what follows too seriously because I have NOT read the whole thread, short of time, just Robert's answer.
I guess you do not have a true modem, (i.e. not a winmodem) on port COM1
(= /dev/ttyS0) in your computer.

So please look at the output of command   ls -l /dev/modem
If by chance it shows /dev/ttyS0 for sure, or perhaps nothing
at all, just give
ln -s /dev/ttyS_PCTEL0 /dev/modem
You can enforce such a work around blindly by typing
ln -sf /dev/ttyS_PCTEL0 /dev/modem
but do not try it before having reported the sitation to us, or at least carefully made a record of the answer to ls -l /dev/modem before making any change.


Jacques


Robert Thornburrow wrote:
Hi Sharon,

I can see the problem: the fax software is looking on /dev/ttyS0 (the
first serial port) for the modem, but it is on /dev/ttyS_PCTEL0.
I am not sure where you need to change this setting, but it should
be in one of the Efax config files somewhere.

Best regards,

    Robert

Sharon or Dan Donegan wrote:
Not sure I'm sending this out correctly so I'm trying again.

I'm using Hardy and am still unable to fax.  This is what I get from
Efax-Gtk:

From Efax:

Socket running on port 9900

efax-0:9a: 7:46:08 Efax opened dev/ttyS0

efax-0:9a: 7:46:08 sync: dropping DTR

efax-0:9a: 7:46:08 sync: sending escapes

Error: sync: modem not responding

failed page /home/sharon/stuff.ps

finished no response from modem

-------------------------- System information ----------------------------

CPU=i686,

Linux version 2.6.24-22-generic (buildd@vernadsky) (gcc version 4.2.3
(Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon Nov 24 18:32:42 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: 201801 XT-PIC-XT uhci_hcd:usb1

--- Bootup diagnostics for card in PCI slot 01:0a.0 ----

[ 25.559482] PCI: Enabling device 0000:01:0a.0 (0000 -> 0001)

[ 25.560109] 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-22-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-12-01 07:33
/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 --------








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

  Powered by Linux