Total meltdown story

[Retor]

I´m having a really bad day.

1. I decided it probably was to to upgrade, and followed the instructions.
2. After a reboot, the dual monitors didn´t work
3. I tried to follow the instructions to install Nvidia drivers, but I have 10-series card - not 8xxx og 400, so I …
4. tried to go to Nvidia - that borked my system, so i booted up with nomodeset 3 and rolled back to nouvau.
5. I found I guy who had used G04 for hos 1070, so i figured that was the right choice even though I have 1060 mobile. But that also borked my system - so i decided the best thing was to just start over
6. I downloaded Leap 15, put it on a usb stick and installed it, keeping my home and formatting the boot, swap and root partition
7. After booting, windows 10 was gone from the boot menu, and openSuSE kept hanging at random places during boot
8. I got in using nomodeset and started X. I googled more and decided I might have previously bootet Win 10 and openSuSE from MBR, not UEFI and changed from UEFI grub to grub
9. Windows still did not appear, and opensuse will now not leave grub. It just flashes.
10. I thought I´d try to reinstall Leap again - but now the installer hangs on the bar with three shades of green.

I have no idea where to go from here.

[Retor]

Hey, I found out how to deactivate UEFI. Now it boots again (with nomodeset).

Any tips on brinng Win 10 back alive?

sudo parted -l

Model: ATA WDC WD10SPZX-75Z (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  135MB   134MB                Microsoft reserved partition  msftres
 2      135MB   1000GB  1000GB  ntfs         Basic data partition          msftdata


Model: SanDisk SanDisk Cruzer (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  16.0GB  16.0GB  fat32


Model: SanDisk Cruzer (scsi)
Disk /dev/sdc: 8000MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  8000MB  8000MB  fat32


Model: NVMe Device (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  525MB  524MB   fat16           EFI system partition          boot, esp
 2      525MB   660MB  134MB                   Microsoft reserved partition  msftres
 3      660MB   218GB  218GB   ntfs            Basic data partition          msftdata
 7      218GB   220GB  2159MB  linux-swap(v1)  primary                       swap
 8      220GB   231GB  10.7GB  ext4            primary                       legacy_boot
 9      231GB   240GB  8656MB  ext4            primary
 4      240GB   241GB  847MB   ntfs                                          hidden, diag
 5      241GB   255GB  14.2GB  ntfs                                          hidden, diag
 6      255GB   256GB  1205MB  ntfs                                          hidden, diag

From what I can see, it looks like it should have been UEFI all along.

sudo efibootmgr -v

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0000,0003
Boot0000* Windows Boot Manager    HD(1,GPT,cb7eac6d-2dd8-48bc-b7be-bac9f2407bbe,0x800,0xfa000)/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.}....................
Boot0001* opensuse-secureboot    HD(1,GPT,cb7eac6d-2dd8-48bc-b7be-bac9f2407bbe,0x800,0xfa000)/File(\EFI\opensuse\shim.efi)
Boot0003* test    PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/HD(1,MBR,0x37a2e323,0x800,0x1cf7800)/File(\EFI\BOOT\grub.efi)

[mrmazda]

As long as Windows is installed in UEFI mode, it can only be booted by a UEFI bootloader. Thus, openSUSE must also be installed in UEFI mode, unless you’re OK with needing to enter BIOS setup to switch boot mode each time you wish to boot to the other OS.

For installation, instead of using nomodeset as a video workaround, try removing quiet and splash=silent, and if that’s not good enough, add plymouth.enable=0.

NVidia and nouveau are not the only drivers suitable for NVidia gfxcards. There’s also modesetting, which is integral to the X server and automatically used whenever neither xf86-video-nouveau nor proprietary NVidia drivers are installed. Neither nouveau nor modesetting X drivers will load if kernel cmdline contains nomodeset.

[Retor]

Thanks, man. I really appreciate your effort to help!

@mrmazda

As long as Windows is installed in UEFI mode, it can only be booted by a UEFI bootloader. Thus, openSUSE must also be installed in UEFI mode, unless you’re OK with needing to enter BIOS setup to switch boot mode each time you wish to boot to the other OS.

Something is way more wrecked. openSuSE was installed in UEFI mode. I tried to switch to legacy just in case I remeber wrong, but I know understand that Windows can’t be in legacy. So I switched back.

@mrmazda

For installation, instead of using nomodeset as a video workaround, try removing quiet and splash=silent, and if that’s not good enough, add plymouth.enable=0.

None of those worked, unfortunately.

@mrmazda

NVidia and nouveau are not the only drivers suitable for NVidia gfxcards. There’s also modesetting, which is integral to the X server and automatically used whenever neither xf86-video-nouveau nor proprietary NVidia drivers are installed. Neither nouveau nor modesetting X drivers will load if kernel cmdline contains nomodeset.

I tried uninstalling nouveau, but things looked a little strange in Yast, so I’m not sure I managed.

Status now is that I gave up and installed Ubutnu, which looks better, but there’s still no windows 10. In fact - the entire grub menu is gone (probably because there’s only 1 item in it). I tried grub probing, but no luck so far.

So. Fixing windows is my primary concern, and I feel like openSuSE is in better shape to help me with that, so my next step i reinstalling openSuSE and try to figure out how to bring win 10 back to life. The files are all there. I just can’t boot into the partition.

[Retor]

Got 1 thing fixed!

I think my problem was that when I installed openSuSE, I formated the EFI boot partition. So the microsoft folder with all the WIndows efi-files (or whatever they were) got deleted. In order to recreate those, I had to download windows 10, put it on a USB and boot into that. I tried runing vanila recovery, but it couldn’t fix it. So I ran Bootrec.exe and first did /ScanOS to find the os, then wrote those using RebuildBcd. That didn’t work in itself, but then i ran /FixMbr. That didn’t work, but now I was able to run vanilla recovery, then deactivated grub and finally it booted into windows.

So. My family wont kill me. Now I just need to a Linux back. Since Ubuntu seem to handle my Nvidia card without me having to install,uinstall stuff, I’m just gonna stick with it. For now

[mrmazda]

You can rescue boot openSUSE and use chroot to get YaST to update the bootloader. Simply change the timeout value and exit should be all it takes. YaST won’t delete anything from the ESP partition, but probably will switch the default from Windows to openSUSE. You can use efibootmgr to change it back, or make the default switch back by using the EFI BIOS boot priority menu.

[brunomcl]

@Retor

1. I found I guy who had used G04 for hos 1070, so i figured that was the right choice even though I have 1060 mobile.
   But that also borked my system - so i decided the best thing was to just start over

Mobile? Not dual graphics, perhaps? If so, you’d need bumblebee or similar, nvidia driver would be problematic.

FWIW, G04 works fine here with a GTX1050 in LEAP 42.3, and G03 for a GTX650 in LEAP 15. Both are Intel desktops.