Tag Info

New answers tagged

0

I'd start with taking a look at the setup of your system, specifically the contents of the file, /etc/fstab. In there it will show you what partitions are being mounted and how they're being mounted. It's likely the case that with the addition of this new device that it's throwing the device handles off slightly, causing your system not to be able to access ...


0

I didn't find the cause of the slow booting with GRUB 2. I ended up using EXTLINUX instead, which is compact and fast, and better-suited if you don't need all the fancy GRUB 2 things. http://www.syslinux.org/wiki/index.php/EXTLINUX


2

I've just had to deal with this on a laptop running Debian Testing (Jessie/Sid). Possibly relevant: swap partition on an LVM volume (non-encrypted) at /dev/vg1/swap. To make the system resume after hibernation, I had to edit /etc/default/grub and change GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX="resume=/dev/mapper/vg1-swap" and then run ...


2

I would guess that this has much to do with the way bootloader and kernel are glued. Section 5.1.3 (Bootstrap Loader) in Hallinan's Embedded Linux Primer has the following to say on this : Some bootstrap loaders perform checksum veriļ¬cation of the kernel image, and most decompress and relocate the kernel image. The difference between a bootloader and a ...


1

I don't think there's a way of bypassing GRUB2 (or any other Linux bootloader) via EasyBCD. Most probably EasyBCD is not a universal bootloader and it works by chain loading into GRUB2. Your best bet is to try and make GRUB2 timeout on the Ubuntu entry immediately as Jonyburd's answer is suggesting. I believe you should look into why it failed.


2

Try changing the values that are in etc/default/grub to look like these: GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" Then run sudo update-grub.


0

Just in case anyone else ever has to the same thing I did here, I'll answer my own question. 1) Get the binary DVD iso image from redhat.com 2) Remove unnecessary rpms (GNOME, eclipse) so that it is less than 4GB (this allows it to be stored on a FAT32 filesystem) -copy this iso onto a USB 3) Remove the iso image that comes with the previous bootable USB ...


3

As the kernel documentation states, /dev/nfs is not a real device but only a hint to the kernel to use NFS as rootfs. You'll also have to tell the kernel where to find this root through the nfsroot parameter or a properly set up DHCP daemon. For the latter one to work you'll also have to either configure your kernel to auto-configure its network ...


1

You can make a partition bootable with out making an other changes. Also you may try re-installing grub on the hard disk, which should not hurt the partitions either.


4

Using unofficial install scripts and guides are typically a recipe for unhappiness under Arch Linux. As recommended by @jasonwryan, you should really just follow the Beginners' Guide on the ArchWiki. If you do not have access to another computer on which to keep the Wiki page open, you can actually install one of two packages which provide (fairly) ...


5

As @Leiaz very correctly pointed out in the comments, /sbin in Arch (and by extension, Manjaro) is now a symlink to /usr/bin. This means that unless /usr is mounted, /usr/sbin/init will not exist. You therefore need to make sure that /usr is mounted by the initial ramdisk. That's what the Arch wiki quote in your OP means: If you keep /usr as a separate ...


2

From Mint, you can change root to your Manjaro installation, in order to regenerate initramfs. Mount your Manjaro root under the directory of your choice ( ~/foo). Mount your /usr partition at ~/foo/usr, also mount boot if it is separate. Mount proc sys dev : # mount -t proc proc ~/foo/proc/ # mount --rbind /sys ~/foo/sys/ # mount --rbind /dev ~/foo/dev/ ...


0

You didn't say which distro of Linux you have installed, but I'll make a bad assumption here the since you have a flash drive with Ubuntu, you are running Ubuntu. Also, make sure you have a back up. You can still get to your files by mounting the drive. I explain how to mount below, or you can look at man pages. There is a program called boot repair. Open ...


1

This kind of functionality is far too advanced for GRUB. GRUB can't even talk over the network except for TFTP. The SSH server that you saw runs under Linux. It is started early during the boot process, after the kernel has booted but before mounting the root filesystem. Linux runs programs from the initramfs (or initrd on older systems) before mounting the ...


1

You start with the function do_bootm_linux in bootm.c and work your way to the code. You could also try adding the parameter debug or loglevel=7 when starting the kernel to get more information.


-1

You could try disabling evdev in X11, or try to login via ssh and look in X11's logs for suspicious things.


2

Adding fake entries or some hidden keystrokes are NOT secure. If you don't want someone to boot Windows on your computer, then adding protection only for newbies is not sufficient. I can't imagine a case where you don't want to protect from experienced people, but only from newbies. As a solution, I would password protect the bootloader (you use GRUB2, ...


0

Try alias parport_lowlevel parport_pc and adding parport_pc, lp and parport modules to /etc/modules echo "parport_pc" >> /etc/modules echo "parport" >> /etc/modules echo "lp" >> /etc/modules


0

Apologize in advance, this isn't super helpful, but I think I can confirm that your issue may be the processor. I was recently trying to install CentOS on a laptop and encountered an incompatibility issue with Haswell, so it was sort of the inverse of your issue. Try yet another computer, with the same type of processor as your initial computer on which the ...


0

The problem seems to be that the guided / automatic hard drive partitioning uses a GPT partitioning scheme. After a clean FreeBSD 10.0 AMD64 installation using default values everywhere (except obviously for root password, etc.), my machine wouldn't boot either. I re-did the installation, this time partitioning the hard drive manually using an MBR partition ...


1

Your monitor provides information about itself using a digital standard called EDID. The kernel reads this information when detecting a display device and automatically configures its display to match as near as it can the display device's native resolution. LCD devices can, in truth, support only one resolution - their native resolution - and emulate all ...


0

It sounds like you have something funky going on with you USB bus and keyboard. Here are some steps to find the culprit. You may find more than one of these addresses the problem. Try a different keyboard. If this system has a PS/2 port, try a non-USB keyboard. Make sure you aren't using a USB3 port for your keyboard. Plug the keyboard directly into the ...


1

"enabling additional executable binary formats" is a message that originates from binfmt-support. As seen above, reinstalling said service is the way to go.



Top 50 recent answers are included