Hardware used: - Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|GP108 [GeForce GT 1030] [DISPLAY_VGA] (rev: a1) - Screen: IIYAMA ProLite XB3070WQS With Mageia 7.1 my screen worked perfectly at 2560x1600 (16/10). With Mageia 8, after a fresh install, I had a resolution of 2048x1152 which is a 16/9 ration instead of 16/10. I have tried to modify it with MCC and I have lossed the graphic screen. Then with drakx11 (text mode), I had more sucess, but it works now only with 1920x1080 (16/9) after starting it with the command startx. I have tried this with a these configurations of mother card and graphic cards: - Intel i5 and GT730 - Intel i5 and GT1030 - AMD Rysen 5 and GT1030 In each case (installed or live), the problem is the same.
Hi, thanks reporting this. I don't see anything in X11, Plasma or Mesa release notes that will prevent 16:10 ratio screen to be used. Do you use "automated" mode? Try also to remove /etc/X11/xorg.conf to let X11 to be in complete automated mode. But, sometimes the Devil resides in details: perhaps now the EDID parser detect wrong resolution from your monitor. How the monitor is connected to the graphic card? HDMI? DVI? VGA? DisplayPort?
CC: (none) => ouaurelien
I have removed xorg.conf and restart the graphic mode with startx. The resolution is now 2048x1152 at 60 Hz (16/9) I use DVI-D which works perfectly with Mageia 7. HDMI is not better.
I use now the "automated" mode without xorg.conf but the resolution 2560x1600 and the ratio 16/10 are not obtained as they was with mageia 7. Live or DVD install give also 2048x1152 (16/9) which is not correct. Is there any documentation to understand how "automated" mode works? I wish to investigate but how and where ?
Unsure where to assign this first. I thought drivers issues or EDID parsing?
Assignee: bugsquad => kernel
Component: Installer => RPM Packages
(In reply to Pierre Jarillon from comment #3) > Is there any documentation to understand how "automated" mode works? > I wish to investigate but how and where ? # monitor-get-edid|monitor-parse-edid
CC: (none) => davidwhodgins
Thanks, I discover these programs (root is not necessary) ------------------------------------------ $ monitor-get-edid | monitor-parse-edid Name: PL3070WQ EISA ID: IVM7601 EDID version: 1.3 EDID extension blocks: 1 Screen size: 64.1 cm x 40.1 cm (29.77 inches, aspect ratio 16/10 = 1.60) Gamma: 2.2 Digital signal Max video bandwidth: 310 MHz HorizSync 30-103 VertRefresh 55-76 # Monitor preferred modeline (60.0 Hz vsync, 98.7 kHz hsync, ratio 16/10, 101 dpi) ModeLine "2560x1600" 268.5 2560 2608 2640 2720 1600 1603 1609 1646 -hsync +vsync # Monitor supported modeline (60.0 Hz vsync, 100.0 kHz hsync, ratio 16/9, 114x102 dpi) (bad ratio) ModeLine "2880x1620" 303.88 2880 2928 2960 3040 1620 1623 1628 1666 -hsync +vsync # Monitor supported modeline (60.0 Hz vsync, 88.8 kHz hsync, ratio 16/9, 101x91 dpi) (bad ratio) ModeLine "2560x1440" 241.5 2560 2608 2640 2720 1440 1443 1448 1481 -hsync +vsync $ ------------------------------------------ This is perfect. But the installer (or drakx11) don't use these indications (Mageia 7 does it). The preferred modeline is exactly the same than in xorg.conf for Mageia 6. xorg.conf of Mageia 7 don't have this modeLine, but it works! What is the next step?
It shows that there is nothing wrong with the edid being returned from the monitor. I'd try installing task-xfce-minimal, creating a new user, and then logout/in with the new user using xfce instead of plasma, and see if the resolution is correct then. I remember from back when I had a crt monitor, that kde would override whatever was defined in xorg. I don't know if that's still a problem. If it works in xfce, check in plasma for that new user. The purpose of these tests are to see if it's a kernel/driver problem, a plasma problem, or a plasma/user config problem.
I have installed task-xfce-minimal and create a new user toto. There is no xorg.conf and the login is in text mode (no sddm) When toto uses startxfce4, the display is 1920x1080 (16/9) When pierre uses startx, the display is 2048x1152 (16/9)
Created attachment 12667 [details] xorg.conf generated with MCC systemsettings5 shows always the current name of the screen and the current resolution. With MCC - drakx11, without proprietary driver, it offers the correct parameters and generate a nice xorg.conf (in attachment) but startx makes a black screen.
Created attachment 12668 [details] startx output After using drakx11, I have run startx which shows a black screen. Here is the output. I have stripped hundreds tabs (^I) and spaces and CR to be readable. The owner of /home/pierre/.Xauthority was root. I had to remove the new created xorg.conf to avoid the black screen and get a plasma session 2048x1152.
Thanks Pierre. That rules out plasma or config issues, so it's clearly in the realm of the kernel and video drivers. The bug is already assigned to that team. Hopefully one of them will be able to figure out how to fix the screen ratio being displayed so it reflects what the edid prefers.
Hi there, I am running mageia 8 in 16:10 with nvidia card without problem, but I am on digital port (DP). Pierre, could you report the output of "xrandr", I may be able to help.
CC: (none) => eatdirt
NB: you don't use nvidia proprietary drivers on purpose?
Created attachment 12672 [details] Output of xrandr Good idea! We're getting closer ... xrandr gives values that disagree with monitor-get-edid. The values of xrandr strike me as fanciful.
Hum. Duh! As long as KScreen from Plasma relies on xrandr function, there is nothing to teach plasma5... I wonder if there is some incorrect nvidia settings in your home directory. Please remove all .nvidia files or directory at root of your user directory.
They are already renamed: .nv-xxx/ and .nvidia-settings-rc-xxx I did this before opening the bug report. In reply to Chris Denice - Comment 13 I wish to use the nvidia driver, but it it not usable for the moment. It provides locks and crashes as much you want. Nouveau is more robust, happily! I'll try nvidia again as soon as it will be possible.
(In reply to Pierre Jarillon from comment #16) > They are already renamed: .nv-xxx/ and .nvidia-settings-rc-xxx > I did this before opening the bug report. > > In reply to Chris Denice - Comment 13 > I wish to use the nvidia driver, but it it not usable for the moment. It > provides locks and crashes as much you want. Nouveau is more robust, happily! > I'll try nvidia again as soon as it will be possible. Hardware used: - Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|GP108 [GeForce GT 1030] Hum, nvidia nonfree driver should give you the correct resolution. Nouveau driver perhaps can not have all nonfree driver functionalities. According to freedesktop.org: Nvidia Geforce GT 1030 is NV130 family (Pascal) Code name Official Name NV132 (GP102) NVIDIA Titan (X, Xp), GeForce GTX 1080 Ti NV134 (GP104) GeForce GTX (1070, 1080) NV136 (GP106) GeForce GTX 1060 NV137 (GP107) GeForce GTX (1050, 1050 Ti) NV138 (GP108) GeForce GT 1030 and https://nouveau.freedesktop.org/FeatureMatrix.html Nouveau lacks videod decoding (vdpau) and Power Management feature. But I don't see any defect for xrandr... Upstream bug? Nouveau was good under Mageia 7?
With Mageia 7, I can use nvidia or nouveau. Both automatically select 2560x1600. I have always the system partitions of mga6 and mga7. According to xorg.conf, mga6 uses nouveau and mga7 uses nvidia. I have also tried mga7-live with nvidia and nouveau. Both are good. This is not the case with mageia 8, live or not.
Adding Giuseppe Ghibò, who recently package NVIDIA drivers. @Guiseppe, any idea here?
CC: (none) => ghibomgx
Created attachment 12689 [details] When xrandr shows 2560x1600 ... with mga6! With my second computer which has also a card nvidia GeForce 1030, I succeed to boot with my old Mageia 6. The screen worked perfectly at 2560x1600. xrandr is also correct and shows 2560x1600. If I boot with mga7 (updated) I have only 2048x1152 @ 60.00 Hz As the LiveMageia 7 works well, it seems that the problem has occured during the life of Mageia 7.
There is now a newer nvidia-current-460.73.01-1.mga8.nonfree in testing https://bugs.mageia.org/show_bug.cgi?id=28854
Thanks Thomas! As soon as I can get the rpm on my mirrors, I'll try it. Is there some recommendation or procedure to set up this new package?
The packages installed are now: # rpm -qa "*nvidia*" nvidia-current-cuda-opencl-460.73.01-1.mga8.nonfree x11-driver-video-nvidia-current-460.73.01-1.mga8.nonfree dkms-nvidia-current-460.73.01-1.mga8.nonfree lib64nvidia-egl-wayland1-1.1.5-3.mga8 nvidia-current-utils-460.73.01-1.mga8.nonfree nvidia-current-doc-html-460.67-1.mga8.nonfree drakx11 shows now PL3070WQ and 2560x1600 but the resolution is still 2148x1152, value also given by xrandr. If automatic graphic display is enabled, sddm locks... I continue to use startx.
What is the output of /var/log/Xorg.0.log in both cases? According to your xrandr outputs, it says you are using a DVI-D connection, while on mga6 you are using the DisplayPort. Your monitor supports DVI, HDMI 1.4 and DisplayPort 1.2. The DisplayPort connection is also the one allowing the highest bandwidth. Probably the DVI-D is single-link connection and hasn't enough bandwidth to support 2560x1600. I'd try disconnecting the DVI cable if you have connected both and use only the DisplayPort.
I have 2 desktop gaina and azkar (basque words) - gaina : i5, GP108 (GeForce GT 1030) hdmi + DP, Screen iiyama E2607 1920x1200 mga 7, mga 6 - azkar : Rysen 5, GP108 [GeForce GT 1030] hdmi + DVI, iiyama XB3070WQS 2560x1600 mga8 With azkar, my main desktop, I have unplugged DVI and use HDMI. The result is not good: $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 641mm x 401mm With this card, the best result has never been with hdmi. I have also a DVI cable which gives poor results. I have tried all combinations with my hardwares. I am sure that DVI, the cable and the screen can work at 2560x1600 as they did it. Now, with the newer nvidia-current-460.73, nvidia works, I can see mp4 videos. Before, this was not viewable... I have problems with .Xauthority. I wonder if my configuration is always truely configurable.
I am back to DVI-D-0 connected primary 2048x1152+0+0 When I call startx, I have always such messages: /home/pierre/.serverauth.76983 does not exist xauth: file /home/pierre/.serverauth.77091 does not exist xauth: timeout in locking authority file /home/pierre/.Xauthority xauth: timeout in locking authority file /home/pierre/.Xauthority After 3 timeouts, the graphic session starts.
You can compare the two /var/log/Xorg.0.log between the cases where it was working and where it isn't. Also checks at kernel journal to see whether there is some strange message during the timeouts. File permissions for your $HOME are correct? As for bandwidth, maybe (it's just an hyptothesis) it tries to automatically use the 30bit (10bit per component) that your 2560x1600 monitor support, so there could be not enough bandwidth in this mode at this depth for DVI. Maybe in the older distro drivers these extra features were not detected. The 30" monitor hasn't the DisplayPort? What if you swap monitor or cable between the two hosts? If you suspect of a problem with nvidia 460.xx series, you might try to uninstall the nvidia-current driver, and try once with nvidia390 series, and see what happens. The Nvidia GeForce 1030 (unless of some particular variant) is supported by both nvidia-current and nvidia390.
Now with nvidia390, startx cannot start. I have reinstalled nvidia-current-460.73.01-1.mga8.nonfree. $ xrandr Screen 0: minimum 320 x 200, current 2048 x 1152, maximum 16384 x 16384 DVI-D-1 connected primary 2048x1152+0+0 (normal left inverted right x axis y axis) 641mm x 401mm 2560x1600 59.97 + 2560x1600_60 60.00 2048x1152 60.00* ........ Note + and * ______________________________________ I have also tried to use my "old" desktop I wish to give to one of my grandsons. It is a fresh installed of mga8, fully updated. I have used the same DVI cable. Card:NVIDIA GeForce 420 to GeForce 630: NVIDIA Corporation|GF108 [GeForce GT 730] [DISPLAY_VGA] (rev: a1) On hdmi, it gives 1920x1080 and on DVI it gives perfect 2560x1600px! $ xrandr Screen 0: minimum 8 x 8, current 2560 x 1600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) VGA-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 641mm x 401mm 2560x1600 59.97*+ 2880x1620 60.00 2560x1440 59.95 ........ Note + and * ______________________________________ You are right, a problem with nvidia 460.xx series cannot be excluded. The GT1030 of gaina is made by MSI (HDMI + DP) ~ 1 year old. (Mother card MSI) The GT1030 of azkar is made by Gigabyte (HDMI + DVI) just bought (M.C. Gigabyte) I'll install mga8 on gaina (which still use mga7) and try DP.
On gaina : i5, GP108 (GeForce GT 1030) MSI, DP, Screen iiyama XB3070 1- mga8 live => 2560x1600 2- mga8 new install (without any update) => 2560x1600 $ xrandr Screen 0: minimum 8 x 8, current 2560 x 1600, maximum 32767 x 32767 DP-0 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 641mm x 401mm 2560x1600 59.97*+ On azkar, Rysen 5, MB and GT 1030 Gigabyte, I have reinstalled 4 or 5 times without success. Then I have a last operation to do: interchange the video cards. Is there a way to investigate further?
To investigate further you need to compare and look the various /var/log/Xorg.0.log of each installation. xrandr --prop --verbose can also show further info about current connection. Maybe you can try with also with better quality HDMI cable (e.g. certified for HDMI 1.4 or 2.0b).
Now the video card MSI is on the mother board Geforce and I have a correct screen at 2560x1600 (16/10). I just notice that the videos are more fluid with the user toto than with pierre. I wonder what is wrong in my config. My local problem is solved, but IMO there is always a problem with the Gigabyte video card. Is this only for my card or for all Gigabyte GT1030 cards ? What may I do ?
xrandr --prop --verbose is very impressive! But difficult to understand all. The newer Gigabyte video card works now in gaina at 1920x1200 The oldest MSI card works in azkar at 2560x1600 I have searched on Internet and I have found some problems related to this card where a resolution of 2560x1440 or 2560x1600 is reported as unreachable... Even with Windows! My opinion is that the problem is related to Gigabyte.
As experiment you can try instead of 2560x1600 at 60Hz, 2560x1600 at 30Hz (adding the entries for 30Hz frequency) to see whether it's a problem of bandwidth.
Created attachment 12694 [details] Differences between two cards GT1030 on the same display With the same screen, the card Gigabyte on I5 (MSI Main board), DVI port gives a shorter output than MSI video on Rysen5 (Gigabyte Main board). One card (Gigabyte) uses DVI and the other DP. They are better than their HDMI. In both cases, they give a good display of 2560x1600 px. The cables are goods and there is no problem of bandwidth. I have just a problem on my main computer, video are not as fluid as they are with another user... But this is another problem related to the tests I have done.
Now I have cleaned a lot of files related to nvidia in /var/cache/urpmi/rpms/ and loaded the nvidia non-free driver. Videos in full screen are fluid and Pysol is no longer jerky and works smoothly. Note that this was a fresh and default installation on a new empty SSD. In my opinion, the problem is still there. As my problem is locally solved, must I close the bug?
Yes, close this bug. In my opinion, there might be a problem with the nouveau driver for such resolutions and the 16:10 format. We're not so many using it, although it is far better than 4:3 and 16:9. I'll test on my side with nouveau an reopen a more targeted bug if I find issues.
Closing as fixed for now... Nouveau will always have some issues as pretty much all bits are done without help or even basic info from nVidia so ... This is one of the reasons I switched from nVidia to AMD as AMD is way better nowdays in working with upstream linux / open source integration
Status: NEW => RESOLVEDResolution: (none) => FIXED
Good to now, thanks Thomas!