F11 on Atom D510Mo - all good except screen resolution not correct

[jimbux]

As promised months ago, I chucked out an old coppermine PIII computer and built myself a new
inexpensive/low power computer to replace it. I chose the D510MO as the basis of the new machine.

Here's the smolt profile FYI.

Fedora11-x86_64 seems to install just fine on it. The only minor point seems to be that F11 isn't picking up the screen resolution of the monitor I'm using which is 1680x1050, it thinks the monitor is 1280x1024. The xorg.conf file at this point is fairly simple:

Section "Device"
	Identifier "Videocard0"
	Driver "vesa"
EndSection

I hunted around the forums, plus the intel website, to see if I could find a driver or "how to get it to work" posting for the onboard graphics chip (Intel GMA 3150 graphics controller) but to no avail.

I had installed F13 on the new D510MO machine earlier, and it picked up the graphics chip fine, so whatever improvements have been made to xorg (or whatever - I'm not sure) since F11 have allowed F13 to recognize the screen resolution properly. The problem is, all my other machines (I have quite a few) are F11 (requirement at this point) so I wanted to just keep things simple and have this new machine also be F11, so I installed F11 on it to see if I could get things working.

I tried just grabbing an xorg.conf file from another of my F11 machines and stripped out some nvidia specific stuff to see if I could just get it to work, but it ended up causing the graphics chip to slip into the 640x480 mode - worse obviously. Here's the new offending xorg.conf file as I tested it:

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "NEC"
    ModelName      "AccuSync LCD223WXM"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    DisplaySize    1680 1050
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Videocard0"
    Driver         "vesa"
EndSection

Section "Screen"
    Identifier     "Default Screen"
    Device         "Videocard0"
    Monitor        "Monitor0"
EndSection

So I'm at a bit of a dead end. My best choice was to ping you guys to see if anyone has any good tips on how to fix this. Another decent choice is to ignore the stretched screen, as I really don't care that much about the graphics (but now I'm curious to see if I can get it to work). Finally if I really feel like it's bugging me, I'll just reinstall F13 on the new machine.

First however... any ideas folks!? :-)

Thanks in advance - J.

[stevea]

The problem is, all my other machines (I have quite a few) are F11 (requirement at this point)

Write a new requirement spec. Spend a week upgrading. Seriously - I don't blame anyone for lagging a new release by a few months, but if you plan to migrate from F11 to F14 you are looking at a new-install level of effort. Sorry for the lecture, but you can't get much help with a distro that old.

There have been a lot of changes to Xorg since F11. Yes it now attempts to auto-identify the hardware for the X console, includes new X drivers for a lot of parts including your Intel GPU.

[jimbux]

Originally Posted by stevea

Write a new requirement spec. Spend a week upgrading. Seriously - I don't blame anyone for lagging a new release by a few months, but if you plan to migrate from F11 to F14 you are looking at a new-install level of effort. Sorry for the lecture, but you can't get much help with a distro that old.

There have been a lot of changes to Xorg since F11. Yes it now attempts to auto-identify the hardware for the X console, includes new X drivers for a lot of parts including your Intel GPU.

Thanks Stevea, good to know - I always appreciate your frankness.

Right now I can't upgrade from F11 (it's not the effort required stopping me, I don't mind knuckling down and doing it) - but at some point in the not too distant future (like 6 months?) I can probably just upgrade everything to F14, but I can't right now.

...however, I may just upgrade the Atom D510MO to F13 (or F14 in ...what, two weeks?), or I'll just live with a stretched screen for now.

As always - thanks for the help.