#10

I just did that and now for some reason my Norns on RPI install won’t start anymore. The screen is not displaying anything and Maiden can’t connect to Matron. That’s strange.
With the previous 191016 update (one hour ago) it was still working (minus a Supercollider fail error that I was trying to solve). I should probably try a fresh install of the whole system.

#11

oh, i know the problem. new files in two minutes.

EDIT: the files have been updated. please try them again. i apologize for the re-upload trouble.

3 Likes
#12

Thanks @Tehn . Quick question, i’ve deleted the version.txt via ftp but is there a command for running the update via ssh ? The screen shows nothing so I can’t run the update directly from the device. Edit: I’ve found it, I’ll download the .tar and run update.sh manually.

Edit: Yep, it’s back, it’s working again. thanks :wink:

1 Like
#13

Installed no problems. I didn’t notice the shutting down message that I think I should have seen from the code. I wonder if extending the sleep prior to shutdown would make sense?

#18

norns didn’t show any available updates after i deleted version.txt, but after powering norns off and on, checking for updates again showed the revised 191016 update, which then installed cleanly from within norns.

#19

Just updated via the norns hardware and, following the on-screen text ‘complete.’, the screen went black and norns is utterly unresponsive (although wifi adapter is lit, and so is the rear status light). First time this has occurred and not sure where to go from here?

UPDATE: approx 30min after first update process, screen came alive again and showed update being available. Followed installation, but now back to a black screen and unresponsive interface. Maiden shows “update complete.” as final line, but I can’t seem to do anything with the hardware.

#20

When the update isn’t complete, press key 3 and the Norns will shutdown. Restart it as normal.

#21

Ahh…many thanks. I thought I had done that the first two efforts, but obviously not.

#22

i would’ve thought any key would’ve shut it down but wow i am sorry. i will fix this.

1 Like
#23

Thanks @tehn. I’m not ruling out a small sprinkling of user error…it’s been one of those days…but it was a new issue in the handful of updates I’ve made.

#24

Hi, there used to be a way to update offline. I can’t seem to find the info for that. Is it still possible to do, and if so how? The wifi settings at my work are a little troublesome.

#25

Curious - the we script directory is not showing up in the script menu after pulling the current (October 23, 2019) norns master branch.

Does anyone with 191016 see this (or not see this) as well?

1 Like
#26

oh, oops. this is on me. i thought the script scanning command was recursing, but i guess not. we doesn’t have any scripts in the top level.

#27

OK - should I github issue that?

#28

fixing it is faster than issuing it

…PR with reversion

4 Likes
#30

Sorry to be so dumb but how do I pull this version onto norns ? (Sorry - very very new to monome and norns !!!)

#31

Connect to wifi and use the update feature: system > update.

1 Like
#32

That didnt pull@zebra ‘s fix for reverting to find though (when I tried it previously) Ah! Just realised what you meant! No - I dont want to update to the latest release, I want to pull the latest revision (which has been added after the release!)

2 Likes
#33

SSH to norns

cd norns
git pull
2 Likes
#34

Thanks a lot for the reply.