Bug 614 - intel i810 chipset shows by default wrong resolutions
Summary: intel i810 chipset shows by default wrong resolutions
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-04-01 21:20 CEST by AL13N
Modified: 2011-10-01 09:57 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
xrandr (84.99 KB, image/png)
2011-04-01 21:26 CEST, AL13N
Details
how it looks (433.18 KB, image/jpeg)
2011-04-01 21:31 CEST, AL13N
Details

Description AL13N 2011-04-01 21:20:15 CEST
Description of problem:

even though it's configured as 1280x800 (correctly detected), it shows a smaller 4/3 version (1024x768) with black borders on the sides, but the kicker is still the correct size, which means you can't see all the buttons on the right side, as if the TV output was connected, checking xrandr, it shows that the TV output is indeed disconnected

after doing "xrandr --output LVDS1 --auto" it seems the disconnected TV output is then also disabled and returned to normal 1280x800. (see attached screenshots)

upon bootup, disconnected output should be disabled, so that the correct formats can be set. (possibly some kind of udev event could be triggered if an output would become connected.)

Reproducible: 

Steps to Reproduce:
Comment 1 AL13N 2011-04-01 21:26:15 CEST
Created attachment 183 [details]
xrandr
Comment 2 AL13N 2011-04-01 21:31:06 CEST
Created attachment 184 [details]
how it looks
Comment 3 Ahmad Samir 2011-05-06 16:09:54 CEST
As root:
monitor-edid

Keywords: (none) => NEEDINFO

Comment 4 José Jorge 2011-09-30 17:34:36 CEST
Is this still valid in current cooker?

CC: (none) => lists.jjorge

Comment 5 AL13N 2011-09-30 23:54:20 CEST
cooker? you'll mean cauldron? and i wouldn't know, i don't have the hardware anymore...
Comment 6 José Jorge 2011-10-01 09:57:54 CEST
cLosing as old so.

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


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