{"id":931065,"date":"2026-04-16T17:35:34","date_gmt":"2026-04-16T15:35:34","guid":{"rendered":"https:\/\/blog.darkbyte.sk\/?p=931065"},"modified":"2026-04-16T17:44:43","modified_gmt":"2026-04-16T15:44:43","slug":"voron-trident-a-aktualizacia-os","status":"publish","type":"post","link":"https:\/\/blog.darkbyte.sk\/?p=931065","title":{"rendered":"Voron Trident a aktualiz\u00e1cia OS"},"content":{"rendered":"

Ke\u010f som asi pred dvomi rokmi staval Tridenta, ako mozog som pou\u017eil vtedy aktu\u00e1lny Armbian zalo\u017een\u00fd na Debiane 11 s \u00fapravami od BTT. Je u\u017e trocha zastaral\u00fd, tak sa dnes pozrieme na to, ako som ho upgradol na Bookworma (12).<\/p>\n

<\/p>\n

Ob\u00e1val som sa tohto upgradu, ale t\u00fdm, \u017ee ako z\u00e1klad v BTT pou\u017eili \u0161tandardn\u00fd Armbian, len s vlastn\u00fdm kernelom s drobn\u00fdmi \u00fapravami pre BTT-CB1, nejednalo sa o \u017eiadnu dr\u00e1mu. M\u00e1 to v\u0161ak svoje \u0161pecifik\u00e1 a tak som to rad\u0161ej sp\u00edsal pre bud\u00face gener\u00e1cie a predpoklad\u00e1m, \u017ee i bud\u00face verzie Armbianu sa bud\u00fa upgradova\u0165 podobne. Upgrade tie\u017e nerie\u0161i star\u0161\u00ed kernel 5.x, tak\u017ee ak chcete nov\u0161\u00ed kernel 6.x, mus\u00edte si ho tie\u017e upgradova\u0165 ru\u010dne, ale lep\u0161ie je za\u010da\u0165 na zelenej l\u00fake. Odz\u00e1lohujte si konfigur\u00e1ciu a stiahnite si nov\u0161\u00ed image od BTT<\/a>, ktor\u00fd u\u017e je zalo\u017een\u00fd priamo na \u0161tandardnom Armbiane Bookworm a pou\u017e\u00edva teda aj \u0161tandardn\u00fd kernel. Mne sa s t\u00fdm nechcelo prca\u0165, tak som 5.x kernel nerie\u0161il lebo funguje dobre.<\/p>\n

Upgrade som musel rozlo\u017ei\u0165 do nieko\u013ek\u00fdch f\u00e1z. Je treba aktualizova\u0165 samotn\u00fd Armbian 11, potom v\u0161etko pod Mainsailom, a\u017e n\u00e1sledne sa m\u00f4\u017ee upgradova\u0165 Armbian na Bookworm. T\u00fdm sa rozbij\u00fa environmenty Moonrakera a Klippera, ktor\u00e9 treba n\u00e1sledne doaktualizova\u0165 a t\u00fdm by mal by\u0165 upgrade hotov\u00fd. Dos\u0165 bolo kecov, po\u010fme na to.<\/p>\n

F\u00e1za prv\u00e1<\/strong> – ak nem\u00e1te v syst\u00e9me nejak\u00e9 chu\u0165ovky, aktualiz\u00e1cia Armbian Bullseye sa urob\u00ed \u0161tandardn\u00fdm sp\u00f4sobom:<\/p>\n

sudo apt -y update
\nsudo apt -y upgrade<\/code><\/p>\n

Dobehnete t\u00fdm v\u0161etko, \u010do sa stihlo v Bullseye aktualizova\u0165 a ak ste to robili pravidelne, nemalo by to ani dlho trva\u0165.<\/p>\n

F\u00e1za druh\u00e1<\/strong> – treba aktualizova\u0165 v\u0161etky moduly v Mainsaile, aby boli v zelenom stave UP-TO-DATE. Ani tu by ste nemali ma\u0165 probl\u00e9my, ak nem\u00e1te nejak\u00fa ve\u013emi star\u00fa in\u0161tal\u00e1ciu. Bu\u010f kliknete na hromadn\u00fd update, alebo si to zaktualizujte jedno po druhom, ak sa boj\u00edte, \u017ee by sa v\u00e1m to rozsypalo.<\/p>\n

Tretia f\u00e1za<\/strong> – upgrade OS na Bookworm. V \/etc\/apt\/sources.list<\/em> presmerujeme v\u0161etko na Bookworm a uprav\u00edme aj n\u00e1zov non-free<\/em> repozit\u00e1ra, ke\u010f\u017ee v Bookworme sa to zmenilo. N\u00e1sledne spust\u00edme pln\u00fd upgrade:<\/p>\n

sudo sed -i 's\/bullseye\/bookworm\/g' \/etc\/apt\/sources.list
\nsudo sed -i 's\/non-free\/non-free-firmware\/g' \/etc\/apt\/sources.list
\nsudo apt -y update
\nsudo apt -y full-upgrade
\nsudo reboot<\/code><\/p>\n

Po\u010das tohto procesu dostanete p\u00e1r ot\u00e1zok, ja som na ne odpovedal takto:<\/p>\n

  • Iperf3 = No<\/li>\n
  • Configuration file \/etc\/issue<\/em> = Yes<\/li>\n
  • Configuration file \/etc\/issue.net<\/em> = Yes<\/li>\n
  • Restart services during package upgrades without asking = Yes<\/li>\n
  • Configuration file \/etc\/systemd\/journald.conf<\/em> = Yes<\/li>\n
  • Configuration file \/etc\/sudoers<\/em> = No<\/li>\n
  • Configuration file \/etc\/initramfs-tools\/initramfs.conf<\/em> = Yes<\/li>\n
  • Configuration file \/etc\/ssh\/ssh_config<\/em> = Install the package maintainer’s version<\/li>\n

    Vy samozrejme zvol\u00edte odpovede, ktor\u00e9 vyhovuj\u00fa va\u0161ej konfigur\u00e1cii. Napr\u00edklad posledn\u00e1 vo\u013eba by v\u00e1m mohla rozbi\u0165 ssh, ak ho m\u00e1te nejako prisp\u00f4soben\u00e9 pre vlastn\u00e9 potreby. Ja ni\u010d podobn\u00e9 nem\u00e1m, tak\u017ee nov\u00fd s\u00fabor mi neu\u0161kodil. Pr\u00e1ve naopak sudoers<\/em> je dobr\u00e9 si zachova\u0165, lebo v \u0148om m\u00e1te vlastn\u00e9 zmeny takmer ur\u010dite. Ak sa ni\u010d nezosypalo, po reboote by v\u00e1m mal syst\u00e9m norm\u00e1lne nabehn\u00fa\u0165, av\u0161ak ako som spom\u00ednal, bude rozbit\u00fd Moonraker aj Klipper, tak\u017ee Mainsail v\u00e1m nenabehne.<\/p>\n

    \u0160tvr\u00e1 f\u00e1za<\/strong> – aktualiz\u00e1cia environmentov Moonrakera a Klippera by n\u00e1m mala tento probl\u00e9m vyrie\u0161i\u0165. Ako prv\u00e9 si stiahnite pr\u00edkaz get-pip<\/em>:<\/p>\n

    curl https:\/\/bootstrap.pypa.io\/get-pip.py -o ~\/get-pip.py<\/code><\/p>\n

    Ke\u010f ho m\u00e1te stiahnut\u00fd, aktivujte si Moonraker environment, stiahnite si pip<\/em> a aktualizujte a doin\u0161talujte \u010do treba. Potom Moonraker-env deaktivujte a zre\u0161tartujte servis:<\/p>\n

    source ~\/moonraker-env\/bin\/activate
    \npython ~\/get-pip.py
    \npython -m pip install --upgrade pip setuptools wheel
    \npip install importlib-metadata pyserial
    \ndeactivate
    \nsudo systemctl restart moonraker<\/code><\/p>\n

    Obdobne postupujeme aj s Klipperom. Aktivujte environment, stiahnite si pip<\/em> a potom aktualizujte a doin\u0161talujte pr\u00edslu\u0161n\u00e9 moduly: <\/p>\n

    source ~\/klippy-env\/bin\/activate
    \npython ~\/get-pip.py
    \npython -m pip install --upgrade pip setuptools wheel
    \npip install greenlet cffi jinja2 pyserial python-can<\/code><\/p>\n

    T\u00fdm by sme mali aktualiz\u00e1ciu hotov\u00fa, no e\u0161te treba skontrolova\u0165, \u010di sa ni\u010d nepoka\u0161\u013ealo. Pozrite si logy Klippera aj Moonrakera pomocou pr\u00edkazu journalctl, pri Moonrakeri si dajte trocha na\u010das, najprv vyzer\u00e1 neakt\u00edvne, ale e\u0161te si dotiahne nejak\u00e9 z\u00e1vislosti:<\/p>\n

    journalctl -fu klipper
    \njournalctl -fu moonraker<\/code><\/p>\n

    Ak je v\u0161etko v poriadku, sta\u010d\u00ed servisy pre istotu zre\u0161tartova\u0165 a n\u00e1sledne m\u00f4\u017eete Klipper-env deaktivova\u0165 a nastavi\u0165 policykit pravidl\u00e1:<\/p>\n

    sudo systemctl restart klipper
    \nsudo systemctl restart moonraker
    \ndeactivate
    \n~\/moonraker\/scripts\/set-policykit-rules.sh<\/code><\/p>\n

    Ako posledn\u00fd krok je e\u0161te treba rein\u0161talova\u0165 KlipperScreen. Neb\u00fdva v \u0148om ni\u010d z\u00e1sadn\u00e9, tak\u017ee ja som jeho environment proste zmazal a spustil som \u010derstv\u00fa in\u0161tal\u00e1ciu. Ako si ju skonfigurujete je u\u017e na v\u00e1s (ja som dal default<\/em> a X<\/em>):<\/p>\n

    rm -rf ~\/.KlipperScreen-env\/
    \n~\/KlipperScreen\/scripts\/KlipperScreen-install.sh<\/code><\/p>\n

    Teraz je aj vhodn\u00fd \u010das skontrolova\u0165, \u010di netreba rein\u0161talova\u0165, alebo aktualizova\u0165 pluginy \u010do m\u00e1te, ako napr\u00edklad Klipper LED plugin a podobne. Ja pluginy ve\u013emi nevyu\u017e\u00edvam a tie \u010do m\u00e1m sa rozbehli, tak\u017ee som ich zatia\u013e nechal tak. To v\u0161ak nemus\u00ed by\u0165 v\u00e1\u0161 pr\u00edpad, tak\u017ee tento krok rozhodne nevynechajte.<\/p>\n

    No a \u00fapln\u00e9 fin\u00e1le je o\u010distenie Bookworma od osirel\u00fdch bal\u00edkov \u0161tandardn\u00fdm pr\u00edkazom, ja som nevynechal ani reboot, ktor\u00fd prever\u00ed \u010di je v\u0161etko nakonfigurovan\u00e9 spr\u00e1vne:
    \n
    \nsudo apt -y autoremove
    \nsudo reboot<\/code><\/p>\n

    Ke\u010f som asi pred dvomi rokmi staval Tridenta, ako mozog som pou\u017eil vtedy aktu\u00e1lny Armbian zalo\u017een\u00fd na Debiane 11 s \u00fapravami od BTT. Je u\u017e trocha zastaral\u00fd, tak sa dnes pozrieme na to, ako som ho upgradol na Bookworma (12).<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-931065","post","type-post","status-publish","format-standard","hentry","category-3d-printing"],"_links":{"self":[{"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=\/wp\/v2\/posts\/931065","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=931065"}],"version-history":[{"count":18,"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=\/wp\/v2\/posts\/931065\/revisions"}],"predecessor-version":[{"id":931132,"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=\/wp\/v2\/posts\/931065\/revisions\/931132"}],"wp:attachment":[{"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=931065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=931065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.darkbyte.sk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=931065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

    Mne sa v\u0161etko rozbehlo, no skon\u010dil som s v\u00fdstrahou, \u017ee treba aktualizova\u0165 Klipper firmware v hlavnej doske a toolheade. Ale to u\u017e je in\u00fd pr\u00edbeh. Ak ho chcete sf\u00faknu\u0165 jedn\u00fdm dychom, \u010d\u00edtajte v nasleduj\u00facom \u010dl\u00e1nku<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"