public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Cyrus <cyjamten@ihug.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go...
Date: 08 Nov 2001 12:14:52 -0500	[thread overview]
Message-ID: <1005239692.939.34.camel@phantasy> (raw)
In-Reply-To: <3BEA7525.7070807@ihug.com.au>
In-Reply-To: <20011108113615.F27652@suse.de> <Pine.LNX.4.33.0111081322570.8555-100000@localhost.localdomain> <20011108123808.I27652@suse.de>  <3BEA7525.7070807@ihug.com.au>

On Thu, 2001-11-08 at 07:05, Cyrus wrote:
> i've been having problems with starting my xserver all the time... my 
> monitor tells me that i have no connection at all after starting X... 
> complete system failure... no sysrq keys and stuff.. this is my fifth to 
> seventh install of slackware 8 in approximately 3 weeks... errors in 
> filesystems and reiserfs couldn't handle the crashing anymore and tells 
> me i couldn't mount my root filesystem (superblock errors, etc.)...
> 
> anyway, i'm just curious if this is about the radeon drivers or the amd 
> 761 agpgart that Robert Love had made.. with all due respect to Robert 
> he did a good job... my amd chipset wasn't even recognized before this 
> patch-turned main stream kernel supported hardware...(but is it really 
> supported?). my friend is also experiencing the same problems and he has 
> the amd 751 chipset and the radeon combo as well... i've tried quite a 
> lot of things just to make my machine perform like a real linux box 
> should be but to no avail... X keeps me down as in crashes 7 out of 8 
> times i start X... i've read and researched on this issue for months and 
> i'm still one of the guys who hasn't found the answer...

I doubt its the AMD 761 AGPGART driver.  It is easy to see if it is:
don't load the AMD 761 driver.  I think the DRI component of the ATI
driver is all that uses AGPGART, so unload that too.

Thus, see if just the Radeon with no DRI and no AGPGART is a problem.

	Robert Love


  reply	other threads:[~2001-11-08 17:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07  4:11 disaster with 2.4.14+preempt J Sloan
2001-11-07  5:07 ` Robert Love
2001-11-07  6:52   ` J Sloan
2001-11-07 21:17   ` J Sloan
2001-11-07 22:30     ` Robert Love
2001-11-08  3:48     ` preempt-patch cleared of blame J Sloan
2001-11-08 10:36       ` Jens Axboe
2001-11-08 12:23         ` Ingo Molnar
2001-11-08 11:38           ` Jens Axboe
2001-11-08 11:41             ` [patch] cciss dequeue race fix (was Re: preempt-patch cleared of blame) Jens Axboe
2001-11-08 12:05             ` AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go Cyrus
2001-11-08 17:14               ` Robert Love [this message]
2001-11-09  0:45                 ` David S. Miller
2001-11-08 22:04               ` Jussi Laako
2001-11-08 23:28                 ` Alan Cox
2001-11-09 21:04                   ` Jussi Laako
2001-11-15 23:25                     ` Stephen C. Tweedie
2001-11-11  7:59             ` AMD761Agpgart+Radeon64DDR+kernel+2.4.15-pre2...still testing Cyrus
2001-11-09  1:35         ` Success with 2.4.14 on Compaq 6500 J Sloan

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=1005239692.939.34.camel@phantasy \
    --to=rml@tech9.net \
    --cc=cyjamten@ihug.com.au \
    --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