New answers tagged

0

I guess the post install commands I was having to issue where a bit of a clue. Following another "successful" install I checked the contents of /mnt/sysimage/var/log/anaconda/anaconda.log which indicated that no kernel was being installed. Sure enough I hadn't added the kernel package into the repo on my ISO - so I added in the kernel package (and grubby, ...


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 ...


0

I just had the same problem on my Debian / Ubuntu / Mint machine getting it to work with an Nvidia GTX-960M. I got it to work by getting rid of everything as you have done, and then by adding xorg-edgers ppa and then installing the nvidia-352 driver. sudo add-apt-repository ppa:xorg-edgers/ppa sudo apt-get update sudo apt-get install nvidia-352 I also had ...


0

(Install and) run tasksel, and select what you want.


0

Boot it (in virtualbox) and press esc to bring up the grub menu and from there edit the command-line. Once it's running edit the grub config and run update-grub.


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


0

Try configuring /dev/disk-by-id etc, to the /dev/sda or /dev/sdb according to the disk your system is installed, i know the first notation is better but sometimes it is broken here, i made a little distro for the company and having this problem in some random dimensions...


0

You must use the "dd" command, I've tried with Win32Imager and gotten far but mkfs has issues, install guide even says to use "dd". Easiest is to fresh install Arch, download BlackArch; sudo dd bs=512M if=blackarch-linux.iso of=/dev/sda ;


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 ...


0

Well, one thing you haven't mentioned is whether that disk is structured with GPT or the old MBR style. That would be very important. But beyond that there may be Secure Boot issues My ASUS (different model) was a pain to boot non-Microsoft stuff from USB or CD. Maybe this affects booting from hard disk too ( have not tried that yet) Basically I had to ...


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 ...


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 ...


0

"Solution" found..update to grub I prefer lilo,but strange doesn't work with this procedure.


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.


0

Problem solved. PXE cfg was wrong which should be. append ip=dhcp inst.repo={repo url} I also found such issue was largely pointing to incorrect/incomplete ks.cfg (for kickstart install case) from my web search.


0

Here is an authoritative answer from Marek Marczykowski-Górecki (Invisible Things Lab), who is one of the core developers of the Qubes OS. The source is the qubes-users forum, where I originally asked the question. This is main problem - you're trying to boot legacy system (Qubes here) from UEFI grub (Fedora). You need to choose one of them - either ...


0

I had to boot a LiveISO then edit the grub.conf, I wasn't exaclty sure it would work, but I just uncommented an already existing line that specified the boot drive. [root@localhost ~]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot ...


0

Have a look at the boot order through your raid controller bios. Seems like it tries to boot from the other LV (i.e. your 1TB array).


0

There are at least two ways to accomplish this: Take a look at http://ipxe.org/appnote/work_around_bios_halting_on_ipxe_exit#examples, one of these commands could work for you: chain ${server}/grub4dos.exe --config-file="find --set-root /BOOTMGR;chainloader /BOOTMGR" chain ${server}/grub4dos.exe --config-file="root (hd0,1);chainloader +1" I am currently ...


0

When the service NetworkManager-wait-online.service is enabled it will ensure that all configured network devices are up and have an IP address assigned before boot continues. This service will time out after 90s. Enabling this service might considerably delay your boot even if the timeout is not reached.


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 ...


0

I doubt this will help, but here's what I've done to dual-boot Qubes and Mint. This is a direct crib from Micah Lee's blog, so I take no credit for it. (https://micahflee.com/2014/04/dual-booting-qubes-and-ubuntu-with-encrypted-disks/) I booted from a Mint live DVD for the initial hdd partitioning. Create three partitions on the HDD: one for Qubes and ...


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.


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.


0

Solution for all Corsair mechanical keyboards with usbhid quirks. sudo nano /etc/default/grub or any other editor you like to use instead of nano. you will see this line GRUB_CMDLINE_LINUX_DEFAULT="" make sure to put the usbhid.quircks between the quotes and save that. In my case I had to change it to this line ...


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.


2

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


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.


0

Found that adding File 11_windows in /etc/grub.d was more helpful: Contents: #!/bin/sh cat << EOF menuentry "WINDOWS"{ set root='(hd0,msdos1)' chainloader +1 } EOF Then ran grub2-mkconfig after saving backup of grub.cfg in /boot/grub2. Results included added Entry "WINDOWS" in grub menu during start up. My case was for Windows10, but should be ...


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

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 ...


0

You should be able to create it with dd on a Mac. I have done this successfully with an Arch Linux ISO. Make sure the output destination is the USB device, not a partition on the device.


0

The system is probing for hardware, that is no longer installed in this setup. After a timeout the system starts all network related processes. Solution is to change probing for hardware.


0

I had the same symptom, after moving a F23 installation (ssd) to a different motherboard+chipset. The solution was to change the Secure Boot settings in BIOS. It was set to "Windows 7," and I set it to "Other OS." I guess the first motherboard had this setting by default. I became aware that this may be the issue when I tried to reinstall the Nvidia driver ...


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.


0

In dracut emergency shell: Dracut offers a shell for interactive debugging in the event dracut fails to locate your root filesystem. To enable the shell: Add the boot parameter ''rd.shell'' to your bootloader configuration file (e.g. /etc/grub.conf) rhgb = redhat graphical boot - This is a GUI mode booting screen with most of the information hidden ...



Top 50 recent answers are included