Linus Torvalds wrote:
On Mon, 2 Jun 2003, Keith Whitwell wrote:
Under what circumstances does this actually happen? First 3d app run? Even
something like 'glinfo'?
I don't even get a desktop - the thing hangs at initialization time
(probably when clearing the screen.
My hardware may actuall
On Mon, 2 Jun 2003, Keith Whitwell wrote:
>
> Under what circumstances does this actually happen? First 3d app run? Even
> something like 'glinfo'?
I don't even get a desktop - the thing hangs at initialization time
(probably when clearing the screen.
My hardware may actually have gone bad,
Am Montag, 2. Juni 2003 15:09 schrieb Keith Whitwell:
> Linus Torvalds wrote:
> > Have others seen this? Current DRI CVS tree, current 2.5.x kernel (which
> > is pretty current kernel-module-wise, the only difference to the current
> > DRI tree _seems_ to be the documentation updates).
> >
> > Same
Linus Torvalds wrote:
On Fri, 30 May 2003, Linus Torvalds wrote:
Modulo that, X is happy, with no error messages apart from a mention of
the irq issue in the logs up until the lockup:
(II) RADEON(0): [drm] failure adding irq handler, there is a device already
using that irq
[drm]
Linus Torvalds wrote:
Have others seen this? Current DRI CVS tree, current 2.5.x kernel (which
is pretty current kernel-module-wise, the only difference to the current
DRI tree _seems_ to be the documentation updates).
Same thing happens with an older DRI CVS tree too (with new kernel
modules),
On Fri, 30 May 2003, Linus Torvalds wrote:
>
> Modulo that, X is happy, with no error messages apart from a mention of
> the irq issue in the logs up until the lockup:
>
> (II) RADEON(0): [drm] failure adding irq handler, there is a device already
> using that irq
> [drm] falling ba
Have others seen this? Current DRI CVS tree, current 2.5.x kernel (which
is pretty current kernel-module-wise, the only difference to the current
DRI tree _seems_ to be the documentation updates).
Same thing happens with an older DRI CVS tree too (with new kernel
modules), for that matter.
It'
