[Software] Debian 12 x11 dual screen error

[gablea]

Hi everyone,

I have a Wincor base unit that I have installed Debian 12 onto and I can get it working almost fully but I seem to have a issue that I am not sure how to sort

What I have is the following
12" 800x600 display on display port-1
15" 1024x768 touchscreen on dvi-1 port

If I do not use "no mode set" in grub the system will boot on to the 15" screen but the moment grub has started the kernal it switches to the smaller screen and turns off the 15" screen.

So if I use "nomodeset" the 15" screen stays on and works fine but the small 12" screen stays off and shows "no connection" on the screen.

I have tried xrandr and it has shown just once the dp-1 and dvi-1 ports but it always shows one of them as disconnected.

What do I need to do to get this to work.

My set up is
Debian 12 64bit
X11 with openbox

Linux detects the screens when swapping them but they will not work together.

If someone smarter then me knows what to do I would be for ever greatful.

Andy

[mrmazda]

Using nomodeset disables ability to use more than one display output at a time, unless using certain of NVidia GPUs with NVidia's proprietary drivers.

Are your cables connecting the displays the same on both ends, no converters installed? If any converter is involved, explain.

Booted without using nomodeset, from a terminal within openbox, please run command inxi -GSaz and copy/paste all of the input/output here within code tags (</> icon above input window). Not all installations include it by default, so you might need to install inxi first.

Edited by admin to correct reference to code tag icon (it's not pre)

[bbbhltz]

If you remove ~/.config/monitors.xml and try plugging in the second monitor after booting does that help? Have you tried using arandr or lxrandr to set things up?

[gablea]

Using nomodeset disables ability to use more than one display output at a time, unless using certain of NVidia GPUs with NVidia's proprietary drivers.

Are your cables connecting the displays the same on both ends, no converters installed? If any converter is involved, explain.

Booted without using nomodeset, from a terminal within openbox, please run command inxi -GSaz and copy/paste all of the input/output here within code tags (</> icon above input window). Not all installations include it by default, so you might need to install inxi first.

Edited by admin to correct reference to code tag icon (it's not pre)

@mrmazda
I have booted my machine without the nomodeset option and below are the results from the inxi -GSaz

Code: Select all

System:
  Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64
    root=UUID=8b070891-4954-45c6-b4ae-75b866531cf3 ro 8250.nr_uarts=6
  Desktop: Openbox v: 3.6.1 vt: 1 dm: startx Distro: Debian GNU/Linux 12
    (bookworm)
Graphics:
  Device-1: Intel Atom Processor D2xxx/N2xxx Integrated Graphics
    driver: gma500 v: N/A alternate: gma500_gfx arch: PowerVR SGX545
    process: Intel 65nm built: 2008-10 ports: active: DP-1 empty: DP-2,
    DVI-D-1, DVI-D-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0be2 class-ID: 0300
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
    unloaded: fbdev alternate: vesa dri: swrast gpu: gma500 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 800x600 s-dpi: 96 s-size: 211x158mm (8.31x6.22")
    s-diag: 264mm (10.38")
  Monitor-1: DP-1 model: BA82-3DVI serial: <filter> built: 2012 res: 800x600
    hz: 60 dpi: 83 size: 246x184mm (9.69x7.24") diag: 307mm (12.1") ratio: 4:3
    modes: max: 800x600 min: 720x400
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 128 bits)
    direct-render: Yes

This is the Result I am getting with xrandr

Code: Select all

Screen 0: minimum 320 x 200, current 800 x 600, maximum 4096 x 4096
VGA-1 disconnected primary (normal left inverted right x axis y axis)
DVI-D-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected 800x600+0+0 (normal left inverted right x axis y axis) 246mm x 184mm
   800x600       60.32*+
   640x480       59.94  
   720x400       70.08  
DVI-D-2 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)

My Displays are connected the following ways
Wincor BA82 800x600 is a DVI to DisplayPort connection
Winfor BA83 1024x768 is connected to the DVI Port

When the Machine Boots the BIOS and Loading screen is show in the BA83 just when the system logs the user in the image is swiched to the BA82 screen the issue I have is my Primary application is designed to Run on the BA83 (at 1024x768) and I have a secondy program that should run on the BA82 (800x600)

IF it helps anyone I can do a Video of the system booting so you can see what I mean

If you remove ~/.config/monitors.xml and try plugging in the second monitor after booting does that help? Have you tried using arandr or lxrandr to set things up?

@bbbhltz I tried to delete the file but I got a error Message saying no file name or directory existed

[mrmazda]

Code: Select all

$ xrandr
Screen 0: minimum 320 x 200, current 800 x 600, maximum 4096 x 4096
VGA-1 disconnected primary (normal left inverted right x axis y axis)
DVI-D-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected 800x600+0+0 (normal left inverted right x axis y axis) 246mm x 184mm
   800x600       60.32*+
   640x480       59.94  
   720x400       70.08  
DVI-D-2 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
$

Had you followed my instruction to "copy/paste all of the input/output" for inxi in order to run xrandr, your response would have appeared as you see above. Excluding the command, and the following prompt, from the pasted block, makes it unclear whether or not you actually followed instruction correctly.

My Displays are connected the following ways
Wincor BA82 800x600 is a DVI to DisplayPort connection
Winfor BA83 1024x768 is connected to the DVI Port

This is clear as mud. What does "Wincor BA82" mean? What does "Wincor BA83 mean? There is no such thing that I am aware of as a valid DVI-to-DisplayPort connection, where DVI is the "from" (aka computer) and DisplayPort is the "to" (aka display). According to specifications (AFAIK), VGA, DVI and HDMI output from a computer cannot be converted to DisplayPort display input. I have never been able to get a backwards connection between a DisplayPort-to-something-else converter to work with the DisplayPort end connected to a display, confirming the specifications of the converters involved. WRT DVI, there are different DVI types of ports and cables. Referring to Wikipedia or specifications elsewhere, are you sure you're not trying to use an inappropriate DVI cable? Can both ports work at the same time if you connect to a different pair of displays?

When the Machine Boots the BIOS and Loading screen is show in the BA83 just when the system logs the user in the image is swiched to the BA82 screen the issue I have is my Primary application is designed to Run on the BA83 (at 1024x768) and I have a secondy program that should run on the BA82 (800x600)

Are these "BA8?"s references to docking station outputs or inputs? If they refer to display screens, then additional information is required: CPU model number. Both lscpu and inxi -C can provide it.

As long as it is possible to get both displays working at once, and xrandr output shows two connected, xrandr can fix "primary" status to the appropriate display so that outputs do go to the desired displays.

I have a suspicion the fly in the ointment here is a DisplayPort to DVI converter that is not fully functional WRT your touchscreen needs. Some cost more than others, and you may need one of the more expensive varieties. Another suspicion is the computer to display cables need to be swapped. At least, I would try it.

[gablea]

@mrmazda

I did indeed follow your instructions to the letter the output from the inxi below is ALL the information that was shown on screen (and I piped it to a file so i did not miss anything)

This is the output from the inxi command

this is the BA82 display


This is the BA83 display

I am sorry I may have had the ports the wrong way round I was describing from the screen to the PC

FROM the PC the first screen (BA82) is connect to the DisplayPort via a adaptpr to DVI and the BA83 screen is connected directly to the
DVI port on the Base of the Computer

So should I look at replacing the DisplayPort to DVI Connector with a new one (maybe replace all the cables as well)

Would X handle dual screen as the only window Manager I have is OpenBox (i do not have any Full blown desktops installed)

[mrmazda]

IME, most BIOS for PCs connected to more than one display will during POST and within BIOS setup output only to the display connected to the oldest connection type available, which in your case is DVI. The Linux kernel has its own ideas about priorities, as do the various kernel modules for GPUs, so a switch during boot, or an addition during boot, are not uncommon. It is only after the GPU's kernel module loads, engaging KMS, that more than one engaged disaplay can be expected.

I'm awaiting your CPU type before continuing.

[gablea]

According to the BIOS I have a Intel Atom CPU D2700 2.13GHz with 4096MB RAM

if you want a more detail report tell me what command to run in linux and I will post the result here for you

[mrmazda]

I needed "D2700" in order to find your CPU capabilities here. Comment #5 contained two commands capable of showing it without entering BIOS setup. If you cannot access additional displays just for mere testing, then the cables, and more particularly, the DP-to-DVI adapter, would be the next logical steps to try. Are the cables and adapter the same as originally shipped with the three Wincor units?

Once all is working as expected, inxi input/output should resemble the following in overall format and a significant number of details:

Code: Select all

$ inxi -GSaz --vs
inxi 3.3.33-00 (2024-02-06)
System:
  Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 12.2.0 clocksource: hpet avail: acpi_pm parameters: BOOT_IMAGE=/vmlinuz
    root=LABEL=<filter> resume=LABEL=<filter> ipv6.disable=1 net.ifnames=0
    consoleblank=0 mitigations=off no_console_suspend
  Desktop: Trinity v: R14.1.1 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
    vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 12 (bookworm)
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell
    driver: i915 v: kernel arch: Gen-5 process: Intel 45nm built: 2008 ports:
    active: DP-1,LVDS-1 empty: DP-2, DP-3, HDMI-A-1, HDMI-A-2, VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:2a42 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: Twin v: 3.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2960x1050 s-dpi: 108 s-size: 696x246mm (27.40x9.69")
    s-diag: 738mm (29.06")
  Monitor-1: DP-1 pos: right model: Dell P2213 serial: <filter> built: 2012
    res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
    diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
  Monitor-2: DVI-D-1 pos: primary,left model: Seiko Epson 0x5441 built: 2008
    res: 1280x800 hz: 60 dpi: 107 gamma: 1.2 size: 303x190mm (11.93x7.48")
    diag: 358mm (14.1") ratio: 16:10 modes: 1280x800
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
    device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
    drv: crocus inactive: wayland
  API: OpenGL v: 2.1 vendor: intel mesa v: 22.3.6 glx-v: 1.4 es-v: 2.0
    direct-render: yes renderer: Mesa Mobile Intel GM45 Express (CTG)
    device-ID: 8086:2a42 memory: 1.46 GiB unified: yes
$

[gablea]

I needed "D2700" in order to find your CPU capabilities here. Comment #5 contained two commands capable of showing it without entering BIOS setup. If you cannot access additional displays just for mere testing, then the cables, and more particularly, the DP-to-DVI adapter, would be the next logical steps to try. Are the cables and adapter the same as originally shipped with the three Wincor units?

Once all is working as expected, inxi input/output should resemble the following in overall format and a significant number of details:

Code: Select all

$ pinxi -GSaz --vs
pinxi 3.3.33-02 (2024-02-10)
System:
  Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 12.2.0 clocksource: hpet avail: acpi_pm parameters: BOOT_IMAGE=/vmlinuz
    root=LABEL=<filter> resume=LABEL=<filter> ipv6.disable=1 net.ifnames=0
    consoleblank=0 mitigations=off no_console_suspend
  Desktop: Trinity v: R14.1.1 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
    vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 12 (bookworm)
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell
    driver: i915 v: kernel arch: Gen-5 process: Intel 45nm built: 2008 ports:
    active: DP-1,LVDS-1 empty: DP-2, DP-3, HDMI-A-1, HDMI-A-2, VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:2a42 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: Twin v: 3.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2960x1050 s-dpi: 108 s-size: 696x246mm (27.40x9.69")
    s-diag: 738mm (29.06")
  Monitor-1: DP-1 pos: right model: Dell P2213 serial: <filter> built: 2012
    res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
    diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
  Monitor-2: DVI-D-1 pos: primary,left model: Seiko Epson 0x5441 built: 2008
    res: 1280x800 hz: 60 dpi: 107 gamma: 1.2 size: 303x190mm (11.93x7.48")
    diag: 358mm (14.1") ratio: 16:10 modes: 1280x800
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
    device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
    drv: crocus inactive: wayland
  API: OpenGL v: 2.1 vendor: intel mesa v: 22.3.6 glx-v: 1.4 es-v: 2.0
    direct-render: yes renderer: Mesa Mobile Intel GM45 Express (CTG)
    device-ID: 8086:2a42 memory: 1.46 GiB unified: yes
$

Yes they are the orginal cables. I've ordered some new ones so hopefully that will fix the issues

[gablea]

Hi everyone,

Well I have received my new cable and I'm still having the same issues.

I check to see what driver the kernel is using and it is using a gk_5000 but my graphics card is a intel i915

So does anyone know how I can install the i915 driver I have used the non-free command on the apt list as well as intel-microcode and Linux-misc-firmware

Nothing seems to install the driver for the card.

I would love to get this working as I can get 10 of the base units at a very reasonable price (EPoS base units) if I can not it's not a big deal I can just use the 2x20 line customer displays but it would have been nice to have a graphical display for the customer

[mrmazda]

I check to see what driver the kernel is using and it is using a gk_5000 but my graphics card is a intel i915

Your prior post's inxi output shows:

	driver: gma5001

That coincides with my understanding that your 2011 Intel D2700 Atom processor² is not supported by the i915, which is for Intel's mainline CPU/GPU series. The D2700 provides GMA3650^3,4 graphics, for which the gma500 driver exists, but providing questionable support⁵.

[1] https://en.wikipedia.org/wiki/Intel_GMA#GMA_500
[2] https://en.wikipedia.org/wiki/Intel_Atom
[3] https://www.techpowerup.com/gpu-specs/gma-3650.c3143
[4] https://en.wikipedia.org/wiki/Intel_GMA#GMA_3650
[5] https://forums.linuxmint.com/viewtopic.php?t=388011

[gablea]

I check to see what driver the kernel is using and it is using a gk_5000 but my graphics card is a intel i915

Your prior post's inxi output shows:

	driver: gma5001

That coincides with my understanding that your 2011 Intel D2700 Atom processor² is not supported by the i915, which is for Intel's mainline CPU/GPU series. The D2700 provides GMA3650^3,4 graphics, for which the gma500 driver exists, but providing questionable support⁵.

[1] https://en.wikipedia.org/wiki/Intel_GMA#GMA_500
[2] https://en.wikipedia.org/wiki/Intel_Atom
[3] https://www.techpowerup.com/gpu-specs/gma-3650.c3143
[4] https://en.wikipedia.org/wiki/Intel_GMA#GMA_3650
[5] https://forums.linuxmint.com/viewtopic.php?t=388011

Yea questionable is putting it mildly lol

If I put another vga card into the machine can I have dual
Screen that way?

Thinking about something like https://www.ebay.co.uk/itm/374067508670 ... BM0N7P7sJj

[mrmazda]

That single output card was introduced a month or so after Debian 2.0 24 years ago. Whether the r128 or mach64 drivers in Bookworm actually work I have no idea. I suggest for better likelihood of success you try to find dual output PCI Radeon 7500 or newer cards. When Trixie is finally released next year we may find none of mach64 or r128 are still available and functional. If they do still work, and if that happens, those boxes would be stuck in rather short order in an unsupported Debian release.

For 800x600 and 1024x768 you might get by with the crude fbdev or vesa drivers, but only if you could find a way to need only one display, or possibly to put two discrete GPUs in each box. I have no idea if dual discrete GPU cards so old were ever supported, much less currently.

If you can't find dual output PCI Radeons, you could possibly get by using dual output Matrox cards with the iffy mga driver that doesn't actually work in most distros except in much newer HP servers using a modified version of the old G200 GPU onboard. GeForce PCI cards with dual outputs might even be as good a bet as a Radeon, working with nouveau kernel driver and nouveau DDX driver.

[gablea]

So would a MSI ATI Radeon HD 5450 1GB PCI-E HDMI VGA DVI Low Profile card work ok?

[CwF]

So would a MSI ATI Radeon HD 5450 1GB PCI-E HDMI VGA DVI Low Profile card work ok?

ah, maybe no!
@mrmazda has mentioned PCI options, not pci-e, I think mrmazda knows the difference, make sure you know the difference gablea.

There exist HD5450 PCI that will work fine. I haven't tested old PCI cards recently but as mrmazda said early matrox and ati will generally work. I would stay away from late Nvidia PCI cards since their pci-e to pci chip needed to adapt the native pci-e gpu to the earlier pci bus has proven problematic.

I have used a HD5450 PCI in serverworks P3T (i686) boards as well as ati 7500/9x00 native PCI gpus.

[gablea]

So stay well away from PCI-E cards

[mrmazda]

So would a MSI ATI Radeon HD 5450 1GB PCI-E HDMI VGA DVI Low Profile card work ok?

It might. You haven't provided any specs on your base unit, so we don't know what kind of cards it supports, if any at all, or whether you need low profile or standard profile. My prior response was based upon your eBay selection of an ancient ATI Rage GPU card in PCI form factor. What model is your base unit? Does it provide any expansion slots? If yes, what type(s)? PCI? PCIe? If PCIe, what type(s)? X16? X8? X4? X1? If it has a PCIe X16 or X8 slot for low profile, then a low profile HD 5450 with passive cooler could be OK with a DP-to-HDMI adapter. I have two of them, an XFX, and a Sapphire. My cards provide DVI and HDMI ports on the card, and came with dongles providing VGA output. Ideally, since your cables are DP and DVI, you'd want a card that provides matching ports. My low profile Dell HD 6450 PCIe card has DP and DVI outputs. Perhaps eBay now has some more of those, if PCIe is what you need. Here's a full height model.

[gablea]

https://www.dieboldnixdorf.com/-/media/ ... nglish.pdf

This I think is the manual for my base unit.

[mrmazda]

That seems to support at most one expansion card via an optional riser card. You would need whatever form factor GPU card that the riser card supports. Looking at the available manual images, I expect that should be a full-height card. Whether a riser card is present in yours, or if not, one is available with a slot type matching an available GPU card, I can't tell from scanning that .pdf. Looks like you need to remove the cover and inspect.