Bugzilla – Bug 117408
Can not select primary graphics card when multiple cards are installed - SaX2 now seg faulting
Last modified: 2008-06-25 09:46:38 UTC
I installed on a system with an ATI 9600 and a Matrox RTX100 (which has a G550 chip on it). During the hardware configuration part of the install, it chose the G550 as the device to configure for a graphics card. There was no choice to select the ATI 9600. I skipped the hardware configuration and logged in. Running SaX2, it showed the G550 as well and could not select the ATI. I selected cancel and ran sax2 -p, it shows the ATI as Chip 0 and the G550 as Chip 1. Trying to run SaX2 again, it starts to load, but then exists with no error. Looking at the System Log, it's showing a seg fault when trying to run SaX2 now. I shutdown, removed the Matrox RTX100, and booted. Same issue with SaX2. System Log segfault messages are (one entry for each try to run SaX2) --------------------------------- Sep 15 21:22:16 linux kernel: xapi[7645]: segfault at 0000000000000000 rip 00002aaaab6851e3 rsp 00007ffffffdcd68 error 4 Sep 15 21:23:30 linux kernel: xapi[7915]: segfault at 0000000000000000 rip 00002aaaab6851e3 rsp 00007ffffff1f9a8 error 4 /var/log/sax2.log --------------------------------- /************* SaX2 log : SaX2 version 7.1 - SVN Release: 1.49 2003/03/17 ************** SVN BUILD : 26443 : DESCRIPTION : X11 configuration log file to collect information : about detection, startup and configuration. : There are three parts of logging: : --- : 1) INIT ( detection, 3D ) : 2) STARTUP ( xorg.conf, X11 log, glxinfo ) : 3) CONFIG ( config actions ) : --- : VERSION : SaX2 compiled for: [SUSE LINUX 10.0 (X86-64)] PARAMETER : no parameter(s) given : LOG DATE : Thu Sep 15 21:23:28 PDT 2005 *************/ ============================ Framebuffer Info: ---------------------------- mode "1024x768-76" # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode Frame buffer device information: Name : VESA VGA Address : 0xd0000000 Size : 6291456 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 0 YPanStep : 0 YWrapStep : 0 LineLength : 2048 Accelerator : No 15-Sep 21:23:28 <X> Startup... 15-Sep 21:23:28 <X> [ Startup on already running Server: :0.0 -> grant ] 15-Sep 21:23:29 <I> Imported: Card 15-Sep 21:23:29 <I> Imported: Desktop 15-Sep 21:23:29 <I> Imported: Pointers 15-Sep 21:23:29 <I> Imported: Keyboard 15-Sep 21:23:29 <I> Imported: Layout 15-Sep 21:23:29 <I> Imported: Path 15-Sep 21:23:29 <I> Imported: Extensions QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key hwinfo --mouse -------------------------- 16: USB 00.1: 10503 USB Mouse [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_d3d_1_noserial_if1_logicaldev_input Unique ID: 8e8U.PB2t7_x6gBA Parent ID: pBe4.qV7cuxFANI2 SysFS ID: /devices/pci0000:00/0000:00:10.1/usb2/2-2/2-2:1.1 SysFS BusID: 2-2:1.1 Hardware Class: mouse Model: "USBPS2" Hotplug: USB Vendor: usb 0x0d3d Device: usb 0x0001 "USBPS2" Revision: "0.01" Compatible to: int 0x0210 0x0025 Driver: "usbhid" Device File: /dev/input/mice (/dev/input/mouse0) Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event2 Device Number: char 13:63 (char 13:32) Speed: 1.5 Mbps Module Alias: "usb:v0D3Dp0001d0001dc00dsc00dp00ic03isc01ip02" Driver Info #0: Buttons: 5 Wheels: 2 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (Hub) Contents of /var/lib/sax: ------------------------------------ linux:/var/lib/sax # ls -l total 33 drwxr-xr-x 2 root root 208 Sep 15 18:35 . drwxr-xr-x 34 root root 888 Sep 15 19:15 .. -rwxr-xr-x 1 root root 2185 Sep 6 09:08 createAPI.pl -rwxr-xr-x 1 root root 419 Sep 6 09:08 createCHK.sh -rwxr-xr-x 1 root root 10430 Sep 6 09:08 createPRO.pl -rwxr-xr-x 1 root root 6269 Sep 6 09:08 createTST.pl -rwxr-xr-x 1 root root 393 Sep 6 09:08 createVNC.sh Please note that the Matrox RTX100 is a video editing card and although it has a G550 chip on it, it doesn't act as a display device (at least in Windows, and Windows doesn't see it as one). I know the card isn't supported in Linux, but I'm dual booting so I can use it. The issue should exist with other AGP + PCI graphics cards combinations. Questions: 1 - Shouldn't SaX2 allow you to choose which graphics card to use when multiple cards are detected? 2 - Should SaX2 already know which card to configure as X is already running on the correct one? 3 - Did SaX2 write out a config file that's causing the problem (even though I selected cancel without saving anything)? Please let me know if you need further info or what else I can do to help correct the problem. Many Thanks
First I will answer your questions: ----------------------------------- 1) sax allows to choose the card and can activate/deactivate it if the startup would have been successfull. Additionally you can select which card to use at startup using the option -c 2) If X is running sax will import the configuration if this X-Server which means it uses the information from /etc/X11/xorg.conf 3) Selecting cancel will not save anything, I promise :-) Ok, now flip into the bug ------------------------- you have two cards in your system this may cause trouble to the X-server but should work. As far as I can see both cards are dualhead cards so you are able to setup 4 heads ?. To be able to debug this I need a starting point and a new log file. So if you don't mind proceed the following workflow: - switch to runlevel 3 and login as user root - call sax2 -r - click on "Change Configuration" ... followed by exiting sax - now send me the log file /var/log/SaX.log - and the complete library cache as tgz archive /var/cache/sax Thanks
no further information...
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
no response: wontfix
I said wontfix !!!!!!!!!