#1923

FWIW, I just tried to update and my disk was full again. This time it was the daemon.log files (last time it was kern.log). not sure if that helps trouble shooting at all. 20%20PM

02%20PM
Screen Shot 2019-10-01 at 5.27.02 PM.png954×1222 211 KB

after deleting the 2 biggest log files, I was able to easily update via wifi from the Norns menu.

(here are the instructions @zebra provided before, kindly walking me through terminal stuff for those following this thread who are in the same boat)

41%20PM
Screen Shot 2019-10-01 at 5.29.41 PM.png1136×172 10.5 KB
51%20PM
Screen Shot 2019-10-01 at 5.29.51 PM.png1528×516 35.7 KB
26%20PM
Screen Shot 2019-10-01 at 5.29.26 PM.png1440×350 22.8 KB

#1924

daemon.log contains all the output from the crone process, among other things.

in the previous release there was some debug crud left in there. didn’t realize it would be an issue. in the last release i believe that should be gone.

sorry i don’t understand off top of head, enough about how to set more aggressive systemd service log rotation.

1 Like
#1925

Hello, apologies if this has been covered before, is there somewhere where I can read documentation on each of the engines? I’m having trouble parsing the immense amounts of discussion here as a mode for learning Norns.

3 Likes
#1926

You might realize this already but they generally each have their own thread here, and should have documentation in their README. Some attempt at centralizing this information that isn’t too much of a maintenance nightmare seems like a good idea, though.

4 Likes
#1927

I have a potential fix for this, but it has some issues. I would greatly appreciate a code review. PR here: https://github.com/monome/norns/pull/886

1 Like
#1928

Troubleshooting Wifi connectivity issues. I’ve searched through previous posts, but it seems earlier issues were perhaps solved with an update. Previously I’ve had no issues with updating Norns via Wifi or SSH connectivity via Wifi.

I’m running Norns 190817, and am trying to update to this most recent update. It won’t get past STATUS: activating. Doesn’t get an IP or any SIGNAL strength. My laptop / other devices connect to Wifi just fine.

I bought a new Wifi nub today, with same specs as the one included, but still the same issue persists.

Anyone else encounter this suddenly / randomly?

Fates - a DIY norns DAC board for Raspberry Pi
#1929

Have you ruled out signal strength by getting close to your wireless router? When I’ve seen this it was in places where my phone and computer connected fine, but I needed to move closer w/norns to get it to connect.

#1930

Yes, thank you for pointing that out. I’ve tried right next to the router, no luck.

The network name will appear briefly, then disappear. Status doesn’t change (from activating), and no register IP or Signal strength.

A couple times, Norns has locked up with no ability to control, requiring long wait times until I can put to sleep and wake up.

UPDATE: wifi working now! Perhaps it was @license tip to reboot router, although that didn’t work immediately. 24 hrs later, with my new wifi nub, wifi connected and update ran seamlessly. Old wifi nub couldn’t complete the update. Thanks for all of your help!

1 Like
#1931

Rats. I haven’t seen similar behavior. I’m sure someone else will chime in.

1 Like
#1932

I’m seeing similar problems with my 190801 “Fates” Norns, checked into logs and didn’t see much that was helpful other than wifi isn’t working, I noticed there is no /etc/wpa_supplicant/wpa_supplicant.conf available but there is a /etc/wpa_supplicant/wpa_supplicant_bak.conf with some useless info in there… I dunno will keep looking into it… I can get a hotspot going every two in five boots maybe…

#1933

Have you tried rebooting your router? I saw the exact same thing last weekend and that sorted it for me.

1 Like
#1934

I fixed it!

Turns out, I had to:

sudo vi /etc/NetworkManager/system-connections/my wifi network.nmconnection and fix the psk (password) under [wifi-security] … the password was ALL CAPITALS, and my password is lowercase on my router… I rebooted and it’s working now, BUT I had to fire up a hotspot FIRST then it will allow me to connect to the saved connection, otherwise it doesn’t show up in the list of options under “add”…

Update: now upon booting up, wifi connects automatically just fine, i was able to run “update” and upgrade to 190930 just fine with no problems so far :partying_face:

4 Likes
Fates - a DIY norns DAC board for Raspberry Pi
#1935

We (obviously :wink: ) don’t change the password anywhere when we pass it to the wifi config tools, see https://github.com/monome/norns/blob/55b52551fd51ac9e714b9de8810e699cf4f20934/lua/core/wifi.lua#L265
I’m assuming this is pebkac, you might’ve had caps-lock on or something like that?

P.S. nmtui for a tui or nmcli for a command-line interface is probably easier/a better approach than editing NetworkManager files, since NetworkManager likes to keep it’s own state and overwrite stuff in the files it uses.

If you’re buying a different wifi USB stick buy a better one with a better/properly supported chipset (see https://llllllll.co/search?q=chipset%20topic%3A14016 for some posts about this in this topic).

1 Like
#1936

An ID10-T error huh? :nerd_face:

Is there a method in Norns to change the case? I didn’t realize, it looked like the only option was uppercase, at least that was the default.

Edit: well that’s embarrassing

2 Likes
#1937

Keep scrolling for lowercase

2 Likes
#1938

20 characters of :hugs:

1 Like
#1939

I think I ran into this same problem this afternoon, listening back to a TAPE file, and for me it wasn’t exactly clipping – it sounded like clipping, but somehow extra awful. Lo and behold, when I zoomed in on the waveform:

14%20AM
Screen Shot 2019-10-05 at 12.34.14 AM.png733×527 11.2 KB

Apparently samples outside [-1.0, 1.0] were not clamped, but wrapped around.

I don’t think I heard these artifacts while recording, but I can’t say for sure. I was running a modified version of ash/earthsea with audio input feeding two softcut voices.

I won’t rule out my less-than-ideal “headless” setup (Raspberry Pi 3b+ with no special hardware, just a Behringer UMC-404 as audio interface) as the cause of my problem, but it sounded awfully familiar.

Obviously I too need to watch my levels. Someday I’ll have a screen, which will help with that…!

#1940

that makes me suspect that signal is out of range hitting tape, and getting wrapped during the conversion to 24b fixed.

i’ll try and reproduce. hard/soft clipper before tape write is probably called for.

[update] yep, this fixes it for me.

(i mean… you still don’t wanna be clipping.)

7 Likes
#1943

Sorry if this has been asked but my searches didn’t find an answer. How is norns at taking hot euro signals at the input?

Have a norns in the mail and am planning my rack which at this point would just be a mangrove, sisters, just friends, cold Mac and crow. Would rather not attenuate on the way in if I can just adjust in norns adequately. Thanks!

#1944

i would not suggest this— it’s the same as putting up to 10V into any normal soundcard. norns does not have any particular accommodation to temper these big signals, and it could even cause damage.

i use a RIP in between modular and norns, but there are smaller options of course.