Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #258615

Re: video issue following latest bullseye update

Show all headers | View raw

Felix Miata wrote on 5/19/23 11:23:

> 
> How much time did you allow the login screen to show up? I've lately seen on

Somewhere between three and five minutes, I'd say. Certainly long after the 
disk light stopped flickering and the system seemed to have reached a stable 
state.

> 
> 	systemctl restart <dmname>

OK; so that would be:
   systemctl restart lightdm
Useful to know; thank you.

> 
>> I reinstalled xserver-xorg-video-nouveau from the console, and (fortunately)
>> when I rebooted LDM came up as usual and I was able to log in as I normally
>> do. Obviously, the original issue still exists, but at least I got a graphical
>> display back.
> 
> If by that you mean back to 640x480 or 800x600 instead of your display's native

No; I didn't mean that. Sorry I wasn't clear. I meant that after reinstalling 
xserver-xorg-video-nouveau and rebooting, everything looked the way it did 
before I removed xserver-xorg-video-nouveau, so I was back exactly to what I 
was seeing when I first started this thread.

> 
> [1] Instead of driver removal/reinstallation, create file, or add following
> content to existing file:
> 
> 	/etc/X11/xorg.conf.d/50-device.conf
> 
> Section "Device"
>    Identifier "DDX"
> 	Driver "modesetting"
> #	Driver "nouveau"
> EndSection
> 

I have created that file, with those contents:

----

[ZB:~] cat /etc/X11/xorg.conf.d/50-device.conf
Section "Device"
   Identifier "DDX"
         Driver "modesetting"
#       Driver "nouveau"
EndSection
[ZB:~]

----

Do you really mean "DDX", not "DIX"? <--------

I made the edit according to your instructions (i.e., "DDX") but I'm not 
certain that your e-mail didn't contain a typo.

> By simply moving the # to the other driver line, you can easily switch between
> using the two display drivers by restarting your DM or rebooting.
Right now, the 50-device.conf file looks exactly as it does above but, and I 
have restarted lightdm by issuing:
   systemctl restart lightdm
from the console.

I currently get:

----

[ZB:~] sudo inxi -GSaz
System:    Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
            parameters: BOOT_IMAGE=/BOOT/debian@/vmlinuz-5.10.0-23-amd64 
root=ZFS=/ROOT/debian ro root=ZFS=rpool/ROOT/debian
            Desktop: Trinity R14.1.1~[DEVELOPMENT] tk: Qt 3.5.0 info: kicker 
wm: Twin 3.0 dm: LightDM 1.26.0
            Distro: Debian GNU/Linux 11 (bullseye)
Graphics:  Device-1: NVIDIA GF108 [GeForce GT 430] vendor: Gigabyte driver: 
nouveau v: kernel bus ID: 04:00.0
            chip ID: 10de:0de1 class ID: 0300
            Display: server: X.Org 1.20.11 driver: loaded: nouveau unloaded: 
modesetting display ID: :0 screens: 1
            Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm 
(20.0x11.2") s-diag: 582mm (22.9")
            Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm 
(20.0x11.3") diag: 584mm (23")
            OpenGL: renderer: NVC1 v: 4.3 Mesa 20.3.5 direct render: Yes

----

But I am still seeing the original problem I reported.

[I also did a test, just to prove to myself that what I'm seeing isn't due to 
some weird monitor problem (it's a pretty new monitor, and I wanted to be sure 
that somehow I hadn't just missed seeing the problem before I performed the 
update -- even though the issue is so obvious that I can't really believe that 
I wouldn't have noticed it before). I took a screenshot of a screen display 
that exhibited the problem (a konqueror file listing), and copied the file to 
another system that is attached to the same KVM switch.

When I display the screenshot image in this, my normal desktop system, I see 
the problem; when I look at the same image file on my other system -- which 
has NOT had the recent update applied -- the problem is absent, even though 
I'm viewing it on the very same monitor. So I am as sure as I can be that, as 
I believed, the recent bullseye update led to the issue.]

   Doc

-- 
Web:  http://enginehousebooks.com/drevans

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

video issue following latest bullseye update "D. R. Evans" <doc.evans@gmail.com> - 2023-05-15 17:50 +0200
  Re: video issue following latest bullseye update Felix Miata <mrmazda@earthlink.net> - 2023-05-15 19:20 +0200
    Re: video issue following latest bullseye update "D. R. Evans" <doc.evans@gmail.com> - 2023-05-15 21:00 +0200
      Re: video issue following latest bullseye update Felix Miata <mrmazda@earthlink.net> - 2023-05-15 21:30 +0200
        Re: video issue following latest bullseye update "D. R. Evans" <doc.evans@gmail.com> - 2023-05-17 18:20 +0200
          Re: video issue following latest bullseye update Felix Miata <mrmazda@earthlink.net> - 2023-05-17 19:00 +0200
          Re: video issue following latest bullseye update Felix Miata <mrmazda@earthlink.net> - 2023-05-18 06:20 +0200
        Re: video issue following latest bullseye update "D. R. Evans" <doc.evans@gmail.com> - 2023-05-18 22:20 +0200
          Re: video issue following latest bullseye update Felix Miata <mrmazda@earthlink.net> - 2023-05-19 19:30 +0200
            Re: video issue following latest bullseye update "D. R. Evans" <doc.evans@gmail.com> - 2023-05-22 22:40 +0200
              Re: video issue following latest bullseye update Felix Miata <mrmazda@earthlink.net> - 2023-05-23 21:40 +0200
                Re: video issue following latest bullseye update "D. R. Evans" <doc.evans@gmail.com> - 2023-05-31 19:50 +0200
  Re: video issue following latest bullseye update Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-05-16 02:30 +0200

csiph-web