http://bugzilla.opensuse.org/show_bug.cgi?id=1127765 http://bugzilla.opensuse.org/show_bug.cgi?id=1127765#c4 --- Comment #4 from Nick Dordea <ndordea@gmail.com> --- Hello Stefan, A) Unfortunately I did not get any other messages . I was not able to start opensuse so I did not have access to yast2 messages . However as I said on my comment#2 I tried a new install in which I did not mounted /dev/sdb2 as /boot/efi [ even if the install indicated that ] I created a new partition /dev/sda1 1GB as EFI Boot Partition formatted as FAT and mounted as /boot/efi . It worked . opensuse leap 15.0 started nicely [ via Boot from Harddisk ] . Then I tried to boot without the install CD present . The boot went directly to Windows. So today I created a usb bootable usb based on opensuse-15-0_NETWORK_...iso [ via a windows 10 freebie ] . I keep that usb in one port and I can boot opensue/windows . I do not know how to avoid the install CD or usb to boot in linux. It is not big deal .... I believe that , if the machine has more than one disk, the install should not tell the user to mount other ESP as /boot/efi . I wonder if the install tells the user that there is another ESP [ in my case associated with windows ] . It that one is created by Linux ... use it otherwise tell the user to create a new one on "linux" disk . Maybe my assumption is wrong, but creating a EFI partition via linux helped me. ==================== B). Today I discovered that the wifi connection is not defined/started . Yast2 hardware reports RTL8822BE 802.11 a/b/g/n/ac Wifi Adaper . I tried to install it manually but I do not know the Kernel driver associated with this adapter. The only info found relative to rtl8822 is in /lib/firmware/rtlwifi/rtl8822befw.bin other 3 enttries are in /lib/firmware/rtl-bt/rtl8822b_config.bin rtl8822b_fw.bin rtl8822cu-fw.bin Is it possible to try with 2t2800pci.ko which is used by my old machine ? Should I open a new ticket for this wifi issue ======================== Thank you very much for looking into this issue. Best, Nick -- You are receiving this mail because: You are on the CC list for the bug.