• Content count

  • Joined

  • Last visited

About grg

  • Rank

Recent Profile Visitors

79 profile views
  1. Looks pretty similar. Perhaps it's just an updated version.
  2. Awesome write up! Thanks!
  3. I'm powering a few Orange Pi Zeros, so I don't have any choice but to use USB for power (well, more or less). So, I spent some time searching for the right power adapter. It has to be at least 2A and only have one plug (to keep people from plugging in their phones). I thought I found the right product and purchased 20 of them. I was having issues with not booting from the microSD card and was really lost as to why this problem kept popping up. Anyway, I thought to double check the power. I wasn't getting more than 700mA -- sometimes much less. And so, I decided to look deeper...
  4. Same microSD card, v1.4 board, pushing the CPU a little harder (maybe even twice as hard). Nothing else was done to help it run cooler.
  5. Just adding this for a bit of historical context... This was running v1.1 of the OPi Zero board. I had a little script running to create some load. Also, this was inside a pretty tight enclosure with no heat spreader or heatsink.
  6. OTA Imaging / Remote Update /

    I find this super interesting. I'm going to dig in and see what it would take.
  7. Sorry, I didn't really speak to your problem. What I meant to say is that, I haven't been hitting that issue and I've done a TON of building. Here's what I've got running: Vagrant == 1.8.7 Virtualbox == 5.0.30 r112061 Running on a Mac. I can ssh-in every time. What I am having issues with is IO issues under heavy load. Still need to figure that out. But, I'll save that for another post. Best, Gabe
  8. I just updated it a bit ago. It's basically the same, but more inline with the directory layout the build tool wants. I would freshen it up and try again: $ vagrant destroy $ vagrant box update $ vagrant up BTW, have a look at the README and see what we can do to improve it. Let us know what if that doesn't work. Best, Gabe
  9. Just wanted to comment that, currently, the UUID is the same for every host installed from the same image. I'm sure this is well known, I just wanted to mention it here for additional context.
  10. Disable login on ttyGS0

    It seems to be somewhat nuanced (well, at least from the perspective of someone like me that hasn't done much systemctl stuff). I tried that command previously and it didn't work. It seems you have to plug your USB cable in between the Orange Pi and the other computer you're using *before* you disable that tty. Doing so will make sure you have the other device available (on my Mac it's /dev/tty.usbmodem1411). Once you've done that, you can then disable serial-getty@ttyGS0.service. Then you're able to use screen (or whatever) to communicate over that connection. If you reboot with it *disabled*, upon reboot, you can't establish the connection (/dev/tty.usbmodem1411 doesn't populate on the other host). This is where I was stuck before. The interesting thing is that the status from "sudo systemctl status serial-getty@ttyGS0.service" shows the same either way. Also, the kernel modules is loaded in each cases. Anyway, I'll dig around and see if I can figure out what's causing that. Thanks for the input. It pushed me in the right direction and helped me find that little inconsistency.
  11. I'd like to be able to plug my laptop into the USB OTG port and use that serial connection to communicate with an application on the orange pi. The default configuration is to give me a login. What's the correct way to change the getty settings for ttyGS0? Thanks!