Petee

Members
  • Content Count

    55
  • Joined

  • Last visited

About Petee

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Time

Recent Profile Visitors

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

  1. Testing X9T Pro (S912 3Gb RAM Gb NIC) today with ARMBIAN 5.86 user-built Ubuntu 18.04.2 LTS 5.1.0-aml-s905 and using meson-gxm-vega-s96.dtb. Also tested desktop version. Boots fine. Network comes up. Looks like it talks IP6 just fine except that it cannot get to the armbian site on update using IP6. Wierd stuff with SSH. Reconfigured it and sometimes it just disconnects me. Disabled IP6 via armbian-config. Rebooted. Boot up got stuck in boot directory. Cold booted and it was OK and accessible via SSH. Using armbian-config installed desktop except that root ssh got locked. Redid the ssh config. Rebooted from console. Keep having issues with root and user ssh access. IE: disconnects randomly. Not sure what the issue is right now. For headless server use only care about the network connection. What is not needed is bluetooth or WLAN.
  2. Wanting to build a new Armbian server from a TV Box. Video is not a requirement here as the device will be headless. Just a quickie picture relating to the size of this box. I am impressed. It will be mounted inside of a security panel (Leviton Omni Pro 2) and serve as a console to said security panel using automation software. Ideally though want: - Gb NIC - 32 Gb eMMC - 4 Gb RAM Bluetooth and WLAN is nice to have but not necessary for my use. Been only tinkering here with Octocore ARM CPU TV boxes but not necessary. I am currently wanting to add a firewall (2nd NIC) and am familiar mostly with BSD PFSense and OpenWRT on a variety of devices. Currently doing this with a hardware modified micro router (NEXX) running OpenWRT. It is so small I can really just leave this device in place. Goal here is to install TV box inside of a combo automation / security media panel. The firewall would face current home LAN and may run a VPN server. Checking out Amazon see: 1 - Android 9.0 TV Box, 2019 H96 Max X2 4GB DDR4 Ram 32GB ROM 4K Smart TV Box Amlogic CPU HDMI 2.1/H265 /Dual WiFi 2.4G 5.0G/100M Ethernet/BT/USB3.0 Set Top Box (no Gb NIC) - S905 chipset 2 - ZYX 4GB 32GB Android TV Box - MX10 Android 8.1 Smart TV-Box Streaming Media Player H.265 64bit Supporting Wireless, 4K (60Hz),3D, RK3328 Quad Core Set-Top-Box - no Gb NIC - RK3328 3 - Android 8.1 TV Box with 4GB RAM 32GB ROM,GiMiBOX T9 Android Boxes Quad- Core 64 Bits Support BT4.1/ H.265/ 3D /5G WiFi/USB 3.0/ UHD 4K Smart TV Box with Remote Keyboard - RK3328 4 - H96 max X2 Android 8.1 TV Box, 4GB RAM 32GB ROM Amlogic Quad core Support WiFi 2.4G+5G/4K/3D Smart TV Box Streaming Media Player - no GB NIC The list goes on and on. What would you guys recommend me to get?
  3. Gave up and went back to the VIMII image which was all configured as a server. I stumbled here after installing docker and a custom docker application which you had to build to get it to work and running in to unavailble ARM64 libraries which I have never seen before. Wondering if this was because of the kernel version running.
  4. Updated to nightly build and it now shows on login: ____ _ ____ __ _ _ | _ \ ___ ___| | _| _ \ _ __ ___ / /_ | || | | |_) / _ \ / __| |/ / |_) | '__/ _ \ | '_ \| || |_ | _ < (_) | (__| <| __/| | | (_) | | (_) |__ _| |_| \_\___/ \___|_|\_\_| |_| \___/ \___/ |_| Welcome to ARMBIAN 5.84.190505 nightly Ubuntu 18.04.2 LTS 3.14.29 System load: 1.23 1.22 1.10 Up time: 41 min Memory usage: 4 % of 2733MB IP: 192.168.244.250 CPU temp: 35°C Usage of /: 4% of 29G [ 0 security updates available, 1 updates total: apt upgrade ] Last check: 2019-05-06 19:46 [ General system configuration (beta): armbian-config ] Doing an upgrade it wants to install: Calculating upgrade... Done The following packages will be upgraded: linux-image-rockchip64 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Then errors out trying to install the upgrade. Unpacking linux-image-rockchip64 (5.84.190505) over (5.83.190426) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-rockchip64_5.84.190505_arm64.deb (--unpack): unable to make backup link of './boot/System.map-4.4.178-rockchip64' before installing new version: Operation not permitted dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) mv: cannot stat '/boot/vmlinuz-4.4.178-rockchip64': No such file or directory Errors were encountered while processing: /var/cache/apt/archives/linux-image-rockchip64_5.84.190505_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
  5. Today tried with image: Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_server_20180601 I did not know that the older images were posted until reading another thread here. Works perfectly. ____ ___ / ___|/ _ \__ ____ ____ __ \___ \ (_) \ \/ /\ \/ /\ \/ / ___) \__, |> < > < > < |____/ /_//_/\_\/_/\_\/_/\_\ Welcome to ARMBIAN 5.44 user-built Ubuntu 18.04 LTS 3.14.29 System load: 1.06 1.11 1.14 Up time: 39 min Memory usage: 4 % of 2733MB IP: 192.168.244.250 CPU temp: 36°C Usage of /: 4% of 29G [ 0 security updates available, 1 updates total: apt upgrade ] Last check: 2019-05-06 22:26 Last login: Mon May 6 22:26:24 2019 root@amlogic:~# uname -a Linux amlogic 3.14.29 #207 SMP PREEMPT Fri Jun 1 09:27:52 MSK 2018 aarch64 aarch IE: network came up right away. It is a server and will be running headless such that a monitor will never be connected to it. Will try to update this image to current kernel to see if that works?
  6. Petee

    Updated htop

    Very nice works great!
  7. Thank you Dariusz Biernat. Tried mentioned Armbian_5.78_Aml-s912_Ubuntu_bionic_default_5.1.0-rc1_desktop_20190409.img. Same results. Yes tried again last night with same images dated 20190409. The Logitech wireless keyboard combo works well now. Thinking the battery was going out on the device. All except for the ethernet port works with both the desktop and server build. Tried every server and desktop version posted and same issue with all of them relating to not getting a DHCP address. It is odd cuz I tested the VIM2 build to work perfectly with the new box except that I do not get the bells and whistles from the Armbian build. None the less have configured the box for use and rebooted it a few times and all is well long math way. It is using the same VTB file for both images so do not understand.
  8. Relating to the T95Z Max - s912 octacore 3gb ram - purchased in May, 2019 from Amazon. I can get current Armbian releases to boot fine except it appears that the network interface doesn't come up with the standard release vtb or g200 vtb file. Bluetooth, Wireless, USB (even see USB 3.0 now) works. Display does not show when booting these in Armbian.
  9. Switched to an alternate Ubuntu 18.04 OS which booted up fine and works fine but doesn't have the same bells and whistles that Armbian has which I prefer. Everything is long math way with this OS but it is only a server so it doesn't really matter much. I did try all of the newer current releases of Armbian and they worked fine except for the Gb ethernet interface which doesn't make sense to me. Run these boxes headless and prefer them to boot up running SSH with an IP versus using a monitor and keyboard. Welcome to Fenix 0.5 Ubuntu 18.04.2 LTS Linux 4.9.40 _ ___ _ __ _____ __ __ ____ | |/ / |__ __ _ __| | __ _ ___ \ \ / /_ _| \/ |___ \ | ' /| '_ \ / _` |/ _` |/ _` / __| \ \ / / | || |\/| | __) | | . \| | | | (_| | (_| | (_| \__ \ \ V / | || | | |/ __/ |_|\_\_| |_|\__,_|\__,_|\__,_|___/ \_/ |___|_| |_|_____| * Website: https://www.khadas.com * Documentation: https://docs.khadas.com * Forum: https://forum.khadas.com Last login: Fri May 3 22:49:27 2019 from 192.168.244.231 root@HS3-ATL:~#
  10. For whatever reasons here cannot get an ethernet LAN DHCP address. I see the ethernet mac address fine. Wireless works fine. Should I give up and look for another device?
  11. Purchased two more Amazon sold Octocore / 32Gb emmc / 3Gb RAM / Gb NIC boxes a couple of days ago. These are T9SZ Max devices. The reset button is inside of the AV port (PITA). Less than $60 USD on Amazon now with one day shipping. Booting in Android WLAN and LAN work fine. USB Wireless keyboard does not work. Coreelec works fine except for the USB wireless keyboard. Using image: Armbian_5.78_Aml-s912_Ubuntu_bionic_default_5.1.0-rc1_20190412 Boots fine except that the USB wireless keyboard doesn't work and it never connects to the network via DHCP. Any suggestions? Got it it going. Noticed that I had to change the dtb file for ethernet to work. USB is working fine.
  12. The heat sink adhesive melted off? No. This was the second heatsink pack I purchased at Amazon. The first one didn't really have any adhesive on it. I thought the second pack of heat sinks had more adhesive. Best to purchase a sticky adhesive compound when installing these little heatsinks.
  13. Thank you Sundry. The ATL (Atlanta, Georgia) Pine64 crashed and burned up (literally) after the heat sinks installed slide off yesterday. I ordered a new TVBox / SD card to replace the dead Pine64 today and it will be there tomorrow and configured by end of business day tomorrow. I shut local Pine64 off (near Chicago here) and switched over to using a TVBox for the mini automation server. Currently moving all of the automation software from the ATL Pine64 to another TVBox there in Atlanta. That said and relating to the Pine64 I had asked about a promised updated to the Rock64 that never materilized for a year so I gave up on them and decided to maybe try the RockPi4 with more features and same size as the Rock64. Posted on the Rock64 forum- yeah I was nagging a bit here... ROCK64 RTC December 3, 2017 Question: Will the RTC be available in the December 12, 2017 Rock64 release? Answer: RTC is working, just lacking battery backup. The battery backup circuit not available on December production, we plan to merge in on January production but not sure will happen. This due to there is super long lead time on PCB manufacturing. January 30, 2018 Question: Wondering if the RTC / battery stuff is available on current Rock54 hardware? If not can I have instructions for soldering in battery posts and utilize the Pine64 battery holder? Answer: Attached is the RTC mod circuit for ROCK64. However, ROCK64 don't support battery charging and no such circuit available. February 9, 2018 Question: Thank you tlimm. So the hardware RTC with battery changes have been abandoned eh? Basically then all I need to do is solder on a battery to the Rock64 board. I have done similar here with my tabletop touchscreens. Answer: The ROCK64 board with RTC battery connector is not abandon. Check out the FOSDEM PINE64 table stand photo and you may able to spot this board. This is just a minor change and we will revise board revision during production run sometimes on Q2 2018 timeframe. May 2, 2018 Question: Curious if the new Rock64 hardware release has the built in RTC battery connections? Answer: This release already on the plan and originally plan release to production on this month. However, due to focus on ROCKPro64 activity, and has push to June/July. June 11, 2018 Posting another couple of requests today. 1 - when will the updated Rock64 with RTC and Battery will be available? 2 - will the Rock64Pro ever have a battery RTC option? (it would be a great little firewall) August 6, 2018 tllim Wrote: already factor into new ROCK64 revision including PoE option and micro SD UHS design. Needs to test all new function first before release and this takes couple months. 02-08-2019, 07:17 AM I do not see any update to using a battery for RTC on newest Rock64 which was going to be utilized as an automation server combo firewall. I have not used the Internet for time in over 15 years now and always used an NTP server with GPS / PPS. Over the years transitioned to using the PFSense box with a serial / PPS connection to a GPS which provides great time for me. I am very particular about automation and time. We are at the two year mark here. Time to give up and move on. The best thing that happened for the Pine64 was Armbian. That said I have moved on now from the Pine64 / Rock64 stuff. I would like to add an RTC / Battery to the TV Box. (icing on the cake)
  14. Did a nightly build update to the second TV Box here (TX9 Pro - Octocore, 3Gb, 1Gb NIC) and it is working well. Only thing though when logging in to the computer see the following stuff relating to RockPro64 changing from S912 standard release logo when logging in. ____ _ ____ __ _ _ | _ \ ___ ___| | _| _ \ _ __ ___ / /_ | || | | |_) / _ \ / __| |/ / |_) | '__/ _ \ | '_ \| || |_ | _ < (_) | (__| <| __/| | | (_) | | (_) |__ _| |_| \_\___/ \___|_|\_\_| |_| \___/ \___/ |_| Welcome to ARMBIAN 5.82.190423 nightly Ubuntu 18.04.2 LTS 5.1.0-rc1-aml-s912 System load: 0.00 0.00 0.00 Up time: 8:33 hours Memory usage: 10 % of 2840MB Zram usage: 1 % of 1023Mb IP: 192.168.244.150 CPU temp: 44°C Usage of /: 14% of 29G Last login: Thu Apr 25 00:25:58 2019 from 192.168.244.232 Running a couple of automation pieces of software, docker and mono (CPU sucker)..it is hardly working...headless Found the configuration file for the MOTD here: /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=rockpro64 BOARD_NAME="RockPro 64" BOARDFAMILY=rockchip64 VERSION=5.82.190423 LINUXFAMILY=rockchip64 BRANCH=default ARCH=arm64 IMAGE_TYPE=nightly BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image /etc/update-motd.d/10-armbian-header printf '\nWelcome to \e[0;91mARMBIAN\x1B[0m %s %s %s %s\n' "$VERSION $IMAGE_TYPE $PRETTY_NAME $KERNELID" Changed the file above such that I see this when I log on. _ ___ ___ _ ____ / ___|/ _ \/ |___ \ \___ \ (_) | | __) | ___) \__, | |/ __/ |____/ /_/|_|_____| Welcome to ARMBIAN 5.82.190423 nightly Ubuntu 18.04.2 LTS 5.1.0-rc1-aml-s912 System load: 0.13 0.18 0.23 Up time: 7:09 hours Memory usage: 31 % of 2840MB IP: 192.168.244.149 CPU temp: 47°C Usage of /: 18% of 29G Last login: Fri Apr 26 08:16:38 2019 from 192.168.244.231 root@ICS-TX9:~# Box is doing well running Docker, Home Assistant, Node Red, HomeSeer, Mosquitto. I have it connected to a Leviton OmniPro 2 security panel which also does automation via X10, UPB, Zigbee and ZWave. Doing WiFi using Tasmota and Espurna firmware for 1-wire temperature sensors, LED controllers, et al. This was all originally running on an XiS Xi5a dual AMD cube, then on a Pine64 and today on the TX9. I am impressed so far with the performance I see.