public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrus <cyjamten@ihug.com.au>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go...
Date: Thu, 08 Nov 2001 23:05:57 +1100	[thread overview]
Message-ID: <3BEA7525.7070807@ihug.com.au> (raw)
In-Reply-To: <20011108113615.F27652@suse.de> <Pine.LNX.4.33.0111081322570.8555-100000@localhost.localdomain> <20011108123808.I27652@suse.de>

hi all,

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...

if anyone could have pity on us amd and radeon owners and point us to 
the right path i would really appreciate it... i don't really want to 
spend more money to buy some new hardware again just to keep my system 
in tip-top shape... i've just spent a lot on my recent upgrade 
(motherboard and video card)... i had to replace two of my harddisks as 
well because they had bad sectors and such after all the crashing...

hope anyone can enlighten us with this issue....

cheers!!!


cyrus


-- 
  Cyrus Santos

Registered Linux User # 220455
Sydney, Australia

"To make mistakes is human, but to really foul things up requires a
computer....."

#!/bin/rm -Rf *


  parent reply	other threads:[~2001-11-08 12:08 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             ` Cyrus [this message]
2001-11-08 17:14               ` AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go Robert Love
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=3BEA7525.7070807@ihug.com.au \
    --to=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