Bug 144729

Summary:	Problem with sax2 and ati-driver-installer-8.21.7-i386.run
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Joop Boonen <joop.boonen>
Component:	SaX2	Assignee:	Jammy Zhou <atilinuxnovellbugs>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	sndirsch
Version:	Beta 1
Target Milestone:	---
Hardware:	x86
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	All files that might be usefull The screen i get after sax2 starts xorg xorg.0.log(ing) all xorg.conf(igs) auto matically generated xorg.conf xorg.conf with resoltion adjustment (1600x1200) Even this config suggested by sax wich previously didn't work is working with 25 Modelines

Description Joop Boonen 2006-01-23 08:10:42 UTC

Yesterday i was trying to installing the ati fglx driver of ati (last version) according to the follwing instructions: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html .
This worked perfectly untill i wanted i came to the part of sax2: sax2 -m 0=fglrx -b /usr/share/doc/packages/fglrx/sax2-profile

There i got an error on the follwing lines:
ServerLayput -> all -> Screen -> 0 -> top    =
ServerLayout -> all -> Screen -> 0 -> bottom =
ServerLayout -> all -> Screen -> 0 -> left   =
ServerLayout -> all -> Screen -> 0 -> right  =

I didn't get into it yet. So i  don't know what exactly the problem is. I didn't have any time anymore yesterday. I'm also not familiar with the sax2 Activate the SaX2 batch modus. I  might look into it tonight, if needed.

Comment 1 Joop Boonen 2006-01-23 09:43:05 UTC

It looks like the = shouldn't be in this line (i looked in sax.pdf):
ServerLayput -> all -> Screen -> 0 -> top    =
ServerLayout -> all -> Screen -> 0 -> bottom =
ServerLayout -> all -> Screen -> 0 -> left   =
ServerLayout -> all -> Screen -> 0 -> right  =

So it should be:
ServerLayput -> all -> Screen -> 0 -> top
ServerLayout -> all -> Screen -> 0 -> bottom
ServerLayout -> all -> Screen -> 0 -> left
ServerLayout -> all -> Screen -> 0 -> right

I cant test this right now. I will check it this evening.

Comment 2 Marcus Schaefer 2006-01-23 09:56:56 UTC

---from the README---
On (open)SUSE 10.1 (Alpha) or later it's no longer required to
specify the profile, so use "sax2 -r -m 0=fglrx" instead.
---snap----

You only need to call:

  sax2 -m 0=fglrx

Using the latest version even doesn't requires this because we added
a check to find whether the fglrx driver is installed or not. But I think
this version doesn't make it on beta1 but beta2 will have it.

If you don't mind try calling:

   sax2 -m 0=fglrx

Thanks

Comment 3 Marcus Schaefer 2006-01-23 10:01:46 UTC

---from the README---
On (open)SUSE 10.1 (Alpha) or later it's no longer required to
specify the profile, so use "sax2 -r -m 0=fglrx" instead.
---snap----

You only need to call:

  sax2 -m 0=fglrx

Using the latest version even doesn't requires this because we added
a check to find whether the fglrx driver is installed or not. But I think
this version doesn't make it on beta1 but beta2 will have it.

If you don't mind try calling:

   sax2 -m 0=fglrx

Thanks

Comment 4 Joop Boonen 2006-01-23 10:36:57 UTC

I should have read propperly.

I'll test it tonight.

Comment 5 Marcus Schaefer 2006-01-23 10:49:47 UTC

no problem, I hope it will work that way :-)

Comment 6 Joop Boonen 2006-01-23 19:37:30 UTC

I've tried sax2 -m 0=fglrx and sax2 -r -m 0=fglrx. They both don't work. I only get a gray screen (wich looks extremly enlarged (gray lines) and a blinking cursos. The config tool that came with fglrx works perfectly. So it looks like yast cant handle it porperly.

Comment 7 Joop Boonen 2006-01-23 20:10:46 UTC

Created attachment 64600 [details]
All files that might be usefull

SaX.log two files
hwinfo_ati.txt of my system
xorg.conf as generated by aticonfig (which is ok)

Comment 8 Joop Boonen 2006-01-24 07:10:55 UTC

Created attachment 64644 [details]
The screen i get after sax2 starts xorg

Comment 9 Marcus Schaefer 2006-01-24 10:24:46 UTC

Well this is strange because the Device section sax writes is almost the
same the ati config tool writes: Have a look at the following:

---from ati
Section "Device"
    Identifier                          "ATI Graphics Adapter"
    Driver                              "fglrx"
    #Option                              "NoDDC"
    Option "no_accel"                   "no"
    Option "no_dri"                     "no"
    Option "mtrr"                       "off" # disable DRI mtrr mapper, driver has its own code for mtrr
    Option "DesktopSetup"               "(null)"
    Option "ScreenOverlap"              "0"
    Option "TVFormat"                   "PAL-G"
    Option "TVStandard"                 "VIDEO"
    Option "TVHSizeAdj"                 "0"
    Option "TVVSizeAdj"                 "0"
    Option "TVHPosAdj"                  "0"
    Option "TVVPosAdj"                  "0"
    Option "TVHStartAdj"                "0"
    Option "TVColorAdj"                 "0"
    Option "GammaCorrectionI"           "0x00000000"
    Option "GammaCorrectionII"          "0x00000000"
    Option "Capabilities"               "0x00000000"
    Option "CapabilitiesEx"             "0x00000000"
    Option "VideoOverlay"               "on"
    Option "OpenGLOverlay"              "off"
    Option "CenterMode"                 "off"
    Option "PseudoColorVisuals"         "off"
    Option "Stereo"                     "off"
    Option "StereoSyncEnable"           "1"
    Option "FSAAEnable"                 "no"
    Option "FSAAScale"                  "1"
    Option "FSAADisableGamma"           "no"
    Option "FSAACustomizeMSPos"         "no"
    Option "FSAAMSPosX0"                "0.000000"
    Option "FSAAMSPosY0"                "0.000000"
    Option "FSAAMSPosX1"                "0.000000"
    Option "FSAAMSPosY1"                "0.000000"
    Option "FSAAMSPosX2"                "0.000000"
    Option "FSAAMSPosY2"                "0.000000"
    Option "FSAAMSPosX3"                "0.000000"
    Option "FSAAMSPosY3"                "0.000000"
    Option "FSAAMSPosX4"                "0.000000"
    Option "FSAAMSPosY4"                "0.000000"
    Option "FSAAMSPosX5"                "0.000000"
    Option "FSAAMSPosY5"                "0.000000"
    Option "UseFastTLS"                 "0"
    Option "BlockSignalsOnLock"         "on"
    Option "UseInternalAGPGART"         "yes"
    Option "ForceGenericCPU"            "no"
    BusID "PCI:1:5:0"    # vendor=1002, device=4150
    Screen 0
EndSection

---from sax
Section "Device"
      BoardName    "RV350 AP"
      BusID        "PCI:1@0:5:0"
      Driver       "fglrx"
      Identifier   "Device[0]"
      #Option       "NoDDC"
      Option       "UseInternalAGPGART" "no"
      Option       "no_accel" "no"
      Option       "no_dri" "no"
      Option       "mtrr" "off"
      Option       "ScreenOverlap" "0"
      Option       "GammaCorrectionI" "0x00000000"
      Option       "GammaCorrectionII" "0x00000000"
      Option       "Capabilities" "0x00000000"
      Option       "CapabilitiesEx" "0x00000000"
      Option       "VideoOverlay" "on"
      Option       "OpenGLOverlay" "off"
      Option       "CenterMode" "off"
      Option       "PseudoColorVisuals" "off"
      Option       "Stereo" "off"
      Option       "StereoSyncEnable" "1"
      Option       "FSAAEnable" "no"
      Option       "FSAAScale" "1"
      Option       "FSAADisableGamma" "no"
      Option       "FSAACustomizeMSPos" "no"
      Option       "FSAAMSPosX0" "0.000000"
      Option       "FSAAMSPosY0" "0.000000"
      Option       "FSAAMSPosX1" "0.000000"
      Option       "FSAAMSPosY1" "0.000000"
      Option       "FSAAMSPosX2" "0.000000"
      Option       "FSAAMSPosY2" "0.000000"
      Option       "FSAAMSPosX3" "0.000000"
      Option       "FSAAMSPosY3" "0.000000"
      Option       "FSAAMSPosX4" "0.000000"
      Option       "FSAAMSPosY4" "0.000000"
      Option       "FSAAMSPosX5" "0.000000"
      Option       "FSAAMSPosY5" "0.000000"
      Option       "UseFastTLS" "0"
      Option       "BlockSignalsOnLock" "on"
      Option       "ForceGenericCPU" "no"
      Option       "EnablePrivateBackZ" "yes"
      VendorName   "ATI"
    EndSection


The only difference I can see is the Bus ID:

  ATI: "PCI:1:5:0"    # vendor=1002, device=4150
  SaX: "PCI:1@0:5:0"

This is the same location on the bus but SaX takes care about the
PCI domain. The ati driver reports in case of the SaX config:

  (WW) fglrx(0): board is an unknown third party board, chipset is supported

       *** If unresolved symbols were reported above, they might not
       *** be the reason for the server aborting.

    Backtrace:
    0: /usr/sbin/xw(xf86SigHandler+0x89) [0x8088339]
    1: [0xffffe420]
    2: [0x610000]

    Fatal server error:
    Caught signal 11.  Server aborting

I think this driver is again broken :-((

Comment 10 Stefan Dirsch 2006-01-24 10:37:44 UTC

Could you please replace this PCI line in your xorg.conf, you created with fglrxconfig, with the one SaX2 creates? Just to make sure, this is really the problem. Thanks.

Comment 11 Joop Boonen 2006-01-24 19:50:44 UTC

I'm sorry but it didn't solve the problem.

Comment 12 Joop Boonen 2006-01-24 19:51:47 UTC

Created attachment 64848 [details]
xorg.0.log(ing)

Comment 13 Joop Boonen 2006-01-24 19:54:06 UTC

Created attachment 64849 [details]
all xorg.conf(igs)

Comment 14 Evan McClain 2006-02-08 22:19:24 UTC

I had the same problem when starting sax2 -r -m 0=fglrx from level 3 but when I installed the rpm and ran sax2 -r -m 0=fglrx while in kde I was able to test and save the configuration fine. (the sax2 test didn't recognize the 3d accel, but it worked)

Comment 15 Joop Boonen 2006-02-10 09:11:26 UTC

I think it'll be solved with the new ati driver.
See:
Linux Proprietary Driver 8.22.5 Release: x86 and x86_64 variants

 Feb 08, 2006  -  Show original item
NEW FEATURES: (1) ATI Proprietary Linux Driver now supports Linux Kernel 2.6.15. ISSUES RESOLVED: (1) Creating 22 or more display configuration mode lines in the X Server configuration file no longer results in a fatal server error.

There are 25 modelines:
	Section "Modes"
	  Identifier   "Modes[0]"
	  Modeline 	"1280x1024" 163.41 1280 1376 1512 1744 1024 1025 1028 1077
	  Modeline 	"1280x1024" 145.69 1280 1376 1512 1744 1024 1025 1028 1071
	  Modeline 	"1280x1024" 125.14 1280 1368 1504 1728 1024 1025 1028 1065
	  Modeline 	"1024x768" 130.12 1024 1096 1208 1392 768 769 772 820
	  Modeline 	"1024x768" 122.97 1024 1096 1208 1392 768 769 772 818
	  Modeline 	"1024x768" 110.91 1024 1096 1208 1392 768 769 772 813
	  Modeline 	"1024x768" 97.84 1024 1088 1200 1376 768 769 772 808
	  Modeline 	"1024x768" 86.18 1024 1088 1200 1376 768 769 772 803
	  Modeline 	"1024x768" 73.89 1024 1080 1192 1360 768 769 772 799
	  Modeline 	"800x600" 97.59 800 856 944 1088 600 601 604 650
	  Modeline 	"800x600" 90.10 800 856 944 1088 600 601 604 647
	  Modeline 	"800x600" 82.55 800 856 944 1088 600 601 604 643
	  Modeline 	"800x600" 73.98 800 848 936 1072 600 601 604 639
	  Modeline 	"800x600" 66.71 800 848 936 1072 600 601 604 635
	  Modeline 	"800x600" 58.73 800 840 928 1056 600 601 604 632
	  Modeline 	"800x600" 51.73 800 840 928 1056 600 601 604 628
	  Modeline 	"800x600" 44.13 800 840 920 1040 600 601 604 624
	  Modeline 	"768x576" 89.56 768 824 904 1040 576 577 580 624
	  Modeline 	"768x576" 82.67 768 824 904 1040 576 577 580 621
	  Modeline 	"768x576" 75.72 768 824 904 1040 576 577 580 617
	  Modeline 	"768x576" 67.79 768 816 896 1024 576 577 580 613
	  Modeline 	"768x576" 61.21 768 816 896 1024 576 577 580 610
	  Modeline 	"768x576" 53.75 768 808 888 1008 576 577 580 606
	  Modeline 	"768x576" 47.41 768 808 888 1008 576 577 580 603
	  Modeline 	"768x576" 40.41 768 800 880 992 576 577 580 599
	EndSection

I'll test it tonight on beta1 as beta2 and 3 don't work on this system see bug # 146529

Comment 16 Joop Boonen 2006-02-10 22:30:53 UTC

As espected it now works perfectly. Even with the by SaX suggested file.

Only 3D is not working might be caused by Beta 1. AS this is not a current beta, i don't know if this is considered a bug?

Comment 17 Joop Boonen 2006-02-10 22:32:59 UTC

Created attachment 67738 [details]
auto matically generated xorg.conf

Comment 18 Joop Boonen 2006-02-10 22:34:00 UTC

Created attachment 67739 [details]
xorg.conf with resoltion adjustment (1600x1200)

Comment 19 Joop Boonen 2006-02-10 22:39:47 UTC

Created attachment 67741 [details]
Even this config suggested by sax wich previously didn't work is working with 25 Modelines

Comment 20 Joop Boonen 2006-02-10 22:44:55 UTC

Probably related to beta 1. 3D isn't working. dri issue? 

(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID PCI:1:5:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed

Comment 21 Joop Boonen 2006-02-10 23:02:51 UTC

It's clearly getting late. 3D is working.

jboonen@linux:~> fglrxinfo
display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5642 (8.22.5)

Also tested tuxracer.

As far as i'm concerned i think the problem is solved.

Comment 22 Stefan Dirsch 2006-02-11 09:29:07 UTC

Thanks for testing again.