On Thu, 2006-08-03 at 09:27 +0200, B. Zhang wrote:
> Hi,
>
> I have the same problem, but only for kernel 2.6.18-rc.
>
> $ grep agp /var/log/Xorg.0.log
> (WW) RADEON(0): [agp] AGP not available
> (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
> (II) RADEON(0): [agp] You may w
Hi,
I have the same problem, but only for kernel 2.6.18-rc.
$ grep agp /var/log/Xorg.0.log
(WW) RADEON(0): [agp] AGP not available
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
(II) RADEON(0): [agp] You may want to make sure the agpgart kernel
module
(**) RADEON(0): agp_si
Dear kernel maintainers,
could you please check if this bug is really a kernel problem ?
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, 2006-07-19 at 08:57 +0200, Michel Dänzer wrote:
> Now, it's odd that there isn't anything pertaining to your AGP bridge in
> the kernel output, and that lsmod shows intel_agp being unused. In my
> experience, intel_agp should generate output about the hardware it
> detects, and agpgart sho
On Wed, 2006-07-19 at 09:31 +0200, Michel Dänzer wrote:
> I forgot to mention that you may be able to enable the DRI with
>
> Option "BusType" "PCI"
>
> as a workaround, but performance probably won't be great.
Thank you for the tip ! I cannot test the speed ATM because I work
remotely,
On Wed, 2006-07-19 at 11:28 -0400, Carlos Moffat wrote:
> I find a similar problem with my custom build 2.6.17 kernel. With the
> same setup, but using a 2.6.16 kernel, everything works, so it does
> seems like the kernel is guilty of this one.
In my case the problem was there before kernel 2.6.1
I find a similar problem with my custom build 2.6.17 kernel. With the
same setup, but using a 2.6.16 kernel, everything works, so it does
seems like the kernel is guilty of this one.
The 'BusType' workaround does seem to work on 2.6.17, but it quite a bit
slower.
Cheers,
Carlos
signature.asc
De
On Wed, 2006-07-19 at 08:57 +0200, Michel Dänzer wrote:
>
> At any rate, this looks like a kernel AGP issue rather than an X driver
> issue.
I forgot to mention that you may be able to enable the DRI with
Option "BusType" "PCI"
as a workaround, but performance probably won't be great.
On Tue, 2006-07-18 at 23:17 +0200, Laurent Bonnaud wrote:
> On Tue, 2006-07-18 at 17:44 +0200, Michel Dänzer wrote:
>
> > Note that I don't think lsmod lists the modules in the order they were
> > loaded. Also, the above message was written back when both radeon and
> > agpgart were still monolith
On Tue, 2006-07-18 at 17:44 +0200, Michel Dänzer wrote:
> Note that I don't think lsmod lists the modules in the order they were
> loaded. Also, the above message was written back when both radeon and
> agpgart were still monolithic modules. Now that they have both been
> split into core and backe
On Tue, 2006-07-18 at 16:19 +0200, Laurent Bonnaud wrote:
> Package: xserver-xorg-video-ati
> Version: 1:6.5.8.0-1
> Severity: important
>
>
> Hi,
>
> since a few revisions of the xorg server, DRI does not work any longer
> on this system. The computer is equipped with this videocard:
>
> 01:0
11 matches
Mail list logo
