ppp connected, but no IP, DNS, GW

Hello,

I've got RedHat 9 (2.4.20-8 kernel) on a ThinkPad T40.
I am trying to get the modem to work. It is a Wintel modem (Agere),
but Agere and/or IBM provide the driver for it, which I have
installed.

The machine identifies the modem and is able to connect to my ISP,
start pppd, but the connection is only half-made - no DHCP information
is set:
- no IP
- no Gateway
- no name servers

`route -n` and `ifconfig` show only 'lo' interface.

How do I get my IP, name servers, and the gateway to get set?

I have dialed up using these methods:
- ifup ppp0
- wvdialer <my setting name here>
- redhat-config-network (by trying to activate the ppp0 device from
there)

Any help would be veeery muuuuch appreciated!
Thank you.

OtisUsenet <(E-Mail Removed)> wrote:

> I've got RedHat 9 (2.4.20-8 kernel) on a ThinkPad T40.
> I am trying to get the modem to work. It is a Wintel modem (Agere),
> but Agere and/or IBM provide the driver for it, which I have
> installed.

Hmmm. A winmodem. Good luck!

> The machine identifies the modem and is able to connect to my ISP,
> start pppd, but the connection is only half-made - no DHCP information

DHCP is not involved in normal PPP usage, be it a regular landline PPP
connection or a PPPoE connection.

> is set:
> - no IP
> - no Gateway
> - no name servers

> `route -n` and `ifconfig` show only 'lo' interface.

Then the PPP link was never established.

> How do I get my IP, name servers, and the gateway to get set?

We need more information to find why the PPP link wasn't established
and provide answers.

> I have dialed up using these methods:
> - ifup ppp0
> - wvdialer <my setting name here>
> - redhat-config-network (by trying to activate the ppp0 device from
> there)

> Any help would be veeery muuuuch appreciated!
> Thank you.

1) Generate a detailed pppd/<chat or dialing frontend> log file:

echo 'daemon.*;local2.* /var/log/ppp.log' >> /etc/syslog.conf
killall -HUP syslogd
echo debug >> /etc/ppp/options

Run whatever (script, kppp, wvdial, ect.) to start pppd and/or chat.
Configure chat with the -v option for the script. Configure a pppd
dialing frontend (kppp, wvdial, ect.) for maximum verbosity and hope
the messages are sent to ppp.log .

2) Post an exact copy of the messages in ppp.log (not hand-copied).

3) Clean up when done:

rm /var/log/ppp.log
sed '$d' /etc/syslog.conf > foo; mv foo /etc/syslog.conf
killall -HUP syslogd
sed '$d' /etc/ppp/options > foo; mv foo /etc/ppp/options

Remove the chat "-v", or reconfigure the dialing frontend, to stop
verbose logging (which may be sent to other system log files).

Note: All the changes to /etc/syslog.conf and /etc/ppp/options could
also be done by simply using an editor rather than the echo, sed, and
mv utilities. Making file changes by first creating foo as shown above
assumes that root's umask is 022.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Those who can't write, write manuals. */

Hello,

Thank you for the detailed instructions, here is some more
information.

Clifford Kite <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> OtisUsenet <(E-Mail Removed)> wrote:
>
> > I've got RedHat 9 (2.4.20-8 kernel) on a ThinkPad T40.
> > I am trying to get the modem to work. It is a Wintel modem (Agere),
>
> 1) Generate a detailed pppd/<chat or dialing frontend> log file:
>
> echo 'daemon.*;local2.* /var/log/ppp.log' >> /etc/syslog.conf
> killall -HUP syslogd
> echo debug >> /etc/ppp/options
>
> Run whatever (script, kppp, wvdial, ect.) to start pppd and/or chat.
> Configure chat with the -v option for the script. Configure a pppd
> dialing frontend (kppp, wvdial, ect.) for maximum verbosity and hope
> the messages are sent to ppp.log .

If I start the dial up with `wvdial <config name>` I get this in the
console:

[root@localhost modem]# wvdial HTppp
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATM3
ATM3
OK
--> Modem initialized.
--> Sending: ATDT077100000
--> Waiting for carrier.
ATDT077100000
CONNECT 52000 V42bis <===========
CCC HiNet, HT d.d. <===========
User Access Verification
Username:
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sun Apr 11 14:10:56 2004
--> pid of pppd: 5283


Note the lines with '<============'. Those indicate that my modem IS
talking to my ISP, because 'HiNet, HT d.d.' is the name of the ISP,
and I did not enter that name anywhere. This must be coming from the
remote dial-in server.

In /var/log/ppp.log I get only this:

Apr 11 14:10:56 localhost pppd[5283]: pppd 2.4.1 started by root, uid
0

Here are some of the relevant configs from my ifcfg-HTppp file:

BOOTPROTO=dhcp <==== is this wrong? what should I set it to?
ONBOOT=no
CCP=off
PC=off
AC=off
BSDCOMP=off
VJ=off
VJCCOMP=off
LINESPEED=57600
MODEMPORT=/dev/modem
DEMAND=no
DEFROUTE=yes <==== is this wrong? that should set the
routes, no?
PERSIST=no
PAPNAME=samofix


There are no errors in any of the logs.
However, when wvdial connects to the remove dial-in server, there are
also no routes set, no IP for my computer, and no DNS servers.


Then I tried using `ifup-ppp0` and I got this in the ppp.log:

pr 11 14:37:23 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
at 57600
Apr 11 14:37:23 localhost pppd[6155]: pppd 2.4.1 started by root, uid
0
Apr 11 14:37:24 localhost wvdial[6170]: WvDial: Internet dialer
version 1.53
Apr 11 14:37:24 localhost wvdial[6170]: Initializing modem.
Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATZ
Apr 11 14:37:24 localhost wvdial[6170]: ATZ
Apr 11 14:37:24 localhost wvdial[6170]: OK
Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATM3
Apr 11 14:37:24 localhost wvdial[6170]: ATM3
Apr 11 14:37:24 localhost wvdial[6170]: OK
Apr 11 14:37:24 localhost wvdial[6170]: Modem initialized.
Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATDT077600000
Apr 11 14:37:24 localhost wvdial[6170]: Waiting for carrier.
Apr 11 14:37:24 localhost wvdial[6170]: ATDT077600000
Apr 11 14:37:49 localhost wvdial[6170]: CONNECT 52000 V42bis
Apr 11 14:37:49 localhost wvdial[6170]: HiNet, HT d.d. <===
connects?
Apr 11 14:37:49 localhost wvdial[6170]: User Access Verification
Apr 11 14:37:49 localhost wvdial[6170]: Username:
Apr 11 14:37:49 localhost wvdial[6170]: Carrier detected. Chatmode
finished.
Apr 11 14:37:49 localhost pppd[6155]: Serial connection established.
Apr 11 14:37:49 localhost pppd[6155]: Couldn't set tty to PPP
discipline: Invalid argument
Apr 11 14:37:51 localhost pppd[6155]: Exit.


So it looks like the modem connected, and then something blew up and
killed pppd.
In the /var/log/messages.log I saw this:

Apr 11 14:37:23 localhost ifup-ppp: pppd started for ppp0 on
/dev/modem at 57600
Apr 11 14:37:23 localhost pppd[6155]: pppd 2.4.1 started by root, uid
0
Apr 11 14:37:24 localhost wvdial[6170]: WvDial: Internet dialer
version 1.53
Apr 11 14:37:24 localhost wvdial[6170]: Initializing modem.
Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATZ
Apr 11 14:37:24 localhost wvdial[6170]: ATZ
Apr 11 14:37:24 localhost wvdial[6170]: OK
Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATM3
Apr 11 14:37:24 localhost wvdial[6170]: ATM3
Apr 11 14:37:24 localhost wvdial[6170]: OK
Apr 11 14:37:24 localhost wvdial[6170]: Modem initialized.
Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATDT077600000
Apr 11 14:37:24 localhost wvdial[6170]: Waiting for carrier.
Apr 11 14:37:24 localhost wvdial[6170]: ATDT077600000
Apr 11 14:37:49 localhost wvdial[6170]: CONNECT 52000 V42bis
Apr 11 14:37:49 localhost wvdial[6170]: HiNet, HT d.d.
Apr 11 14:37:49 localhost wvdial[6170]: User Access Verification
Apr 11 14:37:49 localhost wvdial[6170]: Username:
Apr 11 14:37:49 localhost wvdial[6170]: Carrier detected. Chatmode
finished.
Apr 11 14:37:49 localhost pppd[6155]: Serial connection established.
Apr 11 14:37:49 localhost kernel: <1>Unable to handle kernel paging
request at virtual address 00210093
Apr 11 14:37:49 localhost kernel: printing eip:
Apr 11 14:37:49 localhost kernel: c012b535
Apr 11 14:37:49 localhost kernel: *pde = 00000000
Apr 11 14:37:49 localhost kernel: Oops: 0002
Apr 11 14:37:49 localhost kernel: ppp_deflate zlib_deflate ppp_generic
slhc nls_iso8859-1 nls_cp437 vfat fat sd_mod sr_mod radeon agrserial
agrmodem autofs e1000 ipt_REJECT iptable_filter ip_t
Apr 11 14:37:49 localhost kernel: CPU: 0
Apr 11 14:37:49 localhost pppd[6155]: Couldn't set tty to PPP
discipline: Invalid argument
Apr 11 14:37:49 localhost kernel: EIP: 0060:[<c012b535>]
Tainted: PF
Apr 11 14:37:49 localhost kernel: EFLAGS: 00010282
Apr 11 14:37:50 localhost kernel:
Apr 11 14:37:50 localhost kernel: EIP is at use_init_fs_context
[kernel] 0x15 (2.4.20-8)
Apr 11 14:37:50 localhost kernel: eax: 00210093 ebx: c012b150 ecx:
d5320110 edx: d5320050
Apr 11 14:37:50 localhost kernel: esi: d5320000 edi: 00000000 ebp:
00000000 esp: d5321f7c
Apr 11 14:37:50 localhost kernel: ds: 0068 es: 0068 ss: 0068
Apr 11 14:37:50 localhost kernel: Process pppd (pid: 6171,
stackpage=d5321000)
Apr 11 14:37:50 localhost kernel: Stack: d5320000 c012b150 d5320000
00000000 c012b150 d5320000 00000000 00000000
Apr 11 14:37:50 localhost kernel: c012b055 00000001 00000001
00000000 c012b150 d6059ee4 c012b1a7 c030c2c0
Apr 11 14:37:50 localhost kernel: d5321fc8 c030c3c0 c012b150
c030c2c0 c025dca2 c025dca5 c02691c4 d6059ee4
Apr 11 14:37:50 localhost kernel: Call Trace: [<c012b150>]
exec_modprobe [kernel] 0x0 (0xd5321f80))
Apr 11 14:37:50 localhost kernel: [<c012b150>] exec_modprobe [kernel]
0x0 (0xd5321f8c))
Apr 11 14:37:50 localhost kernel: [<c012b055>] exec_usermodehelper
[kernel] 0x25 (0xd5321f9c))
Apr 11 14:37:50 localhost kernel: [<c012b150>] exec_modprobe [kernel]
0x0 (0xd5321fac))
Apr 11 14:37:50 localhost kernel: [<c012b1a7>] exec_modprobe [kernel]
0x57 (0xd5321fb4))
Apr 11 14:37:50 localhost kernel: [<c012b150>] exec_modprobe [kernel]
0x0 (0xd5321fc4))
Apr 11 14:37:50 localhost kernel: [<c012b150>] exec_modprobe [kernel]
0x0 (0xd5321fe8))
Apr 11 14:37:50 localhost kernel: [<c010742d>] kernel_thread_helper
[kernel] 0x5 (0xd5321ff0))
Apr 11 14:37:50 localhost kernel:
Apr 11 14:37:50 localhost kernel:
Apr 11 14:37:50 localhost kernel: Code: ff 00 ba 00 e0 ff ff 21 e2 8b
b2 48 06 00 00 89 82 48 06 00
Apr 11 14:37:51 localhost pppd[6155]: Exit.


This also shows that the modem first connected, and then something in
pppd and/or kernel blew up. I see that the ppp-related kernel modules
are mentioned.

These are the modules that I loaded with modprobe ppp_generic.o (I
think that is the module I loaded, but I'm not 100% certain now..
maybe it was ppp_deflate):

ppp_deflate 4504 0 (unused)
zlib_deflate 21368 0 [ppp_deflate]
ppp_generic 24444 0 [ppp_deflate]
slhc 6740 0 [ppp_generic]

Am I missing a module that is required for ppp to work?


Any help would be very much appreciated.

Thank you.

OtisUsenet <(E-Mail Removed)> wrote:
> Hello,

> Thank you for the detailed instructions, here is some more
> information.

> Clifford Kite <(E-Mail Removed)> wrote in message
> news:<(E-Mail Removed)>...
>> OtisUsenet <(E-Mail Removed)> wrote:
>>
>> > I've got RedHat 9 (2.4.20-8 kernel) on a ThinkPad T40.
>> > I am trying to get the modem to work. It is a Wintel modem (Agere),
>>
>> 1) Generate a detailed pppd/<chat or dialing frontend> log file:
>>
>> echo 'daemon.*;local2.* /var/log/ppp.log' >> /etc/syslog.conf
>> killall -HUP syslogd
>> echo debug >> /etc/ppp/options
>>
>> Run whatever (script, kppp, wvdial, ect.) to start pppd and/or chat.
>> Configure chat with the -v option for the script. Configure a pppd
>> dialing frontend (kppp, wvdial, ect.) for maximum verbosity and hope
>> the messages are sent to ppp.log .

> If I start the dial up with `wvdial <config name>` I get this in the
> console:

> [root@localhost modem]# wvdial HTppp
> --> WvDial: Internet dialer version 1.53
> --> Initializing modem.
> --> Sending: ATZ
> ATZ
> OK

ATZ is an iffy way of initializing a (real) modem. Usually ATZ&F
is better.

> --> Sending: ATM3
> ATM3
> OK

If this M3 is the same as described in my old modem manual then it turns
off the modem's speaker unless a call is being answered. Is that what
you want? Here M0 turns off the speaker altogether, M1 turns it on only
during negotiation by a call out, and M2 turns on the speaker only while
answering.

> --> Modem initialized.
> --> Sending: ATDT077100000
> --> Waiting for carrier.
> ATDT077100000
> CONNECT 52000 V42bis <===========
> CCC HiNet, HT d.d. <===========
> User Access Verification
> Username:
> --> Carrier detected. Starting PPP immediately.
> --> Starting pppd at Sun Apr 11 14:10:56 2004
> --> pid of pppd: 5283


> Note the lines with '<============'. Those indicate that my modem IS
> talking to my ISP, because 'HiNet, HT d.d.' is the name of the ISP,
> and I did not enter that name anywhere. This must be coming from the
> remote dial-in server.

Correct. And a connect speed of 52000 is great (assuming the winmodem
reports the connect speed correctly)!

> In /var/log/ppp.log I get only this:

> Apr 11 14:10:56 localhost pppd[5283]: pppd 2.4.1 started by root, uid
> 0

There should be a lot more unless pppd died immediately.

> Here are some of the relevant configs from my ifcfg-HTppp file:

> BOOTPROTO=dhcp <==== is this wrong? what should I set it to?

It is probably wrong unless you need DHCP for something other than
the PPP connection; PPP doesn't use DHCP.

> ONBOOT=no
> CCP=off
> PC=off
> AC=off
> BSDCOMP=off
> VJ=off
> VJCCOMP=off
> LINESPEED=57600

If this means what I think then 115200 would be better (at least with
a real modem).

> MODEMPORT=/dev/modem
> DEMAND=no
> DEFROUTE=yes <==== is this wrong? that should set the

If it means what I think it does then it's correct.

> routes, no?
> PERSIST=no
> PAPNAME=samofix

> There are no errors in any of the logs.
> However, when wvdial connects to the remove dial-in server, there are
> also no routes set, no IP for my computer, and no DNS servers.

So PPP didn't come up for IP.

> Then I tried using `ifup-ppp0` and I got this in the ppp.log:

> pr 11 14:37:23 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
> at 57600
> Apr 11 14:37:23 localhost pppd[6155]: pppd 2.4.1 started by root, uid
> 0
> Apr 11 14:37:24 localhost wvdial[6170]: WvDial: Internet dialer
> version 1.53
> Apr 11 14:37:24 localhost wvdial[6170]: Initializing modem.
> Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATZ
> Apr 11 14:37:24 localhost wvdial[6170]: ATZ
> Apr 11 14:37:24 localhost wvdial[6170]: OK
> Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATM3
> Apr 11 14:37:24 localhost wvdial[6170]: ATM3
> Apr 11 14:37:24 localhost wvdial[6170]: OK
> Apr 11 14:37:24 localhost wvdial[6170]: Modem initialized.
> Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATDT077600000
> Apr 11 14:37:24 localhost wvdial[6170]: Waiting for carrier.
> Apr 11 14:37:24 localhost wvdial[6170]: ATDT077600000
> Apr 11 14:37:49 localhost wvdial[6170]: CONNECT 52000 V42bis
> Apr 11 14:37:49 localhost wvdial[6170]: HiNet, HT d.d. <===
> connects?
> Apr 11 14:37:49 localhost wvdial[6170]: User Access Verification
> Apr 11 14:37:49 localhost wvdial[6170]: Username:
> Apr 11 14:37:49 localhost wvdial[6170]: Carrier detected. Chatmode
> finished.

> Apr 11 14:37:49 localhost pppd[6155]: Serial connection established.
> Apr 11 14:37:49 localhost pppd[6155]: Couldn't set tty to PPP
> discipline: Invalid argument
> Apr 11 14:37:51 localhost pppd[6155]: Exit.

So pppd did die (almost) immediately.

> So it looks like the modem connected, and then something blew up and
> killed pppd.

Correct. Pppd couldn't set some attribute of the modem's device file
(the "tty") to the PPP line discipline, so it exited.

> In the /var/log/messages.log I saw this:

> Apr 11 14:37:23 localhost ifup-ppp: pppd started for ppp0 on
> /dev/modem at 57600
> Apr 11 14:37:23 localhost pppd[6155]: pppd 2.4.1 started by root, uid
> 0
> Apr 11 14:37:24 localhost wvdial[6170]: WvDial: Internet dialer
> version 1.53
> Apr 11 14:37:24 localhost wvdial[6170]: Initializing modem.
> Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATZ
> Apr 11 14:37:24 localhost wvdial[6170]: ATZ
> Apr 11 14:37:24 localhost wvdial[6170]: OK
> Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATM3
> Apr 11 14:37:24 localhost wvdial[6170]: ATM3
> Apr 11 14:37:24 localhost wvdial[6170]: OK
> Apr 11 14:37:24 localhost wvdial[6170]: Modem initialized.
> Apr 11 14:37:24 localhost wvdial[6170]: Sending: ATDT077600000
> Apr 11 14:37:24 localhost wvdial[6170]: Waiting for carrier.
> Apr 11 14:37:24 localhost wvdial[6170]: ATDT077600000
> Apr 11 14:37:49 localhost wvdial[6170]: CONNECT 52000 V42bis
> Apr 11 14:37:49 localhost wvdial[6170]: HiNet, HT d.d.
> Apr 11 14:37:49 localhost wvdial[6170]: User Access Verification
> Apr 11 14:37:49 localhost wvdial[6170]: Username:
> Apr 11 14:37:49 localhost wvdial[6170]: Carrier detected. Chatmode
> finished.
> Apr 11 14:37:49 localhost pppd[6155]: Serial connection established.
> Apr 11 14:37:49 localhost kernel: <1>Unable to handle kernel paging
> request at virtual address 00210093
> Apr 11 14:37:49 localhost kernel: printing eip:
> Apr 11 14:37:49 localhost kernel: c012b535
> Apr 11 14:37:49 localhost kernel: *pde = 00000000
> Apr 11 14:37:49 localhost kernel: Oops: 0002
> Apr 11 14:37:49 localhost kernel: ppp_deflate zlib_deflate ppp_generic
> slhc nls_iso8859-1 nls_cp437 vfat fat sd_mod sr_mod radeon agrserial
> agrmodem autofs e1000 ipt_REJECT iptable_filter ip_t
> Apr 11 14:37:49 localhost kernel: CPU: 0
> Apr 11 14:37:49 localhost pppd[6155]: Couldn't set tty to PPP
> discipline: Invalid argument

<snip>
(I couldn't make much out of the remaining kernel Oops messages.]

> Apr 11 14:37:51 localhost pppd[6155]: Exit.

Same song, second verse.

> This also shows that the modem first connected, and then something in
> pppd and/or kernel blew up. I see that the ppp-related kernel modules
> are mentioned.

Correct. You almost certainly don't need ppp_deflate or zlib_deflate
unless the peer is a *nix host, and even then it's not likely they would
be needed for an ISP connection.

> These are the modules that I loaded with modprobe ppp_generic.o (I
> think that is the module I loaded, but I'm not 100% certain now..
> maybe it was ppp_deflate):

> ppp_deflate 4504 0 (unused)
> zlib_deflate 21368 0 [ppp_deflate]
> ppp_generic 24444 0 [ppp_deflate]
> slhc 6740 0 [ppp_generic]

> Am I missing a module that is required for ppp to work?

Yes, there should be a ppp_async, unless that's compiled directly into
the kernel. I believe there is a very high probability that it's absence
is causing the problem.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* 97.3% of all statistics are made up. */

Clifford Kite <(E-Mail Removed)> writes:


]ATZ is an iffy way of initializing a (real) modem. Usually ATZ&F
]is better.

I agree that ATZ is not good, and that your suggestion will work.
However the &F will cancel out anything the Z does. &F is factory
defaults ( and use &F1 for Sportster modems as &F uses software flow
control.)
Thus AT&F would be "better" in the sense of being a shorter
sentence to accomplish the same thing.
The reason ATz is iffy is because ATZ sets the modem to whatever
attributes it had when some unknown person or program issued a save
settings command-- Ie you have no idea what atz sets the modem to.

Of course what a winmodem does with either of these is pretty uncertain.

Bill Unruh <(E-Mail Removed)> wrote:
> Clifford Kite <(E-Mail Removed)> writes:

> ]ATZ is an iffy way of initializing a (real) modem. Usually ATZ&F
> ]is better.

> I agree that ATZ is not good, and that your suggestion will work.
> However the &F will cancel out anything the Z does. &F is factory
> defaults ( and use &F1 for Sportster modems as &F uses software flow
> control.)

AIUI, it won't quite cancel all ATZ does. In addition to setting a
preset user (which for some modems is not user settable) profile,
it's supposed to "clear the serial port buffers."

> Thus AT&F would be "better" in the sense of being a shorter
> sentence to accomplish the same thing.
> The reason ATz is iffy is because ATZ sets the modem to whatever
> attributes it had when some unknown person or program issued a save
> settings command-- Ie you have no idea what atz sets the modem to.

> Of course what a winmodem does with either of these is pretty uncertain.

Indeed so.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* ... packets usually cross many administrative boundaries on their way
from a source to a destination and often the only point of agreement
between those separate administrations is that all problems are someone
else's fault. --Van Jacobson, abstract of April 97 MSRI talk */

I actually have installed the smartlink modem drivers for my T41 and
it is working great. I tested it with KPPP. You can get the drivers
here:

ftp://ftp.smlink.com/linux/unsupported/

My installation and modem usage can be found here:

http://www.rit.edu/~sak5991/modem.html

x86



SuSE Linux 9.0-Intel Pentium M 1.40GHz-512 MB-40
GB-14"-1024x768-4.5-4.9 lbs-CD-RW/DVD-ROM-Intel PRO/1000 Gigabit
Ethernet-Intel PRO/Wireless Network Connection 802.11b

----------------------------------------
The post originated from Linux Forum:
----------------------------------------
http://www.linuxforum.com
http://www.linuxforum.com/forums