(In reply to Kevin Brace from comment #17) Hi Kevin > I am a little getting lost. > Are you saying that the current master branch OpenChrome code produces a > blank screen after OS boots?
That's true. > One known configuration that causes this is if you use DVI to VGA adapter. > Another configuration is if you use VX900 chipset (or possibly CX700, VX700, > VX800, or VX855 chipset) where VGA is not available, device is detected via > weird known device table, and LCD enable option is not listed in the weird > known device table. > If you can clarify your particular system configuration, that will be > appreciated. The device has a DVI *and* VGA output and while using DVI output (without adapter of any kind) we're getting a blank output. VGA output to VGA display works fine - this is what we use currently as a work- around. This is another issue however and is probably related to the topic you mentioned above and is not related to this bug. > I do understand that Canonical people do not want to tinker with the code, > and "think" that the current code is stable. > It is not. > Between Version 0.2.904 (used by Ubuntu 10.04 LTS and 12.04 LTS) and Version > 0.3.3, the previous developer broke VGA detection code if DVI to VGA adapter > is used. > This is a fatal regression. > One of the reason why I am holding up Version 0.3.4 release is due to this. I fully agree with you and I also want to see this fixed and present in Ubuntu. Unfortunately the rules (btw. those are Ubuntu rules rather than Canonical) are very strict and I don't think they can be bypassed in any way other that those described at the wiki pages (SRU and MRE). However, I would still like to provide any help necessary in making sure the new releases will be included in upcoming Ubuntu releases. Would you mind if we continue the discussion on the openchrome-devel mailing list? Thank you, Dariusz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1554004 Title: Segfault on X startup with VX900 Status in openchrome: Fix Released Status in xserver-xorg-video-openchrome package in Ubuntu: Fix Released Status in xserver-xorg-video-openchrome source package in Trusty: Fix Committed Status in xserver-xorg-video-openchrome source package in Wily: Fix Committed Bug description: [Impact] * Prevents from using X at all with some VIA chipsets - a segfault occurs and is logged in Xorg.log [Test Case] * Start X on a affected hw (e.g. VX900). * Examine Xorg.log after crash. [Regression Potential] * This is a bug fixed upstream (https://cgit.freedesktop.org/openchrome/xf86-video- openchrome/commit/?id=ecb1695ac2de1d840c036f64b5b71602e0f522a4). * The fix is a one-liner with minimal impact. [Other Info] * Original bug description: There is a segfault in Xorg.log visible when starting X on Trusty 14.04 with the following hardware: 00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 Interrupt: pin A routed to IRQ 10 Region 0: Memory at fb000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at fc000000 (32-bit, non-prefetchable) [size=16M] Region 2: Memory at f0000000 (32-bit, prefetchable) [size=128M] Expansion ROM at febf0000 [disabled] [size=64K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Snip of the Xorg.log: [ 549.260] (EE) Backtrace: [ 549.260] (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb77551bf] [ 549.261] (EE) 1: /usr/bin/X (0xb75ac000+0x1acfa4) [0xb7758fa4] [ 549.261] (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb7589410] [ 549.261] (EE) 3: /usr/lib/xorg/modules/drivers/openchrome_drv.so (0xb6c84000+0x13ccc) [0xb6c97ccc] [ 549.261] (EE) 4: /usr/bin/X (InitOutput+0xb43) [0xb762f623] [ 549.261] (EE) 5: /usr/bin/X (0xb75ac000+0x410c7) [0xb75ed0c7] [ 549.262] (EE) 6: /usr/bin/X (0xb75ac000+0x2ae1e) [0xb75d6e1e] [ 549.262] (EE) 7: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb7197a83] [ 549.262] (EE) 8: /usr/bin/X (0xb75ac000+0x2ae54) [0xb75d6e54] [ 549.262] (EE) [ 549.262] (EE) Segmentation fault at address 0x0 [ 549.262] (EE) [ 549.263] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 549.263] (EE) [ 549.263] (EE) [ 549.263] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. [ 549.263] (EE) [ 549.269] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/openchrome/+bug/1554004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
