Upon further inspection in bios, this port is set (by manufacturer) to topology x4 and has AER + PME SCI enabled. Most others are x1 and don’t have AER enabled. If it’s not NVME, SATA, or GPU, what sort of device could use 4 lanes?
I don’t understand what PME SCI is, or how to determine when it should be enabled. My first instinct was to entirely disable power management on this link, but that had no effect. I’m not even really sure there’s any device there. TPM is disabled, so maybe that’s it, but TPM shouldn’t be a 4 lane hotplug device.
Is there a general BIOS guide anywhere that says what these type of settings are meant for beyond “Enable/Disable <Name of thing we don’t explain what it is or does>”?
@tastaturri You didn’t say which video card and which laptop you have. There are different types of video switching. Some computers can use both cards at once, some can’t. Some have a specific output that can’t be used at the same time as the laptop screen, but I think those are pretty rare. Also, are you using a dock and are you sure you have all the optimus stuff on in BIOS? I have a Dell that goes either-or with internal screen and side VGA port when it’s docked, solution for that is plug into the dock instead.
The type of external monitor might matter too. I had a Geforce 560M which needed a bunch of xrandr setup to use a 2560x1440 Asus monitor and XFCE was always a bit glitchy with hotplugging, though it mostly worked after I went into the configuration files and defined settings for devices and screens. It had previously worked just fine with some cheap korean monitor at the same resolution.
Once I had the display and screen configuration set, XFCE would accept hotplugging, but I’d still have to go into display settings and enable the monitor (or make sure it’s not set to clone) every time I plugged it in. As a warning, don’t set the laptop screen as “not used” unless you need to, or you do some extra setup that I couldn’t figure out. When you unplug the monitor, then you’re still “not using” your only screen, the laptop, and when you plug it back in, XFCE will ask you which screens you’d like to use, but not turn either of them on so you can make the choice. The way I dealt with it was to use the lid switch only to turn off the laptop screen, and when I closed it then reopened it, it would be enabled again.
Your card is probably newer, so I’ll also mention other issues I had with XFCE as best I can remember: Forgetting to restart the display manager will get you, also make sure you’re set to use either a large enough screen or two separate screens. If you position the 2nd display outside XFCE’s screen area, it won’t work. The whole display/screen thing is a bit counterintuitive for me, so I hope I didn’t say that backwards. The important thing to know is you need to configure both.
I’ve used Arch, Manjaro, and now just installed Antergos. I also have another computer using GalliumOS (Ubuntu-based). “Lightweight” is not a concern for me, I just don’t want to faff about with docks and floating icons.
I have installed Gentoo, it’s really not noticeably faster for average use and you can always compile your own software if you want anyway.
Manjaro is great, but it has its own little quirks, like putting configuration files in slightly different places, which is really annoying when you need to fix something and get back to work. Some of their distro-specific packages would occasionally break everything on upgrade, and minor config issues were semi-common with AUR packages.
The only very serious issues I had in Manjaro, besides things like graphics and once or twice other devices breaking after updates, were entirely with Thunar, and it behaves the same on GalliumOS. Mostly file transfer and hotplug/eject issues. I did have a number of minor, annoying, time-consuming issues where I couldn’t rely on the Arch documentation because Manjaro wanted to be different, though I can’t remember specific ones at the moment.
I only used XFCE, so I can’t say much about the other desktops. I’m trying Openbox on Antergos now, it seems OK so far.
I like Antergos so far. It didn’t do anything weird with the install as far as I can tell, and I was probably going to install most of the stuff cnchi did anyway. Cnchi let me install to a fairly unusual drive configuration and it worked 99%, I just had to modify a little bit of boot stuff. There’s no way Calamares would have done it correctly.
Hi, I’ve just installed Antergos on a new laptop and I’m stuck with some errors during boot.
It’s a Clevo P775, 8700K processor, NVidia 1070M, and the only special configuration I’ve done outside cnchi is to set up LVM on LUKs on 4-disk RAID10 using two Samsung 970 EVO drives and two Samsung 850 evo 2.5" drives. It’s set up for EFI boot and an encrypted /boot on the RAID10. I’m using the unlocked Prema BIOS but I haven’t messed with PCIE settings. CSM is off, and I’m in AHCI mode so linux can see the nvme drives.
During boot I get two errors:
kernel: sdhci-pci 0000:6f:00.0: SDHCI controller found [10ec:5250] (rev 1) kernel: sdhci-pci 0000:6f:00.0: enabling device (0000 -> 0002) kernel: mmc0: Unknown controller version (3). You may experience problems. kernel: mmc0: SDHCI controller on PCI [0000:6f:00.0] using ADMA
And this PCIE bus error below that I can’t figure out. It references a root port, but I don’t know what’s on it.
kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) kernel: pcieport 0000:00:1c.0: device [8086:a290] error status/mask=00000001/00002000 kernel: pcieport 0000:00:1c.0: [ 0] Receiver Error (First) kernel: pcieport 0000:04:00.0: Refused to change power state, currently in D3
dmesg |grep failed:
[ 0.722675] pci 0000:04:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref] [ 0.722680] pci 0000:04:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref] [ 22.502050] thermal thermal_zone2: failed to read out thermal zone (-61)
There are plenty of instructions online about how to mute the errors, but I would rather figure out what the issue is here.