Bsrgvty

Daily scratch org signup limit reached - Workaround or extension possible?

Is "那些你很冒險的夢" a common expression or just a song title?

What does this "ICAgICAg…" mean in public key certificates and messages?

Life insurance as a lottery ticket

Learn university maths or train for high school competitions: which is better?

Was refused in UK, should I replace my passport?

Character Development - Robert Baratheon

QGIS 3.4 Python script output to console doesn't update beyond first page

Stack Exchange Answerer

Smoke coming out of my light

One of my friends deposited 42 pounds that he borrowed into my account. Will it affect the processing of my UK visa application?

packet routing between subnets on same vlan

Are "terminal block" style junction boxes allowed in the US?

How to verify if router firmware is legitimate

What is a short code for generating this matrix in R?

How much can I change a NY cheesecakes recipe?

Feasible explanation to the continued existence of dangerous magical creatures in a modern setting

60's or older story about two kinds of mutant telepaths

Am I being exploited by my supervisor?

What counts as on- or off-route outdoors?

Germany's Ladenschlussgesetz in comparison to a debatable law in Israel

If thermodynamics says entropy always increases, how can the universe end in heat death?

Can one get into trouble if one doesn't show up at the gate 30 minutes before departure (or whatever time window the boarding pass is indicating)?

RAW, can a 3rd level sword-and-board eldritch knight usefully cast Absorb Elements?

Booting Ubuntu from USB drive on MSI motherboard — EVERYTHING fails

Why does Ubuntu boot from flash with the screen turned off?Trouble booting into Ubuntu with UEFIUbuntu live USB won't start with CSM disabledUSB not shown in UEFI boot option18.04: After failed start of ubuntu live system (from DVD) BIOS can no longer be opened with F11

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

24

4

I just built a new system with MSI 5700 Gaming Edge Wifi motherboard (with click bios), Ryzen 7 CPU and Radeon 5 GPU and Samsung M.2 SSD.

I made a bootable Ubuntu image with UNetbootin and confirmed that it works fine on my current computer. When I try to boot from it on the new system I initially get the error:

Couldn't get size: 0x800000000000000e
MODSIGN: Couldn't get UEFI db list
Couldn't get size: 0x800000000000000e

and then it gets stuck in the purple Ubuntu loading screen forever.

When I edit the GRUB entry and remove quiet splash and add nomodest I get the following scroll of messages (it goes way off the page but scrolls faster than I can read).

I'm assuming this is all caused by one problem (blocked by a certain hardware thing?) but I have no idea what it is or how to find out. I followed all the solutions I could find for the "UEFI db list" error and nothing helped. I have secure boot disabled (it was disabled by default). I tried switching between UEFI and CSM but that didn't change it.

What are the next steps I can take to diagnose this? Or does anyone have a guess what could be the issue?

boot grub2 system-installation uefi

share|improve this question

asked Sep 24 at 17:47

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  What version of Ubuntu are you attempting to run? Have you checked for any bios updates for that motherboard?
  
  – Gordster
  Sep 24 at 17:49
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  I tried 2 different USB drives and two different copies of the ISO, but it boots fine on my laptop so I don't think the installation media is bad. This also happens whether I pick install or try without installing, with or without safe graphics, and it happens whether I boot from the partition or the whole device
  
  – B1CL0PS
  Sep 24 at 17:51
  

  
  
  
  


• 
  
  
  

  
  9
  

  
  
  
  
  
  

  
  
  it looks like the latest bios version is 7C37v14 (Release Date 2019-09-18). Do you have the latest bios?
  
  – Gordster
  Sep 24 at 17:59
  

  
  
  
  


• 
  
  
  

  
  10
  

  
  
  
  
  
  

  
  
  @Gordster Thanks for your help! Updating the BIOS did it (Ubuntu 19.04 btw)
  
  – B1CL0PS
  Sep 24 at 18:09
  

  
  
  
  

add a comment
 | 

24

4

I just built a new system with MSI 5700 Gaming Edge Wifi motherboard (with click bios), Ryzen 7 CPU and Radeon 5 GPU and Samsung M.2 SSD.

I made a bootable Ubuntu image with UNetbootin and confirmed that it works fine on my current computer. When I try to boot from it on the new system I initially get the error:

Couldn't get size: 0x800000000000000e
MODSIGN: Couldn't get UEFI db list
Couldn't get size: 0x800000000000000e

and then it gets stuck in the purple Ubuntu loading screen forever.

When I edit the GRUB entry and remove quiet splash and add nomodest I get the following scroll of messages (it goes way off the page but scrolls faster than I can read).

I'm assuming this is all caused by one problem (blocked by a certain hardware thing?) but I have no idea what it is or how to find out. I followed all the solutions I could find for the "UEFI db list" error and nothing helped. I have secure boot disabled (it was disabled by default). I tried switching between UEFI and CSM but that didn't change it.

What are the next steps I can take to diagnose this? Or does anyone have a guess what could be the issue?

boot grub2 system-installation uefi

share|improve this question

asked Sep 24 at 17:47

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  What version of Ubuntu are you attempting to run? Have you checked for any bios updates for that motherboard?
  
  – Gordster
  Sep 24 at 17:49
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  I tried 2 different USB drives and two different copies of the ISO, but it boots fine on my laptop so I don't think the installation media is bad. This also happens whether I pick install or try without installing, with or without safe graphics, and it happens whether I boot from the partition or the whole device
  
  – B1CL0PS
  Sep 24 at 17:51
  

  
  
  
  


• 
  
  
  

  
  9
  

  
  
  
  
  
  

  
  
  it looks like the latest bios version is 7C37v14 (Release Date 2019-09-18). Do you have the latest bios?
  
  – Gordster
  Sep 24 at 17:59
  

  
  
  
  


• 
  
  
  

  
  10
  

  
  
  
  
  
  

  
  
  @Gordster Thanks for your help! Updating the BIOS did it (Ubuntu 19.04 btw)
  
  – B1CL0PS
  Sep 24 at 18:09
  

  
  
  
  

add a comment
 | 

I just built a new system with MSI 5700 Gaming Edge Wifi motherboard (with click bios), Ryzen 7 CPU and Radeon 5 GPU and Samsung M.2 SSD.

I made a bootable Ubuntu image with UNetbootin and confirmed that it works fine on my current computer. When I try to boot from it on the new system I initially get the error:

Couldn't get size: 0x800000000000000e
MODSIGN: Couldn't get UEFI db list
Couldn't get size: 0x800000000000000e

and then it gets stuck in the purple Ubuntu loading screen forever.

When I edit the GRUB entry and remove quiet splash and add nomodest I get the following scroll of messages (it goes way off the page but scrolls faster than I can read).

I'm assuming this is all caused by one problem (blocked by a certain hardware thing?) but I have no idea what it is or how to find out. I followed all the solutions I could find for the "UEFI db list" error and nothing helped. I have secure boot disabled (it was disabled by default). I tried switching between UEFI and CSM but that didn't change it.

What are the next steps I can take to diagnose this? Or does anyone have a guess what could be the issue?

boot grub2 system-installation uefi

share|improve this question

asked Sep 24 at 17:47

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

Couldn't get size: 0x800000000000000e
MODSIGN: Couldn't get UEFI db list
Couldn't get size: 0x800000000000000e

share|improve this question

asked Sep 24 at 17:47

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

share|improve this question

asked Sep 24 at 17:47

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

asked Sep 24 at 17:47

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

asked Sep 24 at 17:47

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

3 Answers
3

active

oldest

votes

61

It looks like the latest bios version is 7C37v14 (Release Date 2019-09-18). Update your bios to this version in order to get the latest Linux support.

With these processors and motherboards being so new it is a good idea to pay attention to the latest bios releases.

share|improve this answer

edited Sep 24 at 19:54

answered Sep 24 at 18:20

GordsterGordster

1,02644 silver badges1313 bronze badges

add a comment
 | 

17

Updating the BIOS to version 7C37v14 fixed the issue!

share|improve this answer

answered Sep 24 at 18:10

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

• 
  
  
  

  
  21
  

  
  
  
  
  
  

  
  
  Great that it worked for you. But please, don't just post this as another answer, instead accept the answer by Gordster by clicking on the tickmark below the votes. If you don't, the question will remain as "unanswered" in the system.
  
  – Gerald Schneider
  Sep 25 at 10:03
  

  
  
  
  


• 
  
  
  

  
  20
  

  
  
  
  
  
  

  
  
  @GeraldSchneider This answer was posted 10 minutes before the Gordster’s answer actually. However, since the advice came from Gordster’s comment, OP should really accept Gordster’s answer and remove their own.
  
  – Melebius
  Sep 25 at 12:40
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  annoyingly, StackExchange makes you wait 2 days before accepting your answer. But it's done now.
  
  – B1CL0PS
  Sep 25 at 20:14
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  You have to wait 2 days before accepting your own answer only, see askubuntu.com/help/self-answer. You can accept anyone else’s answer sooner.
  
  – Melebius
  Sep 26 at 6:28
  

  
  
  
  

add a comment
 | 

3

Modern distros like Ubuntu can have live USB disks made with dd. If even go so far as to say this is a superior way of doing it.

As root:

dd if=/path/to/iso.iso of=/dev/sdb 

Replace sdb with whatever your USB device is showing up as.

On mobile, but IIRC you can check with lsusb.

Edit: I thought this was a bug with unetbootin. It can be iffy sometimes.

share|improve this answer

edited Sep 25 at 19:14

Simon Sudler

2,2241010 silver badges2222 bronze badges

answered Sep 25 at 19:04

PeePeePhDPeePeePhD

3111 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Or just cat /path/to/iso > /dev/sdb ;)
  
  – marcelm
  Sep 25 at 23:04
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I've always had success with DD over other tools. I would have recreated the usb as well if it wasn't for the fact that it was a new motherboard/processor
  
  – Gordster
  Sep 26 at 16:10
  

  
  
  
  

add a comment
 | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1176391%2fbooting-ubuntu-from-usb-drive-on-msi-motherboard-everything-fails%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

61

It looks like the latest bios version is 7C37v14 (Release Date 2019-09-18). Update your bios to this version in order to get the latest Linux support.

With these processors and motherboards being so new it is a good idea to pay attention to the latest bios releases.

share|improve this answer

edited Sep 24 at 19:54

answered Sep 24 at 18:20

GordsterGordster

1,02644 silver badges1313 bronze badges

add a comment
 | 

61

It looks like the latest bios version is 7C37v14 (Release Date 2019-09-18). Update your bios to this version in order to get the latest Linux support.

With these processors and motherboards being so new it is a good idea to pay attention to the latest bios releases.

share|improve this answer

edited Sep 24 at 19:54

answered Sep 24 at 18:20

GordsterGordster

1,02644 silver badges1313 bronze badges

add a comment
 | 

It looks like the latest bios version is 7C37v14 (Release Date 2019-09-18). Update your bios to this version in order to get the latest Linux support.

With these processors and motherboards being so new it is a good idea to pay attention to the latest bios releases.

share|improve this answer

edited Sep 24 at 19:54

answered Sep 24 at 18:20

GordsterGordster

1,02644 silver badges1313 bronze badges

share|improve this answer

edited Sep 24 at 19:54

answered Sep 24 at 18:20

GordsterGordster

1,02644 silver badges1313 bronze badges

answered Sep 24 at 18:20

GordsterGordster

1,02644 silver badges1313 bronze badges

answered Sep 24 at 18:20

GordsterGordster

1,02644 silver badges1313 bronze badges

17

Updating the BIOS to version 7C37v14 fixed the issue!

share|improve this answer

answered Sep 24 at 18:10

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

• 
  
  
  

  
  21
  

  
  
  
  
  
  

  
  
  Great that it worked for you. But please, don't just post this as another answer, instead accept the answer by Gordster by clicking on the tickmark below the votes. If you don't, the question will remain as "unanswered" in the system.
  
  – Gerald Schneider
  Sep 25 at 10:03
  

  
  
  
  


• 
  
  
  

  
  20
  

  
  
  
  
  
  

  
  
  @GeraldSchneider This answer was posted 10 minutes before the Gordster’s answer actually. However, since the advice came from Gordster’s comment, OP should really accept Gordster’s answer and remove their own.
  
  – Melebius
  Sep 25 at 12:40
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  annoyingly, StackExchange makes you wait 2 days before accepting your answer. But it's done now.
  
  – B1CL0PS
  Sep 25 at 20:14
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  You have to wait 2 days before accepting your own answer only, see askubuntu.com/help/self-answer. You can accept anyone else’s answer sooner.
  
  – Melebius
  Sep 26 at 6:28
  

  
  
  
  

add a comment
 | 

17

Updating the BIOS to version 7C37v14 fixed the issue!

share|improve this answer

answered Sep 24 at 18:10

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

• 
  
  
  

  
  21
  

  
  
  
  
  
  

  
  
  Great that it worked for you. But please, don't just post this as another answer, instead accept the answer by Gordster by clicking on the tickmark below the votes. If you don't, the question will remain as "unanswered" in the system.
  
  – Gerald Schneider
  Sep 25 at 10:03
  

  
  
  
  


• 
  
  
  

  
  20
  

  
  
  
  
  
  

  
  
  @GeraldSchneider This answer was posted 10 minutes before the Gordster’s answer actually. However, since the advice came from Gordster’s comment, OP should really accept Gordster’s answer and remove their own.
  
  – Melebius
  Sep 25 at 12:40
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  annoyingly, StackExchange makes you wait 2 days before accepting your answer. But it's done now.
  
  – B1CL0PS
  Sep 25 at 20:14
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  You have to wait 2 days before accepting your own answer only, see askubuntu.com/help/self-answer. You can accept anyone else’s answer sooner.
  
  – Melebius
  Sep 26 at 6:28
  

  
  
  
  

add a comment
 | 

Updating the BIOS to version 7C37v14 fixed the issue!

share|improve this answer

answered Sep 24 at 18:10

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

share|improve this answer

answered Sep 24 at 18:10

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

answered Sep 24 at 18:10

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

answered Sep 24 at 18:10

B1CL0PSB1CL0PS

51133 silver badges99 bronze badges

3

Modern distros like Ubuntu can have live USB disks made with dd. If even go so far as to say this is a superior way of doing it.

As root:

dd if=/path/to/iso.iso of=/dev/sdb 

Replace sdb with whatever your USB device is showing up as.

On mobile, but IIRC you can check with lsusb.

Edit: I thought this was a bug with unetbootin. It can be iffy sometimes.

share|improve this answer

edited Sep 25 at 19:14

Simon Sudler

2,2241010 silver badges2222 bronze badges

answered Sep 25 at 19:04

PeePeePhDPeePeePhD

3111 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Or just cat /path/to/iso > /dev/sdb ;)
  
  – marcelm
  Sep 25 at 23:04
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I've always had success with DD over other tools. I would have recreated the usb as well if it wasn't for the fact that it was a new motherboard/processor
  
  – Gordster
  Sep 26 at 16:10
  

  
  
  
  

add a comment
 | 

3

Modern distros like Ubuntu can have live USB disks made with dd. If even go so far as to say this is a superior way of doing it.

As root:

dd if=/path/to/iso.iso of=/dev/sdb 

Replace sdb with whatever your USB device is showing up as.

On mobile, but IIRC you can check with lsusb.

Edit: I thought this was a bug with unetbootin. It can be iffy sometimes.

share|improve this answer

edited Sep 25 at 19:14

Simon Sudler

2,2241010 silver badges2222 bronze badges

answered Sep 25 at 19:04

PeePeePhDPeePeePhD

3111 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Or just cat /path/to/iso > /dev/sdb ;)
  
  – marcelm
  Sep 25 at 23:04
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I've always had success with DD over other tools. I would have recreated the usb as well if it wasn't for the fact that it was a new motherboard/processor
  
  – Gordster
  Sep 26 at 16:10
  

  
  
  
  

add a comment
 | 

Modern distros like Ubuntu can have live USB disks made with dd. If even go so far as to say this is a superior way of doing it.

As root:

dd if=/path/to/iso.iso of=/dev/sdb 

Replace sdb with whatever your USB device is showing up as.

On mobile, but IIRC you can check with lsusb.

Edit: I thought this was a bug with unetbootin. It can be iffy sometimes.

share|improve this answer

edited Sep 25 at 19:14

Simon Sudler

2,2241010 silver badges2222 bronze badges

answered Sep 25 at 19:04

PeePeePhDPeePeePhD

3111 bronze badge

dd if=/path/to/iso.iso of=/dev/sdb 

share|improve this answer

edited Sep 25 at 19:14

Simon Sudler

2,2241010 silver badges2222 bronze badges

answered Sep 25 at 19:04

PeePeePhDPeePeePhD

3111 bronze badge

edited Sep 25 at 19:14

Simon Sudler

2,2241010 silver badges2222 bronze badges

edited Sep 25 at 19:14

Simon Sudler

2,2241010 silver badges2222 bronze badges

answered Sep 25 at 19:04

PeePeePhDPeePeePhD

3111 bronze badge

answered Sep 25 at 19:04

PeePeePhDPeePeePhD

3111 bronze badge