On Wed, 1 Jul 1998, Jason Wright wrote:
> Since the Nitro was easily outperforming the 771 for me, I'd like to get it
> working again in the new machine. Any ideas why it might not be working? The
> motherboard is an ASUS PE5NP4 with dual P133's installed.
is it possible one of the chipsets is
On Tue, Jun 30, 1998 at 04:09:27PM -0700, Ian Eure spewed forth:
> > > (--) SVGA: S3 ViRGE chipset: please load "libs3v.a" module
> > > (--) SVGA: CHIPS: chip revision: 6
> > > (--) SVGA: Chipset: ct65530
> > > (--) SVGA: CHIPS: no monitor detected.
> > > (**) SVGA: CHIPS: 4096 kB VRAM
> > > (--)
On Tue, Jun 30, 1998 at 04:09:27PM -0700, Ian Eure spewed forth:
> It looks to me like there might be an onboard c&t adapter on the new
> motherboard, or a second card. Check under /proc/pci and see what devices it
> finds... Look and see if more than one display adapter is getting detected.
> For
On Tue, Jun 30, 1998 at 10:25:16AM -0500, Richard E. Hawkins Esq. wrote:
> > --OgqxwSJOaUobr8KG
> > Content-Type: text/plain; charset=us-ascii
> >
> > Clue required, please. I've never had XF86 give me an error like this one.
> >
> > I just completed transferring my existing hardware to a new
>
On Tue, Jun 30, 1998 at 10:25:16AM -0500, Richard E. Hawkins Esq. spewed forth:
> try "X :1 -bpp 8 -query localhost"
>
> (assuming that you're using xdm. use similar arguments without the query for
> startx)
No xdm here. If I try to start X in 8bpp, I get garbage and have to zap the
server.
> --OgqxwSJOaUobr8KG
> Content-Type: text/plain; charset=us-ascii
>
> Clue required, please. I've never had XF86 give me an error like this one.
>
> I just completed transferring my existing hardware to a new case/motherboard.
> If it matters, I went from a P90 to a dual P133. I moved over the
Sorry to follow up on my own post. I did attach my XF86Config but I either
screwed up, or something ate the second attachment to my previous message.
Here's the config...
PeeWee
# **
# Files section. This allows default font an
7 matches
Mail list logo
