Regular monome made norns - yeah, it plays fine over a midi track but isn’t receiving the clock data for some reason.

Edit - Definitely wasn’t a norns thing - sorry for the noise.

Yes and also tried turning file sharing on and off, restarting, etc. I’ve seen other comments about smb sharing being broken. Dumb question, can I file manage using another protocol from a Mac?

1 Like

sftp would also work — https://monome.org/docs/norns/sftp/

fwiw, i have smb working on macos 10.14.6, so maybe a catalina thing? thanks for the heads up!

also, if u could please share a screenshot of the permission alert (or email to help@monome.org), that would be dope

little confused here - I thought norns shield didn’t have UART over USB ? Is there a way to update norns shield without a UART > USB cable or an ethernet-usb cable ?

@corpusjonsey how did you update ?

I simply selected the menu option to update. I used a wifi dongle that came with standard norns.

1 Like

Adding new files over SMB is no problem; overwriting or deleting, however, just doesn’t work:

image

(attempting to delete via SMB on 10.13.latest)

OK, so, quick update. In the past few days I;

  • expanded my filesystem
  • ran the auto-update.

The files I tried to overwrite or delete over SMB seemed to have their owner/group set to root:root. I chowned them back to we:we, and everything is playing ball again. Strange.

1 Like

my apologies for the SMB problems. i clearly didn’t test enough use cases (like, deleting, gah)

i’ll get a fix out right away— has anyone solved the perms issue? (to save me some time on this)

1 Like

weird, i’m totally able to perform these actions. i had no idea things were this wonky for others, apologies! thank you for sharing the troubleshooting path <3

ok so I went ahead and build the latest image from @simonvanderveldt repo and tried that out. I’m on a pi 3 norns shield

in the wifi menu:

shows status: unavailable
shows list of networks under add
entered my password for my network, hit OK
I’m back to the wifi menu, shows status: unavailable
under connect I see none
hitting K3 on hotspot doesn’t have any effect

seems like K1 is causing the text blur issue, which I didn’t run into on previous images. forget if this ever got tied to build issues

** this could be a network issue - I don’t have vanilla norns to cross-check (though it doesn’t seem like hotspot is working anywho)

@andrew it’s going to be really difficult to help debug a self-built image, and the buildroot image has known issues. please just use the working-tested shield image i uploaded in the shield thread. run the 191230 update to get wifi working. i’ll try to get an already-updated image uploaded in the next couple days.

the issue is that I don’t have a way to connect sans-wifi (wifi nub, ethernet dongle, UART cable, etc) - an updated image would be great !

After adding my network/password it took like 30-40secinds for everything to connect. Are you pushing buttons too soon maybe?

gahhhh - I’m getting mixed up. for some reason I thought folks were connecting to a computer but I see now that a wired connection shows on norns when I plug into my router. sorry for the clutter ! I think I can get this figured out :woman_facepalming:

3 Likes

Yeah, with norns-shield on a raspberry pi you can simply plug in a network cable :slight_smile:

thanks to @simonvanderveldt and @zebra for some pointers on smb.

slightly modified config file. if someone who is explicitly having problems and is comfortable with terminal can test this.

smb.conf (788 Bytes)

download the attached file, copy if to your norns, then put it in the config folder. reboot.

sudo cp smb.conf /etc/samba/

i’m able to copy, add, delete files with no problem. also no invisibles are being made. (though any existing invisible .DS ._ files will need to be manually deleted)

4 Likes

Working OK here on shield.

I was going to suggest veto files after some research, but then saw many suggestions that it might not be the best thing to do?

I also just pinged the github thread with a fix for dot files in the select menu (if some still sneak thru after this fix).

EDIT - If someone wants to delete those ._ and .DS_Store files you could try this (Use at your own risk)

find ~/dust/code -name ._\* -delete

and

find ~/dust -name .DS_Store -delete
find ~/dust -name ._.DS_Store -delete
1 Like

This doesn’t work for me - do you have to prepend something to ;reset ?

sorry! meant ;restart @license

2 Likes

Nice, that works - cheers!

2 Likes