yup. that seemed to be the main problem. doing a fresh install of os3.1 got me sd card access, and got tigervnc working through the access point. still no working wifi connection to networks… but i’m happy for now. thanks a ton!!!
1 Like
Just got one of these:
I can’t for the life of me get it to connect to my wifi. I put the right network name and password and it still says “problem connecting”. There’s no extra line in the text file and I’ve read everything over and haven’t found a solution yet. It connects over AP but I’d like to actually connect it to my network. Sadly being a musician doesn’t automatically include programming and tech knowledge right off the bat so forgive me if this is repetitive.
What type of WiFi router do you have? if it is operating at 5 GHz it won’t work, it needs to be 2.4 GHz. usually if it does 5, it can also be set to do 2.4. also could be the security settings on the router. it should be WPA2.
1 Like
It’s a Bell 3000 modem.
On the website it says “Two 5 GHz bands and one 2.4 GHz band, ideal for multiple devices.” As for the security it’s WPA2.
Are you trying to join the 2.4GHz band?
I’m trying to figure out how to do that. I believe it’s set to 5 GHz and I don’t want to change the settings just for the Organelle. I need my administrator password to see the options. I don’t have that with me so I tried to reset the password and for some reason the link to change my password hasn’t reached me yet so I’ll check back when I get that figured out.
Got the admin password but still have no idea how to select bands. I found two wifi connections that I assume one is for 5GHz and one for 2.4GHz but they both don’t work. On the Bell site it shows that both bands are up and running so I don’t know what could be the problem.
…As @oweno mentioned, it could be security settings on the router. Since the AP works, we know that the WiFi adapter and the Organelle are working correctly…
Just from observing discussions about the WIFI and the Organelle. I don’t think falling on the idea of it being a ‘user error’ is appropriate. This feature doesn’t work for everyone and it isn’t clear what is required in the manual or any resource for the Organelle. People are spending money on the Organelle and these WIFI adapters. Maybe don’t rely on the cutesy, quirky, “anyone can use it” facade when it comes to advertising the product when clearly it’s not that simple. I’d take a decent manual, guide and bug fixes over pumping out quirky videos with no voiceovers, irrelevant props, the same sonic textures as the previous video. Don’t blame those who support you when you yourself can do better.
1 Like
… Well finally someone said it lol. Had to create a throwaway account in support for this because I don’t want my opinion to paint my interactions on here but I to feel disappointed. The appeal of the Organelle is certainly there but I feel whenever someone with less knowledge about technical stuff makes an attempt to try an understand comes here for support they’ll get the typical unhelpful forum attitude which isn’t valid. Critter & Guitari definitely rely on that quirky cute aesthetic which makes it an approachable device in my opinion. The problem lies in that there isn’t any formal guide that addresses concerns. Two sentences or a sheet with a basic overview of the device isn’t going to cover what the Organelle demands of the user if they don’t know programming and computers. I agree with @Roses if the same amount of effort is put into a guide or manual that you guys put into creating videos with numerous props and staging it would definitely benefit a lot of people. Also I’m supporting @Roses opinion because I think he/she is criticizing the ideas presented here not the people as suggested on this forum.
Are @uhohthrowaway & @Roses & @TheMoonshiner all the same person? they all have the same IP address…
Or we’re in the same room together sharing the same WIFI hovering over 3 Organelles creating music and discussing the device. 
Are we really going to bring IP addresses into this to decide whether or not the points brought forward are valid? And to be fair leave @TheMoonshiner out of this. @Roses and I couldn’t get the WIFI figured out here in this space and he asked a genuine question. @Roses and I are the ones that have been discussing disappointments regarding what we’ve observed. We all like the Organelle and Critter & Guitari but really can you not bring forward constructive criticism here?
unfortunately, networking can be tricky…
@TheMoonshiner, the wifi stick you bought doesn’t support 5ghz… so you have to get it working on the 2.4ghz.
most often, the 5ghz and 2.4ghz are put on a different network name,
the next thing you have to check is what encryption is used,
@uhohthrowaway / @Roses
if you search the forum, you’ll see the most common cause for wifi issues, is using a wifi stick that is not supported by the kernel used on the Organelle - so not all wifi sticks will work
thats why a specific wifi stick (with a particular chipset) is recommend
also, best step to take initially is to run by DiagnosticLog, (see patchstorage) this will provide details of the stick etc, so its easier to see if its working or not… before hunting for network oldies.
1 Like
@thetechnobear I believe the Bell 3000 hub merges the two bands under a feature that decides for you which band is appropriate to use. I have to talk to Bell about this because they’re the ones that set up the internet for me and I want to make sure I don’t mess anything up. As for the security settings it’s set to WPA2. I’ll see if I can split the bands if not I’ll order another adapter.
@chrisk Yeah leave me out of the drama. While I don’t fully agree with @Roses & @uhohthrowaway opinions, constructive criticism is welcome on here and it specially says that on the site and I do think they bring forward some truths like little nuances that aren’t clear before making purchases for features that are included on the device. I get where you’re coming from regarding the IP address but 3 musicians using the same laptop in a studio isn’t the weirdest thing.
did you try running the organelle as an access point, and then connecting to its network?
at least to get you running, that should work regardless of the router etc.
(start AP in wifi menu)
I have but sadly I need my wifi network on the computer for other things as well. I’m going to place my bets on it being a band issue. Hopefully Bell can help me out with splitting them without issue.
Here’s the diagnostic log in case you guys see something that I don’t:
Diagnostic log
Sat Oct 17 01:07:49 UTC 2015
Organelle version 3.1
=================================================
ACONNECT
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
Connecting To: 15:0
client 15: 'OSS sequencer' [type=kernel]
0 'Receiver '
Connected From: 0:1
=================================================
AMIDI
Dir Device Name
=================================================
APLAYMIDI
Port Client name Port name
=================================================
LSUSB
Bus 002 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x148f Ralink Technology, Corp.
idProduct 0x5370 RT5370 Wireless Adapter
bcdDevice 1.01
iManufacturer 1 Ralink
iProduct 2 802.11 n WLAN
iSerial 3 1.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 450mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 7
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 1.0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.14
iManufacturer 3 Linux 3.14.14+ ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 ci_hdrc.1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 1
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0503 highspeed power enable connect
Device Status: 0x0001
Self Powered
Bus 001 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0781 SanDisk Corp.
idProduct 0x5571 Cruzer Fit
bcdDevice 1.00
iManufacturer 1 SanDisk'
iProduct 2 Cruzer Fit
iSerial 3 4C530000311111122571
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.14
iManufacturer 3 Linux 3.14.14+ ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 ci_hdrc.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 1
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0503 highspeed power enable connect
Device Status: 0x0001
Self Powered
=================================================
DMESG
[ 4.668149] systemd-journald[127]: Received request to flush runtime journal from PID 1
[ 5.385569] IR keymap rc-rc6-mce not found
[ 5.516501] Registered IR keymap rc-empty
[ 5.623028] input: gpio_ir_recv as /devices/soc0/ir-receiver.23/rc/rc0/input0
[ 5.652321] rc0: gpio_ir_recv as /devices/soc0/ir-receiver.23/rc/rc0
[ 5.949318] IR SANYO protocol handler initialized
[ 5.953224] input: MCE IR Keyboard/Mouse (gpio-rc-recv) as /devices/virtual/input/input1
[ 5.967959] lirc_dev: IR Remote Control driver registered, major 241
[ 5.979834] IR MCE Keyboard/mouse protocol handler initialized
[ 6.015899] rc rc0: lirc_dev: driver ir-lirc-codec (gpio-rc-recv) registered at minor = 0
[ 6.024139] IR LIRC bridge handler initialized
[ 7.037480] fec 2188000.ethernet eth0: Freescale FEC PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet:04, irq=-1)
[ 7.037905] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.341591] cfg80211: Calling CRDA to update world regulatory domain
[ 7.815880] usb 2-1: reset high-speed USB device number 2 using ci_hdrc
[ 7.959023] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[ 8.062894] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5370 detected
[ 8.153154] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 8.160339] usbcore: registered new interface driver rt2800usb
[ 10.490376] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.but did AP work? if it works, then you know the wifi stick is working …
this is why its always worth testing this first 
I suspect it might need to be WPA2 personal (WPA-PSK), at least thats what I have here working.
(dont think I have WPA2 enterprise available without reconfiguring my networking - which is not happening )
if AP is working, why not just switch over to it while your transferring stuff to the Organelle,
then switch over to your other wifi when you need to do that?
i guess its a pain if coding, but we all know its best to disconnect from the internet when coding, to help focus - distraction free mode 
1 Like
Yep AP works I just find connecting to the WIFI network would be much more convenient. I don’t know about the security settings, I don’t think I’d be able to change that here at least. I guess the Organelle wants me to work in distraction free mode which isn’t too bad haha. I’ll see if I can get Bell to provide me with some other info about my network here. I really want to try just connecting to the 2.4 GHz band to rule that out. AP mode will be my last resort. Thanks for taking the time to help me out Mark @thetechnobear.
1 Like
@TheMoonshiner & @Roses & @uhohthrowaway there was some concern on your end of about a lack of a manual… I just want to make sure that you have seen this one:
https://critterandguitari.github.io/Organelle_Manual
FWIW I’m all for constructive criticism. This is one reason for having the forum. Thank you for posting about your troubles here. As @thetechnobear said, networking can be tricky. And since you didn’t set up your studio’s WiFi and don’t know the security settings, it is probably pretty frustrating to have one aspect of the Organelle’s WiFi capability (Access Point) working but not being able to join your existing network.
@chrisk Yep well aware of the manual. In fact I have the whole thing printed out and put into a binder and it didn’t have the updated “This chipset operates on the 2.4GHz band (5GHz is not supported). NOTE: When joining an existing network, make sure it supports WPA2 encryption.” written down That line could have been crucial information for many who ran into this error especially for those who went out of their way to purchase adapters that really had no specification on what to look for. The manual was printed 14/03/2019 so not that long ago.
As you can imagine being musicians first, when you sit down with a device intended for musical creation you don’t sit down intending to troubleshoot for weeks. It’s frustrating and that’s why it’s important that we’re allowed to bring these issues to the surface because they aren’t always clear and the information isn’t always provided when needed. Hopefully this can be a learning lesson.