Solus OS Intallation: PCIe Errors?

[Rilvin2]

I've spent the past few days trying out various different Linux distros. I've been installing them alongside Windows 10 on my ASUS Zenbook Pro (UX550VE). Recently, I uninstalled Kali so that I could install the Solus OS. I deleted the partition Kali was on, this caused an issue with GRUB going into rescue mode on startup. I fixed this (I think) by removing the boot option from the BIOS. Now trying to install Solus, I run into a PICe BUS error when I try to boot from the USB drive that has the Solus installer on it. 

 

1.871984] pcieport 0000:00:1c.0: AER:	[12] Timeout
1.872523] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer,
(Reciever ID)
1.873899] pcieport 0000:00:1c.0: AER: device [8086:a110] error status/mask=00000001/00002000
1.874587] piceport 0000:00:1c.0: AER:	[ 0] RxErr
1.875603] pcieport 0000:00:1c.0: AER:	[ 0] Rollover
1.879305] pcieport 0000:00:1c.0: AER:	[12] Timeout
1.880075] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=corrected type=Data Link Layer,

There were a lot more errors displayed beneath this as well, almost identical but for a "Transmitter ID".

Luckily, Windows is behaving completely fine.

 

BIOS Settings:

Secure Boot: Disabled

CSM: Disabled

Fastboot: Disabled

 

System Specifications: 

CPU: i7 7700HQ

Chipset: HM175 Express

GPU: GTX 1050M

SSD: 970 EVO M.2

 

 

[Sauron]

Those errors can most likely be safely ignored. You can disable them by setting the kernel parameters detailed here. I'm not sure if the solus installation image allows you to customize kernel parameters before booting though, which would be a problem because changes are not persistent across reboots in the live image.

[Rilvin2]

On 4/13/2020 at 4:04 AM, Sauron said:

Those errors can most likely be safely ignored. You can disable them by setting the kernel parameters detailed here. I'm not sure if the solus installation image allows you to customize kernel parameters before booting though, which would be a problem because changes are not persistent across reboots in the live image.

That does seem to be an issue. I get these errors as soon as I select the boot option from my BIOS menu. Is there anyway that I can change these parameters on the live USB with a text editor or something? I know very little about Linux systems or their structure. 

[Sauron]

6 minutes ago, Rilvin2 said:

That does seem to be an issue. I get these errors as soon as I select the boot option from my BIOS menu. Is there anyway that I can change these parameters on the live USB with a text editor or something? I know very little about Linux systems or their structure. 

You'd need another Linux OS to read the file system but in theory yes, you could modify grub's configuration.

[sp331yi]

Did you try loggin in as Root and issuing the

update-grub

command?