Tag Info

New answers tagged

0

This is more of a windows question than an unix one, but heres how you can recover the windows bootloader: Boot into a Windows 7 install or recovery disk. You should be able to find a recovery iso online or on the Microsoft website. Once in, open up a command prompt and run the following: bootrec.exe /fixmbr This will reinstall the Windows bootloader, and ...


0

Simple things are often the best, but they lack the features from more complex tools that are sometimes useful. If you don't use those features, the extra documentation you have to wade through and things you can do wrong is a disadvantage. This applies to lilo vs. grub as well as to many other software (sed vs awk, C vs C++ (especially the newer versions ...


1

In looking through the manual it only seems to pertain to theming. This excerpt had a bit more on the subject. excerpt - http://www.gnu.org/software/grub/manual/grub.html#menuentry The boot menu where GRUB displays the menu entries from the “grub.cfg” file. It is a list of items, where each item has a title and an optional icon. The icon is selected ...


2

I found a case when I tried to use gummiboot instead of grub. Gummiboot reported error, that it cant find kernel images. It looks like I mounted /boot and configured fstab after I installed base system with pacstrap -i. So kernel images, that were placed in a /boot directory were lost after mounting and thus system could not boot. I wonder what happened with ...


-1

Please note, as Giles pointed out, this applies to the x86 architecture only. Background If you want to learn the proper order, you need to install a host system in QEMU before you install a kernel. While this approach seems counter intuitive to learning about the boot process, it is the only working way. Let me explain: A running system of any OS has ...


0

Did you export the esp variable for the grub-install command to use? If not, grub has no idea where the efi directory is located. # export esp=/boot/efi # grub-install --target=x86_64-efi --efi-directory=$esp ..... Archlinux supports EFISTUB, removing the need for a bootloader. See EFISTUB for more info. If you would like to try an EFI only bootloader, ...


0

Nevermind, i edited the boot line, removed the "quiet" keyword and found the nvidia drivers to be messing up the boot process. Installed 340xx and problem solved.


0

Sorry that this is posted as an 'answer'. I think it is probably more of a comment, but I just don't enough rep to post a comment... :( Anwyay, TurnKey Linux is currently based on Debian (v13.x is based on Debian Wheezy; previous v12.x based on Squeeze; prior to that it was Ubuntu based - v11.x based on Lucid). I have read that editing /etc/default/rcS and ...


0

Ok, the next few boots identified the problem. There were increasing problems reading the memory, and eventually the video never even turned on for the bios power-on self test. I opened up the case -- the graphics card and AGP slot have a scorch mark covering 2-3 connectors. The card is busted, probably ditto for the main board.


0

When the system transitions from one runlevel to another, it executes all the "K" scripts in the existing runlevel, in order, then all the "S" scripts in the new runlevel, in order. Debian implements parallel boot, so most of the scripts will run concurrently (but effectively in order), and there's a standard for including dependency information on each ...


1

Was an UEFI configuration problem, Hitachi SMP blades with more than 1TB of RAM need some tweeks. (Firmware dependant, so if you have such problem, ask Hitachi for the correct parameters).


0

That was because the downloading was not complete, Although Chrome showed that it is complete I re-downloaded from another browser and it work fine now.


0

First, I would not use MBR, because you have there 4 OS's and that will not go far. You need to have the /boot partition as primary and not extended. So you either throw out the Solaris installation, or the Linux one. Booting into FreeBSD (or PC-BSD... whatever, makes no difference) with GRUB2 is easy. You just define your "set root=..." and then you say ...


0

Boot in Shell mode from your LiveCD and active your partition as follow : gpart set -a active ada0


1

I'm most familiar with how Cobbler sets up TFTP so I'm not sure if this is relevant but I'll offer this info up anyway. Cobbler sets up a bootloader using pxelinux.0 as @Patrick explains in the comments as well as @msw. But it also sets up a corresponding pxelinux.cfg/ directory along side it that contains MAC addresses for each system that will be ...


3

The comment @Patrick made to your question was dead right: all the client machine needs to bootstrap PXE is to broadcast a DHCP request. The DHCP server (usually on the PXE boot server) will see the MAC address of the client device and will use it to give the client an IP address tell the client what files it should get from the PXE server at that point, ...


2

How about using a real tftp client? Those two which come to my mind: tftp atftp


0

Please download memstick image from here (or you can use amd64 of course). Attach the pendrive and write the img file with dd: dd if=your_img_file.img of=/dev/device_name_of_pendrive bs=512 The device_name_of_pendrive is the device name of pendrive, NOT partition! (e.g. /dev/sdc and not /dev/sdc1 or similar)


1

To find out how long it takes for the system to boot, systemd provides systemd-analyze. Without parameters, it will tell you the time to boot. Calling systemd-analyze critical-chain will print a tree of the chain of services that took the longest, while systemd-analyze blame will tell you how long each service took independently. Finally, systemd-analyze ...


3

Use systemd-analyze built-in tool. You are especially interested in two options: blame and plot systemd-analyze blame systemd-analyze plot > graph.svg blame: Print list of running units ordered by time to init plot: Output SVG graphic showing service initialization


0

CTRL + ALT + F2 Login, type service gdm stop or systemctl stop gdm Type startx Post the results in your question


0

This is was an embarrasing layer 8 problem. I was trying to install this iso debian-testing-ia64-DVD-1.iso which has compatibility problems with many motherboards AND is a live CD not a debian installer iso. I downloaded the debian net installer and that solved the issue.


0

This is a very interesting FOSS-support problem. UEFI BIOS enabled motherboards tend to be problematic. This really can't be as bad as the Power-VR graphics support issue I solved earlier this year, and I seriously doubt we will be requiring any kernel hacking, as this issue is with GRUB. I am aware that you are requiring dual-boot capabilities. Therefore, ...


1

You should build your own Debian image according to the instructions contained in this link: Debian UEFI-BIOS Compatibility I've done this before, following this exact guide. Let me know if you have any questions.


1

I'm not sure what this has to do with UEFI, as I've never heard of any Linux distro that won't still boot via BIOS. Just download an ISO image of the distro you wish to install, and use something like Rufus to "burn" it to a USB flash drive.


1

CONFIG_EFI_MIXED might be what you need.


3

After some chat, I'm posting an answer summing up a few interesting leads to follow while facing such problems. Booting safely on a USB image As you can see here, it seems like your system went into some trouble when trying to boot from the USB drive: ERROR: '/dev/disk/by-label/ARCH_201409' device did not show up after 30 seconds... Falling back to ...



Top 50 recent answers are included