Anna Vahtera

Members
  • Content Count

    23
  • Joined

  • Last visited

About Anna Vahtera

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. How are you able to use Network Manager via serial console? Mine just outputs garbled junk when trying to view anything that has an interface. And how would you use arrow keys or any other special keys via serial console for that matter?
  2. so.. how do you input your SSID and passphrase if you don't have to modify anything? And what do you mean by router? What has THAT got to do with ANYTHING in this?
  3. armbianmonitor - u says this: Network/firewall problem detected. Not able to upload debug info. Please fix this or use "-U" instead and upload whole output manually this is why I used "-U" EDIT: nvm, got armbianmonitor -u to work. My bad.
  4. I'm trying to set up an OPi Zero Plus 2 with Armbian Buster. As the board has no soldered USB connectors and mine is still in the mail, I was forced to do all this via the serial console via the three pins on the board. (So no nano or nmtui or anything that has an interface.) I run into a problem where a) I couldn't join my WiFi network and b) NetworkManager refused to believe I don't want to use IPv6. So I had to disable NetworkManager and go the wpa_supplicant route. So now I'm in the position that I got everything to work BUT I have to *manually* enable wpa_supplicant and then issue ifdown and ifup - all via the serial console - at every boot before it works. Basically I have to do this at *every* boot: > login as user # sudo su # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf # ifdown wlan0 # ifup wlan0 After that I have a working IPv4 address and everything works, I can use ssh to connect to the OPi and it connects to the internet like it should (can 'apt update' etc.) The thing is, I REALLY don't want to keep it connected to another computer 24/7 and issue those commands every time it reboots. systemctl: https://pastebin.com/y8tk0DaN At this point, what should've been a 5min job (install armbian on the eMMC on the board) have turned into a 4h+ series of problems after problems after problems. I have followed some eight tutorials and advice that I've found on the subject and NONE of them have worked fully. Some at all. If I had the USB port, I'd most probably just re-flash the SD and start over and keep network manager and deal with whatever that comes with (I don't like NM, it gets in the way FAR too often if you want to manually do something), but I don't and it's impossible to use nmtui via the serial console. And it more or less works right now, only it doesn't start fine at reboot. There must be some easy way to get this to work from this point onward, right? ps. I can't paste armbianmonitor -U anywhere as it exceeds all limits on every paste site I have tried. EDIT: Managed to get armbianmonitor -u working, my bad for forgetting to "sudo" it. sorry.
  5. I mean this: "fbtft_device and flexfb are gone in 5.4" from https://github.com/notro/fbtft/wiki meaning now you have to you DT and cannot just use the fbtft device (like every tutorial out there says). That's the problem. "You have to use it with DT", but nowhere does it say HOW to do that.
  6. I want to control a fan via a script. I found a bunch of tutorials for pwm, but they were either for older version of Armbian, or for another board. I could not find a tutorial for Allwinner H6 boards. Apparently simple overlays=pwm doesn't work anymore. Anyone have any pointers as to how to go about it? my goal is to do something like $ ./setfan.sh 50 Setting Fan Duty Cycle to 50%... Nothing more complicated. I have a 5V fan for the system and I just want to tune how fast it should run - now it's going full 100% and it's louder than I'd like. I planned to do this with a trimmer but because the world situation and distances, the trimmers will arrive only after several weeks. And while I was thinking about it I figure why not just use the GPIO pins for driving the fan with pwm? Should be easily doable, I think. I just don't know how EDIT: I've been trying with WiringOP (now that I found a recent version that had support), but I've bumbed into another weird problem: The PWM pin on the OPi3 board is (physical) pin #7. If I do "gpio readall", it even lists that pin as "PWM.0" (It has WPi number 2), but when I try to put it into pwm mode (via 'gpio -1 mode 7 pwm' or 'gpio mode 2 pwm'), I only get an error that says: the pin you choose doesn't support hardware PWM you can select wiringPi pin 42 for PWM pin or you can use it in softPwm mode There is no WPi pin number 42. If I try to enable pwm on that ('gpio mode 42 pwm') I get an error "[pinMode:L1384] the pin:-1 is invaild,please check it over!" So no dice there either, unfortunately.
  7. Hello. I feel like this is a really basic stupid question, but for the life of me I can't find an answer. Every thread that I read about getting a display XYZ to work in Armbian references using fbtft. But apparently fbtft is now deprecated and cannot be used anymore. So.. what do I do now? I'm mainly looking to get ILI9341 -based 3.2" TFT and MPI3508 3.5" TFT to work with Armbian. Mainly testing with an Orange Pi Lite2 and Orange Pi 3 currently. I've read this: downloaded, compiled and installed the .dts. Also modified/added line to boot.cmd to use lcd as display according to https://docs.armbian.com/Hardware_Allwinner/ that page also mentions that a kconfig setting of CONFIG_VIDEO_LCD_MODE is required, but nowhere does it say how to do it, nor can I find it via Google (that might be on me, but "armbian kconfig CONFIG_VIDEO_LCD_MODE" does not result in any meaningful answers, except OTHER people asking the same question.
  8. I cannot get the screen to rotate 90 or 270 degrees. Inverting it works like it should, but not "sideways". uname -a: Linux orangepilite2 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 GNU/Linux xrandr --version: xrandr program version 1.5.0 xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 HDMI-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 /etc/X11/xorg.conf.d/01-armbian-defaults.conf: Section "Monitor" Identifier "Monitor0" Option "DPMS" "false" Option "Rotate" "right" EndSection Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection Screen is in "normal" orientation regardless of the rotate right option in the xorg conf. xrandr -o inverted works like it should and is noted in the xrandr output. Similarly with "normal". "right" and "left" however, do nothing. Or more precisely, they turn the display black for 1-2 seconds and then it returns to "normal" and displays the normal xrandr output, no "right" or "left" after resolution. echo <number> sudo tee /sys/class/graphics/fbcon/rotate_all works perfectly for all rotations on the console however. But of course it does not rotate X. EDIT: xrandr --output HDMI-1 --mode 848x480 works perfectly and sets the resolution like it should. xrandr --output HDMI-1 --mode 848x480 --rotate right does not. It blanks the display for 2 seconds, resets rotation to normal and resolution to 1024x7688, regardless of what they were before.
  9. I looked at those solutions earlier (my plan is quite similar to your doorbell thing), but I'm concerned about it being 5V and the length of the cable. How long is yours? I'd need to use 20m+ long cable, I'm afraid the 5V can't travel that far (that's why the standard really is 48V - to allow longer travel for the voltage). That's perfectly usable for shorter lengths and I think I'll order a few pairs of those just for trying them out and maybe even using them on shorter lengths - some places are just a pain to route another cable where one already is.
  10. That's a dang shame, really. POE would be an ideal way to power an SBC, if it's connected to a wired network. It's actually kinda weird now that I think of it, why there aren't many SBC that could be powered that way. Thanks for the answer though, appreciated. I guess I'll go the "dongle way" then, or come up with some other stupid solution... (knowing me, very probably the latter...)
  11. Hello. I've been playing with several low-cost SBCs for a couple of weeks now and I'm totally hooked on these incredible little things. Most of my boards are Orange Pi's simply because of the low cost (but I do have ODROID XU4 and a couple RPis too). Somehow one of my favorites seem to be the little OPi Zero (H2+), I'm using it as a "shell account" for if and when I need access to linux command line (most of my "big machines" are Win-based). However the Zero's POE implementation is... kinda non-existant really. You can read more about it elsewhere, let's just say it isn't usable without additional hardware. For my purposes, the OPiZero H2+ is powerful enough (I have the 512Mb version), so I don't need much power (however more memory wouldn't hurt). But for placement and usability, I'd REALLY like to have one that I can power with POE so I could just connect one cable and be done with it. What are my options for getting a new SBC for my purposes? Let's list some features: Absolutely needed: a) Gigabit Ethernet with Power Over Ethernet b) Small Size (well it's an SBC, but anyway) c) Must work with/be supported by Armbian [Mainline] d) Allwinner H2+ or faster, 512Mb RAM or more. Nothing really much else, but it would be nice to have:: e) 1Gb RAM (or more, this is one where more doesn't make it worse) f) Allwinner H5 -level power (and preferable 64bit) g) RPi-compatible GPIO header (at least the first 26-pins) Won't need: display output if it has serial connection header. Any audio capability, WiFi, BT.
  12. I got the PhoenixCard v4.1.2 straight from OrangePi.org, from their download folders, here: https://drive.google.com/drive/folders/1Vh2H14q9GDyfTdepVOIfAlrVjVZ_FM2A I'm using Windows 10 too and I didn't have any problems with it. I don't know if it needs the latest dotNET or no, but might be worth to see if both 3.x and 4.x are of the latest version. Other than that, I can't really help since it's working on my computer without problems.
  13. Also, note that OrangePi Android images cannot be flashed to microsd cards with a simple Etcher or WinImager (or whatever it was called). You need to use PhoenixCard v4.1.2 I'll type that out again; 4.1.2. I know, google tells you that the latest version of PhoenixCard is 3.1.x, but you can find the 4.1.2 from orangepi's site somewhere, I forgot exactly where. At least for me, the 3.1.x did NOT work at all. Once I found the v4.1.2 everything worked.
  14. Hello! I've just recently gotten a few (okay, several. I might have a problem here.) small single-board computers and I'm thoroughly in love with them. I also purchased a few small LCDs so I could make small independent thing that wouldn't require a huge display - perhaps even portable ones. While I do enjoy using the terminal for practically anything (give me lynx, rtv, byobu and the likes and I'm happy), there are certain advantages in a graphical user interface. But let's face it, the default UIs with modern window managers are... not exactly designed for small, low-res screens. With a 800x480 screen it's plausible to use just a normal WM and be rather fine with it. But let's take the more common 3.2" and 3.5" screens that have either 320x240 or in my case 480x320 resolution. Trying to navigate and use a computer with a 480x320 resolution with a normal window manager is not exactly the most joyous activity in the world. I can drive mine at 720x480 and that is almost usable with LXDE, but I'd prefer to run it at 480x320 because text is better at that res. So, anyone got any suggestions? Requirements are that it runs on ARM (of course) and is lightweight, preferably. Bonus points for being designed for touch screens (as most of the screens do have touch), but is not necessary (I don't have touch drivers installed on most of them, I prefer mouse + keyboard). But I admit having the advantage of being designed for touch use would be nice.
  15. Wait.. both pins, 2 and 4 are +5V pins, you can't use a cooler between to positive pins, you need a ground. Pins 6, 9, 14, 20 and 25 are ground. Connect the cooler wires so that one goes to any of them and the other to pins 2 or 4. (The manual calls those two DCIN, but as far as I know, they work perfectly well as outputs also. Just be aware of that. YMMV.) Also do note that some coolers drain quite a lot of power, so be sure your PSU can power the cooler AND the OPi3 at the same time.