From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
(This is FC3 rc1, which wasn't in the version selection choices).
When I run the installer on my laptop (Dell D800), when the monitor is
probed, it finds my connected (but currently unused) external monitor,
and not the LCD display on the laptop itself.
Since the settings aren't compatible, I end up with a bogus X
configuration file unless I boot and immediately switch to my
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start FC installer on laptop display, when external monitor is
2. note that the external monitor is the one returned during video probe
3. continue installation, boot when finished,
Actual Results: note that X configuration is botched (suitable for
external monitor, not laptop display)
Expected Results: I would expect that the generated configuration
matches what I used during the installation -- if I had switched to
the external monitor, I wouldn't have a problem with the config file
being written for it.
But to be using one display and have the config file written for the
other one is confusing.
Installation does not configure X it's done in first boot.
The dell laptop display is not probable with DDC, but you should have
been able to change the setup in firstboot to be correct selecting a
generic LCD panel of appropriate resolution.
If you remove /etc/sysconfig/firstboot and /sbin/chkconfig --add
firstboot and reboot can you select the appropriate display in firstboot?
Well, after a kickstart config, my system boots up straight to the GDM
screen. So, I'm not offered a choice of monitor settings.
When I explicitly force a firstboot run after the kickstart (by
writing to /etc/sysconfig/firstboot from %post), I can select a
I was hoping to avoid having to do this manual step during a mass
install of these machine, by making sure the kickstart config was
correct in the first place. If anaconda isn't going to use these
values, then why are there arguments for providing them.
The original bug report did not mention kickstart at all - merely
mentioning the installer.
Please attach your kickstart file, and the generated xorg.conf.
Let me modify this report (I had too many things going on at once).
When doing a regular (non-kickstart) installation, the monitor probe
finds the attached, but unused, external monitor. When firstboot
comes up and prompts me for X selection, the choice defaults to what
is probed, not what's actually running.
If I choose these defaults, X then comes up on the LCD display anyway.
When I switch to the external monitor (via Fn- keys), I get no display
on the external monitor. After switching back to the built-in
display, the display is heavily compressed vertically and I don't have
any way to return it to a correct state.
I believe that it's a bug that it defaults to the unused external
monitor, but if that's what I selected, it should work.
For the kickstart related issues, it looks similar to 127475.
Created attachment 105736 [details]
The log from the first session after firstboot
I switched to the external monitor (attempted, at least) and back during this
session, and the end results were pretty badly messed up. Everything was very
Created attachment 105737 [details]
The X config file, as generated from firstboot
Does this persists on FC3 final or FC4?
Closing due to lack of response from reporter.