Hello
I can not install Leap 15.0 (openSUSE-Leap-15.0-DVD-x86_64.iso downloaded today) on a friend's old Asus X53S laptop. This was a bit unexpected because the machine was running a dual boot setup Win7 / openSUSE-42.1 that I installed a few years ago. A sticker on the laptop sayes that it has a "GEFORCE GT540M CUDA 2GB" card.
The installation of Leap 15.0 stops abruptly at boot menu right after I select "Leap 15.0" to initiate the installation : Loading initial kernel... Loading initial ramdisk...
I tried hitting 'e' at the boot menu screen at the beginning of the Leap 15.0 installation and then scrolling down to the line that begins "linuxefi" and adding "nomodeset" at the end..
Existing line was : linuxefi /boot/x86_64/loader/linux splash=silent I added nomodeset like this : linuxefi /boot/x86_64/loader/linux splash=silent nomodeset After which I hit Ctrl + X or F10 to contine booting. This changed nothing. The installation of Leap 15.0 stops abruptly as before. I also had the same problem trying to install Leap-15.0 with the openSUSE-Leap-15.0-NET-x86_64.iso
I downloaded TW (openSUSE-Tumbleweed-DVD-x86_64-Current.iso) and it installed fine. :)
The Asus X53S video details on TW setup follow : linux-ws6z:~ # lspci -nnk | grep -A3 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) Subsystem: ASUSTeK Computer Inc. Device [1043:15f2] Kernel driver in use: i915 Kernel modules: i915 -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) Subsystem: ASUSTeK Computer Inc. Device [1043:15f2] Kernel driver in use: nouveau Kernel modules: nouveau
I also dug out an old usb key which had Leap-42.3. When I tried installing it, I had same problem - that is the installation of Leap-42.3 stoped abruptly at boot menu with the same info : Loading initial kernel... Loading initial ramdisk...
Any and all help to install Leap-15.0 and/or comments are appreciated. TIA
Regards James
On 2018-07-15 19:30, James PEARSON wrote:
Hello
I can not install Leap 15.0 (openSUSE-Leap-15.0-DVD-x86_64.iso downloaded today) on a friend's old Asus X53S laptop. This was a bit unexpected because the machine was running a dual boot setup Win7 / openSUSE-42.1 that I installed a few years ago. A sticker on the laptop sayes that it has a "GEFORCE GT540M CUDA 2GB" card.
The installation of Leap 15.0 stops abruptly at boot menu right after I select "Leap 15.0" to initiate the installation : Loading initial kernel... Loading initial ramdisk...
I tried hitting 'e' at the boot menu screen at the beginning of the Leap 15.0 installation and then scrolling down to the line that begins "linuxefi" and adding "nomodeset" at the end..
Existing line was : linuxefi /boot/x86_64/loader/linux splash=silent I added nomodeset like this : linuxefi /boot/x86_64/loader/linux splash=silent nomodeset
I would use "splash=verbose" instead. Maybe you get some message that way.
Hello
Sunday 15 Jul 2018 19:55:04 +0200, "Carlos E. R." robin.listas@telefonica.net said : I would use "splash=verbose" instead. Maybe you get some message that way.
Thank-you for the come-back.
Done. Below is the result : opensSUSE Leap 15.0
Booting a command list
Loading kernel ... Loading inital ramdisk ... _
Regards James
On 2018-07-15 20:47, James PEARSON wrote:
Hello
Sunday 15 Jul 2018 19:55:04 +0200, "Carlos E. R." robin.listas@telefonica.net said : I would use "splash=verbose" instead. Maybe you get some message that way.
Thank-you for the come-back.
Done. Below is the result : opensSUSE Leap 15.0
Booting a command list
Loading kernel ... Loading inital ramdisk ...
Nothing more? Very discouraging :-( Did you wait long enough? Like five minutes.
If not, let's wait for more people to comment.
Some extra comments:
The email signature separator has to be dash-dash-space-newline. The way you have it, it is not recognized as such.
You are using PGP signing, but you have not uploaded your key to the public servers, so I can not find it and thus not verify your email ;-)
James PEARSON composed on 2018-07-15 19:30 (UTC+0200): ...
Any and all help to install Leap-15.0 and/or comments are appreciated.
Is it still bootable to 42.1 and/or Windows? If yes, do an online upgrade. I've done a bunch of those from 13.1, 42.1, 42.2 and 42.3 to 15.0 with no material negative effects apparent so far.
Did you burn the .iso to DVD, or stick? If only one, try the other. I have yet to install any version of openSUSE from a stick. From DVD to UEFI I just did again last week or so.
Have you already digested? https://en.opensuse.org/SDB:NVIDIA_Bumblebee I have no idea whether at the point you are reaching if Bumblebee is relevant yet. It may not be (I'm guessing not), which means some other cmdline option may be needed.
I acquired two Asus motherboards in recent weeks that are at least 4 years newer than that laptop. I'm not too pleased with either's UEFI functionality. One is boxed up ready to return to vendor. I suspect it's possible you may need to experiment with BIOS UEFI/CSM settings rather than software installation options.
There are other video settings besides nomodeset that could be worth trying. Easiest would be skipping GUI by installing in text mode, so change the cmdline with the e key from:
splash=silent to text
Text mode isn't nearly as convenient, but works on the kernel's framebuffer which don't care about X drivers.
Before falling back to text, you could try other cmdline options besides removing splash=silent (which is a quieting _option_ - without it you get unquiet, which may let you see a useful error message). There's no need to type in verbose. Just remove the whole option, or any part of it.
By adding vga=788 or vga=791 or vga=normal you might get a little farther, or a lot farther, or no farther than you got already. Same goes for explicitly setting a KMS mode, such as that native to your X53S, or close thereto:
video=1366x768 or video=1366x768@60 or video=1360x768
Another possibility: plug it into a TV using an HDMI cable. If it's a 720p rather than full HD 1080 but no better than with the laptop display, video=1366x768 may or may not be helpful, but video=1280x720 could work. If it's full HD 1080 and otherwise no better, video=1920x1080 or video=1280x720 might be. Even video=80x600 or video=640x480 could help.
https://en.opensuse.org/SDB:Linuxrc may have some other cmdline option to get you over the hump.
Hello
On Sunday the 15th of Jul 2018 Felix Miata wrote : Did you burn the .iso to DVD, or stick? If only one, try the other. I have yet to install any version of openSUSE from a stick. From DVD to UEFI I just did again last week or so.
I have been installing openSUSE using usb sticks for quite some time. I would be hard pressed to say how long....
I tried adding nomodeset on the boot menu page like this (this is on an usb stick installation) : linuxefi /boot/x86_64/loader/linux splash=verbose nomodeset
Then I waited 10 minutes or so after which I hit Ctrl + X or F10 to contine booting. Nothing ever happened. I did try switch to text console (ctrl-alt-f1) but no luck.
For test # 2, I burnt openSUSE-Leap-15.0-DVD-x86_64.iso that I downloaded 2 days ago to a DVD medium. I must admit that it has been quite a few years since I burnt an openSUSE iso to a DVD medum (which is probably why I have tons in the garage). I am very happy to report that your idea worked ! Thank-you very much :)
The bottom line is that I now have dual boot Leap 15.0 / TW system with UEFI functionality. Next step is to install Win10 in virtualbox in common directory.
I acquired two Asus motherboards in recent weeks that are at least 4 years newer than that laptop. I'm not too pleased with either's UEFI functionality.
I am (unfortunately) 100% agreement with you on that .
Regards from Paris James
P.S. Thanks to all for their help
On 2018-07-16 19:47, James PEARSON wrote:
Hello
On Sunday the 15th of Jul 2018 Felix Miata wrote : Did you burn the .iso to DVD, or stick? If only one, try the other. I have yet to install any version of openSUSE from a stick. From DVD to UEFI I just did again last week or so.
I have been installing openSUSE using usb sticks for quite some time. I would be hard pressed to say how long....
I tried adding nomodeset on the boot menu page like this (this is on an usb stick installation) : linuxefi /boot/x86_64/loader/linux splash=verbose nomodeset
Then I waited 10 minutes or so after which I hit Ctrl + X or F10 to contine booting. Nothing ever happened. I did try switch to text console (ctrl-alt-f1) but no luck.
For test # 2, I burnt openSUSE-Leap-15.0-DVD-x86_64.iso that I downloaded 2 days ago to a DVD medium. I must admit that it has been quite a few years since I burnt an openSUSE iso to a DVD medum (which is probably why I have tons in the garage). I am very happy to report that your idea worked ! Thank-you very much :)
WHAAT!!?? :-O
This is very surprising. May I suggest that you write this in a Bugzilla official report, against "install/update issues"? The idea is to make the people that create the media to be aware of this strange situation.
I do have an idea of what it might be, if it is what happened to me the other days in a laptop: it will not boot a hard disk from USB3 (with Windows), but it does from USB2. The explanation I got is that the USB 3 bus got reset on mid boot and lost track. In my case, it turned to boot instead from the internal disk.
On 07/15/2018 12:30 PM, James PEARSON wrote:
The installation of Leap 15.0 stops abruptly at boot menu right after I select "Leap 15.0" to initiate the installation : Loading initial kernel... Loading initial ramdisk...
I suspect the install is not actually stuck, but a NMI handler and watchdog timer probably detected a "soft lockup - CPU#6 stuck for 22s!" (or 23s -- both are common).
When this occurs, it triggers a length check on startup where the kernel will dump all registers on each CPU core and verify all interrupts only to find out that everything is actually OK -- and then complete the boot.
The only problem is **this can take up to 5 minutes** where there is no indication of what is happening. No doubt your pulled to plug long before that amount of time elapse (there is no way you could tell what was going on)
If you do try it again. When it looks stuck at:
Loading initial kernel... Loading initial ramdisk...
Start a timer and let a full 6:30 seconds elapse before you do anything else. If the boot does ultimately succeed, then if you can get to a xterm or console (perhaps at the end of the install, but before reboot) Save the dmesg output, e.g.
$ cd ## make sure you are in your (or roots) home directory $ mkdir tmp ## make a tmp directory $ dmesg > tmp/$(date +%Y%m%d-%H%M%S)_dmesg ## save dmesg in file
The command substitution $(date +%Y%m%d_%H%M%S) just appends the date and time to the beginning of the output filename, e.g. you would see in tmp/ something similar to:
20180716_030147_dmegs
Then upload the result of dmesg to http://paste.opensuse.org/
On 2018-07-16 10:05, David C. Rankin wrote:
On 07/15/2018 12:30 PM, James PEARSON wrote:
Start a timer and let a full 6:30 seconds elapse before you do anything else. If the boot does ultimately succeed, then if you can get to a xterm or console (perhaps at the end of the install, but before reboot) Save the dmesg output, e.g.
$ cd ## make sure you are in your (or roots) home directory
The one on the harddisk, not in the install media.
$ mkdir tmp ## make a tmp directory $ dmesg > tmp/$(date +%Y%m%d-%H%M%S)_dmesg ## save dmesg in file
On 07/16/2018 03:54 AM, Carlos E. R. wrote:
Start a timer and let a full 6:30 seconds elapse before you do anything else. If the boot does ultimately succeed, then if you can get to a xterm or console (perhaps at the end of the install, but before reboot) Save the dmesg output, e.g.
$ cd ## make sure you are in your (or roots) home directory
The one on the harddisk, not in the install media.
Yes, yes :) -- the one on tmpfs will not be there after reboot.
$ mkdir tmp ## make a tmp directory $ dmesg > tmp/$(date +%Y%m%d-%H%M%S)_dmesg ## save dmesg in file
On 2018-07-16 11:03, David C. Rankin wrote:
On 07/16/2018 03:54 AM, Carlos E. R. wrote:
Start a timer and let a full 6:30 seconds elapse before you do anything else. If the boot does ultimately succeed, then if you can get to a xterm or console (perhaps at the end of the install, but before reboot) Save the dmesg output, e.g.
$ cd ## make sure you are in your (or roots) home directory
The one on the harddisk, not in the install media.
Yes, yes :) -- the one on tmpfs will not be there after reboot.
Right :-)
It has to be said because it is not trivial to see where it is during install or upgrade. It has to be mounted, else packages would not be installed there, but the problem for the user is to find out where.
So inspect the output of the command "mount" and it can be seen, probably hanging down from /mnt or somewhere I don't remember ;-)
-
Carlos E. R. -
David C. Rankin -
Felix Miata -
James PEARSON