similar to: installing C7 on a laptop with Win7, dual boot

------------ Original Message ------------ > Date: Sunday, March 01, 2015 20:06:26 -0500 > From: Fred Smith <fredex at fcshome.stoneham.ma.us> > To: centos at centos.org > Subject: [CentOS] installing C7 on a laptop with Win7, dual boot > > Hi all! > > I've just installed C7 on my netbook that already contained Win7 > (and also Fedora 19, which the C7 is

Hi all! I've just installed C7 on my netbook that already contained Win7 (and also Fedora 19, which the C7 is intended to replace). The Fedora installer had found the windows installation and it appeared in the grub menu, and was bootable and worked fine. The C7 installer did not put the windows installation into the grub menu. with some googling I found a page at

On Mon, Mar 02, 2015 at 03:33:59PM +0100, M?rio Barbosa wrote: > On 03/02/2015 02:06 AM, Fred Smith wrote: > > Hi all! > > > > I've just installed C7 on my netbook that already contained Win7 (and > > also Fedora 19, which the C7 is intended to replace). The Fedora installer > > had found the windows installation and it appeared in the grub menu, > > and

On 03/02/2015 02:06 AM, Fred Smith wrote: > Hi all! > > I've just installed C7 on my netbook that already contained Win7 (and > also Fedora 19, which the C7 is intended to replace). The Fedora installer > had found the windows installation and it appeared in the grub menu, > and was bootable and worked fine. > > The C7 installer did not put the windows installation

On Sun, Mar 01, 2015 at 09:26:59PM -0700, Chris Murphy wrote: > On Sun, Mar 1, 2015 at 6:06 PM, Fred Smith > <fredex at fcshome.stoneham.ma.us> wrote: > > Unfortunately, when I did it, I got this: > > > > Generating grub configuration file ... > > Found linux image: /boot/vmlinuz-3.10.0-123.el7.x86_64 > > Found initrd image:

> > Unfortunately, when I did it, I got this: > Generating grub configuration file ... > Found linux image: /boot/vmlinuz-3.10.0-123.el7.x86_64 > Found initrd image: /boot/initramfs-3.10.0-123.el7.x86_64.img > Found linux image: /boot/vmlinuz-3.10.0-123.20.1.el7.x86_64 > Found initrd image: /boot/initramfs-3.10.0-123.20.1.el7.x86_64.img > Found linux image:

I have a laptop with windows 10. I went into the Windows disk manager and shrunk the volume to make room for C7. That worked. I also changed the BIOS from secure boot to "both" (secure/legacy) I installed C7, went fine. About the time it was done I realized I never saw anything about "other" boot options (seems I saw that in the past). Anyway sure enough, got done and C7

I am trying to take a CentOS 7 img and get hyperv to boot. First step. qemu-img convert "CentOS7.img" -O vhdx -o subformat=dynamic "CentOS7.vhdx" after adding new hyper-v I get dracut-timeout... So doing some searching it says add hv_vmbus hv_netvsc hv_storvsc to INITRD_MODULES. which doesnt really exist any more in CentOS 7. I did find /etc/dracut.conf and add_drivers... I

Il 08/04/20 01:46, Jonathan Billings ha scritto: > On Apr 7, 2020, at 04:14, Alessandro Baggi <alessandro.baggi at gmail.com> wrote: >> thank you for your explanation. So in el8 grubby should be used to update kernel opts and grub2-mkconfig is used to generate an initial config. >> >> If I'm not wrong, grubby updates every single (sperated) entries on

On Sun, Mar 1, 2015 at 6:06 PM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > Unfortunately, when I did it, I got this: > > Generating grub configuration file ... > Found linux image: /boot/vmlinuz-3.10.0-123.el7.x86_64 > Found initrd image: /boot/initramfs-3.10.0-123.el7.x86_64.img > Found linux image: /boot/vmlinuz-3.10.0-123.20.1.el7.x86_64 > Found initrd

I installed CentOS 7 on a Shuttle X27D box (dual-core Atom 330), and so far it seems to work fine, but it didn't set up a Grub2 entry for the existing Windows XP installation in the first partition (MBR). Running os-prober generates no output. fdisk shows that the NTFS partition is still present as /dev/sda1, and still has the bootable flag set. I added a menuentry for Windows to the end of

On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with 'grub2-'. We have to detect the correct name of the tool to use it. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/convert_linux.ml | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index

On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with 'grub2-'. We have to detect the correct name of the tool to use it. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/linux_bootloaders.ml | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/v2v/linux_bootloaders.ml b/v2v/linux_bootloaders.ml index

On Debian family of OSes Grub2 tools are prefixed with 'grub-', not with 'grub2-'. We have to detect the correct name of the tool to use it. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/linux_bootloaders.ml | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/v2v/linux_bootloaders.ml b/v2v/linux_bootloaders.ml index

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

Am 14.03.23 um 12:30 schrieb Rob Kampen: > OK, > > found out the problem as to why it doesn't boot any kernel except 36.2 > > the system reports that it cannot find > > vmlinuz-3.10.0-1160.88.1.el7.x86_64 > > or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64 > > hence a manual selection from the grub menu when in front of the machine

Il 06/04/20 20:51, Jonathan Billings ha scritto: > On Mon, Apr 06, 2020 at 04:03:53PM +0200, Alessandro Baggi wrote: >> I'm on 8.1. I'm searching help to see if this is a bug or error by me but >> can't find nothing. >> Currently I used grubby but it does not write any file that I know like >> /boot/efi/EFI/centos/grub.cfg (I tried to remove and add arg but

Il 06/04/20 15:21, Simon Matter via CentOS ha scritto: >> Il 06/04/20 11:54, Georgios ha scritto: >>> Hi there! >>> I had a similar problem recently with grub. No idea why it doesnt work. >>> Try using grubby instead of grub2-mkconfig if you want the system to >>> keep your kernel parameters between boots. >>> >>> Something like:

Hi, I noticed that some, but not all, of my CentOS 7 machines have these kernel parameters for turning on systemd debug level logging added to the grub.cfg file. systemd.log_level=debug systemd.log_target=kmsg The parameters are *not* in the /etc/default/grub file, so if I rebuild grub.cfg with grub2-mkconfig, they disappear. I am a bit puzzled over how they got introduced. Has anyone else

Il 06/04/20 11:54, Georgios ha scritto: > Hi there! > I had a similar problem recently with grub. No idea why it doesnt work. > Try using grubby instead of grub2-mkconfig if you want the system to > keep your kernel parameters between boots. > > Something like: > > sudo grubby --args="i915.modeset=0 rd.driver.blacklist=i915" --update- > kernel=ALL > >