Bug 202336
| Summary: | Using vga=0x317 on kernel boot line causes monitor "out of range" error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dick Gingras <dgingras> | ||||
| Component: | xorg-x11-drv-nv | Assignee: | Adam Jackson <ajax> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6 | CC: | mattdm, mcepl, xgl-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | f8 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-12-10 16:52:40 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
Dick Gingras
2006-08-13 00:53:09 UTC
Please attach the Xorg.0.log from a failed startup and from a successful startup. Created attachment 134142 [details]
Xorg log with vga=0x317 at boot
There is no difference in the Xorg logs between booting with and without
vga=0x317. They are identical except for the time-stamp line.
I forgot to mention that the first message emitted on the console at boot with
vga=0x317 is "Console: switching to colour fram buffer device 128x48".
Also, the actual error text that my monitor displays when X starts is
"Frequency over range".
Problem still exists in fc6-test3, kernel 2.6.18-1.2784.fc6 Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.] I have retested and verified that this bug still exists. I used FC6 with kernel 2.6.20-1.2933.fc6 and the nv driver in xorg.conf. When the monitor displays the "Out of Range" message (when rhgb starts up), pressing Ctl-Alt-F1 correctly reverts the screen back to a console display, but the next time X11 is started during the rhgb process, the "Out of Range" message reappears. After the boot process completes and X11 is restarted for the GDM greeter, all is well. Note that this problem does NOT occur when using the closed-source nvidia driver. Thank you. clearing needinfo bit. Fedora Core 6 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora 7, 8, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. [This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or Gecko. If you see any other reason, why this bug shouldn't be closed, please, comment on it here.] Retested with Werewolf (Fedora 8) and kernel 2.6.23.8-63.fc8. Appears to be fixed - no longer getting "out of range" from monitor and all boot-up messages are correctly displayed, including the two penguins (I have a dual-core AMD cpu). |