but @Pavils-Jurjans I don't use nano on Onion/OpenWRT I know that on Linux utf-8 increases the size of the binary, so I suspect this is why OpenWRT disable it. I just looked at the nano makefile in my build system here are the arguments: --enable-tiny --disable-utf8 --without-slang --disable-color \ So if you build it you will need to update the makefile.

Hi David, Great post, it was very easy to follow and all works great however the terminal does not. All I see is Any ideas ? PS a warning at the start about oupgrade resetting previous configurations would be handy.

@Robby-Marston What type of dock do you have please?

@Zheng-Han This morning I turned on my Omega, entered ping repo.onion.io and then opkg uptate. Update did not happen, I was upset and turned off Omega. Now I turned on Omega and it successfully booted without errors, and the update was also performed. I hope that my problem has finally been resolved. But if she comes back, I will return to you. Thank you for your help.

worth mentioning that the 5 "accessible" ethernet are on the omega2s which is quite a bit more expensive.

Okay. This is what I did: I did a factory reset to the Omega. I went back to the documentation and followed all the steps from the beginning. I came to the blink program called 'STK01-blink'. I saved 'STK01-blink' to my Omega. I went to the terminal ran the code and IT WORKS!!!! Thank you sooooo much for your help, both of you!

Resolved using console-install-tool Console working again after typing the following: uci set onion.console.setup=1 uci set onion.console.install=1 uci commit onion console-install-tool Now have to try wifisetup again to fix Terminal problem. From command line: wifisetup reboot Everything back to normal

Resolved with wifisetup Connected to PuTTy via USB and did wifisetup Everything is back to normal, except for DNS issues. It does not recognize omega-xxxx.local. I have to enter IP addresses. I can live with that for now.

ADDING More Info: Adding a USB to Serial Device Worked .... It registered as ttyUSBS0 I setup Minicom with 9600 8n1 And was able to Text to it WTF

My mistake. I really meant something like Linux Gedit editor, which is in Mint or Ubuntu, and most other distros. It just shows up as Text Editor. And of course Terminal is in all versions of Linux. And nano I use all the time. I guess I was just frustrated with Omega2+ in general. PuTTY is just fine. And Omega2+ is getting better. And the rain has stopped and the Sun is out.

@Vinh-Tran The SD card works in the latest build As of 142 or something. They just don't have documentation on it. You can find your SD card in /tmp/mounts I believe. Also, try to install these packages to fix your issues. opkg install onion-console-editor opkg install onion-console-terminal

@Don-DeGregori said in Can't open Console Terminal: I am using Chrome. Saw this in documentation. Check out the manual install of aplication: https://community.onion.io/topic/1125/omega2-apps-editor-terminal-webcam-problems

@Peter-Tiedemann said in Omega2+ console terminal: keys not recognised: Same here, i just ssh'ed to it instead. Yes this is the workaround, ssh ... the console tool is not really a part of the onion os ... so you have to search in internet for the tools website and look there if it has a workaround yet. We had the same issues already with omega1..

@Chris-Parker I think I have found a solution, or more specifically, I personally have found a solution that works for me and solves my variant of the issue that you had. We both had the same problem, namely that in Chrome we were able to access Console Editor but unable to access Console Terminal (and in my instance, Console Webcam). My solution came in an unexpected way, namely by using another web browser to access Console. So, I temporarily abandoned my beloved Chrome and hopped on Microsoft Edge (I am running Win10. Perhaps you might use Firefox or other browser). Because I couldn't get the "http://omega-XXXX.local/" to run, I used "192.168.3.1" to access terminal. Upon logging in, I selected Console Terminal, and voila, it prompted me to install it! Turns out that what you and I are seeing is where the Console Terminal isn't installed, and for some reason it's not prompting us to do so, just showing a page stating that the IP address refused to connect! Hope this solves your issue! Update: After restart Console Terminal is a blank white screen, and Console Webcam doesn't work again. Might not be the solution needed...