#353

FWIW - The version.txt file is incorrect in the current 190314 update package (and will show 190303 on the norns screen). So… that’s not a clear indicator of if the update worked.

If norns is otherwise working, don’t worry too much about it and wait for the next update

1 Like
#354

This is a normal response for that command (or at least I see the same response as Jack is using the audio device).

aplay -l will list your audio devices

You could try ps aux | grep jack to see if jack is running - if it is, that should return something like:

we        1306  0.0  0.0   4376   568 pts/0    S+   21:49   0:00 grep --color=auto jack
we        2671  3.1  9.1  98544 91568 ?        SLsl Mar14  49:38 /usr/bin/jackd -R -P 95 -d alsa -d hw:0 -r 48000 -n 3 -p 128 -S -s

from your journalctl output, it looks like jack is not starting properly.

you might need to hold up and wait for a new cleaned up image to start over.

#355

Thanks for the help! I just tried re-update from ./update.sh and I notice something:
https://bpaste.net/show/b8fccf20b449
tar: boot/fixup.dat: Cannot change ownership to uid 1000, gid 1000: Operation not permitted
Maybe it is related to the issue (edit: not related)?
Also:
we@norns:~/update/190314$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpimonome [snd_rpi_monome], device 0: monome cs4270 cs4270-hifi-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0
we@norns:~/update/190314$ ps aux | grep jack
we 311 0.0 9.1 99664 91632 ? SLsl 09:17 0:00 /usr/bin/jackd -R -P 95 -d alsa -d hw:0 -r 48000 -n 3 -p 128 -S -s
we 30987 0.0 0.0 4376 544 ttyAMA0 S+ 10:01 0:00 grep --color=auto jack

So it is running I guess

2 Likes
#356

i’ve tried several times today and had to use this app to finally flash the emmc

2 Likes
#357

@glia managed to resurrect the norns with a few flash attempts, phew! But seem to have lost all wifi capabilities in the process, just get a blank screen when trying to ‘add’ or ‘connect’… :thinking:

1 Like
#358

You could type nmtui via ssh/screen to configure wifi from terminal or you can wait for the next update:)

1 Like
#359

ah thanks, I’ll try this later :slight_smile:

#360

Thanks. Are/were you also getting this when you flashed (using rpiboot) the 190303 image?
I believe you mentioned that you flashed it. Just to be sure that we’re talking about the same thing, with flashing I mean taking the bottom off, toggling the switch and then using rpiboot to flash the .img.

#361

I’m having a hard time reproducing this problem, could you maybe run some commands and paste their output?
First one would be journalctl | grep -i kill, second one would be rfkill list and finally cat /var/lib/NetworkManager/NetworkManager.state

#362

Yes, I was also getting audio engine error after flashing the 190303 image (on CM3+). But the strange thing is that the next day morning when I boot, norns was working and I got no error (I was able to go into the app by pressing key3, before I cannot) and got sound in awake!?

#363

OK. Have you used v1 before flashing to v2? Did the same failure manifest itself there?

#364

v1 was working ok. I think I was having some problem at the very beginning (1 year ago) but then it is working all the time. Just the day before I flash v2, v1 was working by then.

#365

Maybe it needed a reset and the reboot fixed it?

#366

Is reboot = sleep then boot? I tried that, but not working. Worst scenario, I can try putting my CM3 back and see if it goes back to normal…

#367

Hmm, that’s odd. The issue you’re having seems to be either a driver or a hardware issue. Since we haven’t changed anything regarding drivers between v1 and v2 it seemed to be a hardware issue but since it worked fine with v1 I’m somewhat surprised.

Could you try the CM3 if that’s not too much trouble? The same image should work on it.

[edit] One additional question: what do you have in the USB ports?

#368

please try flashing v1 to the original CM3 to ensure your hardware is working:

https://monome.nyc3.digitaloceanspaces.com/norns181008.img.zip

#369

Eh… now I am also having audio engine error in CM3 (running 181101)!! I do not understand… as I did get it working for a while after flashing v2 190303
After reset audio, the error will disappear from the display but I still get same symptoms as before (no sound and cannot run audio related app).
BTW I have nothing plugged in USB ports.

unnamed
unnamed.jpg3024×4032 1.74 MB

#370

when was the last time you had this working properly? 181101 error isn’t great. might just want to send it in— e-mail info@monome.org

#371

Last time it was working was yesterday morning then the second latest was last week.:sweat_smile:

#372

Edit: OK seems to be fixed.

Flashed back to 190303, was still not working, flashed back to latest. Hard reset, soft reset, changed ports and it seems to have sprung back to life!
:sweat_smile: