#441

if you use

systemctl status raspi-config
systemctl status norns-init

and look at the PIDS of the processes, this should tell you which executed first.

apart from that the only thing i can think of is disabling raspi-config , and then making sure thru systemctl/journalctl its not running.

(if you do this, you’ll need to remove AFTER, as otherwise I suspect this will start it anyway :wink: )

if you can see that raspi-config did not run, and its still ondemand, then something else is doing it…
(no idea what though :wink: )

EDIT: another option, (hacking)
edit
/etc/init.d/raspi-config

and comment out the line that says
echo “ondemand” > $SYS_CPUFREQ_GOVERNOR

#442

test 1 / the PID of norns-init was 368 and raspi-config is 285 so I guess that’s correct.

Test 2 / I’m now disabling raspi-config -> it’s dead, not showing in systctl anymore. Norns-init = success even Still Ondemand

Test 3 / Commented out the line in raspi-config, daemon-reload, reboot. Ondemand again and it didn’t like that :smiley:

17
Capture d’écran 2018-11-17 à 18.38.17.png1373×213 47.4 KB

Yes, I’m gonna try to find the culprit … :slight_smile:

#443

sorry, I’m out of ideas… (and time if im honest :wink: )

what you could try as a hack is to get a service to run this much later…
say wait for 10 seconds before doing it (a bit like i previously did in my init script)

so leave plenty of time for all the startup services to be done… then bam do it.

theres plenty of time between all these services starting, and Supercollider/matron being up - so its not really going to affect you.

I guess the other thing to check is that its not being reset to ondemand continually… not sure why it would, but out of ideas so something to check

1 Like
#444

I understand, I’m really thankful for the time you’ve spent helping me with this issue, don’t worry :slight_smile:
The idea of running a script later could work, I’ll try.
Another thing I could try (Im not sure) is recompiling the Kernel. although I’m 100% sure I did this part
menuconfig :
Kernel Features
Timer Frequenecy 1000hz (optional, as suggested by norns dev, but doesnt make much difference to me)
Full Preemptive
CPU Governor - Performance
I’m starting to think there was a problem at the begining of the install , the Linux part maybe. Not sure about that but it’s worth trying.

Thanks again for your help, I really appreciate :slight_smile:

#445

Problem solved :wink: cpufrequtils was setting the scalinggovernor to ondemand … after norns-init and raspi-config

I re-enabled raspi-config, removed cpufrequtils, put back the After clause in norns-init and

apt-get remove cpufrequtils
update-rc.d -f cpufrequtils remove

Now, it’s working ! (And no more glitches)

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

performance
1 Like
#446

oh yeah, that’s often the way… install things to find out what the problem is, only for them to later to become the problem :slight_smile:

awesome, thats what matters at the end of the day :slight_smile:

enjoy.

1 Like
#447

I’ve got matron drawing the UI to a cute little OLED display! I’ll add a step-by-step to @FigrHed’s guide once I’ve written it up properly.

IMG_1726
IMG_1726.jpg1264×1686 317 KB

I’m having trouble getting encoders to work. I’ve modified the pins defined in norns-buttons-encoders.dts and compiled it. The encoders work and appear in /dev/input/by-path... but for some reason norns does not start and networking seems to be broken too. Things go back to normal when I remove the overlay from /boot/config.txt
This probably isn’t a norns specific issue but figured someone might know a fix?

10 Likes
#448

so terrible photo but got keys and encoders working as should be. no glitching works like a dream am now slowly heading towards getting a launchpad to act as a non varibright grid. got a branch at git for launchpad stuff if anyone would like to chip in. learning a lot anyhow. :grinning:

IMAG0034-20181119-174908387
IMAG0034-20181119-174908387.jpg1512×2687 718 KB

i had the same issue with the screen going blank turned out to be erroneous numbers for gpio in encoder. dtbs
i tried some different ones and it worked.

5 Likes
#450

Could you share your process for getting the encoders and keys working?
Norns doesn’t seem to start when I enable the .dtbo :confused:

#451

hi there its described here just got the correct gpio and inserted in the dts file:

#452

eureka… finally got my rpInorns to see my launchpad as a grid device. now for a bit of tinkering. many thanks all for your help esp technobear. :smiley:

3 Likes
#453

Would love to see your process / steps taken on this.

#454

literally trial and error from technobears push2 code, taken about two weeks. code is still bloated with screen/encoder stuff from original push2 code. will keep you informed :wink:

2 Likes
#456

Can someone help me out why i get this errors?

Nov 25 00:30:27 norns systemd[1]: norns-init.service: Main process exited, code=exited, status=1/FAILURE
Nov 25 00:30:27 norns systemd[1]: Failed to start norns-init.
Nov 25 00:30:27 norns systemd[1]: norns-init.service: Unit entered failed state.
Nov 25 00:30:27 norns systemd[1]: norns-init.service: Failed with result ‘exit-code’.

we@norns:~/norns $ journalctl -u norns-maiden.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:33:38 KST. –
Nov 25 00:30:27 norns systemd[1]: Started norns-maiden.service.
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Main process exited, code=exited, status=203/EXEC
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Unit entered failed state.
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Failed with result ‘exit-code’.

we@norns:~/norns $ bash start.sh
we@norns:~/norns $ ws-wrapper: …/ws-wrapper/src/main.c:43: bind_sock: Assertion `( *eid = nn_bind(sock, url) ) >= 0’ failed.
./crone.sh: line 7: 1133 Aborted ./build/ws-wrapper/ws-wrapper ws://:5556 $SCLANG

I’ve followed instructions on this thread but it seems i’m not getting this working…

#457

you need to look at the logs of norns-init not norns-maiden.

id recommend going thru the last troubleshooting conversation as we went pretty much went thru a full troubleshooting cycle.
as stated above, you should start with crone, then matron , the maiden - only when you know each has worked, should you go to the next step.

(e.g. maiden would be expected to fail if matron is not up)

#458

could you refer the troubleshooting methods?
Do you mean these followings?

journalctl -u norns-init.service -b
journalctl -u norns-jack.service -b
journalctl -u norns-crone.service -b
journalctl -u norns-matron.service -b
journalctl -u norns-maiden.service -b

#459

this is what i get

we@norns:~/norns $ journalctl -u norns-crone.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:33:38 KST. –
Nov 25 00:30:26 norns systemd[1]: Started norns-crone.service.
we@norns:~/norns $ journalctl -u norns-maiden.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:33:38 KST. –
Nov 25 00:30:27 norns systemd[1]: Started norns-maiden.service.
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Main process exited, code=exited, status=203/EXEC
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Unit entered failed state.
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Failed with result ‘exit-code’.
we@norns:~/norns $ journalctl -u norns-crone.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:46:38 KST. –
Nov 25 00:30:26 norns systemd[1]: Started norns-crone.service.
we@norns:~/norns $ journalctl -u norns-matron.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:46:38 KST. –
Nov 25 00:30:27 norns systemd[1]: Started norns-matron.service.
Nov 25 00:30:27 norns matron[490]: *** WARNING *** The program ‘matron’ uses the Apple Bonjour compatibility layer of Avahi.
Nov 25 00:30:27 norns matron[490]: *** WARNING *** Please fix your application to use the native API of Avahi!
Nov 25 00:30:27 norns matron[490]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=matro

we@norns:~/norns $ journalctl -u norns-maiden.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:46:38 KST. –
Nov 25 00:30:27 norns systemd[1]: Started norns-maiden.service.
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Main process exited, code=exited, status=203/EXEC
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Unit entered failed state.
Nov 25 00:30:27 norns systemd[1]: norns-maiden.service: Failed with result ‘exit-code’.
we@norns:~/norns $

#460

what do you get from the above?

#461

this is what i got

we@norns:~/norns $ journalctl -u norns-init.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:46:38 KST. –
Nov 25 00:30:26 norns systemd[1]: Starting norns-init…
Nov 25 00:30:26 norns amixer[311]: Simple mixer control ‘PCM’,0
Nov 25 00:30:26 norns amixer[311]: Capabilities: pvolume pswitch pswitch-joined
Nov 25 00:30:26 norns amixer[311]: Playback channels: Front Left - Front Right
Nov 25 00:30:26 norns amixer[311]: Limits: Playback 0 - 128
Nov 25 00:30:26 norns amixer[311]: Mono:
Nov 25 00:30:26 norns amixer[311]: Front Left: Playback 128 [100%] [0.00dB] [on]
Nov 25 00:30:26 norns amixer[311]: Front Right: Playback 128 [100%] [0.00dB] [on]
Nov 25 00:30:27 norns echo[440]: stopped > /home/we/status.wifi
Nov 25 00:30:27 norns chown[457]: /bin/chown: cannot access ‘/home/we/status.wifi’: No such file or directory
Nov 25 00:30:27 norns systemd[1]: norns-init.service: Main process exited, code=exited, status=1/FAILURE
Nov 25 00:30:27 norns systemd[1]: Failed to start norns-init.
Nov 25 00:30:27 norns systemd[1]: norns-init.service: Unit entered failed state.
Nov 25 00:30:27 norns systemd[1]: norns-init.service: Failed with result ‘exit-code’.
we@norns:~/norns $ journalctl -u norns-jack.service -b
– Logs begin at Fri 2016-11-04 02:16:42 KST, end at Sun 2018-11-25 00:46:38 KST. –
Nov 25 00:30:26 norns systemd[1]: Started norns-jack.service.
Nov 25 00:30:27 norns jackd[323]: jackdmp 1.9.12
Nov 25 00:30:27 norns jackd[323]: Copyright 2001-2005 Paul Davis and others.
Nov 25 00:30:27 norns jackd[323]: Copyright 2004-2016 Grame.
Nov 25 00:30:27 norns jackd[323]: Copyright 2016-2017 Filipe Coelho.
Nov 25 00:30:27 norns jackd[323]: jackdmp comes with ABSOLUTELY NO WARRANTY
Nov 25 00:30:27 norns jackd[323]: This is free software, and you are welcome to redistribute it
Nov 25 00:30:27 norns jackd[323]: under certain conditions; see the file COPYING for details
Nov 25 00:30:27 norns jackd[323]: JACK server starting in realtime mode with priority 95
Nov 25 00:30:27 norns jackd[323]: self-connect-mode is “Don’t restrict self connect requests”
Nov 25 00:30:27 norns jackd[323]: creating alsa driver … hw:0|hw:0|128|3|48000|0|0|nomon|swmeter|soft-mode|16bit
Nov 25 00:30:27 norns jackd[323]: configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 3 periods
Nov 25 00:30:27 norns jackd[323]: ALSA: final selected sample format for capture: 16bit little-endian
Nov 25 00:30:27 norns jackd[323]: ALSA: use 3 periods for capture
Nov 25 00:30:27 norns jackd[323]: ALSA: final selected sample format for playback: 16bit little-endian
Nov 25 00:30:27 norns jackd[323]: ALSA: use 3 periods for playback
Nov 25 00:30:35 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Running
Nov 25 00:30:35 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:30:35 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:30:35 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:30:37 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Running
Nov 25 00:30:37 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:30:37 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:30:37 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:32:42 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:32:42 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:32:42 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:32:42 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:32:42 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:32:42 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:32:42 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:32:42 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:32:42 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:32:42 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Nov 25 00:32:42 norns jackd[323]: JackEngine::XRun: client = supernova was not finished, state = Triggered
Nov 25 00:32:42 norns jackd[323]: JackAudioDriver::ProcessGraphAsyncMaster: Process error

#462

ok, so your first issue jackd is not happy… check your audio setup, and test it by running jackd from command line (described above)

norns.init does not need amixer , nor i2cset - this is covered in the doc I posted above.
also make sure you have edited according to how I describe.
(in particular the after clause is important to add)

also to debug, these things, if you stop/kill them, you can then run them from the command line one at a time, to get better error messages.

what hardware are you running this with? screen/encoders/sound card?
its not going to work at all well with the built in soundcard on the rPI, as its rubbish, and very cpu heavy… perhaps go look at pisound which is on sale this weekend :slight_smile:

sorry, i know this is all a bit vague but i don’t have a lot of time for this today