Red Hat Bugzilla – Bug 435570
(VIA chipset) openchrome breaks VT switching
Last modified: 2018-04-11 02:58:19 EDT
Using openchrome with full auto-configuration. VT switching with CTRL-ALT-Fx
seems to do absolutely nothing. I am stuck in X.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
I currently have no way of getting the Xorg log on this machine, because I
cannot get to the VT and X is showing me a desktop on a remote machine. I would
need to install an entire OS on a USB drive in order to get this. It may take
Could you please at least give a bit of details on the hardware (brand and model
of motherboard/laptop, variant of the unichrome IGP, output used (VGA,laptop
panel, etc...) ?
There is no xorg.conf, this is autoconfiguration. Tested it on rawhide, same
Created attachment 296928 [details]
X without xorg.conf on rawhide.
Created attachment 296929 [details]
lspci -vvv and lspci -vvvn
I do have a CLE266 running F8 and I don't have any problem with VT switch. As
the X server is started without a conf, could it be a problem with the keyboard
not being auto-configured properly ?
> could it be a problem with the keyboard not being auto-configured properly ?
The attachment of the log in Comment #5 has the autogenerated config file near
the top. Furthermore, VT switching works fine on other chipsets booted with
exactly this same manner.
Have you tried starting X without xorg.conf yourself on your CLE266? Might be
an interesting comparison.
> Have you tried starting X without xorg.conf yourself on your CLE266? Might be
> an interesting comparison.
Yes, I did and (unfortunately) it works... I did not compare the logs, but I'll
do asap. Maybe this is related to the DRI problem in RHBZ #207344.
We're currently busy putting the driver into shape for F9, it'll be nice if you
can give the F9 Beta LiveCD a try when it's out. I'll consult with upstream
about the VT/DRI problem when we have more spare cycles.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.