I used the line xconfig --startxonboot --hsync "31-60" --vsync "50-80" in my ks.cfg file but got HorizSync 35.15 VertRefresh 55-65 in XF86Config!? Moreover, it did only set up ----------------------------- DefaultColorDepth 16 Subsection "Display" Depth 16 Modes "800x600" ViewPort 0 0 EndSubsection ------------------------------- Is there a way of specifying the mode/depth in the ks.cfg file?
According to the kickstart documentation, there is currently no way to specify color depth through kickstart. Not a bad idea, though, for future development. I'm looking into the sync rates problem.
The sync problem appears in RHL 7.0 too, so this issue isn't new.
Wait a minute...this did work in 7.0. I tested against the wrong version.
Actually, this works in Wolverine. Here's the line from ks.cfg: xconfig --startxonboot --hsync "31-60" --vsync "50-80" And here's the output in XF86Config-4 HorizSync 31-60 VertRefresh 50-80
(1) If the installer only sets up 800x600 the xconfiguration is useless!!!!! I guess most people will want to have at least 1024x768 these days! (2) I am not talking about XF86Config-4, I am talking about XF86Config! My card still uses the 3.3.6 server.
Forgot to mention, this applies to rc2.
Ok, here's my XF86Config... Section "Monitor" Identifier "DELL P991" VendorName "Unknown" ModelName "Unknown" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 31 - 60 # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 50 - 80 The code that writes out the XF86Config and XF86Config-4 files share the same variables...so the refresh rates will be the same in the two files. What kind of video card do you have? It's possible that the problem appears if the installer can't identify your video card.
00:02.0 VGA compatible controller: Silicon Motion, Inc. SM910 (rev b5) The installer detects the card and chooses the right server. But I guess it cannot dedect the monitor: LCD panel.
It looks like the failure mode is to use the supplied values in the ks.cfg file if the monitor probe failed. Take a look at this Brent.
Any ideas on this Brent?
I'll try to get an LCD and test today.
This works correctly in the qa0320.0 tree. This issue is resolved.