On Sun, Jan 16, 2005 at 05:08:12PM -0500, Jon Smirl wrote:
> On Sun, 16 Jan 2005 13:18:23 +0100, Helge Hafting
> <[EMAIL PROTECTED]> wrote:
> > On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
> > > you need to check the output from "modprobe drm debug=1" "modprobe
> > > radeon" and see i
On Sun, Jan 16, 2005 at 05:08:12PM -0500, Jon Smirl wrote:
> On Sun, 16 Jan 2005 13:18:23 +0100, Helge Hafting
> <[EMAIL PROTECTED]> wrote:
> > On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
> > > you need to check the output from "modprobe drm debug=1" "modprobe
> > > radeon" and see i
On Sun, 16 Jan 2005 13:18:23 +0100, Helge Hafting
<[EMAIL PROTECTED]> wrote:
> On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
> > 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 so
On Sun, 16 Jan 2005 13:18:23 +0100
Helge Hafting <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
> > 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 so
OK, I don't have a module called drm except a .a file in the library
directory for X -- I have some radeon stuff but modprobe radeon
debug=1 says invalid parameter and loads the module. Am I missing
something?
Thanks.
on Sunday 01/16/2005 Jon Smirl([EMAIL PROTECTED]) wrote
> On Sun, 16 Jan 2005
On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
> 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.
>
Stupid question - how do I get a modular drm?
I usuall
>
> I'm fine with adding this code, but we still don't know if this is the
> cause of his problem. The debug output can determine if this really is
> the source of the problem or if it is somewhere else.
>
I actually doubt it is this stuff.. my guess is that it is something
nasty like ACPI break
On Sun, 16 Jan 2005 22:07:13 +1100, Dave Airlie <[EMAIL PROTECTED]> wrote:
> > 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 f
> 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
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.
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Sun, Jan 16, 2005 at 09:08:38PM +1100, Dave Airlie wrote:
> Well the problem with a lot of ATI chips is they can be put onto
> either an AGP or PCI card and work fine, so chips which are AGP chips
> can end up on PCI cards...
>
X uses chip ID to guess wether it is an AGP or PCI card? Ouch.
Do
>
> /* There are signatures in BIOS and PCI-SSID for a PCI card,
> but they are not very reliable.
> Following detection method works for all cards tested so far.
> Note, checking AGP_ENABLE bit after drmAgpEnable call can also
> give the correct result.
> However,
Be sure and run with "modprobe drm debug=1" and check the debug
output. If it is broken the debug output will say the card is AGP. The
message from the X server does not mean anything for DRM, you need to
check the debug output from DRM.
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this l
I use PCI Rage128 cards which are working fine.
I suspect it is this code from radeon_drv.c. There is probably
something wrong with card's BIOS or whatever and it is saying that it
is an AGP card when it is really a PCI one. We used to specify this
manually in xconfig but now DRM code does it au
> Some more data:
> 2.6.10 with agp and drm (drm for radeon & matrox) - dies with X on radeon
> 2.6.10 with drm (for radeon) no agp - runs X fine!
> 2.6.10 with agp and no drm at all - dies with X on radeon
> 2.6.10 no agp no drm - runs X,
On Fri, Jan 14, 2005 at 08:06:09AM +1100, Dave Airlie wrote:
> > on Thursday 01/13/2005 Helge Hafting([EMAIL PROTECTED]) wrote
> > > 2.6.10 boots fine, but is killed by the X server when it
> > > tries to initialize my PCI radeon 9200 SE. This problem exists
> > > in 2.6.9 too, but not in 2.6.8
> I have an apg card and it happens on that one as well. How can I turn
> off drm -- just not load the dri module?
>
don't load the drm kernel module or make sure CONFIG_DRM is set to n..
Dave.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
17 matches
Mail list logo
