#34

Yup tried. I understand your point. If there is a way to re-send my sample folders + scripts with your method anew, i am all in but i dont see it.

#35

Another update. I found an Apple Time Capsule today (2009 version) second hand. Set up the the home wifi network with it and Norns will not connect to it. It just will not add the network. If anyone here is using an apple router and it’s working with Norns maybe I could go over some settings with you? Thanks.

#36

Do you have any control over whether the Time Capsule is using the 2.4Ghz band versus the 5Ghz band? If so try enabling the 2.4Ghz band only.

I hope to be able to do some testing in about 2-3 days.

#37

I tried the manual access method via terminal on a Mac but the TAB key does nothing so I can’t complete the command.

is there a way to keep or re-add the files/samples when doing a fresh SD etching?

#38

If you have an existing SD card and are looking to get your existing files off before re-flashing the SD card you may find one of the utilities to read ext3 / ext4 filesystems from a macOS or Windows 10 machine useful. My recollection is that the RaspberryPi and norns os image consists of two separate partitions. The first is an fat32 formatted filesystem; which the device boots from, is directly readable under Windows and macOS but that isn’t where the sample files are. The second (main) partition that is either ext3 or ext4 formatted and cannot be read from Windows or macOS without installing additional software. This larger second partition is where all the files that you are after live - specifically below the /home/we/dust/ folder.

caveat: I have not tried any of these tools myself
Windows 10 - there appear to be a number of tools for reading ext file outlined in this article.
macOS - using a something like ext4fuse mentioned on the “Add Ext4 Support to macOS” section.

Once you have the files you are concerned about copied off of the SD card then you can re-flash it using etcher as referenced in the shield setting-up documentation.

From there it would probably be a good idea to:

  • work through the WIFI / networking problems with the new clean image
  • go through the normal WIFI / network based update process to pull down the latest norns software and reboot
  • then copy the files pulled off the old image back onto the norns shield using either smb or ftp as outlined in the manage section of the norns documentation.
1 Like
#39

Thanks, i will have to go through this as i tried another pi (3b) and the same issue was consistent, no ethernet either. So pretty sure somehow my firmware got bugged up for some reason.

If for some crazy unluckyness the new image will still have no wifi, will i be able to place the files back in same way as copied for backup?

#40

new WiFi issue happening since updating to: 200712

booted up norns with “none” at startup.

no WiFi

looked a little further and realized no devices either…in fact…no USB whatsoever.
:open_mouth:
tried RESTART a couple of times and then a SLEEP and everything finally came back to life.

any clue at what’s happening?

also…i realized at one point that i had forgotten to turn on the Powerstrip and norns was running on it’s battery for a few mins.

this is occurring on all three norns.

thanks for any help!
:space_invader:

#41

this sounds like a USB hub shutdown as a result of not enough current— i suspect you may have a bunch of USB devices plugged in? this could happen if the norns is powered up without a wall connector.

also heads up, if you’re not actively using the wifi, i’d take the nub out. saves power, keeps the system more stable.

1 Like
#42

I’m having a wifi issue with the new Norns Shield. I’m able to find my network and enter the password. After hitting ‘OK’ I’m taken back to the menu and the STATUS says “activating” with my network name listed. Soon after it shows some activity under SIGNAL, but then my network name disappears and it gets hung on “activating” and never connects.

#43

A reboot / reset usually solves wifi issues.
Also try deleting and re-adding the network before reboot.

#44

Should have tried that before posting. That worked. Thanks.

1 Like
#45

not sure if this is a wifi issue or more specifically a maiden issue…

turned on my norns today in a while and it connected to my wifi just fine, except that I couldn’t access maiden. trying to connect through macos didn’t work either.

I tried to update (because I was one version behind) and that worked just fine, but still couldn’t connect to maiden after the update. removed the wifi network and re-added it, but that didn’t help either.

any ideas?

1 Like
#46

What did you try, what happened?

If you used norns.local and it wouldn’t resolve, i guess is some issue with hosts file / zeroconf, and you could try putting in the ip address explicitly

#47

sorry, to be more precise:

entering the ip address (in a browser or via the network window in macos finder) or norns.local both give me a “server not found” or a timed out connection failure, throughout all the steps listed above (before/after update/reset, before/after removing and re-adding the network info on norns).

wifi signal remains strong on norns through all of this.

1 Like
#48

If the device update completely successfully then that means your norns can access the internet, dns is working, and norns isn’t running in hotspot mode… so if you can’t access maiden via the IP address listed on the norns screen that leads me to suspect the computer being used to access maiden might be the problem. Does your network have multiple base stations? Multiple subsets?

#49

just wanted to report that i have the exact same issue as @karst - connected to wifi > couldn’t connect to norns.local or the IP address in my laptop browser or cyberduck (timeouts on both) > redid all my norns wifi network presets > updated to the new norns os via wifi just fine > still couldn’t access maiden from my laptop or phone. haven’t yet tried it on a different wifi network, will do as soon as i can.

#50

Out of curiousity, @madeofoak, @karst, when typing in norns.local or the IP address of the machine into a browser can you tell if the browser is using HTTP or HTTPS?

Many browsers have started to assume HTTPS (encrypted HTTP) by default when it is not explicitly specified in the URL. The built in server on norns is only setup to listen for HTTP requests (not HTTPS).

Does it work if http://norns.local/ is typed in explicitly?

#51

Does your network have multiple base stations? Multiple subsets?

@ngwese, good call. looks like the issue only exists while on the wifi extender’s network, not on the main network. don’t know why this worked a few weeks ago and not now, but I can only assume something changed on my network’s end.

#52

writing in ‘http’does not fix the problem, and i’m not on an extension or meshed wifi network.

#53

It is hard to say without really getting into the details of the hardware involved, layout of the base stations, etc. While “zeroconf” / “multicast-dns” is really handy for allowing computers to find each other by name (instead of by IP address) there are many things which can make it fail to function on anything beyond the most basic of networks. The chief problem is that mdns uses multicast addressing to broadcast out information regarding its presence to any computer on the same segment of the network. The complication comes when the multicast packets get to a router - the router could be connected to any number of additional network segments. If the router were to rebroadcast the information on all its other network segments one ends up with a bunch of chatter which can hurt the performance of a network (particularly on WiFi). The default behavior for routers it to not rebroadcast multicast packets. In larger networks the use of multicast is restricted if not out right prevented.

In the case of a mesh network I wouldn’t expect each part of the mesh to be a different segment/subnet but it probably depends on the gear involved.

Another problem which can occur is when devices (like norns) use DHCP to request an IP address for the network and get assigned different addresses over time. When norns gets an address it broadcasts that out via mdns, if norns is rebooted or moved to a different network it may acquire a new address and then broadcast that new address out. Computers within mdns range now can have two conflicting mappings for norns.local to an IP address. Generally timeouts/leases on the mdns entries will fix this conflict in time but it is not immediate.

A third potential problem is a variation of the above. If you have multiple norns devices on the same network each will try to claim norns.local which will lead to confusion.

Using the IP address should be reliable if/when norns.local doesn’t appear to be working. One step I’ve taken myself is to tell my DCHP server to give norns a static assignment which results in it getting the same IP address each time it boots (which is handy but not a requirement)

Hmmm. Not sure. What IP address does norns report on its main menu screen (press K2)?

1 Like