From: Zack Gilburd <zack@tehunlose.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21rc6-ac1 Nforce2 AGP+ATI FireGL v2.9.12=hard lock
Date: Sat, 31 May 2003 14:54:52 -0700 [thread overview]
Message-ID: <200305311454.55244.zack@tehunlose.com> (raw)
In-Reply-To: <3ED8E682.5020506@poczta.onet.pl>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1297 bytes --]
On Saturday 31 May 2003 10:29, Gutko wrote:
> Hi,
> Just compiled 2.4.21rc6-ac1 with Nforce2 AGP as module.
> Then tried to install Ati FGLRX 2.9.12 from
> http://www.schneider-digital.de/html/download_ati.html
> http://www.schneider-digital.de/download/ati/glx1_linux_X4.3.zip
> because Ati didn't released XFree 4.3 driver on their www yet.
>
> During install of this rpm i get something like this:
> "Patching drmP.h FAILED, saving rejects to....."
> This *.rej file is in attachment.
> Then module loads normally. I can start X on this driver, but only in 2d.
> Trying to run Tuxracer and any other 3d game hardlocks my machine. 2d
> games works ok.
>
> Everything was OK on clean 2.4.21rc6 patched with this Nforce2 AGP patch.
> http://etudiant.epita.fr:8000/~nonolk/nforce-agp.diff
> but Dave Jones told me it is buggy.
>
> My machine
> Asus A7N8X-deluxe nforce2 mb
> 1 GB of ram
> Ati Radeon 9700 128M
> Agp aperature set to 128M in bios
> Mandrake 9.1
> XFree86 v4.3
>
> I'll be happy to provide more info if needed :)
>
> Gutko
<troll>
does anyone else find it ironic that when he uses ATi FireGL stuff on an
nVidia chipset mobo, it hardlocks? *snicker*
</troll>
mod me down -5 troll accordingly, thanks.
--
Zack Gilburd
http://tehunlose.com
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-31 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 17:29 Gutko
2003-05-31 21:54 ` Zack Gilburd [this message]
2003-05-31 23:17 ` Alan Cox
2003-06-01 0:27 ` Dave Jones
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=200305311454.55244.zack@tehunlose.com \
--to=zack@tehunlose.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
all inboxes | Powered by JetHome®