Re: Re. Total confusion
On Fri, Jun 01, 2001 at 03:41:35PM -0500, Brian Nelson wrote:
| On Fri, Jun 01, 2001 at 01:15:23PM -0700, Sidney Brooks wrote:
| > More information.
| >
| > I have tried minicom, kppp, gnome -ppp, wvdial, and pppconfig. They all
| > dial and get connected to my ISP. None get me on to the internet.
|
| Sounds like a configuration problem with the dialer. pppd should
| log some stuff, which is accessible with plog. What do they say?
No, his dialers are just fine. He said they dial and get connected to
his ISP. That is the first step. Now you need to figure out how to
make a PPP connection on the line that has just been dialed.
Have you read the PPP-howto?
http://www.linuxdoc.org/HOWTO/PPP-HOWTO/index.html
What I did was use minicom interactively (AFAIK that's the only way to
use it) to determine what to expect from my modem/ISP when I dialed,
and what to send in response. I then wrote a chat script (easy,
really, once you have the info from minicom) and spent a fair amount
of trial-and-error time getting the pppd configuration file to work
with my ISP.
The chat script is in /etc/pppd/providers/. There is a sample one
there you can start with.
If you think it might be helpful, I can send you my chat script and
pppd configuration after I get home.
| > As for my printer problem, I think that the facts that the printer is
| > absent from dmesg and the "echo" test failed, shows that higher programs
| > like magicfilter are not the cure and /etc/printcap doesn't matter.
|
| True.
|
| > It acts like some weird failure in the machine architecture. I am
| > suspicious of the BIOS settings, but can find nothing to change.
|
| Is the parallel port enabled, and does it have an IRQ?
I wouldn't expect the kernel to know that you have a printer or what
it is -- that's a little high-level and not all printers can be
queries. I don't even know of any parallel port printers that can be
queried, except maybe by some proprietary mechanism that only the
manufacturer's (windows) driver can do. It might identifiy an
IEEE-1284 device, however.
-D
Reply to: