On Tue, 20 Mar 2001, David Irvine wrote:
> X says it hates me!
You know nothing! Try running X on an Alpha 164LX. THAT's the definition
of X (and samba and kernel SCSI subsystem and ...) hating you :^(
(I'm not bitter)
[snipity snip]
> when i Startx it complains that theres no valid modes.
With the proviso that I don't know XFDrake, this sounds like you've not
setup your monitor definition correctly, ie its Horiz. and Vert. refresh
ranges. Either:
1. 1280x1024 @ 72hz doesn't exist in your mode list
2. X _thinks_ your monitor can't do the mode
3. Your monitor really can't do that resolution at 72Hz
4. X doesn't think your gfx card can do that mode (unlikely).
5. Your graphics card really can't do that mode (very unlikely).
> I tried every
> combination of res XFDrake has and still no joy! Its using the SVGA server,
> there doesnt appear to be one for the matrox g100.
>
> Any ideas?
Try v4.0 (something like "rm /etc/X11/X; ln -s /usr/X11R6/bin/XFree86 X"
should to do it). It does more intelligent things with monitor modes. You
still have to tell it what your monitor can do or use the monitor
plug-n-play option (the name of which escapes me at the moment).
> Next problem is pppd
>
> I'm running it on a slackware box.
>
> It dials, it connects but fails to authenticate.
How do you know it fails to authenticate? AFAIK, the other end normally
drops the line if authentication fails. Also, if you tell pppd not to
authenticate itself, and the remote end is expecting authentication, then
the remote end will drop the line. BTW, are you using chat to do the
dialing?
> The interface never appears under ifconfig,
Curiouser and curiouser. You have got ppp support compiled into the
kernel? (Covering the "doh!"s)
> but it stays connected. From time to time when i Ctrl-c or
> kill the connection i get an error saying the line is not 8 bit clean, the
> modem is a usr sportster v90 which i can use to connect under M$ winblows!
Try turning the debugging on (tag a "debug" onto the command line). You
might need to set up another syslog entry to catch the extra information
as /var/log/messages only captures messages at info level (and above). Add
a line like:
daemon.debug /var/log/pppd
^---^----tabs here -^-------^-------^
and "killall -hup syslogd" (I think pppd logs as daemon, but I could be
wrong)
You may find that your entry in /etc/pppd/papsecrets isn't quite
right, or that pppd is using an incorrect username or remote username.
HTH
Cheers,
Paul.
------------------------------------------------------------------------------
Paul Millar yo-yo, n. :
Particle Physics Theory Group Something that is occasionally
Department of Physics and Astronomy up but normally down.
University of Glasgow, (see also Computer)
Glasgow G12 8QQ, [EMAIL PROTECTED]
Scotland +44 (0)141 330 4717
------------------------------------------------------------------------------
--------------------------------------------------------------------
http://www.lug.org.uk http://www.linuxportal.co.uk
http://www.linuxjob.co.uk http://www.linuxshop.co.uk
--------------------------------------------------------------------
