Hi guys, I’ve done a fresh install of opensuse 13.1 and everything was fine, so I decided to switch to tumbleweed and following the normal wiki procedure I’ve done too many times (so disabling old repo, adding the new ones with one-click install and zypper dupping) I’ve updated my system.
After the reboot I get stucked at:
“starting command scheduler” and there’s nothing I can do, only manually reboot.
Thanks in advance for the help
This thread will be moved to the Tumbleweed forum and is CLOSED for the moment.
Moved from Install/Boot/Login and open again.
I don’t know exactly what is causing your issue, but from my “messages” log the next startup phase would be “Starting Multi-User System”, so it hasn’t been able to reach that target then complete “Startup” by “Starting Graphical Interface” and quitting Plymouth.
I hope that gives someone else a clue… 
And please check in YaST->System->Services Manager that the default target is actually “graphical” or “runlevel5”.
Maybe you are missing the symlink /etc/systemd/system/default.target for some reason?
Try to explicitely add “5” to the kernel boot options by pressing ‘e’ add the boot menu.
If that doesn’t help, add “init=/bin/sh” to at least get into a minimal text system.
With Init=5 nothing changes but with Init=/bin/sh I can start a basic shell. strangely now boot stops at “starting accounts”
Mine shows “runlevel5” as default system target.
From Services Manager, I see this service started Command Scheduler:
cron.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/cron.service; enabled)
Active: active (running) since Mon 2014-04-28 10:24:58 BST; 2min 26s ago
You should add just “5”, not “Init=5”.
but with Init=/bin/sh I can start a basic shell. strangely now boot stops at “starting accounts”
That’s when you add “init=/bin/sh”?
Don’t you get a shell prompt then?
Yes, that’s the default for a graphical installation.
But runlevel5.target is just a symlink to graphical.target, so it doesn’t really matter which one of those 2 you set.
Hello,
It seems I have the same problem since a recent update… The Gnome session manager does not start, I am perfectly able to enter a terminal (ctrl + alt + F1) but the system hangs at the gecko screen 
Any ideas on which tests to run to diagnose the issue ? Already tried adding “5” but to no avail and I don’t think the other lead was of help as I can log into a shell the usual way.
Any help will be appreciated,
Thanks a lot !
Are you using the proprietary nvidia driver, installed “the hard way” (i.e. by downloading and running the .run file from the nvidia homepage)?
There was an update for xorg-x11-server recently that breaks the nvidia driver if installed that way.
So if that’s the case, re-install the driver and everything should work again.
Background: the nvidia driver replaces files of xorg-x11-server and Mesa-libGL1 with its own versions on installation. If one of those packages gets updated, the nvidia version will be replaced by the standard version again, breaking the nvidia driver.
This should not happen when you install the driver via the packages from the nvidia repo, though.
Tried just with “5” nothing changes.
With init=/bin/sh I get a prompt.
I have an Intel integrated videocard, no nvidia cards.
Anyway now if during the boot I hit alt+F1 to see the logs, the boot stops on “Starting Accounts”
Ok, then the default target should not be the problem.
But do you get to a text mode login when adding “3”, or does it hang then as well?
I have an Intel integrated videocard, no nvidia cards.
Ok, that was just an idea.
Anyway now if during the boot I hit alt+F1 to see the logs, the boot stops on “Starting Accounts”
Do I understand you correctly that it’s quite random?
Try adding “plymouth.enable=0” to the boot options. Where does it stop then?
Have you tried “Recovery Mode” yet? (Advanced Options in the boot menu)
When the boot hangs, please press Ctrl+Alt+F10 and post the last lines on that screen. Is there any error message?
With plymouth.enable=0 I have black screen but with ctrl+alt+F1 I can login from a console.
In recovery mode stucked anyway, this is the ctrl+alt+F10 output:
http://i61.tinypic.com/5446a.jpg
In normal boot, the output is:
http://i59.tinypic.com/11ta1x2.jpg
Even here I can login with ctrl+alt+F1 so currently I can correctly login only from terminal.
I see a crash there, apparently related to the audio driver.
In normal boot, the output is:
At the bottom there I see messages from iwlwifi which is unable to load the firmware, and pulseaudio (which would point to the audio driver again I suppose).
My first thought: do you have kernel-firmware installed?
As you are using the Kernel:stable repo apparently, do you also have the updated kernel-firmware from there?
rpm -qi kernel-firmware
EDIT: Oops sorry, you are actually using Tumbleweed. AFAICS there’s no updated kernel-firmware in the Tumbleweed repo. So just check whether it is installed at all.
Also, can you try booting an older kernel in “Advanced Options” in the boot menu?
Does that still work?
There is definitely no kernel-firmware update in Tumbleweed repo. It should be installed from Current Oss Updates repo.
I’ve checked and kernel-firmware is correctly installed.
At the moment I can not paste the output of
rpm -qi kernel-firmware
but when I tried few hours ago version was 3.6 or kind of.
I don’t know if It’s important or not but:
on “zypper dup” Ie says that everything is up to date, but if I try “zypper up” It tries to update the kernel to 3.11 and It’s a bit strange because tumbleweed rrepo all are correct and the currect kernel is 3.14 (the one I’m doing these tests from).
3.6?
The version should be 20130714git.
I don’t know if It’s important or not but:
on “zypper dup” Ie says that everything is up to date, but if I try “zypper up” It tries to update the kernel to 3.11 and It’s a bit strange because tumbleweed rrepo all are correct and the currect kernel is 3.14 (the one I’m doing these tests from).
That’s “normal”. “zypper up” wants to install the kernel update from openSUSE-Current-Updates.
Wouldn’t actually change anything, as you would still be using the higher versioned 3.14.1 kernel.
You’re not supposed to use “zypper up” on Tumbleweed though.
But have you tried to boot to an older kernel?
I’ve tried to boot an old kernel but I’ve the same problems.
Ok about zypper.
rpm -qi kernel-firmware
gives
Which kernel did you boot?
Do you still have a 3.11.x kernel installed you could try?
I’d like to find out whether it’s related to the kernel or not.
Another thing I would try is to set “DISPLAYMANAGER=xdm” in /etc/sysconfig/displaymanager.
Maybe it is an installation problem with your desktop environment/display manager. xdm should work in any case.
Tried also with 3.11, It’s the same, so I think it’s not about the kernel but about something else.
Since this notebook is going to be in assistance because of some dead pixels I will not have available this computer for some days. I really don’t need kernel 3.14 I can live with 3.11 when I will get back, I’ll try again and I will let you know.
Thanks for your help!