Zobrazit příspěvky

Tato sekce Vám umožňuje zobrazit všechny příspěvky tohoto uživatele. Prosím uvědomte si, že můžete vidět příspěvky pouze z oblastí Vám přístupných.


Příspěvky - wakatana

Stran: 1 [2] 3 4 ... 6
16
Mas moznost carovat s grafikami v Biose ?
Ak ano, jednu tam skus tipnut ..alebo prehodit preferovane poradie ...

Bohuzial nic take tam nevidim, a zrejme to ani nieje mozne vid tu

Citace
First:  be sure you understand how your system functions. It does not have a true, discrete GPU.  It has a software-controlled hybrid setup in which the Intel GPU is permanently wired as primary and the nVidia GPU is solely a co-processor for the Intel GPU.  As such, ALL video data passes through the Intel GPU on its way to the screen.  ONLY the Intel GPU has a physical connection to the display panel.

Vcera som narazil na nejaky benchmark od Dellu ktory testoval graficku kartu, pocas tohoto testu som mal teplotu 90C na Nvidia karte. Pride mi to celkom dost ci nie?. Pri teste Intel VGA karty teplota nebola zobrazena.

Teplotu Intel VGA vsak vidim v GPU-Z (v OpenHardwareMonitor nieje vobec zmienka o Intel VGA). Teplota v klude pre CPU aj obe GPU je okolo 52C. Skusim to este nejak presnejsie pomerat.

Vyzera to tak ze na doske je Nvidia separe od CPU a Intel je jeho cusastou. CPU a Nvidia maju spolocny chladic vid video. Takze aj RPM pre CPU a GPU by malo byt rovnake, no nikde ho nevidim, ani v OpenHardwareMonitor ani GPU-Z, neviete o niecom?

17
Dobry den, mam laptop s 2 grafickymi kartami (Intel HD Graphic 530 a Nvidia GeForce GTX 960M) na ktorom mam Windows 10 Home. Casto mam problem pri aktualizovani ovladacov pre VGA a to tak ze dany ovladac mi proste rozbije grafiku. Najcastejsie to vidm napr tak ze  Firefox zacne padat. Zvycajne je to ked otvorim viac tabov s videom. Oobrazovka preblikne na cierno a FF najcastejsie padne. Obcas sa stane ze FF so sebou strhne aj nejake ine aplikacie (Deluge, VScode, Spotify a pod). Par x sa stalo ze PC zatuhol tak ze som musel restartovat graficky driver (Win+Ctrl+Shift+B) alebo rovno cele PC. Casto s mi stava aj to ze zatvorim laptop a PC zostane bezat. Mam podozrenie ze je to prave koli VGA nakolko napr NumLock na klavesnici reaguje a rovnako aj hudba zostane hrat. Avsak ked znova otvorim laptop tak VGA je mrtve (Win+Ctrl+Shift+B nepomaha) a pomoze len restart PC. Povodne som mal podozrenie na grafiku Nvidia avsak skusil som v Device Managery tuto grafiku uplne vypnut no spominane problemy nezmizli. Ked vypnem Intel grafiku tak Windows nedokaze plnohodnote pouzit Nvidiu (nemoznost menit rozlisenie, nefunkcnost win+p , velke ikonky a pod.). Zaujimavostou je ze niekedy PC huci, hoci nic zvlastne nerobi CPU 10%-15% chcel som teda v openhardware monitore pozriet kolko RPM ma ventilator na VGA kartach no nevidm tam taku moznost. Napadlo ma preto ze ci nemoze byt fyzicky poskodene cidlo na RPM a teda toci ventilator uplne zbytocne resp netoci ked ma a ci sa karty nemozu prehrievat a potom to robi problemy?

Vpodstate som skusal nasledujuce:
1. Win10 -> Settings -> System -> Display -> Graphic Settings -> nastavenie Intel resp Nvidia karty pre FF - Nieco podobne ma aj Nvidia control panel avsak je tam spomenute ze: Windows OS now manages selection of the graphic processor
2. FF: webgl.disabled resp webgl.enabled
3. FF: Use hardware acceleration when available (disable/enable)

Otazky:
1. Co mozem este skusit?
2. Viem vypnut Intel a pouzit len Nvidiu?
3. Existuje nejaky benchmark alebo nastroj ktory by odhalil poruchu karty?
4. Ako je na tom Linux s podporou pre 2 VGA?

Dakujem

18
Desktop / Re:VNC připojení na RPi
« kdy: 01. 09. 2020, 12:17:17 »
Dakujem za rady, ked spravne chapem tak podla vypisu nizsie sluzba nieje typu notify. Ake by mali byt spravne nastavenia pre pouzivatela, DISPLAY a XAUTHORITY? Dakujem.

Kód: [Vybrat]
pi@rpi-home:~ $ systemctl cat vncserver-x11-serviced.service
# /usr/lib/systemd/system/vncserver-x11-serviced.service
[Unit]
Description=VNC Server in Service Mode daemon
After=network.target

[Service]
ExecStart=/usr/bin/vncserver-x11-serviced -fg
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
KillMode=process

[Install]
WantedBy=multi-user.target

Kód: [Vybrat]
pi@rpi-home:~ $ journalctl -u vncserver-x11-serviced
-- Logs begin at Tue 2020-08-25 02:53:42 CEST, end at Tue 2020-09-01 12:09:49 CEST. --
Aug 30 21:04:16 rpi-home vncserver-x11[440]: Connections: connected: 192.168.3.107::56633 (TCP)
Aug 30 21:04:16 rpi-home vncserver-x11[440]: Connections: disconnected: 192.168.3.107::56633 (TCP) ([EndOfStream] Disconnection by client)
Sep 01 00:33:58 rpi-home vncserver-x11[440]: Connections: connected: 192.168.3.107::57234 (TCP)
Sep 01 00:33:58 rpi-home vncserver-x11[440]: Connections: disconnected: 192.168.3.107::57234 (TCP) ([ConnFailed] No configured security type is supported by 3.3 VNC Viewer)
Sep 01 01:14:12 rpi-home vncserver-x11[440]: Connections: connected: 192.168.3.107::58312 (TCP)
Sep 01 01:14:12 rpi-home vncserver-x11[440]: Connections: disconnected: 192.168.3.107::58312 (TCP) ([ConnFailed] No configured security type is supported by 3.3 VNC Viewer)
Sep 01 01:21:52 rpi-home vncserver-x11[440]: ServerManager: Server stopped
Sep 01 01:21:52 rpi-home systemd[1]: vncserver-x11-serviced.service: Succeeded.
Sep 01 01:37:02 rpi-home systemd[1]: Started VNC Server in Service Mode daemon.
Sep 01 01:37:02 rpi-home vncserver-x11[24847]: ServerManager: Server started
Sep 01 01:37:02 rpi-home vncserver-x11[24847]: ConsoleDisplay: Found running X server (pid=478, binary=/usr/lib/xorg/Xorg)
Sep 01 01:37:24 rpi-home systemd[1]: Stopping VNC Server in Service Mode daemon...
Sep 01 01:37:24 rpi-home vncserver-x11[24847]: ServerManager: Server stopped
Sep 01 01:37:24 rpi-home systemd[1]: vncserver-x11-serviced.service: Succeeded.
Sep 01 01:37:24 rpi-home systemd[1]: Stopped VNC Server in Service Mode daemon.
Sep 01 01:38:46 rpi-home systemd[1]: Started VNC Server in Service Mode daemon.
Sep 01 01:38:46 rpi-home vncserver-x11[24971]: ServerManager: Server started
Sep 01 01:38:46 rpi-home vncserver-x11[24971]: ConsoleDisplay: Found running X server (pid=478, binary=/usr/lib/xorg/Xorg)
Sep 01 01:39:11 rpi-home systemd[1]: Stopping VNC Server in Service Mode daemon...
Sep 01 01:39:11 rpi-home vncserver-x11[24971]: ServerManager: Server stopped
Sep 01 01:39:11 rpi-home systemd[1]: vncserver-x11-serviced.service: Succeeded.
Sep 01 01:39:11 rpi-home systemd[1]: Stopped VNC Server in Service Mode daemon.
Sep 01 01:39:22 rpi-home systemd[1]: Started VNC Server in Service Mode daemon.
Sep 01 01:39:22 rpi-home vncserver-x11[25054]: ServerManager: Server started
Sep 01 01:39:22 rpi-home vncserver-x11[25054]: ConsoleDisplay: Found running X server (pid=478, binary=/usr/lib/xorg/Xorg)
Sep 01 01:39:39 rpi-home vncserver-x11[25054]: Connections: connected: 192.168.3.107::58663 (TCP)
Sep 01 01:39:39 rpi-home vncserver-x11[25054]: Connections: disconnected: 192.168.3.107::58663 (TCP) ([ConnFailed] No configured security type is supported by 3.3 VNC Viewer)
Sep 01 01:40:06 rpi-home vncserver-x11[25054]: Connections: connected: 192.168.3.107::58691 (TCP)
Sep 01 01:40:06 rpi-home vncserver-x11[25054]: Connections: disconnected: 192.168.3.107::58691 (TCP) ([ConnFailed] No configured security type is supported by 3.3 VNC Viewer)
Sep 01 01:40:12 rpi-home vncserver-x11[25054]: Connections: connected: 192.168.3.107::58692 (TCP)
Sep 01 01:40:12 rpi-home vncserver-x11[25054]: Connections: disconnected: 192.168.3.107::58692 (TCP) ([ConnFailed] No configured security type is supported by 3.3 VNC Viewer)
Sep 01 01:40:41 rpi-home systemd[1]: Stopping VNC Server in Service Mode daemon...
Sep 01 01:40:41 rpi-home vncserver-x11[25054]: ServerManager: Server stopped
Sep 01 01:40:41 rpi-home systemd[1]: vncserver-x11-serviced.service: Succeeded.
Sep 01 01:40:41 rpi-home systemd[1]: Stopped VNC Server in Service Mode daemon.

19
Desktop / VNC připojení na RPi
« kdy: 01. 09. 2020, 01:50:57 »
Zdravim,
Mam problem s VNC na RPI. Ak mam VNC spustene nasledovne potom sa na neho neviem pripojit

Kód: [Vybrat]
pi@rpi-home:~ $ sudo systemctl status vncserver-x11-serviced.service
● vncserver-x11-serviced.service - VNC Server in Service Mode daemon
   Loaded: loaded (/usr/lib/systemd/system/vncserver-x11-serviced.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Tue 2020-09-01 01:39:11 CEST; 2s ago
  Process: 24968 ExecStart=/usr/bin/vncserver-x11-serviced -fg (code=exited, status=0/SUCCESS)
 Main PID: 24968 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 1475)
   Memory: 15.0M
   CGroup: /system.slice/vncserver-x11-serviced.service

Sep 01 01:38:46 rpi-home systemd[1]: Started VNC Server in Service Mode daemon.
Sep 01 01:38:46 rpi-home vncserver-x11[24971]: ServerManager: Server started
Sep 01 01:38:46 rpi-home vncserver-x11[24971]: ConsoleDisplay: Found running X server (pid=478, binary=/usr/lib/xorg/Xorg)
Sep 01 01:39:11 rpi-home systemd[1]: Stopping VNC Server in Service Mode daemon...
Sep 01 01:39:11 rpi-home vncserver-x11[24971]: ServerManager: Server stopped
Sep 01 01:39:11 rpi-home systemd[1]: vncserver-x11-serviced.service: Succeeded.
Sep 01 01:39:11 rpi-home systemd[1]: Stopped VNC Server in Service Mode daemon.
pi@rpi-home:~ $ sudo netstat -pevanut | grep vnc
pi@rpi-home:~ $ sudo systemctl start vncserver-x11-serviced.service
pi@rpi-home:~ $ sudo netstat -pevanut | grep vnc
tcp        0      0 0.0.0.0:5900            0.0.0.0:*               LISTEN      0          6047607    25054/vncserver-x11
tcp        0      0 127.0.0.1:42437         127.0.0.1:56548         ESTABLISHED 1000       6050226    25067/vncserverui
tcp        0      0 127.0.0.1:56548         127.0.0.1:42437         ESTABLISHED 0          6047655    25054/vncserver-x11
tcp6       0      0 :::5900                 :::*                    LISTEN      0          6047606    25054/vncserver-x11

Pri neuspesnom pripajani dostavam hlasky typu:

Kód: [Vybrat]
wakatana@ubuntu:~$ vncviewer 192.168.3.108:0
Connected to RFB server, using protocol version 3.3
No configured security type is supported by 3.3 VNC Viewer
wakatana@ubuntu:~$ vncviewer 192.168.3.108:1
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server

Ak mam VNC spustene nasledovne potom sa pripojim avsak kazde okno ktore otvorim po chvilke zmizne

Kód: [Vybrat]
pi@rpi-home:~ $ vncserver-virtual -Encryption PreferOn -Authentication VncAuth
VNC(R) Server 6.7.1 (r42348) ARMv6 (Jan 30 2020 15:13:47)
Copyright (C) 2002-2020 RealVNC Ltd.
RealVNC and VNC are trademarks of RealVNC Ltd and are protected by trademark
registrations and/or pending trademark applications in the European Union,
United States of America and other jurisdictions.
Protected by UK patent 2481870; US patent 8760366; EU patent 2652951.
See https://www.realvnc.com for information on VNC.
For third party acknowledgements see:
https://www.realvnc.com/docs/6/foss.html
OS: Raspbian GNU/Linux 10, Linux 4.19.97, armv7l

On some distributions (in particular Red Hat), you may get a better experience
by running vncserver-virtual in conjunction with the system Xorg server, rather
than the old version built-in to Xvnc. More desktop environments and
applications will likely be compatible. For more information on this alternative
implementation, please see: https://www.realvnc.com/doclink/kb-546

Running applications in /etc/vnc/xstartup

VNC Server catchphrase: "Flame monster buffalo. Demo Ralph bazaar."
             signature: f1-37-1f-cc-c4-19-1b-82

Log file is /home/pi/.vnc/rpi-home:1.log
New desktop is rpi-home:1 (192.168.3.108:1)
pi@rpi-home:~ $ sudo netstat -pevanut | grep vnc
tcp        0      0 0.0.0.0:5901            0.0.0.0:*               LISTEN      1000       6051865    25139/Xvnc-core
tcp        0      0 0.0.0.0:6001            0.0.0.0:*               LISTEN      1000       6050967    25139/Xvnc-core
tcp        0      0 127.0.0.1:58600         127.0.0.1:37497         ESTABLISHED 1000       6050458    25139/Xvnc-core
tcp        0      0 127.0.0.1:37497         127.0.0.1:58600         ESTABLISHED 1000       6051935    25183/vncserverui
tcp6       0      0 :::5901                 :::*                    LISTEN      1000       6051864    25139/Xvnc-core
tcp6       0      0 :::6001                 :::*                    LISTEN      1000       6050966    25139/Xvnc-core
pi@rpi-home:~ $

Pripajam sa  nasleovne:

Kód: [Vybrat]
vncviewer 192.168.3.108:1
resp
vncviewer 192.168.3.108:0

20
Hardware / Re:Notetebook Toshiba Satellite A300 sa nechce zapnut
« kdy: 10. 07. 2020, 11:18:40 »
Nestartující NTB opravdu není vhodný začátek studia elektroniky. To je poctivé soustu i pro specialistu.

s cim by ste doporucili zacat?

21
Hardware / Re:Notetebook Toshiba Satellite A300 sa nechce zapnut
« kdy: 10. 07. 2020, 10:56:48 »
Regulovany zdroj mi bol odporuceny v diskusii preto som sa nan pytal. V ziadom pripade nechcem mrhat vasim casom. A mate pravdu, o opravovani zakladnych dosiek neviem prakticky nic, o elektornike nieco malo, to bol sekundarny ciel, nieco nove sa naucit (najlepsie na notebooku ktoremu uz nemam ako ublizit). Pekny den

22
Hardware / Re:Notetebook Toshiba Satellite A300 sa nechce zapnut
« kdy: 10. 07. 2020, 08:05:48 »
Tu som prave nasiel jedno zaujimave video cca od 14 minuty robi to ze pripaja dosku na externy regulovatelny zdroj, ak som to spravne pochopil.

23
Hardware / Re:Notetebook Toshiba Satellite A300 sa nechce zapnut
« kdy: 10. 07. 2020, 07:39:49 »
Dakujem za odpovede
Viete odporucit nejaky regulovany zdroj za rozumnu cenu? Uvazoval som nad tym davnejsie. Respektive aky regulovatelny zdroj mate na mysli, existuje aj taky do ktoreho zapojim notebook nabijacku na 230V a odtial ju nasledne regulujem? Alebo treba zohnat taky ktory ma uz vystup rovnaky ako ma kontektor pre nabijanie na notebooku? Nestaci napr merac spotreby ktory sa zapoji medzi zasuvku a nabijacku?

Baterka uz davno nefunguje, no skusal som notebook zapinat aj ked bola vlozena/vybrata. LEDky tiez nesvietia ziadne, skusal som aj kabel v rj45 ale ani to nesvieti. CMOS baterku sa mi vybrat nepodarilo lebo tam drzi ako prizvarana a bal som sa za urvem ten plech co ju drzi.

Skusal som mat odpojene prakticky vsetko okrem ventilatoru na CPU, napajania, mikro spinaca na zapinanie. Vcera som pomeral mikro spinac (zlty a cierny drotik) a vyzera ze je OK (pri zopnui ma 0 ohm). Po zapnuti sa nedeje absolutne nic - ventilator sa ani nepohne.

Nejake schemy som nasiel tu ale bohuzial mi to nic nepovedalo

Dakujem

24
Hardware / Notetebook Toshiba Satellite A300 sa nechce zapnut
« kdy: 03. 07. 2020, 01:01:43 »
Zdravim, mam doma starsi notebook Toshiba Satellite A300. Jedneho dna sa proste odmietol zapnut. Vraj sa mu nieco podobne stalo aj v minulosti a vtedy pomohlo mierne zatrasenie. Bohuzial zatrasenie nepomaha. Podla multi metra vyzera byt nabijacka OK, rovnako aj konektor pre napajanie ktory je pripojeny do zakladnej dosky. Skusil som odpojit prakticky vsetko co nutne nemusi byt do zakladnej dosky pripojene (usb, display, hdd, dvd ... nechal som len mikrospinac pre zapnutie) a tak skusal zapnut.

Ak v minulosti pomohlo mierne zatrasenie tak by som to tipol na nejaky zly kontakt alebo zly mikro spinac? Vizualne som na zakladnej doske nevidel nic zhorene (ale to asi neznamena ze tam nieco nieje odpalene). Je este nieco co mozem vyskusat? Viem nejako zmerat zakladnu dosku?  Foto dokumentacia je dostupna tu. Dakujem za kazdu radu.





25
Hardware / Re:Výběr NAS: QNAP nebo Synology
« kdy: 23. 06. 2020, 15:30:13 »
Ahoj všem.
Potřebuji nahradit NAS QNAP TS-228A, který odešel do křemíkového nebe.

Mozem sa opytat ako ste mali zapojene disky (RAID resp nieco ine) a ci ste uz riesili ako sa dostanete k datam? Myslite ze disky bude stacit pripojit do noveho zariadenia? Vdaka

26
Distribuce / Re:Velký /var/log/syslog
« kdy: 22. 06. 2020, 23:27:16 »
Este by som upresnil. Jedna sa o stroj ktory mi nebezi permanentne, naposledy som ho zapol aby som nan robil backup. Neviem ci spominana hlaska v syslogu mohla mat suvis s tym ze som tam kopiroval data. Vtedy bol velky aj /var/log/kern.log ale som urobil chybu a zmazal ho bez toho aby som pozrel co v nom je. V tom case som si vsimol aj to ze SSH mi dost lagovalo. Momentalne je /var/log/kern.log prazdny a vo /var/log/syslog je len par veci. SSH ide plynule. Vo /var/log/syslog.2.gz je spominana hlaska + este jedna o nedostupnosti. A je tam par starych archivnych logov (takze predpokladam ze rotate bezi)


Kód: [Vybrat]
wakatana@lubuntu:/var/log$ zless /var/log/syslog.2.gz
Jun 15 09:34:38 lubuntu kernel: [ 4566.515601] ------------[ cut here ]------------
Jun 15 09:34:38 lubuntu kernel: [ 4566.515602] Hardware became unavailable during restart.
Jun 15 09:34:38 lubuntu kernel: [ 4566.515697] WARNING: CPU: 0 PID: 2991 at /build/linux-CbANGF/linux-4.15.0/net/mac80211/util.c:1870 ieee80211_reconfig+0x22c/0x11b0 [mac80211]
Jun 15 09:34:38 lubuntu kernel: [ 4566.515698] Modules linked in: ccm bnep hp_wmi sparse_keymap wmi_bmof arc4 coretemp kvm_intel kvm irqbypass iwl3945 snd_hda_codec_hdmi snd_hda_codec_analog iwlegacy i915 input_leds joydev snd_hda_codec_generic pcmcia mac80211 serio_raw snd_hda_intel snd_hda_codec drm_kms_helper cfg80211 yenta_socket drm snd_hda_core pcmcia_rsrc snd_hwdep pcmcia_core lpc_ich snd_pcm i2c_algo_bit fb_sys_fops btusb snd_timer btrtl btbcm btintel shpchp bluetooth syscopyarea ecdh_generic snd sysfillrect sysimgblt soundcore wmi tpm_infineon hp_accel lis3lv02d mac_hid input_polldev video sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 psmouse firewire_ohci tg3 pata_acpi firewire_core ptp crc_itu_t pps_core
Jun 15 09:34:38 lubuntu kernel: [ 4566.515745] CPU: 0 PID: 2991 Comm: kworker/0:2 Not tainted 4.15.0-99-generic #100-Ubuntu
Jun 15 09:34:38 lubuntu kernel: [ 4566.515746] Hardware name: Hewlett-Packard HP Compaq 6710b (GB892EA#ABB)/30C0, BIOS 68DDU Ver. F.0B 08/02/2007
Jun 15 09:34:38 lubuntu kernel: [ 4566.515769] Workqueue: events_freezable ieee80211_restart_work [mac80211]
Jun 15 09:34:38 lubuntu kernel: [ 4566.515797] RIP: 0010:ieee80211_reconfig+0x22c/0x11b0 [mac80211]
Jun 15 09:34:38 lubuntu kernel: [ 4566.515799] RSP: 0018:ffffb739808ffe00 EFLAGS: 00010286
Jun 15 09:34:38 lubuntu kernel: [ 4566.515802] RAX: 0000000000000000 RBX: ffff8a78f67c0760 RCX: 0000000000000006
Jun 15 09:34:38 lubuntu kernel: [ 4566.515803] RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff8a78ffc16490
Jun 15 09:34:38 lubuntu kernel: [ 4566.515805] RBP: ffffb739808ffe48 R08: 0000000000000390 R09: 0000000000000004
Jun 15 09:34:38 lubuntu kernel: [ 4566.515807] R10: ffffb739808ffc78 R11: 0000000000000001 R12: ffff8a78f67c13a8
Jun 15 09:34:38 lubuntu kernel: [ 4566.515808] R13: 00000000fffffffb R14: ffff8a78f67c0f98 R15: 0000000000000000
Jun 15 09:34:38 lubuntu kernel: [ 4566.515811] FS:  0000000000000000(0000) GS:ffff8a78ffc00000(0000) knlGS:0000000000000000
Jun 15 09:34:38 lubuntu kernel: [ 4566.515813] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 15 09:34:38 lubuntu kernel: [ 4566.515815] CR2: 00007ff3edf28450 CR3: 0000000136a1c000 CR4: 00000000000006f0
Jun 15 09:34:38 lubuntu kernel: [ 4566.515816] Call Trace:
Jun 15 09:34:38 lubuntu kernel: [ 4566.515841]  ieee80211_restart_work+0xbb/0xf0 [mac80211]
Jun 15 09:34:38 lubuntu kernel: [ 4566.515847]  process_one_work+0x1de/0x420
Jun 15 09:34:38 lubuntu kernel: [ 4566.515850]  worker_thread+0x32/0x410
Jun 15 09:34:38 lubuntu kernel: [ 4566.515853]  kthread+0x121/0x140
Jun 15 09:34:38 lubuntu kernel: [ 4566.515856]  ? process_one_work+0x420/0x420
Jun 15 09:34:38 lubuntu kernel: [ 4566.515858]  ? kthread_create_worker_on_cpu+0x70/0x70
Jun 15 09:34:38 lubuntu kernel: [ 4566.515863]  ret_from_fork+0x35/0x40
Jun 15 09:34:38 lubuntu kernel: [ 4566.515865] Code: 00 c6 45 d6 00 c6 83 9c 04 00 00 00 48 89 df e8 6b a2 fc ff 85 c0 41 89 c5 0f 84 6e 01 00 00 48 c7 c7 80 da 7f c0 e8 e4 88 2d d2 <0f> 0b 48 89 df e8 9a db ff ff eb b0 4c 8d ab 28 05 00 00 4c 8d
Jun 15 09:34:38 lubuntu kernel: [ 4566.515895] ---[ end trace 7d4fa9e1313e8b24 ]---
Jun 15 09:34:38 lubuntu kernel: [ 4566.515913] wlp16s0: deauthenticating from 00:1b:fc:6b:81:02 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 15 09:34:38 lubuntu kernel: [ 4566.515920] ------------[ cut here ]------------


wakatana@lubuntu:/var/log$ sudo du -sh * | sort -hr | head
866M    syslog.2.gz
801M    journal
16M     installer
204K    syslog.6.gz
172K    apt
164K    dpkg.log.1
144K    syslog.1
124K    kern.log.4.gz
120K    lightdm
112K    dpkg.log.2.gz


wakatana@lubuntu:/var/log$ journalctl --disk-usage
Archived and active journals take up 800.3M in the file system.


wakatana@lubuntu:~$ cat /var/log/syslog
Jun 22 21:51:46 lubuntu rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="529" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Jun 22 21:51:51 lubuntu anacron[525]: Job `cron.daily' terminated
Jun 22 21:51:52 lubuntu anacron[525]: Job `cron.weekly' started
Jun 22 21:51:52 lubuntu anacron[1787]: Updated timestamp for job `cron.weekly' to 2020-06-22
Jun 22 21:51:53 lubuntu anacron[525]: Job `cron.weekly' terminated
Jun 22 21:51:53 lubuntu anacron[525]: Normal exit (2 jobs run)
Jun 22 21:57:09 lubuntu systemd[1]: Starting Cleanup of Temporary Directories...
Jun 22 21:57:09 lubuntu systemd[1]: Started Cleanup of Temporary Directories.
Jun 22 21:58:20 lubuntu systemd[1]: Started Session 4 of user wakatana.
Jun 22 22:05:04 lubuntu systemd[1]: Started Run anacron jobs.
Jun 22 22:05:04 lubuntu anacron[2492]: Anacron 2.3 started on 2020-06-22
Jun 22 22:05:04 lubuntu anacron[2492]: Normal exit (0 jobs run)
Jun 22 22:17:01 lubuntu CRON[3569]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)


wakatana@lubuntu:~$ cat /etc/systemd/journald.conf | grep -v '^#'

[Journal]
wakatana@lubuntu:~$ cat /etc/logrotate.conf | grep -v '^#'
weekly

su root syslog

rotate 4

create


include /etc/logrotate.d

/var/log/wtmp {
    missingok
    monthly
    create 0664 root utmp
    rotate 1
}

/var/log/btmp {
    missingok
    monthly
    create 0660 root utmp
    rotate 1
}

27
Server / Re:Oboustranná synchronizace v Debianu
« kdy: 22. 06. 2020, 22:40:56 »
Boli tu zmienene unison, rsync, syncthing. Chcel by som sa opytat ze ci moze dojst k poskodeniu dat na oboch stranach. A to takym sposobom ze na jednej strane zacne disk vykazovat chybu, data z neho budu zle precitane a nasledne sa tieto zle precitane data zosynchronizuju s druhou stranou. Dakujem

28
Sítě / Re:Jak co nejlevněji zpřístupnit stroj za NAT
« kdy: 22. 06. 2020, 22:16:36 »
Pouzival som ZeroTier ale na hosting to asi nebude to prave orechove, nakolko klient musi mat nainstalovany taktiez ZeroTier a musi patrit do danej VPN. Napada ma este TOR - tam sa vraj da pristupit na domenu aj bez nainstalovaneho klienta cez tor2web. Toto by teoreticky tiez mohlo fungovat https://openport.io/ https://sshreach.me/init/default/index.html

29
Distribuce / Re:Velký /var/log/syslog
« kdy: 16. 06. 2020, 15:38:49 »
Dakujem za rady, Wifi urcite funguje. Log rotate som nenastavoval, neviem ci je by default, pozriem

30
Distribuce / Velký /var/log/syslog
« kdy: 15. 06. 2020, 11:43:33 »
Zdravim,
moj /var/log/syslog narastol na uctihodnych 17GB a vidim ze sa vnom opakuje nasledujuca hlaska

Kód: [Vybrat]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850071] ------------[ cut here ]------------
Jun 15 10:28:40 lubuntu kernel: [ 7808.850072] wlp16s0:  Failed check-sdata-in-driver check, flags: 0x4
Jun 15 10:28:40 lubuntu kernel: [ 7808.850097] WARNING: CPU: 0 PID: 2991 at /build/linux-CbANGF/linux-4.15.0/net/mac80211/driver-ops.h:18 drv_sta_state+0x165/0x410 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850098] Modules linked in: ccm bnep hp_wmi sparse_keymap wmi_bmof arc4 coretemp kvm_intel kvm irqbypass iwl3945 snd_hda_codec_hdmi snd_hda_codec_analog iwlegacy i915 input_leds joydev snd_hda_codec_generic pcmcia mac80211 serio_raw snd_hda_intel snd_hda_codec drm_kms_helper cfg80211 yenta_socket drm snd_hda_core pcmcia_rsrc snd_hwdep pcmcia_core lpc_ich snd_pcm i2c_algo_bit fb_sys_fops btusb snd_timer btrtl btbcm btintel shpchp bluetooth syscopyarea ecdh_generic snd sysfillrect sysimgblt soundcore wmi tpm_infineon hp_accel lis3lv02d mac_hid input_polldev video sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 psmouse firewire_ohci tg3 pata_acpi firewire_core ptp crc_itu_t pps_core
Jun 15 10:28:40 lubuntu kernel: [ 7808.850120] CPU: 0 PID: 2991 Comm: kworker/0:2 Tainted: G        W        4.15.0-99-generic #100-Ubuntu
Jun 15 10:28:40 lubuntu kernel: [ 7808.850121] Hardware name: Hewlett-Packard HP Compaq 6710b (GB892EA#ABB)/30C0, BIOS 68DDU Ver. F.0B 08/02/2007
Jun 15 10:28:40 lubuntu kernel: [ 7808.850135] Workqueue: events_freezable ieee80211_restart_work [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850150] RIP: 0010:drv_sta_state+0x165/0x410 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850151] RSP: 0000:ffffb739808ff8a8 EFLAGS: 00010282
Jun 15 10:28:40 lubuntu kernel: [ 7808.850152] RAX: 0000000000000000 RBX: ffff8a78f67c0760 RCX: 0000000000000006
Jun 15 10:28:40 lubuntu kernel: [ 7808.850153] RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffff8a78ffc16490
Jun 15 10:28:40 lubuntu kernel: [ 7808.850154] RBP: ffffb739808ff8e0 R08: 0000000011efebab R09: 0000000000000004
Jun 15 10:28:40 lubuntu kernel: [ 7808.850155] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000004
Jun 15 10:28:40 lubuntu kernel: [ 7808.850157] R13: 0000000000000003 R14: ffff8a78f67c0cb8 R15: ffff8a78f685c8c0
Jun 15 10:28:40 lubuntu kernel: [ 7808.850158] FS:  0000000000000000(0000) GS:ffff8a78ffc00000(0000) knlGS:0000000000000000
Jun 15 10:28:40 lubuntu kernel: [ 7808.850159] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 15 10:28:40 lubuntu kernel: [ 7808.850160] CR2: 00007ff3ec8de000 CR3: 00000001328ae000 CR4: 00000000000006f0
Jun 15 10:28:40 lubuntu kernel: [ 7808.850161] Call Trace:
Jun 15 10:28:40 lubuntu kernel: [ 7808.850176]  sta_info_move_state+0x284/0x360 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850191]  __sta_info_destroy_part2+0x36/0x1a0 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850205]  __sta_info_flush+0x139/0x1b0 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850224]  ieee80211_set_disassoc+0xb9/0x400 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850242]  ieee80211_mgd_deauth+0x287/0x440 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850259]  ieee80211_deauth+0x18/0x20 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850274]  cfg80211_mlme_deauth+0xaf/0x1c0 [cfg80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850289]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850304]  cfg80211_disconnect+0x12a/0x1e0 [cfg80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850317]  __cfg80211_leave+0x13e/0x190 [cfg80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850329]  cfg80211_leave+0x2b/0x40 [cfg80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850341]  cfg80211_netdev_notifier_call+0x2dd/0x6a0 [cfg80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850343]  ? __warn+0xa3/0x110
Jun 15 10:28:40 lubuntu kernel: [ 7808.850345]  ? inetdev_event+0x46/0x540
Jun 15 10:28:40 lubuntu kernel: [ 7808.850363]  ? ieee80211_reconfig+0x22c/0x11b0 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850365]  ? skb_dequeue+0x59/0x70
Jun 15 10:28:40 lubuntu kernel: [ 7808.850367]  notifier_call_chain+0x4c/0x70
Jun 15 10:28:40 lubuntu kernel: [ 7808.850368]  raw_notifier_call_chain+0x16/0x20
Jun 15 10:28:40 lubuntu kernel: [ 7808.850370]  call_netdevice_notifiers_info+0x2d/0x60
Jun 15 10:28:40 lubuntu kernel: [ 7808.850372]  __dev_close_many+0x63/0x110
Jun 15 10:28:40 lubuntu kernel: [ 7808.850373]  dev_close_many+0x8c/0x140
Jun 15 10:28:40 lubuntu kernel: [ 7808.850375]  dev_close.part.88+0x4a/0x70
Jun 15 10:28:40 lubuntu kernel: [ 7808.850377]  dev_close+0x19/0x20
Jun 15 10:28:40 lubuntu kernel: [ 7808.850389]  cfg80211_shutdown_all_interfaces+0x77/0xc0 [cfg80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850407]  ieee80211_handle_reconfig_failure+0x98/0xb0 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850425]  ieee80211_reconfig+0x236/0x11b0 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850439]  ieee80211_restart_work+0xbb/0xf0 [mac80211]
Jun 15 10:28:40 lubuntu kernel: [ 7808.850441]  process_one_work+0x1de/0x420
Jun 15 10:28:40 lubuntu kernel: [ 7808.850443]  worker_thread+0x32/0x410
Jun 15 10:28:40 lubuntu kernel: [ 7808.850444]  kthread+0x121/0x140
Jun 15 10:28:40 lubuntu kernel: [ 7808.850446]  ? process_one_work+0x420/0x420
Jun 15 10:28:40 lubuntu kernel: [ 7808.850447]  ? kthread_create_worker_on_cpu+0x70/0x70
Jun 15 10:28:40 lubuntu kernel: [ 7808.850449]  ret_from_fork+0x35/0x40
Jun 15 10:28:40 lubuntu kernel: [ 7808.850451] Code: 48 85 c9 75 e3 e9 56 ff ff ff 49 8b 87 f8 03 00 00 49 8d b7 18 04 00 00 48 c7 c7 48 ae 7f c0 48 85 c0 48 0f 45 f0 e8 7b df 30 d2 <0f> 0b 41 bd fb ff ff ff e9 28 ff ff ff 41 83 fc 02 0f 85 85 00
Jun 15 10:28:40 lubuntu kernel: [ 7808.850471] ---[ end trace 7d4fa9e131952e56 ]---
Jun 15 10:28:40 lubuntu kernel: [ 7808.850482] ------------[ cut here ]------------

Konfiguracia:

Kód: [Vybrat]
wakatana@lubuntu:~$ uname -a
Linux lubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

wakatana@lubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.4 LTS
Release:        18.04
Codename:       bionic

Docasne som sa pokusal syslog vypnut no nevyzera ze to pomohlo

Kód: [Vybrat]
wakatana@lubuntu:~$ sudo systemctl stop rsyslog.service
[sudo] password for marek:
Warning: Stopping rsyslog.service, but it can still be activated by:
  syslog.socket
wakatana@lubuntu:~$ sudo systemctl stop rsyslog.socket
Failed to stop rsyslog.socket: Unit rsyslog.socket not loaded.

wakatana@lubuntu:~$ sudo systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-06-15 11:36:31 CEST; 24s ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
 Main PID: 2019 (rsyslogd)
    Tasks: 4 (limit: 4671)
   CGroup: /system.slice/rsyslog.service
           └─2019 /usr/sbin/rsyslogd -n


Dakujem za kazdu radu

Stran: 1 [2] 3 4 ... 6