SuSE 10.0 and Sax2

I've a problem, since when I installed SuSE 10.0, sax2
does no more works.This is what happen when I lunch the command :

root@linux bash 3.00 # sax2
SaX: initializing done, using cache data...
SaX: startup

root@linux bash 3.00 #

When I lunch it appears a little windows " Sax2 : importing data ",
a bar fills but then it disappears and nothing happen.
I tried to reinstall all the sax2 packages from cd and with
apt from SuSE site but nothing changes.
Does anyone has an idea ?

r adjusted his/her tinfoil beanie to post:

> I've a problem, since when I installed SuSE 10.0, sax2
> does no more works.This is what happen when I lunch the command :
>
> root@linux bash 3.00 # sax2
> SaX: initializing done, using cache data...
> SaX: startup
>
> root@linux bash 3.00 #
>
> When I lunch it appears a little windows " Sax2 : importing data ",
> a bar fills but then it disappears and nothing happen.
> I tried to reinstall all the sax2 packages from cd and with
> apt from SuSE site but nothing changes.
> Does anyone has an idea ?

Have you tried the repair function on the install CD?

Boot from the CD and proceed as if you are going to install a new
system, after the language and keyboard page you should get a menu with
"Repair" being one of the choices, let it run through all the tests and
see what it picks up, if you want you can posts here with the results
if you do not know if the repair might break something if you want to
make sure.

If it does pick up something and it looks sax based then let it repair
and see if that fixes it.

HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

baskitcaise wrote:

> r adjusted his/her tinfoil beanie to post:
>
>> I've a problem, since when I installed SuSE 10.0, sax2
>> does no more works.This is what happen when I lunch the command :
>>
>> root@linux bash 3.00 # sax2
>> SaX: initializing done, using cache data...
>> SaX: startup
>>
>> root@linux bash 3.00 #
>>
>> When I lunch it appears a little windows " Sax2 : importing data ",
>> a bar fills but then it disappears and nothing happen.
>> I tried to reinstall all the sax2 packages from cd and with
>> apt from SuSE site but nothing changes.
>> Does anyone has an idea ?
>
> Have you tried the repair function on the install CD?
>
> Boot from the CD and proceed as if you are going to install a new
> system, after the language and keyboard page you should get a menu with
> "Repair" being one of the choices, let it run through all the tests and
> see what it picks up, if you want you can posts here with the results
> if you do not know if the repair might break something if you want to
> make sure.
>
> If it does pick up something and it looks sax based then let it repair
> and see if that fixes it.

Nothing
I did the repair but in the list there was not sax and it did not analyzed
it. I tried to install nvidia drivers without success. Do you have any
clue ?

Bye
R

r adjusted his/her tinfoil beanie to post:


> Nothing
> I did the repair but in the list there was not sax and it did not
> analyzed it. I tried to install nvidia drivers without success. Do you
> have any clue ?
>
> Bye
> R

R,

Have a look in /var/log/ and see if sax has left a log in there, post it
here if you want so we can see if there are any pointers to what might
be happening.


--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

> r adjusted his/her tinfoil beanie to post:
>
>
> > Nothing
> > I did the repair but in the list there was not sax and it did not
> > analyzed it. I tried to install nvidia drivers without success. Do you
> > have any clue ?
> >
> > Bye
> > R
>
> R,
>
> Have a look in /var/log/ and see if sax has left a log in there, post it
> here if you want so we can see if there are any pointers to what might
> be happening.

ok, tonight I will post

baskitcaise wrote:

> R,
>
> Have a look in /var/log/ and see if sax has left a log in there, post it
> here if you want so we can see if there are any pointers to what might
> be happening.

Ok this is the file /var/log/Sax.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 )
/*************
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 (i586)]
PARAMETER : no parameter(s) given
:
LOG DATE : Tue Mar 14 00:38:30 CET 2006
*************/
============================
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

14-Mar 00:38:31 <X> Startup...
14-Mar 00:38:31 <X> [ Startup on already running Server:
:0.0 -> grant
]
_IceTransOpen: Unable to Parse address ^X
Session management error: Could not open network socket
_IceTransOpen: Unable to Parse address ^X
Session management error: Could not open network socket
14-Mar 00:38:31 <I> Checksum of installed configuration is invalid !
14-Mar 00:38:31 <I> Imported: Card
14-Mar 00:38:32 <I> Imported: Desktop
14-Mar 00:38:32 <I> Imported: Pointers
14-Mar 00:38:32 <I> Imported: Keyboard
14-Mar 00:38:32 <I> Imported: Layout
14-Mar 00:38:32 <I> Imported: Path
14-Mar 00:38:32 <I> Imported: Extensions

r wrote:

> baskitcaise wrote:
>
>> R,
>>
>> Have a look in /var/log/ and see if sax has left a log in there, post it
>> here if you want so we can see if there are any pointers to what might
>> be happening.
>
> Ok this is the file /var/log/Sax.log
>

I solved the problem :
During installation Server x did not start, it gaves me error of
" out of synch ", I changed the xorg.conf with another xorg.conf
inside /etc/X11 and I did solve the problem.
Now I have changed it again with the original one and sax2 started
and make the correct configuration, it was set to resolution of 1280x....
I changed to 1024x768 and changed the screen model.
It seems to be ok.

r adjusted his/her tinfoil beanie to post:


> I solved the problem :
> During installation Server x did not start, it gaves me error of
> " out of synch ", I changed the xorg.conf with another xorg.conf
> inside /etc/X11 and I did solve the problem.
> Now I have changed it again with the original one and sax2 started
> and make the correct configuration, it was set to resolution of
> 1280x.... I changed to 1024x768 and changed the screen model.
> It seems to be ok.

Good show r,

This is a problem with the default screen size and refresh rates set on
installation, if the monitor is unknown or does not report its
capabilities when probed it is set to a higher rate than most flat
screens can handle and so it will not work for some ( the figure is
obviously getting bigger now with a lot of people using flat screen )

This can make it awkward for some screens as the default does not work,
I am hoping this is fixed in the next release as it is one of the most
annoying "features", I do not suffer with it here as I still use *BIG*
crt monitors ( 21" & 20" ) which can handles most screen resolutions.

HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

> Good show r,
>
> This is a problem with the default screen size and refresh rates set on
> installation, if the monitor is unknown or does not report its
> capabilities when probed it is set to a higher rate than most flat
> screens can handle and so it will not work for some ( the figure is
> obviously getting bigger now with a lot of people using flat screen )
>
> This can make it awkward for some screens as the default does not work,
> I am hoping this is fixed in the next release as it is one of the most
> annoying "features", I do not suffer with it here as I still use *BIG*
> crt monitors ( 21" & 20" ) which can handles most screen resolutions.

ahh ook