Bug 240589 - sax2 fails to suggest configuration
Summary: sax2 fails to suggest configuration
Status: RESOLVED DUPLICATE of bug 245396
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Alpha 0plus
Hardware: PowerPC Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-31 10:01 UTC by peter czanik
Modified: 2007-02-15 09:21 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
/var/log/SaX.log (2.56 KB, text/x-log)
2007-01-31 10:03 UTC, peter czanik
Details
Xorg.99.log (17.06 KB, text/x-log)
2007-01-31 10:36 UTC, peter czanik
Details
xorg.conf (14.77 KB, text/plain)
2007-01-31 12:36 UTC, peter czanik
Details
Xorg.0.log (49.71 KB, text/plain)
2007-01-31 12:37 UTC, peter czanik
Details
Xorg.0.log (50.28 KB, text/plain)
2007-02-02 11:47 UTC, peter czanik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description peter czanik 2007-01-31 10:01:45 UTC
Sax2 on Pegasos PPC fails to suggest an Xorg configuration during installation. When called later on an installed system, it says:

"SaX: something went wrong while X was called with -probeonly
Sax: try to call 'sax2 -p' and select a single device?
abort
"
Comment 1 peter czanik 2007-01-31 10:03:33 UTC
Created attachment 116469 [details]
/var/log/SaX.log
Comment 2 Marcus Schaefer 2007-01-31 10:15:15 UTC
This is because the call of

   sysp -s xstuff

aborted. In most cases this happens because the X-Server which
is called with -probeonly crashed. The server is started on Display :99
so you should have a log file:

   /var/log/Xorg.99.log

Is there a login possibility to the machine ? 
Comment 3 peter czanik 2007-01-31 10:36:39 UTC
Created attachment 116484 [details]
Xorg.99.log

I wonder, if it's not bug #202133 resurfacing...
Comment 4 Marcus Schaefer 2007-01-31 10:41:40 UTC
Hmm, the driver doesn't know about your chipset:

(II) Primary Device is: PCI 01:08:0
(WW) RADEON: No matching Device section for instance (BusID PCI:1:8:0) found
(WW) RADEON: No matching Device section for instance (BusID PCI:1:8:1) found
(EE) No devices detected

Something for Stefan I think
Comment 5 Stefan Dirsch 2007-01-31 11:21:24 UTC
Use xorgconfig to generate your xorg.conf and make sure that BusID is not specified. Does it work for you? Attach xorg.conf and /var/log/Xorg.0.log afterwards.
Comment 6 peter czanik 2007-01-31 12:34:34 UTC
Yes, it works. I got some nostalgic feelings :) Attachments are coming in a few minutes. Took out glx and dri from comment by hand. 'glxgears' works nicely (480 FPS)
Comment 7 peter czanik 2007-01-31 12:36:37 UTC
Created attachment 116524 [details]
xorg.conf
Comment 8 peter czanik 2007-01-31 12:37:16 UTC
Created attachment 116525 [details]
Xorg.0.log
Comment 9 Stefan Dirsch 2007-01-31 12:51:40 UTC
Ok. Probably the issue is related to the BusID line, which is used by SaX2
by default. Marcus, could you figure out which BusID SaX2 probably tried to use? So we can verifiy my assumption ...

Comment 10 Marcus Schaefer 2007-02-01 08:53:03 UTC
according to comment #1

        Card0     =>  DomainId   : 0x1
	Card0     =>  BusId      : 0x1
	Card0     =>  SlotId     : 0x08
	Card0     =>  FuncId     : 0x0

this is:

   1:8:0

domain is not used on ppc
Comment 11 Stefan Dirsch 2007-02-01 09:33:24 UTC
Thanks, Marcus. So could you please add 

  BusID "1:8:0"

to ' Section "Device" ' of your /etc/X11/xorg.conf - created with xorgconfig - to check if this breaks it again. Attach the new logfile.
Comment 12 peter czanik 2007-02-02 11:47:03 UTC
Created attachment 117041 [details]
Xorg.0.log

It works fine with this 'BusID' line.
Comment 13 Stefan Dirsch 2007-02-02 12:20:16 UTC
Strange!

--- non-working-config-file
+++ working-config-file
 (II) Primary Device is: PCI 01:08:0
-(WW) RADEON: No matching Device section for instance (BusID PCI:1:8:0) found
 (WW) RADEON: No matching Device section for instance (BusID PCI:1:8:1) found
-(EE) No devices detected.
-
-Fatal server error:
-no screens found
+(--) Chipset ATI Radeon 9250 5960 (AGP) found

Unfortunately there's no way to have a look at the config file SaX2 uses
for the initial start of the Xserver. :-(

Marcus, any idea?
Comment 14 peter czanik 2007-02-02 12:30:42 UTC
Which configuration? I'm just doing a fresh network install of factory, so I can scp out any file you want.
Comment 15 Stefan Dirsch 2007-02-02 12:37:39 UTC
It's a tempfile, e.g. ""/tmp/sysdata-3919". You'll need a "while true; do ..." loop running during SaX2 start to copy it. :-(
Comment 16 Marcus Schaefer 2007-02-02 12:45:43 UTC
This one here could be a duplicate of #240693

I'd suggest to test the current version, available on openSUSE
Comment 17 Stefan Dirsch 2007-02-02 13:49:28 UTC
> I'd suggest to test the current version, available on openSUSE
Where exactly on openSUSE? 
Comment 19 Marcus Schaefer 2007-02-02 13:53:46 UTC
changelog:

   - fixed sysp detection (#240693)
Comment 20 peter czanik 2007-02-02 13:54:37 UTC
Tested with factory downloaded this morning, I still get 'No proposal' message.
Comment 21 peter czanik 2007-02-02 13:56:10 UTC
(In reply to comment #18)
> http://ftp.opensuse.org/pub/opensuse/repositories/SaX2/
> 

But that's x86 only, this is on PPC.
Comment 22 Stefan Dirsch 2007-02-02 14:02:25 UTC
Then you need wait until it's in factory. Check after updating the package with "rpm --changelog -q sax2|less" that the fix (see comment #19) is already in.
Comment 23 peter czanik 2007-02-14 17:28:13 UTC
Changelog indicates, that the mentioned fix is already there, but problem remains.
Comment 24 Marcus Schaefer 2007-02-15 09:21:02 UTC

*** This bug has been marked as a duplicate of bug 245396 ***