Dzisiaj jest 25 wrz 2022, 14:08

Strefa czasowa UTC+1godz. [letni]




Nowy temat Odpowiedz w temacie  [ Posty: 6 ] 
Autor Wiadomość
 Tytuł: Brak Wi-Fi w Netgear R6220 - wina sprzetu, czy softu?
Post: 16 cze 2022, 19:11 
Offline
Użytkownik
Awatar użytkownika

Rejestracja: 25 lut 2011, 22:28
Posty: 722
W jednym z moich routerów Netgear R6220 zniknęło Wi-Fi.
W konfiguracji nic nie grzebałem, restart urządzenia nie pomaga.
wifi status
mówi:
{
        "radio0": {
                "up": false,
                "pending": false,
                "autostart": true,
                "disabled": false,
                "retry_setup_failed": true,
                "config": {
                        "hwmode": "11g",
                        "path": "1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0",
                        "htmode": "HT40",
                        "channel": "9",
                        "cell_density": 0
                },
                "interfaces": [
                        {
                                "section": "default_radio0",
                                "config": {
                                        "mode": "ap",
                                        "ssid": "**1",
                                        "encryption": "psk2",
                                        "key": "*************************",
                                        "network": [
                                                "lan"
                                        ],
                                        "mode": "ap"
                                },
                                "vlans": [

                                ],
                                "stations": [

                                ]
                        }
                ]
        },
        "radio1": {
                "up": false,
                "pending": false,
                "autostart": true,
                "disabled": false,
                "retry_setup_failed": true,
                "config": {
                        "hwmode": "11a",
                        "path": "1e140000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0",
                        "htmode": "VHT80",
                        "channel": "64",
                        "country": "PL",
                        "cell_density": 0,
                        "disabled": false
                },
                "interfaces": [
                        {
                                "section": "default_radio1",
                                "config": {
                                        "mode": "ap",
                                        "ssid": "**5",
                                        "encryption": "psk2",
                                        "key": "*************************",
                                        "network": [
                                                "lan"
                                        ],
                                        "mode": "ap"
                                },
                                "vlans": [

                                ],
                                "stations": [

                                ]
                        }
                ]
        }
}

Macie pomysł co z tym zrobić?

_________________
Halny HL-4GMV + 2xNetgear R6220 (OpenWrt 22.03 z LuCI)
System: OpenSUSE
http://software.opensuse.org/


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Brak Wi-Fi w Netgear R6220 - wina sprzetu, czy softu?
Post: 16 cze 2022, 20:40 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 14083
Lokalizacja: Warszawa
logread i zobacz czy nie masz błędów odczytu squashfs.

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Brak Wi-Fi w Netgear R6220 - wina sprzetu, czy softu?
Post: 17 cze 2022, 01:03 
Offline
Użytkownik
Awatar użytkownika

Rejestracja: 25 lut 2011, 22:28
Posty: 722
Trochę tego jest:
hu Jun 16 19:01:07 2022 kern.err kernel: [    5.172239] SQUASHFS error: xz decompression failed, data probably corrupt
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.185999] SQUASHFS error: squashfs_read_data failed to read block 0x1429da
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.200040] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.213387] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.226775] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.240121] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.253482] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.266837] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.280198] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.293542] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.306907] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.320254] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.333615] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.346962] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.360325] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.373677] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.387055] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.400403] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.413783] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.427129] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.440503] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [    5.453854] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 user.info kernel: [    5.474101] init: - preinit -
Thu Jun 16 19:01:07 2022 kern.info kernel: [    6.314879] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
Thu Jun 16 19:01:07 2022 kern.info kernel: [    6.330958] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Thu Jun 16 19:01:07 2022 kern.info kernel: [    6.348346] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Jun 16 19:01:07 2022 kern.notice kernel: [    6.550395] random: jshn: uninitialized urandom read (4 bytes read)
Thu Jun 16 19:01:07 2022 kern.notice kernel: [    6.670050] random: jshn: uninitialized urandom read (4 bytes read)
Thu Jun 16 19:01:07 2022 kern.notice kernel: [    6.715856] random: jshn: uninitialized urandom read (4 bytes read)
Thu Jun 16 19:01:07 2022 kern.info kernel: [    6.947882] mt7530 mdio-bus:1f lan1: configuring for phy/gmii link mode
Thu Jun 16 19:01:07 2022 kern.info kernel: [    6.961477] 8021q: adding VLAN 0 to HW filter on device lan1
Thu Jun 16 19:01:07 2022 kern.info kernel: [   11.070344] mt7530 mdio-bus:1f lan1: Link is Up - 1Gbps/Full - flow control rx/tx
Thu Jun 16 19:01:07 2022 kern.info kernel: [   11.085385] IPv6: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.225136] UBIFS (ubi0:1): Mounting in unauthenticated mode
Thu Jun 16 19:01:07 2022 kern.warn kernel: [   11.226612] urandom_read: 6 callbacks suppressed
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.226625] random: procd: uninitialized urandom read (4 bytes read)
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.259656] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 559
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.325140] UBIFS (ubi0:1): recovery needed
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.512986] UBIFS (ubi0:1): recovery completed
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.522039] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.537643] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.557403] UBIFS (ubi0:1): FS size: 20697088 bytes (19 MiB, 163 LEBs), journal size 1015809 bytes (0 MiB, 8 LEBs)
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.578027] UBIFS (ubi0:1): reserved for root: 977574 bytes (954 KiB)
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   11.590867] UBIFS (ubi0:1): media format: w5/r0 (latest is w5/r0), UUID 534026A7-759D-4D44-9CA3-B537A346CA05, small LPT model
Thu Jun 16 19:01:07 2022 user.info kernel: [   11.620041] mount_root: switching to ubifs overlay
Thu Jun 16 19:01:07 2022 user.warn kernel: [   11.646740] urandom-seed: Seeding with /etc/urandom.seed
Thu Jun 16 19:01:07 2022 kern.info kernel: [   11.784976] mt7530 mdio-bus:1f lan1: Link is Down
Thu Jun 16 19:01:07 2022 user.info kernel: [   11.804357] procd: - early -
Thu Jun 16 19:01:07 2022 user.info kernel: [   11.810223] procd: - watchdog -
Thu Jun 16 19:01:07 2022 user.info kernel: [   12.417850] procd: - watchdog -
Thu Jun 16 19:01:07 2022 user.info kernel: [   12.427464] procd: - ubus -
Thu Jun 16 19:01:07 2022 user.info kernel: [   12.491761] procd: - init -
Thu Jun 16 19:01:07 2022 kern.err kernel: [   13.238818] SQUASHFS error: xz decompression failed, data probably corrupt
Thu Jun 16 19:01:07 2022 kern.err kernel: [   13.252608] SQUASHFS error: squashfs_read_data failed to read block 0x1429da
Thu Jun 16 19:01:07 2022 kern.err kernel: [   13.266657] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [   13.280012] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 kern.err kernel: [   13.293394] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:07 2022 kern.err kernel: [   13.306750] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:07 2022 user.info kernel: [   13.475465] urngd: v1.0.2 started.
Thu Jun 16 19:01:07 2022 kern.notice kernel: [   13.704482] random: crng init done
Thu Jun 16 19:01:09 2022 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Thu Jun 16 19:01:09 2022 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: Connected to system UBus
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: started, version 2.84 cachesize 150
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: DNS service limited to local subnets
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: UBus support enabled: connected to system bus
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: using only locally-known addresses for domain test
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: using only locally-known addresses for domain onion
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: using only locally-known addresses for domain localhost
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: using only locally-known addresses for domain local
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: using only locally-known addresses for domain invalid
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: using only locally-known addresses for domain bind
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: using only locally-known addresses for domain lan
Thu Jun 16 19:01:09 2022 daemon.warn dnsmasq[1001]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: read /etc/hosts - 4 addresses
Thu Jun 16 19:01:09 2022 daemon.info dnsmasq[1001]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Thu Jun 16 19:01:10 2022 authpriv.info dropbear[1063]: Not backgrounding
Thu Jun 16 19:01:10 2022 daemon.notice wpa_supplicant[1113]: Successfully initialized wpa_supplicant
Thu Jun 16 19:01:11 2022 user.notice : Added device handler type: 8021ad
Thu Jun 16 19:01:11 2022 user.notice : Added device handler type: 8021q
Thu Jun 16 19:01:11 2022 user.notice : Added device handler type: macvlan
Thu Jun 16 19:01:11 2022 user.notice : Added device handler type: veth
Thu Jun 16 19:01:11 2022 user.notice : Added device handler type: bridge
Thu Jun 16 19:01:11 2022 user.notice : Added device handler type: Network device
Thu Jun 16 19:01:11 2022 user.notice : Added device handler type: tunnel
Thu Jun 16 19:01:11 2022 cron.err crond[1292]: crond (busybox 1.33.0) started, log level 5
Thu Jun 16 19:01:12 2022 daemon.notice procd: /etc/rc.d/S50uhttpd: 4+0 records in
Thu Jun 16 19:01:12 2022 daemon.notice procd: /etc/rc.d/S50uhttpd: 4+0 records out
Thu Jun 16 19:01:12 2022 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/dhcp
Thu Jun 16 19:01:12 2022 user.notice ucitrack: Setting up /etc/config/wireless reload dependency on /etc/config/network
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/luci-splash
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/qos
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/miniupnpd
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/odhcpd
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up non-init /etc/config/fstab reload handler: /sbin/block mount
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up /etc/config/system reload trigger for non-procd /etc/init.d/led
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/luci_statistics
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.672107] SQUASHFS error: xz decompression failed, data probably corrupt
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.685878] SQUASHFS error: squashfs_read_data failed to read block 0x1429da
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.700102] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:13 2022 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/dhcp
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.713567] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.727100] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.740547] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.764630] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.778158] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.791666] SQUASHFS error: Unable to read fragment cache entry [1429da]
Thu Jun 16 19:01:13 2022 kern.err kernel: [   20.805136] SQUASHFS error: Unable to read page, block 1429da, size a52c
Thu Jun 16 19:01:14 2022 kern.info kernel: [   20.835507] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
Thu Jun 16 19:01:14 2022 daemon.debug dnsmasq[1001]: stopped listening on eth0(#2): fe80::2e30:33ff:fe34:5498%eth0 port 53
Thu Jun 16 19:01:14 2022 kern.info kernel: [   20.924281] mtk_soc_eth 1e100000.ethernet eth0: configuring for fixed/rgmii link mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   20.940592] mtk_soc_eth 1e100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Thu Jun 16 19:01:14 2022 kern.info kernel: [   20.957998] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Jun 16 19:01:14 2022 kern.info kernel: [   20.974597] mt7530 mdio-bus:1f lan1: configuring for phy/gmii link mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   20.990384] 8021q: adding VLAN 0 to HW filter on device lan1
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.013173] br-lan: port 1(lan1) entered blocking state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.023888] br-lan: port 1(lan1) entered disabled state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.040603] device lan1 entered promiscuous mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.049960] device eth0 entered promiscuous mode
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Interface 'lan' is enabled
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.079107] mt7530 mdio-bus:1f lan2: configuring for phy/gmii link mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.112166] 8021q: adding VLAN 0 to HW filter on device lan2
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.127282] br-lan: port 2(lan2) entered blocking state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.137844] br-lan: port 2(lan2) entered disabled state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.149907] device lan2 entered promiscuous mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.173338] mt7530 mdio-bus:1f lan3: configuring for phy/gmii link mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.197141] 8021q: adding VLAN 0 to HW filter on device lan3
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.212089] br-lan: port 3(lan3) entered blocking state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.222651] br-lan: port 3(lan3) entered disabled state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.239090] device lan3 entered promiscuous mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.261354] mt7530 mdio-bus:1f lan4: configuring for phy/gmii link mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.278512] 8021q: adding VLAN 0 to HW filter on device lan4
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.294412] br-lan: port 4(lan4) entered blocking state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.304991] br-lan: port 4(lan4) entered disabled state
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.317517] device lan4 entered promiscuous mode
Thu Jun 16 19:01:14 2022 daemon.debug dnsmasq[1001]: listening on lo(#1): 127.0.0.1 port 53
Thu Jun 16 19:01:14 2022 daemon.debug dnsmasq[1001]: listening on lo(#1): ::1 port 53
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Interface 'loopback' is enabled
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Interface 'loopback' is now up
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.353053] mt7530 mdio-bus:1f wan: configuring for phy/gmii link mode
Thu Jun 16 19:01:14 2022 kern.info kernel: [   21.380699] 8021q: adding VLAN 0 to HW filter on device wan
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Interface 'wan' is enabled
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Network device 'eth0' link is up
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Network device 'lo' link is up
Thu Jun 16 19:01:14 2022 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Jun 16 19:01:15 2022 daemon.notice netifd: radio1 (1599): ls: /sys/class/ieee80211: No such file or directory
Thu Jun 16 19:01:15 2022 daemon.notice netifd: radio0 (1598): ls: /sys/class/ieee80211: No such file or directory
Thu Jun 16 19:01:15 2022 daemon.notice netifd: radio1 (1599): Could not find PHY for device 'radio1'
Thu Jun 16 19:01:15 2022 daemon.notice netifd: radio0 (1598): Could not find PHY for device 'radio0'
Thu Jun 16 19:01:15 2022 daemon.notice netifd: radio1 (1699): WARNING: Variable 'data' does not exist or is not an array/object
Thu Jun 16 19:01:15 2022 daemon.notice netifd: radio0 (1706): WARNING: Variable 'data' does not exist or is not an array/object
Thu Jun 16 19:01:15 2022 daemon.debug dnsmasq[1001]: listening on eth0(#2): fe80::2e30:33ff:fe34:5498%eth0 port 53
Thu Jun 16 19:01:16 2022 daemon.info procd: - init complete -
Thu Jun 16 19:01:16 2022 kern.info kernel: [   23.166248] mt7530 mdio-bus:1f lan2: Link is Up - 100Mbps/Full - flow control off
Thu Jun 16 19:01:16 2022 kern.info kernel: [   23.181222] br-lan: port 2(lan2) entered blocking state
Thu Jun 16 19:01:16 2022 kern.info kernel: [   23.191679] br-lan: port 2(lan2) entered forwarding state
Thu Jun 16 19:01:16 2022 daemon.notice netifd: Network device 'lan2' link is up
Thu Jun 16 19:01:16 2022 kern.info kernel: [   23.203700] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Thu Jun 16 19:01:16 2022 daemon.notice netifd: bridge 'br-lan' link is up
Thu Jun 16 19:01:16 2022 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Jun 16 19:01:16 2022 daemon.notice netifd: Interface 'lan' is setting up now

_________________
Halny HL-4GMV + 2xNetgear R6220 (OpenWrt 22.03 z LuCI)
System: OpenSUSE
http://software.opensuse.org/


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Brak Wi-Fi w Netgear R6220 - wina sprzetu, czy softu?
Post: 17 cze 2022, 06:43 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 14083
Lokalizacja: Warszawa
To samo co zawsze - zrób sobie backup dopóki jeszcze możesz i wgraj jeszcze raz system na czysto, bez zachowania konfiguracji. Jeżeli po tym nie wstanie to poleciał flash.

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Brak Wi-Fi w Netgear R6220 - wina sprzetu, czy softu?
Post: 18 cze 2022, 18:52 
Offline
Użytkownik
Awatar użytkownika

Rejestracja: 25 lut 2011, 22:28
Posty: 722
Dzięki.
sysupgrade -n

zadziałało. Przy okazji mam najnowsze OpenWRT :)

_________________
Halny HL-4GMV + 2xNetgear R6220 (OpenWrt 22.03 z LuCI)
System: OpenSUSE
http://software.opensuse.org/


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Brak Wi-Fi w Netgear R6220 - wina sprzetu, czy softu?
Post: 18 cze 2022, 20:24 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 14083
Lokalizacja: Warszawa
Czyli leci flash ale realokacja sektorów nastąpiła. Jeszcze będzie działał.

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
Wyświetl posty nie starsze niż:  Sortuj wg  
Nowy temat Odpowiedz w temacie  [ Posty: 6 ] 

Strefa czasowa UTC+1godz. [letni]


Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 42 gości


Nie możesz tworzyć nowych tematów
Nie możesz odpowiadać w tematach
Nie możesz zmieniać swoich postów
Nie możesz usuwać swoich postów

Szukaj:
Przejdź do:  
designed by digi-led.pl
...Copyright © 2010-2013, Ekipa openrouter.info