On Wednesday, June 28, 2017 at 2:11:51 PM UTC-4, yreb-qusw wrote: > On 06/26/2017 05:11 PM, cooloutac wrote: > > On Monday, June 26, 2017 at 2:21:02 PM UTC-4, yreb-qusw wrote: > >> On 06/25/2017 06:16 AM, yreb-qusw wrote: > >>> On 06/24/2017 11:52 PM, Alchemist wrote: > >>>> On Saturday, June 24, 2017 at 7:09:32 PM UTC-7, yreb-qusw wrote: > >>>>> Hello, so I have win10 on the 1st 2 partitions of my SSD, and install > >>>>> Qubes 3.2 onto the empty partition/s after the win10 installation. > >>>>> > >>>>> However, looking in my InsydeH20 BIOS, I am given no option to select a > >>>>> win10 vs. Qubes boot. Only "notebook HD", "USB" etc. > >>>>> > >>>>> Perhaps my mistake for thinking the laptop BIOS might function the way > >>>>> the ASrock BIOS, does, which does give me a choice. > >>>>> > >>>>> So, Now the "notebook" option just boots Qubes, Can I still boot > >>>>> Win10 on the other , 1st, partitions? > >>>>> > >>>>> if so, how ? > >>>>> > >>>>> thx > >>>> > >>>> What you want to do is install Windows first and then install Qubes, > >>>> you want to edit GRUB so you can boot Windows from GRUB. > >>>> > >>>> https://www.qubes-os.org/doc/multiboot/ > >>>> > >>> > >>> thanks, so if I got Qubes installed and up and running, does this mean > >>> my Bios is in "legacy mode" already? As I don't really see an option in > >>> the INSYDEH20 Bios to enable Legacy mode. > >>> > >>> re: > >>> -- > >>> > >>> > >>> Add this stanza to /etc/grub.d/40_custom, > >>> > >>> menuentry "Windows" { > >>> insmod part_msdos > >>> insmod ntldr > >>> insmod ntfs > >>> ntldr (hd1,X)/bootmgr > >>> } > >>> > >>> (Change X to reflect the relevant system partition.) > >>> -- > >>> > >>> What would be an example of what goes in "X" ? > >> > >> FURTHER, > >> > >> re: > >> -- > >> > >> > >> Identify the Windows system partition that has /bootmgr > >> > >> In blkid output, the system partition is the one with LABEL=’SYSTEM > >> RESERVED’ or LABEL=’SYSTEM’ and is only about 100 to 200 MB in size > >> -- > >> > >> I seem not such partition, what I do see is : > >> /dev/sda1: LABEL="DATA" UUID=" foo " TYPE="ntfs" PARTUUID="bdefoo-01" > >> > >> nothing with a LABEL='SYSTEM' not "SYSTEM" :) > > > > run fdisk from grub and try to identify it there. which will also be > > labeled in same format you need I believe. > > > > OK, so, I pressed 'e' during boot -grub and got to grub> when I > type fdisk I get 'error: can't find the command 'fdisk' > > however if I type ls I see > Device hd0: No known filesystem detected - Sector Size 512B -Total size > 244198584Kib THEN: > > 4 Partitions all labeled hd0, after hd0 they are hd0,msdos1 msdos2 > msdos 3 msdos5 > > the 'Data' one is msdos1 409600KiB that I guess is the same 'Data' > partition > > msdos2 has filesystem ntfs 185764864KiB > > msdos3 is filesystem ext* size 512000KiB > > msdos5 says no known filesystem > IIRC: Win10 has like a recovery partition ? > > > > Based on the above what would be my best chance-guess to try the grub > 'stanza' ? > > ntldr (hd0,msdos2)/bootmgr ? > > or > > ntldr (hd0,2)/bootmgr ? > > > Thanks in advance
look for the one is the size of that windows boot partition you mentioned earlier. Then when you make the 40_custom file in grub.d directory like was mentioned earlier. For whatever msdos1 msdos2 is when you list them. you put in 1 2 or 3 etc... as explained earlier. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1c41e56d-cbdc-432c-a627-76d74e147dfb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
