Bug 128363
Summary: | LCD laptop screen not properly detected by firstboot | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dee-Ann LeBlanc <dee> | ||||
Component: | system-config-display | Assignee: | Adam Jackson <ajax> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | athlon | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-04-03 18:06:33 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Dee-Ann LeBlanc
2004-07-22 05:17:39 UTC
I just wanted to add here that I have the same result when I install on one of my machines that's using a KVM. I expect it not to be able to detect my monitor properly through a KVM, but it's a bit annoying to have to manually bump it up to 1024x768 after the firstboot process. Is it safe these days to use 1024x768 Generic SVGA as a default instead of an 800x600 default? I'm not really sure what the best solution to this problem is, but KVMs are certainly heavily in use. I like the solution to the KVM issue in FC3T2candidate0908.0, the Configure button makes all the difference. After installing FC3T2candidate0908.0 on the emachine laptop specified earlier and updating it to rawhide 9/14, firstboot starts properly here as well but it doesn't detect my LCD panel. More frustratingly, again it lets me tell it that my panel is 1280x800 but then doesn't let me select 1280x800 under resolution. Please fix this. :) The 1280x800 issue may be dealt with at Bug #122739. It sounds like I experienced similar initial detection woes as the reporter of this bug, as follows: I have a Toshiba M35X-S106 laptop (Celeron M). Its LCD display supports 1024x768 resolution at 16M colors, but the install process configured it as "unknown monitor" at 800x600 with "thousands of colors". I changed the hardware setting in system-config-display to LCD Panel 1024x768, but when I rebooted, Kudzu detected "new" video-related hardware. I allowed it to "Configure" and it unfortunately reset the configuration to "Unknown monitor", at the lower resolution. So I manually switched it back, and know to tell Kudzu not to do anything when it detects "new" video hardware. The right thing, of course, would be for my display to have been configured at the correct resolution the first time around, and for Kudzu not to try to break it later on. This was with a fresh install of Fedora Core 3 (final). please attach the Xorg.0.log from a successful startup after installation. Ping timeout from reporter. Please attach an X log from a successful startup after installation, so that your laptop may be added to the monitor database. Please move the bug back from NEEDINFO to ASSIGNED when you do. Changing version to correct one. (test1 -> fc3test1, and some were filed as test3 accidentally instead; but clearly must be fc3test1 given the date of filing.) NEEDINFO timeout, resolving as INSUFFICIENT_DATA. Created attachment 151623 [details]
Xorg.0.log for Toshiba laptop
I installed Fedora 7 from the LiveCD, and my Toshiba laptop's LCD screen was configured correctly, at 1024x768. There were no problems when rebooting. (Yay!) |