Bug 116549

Summary:	Desktop unstable after installation on Toshiba Satellite P35-S629
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	dante bly <blade2445>
Component:	Kernel	Assignee:	Stefan Dirsch <sndirsch>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	eich
Version:	RC 1
Target Milestone:	---
Hardware:	x86
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description dante bly 2005-09-12 16:15:12 UTC

After installation of RC1, the mouse movements are "jumpy" and the system will
freeze after a few seconds. This occurs even with no applications running. 

The system becomes a bit more stable if I load in failsafe mode and start KDE
with the command "startx". However, even with this method, the system still
often freezes. 

I don't know what else I can report. 

Hardware is:

  Pentium 4 processor 548
  17.0" WXGA truebrite monitor
  ATI mobility radeon 97000 graphics

Comment 1 Dr. Werner Fink 2005-09-12 16:19:38 UTC

*** Bug 116552 has been marked as a duplicate of this bug. ***

Comment 2 Dr. Werner Fink 2005-09-12 16:21:23 UTC

Does this depend on bug 115226

Comment 3 Dr. Werner Fink 2005-09-13 09:21:45 UTC

I don't think the bug is related to the one you
mentioned. The desktop freezing may be related to a
previously reported bug regarding an ial and fnfx
conflict on toshiba laptops. I think someone fixed
this bug by removing ial when there was a conlict with
fnfx. However, I'm not sure if this is what's causing
the desktop freezing problem.

I've tried installing both suse 9.2 and 9.3 on this
laptop and both failed to even install. It seems this
laptop is very unfriendly to linux.

Comment 4 Lubos Lunak 2005-09-14 15:45:23 UTC

I don't think this bugreport has anything to do with KDE. Does it work correctly if you 
don't use KDE but e.g. GNOME or WindowMaker?

Comment 5 Stefan Behlert 2005-11-18 14:06:12 UTC

So, this bug report contains two bugs: 
a) the jumpy mouse
b) the freezing.

I assume the problem is still available with the final release.

Let's concentrate on b), please open another bug for a) if it's still present after you have started sax2 and tested if another mouse-setting is working.

The freezing is a problem. Can you attach /var/log/messages, hwinfo-output and lspci?

Comment 6 Chris L Mason 2005-11-18 14:19:28 UTC

ATI mobility radeon 97000 graphics

Are you using the 3d radeon driver?  If so, does the problem go away without it?

Comment 7 dante bly 2005-11-20 22:18:50 UTC

I no longer have RC1 cds, but I tested Suse 10.0 dvd version on a Toshiba Satellite and the problem still exists. I tried both Gnome and KDE with the same results. 

When I try to install Suse 10.0, it goes through the preparation stage but goes to a black screen after all the software has been installed. It never makes it to the configuration stage of the installation. When I reboot, GRUB loads fine, but when I try to boot into Suse I just get a black screen.

When I try to boot into failsafe mode, I get the message "Graphical interface could not be started". So this is probably a video driver problem.

During the hardware detection part of the installation, I looked at hardware details. Under VGA compatible controller" it said "Toshiba America info RV350 NP". 

I was unable to modify the video driver because that option is only available in the "configuration" portion of the installation.

Comment 8 Olaf Kirch 2005-11-21 08:26:20 UTC

Assigning to X11 folks

Comment 9 Stefan Dirsch 2005-11-21 08:56:10 UTC

Could you attach X.Org config and logfile? Thanks.

Comment 10 dante bly 2005-11-22 19:16:45 UTC

I don't think I can even get to the X.org config and log files since I can't even complete the installation with version 10.0 dvd. 

I recently tried installing 10.1 Alpha 3 version on the Toshiba laptop and everything works fine. In still uses the ATI RV350NP driver for the graphics card, but so far I don't see any problems.

Comment 11 Stefan Dirsch 2005-11-22 19:34:34 UTC

Ok. I close this now as FIXED (for 10.1).