Bug 2032011 - Shim error - not able to install on Fujitsu Lifebook T938
Summary: Shim error - not able to install on Fujitsu Lifebook T938
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: shim
Version: 35
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-13 21:01 UTC by Martin
Modified: 2024-01-24 10:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 16:06:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin 2021-12-13 21:01:08 UTC
Description of problem:
I'm not able to install Fedora 35 (and 34 - same behavior) on a Fujitsu Lifebook T938.
Booting of livesystem fails with following error:
set_second_stage() failed: Invalid Parameter
Something has gone seriously wrong: shim_init() failed: Invalid Parameter

Also tried Fedora 34 - same error.

Installation of latest manajaro distri is possible without error, so hardware is fine.

Regarding fedora I didn't find any clue or similar bug reports, but there seems to be a similar report in debian (https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1823125.html)


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Boot from live stick (stick is ok, booting on a Lifebook T904 without any problem)
2. Error message appears (see description)
3. After a few seconds, Notebook turns off

Actual results:
Booting Live system failed

Expected results:
Live System should boot

Additional info:

Comment 1 jdw 2022-02-03 19:30:03 UTC
I just want to report that the same issue occurs on a Fujitsu Lifebook E5510.
Over at the Debian mailing list it seems to be suggested that an easy fix to this bug is available.

Comment 2 glavina.nikola5 2022-02-22 15:27:23 UTC
I can also confirm that the same problem affects Fujitsu Lifebook A3510.
It seems that this problem is common on Fujitsu laptops.

Comment 3 jdw 2022-03-30 23:43:35 UTC
I am not sure whether I should make a comment here or file a new bug for Fedora 36, but I want to report that the issue still occurs with the recently released beta version of Fedora 36.

Comment 4 Botond BALÁZS 2022-06-22 13:42:39 UTC
I want to report that this bug still affects Fedora 36 on a Fujitsu Lifebook E548.

A workaround I found is to use [Ventoy](https://www.ventoy.net/en/index.html) to create a bootable USB drive and copy the ISO to it. I could install Fedora this way and it works flawlessly.

Comment 5 Robbie Harwood 2022-09-01 20:06:25 UTC
If it's in fact the bug you linked, this should be fixed in 15.6.  Can you confirm that?

Comment 6 Martin 2022-10-09 14:08:09 UTC
Not working with actual fedora 36 workstation live ISO (https://download.fedoraproject.org/pub/fedora/linux/releases/36/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-36-1.5.iso) --> same error as initially reported 

Tested fedora 37 workstation beta (https://download.fedoraproject.org/pub/fedora/linux/releases/test/37_Beta/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-37_Beta-1.5.iso)
--> booting into live system succeeded!

Therefore I can confirm that I can boot a fedora 37 BETA workstation (downloaded from the mentioned link above) using a usb stick into a live system on a Fujitsu Lifebook T938. Didn't test to install to harddrive. Fedora 36 workstation still doesn't work (at least the version provided through the official download).

Comment 7 Ben Cotton 2022-11-29 17:29:29 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Ben Cotton 2022-12-13 16:06:21 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 Red Hat Bugzilla 2023-09-18 04:29:15 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days

Comment 10 Sean 2024-01-24 10:05:59 UTC
I am getting the same error installing Nobara 39 on a Fujitsu Lifebook P728. Ventoy finally got the live image to go through, but once it's actually been installed it's back to the same old song and dance.


Note You need to log in before you can comment on or make changes to this bug.