Mattitude

Members
  • Posts

    3
  • Joined

  • Last visited

Mattitude's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I've managed to find a solution by using a different command in the syslinux configuration. append initrd=/bzroot pci=noaer Apparently pci=noaer disables Advanced Error Reporting. Unfortunately its a bit like pulling the bulb behind your check engine light on your car but not sure how else to disable these warnings. There are some other options as well which i might try and see if they also work. pci=noaer or pci=nomsi or pci=nommcon Found this info here: See more details here: And Here: https://askubuntu.com/questions/1104219/what-does-pci-noaer-or-pci-nomsi-mean
  2. Did you manage to resolve this? I'm getting the same thing for my NVME drive as well and it fills the log file in a matter of hours. kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:02:00.0 kernel: nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) kernel: nvme 0000:02:00.0: device [144d:a804] error status/mask=00000001/00006000 kernel: nvme 0000:02:00.0: [ 0] RxErr
  3. Great job on this Docker! Got it up and running easily and getting almost the same hash rate with 1gb pages as i was when mining on this machine with windows. Any possibility of creating a docker for XMRIG-PROXY as well? :-) I have a bunch of other older pc's and laptops that I run xmrig on that used to all point to xmrig-proxy on this machine, I could easily stop and start them all or change over to another pool with the proxy. Having this in a docker would be awesome!