640x480 only res available after f14 - f20 upgrade?

[Ahmad Samir]

On 18 March 2014 00:16, Morgan Read <mstuff at read.org.nz> wrote:

> On 17/03/14 21:26, Bruno Wolff III wrote:
> > On Mon, Mar 17, 2014 at 21:21:57 +0000,
> >   Morgan Read <mstuff at read.org.nz> wrote:
> >>
> >> I'd really appreciate anybody pointing me in the right direction(s) - I
> >> suspect I've just not done something really straight forward as it seems
> >> very strange that this old HP ProLiant ML 150 and equally old Dell
> >> 1703FP monitor combo which worked fine under f14 now doesn't under f20.
> >
> > Does that monitor do EDID? If it doesn't or returns bogus information,
> > that could be what is triggering the problem. In which case using an
> > xorg.conf file to state the capabilities of your monitor might help.
>
>
> Hi Bruno, thanks for coming back to me.  This is from the Xorg.log:
> ...
> > [    22.238] (II) modesetting(0): Serial No: 2Y31741AD165
> > [    22.238] (II) modesetting(0): Monitor name: DELL 1703FP
> > [    22.238] (II) modesetting(0): Ranges: V min: 56 V max: 76 Hz, H min:
> > 30 H max: 80 kHz, PixClock max 145 MHz
> > [    22.238] (II) modesetting(0): EDID (in hex):
> > [    22.238] (II) modesetting(0):     00ffffffffffff0010ac103035363144
> > [    22.238] (II) modesetting(0):     020e01030e221b78ee8706a55c479c25
> > [    22.239] (II) modesetting(0):     1e4f54a54b00714f8180010101010101
> > [    22.239] (II) modesetting(0):     010101010101302a009851002a403070
> > [    22.239] (II) modesetting(0):     1300520e1100001e000000ff00325933
> > [    22.239] (II) modesetting(0):     3137343141443136350a000000fc0044
> > [    22.239] (II) modesetting(0):     454c4c203137303346500a20000000fd
> > [    22.239] (II) modesetting(0):     00384c1e500e000a202020202020001e
> > [    22.239] (II) modesetting(0): Printing probed modes for output VGA-0
> > [    22.239] (II) modesetting(0): Modeline "640x480"x75.0   31.50  640
> > 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
> > [    22.239] (II) modesetting(0): Modeline "640x480"x60.0   25.20  640
> > 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
> > [    22.239] (II) modesetting(0): Modeline "720x400"x70.1   28.32  720
> > 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
> > [    22.239] (II) modesetting(0): Output VGA-0 connected
> > [    22.239] (II) modesetting(0): Using exact sizes for initial modes
> > [    22.239] (II) modesetting(0): Output VGA-0 using initial mode
> > 640x480 +0+0
> > [    22.239] (II) modesetting(0): Using default gamma of (1.0, 1.0, 1.0)
> > unless otherwise stated.
> > [    22.239] (==) modesetting(0): DPI set to (96, 96)
> ...
> That looks like it does do EDID?
>
> I've done this to no effect in /etc/X11/xorg.conf.d :
> > 40-monitor.conf
> >
> > Section "Monitor"
> >   Identifier  "VGA1"
> >   Option      "PreferredMode" "1280x1024"
> > EndSection
> >
> > Restart your X system.
> >
> > If it doesn't work try creating the next two files in the same path, and
> restarting again:
> >
> > 30-graphic.conf
> >
> > Section "Device"
> >     Identifier      "Intel Integrated"
> >     Driver          "intel"
> > EndSection
> >
>

This machine doesn't have an intel chip, it's got a MGA G200E IIUC, c.f.
http://pci-ids.ucw.cz/read/PC/102b/0522 (that matches the PCI info from X
log you posted).

I am not an expert but looking at this patch
http://pkgs.fedoraproject.org/cgit/xorg-x11-drv-mga.git/tree/mga-1.6.2-fix-kms-matching.patch?h=f20

it looks like the mgag200 kernel module is automatically used on your
machine, check the output of 'lsmod'; and from the log indeed the
modesetting X11 driver is auto-configured.

I wonder if disabling KMS (booting with nomodeset or modeset=0 on the
kernel cmdline) would give better results (i.e. the system will use the mga
driver); you could try that, see what happens.



> > 50-screen.conf
> >
> > Section "Screen"
> >     Identifier      "Default Screen"
> >     DefaultDepth  24
> >     SubSection "Display"
> >             Depth          24
> >             Modes         "1280x1024"  "1024x768"   "640x480"
> >     EndSubSection
> > EndSection
>
> But, without any effect?
>
> What's so frustrating is that this used to work...
>
> Thanks,
> M.
> --
> Morgan Read
> NEW ZEALAND
> <mailto:mstuffATreadDOTorgDOTnz>
>
> Confused about DRM?
> Get all the info you need at:
> http://drm.info/
>
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>



-- 
Ahmad Samir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140318/f6223639/attachment.html>