I am trying to help a friend to install suse on his ASUS A6V Laptop. Because opensuse 10.0 left us alone with a black screen at x-startup after installation, we gave beta 3 a try. Here some of our experiences: The Installation Process was working well until it should start x in the end. The same problem as with 10.0 before. We tried to compile the proprietary ati driver 8.20.8-i386.run without succes from the commandline. Afterwards I tried sax2, and it was able to make a (very generic) guess to run x. Then it was possible to boot into KDE. We wanted to configure the monitor settings from Yast, but Yast just did not open (several tries). CTRl + ALT + Fx did not skip to a commandline-login but restarted x to kdm or xdm (I dont know for sure). Strange, not?! Unfortunately we are not able to do more testing on this machine because now we try it again with 10.0 and hope to get it working with sax2. We hope most of the problems can be fixed by the final release. cheers Peter Buschbacher

Hello, Am Dienstag, 7. Februar 2006 19:32 schrieb Peter Buschbacher:

I am trying to help a friend to install suse on his ASUS A6V Laptop. [beta3] The Installation Process was working well until it should start x in the end. The same problem as with 10.0 before. We tried to compile the proprietary ati driver 8.20.8-i386.run without succes from the commandline.

According to a bugzilla entry (don't ask for the number ;-) the radeon (open source) driver was broken (in several cases, but it works on my machine) and will be better in beta4. There are also some issues with fglrx in bugzilla - but without knowing more details, I can't tell if your problem is a known bug. Please search bugzilla yourself ;-) The next possible bug is that YaST created a non-working xorg.conf - please enter that in bugzilla also if nobody did before and attach your y2logs and /var/log/SaX.log.

We wanted to configure the monitor settings from Yast, but Yast just did not open (several tries).

Please check bugzilla if there is a similar report already. If not, please create a bugreport and attach the y2logs to it.

CTRl + ALT + Fx did not skip to a commandline-login but restarted x to kdm or xdm (I dont know for sure). Strange, not?!

radeon or fglrx driver? Again: please check bugzilla and report your problem if nobody did it before. Required attachments in this case: /etc/X11/xorg.conf, /var/log/Xorg.0.log, /var/log/Xorg.0.log.old

We hope most of the problems can be fixed by the final release.

If you file bugreports ;-) Regards, Christian Boltz --

I want to get off this list You can't leave the list... your soul is now attached to the SUSE server. If you leave, you must put the soul of someone who you love in your place. [> Robert and joao marka in suse-security]