On Saturday 05 February 2011 19:54:46 Felix Miata wrote:
On 2011/02/05 19:31 (GMT+0200) Stan Goodman composed:
Before preparing to upgrade to KDE4.6, I found that the system wanted to install essential patches. I debated whether to accept this or to pass on it and upgrade KDE first. I took what turns out to be the wrong choice, and accepted the patches.
When the smoke cleared away an hour or so later, I was asked to reboot, which I did. The boot never finished, but froze while the chameleon screen was still up, with the mouse cursor stuck in the center and the keyboard dead. I reset, and the new reboot ended with a black screen, but with all else frozen as before. I would like, if possible, to avoid reinstalling v11.3 from scratch; if somebody has a better idea, please mention it.
Type a <space> 3 when the Grub menu comes up, then press <Return>. That should get you into text mode with full networking. Login as root on tty2 and open mc. Login as root on tty3 and do 'zypper up' and see if it finds anything to do. If it does, let it proceed, then either try rebooting normally, or switch to tty2, navigate to /etc/zypp/repos.d/, where you'll want to configure a file for using the 4.6 repo. One way to do that is if you have a 4.5.5 already configured, just edit it using mc's internal editor to change title, name, and applicable URL. First make a copy for backup [highlight old file; shift-F3; end; BS: removes "o" from name of original filename, creating new file with .rep as ending] Once that's done, goto tty2 and do zypper ref. If no errors, do zypper dup. If while all this is going on you need internet access, you can right inside mc via its built in FTP, such as fetching an RPM or getting a repo URL correct in your mind. After zypper dup is done, try rebooting normally. Look at man zypper for the -r command if you want only to upgrade from a particular repo, such as your new 4.6.
Felix... After the <space> 3 to get into text mode, the system returned to the chameleon screen, moved the progress gauge a bit, and froze for about five minutes. After several minutes more, I happened to glance at it again, and found it had entered actually entered text mode -- this timing does not look like previous times when I have entered runmode 3. At the bottom of the logging sequence appear the following lines: ----- Starting Firewall Initialization (phase 2 of 2) Master Resource Control: runlevel 3 has been <--sic Failed services in runlevel 3: Skipped services in runlevel 3: Welcome to openSUSE 11.3 "Teal" - Kernel 2.6.34.7-0.7-desktop (tty1). poblano2 login: WARNING: Number of errors: 0, skipped probes:57 ----- Does that last line modify your suggested procedure? I am now logged into tty1; I will search how to switch to another tty, but if you want to give a hint, that would be helpful. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org