Johann Spies <johann.sp...@gmail.com> writes: > This morning my work laptop would not boot. I could not even get to single > user mode initially and when I got as far as that I could not > type anything on the terminal. I suspect some upgrade yesterday caused it. > > In the end I had to search for a windows user who could write me a > debian-live cd. > > Using this, I could, after using some hints shown in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358 get my system to > boot (taking > about 10 minutes do do so) and just as I started to work it rebooted > spontaneously. > > In the end after several experiments, I removed systemd and as a result a lot > of other packages, reinstalled sysvinit and it booted normally > again and now I can work. > > I know systemd is not an option any more, but if this is the way it is going > to waste my time, I will have to look at a reinstallation of my > system and then use something that is less buggy than Debian Testing/Sid. > > I have heard from a colleague of mine that on Mandriva and other systems he > has used systemd without such problems. > Yesterday I had the same problem when I rebooted, it left me at a tty screen, where I was prompted to input my login and password, it then lead on to my lightdm screen, as expected.
Whilst booting it showed an error message, which I've since been unable to find, that systemd had broken error/start messages. It was a bit of a shock to find that I was now using systemd, as I was intending to not use it until forced to, but since then I haven't found any problems, but then I haven't rebooted since then either. Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.5, emacs 24.3.92.1
signature.asc
Description: PGP signature
