nematocyst

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

836 profile views

nematocyst's Achievements

  1. That's a good point. I suspected it did, but wasn't sure. I tested it as you suggested and indeed it does-- the engine does have a benchmark mode. The h3consumption utility seems to work well. I disabled hdmi, usb, and reduced cores to 2, all without issue. I can't measure actual consumption though. The only indicator is I can look at the trends in armbianmonitor to see if there's improvement. Also, I got an error when trying to lower DRAM settings. It seemed to work, as evidenced by the speed reduction on the benchmark test, however there was no /etc/armbian-release, spitting out an error. It seems I'm still running 5.11. heh. I'm not anxious to update, but the next release I will make myself do it, since I suspect the one I'm running has that awful allwinner root exploit. Actually... I guess waiting doesn't really matter since after 5.15? apt-get upgrade is all one needs to do. My issue is using a fresh image, but no way around that. It's just I have it working nicely already.
  2. I'm going to investigate thist stuff tomorrow, but I wanted to ask about my main usage case. I have an OjPi PC running a chess engine 24/7 on two cores atm, but could use 4 soon. Anyway, it does a LOT of idling, so I'd like to reduce power there if possible, but obviously when a game starts, it can require 100% DRAM and CPU for long periods. It doesn't think during the opening, and occasionally (due to the nature of chess engines) it is unable to come up with a move to ponder while waiting for the opponent. So it does sometimes go back to idle during a game, just not for long. I don't think a cron solution for DRAM will work in this scenario, but clearly reducing DRAM speed is desirable if it can kick back up when needed. I don't need any USB ports active, though it's in a location where it's rarely useful to use the box for fdisk or a TTL connection via screen. HDMI is off, but I don't think it's done in the fex file. It gets not much network activity, but relatively constant trickle. What do you think?
  3. Does exposing the 8888 port used by rpi-monitor represent a security risk? My OPi-PC runs 24/7 on a chess server, and I thought it would be interesting to allow people to inspect the RPI-Monitor pages. So I exposed/forwarded port 8888 on that device. I'm wondering if that's got potential security risks. It hasn't happened in a few years, but once I was accused of lying about my hardware specs. That's another motivation for allowing such access-- to demonstrate the reality of the situation to those concerned. I've become somewhat of a trustworthy figure in the years I've been running an engine online, so I doubt any accusations would go too far without any merit these days, but it is nice to be able to point to actual data that shows the truth.
  4. This is slightly tangential, but how to cycle power on the Orange Pi+? I'm not crazy about removing the barrel and re-inserting it, and it's quite inconvenient to do that at the wall plug. The switch doesn't seem to do that task.
  5. I've not had any troubles with power. My Orange Pi+ uses wifi + USB kyb + USB mouse + (powered) USB drive without issue. I bought the Plus with a power supply because I read people were having troubles. Before it even arrived, I was browsing through my computer paraphernalia box and discovered my ancient Belkin F5D7230-4 uses the same barrel and has correct voltage / amperage. I use it with an Orange Pi PC without issues. I've since noticed many power adapters in my box of stuff that would work if they had the right barrel. It is inexpensive to convert them if needed, though it's also inexpensive to just buy a correct adapter. You can probably buy 10 barrels that would work for the cost of one adapter though.
  6. I ran the nand-sata-install from git, presuming it was the latest, on an Orange Pi+. It doesn't quite work, no lights nor anything after removing the SD card and rebooting. I can, however, boot from SD and use the EMMC partition for the rootfs. This required rebuilding boot.scr from boot.cmd, changing the root= argument. What do I have to do to fix the EMMC so it doesn't need the SD card for initial image? I'm guessing I just failed to update the .fex boot sector before running the script.