[opensuse-factory] Unable to install Leap 42.2 on a Window 10 system
Hello I am trying to add Leap 42.2 to a fresh Windows 10 installation. The Windows installation was performed with the legacy option activated in the BIOS. The laptop has a brand new Seagate ST1000LM014* hard drive. [*] 1 TB SSHD HDD Laptop Upgrade Hybrid 2.5" 9.5mm 5400 RPM 64 Mo NAND Flash MLC 8 GiB Before installing Windows 10 I set the hard drive partition table to GPT using parted on systemrescuecd-x86-4.8.1 . After installing Windows 10, I booted systemrescuecd again to find out what kind and how many partiions the Windows 10 installation had created - there were 2. The install was a legacy installatiion with no efi. The hard drive partitons show up GPT under Windows disk manager but the overall hard drive partition scheme according to parted on systemrescuecd had been set to MSDOS by the Windows 10 installation. I resized /dev/sda2 partition (which was all of the remaining HD (931.51 GiB - 500 MiB) to 128 GiB using the parted tool, and left the rest of the hard drive (931.51 GiB - 500 MiB - 128 Gib) unformated and empty. To resume, the HD now had 2 partitions: /dev/sda1 500 MiB : Windows Recovery partition (I believe) - formated NTFS and confirmed to be GPT /dev/sda2 128 GiB : Windows system partition - formated NTFS and confirmed to be GPT Next , I tried installing Leap 42.2 which I had burnt to an usb key using Suse Studio ImageWriter Note : The usb key is 8 GiB but it appears as 4 GiB once the Leap DVD image has been added. When I got to the "Suggested Partitioning" page, the suggestion was to install Leap on the usb key (that I was using for the installation). The message was: Delete Partiton /dev/sdb1 (369 MiB) Delete Windows partion /dev/sdb2 (4.00 GiB) Set disk label of /dev/sdb tp GPT Here's a screenshot: http://j.pearson.pagesperso-orange.fr/Suggestion_partitionning_20161001_1522... Next I opened the Expert mode and I tried to manually add a /dev/sda3 partion for Leap. When I selected /dev/sda and right clicked and selected "Add Partiton", the following message occured YaST2 Error Operation not permeted on disk /dev/sda The partitioning on your disk /dev/sda is either not readable or not supported by the partitionning tool parted used to change the partition table. Here's a screenshot: http://pagesperso-orange.fr/j.pearson/Operation_not permitted_20161001_152212.jpg I also tried to delete the two existing Windows partitions (/dev/sda1and /dev/sda2) individually. I could not. I redid anything again. That is, I blanked the HD and reset the hard drive partition table to GPT using parted on systemrescuecd-x86-4.8.1. I reinstalled Windowd 10 and resized /dev/sda2 My second attempt to install Leap 42.2 produced the same results. I did an "Ctrl+Alt+Fx" and opened a tty window and ran the command "parted -I". The following message appeared ; Warning : /dev/sda contains GPT signatures, indicating that it has a GPT table. However, it does not haave a valid fake msdos partition table, as it should. Perhaps, it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table ? All comments and help appreciated TIA James P.S Comment for the list montors - this is V2* of an email that I sent earlier today using the wrong email address - sorry. Please ignore my first email [*] Subject: Awaiting release to opensuse-factory@opensuse.org: Problems to install a dual boot Windows 10 & Leap 42.2 system -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-01 23:30, James PEARSON wrote: ... ...
Error Operation not permeted on disk /dev/sda The partitioning on your disk /dev/sda is either not readable or not supported by the partitionning tool parted used to change the partition table.
I'm not surprised. You have a frankestein of a disk. GPT disk with classic partitions on a computer with UEFI set to legacy mode. Ufff. IMHO, you have to repartition and reformat the disk to pure gpt and instal in native uefi mode both windows and linux. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Hello
Sun, 2 Oct 2016 00:24:07 +0200, Carlos E. R. wrote:
Error Operation not permeted on disk /dev/sda The partitioning on your disk /dev/sda is either not readable or not supported by the partitionning tool parted used to change the partition table.
I'm not surprised. You have a frankestein of a disk. GPT disk with classic partitions on a computer with UEFI set to legacy mode. IMHO, you have to repartition and reformat the disk to pure gpt and instal in native uefi mode both windows and linux.
Thank you for your comments . I would like to mention that I am still trying unsucessfully to get a normal dual boot Windows 10 UEFI / 42.2 UEFI system. Below is what I have tried / managed to do since my last email. I burnt Windows 10 to to another usb key and paid more attention to partition type of the destination partition on the usb key this time. Next, I blanked the computer's HD (again - as recommended) and reset the hard drive partition table to GPT using parted on systemrescuecd-x86-4.8.1 and then I reinstalled Windowd 10 as a proper UEFI system using the new usb key drive. IMHO I now have a proper UEFI installation of Windows 10 (see below for more info). I tested that Windows 10 booted OK - it did. Then I installed 42.2. When the machine rebooted - it booted Windows 10. I installed 42.2 again. Same problem - when the machine rebooted - it booted Windows 10. With regards to installing 42.2 version UEFI on a Windows 10 UEFI system, my findings to date are: - During the 42.2 installation, one can not use the expert partitionner mode and add a new EXT4 partition - One can however modify the proposed partition settings and set a filesystem to EXT4 - After installing 42.2 on a UEFI installation of Windows 10, the PC will reboot to Windows 10 - there is no option to boot to 42.2 Note: The machine in question is an HP Pavillion 15 I would like to add that after searching that I noticed that 42.2 was installed and that I could boot it if I hit the F8/F9 keys to raise the boot manager in the BIOS. The Boot Option Menu will present the following choices: OS boot Manager (UEFI) - Windows Boot Manager OS boot Manager (UEFI) - opensuse-secureboot Boot for EFI file If you choose "OS boot Manager (UEFI) - opensuse-secureboot" the machine will boot 42.2 and all is normal. As a second note, I would like to add that the wifi works on Windows 10 on a HP Pavillion 15 but it was not picked up by 42.2 (see below for more info) lspci sayes 08:00 Network controller: Broadcom Corportion BCM43142 802.11b/g/n (rev 01) More info follows.. linux-ytik:~ # parted -l /dev/sda Model: ATA ST1000LM014-1EJ1 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 473MB 472MB ntfs Basic data partition hidden, diag 2 473MB 578MB 105MB fat32 EFI system partition boot 3 578MB 595MB 16.8MB Microsoft reserved partition msftres 4 595MB 349GB 348GB ntfs Basic data partition 5 349GB 353GB 4299MB linux-swap(v1) primary 6 353GB 1000GB 647GB ext4 primary linux-ytik:~ # fdisk -l Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: CA3409E3-70F7-4C81-851D-8B689234742C Device Start End Sectors Size Type /dev/sda1 2048 923647 921600 450M Windows recovery environment /dev/sda2 923648 1128447 204800 100M EFI System /dev/sda3 1128448 1161215 32768 16M Microsoft reserved /dev/sda4 1161216 681706745 680545530 324.5G Microsoft basic data /dev/sda5 681707520 690104319 8396800 4G Microsoft basic data /dev/sda6 690104320 1953523711 1263419392 602.5G Microsoft basic data linux-ytik:~ # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 08:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 08) 0a:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2) linux-ytik:~ # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 1.9G 4.0K 1.9G 1% /dev tmpfs 1.9G 92K 1.9G 1% /dev/shm tmpfs 1.9G 2.3M 1.9G 1% /run tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda6 593G 5.3G 587G 1% / /dev/sda2 96M 29M 68M 30% /boot/efi tmpfs 389M 8.0K 389M 1% /run/user/1000 All remarks and comments weclome Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thank you for your comments . I would like to mention that I am still trying unsucessfully to get a normal dual boot Windows 10 UEFI / 42.2 UEFI system. Below is what I have tried / managed to do since my last email.
I burnt Windows 10 to to another usb key and paid more attention to partition type of the destination partition on the usb key this time.
Next, I blanked the computer's HD (again - as recommended) and reset the hard drive partition table to GPT using parted on systemrescuecd-x86-4.8.1 and then I reinstalled Windowd 10 as a proper UEFI system using the new usb key drive. IMHO I now have a proper UEFI installation of Windows 10 (see below for more info). I tested that Windows 10 booted OK - it did.
Then I installed 42.2. When the machine rebooted - it booted Windows 10. I installed 42.2 again. Same problem - when the machine rebooted - it booted Windows 10. <snip> Hi Boot into openSUSE and switch to root user and use efibootmgr -v to see
On Sun 02 Oct 2016 11:22:19 PM CDT, James PEARSON wrote: <snip> the boot order, then use efibootmgr -o nnnn nnnn (where nnnn is the numbers in the -v output) and see how that goes, it maybe your BIOS resets and default to the Windows Boot Manager label. In cases like that I've just used efibootmgr to wipe the nvram entries and manually add back in. Oh, also check in YaST Boot Loader BootLoader Options tab that Probe Foreign OS is checked. -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.31-30-default up 7 days 23:29, 2 users, load average: 0.27, 0.25, 0.29 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello
Sun, 2 Oct 2016, Malcolm wrote : Boot into openSUSE and switch to root user and use efibootmgr -v to see the boot order, then use efibootmgr -o nnnn nnnn (where nnnn is the numbers in the -v output) and see how that goes,
I would like to thank you for your super quick come back Malcolm. I followed your advice - for more info see below. linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,3001,0002,2001,2002,2003 Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC # I want the first choice to be Windows 10 (sorry but this is not my PC) and the second choice to be 42.2 linux-ytik:~ # efibootmgr -o 0001 0002 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001 Boot0001* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk linux-ytik:~ # reboot I booted Windows 10 :( I shutdown the machine down and restarted it - the machine still boots into Windows 10. There are no other options Bottom line : The only way I can boot 42.2 is if I hit the F8/F9 keys (quick enough when I start the machine) to raise the boot manager in the BIOS. Question ; I imagine that the line "Boot2001* USB Drive (UEFI) RC" refers to one of the 2 usb flash drives that I used to install Windows 10 and 42.2? All comments and suggestions welcome. Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
03.10.2016 20:16, James PEARSON пишет:
Hello
Sun, 2 Oct 2016, Malcolm wrote : Boot into openSUSE and switch to root user and use efibootmgr -v to see the boot order, then use efibootmgr -o nnnn nnnn (where nnnn is the numbers in the -v output) and see how that goes,
I would like to thank you for your super quick come back Malcolm. I followed your advice - for more info see below.
linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,3001,0002,2001,2002,2003 Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC
# I want the first choice to be Windows 10 (sorry but this is not my PC) and the second choice to be 42.2 linux-ytik:~ # efibootmgr -o 0001 0002
List should be one word, separate by comma, not spaces.
BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001
It took only the first boot entry. Boot openSUSE once more and redo command with correct parameter (-o 0001,0002).
Boot0001* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk
linux-ytik:~ # reboot
I booted Windows 10 :(
I shutdown the machine down and restarted it - the machine still boots into Windows 10. There are no other options
Bottom line : The only way I can boot 42.2 is if I hit the F8/F9 keys (quick enough when I start the machine) to raise the boot manager in the BIOS.
Question ; I imagine that the line "Boot2001* USB Drive (UEFI) RC" refers to one of the 2 usb flash drives that I used to install Windows 10 and 42.2?
All comments and suggestions welcome.
Regards James
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello
Mon, 3 Oct 2016 Andrei Borzenkov wrote : List should be one word, separated by comma, not spaces. It took only the first boot entry. Boot openSUSE once more and redo the command with correct parameters (-o 0001,0002).
Thank very much for you come back. In addtion, you are 100% correct. When I hit the F8/F9 keys (if I am quick enough when I start the machine) to raise the boot manager in the BIOS, the Boot Option Menu now presents the following choices: OS boot Manager (UEFI) - Windows Boot Manager Boot for EFI file For info, before I had: OS boot Manager (UEFI) - Windows Boot Manager OS boot Manager (UEFI) - opensuse-secureboot Boot for EFI file I will try to delete the 42.2 partitions on this machine and reinstall 42.2 after work tomorrow. After that I will follow your advice. Thanks again Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
03.10.2016 20:49, James PEARSON пишет:
Hello
Mon, 3 Oct 2016 Andrei Borzenkov wrote : List should be one word, separated by comma, not spaces. It took only the first boot entry. Boot openSUSE once more and redo the command with correct parameters (-o 0001,0002).
Thank very much for you come back. In addtion, you are 100% correct. When I hit the F8/F9 keys (if I am quick enough when I start the machine) to raise the boot manager in the BIOS, the Boot Option Menu now presents the following choices: OS boot Manager (UEFI) - Windows Boot Manager Boot for EFI file
For info, before I had: OS boot Manager (UEFI) - Windows Boot Manager OS boot Manager (UEFI) - opensuse-secureboot Boot for EFI file
I will try to delete the 42.2 partitions on this machine and reinstall 42.2
Why? Select "Boot EFI file", chose \EFI\opensuse\shim.efi to boot openSUSE. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello
Why? Select "Boot EFI file", chose \EFI\opensuse\shim.efi to boot openSUSE.
Thank you. I managed to boot 42.2 again. For info, the key word to look for when scrolling through the BIOS under "Boot for EFI file", (IMO) is "shim". Once I managed to make the correct choice and boot 42.2 again, I did the following. ############################## # FIRST TRY - selecting 42.2 and Win10 ############################## linux-ytik:~ # efibootmgr -v BootCurrent: 003D Timeout: 0 seconds BootOrder: 2002,0001,3001,2001,2003 Boot0000* Internal CD/DVD ROM Drive (UEFI) ACPI(a0341d0,0)PCI(1f,2)03120a00010000000000CD-ROM(1,58,b40)RC Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC # linux-ytik:~ # efibootmgr -o 0002,0001 BootCurrent: 003D Timeout: 0 seconds BootOrder: 0002,0001 Boot0000* Internal CD/DVD ROM Drive (UEFI) Boot0001* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # reboot What happened next... 42.2 tried to boot ) => KO I finally hit the start button and then I reboot again Windows 10 is still the default boot If I hit the F8/F9 keys (if I am quick enough when I start the machine) to raise the boot manager in the BIOS, I can boot 42.2 and things works as per usual. ############################## # SECOND TRY - selecting 42.2 only ############################## linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,3001,0002,2001,2002,2003 Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC linux-ytik:~ # efibootmgr -o 0002 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0002 Boot0001* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # reboot What happened next... Windows 10 booted. Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon 03 Oct 2016 10:11:21 PM CDT, James PEARSON wrote: <snip>
linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,3001,0002,2001,2002,2003 Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC linux-ytik:~ # efibootmgr -o 0002 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0002 Boot0001* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # reboot
What happened next... Windows 10 booted.
Regards James Hi What I suggest is to boot into openSUSE, delete the existing windows and openSUSE entries and re-add with efibootmgr so openSUSE is first;
efibootmgr -b 1 -B 1 efibootmgr -b 0 - B 0 efibootmgr -c -L "opensuse-secureboot" -l "\\EFI\\opensuse\\shim.efi" efibootmgr -c -L "Windows Boot Manager" -l "\\EFI\\Microsoft\\Boot\\bootmgfw.efi" -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.31-30-default up 9 days 3:50, 2 users, load average: 0.41, 0.61, 0.39 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/10/2016 03:51, Malcolm wrote:
On Mon 03 Oct 2016 10:11:21 PM CDT, James PEARSON wrote:
<snip>
linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,3001,0002,2001,2002,2003 Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC linux-ytik:~ # efibootmgr -o 0002 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0002 Boot0001* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # reboot
What happened next... Windows 10 booted.
Regards James Hi What I suggest is to boot into openSUSE, delete the existing windows and openSUSE entries and re-add with efibootmgr so openSUSE is first;
efibootmgr -b 1 -B 1 efibootmgr -b 0 - B 0 efibootmgr -c -L "opensuse-secureboot" -l "\\EFI\\opensuse\\shim.efi" efibootmgr -c -L "Windows Boot Manager" -l "\\EFI\\Microsoft\\Boot\\bootmgfw.efi"
Doesn't yast2 bootloader work with efi or gpt? Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue 04 Oct 2016 06:22:24 AM CDT, Dave Plater wrote:
Doesn't yast2 bootloader work with efi or gpt?
Hi Sure, based on os-prober, but only to add the entry, not manipulate the nvram. -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.31-30-default up 9 days 14:59, 2 users, load average: 0.00, 0.06, 0.15 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue 04 Oct 2016 06:22:24 AM CDT, Dave Plater wrote:
Doesn't yast2 bootloader work with efi or gpt? Hi Sure, based on os-prober, but only to add the entry, not manipulate the nvram. I meant that if efi is turned on in the bios, does "yast2 partitioner" fail to allow dual boots, windows 10/openSUSE:42.2" I can remember seeing a similar problem on this list with 42.1. In fact I had to reboot once, after opening ( and not doing anything) in yast2 bootloader, with 42.1 for a Vista partition to show up in the boot
On 04/10/2016 14:58, Malcolm wrote: menu. Maybe this feature is interfering with your setup? Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue 04 Oct 2016 10:16:28 PM CDT, Dave Plater wrote:
On 04/10/2016 14:58, Malcolm wrote:
On Tue 04 Oct 2016 06:22:24 AM CDT, Dave Plater wrote:
Doesn't yast2 bootloader work with efi or gpt? Hi Sure, based on os-prober, but only to add the entry, not manipulate the nvram. I meant that if efi is turned on in the bios, does "yast2 partitioner" fail to allow dual boots, windows 10/openSUSE:42.2" I can remember seeing a similar problem on this list with 42.1. In fact I had to reboot once, after opening ( and not doing anything) in yast2 bootloader, with 42.1 for a Vista partition to show up in the boot menu. Maybe this feature is interfering with your setup? Regards Dave P
Hi No it works and adds the right entries (well I've had no issues) I have a dual boot efi HP ProBook 455 with Win10 and openSUSE 42.2 Beta. I also have a multiboot/multi SSD's (DELL 5555) machine, openSUSE 42.2 Beta, SLED 12 SP2 RC on one disk/ESP and Win10, Tumbleweed on a second disk/ESP since tumbleweed and Leap use the word opensuse in the directory... The only thing in SLE and Leap is os-prober is older so it shows Tumbleweed as an unknown... I set the default to use Tumbleweed in the efi boot order..... -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.31-30-default up 9 days 22:26, 2 users, load average: 0.11, 0.06, 0.08 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello
Mon, 3 Oct 2016, Malcolm wrote : What I suggest is to boot into openSUSE, delete the existing windows and openSUSE entries and re-add with efibootmgr so openSUSE is first;
efibootmgr -b 1 -B 1 efibootmgr -b 0 - B 0 efibootmgr -c -L "opensuse-secureboot" -l "\\EFI\\opensuse\\shim.efi" efibootmgr -c -L "Windows Boot Manager" -l "\\EFI\\Microsoft\\Boot\\bootmgfw.efi"
linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC # linux-ytik:~ # efibootmgr -b 1 -B 1 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # efibootmgr -b 0 - B 0 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC # linux-ytik:~ # efibootmgr -c -L "opensuse-secureboot" -l "\\EFI\\opensuse\\shim.efi" ** Warning ** : Boot0002 has same label opensuse-secureboot BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk Boot0001* opensuse-secureboot # linux-ytik:~ # efibootmgr -c -L "Windows Boot Manager" -l "\\EFI\\Microsoft\\Boot\\bootmgfw.efi" ** Warning ** : Boot0000 has same label Windows Boot Manager BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0003,0001,0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0001* opensuse-secureboot Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk Boot0003* Windows Boot Manager # linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0003,0001,0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0001* opensuse-secureboot HD(1,800,e1000,48870217-1384-4b8b-9287-0e6402622261)File(\EFI\opensuse\shim.efi) Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot0003* Windows Boot Manager HD(1,800,e1000,48870217-1384-4b8b-9287-0e6402622261)File(\EFI\Microsoft\Boot\bootmgfw.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC linux-ytik:~ # reboot What happened next... Windows 10 boots Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Oct 4, 2016 at 8:27 AM, James PEARSON
linux-ytik:~ # efibootmgr -b 0 - B 0 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager
So your firmware does not allow you to delete Windows entry (or may be it adds it back after it deletes it). ...
linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0003,0001,0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0001* opensuse-secureboot HD(1,800,e1000,48870217-1384-4b8b-9287-0e6402622261)File(\EFI\opensuse\shim.efi) Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot0003* Windows Boot Manager HD(1,800,e1000,48870217-1384-4b8b-9287-0e6402622261)File(\EFI\Microsoft\Boot\bootmgfw.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC linux-ytik:~ # reboot
What happened next... Windows 10 boots
Well, in this case you told it to boot Windows (BootOrder: 0003,...). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Moin, On Tue, 04 Oct 2016, 07:27:24 +0200, James PEARSON wrote: [...]
linux-ytik:~ # efibootmgr -b 0 - B 0
Notice the ' ' *between* "- B". In case you typed it this way, I'm sure it wouldn't remove the Windows entry. HTH, cheers. l8er manfred
On Tue 04 Oct 2016 07:27:24 AM CDT, James PEARSON wrote:
Hello
Mon, 3 Oct 2016, Malcolm wrote : What I suggest is to boot into openSUSE, delete the existing windows and openSUSE entries and re-add with efibootmgr so openSUSE is first;
efibootmgr -b 1 -B 1 efibootmgr -b 0 - B 0 efibootmgr -c -L "opensuse-secureboot" -l "\\EFI\\opensuse\\shim.efi" efibootmgr -c -L "Windows Boot Manager" -l "\\EFI\\Microsoft\\Boot\\bootmgfw.efi"
linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC # linux-ytik:~ # efibootmgr -b 1 -B 1 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # efibootmgr -b 0 - B 0 BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk # linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC # linux-ytik:~ # efibootmgr -c -L "opensuse-secureboot" -l "\\EFI\\opensuse\\shim.efi" ** Warning ** : Boot0002 has same label opensuse-secureboot BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk Boot0001* opensuse-secureboot # linux-ytik:~ # efibootmgr -c -L "Windows Boot Manager" -l "\\EFI\\Microsoft\\Boot\\bootmgfw.efi" ** Warning ** : Boot0000 has same label Windows Boot Manager BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0003,0001,0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager Boot0001* opensuse-secureboot Boot0002* opensuse-secureboot Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3001* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3003* Internal Hard Disk or Solid State Disk Boot0003* Windows Boot Manager # linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0003,0001,0000,3000,0002,2001,2002,2003 Boot0000* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC Boot0001* opensuse-secureboot HD(1,800,e1000,48870217-1384-4b8b-9287-0e6402622261)File(\EFI\opensuse\shim.efi) Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot0003* Windows Boot Manager HD(1,800,e1000,48870217-1384-4b8b-9287-0e6402622261)File(\EFI\Microsoft\Boot\bootmgfw.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC linux-ytik:~ # reboot
What happened next... Windows 10 boots
Regards James Hi Delete the entries (all three now) and re add, as pointed out the -<space>B won't work, it was an error (they happen). If you run a command and the output isn't what you think it should be, investigate as to why..
You want openSUSE first, then Windows second, don't restart until that's sorted.... ;) Only 0000 and 0001 (Ignore the 2nnn etc) -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.31-30-default up 9 days 13:56, 2 users, load average: 0.25, 0.23, 0.18 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello
Hi Delete the entries (all three now) and re add, as pointed out the -<space>B won't work, it was an error (they happen). If you run a command and the output isn't what you think it should be, investigate as to why..
You want openSUSE first, then Windows second, don't restart until that's sorted.... ;) Only 0000 and 0001 (Ignore the 2nnn etc)
Below is the situation I have now. linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2002,0002 Boot0000* USB Hard Drive (UEFI) - Crucial Gizmo! Plus ACPI(a0341d0,0)PCI(1d,0)USB(0,0)USB(1,0)HD(1,1,777fff,00049250)RC Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot0003* Internal CD/DVD ROM Drive (UEFI) ACPI(a0341d0,0)PCI(1f,2)03120a00010000000000CD-ROM(1,58,b40)RC Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC # When I rebooted, Windows 10 again. Of course I can hit F9 and get the Boot Meno and manually select 42.2. I just wiped the hard drive because I have to give the PC back to the owner. Many thanks to all that responded. Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-03 19:16, James PEARSON wrote:
linux-ytik:~ # efibootmgr -v BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0001,3001,0002,2001,2002,2003 Boot0001* Windows Boot Manager HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0002* opensuse-secureboot HD(2,e1800,32000,30921fec-a94d-42a8-a047-7fce3417496e)File(\EFI\opensuse\shim.efi) Boot2001* USB Drive (UEFI) RC Boot2002* Internal CD/DVD ROM Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC
# I want the first choice to be Windows 10 (sorry but this is not my PC) and the second choice to be 42.2
No. First choice has to be openSUSE grub, like it or not. Then grub may have as first choice Windows. You have two methods to choose what to boot: boot by default Linux, meaning grub, which presents you a menu with 8 seconds in which to make a choice, or else, present situation in which you have to be fast pressing keys to get the BIOS menu to choose what to boot. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-10-02 23:22, James PEARSON wrote:
I would like to add that after searching that I noticed that 42.2 was installed and that I could boot it if I hit the F8/F9 keys to raise the boot manager in the BIOS. The Boot Option Menu will present the following choices: OS boot Manager (UEFI) - Windows Boot Manager OS boot Manager (UEFI) - opensuse-secureboot Boot for EFI file
So Linux boots, but it is not the first choice. Maybe the uefi (bios) has an option to change the boot order permanently. Otherwise, do what Malcolm said.
As a second note, I would like to add that the wifi works on Windows 10 on a HP Pavillion 15 but it was not picked up by 42.2 (see below for more info) lspci sayes 08:00 Network controller: Broadcom Corportion BCM43142 802.11b/g/n (rev 01)
It would perhaps be better to place this in a separate post with proper subject, few people will see it in a long post.
linux-ytik:~ # parted -l /dev/sda Model: ATA ST1000LM014-1EJ1 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags:
Number Start End Size File system Name Flags 1 1049kB 473MB 472MB ntfs Basic data partition hidden, diag 2 473MB 578MB 105MB fat32 EFI system partition boot 3 578MB 595MB 16.8MB Microsoft reserved partition msftres 4 595MB 349GB 348GB ntfs Basic data partition 5 349GB 353GB 4299MB linux-swap(v1) primary 6 353GB 1000GB 647GB ext4 primary
A single 647GB partition for both home and root? This is not normal. Was it intentional on your side? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Dave Plater -
James PEARSON -
Malcolm -
Manfred Hollstein