Bug 9084 - Wrong default screen resolution on Thinkpad T42p 1600x1200 installer and Live
Summary: Wrong default screen resolution on Thinkpad T42p 1600x1200 installer and Live
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-16 01:19 CET by Morgan Leijström
Modified: 2018-03-08 22:22 CET (History)
3 users (show)

See Also:
Source RPM: drakx-kbd-mouse-x11
CVE:
Status comment:


Attachments
Output of lspci -v (5.33 KB, text/plain)
2013-02-16 01:21 CET, Morgan Leijström
Details
Output of # monitor-edid -v --try-in-console (931 bytes, text/plain)
2013-05-05 00:37 CEST, Morgan Leijström
Details
Output of # dmidecode (13.20 KB, text/plain)
2013-05-05 00:38 CEST, Morgan Leijström
Details
bug.tar.gz install no screens found, cauldron 2015-09-26 (42.27 KB, application/octet-stream)
2015-09-26 23:06 CEST, Morgan Leijström
Details
report.bug.tar.gz of working mga5 network install (29.23 KB, application/octet-stream)
2015-09-27 00:12 CEST, Morgan Leijström
Details

Description Morgan Leijström 2013-02-16 01:19:32 CET
System: mga3 beta 2 Live i586 KDE installed and updated today.

Machine: Thinkpad T42p, with wonderful 1600x1200 wide angle screen.
The sticker say TYPE 2379-DXU, this seem to come with 1400x1050 display, but some are (factory?) rebuilt to 1600x1200

Description of problem:
Screen get configured as 1400x1050

Appearance: Without any changes, Rightmost 4 centimeters of screen is cluttered with tiny red lines that vibrates in intensity - pretty cool, but i need the area for real work... ;)

Observation: It looks like the desktop use the whole full resolution, but the pesky red lines are on top.

Workaround: opening mcc > hardware > graphics, i see resolution is set to 1400 x 1050 on both driver and monitor.  I change oth to 1600 x 1200, reboot and it is Fixed :)
Comment 1 Morgan Leijström 2013-02-16 01:21:52 CET
Created attachment 3520 [details]
Output of lspci -v
Comment 2 Morgan Leijström 2013-02-16 01:25:04 CET
# monitor-edid --MonitorsDB
give no output.

# monitor-edid
give no output either.
Comment 3 Morgan Leijström 2013-02-16 01:26:34 CET
I remember this have always been a problem since back in Mandriva.
Comment 4 Morgan Leijström 2013-02-16 01:38:48 CET
# monitor-probe radeon
Resolution: 1400x1050

HUH?  where do it get that from?!

I use this perfectly OK in 1600x1200, also in dual booted WinXP.

Of course as this model most often is 1400x1050 maybe the hardware itself report erroneously when equipped with the larger screen?  Bad design if so, as that parameter should better be stored in the screen...

When in MCC browsing hardware there is in unknown hardware (the last cathegory) the entry "âThinkPad T41p", containing:

Identifiering
Tillverkare: âIBM
Beskrivning: âThinkPad T41p
Diverse
Modul: âResolution:1400x1050

= Wrong computer model and wrong screen resolution
Manuel Hiebel 2013-02-16 16:45:01 CET

CC: (none) => guillomovitch, thierry.vignaud
Source RPM: (none) => drakx-kbd-mouse-x11

Comment 5 Morgan Leijström 2013-04-20 23:54:52 CEST
After a massive update it set itself to wrong resolution.
Had to set it right manually as in description.
Comment 6 Anssi Hannula 2013-05-03 20:26:06 CEST
Can you provide (as root) the output of:

monitor-edid -v --try-in-console

and:

dmidecode

Thanks.

CC: (none) => anssi.hannula

Comment 7 Morgan Leijström 2013-05-05 00:37:22 CEST
Created attachment 3888 [details]
Output of # monitor-edid -v --try-in-console

After full update + reboot right now, commands ran in KDE Terminal
Comment 8 Morgan Leijström 2013-05-05 00:38:14 CEST
Created attachment 3889 [details]
Output of # dmidecode
Comment 9 Anssi Hannula 2013-05-05 01:01:32 CEST
I guess your "lspcidrake -v" says 1400x1050 as well?

@Thierry, do you remember off-hand where that info is gathered from?
Comment 10 Morgan Leijström 2013-05-06 10:47:01 CEST
lspcidrake - v do no tell any resolution.  The only relevant line i see is:

Card:ATI r300/r400/r500 based FireGL: Advanced Micro Devices [AMD] nee ATI|RV350/M10 [Mobility FireGL T2] [DISPLAY_VGA] (vendor:1002 device:4e54 subv:1014 subd:054f) (rev: 80)
Comment 11 Thierry Vignaud 2013-05-06 22:55:41 CEST
(In reply to Anssi Hannula from comment #9)
Did you mean the last field of /usr/share/ldetect-lst/MonitorsDB?
The file structure initially came from RH (which actually dropped it (least year?).
We replaced the unused last field by the resolution.
It was filled manually either by Pixel or me on demand.
Comment 12 Samuel Verschelde 2015-05-06 19:49:32 CEST
Morgan, Anssi, Thierry, what's the status in Mageia 4 and cauldron ?

Keywords: (none) => NEEDINFO

Comment 13 Morgan Leijström 2015-05-07 08:58:43 CEST
I will do a clean install of mga5 on that same laptop.
(but not very soon)
Comment 14 Marja Van Waes 2015-09-22 20:49:49 CEST
(In reply to Samuel VERSCHELDE from comment #12)
> Morgan, Anssi, Thierry, what's the status in Mageia 4 and cauldron ?

(In reply to Morgan Leijström from comment #13)
> I will do a clean install of mga5 on that same laptop.
> (but not very soon)

And?

CC: (none) => marja11

Comment 15 Morgan Leijström 2015-09-23 09:29:08 CEST
Oh, that machine is collecting dust... charging it now

@Anssi, @Thierry :What would give you best input: 
§ mga5 DVD .iso install, 
§ mga5 network install, or
§ cauldron network install?
Comment 16 Morgan Leijström 2015-09-26 23:04:07 CEST
Cauldron network install, using nonfree boot iso and stage 2 downloaded today:
 in stage 2, X fail to start ! (no screens found) = raising to critical.

The install script then guess it worked anyhow and thinks it displays the step select language.  Is that another bug or is that by design?

Output of # monitor-edid -v --try-in-console is exactly as in comment 7 & 8.

Keywords: NEEDINFO => (none)
Severity: normal => critical

Comment 17 Morgan Leijström 2015-09-26 23:06:32 CEST
Created attachment 7055 [details]
bug.tar.gz install no screens found, cauldron 2015-09-26
Comment 18 Morgan Leijström 2015-09-27 00:05:42 CEST
Mageia network install works, using nonfree boot iso and stage 2 downloaded today:
Same issues as in comment 10 and above.

So the state for mga 5 is not critical

I can not tell if on Cauldron X fail to launch because of wrong monitor assumtions, or other reasons.  Someone more knowledgeable need to have a look in attachement 7055.
Morgan Leijström 2015-09-27 00:07:08 CEST

Summary: Wrong default screen resolution on Thinkpad T42p 1600x1200 => Wrong default screen resolution on Thinkpad T42p 1600x1200 & X in mga6 installer fail

Comment 19 Morgan Leijström 2015-09-27 00:12:41 CEST
Created attachment 7056 [details]
report.bug.tar.gz of working mga5 network install

Bug output from the begining (X start and language selected) of working mga5 network install (wrong resolution but installer works) , proceeding just a bit longer than the previous output from mga6 where X failed to start.
Comment 20 Morgan Leijström 2015-09-27 01:49:21 CEST
In mga5 running KDE all is OK.
I think read somewhere that KDE sets resolution by itself by some method - is that correct?

But some other DE do not do that?

Which should i try?  (some that rely in what the installer had set, so we can see if it is wrong or correct)
Comment 21 Morgan Leijström 2015-09-27 01:51:22 CEST
Clarifying comment 18 first word "Mageia" -> "Mageia 5" (i forgot the "5")
Comment 22 Morgan Leijström 2016-05-09 09:02:30 CEST
The status for Mageia6 cauldron is same as for mga5 comment 20:

Fresh install cauldron mageia6 today.

The installer is using wrong resolution during install but that is no real problem itself; readable but a tiny bit blurry text.

I let it proceed fully by default

MCC say it is wrongly set to Flat Panel 1400x1050

But KDE use correctly 1600x1200 resolution automatically anyway
So at least for KDE users all is OK
I degrade issue severity to normal.

For own reference: i now set MCC manually to Flat Panel 1600x1200

Severity: critical => normal

Samuel Verschelde 2016-10-15 21:58:58 CEST

Assignee: bugsquad => mageiatools

Guillaume Rousse 2016-10-16 16:11:13 CEST

CC: guillomovitch => (none)

Comment 23 Morgan Leijström 2017-06-07 22:06:29 CEST
Test of Live Mageia 6 RC i586 xfce on same machine as in comment 0
And it works exactly as in comment 0:
Slightly blurry and settings say it is 1400x1050, but hardware expands to full screen and rightmost 4 cm is garbled (but see-through enough so you can find and use scrollbars etc.)

Summary: Wrong default screen resolution on Thinkpad T42p 1600x1200 & X in mga6 installer fail => Wrong default screen resolution on Thinkpad T42p 1600x1200 installer and Live

Comment 24 Morgan Leijström 2018-03-08 22:03:20 CET
Test of final mga6 Live xfce i586: same fail as comment 23.

Additionally testing installed system updated today: Full OK;
correct resolution in Xfce, Plasma5.8, and also Plasma5.12 from testing OK.
Comment 25 Morgan Leijström 2018-03-08 22:22:22 CET
As before monitor-probe radeon returns wrong resolution 1400x1050
Which seem to be used by installer and live.

I have no idea how the installed system get it right and automatically use the correct 1600x1200, but however it do that it would on this machine be good if installer and live use that method...

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