#542

Not yet, but will do once it’s imminent for release ( or released :)). - I’m not sure how ‘fiinished’ it is at the moment , and don’t want to create noise around something that’s not known not to be quite ready yet.

2 Likes
#543

Not looking to create noise about it really. I contributed some bits and I want to get my test/demo scripts updated with other system changes. Devs are focused on the main hardware so I don’t want to delay/derail any effort there.

#544

@okyeron happy to help debug if you want to post compile errors to the pre-2.0 github issue

1 Like
#545

i wasn’t suggesting you were … i was saying why I hadn’t tried to upgrade it yet.
if its in a “stable” state, a point where testing and feedback is useful - then id be happy to give it a go.

1 Like
#546

This just in…

heads up: SuperCollider 3.10.1 successfully built for RaspberryPi…
…and the still-in-development Ableton Link code, also working on the Pi!

4 Likes
#547

if anyone is using my push 2 branch, then the new Norns 2.0 version is on the new branch tb2.0.
(new branch name as I might be adding some other devices, the previous push2 branch will be retired)

note: please read the 2.0 beta caveats on the main norns 2.0 beta thread

also, Ive made crib notes of what I did to update from 1.x, if anyone needs them.

main change, if your building on something other than a norns 2.0 image, then you will need to install boost

sudo apt-get install  libboost1.62-dev
./waf configure
2 Likes
#548

@TheTechnobear Did you also need to install libjack-jackd2-dev ?

I have that in my notes from awhile back, but can’t remember if that was really necessary

Otherwise can report that Norns 2 beta has been working well for me on RasPi

#549

What kernel are you using atm?

#550

@okyeron , no , probably because my nornsPI image is very close to norns,
so what I do is use the update.tgz, unpack it, and adapt it to my setup - this only takes a few minutes. so its likely the update had jackd2-dev installed. (this was the case with boost on my nornsPI)

the other possibility, is I also have Orac (inc PD) / MEC (my software) and EigenD, running on my Norns PI - so Ive likely installed it as part of that.
(but I don’t use boost for other software, hence why I noticed it needed to be installed on other platforms)

@reijo, good question … its the latest Raspbian kernel, (not the norns kernel build)
I cannot remember if i kept with my own build of it, or reverted it back to stock.
I did play with quite a lot of kernels, including RT pre-empts, but they didn’t provide much better performance when I did tests with norns, so possibly i reverted, but i might not :wink:
Then I upgraded to a rPI3B+ when it was released, and thats has a bit of ‘headroom’ over the CM3 of the Norn, so performance was never an issue.

I guess now some are starting to upgrade their Norns to CM3+, which is same cpu as rPI3B+, we may start to see some scripts that push it a little more :wink: …
on the flip side 2.0 should offer a little better load distribution over cores, so should be less of an issue.

2 Likes
#551

would love to see your crib notes TB have installed boost and would like to upgrade rather than build norns from scratch again. :grinning:

#552

here you go :

as I said, mostly its just take the update.zip and then edit it according to you needs :slight_smile:

#553

my initial tests show no real CPU improvement between the CM3 and CM3+. i was under the impression (from the specs given for the CM3+) that the main improvement was heat management and huge flash. did i misunderstand this?

1 Like
#554

sorry, my mistake …
the rPI3b to rPI3b+ went from 1.2ghz to 1.4ghz, I assumed , incorrectly the CM3, to CM3+ did the same processor bump…
but your right, CM3+ stayed at 1.2ghz … perhaps they thought the heat management was more important for the CM3 line?!

its no big deal really, that 200mhz bump is pretty modest really - as i implied above, it just feels like a bit more ‘headroom’ rather than any real extra processing power.

#555

Linux norns 4.14.52-v7+ #1123 (although I can’t remember now if this is a fresh recompile of everything or my working setup from norns 1.0). I’ve got to work on making a new image and install instructions for my DAC board soon.

1 Like
#556

While updating won’t let me run /.update.sh saying permission denied for some reason?

#557

should be : ./update.sh
its it update.sh that can be run, or something its running?
(Id need to see the error message really)

if its just update.sh , then you could do
. ./update.sh
or
chmod +x ./update.sh

(im assuming your are in the update directory (i.e the one where update.sh is sitting)

#558

chmod +x ./update.sh this makes it run but i am getting these permission errors when running ./start.sh in /norns
192.168.1.12 ~/norns $ ./stop.sh
matron: no process found
sclang: no process found
scsynth: no process found
crone: no process found
192.168.1.12 ~/norns $ ./start.sh
192.168.1.12 ~/norns $ ./matron.sh: line 3: ./build/ws-wrapper/ws-wrapper: Permission denied
./crone.sh: line 12: ./build/ws-wrapper/ws-wrapper: Permission denied

#559

which user are you running this as? this all should be setup and run as ‘we’

did you have all this working prior to the ‘upgrade’ , as none of this should have changed during this process…

#560

yes still ‘we’ and was fully working before.:thinking:

have been using an external editor instead of nano could this be it?

yes it was. thanks all good now :smile:

1 Like
#561

Currently stuck with this error after running
journalctl -u norns-crone.service -b

07
Skjermbilde 2019-03-16 kl. 15.03.07.png1504×174 104 KB

Any ideas on where I f-ed up?