winmodem pctel 789t c1 mit linux

Hallo linux-community,

i'm a newbie and one of the crazy people which try to install
an intern winmodem (pctel 789T-C1) in a linux-system.

I have red the Howto www.peacefulaction.org/sayamindu/pctel.pdf.
(System: knoppix 3.3 mit Kernel 2.4.24; Treiber: pctel-0.9.7-9.tar.gz)

I'm was able to go through each step without any success.

My question : I type in the command lspci at the Shell and can't see any device
like HSP ... . Does that mean the modem doesn't exist or is damaged?
Is it a requirement for any further step, that lspci print an entry
concerning to HSP Modem?

root@tarantoga:/tmp/modem/pctel-0.9.7-9# lspci
00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 02)
00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02)
00:09.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 40)
root@tarantoga:

That's all.

Thank you for any kind of support

Steffen

["Followup-To:" header set to comp.os.linux.help.]
On 6 Aug 2004 02:39:08 -0700, popeffen
<sweber@ibseteq.de> wrote:
> Hallo linux-community,
>
> i'm a newbie and one of the crazy people which try to install
> an intern winmodem (pctel 789T-C1) in a linux-system.
>
> I have red the Howto www.peacefulaction.org/sayamindu/pctel.pdf.
> (System: knoppix 3.3 mit Kernel 2.4.24; Treiber: pctel-0.9.7-9.tar.gz)
>
> I'm was able to go through each step without any success.
>
> My question : I type in the command lspci at the Shell and can't see any device
> like HSP ... . Does that mean the modem doesn't exist or is damaged?
> Is it a requirement for any further step, that lspci print an entry
> concerning to HSP Modem?
>
> root@tarantoga:/tmp/modem/pctel-0.9.7-9# lspci
> 00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 02)
> 00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
> 00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02)
> 00:09.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 40)
> root@tarantoga:
>
If the modem is a PCI device, it should show something in lspci. Try
putting it in another slot.


--
The truth you speak has no past and no future. It is, and that's all it
needs to be.

Bill Marcum <bmarcum@iglou.com.urgent> wrote in message news:<66hcu1-91v.ln1@don.localnet>...
> ["Followup-To:" header set to comp.os.linux.help.]
> On 6 Aug 2004 02:39:08 -0700, popeffen
> <sweber@ibseteq.de> wrote:
> > Hallo linux-community,
> >
> > i'm a newbie and one of the crazy people which try to install
> > an intern winmodem (pctel 789T-C1) in a linux-system.
> >
> > I have red the Howto www.peacefulaction.org/sayamindu/pctel.pdf.
> > (System: knoppix 3.3 mit Kernel 2.4.24; Treiber: pctel-0.9.7-9.tar.gz)
> >
> > I'm was able to go through each step without any success.
> >
> > My question : I type in the command lspci at the Shell and can't see any device
> > like HSP ... . Does that mean the modem doesn't exist or is damaged?
> > Is it a requirement for any further step, that lspci print an entry
> > concerning to HSP Modem?
> >



> > root@tarantoga:/tmp/modem/pctel-0.9.7-9# lspci
> > 00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 02)
> > 00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
> > 00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02)
> > 00:09.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 40)
> > root@tarantoga:
> >
> If the modem is a PCI device, it should show something in lspci. Try
> putting it in another slot.


Yes, thank you very much - it works!

popeffen wrote:
> Hallo linux-community,
>
> i'm a newbie and one of the crazy people which try to install
> an intern winmodem (pctel 789T-C1) in a linux-system.
>
> I have red the Howto www.peacefulaction.org/sayamindu/pctel.pdf.
> (System: knoppix 3.3 mit Kernel 2.4.24; Treiber: pctel-0.9.7-9.tar.gz)
>
> I'm was able to go through each step without any success.
>
> My question : I type in the command lspci at the Shell and can't see any device
> like HSP ... . Does that mean the modem doesn't exist or is damaged?
> Is it a requirement for any further step, that lspci print an entry
> concerning to HSP Modem?
>
> root@tarantoga:/tmp/modem/pctel-0.9.7-9# lspci
> 00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 02)
> 00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
> 00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02)
> 00:09.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 40)
> root@tarantoga:
>
> That's all.
>
> Thank you for any kind of support
>
> Steffen

Hello,
Some internal winmodems can be made to work with Linux, but mostly not.
This is because they lack their own controller chip, and depend on MS
proprietary software to work. Most external modems have this chip, and
can be made to work.

Here is a procedure that I have successfully used in the past with
internal modems. I wrote it for Mandrake, so it is only meant to be a
guide. You will need to make neccessary path adjustments for your
particular distribution.



#Installing an internal serial modem under Mandrake Linux

# This file was written to setup the Archtek Telecom Smartlink
# 5634PCV Internal Modem for Mandrake Linux versions 9.0 through
# 10.0 inclusively.

# I believe that it is generic enough to help with setting up any
# internal modem that has it's own controller chip.

###########################################
# Michael Hearne <mhearne@springma*l.com> #
# Registered Linux User #352695 #
# All work licensed under the GPL #
###########################################

# Please improve my work. Change springma*l to springmail to send
# praises, flames and blames. I check it once a month.


1. From the installation disks, install setserial and kppp.

2. Determine your modem type, IRQ number and I/O address with the
following command:

cat /proc/pri

This lists all of your pci devices. In my case, this is:

Bus 0, device 9, function 0:
Communication controller: TOPIC SEMICONDUCTOR Corp TP560 Data/Fax/Voice 56k
modem (rev 0).
IRQ 5.
I/O at 0xd800 [0xd807].

Now I know that I am going to use ttyS2, that my IRQ is 5 and my
I/O address is 0xd800. Write those numbers down, you'll need them
in a moment.

3. Open a console and become superuser:

su
password: <your root password goes here>

4. cd to /dev and check your serial devices.

cd /dev
ls -l ttyS*
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS0 -> tts/0
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS1 -> tts/1
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS2 -> tts/2
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS3 -> tts/3
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS4 -> tts/4
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS5 -> tts/5
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS6 -> tts/6
lr-xr-xr-x 1 root root 5 Aug 7 06:04 ttyS7 -> tts/7

5. Depending on your modem, you are probably going to use ttyS2
(com2) or ttyS4 (com5). In my case, under Mandrake-10, the device
already exits. For any version of Mandrake 9, you will have to
create it. To do this you will need to know the major and minor
numbers for the serial ports.

Here is the list, from the Serial HOWTO:

/dev/ttyS0 major 4, minor 64 (dos com1)
/dev/ttyS1 major 4, minor 65 (dos com2)
/dev/ttyS2 major 4, minor 66 (dos com3)
/dev/ttyS3 major 4, minor 67 (dos com4)
/dev/ttyS4 major 4, minor 68 (dos com5)

6. If you're using Mandrake-10, don't do this. Serial devices are
setup differently under Mandrake-10. If you are using any version
of Mandrake 9, create the new device:

#COM2
mknod -m 666 /dev/cua2 c 5 66
mknod -m 666 /dev/ttyS2 c 4 66

#COM5
mknod -m 666 /dev/cua4 c 5 68
mknod -m 666 /dev/ttyS4 c 4 68

7. Enable the new serial device and create a link to /dev/modem
with the command:

# Here's where you need the numbers you wrote down before.

setserial /dev/ttyS2 uart 16550A irq 5 port 0xd800
ln -s /dev/ttyS2 /dev/modem # This creates /dev/modem

8. Now cd to the /etc/rc.d directory, and create rc.serial:
(Remember that your irq and port numbers will be different from mine)

cd /etc/rc.d # Change to /etc/rc.d
vi rc.serial # Create rc.serial with vi

#!/bin/sh # This is the shebang, don't leave it out
# rc.serial # This is file to execute
#
rm -f /dev/modem
setserial /dev/ttyS2 uart 16550A irq 5 port 0xd800
ln -s /dev/ttyS2 /dev/modem
echo "Modem Ready"

:wq # Type :wq to save the file and quit vi

9. Make rc.serial executable with:

chmod 755 rc.serial

10. Make a link from /etc/rc.d/rc.serial to /etc/rc.serial:

cd /etc
ln -s /rc.d/rc.serial

Reboot and start KPPP (Kicker > Internet > Remote Access > KPPP)
Click on 'Configure' and enter your ISP's information and dial.

Depending on your version of Linux, rc.serial may not have executed on
boot. If not, you should add the following as the last line of
/etc/rc.d/rc.local:

/bin/sh /etc/rc.serial

This is not needed by Mandrake-10. You may start the modem without
rebooting with the command:

/etc/rc.serial (./rc.serial)

HTH

Michael

--
Registered Linux User #352695