LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Duo Boot: Solid State Drive (Windows), Regular Drive (Linux) (https://www.linuxquestions.org/questions/slackware-14/duo-boot-solid-state-drive-windows-regular-drive-linux-4175650132/)

Zaxxon 03-13-2019 07:10 PM

Duo Boot: Solid State Drive (Windows), Regular Drive (Linux)
 
Hi,

I recently got a new computer that has: "931GB Seagate ST1000DM010-2EP102 (SATA)" and "476GB PCIe SSD (RAID (SSD))"
Using Slackware 14.2 DVD, I could install onto the Seagate (/dev/sdb), but lilo couldn't see the "PCIe SSD".

Using fdisk -l, I think the PCIe SSD was /dev/mvme-something, but even putting it in manually into lilo.conf, got some error message (which I didn't save) and Windows 10 won't be seen by lilo.

Any idea how to duo boot in this case?

Ztcoracat 03-13-2019 07:53 PM

Hi:

You might want to install the Grub bootloader.
That way Grub will allow you to boot into Linux and Windows.

http://gnu-linux-slackware.blogspot....gnu-grand.html

enorbet 03-13-2019 08:09 PM

It seems any bootloader can recognize and implement an NVME drive. It just takes some switches

See solutions here https://www.linuxquestions.org/quest...5586404-print/

phalange 03-14-2019 12:04 AM

Quote:

Originally Posted by Zaxxon (Post 5973603)
Any idea how to duo boot in this case?

There are some Grub slackdocs here:https://docs.slackware.com/slackbook...ith_partitions

And I have some supplements here:https://andrewpayne.gitlab.io/someth...06-grub2-luks/

I'm pretty sure that the GRUB2 version included with 14.2 does not support booting windows though. It will just give an error during the os probe process. You'll need a more recent GRUB.

Richard Cranium 03-15-2019 04:10 PM

Quote:

Originally Posted by phalange (Post 5973658)
I'm pretty sure that the GRUB2 version included with 14.2 does not support booting windows though. It will just give an error during the os probe process. You'll need a more recent GRUB.

Works for fine for me. (Windows 10 and BIOS)

Ztcoracat 03-15-2019 04:15 PM

Quote:

Originally Posted by Richard Cranium (Post 5974262)
Works for fine for me. (Windows 10 and BIOS)

Grub should be in the Slackware .iso, in other words on the DVD or live usb.

That's good that grub work for you.

Have you ever had any problems like after a new kernel?

Alien Bob 03-15-2019 04:21 PM

Slackware 14.2 can not handle NVMe drives properly, but Slackware-current can.

phalange 03-15-2019 05:40 PM

Quote:

Originally Posted by Richard Cranium (Post 5974262)
Works for fine for me. (Windows 10 and BIOS)

I'm guessing the difference must be UEFI vs bios. grub-mkconfig generates "Windows Boot Manager is not yet supported by grub-mkconfig" when I run it using Grub 2.00

Richard Cranium 03-15-2019 08:36 PM

Quote:

Originally Posted by phalange (Post 5974290)
I'm guessing the difference must be UEFI vs bios. grub-mkconfig generates "Windows Boot Manager is not yet supported by grub-mkconfig" when I run it using Grub 2.00

I've also got entire disks for each OS (well, only 1 for Windows); however, I thought that might be the case so I made sure to mention that my experience was with BIOS only. Thanks for the feedback!

chrisVV 03-16-2019 06:40 AM

Quote:

Originally Posted by phalange (Post 5974290)
I'm guessing the difference must be UEFI vs bios. grub-mkconfig generates "Windows Boot Manager is not yet supported by grub-mkconfig" when I run it using Grub 2.00

That's right, although you can boot windows in a UEFI system with grub-2.00 if you are prepared to write your own grub.cfg stanzas by hand. My notes indicate that at one time this seemed to work for me on a laptop I no longer have, I think with grub-1.99:

Code:

menuentry "Microsoft Windows" {
      insmod part_gpt
      insmod fat
      insmod search_fs_uuid
      insmod chain
      set root='(hd0,gpt2)'
      chainloader (hd0,gpt1)/EFI/Microsoft/Boot/bootmgfw.efi
}

This assumes that the EFI system partition is the gpt1 partition of the first disk and windows is on the gpt2 partition of that disk. (Note that in grub2,
disk numbering begins at 0 but partition numbering begins at 1)! I think I included the stanza above in /etc/grub.d/40_custom, I am not entirely sure.

Much easier though is to use grub-2.02, which can do the probing for you with /etc/grub.d/30_os-prober. Even easier than that though is to use rEFInd, which I thoroughly recommend.


All times are GMT -5. The time now is 03:19 AM.