From: Dave Airlie <airlied@gmail.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
covici@ccs.covici.com,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10 dies when X tries to initialize PCI radeon 9200 SE
Date: Sun, 16 Jan 2005 22:07:13 +1100 [thread overview]
Message-ID: <21d7e99705011603072d26727a@mail.gmail.com> (raw)
In-Reply-To: <9e4733910501160304642f7882@mail.gmail.com>
> you need to check the output from "modprobe drm debug=1" "modprobe
> radeon" and see if drm is misidentifying the board as AGP. We don't
> want to fix something if it isn't broken.
have a look at bug 255 in fd.o bugzilla, this was what was wrong with
the original code, I'd seriously think about putting this code into
the radeon drm not the old stuff..
Dave.
next prev parent reply other threads:[~2005-01-16 11:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 10:30 2.6.10 dies when X tries to initialize PCI radeon 9200 SE Helge Hafting
2005-01-13 11:00 ` John covici
2005-01-13 21:06 ` Dave Airlie
2005-01-15 18:57 ` Helge Hafting
2005-01-16 10:08 ` Dave Airlie
2005-01-16 10:33 ` Jon Smirl
2005-01-16 10:37 ` Dave Airlie
2005-01-16 10:35 ` Jon Smirl
2005-01-16 10:50 ` Helge Hafting
2005-01-16 11:04 ` Jon Smirl
2005-01-16 11:07 ` Dave Airlie [this message]
2005-01-16 11:34 ` Jon Smirl
2005-01-16 11:41 ` Dave Airlie
2005-01-21 18:26 ` 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result Helge Hafting
2005-01-21 18:49 ` John covici
2005-01-16 12:26 ` 2.6.10 dies when X tries to initialize PCI radeon 9200 SE John covici
2005-01-16 12:18 ` Helge Hafting
2005-01-16 20:25 ` Mike Houston
2005-01-16 22:08 ` Jon Smirl
2005-01-16 22:24 ` Helge Hafting
2005-01-17 17:19 ` Helge Hafting
2005-01-14 2:20 ` David Lang
2005-01-14 10:35 ` Helge Hafting
2005-01-14 12:41 ` John covici
2005-01-15 8:23 ` Dave Airlie
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=21d7e99705011603072d26727a@mail.gmail.com \
--to=airlied@gmail.com \
--cc=covici@ccs.covici.com \
--cc=helgehaf@aitel.hist.no \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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