Screw all that. Use wvdial.
# wvdialconf
edit /etc/wvdial.conf (or something)
# wvdial
If you have a PCI modem, it's likely to be a winmodem. Is it a windmodem?
If so, you need to get the right driver for it.
> I have followed the instructions that are detailed
> below, and also tryed using kppp with no luck. Can
> anyone give me some tips.
>
> On my CMOS setting, I have no way of disabling my
> COM2, but I did try just changing my serial port
> designation in CMOS.
>
> I can see the modem, when I do a cat /proc/pci
>
> Anyway, here are some instructions I found online, but
> haven't had luck with them.
>
> After physically installing your PCI modem enter your
> CMOS setup and disable COM2 (Serial Port Boot into
> Linux and log in as root. Then run:
>
> cat /proc/pci
>
> Look at the output and locate the "bus" entry for your
> modem. You need to locate the IRQ and the base I/O
> address for the modem. Here is an example of the modem
> output:
>
> Non-prefetchable 32 bit memory at 0x00000000.
>
> Bus 0, device 17, function 0:
> Communication controller: Unknown vendor Unknown
> device (rev 0).
> Vendor id=1ac1. Device id=480.
> Medium devsel. Fast back-to-back capable. IRQ 3.
> Master Capable.
> No bursts.
> Min Gnt=252.Max Lat=14
> Non-prefetchable 32 bit memory at 0xe4000000.
> I/O at 0xb800 [0xb801]
> Note in the output above the IRQ is 3 and the base I/O
> is 0xb800. This is common for 56K PCI modem with COM2
> disabled. Now link the modem to COM2 (/dev/ttyS1):
>
> ln -s /dev/ttyS1 /dev/modem
>
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:03:50 EDT