Hot answers tagged

4

This worked for me. Add the following to your kernel parameter. selinux=1 enforcing=0 This sets the SELinux enforcement mode from strict to permissive. This is a temporary solution until I figure out what is going on, or until an update fixes the problem. Hope it helps.


2

You can use the other command line options of systemd-analyze to get a better overview about what delays your boot. Your command showed that most of the time is eaten up by userspace processes. Therefore I recommend investigating this further. Take a look at systemd-analyze blame and systemd-analyze plot The first one will give you a per process list ...


2

The root filesystem is passed to the kernel upon boot using the root argument. So you should be able to: cat /proc/cmdline and then look for root=/some/path, or perhaps root=UUID=longstring. For instance, I get: BOOT_IMAGE=/boot/kernel-genkernel-x86_64-4.4.0-sabayon root=UUID=18f3b5a1-3994-43ef-ad6d-cb4c86ff5f95 ro quiet splash If it's a path, it ...


2

Yes, it'll remain on the login screen indefinitely unless it's set otherwise (I've never seen anything else happen). If you have the sshd configured to start at boot, which I think is almost always the case by default, you shouldn't have to manually start it.


2

efivar version 0.23 needs a patch to work with kernel headers from 4.4 (and later kernels), because the header defining NVME_IOCTL_ID changed (it was renamed from nvme.h to nvme_ioctl.h). To build efivar on your system, you'll need the "Workaround rename of linux/nvme.h" patch. To apply that, go into the directory containing the efivar source code (with the ...


1

Suppose you want Mint on /dev/sda, and Ubuntu on /dev/sdb. Only one OS needs the grub installer, preferably Mint on the boot disk. After you install Ubuntu, rerun sudo update-grub on Mint, and grub will detect and make menu entries for both OSes. But even if you installed Mint, then Ubuntu, and used the grub installer on both, it should still work OK.


1

im not sure about grub legacy but in grub 2 which im using ive added 'insmod progress' to grub. that give me indication and progress.


1

UUIDs solved my problem, which was the same as your problem. The following excerpt from the Arch Wiki is very helpful: If your machine has more than one SATA, SCSI or IDE disk controller, the order in which their corresponding device nodes are added is arbitrary. This may result in device names like /dev/sda and /dev/sdb switching around on each boot, ...


1

I also have an N2600 with similar symptoms. But for my, anything after 3.16 would see this problem, but 3.16 and below was fine. I've found that acpi=off gets stuff working again. Clearly there is some kind of issues with timers or CPU sleep states that needs to be addressed.


1

If you wish to use screen, use something like: screen -dmS yourscreenname sudo python /path/to/file.py from rc.local to run your program on detached screen. Next, after boot you can attach to it by screen -r yourscreenname from root account. Alternativly - if you only wish to have logs from your program - maybe simpler is redirect output to syslog? ...


1

Some notes, mainly on BIOS/GRUB systems. BIOS system with GRUB: BIOS start of from address 0xfffffff0 (x86). Do various tests e.g. POST. If all well then check the devices, in the order configured and saved in CMOS. First boot device that has a valid MBR, (signature at offset 510 is 0x55aa), is loaded into memory at address 0x7c00. Then BIOS leaves ...


1

The solution I used was Change default.target to multi-user.target (Was graphical.) setenforce 0 systemctl isolate graphical


1

For the sake of completeness, i will add that this is a problem with selinux-policy and selinux-policy-targeted version 3.13.1-183.fc24. Downgrading these to previous versions or using 3.13.1-184.fc24 fixes this issue. Also see bugzilla entries here and here.



Only top voted, non community-wiki answers of a minimum length are eligible