Jump to content

SUBIECTE NOI
« 1 / 5 »
RSS
Alternativa la manea

Taxarea vacilor in Danemarca si..

Oamenii fara Whatsapp

Pompe apa fotovoltaice.
 Valori ok fibra?

recomandare smartwatch copil

Viata traita asa cum vrei tu vs v...

Melodie dance veche
 RIP Shifty Shellshock

Daca nu ar conta salariul, ce mes...

Racordare la apa termosemineu

Mi-am luat 4x4 si vreau sa-l testez
 Recomandare laptop cu luminozitat...

Cautarea pe google android nu merge

Caut serviciu serios de captura v...

Frauda magazin online
 

Linux Manjaro - topic general

- - - - -
  • Please log in to reply
706 replies to this topic

#541
lucifer76

lucifer76

    Bashtan

  • Grup: Moderators
  • Posts: 32,574
  • Înscris: 13.06.2007

Quote

lucifer@lucifer-laptop:~$ downgrader kdenlive
Downgrade package: Kdenlive
1: kdenlive-19.08.1-1  (from ALA)
2: kdenlive-19.08.0-2  [installed]
3: kdenlive-19.08.0-1  (from ALA)
4: kdenlive-19.07.90-1https://archive.archlinux.org/packages/k/kdenlive/kdenlive-19.07.90-1-x86_64.pkg.tar.xz  (from ALA)
5: kdenlive-19.07.80-1https://archive.archlinux.org/packages/k/kdenlive/kdenlive-19.07.80-1-x86_64.pkg.tar.xz  (from ALA)
6: kdenlive-19.04.3-1  (from ALA)
7: kdenlive-19.04.2-2  (from ALA)
8: kdenlive-19.04.2-1  (from ALA)
9: kdenlive-19.04.1-1  (from ALA)
10: kdenlive-19.04.0-3  (from ALA)
11: kdenlive-19.04.0-2  (from ALA)
12: kdenlive-19.04.0-1  (from ALA)
13: kdenlive-19.03.90-1https://archive.archlinux.org/packages/k/kdenlive/kdenlive-19.03.90-1-x86_64.pkg.tar.xz  (from ALA)
14: kdenlive-19.03.80-1https://archive.archlinux.org/packages/k/kdenlive/kdenlive-19.03.80-1-x86_64.pkg.tar.xz  (from ALA)
15: kdenlive-18.12.3-1  (from ALA)
16: kdenlive-18.12.2-1  (from ALA)
17: kdenlive-18.12.1-1  (from ALA)
>> Please enter package number, [q] to quit


#542
spps2019

spps2019

    Member

  • Grup: Validating
  • Posts: 445
  • Înscris: 08.08.2019
da nu-i mai la indemana sa foloseasca acelasi kernel 4.19.x?

#543
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
Am ramas la manjaro-kde-18.0.4 pe kernel 4.19.77-1 si Kdenlive 19.08.1. care s-a upgradat cred ca din cauza ca am schimbat repositories. Sunt ok atat pe laptop cat si pe un pc aceste versiuni unde imi functioneaza accelerarea la export in kdenlive pe intel QS(vaapi) iar pe laptop cu nvenc(pe o placa k2000m).

Referitor la encodarea cu gpu amd(un r7 260x) am dubii daca a functionat vreodata deoarece mi se pare ca se inverseaza aleatoriu vaapi_device=/dev/dri/renderD128 cu  vaapi_device=/dev/dri/renderD129(zic asta fiindca am facut cateva encodari cu FFMpeg si uneori am viteza mai buna pe vaapi_device=/dev/dri/renderD128, alteori pe vaapi_device=/dev/dri/renderD129), deci nici nu mai stiu daca D128 e pt intel si D129 e pt amd.

Edited by c_anicai, 08 October 2019 - 21:45.


#544
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
Pe celalalt pc cu Manjaro kde 18.0.4 la care nu am modificat lista de repositories kernelul a ramas default la 4.19.69-1 si Kdenlive 19.08.0 desi am dat si pe ala update.

#545
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
Update-ul de astazi a adus in Manjaro vesiunea de 19.08.2 la Kdenlive:

Am repositories modificat:

##
## Manjaro Linux default mirrorlist
## Generated on 2018-02-17 13:32
##
## Please use 'pacman-mirrors -f [NUMBER]' to modify mirrorlist
## Edit list: sudo gedit /etc/pacman.d/mirrorlist
##
## Country : Germany
Server = https://mirror.philp...ble/$repo/$arch
## Country : Denmark
Server = https://www.uex.dk/p...ble/$repo/$arch
## Country : United_Kingdom
Server = http://manjaro.mirro...ble/$repo/$arch
## Country : Poland
Server = https://mirror.tucho...ble/$repo/$arch
## Country : Germany
Server = http://mirror.ragene...ble/$repo/$arch
## Country : Netherlands
Server = https://mirror.koddo...ble/$repo/$arch
## Country : Netherlands
Server = https://manjaro.mirr...ble/$repo/$arch
## Country : Germany
Server = https://mirror.alpix...ble/$repo/$arch
## Country : Netherlands
Server = https://mirror.neost...ble/$repo/$arch
## Country : United_Kingdom
Server = https://www.mirrorse...ble/$repo/$arch
#----->snipped

#546
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
Referitor la drivere placa video amd, (un r7 260x) pe doua versiuni de kernel:


Pe versiunea 4.19.79-1, comanda: cat /sys/kernel/debug/dri/0/radeon_pm_info
imi da:
uvd disabled
vce disabled
power level AVG sclk: 30000 mclk: 150000


journalctl -b | grep radeon
Oct 18 09:21:43 i5-3470 kernel: [drm] radeon kernel modesetting enabled.
Oct 18 09:21:43 i5-3470 kernel: fb: switching to radeondrmfb from VESA VGA
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: GTT: 2048M 0x0000000040000000 - 0x00000000BFFFFFFF
Oct 18 09:21:43 i5-3470 kernel: [drm] radeon: 1024M of VRAM memory ready
Oct 18 09:21:43 i5-3470 kernel: [drm] radeon: 2048M of GTT memory ready.
Oct 18 09:21:43 i5-3470 kernel: [drm] radeon: dpm initialized
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: WB enabled
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff9baa3d3d3c00
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff9baa3d3d3c04
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff9baa3d3d3c08
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff9baa3d3d3c0c
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff9baa3d3d3c10
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000078d30 and cpu addr 0xffffbe5fc9438d30
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0xffff9baa3d3d3c18
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0xffff9baa3d3d3c1c
Oct 18 09:21:43 i5-3470 kernel: radeon 0000:01:00.0: radeon: using MSI.
Oct 18 09:21:43 i5-3470 kernel: [drm] radeon: irq initialized.
Oct 18 09:21:45 i5-3470 kernel: fbcon: radeondrmfb (fb0) is primary device
Oct 18 09:21:45 i5-3470 kernel: radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
Oct 18 09:21:45 i5-3470 kernel: [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0


Iar pe versiunea 5.2.21-1, comanda: cat /sys/kernel/debug/dri/0/radeon_pm_info
imi da:
default engine clock: 1075000 kHz
current engine clock: 299450 kHz
default memory clock: 1500000 kHz
current memory clock: 149990 kHz


journalctl -b | grep radeon
Oct 18 09:35:01 i5-3470 kernel: [drm] radeon kernel modesetting enabled.
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf07fffff
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xf7e00000 -> 0xf7e3ffff
Oct 18 09:35:01 i5-3470 kernel: fb0: switching to radeondrmfb from VESA VGA
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: vgaarb: deactivate vga console
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: No more image in the PCI ROM
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: GTT: 2048M 0x0000000040000000 - 0x00000000BFFFFFFF
Oct 18 09:35:01 i5-3470 kernel: [drm] radeon: 1024M of VRAM memory ready
Oct 18 09:35:01 i5-3470 kernel: [drm] radeon: 2048M of GTT memory ready.
Oct 18 09:35:01 i5-3470 kernel: [drm] radeon: dpm initialized
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: WB enabled
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x0000000081ab3d4f
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0x00000000cd1007a6
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0x000000005af4b8c9
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x0000000016436cb1
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0x00000000d3054244
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000078d30 and cpu addr 0x00000000d3b1ee6f
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0x00000000c79cb30a
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0x00000000f3de4d90
Oct 18 09:35:01 i5-3470 kernel: radeon 0000:01:00.0: radeon: using MSI.
Oct 18 09:35:01 i5-3470 kernel: [drm] radeon: irq initialized.
Oct 18 09:35:02 i5-3470 kernel: fbcon: radeondrmfb (fb0) is primary device
Oct 18 09:35:02 i5-3470 kernel: radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
Oct 18 09:35:02 i5-3470 kernel: [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0
Oct 18 09:39:04 i5-3470 kernel: radeon 0000:01:00.0: ring 5 stalled for more than 10150msec
Oct 18 09:39:04 i5-3470 kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000002 last fence id 0x0000000000000006 on ring 5)
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: couldn't schedule ib
Oct 18 09:39:05 i5-3470 kernel: [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)!
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: Saved 11620 dwords of commands on ring 0.
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: GPU softreset: 0x00000008
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS=0xA0003028
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS2=0x50000008
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE2=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE3=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS=0x20000040
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS2=0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STAT = 0x80010200
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT1 = 0x00000c00
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT2 = 0x00010000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT3 = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_BUSY_STAT = 0x00000002
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STALLED_STAT1 = 0x00000001
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STATUS = 0x80000023
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_BUSY_STAT = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STATUS = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00010001
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS=0x00003028
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS2=0x00000008
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE2=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE3=0x00000006
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS=0x20000040
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS2=0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STAT = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT1 = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT2 = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT3 = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_BUSY_STAT = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STALLED_STAT1 = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STATUS = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_BUSY_STAT = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STATUS = 0x00000000
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Oct 18 09:39:05 i5-3470 kernel: [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed
Oct 18 09:39:05 i5-3470 kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: WB enabled
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x0000000081ab3d4f
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0x00000000cd1007a6
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0x000000005af4b8c9
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x0000000016436cb1
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0x00000000d3054244
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000078d30 and cpu addr 0x00000000d3b1ee6f
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0x00000000c79cb30a
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0x00000000f3de4d90
Oct 18 09:39:05 i5-3470 kernel: [drm:radeon_vce_ring_test [radeon]] *ERROR* radeon: ring 6 test failed
Oct 18 09:39:05 i5-3470 kernel: radeon 0000:01:00.0: failed initializing VCE (-110).
Oct 18 09:39:05 i5-3470 kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
Oct 18 09:39:06 i5-3470 kernel: [drm:cik_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
Oct 18 09:39:06 i5-3470 kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-110).
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: couldn't schedule ib
Oct 18 09:39:06 i5-3470 kernel: [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)!
Oct 18 09:39:06 i5-3470 kernel: WARNING: CPU: 3 PID: 1500 at drivers/gpu/drm/radeon/radeon_object.c:84 radeon_ttm_bo_destroy+0xf1/0x100 [radeon]
Oct 18 09:39:06 i5-3470 kernel: Modules linked in: ccm amdgpu gpu_sched squashfs loop rtl8xxxu arc4 intel_rapl rtl8192cu x86_pkg_temp_thermal intel_powerclamp rtl_usb CoreTemp rtl8192c_common kvm_intel rtlwifi kvm mac80211 irqbypass radeon crct10dif_pclmul input_leds crc32_pclmul mousedev fuse cfg80211 ghash_clmulni_intel snd_hda_codec_realtek snd_hda_codec_generic i2c_algo_bit tpm_infineon hid_generic ledtrig_audio snd_hda_codec_hdmi ttm snd_hda_intel aesni_intel snd_hda_codec aes_x86_64 uas crypto_simd drm_kms_helper hp_wmi usb_storage mei_hdcp mei_wdt snd_hda_core cryptd usbhid snd_hwdep glue_helper sparse_keymap iTCO_wdt rfkill wmi_bmof tpm_tis intel_cstate iTCO_vendor_support intel_uncore drm hid snd_pcm intel_rapl_perf tpm_tis_core mei_me pcspkr i2c_i801 snd_timer e1000e agpgart psmouse mei snd lpc_ich wmi syscopyarea soundcore tpm sysfillrect sysimgblt fb_sys_fops pcc_cpufreq rng_core evdev ie31200_edac mac_hid uinput crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 sr_mod cdrom
Oct 18 09:39:06 i5-3470 kernel: RIP: 0010:radeon_ttm_bo_destroy+0xf1/0x100 [radeon]
Oct 18 09:39:06 i5-3470 kernel:  radeon_bo_unref+0x1a/0x30 [radeon]
Oct 18 09:39:06 i5-3470 kernel:  radeon_gem_object_free+0x33/0x50 [radeon]
Oct 18 09:39:06 i5-3470 kernel:  radeon_drm_ioctl+0x49/0x80 [radeon]
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: GPU softreset: 0x00000008
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS=0xA0003028
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS2=0x50000008
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE2=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE3=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS=0x20000040
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS2=0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STAT = 0x84090200
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT1 = 0x00000c00
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT2 = 0x00010000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT3 = 0x00000400
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_BUSY_STAT = 0x00000002
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STALLED_STAT1 = 0x00000001
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STATUS = 0x80001023
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_BUSY_STAT = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STATUS = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00010001
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS=0x00003028
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS2=0x00000008
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE2=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   GRBM_STATUS_SE3=0x00000006
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS=0x20000040
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SRBM_STATUS2=0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STAT = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT1 = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT2 = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_STALLED_STAT3 = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_BUSY_STAT = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STALLED_STAT1 = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPF_STATUS = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_BUSY_STAT = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0:   CP_CPC_STATUS = 0x00000000
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Oct 18 09:39:06 i5-3470 kernel: [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed
Oct 18 09:39:06 i5-3470 kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: WB enabled
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x0000000081ab3d4f
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0x00000000cd1007a6
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0x000000005af4b8c9
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x0000000016436cb1
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0x00000000d3054244
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000078d30 and cpu addr 0x00000000d3b1ee6f
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0x00000000c79cb30a
Oct 18 09:39:06 i5-3470 kernel: radeon 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0x00000000f3de4d90
Oct 18 09:39:07 i5-3470 kernel: [drm:radeon_vce_ring_test [radeon]] *ERROR* radeon: ring 6 test failed
Oct 18 09:39:07 i5-3470 kernel: radeon 0000:01:00.0: failed initializing VCE (-110).
Oct 18 09:39:07 i5-3470 kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed
Oct 18 09:39:08 i5-3470 kernel: [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
Oct 18 09:39:08 i5-3470 kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 7 (-110).


Practic urmaresc sa activez  amd vce(sau in linux o fi echivalent vaapi), ceva idei ?

Edited by c_anicai, 18 October 2019 - 09:00.


#547
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
Amd vce de care ziceam in postarea anterioara este functional, nu trebuia sa fac nimic deoarece se activeaza doar cand il solicita softul de editare video dar nu m-am prins din prima. Deci am rezolvat.


Am o problema, nu reusesc sa instalez tv-maxe, nici yaourt, nici yay. Vreau laptopul sotiei sa-l trec pe Manjaro dar nu pot fara tv-maxe. Sotiei nu ii trebuie des acest laptop ca are unul mai mic si din cauza ca sta nefolosit  as fi vrut sa vad cum ruleaza Kdenlive pe o placa firepro m4000.

Edited by c_anicai, 27 October 2019 - 10:02.


#548
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 399,717
  • Înscris: 08.10.2015
yaourt nu mai e dezvoltat, tv-maxe nu stiu, yay inlocuieste yaourt (yay = yet another yaourt).

Specifica exact cum / de ce nu poti instala respectivele pachete. Nu am un Manjaro acum dar folosesc Arch care e parintele. Am impresia ca pui un yay care e mai vechi si care e compilat versus pacman < 5.2.0 si da conflict de dependinte. Asta se rezolva.Trebuie doar sa compilezi de mana yay, Descarci pachetul din AUR si folosesti makepkg pentru a compila ca user pachetul apoi pacman -U ca root sa il instalezi.

#549
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
La yay am eroarea asta care nu prea o inteleg:  target not found: pacman>=5.2
==> ERROR: 'pacman' failed to install missing dependencies.

Edit: yay a mers, mersi;

git clone https://aur.archlinux.org/yay-bin.git
cd yay-bin
makepkg -si
sudo pacman -U yay-bin*.tar.xz

Attached Files

  • Attached File  yay.png   75.35K   8 downloads

Edited by c_anicai, 27 October 2019 - 11:23.


#550
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 399,717
  • Înscris: 08.10.2015
sudo pacman -Syyuu
makepkg
sudo pacman -U yay-9.4.2-1-x86_64.pkg.tar.xz

Update la pachete si apoi dupa ce ai pacman 5.2.0 instalat compilezi yay si il instalezi.

tv-maxe e in AUR:
┌(ghost)─(Timberwolf)─(5.3.7-arch1-1-ARCH)
└─(~)─(3 files, 408KB)─ $ yay -Ss tv-maxe
aur/tv-maxe-git 0.11+r43.0906f69-1 (+8 0.00%)
	Watch TV channels on Linux.
┌(ghost)─(Timberwolf)─(5.3.7-arch1-1-ARCH)
└─(~)─(3 files, 408KB)─ $ yay -S aur/tv-maxe-git
:: Checking for conflicts...
:: Checking for inner conflicts...
[Repo: 30]  a52dec-0.7.4-10  libdvbpsi-1:1.3.3-1  libxpm-3.5.12-2  libdca-0.0.6-1  libebml-1.3.9-1  libmatroska-1.5.2-1  taglib-1.11.1-3  libmpcdec-1:0.1+r475-2  libupnp-1.6.25-1  libmpeg2-0.5.1-6  libtar-1.2.20-4  aribb24-1.0.3-2  vlc-3.0.8-1  recode-3.7.6-1  enca-1.19-3  libftdi-1.4-2  libusb-compat-0.1.5-2  lirc-1:0.10.1-2  libmng-2.0.3-2  aalib-1.4rc5-13  libxxf86dga-1.1.5-1  mpg123-1.25.12-1  rtmpdump-1:2.4.r96.fa8646d-5  libbs2b-3.1.0-6  mplayer-38139-1  libstdc++5-3.3.6-6  lib32-glibc-2.30-1  lib32-gcc-libs-9.2.0-2  libimagequant-2.12.5-1  python2-pillow-6.2.0-1
[Repo Make: 5]  python-markupsafe-1.1.1-1  python-beaker-1.11.0-1  python-mako-1.0.14-1  python-markdown-3.1.1-2  gobject-introspection-1.62.0-1
[Aur: 6]  lib32-libstdc++5-3.3.6-8  sopcast-3.2.6-2  gstreamer0.10-0.10.36-17  gstreamer0.10-base-0.10.36-11  gstreamer0.10-python-0.10.22-8  tv-maxe-git-0.11+r43.0906f69-1
==> Remove make dependencies after install? [y/N]

Nu l-am instalat ca nu il folosesc. Poti incerca sa vezi daca este okay. yaourt nu se mai gaseste in AUR poate in repo-urile oficiale de la Manjaro.

Edited by MembruAnonim, 27 October 2019 - 14:41.


#551
lucifer76

lucifer76

    Bashtan

  • Grup: Moderators
  • Posts: 32,574
  • Înscris: 13.06.2007
Tvmaxe nu mai e dezvoltat de mult timp. Stiu ca trebuia sa fac un artificiu ca sa porneasca.

#552
spps2019

spps2019

    Member

  • Grup: Validating
  • Posts: 445
  • Înscris: 08.08.2019
dbus python

#553
hidomuz

hidomuz

    Junior Member

  • Grup: Junior Members
  • Posts: 85
  • Înscris: 10.08.2019

Quote

Please replace: depends=('python2' 'pygtk' 'vlc' 'mplayer' 'libstdc++5' 'sopcast' 'gstreamer0.10-python' 'ffmpeg' 'python2-pillow') with: depends=('python2' 'pygtk' 'vlc' 'lib32-libstdc++5' 'sopcast' 'gstreamer0.10-python' 'ffmpeg' 'python2-pillow' 'python2-dbus')


#554
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
deocamdata n-am reusit, am incercat astea:
sudo yay -S aur/tv-maxe-git
yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory

git clone https://aur.archlinux.org/package-query.git
cd package-query
makepkg -si
==> ERROR: PKGBUILD does not exist
./autogen.sh
./configure

sudo pacman -S gstreamer
sudo pacman -S python2-dbus

sudo yay -S aur/tv-maxe-git
yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory

sudo pacman -R package-query
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: yaourt: removing package-query breaks dependency 'package-query>=1.8'




Edited by c_anicai, 28 October 2019 - 09:28.


#555
lucifer76

lucifer76

    Bashtan

  • Grup: Moderators
  • Posts: 32,574
  • Înscris: 13.06.2007
Sa nu muncesti degeaba, poate nici nu mai sunt canalele disponibile.

#556
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
Nu prea ma intereseaza cate canale sunt, sotia il are deja instalat pe Kubuntu  insa vreau Manjaro pe acel laptop din motiv de drivere gpu  ca sa-mi ruleze Kdenlive,
Tv-maxe incerc pe laptopul meu si doar daca imi reuseste voi pune Manjaro si pe asta.

Attached Files


Edited by c_anicai, 28 October 2019 - 10:15.


#557
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 399,717
  • Înscris: 08.10.2015
@c_anicai: libalpm.so.12 vine cu pacman si este simlink catre libalpm.so.12.0.0 care e continut de acelasi pachet, pacman (5.2.0-2). Vezi in /usr/lib/ daca ai simlink-ul daca nu il creezi tu (ln -sf /usr/lib/libalpm.so.12.0.0 /usr/lib/libalpm.so.12), nu este o solutie corecta, este functionala dar nu recomandata. Daca problema persista atunci fa un update la sistem cum am zis mai sus (pacman -Syyuu sau pacman -Syu) apoi recompilezi yay (makepkg ca si user in directorul unde ai PKGBUILD-ul) si apoi instalezi yay cu pacman -U.

Ai nevoie de package-query? Eu nu il am instalat si nu am probleme ca nu e prezent in sistem. Daca ai nevoie de el atunci il recompilezi, apoi recompilezi yay si ar terbui sa rezolvi problema.

Spoiler

Edited by MembruAnonim, 28 October 2019 - 12:02.


#558
c_anicai

c_anicai

    Senior Member

  • Grup: Senior Members
  • Posts: 5,286
  • Înscris: 25.01.2007
Multumesc de ajutor, am rezolvat. :) Trebuiau instalate in ordinea asta: gstreamer0.10, gstreamer0.10-base, gstreamer0.10-python, lib32-libstdc++5, Sopcast, tv-maxe-git. Urmeaza  de acum cand am timp sa fac backup la ce este in acel laptop si sa-l schimb pe Manjaro :)

Attached Files


Edited by c_anicai, 28 October 2019 - 17:16.


Anunturi

Neurochirurgie minim invazivă Neurochirurgie minim invazivă

"Primum non nocere" este ideea ce a deschis drumul medicinei spre minim invaziv.

Avansul tehnologic extraordinar din ultimele decenii a permis dezvoltarea tuturor domeniilor medicinei. Microscopul operator, neuronavigația, tehnicile anestezice avansate permit intervenții chirurgicale tot mai precise, tot mai sigure. Neurochirurgia minim invazivă, sau prin "gaura cheii", oferă pacienților posibilitatea de a se opera cu riscuri minime, fie ele neurologice, infecțioase, medicale sau estetice.

www.neurohope.ro

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Forumul Softpedia foloseste "cookies" pentru a imbunatati experienta utilizatorilor Accept
Pentru detalii si optiuni legate de cookies si datele personale, consultati Politica de utilizare cookies si Politica de confidentialitate