I run Etch on machine with Nvidia nForce3 250 motherboard and Radeon
9550 graphics card. DRI is not working neither with radeon, nor fglrx
driver. I tried several versions of fglrx driver and kernel, Debian and
vanilla.

I think it's a bug and that probably is in kernel. I want to file a bug
report.

Both radeon and fglrx log files refer to kernel module, which in was in
all cases loaded (agpgart was linked statically, and also drm and radeon
modules were present, sometimes statically, sometimes dynamically).

Also may be interesting, I tried with Nvidia card and DRI was working.

Do you think it's kernel or video drivers? Should I file a bug report
only to Debian or also to original project?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu March 29 2007 10:08, Marko Randjelovic wrote:
> I run Etch on machine with Nvidia nForce3 250 motherboard and Radeon
> 9550 graphics card. DRI is not working neither with radeon, nor fglrx
> driver. I tried several versions of fglrx driver and kernel, Debian and
> vanilla.
>
> I think it's a bug and that probably is in kernel. I want to file a bug
> report.
>
> Both radeon and fglrx log files refer to kernel module, which in was in
> all cases loaded (agpgart was linked statically, and also drm and radeon
> modules were present, sometimes statically, sometimes dynamically).
>
> Also may be interesting, I tried with Nvidia card and DRI was working.
>
> Do you think it's kernel or video drivers? Should I file a bug report
> only to Debian or also to original project?

I'm not sure where/what the problem is. I would file a bug against radeon or
fglrx and let the debian developers decide what needs to be done with it
since they will have a better view of the situation.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Scribit Marko Randjelovic dies 29/03/2007 hora 19:08:
> I run Etch on machine with Nvidia nForce3 250 motherboard and Radeon
> 9550 graphics card. DRI is not working neither with radeon, nor fglrx
> driver. I tried several versions of fglrx driver and kernel, Debian
> and vanilla.
>
> I think it's a bug and that probably is in kernel. I want to file a
> bug report.

Begin by publishing somewhere a complete output (error messages you see
or description or a bad graphical output) and X server log for each
combination of kernel and DRI driver used. If you have a personal web
space, it would be perfect. If you don't, you could file a bug report on
fglrx for each combination, with the log attached to the bug report.

Quickly,
Pierre
--
nowhere.man@levallois.eu.org
OpenPGP 0xD9D50D8A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGC+pdxe13INnVDYoRAnc3AJ9KBMgNE0OIig1thWeEgL/GyfbFIQCfXoUj
95ScU8IQwH3Q9BsMCJrmXFo=
=4EKD
-----END PGP SIGNATURE-----

On my surprise, today I checked again and saw direct rendering is
enabled. It looks like the problem was reaired in some recent kernel
upgrade, but I didn't notice it yesterday, because two days ago I
uninstalled libgl1-mesa-dri, because it was listed by deborphan.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Marko Randjelovic wrote:
> On my surprise, today I checked again and saw direct rendering is
> enabled. It looks like the problem was reaired in some recent kernel
> upgrade, but I didn't notice it yesterday, because two days ago I
> uninstalled libgl1-mesa-dri, because it was listed by deborphan.
>
>

The problem was in BIOS settings of the motherboard. AGP aperture size
was at default value of 32MB, which was to small for kernel.
Furthermore, that option was hidden, so you have to press CTLR+F1 to
unhide it. I have set it to 256MB, but later I didn't remmember it.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org