On Wed, Nov 3, 2010 at 11:24, Gregory Edigarov wrote:
> It now seems like 4.7's X on 4.8 base system (yes I know it's bad and
> unsupported but that's where I left after all) works perfectly with DRI
> turned off. However, there were hungups when I've been trying to run
> 4.7's with DRI, AND 4.8's
Just to add some more information to this discussion, it appears that
I'm now getting a similar error:
inteldrm0: gpu hung!
no reset function for chipset.
error: [drm:pid3099::inteldrm_lastclose] *ERROR* failed to idle hardware: 5
error: [drm:pid8658:inteldrm_lastclose] *ERROR* failed to idle hard
On Thu, 4 Nov 2010 13:25:18 +
Tom Murphy wrote:
> Hi,
>
> This might be a bit of a long shot, but try:
>
> Option "FramebufferCompression" "False"
>
> It fixed inteldrm0: gpu hung! messages on my Acer's Intel 845GM
> chipset. It might keep it from hanging in yours?
Will try it a bit
On Thu, Nov 4, 2010 at 2:25 PM, Tom Murphy wrote:
> Hi,
>
> This might be a bit of a long shot, but try:
>
> Option "FramebufferCompression" "False"
>
> It fixed inteldrm0: gpu hung! messages on my Acer's Intel 845GM
> chipset. It might keep it from hanging in yours?
Maybe this[1] should be ex
Hi,
This might be a bit of a long shot, but try:
Option "FramebufferCompression" "False"
It fixed inteldrm0: gpu hung! messages on my Acer's Intel 845GM
chipset. It might keep it from hanging in yours?
Tom
On Wed, 3 Nov 2010 13:10:52 +0200
Gregory Edigarov wrote:
> On Wed, 3 Nov 2010 12:20:53 +0200
> Gregory Edigarov wrote:
>
> > On Tue, 2 Nov 2010 12:52:00 -0500
> > Marco Peereboom wrote:
> >
> > > That looks like a hardware driver issue.
> >
> > That's what I think for now... I have turned o
On Wed, 3 Nov 2010 12:20:53 +0200
Gregory Edigarov wrote:
> On Tue, 2 Nov 2010 12:52:00 -0500
> Marco Peereboom wrote:
>
> > That looks like a hardware driver issue.
>
> That's what I think for now... I have turned off DRI in my adapter
> section
> Will observe the behaviour, and update so
On Tue, 2 Nov 2010 12:52:00 -0500
Marco Peereboom wrote:
> That looks like a hardware driver issue.
That's what I think for now... I have turned off DRI in my adapter
section
Will observe the behaviour, and update soon.
> oga any insight?
--
With best regards,
Gregory Edigarov
That looks like a hardware driver issue.
oga any insight?
On Tue, Nov 02, 2010 at 06:22:43PM +0200, Gregory Edigarov wrote:
>
> well, it seems like it was xorg.conf.
>
> after running X -configure and reinstalling the config - problem seems
> to have wanished.
>
> will observe the behaviour, t
On Tue, Nov 02, 2010 at 06:22:43PM +0200, Gregory Edigarov wrote:
> well, it seems like it was xorg.conf.
>
> after running X -configure and reinstalling the config - problem seems
> to have wanished.
>
> will observe the behaviour, though...
>
What are the diferences between the old config file
well, it seems like it was xorg.conf.
after running X -configure and reinstalling the config - problem seems
to have wanished.
will observe the behaviour, though...
On Tue, 2 Nov 2010 17:36:08 +0200
Gregory Edigarov wrote:
> Hello,
>
> not sure about fvwm yet, but it seems like scrotwm can't
Hello,
not sure about fvwm yet, but it seems like scrotwm can't work correctly:
inteldrm0: gpu hung!
no reset function for chipset.
error: [drm:pid8065:inteldrm_lastclose] *ERROR* failed to idle
hardware: 5 error: [drm:pid26694:inteldrm_lastclose] *ERROR* failed to
idle hardware: 5 error: [drm:p
12 matches
Mail list logo
