🚀 go-pugleaf

David. E. Goble <goble@gtech> wrote:
> Hi All;

> Iam running RedHat 6.2. Iam trying to follow the how-to to connect to
> the internet.

> My modem is on com3 (/dev/ttyS2), but it seems not to work.

> Here is what I have;

[snip]

> /usr/sbin/pppd /dev/ttyS2 57600 debug user username connect
> "/usr/sbin/chat -v '' AT OK ATDT85534300 CONNECT '\d\c'"


> Jan  6 18:29:15 gtech pppd[798]: pppd 2.3.11 started by root, uid 0
> Jan  6 18:29:16 gtech chat[799]: send (AT^M)
> Jan  6 18:29:16 gtech chat[799]: expect (OK)
> Jan  6 18:29:35 gtech chat[799]: ^M
> Jan  6 18:30:01 gtech chat[799]: alarm

Your serial port may not be set up correctly since pppd is timing out
waiting for an "OK" from your modem.  When you run "cat /proc/interrupts"
do you see the IRQ for your modem?  Do you see your modem when you run 
"cat /proc/ioports"?

Another thing that has bitten me in the past:  Does your modem actually
return "OK" or does it return "Ok" (or possibly "ok")?

[...]

In article <3a56e660.880073@news.adelaide.on.net>,
  goble@gtech wrote:
> Hi All;
>
> Iam running RedHat 6.2. Iam trying to follow the how-to to connect to
> the internet.
>
> My modem is on com3 (/dev/ttyS2), but it seems not to work.
>
> Here is what I have;
>
> >/etc/syslog.conf
> >local2.*                                /var/log/ppp
> >daemon.*                                /var/log/ppp
>
> killall -1 syslogd
>
> >/etc/resolv.conf
> nameserver 127.0.0.1
> nameserver 230.48.5.1
>
> >/etc/host.conf
> order hosts, bind
> >chmod a+r /etc/resolv.conf /etc/host.conf
>
> >/usr/sbin/pppd
> I get a line of garbage which repeats about 10 times and then the
> command exits.
>
> >/etc/ppp/options
> lock
> crtscts
> defaultroute
>
> chmod a+rwx /dev/ttyS2
>
> /usr/sbin/pppd /dev/ttyS2 57600 debug user username connect
> "/usr/sbin/chat -v '' AT OK ATDT85534300 CONNECT '\d\c'"
>
> Jan  6 18:29:15 gtech pppd[798]: pppd 2.3.11 started by root, uid 0
> Jan  6 18:29:16 gtech chat[799]: send (AT^M)
> Jan  6 18:29:16 gtech chat[799]: expect (OK)
> Jan  6 18:29:35 gtech chat[799]: ^M
> Jan  6 18:30:01 gtech chat[799]: alarm
> Jan  6 18:30:01 gtech chat[799]: Failed
> Jan  6 18:30:01 gtech pppd[798]: Connect script failed
> Jan  6 18:30:02 gtech pppd[798]: Exit.
>
>


If you are sure your modem can work with linux then this is a way that
should get your modem initialized.

1) logon as root, and at the command prompt type: cat /proc/pci
2)Scroll down until you find the data for the serial controller. it
will probably look like this
 /*
   Bus 0, device 15, function 0:
      Serial controller: Unknown vendor Unknown device (rev1).
        Vendor id=12b9. Device id=1008
        Medium devsel.  IRQ 10.
        I/O at 0x1890 [0x1891].
 */

3) Make a note of the values for IRQ and I/O port (use the number not
in the brackets). For instance it would be 10 and 0x1890.
4) Then at the command prompt type
setserial /dev/ttyS# irq 10 port 0x1890 autoconfig
# = what ever port you are using
5) Then at the command prompt type ln -s /dev/ttyS# /dev/modem
6) now use minicom - easy to get to from the GUI
  programs->internet->minicom
7) minicom should initialize the modem and will say "OK"
8) next configure your modem and interne settings..make sure to use the
same port ttyS#.
9) if this works, then you want to write steps 4 and 5 in rc.local so
that the modem is initialized automatically everytime you reboot or
else you will need to do this set of steps manually each time.
10) also while in minicom if you type ATI3 you see the type of modem
you have displayed on the screen.

I hope this helps.

Sean


Sent via Deja.com
http://www.deja.com/