Hot answers tagged

5

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.


4

Thank you for flying xorriso. The problem is in the image file which you let xorriso mark as EFI System Partition. It is supposed to be a FAT filesystem image which contains a binary file named /EFI/BOOT/BOOTX64.EFI (or .../BOOTIA32.EFI for 32 bit x86) plus possibly other files. Mount the file /boot/grub/efi.img from the Ubuntu ISO for learning about its ...


3

Thanks to Don Crissti's insights and via process of elimination, it is concluded that the culprit is the initramfs image. Somehow dracut when it builds the image decides to include a cached version of the hostname (!?!). Rebuilding the initrd/initram fs is covered here but in short (since you, dear reader might not have access), do dracut -f -v


2

If your laptop (I assume that's what you want to boot ubuntu on, but your question is actually not clear on that) supports PXE booting, you can set up PXE, DHCP and TFTP on either the server or the Pi and NFS on the Pi. But it's a lot of work. PXEInstallServer looks like it might a good starting point.


2

This is caused by a bug in the SELinux policy. See https://bugzilla.redhat.com/show_bug.cgi?id=1331668 — as of May 2, 2016, there is an update in testing which should resolve the issue. In the meantime, booting with enforcing=0 will work around the problem.


2

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


1

It sounds more like System Rescue CD uses GRUB, not syslinux. My grub64.efi is about 1MB, but I imagine you can build it with fewer modules included. The image you copied is called syslinux.efi, so I would not call it isolinux. I expect it looks for a file called syslinux.cfg, not isolinux.cfg. (isolinux will fall back to syslinux.cfg though). I also ...


1

Any code that runs before the main operating system is started, and that's involved in starting other programs, is a bootloader. Most computers, even most embedded devices have a chain of bootloaders: code in ROM or flash memory that loads another piece of code from flash memory or a disk drive, that loads another piece of code and so on. The BIOS is a ...


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.


1

make install simply copies the kernel image to the /boot directory. make modules_install copies the modules to /lib/modules/kernel-version/. Most linux distributions these days boot using grub, so you need to run update-grub to notice the new kernel image in /boot, and add an entry to boot it to the grub configuration file so you get the option to boot ...


1

Start another Linux VM, and mount that disk to repair the problem. In addition, to avoid the password entered in single user mode, change as follows /lib/systemd/system/rescue.service. --- /lib/systemd/system/rescue.service.orig 2015-11-20 13:49:03.000000000 +0900 +++ /lib/systemd/system/rescue.service 2016-04-11 15:58:31.002000000 +0900 @@ -18,11 ...


1

I had to copy the modules from Qubes and regenerate the initramfs using the sudo dracut -f command.


1

You need to mount your root into which you will switch. I assume you already know how to do that. Basically it's just mkdir /newroot; mount -r /dev/something /newroot Then you need to replace your currently running fallback shell. It's running with PID 1 (you can verify that with echo $$), and target init needs to get this number again. So you need an exec ...


1

I also have an N2600 with similar symptoms. But for me, 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

The origin of the error code can be found in the source code for the hub in question. e.g. grep -A 1 -m 1 22 /usr/src/linux-source-4.3/drivers/usb/host/xhci.h #define PORT_PLC (1 << 22) /* port configure error change - port failed to configure its link partner */ You'll find the meaning of some error codes in ...


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.



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