Hi openSUSE users,
Recently I’m giving up Win 10 and planning on moving to Linux. I am a complete newbie to the Linux system, so please bear with me if I have to post photos instead of logs and such. I am not familiar with many things and just trying to make myself as understandable.
I tried to install openSUSE but something really weird happened. The installation didn’t took place as expected.
(My system settings are listed at the end of this thread.)
The ISO is the latest stable release of LEAP 42.1, SHA 256 matched. I created a bootable with ImageUSB, with the FS being FAT. Everything seemed smooth.
When I first bought my laptop, it has one PCIe ssd with no OS installed (I plan to install openSUSE on this drive). So I plugged in another SATA3 SSD w/ win10 installed which I took off from my old laptop. For some reason I don’t know under UEFI I cannot boot into Win 10 so I ran on Legacy.
After searching through various installation guides. I turned BIOS back to UEFI mode, with Fast Boot and Secure Boot turned off.
With the USB stick plugged in I came to such a screen, which seem to be slightly different from what I’ve seen in tutorials. It lacks a few options. (Please forgive me for the big chunk of image)
No matter which 1 of the 4 options I chose. When I pressed Enter I was directed to a black screen with green loading bar at bottom, with “openSUSE Leap 42.1 (x86_64)” at the bottom right corner.
If I press any button like the arrow keys or esc, it shows a log like this:
"
Loading basic drivers… ok
Starting hardware detection… ok
(If a driver is not working for you, try booting with brokenmodules=driver_name.)
Activating usb devices… ok
Kingston DataTraveler 3.0
drivers: uas, usb_storage*
MSI EPF USB
drivers: usbhid*
Logitech Gaming Mouse G502
drivers: usbhid*
Realtek RTS 5129 Crad Reader Controller
drivers: rtsx_usb*
Intel Dual Band Wireless AC 3165
drivers: iwlwifi*
"
and when the green bar appears fully loaded. I am stuck forever. No GUI is showing up, so I have to shut down my computer. It happens when I choose either of the 4 options when I am at the boot option screen.
I have tried installing Linux Mint, didn’t access installation either but the error message was something like “NMI watchdog, soft lockup, CPU stuck for 22 seconds”. The nomodeset parameter added to kernel lines didn’t solve the issue. I have also tried installing Arch, it always shows loader.efi not found. I successfully installed Antergos once under Legacy mode, but couldn’t boot in GUI. so I formatted the partition and fixed the MBR.
I really have no idea about what is going on with my laptop. Using Win 10 have not been a so friendly experience lately and I really want to join the Linux club. Please bear with my noobness, cause I am really new to the OS. Any guidance will be more than appreciated.
Thank you.
***The model is MSI GE62 6QF-013XCN
CPU: Intel Core i7-6700HQ
Chipset: Intel HM170
RAM: 28g DDR4
BIOS: AMI (09/11/2015)
Graphics: Intel HD Graphics 530 and nVIDIA GeForce GTX 970M
IDE controller: Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller
Perfect - this screen is the installation start screen, when the DVD was booted in UEFI mode. So nothing to worry about.
Your machine has two graphic devices. Searching the forum with “bumblebee” might give you some hints on how to deal with that (i do not have such a combination, so i can’t help). And your CPU seems rather new. I read about problems with Skylake CPUs and older kernels. So again, searching the forum/the internet with “Skylake” might produce information on this.
Thank you for the reply! Much appreciated.
Actually I have looked into bumblebee. Almost all the info I could find are dealing with “after an installation of the OS”. Same thing with searching skylake, all the troubleshooting seemed to be based on a buggy yet successful installation. I see “install packages” being mentioned. Is that something we can do before an OS is set up on the machine? I really have no idea, and didn’t really find any similar situation like mine. From what I learned so far, with Skylake, Linux kernel 4.1 could be really buggy. Does it mean that Leap 42.1 shall not be the suitable system for my machine?
Yes sir, I have tried a live system. Yet not openSUSE have I tried. Last month when I was trying to install Antergos I did get a live system on my USB stick. I have it installed on the PCIe drive afterwards, but find myself a load of error messages and not able to access the GUI with the latest kernel. Though I succeeded with the LTS kernel, lacking driver for everything, I found Arch a bit difficult to set up for me so I formatted the partition and fixed MBR.
With Krypton Live I was stuck at a line “EDD INFORMATION NOT AVAILABLE”, so I tried the Failsafe mode and was asked for a “nohostname login” which I have no clue about what to put in. I didn’t get to have the chance for setting up such an account. I tried to leave the name and password blank but no luck. Any suggestion?
At boot, on the line that starts the live system, hit “e”, navigate towards “showopts” and add a space and “nomodeset”, then hit F10 to boot. Don’t think too soon that it’s notworking, on one laptop here it took ~5 minutes before the destop started.
Yes sir, I left it there and went for a workout which was 40 min, and it was still stuck there, so I boldly assumed it was not working . I will try the line right now.
I have no idea whether that will help but here are some settings from my MS-7918/Z97 GAMING 3 motherboard (desktop, no notebook and Haswell not Skylake !!!):
Sorry, but i do not have any better idea at the moment. Maybe it helps if you check your settings and try the ones above (if they are available in your UEFI).
One more question:
If you choose the option “Rescue System” (with boot splash disabled), what are the last messages before the system stops?
Knurpht,
Krypton Live plus “nomodeset” certainly did some magic. I have just successfully installed openSUSE to my hard drive (though I don’t see win 10 as boot option, it makes me happier actually!) Now I will be dealing with SUSE prime and soon playing around with my brand new OS!
Thank you so much for your help. I’m certainly grateful.
Please don’t be sorry. You’re really trying to help and I really appreciate it! I followed Knupht’s lead, downloaded the latest Krypton Live image, created live USB, and put in “nomodeset” at the end of the kernel line. And now everything’s running like a charm. I’m enjoying the new OS!
Seems that the problem should be the kernel of Leap 42.1 is not playing nicely with my hardware…
For your question:
When I chose “rescue system” (though I didn’t disable splash screen), it shows the log below. Exactly like what I’m shown when I choose other options, which seemed to be really weird.
"
Loading basic drivers… ok
Starting hardware detection… ok
(If a driver is not working for you, try booting with brokenmodules=driver_name.)
Activating usb devices… ok
Kingston DataTraveler 3.0
drivers: uas, usb_storage*
MSI EPF USB
drivers: usbhid*
Logitech Gaming Mouse G502
drivers: usbhid*
Realtek RTS 5129 Crad Reader Controller
drivers: rtsx_usb*
Intel Dual Band Wireless AC 3165
drivers: iwlwifi*
"
Anyway, I have the OS successfully installed to my hard drive now. OpenSUSE, not only the OS, but also the community looks amazing so far!
Ok you must install in the same boot mode as Windows 10 which is probably EFI to see the Windows OS. So you must boot the Installer in EFI mode. If you did (initial screen should correct) then check Win10 (should be able to boot from EFI boot screen) and be sure that FAST boot is off, since it make the Windows partitions unmountable and the installer may not include any Windows stuff. You still have to deal with the Optimus graphics (Intel+NVIDIA)
I’ve been using openSUSE for over a decade & upgraded to Leap 42.1 (KDE Plasma 5) a few weeks ago. Yesterday I successfully installed the nVidia driver for my video card but the change resulted in a 2-3 minute lag between leaving the login screen and getting my desktop (which is not complicated) displayed. This had not been the case prior to the nVidia driver install.
Following your instructions, I easily changed GRUB2, rebooted, and - voila! - quick display of my desktop with no problems. I am a happy puppy.
PS - added to your reputation - the least I could do.
nomodeset cause the use of fall back drivers which in general are inferior but almost certain to function. Also making the change at the grub screen is not permanent so will not be set at the next boot. Essentially this is a one time method to get to a working GUI where you can then hopefully fix the problem. Since krypton is about as cutting edge as you can get proprietary drivers may or may not work.
Note even MS is not supporting Win7 on skylake processors.
From what I learned so far, with Skylake, Linux kernel 4.1 could be really buggy. Does it mean that Leap 42.1 shall not be the suitable system for my machine?
. I will try the line right now.