|
|||||||||||
06.06.2024., 22:34
|
#3271 |
|
Premium
Datum registracije: May 2006
Lokacija: München/Varaždin
Postovi: 3,465
|
Ko da je tesko grepat...ima tu malo vise sumnjivih stvari (kaj su ti ova 2 cron joba za web browsere?) ali ono kaj je bitno: Code:
lip 06 20:42:42 fedora systemd-resolved[988]: enp6s0: Bus client reset search domain list. lip 06 20:42:42 fedora systemd-resolved[988]: enp6s0: Bus client set default route setting: no lip 06 20:42:42 fedora systemd-resolved[988]: enp6s0: Bus client reset DNS server list. lip 06 20:42:43 fedora systemd-resolved[988]: enp6s0: Bus client set search domain list to: home lip 06 20:42:43 fedora systemd-resolved[988]: enp6s0: Bus client set default route setting: yes lip 06 20:42:43 fedora systemd-resolved[988]: enp6s0: Bus client set DNS server list to: 192.168.1.1 lip 06 20:42:49 fedora systemd-resolved[988]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1. lip 06 20:42:55 fedora systemd-resolved[988]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1. lip 06 20:43:05 fedora systemd-resolved[988]: Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1. lip 06 20:43:10 fedora systemd-resolved[988]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1. lip 06 20:43:31 fedora systemd-resolved[988]: Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1. lip 06 20:43:32 fedora systemd-resolved[988]: enp6s0: Bus client reset search domain list. lip 06 20:43:32 fedora systemd-resolved[988]: enp6s0: Bus client set default route setting: no lip 06 20:43:32 fedora systemd-resolved[988]: enp6s0: Bus client reset DNS server list. lip 06 20:44:52 fedora systemd-resolved[988]: enp6s0: Bus client set search domain list to: home lip 06 20:44:52 fedora systemd-resolved[988]: enp6s0: Bus client set default route setting: yes lip 06 20:44:52 fedora systemd-resolved[988]: enp6s0: Bus client set DNS server list to: 192.168.1.1 lip 06 20:44:53 fedora systemd-resolved[988]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1. Code:
lip 06 20:41:30 fedora NetworkManager[1276]: <info> [1717699290.0687] audit: op="statistics" interface="enp6s0" ifindex=2 args="2000" pid=2167 uid=1000 re> lip 06 20:42:39 fedora NetworkManager[1276]: <info> [1717699359.9295] audit: op="statistics" interface="enp6s0" ifindex=2 args="2000" pid=2167 uid=1000 re> lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.0846] device (enp6s0): state change: activated -> deactivating (reason 'user-requested', s> lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.0848] manager: NetworkManager state is now DISCONNECTING lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.0853] audit: op="device-disconnect" interface="enp6s0" ifindex=2 pid=2167 uid=1000 result=> lip 06 20:42:42 fedora systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... lip 06 20:42:42 fedora systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. lip 06 20:42:42 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatc> lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.1165] device (enp6s0): state change: deactivating -> disconnected (reason 'user-requested'> lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.1167] dhcp4 (enp6s0): canceled DHCP transaction lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.1167] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds) lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.1167] dhcp4 (enp6s0): state changed no lease lip 06 20:42:42 fedora plasmashell[5589]: QHttpNetworkConnectionPrivate::_q_hostLookupFinished could not de-queue request, failed to report HostNotFoundErr> lip 06 20:42:42 fedora plasmashell[5589]: QHttpNetworkConnectionPrivate::_q_hostLookupFinished could not de-queue request, failed to report HostNotFoundErr> lip 06 20:42:42 fedora plasmashell[5589]: QHttpNetworkConnectionPrivate::_q_hostLookupFinished could not de-queue request, failed to report HostNotFoundErr> lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.1467] manager: NetworkManager state is now DISCONNECTED lip 06 20:42:42 fedora NetworkManager[1276]: <info> [1717699362.1476] audit: op="statistics" interface="enp6s0" ifindex=2 args="0" pid=2167 uid=1000 resul> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.5834] device (enp6s0): Activation: starting connection 'Wired connection 2' (6b1d8931-ea89> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.5836] audit: op="connection-activate" uuid="6b1d8931-ea89-3098-abc2-1ad46efc2f30" name="Wi> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.5837] device (enp6s0): state change: disconnected -> prepare (reason 'none', sys-iface-sta> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.5840] manager: NetworkManager state is now CONNECTING lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.5842] device (enp6s0): state change: prepare -> config (reason 'none', sys-iface-state: 'm> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.6052] device (enp6s0): state change: config -> ip-config (reason 'none', sys-iface-state: > lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.6055] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds) lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.6399] dhcp4 (enp6s0): state changed new lease, address=192.168.1.113, acd pending lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.7942] dhcp4 (enp6s0): state changed new lease, address=192.168.1.113 lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.7946] policy: set 'Wired connection 2' (enp6s0) as default for IPv4 routing and DNS lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.8101] device (enp6s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.8122] device (enp6s0): state change: ip-check -> secondaries (reason 'none', sys-iface-sta> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.8123] device (enp6s0): state change: secondaries -> activated (reason 'none', sys-iface-st> lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.8125] manager: NetworkManager state is now CONNECTED_SITE lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.8126] device (enp6s0): Activation: successful, device activated. lip 06 20:42:43 fedora NetworkManager[1276]: <info> [1717699363.8457] audit: op="statistics" interface="enp6s0" ifindex=2 args="2000" pid=2167 uid=1000 re> lip 06 20:42:53 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. lip 06 20:42:53 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatch> lip 06 20:43:30 fedora NetworkManager[1276]: <info> [1717699410.8468] audit: op="statistics" interface="enp6s0" ifindex=2 args="2000" pid=2167 uid=1000 re> lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2072] device (enp6s0): state change: activated -> deactivating (reason 'user-requested', s> lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2075] manager: NetworkManager state is now DISCONNECTING lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2085] audit: op="device-disconnect" interface="enp6s0" ifindex=2 pid=2167 uid=1000 result=> lip 06 20:43:32 fedora systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... lip 06 20:43:32 fedora systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. lip 06 20:43:32 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatc> lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2456] device (enp6s0): state change: deactivating -> disconnected (reason 'user-requested'> lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2458] dhcp4 (enp6s0): canceled DHCP transaction lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2458] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds) lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2458] dhcp4 (enp6s0): state changed no lease lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2726] manager: NetworkManager state is now DISCONNECTED lip 06 20:43:32 fedora NetworkManager[1276]: <info> [1717699412.2733] audit: op="statistics" interface="enp6s0" ifindex=2 args="0" pid=2167 uid=1000 resul> lip 06 20:43:42 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. lip 06 20:43:42 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatch> lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7508] device (enp6s0): Activation: starting connection 'Wired connection 2' (6b1d8931-ea89> lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7510] audit: op="connection-activate" uuid="6b1d8931-ea89-3098-abc2-1ad46efc2f30" name="Wi> lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7510] device (enp6s0): state change: disconnected -> prepare (reason 'none', sys-iface-sta> lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7512] manager: NetworkManager state is now CONNECTING lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7512] device (enp6s0): state change: prepare -> config (reason 'none', sys-iface-state: 'm> lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7632] device (enp6s0): state change: config -> ip-config (reason 'none', sys-iface-state: > lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7635] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds) lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.7920] dhcp4 (enp6s0): state changed new lease, address=192.168.1.113, acd pending lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.9772] dhcp4 (enp6s0): state changed new lease, address=192.168.1.113 lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.9775] policy: set 'Wired connection 2' (enp6s0) as default for IPv4 routing and DNS lip 06 20:44:52 fedora NetworkManager[1276]: <info> [1717699492.9927] device (enp6s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state> lip 06 20:44:52 fedora systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... lip 06 20:44:53 fedora systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. lip 06 20:44:53 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatc> lip 06 20:44:53 fedora NetworkManager[1276]: <info> [1717699493.0045] device (enp6s0): state change: ip-check -> secondaries (reason 'none', sys-iface-sta> lip 06 20:44:53 fedora NetworkManager[1276]: <info> [1717699493.0046] device (enp6s0): state change: secondaries -> activated (reason 'none', sys-iface-st> lip 06 20:44:53 fedora NetworkManager[1276]: <info> [1717699493.0049] manager: NetworkManager state is now CONNECTED_SITE lip 06 20:44:53 fedora NetworkManager[1276]: <info> [1717699493.0050] device (enp6s0): Activation: successful, device activated. lip 06 20:44:53 fedora NetworkManager[1276]: <info> [1717699493.0248] audit: op="statistics" interface="enp6s0" ifindex=2 args="2000" pid=2167 uid=1000 re> lip 06 20:44:53 fedora NetworkManager[1276]: <info> [1717699493.0844] manager: NetworkManager state is now CONNECTED_GLOBAL lip 06 20:45:03 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. lip 06 20:45:03 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatch> Code:
ip 06 20:42:42 fedora avahi-daemon[1024]: Withdrawing address record for 192.168.1.113 on enp6s0. lip 06 20:42:42 fedora avahi-daemon[1024]: Leaving mDNS multicast group on interface enp6s0.IPv4 with address 192.168.1.113. lip 06 20:42:42 fedora avahi-daemon[1024]: Interface enp6s0.IPv4 no longer relevant for mDNS. lip 06 20:42:43 fedora avahi-daemon[1024]: Joining mDNS multicast group on interface enp6s0.IPv4 with address 192.168.1.113. lip 06 20:42:43 fedora avahi-daemon[1024]: New relevant interface enp6s0.IPv4 for mDNS. lip 06 20:42:43 fedora avahi-daemon[1024]: Registering new address record for 192.168.1.113 on enp6s0.IPv4. lip 06 20:43:32 fedora avahi-daemon[1024]: Withdrawing address record for 192.168.1.113 on enp6s0. lip 06 20:43:32 fedora avahi-daemon[1024]: Leaving mDNS multicast group on interface enp6s0.IPv4 with address 192.168.1.113. lip 06 20:43:32 fedora avahi-daemon[1024]: Interface enp6s0.IPv4 no longer relevant for mDNS. lip 06 20:44:52 fedora avahi-daemon[1024]: Joining mDNS multicast group on interface enp6s0.IPv4 with address 192.168.1.113. lip 06 20:44:52 fedora avahi-daemon[1024]: New relevant interface enp6s0.IPv4 for mDNS. lip 06 20:44:52 fedora avahi-daemon[1024]: Registering new address record for 192.168.1.113 on enp6s0.IPv4. enp6s0 je 2.5G ili 1G mrezna? Ignoriraj ove gore protivnike gore systemd-a. Ja sam gori. Da govno je al je standard hocemo ili necemo i mora s tim radit. Zaobilazenje problema ne rijesava nikad dugorocno problem. Razumijevanje uzroka problema ga rijesava. Resolv.conf je nebitan ako je sve ostalo postavljeno kak spada osim ak je opet neki KDE bug. 0. Nemoj se zajebavat s tim ak si umoran - odmori pa onda cekiraj 1. Prvo i osnovno imas 2 mrezne - kak su postelane? Su obje aktivne? Gateway si samo na primarnoj definirao ili? Jel imas kakve ifcfg fajlove osim lo u /etc/sysconfig/network-scripts/ ? 2. setroubleshoot nije komanda nego grepas za tim u syslogu (journalctl -xe ili u /var/log/messages ili journalctl -t setroubleshoot) 3. Ako zelis vidjet sto je instalirano > Code:
rpm -qa |grep firmware 4. Ne vjerujem da te selinux kolje ali postavi ga na permissive (/etc/selinux/config) i rebootaj komp Smrdi mi na problem koji je Ivo opisao. Mozda ne direktno nekompatibilnost nego neki usrani power saving feature. Ili KDE bug (bilo je nesto da je KDE 6 sjebo na nekim distrama mrezne servise). P.S.- kod mene B550M Pro VDH-WIFI: 2a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15) rpm -qa |grep realtek realtek-firmware-20240513-1.fc40.noarch Mrezne postavke na kompu nisam ni pipnuo od instalacije. Preuzima najnormalnije default od routera sve. Razlika je kaj se kod mene vrti Gnome. Zadnje izmijenjeno od: tomek@vz. 06.06.2024. u 23:00. |
|
|
|
06.06.2024., 22:48
|
#3272 |
|
Premium
Datum registracije: Sep 2018
Lokacija: tu
Postovi: 2,069
|
Ne znam što ste se toliko za log uhvatili, pa dao sam par desetaka linija. Htio sam da se vidi malo šire što se dešava. Miopija često šteti. Evo ti ovo za sada. Code:
root@fedora:~# resolvectl
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (enp6s0)
Current Scopes: DNS LLMNR/IPv4
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: home
Link 3 (enp42s0)
Current Scopes: none
Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Prebacio sam se sada na enp42s0. Nisam o ovome vodio računa, moguće da sam se i nehotice prebacio s jednog na drugi kada sam zadnji put ubacivao lan u drugi uređaj. Code:
root@fedora:~# rpm -qa |grep firmware alsa-sof-firmware-2024.03-2.fc40.noarch linux-firmware-whence-20240513-1.fc40.noarch amd-gpu-firmware-20240513-1.fc40.noarch amd-ucode-firmware-20240513-1.fc40.noarch atheros-firmware-20240513-1.fc40.noarch brcmfmac-firmware-20240513-1.fc40.noarch cirrus-audio-firmware-20240513-1.fc40.noarch intel-audio-firmware-20240513-1.fc40.noarch intel-gpu-firmware-20240513-1.fc40.noarch mt7xxx-firmware-20240513-1.fc40.noarch nvidia-gpu-firmware-20240513-1.fc40.noarch nxpwireless-firmware-20240513-1.fc40.noarch realtek-firmware-20240513-1.fc40.noarch tiwilink-firmware-20240513-1.fc40.noarch linux-firmware-20240513-1.fc40.noarch iwlegacy-firmware-20240513-1.fc40.noarch iwlwifi-dvm-firmware-20240513-1.fc40.noarch iwlwifi-mvm-firmware-20240513-1.fc40.noarch libertas-firmware-20240513-1.fc40.noarch Code:
*-pci:2
description: PCI bridge
product: Advanced Micro Devices, Inc. [AMD]
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 7
bus info: pci@0000:03:07.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci msi pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:38 ioport:e000(size=4096) memory:fc300000-fc3fffff
*-network
description: Ethernet interface
product: RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:06:00.0
logical name: enp6s0
version: 15
serial: 2c:f0:5d:5d:72:7d
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiatio
n
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.8.11-300.fc40.x86_64 firmware=rtl8168h-2_0.0.2 02/26/15 l
atency=0 link=no multicast=yes port=twisted pair
resources: irq:37 ioport:e000(size=256) memory:fc304000-fc304fff memory:fc300000-fc303fff
*-pci:3
description: PCI bridge
product: Advanced Micro Devices, Inc. [AMD]
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 9
bus info: pci@0000:03:09.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pci msi pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:40 ioport:d000(size=4096) memory:fc200000-fc2fffff
*-network
description: Ethernet interface
product: RTL8125 2.5GbE Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:2a:00.0
logical name: enp42s0
version: 04
serial: 2c:f0:5d:5d:72:7c
size: 1Gbit/s
capacity: 2500Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd 2500bt-fd
autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.8.11-300.fc40.x86_64 duplex=full firmware=rtl8125b-2_0.0.
2 07/13/20 ip=192.168.1.111 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:39 ioport:d000(size=256) memory:fc200000-fc20ffff memory:fc210000-fc213fff
Code:
journalctl -xe | grep setroubleshoot ne vrati ništa
__________________
Zadnje izmijenjeno od: mkey. 06.06.2024. u 22:57. |
|
|
|
|
06.06.2024., 22:52
|
#3273 | |
|
Premium
Datum registracije: Feb 2007
Lokacija: Istra
Postovi: 3,023
|
Citiraj:
Odustajem. Ti si baš ne daš pomoći... ko s malom djecom... |
|
|
|
|
|
06.06.2024., 22:59
|
#3274 |
|
Premium
Datum registracije: Sep 2018
Lokacija: tu
Postovi: 2,069
|
shadow, ne čitaš što čovjek koji traži pomoć piše. Što očekuješ? I nije ti prvi puta da se tako ponašaš. Hvala na vremenu. Sada sam već napravio 22 edita, nema smisla. Tomek, ti cronjobovi pojma nemam što rade tamo. Možda neki update? Maknut ću te browsere pošto ih i tako ne koristim i kao pokušavam se skrasiti na librefox. Thorium je instaliran kao RPM, sada sam maknuo. A za vivaldi sam dodao repositorij, maknem i to.
__________________
|
|
|
|
|
07.06.2024., 09:51
|
#3275 | |
|
Premium
Datum registracije: Aug 2006
Lokacija: Zagreb, Sesvetski Kraljevec
Postovi: 560
|
Citiraj:
 Linux desktop nije server i nemaš brige da će netko preuzeti tvoj nestandardizirani kaos, i u tom slučaju ne vidim razlog zašto bi se nešto moralo... ljepota Linux desktopa upravo i je u mogućnosti izbora i slobodi customiziranja. |
|
|
|
|
|
07.06.2024., 10:26
|
#3277 | ||
|
Premium
Datum registracije: May 2006
Lokacija: München/Varaždin
Postovi: 3,465
|
Citiraj:
Ti cronjobovi nisu uzrok problema samo me zanimalo zasto. No da se vratimo tvom problemu. Ono sto me zanimalo koja mrezna zeza i puca veza. Dakle: 1. Puca na Gigabit LAN 2. Imas instaliran ispravan firmware Mislim da saltanje mreznih nebu pomoglo. Mozes ostavit kao test sad na 2.5G cisto da iskljucimo mogucnost da je 1G kartica neispravna. Tvoj komp uvijek pita Router kao DNS server kad hoce van. Ono kaj bi trebao provjeriti ako budes u mogucnosti - kad se ponovi to sranje - jel mozes pingat router? Da nije da na Routeru nekaj sere pa je Fedora osjetljiva na to...mozda...valjda...testirat. Suma sumarum - imas skoro identican setup kao i ja - jedina razlika je GUI. TO MORA RADIT DA GA HEBES. Citiraj:
 (dida mi je iz Rupa porijeklom). E moj Dule da pricamo o sigurnosti da se mene pita systemd bi letio sa server distri dok si reko keks. BSD pristup mi je na severima iskreno drazi....Ako nesto na serveru ne zelim je automatizacija koja pokusava biti pametnija od (sposobnijih) admina. Samim time je potencijal za ogromnu sigurnosnu rupu i iskreno privat su mi draze distre kao Alpine sve vise i vise. Al hebiga - badava ti odlican OS ak ono kaj trebas gore ne dela il ne dela kak spada. Za desktop Linux systemd je postala kicma za sve ostalo sto mora radit ko "magijom". Kad to iscupas - skrsis previse toga jednostavno na distrama kojima je systemd primani backbone. Systemd je jedna od stvari koju Linux ne treba al bez nje moderan Desktop Linux sustav jednostavno ne funkcionira kak Ivica i Marica ocekuju. Ako imas vremena i znanja - da naravno da mozes raditi sa non-systemd distrom. Ali iskreno - moram priznati da je meni osobno zivot s njim laksi, elegantniji i stvari 99,9% vremena - rade kako je zamisljeno. Kad ne - onda mu hebem mater i sve po spisku. |
||
|
|
|
|
08.06.2024., 14:06
|
#3278 |
|
Premium
Datum registracije: Sep 2018
Lokacija: tu
Postovi: 2,069
|
> jel mozes pingat router? Budem probao, ali prilično sam siguran da da, jer mogu sve što sam probao pingat sa IP adresom. Torrenti rade normalno, promet teče. > TO MORA RADIT DA GA HEBES. I bit će tako, samo da mu damo malo vremena i živaca Gledao sam ovaj svoj ruter, nema custom DNS opciju. Koji bi bio najpametniji način za podesiti DNS na kompu? Prošlog puta kada sam to radio sam napravio 15 stvari, možda ipak bolje pitati nego poslije popravljati Inače, jučer nisam imao nikakvih problema, ali nisam niti palio komp uopće, pa moguće zbog toga. Danas budemo vidjeli što je na meniju.
__________________
|
|
|
|
|
08.06.2024., 14:25
|
#3279 |
|
Moderator
Datum registracije: Sep 2006
Lokacija: St
Postovi: 22,674
|
A hebemu miša, fino postavi fiksne mrežne postavke za tu mrežnu preko je si spojen, IP, Subnet, Gateway, DNS1, DNS2. Većina operatera prilikom svoje idiot customizacije sklanja opciju custom definiranja DNS - ova jer forsiraju svoje. Fino otvori taj svoj xyz router, ako već nije u DHCP Serveru oslobodi / ostavi si xy IP adresa slobodno za klijente sa fiksnim IP adresama. Nakon toga je lako, ako zapneš onda pitaj  |
|
|
|
08.06.2024., 14:41
|
#3280 | |
|
Premium
Datum registracije: May 2006
Lokacija: München/Varaždin
Postovi: 3,465
|
Citiraj:
U Network Manageru...fino klik klik  Ak hoces u konzoli - nmtui (instaliras ak ti fali) ili nmcli. |
|
|
|
|
|
08.06.2024., 16:25
|
#3281 |
|
Premium
Datum registracije: Nov 2004
Lokacija: HR
Postovi: 778
|
stubby |
|
|
|
|
09.06.2024., 13:04
|
#3283 | |
|
Premium
Datum registracije: May 2006
Lokacija: München/Varaždin
Postovi: 3,465
|
Citiraj:
Router. Ovako doznas koje DNS-ove ti Fedora koristi: ( nmcli dev list || nmcli dev show ) 2>/dev/null | grep DNS IP4.DNS[1]: 1.1.1.2 IP4.DNS[2]: 1.0.0.2 Alternativno: systemd-resolve --status | grep "DNS Servers" |
|
|
|
|
|
09.06.2024., 15:02
|
#3284 |
|
Premium
Datum registracije: Sep 2018
Lokacija: tu
Postovi: 2,069
|
Opet izletilo. Pinganje 192.168.1.1 radi bez problema. Ovo i dalje ništa ne vraća. Code:
root@fedora:~# journalctl -xe | grep setroubleshoot root@fedora:~# Probao "sudo nmcli con reload enp42s0" ali to nije riješilo problem. Probao "sudo systemctl restart NetworkManager" i to je riješilo problem. Žao mi je da nisam pogledao što kaže "systemctl status systemd-resolved.service" dok problem traje, budem idući puta. Stavio sam provizorno Open DNS. Code:
[mkey@fedora ~]$ ( nmcli dev list || nmcli dev show ) 2>/dev/null | grep DNS IP4.DNS[1]: 208.67.222.222 IP4.DNS[2]: 208.67.220.220 Code:
[mkey@fedora ~]$ systemd-resolve --status | grep "DNS Servers"
DNS Servers: 208.67.222.222 208.67.220.220
Vjerojatno treba jedan restart network managera da prihvati? nikky opet precjenujuje moje znanje mreža, fatalna greška.Ovo su moje DHCP postavke na ruteru. Ipak ima DNS pa sam ga i tu postavio.-> https://imgur.com/a/WjQuDGI Ovo su network manager postavke. -> https://imgur.com/RK17NXb (SS pokazuje 110, postavio sam na 100 na kraju) Meni je ovaj GUI bio toliko jasan da sam na kraju posegnuo za terminalom. Ako je GUI manje jasan od komandi u terminalu onda znaš da nešto nije u redu Mrzim to reći, ali ekvivalentne postavke u windowsima su ipak puno jasnije.Code:
nmcli con mod "Wired connection 2" ipv4.addresses "192.168.1.100" ipv4.gateway "192.168.1.1" ipv4.dns "208.67.222.222,208.67.220.220" ipv4.dns-search "fedora" ipv4.method "manual" Nisam siguran zašto ifconfig kaže 111. Code:
root@fedora:~# ifconfig
enp42s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.111 netmask 255.255.255.0 broadcast 192.168.1.255
ether 2c:f0:5d:5d:72:7c txqueuelen 1000 (Ethernet)
RX packets 13638411 bytes 2278532391 (2.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29224194 bytes 16596583333 (15.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
EDIT: ifconfig pokazuje 100 nakon reboota.
__________________
Zadnje izmijenjeno od: mkey. 09.06.2024. u 15:15. |
|
|
|
|
09.06.2024., 15:52
|
#3285 |
|
Moderator
Datum registracije: Sep 2006
Lokacija: St
Postovi: 22,674
|
DHCP Server pool si stavio od 192.168.1.110 do 192.168.1.199, znači da za klijente sa fiksnim mrežnim postavkama imaš na raspolaganju od 192.168.1.2 do 192.168.1.109 + još odr, br adresa "na kraju" do 192.168.1.254. Dakle, za taj komp stavi recimo IP = 192.168.1.5, za svaki drugi ide različita IP adresa. Vidim da si našao gdje se postavlja custom DNS u routeru i na kompu, kad se već baviš svime tim, nije zgorega da sekundarni bude od drugog "davatelja usluge", u prevodu za Primarni si stavio Open DNS, za secondary stavi recimo Google (8.8.8.8). Inače bravo, sve si pohvatao |
|
|
|
|
09.06.2024., 16:08
|
#3288 |
|
Moderator
Datum registracije: Sep 2006
Lokacija: St
Postovi: 22,674
|
I ne mora, jeli može CloudFlare (1.1.1.1) ? Za žuntu DNS by ISP Sticky > http://forum.pcekspert.com/showthread.php?t=91801 |
|
|
|
|
10.06.2024., 17:35
|
#3290 | |
|
Premium
Datum registracije: May 2006
Lokacija: München/Varaždin
Postovi: 3,465
|
Heads up... Citiraj:
https://www.gamingonlinux.com/2024/0...e-on-a-laptop/  |
|
|
|
|
|
Jučer, 19:14
|
#3291 |
|
Premium
Datum registracije: Sep 2018
Lokacija: tu
Postovi: 2,069
|
Novi dan, novi problemi. Naime, primijetio sam da zadnjih par puta (sada već 3 od 3 ukupno, čini mi se prvi puta da je bio problem u subotu) kad napravim shutdown računalo zaglavi u nekoj fazi i ne mrda. Dobijem crni ekran s pointerom od miša. Ne reagira na podražaje osim TTY. Shutdown kreće odavde (oko 22:15) Code:
lip 11 22:15:16 fedora systemd[1608]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service. Code:
lip 11 22:18:13 fedora login[20081]: LOGIN ON tty3 BY mkey https://pastebin.com/AdgU5EqK Jedino što mi pada na pamet je sitan povremen problem kojeg imam s MX Master 3S i njegom donglom. Svako toliko (možda jednom od deset puta) kod dizanja iz standby miš kao da nije prepoznat, pa onda izvadim dongle i vratim ga u isti USB port i onda proradi. Isti problem je bio prisutan i u manjaru. Neki dan se dogodilo da je isti miš ostao prazne baterije i prestao raditi. Onda sam ga spojio na punjač ali nakon toga ga OS više nije prepoznavao odnosno primao input. Prebacio sam se privremeno na starog žičanog MX518 i nešto kasnije master je opet radio. Imao sam do jučer ugašen verbose boot, sada sam maknuo one dvije opcije iz /etc/default/grub i rebuildao grub.cfg, pa budem vidio kako će se dalje ponašati. Također bi možda bilo pametno probati s waylandom i provjeriti da li se i tamo dešava.
__________________
|
|
|
|
|
Jučer, 20:08
|
#3292 |
|
49%winner
Datum registracije: Sep 2007
Lokacija: PU
Postovi: 8,882
|
Ima neko vrijeme da sam se i ja vratio na Fedoru... zasad imam malo vise srece od kolege iznad. Mozda jer svaki put nakon njegovog posta triput pljunem u kantu za smece i zapalim mirisni stapic pored kompjutera ^^,
__________________
♕ Keep calm and fastboot oem unlock. ♕
|
|
|
|
|
Jučer, 20:09
|
#3293 | |
|
Premium
Datum registracije: May 2006
Lokacija: München/Varaždin
Postovi: 3,465
|
Citiraj:
Ili se neka apikacija ne zeli ugasiti ili te nekaj od HW hebe. Postavio si KDE da se uvijek sa clean seassionom starta nadam se a ne da uvijek vraca sve od prosli puta? Ako smatras da bi te Logi mogao zezat - probaj sa iskljucenim misem pa vidi jel se isto ponasa. Cekiraj i ovo: https://itsfoss.com/long-shutdown-li...dirty%20fix%5D Pa javi rezultate. P.S.: https://bbs.archlinux.org/viewtopic.php?id=283539 Kod mene je GDM+Gnome....just saying :P |
|
|
|
|
|
Jučer, 21:25
|
#3295 |
|
Premium
Datum registracije: Sep 2018
Lokacija: tu
Postovi: 2,069
|
Radije bih se na windows vratio nego da gnome koristim. Nije niti do jedne aplikacije, na čistom startupu isti problem. Čisti session koristim, pogotovo pošto u 90+% slučajeva koristim standby. Verbose kernel logging (kako li se to već zove) ne igra ulogu jer izgleda da x server niti ne izađe vanka nego pusti samo crni ekran s funkcionalnim pokazivačem miša. Zanimljiva situacija se dogodila tijekom testiranja gdje sam na desktopu samo konsole imao otvoren, napravim shutdown, crna pozadina, pointer i konsole ostao otvoren. Ukucam reboot, enter i ode dolje bez problema. Dakle problem je isključivo s shutdown/restart preko GUI iz menija, ne sa reboot/shutdown naredbom koje rade kako spada. Problem je izgleda riješen s prisilnom reinstalacijom/rebuildanjem nevidijinih sranja. Malo me prckao akmods i nije htio odraditi pa nakon nešto peripetija i bootanja u prethodni kernel ipak je odradio. Užasno je ovo njesra osjetljivo, i ako ne odradi do kraja ne znaš dok ne uletiš u probleme. Pustio sam ga 10 minuta i napravio reboot natrag u 11 kernel. Code:
sudo dnf remove kmod-nvidia-6.8.11\* sudo akmods --force --kernels 6.8.11-300.fc40.x86_64 Code:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Micro-Star MSI
driver: nvidia v: 550.78 arch: Pascal pcie: speed: 8 GT/s lanes: 16 ports:
active: none off: DP-3 empty: DP-1, DP-2, DVI-D-1, HDMI-A-1
bus-ID: 2b:00.0 chip-ID: 10de:1b81 class-ID: 0300
EDIT: Što se tiče tih SDDM poruka, drugdje sam našao da se to može komotno ignorirati. Da ga dosta trkelja, i preporučuju ugasiti to logiranje.
__________________
Zadnje izmijenjeno od: mkey. Jučer u 21:32. |
|
|
|
|
Jučer, 21:59
|
#3296 |
|
Premium
Datum registracije: May 2006
Lokacija: München/Varaždin
Postovi: 3,465
|
M...da ti nije bio kernel ili driver update? Rebuild nvidia drivera zna potrajat par minuta. P.S. - znam da mnogi imaju averziju prema Gnome sucelju ali - isprobaj malo druga sucelja...najcesce su bolje ispolirani (barem po mom iskustvu) nego KDE iako nije KDE 6 los. Samo kaj sam uvijek na neke bugove naletio na koje sam popoizdio. Na gnome lupis par extenzija koje ti pasu i vozi misko. Kazem - sprobaj par dana, nemas kaj izgubiti, ak ti se nakon toga ne svidi - hebiga |
|
|
|
|
Jučer, 22:43
|
#3297 |
|
Premium
Datum registracije: Sep 2018
Lokacija: tu
Postovi: 2,069
|
Ne znam kada je bio zadnji kernel update, nisam pratio. Moram o tome više voditi računa. Probao sam tonu DE i KDE mi najviše odgovara, ima sve šta mi treba out of the box. A bugovi kao bugovi, nema gdje ih nema.
__________________
|
|
|
|
 |
|
|
