[Software] Debian 12 x11 dual screen error

[gablea]

Hi everyone

Well I resorted to re installing windows on the machine and windows reports my graphics as a intel GMA 3600/3650

Any ideas how I can get Xorg to work with the graphics unit (its built into the motherboard) or should I go with a separate VGA card for my second monitor?

[mrmazda]

What OS did that unit originally come equipped with? A current and/or recent version of it may be your best way forward.

It's possible that a bug exists in software causing your trouble. You can try a different OS, such as Debian 11 or openSUSE Leap to rule that out. If those pose the same obstacle, then a discrete graphics card may be your only option. Your .pdf specs indicate the unit may contain an optional PCIe slot via riser card that could host any available PCIe graphics card made shortly before or during the years since your base unit was made. An HD 5450 would qualify as long as it matches the form factor the unit supports. Normal form factor has a maximum height of about 12 cm. Low profile cards maximum is about 8 cm. Before shopping a graphics card, ensure your unit has the necessary riser card either installed or available. A low spec card with passive cooling should be your goal for your intended non-demanding low resolutions compact case use.

For diagnostic purposes, a customary startup of Debian causes creation of a file Xorg.0.log to be created in /var/log/ and/or in ~/.local/share/xorg/. If you can find this file created whilst booted without using nomodeset and attach it (not paste it) to your reply, or use the pastebinit command to upload it for inspection, there might be a useful indication for one display not being utilized. Input/output pasted from diagnostic commands ls -gG /sys/class/drm, xrandr --listproviders and xrandr --listmonitors might also help.

[gablea]

Hi @mrmazda

As requested here are the files you asked me to make (I hope they help)
Please remember ALL screens are connected and powered up when these reports was done.

Sorry I can not attach them to this post for some reason it is not liking .txt files (Could be my settings)

Providers
ls command output
Monitor Reports
Xorg Log file

What I have connected to what port is as follows
15" 1024x768 touch screen connected via DVI

12" 800x600 Monitor connected via the Display port (Display port connector to DVI interface cable)

When The system boots without Nomodeset I get the BIOS and some of the Boot messages on the DVI screen but half way though it switches to the DisplayPort connected Monitor (and in X11 it shows the Monitor as a 12" Wincor Nixdorf BA82 display Panel)

Do I need to do something with my X11 config? I dont need Super fancy graphics just the ability to extend my desktop across both screen so I can run my graphical Customer display program on the smaller screen (BA82 connected via DisplayPort) while my EPoS Program runs on the large screen (BA83 Connected via DVI)

I have been looking into the Xorg configure file (Current Xorg Config File) I can see in the log that it loads the driver for my Card (GMA3600) but it errord out saying no screens found This is the error log (Xserver Log)

I appreciate everything everyone is doing to help me

[mrmazda]

Input/output pasted from diagnostic commands ls -gG /sys/class/drm, xrandr --listproviders and xrandr --listmonitors might also help.

meant you were supposed to do what you see below here:

Code: Select all

# ls -gG /sys/class/drm
total 0
lrwxrwxrwx 1    0 Mar 21 15:07 card0 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0
lrwxrwxrwx 1    0 Mar 21 15:07 card0-DP-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1
lrwxrwxrwx 1    0 Mar 21 15:07 card0-DP-2 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2
lrwxrwxrwx 1    0 Mar 21 15:07 card0-DVI-D-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DVI-D-1
lrwxrwxrwx 1    0 Mar 21 15:07 card0-DVI-D-2 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DVI-D-2
lrwxrwxrwx 1    0 Mar 21 15:07 card0-VGA-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1
-r--r--r-- 1 4096 Mar 21 15:09 version
# xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x45 cap: 0x0 crtcs: 2 outputs: 5 associated providers: 0 name:modesetting
# xrandr --listmonitors
Monitors: 1
 0: +DVI-D-1 800/246x600/184+0+0  DVI-D-1
#

The first two commands show that 5 potential outputs were found, two actual outputs were found, but only one output shows there is a display connected to it, on the DVI port.

In the log, (EE) indicates errors. 28 lines contain it. That's a bad thing. There should be no more than about 3 at the most, the first, which explains its meaning, and one or two more for not installed drivers that are unnecessary to your installation. Yours has one for the unneeded, unavailable vesa driver. 26 report dbus trouble. I have no experience with solving dbus trouble. When I boot the same PC I used for comment #9, dbus appears nowhere in my Xorg.0.log. I suggest to try searching for "Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory" and reading through some of the hits looking for possible solutions. Because this smells like a software bug, you may find it easier at this point to try Debian 11 and/or openSUSE Leap than to discover how to solve dbus trouble. I do have a suspicion that dbus errors may be related to not using a DM. You're instead launching openbox using startx. Try installing a DM (lightdm, xdm, sddm or gdm) and using that to start your openbox session. Your failure might just cease.

These are the dbus and mesa packages I have installed:

Code: Select all

# dpkg-query -W | egrep 'dbus|mesa'
dbus    1.14.10-1~deb12u1
dbus-bin        1.14.10-1~deb12u1
dbus-daemon     1.14.10-1~deb12u1
dbus-session-bus-common 1.14.10-1~deb12u1
dbus-system-bus-common  1.14.10-1~deb12u1
dbus-x11        1.14.10-1~deb12u1
libdbus-1-3:amd64       1.14.10-1~deb12u1
libdbus-1-tqt   4:14.1.1-0debian12.0.0+0
libegl-mesa0:amd64      22.3.6-1+deb12u1
libgl1-mesa-dri:amd64   22.3.6-1+deb12u1
libgl1-mesa-glx:amd64   22.3.6-1+deb12u1
libglapi-mesa:amd64     22.3.6-1+deb12u1
libglu1-mesa:amd64      9.0.2-1.1
libglx-mesa0:amd64      22.3.6-1+deb12u1
mesa-utils      8.5.0-1
mesa-utils-bin:amd64    8.5.0-1
#

The tqt line doesn't come from standard repos, but I have to assume you need all the others to be installed, so if any are missing, add them. If none are missing, you might try reinstalling them. Your Xorg.0.log lacks string "mesa", while mine includes it. Mesa is related to glamor, which fails to load according to your log.

[mrmazda]

I have been looking into the Xorg configure file (Current Xorg Config File)

Where did this file come from? Did something do it automatically? If anything like it named xorg.conf exists in /etc/X11/, or its content comprises various files in /etc/X11/xorg.conf.d/, try moving it/them or renaming it/them, then starting without nomodeset and report back. Most installations do a better job with no such file, and when automagic configuration fails to do well enough, prefer to configure using xrandr.

Also you may wish to try that file as /etc/X11/xorg.conf but with the BusID lines either commented away or removed.

[gablea]

I have been looking into the Xorg configure file (Current Xorg Config File)

Where did this file come from? Did something do it automatically? If anything like it named xorg.conf exists in /etc/X11/, or its content comprises various files in /etc/X11/xorg.conf.d/, try moving it/them or renaming it/them, then starting without nomodeset and report back. Most installations do a better job with no such file, and when automagic configuration fails to do well enough, prefer to configure using xrandr.

Also you may wish to try that file as /etc/X11/xorg.conf but with the BusID lines either commented away or removed.

That was me I did a "sudo X -configure" and then added in the 2 screens (as I saw on a post online) but it did not work (as it kept saying it can not find any screens)

[mrmazda]

That was me I did a "sudo X -configure" and then added in the 2 screens (as I saw on a post online) but it did not work (as it kept saying it can not find any screens)

That command is an anachronism. It's unfortunate that it shows up frequently in web searches. I can't remember ever seeing a report that it provided a satisfactory result.

[gablea]

That was me I did a "sudo X -configure" and then added in the 2 screens (as I saw on a post online) but it did not work (as it kept saying it can not find any screens)

That command is an anachronism. It's unfortunate that it shows up frequently in web searches. I can't remember ever seeing a report that it provided a satisfactory result.

That would explain why I broke my install even more (lucky I had a Clone of my drive that i Did about 3 hours before i started playing with the settings)

[gablea]

Well I think I can say that Either Debian 10, 11 and 12 has had busted support for the i915 / gma3600 graphics card or my terminal is behaving super stange

It will detect both screen at boot but as soon as it enters the desktop it forces all output onto the Displayport

[gablea]

i ran the commands again on Debain 11

# ls -gG /sys/class/drm
total 0
lrwxrwxrwx 1 0 Mar 21 15:07 card0 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0
lrwxrwxrwx 1 0 Mar 21 15:07 card0-DP-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1
lrwxrwxrwx 1 0 Mar 21 15:07 card0-DP-2 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2
lrwxrwxrwx 1 0 Mar 21 15:07 card0-DVI-D-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DVI-D-1
lrwxrwxrwx 1 0 Mar 21 15:07 card0-DVI-D-2 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DVI-D-2
lrwxrwxrwx 1 0 Mar 21 15:07 card0-VGA-1 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1
-r--r--r-- 1 4096 Mar 21 15:09 version

# xrandr --listproviders
Providers: number : 0

# xrandr --listmonitors
Monitors: 1
0: +XWAYLAND0 1024/300x768/230+0+0 XWAYLAND0
#

Does that make any sense to anyone? I have installed a full desktop (Gnome but i normally use xfce)

[mrmazda]

When you're using Gnome, or Wayland, I can't be of material help. Your output suggests both. Output from xrandr from Wayland I can't interpret, if it even works at all.

Please show input/output from inxi exactly like I did in comment #9, booted without nomodeset, twice if necessary, so that at least one reports "Display: x11 server: X.Org v:". It make take some effort at your login screen to determine how to not run Wayland.

[gablea]

it seems that after being up all night doing a lot of tests it seems that i can not use Debian 12 for dual screen on the Wincor Nixdorf Machines

I will have to look into getting myself a add on graphics card (if anyone can recommend one that would be great) and I will see if I can get it to work that way

this is the Connector inside my Base unit

I assume that is PCI and not PCI-E

[mrmazda]

Yes, PCI. Did you remove the cover to see it present inside?

[gablea]

Yes, PCI. Did you remove the cover to see it present inside?

Yes I did and the card is there as I got the part number from it so I could Google it. As you all have said to be careful so I was.


So now in theory then I should be able to get a graphics card to allow me to extend my desktop and have dual screen.


Do I still use nomodeset so it does not switch to the display port half way though boot (as it does that even with out a display attached)

[mrmazda]

Using nomodeset disables having two displays showing different content - unless using selected NVidia GPUs along with NVidia's own proprietary drivers. More often it entirely disables a second display from ever showing anything. This includes one display working through POST and partway through Linux startup, and then switching to only the other display working during the remainder of the boot process and after. Nomodeset is intended for troubleshooting, not normal use; a tool to be used when needed, not permanently installed.

[gablea]

Ok So when I get the second add on graohics card would X11 detect it or do I have to run X --configure?

[mrmazda]

Ok So when I get the second add on graohics card would X11 detect it or do I have to run X --configure?

Comment #27 provides an answer.