Hello, Michael - Yes, I was able to SSH into the machine from a Windows box on the same subnet. The mask configuration above didn't help, I'm afraid.
Thanks - On Sat, Dec 27, 2014 at 4:56 PM, Michael Biebl <bi...@debian.org> wrote: > control: tags -1 moreinfo > > Am 27.12.2014 um 14:58 schrieb allan grossman: > > Package: systemd > > Version: 215-8 > > Severity: critical > > Justification: breaks the whole system > > > > * What led up to the situation? > > > > Unknown. First noticed the problem on reboot a couple of days ago. > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > Using grub option to boot into recovery then pressing Ctrl-D causes the > machine > > to boot normally. > > > > * What was the outcome of this action? > > > > Ctrl-D from rescue mode results in a normal boot. > > > > * What outcome did you expect instead? > > > > Expected the system to boot without starting rescue mode first. > > > > Is the system completely locked up or can you e.g. access it via SSH? > What kind of hardware is this? If it's a laptop, can you attach an > external monitor to find out if it's a graphics issue / backlight issue. > > > Does the following help: > systemctl mask systemd-backlight@backlight:nv_backlight.service > systemd-backlight@backlight:acpi_video0.service > > (don't forget to run systemctl unmask for the above two services after > you've completed the tests). > > > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
