Jump to content

SUBIECTE NOI
« 1 / 5 »
RSS
Incalzire in pardoseala etapizata

Suprataxa card energie?!

Cum era nivelul de trai cam din a...

probleme cu ochelarii
 Impozite pe proprietati de anul v...

teava rezistenta panou apa calda

Acces in Curte din Drum National

Sub mobila de bucatarie si sub fr...
 Rezultat RMN

Numar circuite IPAT si prindere t...

Pareri brgimportchina.ro - teapa ...

Lucruri inaintea vremurilor lor
 Discuții despre TVR Sport HD.

Cost abonament clinica privata

Tremura toata, dar nu de la ro...

Renault Android
 

Linux Mint 19 tara - citire si intelegere log erori

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

#1
pinguinul666

pinguinul666

    Senior Member

  • Grup: Senior Members
  • Posts: 4,689
  • Înscris: 06.10.2015
sal

am un amd ryzen 5 2400g (raven bridge), memorie ram 8 gb ddr4 si am instalat Linux Mint 19 tara.
e actualizat la zi, fara erori

Acum cateva clipe, am avut parte de...green screen of death !
Adica ecranul s-a facut verde, sunetul s-a "balbait" vreo 2-3 secunde (eram pe youtube) , apoi a amutit de tot...si calc a inghetat.

Am doua intrebari:

1) Unde citesc logul de rori? in /var/log?  care log?

2) Cum descifrez din ce cauza s-a intamplaT?

Pot sa pun aici, pe forum, textul logului daca trebuie.

multumesc

Edited by pinguinul666, 06 October 2018 - 15:14.


#2
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 398,226
  • Înscris: 08.10.2015
journalctl -k
journalctl -e -b 1
journalctl -S "2018-10-06"
dmesg

Vezi ce zic fiecare.

#3
shogun1

shogun1

    Cranky old n00b ☯

  • Grup: Senior Members
  • Posts: 7,542
  • Înscris: 31.01.2009
Mutat, nu e un tutorial.


#4
pinguinul666

pinguinul666

    Senior Member

  • Grup: Senior Members
  • Posts: 4,689
  • Înscris: 06.10.2015
Putea fi tutorial despre cum sa citesc erori...dar fie :)

Anyway, am copiat output-ul acelor comenzi journalctl.
Atasez un PDF cu ele, ca e lunga lista.

Am colorat in rosu - sa sara in evidenta! - erorile.

Cred ca mi-am dat seama ...judecand dupa erori ca (si citez din log):

Quote


[drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 1us * 100 tries - tgn10_lock line:566

ACPI Error: [SMIC] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dswload-378)

Oct 06 18:33:47 utilizator kernel: ACPI Exception: AE_ALREADY_EXISTS, During name
lookup/catalog (20170831/psobject-252)

Oct 06 18:33:47 utilizator kernel: ACPI Exception: AE_ALREADY_EXISTS, (SSDT:  AMD PT)
while loading table (20170831/tbxfload-228)

Oct 06 18:33:47 utilizator kernel: ACPI Error: 1 table load failures, 6 successful (20170831/tbxfload-
246)

ACPI Error: [PTOS] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)

ACPI Error: Method parse/execution failed \, AE_NOT_FOUND (20170831/psparse-550)

Am sa presupun ca problema e grafica integrata din AMD Ryzen 5 2400G (arhitectura Raven Bridge) care nu e fully supported...

ma insel sau nu?

Attached Files



#5
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 398,226
  • Înscris: 08.10.2015
Ignora erorile de ACPI e vorba de faptul ca producatorul placii de baza si automat al BIOS-ului nu respecta in intregime standardul. Adica sunt  intrari in BIOS care genereaza erori sub GNU/Linux deoarece majoritatea jegurilor de producatori hardware, ma rog de placi de baza, au BIOS-ul optimizat si scris pentru ferestre. Kernel-ul nu stie de anumite inregistrari din firmware-ul scris in chip si automat se genereaza acele erori:
oct 06 16:22:07 Timberwolf kernel: ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20180531/exresop-69)
oct 06 16:22:07 Timberwolf kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20180531/dswexec-427)
oct 06 16:22:07 Timberwolf kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516)
oct 06 16:22:07 Timberwolf kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.ASHS._STA._OSI], AE_NOT_FOUND (20180531/psargs-330)
oct 06 16:22:07 Timberwolf kernel: ACPI Error: Method parse/execution failed \_SB.ASHS._STA, AE_NOT_FOUND (20180531/psparse-516)
oct 06 16:22:07 Timberwolf kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0._OSC._OSI], AE_NOT_FOUND (20180531/psargs-330)
oct 06 16:22:07 Timberwolf kernel: ACPI Error: Method parse/execution failed \_SB.PCI0._OSC, AE_NOT_FOUND (20180531/psparse-516)
oct 06 16:22:07 Timberwolf kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.ASHS._STA._OSI], AE_NOT_FOUND (20180531/psargs-330)
oct 06 16:22:07 Timberwolf kernel: ACPI Error: Method parse/execution failed \_SB.ASHS._STA, AE_NOT_FOUND (20180531/psparse-516)
oct 06 16:22:07 Timberwolf kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.ASHS._STA._OSI], AE_NOT_FOUND (20180531/psargs-330)
oct 06 16:22:07 Timberwolf kernel: ACPI Error: Method parse/execution failed \_SB.ASHS._STA, AE_NOT_FOUND (20180531/psparse-516)
oct 06 16:22:13 Timberwolf kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.ASHS._STA._OSI], AE_NOT_FOUND (20180531/psargs-330)
oct 06 16:22:13 Timberwolf kernel: ACPI Error: Method parse/execution failed \_SB.ASHS._STA, AE_NOT_FOUND (20180531/psparse-516)

Mesajele astea le vad de un an de zile aproape, mai bine zis de cand kernel-ul a ajuns la versiunea 4.9 sau 4.10 ca inainte de asta nu apareau.

Vezi ca m-am inselat eu, journalctl -k arata log-urile de la ultimul boot dar pe tine te intereseaza ce a fost inainte de ultima pornire a sistemului deci pe tine te ajuta mai mult journalctl -S "2018-10-06 15:00:00" de exemplu. Asa vei vedea log-urile incepand cu data specificata, in exemplul meu data de astazi, de la ora specificata in exemplul meu ora 1500.
┌(ghost)─(Timberwolf)─(4.18.10-arch1-1-ARCH)
└─(lg-test-php-py-version)─(6 files, 32KB)─ $ sudo journalctl -S "2018-10-06 15:00:00"
-- Logs begin at Tue 2018-08-14 21:25:09 EEST, end at Sun 2250-07-14 21:18:49 EEST. --
oct 06 16:22:07 Timberwolf kernel: Linux version 4.18.10-arch1-1-ARCH (builduser@heftig-3658) (gcc version 8.2.1 20180831 (GCC)) #1 SMP PREEMPT Wed Sep 26 09:48:22 UTC 2018
oct 06 16:22:07 Timberwolf kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=a63fc044-4945-4b2e-b8ed-827e91e40492 rw rcutree.rcu_idle_gp_delay=1 quiet quiet net.ifnames=0 acpi_osi= nmi_watchdog=0

Nu aveam laptopul pornit la 1500 de asta prima linie din log e la 1622 ca atunci l-am pornit.
Legat de journalctl -e -b 1 de fapt trebuie sa dai intai comanda journalctl -F N_RESTARTS apoi journalctl -e -b X unde X este numarul maxim dat de comanda anterioara minus 1:
┌(ghost)─(Timberwolf)─(4.18.10-arch1-1-ARCH)
└─(lg-test-php-py-version)─(6 files, 32KB)─ $ journalctl -F N_RESTARTS
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
┌(ghost)─(Timberwolf)─(4.18.10-arch1-1-ARCH)
└─(lg-test-php-py-version)─(6 files, 32KB)─ $ journalctl -e -b 23
sep 23 01:43:57 Timberwolf systemd[1]: Stopping Load/Save Screen Backlight Brightness of leds:asus::kbd_backlight...
sep 23 01:43:57 Timberwolf systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:intel_backlight...
sep 23 01:43:57 Timberwolf systemd[1]: Stopping Network Time Synchronization...
sep 23 01:43:57 Timberwolf systemd[1]: Stopped Network Time Synchronization.
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf systemd[1]: Stopped Load/Save Random Seed.
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:acpi_video0.
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:acpi_video0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:acpi_video0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf systemd[1]: Stopped Load/Save Screen Backlight Brightness of leds:asus::kbd_backlight.
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@leds:asus::kbd_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@leds:asus::kbd_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight.
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:intel_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:intel_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
sep 23 01:43:57 Timberwolf audit[8432]: SYSTEM_SHUTDOWN pid=8432 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:57 Timberwolf systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
sep 23 01:43:57 Timberwolf systemd[1]: Stopped Create Volatile Files and Directories.
sep 23 01:43:57 Timberwolf systemd[1]: Stopped target Local File Systems.
sep 23 01:43:57 Timberwolf systemd[1]: Unmounting /boot...
sep 23 01:43:57 Timberwolf systemd[1]: Unmounting Temporary Directory (/tmp)...
sep 23 01:43:57 Timberwolf systemd[1]: Unmounting /mnt/stuff...
sep 23 01:43:57 Timberwolf systemd[1]: Unmounting /home...
sep 23 01:43:57 Timberwolf systemd[1]: Unmounted Temporary Directory (/tmp).
sep 23 01:43:57 Timberwolf systemd[1]: Stopped target Swap.
sep 23 01:43:58 Timberwolf systemd[1]: Unmounted /boot.
sep 23 01:43:58 Timberwolf systemd[1]: Stopped File System Check on /dev/disk/by-uuid/dd937882-f19b-4c33-9eb6-a30c99c83983.
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-dd937882\x2df19b\x2d4c33\x2d9eb6\x2da30c99c83983 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-dd937882\x2df19b\x2d4c33\x2d9eb6\x2da30c99c83983 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:58 Timberwolf systemd[1]: Unmounted /mnt/stuff.
sep 23 01:43:58 Timberwolf systemd[1]: Stopped File System Check on /dev/disk/by-uuid/72e75b94-b478-4829-933e-0d68c16cb780.
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-72e75b94\x2db478\x2d4829\x2d933e\x2d0d68c16cb780 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-72e75b94\x2db478\x2d4829\x2d933e\x2d0d68c16cb780 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:58 Timberwolf systemd[1]: Unmounted /home.
sep 23 01:43:58 Timberwolf systemd[1]: Reached target Unmount All Filesystems.
sep 23 01:43:58 Timberwolf systemd[1]: Stopped File System Check on /dev/disk/by-uuid/65e07373-ddfb-498a-915a-dd32725a38bd.
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-65e07373\x2dddfb\x2d498a\x2d915a\x2ddd32725a38bd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-65e07373\x2dddfb\x2d498a\x2d915a\x2ddd32725a38bd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:58 Timberwolf systemd[1]: Stopped target Local File Systems (Pre).
sep 23 01:43:58 Timberwolf systemd[1]: Stopped Create Static Device Nodes in /dev.
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:58 Timberwolf systemd[1]: Stopped Remount Root and Kernel File Systems.
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:58 Timberwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 23 01:43:58 Timberwolf systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
sep 23 01:43:58 Timberwolf systemd[1]: Removed slice system-systemd\x2dfsck.slice.
sep 23 01:43:58 Timberwolf systemd[1]: Reached target Shutdown.
sep 23 01:43:58 Timberwolf systemd[1]: Reached target Final Step.
sep 23 01:43:58 Timberwolf systemd[1]: Starting Power-Off...
sep 23 01:43:58 Timberwolf systemd[1]: Shutting down.
sep 23 01:43:58 Timberwolf kernel: systemd-shutdow: 28 output lines suppressed due to ratelimiting
sep 23 01:43:58 Timberwolf systemd-shutdown[1]: Syncing filesystems and block devices.
sep 23 01:43:59 Timberwolf systemd-shutdown[1]: Sending SIGTERM to remaining processes...
sep 23 01:43:59 Timberwolf systemd-journald[277]: Journal stopped

Iar daca stii aproximativ intervalul cand a crash-uit jucaria folosesti jurnalctl la modul:
┌(ghost)─(Timberwolf)─(4.18.10-arch1-1-ARCH)
└─(lg-test-php-py-version)─(6 files, 32KB)─ $ sudo journalctl -S "2018-10-06 22:00:00" -U "2018-10-06 22:01:00"
-- Logs begin at Tue 2018-08-14 21:25:09 EEST, end at Sun 2250-07-14 21:18:49 EEST. --
oct 06 22:00:33 Timberwolf kwin_x11[769]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22183, resource id: 23799663, major code: 20 (GetProperty), minor code: 0
┌(ghost)─(Timberwolf)─(4.18.10-arch1-1-ARCH)
└─(lg-test-php-py-version)─(6 files, 32KB)─ $

Sau verifici /var/log/Xorg* pentru a vedea daca X-ul a inregistrat ceva:
┌(ghost)─(Timberwolf)─(4.18.10-arch1-1-ARCH)
└─(lg-test-php-py-version)─(6 files, 32KB)─ $ sudo grep -Rn EE /var/log/Xorg*
/var/log/Xorg.0.log:6:[	22.492] Current Operating System: Linux Timberwolf 4.18.10-arch1-1-ARCH #1 SMP PREEMPT Wed Sep 26 09:48:22 UTC 2018 x86_64
/var/log/Xorg.0.log:15: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
/var/log/Xorg.0.log:354:[	23.114] (II) Initializing extension MIT-SCREEN-SAVER
/var/log/Xorg.0.log:1423:[  2855.775] (EE) client bug: timer event6 debounce short: offset negative (-4ms)
/var/log/Xorg.0.log:1451:[  7659.652] (EE) client bug: timer event6 debounce short: offset negative (-2ms)
/var/log/Xorg.0.log:1452:[  7850.570] (EE) client bug: timer event6 debounce: offset negative (-0ms)
/var/log/Xorg.0.log:1453:[  8446.299] (EE) client bug: timer event6 debounce short: offset negative (-0ms)
/var/log/Xorg.0.log:1454:[  8639.445] (EE) client bug: timer event6 debounce short: offset negative (-12ms)
/var/log/Xorg.0.log:1455:[  8648.324] (EE) client bug: timer event6 debounce short: offset negative (-4ms)
/var/log/Xorg.0.log:1456:[  8699.747] (EE) client bug: timer event6 debounce: offset negative (-6ms)
/var/log/Xorg.0.log:1457:[ 10669.028] (EE) client bug: timer event6 debounce short: offset negative (-1ms)



#6
pinguinul666

pinguinul666

    Senior Member

  • Grup: Senior Members
  • Posts: 4,689
  • Înscris: 06.10.2015
Salut si multumesc de raspuns!

Am notat acea comanda cu jounalctl -S ...  pt urmatoarea data cand se va intampla!

Intre timp, re-aduc in vedere urmatoarea eroare:

Quote

[drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 1us * 100 tries - tgn10_lock line:566


Asta nu inseamna ca e o problema cu grafica integrata?

Am mai citit si eu pe niscaiva forumuri si observ ca suportul pt arhitectura Raven Bridge e relativ recent si inca de prin Iulie/August 2018 unii programatori spun ca un modul - mesa - tot da probleme la interactiunea cu accelerarea grafica integrata in raven bridge.

#7
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 398,226
  • Înscris: 08.10.2015
Hmmm... adauga la kernel urmatorii parametrii rcu_nocbs=0-7 amdgpu.dpm=0 idle=nomwait nu stiu daca ajuta dar eu fug ca de ala cu coarne si coada de porcaria aia de producator de asa zise procesoare si placi video.

#8
pinguinul666

pinguinul666

    Senior Member

  • Grup: Senior Members
  • Posts: 4,689
  • Înscris: 06.10.2015

View PostMembruAnonim, on 06 octombrie 2018 - 22:26, said:

Hmmm... adauga la kernel urmatorii parametrii rcu_nocbs=0-7 amdgpu.dpm=0 idle=nomwait nu stiu daca ajuta dar eu fug ca de ala cu coarne si coada de porcaria aia de producator de asa zise procesoare si placi video.

Si ce anume fae comanda aceasta, daca nu te superi ?

PS: am citit ceva benchmarkuri, si pound for pound, am vazut ca ryzen 2400g bate intel i5 8400, mai ales la partea cu grafica integrata. unde hd630 nu se compara cu vega 11  (asa zic acele site-uri...caut si iti dau si link)

    problema e ca e prea curand scos pe piata, si cam stranie arhitectura Racen Bridge pt developerii linux :(

#9
MembruAnonim

MembruAnonim

    MembruAnonim

  • Grup: Banned
  • Posts: 398,226
  • Înscris: 08.10.2015
Nu ma intereseaza performantele grafice ale placii video integrate. Sunt foarte multumit de Intel si pentru mine infectii aia de la amd nu exista nici pe parte de procesoare nici pe parte de placi video si pe nici o altfel de parte. Combinatia Intel + nVidia rules. Pentru mine aia care au produs acel "procesor" pe care il ai tu sunt niste boschetari infecti iar rostirea numelui lor e o blasfemie.  Parametrii aia de kernel fac nis te magarii care poate te vor ajuta, vor rezolva situatia de care te-ai lovit sau este posibil ca in cazul tau sa nu rezolve nimic. Insa nu strica sa incerci.

Anunturi

Second Opinion Second Opinion

Folosind serviciul second opinion ne puteți trimite RMN-uri, CT -uri, angiografii, fișiere .pdf, documente medicale.

Astfel vă vom putea da o opinie neurochirurgicală, fără ca aceasta să poată înlocui un consult de specialitate. Răspunsurile vor fi date prin e-mail în cel mai scurt timp posibil (de obicei în mai putin de 24 de ore, dar nu mai mult de 48 de ore). Second opinion – Neurohope este un serviciu gratuit.

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