#22

try logging in via serial and run nmtui which is a networkmanager text user interface. it sometimes does a better job picking up networks. once your network is set up it’ll appear in the norns menu.

do you know anything about your routers’ setup ie WPA/WEP?

#23

Do you know how to connect via serial?
If so, can you paste the output of date?

#24

To make sure we’re on the same page, it shows up at the top of the list when I go to “add” network, it just doesn’t succeed (or fail) to connect. I can try to connect over serial, but I haven’t done that before. Might be a couple of days before I can get around to it, I have a couple of performances this weekend

#25

So, rookie move, I updated from 181101 straight to 190422 as I didn’t see the bold warning. Things aren’t working properly. Is there a way to revert back to 181101 to proceed properly?

#26

did you do a manual update? the 1.x menu system should’ve failed trying to use a 2.x update file.

i’d suggest manually running the 190405 (2.0.0) update and you’ll be fine. you can then use the MENU UPDATE function to get to 2.0.1

#27

i had 190405 and 190422 on the same USB key and it grabbed 190422. if i run update from the norns menu i get nothing. can’t connect over wifi either.

#28

are you sure the update actually ran?

you can see the version number in the SYSTEM menu, or (if it did run) by pushing KEY2 at the HOME screen

#29

yeah, it says 190422 beside system on the menu.

#30

ok. you’ll want to manually run the 190405.

see the instructions here: monome.org/docs/norns/#update

be sure to erase 190422 off the usb stick

#31

quick shortcut for updating all scripts at once with git pull.
cd into ~/dust/code then:

find . -mindepth 1 -maxdepth 1 -type d -print -exec git -C {} pull \;

8 Likes
#32

FYI - there’s a bug or two with foulplay and fairplay (also awake and maybe others) regarding external clock (or other midi inputs when set to external).

I’ve submitted a PR to fix fairplay. I’m gonna message @Justmat about foulplay as that might be a more involved fix.

5 Likes
#33

Hey! Looking for some help. I updated from 181101 straight to 190422, bypassing 190405, and now my Norns ain’t performing it’s usual magic. I’ve tried to follow the manual for “Other Access” and seem to be struggling updating via USB. I’ve got 190422 on a USB plugged into the Norns and my Norns connected to my Macbook via USB. I access Terminal and that’s where I get error messages.

I’m typing: screen /dev/tty.usb(A9053JGF) 115200
and having no luck. Confused if the serial is supposed to be my Norns serial # or the port # on my macbook…

Any idea what I’m doing wrong? Thanks in advance!

1 Like
#34

hmmmmm maybe a long shot, but how did you arrive at A9053JGF? that part of the command should be auto-completed by pressing tab after tty.usb.

#35

First of all, compliments for the new updating process. It’s really something new, powerful and user-centered.

And thanks for letting me know about nmtui because with my second norns (my primary norns is non-textured, black-bottomed, nub with a red line, my secondary one, acquired a month or so ago, is textured, grey-bottomed, nub with no line) I had never been able to connect to my home network. This solved it. I had tried with both nubs to no avail. Now if the nub is inserted, it’s automatically connected. :raised_hands: :rainbow: :unicorn:

1 Like
#36

whenever I pressed tab there it would make a sound and nothing would happen so I found my serial # and typed it in there.

#37

Prob not what you want. You need the serial address

On you Mac type ls /dev/tty.usb* (in terminal) and look for the address of your serial connected norns.

1 Like
#39

Are you maybe including the parentheses? i.e.

/dev/tty.usb(

then pressing tab? If so, leave out the parenthesis and then press tab.

#40

So that worked but it only takes me to a blank Terminal screen with the error message:

"cannot open line for /dev/tty.usbserial-A9053JGF R/W: Resource buy

sorry could not find PTY"

Any thoughts?
Thanks for all the help folks!

#41

Fixed my duplicate engine issue from earlier and everything seems to be running well…except for what appears to be a little tape bug: when scrolling to the tape screen, and arming record, Norns doesn’t seem to always increment the number of the file it’s writing to — either it overwrites the latest recording, or it jumps back to position 000.wav.

Experienced this when working in Glut and Haven, so far. Can log on Github if needed!

#42

Ok, I don’t have experience with this error, but google tells me that you may need to close a previously attempted screen session. Try using Activity Monitor to close the previous screen attempt, or just restarting your computer and attempting again, this should clear it up.

1 Like