Description of problem:
During its initialization, X.Org crashes with SIGSEGV shortly after loading SiS driver. As Anaconda relies on X, this makes installation of F18 on machines with such video adapter impossible. (The alternative VESA driver results in only part of the screen visible.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Get F18 installation image (DVD, Live DVD, netinst...)
2. Create desired media (DVD, USB...)
3. Boot and chose to install F18
When Anaconda starts X.Org, the latter crashes with SIGSEGV.
Normal initialization of X.Org.
In F18 the SiS driver was updated from 0.10.4 to 0.10.7. F17 has 0.10.4 and the driver works correctly.
Video adapter PCI ID from 'lspci' and 'lspci -n':
01:00.0 0300: 1039:6325
"VGA compatible controller" "Silicon Integrated Systems [SiS]" "65x/M650/740 PCI/AGP VGA Display Adapter" "ASUSTeK Computer Inc." "Device 8081"
Created attachment 679853 [details]
I tested the F18 Release DVD on USB and:
[ 26.123] (**) Option "xkb_layout" "us"
[ 41.869] (EE)
[ 41.869] (EE) Backtrace:
[ 41.869] (EE) 0: Xorg (xorg_backtrace+0x36) [0x46c316]
[ 41.869] (EE) 1: Xorg (0x400000+0x71c49) [0x471c49]
[ 41.869] (EE) 2: /lib64/libpthread.so.0 (0x7f1e84062000+0xf000) [0x7f1e84071000]
[ 41.869] (EE) 3: /lib64/libc.so.6 (0x7f1e82ab4000+0x8e88b) [0x7f1e82b4288b]
[ 41.869] (EE) 4: /usr/lib64/xorg/modules/drivers/sis_drv.so (0x7f1e81a93000+0x2925c) [0x7f1e81abc25c]
[ 41.869] (EE) 5: /usr/lib64/xorg/modules/libexa.so (0x7f1e80e3a000+0x5dcb) [0x7f1e80e3fdcb]
[ 41.869] (EE) 6: /usr/lib64/xorg/modules/libexa.so (0x7f1e80e3a000+0x61a8) [0x7f1e80e401a8]
[ 41.869] (EE) 7: /usr/lib64/xorg/modules/libexa.so (0x7f1e80e3a000+0x6d74) [0x7f1e80e40d74]
[ 41.869] (EE) 8: /usr/lib64/xorg/modules/libexa.so (0x7f1e80e3a000+0x6e74) [0x7f1e80e40e74]
[ 41.869] (EE) 9: /usr/lib64/xorg/modules/libexa.so (0x7f1e80e3a000+0x12898) [0x7f1e80e4c898]
[ 41.869] (EE) 10: /usr/lib64/xorg/modules/libexa.so (0x7f1e80e3a000+0xf21c) [0x7f1e80e4921c]
[ 41.869] (EE) 11: Xorg (0x400000+0x12a3c9) [0x52a3c9]
[ 41.869] (EE) 12: Xorg (miGlyphs+0x403) [0x5190c3]
[ 41.869] (EE) 13: /usr/lib64/xorg/modules/libexa.so (0x7f1e80e3a000+0x12d37) [0x7f1e80e4cd37]
[ 41.870] (EE) 14: Xorg (0x400000+0x12a651) [0x52a651]
[ 41.870] (EE) 15: Xorg (0x400000+0x123856) [0x523856]
[ 41.870] (EE) 16: Xorg (0x400000+0x395ea) [0x4395ea]
[ 41.870] (EE) 17: Xorg (0x400000+0x2805a) [0x42805a]
[ 41.870] (EE) 18: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f1e82ad5a05]
[ 41.870] (EE) 19: Xorg (0x400000+0x2839d) [0x42839d]
[ 41.870] (EE)
[ 41.870] (EE) Segmentation fault at address 0x3c7d8
Fatal server error:
[ 41.870] Caught signal 11 (Segmentation fault). Server aborting
[ 41.870] (EE)
Please consult the Fedora Project support
01:00.0 VGA compatible controller : Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1039:6330] (rev 03)
Booting in 'Basic Video' (VESA) does work for me. (The monitor max resolution is very low by today standards... a CRT 1024x768....).
I have ran into this bug on CentOS 6.4 x86_64:
CentOS 6.4 is still GLIBC_2.12 (Fedora 18 is GLIBC_2.14) so drivers from Fedora will not work though obviously issue is not related to version of GLIBC (if that is helpful).
But it works if NoAccel option is enabled - add following line in Section "Device":
Option "NoAccel" "True"
It works, and detects resolution properly.
Hope it helps!
Looks like this bug is now part of CentOS 6.4. too :-)
If you're bold enough, here is my guide how to get back a fully accelerated X server on Fedora 18 by compiling an older version of X.org manually. Also works on CentOS 6.4 (tried myself few days ago).
I've created bug 987519 for RHEL6 which might well be the same issue.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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
Thank you for reporting this bug and we are sorry it could not be fixed.