Ubuntu
linux package

PCIe Error on install of Ubuntu 20.04

Asked by Dan

I'm trying to install Ubuntu 20.04 on an Asus F541 Laptop

Specs

Intel i3
8GB Ram
1TB HDD

I've disabled secure Boot, Fast Boot and CSM Support via the motherboard. I tried booting the USB stick in both UEFI and BIOS mode and both produce the same error. Each time I tell the installer to wipe the 1TB disk and use the whole drive for Ubuntu. I don't want to dual boot into another OS.

Hitting Ctrl + Alt + F2 shows me a console filled with:

PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) device [8086:9d15] error status/maskl000000001/00002000 [ 0] RxError

I'm now trying the suggestion from this post: https://askubuntu.com/questions/771899/pcie-bus-error-severity-corrected

Has anyone else experienced the same issue? What else can I try to boot into ubuntu?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Solved by:
Dan
Solved:
Last query:
Last reply:

This question was reopened

  • by Dan
Revision history for this message
Dan (bakerdude) said : 		#1

Followed the steps in the linked ask Ubuntu. Posting here the actual step by step.

1. on the GRUB Bootloader press 'e' on the first option
2. Find the line with the flags: `quiet splash`
3. After `splash` add `pci=nomsi'
4. Press `Ctrl+x` to boot. Install should go smooth and not hang,

My question now is what is the consequence of adding this flag and will I need to make this a permanent change to be able to boot and run the OS?

Revision history for this message
Dan (bakerdude) said : 		#2

Install went smooth but when I tried to login the screen froze. Ctrl + Alt + F2 gave the same error as during the install.

I powered off and restarted and was able to log in after selecting Ubuntu on Wayland.

Ctrl + Alt + F2 gave the same message in the console but I was able to still use the desktop to add the boot parameter.

However now the boot takes forever and the error is still present in the console. From what I've read online Wayland also doesn't sound like it will be a great long term solution. (Based on this page: https://askubuntu.com/questions/1138155/ubuntu-on-wayland)

Any advice?

Revision history for this message
Dan (bakerdude) said : 		#3

Sorry for the SPAM but one last update from me.

I actually forgot to run `sudo update-grub` after updating the GRUB file as mentioned above. Everything looks like it works fine now and I don't see the error in the logs.

I would just like to understand what is the consequence of booting with the flag: `pci=nomsi'?

Thanks,
Dan

Revision history for this message
Dan (bakerdude) said : 		#4

Sorry for the SPAM but one last update from me.

I actually forgot to run `sudo update-grub` after updating the GRUB file as mentioned above. Everything looks like it works fine now and I don't see the error in the logs.

I would just like to understand what is the consequence of booting with the flag: `pci=nomsi'?

Thanks,
Dan

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

https://askubuntu.com/questions/1104219/what-does-pci-noaer-or-pci-nomsi-mean

Revision history for this message
Dan (bakerdude) said : 		#6

Thanks but that link doesn't answer my question of what is the consequence of turning off Message Signal Interrupt?

I understand that it turns off the ability of the hardware to send a special interrupt signal to the kernal but I don't know if that means that it's going to disable a feature, or cause some hardware to not work correctly.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#7

Some hardware needs it to work right. All I can say is trial it. Its easy to turn off/on with the boot options

Revision history for this message
Dan (bakerdude) said : 		#8

OK, thanks. I'll trial it and see what happens then. It seems to be running fine for the time being.

Thanks,
Dan