• Content Count

  • Joined

  • Last visited

About thomasgrzybowski

  • Rank

Recent Profile Visitors

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

  1. Jens, Thanks again, thank you very much for explaining this - because without good understanding of what is going-on, any little mistake and you are dead-in-the water.
  2. Hi, I see where this bootcmd comes from - from the espressobin download page here. I was just tryin' to follow directions. I'll try to follow your directions instead. Tom
  3. So Jens, I created a fresh microSD card, flashed with Armbian_5.59_Espressobin_Debian_stretch_next_4.18.6.img, and booted to the Marvell>> prompt. Right away I see a problem: At the Marvell>> prompt, after I enter "printenv bootcmd", I get a garbage string return: Should I change it to "run boot_armbian"? Thanks, Tom
  4. ^ Jens, - Thank-you so much for your instructions! Yes, I had kind-of given-up. I'll try again with your suggestions and let you know how it goes! Thanks, Tom
  5. ebin-dev, thanks for the instructions! Just so that I understand, where do "these settings" referenced above need to be defined, in /boot/boot.cmd? Also, where do I run mkimage, at the Marvell>> prompt? Thanks again!
  6. I goofed-up my espressobin install and need to recover and start over. Here is what happened (to my embarrassment): I recently obtained a 1GB espressobin from I flashed the Armbian_5.59_Espressobin_Debian_stretch_next_4.18.6.img to a Sandisk Ultra and booted the board. The marvell>> prompt came up just fine, and I used the command bubt .flash-image-1g-1cs-800_800.bin spi usb to load the flash binary from my usb drive. But I did not know at the time that the correct flash to use was actually flash-image-1g-1cs-1000_800.bin. But my worse mistake was a
  7. Igor: "The build I am running on my NanoPC-T4 is showing all 6 cores." Igor: "If you build an image with build tools now, DVFS is partially broken on two cores since sources were switched to Ayufan's repo and they need further adjustments (WIP). Perhaps this is the problem?" Great! I'm gonna get me one of these, and will use the Download build instead of building one myself, for now. Thanks much! Tom
  8. Hi, I'm thinking of purchasing one of these boards. The CPU specs look very promising: CPU: big.LITTLE,Dual-Core Cortex-A72(up to 2.0GHz) + Quad-Core Cortex-A53(up to 1.5GHz). BUT, from what I read, only the Dual-Core Cortex-A72 is available to use from existing builds. What can the Quad-Core Cortex-A53 be used-for? Can I access these cores in any way? Thanks, TG
  9. Interesting that the BananaPi m64 Armbian image gives you eMMC support. I'm trying to get eMMC working with my Pine64so. I'm thinking if you can get eMMC working with your board, so can others with their Pine64so's - or vis-a-versa.
  10. Isn't this a common problem? Has anyone found a solution? Thanks, Tom
  11. Hi, I'm trying to use the emmc device located on the Pine64LTS - not neccessarily to boot (though that would be nice). I'm employing a 16GB FORESEE card, which I obtained from the Pine folks. First I installed the Stable SoPine64 Armbian_5.30_Pine64so_Ubuntu_xenial_default_3.10.105 image from the Download web page. When I booted the image from an microSD card, only /dev/mmcblk0 showed up - no /dev/mmcblk1. When I tried to boot from the image loaded on the emmc card, the boot failed. Next I tried to build a more up-to-date image, using: git clone --dep
  12. Cool - rebooted without the ethernet cable, and wifi came right up. Also able to successfully run transfer the results of armbianmonitor -u: /var/log/armhwinfo.log has been uploaded to Please post the URL in the Armbian forum where you've been asked for. I'm happy this all works now - thanks everyone for your advice. Would we expect the standard network tools to be used when this image is in production?
  13. Wow! When I plugged-in an ethernet cable and then ran nmtui-connect again (sorry), the wireless interface showed up. I was then able to activate it! Now this is a little strange to me. Here are the results from iwconfig: iwconfig lo no wireless extensions. wlx0013ef800c58 IEEE 802.11bgn ESSID:"verizon" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:2.462 GHz Access Point: 00:25:9C:13:CE:8B Bit Rate:72.2 Mb/s Sensitivity:60/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off
  14. Hmm, OK, I removed everything from /etc/network/interfaces, other than the loopback device. Removed everything under /etc/NetworkManager/system-connections/. Rebooted the machine to make things clean. Then ran nmtui-connect. Some progress: I now see a "Wired connection 1" there, where there was nothing before. Too bad I was expecting to see Wireless connection" Anyway, when I hit <Activate> I get the message: Could not activate connection: 'Connection 'Wired connection 1' is not available on the device eth0 at this time. I'll next provide the info from
  15. Also interesting: $ifup --force wlx0013ef800c58 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit Listening on LPF/wlx0013ef800c58/00:13:ef:80:0c:58 Sending on LPF/wlx0013ef800c58/00:13:ef:80:0c:58 Sending on Socket/fallback DHCPDISCOVER on wlx0013ef800c58 to port 67 interval 3 (xid=0xcb025177) DHCPDISCOVER on wlx0013ef800c58 to port 67 interval 3 (xid=0xcb025177) DHCPDISCOVER on wlx0013ef800c58 to 255