Posts made by Josh Rosenthal

So, a bit belatedly, but did ya'll ever get usb-ip ever working? While working on it, I found http://www.virtualhere.com/ which works using the MIPS version of their server on the Onion Omega. Performance doesn't seem particularly amazing, but definitely works, and gives a basic gui for control on clients.

Congratulations guys!

@Gabor-Flandorffer : Is that windows 10, and if so did you use the beta USB to serial drivers? The ones Onion has posted in the download section only work for win7/8.

See: https://community.onion.io/topic/329/windows-10-cp210x-driver/2

(@Boken-Lin, maybe we can update the downloads/documentation to reference the different driver for Win10?)

@Chris-Chibato, @Boken-Lin - Try this driver. Beta, but its been working ok for me on Win10 Pro
http://community.silabs.com/mgrfq63796/attachments/mgrfq63796/5/2268/1/Win10_Drive.zip referenced a few posts in by cgiga (silabs employee) on ‎08-10-2015 10:25 AM
http://community.silabs.com/t5/Interface/Is-or-will-Usb-to-Uart-CP210X-bridge-be-compatable-with-windows/m-p/147075#M2251
If you have issues with it make sure you're using a data cable (ie: can you connect your phone to your computer with it).

You may need to Add the device manually to the Device Manager. As ports do not show up in the list in Windows 10, you'll go to Action>Add Legacy Hardware>Install Manually from a List>Ports (COM & LPT)>Manufacturer = Silicon Labs, Model = Silicon Labs CP210x USB to UART Bridge.

Thereafter it should install, and display the COM Port in the Device Manager, which you can use for Putty. If it displays a COM port, but shows as a broken device, check your cable.

Hi @Lazar-Demin -
So, no, after the nonblocking pool, no keystrokes would work.

However, I resolved the issue. Tonight I decided to sit down and deconstruct my network settings one at a time (aka, time for a tomato upgrade, so why not wipe my settings and rebuild them). It looks like the issue was that my network was set to operate on a 192.168.3.* ip range.... and that made the Onion very very grumpy. When I tried to connect the Onion to the network set to 192.168.3.* it would claim to connect, but would never be able to ping google.com (pinging 8.8.8.8 worked fine). When I switched the network to 192.168.1.* , the Onion connected fine. I'm not sure if the Onion requires 192.168.1., or if the 3. settings are an issue because that's what the Onion uses for it's configuration AP, but that seems to have been an issue. I'd do more testing, but the wife is getting a bit upset with the network instability that I've wrought, so I think I'll leave answering the question of "Well, what if your network runs on 2.*?" to someone else.

Thanks again,
Josh

Update/further wackyness. I think this may be related to my wifi settings. I gave up around 10 hrs, rebooted, factory reset, and saw the serial connection appear to be stuck saying "[ 68.610000] random: nonblocking pool is initialized".

So I tried the second Omega. Same thing. At some point I decided to try my phone's wifi hotspot... and suddenly it all "worked". Wifi connection, hot spot, etc. So I took the original Omega, logged onto its network, switched it over, and again, it works.

A few notes and questions:

1. Any ideas what might be wrong in my main network's settings? TomatoUSB, with a small amount of DNS games (DNSmasq is running to intercept an amazon dash so it can be used as a light switch), but I've been slowly disabling those, and still no luck.
2. Network issue symptoms. When the Omegas are connected to the main network, they

• cannot ping google.com
• can ping outside ip addresses
• from the Onion console, they cannot access the terminal (but can access the file system, stats, etc)
• they cannot do oupgrades
• simply adding a name server to resolve.conf doesn't fix the inability to access Onion terminal

1. Not sure if its supposed to be this way... When I connect to the Serial terminal for both of these, I see what appears to be a timestamp and log, not a console I can type things in, except for a few prompts during reboots.

Any thoughts are most welcome.
Josh

Hi All,

How long should oupgrade take? I'm currently on > 6 hours and waiting, but don't want to pull the plug or control-c given that I don't have an Ethernet module (or an expansion dock, as mine was one of the lost orders that only recently started getting partially filled, and I'm told they're OOS while the new ones come in).

A couple notes that might be relevant:

• I had problems with wifi setup. I wound up doing a windows 10 serial connection setup
  (using the driver from
  http://community.silabs.com/t5/Interface/Is-or-will-Usb-to-Uart-CP210X-bridge-be-compatable-with-windows/m-p/147075#M2251 )
• This still did not allow me to ping google.com. I tried ctrl-c during the wifisetup as per other threads, but that had no noticeable affect
• I noticed I could ping IP addresses, so I added a nameserver (8.8.8.8) to /etc/resolve.conf, at which point I could ping google.com.
• I then ran oupgrade last night. As of leaving home this morning (6+ hours later), this was still saying "Checking latest version online"

So...

1. How long should oupgrade take?
2. Given that I don't have an Ethernet module and the ability to reflash, what's my suggested next step?

Thanks!
Josh