#2179

you have to wait for a fates update. see the fates thread.

2 Likes
#2180

well… I’m lost. I’m so stupid I jumped on a new update so quickly.

So you mean Fates users that have the same issue as I have, should do a manual install of this file : https://github.com/fates-project/norns/releases/tag/v2.2.9

And not update from yours ?

#2181

tomorrow, I will try this disk image and keep this post upadted.

#2182

So yeah - Fates now has a separate UPDATE from the original norns and norns shield. This newest 201115 update is not yet available on Fates.

If you were on an older system version (before 200218), then the UPDATE on device will have bricked your system and you will need to re-install from disk image with the instructions you linked above (instructions here)

If you were on 200218 or later, the menu option for SYSTEM > UPDATE should work and would get you to version 201029.

Important note for support - All Fates support requests should go in this thread and not in the main norns threads. If its a general scripting question and you’re not sure, then be clear and identify what hardware you’re using so there’s no confusion.

3 Likes
#2183

Hi and thanks for those precision (a bit new to all of this marvellous universe). So, I did flash the card with the 20200218 image. Fist I tried an update but I had the message : disk full.
I tried to connect via ssh and activate the expand option. I think it worked cause now, I just tried to update on the fates, and it worked ! So I now have the last fates OS. And that’s awesome…

6 Likes
#2184

That’s good to hear! You absolutely do need to do the disk expansion in order to use Fates; that’s probably why the update did not work the first go-round.

#2185

Any fates users tried CC2 yet? I know it says it needs norns fw 201115 and later but I’m wondering if it actually works with the most recent fates update… not near my machine currently or I’d just give it a go myself.

#2186

oh, it probably does! i just like adhering to the latest release for consistency :slight_smile:

1 Like
#2187

Yes, it does definitely :wink: .

3 Likes
#2188

yeah, I was on 1001 and it did not work :stuck_out_tongue: but a quick update and CC2 came right up. thanks @okyeron and @dan_derks for everything!

1 Like
#2189

Update 201115 now available

(sorry for the delay - was waiting on some bugs in the initial release to get stabilized)

If you are on 200218 or later
use SYSTEM > UPDATE while connected to the internet.
(please report back if you have problems with this)

If you are running a version prior to 200218, DO NOT USE SYSTEM > UPDATE .
You must update manually via SSH. Instructions are on the release page: https://github.com/fates-project/norns/releases/tag/2.4.6

See Norns: update 201113 for change log. NOTE - disk images on that post are for factory norns and norns shield ONLY.

If you have a new rev pi4 (rev 1.2 I think) or an 8GB pi4, please DM me - I have a new disk image for pi4 for testing.

11 Likes
#2190

What is the threshold of new? Mine’s from december last year so I don’t think it counts as new, is there a way to check w/o opening Fates?

#2191

I believe this is the way to find out the revision.

1 Like
#2192

The threshold for new rev boards is kinda “ does it work with the fates image or not” :laughing:

If it works, you’re good.

1 Like
#2193

That just boosts my confidence to a whole new level. I’ll back up and try tomorrow :wink:

#2194

Reading again I’m not actually sure what “threashold of new” was talking about.

Do you mean the version of your Pi hardware?

Or do you mean your norns software version? In this situation be sure to read all the instructions - check your norns version by hitting the K2 button while on the SELECT menu page. The software version will show under the current script name.

AGAIN - If you are on something before 200218 you have to do a manual update. If you do that on an earlier version you’ll brick the system and you’ll need reinstall from disk image. See the update page for more.

#2195

I meant the threshold of what constitutes a ‘new rev pi4’ as I’m running my Fates on a 4GB Pi4 (1.1 it appears to be). I’m all up to date on Fates updates.

1 Like
#2196

Went perfectly (as always). Thanks a lot again for your work!

#2197

One of the encoders on my Fates seems a lot jumpier than it was before the latest update.

#2198

Curious… that’s the second report of this.

There were some encoder sensitivity changes in the code

If you want to hack a bit, you could try changing ~/norns/lua/core/encoders.lua line 70 to `local sens = {1,1,1,1}

You would need to restart matron afterwards to get the change to show up.

Could be the sensitivity change is exposing flakey encoder behavior (the encoder component itself)

2 Likes