Dear friends
Would very much appreciate your help with figuring out why my new
Earthlink/Covad/ADSL works in Win98 but not in Linux.
I received my Earthlink self-install kit this afternoon and spent an
hour on the phone with Earthlink tech support installing my new ADSL.
There was a problem at first with having Windows recognize my ADSL. That
is, the ADSL light did not come on. That was quickly solved: When I
removed the splitter and connected the phone line directly to the jack,
the ADSL light came on automatically and all was well. It's a ZyXel ADSL
modem. I was then able to use a better kind of splitter and now I can
run my ADSL on Windows and my telephone on the same line (it's a
line-sharing type of ADSL, not a dedicated line). So, all is well in
Windows.
When I booted up to Linux, Linux could not detect my ADSL. The eth0
refuses to recognize my ADSL. After two minutes I get a big fat red X
and it moves on.
(By the way, Earthlink's ADSL modem is made by a different company than
the one used by Bellsouth or by Juno/Covad)
I installed networking last night in anticipation of my new ADSL. I may
have caused problems in the process. Using DrakConf's Network
installation I found that there are two options for installation, each
involving different ways of setting up dhcp in Linux. One says: pppop
(something like that -- unfortunately, I am in Windows right now) and
another says: non-pppop (really apologize for not writing this down
beforehand). At any rate, when I installed Juno/Covad ADSL two months
ago, I selected the "non-" option and Linux immediately installed the
dhcpd file. When I rebooted, Juno ADSL was immediately recognized. No
problem. This time around, though, I selected the first option and
installed a certain number of files from my 2-CD LM 7.2. I then decided
that perhaps I had made a mistake and went back and selected the second
"non" option. In other words, I now had selected both options. This
time, in addition to the first set of files, I got the dhcpd file. The
main difference I noticed (last night before the installation of
Earthlink/ADSL and now after ADSL) is that upon booting up, Linux took
an extra 30 or more seconds to take me into the console (where I log on
into KDE2. Previously, my last "stop" on the Aurora bootup ladder was
portsentry. It would quickly get a green check mark and go right into my
console. This time, after getting the green check mark for Portsentry,
Linux waits another 30-40 seconds before taking me uneventfully into the
console. I though last night that this might be solved by Linux when it
recognizes my ADSL. I hope that is the case. I mention this only because
I clearly noticed this change in my bootup and thought it might be
related to my choice of both options in DrakConf's Networking/ADSL
installation. What may seem insignificant to me may be important in your
troubleshooting.
I talked to Earthlink's tech support about Linux. They said that I
should have no problem in running their ADSL in Linux. It's just that
they do not support it. Obviously, I had no problem running either
Bellsouth's ADSL or Juno's ADSL and should certainly have no problem
running Earthlink's ADSL (both Juno and Earthlink use Covad). But I have
no idea what the problem is. I tried booting up to Linux with a direct
telephone line to the wall jack, that is, without the splitter. It won't
connect. That is, the ADSL button won't light up on the ADSL modem (the
other three buttons do come on solid green). Could someone please help?
Thanks so much.
Benjamin
--
Sher's Russian Web
http://www.websher.net
Benjamin and Anna Sher
[EMAIL PROTECTED]
