Posts by rolfie

rolfie · Hardware & System Configuration

You are right, on a second look there are the same messages present, did not see them.

For the time being: problem solved.

rolfie · Installation

nonbrob user wrote:

hi admin thank you for rep ~ fact > de hardware is a elder thing pad and very common with a non brob bios > the very beginning of booding doesnt work and booding takes very long > failed to connect to lvmetad>falling back to device scanning>openrc0.23 in 4.9.0.11 amd64>vers 2.88 booting

Lets assume you have an older Thinkpad with normal Bios, and you have installed ASCII.

The message "failed to connect to lvmetad" shows that you also have a LVM configured. You can ignore the message, its normal. Booting obviously continues.

nonbrob user wrote:

os brober is installed but nod in GUI > in terminal commend > os-prober unshare failed: Operation not permitted > so unable to stard de prog.

Os-prober is a CLI command and requires root = admin priviliges to run. The message you get is when you run os-prober as user. Open a user terminal and enter su - and enter the root password. Then run os-prober.

rolfie

rolfie · Hardware & System Configuration

Thanks for your feedback. Well, the link you posted deals with an AC supply problem on a laptop, if I read it right. Different issue.
Using the Duck I could not find many threads about this Voltage value error. From the ones I found I could not take any benefit for me and this problem.

My Ryzen worked satisfactory for one and a half years on ASCII now. Its my workbench, and I do not see an urgent need to upgrade right now. And I have a complex setup that works for me, so I don't want to risk this and be offline. Maybe I install Beowulf in the free space I have on my SSD in parallel to ASCII. Need to have a closer look how to do this, never had this setup before.

rolfie

rolfie · Hardware & System Configuration

Just when finished posting this topic the idea crossed my mind that I should better check the version of firmware-amd-graphics installed.

Result is that that I had the original ASCII package dated 2016 on board, and not the one from backports as I thought. Update done, and now I see different messages.

Whats left looks like there is an residual error "Voltage value looks like a Leakage ID but it's not patched" thats also displayed as boot message. The kernel panic like section also is gone.

Any ideas how to get rid of this?

Thanks, rolfie

Feb 22 20:43:48 rh050 kernel: [   16.354304] [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
Feb 22 20:43:48 rh050 kernel: [   16.354649] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_pfp_2.bin
Feb 22 20:43:48 rh050 kernel: [   16.354809] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_me_2.bin
Feb 22 20:43:48 rh050 kernel: [   16.354940] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_ce_2.bin
Feb 22 20:43:48 rh050 kernel: [   16.354942] [drm] Chained IB support enabled!
Feb 22 20:43:48 rh050 kernel: [   16.355168] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_rlc.bin
Feb 22 20:43:48 rh050 kernel: [   16.355928] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec_2.bin
Feb 22 20:43:48 rh050 kernel: [   16.356678] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec2_2.bin
Feb 22 20:43:48 rh050 kernel: [   16.357625] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma.bin
Feb 22 20:43:48 rh050 kernel: [   16.357730] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma1.bin
Feb 22 20:43:48 rh050 kernel: [   16.358553] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_uvd.bin
Feb 22 20:43:48 rh050 kernel: [   16.358555] [drm] Found UVD firmware Version: 1.130 Family ID: 16
Feb 22 20:43:48 rh050 kernel: [   16.359655] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_vce.bin
Feb 22 20:43:48 rh050 kernel: [   16.359657] [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Feb 22 20:43:48 rh050 kernel: [   16.360300] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_k_smc.bin
Feb 22 20:43:48 rh050 kernel: [   16.406712] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Feb 22 20:43:48 rh050 kernel: [   16.406716] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Feb 22 20:43:48 rh050 kernel: [   16.406717] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Feb 22 20:43:48 rh050 kernel: [   16.406719] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Feb 22 20:43:48 rh050 kernel: [   16.406721] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Feb 22 20:43:48 rh050 kernel: [   16.406722] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Feb 22 20:43:48 rh050 kernel: [   16.406724] amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched 
Feb 22 20:43:48 rh050 kernel: [   16.416856] amdgpu: [powerplay] Failed to retrieve minimum clocks.
Feb 22 20:43:48 rh050 kernel: [   16.416858] amdgpu: [powerplay] Error in phm_get_clock_info

rolfie · Installation

yeti wrote:

Ich dacht schon fast, die Sachsen kommen.

Look at the signature of the OP, that explains a lot.

@OP: the "black forrest" may mean that you are from Germany. If that is the case and if it helps you, you may post in German. I will try to help directly in German or translate if I am stuck.

rolfie

rolfie · Hardware & System Configuration

Hardware: ASUS Prime X470 Pro, Ryzen 2700X CPU, 32 GByte RAM.

Original graphics card: Sapphire GPRO 2200 fanless
lspci: 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

Replacment card: Sapphire Pulse Radeon RX 570 8G lite
lspci: 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)

Running on ASCII amd64 in uefi mode, Mate desktop 1.20 from backports on Lightdm, backports kernel 4.19.6, encrypted except /boot, kept up to date. Non-free firmware is installed.

The system was set up with ASCII in September 2018 originally. Some time last year the boot screen started to get grey when switching to graphics mode past some upgrade. This made it hard to read the bootup messages before the login screen by Lightdm. I lived with this situation for several months hoping for a fix by a later update.

In autumn I finally decided that I would go for a fix and bought the replacement card. After plugging that in the situation is different again.

Now the messages scroll down until "waiting for /dev to be fully populated / sp5100-tco sp5100-tco: Watchdog hardware is disabled", then nothing else is happening on the display until the Lightdm login prompt is displayed. Similar issue with shutting down: the exit screen remains until the PC powers off, no more messages scrolling.

When looking into the syslog, I see some error messages. The first complex is related to amd firmware (does that mean the correct firmware for the card is not included?), the second complex looks similar to a kernel panic, though the PC seems to be working fine.

What can I do to fix the issues?

Thanks, rolfie

Feb 22 10:59:38 rh050 kernel: [   15.611189] sp5100-tco sp5100-tco: Watchdog hardware is disabled
Feb 22 10:59:38 rh050 kernel: [   15.613046] input: PC Speaker as /devices/platform/pcspkr/input/input9
Feb 22 10:59:38 rh050 kernel: [   15.613312] EFI Variables Facility v0.08 2004-May-17
Feb 22 10:59:38 rh050 kernel: [   15.616899] ccp 0000:0d:00.2: enabling device (0000 -> 0002)
Feb 22 10:59:38 rh050 kernel: [   15.617215] efivars: duplicate variable: DeploymentModeNv-97e8965f-c761-4f48-b6e4-9ffa9cb2a2d6
Feb 22 10:59:38 rh050 kernel: [   15.619817] pstore: Using compression: deflate
Feb 22 10:59:38 rh050 kernel: [   15.619822] pstore: Registered efi as persistent store backend
Feb 22 10:59:38 rh050 kernel: [   15.624500] ccp 0000:0d:00.2: ccp enabled
Feb 22 10:59:38 rh050 kernel: [   15.624537] ccp 0000:0d:00.2: psp initialization failed
Feb 22 10:59:38 rh050 kernel: [   15.624538] ccp 0000:0d:00.2: enabled
Feb 22 10:59:38 rh050 kernel: [   15.665399] kvm: Nested Virtualization enabled
Feb 22 10:59:38 rh050 kernel: [   15.665406] kvm: Nested Paging enabled
Feb 22 10:59:38 rh050 kernel: [   15.665406] SVM: Virtual VMLOAD VMSAVE supported
Feb 22 10:59:38 rh050 kernel: [   15.665406] SVM: Virtual GIF supported
Feb 22 10:59:38 rh050 kernel: [   15.667220] MCE: In-kernel MCE decoding enabled.
Feb 22 10:59:38 rh050 kernel: [   15.669022] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   15.669023] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   15.669023]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   15.669023]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   15.673506] snd_hda_intel 0000:0c:00.1: Handle vga_switcheroo audio client
Feb 22 10:59:38 rh050 kernel: [   15.673507] snd_hda_intel 0000:0c:00.1: Force to non-snoop mode
Feb 22 10:59:38 rh050 kernel: [   15.673760] snd_hda_intel 0000:0e:00.3: enabling device (0000 -> 0002)
Feb 22 10:59:38 rh050 kernel: [   15.685450] asus_wmi: ASUS WMI generic driver loaded
Feb 22 10:59:38 rh050 kernel: [   15.686554] asus_wmi: Initialization: 0x0
Feb 22 10:59:38 rh050 kernel: [   15.686584] asus_wmi: BIOS WMI version: 0.9
Feb 22 10:59:38 rh050 kernel: [   15.686657] asus_wmi: SFUN value: 0x0
Feb 22 10:59:38 rh050 kernel: [   15.687007] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input10
Feb 22 10:59:38 rh050 kernel: [   15.687153] asus_wmi: Number of fans: 1
Feb 22 10:59:38 rh050 kernel: [   15.689229] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input11
Feb 22 10:59:38 rh050 kernel: [   15.689364] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input12
Feb 22 10:59:38 rh050 kernel: [   15.689451] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input13
Feb 22 10:59:38 rh050 kernel: [   15.689560] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input14
Feb 22 10:59:38 rh050 kernel: [   15.689682] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input15
Feb 22 10:59:38 rh050 kernel: [   15.689743] input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input16
Feb 22 10:59:38 rh050 kernel: [   15.693627] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
Feb 22 10:59:38 rh050 kernel: [   15.693629] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 22 10:59:38 rh050 kernel: [   15.693631] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Feb 22 10:59:38 rh050 kernel: [   15.693632] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Feb 22 10:59:38 rh050 kernel: [   15.693633] snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x1e/0x0
Feb 22 10:59:38 rh050 kernel: [   15.693634] snd_hda_codec_realtek hdaudioC1D0:    inputs:
Feb 22 10:59:38 rh050 kernel: [   15.693636] snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
Feb 22 10:59:38 rh050 kernel: [   15.693638] snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
Feb 22 10:59:38 rh050 kernel: [   15.693639] snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
Feb 22 10:59:38 rh050 kernel: [   15.702636] usbcore: registered new interface driver usbserial_generic
Feb 22 10:59:38 rh050 kernel: [   15.702643] usbserial: USB Serial support registered for generic
Feb 22 10:59:38 rh050 kernel: [   15.705978] usbcore: registered new interface driver ftdi_sio
Feb 22 10:59:38 rh050 kernel: [   15.705984] usbserial: USB Serial support registered for FTDI USB Serial Device
Feb 22 10:59:38 rh050 kernel: [   15.706073] ftdi_sio 6-2:1.0: FTDI USB Serial Device converter detected
Feb 22 10:59:38 rh050 kernel: [   15.706095] usb 6-2: Detected FT232BM
Feb 22 10:59:38 rh050 kernel: [   15.707909] input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/sound/card1/input17
Feb 22 10:59:38 rh050 kernel: [   15.707961] input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/sound/card1/input18
Feb 22 10:59:38 rh050 kernel: [   15.708015] input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/sound/card1/input19
Feb 22 10:59:38 rh050 kernel: [   15.708076] input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/sound/card1/input20
Feb 22 10:59:38 rh050 kernel: [   15.708120] input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/sound/card1/input21
Feb 22 10:59:38 rh050 kernel: [   15.708155] input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/sound/card1/input22
Feb 22 10:59:38 rh050 kernel: [   15.708196] input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/sound/card1/input23
Feb 22 10:59:38 rh050 kernel: [   15.708243] snd_hda_intel 0000:0e:00.3: device 1043:8733 is on the power_save blacklist, forcing power_save to 0
Feb 22 10:59:38 rh050 kernel: [   15.711129] usb 6-2: FTDI USB Serial Device converter now attached to ttyUSB0
Feb 22 10:59:38 rh050 kernel: [   15.725057] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 22 10:59:38 rh050 kernel: [   15.748707] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   15.748708] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   15.748708]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   15.748708]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   15.788172] [drm] amdgpu kernel modesetting enabled.
Feb 22 10:59:38 rh050 kernel: [   15.801773] Parsing CRAT table with 1 nodes
Feb 22 10:59:38 rh050 kernel: [   15.801777] Ignoring ACPI CRAT on non-APU system
Feb 22 10:59:38 rh050 kernel: [   15.801779] Virtual CRAT table created for CPU
Feb 22 10:59:38 rh050 kernel: [   15.801779] Parsing CRAT table with 1 nodes
Feb 22 10:59:38 rh050 kernel: [   15.801780] Creating topology SYSFS entries
Feb 22 10:59:38 rh050 kernel: [   15.801788] Topology: Add CPU node
Feb 22 10:59:38 rh050 kernel: [   15.801788] Finished initializing topology
Feb 22 10:59:38 rh050 kernel: [   15.801849] kfd kfd: Initialized module
Feb 22 10:59:38 rh050 kernel: [   15.802010] checking generic (e0000000 300000) vs hw (e0000000 10000000)
Feb 22 10:59:38 rh050 kernel: [   15.802012] fb: switching to amdgpudrmfb from EFI VGA
Feb 22 10:59:38 rh050 kernel: [   15.802041] Console: switching to colour dummy device 80x25
Feb 22 10:59:38 rh050 kernel: [   15.802345] [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x174B:0x353E 0xEF).
Feb 22 10:59:38 rh050 kernel: [   15.802363] [drm] register mmio base: 0xFCE00000
Feb 22 10:59:38 rh050 kernel: [   15.802364] [drm] register mmio size: 262144
Feb 22 10:59:38 rh050 kernel: [   15.802374] [drm] add ip block number 0 <vi_common>
Feb 22 10:59:38 rh050 kernel: [   15.802375] [drm] add ip block number 1 <gmc_v8_0>
Feb 22 10:59:38 rh050 kernel: [   15.802376] [drm] add ip block number 2 <tonga_ih>
Feb 22 10:59:38 rh050 kernel: [   15.802376] [drm] add ip block number 3 <powerplay>
Feb 22 10:59:38 rh050 kernel: [   15.802377] [drm] add ip block number 4 <dm>
Feb 22 10:59:38 rh050 kernel: [   15.802378] [drm] add ip block number 5 <gfx_v8_0>
Feb 22 10:59:38 rh050 kernel: [   15.802379] [drm] add ip block number 6 <sdma_v3_0>
Feb 22 10:59:38 rh050 kernel: [   15.802380] [drm] add ip block number 7 <uvd_v6_0>
Feb 22 10:59:38 rh050 kernel: [   15.802381] [drm] add ip block number 8 <vce_v3_0>
Feb 22 10:59:38 rh050 kernel: [   15.802392] [drm] UVD is enabled in VM mode
Feb 22 10:59:38 rh050 kernel: [   15.802393] [drm] UVD ENC is enabled in VM mode
Feb 22 10:59:38 rh050 kernel: [   15.802394] [drm] VCE enabled in VM mode
Feb 22 10:59:38 rh050 kernel: [   15.802608] ATOM BIOS: 113-YE353HM-UPE
Feb 22 10:59:38 rh050 kernel: [   15.802639] [drm] vm size is 128 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
Feb 22 10:59:38 rh050 kernel: [   15.803539] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_mc.bin
Feb 22 10:59:38 rh050 kernel: [   15.803549] amdgpu 0000:0c:00.0: VRAM: 8192M 0x000000F400000000 - 0x000000F5FFFFFFFF (8192M used)
Feb 22 10:59:38 rh050 kernel: [   15.803551] amdgpu 0000:0c:00.0: GART: 256M 0x0000000000000000 - 0x000000000FFFFFFF
Feb 22 10:59:38 rh050 kernel: [   15.803558] [drm] Detected VRAM RAM=8192M, BAR=256M
Feb 22 10:59:38 rh050 kernel: [   15.803559] [drm] RAM width 256bits GDDR5
Feb 22 10:59:38 rh050 kernel: [   15.803619] [TTM] Zone  kernel: Available graphics memory: 16458446 kiB
Feb 22 10:59:38 rh050 kernel: [   15.803620] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
Feb 22 10:59:38 rh050 kernel: [   15.803620] [TTM] Initializing pool allocator
Feb 22 10:59:38 rh050 kernel: [   15.803624] [TTM] Initializing DMA pool allocator
Feb 22 10:59:38 rh050 kernel: [   15.803660] [drm] amdgpu: 8192M of VRAM memory ready
Feb 22 10:59:38 rh050 kernel: [   15.803661] [drm] amdgpu: 8192M of GTT memory ready.
Feb 22 10:59:38 rh050 kernel: [   15.803670] [drm] GART: num cpu pages 65536, num gpu pages 65536
Feb 22 10:59:38 rh050 kernel: [   15.805362] [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
Feb 22 10:59:38 rh050 kernel: [   15.805461] amdgpu 0000:0c:00.0: firmware: failed to load amdgpu/polaris10_pfp_2.bin (-2)
Feb 22 10:59:38 rh050 kernel: [   15.805466] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
Feb 22 10:59:38 rh050 kernel: [   15.805470] amdgpu 0000:0c:00.0: Direct firmware load for amdgpu/polaris10_pfp_2.bin failed with error -2
Feb 22 10:59:38 rh050 kernel: [   15.805775] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_pfp.bin
Feb 22 10:59:38 rh050 kernel: [   15.805787] amdgpu 0000:0c:00.0: firmware: failed to load amdgpu/polaris10_me_2.bin (-2)
Feb 22 10:59:38 rh050 kernel: [   15.805792] amdgpu 0000:0c:00.0: Direct firmware load for amdgpu/polaris10_me_2.bin failed with error -2
Feb 22 10:59:38 rh050 kernel: [   15.805930] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_me.bin
Feb 22 10:59:38 rh050 kernel: [   15.805941] amdgpu 0000:0c:00.0: firmware: failed to load amdgpu/polaris10_ce_2.bin (-2)
Feb 22 10:59:38 rh050 kernel: [   15.805946] amdgpu 0000:0c:00.0: Direct firmware load for amdgpu/polaris10_ce_2.bin failed with error -2
Feb 22 10:59:38 rh050 kernel: [   15.806108] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_ce.bin
Feb 22 10:59:38 rh050 kernel: [   15.806265] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_rlc.bin
Feb 22 10:59:38 rh050 kernel: [   15.806279] amdgpu 0000:0c:00.0: firmware: failed to load amdgpu/polaris10_mec_2.bin (-2)
Feb 22 10:59:38 rh050 kernel: [   15.806284] amdgpu 0000:0c:00.0: Direct firmware load for amdgpu/polaris10_mec_2.bin failed with error -2
Feb 22 10:59:38 rh050 kernel: [   15.807829] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec.bin
Feb 22 10:59:38 rh050 kernel: [   15.807841] amdgpu 0000:0c:00.0: firmware: failed to load amdgpu/polaris10_mec2_2.bin (-2)
Feb 22 10:59:38 rh050 kernel: [   15.807846] amdgpu 0000:0c:00.0: Direct firmware load for amdgpu/polaris10_mec2_2.bin failed with error -2
Feb 22 10:59:38 rh050 kernel: [   15.808869] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec2.bin
Feb 22 10:59:38 rh050 kernel: [   15.809826] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma.bin
Feb 22 10:59:38 rh050 kernel: [   15.809987] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma1.bin
Feb 22 10:59:38 rh050 kernel: [   15.811331] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_uvd.bin
Feb 22 10:59:38 rh050 kernel: [   15.811333] [drm] Found UVD firmware Version: 1.79 Family ID: 16
Feb 22 10:59:38 rh050 kernel: [   15.811337] [drm] UVD ENC is disabled
Feb 22 10:59:38 rh050 kernel: [   15.812430] amdgpu 0000:0c:00.0: firmware: direct-loading firmware amdgpu/polaris10_vce.bin
Feb 22 10:59:38 rh050 kernel: [   15.812434] [drm] Found VCE firmware Version: 52.4 Binary ID: 3
Feb 22 10:59:38 rh050 kernel: [   15.812675] amdgpu 0000:0c:00.0: firmware: failed to load amdgpu/polaris10_k_smc.bin (-2)
Feb 22 10:59:38 rh050 kernel: [   15.812679] amdgpu 0000:0c:00.0: Direct firmware load for amdgpu/polaris10_k_smc.bin failed with error -2
Feb 22 10:59:38 rh050 kernel: [   15.812729] [drm:amdgpu_cgs_get_firmware_info [amdgpu]] *ERROR* Failed to request firmware
Feb 22 10:59:38 rh050 kernel: [   16.283720] amdgpu: [powerplay] Failed to send Message.
Feb 22 10:59:38 rh050 kernel: [   16.761165] amdgpu: [powerplay] SMU Firmware start failed!
Feb 22 10:59:38 rh050 kernel: [   16.761165] amdgpu: [powerplay] Failed to load SMU ucode.
Feb 22 10:59:38 rh050 kernel: [   16.761166] amdgpu: [powerplay] smc start failed
Feb 22 10:59:38 rh050 kernel: [   16.761168] amdgpu: [powerplay] powerplay hw init failed
Feb 22 10:59:38 rh050 kernel: [   16.761204] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <powerplay> failed -22
Feb 22 10:59:38 rh050 kernel: [   16.761207] amdgpu 0000:0c:00.0: amdgpu_device_ip_init failed
Feb 22 10:59:38 rh050 kernel: [   16.761209] amdgpu 0000:0c:00.0: Fatal error during GPU init
Feb 22 10:59:38 rh050 kernel: [   16.761219] [drm] amdgpu: finishing device.
Feb 22 10:59:38 rh050 kernel: [   17.767534] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   17.767534]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   18.270243] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   18.270243]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   19.275704] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   19.275704]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   19.778467] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   19.778467]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   20.783863] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   20.783863]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   21.286594] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   21.286594]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   22.292035] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   22.292035]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   22.794757] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   22.794757]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   23.800230] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   23.800230]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   24.302904] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   24.302904]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   25.308369] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   25.308369]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   25.811084] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   25.811084]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   26.816541] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   26.816541]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   27.319268] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   27.319268]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   28.324723] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   28.324723]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   28.827422] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   28.827422]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   29.832877] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   29.832877]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   30.335578] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   30.335578]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   31.341038] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   31.341038]  last message was failed ret is 0
Feb 22 10:59:38 rh050 kernel: [   31.843745] amdgpu: [powerplay] 
Feb 22 10:59:38 rh050 kernel: [   31.843745]  failed to send message 261 ret is 0 
Feb 22 10:59:38 rh050 kernel: [   31.844311] igb 0000:0a:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 22 10:59:38 rh050 kernel: [   31.849818] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   31.849819] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   31.849819]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   31.849819]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   31.909251] ------------[ cut here ]------------
Feb 22 10:59:38 rh050 kernel: [   31.909252] Memory manager not clean during takedown.
Feb 22 10:59:38 rh050 kernel: [   31.909281] WARNING: CPU: 11 PID: 684 at /build/linux-3Qtbv4/linux-4.19.67/drivers/gpu/drm/drm_mm.c:950 drm_mm_takedown+0x20/0x30 [drm]
Feb 22 10:59:38 rh050 kernel: [   31.909281] Modules linked in: amd64_edac_mod(-) amdkfd amdgpu(+) ftdi_sio usbserial snd_hda_codec_realtek joydev snd_hda_codec_generic eeepc_wmi asus_wmi snd_hda_codec_hdmi sparse_keymap rfkill video wmi_bmof mxm_wmi evdev snd_hda_intel snd_hda_codec edac_mce_amd snd_hda_core kvm_amd snd_hwdep chash snd_pcm gpu_sched kvm ttm drm_kms_helper snd_timer irqbypass snd efi_pstore soundcore ccp k10temp drm efivars pcspkr sp5100_tco rng_core pcc_cpufreq wmi acpi_cpufreq button ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb algif_skcipher af_alg dm_crypt dm_mod uas usb_storage sr_mod cdrom sg hid_generic usbhid hid sd_mod ohci_pci crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc ahci xhci_pci libahci xhci_hcd ehci_pci libata ohci_hcd ehci_hcd aesni_intel igb usbcore scsi_mod aes_x86_64
Feb 22 10:59:38 rh050 kernel: [   31.909308]  crypto_simd cryptd nvme glue_helper i2c_piix4 i2c_algo_bit nvme_core dca usb_common gpio_amdpt gpio_generic
Feb 22 10:59:38 rh050 kernel: [   31.909313] CPU: 11 PID: 684 Comm: udevd Not tainted 4.19.0-0.bpo.6-amd64 #1 Debian 4.19.67-2+deb10u2~bpo9+1
Feb 22 10:59:38 rh050 kernel: [   31.909314] Hardware name: System manufacturer System Product Name/PRIME X470-PRO, BIOS 5406 11/13/2019
Feb 22 10:59:38 rh050 kernel: [   31.909325] RIP: 0010:drm_mm_takedown+0x20/0x30 [drm]
Feb 22 10:59:38 rh050 kernel: [   31.909327] Code: fc 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 c7 75 02 f3 c3 48 c7 c7 70 a7 5f c0 e8 00 d0 cb fc <0f> 0b c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 41
Feb 22 10:59:38 rh050 kernel: [   31.909328] RSP: 0018:ffffa6e6c84fb9d8 EFLAGS: 00010282
Feb 22 10:59:38 rh050 kernel: [   31.909329] RAX: 0000000000000000 RBX: ffff9a9ef1e351e8 RCX: ffffffffbe24dea8
Feb 22 10:59:38 rh050 kernel: [   31.909330] RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000247
Feb 22 10:59:38 rh050 kernel: [   31.909331] RBP: ffff9a9ef1e35100 R08: 0000000000000001 R09: 00000000000004e2
Feb 22 10:59:38 rh050 kernel: [   31.909331] R10: ffff9a9ef5994900 R11: 0000000000000000 R12: ffff9a9ef73a29a0
Feb 22 10:59:38 rh050 kernel: [   31.909332] R13: 0000000000000000 R14: 0000000000000170 R15: ffff9a9ef73a3080
Feb 22 10:59:38 rh050 kernel: [   31.909333] FS:  00007fe735655880(0000) GS:ffff9a9efe8c0000(0000) knlGS:0000000000000000
Feb 22 10:59:38 rh050 kernel: [   31.909334] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 22 10:59:38 rh050 kernel: [   31.909335] CR2: 00007f2a85dacab4 CR3: 00000007f9616000 CR4: 00000000003406e0
Feb 22 10:59:38 rh050 kernel: [   31.909335] Call Trace:
Feb 22 10:59:38 rh050 kernel: [   31.909390]  amdgpu_vram_mgr_fini+0x27/0x50 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909397]  ttm_bo_clean_mm+0xa7/0xf0 [ttm]
Feb 22 10:59:38 rh050 kernel: [   31.909447]  amdgpu_ttm_fini+0x72/0x110 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909496]  amdgpu_bo_fini+0xe/0x30 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909551]  gmc_v8_0_sw_fini+0x32/0x60 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909598]  amdgpu_device_fini+0x431/0x550 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909645]  amdgpu_driver_unload_kms+0x42/0x90 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909692]  amdgpu_driver_load_kms+0x154/0x2d0 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909703]  drm_dev_register+0x112/0x1a0 [drm]
Feb 22 10:59:38 rh050 kernel: [   31.909750]  amdgpu_pci_probe+0x1b5/0x280 [amdgpu]
Feb 22 10:59:38 rh050 kernel: [   31.909754]  local_pci_probe+0x44/0xa0
Feb 22 10:59:38 rh050 kernel: [   31.909757]  ? _cond_resched+0x16/0x40
Feb 22 10:59:38 rh050 kernel: [   31.909759]  pci_device_probe+0x105/0x1c0
Feb 22 10:59:38 rh050 kernel: [   31.909761]  really_probe+0x215/0x3f0
Feb 22 10:59:38 rh050 kernel: [   31.909763]  driver_probe_device+0x10b/0x130
Feb 22 10:59:38 rh050 kernel: [   31.909765]  __driver_attach+0x119/0x120
Feb 22 10:59:38 rh050 kernel: [   31.909766]  ? driver_probe_device+0x130/0x130
Feb 22 10:59:38 rh050 kernel: [   31.909768]  bus_for_each_dev+0x67/0xc0
Feb 22 10:59:38 rh050 kernel: [   31.909770]  ? klist_add_tail+0x3b/0x70
Feb 22 10:59:38 rh050 kernel: [   31.909771]  bus_add_driver+0x16a/0x260
Feb 22 10:59:38 rh050 kernel: [   31.909773]  driver_register+0x5b/0xe0
Feb 22 10:59:38 rh050 kernel: [   31.909774]  ? 0xffffffffc09ed000
Feb 22 10:59:38 rh050 kernel: [   31.909776]  do_one_initcall+0x4d/0x1c5
Feb 22 10:59:38 rh050 kernel: [   31.909778]  ? _cond_resched+0x16/0x40
Feb 22 10:59:38 rh050 kernel: [   31.909780]  ? kmem_cache_alloc_trace+0x16a/0x1d0
Feb 22 10:59:38 rh050 kernel: [   31.909783]  do_init_module+0x5b/0x21b
Feb 22 10:59:38 rh050 kernel: [   31.909785]  load_module+0x24de/0x2b20
Feb 22 10:59:38 rh050 kernel: [   31.909788]  ? __do_sys_finit_module+0xd7/0x110
Feb 22 10:59:38 rh050 kernel: [   31.909790]  __do_sys_finit_module+0xd7/0x110
Feb 22 10:59:38 rh050 kernel: [   31.909792]  do_syscall_64+0x55/0x120
Feb 22 10:59:38 rh050 kernel: [   31.909794]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 22 10:59:38 rh050 kernel: [   31.909795] RIP: 0033:0x7fe734b1b469
Feb 22 10:59:38 rh050 kernel: [   31.909797] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ff 49 2b 00 f7 d8 64 89 01 48
Feb 22 10:59:38 rh050 kernel: [   31.909798] RSP: 002b:00007ffcdf856cf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Feb 22 10:59:38 rh050 kernel: [   31.909799] RAX: ffffffffffffffda RBX: 000056465676ff20 RCX: 00007fe734b1b469
Feb 22 10:59:38 rh050 kernel: [   31.909799] RDX: 0000000000000000 RSI: 00007fe734de7265 RDI: 000000000000000f
Feb 22 10:59:38 rh050 kernel: [   31.909800] RBP: 00007fe734de7265 R08: 0000000000000000 R09: 00007ffcdf857270
Feb 22 10:59:38 rh050 kernel: [   31.909801] R10: 000000000000000f R11: 0000000000000246 R12: 0000000000000000
Feb 22 10:59:38 rh050 kernel: [   31.909801] R13: 0000564656772090 R14: 0000000000020000 R15: 0000564655a76319
Feb 22 10:59:38 rh050 kernel: [   31.909803] ---[ end trace b98908ecc39fa167 ]---
Feb 22 10:59:38 rh050 kernel: [   31.909808] [TTM] Finalizing pool allocator
Feb 22 10:59:38 rh050 kernel: [   31.909812] [TTM] Finalizing DMA pool allocator
Feb 22 10:59:38 rh050 kernel: [   31.909840] [TTM] Zone  kernel: Used memory at exit: 22 kiB
Feb 22 10:59:38 rh050 kernel: [   31.909842] [TTM] Zone   dma32: Used memory at exit: 22 kiB
Feb 22 10:59:38 rh050 kernel: [   31.909844] [drm] amdgpu: ttm finalized
Feb 22 10:59:38 rh050 kernel: [   31.910039] amdgpu: probe of 0000:0c:00.0 failed with error -22
Feb 22 10:59:38 rh050 kernel: [   31.952908] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   31.952910] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   31.952910]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   31.952910]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.000861] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.000863] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.000863]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.000863]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.057072] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.057073] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.057073]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.057073]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.097084] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.097086] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.097086]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.097086]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.137102] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.137103] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.137103]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.137103]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.181398] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.181400] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.181400]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.181400]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.221396] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.221397] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.221397]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.221397]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.273256] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.273258] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.273258]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.273258]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.321052] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.321053] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.321053]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.321053]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.373105] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.373106] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.373106]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.373106]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.413134] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.413136] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.413136]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.413136]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.445207] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.445209] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.445209]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.445209]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.485111] EDAC amd64: Node 0: DRAM ECC disabled.
Feb 22 10:59:38 rh050 kernel: [   32.485112] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Feb 22 10:59:38 rh050 kernel: [   32.485112]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Feb 22 10:59:38 rh050 kernel: [   32.485112]  (Note that use of the override may cause unknown side effects.)
Feb 22 10:59:38 rh050 kernel: [   32.653619] EXT4-fs (dm-1): re-mounted. Opts: discard,errors=remount-ro
Feb 22 10:59:38 rh050 kernel: [   34.012335] igb 0000:0a:00.0: exceed max 2 second
Feb 22 10:59:38 rh050 kernel: [   34.012507] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 22 10:59:38 rh050 kernel: [   44.136814] lp: driver loaded but no devices found
Feb 22 10:59:38 rh050 kernel: [   44.140919] ppdev: user-space parallel port driver
Feb 22 10:59:38 rh050 kernel: [   44.216544] Adding 31997948k swap on /dev/mapper/vgsys-2_swap.  Priority:-2 extents:1 across:31997948k SSFS
Feb 22 10:59:38 rh050 kernel: [   44.384616] EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Opts: (null)
Feb 22 10:59:38 rh050 kernel: [   44.411627] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: discard
Feb 22 10:59:38 rh050 kernel: [   44.433402] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: (null)
Feb 22 10:59:38 rh050 kernel: [   44.469276] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null)
Feb 22 10:59:38 rh050 kernel: [   44.491782] fuse init (API version 7.27)
Feb 22 10:59:38 rh050 kernel: [   44.884523] audit: type=1400 audit(1582365577.327:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="virt-aa-helper" pid=2229 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   44.891532] audit: type=1400 audit(1582365577.331:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/libvirtd" pid=2240 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   44.891633] audit: type=1400 audit(1582365577.331:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/libvirtd//qemu_bridge_helper" pid=2240 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   44.901362] audit: type=1400 audit(1582365577.343:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=2228 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   44.905792] audit: type=1400 audit(1582365577.347:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=2233 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   44.906789] RPC: Registered named UNIX socket transport module.
Feb 22 10:59:38 rh050 kernel: [   44.906790] RPC: Registered udp transport module.
Feb 22 10:59:38 rh050 kernel: [   44.906790] RPC: Registered tcp transport module.
Feb 22 10:59:38 rh050 kernel: [   44.906790] RPC: Registered tcp NFSv4.1 backchannel transport module.
Feb 22 10:59:38 rh050 kernel: [   44.915815] FS-Cache: Loaded
Feb 22 10:59:38 rh050 kernel: [   44.931224] FS-Cache: Netfs 'nfs' registered for caching
Feb 22 10:59:38 rh050 kernel: [   44.952692] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Feb 22 10:59:38 rh050 kernel: [   45.016082] audit: type=1400 audit(1582365577.459:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2232 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   45.016281] audit: type=1400 audit(1582365577.459:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=2232 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   45.016326] audit: type=1400 audit(1582365577.459:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=2232 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   45.162551] audit: type=1400 audit(1582365577.603:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/mission-control-5" pid=2230 comm="apparmor_parser"
Feb 22 10:59:38 rh050 kernel: [   45.162807] audit: type=1400 audit(1582365577.603:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-*" pid=2230 comm="apparmor_parser"
Feb 22 10:59:38 rh050 ntpd[2722]: ntpd 4.2.8p10@1.3728-o Sun Feb 25 21:22:55 UTC 2018 (1): Starting
Feb 22 10:59:38 rh050 ntpd[2722]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 108:113
Feb 22 10:59:38 rh050 ntpd[2790]: proto: precision = 0.050 usec (-24)
Feb 22 10:59:38 rh050 cron[2800]: (CRON) INFO (pidfile fd = 3)
Feb 22 10:59:38 rh050 cron[2865]: (CRON) STARTUP (fork ok)
Feb 22 10:59:38 rh050 ntpd[2790]: Listen and drop on 0 v6wildcard [::]:123
Feb 22 10:59:38 rh050 ntpd[2790]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Feb 22 10:59:38 rh050 ntpd[2790]: Listen normally on 2 lo 127.0.0.1:123
Feb 22 10:59:38 rh050 ntpd[2790]: Listen normally on 3 eth0 10.6.6.50:123
Feb 22 10:59:38 rh050 ntpd[2790]: Listen normally on 4 lo [::1]:123
Feb 22 10:59:38 rh050 ntpd[2790]: Listen normally on 5 eth0 [fe80::4eed:fbff:fe79:1cdf%2]:123
Feb 22 10:59:38 rh050 ntpd[2790]: Listening on routing socket on fd #22 for interface updates

rolfie · Hardware & System Configuration

Well, I just recently had a case with my wifes desktop where also the network stopped working, the onBoard Realtek chip went bad. Indication was that the usual lights for speed and activity did no more work.

I put in EE1000 card I had laying around, and the network was up again.

Consider such a scenario.

Good luck, rolfie

rolfie · Hardware & System Configuration

Got two PC running ASCII with backports kernel 4.19.6, 4.9.12 also is installed as backup, no network issues since the ASCII installation about two years ago. I have wired GBit lan here. Basically the same sources.list entries here.

What exactly is your setup? Wifi? Can you try wired network?

Regards, rolfie

rolfie · News & Announcements

Just tried to update my ASCII installation, works like a charm.

My sources.list also contains contrib and non-free, and also includes backports and proposed updates, here is the first line:

deb http://deb.devuan.org/merged ascii main contrib non-free

Found 35 updates.

I can't see a mistake in your sources.list. Try again apt update, apt list --upgradable, apt upgrade.

rolfie

rolfie · Installation

Give the root terminal a try. First do an apt update/apt upgrade, then:

apt -t ascii-backports install linux-headers-4.19.0-0.bpo.6-amd64

You will have to replace the 4.19.0-0.bpo.6-amd64 with the correct suffix for your machine. That apt install will pull all the required dependencies for the headers.

Rolfie

rolfie · Hardware & System Configuration

Despite the d on the end, elogind is a systemd free program, and not comparable to the Gentoo stuff. Look at post #12 in https://dev1galaxy.org/viewtopic.php?id=2675.

When you remove elogind, I bet you will get issues with permissions.

When you search the forum for elogind and take a read through some threads you might get an idea why elogind is a good choice.

rolfie

rolfie · Hardware & System Configuration

libusb-1.0-0 1.0.19-1 is available in Jessie. Refer to https://pkginfo.devuan.org/. You have to specify the complete name in your apt install command.

rolfie

rolfie · News & Announcements

Head_on_a_Stick wrote:

Note that the apt-transport-https package is needed to take advantage of https sources.

Tried this and it didn't work. I think I discussed this in a thread a while ago, but I couldn't find it.

golinux wrote:

rolfie wrote:
@golinux: the current page https://devuan.org/os/ is corrected now, as you said. I looked at his page a few days ago, and it still had the hint to the country codes.
There is a link to https://devuan.org/os/etc/apt/sources.list which still refers to country codes. I would patch that page too.
That section is a partial that is called on both pages. Last I looked, both pages were picking it up. Try refreshing the page if you're not seeing it.

Called that page pointing to /etc/apt/sources.list with my up-to-date FF-ESR and Chromium, still get the hint to the country codes.

rolfie

rolfie · News & Announcements

@golinux: the current page https://devuan.org/os/ is corrected now, as you said. I looked at his page a few days ago, and it still had the hint to the country codes.

There is a link to https://devuan.org/os/etc/apt/sources.list which still refers to country codes. I would patch that page too.

rolfie

rolfie · News & Announcements

I can confirm that https does not work. There is at least one thread somewhere in this forum about this topic.

A simple http://deb.devuan.org/merged without country code works fine (ignore the Devuan web page).

rolfie

rolfie · Installation

little wrote:

golinux wrote:
Why didn't you use ascii 2.1? It was released 2 months ago.
https://devuan.org/os/debian-fork/ascii … nce-112119
I already had an older 2.0 ascii, and to make a new one would require burning a new CD. I did an apt-get update / dist-upgrade after installation, and according to forum post: http://dev1galaxy.org/viewtopic.php?id=3195 it shouldn't make a difference which install cd I use.
Of course, I may be wrong here. Should I have used 2.1? If that's the case, then this report can be ignored.

Makes no difference. It was not clear if you used a fresh install (then 2.1 as a start would have been easier) or an existing installation. When the older installation is updated, there is no difference.

little wrote:

rolfie wrote:
I used a different approach when the netinstall-images were not working:
- install ASCII to cli, no desktop, just base system
- apt update/upgrade to lastest status
- modify sources.list to beowulf
- apt update/upgrade/full-upgrade
- apt install xorg lightdm mate-desktop-environment-extras
@OP: why do you use sudo? Use a root terminal, works fine.
Install mate-tweak to easily configure the desktop icons.
rolfie
That install is not typical of people upgrading existing (mate) machines from ascii to beowulf. So it's good that mate works from fresh install, but this is a migration. The issue about the computer icon is more a bug report, than anything else. It was there in Ascii, and disappeared in Beowulf. Users should not need to use mate-tweak...

Maybe you don't remember: no matter if 1.16 or 1.20, on a fresh install Mate comes with the Home folder icon only on the desktop. You have to configure your desktop anyhow. The hard way is via the dconf-editor, at least for me, I never immediately find the settings, mate-tweak is much easier.

Regards, rolfie

rolfie · Installation

I used a different approach when the netinstall-images were not working:
- install ASCII to cli, no desktop, just base system
- apt update/upgrade to lastest status
- modify sources.list to beowulf
- apt update/upgrade/full-upgrade
- apt install xorg lightdm mate-desktop-environment-extras

@OP: why do you use sudo? Use a root terminal, works fine.

Install mate-tweak to easily configure the desktop icons.

rolfie

rolfie · Hardware & System Configuration

Thanks, the contents pointed to the Realtek NIC. Renamed the file and everything is back to eth0.

I have the feeling that FF is resolving adresses very slowly now. Is there an easy way to generate a new rule for the Intel NIC?

Thanks, rolfie

rolfie · Hardware & System Configuration

Got a M5A99X EVO R2 board running ASCII. The onboard NIC (Realtek) suddenly stopped working. I had an Intel GBit NIC around I did install in the PC and disabled the onboard chip in the BIOS. This is no more detected by lspci.

But now ASCII insists on replacing eth0 with eth1. Had to modify the interfaces settings.

Where do I need to look to stop ASCII/(eudev?) doing this?

Thnaks, rolfie

rolfie · Hardware & System Configuration

jamesthedisciple wrote:

Also it waits at:
MTA
I have no idea what this means!

MTA = Mail Transfer Agent, typically exim. Starting up exim can take a while when no network is detected until some timeouts have passed.

Regards, rolfie

rolfie · Installation

I just use Mate in ASCII and Beowulf. There is no difference, you find the lightdm.conf in /etc/lightdm. There you need to uncomment:

[Seat:*]
#type=xlocal

....

#greeter-session=example-gtk-gnome
greeter-hide-users=false

That works fine and display a list of full usernames on the login screen.

I have just done an apt install lightdm, there are no options.

rolfie

rolfie · Installation

@OP: as you say you are using a LVM, then the message is normal. As long as the LVM finally is opened, everything is fine.

rolfie

rolfie · Installation

Hi roluan17,

I'm from Germany also. I have dropped all tries to add a country code or a specific mirror. I simply use:

deb http://deb.devuan.org/merged ascii main contrib non-free
deb http://deb.devuan.org/merged ascii-security main contrib non-free
deb http://deb.devuan.org/merged ascii-updates main contrib non-free
deb http://deb.devuan.org/merged ascii-backports main contrib non-free

This works fine.

Regards, rolfie

rolfie · Installation

rich43 wrote:

I've used Debian for a number of years and am used to updating Debian releases using their announcements
and apt's update, upgrade (or full-upgrade), using apt/aptitude..

If you have been using apt update/upgrade regularly since installation, you have an up to date ASCII installation, which only has very minor differences to the 2.1 point release. i.e. if you have selected openrc during your initial installation, you still got it and its up to date. If you want to install it now and change to using it, it is more work to do.

Under normal circumstances there is no point in re-installing with 2.1 if you are happy and have not totally screwed your system. This point release has the charm that when you do a fresh installation, you have an easier access to openrc and you have much less updates that need to be installed vs a 2.0 installation. Thats it.

I'm running two PCs at home that have been installed with a 2.0 beta which is my wifes PC and mine that was build after the release of 2.0. Both work fine and are up to date without re-installation.

rolfie

rolfie · Installation

Which release do you intend to use? ASCII = stable, Beowulf = testing, ceres = unstable/experimental?

Check if changing the sources to

deb http://deb.devuan.org/merged ascii

helps. This is the official notification, refer to https://devuan.org/os/etc/apt/sources.list.

The officially official Devuan Forum!

#1051 Re: Hardware & System Configuration » [Solved] Boot messages surpressed with new graphics card » 2020-02-23 12:28:41

#1052 Re: Installation » bood manager ?? » 2020-02-23 09:46:13

#1053 Re: Hardware & System Configuration » [Solved] Boot messages surpressed with new graphics card » 2020-02-22 20:52:39

#1054 Re: Hardware & System Configuration » [Solved] Boot messages surpressed with new graphics card » 2020-02-22 19:56:22

#1055 Re: Installation » bood manager ?? » 2020-02-22 19:11:39

#1056 Hardware & System Configuration » [Solved] Boot messages surpressed with new graphics card » 2020-02-22 19:10:07

#1057 Re: Hardware & System Configuration » TWO kernels in one update? » 2020-02-13 22:10:28

#1058 Re: Hardware & System Configuration » TWO kernels in one update? » 2020-02-13 10:33:55

#1059 Re: News & Announcements » Sources.list broken » 2020-02-05 17:19:10

#1060 Re: Installation » [SOLVED] ASCII Backports Linux Headers » 2020-02-02 09:40:18

#1061 Re: Hardware & System Configuration » Any issues to be expected by disabling elogind? » 2020-01-29 20:01:09

#1062 Re: Hardware & System Configuration » Recommended installation method for newer version of HPLIP - Jessie. » 2020-01-26 20:09:07

#1063 Re: News & Announcements » sources.list confusion. » 2020-01-26 16:01:54

#1064 Re: News & Announcements » sources.list confusion. » 2020-01-26 09:11:21

#1065 Re: News & Announcements » sources.list confusion. » 2020-01-25 21:42:03

#1066 Re: Installation » Mate: Ascii to Beowulf Migration » 2020-01-20 09:29:11

#1067 Re: Installation » Mate: Ascii to Beowulf Migration » 2020-01-19 16:05:14

#1068 Re: Hardware & System Configuration » NIC replacement issues » 2020-01-18 10:42:50

#1069 Hardware & System Configuration » NIC replacement issues » 2020-01-17 17:48:14

#1070 Re: Hardware & System Configuration » hanging on boot (openrc) on eth0 » 2020-01-11 12:29:12

#1071 Re: Installation » SOLVED: /etc/lightdm/lightdm.conf different in Cinnamon versus MATE » 2020-01-09 20:01:52

#1072 Re: Installation » "Warning": Failed to connect to lvmetad » 2020-01-01 15:29:43

#1073 Re: Installation » sources.list for bloody germans » 2019-12-12 18:13:18

#1074 Re: Installation » Updating ASCII to ASCII 2.1 point release » 2019-12-03 21:22:41

#1075 Re: Installation » Hash Sun mismatch » 2019-11-29 20:24:53

Board footer