LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: brad allison <jackal@aol.net>
Cc: Multiple recipients of list <linuxppc-dev@lists.linuxppc.org>,
	yellowdog-general@lists.terrasoftsolutions.com
Subject: Re: What video driver should I use?
Date: 30 Apr 2002 00:37:45 +0200	[thread overview]
Message-ID: <1020119865.9567.2203.camel@tibook> (raw)
In-Reply-To: <Pine.LNX.4.30.0204291754430.2830-100000@horus.office.aol.com>


On Tue, 2002-04-30 at 00:02, brad allison wrote:

> 	(WW) R128: No matching Device section for instance (BusID PCI:0:16:0) found
> 	(EE) No devices detected.

This means you have to put

	BusID		"PCI:0:16:0"

in the device section.


--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-04-29 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29 22:02 What video driver should I use? brad allison
2002-04-29 22:37 ` Michel Dänzer [this message]

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=1020119865.9567.2203.camel@tibook \
    --to=michel@daenzer.net \
    --cc=jackal@aol.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-general@lists.terrasoftsolutions.com \
    /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