https://bugzilla.novell.com/show_bug.cgi?id=447433 Summary: Installation through vnc fails in openSUSE-11.1-Beta3 Product: openSUSE 11.1 Version: Beta 5 Platform: PowerPC-64 OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bugproxy@us.ibm.com QAContact: jsrain@novell.com Found By: Third Party Developer/Partner Partner ID: LTC 49449 =Comment: #0================================================= Pavan Naregundi - /var/log/YaST details VNC installation fails in openSUSE-11.1-Beta3 saying "couldn't create VNC password file". Message in console notices during installation through image in Hard Disk: ==============================

3

Choose the hard disk partition. 1) sda2 (38 GB, ext3) 2) sda5 (18 GB, ext3)

2

Enter the source directory> /suse/ Loading Installation System (1/6) (20644 kB) - 100% Loading Installation System (2/6) (36712 kB) - 100% Loading Installation System (3/6) (3676 kB) - 100% Loading Installation System (4/6) (1412 kB) - 100% Loading Installation System (5/6) (2356 kB) - 100% Loading Installation System (6/6) (51 kB) - 100% Reading Driver Update... No new Driver Updates found starting hald... ok starting syslogd (logging to /dev/tty4)... ok starting klogd... ok starting slpd to announce VNC... starting yast... Probing connected terminal... Initializing virtual console... -I: symbol lookup error: -I: undefined symbol: _nc_free_tinfo Found a Linux console terminal on /dev/console (80 columns x 62 lines). Password too short *** Fatal Error occured, process stopped *** - Commandline available at <Alt-F2> - Further information written to: /var/log/YaST2/y2start.log ================================================ =Comment: #1================================================= Cijurajan Kollanoor <> - Pavan, Is this a regression from the previous beta releases? Are you able to install using test mode of installation? I could see some messages in yast logs: --- |-- couldn't create VNC password file... |-- VNC access has been disabled due to a password exception |-- Please make sure the password is at least 8 characters long --- Did you try with a password of eight or more characters? =Comment: #2================================================= Pavan Naregundi - (In reply to comment #1)

Pavan,

Is this a regression from the previous beta releases? No.

Are you able to install using test mode of installation? I can bypass this stage using test mode, but unable to complete installation because of other errors.

I could see some messages in yast logs:

--- |-- couldn't create VNC password file... |-- VNC access has been disabled due to a password exception |-- Please make sure the password is at least 8 characters long ---

Did you try with a password of eight or more characters?

I have given eight character password.

Thanks Pavan =Comment: #6================================================= Pavan Naregundi - Tried it on openSuSE 11.1 Beta5, error occurs on installation through Hard disk image. In my scenario I have image in /dev/sda8 in /suse directory. My /etc/lilo.conf entry looks as follows image=/boot/inst64 label=slp append="quiet sysrq=1 install=slp " Boot prompt option looks like: boot: slp vnc=1 Error message is as follows ================= boot: slp vnc=1 Please wait, loading kernel... Allocated 01400000 bytes for executable @ 03500000 Elf32 kernel loaded... SuSE Linux zImage starting: loaded at 03500000-0477dd30 (4000000/0/02039a68; sp: 02e7fd50) uncompressing ELF header done. (00000100 bytes) Allocated 00efc588 bytes for kernel @ 04900000 Leave 00f45890 bytes for initrd @ 0382b771 uncompressing kernel done. (00a2a9f8 bytes) entering kernel at 04910000(382b771/f45890/02039a68) OF stdout device is: /vdevice/vty@30000000 Hypertas detected, assuming LPAR ! command line: quiet sysrq=1 install=slp vnc=1 memory layout at init: alloc_bottom : 0000000005511000 alloc_top : 0000000008000000 alloc_top_hi : 0000000008000000 rmo_top : 0000000008000000 ram_top : 0000000008000000 Looking for displays instantiating rtas at 0x0000000007632000 ... done boot cpu hw idx 0000000000000000 starting cpu hw idx 0000000000000002... done copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x0000000005812000 -> 0x0000000005813569 Device tree struct 0x0000000005814000 -> 0x0000000005822000 Calling quiesce ... returning from prom_init Moving into tmpfs... done. Integrating /parts/00_lib insmod /modules/squashfs.ko mount: /parts/00_lib: we need a loop device mount: using /dev/loop0 Integrating /parts/01_usr mount: /parts/01_usr: we need a loop device mount: using /dev/loop1

...

...

openSUSE installation program v3.3.15 (c) 1996-2008 SUSE Linux Products GmbH <<<

Starting udev... sd 0:0:1:0: [sda] Assuming drive cache: write through sd 0:0:1:0: [sda] Assuming drive cache: write through ok Loading basic drivers... ok Starting hardware detection... ok (If a driver is not working for you, try booting with brokenmodules=driver_name.) IBM Virtual SCSI 0 drivers: ibmvscsic* Reading driver update: disk:/?device=*usb* No new driver updates found. Sending DHCP request to eth0... *** Could not find the openSUSE Repository. Activating manual setup program.

...

...

Linuxrc v3.3.15 (Kernel 2.6.27.5-2-ppc64) <<<

Main Menu 1) Start Installation 2) Settings 3) Expert 4) Exit or Reboot

1

Start Installation 1) Start Installation or Update 2) Boot Installed System 3) Start Rescue System

1

Choose the source medium. 1) DVD / CD-ROM 2) Network 3) Hard Disk

3

Choose the hard disk partition. 1) sda6 (20 GB, ext3) 2) sda7 (28 GB, ext3) 3) sda8 (6.0 GB, ext2) 4) sda9 (6.0 GB, ext3) 5) sda10 (6.0 GB, ext4dev) 6) sda11 (12 GB, reiserfs)

3

Enter the source directory

/suse/ Loading Installation System (1/6) (21880 kB) - 100% Loading Installation System (2/6) (37844 kB) - 100% Loading Installation System (3/6) (3677 kB) - 100% Loading Installation System (4/6) (1508 kB) - 100% Loading Installation System (5/6) (2580 kB) - 100% Loading Installation System (6/6) (52 kB) - 100% Reading Driver Update...

No new Driver Updates found starting hald... ok starting syslogd (logging to /dev/tty4)... ok starting klogd... ok starting slpd to announce VNC... starting yast... Probing connected terminal... Initializing virtual console... Found a Linux console terminal on /dev/console (157 columns x 42 lines). Password too short *** Fatal Error occured, process stopped *** - Commandline available at <Alt-F2> - Further information written to: /var/log/YaST2/y2start.log ========================= -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.