Re: Bug#711305: Loading i915 with modeset=1 disables display

[Robert de Bath]

On Mon, 15 Jul 2013, Julien Cristau wrote:


On Mon, Jul 15, 2013 at 07:37:47 +0100, Robert de Bath wrote:


On Sun, 9 Jun 2013, Julien Cristau wrote:


If i915 doesn't give you a working display that's a kernel bug.

Thanks, I'll add my voice to the multitude over there.


Is it an X bug that X doesn't work with the driver if that option is
set ? Is it a kernel bug ?


Neither.

OTOH, I think this should belong to at least one of them as it's a valid
configuration option for the end user. They can reasonably choose to
not have a graphic display unless they start X.

In that way I think it's Both. 
X has a bug in that it can't configure the driver properly.

The kernel is bugged in that it can't remove the driver and restore the
display back to what it "should be" without a reboot.

But I suppose both projects will look on this as some sort of "reasonable
limitation" and so WONTFIX.

Anyway, thankyou for your time.

--
Rob.  (Robert de Bath )
 



--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/alpine.DEB.2.00.1307161929301.21887@mayday

Re: Bug#717054: gdm3: greeter garbles up screen, no input possible, cannot even switch to tty

[Simon McVittie]

On 16/07/13 12:43, Axel Stammler wrote:
> Package: gdm3
> Version: 3.4.1-8
> Severity: important

> [24.009] (EE) R128(0): R128DRICloseScreen: CCE stop -22
...
> [24.014] (WW) R128(0): Direct rendering disabled
...
> [24.966] (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> [24.966] (EE) R128(0): Idle timed out, resetting engine...
> [24.966] (EE) R128(0): R128CCEWaitForIdle: CCE stop -9
> [24.966] (EE) R128(0): R128CCEWaitForIdle: CCE start -9
> [24.966] (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> [24.966] (EE) R128(0): Idle timed out, resetting engine...

I suspect this isn't gdm3's fault, and should be reassigned to
xserver-xorg-video-r128 (or possibly the kernel, or something else in
the graphics stack). X maintainers: any ideas?

If you disable gdm3 ("sudo update-rc.d gdm3 disable"), log in using text
mode, and try using startx or similar, that might indicate whether gdm3
is somehow triggering or causing this - if you get the same errors when
X is started by startx, then it isn't gdm3's fault.

Please attach the output of "reportbug --template
/usr/lib/xorg/modules/drivers/r128_drv.so", which should contain
information on X and the R128 driver.

S


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51e53cfa.1000...@debian.org