Bug 9084

Created attachment 3520 [details]
Output of lspci -v

# monitor-edid --MonitorsDB
give no output.

# monitor-edid
give no output either.

I remember this have always been a problem since back in Mandriva.

# 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

After a massive update it set itself to wrong resolution.
Had to set it right manually as in description.

Can you provide (as root) the output of:

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

and:

dmidecode

Thanks.

CC: (none) => anssi.hannula

Created attachment 3888 [details]
Output of # monitor-edid -v --try-in-console

After full update + reboot right now, commands ran in KDE Terminal

Created attachment 3889 [details]
Output of # dmidecode

I guess your "lspcidrake -v" says 1400x1050 as well?

@Thierry, do you remember off-hand where that info is gathered from?

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)

(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.

Morgan, Anssi, Thierry, what's the status in Mageia 4 and cauldron ?

Keywords: (none) => NEEDINFO

I will do a clean install of mga5 on that same laptop.
(but not very soon)

(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

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?

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

Created attachment 7055 [details]
bug.tar.gz install no screens found, cauldron 2015-09-26

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.

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.

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)

Clarifying comment 18 first word "Mageia" -> "Mageia 5" (i forgot the "5")

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

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

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.

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...