Norns on Raspberry Pi

[noiserock]

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

Any ideas on where I f-ed up?

[Taubaland]

maybe check norns-init.service, norns-jack.service and norns-maiden.service to see if they’re throwing any more human readable errors

[noiserock]

decided to do a fresh recompile before continuing.

following errors are present:

norns-init:

Mar 17 00:30:25 norns systemd[1]: Starting norns-init...

Mar 17 00:30:25 norns amixer[252]: amixer: Unable to find simple control 'Master',0

Mar 17 00:30:25 norns systemd[1]: **norns-init.service: Main process exited, code=exited, status=1/FAILURE**

Mar 17 00:30:25 norns systemd[1]: **Failed to start norns-init.**

Mar 17 00:30:25 norns systemd[1]: **norns-init.service: Unit entered failed state.**

Mar 17 00:30:25 norns systemd[1]: **norns-init.service: Failed with result 'exit-code'.**

norns.jack:

Mar 17 00:30:25 norns systemd[1]: Starting norns-jack.service...

Mar 17 00:30:26 norns jackd[268]: Unknown driver "k6"

Mar 17 00:30:26 norns jackd[268]: jackdmp 1.9.12

Mar 17 00:30:26 norns jackd[268]: Copyright 2001-2005 Paul Davis and others.

Mar 17 00:30:26 norns jackd[268]: Copyright 2004-2016 Grame.

Mar 17 00:30:26 norns jackd[268]: Copyright 2016-2017 Filipe Coelho.

Mar 17 00:30:26 norns jackd[268]: jackdmp comes with ABSOLUTELY NO WARRANTY

Mar 17 00:30:26 norns jackd[268]: This is free software, and you are welcome to redistribute it

Mar 17 00:30:26 norns jackd[268]: under certain conditions; see the file COPYING for details

Mar 17 00:30:26 norns systemd[1]: **norns-jack.service: Main process exited, code=exited, status=255/n/a**

Mar 17 00:30:27 norns systemd[1]: **Failed to start norns-jack.service.**

Mar 17 00:30:27 norns systemd[1]: **norns-jack.service: Unit entered failed state.**

Mar 17 00:30:27 norns systemd[1]: **norns-jack.service: Failed with result 'exit-code'.**

maiden seems to be working.

looks like it might be an issue with jack not being set up properly(have a Complete Audio 6 connected, but haven’t done the setup for it yet). Maybe I just answered my own question…

thanks!

[okyeron]

have a Complete Audio 6 connected, but haven’t done the setup for it yet). Maybe I just answered my own question…

Yeah - you gotta get the sound card configured first - otherwise jack will not start properly on launch.

[noiserock]

ok. did the following:

**192.168.86.30** **~ $** aplay -l

**** List of PLAYBACK Hardware Devices ****

card 0: K6 [Komplete Audio 6], device 0: USB Audio [USB Audio]

Subdevices: 1/1

Subdevice #0: subdevice #0

**192.168.86.30** **~ $** export JACK_NO_AUDIO_RESERVATION=1

**192.168.86.30** **~ $** jackd -R -P 95 -d alsa -d hw:0 -r 48000 -n 3 -p 256 -S -s

jackdmp 1.9.12

Copyright 2001-2005 Paul Davis and others.

Copyright 2004-2016 Grame.

Copyright 2016-2017 Filipe Coelho.

jackdmp comes with ABSOLUTELY NO WARRANTY

This is free software, and you are welcome to redistribute it

under certain conditions; see the file COPYING for details

JACK server starting in realtime mode with priority 95

self-connect-mode is "Don't restrict self connect requests"

creating alsa driver ... hw:0|hw:0|256|3|48000|0|0|nomon|swmeter|soft-mode|16bit

configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 3 periods

ALSA: final selected sample format for capture: 32bit integer little-endian

ALSA: use 3 periods for capture

ALSA: final selected sample format for playback: 32bit integer little-endian

ALSA: use 3 periods for playback

And the it stuck, have to end process with ctrl-c.

I get output from the Soundcard with speaker-test -t sine -f 440 -c 2 -Dplug:sysdefault

but I get the following error with speaker-test -c2

speaker-test 1.1.3

Playback device is default

Stream parameters are 48000Hz, S16_LE, 2 channels

Using 16 octaves of pink noise

Sample format not available for playback: Invalid argument

Setting of hwparams failed: Invalid argument

[Taubaland]

To fix that error for me:

in the path /etc/systemd/system,

in norns-init.service,

change Master to PCM ie.

ExecStart=/usr/bin/amixer set PCM 255 on

and in norns-jack.service

change hw:0 to whichever the hw address your usb sound card is (by checking aplay -l or alsamixer)

ExecStart=/usr/bin/jackd -R -P 95 -d alsa -d hw:1 -r 48000 -n 3 -p 128 -S -s

[noiserock]

that gave me a new set of errors after running

norns-init.service:

Mar 17 02:41:43 norns systemd[1]: Starting norns-init...

Mar 17 02:41:43 norns amixer[321]: amixer: Unable to find simple control 'PCM',0

Mar 17 02:41:43 norns systemd[1]: **norns-init.service: Main process exited, code=exited, status=1/FAILURE**

Mar 17 02:41:43 norns systemd[1]: **Failed to start norns-init.**

Mar 17 02:41:43 norns systemd[1]: **norns-init.service: Unit entered failed state.**

Mar 17 02:41:43 norns systemd[1]: **norns-init.service: Failed with result 'exit-code'.**

[okyeron]

hw:0 should be correct based on your aplay -l output.

did you do this: ?

# Comment out options snd-usb-audio so it can load first
sudo nano /lib/modprobe.d/aliases.conf
	# options snd-usb-audio index=-2

FWIW - I just comment out the amixer setting in norns-init.service

you may also need to go to alsamixer and see if your inputs/outputs are enabled.

[noiserock]

commenting out amixer seems to help.

current alsamixer output:

current jack/crone errors:

[okyeron]

FWIW - systemctl status may give you better info: (?)

systemctl status norns-jack.service
systemctl status norns-init.service
systemctl status norns-crone.service

Also FWIW - I rebooted and got the same norns-crone.service error as you have above. did a ./stop.sh and ./start.sh and everything was cool again.

[noiserock]

systemctl status norns-crone.service

got Norns-init.service running, the issue seems to link to ws-wrapper somehow.

current errors:

192.168.86.30 ~ $ systemctl status norns-jack.service
● norns-jack.service
   Loaded: loaded (/etc/systemd/system/norns-jack.service; disabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-03-17 12:28:12 CET; 3min 55s ago
  Process: 300 ExecStartPost=/bin/sleep 2 (code=exited, status=0/SUCCESS)
 Main PID: 299 (jackd)
   CGroup: /system.slice/norns-jack.service
       └─299 /usr/bin/jackd -R -P 95 -d alsa -d hw:0 -r 48000 -n 3 -p 128 -S -s

Mar 17 12:28:10 norns jackd[299]: ALSA: use 3 periods for capture
Mar 17 12:28:10 norns jackd[299]: ALSA: final selected sample format for playback: 32bit integer little-endian
Mar 17 12:28:10 norns jackd[299]: ALSA: use 3 periods for playback
Mar 17 12:28:12 norns systemd[1]: Started norns-jack.service.
Mar 17 12:28:19 norns jackd[299]: JackEngine::XRun: client = supernova was not finished, state = Running
Mar 17 12:28:19 norns jackd[299]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Mar 17 12:28:20 norns jackd[299]: JackEngine::XRun: client = supernova was not finished, state = Running
Mar 17 12:28:20 norns jackd[299]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Mar 17 12:28:20 norns jackd[299]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Mar 17 12:28:20 norns jackd[299]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
192.168.86.30 ~ $ systemctl status norns-crone.service
● norns-crone.service
   Loaded: loaded (/etc/systemd/system/norns-crone.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-03-17 12:28:12 CET; 4min 7s ago
  Process: 446 ExecStart=/home/we/norns/build/crone/crone (code=exited, status=203/EXEC)
 Main PID: 446 (code=exited, status=203/EXEC)

Mar 17 12:28:12 norns systemd[1]: Started norns-crone.service.
Mar 17 12:28:12 norns systemd[1]: norns-crone.service: Main process exited, code=exited, status=203/EXEC
Mar 17 12:28:12 norns systemd[1]: norns-crone.service: Unit entered failed state.
Mar 17 12:28:12 norns systemd[1]: norns-crone.service: Failed with result 'exit-code'.

[noiserock]

narrowing it down, managed to fix my jackd problems it seems like, but my crone issues are persistent.

in the Norns setup guide, it says:

the crone audio engine consists of supercollider classes. copy files to the default location for user SC extensions

what location is this? sc? and is install.sh the only file to move?

errors popping up after running ./start.sh

./matron.sh: line 3:   796 Aborted                 ./build/ws-wrapper/ws-wrapper ws://*:5555 ./build/matron/matron
./crone.sh: line 7:   799 Aborted                 ./build/ws-wrapper/ws-wrapper ws://*:5556 $SCLANG

[TheTechnobear]

which version are you trying to run?
(your errors include supernova which is not being used by the latest 2.0 beta)

to install the sc classes, you needed to do
cd ~/norns/sc
./install.sh

(you can see in the install.sh where the files are headed )

[noiserock]

not 2.0, but the latest version from https://github.com/monome/norns

[noiserock]

Can you do a fresh install of the Norns image without recompiling Linux? Just remove the Norns folders?

[okyeron]

That would be my recommendation.

Start at the setup norns image section

okyeron/norns-image

[TheTechnobear]

essentially, you only need to end up with a jack, supercollider (3.9.x) , and then you can use a norns image - norns “needs” very little to run.
(e.g. i also run norns on a x86_64 standard ubuntu install)

(adding a ‘we’ user, just means less adaptations to start scripts etc)

the ‘complication’ arises from what are you using for a display, encoders,soundcard etc… if your using compatible hardware to the norns that’s a non-issue, but many/most have something slightly different, so that needs a bit of adaptation.

personally, I now tend to use the update image from monone (which gives you various packages at a particular version ) and adapt it to my needs (which means my own kernel, my own norns build from my fork) …

but that is arguably ‘overkill’ (in an attempt to be ‘compatible’ with norns)

if i was to do a build tommorow, id probably just use the Patchbox OS from Blokas.
then just build norns, take madien (coz its a pain to build) from update, and then hack the various systemctl scripts to use the existing patchbox user - job done

btw: if your doing a norns build, I would ‘hold off’ until 2.0 is released. things have moved around a bit, and are still a bit in flux. I’d wait till it settles down , as I expect things will stabilise a bit after 2.0.
( I ‘tracked’ the 2.0 beta, just because I wanted to make sure it hadn’t broken my Push build - now I know that’s ok, I’m letting the dust settle )

[okyeron]

mark… way back you had suggested some kernel tweaks

Timer Frequenecy —> 1000hz
Preemption Model (Preemptible Kernel (Low-Latency Desktop))
CPU Frequency scaling —> Default CPUFreq governor (performance)

do you think these are unnecessary at this point?

[TheTechnobear]

honestly, I did a load of tests with various kernel parameters, and they seem to make ‘marginal’ differences - there was some, but it was debatable if the effort was worthwhile.

(the key thing was to always make sure the governor was using performance and not ondemand, which is the thing that tripped most of us up, as it tends to get reverted )

anyway , I then I got a rPI3b+ , which has a 1.4 rather than 1.2ghz cpu, and it all seemed to be irrelevant - gives us 200mhz headroom over the CM3 on norns.

also, with 2.0, pushing some of the processing to other cores, will probably have more effect than these kernel optimisations, so might become less relevant.

… on the flipside, this is why I mentioned using the Blokas Patchbox OS, as its using an optimised kernel.
Ive not played with it yet, but I really like the idea of an open source, audio centric, pi distribution.
what makes it ‘next level’ for me, is its built on pi-gen, so we can fork it, and adapt it.
so we could easily make a derivative for norns…
(or my other projects which is really my main focus )

---

as an aside, recently I upgraded my norns rPI to the latest stock kernel, (due to soundplane), but not done any tests to see if that’s had any adverse effects. (my suspicion is it’ll be fine)

[okyeron]

as an aside, recently I upgraded my norns rPI to the latest stock kernel, (due to soundplane), but not done any tests to see if that’s had any adverse effects. (my suspicion is it’ll be fine)

yeah - i did a from scratch build of 2.0 with the default stretch install and just compiled in the display driver - seems to work just fine in very limited testing.

Next few days I’m gonna take a poke at trying to install norns from the Patchbox OS and see how it goes.