Pop OS doesn't boot up because of pci-e bus error
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
So, today I downloaded the iso file of the new Pop OS 18.04 in order to try it out.
However, after I created a bootable usb, I opened my laptop, and chose to boot from usb, and suddenly I got a kind of loop that says "PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)"
I got this error in the past, and I still get it every time I boot up Ubuntu, or Ubuntu based distros, but it stops after a moment. In this case, it doesn't.
In theory, I could fix this problem, by adding "pci=noaer" to the grub file, but I can't do the same thing here, because I can't install the OS so I don't even have a grub, or a way to access the terminal.
Is there any way I can fix this problem? Or maybe find the grub file on the USB?
EDIT: I am using a 6th generation intel cpu+hd graphics card. 8gb of ram, and 1TB of storage.
I have already asked a question about this error, and I have seen many others ask the same thing, so, adding the line above will fix the problem.
Also, my laptop uses BIOS and not UEFI
Thanks in advance 😄
usb grub pci
asked Apr 29 at 18:01
user6516763
62
 |Â
show 1 more comment
up vote
1
down vote
favorite
So, today I downloaded the iso file of the new Pop OS 18.04 in order to try it out.
However, after I created a bootable usb, I opened my laptop, and chose to boot from usb, and suddenly I got a kind of loop that says "PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)"
I got this error in the past, and I still get it every time I boot up Ubuntu, or Ubuntu based distros, but it stops after a moment. In this case, it doesn't.
In theory, I could fix this problem, by adding "pci=noaer" to the grub file, but I can't do the same thing here, because I can't install the OS so I don't even have a grub, or a way to access the terminal.
Is there any way I can fix this problem? Or maybe find the grub file on the USB?
EDIT: I am using a 6th generation intel cpu+hd graphics card. 8gb of ram, and 1TB of storage.
I have already asked a question about this error, and I have seen many others ask the same thing, so, adding the line above will fix the problem.
Also, my laptop uses BIOS and not UEFI
Thanks in advance 😄
usb grub pci
asked Apr 29 at 18:01
user6516763
62
The error is probably unrelated to the problem. The problem seems to be the live session either not booting at all or not booting graphically. First thing first, please edit the question and add hardware specs, namely graphics. Is it UEFI or BIOS?
– user252181
Apr 29 at 20:01
@MichaelBay I added the information you asked for. If you want the link to the other question I asked long time ago, I can add it to the question.
– user6516763
Apr 29 at 20:51
Thank you for the edit. Well, the absence of an high-end Nvidia (or AMD) graphics rules out many things. And it's great you're using UEFI mode (as it should be) because it's very easy to add boot parameters just by editing the "Try [some OS]..." entry by pressing "e" to edit. Your desired boot parameter can then be written in the same line where "quiet splash" is.
– user252181
Apr 29 at 21:16
@MichaelBay Apparently I was wrong. Sorry. I have two laptops, and the one who has this bug uses BIOS and not UEFI. Is there anything I can do to fix this problem?
– user6516763
Apr 30 at 18:18
I found the solution here
– user3405291
Jun 11 at 5:35
 |Â
show 1 more comment
up vote
1
down vote
favorite
up vote
1
down vote
favorite
So, today I downloaded the iso file of the new Pop OS 18.04 in order to try it out.
However, after I created a bootable usb, I opened my laptop, and chose to boot from usb, and suddenly I got a kind of loop that says "PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)"
I got this error in the past, and I still get it every time I boot up Ubuntu, or Ubuntu based distros, but it stops after a moment. In this case, it doesn't.
In theory, I could fix this problem, by adding "pci=noaer" to the grub file, but I can't do the same thing here, because I can't install the OS so I don't even have a grub, or a way to access the terminal.
Is there any way I can fix this problem? Or maybe find the grub file on the USB?
EDIT: I am using a 6th generation intel cpu+hd graphics card. 8gb of ram, and 1TB of storage.
I have already asked a question about this error, and I have seen many others ask the same thing, so, adding the line above will fix the problem.
Also, my laptop uses BIOS and not UEFI
Thanks in advance 😄
usb grub pci
asked Apr 29 at 18:01
user6516763
62
So, today I downloaded the iso file of the new Pop OS 18.04 in order to try it out.
However, after I created a bootable usb, I opened my laptop, and chose to boot from usb, and suddenly I got a kind of loop that says "PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)"
I got this error in the past, and I still get it every time I boot up Ubuntu, or Ubuntu based distros, but it stops after a moment. In this case, it doesn't.
In theory, I could fix this problem, by adding "pci=noaer" to the grub file, but I can't do the same thing here, because I can't install the OS so I don't even have a grub, or a way to access the terminal.
Is there any way I can fix this problem? Or maybe find the grub file on the USB?
EDIT: I am using a 6th generation intel cpu+hd graphics card. 8gb of ram, and 1TB of storage.
I have already asked a question about this error, and I have seen many others ask the same thing, so, adding the line above will fix the problem.
Also, my laptop uses BIOS and not UEFI
Thanks in advance 😄
usb grub pci
asked Apr 29 at 18:01
user6516763
62
edited Apr 30 at 18:17
asked Apr 29 at 18:01
user6516763
62
asked Apr 29 at 18:01
user6516763
62
asked Apr 29 at 18:01
user6516763
62
62
The error is probably unrelated to the problem. The problem seems to be the live session either not booting at all or not booting graphically. First thing first, please edit the question and add hardware specs, namely graphics. Is it UEFI or BIOS?
– user252181
Apr 29 at 20:01
@MichaelBay I added the information you asked for. If you want the link to the other question I asked long time ago, I can add it to the question.
– user6516763
Apr 29 at 20:51
Thank you for the edit. Well, the absence of an high-end Nvidia (or AMD) graphics rules out many things. And it's great you're using UEFI mode (as it should be) because it's very easy to add boot parameters just by editing the "Try [some OS]..." entry by pressing "e" to edit. Your desired boot parameter can then be written in the same line where "quiet splash" is.
– user252181
Apr 29 at 21:16
@MichaelBay Apparently I was wrong. Sorry. I have two laptops, and the one who has this bug uses BIOS and not UEFI. Is there anything I can do to fix this problem?
– user6516763
Apr 30 at 18:18
I found the solution here
– user3405291
Jun 11 at 5:35
 |Â
show 1 more comment
The error is probably unrelated to the problem. The problem seems to be the live session either not booting at all or not booting graphically. First thing first, please edit the question and add hardware specs, namely graphics. Is it UEFI or BIOS?
– user252181
Apr 29 at 20:01
@MichaelBay I added the information you asked for. If you want the link to the other question I asked long time ago, I can add it to the question.
– user6516763
Apr 29 at 20:51
Thank you for the edit. Well, the absence of an high-end Nvidia (or AMD) graphics rules out many things. And it's great you're using UEFI mode (as it should be) because it's very easy to add boot parameters just by editing the "Try [some OS]..." entry by pressing "e" to edit. Your desired boot parameter can then be written in the same line where "quiet splash" is.
– user252181
Apr 29 at 21:16
@MichaelBay Apparently I was wrong. Sorry. I have two laptops, and the one who has this bug uses BIOS and not UEFI. Is there anything I can do to fix this problem?
– user6516763
Apr 30 at 18:18
I found the solution here
– user3405291
Jun 11 at 5:35
The error is probably unrelated to the problem. The problem seems to be the live session either not booting at all or not booting graphically. First thing first, please edit the question and add hardware specs, namely graphics. Is it UEFI or BIOS?
– user252181
Apr 29 at 20:01
The error is probably unrelated to the problem. The problem seems to be the live session either not booting at all or not booting graphically. First thing first, please edit the question and add hardware specs, namely graphics. Is it UEFI or BIOS?
– user252181
Apr 29 at 20:01
@MichaelBay I added the information you asked for. If you want the link to the other question I asked long time ago, I can add it to the question.
– user6516763
Apr 29 at 20:51
@MichaelBay I added the information you asked for. If you want the link to the other question I asked long time ago, I can add it to the question.
– user6516763
Apr 29 at 20:51
Thank you for the edit. Well, the absence of an high-end Nvidia (or AMD) graphics rules out many things. And it's great you're using UEFI mode (as it should be) because it's very easy to add boot parameters just by editing the "Try [some OS]..." entry by pressing "e" to edit. Your desired boot parameter can then be written in the same line where "quiet splash" is.
– user252181
Apr 29 at 21:16
Thank you for the edit. Well, the absence of an high-end Nvidia (or AMD) graphics rules out many things. And it's great you're using UEFI mode (as it should be) because it's very easy to add boot parameters just by editing the "Try [some OS]..." entry by pressing "e" to edit. Your desired boot parameter can then be written in the same line where "quiet splash" is.
– user252181
Apr 29 at 21:16
@MichaelBay Apparently I was wrong. Sorry. I have two laptops, and the one who has this bug uses BIOS and not UEFI. Is there anything I can do to fix this problem?
– user6516763
Apr 30 at 18:18
@MichaelBay Apparently I was wrong. Sorry. I have two laptops, and the one who has this bug uses BIOS and not UEFI. Is there anything I can do to fix this problem?
– user6516763
Apr 30 at 18:18
I found the solution here
– user3405291
Jun 11 at 5:35
I found the solution here
– user3405291
Jun 11 at 5:35
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440778%2fpop-os-doesnt-boot-up-because-of-pci-e-bus-error%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
The error is probably unrelated to the problem. The problem seems to be the live session either not booting at all or not booting graphically. First thing first, please edit the question and add hardware specs, namely graphics. Is it UEFI or BIOS?
– user252181
Apr 29 at 20:01
@MichaelBay I added the information you asked for. If you want the link to the other question I asked long time ago, I can add it to the question.
– user6516763
Apr 29 at 20:51
Thank you for the edit. Well, the absence of an high-end Nvidia (or AMD) graphics rules out many things. And it's great you're using UEFI mode (as it should be) because it's very easy to add boot parameters just by editing the "Try [some OS]..." entry by pressing "e" to edit. Your desired boot parameter can then be written in the same line where "quiet splash" is.
– user252181
Apr 29 at 21:16
@MichaelBay Apparently I was wrong. Sorry. I have two laptops, and the one who has this bug uses BIOS and not UEFI. Is there anything I can do to fix this problem?
– user6516763
Apr 30 at 18:18
I found the solution here
– user3405291
Jun 11 at 5:35