Thanks for the log. Well, you picked the wrong (Intrepid) version from the PPA, that's why you get the xserver-xorg-video-4 conflict.
You might also be able to avoid the crash by specifying: Option "DRI" "off" in the Device section of your xorg.conf but with the fixed driver it shouldn't be needed. ** Summary changed: - No signal with Samsung SyncMaster 750s and ProSavage8 + crashes on startup - segfault in DRIFinishScreenInit ** Description changed: Binary package hint: xserver-xorg-video-savage This occurs on trying to boot the intrepid 8.10 CD as a live CD on a gBox computer Display controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] Display: Samsung SyncMaster 570S TFT While trying to boot the CD, eventually the display controller is unable to find a mode that works on the Samsung display. The Samsung display will indicate this by flashing small windows indicating that the controller output is incompatible with the display. I have found no way to get to a shell to attempt to fix the situation, e.g. by changing the xorg.conf file. Under hardy (actually installed), what happened is that a compatible 800x600 mode was found, and I could add an xorg.conf file which was generated by booting a 7.04 live CD, restart X, and get to the 1024x768 mode supported by the display. Under intrepid, I was unable to get to the point where I could copy over the (possibly) 'good' xorg.conf. See bug # 212510, and some bugs listed as duplicates to that, for some further information - this bug report is specifically for this controller/display combination under intrepid; 212510 is listed as fixed for the original hardware combination, but is clearly not fixed for this hardware combination and others I mention in that report. + + + Backtrace: + 0: /usr/bin/X11/X(xorg_backtrace+0x3b) [0x813281b] + 1: /usr/bin/X11/X(xf86SigHandler+0x55) [0x80c5dc5] + 2: [0xb806d400] + 3: /usr/lib/xorg/modules/extensions//libdri.so(DRIFinishScreenInit+0xb1) [0xb8065821] + 4: /usr/lib/xorg/modules/drivers//savage_drv.so(SAVAGEDRIFinishScreenInit+0x60) [0xb7ae9dc0] + 5: /usr/lib/xorg/modules/drivers//savage_drv.so [0xb7add6f2] + 6: /usr/bin/X11/X(AddScreen+0x19d) [0x80711dd] + 7: /usr/bin/X11/X(InitOutput+0x206) [0x80adeb6] + 8: /usr/bin/X11/X(main+0x1e1) [0x80718d1] + 9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7c44775] + 10: /usr/bin/X11/X [0x8070f61] + Saw signal 11. Server aborting. + ddxSigGiveUp: Closing log ** Summary changed: - crashes on startup - segfault in DRIFinishScreenInit + No signal with Samsung SyncMaster 750s and ProSavage8 ** Description changed: Binary package hint: xserver-xorg-video-savage This occurs on trying to boot the intrepid 8.10 CD as a live CD on a gBox computer Display controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] Display: Samsung SyncMaster 570S TFT While trying to boot the CD, eventually the display controller is unable to find a mode that works on the Samsung display. The Samsung display will indicate this by flashing small windows indicating that the controller output is incompatible with the display. I have found no way to get to a shell to attempt to fix the situation, e.g. by changing the xorg.conf file. Under hardy (actually installed), what happened is that a compatible 800x600 mode was found, and I could add an xorg.conf file which was generated by booting a 7.04 live CD, restart X, and get to the 1024x768 mode supported by the display. Under intrepid, I was unable to get to the point where I could copy over the (possibly) 'good' xorg.conf. See bug # 212510, and some bugs listed as duplicates to that, for some further information - this bug report is specifically for this controller/display combination under intrepid; 212510 is listed as fixed for the original hardware combination, but is clearly not fixed for this hardware combination and others I mention in that report. - - - Backtrace: - 0: /usr/bin/X11/X(xorg_backtrace+0x3b) [0x813281b] - 1: /usr/bin/X11/X(xf86SigHandler+0x55) [0x80c5dc5] - 2: [0xb806d400] - 3: /usr/lib/xorg/modules/extensions//libdri.so(DRIFinishScreenInit+0xb1) [0xb8065821] - 4: /usr/lib/xorg/modules/drivers//savage_drv.so(SAVAGEDRIFinishScreenInit+0x60) [0xb7ae9dc0] - 5: /usr/lib/xorg/modules/drivers//savage_drv.so [0xb7add6f2] - 6: /usr/bin/X11/X(AddScreen+0x19d) [0x80711dd] - 7: /usr/bin/X11/X(InitOutput+0x206) [0x80adeb6] - 8: /usr/bin/X11/X(main+0x1e1) [0x80718d1] - 9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7c44775] - 10: /usr/bin/X11/X [0x8070f61] - Saw signal 11. Server aborting. - ddxSigGiveUp: Closing log -- No signal with Samsung SyncMaster 750s and ProSavage8 https://bugs.launchpad.net/bugs/294899 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
