201115 went great for me. no issues! thank you for all the work you put into these.

4 Likes

@okyeron is correct, this is not related

Thanks for everyone’s help. I removed and reinstalled grd and everything works. Not sure what happened but I’m excited everything is back to normal. You people rule!

Sooooooo I just went through the usual System > Update steps and everything seemed fine, but I can’t get my shield to boot up! I’ve power cycled a few times now - all I get is two flashes from the green LED and then nothing.

Curious to see if this has happened to anyone else lately. I know I’ve updated at least once since June and didn’t have any issues then. Do I need to reimage or…?

oy, sorry to hear about the trouble – we haven’t heard any similar reports, but you can still access all of your files by inserting your sd card into your computer and looking at the rootfs drive under /home/we/.

if you need to get up and running quickly, i’d suggest grabbing the files you need and doing a fresh flash. if you can, please keep maiden open when you do the next update so you can catch any errors – please keep us updated!

Thanks! I ended up doing a fresh flash and am back in business. Not sure what happened but looks like it’s behind me now. :slight_smile:

1 Like

5 posts were merged into an existing topic: Fates - a DIY norns DAC board for Raspberry Pi

Hello! That sounds a lot like what happened to me last night. Flashing the card did the trick.

Instructions are here:

i am perplexed why shield updates are not happening correctly for some people— it worked as expected on mine here. were you all able to re-run it after installing the new image? has anyone succeeded in running the update from the shield?

Yup no problem. I kicked off the update and walked away. When I returned some minutes later the screen was completely blank and unresponsive. I did a power cycle and everything came back up on the correct version.

Are folks unplugging half way though the update maybe?

So, I flashed the micro sd card as described with a new image. Flashing went fine. As soon as I plugged the usb power to my fates, I still get a dark screen and red light…

looks like that my stock norns died after the lasted update and needs a fresh installation.
After the update it won’t go to sleep, so i pressed the reset button. Now it’s dead
:roll_eyes:

Pretty strange, after several power cycles, norns came back to live but with the old version. I re-run the update and now ith runs smooth.

ran the update this morning on my shield with no problems!

1 Like

I just tried running the update again after flashing and it worked fine this time around.

I had mentioned to Dan yesterday that when I looked at the contents of the card before flashing it, I did notice that some files had a modified date that was actually in the future, but I didn’t investigate further because that was the “ok probably time to flash” moment for me.

When I attach a handler to midi.remove, it’s called with 0 arguments. Is this a regression, an existing bug, or am I doing something wrong?

    midi.add = function (dev)
        -- handler code
    end

my factory Norns has been acting weird since the update. now it shows loading screen, then is blank. I can see it in maiden and add and delete scripts but the screen is blank. after a bit maiden shows
libmonome: error in write: Resource temporarily unavailable

i just started running into this on one of my norns.
i posed the same problem in the Questions area.

sorry to hear about the troubles. fwiw, i’m investigating the most friendly way to capture helpful logs from these types of situations (@Deru, also relevant to a separate post of yours). the less-friendly version is connecting to the norns via serial (https://monome.org/docs/norns/maiden/#serial-no-wifi), and when this happens execute dmesg and then journalctl. you can share the long logs through something like pastebin.

i’ll report back as soon as i have something concrete, if someone else doesn’t first :slight_smile:

2 Likes

Hi !
I try to back up my stock Norns from usb stick (because a lot of big audio files) but when I try with the command lines the answer is Permission Denied.
I try to reflash the usb disk or change the usb stick but no chance…
All the permissions of writing and reading are done on the usb stick.
I follow all the steps but always this message:

Cannot create directory ‘/media/usb/dust’ : Permission denied

If you have a solution for resolve it, it’s welcome :slight_smile:

1 Like