Bug 407165

Summary:	VNC installation not possible (at least with NET CD)
Product:	[openSUSE] openSUSE 11.0	Reporter:	Thomas Schallar <thomas.schallar>
Component:	Installation	Assignee:	Stefan Dirsch <sndirsch>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	max
Version:	Final
Target Milestone:	---
Hardware:	i386
OS:	openSUSE 11.0
Whiteboard:
Found By:	Corporate Interoperability Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Thomas Schallar 2008-07-08 14:45:02 UTC

Hello!

I'm using openSUSE-11.0-DVD-i386.iso to install openSuSE 11.0 on a hardware, that works flawlessly with SuSE 10.2 and 10.3: Asus P5K-VM, Intel Q9450 4x2.6GHz, 4x2GB DDR2-800 Corsair DHX RAM, 3Ware 9650SE-8LPML SATA2-RAID5, 8x1TB Seagate.

Since many years we install SuSE Linux by network (PXE+HTTP) using the linuxrc options:

  vnc=1 vncpassword=test1234

I tried that with the network installation CD. After a while, the VNC screen becomes available. When I connect with RealVNC to <ip>:1 I see a distorted picture of YaST. When I move the mouse cursor, YaST crashes, the VNC windows closes and the red error text screen shows up on the machine.

I tried several times, downgraded to 1x2GB RAM, disabled the memory remap function, tried ACPI etc. off. Always the same.  :-(

The very same procedure worked for us since SuSE 9-dot-something...

regards from Vienna,
Thomas Schallar

Comment 1 Robert Vojcik 2008-07-18 10:19:19 UTC

Hello, 

could you provide yast2 logs from installation and some screenshot ?
If you unsure follow:
http://en.opensuse.org/Bugs/YaST

Thanks

Comment 2 Kurt Garloff 2008-09-15 11:52:02 UTC

As far as I can determine, YaST2 uses Xvnc for vnc installation.
(See common/vnc.sh in yast2-installation.)
Xvnc writes logs to /var/log/YaST2/vncserver.log, which may be useful for
debugging this further.

Comment 4 Stefan Dirsch 2008-09-15 12:03:26 UTC

This sounds like another duplicate of Bug #389386, which has been fixed by the Driver update feature, i.e. press F6 at the beginning of installation.

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