13:59 debianusr81: I don't know if you remember me and my issue, but in desperation over not having the money to buy new hardware, I went looking online and found something that sounded promising. However...
13:59 debianusr81: ... I did `sudo nano /etc/default/grub` and changed `GRUB_CMDLINE_LINUX_DEFAULT="quiet"` into `GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"`, but after rebooting, I'm still getting the same stupid nonsense flooding `sudo dmesg`: "device [1002:1478] error status/mask=00000080/00002000 ... [ 7] BadDLLP ... pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:01:00.0 ... pcieport 0000:01:00.0: PCIe Bus Error:
13:59 debianusr81: severity=Corrected, type=Data Link Layer, (Receiver ID)"
14:01 debianusr81: So I guess it must really be a hardware issue... which really sucks. But is also a relief in a way, because my Linux experience has been quite bad and now I strongly suspect that a whole bunch of those errors were really due to the hardware.
14:59 Venemo: debianusr81: is it any better under windows?
15:19 debianusr81: Venemo: It's been quite some time since I last ran it now, but I do remember it being somewhat underwhelming on there too performance-wise, yes.
15:19 debianusr81: (Windows 10)
15:20 debianusr81: Actually, I last ran Windows 11. It's what made me finally switch to Linux.
15:20 debianusr81: (After I'd been putting it off for so long, Microsoft decided to make it impossible to not switch.)
15:20 Venemo: have you tried to put your graphics card into the other PCIe slot?
15:20 debianusr81: Venemo: Yes, but it's physically prevented from going all the way in (at least the left part of the card), so I had to abort that attempt.
15:21 Venemo: huh? what is preventing it?
15:21 debianusr81: I also removed the cable which I thought was blocking it (front audio), but it didn't make a difference.
15:21 debianusr81: It just wouldn't go all the way into the secondary (lowest) PCIEx16 slot.
15:22 debianusr81: I've had similar issues in the past with some cards just not fitting with the motherboard/chassis.
15:32 Venemo: heh
15:32 Venemo: well, can you take it out of the chassis and plug it in that way?
15:34 debianusr81: Venemo: I suppose it could be theoretically done, but I'm fearing that I'm damaging the hardware more each time I open it up and it's a major chore...
15:34 Venemo: some of us do it on a weekly basis and our HW hasn't fallen apart yet
15:37 glennk: may be worth re-seating the cpu
16:00 debianusr81: But it's talking about the PCIE slots?
16:03 Venemo: both things are worth a try, independently of each other
16:03 glennk: think for a moment where those pcie wires go to...
17:03 Remco: debianusr81: You could also try the card in a different system. If you get yourself a bootable USB you can reproduce it on your system first so you know it's not the software
18:06 _ds_: debianusr81, did you run “update-grub” (a.k.a. grub-mkconfig) after editing /etc/default/grub?
20:03 debianusr81: Remco: Sadly I have no other computer. Which is another reason why I really should get a whole separate new one so I have redundancy.
20:04 debianusr81: _ds_: No, I did not. Didn't know I was supposed to do that!
20:04 debianusr81: _ds_: They left that little "detail" out on Stack Exchange, it seems.
20:04 debianusr81: Will have to try that.
20:08 debianusr81: _ds_: Does merely running `sudo grub-mkconfig` do the trick? It outputted a bunch of stuff on the screen, but judging by the manpage, it almost seems like I have to actively specify the output file? Or did it "do its thing" from just running the command with no arguments?
20:11 debianusr81: Seems like `sudo update-grub` is NOT simply an alias to `sudo grub-mkconfig`, and it seems to be the command to run here. But still not fully sure.
20:15 _ds_: Looks like “update-grub” runs “grub-mkconfig -o /boot/grub/grub.cfg” with whatever other parameters you pass.
20:16 debianusr81: Yeah, I checked that .cfg file and verified that my extra stuff had been added.
20:17 debianusr81: I should probably not even start asking about why we don't edit that .cfg file directly...
20:17 debianusr81: It will be very interesting tomorrow (it's late now) to see if the next boot this problem is gone. It would be a miracle if so.
20:17 debianusr81: (If it even boots up at all; you never know when touching scary parts of the system like this.)
20:52 Ristovski: heh, they are only scary the first time you tinker with them
21:05 debianusr81: Well, I'll (hopefully) be able to get back here tomorrow to report on what happened.
21:05 debianusr81: I bet you're all excited for that!