linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Erick Ween" <jween@som.llu.edu>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
	Olaf Hering <olh@suse.de>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Xfree86-4.0.1, Lombard, Mach64 driver, X-server Crash
Date: Wed, 27 Sep 2000 12:13:12 -0700	[thread overview]
Message-ID: <B5F794D8.631%jween@som.llu.edu> (raw)
In-Reply-To: <Pine.LNX.4.10.10009272015410.27656-100000@opal.biophys.uni-duesseldorf.de>

[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]

Here's a copy of my XF86Config file.

Two other minor nuisances:

Since using yaboot, my console cursor has disappeared. Is this an OF or a
yaboot problem? It's very hard to navigate in vi to edit anything (.config
files for one thing) without a cursor!

Also, I can't figure out how to uninstall BootX. Throwing it away under
MacOS doesn't seem to help.

Any suggestions?

Thanks

Jon

> From: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>
> Date: Wed, 27 Sep 2000 20:17:02 +0200 (CEST)
> To: Olaf Hering <olh@suse.de>
> Cc: Jon Erick Ween <jween@som.llu.edu> , linuxppc-dev@lists.linuxppc.org
> Subject: Re: Xfree86-4.0.1, Lombard, Mach64 driver, X-server Crash
>
>>> OK, I've switched from BootX to Yboot using a stable 2.2.17 kernel and the
>>> most recent XF86-4.0.1 and ati driver sources I can find. I seem to get
>>> different PCI assignments to the ATI chip on boot-up (looking at dmesg
>>> compared with using BootX) but the X-server still doesn't detect the chip
>>> with "startx" or "XFree86" and exits with a "device not found" and "no
>>> screens" error. Any further suggestions?
>>
>> There is a Modes line in the screen section, use a generic mode.
>> Don't specify a Modes section.
>
> It's probably just some error in the device section (the server doesn't
> complain about 'no valid modes found' but 'no device found'.
>
> Need to see your XF86Config's device section.
>
> Michael
>


[-- Attachment #2: XF86Config --]
[-- Type: audio/wav, Size: 1605 bytes --]

  reply	other threads:[~2000-09-27 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-27 17:22 Xfree86-4.0.1, Lombard, Mach64 driver, X-server Crash Jon Erick Ween
2000-09-27 17:42 ` Olaf Hering
2000-09-27 18:17   ` Michael Schmitz
2000-09-27 19:13     ` Jon Erick Ween [this message]
2000-09-27 19:13       ` Michael Schmitz
2000-09-27 19:21       ` Michael Schmitz
2000-09-28 16:51         ` Jon Erick Ween
2000-09-28 18:14           ` Michael Schmitz
2000-09-27 20:35       ` Benjamin Herrenschmidt
2000-09-28  3:50         ` Takashi Oe
2000-09-28 11:08           ` Geert Uytterhoeven
2000-09-28 23:13             ` Takashi Oe
2000-09-29 11:05               ` Geert Uytterhoeven
2000-09-29 16:27                 ` Takashi Oe
2000-10-01 11:30                   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2000-09-28  4:41 Jon Erick Ween
2000-09-28 19:49 Jon Erick Ween

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B5F794D8.631%jween@som.llu.edu \
    --to=jween@som.llu.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).