Hide Forgot
Created attachment 1151952 [details] X log for 0.3.3 Description of problem: Machine is working perfect with old driver , after upgrade to new 0.4.0 machine hang Version-Release number of selected component (if applicable): xorg-x11-drv-openchrome 0.3.3-17 - working xorg-x11-drv-openchrome 0.4.0 - broken How reproducible: Steps to Reproduce: 1.install Fedora 23 XFCE Live with openchrome 0.3.3-17 2.make dnf update 3.after upgrade openchrome to 0.4.0 machine can't boot to X and freeze only hard reset help Actual results: black screen and machine hang Expected results: working Additional info:
I think this might be a bad interaction between the P4M900 and the TV chipset detection code. There was a workaround in the code preventing probing of TV in case of a P4M900 and this has been removed in 0.4.0. Are you comfortable building from source ? If so, then it would be nice to try latest git tree and see if the hang is still present. Then try the attached patch that removes probing of the TV chip. If you're not comfortable with building, just say so, I'll provide an RPM for you to test. Here are some instruction to build from source : https://www.freedesktop.org/wiki/Openchrome/Installation
Created attachment 1152570 [details] Disable TV probe
Created attachment 1152579 [details] Disable TV probe on P4M900
Hi , thank you for patience. I am not comfortable with building from source so rpm would be better. Regards Kuba I replied via email first so my answer can be duplicated.
Sorry for the late answer. Please find 2 sets of rpms for you to test here : https://www.bachelot.org/openchrome-f23/ - 0.4.169-1 is the vanilla openchrome tree. Test this one first. - 0.4.169-2 is the same plus a patch that disables tv chipset probing on the P4M900. You need to run the following command : sudo dnf update https://www.bachelot.org/openchrome-f23/xorg-x11-drv-openchrome-0.4.169-1.fc23.i686.rpm Then test. if the test fails, update to the patched version with : sudo dnf update https://www.bachelot.org/openchrome-f23/xorg-x11-drv-openchrome-0.4.169-2.fc23.i686.rpm Then test again and report back. Also, please note the latest F23 kernel (4.5.5) is causing some unrelated troubles with openchrome, I had to revert to 4.4.9.
Can you please re-test with openchrome 0.5.0, which is soon going to hit updates-testing ? You can get it from koji meanwhile : http://koji.fedoraproject.org/koji/buildinfo?buildID=778286
Any improvement with openchrome 0.5.0 ?
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.