https://bugzilla.novell.com/show_bug.cgi?id=390837 User brian@aljex.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390837#c31 white brian <brian@aljex.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brian@aljex.com --- Comment #31 from white brian <brian@aljex.com> 2008-07-01 12:23:21 MDT --- I don't even use the vnc install option myself so I'm not highly motivated to fix it or see that it gets fixed either, but I can confirm it's definitely broken in the final release 11.0 when trying to install onto 2 different Dell PowerEdge 1550. These are dual p3 with 1G registered ecc ram. I have not tried the 11.0 vnc installer on other machines. I have tried the vnc installer from opensuse 10.3 on the same machines and it worked fine. I have installed 10.3 and 11.0 using everything but vnc (serial console, ssh, and regular direct gui console) and those install methods all worked fine and the resulting installed os shows no problems. If I can find any way to spare any of my copious free time, I'll try to find a machine that doesn't produce the same results. There is one suspect thing. The machines display no problems running linux/freebsd/dos/freedos, but they do cause memtest86+ 2.01 to display an error that a tiny bit of ram at the top end of the physical address space is bad. It doesn't matter how much ram is installed or what physical chips are installed or in what order, the error is always the last few K at the top end. And, both machines do the same thing, and I've read other people describing the same thing for years on these particular machines and other similar ones from Dell. So, that appears to be some kind of bios shadowing. My install kernel, initrd, and oss repository all came from this script, run and re-run several times well after the final release of 11.0. [code] SYNC="rsync -a --del --delete-excluded --exclude ppc --exclude ppc64 --exclude src --exclude SRPMS $@" # 11.0 $SYNC rsync://mirrors.kernel.org/mirrors/opensuse/distribution/11.0/repo/oss /opt/SUSE/11.0 $SYNC rsync://mirrors.kernel.org/mirrors/opensuse/distribution/11.0/repo/non-oss /opt/SUSE/11.0 $SYNC rsync://rsync.opensuse.org/opensuse-updates/11.0/* /opt/SUSE/11.0/update $SYNC rsync://ftp5.gwdg.de/pub/linux/misc/packman/suse/11.0/* /opt/SUSE/11.0/packman [/code] The clients booted the kernel and initrd via pxe. The exact pxelinux config stanza was: LABEL opensuse KERNEL linux APPEND initrd=initrd showopts install=http://host/SUSE/11.0/oss vnc=1 vncpassword=foo More details about my test, including vc4 error messages are here: http://lists.opensuse.org/opensuse/2008-06/msg02365.html It's really part of this thread but I was posting from a new machine without the prior posts to reply to: http://lists.opensuse.org/opensuse/2008-06/msg01931.html And at least someone else has the same problem: http://forums.opensuse.org/install-boot-login/386983-remote-vnc-controlled-i... I'd say there is a problem that doesn't affect every machine, and appears in a feature that not many people use, and so the reports will be a bit rare, but I think it's hard to say the problem doesn't exist. But perhaps it's just hard for me to say that because I am staring at 2 machines showing the problem. Remember, the same feature in the 10.3 installer does not fail on the same hardware, 2 different copies of the same hardware. -- 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.