You are not logged in.
- Topics: Active | Unanswered
#901 Re: Desktop and Multimedia » [Solved] Mesa update for Cinnamon in Beowulf » 2020-09-11 19:09:49
@HOAS: don't worry, the installation went fine and the X570 with Cinnamon still works ok. No harm, libc6 still is the Beowulf stable version.
# apt list libc6
Auflistung... Fertig
libc6/stable,now 2.28-10 amd64 [installiert]
libc6/stable,now 2.28-10 i386 [Installiert,automatisch]What I did:
# apt -t mx install mesa-va-drivers mesa-vdpau-driversThey are on the MX version now:
# apt list mesa*
Auflistung... Fertig
mesa-common-dev/stable 18.3.6-2+deb10u1 amd64
mesa-common-dev/stable 18.3.6-2+deb10u1 i386
mesa-opencl-icd/stable 18.3.6-2+deb10u1 amd64
mesa-opencl-icd/stable 18.3.6-2+deb10u1 i386
mesa-utils-extra/stable 8.4.0-1+b1 amd64
mesa-utils-extra/stable 8.4.0-1+b1 i386
mesa-utils/stable,now 8.4.0-1+b1 amd64 [Installiert,automatisch]
mesa-utils/stable 8.4.0-1+b1 i386
mesa-va-drivers/mx,now 20.1.5-1~mx19ahs+1 amd64 [Installiert,automatisch]
mesa-va-drivers/stable 18.3.6-2+deb10u1 i386
mesa-vdpau-drivers/mx,now 20.1.5-1~mx19ahs+1 amd64 [installiert]
mesa-vdpau-drivers/stable 18.3.6-2+deb10u1 i386
mesa-vulkan-drivers/stable 18.3.6-2+deb10u1 amd64
mesa-vulkan-drivers/stable 18.3.6-2+deb10u1 i386Something around OpenGL must be requiring an update too, inxi shows still 18.3, I guess thats the problem why Cinnamon still decides to start in SW rendering mode:
# inxi -F
System: Host: rh060 Kernel: 5.7.0-0.bpo.2-amd64 x86_64 bits: 64 Desktop: Cinnamon 3.8.8
Distro: Devuan GNU/Linux 3 (Beowulf)
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: 190957676700346 UEFI: American Megatrends
v: 2606 date: 08/13/2020
CPU: Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP L2 cache: 4096 KiB
Speed: 2796 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2798 2: 2801 3: 2794 4: 2793 5: 1863 6: 2799 7: 2800
8: 2790 9: 2799 10: 2793 11: 1865 12: 2800 13: 2794 14: 2797 15: 2800 16: 2800
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] driver: amdgpu v: kernel
Display: server: X.Org 1.20.4 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1200~60Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6I have looked at apt list llvm* and through Synaptic searching for OpenGL packages, but currently I have no idea what I need to update.
What do I need to look for?
Rolfie
Edit: on a second look searching for OpenGL in Synaptic I found these two libraries that have an 18.3 version tag:
libgl1-mesa-dri
libglx-mesa0
Anything else I need to update?
#902 Re: Desktop and Multimedia » Beowulf crashes often » 2020-09-11 17:21:42
Have you tried with the backports kernel and drivers. It is quite wellknown that kernel 4.19 is a bit to old to support Ryzen 2700X. And there have been reported numerous problems with that should be solved by now.
# inxi -F
System: Host: rh050 Kernel: 5.7.0-0.bpo.2-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Devuan GNU/Linux 3 (beowulf)
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: 180529428800462 UEFI: American Megatrends
v: 5406 date: 11/13/2019
CPU: Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP L2 cache: 4096 KiB
Speed: 1915 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 1883 2: 1890 3: 2094 4: 2080 5: 2088 6: 2106 7: 2096
8: 2187 9: 1889 10: 1887 11: 1884 12: 1889 13: 1890 14: 1956 15: 2126 16: 2088
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480] driver: amdgpu v: kernel
Display: server: X.Org 1.20.4 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~60Hz
OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.37.0 5.7.0-0.bpo.2-amd64 LLVM 7.0.1) v: 4.5 Mesa 18.3.6Also refer to https://dev1galaxy.org/viewtopic.php?id=3616
rolfie
#903 Re: Desktop and Multimedia » [Solved] Mesa update for Cinnamon in Beowulf » 2020-09-10 20:49:58
Well, tried the update and got two packages installed which bring mesa 21 instead of 18, pulled some additional libs, but they do not have the desired effect. Cinnamon still decides to use SW rendering. Need to have a closer look on the logs to find the reason.
Thanks for the suggestion. Too late tonight, will have a closer look on the weekend.
rolfie
#904 Re: Desktop and Multimedia » Beowulf crashes often » 2020-09-10 20:44:46
Jupp, my X470/Ryzen7 2700X/RX580 also crashes on me time by time. I think the RX580 is the reason:
Sep 10 09:43:10 rh050 kernel: [ 4404.339863] pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0
Sep 10 09:43:10 rh050 kernel: [ 4404.339876] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Sep 10 09:43:10 rh050 kernel: [ 4404.339879] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001100/00006000
Sep 10 09:43:10 rh050 kernel: [ 4404.339881] pcieport 0000:00:03.1: AER: [ 8] Rollover
Sep 10 09:43:10 rh050 kernel: [ 4404.339883] pcieport 0000:00:03.1: AER: [12] Timeout
Sep 10 09:44:38 rh050 kernel: [ 4492.979566] pcieport 0000:00:03.1: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:00.0
Sep 10 09:44:38 rh050 kernel: [ 4492.979575] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Receiver ID)
Sep 10 09:44:38 rh050 kernel: [ 4492.979579] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00200000/04400000
Sep 10 09:44:38 rh050 kernel: [ 4492.979581] pcieport 0000:00:03.1: AER: [21] ACSViol (First)
Sep 10 09:44:38 rh050 kernel: [ 4492.979585] amdgpu 0000:0c:00.0: AER: can't recover (no error_detected callback)
Sep 10 09:44:38 rh050 kernel: [ 4492.979586] snd_hda_intel 0000:0c:00.1: AER: can't recover (no error_detected callback)
Sep 10 09:44:38 rh050 kernel: [ 4492.979605] pcieport 0000:00:03.1: AER: device recovery failed
Sep 10 09:44:38 rh050 kernel: [ 4492.990594] pcieport 0000:00:03.1: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:00:00.0
Sep 10 09:44:38 rh050 kernel: [ 4492.990601] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Receiver ID)
Sep 10 09:44:38 rh050 kernel: [ 4492.990604] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00200000/04400000
Sep 10 09:44:38 rh050 kernel: [ 4492.990606] pcieport 0000:00:03.1: AER: [21] ACSViol (First)
Sep 10 09:44:38 rh050 kernel: [ 4492.990609] amdgpu 0000:0c:00.0: AER: can't recover (no error_detected callback)
Sep 10 09:44:38 rh050 kernel: [ 4492.990610] snd_hda_intel 0000:0c:00.1: AER: can't recover (no error_detected callback)
Sep 10 09:44:38 rh050 kernel: [ 4492.990621] pcieport 0000:00:03.1: AER: device recovery failed
Sep 10 09:44:49 rh050 kernel: [ 4503.189629] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=34669, emitted seq=34671
Sep 10 09:44:49 rh050 kernel: [ 4503.189730] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1642, emitted seq=1643
Sep 10 09:44:49 rh050 kernel: [ 4503.189832] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:44:49 rh050 kernel: [ 4503.189846] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Sep 10 09:44:49 rh050 kernel: [ 4503.189849] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:44:49 rh050 kernel: [ 4503.189948] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:44:49 rh050 kernel: [ 4503.189951] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:44:59 rh050 kernel: [ 4503.189953] [drm] Bailing on TDR for s_job:83f6, as another already in progress
Sep 10 09:44:59 rh050 kernel: [ 4513.429441] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Sep 10 09:45:09 rh050 kernel: [ 4523.669346] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:45:plane-5] flip_done timed out
Sep 10 09:45:10 rh050 kernel: [ 4524.273536] amdgpu 0000:0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
Sep 10 09:45:10 rh050 kernel: [ 4524.273619] [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
Sep 10 09:45:10 rh050 kernel: [ 4524.548390] cp is busy, skip halt cp
Sep 10 09:45:10 rh050 kernel: [ 4524.823113] rlc is busy, skip halt rlc
Sep 10 09:45:10 rh050 kernel: [ 4524.824133] amdgpu 0000:0c:00.0: GPU BACO reset
Sep 10 09:45:11 rh050 kernel: [ 4525.125145] amdgpu 0000:0c:00.0: GPU reset succeeded, trying to resume
Sep 10 09:45:11 rh050 kernel: [ 4525.126894] [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
Sep 10 09:45:11 rh050 kernel: [ 4525.126906] [drm] VRAM is lost due to GPU reset!
Sep 10 09:45:11 rh050 kernel: [ 4525.453490] amdgpu 0000:0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
Sep 10 09:45:11 rh050 kernel: [ 4525.453561] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v8_0> failed -110
Sep 10 09:45:11 rh050 kernel: [ 4525.453593] amdgpu 0000:0c:00.0: GPU reset(1) failed
Sep 10 09:45:11 rh050 kernel: [ 4525.453597] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453599] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453603] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453604] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453607] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453608] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453609] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453613] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453615] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453616] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453618] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453619] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453620] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453620] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453621] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453623] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453628] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453630] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453631] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453636] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453638] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453642] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453643] amdgpu 0000:0c:00.0: GPU reset end with ret = -110
Sep 10 09:45:11 rh050 kernel: [ 4525.453650] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453654] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453658] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453659] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453662] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453667] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453673] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453676] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453680] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453682] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453685] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453686] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453687] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453688] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453689] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453690] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453691] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453692] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453693] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453695] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453696] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453698] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453699] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453700] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453702] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453704] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453705] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453706] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453706] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453707] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453708] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453710] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453711] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453712] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453714] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453715] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453716] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453718] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453719] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453720] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453721] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453722] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453723] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453724] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453726] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453727] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453728] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453730] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453731] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453732] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453735] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453736] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453737] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453738] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453739] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453741] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453742] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453742] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453743] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453745] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453747] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453748] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453749] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453750] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453751] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453754] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453755] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453756] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453758] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453758] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453759] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453760] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453762] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453763] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453765] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453766] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453767] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453768] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453771] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453774] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453775] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453777] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453781] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453784] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453787] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.453791] [drm] Skip scheduling IBs!
Sep 10 09:45:11 rh050 kernel: [ 4525.454036] [drm] scheduler sdma0 is not ready, skipping
Sep 10 09:45:11 rh050 kernel: [ 4525.454037] [drm] scheduler sdma1 is not ready, skipping
Sep 10 09:45:11 rh050 kernel: [ 4525.454114] [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update BO_VA (-2)
Sep 10 09:45:11 rh050 kernel: [ 4525.454145] BUG: kernel NULL pointer dereference, address: 0000000000000008
Sep 10 09:45:11 rh050 kernel: [ 4525.454147] #PF: supervisor read access in kernel mode
Sep 10 09:45:11 rh050 kernel: [ 4525.454148] #PF: error_code(0x0000) - not-present page
Sep 10 09:45:11 rh050 kernel: [ 4525.454150] PGD 0 P4D 0
Sep 10 09:45:11 rh050 kernel: [ 4525.454153] Oops: 0000 [#1] SMP NOPTI
Sep 10 09:45:11 rh050 kernel: [ 4525.454156] CPU: 9 PID: 4151 Comm: Xorg Tainted: G OE 5.7.0-0.bpo.2-amd64 #1 Debian 5.7.10-1~bpo10+1
Sep 10 09:45:11 rh050 kernel: [ 4525.454157] Hardware name: System manufacturer System Product Name/PRIME X470-PRO, BIOS 5406 11/13/2019
Sep 10 09:45:11 rh050 kernel: [ 4525.454234] RIP: 0010:amdgpu_vm_sdma_commit+0x50/0x1f0 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.454237] Code: 8b 47 20 80 7f 10 00 48 8b a8 88 01 00 00 48 8b 47 08 4c 8d a0 e0 00 00 00 75 07 4c 8d a0 98 01 00 00 49 8b 44 24 10 8b 55 08 <48> 8b 40 08 48 8d 78 88 85 d2 0f 84 42 01 00 00 48 8b 40 90 48 89
Sep 10 09:45:11 rh050 kernel: [ 4525.454239] RSP: 0018:ffffaeb301cebb50 EFLAGS: 00010246
Sep 10 09:45:11 rh050 kernel: [ 4525.454240] RAX: 0000000000000000 RBX: ffffaeb301cebba0 RCX: 0000000000108000
Sep 10 09:45:11 rh050 kernel: [ 4525.454242] RDX: 0000000000000080 RSI: ffffaeb301cebc48 RDI: ffffaeb301cebba0
Sep 10 09:45:11 rh050 kernel: [ 4525.454243] RBP: ffff9da25c513de8 R08: ffff9da22b80e6c8 R09: 0000000000000000
Sep 10 09:45:11 rh050 kernel: [ 4525.454244] R10: 000000000000007d R11: 0000000000000000 R12: ffff9da2727d8198
Sep 10 09:45:11 rh050 kernel: [ 4525.454245] R13: ffffaeb301cebc48 R14: 0000000000107600 R15: 0000000000000002
Sep 10 09:45:11 rh050 kernel: [ 4525.454247] FS: 00007fc5e6855a80(0000) GS:ffff9da27ea40000(0000) knlGS:0000000000000000
Sep 10 09:45:11 rh050 kernel: [ 4525.454248] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 10 09:45:11 rh050 kernel: [ 4525.454249] CR2: 0000000000000008 CR3: 00000007f5370000 CR4: 00000000003406e0
Sep 10 09:45:11 rh050 kernel: [ 4525.454250] Call Trace:
Sep 10 09:45:11 rh050 kernel: [ 4525.454327] amdgpu_vm_bo_update_mapping+0x1d4/0x200 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.454403] amdgpu_vm_clear_freed+0xe8/0x230 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.454477] amdgpu_gem_va_ioctl+0x3c4/0x4d0 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.454551] ? amdgpu_gem_va_map_flags+0x60/0x60 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.454567] drm_ioctl_kernel+0xac/0xf0 [drm]
Sep 10 09:45:11 rh050 kernel: [ 4525.454583] drm_ioctl+0x201/0x3a0 [drm]
Sep 10 09:45:11 rh050 kernel: [ 4525.454655] ? amdgpu_gem_va_map_flags+0x60/0x60 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.454725] amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.454730] ksys_ioctl+0x86/0xc0
Sep 10 09:45:11 rh050 kernel: [ 4525.454732] __x64_sys_ioctl+0x16/0x20
Sep 10 09:45:11 rh050 kernel: [ 4525.454736] do_syscall_64+0x52/0x170
Sep 10 09:45:11 rh050 kernel: [ 4525.454740] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep 10 09:45:11 rh050 kernel: [ 4525.454742] RIP: 0033:0x7fc5e6f6f427
Sep 10 09:45:11 rh050 kernel: [ 4525.454744] Code: 00 00 90 48 8b 05 69 aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 aa 0c 00 f7 d8 64 89 01 48
Sep 10 09:45:11 rh050 kernel: [ 4525.454745] RSP: 002b:00007ffe16824678 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Sep 10 09:45:11 rh050 kernel: [ 4525.454747] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc5e6f6f427
Sep 10 09:45:11 rh050 kernel: [ 4525.454748] RDX: 00007ffe168246c0 RSI: 00000000c0286448 RDI: 000000000000000e
Sep 10 09:45:11 rh050 kernel: [ 4525.454749] RBP: 00007ffe168246c0 R08: 0000000107600000 R09: 000000000000000e
Sep 10 09:45:11 rh050 kernel: [ 4525.454750] R10: 0000000000000044 R11: 0000000000000246 R12: 00000000c0286448
Sep 10 09:45:11 rh050 kernel: [ 4525.454751] R13: 000000000000000e R14: 0000000000000002 R15: 000056228fa96960
Sep 10 09:45:11 rh050 kernel: [ 4525.454753] Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver bnep bluetooth drbg ansi_cprng ecdh_generic ecc vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) parport_pc ppdev lp parport nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc efivarfs fuse nls_ascii nls_cp437 vfat fat pktcdvd snd_hda_codec_realtek edac_mce_amd amdgpu snd_hda_codec_generic ledtrig_audio gpu_sched snd_hda_codec_hdmi kvm_amd ttm snd_hda_intel drm_kms_helper snd_intel_dspcfg ftdi_sio joydev eeepc_wmi cec asus_wmi kvm usbserial evdev snd_hda_codec drm battery snd_hda_core sparse_keymap irqbypass rfkill snd_hwdep video snd_pcm wmi_bmof efi_pstore pcspkr snd_timer efivars ccp snd sp5100_tco mxm_wmi k10temp watchdog mfd_core soundcore rng_core button acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic algif_skcipher af_alg dm_crypt dm_mod sr_mod cdrom uas usb_storage sg hid_generic usbhid hid sd_mod crc32_pclmul crc32c_intel ghash_clmulni_intel ohci_pci aesni_intel ahci libaes libahci xhci_pci crypto_simd xhci_hcd
Sep 10 09:45:11 rh050 kernel: [ 4525.454790] ohci_hcd ehci_pci libata ehci_hcd igb cryptd glue_helper scsi_mod nvme i2c_piix4 usbcore i2c_algo_bit nvme_core dca ptp pps_core t10_pi crc_t10dif crct10dif_generic crct10dif_pclmul usb_common crct10dif_common wmi gpio_amdpt gpio_generic
Sep 10 09:45:11 rh050 kernel: [ 4525.454802] CR2: 0000000000000008
Sep 10 09:45:11 rh050 kernel: [ 4525.454804] ---[ end trace f9443a0822a20086 ]---
Sep 10 09:45:11 rh050 kernel: [ 4525.676451] RIP: 0010:amdgpu_vm_sdma_commit+0x50/0x1f0 [amdgpu]
Sep 10 09:45:11 rh050 kernel: [ 4525.676455] Code: 8b 47 20 80 7f 10 00 48 8b a8 88 01 00 00 48 8b 47 08 4c 8d a0 e0 00 00 00 75 07 4c 8d a0 98 01 00 00 49 8b 44 24 10 8b 55 08 <48> 8b 40 08 48 8d 78 88 85 d2 0f 84 42 01 00 00 48 8b 40 90 48 89
Sep 10 09:45:11 rh050 kernel: [ 4525.676456] RSP: 0018:ffffaeb301cebb50 EFLAGS: 00010246
Sep 10 09:45:11 rh050 kernel: [ 4525.676458] RAX: 0000000000000000 RBX: ffffaeb301cebba0 RCX: 0000000000108000
Sep 10 09:45:11 rh050 kernel: [ 4525.676459] RDX: 0000000000000080 RSI: ffffaeb301cebc48 RDI: ffffaeb301cebba0
Sep 10 09:45:11 rh050 kernel: [ 4525.676460] RBP: ffff9da25c513de8 R08: ffff9da22b80e6c8 R09: 0000000000000000
Sep 10 09:45:11 rh050 kernel: [ 4525.676461] R10: 000000000000007d R11: 0000000000000000 R12: ffff9da2727d8198
Sep 10 09:45:11 rh050 kernel: [ 4525.676462] R13: ffffaeb301cebc48 R14: 0000000000107600 R15: 0000000000000002
Sep 10 09:45:11 rh050 kernel: [ 4525.676464] FS: 00007fc5e6855a80(0000) GS:ffff9da27ea40000(0000) knlGS:0000000000000000
Sep 10 09:45:11 rh050 kernel: [ 4525.676465] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 10 09:45:11 rh050 kernel: [ 4525.676466] CR2: 0000000000000008 CR3: 00000007f5370000 CR4: 00000000003406e0
Sep 10 09:45:13 rh050 hddtemp[4090]: /dev/sda: CT500MX500SSD1: 33 C
Sep 10 09:45:13 rh050 hddtemp[4090]: /dev/sdb: Crucial_CT1050MX300SSD1: 26 C
Sep 10 09:45:13 rh050 hddtemp[4090]: /dev/sdc: Crucial_CT512MX100SSD1: 31 C
Sep 10 09:45:13 rh050 hddtemp[4090]: /dev/sde: CT2000MX500SSD1: 33 C
Sep 10 09:45:13 rh050 hddtemp[4090]: /dev/sdf: WDC WD4001FFSX-68JNUN0: 39 C
Sep 10 09:45:21 rh050 kernel: [ 4535.701511] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:45:21 rh050 kernel: [ 4535.701602] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=34671, emitted seq=34671
Sep 10 09:45:21 rh050 kernel: [ 4535.701692] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0
Sep 10 09:45:21 rh050 kernel: [ 4535.701783] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:45:21 rh050 kernel: [ 4535.701784] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:45:21 rh050 kernel: [ 4535.701790] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:45:31 rh050 kernel: [ 4535.701792] [drm] Bailing on TDR for s_job:4cd, as another already in progress
Sep 10 09:45:31 rh050 kernel: [ 4545.941531] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:45:31 rh050 kernel: [ 4545.941622] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:45:31 rh050 kernel: [ 4545.941630] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:45:42 rh050 kernel: [ 4545.941632] [drm] Bailing on TDR for s_job:4ce, as another already in progress
Sep 10 09:45:42 rh050 kernel: [ 4556.181492] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:45:42 rh050 kernel: [ 4556.181583] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:45:42 rh050 kernel: [ 4556.181591] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:45:52 rh050 kernel: [ 4556.181594] [drm] Bailing on TDR for s_job:4cf, as another already in progress
Sep 10 09:45:52 rh050 kernel: [ 4566.421393] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:45:52 rh050 kernel: [ 4566.421485] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:45:52 rh050 kernel: [ 4566.421493] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:46:02 rh050 kernel: [ 4566.421495] [drm] Bailing on TDR for s_job:4d0, as another already in progress
Sep 10 09:46:02 rh050 kernel: [ 4576.661299] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:46:02 rh050 kernel: [ 4576.661390] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:46:02 rh050 kernel: [ 4576.661398] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:46:12 rh050 kernel: [ 4576.661401] [drm] Bailing on TDR for s_job:4d1, as another already in progress
Sep 10 09:46:12 rh050 kernel: [ 4586.901180] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:46:12 rh050 kernel: [ 4586.901272] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:46:12 rh050 kernel: [ 4586.901280] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:46:23 rh050 kernel: [ 4586.901283] [drm] Bailing on TDR for s_job:4d2, as another already in progress
Sep 10 09:46:23 rh050 kernel: [ 4597.141105] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:46:23 rh050 kernel: [ 4597.141197] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:46:23 rh050 kernel: [ 4597.141204] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:46:33 rh050 kernel: [ 4597.141207] [drm] Bailing on TDR for s_job:4d3, as another already in progress
Sep 10 09:46:33 rh050 kernel: [ 4607.381004] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:46:33 rh050 kernel: [ 4607.381097] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:46:33 rh050 kernel: [ 4607.381104] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:46:43 rh050 kernel: [ 4607.381106] [drm] Bailing on TDR for s_job:4d4, as another already in progress
Sep 10 09:46:43 rh050 kernel: [ 4617.620748] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:46:43 rh050 kernel: [ 4617.620840] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:46:43 rh050 kernel: [ 4617.620847] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 09:46:53 rh050 kernel: [ 4617.620850] [drm] Bailing on TDR for s_job:4d5, as another already in progress
Sep 10 09:46:53 rh050 kernel: [ 4627.860707] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=1643, emitted seq=1643
Sep 10 09:46:53 rh050 kernel: [ 4627.860799] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 4151 thread Xorg:cs0 pid 4375
Sep 10 09:46:53 rh050 kernel: [ 4627.860807] amdgpu 0000:0c:00.0: GPU reset begin!
Sep 10 10:00:13 rh050 hddtemp[4090]: /dev/sda: CT500MX500SSD1: 33 C
Sep 10 10:00:13 rh050 hddtemp[4090]: /dev/sdb: Crucial_CT1050MX300SSD1: 26 C
Sep 10 10:00:13 rh050 hddtemp[4090]: /dev/sdc: Crucial_CT512MX100SSD1: 39 C
Sep 10 10:00:13 rh050 hddtemp[4090]: /dev/sde: CT2000MX500SSD1: 33 C
Sep 10 10:00:13 rh050 hddtemp[4090]: /dev/sdf: WDC WD4001FFSX-68JNUN0: 39 CSame issue before with ASCII. Does not happen every day, more once a month, but its not nice. Looks like the underground processes like hddtemp still are working, but the computer isn't usable any more, no reaction to mouse and keyboard.
I don't blame Beowulf, its a HW problem.
rolfie
#905 Desktop and Multimedia » [Solved] Mesa update for Cinnamon in Beowulf » 2020-09-09 20:46:21
- rolfie
- Replies: 6
HW: ASUS X570 Pro MC, Ryzen 7 3700X CPU, RX 5500XT graphics card.
SW: Beowulf on backports kernel 5.7.0.2, firmware-amd-graphics from backport installed, the firmware files are successfully loaded during boot.
Problem: Cinnamon starts in SW rendering mode. A Chimaera installation on the same HW starts Cinnamon in 3D mode.
When I compare the Chimaera kernel 5.7.0.3 is a bit newer, but I guess the issue is Mesa. Beowulf brings 18.3, there is nothing newer in backports. Chimaera runs on 20.1. I remember reading some notes that the NAVI chipsets require at least Mesa 19.3., so the Beowulf version most likely is not sufficient.
Before I try to install the package from Ceres/Chimaera on Beowulf: what do I have to consider? What's the best approach? Adding the Ceres repo to the sources list and an apt -t ceres install .... or directly downloading the two packages installed and to use dpkg -i ...?
Thanks for a heads up, rolfie
#906 Re: Desktop and Multimedia » evolution email install » 2020-09-06 09:27:28
I am using evolution on Beowulf with Mate desktop, works. Just tried on a new computer with Beowulf and Cinnamon desktop, install is fine too.
I would first of all look at at the free space on your partitions, and then possibly at user rights.
rolfie
#907 Re: Other Issues » [Solved] System log questions » 2020-09-05 17:49:18
Thank you for your feedback. Got a solution that serves me well.
On my Mate box:
# dpkg -S bin/mate-system-log
mate-utils: /usr/bin/mate-system-log
# apt-file search mate-system-log
bash: apt-file: Kommando nicht gefunden.After some research I learned that apt-file isn't installed by default. Well, dpkg did the job, I didn't care to install that package.
Installed mate-utils and saw that a lot of superflous stuff is installed. I can confirm mate-system-log works with Cinnamon (with a suitable policy), and I saw the usual list of logs I had under Mate desktop.
But finally removed the package again after successfully trying Marjories hint. I was looking in the left menu for a configuration option, and missed the open in the cog in box, thats not really intuitive. That setup works for me, finally got the list I want. Though I saw a side effect: every second Open opened my home instead of /var/log. Is that something special on my box or a bug?
Have a nice evening, rolfie
Note: looks like the package search in Debian is more powerful than the one in Devuan. I need to remember next time.
#908 Other Issues » [Solved] System log questions » 2020-09-04 21:18:05
- rolfie
- Replies: 7
Just working an a new PC with Beowulf and Cinnamon as desktop.
Got gnome-system-log installed, and do not like it. It just shows syslog, auth and 2 other uninteresting logs. From my Mate desktops with mate-system-log I am used to see the complete contents of /var/log. Well, tried to install mate-system-log on the Cinnamon system, and failed. Error: package mate-system-log can't be found.
A closer look showed that on my Mate systems I have an application in /usr/bin/mate-system-log, but I have no idea to which package this application belongs to. Searching in dpkg.log did not help. Search in Synaptic with all available options also did not help. Looked at the files that belong to Mate-desktop-environment*..., no trace of the mate-system-log.
How can I find out in which package this application is hidden?
Thanks, rolfie
#909 Re: Desktop and Multimedia » SOLVED: Thanks and old Cinnamon version » 2020-08-26 17:57:41
As lang as you stay with ASCII you will have 3.2.7. If you move to Beowulf, you will get 3.8.8.
rolfie
#910 Re: Other Issues » EFI trouble » 2020-08-16 19:20:15
Once booted up efibootmgr -v reported an error. After fiddling around for a while I ran
grub-install /dev/sdato try and ensure that it would still boot. This was ok and does still boot via grub as expected.
Wonder why this worked. This is CSM style, not EFI. To my knowledge you have to use something like
# grub-install --bootloader-id=devuanas I use to generate a devuan entry (no secure boot).
efibootmgr (with or with "-v") now reports
efibootmgr No BootOrder is set; firmware will attempt recoveryHowever, as a side effect of all this, the grub entry for Xen now works and I am posting this with Chimaera as Dom0 under Xen.
Doesn't tell me anything, don't use Xen.
The directory /sys/firmware/efi/efivars/ exists, but is empty.
Is the directory mounted?
As everything seems to be working, it is tempting to leave it alone. But where is the fun in that!
It would be nice if efibootmgr agreed with the firmware screen (what is that called, it can't be the BIOS screen, can it?)In writing this an obvious point becomes clear. If I am running Devuan under Xen, then access to EFI stuff may be impaired. Having booted on the bare metal,
efibootmgr BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000,0004,0002 Boot0000* debian Boot0002* Hard Drive Boot0004* zenefibootmgr -v BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000,0004,0002 Boot0000* debianCould not parse device path: Invalid argumentIt is interesting that it couldn't parse option 0000 as that is the one that is actually booted.
Also the directory /sys/firmware/efi/efivars/ now contains the expected stuff.
Setting up stuff seems to be easier on the firmware screen than using efibootmgr as selecting the the parts of the path to the boot image is easier when there is a choice of options rather than entering a complex command line. The first part of the path was incomprehensible to me, but there was a choice of one (disk?) and from there the options were obvious.
What do you mean by "firmware screen"? The bios? On my 3 latest ASUS board with AMI bios I haven't got any chance to modify any settings but the boot order, if any.
Confused, rolfie
#911 Re: Hardware & System Configuration » BDRE mounted read only » 2020-08-14 21:30:53
Many months later:
Learned that I have to format the disk as dvdrw and with UDF2.01. Then mounting RW works.
rolfie
#912 Re: Desktop and Multimedia » Cannot install VLC » 2020-08-14 19:06:40
Dependency hell.
We could reply: What the hell are you doing here?
Before you try to clean out your installation you better read some literature about sources.list and Franken-Debian. Here are some useful links.
You could start on the main page of Devuan.org: https://devuan.org/,
about installation: https://devuan.org/os/install,
about releases: https://devuan.org/os/releases
about sources.list recommendations: https://devuan.org/os/packages
about FrankenDebian: https://wiki.debian.org/DontBreakDebian
HTH, rolfie
Edith: added link to the Debian Wiki.
#913 Re: Desktop and Multimedia » amdgpu-pro drivers » 2020-08-14 18:55:53
Got a RX580 installed on a Ryzen 2700X computer. Worked fine with ASCII and now with Beowulf with KMS driver (included in the kernel) and firmware. You need non-free added to the sources.list, you install amd64-microcode and firmware-amd-graphics. On ASCII you better pull firmware-amd-graphics from backports.
If you need some guidance, check out the Devuan.org website, there you will find some instructions how to set the sources.list.
No fiddling required with amdgpu-pro.
rolfie
#914 Re: Installation » How do I install CUPS? » 2020-08-12 18:47:03
When Synaptic is open you can't install anything with apt(-get).
#915 Re: Installation » How do I install CUPS? » 2020-08-12 17:54:03
# apt install cups
#916 Re: Hardware & System Configuration » Amd Radeon RX 5600 XT » 2020-08-11 15:36:09
To encourage you, please read https://dev1galaxy.org/viewtopic.php?id=3358.
rolfie
#917 Re: Other Issues » Install grub so that EFI directory is 'devuan' » 2020-08-09 19:16:36
The following trick may do what you want:
1.) apt remove grub-efi-amd64-signed
2.) grub-install --bootloader-id=devuan
Worked in my Chimaera VM.
#918 Re: Other Issues » Install grub so that EFI directory is 'devuan' » 2020-08-09 07:20:50
I can confirm that also Chimaera (in a VM) has the same behaviour. What easily worked under Beowulf is no more working with the testing/unstable stuff.
Needs a closer look.
rolfie
#919 Re: Other Issues » Install grub so that EFI directory is 'devuan' » 2020-08-08 21:06:36
That will work if you don't use Secure Boot. But you still will have a debian and a devuan EFI directory.
Use the efibootmgr to boot the devuan entry. If that works, you can delete the debian entry with the file manager.
rolfie
#920 Re: Hardware & System Configuration » [ SOLVED ] cant run command from commandsline » 2020-08-04 16:06:15
Got two PC here with Beowulf installed from scratch, both with Mate desktop. No ash, just bash and bash-completion are installed. Both work fine whenever calling Mate terminal as user or with pkexec as root. Same on the desktop opening the (Mate-)terminal.
Also got two Beowulf VMs running in Virtual Box. One is based on an ASCII upgrade with Mate. Same setup as above, works like a charm w/o ash. The other one is a native Beowulf with Cinnamon. The I only have xterm, but that also works fine.
rolfie
#921 Re: Hardware & System Configuration » [ SOLVED ] cant run command from commandsline » 2020-08-02 19:25:07
I m sitting on fresh installed Beowulf. No ash, just bash, dash and bash-completion. No problems.
Have you got bash-completion installed?
I am not using the alias.
rolfie
#922 Re: Hardware & System Configuration » Shutdown delay due to Veracrypt » 2020-08-02 19:18:05
Checked with my ASCII installation on the same PC. Had to update Veracrypt to run the same version first. There I do not see the shutdown delay I have with Beowulf. Something is different here.
rolfie
#923 Re: Hardware & System Configuration » LibPAM-TMPDIR Causes VeraCrypt Mounting Problems » 2020-08-02 16:47:42
There are several options I know how to mount a Veracrypt volume.
1.) Veracrypt GUI
2.) Veracrypt cli interface
3.) cryptsetup
I use 1 and 2. All in common is that you have to tell the sw which container to open and where to mount it. No idea what LibPAM-TMPDIR does or requires.
If you use 2 you will see the mounted container(s) in the GUI. I am not astonished that a container opened with cryptsetup isn't seen by the GUI.
rolfie
#924 Re: Installation » backports » 2020-07-30 16:23:38
I do consequently use the backports kernels on all my machines. Did that from Squeeze onward for various generations of hardware. Never had any issues.
And every now and then I used bugfixes from backports. But thats rare.
rolfie
#925 Re: Installation » Devuan Chimaer as guest on Virtualbox: any known issues? » 2020-07-27 20:20:24
VirtualBox is a buggy pile of shite which is slower than QEMU/KVM and the developers have a tendency of covering up and ignoring security issues.
See also https://bugs.debian.org/cgi-bin/bugrepo … bug=794466
And it relies on blobs.
Maybe you're right. But for me VBox does what I expect it to do. I can pass through USB drives w/o any problem, UEFI mode is sort of crap but available. I can boot a VM from an iso, ....
Tried the same with qemu/kvm and gave up when bold promoters of qemu/kvm didn't have any advise how to solve my issues. I guess this highly promoted piece of SW still requires a lot of brains to really make it a competition for VBox.
rolfie
Board footer
