rrf 3.4 beta update on ODROID sbc not possible

rjenkinsgb

On mine, I just did
sudo apt update
sudo apt upgrade

to get everything synced to the latest release versions first. and rebooted it.

Then the unstable feed change:

Upgrading to unstable packages
This step is relatively trivial. Be aware that potential downgrades can involve more work.

Change stable to unstable in /etc/apt/sources.list.d/duet3d.list (sudo bash -c "echo 'deb https://pkg.duet3d.com/ unstable armv7' > /etc/apt/sources.list.d/duet3d.list")
Run a system update (sudo apt update && sudo apt upgrade)
The latest unstable packages should be installed
Downgrading to stable packages

And repeat the update / upgrade as above.
That should automatically reflash the Duet and any connected add-on boards.

Downgrading is more complex...

Note that the above is based on using the latest "DuetPi" card image to to run the Raspberry Pi - if you have used any other OS version, there is no guarantee the packages will match up and install properly, I'd guess.

joeko

@rjenkinsgb said in rrf 3.4 beta update on sbc not possible:

On mine, I just did
sudo apt update
sudo apt upgrade

to get everything synced to the latest release versions first. and rebooted it.

Then the unstable feed change:
Upgrading to unstable packages
This step is relatively trivial. Be aware that potential downgrades can involve more work.

Change stable to unstable in /etc/apt/sources.list.d/duet3d.list (sudo bash -c "echo 'deb https://pkg.duet3d.com/ unstable armv7' > /etc/apt/sources.list.d/duet3d.list")
Run a system update (sudo apt update && sudo apt upgrade)
The latest unstable packages should be installed
Downgrading to stable packages
And repeat the update / upgrade as above.
That should automatically reflash the Duet and any connected add-on boards.

Downgrading is more complex...

Note that the above is based on using the latest "DuetPi" card image to to run the Raspberry Pi - if you have used any other OS version, there is no guarantee the packages will match up and install properly, I'd guess.

i did this more than 10 times
rrf 3.3 stable is all fine (after modify the the json) but update to the latest beta is not possible (on an odroid c4 with ubuntu or debian)

rjenkinsgb

@joeko said in rrf 3.4 beta update on sbc not possible:

on an odroid c4

That appears to be the problem, then - if it's not the same base OS and packages as the DuetPi OS image, the new package dependencies may not be met.

Unless someone else has used the exact same board and more information, you appear to be stuck with a non-standard system, at least until 3.4 is a formal release - you could try again then, or try building from scratch.

joeko

thank you for your answer.
i will see.
i like the odroid boards with the emmc card. stable and fast

but the duetpi os is also based on debian...

PCR

@joeko can you post the output of apt upgrade

PCR

@pcr and apt update

joeko

@pcr said in rrf 3.4 beta update on ODROID sbc not possible:

@joeko can you post the output of apt upgrade

hmm, at the moment i dont use this combination but there are no error message. apt update show that the unstable list is loading and apt upgrade also that the duet files "hold back" i have all tried what i have found to fix that but always the same. but !! no problem with the stable rrf 3.3

but if you have an idea i try it again of course and post the output

Nurgelrot

Try unholding the packages:

# sudo apt-mark unhold \
    duetsoftwareframework \
    duetcontrolserver \
    duetruntime \
    duetsd \
    duetsoftwareframework \
    duettools \
    duetwebcontrol \
    duetwebserver \
    reprapfirmware

# sudo apt update
# sudo apt upgrade

joeko

@nurgelrot said in rrf 3.4 beta update on ODROID sbc not possible:

Try unholding the packages:

# sudo apt-mark unhold \
    duetsoftwareframework \
    duetcontrolserver \
    duetruntime \
    duetsd \
    duetsoftwareframework \
    duettools \
    duetwebcontrol \
    duetwebserver \
    reprapfirmware

# sudo apt update
# sudo apt upgrade

i will do it
do you use your odroid c4 with the latest beta ?
if so, which os and did you do this on this way ?

joeko

@pcr said in rrf 3.4 beta update on ODROID sbc not possible:

@joeko can you post the output of apt upgrade

here the apt-update and upgrade

OK:1 http://ppa.launchpad.net/hardkernel/ppa/ubuntu bionic InRelease
OK:2 http://archive.canonical.com/ubuntu focal InRelease
OK:3 http://ports.ubuntu.com/ubuntu-ports focal InRelease
OK:4 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease
OK:5 https://pkg.duet3d.com unstable InRelease
OK:6 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease
OK:7 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease
Holen:8 http://deb.odroid.in/c4 focal InRelease [1.697 B]
Es wurden 1.697 B in 2 s geholt (733 B/s).
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Aktualisierung für 8 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.

and upgrade

sudo apt upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete sind zurückgehalten worden:
  duetcontrolserver duetpluginservice duetruntime duettools duetwebcontrol
  duetwebserver reprapfirmware
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 7 nicht aktualisiert.

but apt list --upgradable

 apt list --upgradable
Listing... Done
duetcontrolserver/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetpluginservice/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetruntime/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetsoftwareframework/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duettools/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
duetwebcontrol/unstable 3.4-b5 all [upgradable from: 3.3.0]
duetwebserver/unstable 3.4-b5 arm64 [upgradable from: 3.3.0]
reprapfirmware/unstable 3.4-b6-1 all [upgradable from: 3.3.0-1]

is there a mix of beta version and make the problem ?

joeko

@nurgelrot said in rrf 3.4 beta update on ODROID sbc not possible:

Try unholding the packages:

# sudo apt-mark unhold \
    duetsoftwareframework \
    duetcontrolserver \
    duetruntime \
    duetsd \
    duetsoftwareframework \
    duettools \
    duetwebcontrol \
    duetwebserver \
    reprapfirmware

# sudo apt update
# sudo apt upgrade

thank you but the same like before. still hold back and update not possible. please look at my post one back

o_lampe

@joeko said in rrf 3.4 beta update on ODROID sbc not possible:

is there a mix of beta version and make the problem ?

Have to tried to upgrade to beta5 first, and if successful, go for beta6?

joeko

@o_lampe said in rrf 3.4 beta update on ODROID sbc not possible:

@joeko said in rrf 3.4 beta update on ODROID sbc not possible:

is there a mix of beta version and make the problem ?

Have to tried to upgrade to beta5 first, and if successful, go for beta6?

no, fresh and new install this morning on duet3 mini.
first with rf 3.3 (all fine) and update to the beta

joeko

@o_lampe said in rrf 3.4 beta update on ODROID sbc not possible:

@joeko said in rrf 3.4 beta update on ODROID sbc not possible:

is there a mix of beta version and make the problem ?

Have to tried to upgrade to beta5 first, and if successful, go for beta6?

hmm, if didnt try it but if possible i will.
but how i can do this ? as far as i know i can only update to the latest beta.

Nurgelrot

@joeko So is this issue solved? I'm on 3.4 beta6 on both a Duet3d mini5 and a BTT GTR board using the STM32 port of RRF.

using Armbian (debian 10.11 aka buster)

joeko

@nurgelrot said in rrf 3.4 beta update on ODROID sbc not possible:

@joeko So is this issue solved? I'm on 3.4 beta6 on both a Duet3d mini5 and a BTT GTR board using the STM32 port of RRF.

using Armbian (debian 10.11 aka buster)

no way, always the same.
updates hold back and it seems that the betas are mixed....
witch gpiochip and pinnumber did you set in the json ?

witch way you have used for install, first stable and than beta ?

Nurgelrot

@joeko I'm always following unstable on these so I went from 3.4 Beta somthing to Beta 6

I did have an issue with the STM32 version not patching right away it complained about a dependency problem with duetsoftwareframework requiring <= reprapfirmware 3.4-b5-999. I removed all the duet packages and reinstalled latest unstable and it worked.

My transfer pin is 67 on /dev/gpiochip0. But these are different on different versions of linux on the odroid C4. I remember that the ubuntu version shipped with the Odroid had it at pin 68 on chip1

if any version is installed but nothing is running (or you have shut it down) try running:

sudo /opt/dsf/bin/DuetControlServer -ud

that will produce errors on screen if you have any sort of communication problem. ^D or ^C to exit.

joeko

@nurgelrot said in rrf 3.4 beta update on ODROID sbc not possible:

@joeko I'm always following unstable on these so I went from 3.4 Beta somthing to Beta 6

I did have an issue with the STM32 version not patching right away it complained about a dependency problem with duetsoftwareframework requiring <= reprapfirmware 3.4-b5-999. I removed all the duet packages and reinstalled latest unstable and it worked.

My transfer pin is 67 on /dev/gpiochip0. But these are different on different versions of linux on the odroid C4. I remember that the ubuntu version shipped with the Odroid had it at pin 68 on chip1

if any version is installed but nothing is running (or you have shut it down) try running:

that will produce errors on screen if you have any sort of communication problem. ^D or ^C to exit.

with armbian buster it works. i also did it with buster from hardkernel (meveric from forum) but this was not possible. now it works.

sudo /opt/dsf/bin/DuetControlServer -ud

give me

Duet Control Server v3.4-b6
Written by Christian Hammacher for Duet3D
Licensed under the terms of the GNU Public License Version 3

[info] Settings loaded
[fatal] Another instance is already running. Stopping.

i think that is ok because it is running

thank you for your help

@chrishamm
it would make it easier when it offer the choice to modify the json for the tfr pin while the installation...much easier.

jay_s_uk

@joeko I've updated our DSF on armbian instructions here
https://teamgloomy.github.io/dsf_on_armbian.html

Nurgelrot

@joeko Yes a opportunity to override the default pin locations in the post-install script would be very handy. Also when you upgrade make sure you do not override your existing config.json. I've done that a couple times now getting annoying

rrf 3.4 beta update on ODROID sbc not possible

Robert J.

Robert J.