Bug 70190
| Summary: | Installer creates wrong monitor values for hsync/vrefresh in /etc/XF86Config | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <thomas.gern> | ||||||||||
| Component: | kudzu | Assignee: | Michael Fulbright <msf> | ||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 8.0 | CC: | mitr | ||||||||||
| 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: | 2002-11-28 23:01:16 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: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 67217, 70186 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Need Real Name
2002-07-30 23:19:51 UTC
The X11 configuration tool suggests the folling values HorizSync/VertRefresh
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync -268377405--268374161
VertRefresh -268374161--268370092
Option "dpms"
DisplaySize 270.933333333 203.2
EndSection
X11 doesn't accept negative values and after installation you aren't able to
boot into X or even start X if you don't alter /etc/X11/XF86Config manually.
This Bug is somehow linked to bug 70186 in which the attempt to start the
graphical installation tool failed.
Created attachment 69169 [details]
[installer] failed start of graphical installer (same happens after installation) -> X.log
Created attachment 69170 [details]
output from "lspci -vv"
Created attachment 69171 [details]
output from "lspci -vvn"
I've added more checking which should avoid this case completely. still the same problem in Version 7.3.94 (null) Happens for me too, running ddcprobe from (null) [admittedly against kudzu-0.99.52-1 from 7.3] gives: Monitor DDC probe results ID: ACTb013 Name: peacock Width (mm): 320 Height(mm): 240 The workaround added on Aug 6 is irrelevant (checks only in the x config screen, long after the XF86Config for running GUI installer has been created); I'll try the workaround added on Aug 21 (monitor.py from rawhide rhpl-0.51) tomorrow. OK, I found it. Not all strange things are hardware bugs... In my case, as can be confirmed by running ddcprobe from 7.3 (the binary,not the python script), the monitor doesn't supply the frequency ranges via ddc. In 7.3., anaconda used this ddcprobe and parsed its output (correctly). In (null), frequency ranges support was added to kudzu and the original dcprobewas replaced by a python script calling kudzu. The code added to kudzu is wrong and accesses a NULL pointer when the monitor doesn't return the frequency range AND the monitor is not in MonitorsDB. Under normal conditions it would segfault, alas ddc probing is done by calling the BIOS in vm86 mode, which maps stuff at virtual address 0, so kudzu continues and returns rubbish. Please reassign this bug to kudzu, patch attached (or is there any procedural reason why should I file a new bug about this?) Created attachment 76144 [details]
Patch for kudzu
OK. problem solved. Installed Red Hat Linux 8.0 today without this issue. |