Demon55

Получается в 4.1.7 stable, draft, delta а в 4.2.6 stable, draft, preview всего 3 канала, понятненько

Старая Giga III на канале delta После обновления c 4.1.7 до 4.2.6 в конфиге канал обновления с delta поменялся на stable Не могу поменять канал обновления на delta components auto-update channel delta system configuration save Команды выполняются, а в конфиге все равно stable

А что за яндекс диск с прошивкой? Почему не обновляешься через официальный канал Delta ? Вот сравнил лог со своим Сравнение файлов self-test(2.16.D.12.0-8).txt и LOG ULTRA.TXT ***** self-test(2.16.D.12.0-8).txt [I] Jan 1 00:00:03 kernel: Linux version 3.4.113 (developers@ndmsystems.com) (gcc version 8.2.0 (crosstool-NG 1.23.0-ndm-13 - NDMS Toolkit 1.0.0) ) #1 SMP Tue Apr 26 08:11:16 MSK 2022 [I] Jan 1 00:00:03 kernel: ISPRAM0: PA=002f8000,Size=00008000,enabled ***** LOG ULTRA.TXT [I] Jan 1 00:00:03 kernel: Linux version 3.4.113 (developers@ndmsystems.com) (gcc version 8.2.0 (crosstool-NG 1.23.0-ndm-13 - NDMS Toolkit 1.0.0) ) #1 SMP Tue Apr 26 07:36:10 MSK 2022 [I] Jan 1 00:00:03 kernel: ISPRAM0: PA=002f8000,Size=00008000,enabled ***** ***** self-test(2.16.D.12.0-8).txt [I] Jan 1 00:00:03 kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [I] Jan 1 00:00:03 kernel: Writing ErrCtl register=00000000 [I] Jan 1 00:00:03 kernel: Readback ErrCtl register=00000000 [I] Jan 1 00:00:03 kernel: Memory: 255888k/262016k available (2944k kernel code, 6128k reserved, 561k data, 204k init, 0k high ***** LOG ULTRA.TXT [I] Jan 1 00:00:03 kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [I] Jan 1 00:00:03 kernel: Writing ErrCtl register=0006e0d0 [I] Jan 1 00:00:03 kernel: Readback ErrCtl register=0006e0d0 [I] Jan 1 00:00:03 kernel: Memory: 255888k/262016k available (2944k kernel code, 6128k reserved, 561k data, 204k init, 0k high ***** ***** self-test(2.16.D.12.0-8).txt [I] Jan 1 00:00:03 ndm: Core::Main: *** Network Device Manager 2.16.D.12.0-8. [I] Jan 1 00:00:03 ndm: Core::Main: *** Built Apr 26 2022 08:06:08. [I] Jan 1 00:00:03 ndm: Core::Main: *** ***** LOG ULTRA.TXT [I] Jan 1 00:00:03 ndm: Core::Main: *** Network Device Manager 2.16.D.12.0-8. [I] Jan 1 00:00:03 ndm: Core::Main: *** Built Apr 26 2022 07:31:14. [I] Jan 1 00:00:03 ndm: Core::Main: *** *****

Сброс настроек делали через WEB интерфейс или через кнопочку reset ? Попробуйте обновиться до 2.16.D.12.0-8, а потом сделать именно hard reset через кнопку.

Проблема с сертификатом решаема Acme::Client: certificate for domain "***.keenetic.io" should be reissued. Acme::Client: start automatic reissuing of certificate for domain "***.keenetic.io". Http::Util::Tools: certificate for domain "***.keenetic.io" is expired. Acme::Client: reissuing of "***.keenetic.io" administratively disabled. От всех бед один ресет ( Hard Reset ) Core::System::Mtd::Partition: "Config" partition erased. Core::Configuration: the system configuration reset to factory defaults. Core::System::RebootManager: reboot in 2000 millisecond(s). Core::System::RebootManager: reboot process started. ... Acme::Runner: generating account RSA key (2048 bits) ... Acme::Client: obtained default domain: "***.keenetic.io". Acme::Runner: generating account RSA key completed. Acme::Runner: trying to register on ACMEv2 server... Acme::Tools: requesting "https://acme-v02.api.letsencrypt.org/directory"... Acme::Tools: requesting "https://acme-v02.api.letsencrypt.org/acme/new-nonce"... Acme::Tools: requesting "https://acme-v02.api.letsencrypt.org/acme/new-acct"... Acme::V2: successfully registered. Acme::V2: account ID is xxxxxxxxxx. Acme::Runner: successfully registered on ACMEv2 server. Acme::Client: saving account key (ID: xxxxxxxxxx) into persistent memory. Acme::Client: account key saved. Acme::Client: retry #1 after 20s. Acme::Client: start automatic reissuing of certificate for domain "***.keenetic.io". Acme::Client: reissuing of "***.keenetic.io" administratively disabled. Т.е. по шагам 1. Бакапим конфиг 2. На включенном кинетике зажимаем кнопку Reset пока не замигает power 3. Ресторим конфиг ЗЫ Наверное лучше конфиг не восстанавливать, а настроить Кинетик с нуля.