[opensuse] Leap 15.0 won't boot on a Lenovo T420
Hello, I've installed Leap 15.0 on a Lenovo T420 laptop twice, and both attempts resulted in a non-bootable system. During the first installation, I used the Suggested Partitioning option (no other OS on the HD). The installation completed without any warning/error messages. After the restart, the system was stuck and showed exactly the screen shown in the first 8 seconds of this video (not mine and advance apologies for the music): https://www.youtube.com/watch?v=zfr6OldZGVM Using Hiren's rescue cd, I was able to boot the system from the cd, then start Leap 15.0 from HDD0. I saw a short notice that GRUB2 was starting (never saw that when booting from the HDD), then Leap 15.0 was starting, and I could log in. Leap 15.0 appeared to be running fine from the HDD. Then I wiped the HDD, and reinstalled Leap 15.0 with the Guided Setup. I noticed a GPT entry in the proposed partitioning scheme, but I didn't touch that and didn't change anything else. Installation completed OK. After the restart it was stuck again just like in the video. At both attempts, I've changed the boot order and disabled network boot in the BIOS to no avail. I've tried *every* available boot option in the BIOS to no avail, including UEFI / Legacy Boot etc. This laptop has been running Leap 42.3 for months with none of above issues. Because I need a running OS on this laptop, I now installed Linux Mint, and it boots fine from the HDD. Just thought I'd bring this to your attention. Regards, Fritz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/11/2018 11.53, 712@vivaldi.net wrote:
Hello,
I've installed Leap 15.0 on a Lenovo T420 laptop twice, and both attempts resulted in a non-bootable system.
During the first installation, I used the Suggested Partitioning option (no other OS on the HD). The installation completed without any warning/error messages. After the restart, the system was stuck and showed exactly the screen shown in the first 8 seconds of this video (not mine and advance apologies for the music):
I have a laptop that shows that message one of each three boots or so. I just press ctrl-alt-del and eventually it boots. In my case, it is related to me changing the hard disk with an ssd.
Using Hiren's rescue cd, I was able to boot the system from the cd, then start Leap 15.0 from HDD0. I saw a short notice that GRUB2 was starting (never saw that when booting from the HDD), then Leap 15.0 was starting, and I could log in. Leap 15.0 appeared to be running fine from the HDD.
Then I wiped the HDD, and reinstalled Leap 15.0 with the Guided Setup. I noticed a GPT entry in the proposed partitioning scheme, but I didn't touch that and didn't change anything else. Installation completed OK. After the restart it was stuck again just like in the video.
At both attempts, I've changed the boot order and disabled network boot in the BIOS to no avail. I've tried *every* available boot option in the BIOS to no avail, including UEFI / Legacy Boot etc.
This laptop has been running Leap 42.3 for months with none of above issues. Because I need a running OS on this laptop, I now installed Linux Mint, and it boots fine from the HDD.
Just thought I'd bring this to your attention.
If you have installed mint now, there is nothing we can do or comment. It is just like a rant, useless. Sorry. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Le 21/11/2018 à 12:10, Carlos E. R. a écrit :
If you have installed mint now, there is nothing we can do or comment. It is just like a rant, useless. Sorry.
seems to me obvious she can reinstall openSUSE, amd mint notice was only to show the laptop can boot jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.1811211251550.19334@Telcontar.valinor> On Wednesday, 2018-11-21 at 12:41 +0100, jdd@dodin.org wrote:
Le 21/11/2018 à 12:10, Carlos E. R. a écrit :
If you have installed mint now, there is nothing we can do or comment. It is just like a rant, useless. Sorry.
seems to me obvious she can reinstall openSUSE, amd mint notice was only to show the laptop can boot
Or a double boot system. But nothing we suggest to do can be tested as it is. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlv1RwwACgkQtTMYHG2NR9XSggCgio8hnLSAaYrn1Cr2eJIWyp4H X0wAnjN1bbnvLSIdswm6DgeWaTbkhDMY =DsOh -----END PGP SIGNATURE-----
Hi, Thanks for your reply, it wasn't meant as a rant, sorry. I just need an OS on this laptop that will boot by itself, without the need of a rescue cd. Mint provides that, temporarily, I hope; I'd rather use Suse. Summarized: Leap 42.3 booted and ran without any problems on this T420. Leap 15.0 won't boot on the same system. Both were clean installs using Suggested Partitioning, BTW. Both were the only OS on the HDD, no dual booting. Could it be that in 15.0 something has changed that would prevent booting of this (fairly old) T420? Regards, Fritz On 2018-11-21 12:10, Carlos E. R. wrote:
If you have installed mint now, there is nothing we can do or comment. It is just like a rant, useless. Sorry.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 21 november 2018 16:41:13 CET schreef 712@vivaldi.net:
Hi,
Thanks for your reply, it wasn't meant as a rant, sorry. I just need an OS on this laptop that will boot by itself, without the need of a rescue cd. Mint provides that, temporarily, I hope; I'd rather use Suse.
Summarized:
Leap 42.3 booted and ran without any problems on this T420.
Leap 15.0 won't boot on the same system.
Both were clean installs using Suggested Partitioning, BTW. Both were the only OS on the HDD, no dual booting.
Could it be that in 15.0 something has changed that would prevent booting of this (fairly old) T420?
Regards, Fritz
On 2018-11-21 12:10, Carlos E. R. wrote:
If you have installed mint now, there is nothing we can do or comment. It is just like a rant, useless. Sorry. What happens, if after a Leap 15 install and removal of the install medium, you use YaST's bootloader module, change the delay from 8 to f.e. 7 secs, OK OK OK, reboot?
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/11/2018 16:41, 712@vivaldi.net wrote:
Leap 42.3 booted and ran without any problems on this T420.
Leap 15.0 won't boot on the same system.
Both were clean installs using Suggested Partitioning, BTW.
So, install 42.3, then upgrade it? -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi,
Thanks for your reply, it wasn't meant as a rant, sorry. I just need an OS on this laptop that will boot by itself, without the need of a rescue cd. Mint provides that, temporarily, I hope; I'd rather use Suse.
Summarized:
Leap 42.3 booted and ran without any problems on this T420.
Leap 15.0 won't boot on the same system.
Both were clean installs using Suggested Partitioning, BTW. Both were the only OS on the HDD, no dual booting.
Could it be that in 15.0 something has changed that would prevent booting of this (fairly old) T420?
Regards, Fritz
On 2018-11-21 12:10, Carlos E. R. wrote:
If you have installed mint now, there is nothing we can do or comment. It is just like a rant, useless. Sorry. A question: did you have 42.3 and did an upgrade or did you just try it, erase it and then
In data mercoledì 21 novembre 2018 16:41:13 CET, 712@vivaldi.net ha scritto: tried to install 15? I have a X201 (so even older). There have been changes the way you can use/ should use the tpm with my model and there are problems with virtualization etc. Your T420 should have a smart check in the BIOS that I would run as a first test and I would also run a memory check. If all results O.K. then you can fairly rule out the hardware as problem. On this page you have a list of numeric error codes for you system, provided the system gets you one. (On the youtube video the image is too smal to be able to read what is written, sorry). https://support.lenovo.com/de/it/solutions/migr-42321 If you did burn a DVD it is good practice to use a second dvd or an usb drive that was converted with suse image writer to exclude a problem of the medium that may(!), seldom but had that one time, allow install but makes you problems thereafter. Hope that helps somewhat. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data mercoledì 21 novembre 2018 17:36:41 CET, stakanov ha scritto:
In data mercoledì 21 novembre 2018 16:41:13 CET, 712@vivaldi.net ha scritto:
Hi,
Thanks for your reply, it wasn't meant as a rant, sorry. I just need an OS on this laptop that will boot by itself, without the need of a rescue cd. Mint provides that, temporarily, I hope; I'd rather use Suse.
Summarized:
Leap 42.3 booted and ran without any problems on this T420.
Leap 15.0 won't boot on the same system.
Both were clean installs using Suggested Partitioning, BTW. Both were the only OS on the HDD, no dual booting.
Could it be that in 15.0 something has changed that would prevent booting of this (fairly old) T420?
Regards, Fritz
Oh and I did forget: at times, try to download the iso a second time or check the checksum well, to be sure the iso of 15 is correct and not damaged during download. (The intrinsic media check will run only on the dvd though, AFAIR, due to a bug, so in case you use usb, use another usb and check the sum of the iso before preparing it). _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
712@vivaldi.net composed on 2018-11-21 16:41 (UTC+0100):
Could it be that in 15.0 something has changed that would prevent booting of this (fairly old) T420?
Nothing on https://www.cnet.com/products/lenovo-thinkpad-t420/specs/ looks suspicious to me. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/11/2018 16.41, 712@vivaldi.net wrote:
Hi,
Thanks for your reply, it wasn't meant as a rant, sorry. I just need an OS on this laptop that will boot by itself, without the need of a rescue cd. Mint provides that, temporarily, I hope; I'd rather use Suse.
I understand, but you see, we can do nothing as we can not test the broken system.
Summarized:
Leap 42.3 booted and ran without any problems on this T420.
Leap 15.0 won't boot on the same system.
Both were clean installs using Suggested Partitioning, BTW. Both were the only OS on the HDD, no dual booting.
Could it be that in 15.0 something has changed that would prevent booting of this (fairly old) T420?
The thing is, that message comes from the BIOS, not from the system. It could be that nothing was installed in the master boot record, thus the bios "sees" nothing. Or that it has the wrong signature. If 15 were installed I'd try running "bootinfoscript" and examine the result or post it here. You can obtain it here <https://github.com/arvidjaar/bootinfoscript> -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Hello Carlos and all, Thank you for your reply. I've reinstalled Leap 15, a clean single install, Mint has been removed. @Knurpht: I changed the delay to 7, 6, and 5 secs in YaST's bootloader module. This made no difference, Leap 15 still wouldn't boot from the HDD. Using Hiren's rescue disk, I am able to boot Leap 15. The output from bootinfoscript (output.txt) is in the zipped attachment. I hope this is helpful. Many thanks for taking the time! Regards, Fritz On 2018-11-21 19:48, Carlos E. R. wrote:
If 15 were installed I'd try running "bootinfoscript" and examine the result or post it here.
You can obtain it here <https://github.com/arvidjaar/bootinfoscript>
Op donderdag 22 november 2018 16:38:39 CET schreef 712@vivaldi.net:
Hello Carlos and all,
Thank you for your reply. I've reinstalled Leap 15, a clean single install, Mint has been removed.
@Knurpht: I changed the delay to 7, 6, and 5 secs in YaST's bootloader module. This made no difference, Leap 15 still wouldn't boot from the HDD.
Using Hiren's rescue disk, I am able to boot Leap 15.
The output from bootinfoscript (output.txt) is in the zipped attachment.
I hope this is helpful. Many thanks for taking the time!
Regards, Fritz
On 2018-11-21 19:48, Carlos E. R. wrote:
If 15 were installed I'd try running "bootinfoscript" and examine the result or post it here.
You can obtain it here <https://github.com/arvidjaar/bootinfoscript> Isn't that missing the small /boot/efi vfat partition?
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Knurpht-openSUSE <knurpht@opensuse.org> [11-22-18 10:44]:
Op donderdag 22 november 2018 16:38:39 CET schreef 712@vivaldi.net:
Hello Carlos and all,
Thank you for your reply. I've reinstalled Leap 15, a clean single install, Mint has been removed.
@Knurpht: I changed the delay to 7, 6, and 5 secs in YaST's bootloader module. This made no difference, Leap 15 still wouldn't boot from the HDD.
Using Hiren's rescue disk, I am able to boot Leap 15.
The output from bootinfoscript (output.txt) is in the zipped attachment.
I hope this is helpful. Many thanks for taking the time!
Regards, Fritz
On 2018-11-21 19:48, Carlos E. R. wrote:
If 15 were installed I'd try running "bootinfoscript" and examine the result or post it here.
You can obtain it here <https://github.com/arvidjaar/bootinfoscript> Isn't that missing the small /boot/efi vfat partition?
Boot Info Script 0.75 [14 November 2016] ============================= Boot Info Summary: =============================== => No boot loader is installed in the MBR of /dev/sda. sda1: __________________________________________________________________________ File system: vfat Boot sector type: Windows 8/2012: FAT32 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/Boot/bootx64.efi /efi/opensuse/grub.efi /efi/opensuse/grubx64.efi /efi/opensuse/MokManager.efi /efi/opensuse/shim.efi /efi/Microsoft/Boot/bootmgfw.efi /efi/Microsoft/Boot/bootmgr.efi /efi/Microsoft/Boot/memtest.efi /efi/toshiba/Boot/bootmgfw.efi /efi/toshiba/Boot/bootmgr.efi /efi/toshiba/Boot/memtest.efi -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/11/2018 16.43, Knurpht-openSUSE wrote:
Op donderdag 22 november 2018 16:38:39 CET schreef 712@vivaldi.net:
Hello Carlos and all,
Thank you for your reply. I've reinstalled Leap 15, a clean single install, Mint has been removed.
@Knurpht: I changed the delay to 7, 6, and 5 secs in YaST's bootloader module. This made no difference, Leap 15 still wouldn't boot from the HDD.
Using Hiren's rescue disk, I am able to boot Leap 15.
The output from bootinfoscript (output.txt) is in the zipped attachment.
I hope this is helpful. Many thanks for taking the time!
On 2018-11-21 19:48, Carlos E. R. wrote:
If 15 were installed I'd try running "bootinfoscript" and examine the result or post it here.
You can obtain it here <https://github.com/arvidjaar/bootinfoscript> Isn't that missing the small /boot/efi vfat partition?
Not needed if booting in BIOS mode. Is it? The report says that Grub2 is installed on the MBR of /dev/sda, and the rest of grub is on sda2. For some reason the BIOS in his machine doesn't see this and says there is no operating system installed. There is also a small bios boot partition on sda1. I would try something. One, make sure that the bios is set to boot on legacy mode, not EFI. Although I think if the computer is old, there will be no chance of EFI anyway. Then, on YaST, load the boot module, and select: store default boot sector on MBR grub is on "/" partition, not on MBR Something else? Maybe boot from sda2 - I'm working from memory, not looking at a similar setup. Hum, booting another computer to look at it. [...] Ok: [X] Boot from boot partition [X] Write generic boot code to MBR Bootloader is Grub2. That should be it. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Hello Carlos and all, Alas, still no self-booting Leap 15 here... On 2018-11-22 23:32, Carlos E. R. wrote:
I would try something. One, make sure that the bios is set to boot on legacy mode, not EFI. Although I think if the computer is old, there will be no chance of EFI anyway.
It is set to Legacy Boot only.
Then, on YaST, load the boot module, and select:
store default boot sector on MBR grub is on "/" partition, not on MBR
After I tried above, the YaST boot module shut down with an error message and became inaccessible. There were instructions to file a bug report, but I haven't done that. Instead, I reinstalled Leap 15 yet another time. It still won't boot.
[X] Boot from boot partition [X] Write generic boot code to MBR
Bootloader is Grub2.
Is below screenshot what you mean by above instructions? https://i.postimg.cc/NFRz0RmQ/Screenshot-from-2018-11-24-15-47-59.png (Using these settings Leap 15 won't boot.) Thanks again for any suggestions. Regards, Fritz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 24 Nov 2018 16:03:38 +0100, 712@vivaldi.net wrote:
Is below screenshot what you mean by above instructions?
https://i.postimg.cc/NFRz0RmQ/Screenshot-from-2018-11-24-15-47-59.png
(Using these settings Leap 15 won't boot.)
Thanks again for any suggestions.
Hello: I suggest trying to boot Leap 15.0 using the rescue CD you mentioned in your very first post. After you've logged in to Leap 15 you can try to fix the boot issue manually from a terminal window. First make sure you are running Leap 15.0 on your HD. Check your partitions with "df -h" command, the output is something like this: Filesystem Size Used Avail Use% Mounted on devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 1.8G 108K 1.8G 1% /dev/shm tmpfs 1.8G 2.5M 1.8G 1% /run tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup /dev/sda9 28G 23G 3.7G 86% / This identifies the root ( / ) partition (in this case /dev/sda9). Then check if the device holding the root partition is on your HD: ls -l /dev/disk/by-id/ata-* lrwxrwxrwx 1 root root 10 Nov 27 10:46 /dev/disk/by-id/ata-xxxxx-part9 -> ../../sda9 where xxxxx is your drive type and ID. This indicates that the root partition is on xxxxx disk. Practically if you have only one HD installed it should be /dev/sda and its partitions should be /dev/sda1 /dev/sda2 etc. Check if you have grub2 directory and files: ls -l /boot/grub2 and the output list has a "grub.cfg" file. Become root user: su - Then as root user run: grub2-install /dev/sda This should install grub2 to the MBR of the HD. Then try to reboot the system (not the rescue disk you used) to see if BIOS can load GRUB2. Report back what is the result of the above. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 24/11/2018 16.03, 712@vivaldi.net wrote:
Hello Carlos and all,
Alas, still no self-booting Leap 15 here...
On 2018-11-22 23:32, Carlos E. R. wrote:
I would try something. One, make sure that the bios is set to boot on legacy mode, not EFI. Although I think if the computer is old, there will be no chance of EFI anyway.
It is set to Legacy Boot only.
Then, on YaST, load the boot module, and select:
store default boot sector on MBR grub is on "/" partition, not on MBR
After I tried above, the YaST boot module shut down with an error message and became inaccessible. There were instructions to file a bug report, but I haven't done that.
:-(
Instead, I reinstalled Leap 15 yet another time. It still won't boot.
[X] Boot from boot partition [X] Write generic boot code to MBR
Bootloader is Grub2.
Is below screenshot what you mean by above instructions?
https://i.postimg.cc/NFRz0RmQ/Screenshot-from-2018-11-24-15-47-59.png
(Using these settings Leap 15 won't boot.)
I think you also need "boot from partition", which is another wording for my "boot from boot partition" above. You can do that on the install screen if yast crashes on the already installed system. An alternative is to go the other way: set boot to pure UEFI instead of Legacy, and install again... Guessing that the bios is buggy (and that Mint knows how to handle it). If you do install mint again, you could run the bootinfo script and post it, so that we find out how it does it. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Hello Carlos and Istvan, Many thanks for taking the time to reply so extensively and my apologies for my late reply. On 2018-11-27 22:04, Carlos E. R. wrote:
An alternative is to go the other way: set boot to pure UEFI instead of Legacy, and install again... Guessing that the bios is buggy (and that Mint knows how to handle it).
The above did the trick! Setting boot to pure UEFI in the BIOS, *before* starting the installation. In all my failed attempts to get the laptop booting from HD, I tinkered with the boot settings *after* the installation. I am relieved that I can continue using SUSE, which is my favorite distribution :-) Regards, Fritz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/12/2018 17.00, 712@vivaldi.net wrote:
Hello Carlos and Istvan,
Many thanks for taking the time to reply so extensively and my apologies for my late reply.
On 2018-11-27 22:04, Carlos E. R. wrote:
An alternative is to go the other way: set boot to pure UEFI instead of Legacy, and install again... Guessing that the bios is buggy (and that Mint knows how to handle it).
The above did the trick! Setting boot to pure UEFI in the BIOS, *before* starting the installation. In all my failed attempts to get the laptop booting from HD, I tinkered with the boot settings *after* the installation.
I am relieved that I can continue using SUSE, which is my favorite distribution :-)
Welcome! :-)) Yes, you have to change the BIOS settings before installation, so that the install program sees them and adjusts. Specially regarding boot, it is very different on UEFI or BIOS. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (9)
-
712＠vivaldi.net -
Carlos E. R. -
Felix Miata -
Istvan Gabor -
jdd＠dodin.org -
Knurpht-openSUSE -
Liam Proven -
Patrick Shanahan -
stakanov