hi
i wanted to see if i could use deken with pd on organelle and i had an extra usb to ethernet adapter
this one
plugged it in and added
iface eth0 inet dhcp to /etc/network/ interfaces and voila
deken-ed else, cyclone, zexy and a few others
1 Like
I’m pretty sure ethernet adapters (or at least the one I have) also worked on the organelle-1 too 
2 Likes
ok cool, just had this extra one and i was curious
I just added: ZEXY, Cyclone and list-abs, which are pretty crucial for me these days for reviving older patches.
1 Like
I’m bummed that I just bought a used Organelle at the end of last month. This is a nice hardware update.
Ok so I finally got myself an usb-ethernet adapter for my M. Wifi was a bit unstable here so I wanted to go with a cabled connection.
After a bit of Duckduckgo-ing and reading this thread I figured out in the end that I also had to add auto eth0 to the interfaces file.
So:
auto eth0
iface eth0 inet dhcp
Vnc works really great now 
2 Likes
I’d love to get this working - where can I find the interfaces file you’re referring to?
Leeets see. I don’t have my organelle-m with me right now but the file should be in /etc/network/. Make the file system rewriteable, edit the file, add auto eth0 and also add iface eth0 inet dhcp. Save file, restart organelle.
It also seem to remember that the ethernet adapter and cable should be plugged in when you start up the organelle as this is when it asks for an ip address.
1 Like
Thanks - I don’t see a network directory under /etc
I should mention I’m on organelle 1, os 3.1
I do have a netctl directory, with a subdirectory called network… also an “examples” directory in there:
Any advice given this info?
Or maybe @thetechnobear or @oweno can help?
I also am stumped on how to make any of these directories or files writable - tried Get Info and checking the boxes “group” and “other” under the “write” column, but forklift gave me back an error: operation failed
bumping this… @chrisk @oweno @thetechnobear if any of you can help 
edit: sorry i am on os 4.0 !!!
this thread was helpful to allow write permission to netconfig: Set system/root as read-write by default
updated the last two lines of the netconfig file in /etc as below, but still unsuccessful for wired connection:
@KristofferLislegaard - any ideas?
What USB ethernet adapter are you using? I’m not sure all of them will work… I can try out the one I have (I think it is an “Amazon basics” adapter) with an Organelle 1 tomorrow and see if it works.
1 Like
Hey thanks, the adapter I’m using shows up as “DM9621A USB To FastEther” in my network settings on my mac. It just says “Inland®” on it. It does work to connect to my Norns - I had to turn on internet sharing in my mac’s System Preferences > Sharing.
I figured I just hadn’t modified the correct files yet, given the names and locations of files mentioned by others was different from mine. Is the screenshot in my last post the correct file to have added those two lines to? Thanks for the help
Yes, it seems to work on the Organelle 1. The issue I ran into was the USB ethernet adapter shows up as eth1. eth0 is an internal one that seems to be enabled but it is not wired up to anything. So first check if eth1 is showing up after plugging in your adapter. This will list the interfaces:
ls /sys/class/net/
You should see eth1, if not, it might be a driver problem, and you could run dmesg to check if any errors occurred. If eth1 is present, you can use the systemctl command to enable it.
systemctl enable dhcpcd@eth1.service
Then it should connect whenever it is powered up. I did notice a delay in booting when this is enabled, and the Organelle hangs on 99% for a few seconds while it tries to connect. This might be remedied by moving the dhcpcd service so that it runs after everything else is loaded, or disabling the service and just starting it in .bash_profile (/root/.bash_profile) after the rest of the Organelle software.
Thank you!!!
I was able to connect successfully after enabling it however…
Several minutes after starting up, I lose the ability to form a new connection (yet somehow any ssh/vnc/forklift sessions I have open seem to remain functional). Any idea why this might be happening?
Not clear on starting it in .bash_profile… maybe doing it this way would help, could you give a couple more details on how to do this?
Thanks again!
That is annoying that it stops accepting new connections…I’m not sure why this would be happening…
In the /root/.bash_profile file there are some commands that get executed when upon root login (which happens automatically). It is a funny place to put commands, but it is where the main Organelle software gets started (for reasons having to do with being in graphic desktop mode or not). Anyway you could disable the service, and then run “systemctl start dhcpcd@eth1.service” in .bash_profile to start networking. But I don’t think it will solve the above problem, since it still the same service ultimately getting run
1 Like