Bug 154101

Summary:	No graphic with beta5
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Karsten Keil <karsten.keil>
Component:	SaX2	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	michael.raskey, Raghavendra_Biligiri, snwint, suse-beta
Version:	Beta 6
Target Milestone:	---
Hardware:	32bit
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	hwinfo output sax2 log

Description Karsten Keil 2006-02-28 14:06:19 UTC

I have some strange problem with one of my machines (VGA:nVidia GeForce2 MX/MX 400):
Beta5 install disk (verified with checkmedia) boots, I get the first menu
select language and install (default 1024x768), the kernel boots shows the
splashimage (all OK) load the install RD, but it give no disply after starting
yast2 - last mesage I see is virtual console found 95x43 
My Monitor entered standby (no signals on input).
All other resolutions (800x600 1280x1024, 1600x1200) give the same effect, but
VESA worked and I was able to install Beta5 but installation could not install graphic mode and end up in runlevel 3. 
Manual sax2 run gives:
SaX: initializing please wait...
SaX: your current configuration will not be read in
SaX: no X-Server is running
SaX: will start own server if needed
Died at /usr/share/sax/init.pl line 620.

So I tried to boot old betas to find out when this starts:
Beta1 - worked
Beta2 - do not show bootscreen (black) but after timeout it boots from HD
Beta3 - same as Beta2
Beta4 - same as Beta5
Beta5.2 - same as Beta5

(10.0 and all versions before run OK on this machine).
HWINFO will follow.

Comment 1 Karsten Keil 2006-02-28 14:07:31 UTC

Created attachment 70627 [details]
hwinfo output

Comment 2 Stefan Dirsch 2006-02-28 14:18:22 UTC

First problem is probably related to the bug in the new package manager, which tells SaX2 that no X11 is installed and therefore SaX2 doesn't write a config file. The Xserver doesn't find a valid config file and tries to start a vesa driver configuration, which obviously doesn't work with your gfx card. 

Could you try "sax2 -r" in runlevel 3? Attach /var/log/SaX.log.

Comment 3 Karsten Keil 2006-02-28 15:30:43 UTC

Created attachment 70658 [details]
sax2 log

Comment 4 Stefan Dirsch 2006-02-28 15:49:10 UTC

I think I just stumbled over the same problem. Do you currently have framebuffer disabled? Check with "fbset". I can reproduce this problem when it isn't. IMHO this would be a SaX2 bug.

Comment 5 Karsten Keil 2006-02-28 16:02:49 UTC

fbset gives: no such device /dev/fb0 - and yes there is nothing with fb* in /dev.

Comment 6 Stefan Dirsch 2006-02-28 16:23:26 UTC

Enable framebuffer and SaX2 will work --> SaX2 bug. I think it's a segfault in "sysp -s xstuff" when /dev/fb0 does not exist.

Comment 7 Karsten Keil 2006-02-28 16:38:46 UTC

Yes sysp -s xstuff  segfaults

Comment 8 Karsten Keil 2006-03-02 00:12:01 UTC

JFYI, Beta6 has the same problems as Beta5.

Comment 9 Marcus Camen 2006-03-02 22:43:48 UTC

Hmmm... Related to bug #154775 and #148271 ?

Comment 10 Marcus Schaefer 2006-03-06 11:59:08 UTC

The problem only occurs if there is no framebuffer plus the
monitor couldn't be detected (no DDC data)

fixed

Comment 11 Marcus Schaefer 2006-03-06 13:18:24 UTC

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

Comment 12 Karsten Keil 2006-03-06 13:23:32 UTC

Which packages should I update on a B6 to verify it ?

Comment 13 Marcus Schaefer 2006-03-08 16:59:03 UTC

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

Comment 14 Karsten Keil 2006-03-09 13:36:33 UTC

OK SAX2 seems to work now, but I still cannot install with the default
(1024x768) or other resolutions (which was working up to Beta1).

Comment 15 Marcus Schaefer 2006-03-09 13:39:44 UTC

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

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

Comment 16 Eric Ward 2006-03-09 17:15:39 UTC

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

Comment 17 Marcus Schaefer 2006-03-10 10:59:44 UTC

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