Suse 10 and X-Windows/Sax2 Problems
Hi all! After successfully installing Suse 10 on my Averatec Notebook, I installed Suse 10 on my Dell Latitude CPx (Pentium III) Notebook. The installation went without any problems. But when I started the new system on the Dell, all troubles began. Instead of getting the normal splash screen that, after a while, opens the KDE system, I get a black screen, that slowly gets grey-white. It is as if something is burning up the monitor from the left bottom corner. Later pink and blue vertical stripes appear and the normal chimes that KDE has started. I cannot see anything. I first thought, that I had configured the graphics hardware wrongly. I installed Suse again - same results. Then I started Suse in Failsafe Mode. After I logged in and entered "starx" X-Windows and KDE started as they always do. I left X-Windows and started sax2 and could configure X as normal. I made sure that all the settings were right (of course they were, as in Failsafe Mode I had no problems with X). Then I restarted in Normal mode. I still have the same problem with X-Windows. When I start sax2 the same happens. When I start Yast and try to configure the display, the same happens. If it would not work in Failsafe mode, I would say, that I had a driver problem or something like that. But it must be something else causing the problem. What could that be? Kind regards Anette Seiler
On Oct 27, 05 13:01:58 +0200, Anette Seiler wrote:
After successfully installing Suse 10 on my Averatec Notebook, I installed Suse 10 on my Dell Latitude CPx (Pentium III) Notebook. The installation
Are you referring to SUSE Linux 10.0? There is no Suse 10.
get a black screen, that slowly gets grey-white. It is as if something is burning up the monitor from the left bottom corner. Later pink and blue vertical stripes appear and the normal chimes that KDE has started. I cannot see anything.
This seems to be a driver bug, as the LCD is not driven at all. During installation a different (slow) driver is used, which doesn't expose this problem.
If it would not work in Failsafe mode, I would say, that I had a driver problem or something like that. But it must be something else causing the problem. What could that be?
Please open a a bug in bugzilla, with the information given in
http://www.opensuse.org/Bugs:X
Perhaps you want to play around a bit with the options that are used
during failsafe login. E.g. select failsafe, press F2, and delete all
options (which only leaves framebuffer mode disabled, so you won't get
the splash screen).
Matthias
--
Matthias Hopf
participants (2)
-
Anette Seiler
-
Matthias Hopf