On 2019-10-30 16:58 +0000, Daniel James wrote:
> Package: xserver-xorg-video-nouveau
> Version: 1:1.0.16-1
> Severity: important
> File: nouveau
>
> Dear Maintainer,
>
> [Message prepared by reportbug 7.5.3-de10u1 but mailed from
> Thunderbird on a different system]
>
> In Debian 10 "Buster" the Nouveau driver does not start correctly
> unless the "nomodeset" kernel parameter is supplied.
>
> Without "nomodeset" the system boots to a full-screen graphical login
> screen. Login credentials can be entered, but the screen then flashes
> off (black) for a fraction of a second and returns to the login dialog.
>
> With "nomodeset" Debian starts but the screen resolution is not
> optimal, and cannot be changed. The system boots to a graphical login
> screen with the edges black -- apparently a 1280x1024 displayed
> full-height but narrower than the screen. When login credentials are
> entered the system boots but still only shows a 1280x1024
> desktop. Attempts to change the resolution (e.g. using xrandr to add a
> new mode and switch to it fail).
With nomodeset X will fallback to the fbev or vesa drivers. The latter
has very limited support for modern wide screens, the former does not
let you change the resolution at all.
> The system uses an Asus M2NPV-VM motherboard with NForce 430 chipset
> and GeForce 61500 onboard graphics. The monitor is a Dell U2410 which
> has a native resolution of 1920x1200 pixels.
There have been many problems with these onboard graphics, quite a large
fraction of the nouveau bug reports in Debian are from system with it.
> On Debian 9 "Stretch" it was not necessary to specify "nomodeset", and
> the full screen resolution was used.
>
> This bug report is being prepared from a text console after booting
> WITHOUT "nomodeset". The errors ("EE") at 45.875 seem to be crucial.
I think you are right here.
> [ 45.875] (EE) NOUVEAU(0): Error creating GPU channel: -19
> [ 45.875] (EE) NOUVEAU(0): Error initialising acceleration.
> Falling back to NoAccel
> [ 45.875] (**) NOUVEAU(0): [COPY] acceleration disabled
That's not good. Can you please send some kernel logs? Run
"sudo dmesg| grep -E '(drm|nouveau)" to retrieve them.
You may want to try different kernels (4.9 from stretch, 5.2 from
testing and/or 5.3 from unstable) and see if they give better results.
Good luck,
Sven
