Bug 28817 - My multiple screens don't works anymore after Mageia 8 maj or install from scratch.
Summary: My multiple screens don't works anymore after Mageia 8 maj or install from sc...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: IN_ERRATA8
Depends on:
Blocks:
 
Reported: 2021-04-20 21:50 CEST by Jean-François Bachelet
Modified: 2021-04-28 10:38 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jean-François Bachelet 2021-04-20 21:50:54 CEST
Description of problem:
Under MGA7.1 I've configured my computer to have two screens each on its own monitor. that was working fine.

but after MGA8 maj or inew install that is not working anymore.
the virtual desks applet work and show all two parts for eaxch desk like before and mouse is able to goi to the second screen.

But the second screen stays black with nothing visible.

that's a real problem 'cause I've changed nothing since except MGA version.

I need that two screens config to work.


Version-Release number of selected component (if applicable):
latests

How reproducible:
just put a graphiucs card and connect two display to it and try to have something on the two screens after the login screen... me I get only an unusable  black screen...
Jean-François Bachelet 2021-04-20 21:51:11 CEST

Priority: Normal => High
CC: (none) => jfbachelet
Severity: normal => major

Comment 1 Morgan Leijström 2021-04-21 12:04:37 CEST
Which desktop environment do you use?

If Plasma, are both screens seen in Hardware > monitor?
What happens if you play around with settings there?

I dont know how other desktops handle screens, but some have similar controls.

CC: (none) => fri

Comment 2 Jean-François Bachelet 2021-04-21 18:55:19 CEST
(In reply to Morgan Leijström from comment #1)
> Which desktop environment do you use?
> 
> If Plasma, are both screens seen in Hardware > monitor?
yes, it are there. and recognized fine for what it are (brand and model)

> What happens if you play around with settings there?
nothing more, asking for 'identification' of screens show just the left screen, the right one stays black.

I've tried to get a screen grab of the desktop and the two screens are shown in it with their background pic... so the screen is definitely open in memory but NOT on the second display.
Comment 3 Aurelien Oudelet 2021-04-21 19:35:36 CEST
Hi thanks reporting this.

As I also have 2 monitors setup with a single GPU (nvidia), under Plasma Desktop,
One is DisplayPort and the second is HDMI.

I wonder your type of connection for your setup.

Have you tried connecting, reconnecting ?
Have you tried to change cable?
Have you tried to change the port on the graphic card ?

So, this is not a Plasma bug, not a packaging bug.


Try also to remove in ~/.config/ kscreenrc file. And reboot.

Severity: major => normal
CC: (none) => ouaurelien
Priority: High => Normal

Comment 4 Jean-François Bachelet 2021-04-21 22:37:29 CEST
(In reply to Aurelien Oudelet from comment #3)
> Hi thanks reporting this.
> 
> As I also have 2 monitors setup with a single GPU (nvidia), under Plasma
> Desktop,
> One is DisplayPort and the second is HDMI.
> 
> I wonder your type of connection for your setup.
left monitor is HDMI and right one VGA, that was working fine in MGA7.1.

> 
> Have you tried connecting, reconnecting ?
yes

> Have you tried to change cable?
cables are new and work perfectly with other stuff that this one

> Have you tried to change the port on the graphic card ?
sorry no ports left on this radeon R7 250 with Oland chipset

> 
> So, this is not a Plasma bug, not a packaging bug.
weel, seems it is for me, as I just see the rigt screen functional 'by miracle'
at the favour of a input switching from HDMI to VGA input.

just to verify if that was the last updates that've cured the problem I've rebooted and... never seen the right screen working since again...

there is a bug somewhere.
> 
> 
> Try also to remove in ~/.config/ kscreenrc file. And reboot.
I have no 'kscreenrc file there, only kscreenlockerrc, kserverrc, and kwinrc...
Comment 5 Jean-François Bachelet 2021-04-22 13:13:10 CEST
just a note to add, when I've seen the right screen on with is desktop shown the left one was decalled and approx 10 pixel on the right screen...

but since after moult resets I still have the right screen not working again :(
Comment 6 Aurelien Oudelet 2021-04-22 22:08:08 CEST
The path to set multiple monitors with Plasma is in:

systemsettings5 => Hardware => Display and Monitor => Display Configuration
It should see you 2 monitors.

If not, Please remove any customization made by hand in /etc/X11/xorg.conf
ditch all Xinerama stuff, leave at least just 1 monitor.

Normally all is done automatically.


Did you ever try with a fresh and newly user account?
Comment 7 Jean-François Bachelet 2021-04-23 00:34:38 CEST
(In reply to Aurelien Oudelet from comment #6)
> The path to set multiple monitors with Plasma is in:
> 
> systemsettings5 => Hardware => Display and Monitor => Display Configuration
> It should see you 2 monitors.
it does sees it both

> 
> If not, Please remove any customization made by hand in /etc/X11/xorg.conf
> ditch all Xinerama stuff, leave at least just 1 monitor.
> 
> Normally all is done automatically.
> 
> 
> Did you ever try with a fresh and newly user account?
yes as I have reinstalled all MGA8 from scratch... and let the screen stuff appart when recopying my prefs. so all stuff plasma wise is new
Comment 8 Jean-François Bachelet 2021-04-24 08:41:59 CEST
Question :

I have this in the boot messages : 'kfd kfd : Oland not supported in kfd'

so, what is kfd and as Oland is the chipset of my Radeon R7 250x card, could this be the cause of that non fonctionning multi screens ?

and second, why ??? under MLGA7.1 I've never seen that message, that would be very idiot to have dropped support for good graphic cards (especially as we shout supporting 'old hardware'...
Comment 9 Aurelien Oudelet 2021-04-24 18:53:06 CEST
@ reporter,
Was screen disposition OK with Kernel 5.10 under Mageia 7?

Can you provide us:
$ inxi -AaGS

Assignee: bugsquad => kernel

Comment 10 Dave Hodgins 2021-04-24 21:27:07 CEST
(In reply to Jean-François Bachelet from comment #8)
> I have this in the boot messages : 'kfd kfd : Oland not supported in kfd'
> so, what is kfd and as Oland is the chipset of my Radeon R7 250x card, could
> this be the cause of that non fonctionning multi screens ?

On my Mageia 8 laptop with an amd gpu built into the cpu and a discreet nvidia
gpu, it has the following messages about in "journalctl --no-hostname -b" ...
Apr 24 15:06:25 kernel: kfd kfd: Allocated 3969056 bytes on gart
Apr 24 15:06:25 kernel: Virtual CRAT table created for GPU
Apr 24 15:06:25 kernel: amdgpu: Topology: Add dGPU node [0x1636:0x1002]
Apr 24 15:06:25 kernel: kfd kfd: added device 1002:1636
Apr 24 15:06:25 kernel: amdgpu 0000:06:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 18, active_cu_number 27

gart is explained at ...
https://en.wikipedia.org/wiki/Graphics_address_remapping_table

I'll leave the debugging to the kernel team, as I have no other info about this.

CC: (none) => davidwhodgins

Comment 11 Jean-François Bachelet 2021-04-25 04:19:02 CEST
(In reply to Aurelien Oudelet from comment #9)
> @ reporter,
> Was screen disposition OK with Kernel 5.10 under Mageia 7?
> 
> Can you provide us:
> $ inxi -AaGS

# inxi -AaGS
System:    Host: localhost Kernel: 5.10.30-desktop-1.mga8 x86_64 bits: 64 compiler: gcc 
           v: 10.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.30-desktop-1.mga8 
           root=UUID=f75a7430-dc34-49c5-8017-a9deb44fe87b ro splash quiet noiswmd 
           resume=UUID=7431c940-d9d3-4fd1-bffd-210387068967 audit=0 vga=791 
           Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM 
           Distro: Mageia 8 mga8 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0102 
           Device-2: AMD Oland XT [Radeon HD 8670 / R5 340X OEM / R7 250/350/350X OEM] 
           vendor: PC Partner Limited driver: amdgpu v: kernel alternate: radeon 
           bus ID: 02:00.0 chip ID: 1002:6610 
           Display: x11 server: Mageia X.org 1.20.11 compositor: kwin_x11 driver: amdgpu,v4l 
           display ID: :0 screens: 1 
           Screen-1: 0 s-res: 3839x1080 s-dpi: 96 s-size: 1013x285mm (39.9x11.2") 
           s-diag: 1052mm (41.4") 
           Monitor-1: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           Monitor-2: VGA-0 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           OpenGL: renderer: AMD Radeon HD 8600 Series (OLAND DRM 3.40.0 
           5.10.30-desktop-1.mga8 LLVM 11.0.1) 
           v: 4.6 Mesa 21.0.2 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] 
           vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 02:00.1 
           chip ID: 1002:aab0 
           Sound Server: ALSA v: k5.10.30-desktop-1.mga8
Comment 12 Jean-François Bachelet 2021-04-25 15:27:38 CEST
(In reply to Jean-François Bachelet from comment #11)
> (In reply to Aurelien Oudelet from comment #9)
> > @ reporter,
> > Was screen disposition OK with Kernel 5.10 under Mageia 7?

oups forgoten to answer that !

Yes it was working perfectly, I just had a little  problem to find all the functions to setup the multiple screens in synch (different models monitors) as it are spread accross a lot of prefs utilities...

at least on AmigaOS we have only one screen prefs tool for all possible configurations ;)
Comment 13 Jean-François Bachelet 2021-04-27 12:31:01 CEST
well, did you find why kfd doesn't support Oland in MGA8 while it was definitely in MGA7.1 ?
Comment 14 Thomas Backlund 2021-04-27 12:49:45 CEST
(In reply to Jean-François Bachelet from comment #4)

> left monitor is HDMI and right one VGA, that was working fine in MGA7.1.
> 

This is the issue.

We default to amdgpu now for all gpus it supports as that is the driver with active upstream support and enhancements (radeon is in "low maintenance mode")
https://wiki.mageia.org/en/Mageia_8_Errata#AMD.2FATI

But...amdgpu does not properly handle legacy VGA yet (there is something in the works, but nothing usable yet)

so to revert back to mga7 behaviour of defaulting to radeon/ati setup, you need to add the following to kernel command line:


radeon.si_support=1 amdgpu.si_support=0

If you have a xorg.conf you have to edit it to change "amdgpu" to "ati"
Comment 15 Jean-François Bachelet 2021-04-27 22:42:44 CEST
(In reply to Thomas Backlund from comment #14)

> so to revert back to mga7 behaviour of defaulting to radeon/ati setup, you
> need to add the following to kernel command line:
> 
> 
> radeon.si_support=1 amdgpu.si_support=0
> 
> If you have a xorg.conf you have to edit it to change "amdgpu" to "ati"

Ahhh ! that did the trick, I've my second screen on now :)

but I still see 5 to 10 pixels of the left screen recopied at the beginning of the right one...

Thanks.

BTW I hope amdgpu will be fully working soon too ^^)

I pick 'resolved' for now.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 16 Jean-François Bachelet 2021-04-27 22:46:19 CEST
Note : the portion of the left screen copied to the right display doesn't appear if I grab the Big screen (the two panels if full)... on the grab the two backgrounds are perfect fit.
Comment 17 Morgan Leijström 2021-04-28 10:38:58 CEST
Thank you Jean-Francois for reporting, and Thomas for explaining.

I have now added a note on the VGA problem to the existing note in the errata section Thomas referenced.

Keywords: (none) => IN_ERRATA8


Note You need to log in before you can comment on or make changes to this bug.