Alan Cox | 1 Jan 03:01 2004
Picon

Status update - VIA CLE266

I "played" tuxracer using XFree 4.3.0 and my test code last might. Depth
buffering in some cases is shot, there is a lot of fallback stuff
occuring for clipped polygons that isnt working and things are a
peculiar brown colour (someone suggested thats fog issues).

Textures sometimes go missing, it doesn't work with 2D accel at the same
time and some other oddments, but the framework is now functional and
debuggable.

One problem here is that the fallbacks clearly worked with old
XFree/DRI/VIA hacks, and since all the other silicon supported seems to
properly support clipping I've not found a good reference on the
fallback side of things yet.

Alan

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
MichaelM | 1 Jan 20:07 2004
Picon

"soft locks" with radeon 9100

I tried installing the new ati binary drivers, and every game, except Enemy 
Territory hard locks on start-up. I can, however, alt-ctrl-backspace back to 
the console, so it's not the end of the world.
I initially though it was an issue with the ati drivers, but when I reverted 
to the DRI drivers, exactly the same thing happened.
It used to work, but I can't figure out what I may have done that will cause 
this to happen. I'm using kernel 2.4.23-rc3(or 2), the CVS version of XFree86 
4.4, and mandrake 9.1. This setup did work at one stage, but now, it doesn't.
The only thing I can think of was my attempt to upgrade to the 2.6 kernel, 
which resulted in upgrading the module utilities. The 2.6 kernel didn't work, 
but my old kernel still worked fine. Is it possible that the new module utils 
case the modules to load somewhat differently?

I'm got an nforce2 mobo, and a radeon 9100.

Cheers.

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
Michel Dänzer | 1 Jan 09:41 2004
Picon

Re: "soft locks" with radeon 9100

On Thu, 2004-01-01 at 20:07, MichaelM wrote:
> I tried installing the new ati binary drivers, and every game, except Enemy 
> Territory hard locks on start-up. I can, however, alt-ctrl-backspace back to 
> the console, so it's not the end of the world.

Nor is it a hard lock. :) Can you also log in remotely and kill the
game? What about glxgears, does it also lock up? Can you close the
window? ...

> I initially though it was an issue with the ati drivers, but when I reverted 
> to the DRI drivers, exactly the same thing happened.
> It used to work, but I can't figure out what I may have done that will cause 
> this to happen. I'm using kernel 2.4.23-rc3(or 2), the CVS version of XFree86 
> 4.4, and mandrake 9.1. This setup did work at one stage, but now, it doesn't.
> The only thing I can think of was my attempt to upgrade to the 2.6 kernel, 
> which resulted in upgrading the module utilities. The 2.6 kernel didn't work, 
> but my old kernel still worked fine. Is it possible that the new module utils 
> case the modules to load somewhat differently?

I think it's rather unlikely that this would cause the symptoms you
describe. It sounds like the 3D driver hangs. Please provide the output
of

LIBGL_DEBUG=verbose glxinfo

and the relevant parts of the X server log and kernel output.

--

-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Software libre enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer
(Continue reading)

MichaelM | 1 Jan 21:21 2004
Picon

Re: "soft locks" with radeon 9100

On Thursday 01 January 2004 08:41, Michel Dänzer wrote:
> Nor is it a hard lock. :) Can you also log in remotely and kill the
> game? What about glxgears, does it also lock up? Can you close the
> window? ...

I haven't tried to log in remotely, but I can alt-ctrl-f2 to a console and 
kill the program. The xserver remains fine, but the mouse is significantly 
slower.

> I think it's rather unlikely that this would cause the symptoms you
> describe. It sounds like the 3D driver hangs. Please provide the output
> of
>
> LIBGL_DEBUG=verbose glxinfo
>
> and the relevant parts of the X server log and kernel output.

Here are the outputs (I'll try not to spam you):

glxinfo:

name of display: :0.0
libGL: XF86DRIGetClientDriverName: 4.0.1 r200 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r200_dri.so
drmOpenByBusid: busid is PCI:3:0:0
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenByBusid: drmOpenMinor returns 5
drmOpenByBusid: drmGetBusid reports PCI:3:0:0
(Continue reading)

Michel Dänzer | 1 Jan 11:36 2004
Picon

Re: "soft locks" with radeon 9100

On Thu, 2004-01-01 at 21:21, MichaelM wrote:
> On Thursday 01 January 2004 08:41, Michel Dänzer wrote:
> > Nor is it a hard lock. :) Can you also log in remotely and kill the
> > game? What about glxgears, does it also lock up? Can you close the
> > window? ...
> 
> I haven't tried to log in remotely, but I can alt-ctrl-f2 to a console and 
> kill the program. The xserver remains fine, but the mouse is significantly 
> slower.
> 
> > It sounds like the 3D driver hangs. Please provide the output of
> >
> > LIBGL_DEBUG=verbose glxinfo
> >
> > and the relevant parts of the X server log and kernel output.
> 
> Here are the outputs (I'll try not to spam you):

Thanks. I don't see any obvious problems; does setting the R200_NO_IRQS
environment variable make a difference?

--

-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Software libre enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
(Continue reading)

Michel Dänzer | 1 Jan 13:03 2004
Picon

Re: 2.6 kernel change in nopage

On Wed, 2003-12-31 at 19:21, Jon Smirl wrote:
> The headers for nopageXX calls just changed.
> 
> struct page * (*nopage)(struct vm_area_struct * area, unsigned long address, int
> unused);
> changed to:
> struct page * (*nopage)(struct vm_area_struct * area, unsigned long address, int
> *type);
> 
> The DRM drivers need to be adjusted. This probably impacts the BSD builds.

No, this is Linux specific.

How does this patch look?

--

-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Software libre enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer
Attachment (drm-nopage.diff): text/x-patch, 6417 bytes
Arjan van de Ven | 1 Jan 13:10 2004
Picon

Re: [Dri-devel] 2.6 kernel change in nopage

On Thu, 2004-01-01 at 13:03, Michel Dänzer wrote:

> How does this patch look?

ugly.

I find using #defines for function arguments ugly beyond belief and
makes it really hard to look through code. I 10x rather have an ifdef in
the function prototype (which then for the mainstream kernel drm can be
removed for non-matching versions) than such obfuscation.

Michel Dänzer | 1 Jan 13:23 2004
Picon

Re: 2.6 kernel change in nopage

On Thu, 2004-01-01 at 13:10, Arjan van de Ven wrote:
> On Thu, 2004-01-01 at 13:03, Michel Dänzer wrote:
> 
> > How does this patch look?
> 
> ugly.
> 
> I find using #defines for function arguments ugly beyond belief and
> makes it really hard to look through code. I 10x rather have an ifdef in
> the function prototype (which then for the mainstream kernel drm can be
> removed for non-matching versions) than such obfuscation.

That doesn't strike me as particularly beautiful either... is it really
easier for merges, considering that the ugly way is kinda needed for
functions which take different arguments on BSD anyway?

--

-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Software libre enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--
Arjan van de Ven | 1 Jan 13:28 2004
Picon

Re: [Dri-devel] 2.6 kernel change in nopage

On Thu, Jan 01, 2004 at 01:23:40PM +0100, Michel Dänzer wrote:
> > > How does this patch look?
> > 
> > ugly.
> > 
> > I find using #defines for function arguments ugly beyond belief and
> > makes it really hard to look through code. I 10x rather have an ifdef in
> > the function prototype (which then for the mainstream kernel drm can be
> > removed for non-matching versions) than such obfuscation.
> 
> That doesn't strike me as particularly beautiful either... 

well the advantage is that the ifdefs can just go away in kernel trees of
specific versions... (eg unifdef it)

> is it really easier for merges, considering that the ugly way is kinda
> needed for functions which take different arguments on BSD anyway?

I disagree there. The "BSD takes different arguments" thing *should* be
fixed imo by making the common core of the function an inline function, and have
one or two (depends if the common core happens to have its arguments in common
with one of the oses) OS specific wrappers with the right prototype. This
way the difference in error return sign can also be solved in the wrapper
instead of with a nasty macro...

The compiler generates the same code, but it's a lot easier to read/review.

Greetings,
    Arjan van de Ven
(Continue reading)

Michel Dänzer | 1 Jan 13:36 2004
Picon

Re: "soft locks" with radeon 9100


Following up to the list as Michael's ISP doesn't seem to accept mail from
me, without giving a reason...

On Thu, 2004-01-01 at 22:49, MichaelM wrote:
> > Thanks. I don't see any obvious problems; does setting the R200_NO_IRQS
> > environment variable make a difference?
> 
> Nup, that made no difference...

Do you have any other GL related environment variables set, e.g.
LIBGL_THROTTLE_REFRESH or LIBGL_SYNC_REFRESH?

> Would it be a problem with the driver or the kernel module (agp or radeon)? 

Hard to tell yet. Can you try to find out where the apps hang, with gdb
or strace?

--

-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Software libre enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
--

Gmane