#14

can you describe what happened when it broke?

it sounds like there was a timeout with detecting the new version— which is likely a wifi/internet issue. if this happens in the future, try rebooting.

but what follows with the terminal business— did you shell in and run the norns update.sh manually?? from the norns folder? this is absolutely not good and should not be done (there are no instructions anywhere suggesting doing this, i hope). while this process should fail— i wouldn’t have expected it to brick your OS (though i haven’t looked, it very well may).

#15

Yeah, based on what I’m seeing and reading here, there was some sort of issue with the internet connection and the update process. It was odd because I was able to connect to Norns via wifi and the system status showed wifi was working.

I did ssh into Norns and manually ran update.sh. The reason behind this is because when I had Norns in the past, that was the update process if I recall. Took a break from things and it seems they are a little different now, so I won’t dare do that again…eek. I’m in good shape though now after reflashing and running update via the Norns menu. It didn’t take me long to get up and running again and to my surprise, a lot of the scripts I use were part of the image. :+1:

Sorry to cloud the thread, but hopefully someone benefits from the odd things that happened and just restarts their Norns if updates don’t seem to start. :slight_smile:

#16

glad it worked out and thanks for the heads up— it gives reason to clarify the purpose of some files in the repo, along with adding some timeouts if the wifi github query isn’t working.

#17

Does this fix the jumpy encoders?

#18

nothing in software is going to fully fix jumpy encoders. you probably need to replace the encoders

#19

Ok. I’ll send it back cause right now it’s unusable.

#20

This update on a DIY shield went well here. Got it trough on the second go. Thanks!

#21

Works on my norns shield and no issues with my script “pixels” as of yet.

1 Like
#22

Hi all!

I hadn’t used my norns shield in a while and decided to check out some of the new scripts.
I checked if there were any updates and there was one so I updated the norns and ran a few scripts.

It may be a coincidence, but after this update, the norns won’t turn on! There’s a red light on the rPi, but I can’t see the norns on the network.

Is there anything I should be doing? Is there any way to do a full reset and get it back running?

Thanks in advance!

#23

see the install instructions for full reset

do you recall what version you were on previously? did the process complete?

#24

Thanks! I’ll have a look at these instructions and report back!

Can’t remember which version I was coming from and the process did complete as I tested a few scripts before being “locked out”.

#25

Apparently it was an SD card problem!
Was having error messages while flashing the drive and tried a different card and it booted up just fine!

Thanks @tehn !

#26

sadly SD card quality is a tricky of failure— glad you had a another to test!

1 Like
#27

FYI in this update, it seems the screen levels have been tweaked to be 0-15, to match grid messages i guess. Previously, screen.level(16) set max brightness on a pixel.

1 Like
#28

I might be seeing some kind issue related to screen sleeping while using my script “pixels” on this version of the OS. Myself and another user have experienced system freezes after the screen timeout (10-15 minutes?). The norns becomes unresponsive when the is asleep and a hard reset is required.

I had not experienced this in my script before the update, although I did alter pixels significantly recently and it is possible that the script itself is hitting a snag. The similarities between the user posting on the pixels thread and my own seem to indicate the possibility of something happening during the display timeout.

I’ll try to get something out of matron and report back.

#29

hi, also running into issues; not sure if its related to the above post by @distropolis but my norns shield went to sleep (i wasnt running a patch at the time) and now it won’t boot back up - red light comes on, green light flashes for a bit then red light stays permanently on but no startup sound and no screen.

i want to try reflashing it but there’s some stuff on the TAPE that i want to save :grimacing: in another thread someone had mentioned plugging the SD card into a computer and getting the dust folder from there, but when i open my SD card on my mac i can’t find it, it only contains files im assuming are related to the image/boot? a bunch of .dtb files etc. what do i need to do to pull stuff from the dust folder?

#30

Unfortunately accessing the portion of the SD card which contains the dust folder requires a Linux machine (or VM).

The SD card (or EMMC in norns) contains two separate partitions. The boot partition is a small file system which contains just the selection of files required to boot the device. It is a FAT32 filesystem which is something that most computers; such as those running macOS, can read. This boot partition is what is showing up on your mac. The main or root partition is the Linux ext3 file system which contains all the scripts, audio recordings, the norns software, etc. I don’t know of any utilities off the top of my head which support reading an ext3 file system on a mac.

UPDATE: I haven’t tested this personally but installing ext4fuse as described here might work. Not sure if it handles ext3 filesystems.

2 Likes
#31

i feel the update is very likely not the issue. have you tested screen wakeup with a known working script?

i quickly glanced at your code and you have some screen calls that are outside of your redraw() function which is not a good thing (basically, it’ll break stuff).

#32

Thanks for taking a quick look. It’s hard to say because I wasn’t aware of the issue before the latest update. I just recovered from another freeze here and neither mator or the sc window reported any errors. The screen had gone to sleep and my script was playing back just fine. When I returned about ten minutes later, the norns had frozen and sound had stopped.

There are several calls outside of the redraw loop, but none of them are executed without direct interaction from the user. Letting the the script just drone on unchecked shouldn’t call any screen functions outside of the redraw() loop. If anything, I suspect it could be possibly be related to my implementation of @zebra’s The Bangs engine (which is also only a week or so old).

I’m just throwing this out there because it is unclear to me as the cause of the issue.

EDIT: I have another user with a similar issue not related to display sleeping, so feel free to delete these posts or move them over to the pixels main thread. It probably is an internal issue.

#33

ah thank you for directing me to this, ext4fuse worked perfectly to get everything i needed!

3 Likes