#332

@isynx

the first error indicates a duplicate process (matron or sclang). try ./stop.sh, ./start.sh from ~/norns.

the second (JACK error) i also get occasionally when relaunching things from the terminal. we’re in the midst of cleaning this up. for now, rebooting works.

if you consistently get the JACK error on every bootup, or everytime you run stop.sh, start.sh, then it would be great to hear as many details as you can provide.

@scrag @n-So
i also am one of the unlucky ones whose wifi dongles are flaky. sometimes it just takes forever or fails to work, regardless of signal strength, and regardless of the connection management method. sometimes it’s fine. (sometimes it fails in the middle of ssh session and emacs freaks the heck out and i have to hard-reboot the laptop. fun!)

that said, if i can get signal strength up around -40dB then things are usually ok.

the best workaround i’ve found is to use a no-name USB-ethernet adapter, though that’s not always convenient. i can’t guarantee this b/c i’m not implementing it myself, but i believe we are gonna try and add kernel support for other (more expensive) wifi hardware.

2 Likes
#333

Is the consensus that the issue is a shonky wifi nub, then? This makes me happy. :slight_smile:

@tehn - if I want to try a new wifi dongle, then what’s supported in norns just now? Is it just the dongle that ships with norns? What do I need to look for so far as support goes - chipset / frequency / anything else?

I’ll try a USB -> Ethernet adapter in the meanwhile and see how I get on with that - do I just plug it in and start norns, or is there some configuration involved?

#334

“consensus” might be too strong a word :slight_smile:

but i have been obnoxiously complaining on slack for a while; no-one else in the dev group seems to share my experience but they tally with those of some forum members. so, it seems likely.

USB -> Ethernet adapter

there are different chipsets; for example r8152 is a common one (i think*) and its driver is included. so IIRC there’s no setup required assuming your network uses DHCP. (*i’m using some unlabeled thing i dug out of a pile of wires in the garage, r8152 is the module loaded by the kernel when i plug it in and it seems to match some common brands.)

2 Likes
#335

Having trouble updating to the latest beta, after I run
cd 190314 ./update.sh

It runs through the update, then hangs on
Setting up network-manager (1.6.2-3+deb9u2) ...

Then the wifi loses connection and I have to reset everything…
Any clues? Seems to happen everytime…

I’m worried I did these git pulls before updating to the latest version and in some way it’s borked it :grimacing:
cd ~/norns git pull
cd ~/dust/we git pull

#336

use a serial connection for this step

2 Likes
#337

Thanks for the quick reply, so I got it connected with serial and ran the update again. Ran through the update, but getting quite a few errors now, the trace ends with:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. rm: cannot remove '/home/we/*.wifi': No such file or directory rm: cannot remove '/home/we/*.conf': No such file or directory

hmm…

#338

Thank you so much! Yes, I am getting consistently JACK error on every boot up:15%20AM
I was using the image of 190303 on a CM3+ then update without re-imaging using the update file 190314. Maybe I need to try re-imaging? I did have once norns working without error and that was before I update (using 190303) after many reboots.

#339

@Molotov ok, i don’t think “cannot remove” errors are a problem. post whole trace if you want esp. if there are other errors

@isynx ok, CM3+ is important information. i can’t test that personally. has it ever worked since the HW upgrade? in any case, i would hang tight since a new image will arrive soon. at that point imaging might be a good idea.

#340

It did work once: no error and awake has sound.
Actually when you have an “audio engine error”, app using audio will stuck on the description page (even I press key 3, there is no response). But the time when it was working, I successfully went into the awake ui.

#341

Why are you using ./start.sh? All components (jack, crone, matron, etc) get started automatically

#342

bah, spent a few hours battling with it and ended up trying a full disk reset.
All appeared to go to plan as per instructions: https://github.com/monome/norns/wiki/img-flash-macos

Now switching norns back to run mode and dead, black screen, nothing apart from led turns on when I try booting. shiiiiiiiiiit :sweat_smile:

#343

Because I have problem to initiate audio on bootup, so I use stop.sh then start.sh to see error message.

#344

@isynx instead try using SYSTEM > RESET which resets the audio system and matron.

@Molotov responded via email

1 Like
#345

Tried re-imaging and reset several times, but still no luck: each time on boot up I got (error: Audio Engine)… I hope it is not some hardware problem:s
As long as it is not audio related script, it can be run without problem.

#346

Hmm, odd.
Can you post your logs (journalctl --no-pager) somewhere (like https://bpaste.net/ or another pastebin service)?

1 Like
#347

It said jack driver was not running?
Here is the log (updated):
https://bpaste.net/show/201a4e129c68
Thanks for the help!

#348

May I just say you guys are incredible and courageous for ironing out this 2.0 version, testing everything and it’s a chance to have you all putting so much energy into this. Can’t wait for the official release :slight_smile:

4 Likes
#349

yea ALSA is sad

Mar 16 07:12:43 norns jackd[339]: ALSA: poll time out, polled for 3999055 usecs
Mar 16 07:12:43 norns jackd[339]: JackAudioDriver::ProcessAsync: read error, stopping...
Mar 16 07:12:45 norns jackd[339]: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Mar 16 07:12:45 norns jackd[339]: Driver is not running
Mar 16 07:12:45 norns jackd[339]: Cannot create new client

are you familiar with ALSA CLI tools? might be worth poking the soundcard with aplay/arecord, &c

i would also try re-running update script (to get kernel overlays)

#350

Not at all familiar with that. I got this:
we@norns:~$ cat /dev/urandom | aplay
aplay: main:788: audio open error: Device or resource busy
I will try running the update script

#352

are you using ssh over network while updating networkmanager?

if so, try serial