Bug 804194
Summary: | X doesn't start | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marcos Mello <marcosfrm> | ||||||||||
Component: | xorg-x11-drv-openchrome | Assignee: | Xavier Bachelot <xavier> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 17 | CC: | airlied, awilliam, xavier | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | AcceptedNTH | ||||||||||||
Fixed In Version: | xorg-x11-drv-openchrome-0.2.905-5.fc17 | Doc Type: | Bug Fix | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2012-04-12 02:51:59 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: | 752652 | ||||||||||||
Attachments: |
|
Description
Marcos Mello
2012-03-16 19:42:05 UTC
Created attachment 570687 [details]
Xorg log
Created attachment 570688 [details]
lspci -nnvvxxx
Xorg server in F17 doesn't support xaa anymore and openchrome default is still xaa. You can probably get the driver going by using a minimal X conf to enable exa, although compositing is buggy and would need to be disabled. Something like that in /etc/X11/xorg.conf.d/openchrome.conf should do : Section "Device" Identifier "Card0" Driver "openchrome" Option "AccelMethod" "exa" Option "ExaNoComposite" EndSection I'll look into fixing that properly to run without an X conf. Thanks for the report. xorg-x11-drv-openchrome-0.2.905-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.905-4.fc17 Package xorg-x11-drv-openchrome-0.2.905-4.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-openchrome-0.2.905-4.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4200/xorg-x11-drv-openchrome-0.2.905-4.fc17 then log in and leave karma (feedback). Thank you for the fix. Once it reaches the next F17 Beta compose I'll test and report here. I did a F17 text install and the problem remains after installing xorg-x11-drv-openchrome from updates-testing (0.2.905-4.fc17). See attached log. Created attachment 572258 [details]
Xorg log (take 2)
Ok, I see the issue. the xaa module is loaded even when not needed. I have a patch, but no machine in an usable state to test, so I'll do a scratch build and ask you to test it. I'll post a link soon. Sorry for the inconvenience, I should have updated at least one of my VIA machines earlier in the release cycle. http://koji.fedoraproject.org/koji/taskinfo?taskID=3926199 Not sure this is enough, I'm discussing the issue upstream, but it worth a try. Still no video with 0.2.905-5.fc17, just a blank screen. And it completely blocks keyboard input (can't switch ttys). Need SSH access to manage the machine. New log attached. I did a new install (VNC this time) with XFCE as DE and changed the "runlevel": ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target Do I need create /etc/sysconfig/desktop with "DISPLAYMANAGER=GNOME"? Created attachment 572441 [details]
Xorg log (take 3)
Just confirming I did a new default "Desktop" install (GNOME) and got the same blank screen. Package xorg-x11-drv-openchrome-0.2.905-5.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-openchrome-0.2.905-5.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4200/xorg-x11-drv-openchrome-0.2.905-5.fc17 then log in and leave karma (feedback). Thanks Xavier! Version 0.2.905-5.fc17 works. I have some display corruption in Gnome Shell with fullscreen windows, but probably isn't xorg-x11-drv-openchrome problem. Xavier can you push this to stable so hopefully will be a next F17 Beta RC and VIA users will have a working Anaconda GUI in F17 Beta? The package needs to stay in testing 3 days before I can push it to stable, but I will definitely push it as soon as I can. How's the screen corruption issue going ? Did you give a try at another desktop manager that doesn't need full 3D support, like KDE, xfce, lxde, etc... ? Yes. Gnome Fallback mode and KDE works without problem (I did just a quick test, opening some programs, changing windows, etc). Unfortunately the P4M900 machine is gone (was from a friend). I have now a P4M800. With this one no corruptions yes (but it's very slow in Shell...). marcos: for the corruption, check you have mesa -9. There was a -7 build which was known to have issues. Discussed at 2012-03-30 NTH review meeting. Accepted as NTH as this is obviously more or less a showstopper for VIA hardware and can't be fixed fully with an update (live boot and graphical install would still be affected). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Dave: are there other drivers which need fixing for this? There was talk in the review meeting of nv being affected. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Thanks Xavier, Adam. Fixed in F17-Beta-RC3. xorg-x11-drv-openchrome-0.2.905-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |