I have experienced 1. on my PC with OS 13.1 after an update that I can’t fully boot the system with OS13.1. ( Link to topic)
Fortunately I have a partition with Win7 -64 pro on the teh same PC which is running without any problem. So no hardware problem !
Then today my wife got after a slow running update of the standard kernel the same problem on her Asus Notebook with OS 13.1 as well and the I remembered that this was the same that happened to my PC last sunday:Kernel update. The symptoms are absolutely equal like those on my PC before.
This can’t be by chance, this must be coincidence, thus I give you this warning !!!
Could it be that someone is able to break into the update procedure or is it just a stupid bug ?
My wife’s notebook was downloading during the update process and it was not finished downloading and because it was very slow she asked the os to shut down. Thus we can assume that in theory it should not have had an impact. As the OS accepted to shut down the pc I assume the update task had not blocked the shut down option yet.
But unfortunately there is an impact now: the system does not boot any longer into the GUI.
had similar experience, checked journal and log files and it showed in the xorg log file that the xserver started then shut down without an error message. So… rebooted machine (13.1 64bit) at the grub2 boot menu I added : init 3 let the machine boot with the new kernel to the init 3 login prompt logged in as root issued command: init 5 && exit the normal graphical login screen appeared and everything worked normally. this of course is a workaround, and after some playing around, I found that reverting to the previous version of systemd and udev (v.208 which is still in the update repo) got me back to a normal boot without the extra steps. unfortunately i don’t have the time to investigqate this further and post it here in hopes that someone with the appropriate knowledge will find out exactly and submit the bug. There are problems littered through the forum about this and network issues which may have the same culprit. cheers.
Hi thanks for your reply, gives me back some hope that 3.11 may run again.
Where at the GRUB2 do you have added something after reboot ?
When my Grub menu starts I have only 2 options:
“OpenSuse 13.1” and “Advanced options for OpenSuse 13.1”, the later one leads to a list of entries with versions:
openSuse 13.1, with Linux 3.11.10-32-desktop
openSuse 13.1, with Linux 3.11.10-32-desktop(recover
openSuse 13.1, with Linux 3.11.10-32-default
openSuse 13.1, with Linux 3.11.10-32-default(recover
openSuse 13.1, with Linux 3.11.10-29-desktop
openSuse 13.1, with Linux 3.11.10-29-desktop(recover
openSuse 13.1, with Linux 3.11.10-29-default
openSuse 13.1, with Linux 3.11.10-29-default(recover
and that’s all I can do.
(A hint for those, like me, who do not see immediateley any difference in these entries: ignore the first 80% of each entry : look at the version number and the last or 2 last words, although I still don’t know the difference between desktop & default, as both simply do not boot, but Recover… shows the log)
Hi thanks for your reply, gives me back some hope that 3.11 may run again.
Where at the GRUB2 do you have added something after reboot ?
When my Grub menu starts I have only 2 options:
“OpenSuse 13.1” and “Advanced options for OpenSuse 13.1”, the later one leads to a list of entries with versions:
openSuse 13.1, with Linux 3.11.10-32-desktop
openSuse 13.1, with Linux 3.11.10-32-desktop(recover
openSuse 13.1, with Linux 3.11.10-32-default
openSuse 13.1, with Linux 3.11.10-32-default(recover
openSuse 13.1, with Linux 3.11.10-29-desktop
openSuse 13.1, with Linux 3.11.10-29-desktop(recover
openSuse 13.1, with Linux 3.11.10-29-default
openSuse 13.1, with Linux 3.11.10-29-default(recover
and that’s all I can do.
(A hint for those, like me, who do not see immediateley any difference in these entries: ignore the first 80% of each entry : look at the version number and the last or 2 last words, although I still don’t know the difference between desktop & default, as both simply do not boot, but Recover… shows the log)
When the boot hangs long enough, I can press ALT-F1 for terminal mode and can login as normal user and then as SU (!) and then I can start KDe with ‘startx’, but its of course not the users KDE, but I assume the one for the superuser !? I can’t startx as normal user.
What a mess, good that I could stop all the other PC’s in our foundation from updating.
could do a zypper refresh, followed by a zypper update, but it does not solve the problem at all.
The network manager needs now 27 seconds to start … for a notebook with an SSD this feels like a century.
Well,yes xavier’s suggestion sounded good indeed and if I would have known how to do so, I would have done it !
So I am forced to play around with those options I have access to and may lead to something !
I used more than 15 years Windows and thus my 1.5 years of Linux knowledge is quite limited.
I was able to start yast in teh command line mode and got a text version of yast.
There I switched the from Lan Manager to IFup and … now the system boots again until KDE runs!!!
Network is also working, Virtualbox with Win7 too - but …
all this only with a 1024x768 resolution.
gogalthorp If you get to a command line as root you could run yast and downgrade the packages.
Thanks for your reply, gogalthorp
Ok how can I find out which package version has to be rolled back to which version ?
Where can I find the update log file ?
TIA, Joe
UPDATE: After a reboot the system seems to run normal again - full resolution !!!
Tried to switch back to Lan Manger and got back in the old mess caused by the update.
Back to ifup and everything runs again, but booting still takes 10 times longer as usual !!
Well I hope that this tells those with Linux knowledge a bit and helps to identify where the problems start.
After updating a 13.1 laptop yesterday I experienced the same issue: a blank screen with the terminal last output being “Graphics target reached” or words to that effect.
I could only login to the desktop as root, running startx from the root command prompt.
Solution was to downgrade systemd and systemd-sysinitV from 210 to 209 (didnt try 208), using ncurses yast2. That’s a very nice tool to have ;).
You should check on bugzilla and see if the problem has been reported and if a fix is coming if no fix yet but reported add a me too post if not reported add the problem so it gets fixed
I’ve searched countless pages with the “reached target graphical interface” combined with “stuck at boot” search terms but no solution. Using Ctrl Alt F2 gave me a console and startx as user worked after changing the /usr/bin/Xorg permissions but things were still acting strange, sound didn’t work for example. Running kdm as root from the command line showed the loging screen but then both sound and network didn’t work. Also USB storage devices needed a password to mount.
After reinstalling X11, kdm &kde and the kernel I suspected the updates and reverted all udev things one step, which solved the problem. The nasty thing is that this is difficult to google, the symptoms mimick very different situations such as a wrongly configured x server, graphics card driver problems and such. After I found the udev downgrade worked I thought “lets post it so other people notice it”. When arriving on the forum here I noticed this thread, and it appears I’m not alone. If only this thread appeared in google, would’ve saved me a few hours.
This happened on my work laptop, somewhat nasty although I’m happy I found the workaround of startx early enough to keep working. What way would I need to go to get this properly solved? It’s a rather nasty problem, if a lot of people are affected it should be solved quickly.
I completly reinstalled now OS 13.1 (tried Leap 42.1, but became nearly mad with it: missing or other functionality; bugs, assumed as solved, boot time 5 minutes with SSD etc. - After the 4th installation I gave up)
After the brandnew installation of OS 13.1 I want to run the updates, but… I only want those updates published before the 01.01.2016, as I don’t want to end up again with which the mess began: OS 13.1 Updates (january or february) made my pc and my wifes notebook unusable and I am now trying to find a usable solution.
Thus, is it somehow possible to update OS 13.1 after a brandnew installation (just from a USB stick and no network ressources) limited up to a certain date ?
I know it has been nine months but I just now have a little time to try to address this issue plus I cannot update the latest kernel without losing the last version that does not have this problem.
I have experienced the same problem but was able to use my OSE 13.1 laptop by booting into the previous kernel. The last kernel that worked is 3.11.10-34-desktop. Unfortunately, I have two later kernel upgrades i need to apply but cannot without losing 3.11.10.
Is the recommended solution still to downgrade systemd, systemd-sysvinit and udev to 208 (I am currently at 210)?
Is there a way to make sure kernel version 3.11.10-34 stays around just in case?
