On Wed, Jan 20, 2016 at 8:31 AM, Armelius Cameron
wrote:
> Hello,
>
> Well, I finally figured out the cause, thanks to Richard's first
> suggestion in looking at journalctl output.
Good deal. I'm glad you got it figured out! Learning stuff the hard way can
be rewarding but very frustrating.
Th
Hello,
Well, I finally figured out the cause, thanks to Richard's first
suggestion in looking at journalctl output.
I was playing around with udev rules to try to automatically mount an
external drive (it didn't really work yet). Apparently having this
extra rule in /etc/udev/rules.d causes the s
On 01/20/16 02:48, Armelius Cameron wrote:
> Sorry for my lag in response, in between work meetings with
> non-working laptop has made this an onerous day!
>
> So I've tried the following kernel options, all to no-avail:
> "systemd.unit=multi-user.target", still reboot after a few seconds, so
> d
Sorry for my lag in response, in between work meetings with
non-working laptop has made this an onerous day!
So I've tried the following kernel options, all to no-avail:
"systemd.unit=multi-user.target", still reboot after a few seconds, so
does this option remove video driver issue (radeon) ?
"ac
Maybe a drivers issue? Looking through the logs as Richard said would be
useful ye.
Cheers,
Sylvia
On Tuesday, 19 January 2016, Richard Shaw wrote:
> On Tue, Jan 19, 2016 at 9:17 AM, Armelius Cameron > wrote:
>
>> Hello,
>> If I boot with "Rescue kernel" though, it stopped the infinite loopi
On Tue, Jan 19, 2016 at 9:17 AM, Armelius Cameron
wrote:
> Hello,
> If I boot with "Rescue kernel" though, it stopped the infinite looping
> reboot. So I can get into the system with Rescue, but then I am not
> sure what to do from there.
>
> I wondered if one of the services or one of the kernel
Hello,
Yes, I tried all version of kernels I still have, and still getting
the same thing.
If I boot with "Rescue kernel" though, it stopped the infinite looping
reboot. So I can get into the system with Rescue, but then I am not
sure what to do from there.
I wondered if one of the services or on
You could try booting into multi-user.target instead of graphical.target
and see if that helps since it doesn't appear to be releated to which
kernel you boot.
Add "systemd.unit=multi-user.target" to your kernel options or perhaps the
traditional "3" on the end still works?
Thanks,
Richard
--
us
Hi!
Did you try to boot with previous kernel? I find very likely there
lies your problem.
Just pick another kernel from the list in GRUB and see what
happens.
Also, you can try booting a live pendrive/DVD to see if there's any
hardware issue.
Cheers,
Sylvia
--
users mailing list
users@lis
