<?xml version="1.0"?>
<rss version="2.0"><channel><title>General Chat Latest Topics</title><link>https://forum.armbian.com/forum/195-general-chat/</link><description>General Chat Latest Topics</description><language>en</language><item><title>Minix UH-9 Auto Power On</title><link>https://forum.armbian.com/topic/59241-minix-uh-9-auto-power-on/</link><description><![CDATA[<p>
	The problem (Armbian on U9-H requires physical button after power loss)
</p>

<p>
	The discovery process (MCU at I2C bus 0, address 0x15, register 0x11)
</p>

<p>
	The fix: i2cset -y 0 0x15 0x11 0x00
</p>

<p>
	The systemd service for persistence
</p>

<p>
	That 0x01 = button required, 0x00 = auto power on
</p>

<p>
	Note it likely applies to the Minix NEO U1 as well since it uses the same MCU
</p>
]]></description><guid isPermaLink="false">59241</guid><pubDate>Tue, 21 Apr 2026 01:14:14 +0000</pubDate></item><item><title>Cheapest box with 1000M/1Gbit ethernet + USB 3.0?</title><link>https://forum.armbian.com/topic/57379-cheapest-box-with-1000m1gbit-ethernet-usb-30/</link><description><![CDATA[<p>
	I currently have a X96 Air S905X3 4GB/64GB box that has 1Gbit ethernet and a USB 3.0 port that works well with Armbian.
</p>

<p>
	This was bought 5 years ago for only 35 USD.
</p>

<p>
	 
</p>

<p>
	I would like to find another box for Armbian that also has 1000M/1Gbit ethernet + USB 3.0.
</p>

<p>
	The same or similar boxes are selling for 50-60USD at the moment which is a lot for an old box.
</p>

<p>
	 
</p>

<p>
	Are there any other boxes with 1Gbit ethernet at a low price that work with Armbian?
</p>

<p>
	Not bothered about other features, wifi quality, performance otherwise - just Gbit ethernet and USB 3.
</p>

<p>
	 
</p>

<p>
	Open to all processors - Amlogic, Allwinner, Rockchip etc
</p>
]]></description><guid isPermaLink="false">57379</guid><pubDate>Wed, 14 Jan 2026 17:30:09 +0000</pubDate></item><item><title>Armbian Ethernet not working on Ugoos AM3</title><link>https://forum.armbian.com/topic/59210-armbian-ethernet-not-working-on-ugoos-am3/</link><description><![CDATA[<p>
	Hello.
</p>

<p>
	I'm running <strong>Armbian</strong> on a <strong>Ugoos AM3</strong> TV box. I downloaded the <strong>Armbian_26.05.0_amlogic_s912_bookworm_6.18.20_server_2026.04.01.img.gz </strong>image from <a href="https://github.com/" rel="external nofollow">https://github.com/</a><abbr title="A fork of Armbian that uses Armbian's name without permission."><abbr title="A fork of Armbian that uses Armbian's name without permission.">ophub</abbr></abbr>/amlogic-s9xxx-armbian/releases/download/Armbian_bookworm_arm64_server_2026.04/ Armbian_26.05.0_amlogic_s912_bookworm_6.18.20_server_2026.04.01.img.gz
</p>

<p>
	 
</p>

<p>
	I'm using an <strong>8GB USB flash</strong> drive. I formatted the flash drive to <strong>FAT32</strong>. I burned the image to the flash drive using <strong>Win32 Disk Imager</strong>. After burning the image, I found the <strong>u-boot-s905x-s912.bin</strong> file in the root directory of the flash drive and renamed it to <strong>u-boot.ext</strong>. In the /<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>/amlogic/ directory, I found the <strong>meson-gxm-ugoos-am3.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr></strong> file and edited the path in the <strong>extlinux/extlinux.conf</strong> file in the <strong>FDT</strong> line. The resulting line was:
</p>

<p>
	FDT /<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>/amlogic/meson-gxm-ugoos-am3.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>
</p>

<p>
	I connected a monitor via <strong>HDMI</strong> to the TV box, a network via <strong>Ethernet</strong>, a <strong>USB keyboard</strong>, and inserted a USB flash drive into the TV box. Armbian loaded normally. I followed the steps to create a user and install locales. No network setup messages appeared during setup. After setup and booting, I ran the command as the user
</p>

<p>
	ip a
</p>

<p>
	I saw that the TV Box <strong>hadn't received an IP address</strong>. I tried running the command <strong>sudo systemctl restart NetworkManager </strong>, but the IP address didn't appear. I turned off the TV Box using the command <strong>sudo poweroff</strong>. I disconnected the USB flash drive and booted into the TV Box in <strong>Android</strong> (I'm using a <strong>slimBox</strong>). I checked the network in Android—both <strong>Ethernet and WiFi were working</strong>. I switched the WiFi status in Android to off, and then re-enabled the WiFi. I inserted the USB flash drive with Armbian into the TV Box and booted into Armbian—the <strong>Ethernet network was working</strong>. I tried shutting down the system using the command <strong>sudo poweroff</strong>. I disconnected the TV Box from the power supply. After that, I booted the TV Box into Armbian again—both <strong>Ethernet and WiFi were still not working</strong>.
</p>

<p>
	If I re-enable the network in Android, the Ethernet will work again until the power is cut off. I tried using the <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> files <strong>meson-gxm-q201.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr></strong> and <strong>meson-gxm-q200.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr></strong>, but the Ethernet also doesn't work after a power outage.
</p>

<p>
	My TV box uses an LTM8830 WiFi module and an Amlogic S912 ARM Cortex-A53 processor. RAM is 2 GB.
</p>
]]></description><guid isPermaLink="false">59210</guid><pubDate>Sun, 19 Apr 2026 03:46:41 +0000</pubDate></item><item><title>Anyone tried Armbian on an EVPad 2S?</title><link>https://forum.armbian.com/topic/57369-anyone-tried-armbian-on-an-evpad-2s/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	I know this is a bit of a long shot given the age of the hardware, but I’m wondering if anyone here has ever experimented with running Armbian on an EVPad 2S (the old Android TV box). I’ve been tinkering with some older devices and thought it might be interesting to see if this one can be repurposed.
</p>

<p>
	<br />
	I’ve attached a screenshot of the system info - unfortunately, it’s pretty sparse. The box is running Android 4.4.2 with kernel version 3.4.39, but the processor type is listed as “UNKNOWN,” and I haven’t found much documentation on the chipset or board layout.<br />
	 
</p>

<p>
	so before I dive deeper I wanted to ask:
</p>

<ul>
	<li>
		Has anyone managed to get Armbian (or any Linux distro) running on it?
	</li>
	<li>
		Are there known limitations with the chipset or bootloader that make it a dead end?
	</li>
	<li>
		Any tips, resources, or even “don’t bother” experiences would be appreciated.
	</li>
</ul>

<p>
	 
</p>

<p>
	Thanks in advance for any insights - sometimes these older boxes surprise us, but I realize support may be very limited.
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2026_01/WhatsAppImage2026-01-14at15_55_46.jpeg.f0e79c957f0ae62d433aea9f2212d8ca.jpeg" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="15837" src="https://forum.armbian.com/uploads/monthly_2026_01/WhatsAppImage2026-01-14at15_55_46.thumb.jpeg.6f3d97232d56345ce9ca9e4986c74daf.jpeg" data-ratio="133.21" width="563" class="ipsImage ipsImage_thumbnailed" alt="WhatsApp Image 2026-01-14 at 15.55.46.jpeg"></a></p>]]></description><guid isPermaLink="false">57369</guid><pubDate>Wed, 14 Jan 2026 08:01:24 +0000</pubDate></item><item><title>Support for Realtek RTD1395</title><link>https://forum.armbian.com/topic/31028-support-for-realtek-rtd1395/</link><description><![CDATA[<p>
	I have recently purchased a Linux-based TV box with the following specifications:
</p>

<ul>
	<li>
		Realtek chipset with the code RTD1395PU
	</li>
	<li>
		1 GB of RAM (SEC 149 model)
	</li>
	<li>
		8 GB Flash memory (SCY brand)
	</li>
	<li>
		Operating system: Linux
	</li>
	<li>
		Support for 1 USB, LAN, HDMI
	</li>
</ul>

<p>
	I have tried connecting the UART interface to it and observed the boot process using Putty. What I received was a boot system that I will describe later. The issue I'm facing is that there is very little information on the internet about this CPU model, and the support for it is similarly scarce, as it seems to have been discontinued. I can use ESC/Space to access Uboot in the Realtek&gt; prompt, but the number of supported commands is limited. I can still access USB, and of course, I can't use Ctrl+D to stop this process due to copyright issues. Does anyone have any ideas on how to install Armbian from a USB drive onto its flash memory?
</p>
]]></description><guid isPermaLink="false">31028</guid><pubDate>Fri, 27 Oct 2023 03:53:25 +0000</pubDate></item><item><title>X88 pro 10 reset android</title><link>https://forum.armbian.com/topic/56100-x88-pro-10-reset-android/</link><description><![CDATA[<p>
	I'm trying to download and reinstall android os on an x88 pro 10 to try and get it working. I have downloaded the file and flashed the device several times but cannot get past the boot up screen I have attached a usb keyboard and mouse but no luck.looking for someone i can chat with step by step
</p>
]]></description><guid isPermaLink="false">56100</guid><pubDate>Thu, 06 Nov 2025 04:27:45 +0000</pubDate></item><item><title>Marvell BG4CT</title><link>https://forum.armbian.com/topic/55574-marvell-bg4ct/</link><description><![CDATA[<p>
	Hello, can someone help me with Armbian for this Android box, which seems to have a good configuration for a media center? I would like to know how to flash it and which firmware image I can install on it. Thank you.
</p>

<p>
	BBox 4K Specifications:
</p>

<p>
	Dimensions: 15x15x3.6cm<br />
	<abbr title="System On a Chip"><abbr title="System On a Chip">SoC</abbr></abbr>: Marvell BG4-CT Processor<br />
	RAM: 2 GB<br />
	Internal Memory: 16 GB<br />
	4K – UHD: Ultra HD, for 4 times better image quality<br />
	<abbr title="Device tree source"><abbr title="Device tree source">DTS</abbr></abbr> and Dolby sound with S/PDIF and HDMI audio output<br />
	128 GB TV recorder, to be completed with the media of your choice<br />
	Connectivity: SD card reader / 2 USB 2.0 ports<br />
	Wi-Fi<br />
	Bluetooth
</p>
]]></description><guid isPermaLink="false">55574</guid><pubDate>Tue, 07 Oct 2025 22:04:13 +0000</pubDate></item><item><title>Tips for choosing my first cheap TV box?</title><link>https://forum.armbian.com/topic/29215-tips-for-choosing-my-first-cheap-tv-box/</link><description><![CDATA[<p>
	Hello, it's been months since I've said to myself "<em>I've got to get a cheap TV box, since SBCs are now so expensive and my Raspberry Pi 3 is showing its I/O and memory limits</em>", and I think I'm now finally forced to, because 2 weeks ago my Pi started to show some strange (load/power) issues, and even started to emit a funny burned smell (!!!), slowly with hours of continuous (even if light) uptime. It still works, but I fear that some component is dying, maybe having kept an USB HDD connected for months has fried something: the smell strangely is always coming even after changing <abbr title="Power supply unit">PSU</abbr> and disconnecting the HDD (apart from that, there are now no other connected peripherals except for the microSD), and it appears to come from the micro-USB port section of the board. Point is, I don't trust this thing to keep working 24/7 after this incident, I have to get a new small homeserver.
</p>

<p>
	 
</p>

<p>
	Indeed, I mostly used the Pi as a server these years, and after reading "<em>Status of Armbian on TV Boxes</em>" I think I can at least give a shot at trying to buy a TV box as a Pi substitute for this kind of task. Since today and tomorrow the Amazon Prime Day takes place, and I'm finding some more-decent-than-usual deals (yes, I did check with Keepa, some boxes are really on discount today), I thought I might as well buy now and stop postponing. So, my requirements are about the following, and they seem easy enough to get on today's TV boxes with Android, but I don't know what happens if I was to desire Armbian:
</p>

<ul>
	<li>
		4 GB RAM or more (unlike the Pi's 1 GB)
	</li>
	<li>
		USB 3.0 ports (unlike the Pi's 2.0), to add big additional storage with minimal bottleneck (but maybe we don't rely on an USB-Y cable anymore if connected to a separate <abbr title="Power supply unit">PSU</abbr>...)
	</li>
	<li>
		WiFi, preferably 5 GHz, because I don't have a good place to put the box near my router, and can't have Ethernet cables going from one corner of the room to the opposite...
	</li>
</ul>

<p>
	 
</p>

<p>
	Now, I probably don't really <em>need </em>bare-metal pure Linux, since the majority of the software I have to run can do so in a proot container in Android (in the past I did use an half-broken Android smartphone as a server actually), but I would have to sacrifice Docker (which sometimes is really useful) and also Pi-Hole (since to work it has to bind on a privileged port, and I wouldn't bet on being able to root these Android boxes), so I am at least making an attempt at buying something that can run Armbian.
</p>

<p>
	 
</p>

<p>
	From what I'm gathering from the forum, the best choices are usually Rockchip boxes (most supported), next come those with some Amlogic SoCs (driven by a small community), and lastly there are some Allwinners. However, it's a bit chaotic trying to infer what's the best choice from browsing semi-random threads, and that's why I'm asking any potential TV box expert (now that's hyperspecialization!) what could be the best choice among what I found for an acceptable price (some are on Prime Day discount, some aren't but still have a good price):
</p>

<ul>
	<li>
		<a href="https://www.amazon.it/Quad-core-Cortex-A53-Decoding-Ethernet-Bluetooth/dp/B07K693HSG" rel="external nofollow">X88 Pro 10</a>, <a href="https://www.amazon.it/Android-Quad-Core-Cortex-A53-Support-Ethernet/dp/B0BXWKHDR5" rel="external nofollow">X88 Pro 12</a><span><span>:</span> </span>RK3318 chip, I understood that it's good support-wise (<a href="https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/#comment-122715" rel="">https://forum.armbian.com/topic/26978-<abbr title="Community supported Chip - no official support">csc</abbr>-armbian-for-rk3318rk3328-tv-box-boards/#comment-122715</a>), WiFi works too if I'm reading correctly, but hardware-wise it's kind of crap, wastes energy, and can fail. Oh well, I'll be honest: I know I should be worried, but I don't know how much worried!
	</li>
	<li>
		X88 Pro 13: RK3528, is it a very new <abbr title="System On a Chip">SoC</abbr>? I can't find anything on the forum about it, and so I fear there is no support.
	</li>
	<li>
		<a href="https://www.amazon.it/Magcubic-Android-Smart-S905W2-Supporta/dp/B08K8Y29RL" rel="external nofollow">Magcubic thingy</a>, <a href="https://www.amazon.it/32-Bluetooth-convertitore-supporto-6K/dp/B08SHC95WD" rel="external nofollow">Magcubic 8K Ultra HD</a>, <a href="https://www.amazon.it/Allwinner-Quad-Core-Corter-A53-CPU-Risoluzione-Bluetooth/dp/B0BFHDNZLZ" rel="external nofollow">Tanix thingy</a> (Allwinner H618); <a href="https://www.amazon.it/Android-Amlogic-Supporto-2-4Ghz-Player/dp/B07H3WQVXF" rel="external nofollow">T95H</a>, <a href="https://www.amazon.it/Android-BOX%EF%BC%8CQ-Quad-Core-Supporto-2-4Ghz/dp/B07MF9NGDV" rel="external nofollow">Q Plus</a> (Allwinner H616): It appears these are not well supported, there are some experimental builds around but many things are broken. Would be happy to discover that I'm wrong on this and support is actually good for my standards, though.
	</li>
	<li>
		<p>
			<a href="https://www.amazon.it/TUREWELL-T95-Quad-core-cortex-A55-Dual-Band/dp/B081H6FSNW" rel="external nofollow">TUREWELL T95 Max+</a>: Amlogic S905X3, here I kinda don't understand at all if there's enough good community support or not, but there are many threads about issues and solutions.
		</p>
	</li>
</ul>

<p>
	 
</p>

<p>
	To be clear: I can tinker if something doesn't work out-of-the-box with Armbian, I have a bit of experience with embedded devices like routers or Android smartphones so I think I could solve minor issues if they arise, but I'm really looking for a quick replacement for my Raspi and don't want to spend more than a few days after getting the box to make Armbian work. That's why I'm thinking so hard on getting a device with good compatibility.
</p>

<p>
	 
</p>

<p>
	Anyways, thank you to anyone who comes here to help, I would appreciate it. If no help comes, I think I will bet on a box with the RK3318 and hope for the best.
</p>
]]></description><guid isPermaLink="false">29215</guid><pubDate>Tue, 11 Jul 2023 21:41:12 +0000</pubDate></item><item><title>ssh shell in to HDMI screen output?</title><link>https://forum.armbian.com/topic/52018-ssh-shell-in-to-hdmi-screen-output/</link><description><![CDATA[<p>
	Good day,
</p>

<p>
	I've installed ARMBIAN to my old TV box. It's running fine as I ussually use it headles with a ssh connection to it.
</p>

<p>
	BUT NOW I've attached it to the hdmi TV and I want to remotely use  that HDMI screen w/o local keyboard and mouse.
</p>

<p>
	I don't know how to do that. Please give me a help?
</p>
]]></description><guid isPermaLink="false">52018</guid><pubDate>Mon, 19 May 2025 15:19:26 +0000</pubDate></item><item><title>hate about tvboxes</title><link>https://forum.armbian.com/topic/50689-hate-about-tvboxes/</link><description><![CDATA[<p>
	Sincerally i don't really understand why so many people say bad thing of tvboxes with armbian.. i work daily with tvboxes and sold a few hundreds.. and i used dozens for installing coreelec, libreelec, armbian and home assistant in it and yes, they give a bit more work to set up than some well known boards specifically designed for development builds, but after everything is installed and set up, it's very rare for them to give any issues.. and you pay just a fraction of the cost and have hardware very close to the best recommended boards, and sometimes even better hardware.. what i recommend is using the more known ones and use good sdcards<u>.. sincerally.. stop spreading so much hate for tvboxes..</u>
</p>
]]></description><guid isPermaLink="false">50689</guid><pubDate>Sat, 22 Mar 2025 00:56:57 +0000</pubDate></item><item><title>Help to review: porting Mainline U-boot and Linux to Tmall MagicBox M16S (Amlogic S912-H Tv Box)</title><link>https://forum.armbian.com/topic/22301-help-to-review-porting-mainline-u-boot-and-linux-to-tmall-magicbox-m16s-amlogic-s912-h-tv-box/</link><description><![CDATA[<p>
	<img alt="4IK3KSG2C8NMDBMX2520303NL16NQPD0.jpg.1b62d993a5d18c971c8c2ce690cb9d4a.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="9172" data-ratio="80.00" width="300" src="https://forum.armbian.com/uploads/monthly_2022_07/4IK3KSG2C8NMDBMX2520303NL16NQPD0.jpg.1b62d993a5d18c971c8c2ce690cb9d4a.jpg" />
</p>

<p>
	 
</p>

<p>
	Hw Spec
</p>

<p>
	<abbr title="System On a Chip"><abbr title="System On a Chip">Soc</abbr></abbr>:       Amlogic S912-H, (S192 with dolby, <abbr title="Device tree source"><abbr title="Device tree source">DTS</abbr></abbr>)
</p>

<p>
	Mem:    2G Ddr3
</p>

<p>
	<abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">Emmc</abbr></abbr>: 16G
</p>

<p>
	4K HDMi
</p>

<p>
	AV out
</p>

<p>
	ethernet ??
</p>

<p>
	Wifi/Bt ??
</p>

<p>
	USB port *1
</p>

<p>
	5V DC-IN
</p>

<p>
	IR receiver
</p>

<p>
	Reset hole
</p>

<p>
	OS: Ali YunOS
</p>

<p>
	 
</p>

<p>
	Steps
</p>

<p>
	1, connect UART from mainboard test points, (I can only find M17's UART port)
</p>

<p>
	2, build u-boot follow q200.rst in u-boot doc, use  VIM2 config and use VIM2 fip blobs (hope that works)
</p>

<p>
	3, build Arm64 debian bookworm with default debian kernel to USB driver, and config system.
</p>

<p>
	4, falsh u-boot to USB driver
</p>

<p>
	5, connect to device with UART, hope to stop at u-boot cmdline, and erase <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>. if failed, find other way to erase, maybe Amlogic flash tool.
</p>

<p>
	6, instert USB driver, and reboot device
</p>

<p>
	 
</p>

<p>
	potaintial issues:
</p>

<p>
	can't find UART port on mainboard
</p>

<p>
	VIM2 mainline Uboot can't boot M16S
</p>

<p>
	device does not support boot from USB.
</p>

<p>
	No schematics for next step dev.
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">22301</guid><pubDate>Thu, 07 Jul 2022 08:01:38 +0000</pubDate></item><item><title>Problems with VLC - Chronic Frame Dropping and Tearing</title><link>https://forum.armbian.com/topic/50890-problems-with-vlc-chronic-frame-dropping-and-tearing/</link><description><![CDATA[<p>
	I've been running ARMbian on my "H96 Max" for 36 hrs now, ha
</p>

<p>
	 
</p>

<p>
	in VLC, i have noticed that if i play the 720 in the native default window, and don't maximize it, it plays perfect with no dropped frames, but it still tears now and then !!. it's because the video does not have to be rescaled. So obviously, the problem is that Hardware Decoding will not work with VLC, and that VLC and ARMbian are just not optimized and not up to the job !!. I have heard that with my "H96 Max"ARM and almost any other SoCs, that they can just not handle the task in ARMbian and in general, , , i was suprized to see the 4 CPU's run a 50% !!, i expected it to be no more than 10
</p>

<p>
	 
</p>

<p>
	If you can get it to work 4K on crappy ARM based Android LINUX, then it's not the <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> hardware, , its ARMbian !!
</p>

<p>
	 
</p>

<p>
	So the main problem is that HVA is not fully supported in my Armbian, and SVA is not working as it should, so a problem with ARMbian again, , , I have been a Computer Technician since 1997 and have seen SVA work perfect on a a lot lesser system, , , , ,Hmmmm, , my 4 Core ARM based "4K fire tv stick max" is a joy to use !!, , , will have to look at the look at its ARM SoCs, especially its <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr>
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">50890</guid><pubDate>Thu, 03 Apr 2025 16:34:28 +0000</pubDate></item><item><title>Armbian_community_25.5.0-trunk. on S905 Minix U1 - random eth0 MAK address after every reboot.</title><link>https://forum.armbian.com/topic/50774-armbian_community_2550-trunk-on-s905-minix-u1-random-eth0-mak-address-after-every-reboot/</link><description><![CDATA[<p>
	I've installed and run a/m OS. BUT i have a problem with MAK address changing at every reboot. How to avoid that ? Is it possible to install the OS on the <abbr title="embedded MultiMediaCard">emmc</abbr> instead of SD card?
</p>
]]></description><guid isPermaLink="false">50774</guid><pubDate>Thu, 27 Mar 2025 14:54:19 +0000</pubDate></item><item><title>Arris vip6102w</title><link>https://forum.armbian.com/topic/32551-arris-vip6102w/</link><description><![CDATA[<p>
	Hi guys. I'm just wondering if I can install Linux on it. STB in DEVELOPER mode, I can connect ADB and I see some stuff here:
</p>

<p>
	 
</p>

<p>
	vip6102w:/ $ df -h<br />
	Filesystem            Size  Used Avail Use% Mounted on<br />
	/dev/root             1.9G  917M  1.0G  47% /<br />
	tmpfs                 822M  492K  821M   1% /dev<br />
	tmpfs                 822M  112K  822M   1% /mnt<br />
	/dev/block/dm-1       488M   77M  401M  17% /vendor<br />
	/dev/block/mmcblk1p22 8.8G  1.4G  7.2G  17% /data<br />
	/dev/block/mmcblk1p8  0.9M   34K  970K   4% /dev/hwcfg<br />
	/dev/block/mmcblk1p15 5.6M  120K  5.2M   3% /cache<br />
	/data/media           8.8G  1.4G  7.2G  17% /storage/emulated
</p>

<p>
	 
</p>

<p>
	<br />
	vip6102w:/ $ uname -a<br />
	Linux localhost 4.9.208-1-6pre #1 SMP Fri Aug 28 15:30:05 PDT 2020 armv7l
</p>

<p>
	 
</p>

<p>
	127|vip6102w:/ $ sudo<br />
	/system/bin/sh: sudo: not found
</p>

<p>
	 
</p>

<p>
	vip6102w:/ $ ls<br />
	ls: ./init: Permission denied<br />
	ls: ./metadata: Permission denied<br />
	ls: ./postinstall: Permission denied<br />
	acct       d            init.environ.<abbr title="Release candidate">rc</abbr>           init.usb.configfs.<abbr title="Release candidate">rc</abbr> oem     storage<br />
	bin        data         init.<abbr title="Release candidate">rc</abbr>                   init.usb.<abbr title="Release candidate">rc</abbr>          proc    sys<br />
	bugreports default.prop init.recovery.block.<abbr title="Release candidate">rc</abbr>    init.zygote32.<abbr title="Release candidate">rc</abbr>     product system<br />
	cache      dev          init.recovery.usb.<abbr title="Release candidate">rc</abbr>      lost+found           res     ueventd.<abbr title="Release candidate">rc</abbr><br />
	charger    eio          init.recovery.vip6102w.<abbr title="Release candidate">rc</abbr> mnt                  sbin    vendor<br />
	config     etc          init.recovery.wificfg.<abbr title="Release candidate">rc</abbr>  odm                  sdcard  verity_key
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">32551</guid><pubDate>Thu, 14 Dec 2023 15:41:31 +0000</pubDate></item><item><title>Allwinner H3</title><link>https://forum.armbian.com/topic/31818-allwinner-h3/</link><description><![CDATA[<p>
	Hello everyone, I have a TV Box (as you can see in the photo) and I want to put Linux on it. But I'm having a problem finding a compatible image. The model is from Allwinner H3. And when I go to configure it to place the image, it is starting directly on the tvBox.
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2023_11/photo2.jpg.a637e8aa9c37ae421e69fe92403fd342.jpg" data-fileid="11320" data-fileext="jpg" rel=""><img alt="photo2.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11320" data-ratio="177.73" width="422" src="https://forum.armbian.com/uploads/monthly_2023_11/photo2.thumb.jpg.f869e7bdd57ffc2d22506c43011e2024.jpg" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2023_11/photo.jpg.178d4e036a3dd8136ce6c4d808a1ba12.jpg" data-fileid="11321" data-fileext="jpg" rel=""><img alt="photo.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11321" data-ratio="177.73" width="422" src="https://forum.armbian.com/uploads/monthly_2023_11/photo.thumb.jpg.3043779929216dd9979c6e1d7c3bb66c.jpg" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2023_11/54f67a67-dbe8-45d3-8093-aff58c71c000.jpg.468837b05f84fd85e365b1895ae787aa.jpg" data-fileid="11319" data-fileext="jpg" rel=""><img alt="54f67a67-dbe8-45d3-8093-aff58c71c000.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11319" data-ratio="56.3" width="1000" src="https://forum.armbian.com/uploads/monthly_2023_11/54f67a67-dbe8-45d3-8093-aff58c71c000.thumb.jpg.40d73c0108c6eb8c9392aab46f0f5e04.jpg" /></a>
</p>
]]></description><guid isPermaLink="false">31818</guid><pubDate>Mon, 20 Nov 2023 16:11:03 +0000</pubDate></item><item><title>Cortex-A7 Quad-Core - Mali-400, supports?</title><link>https://forum.armbian.com/topic/47066-cortex-a7-quad-core-mali-400-supports/</link><description><![CDATA[<p>
	Hello, I am about to buy a TV box with the following characteristics, I would love to know if it is compatible to install a distro
</p>

<p>
	 
</p>

<p>
	CPU
</p>

<p>
	Cortex-A7 Quad-Core
</p>

<p>
	 
</p>

<p>
	Procesador gráfico
</p>

<p>
	Mali-400
</p>
]]></description><guid isPermaLink="false">47066</guid><pubDate>Wed, 13 Nov 2024 13:38:16 +0000</pubDate></item><item><title>X96Q pro problem</title><link>https://forum.armbian.com/topic/45032-x96q-pro-problem/</link><description><![CDATA[<p>
	Hello how are you. I have a smart box X96Q PRO. It is not running play store giving error to update and uninstall it.And neither update not uninstall. And not hard rest . Hidden Rest button not work and not connecting PC . Please help me any where bypass button or any point short idea
</p>
]]></description><guid isPermaLink="false">45032</guid><pubDate>Tue, 10 Sep 2024 10:44:26 +0000</pubDate></item><item><title>Linux on MIPS, Broadcom BCM7583</title><link>https://forum.armbian.com/topic/43834-linux-on-mips-broadcom-bcm7583/</link><description><![CDATA[<p>
	Hi all, I have an android TV box lying around and I wanted to install Linux on it. It has a MIPS processor. I tried looking it up but couldn't find much info. I'm relatively new to Linux so any help is appreciated. Thanks
</p>
]]></description><guid isPermaLink="false">43834</guid><pubDate>Fri, 16 Aug 2024 01:30:14 +0000</pubDate></item><item><title>s905x3 vs  rk3566</title><link>https://forum.armbian.com/topic/40213-s905x3-vs-rk3566/</link><description><![CDATA[<p>
	Hi
</p>

<p>
	 
</p>

<p>
	I’m thinking of buying a more powerful TV box, and I see that everyone recommends Rockchip. However, when I look at performance, I notice that the S905X3 has much more power than an RK3566 and is also cheaper. There are comments that development for Amlogic is stalled, but new versions continue to be released from what I can
</p>

<p>
	see. I only want it for setting up a Pi-hole and some Dockerized applications. Am I making a mistake if I go for an S905X3? Currently, I have an S905X, and although it was a bit challenging, it’s working quite well
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">40213</guid><pubDate>Wed, 29 May 2024 07:05:24 +0000</pubDate></item><item><title>make backup image of emmc Rk chip</title><link>https://forum.armbian.com/topic/41070-make-backup-image-of-emmc-rk-chip/</link><description><![CDATA[<p>
	Hi 
</p>

<p>
	i installed an armbian img dirictly to the <abbr title="embedded MultiMediaCard">emmc</abbr>, and i want to make a backup img file of it after installing and config few things on it!
</p>

<p>
	i can't use the "ddbr" command cuz it's already installed directly to the <abbr title="embedded MultiMediaCard">emmc</abbr>.
</p>

<p>
	is there any other way? 
</p>
]]></description><guid isPermaLink="false">41070</guid><pubDate>Wed, 12 Jun 2024 18:31:04 +0000</pubDate></item><item><title>Chips with supported video acceleration</title><link>https://forum.armbian.com/topic/37558-chips-with-supported-video-acceleration/</link><description><![CDATA[<p>
	Hello, I find armbian awesome and my problem is because of the manufacurers. 
</p>

<p>
	I basically want to play accelerated video (because I need 4k).
</p>

<p>
	 
</p>

<p>
	I tried amlogic, but it is not still supported (<a href="https://linux-meson.com/hardware.html" rel="external nofollow">https://linux-meson.com/hardware.html</a>) the status is partial for the chips I tried. I don't what "partial" means but I can hardware decoding.
</p>

<p>
	I also tried allwinner, several chips. In this page <a href="https://linux-sunxi.org/Sunxi-Cedrus" rel="external nofollow">https://linux-sunxi.org/Sunxi-<abbr title="driver for hardware accelerated video de-/encoding">Cedrus</abbr></a> I see that it is supported but I tried with new kernels, old kernels... Nothing worked. I always reach a point that stops me (like segmentation fault when loading sunxi modules, system freeze when using vdpau, compilation errors due incompatibility between version...)
</p>

<p>
	I was thinking of try some rockchip but I think that I will suffer the same pain so this is why I want to ask you guys because I am a bit lost and I am starting to think that everything I try is worthless. 
</p>

<p>
	 
</p>

<p>
	Can someone bring me some light? Any tip about what chips are more "friendly" with video acceleration and, if mainline kernel or not, player to use... All the documentation/posts I found are outdated or incomplete and this is the reason I am writing this post, because I am not able to find more information.
</p>

<p>
	 
</p>

<p>
	I know that the manufacturers does not help and everything we have is due the awesome work of the community. It is complicated stuff. Any kind of information will be very helpful.
</p>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">37558</guid><pubDate>Wed, 17 Apr 2024 11:43:33 +0000</pubDate></item><item><title>Extract DTB files from Android TV BOX</title><link>https://forum.armbian.com/topic/33371-extract-dtb-files-from-android-tv-box/</link><description><![CDATA[<p>
	Is it possible to <strong>extract the <abbr title="Device tree blob">DTB</abbr> file</strong> from a working Android TV BOX?
</p>

<p>
	I'm having fun with a new TV BOX TX3 Mini with Amlogic S905L2B (I was sure to find S905W) and before asking for help I wanted to know if I can recover the <abbr title="Device tree blob">DTB</abbr> file from the Android image that works correctly.
</p>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">33371</guid><pubDate>Tue, 23 Jan 2024 08:48:40 +0000</pubDate></item><item><title>S905X TV box bricked after installing to emmc</title><link>https://forum.armbian.com/topic/33600-s905x-tv-box-bricked-after-installing-to-emmc/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	After running armbian-install on S905x device it stopped booting. USB Burning Tool doesn't recognize the device, nothing.
</p>

<p>
	After connecting to UART it looks like install script has overwritten the original u-boot.
</p>

<p>
	That's the boot log from UART connection without sd card:
</p>

<p>
	 
</p>

<pre class="ipsCode">GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 104174

BL2 Built : 11:58:42, May 27 2017.
gxl gc3c9a84 - xiaobo.gu@droid05

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400
Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000
NOTICE:  BL3-1: v1.0(release):3348978
NOTICE:  BL3-1: Built : 15:44:01, May 12 2017
[BL31]: GXL CPU setup!
mpu_config_enable:ok
[Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
OPS=0x82
8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.359461 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast

&lt;debug_uart&gt;


U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc

Model: Libre Computer AML-S905X-CC
SoC:   Amlogic Meson GXL (S905X) Revision 21:b (82:2)
DRAM:  2 GiB
Core:  169 devices, 27 uclasses, devicetree: separate
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
1:      Armbian
Retrieving file: /uInitrd
** File not found /uInitrd **
Skipping Armbian for failure retrieving initrd
SCRIPT FAILED: continuing...
Found U-Boot script /boot/boot.scr
8147 bytes read in 1 ms (7.8 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: amlogic/meson-gxl-s905x-libretech-cc.dtb
Current variant:
Current fdtfile after armbianEnv: amlogic/meson-gxl-s905x-libretech-cc.dtb
Mainline bootargs: root=/dev/mmcblk1p1 rootwait rootfstype=ext4 splash=verbose c                                                                                                                                     onsole=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ub                                                                                                                                     ootpart=d27dbd06-01 libata.force=noncq usb-storage.quirks=    cgroup_enable=memo                                                                                                                                     ry swapaccount=1
22783841 bytes read in 500 ms (43.5 MiB/s)
27433472 bytes read in 601 ms (43.5 MiB/s)
40228 bytes read in 4 ms (9.6 MiB/s)
Failed to load '/boot/dtb/amlogic/overlay/-fixup.scr'
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    22783777 Bytes = 21.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 7a982000, end 7bf3c721 ... OK
   Loading Device Tree to 000000007a90f000, end 000000007a981fff ... OK
"Synchronous Abort" handler, esr 0x96000004
elr: 00000000010656ec lr : 0000000001055038 (reloc)
elr: 000000007dfb46ec lr : 000000007dfa4038
x0 : e14b4287a666c25d x1 : 000000007dfbc290
x2 : 0000000000000010 x3 : 000000007bf54e10
x4 : 0000000000000000 x5 : e14b4287a666c25d
x6 : 0000000001000000 x7 : 0000000000000000
x8 : 0000000000000007 x9 : 0000000000000000
x10: 0000000000000178 x11: 000000007bf40eec
x12: 00000000000000a4 x13: 000000007bf40ea8
x14: 000000007a90f000 x15: 0000000000000020
x16: 000000007df5946c x17: 0000000000000000
x18: 000000007bf4cdb0 x19: 000000007af41040
x20: 000000007df4fb18 x21: 000000007dfbc290
x22: 0000000000001000 x23: 000000007bf54d60
x24: 000000007dfdacb8 x25: 0000000001000000
x26: 0000000000000000 x27: 0000000001000000
x28: 0000000000001000 x29: 000000007bf40ea0

Code: eb04005f 54000061 52800000 14000006 (386468a3)
Resetting CPU ...

resetting ...
bl31 reboot reason: 0xd
bl31 reboot reason: 0x0
system cmd  1.
</pre>

<p>
	 
</p>

<p>
	And with sd card
</p>

<p>
	 
</p>

<pre class="ipsCode"> GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 103545

BL2 Built : 11:58:42, May 27 2017.
gxl gc3c9a84 - xiaobo.gu@droid05

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400
Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000
NOTICE:  BL3-1: v1.0(release):3348978
NOTICE:  BL3-1: Built : 15:44:01, May 12 2017
[BL31]: GXL CPU setup!
mpu_config_enable:ok
[Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
OPS=0x82
8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.358822 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast

&lt;debug_uart&gt;


U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc

Model: Libre Computer AML-S905X-CC
SoC:   Amlogic Meson GXL (S905X) Revision 21:b (82:2)
DRAM:  2 GiB
Core:  169 devices, 27 uclasses, devicetree: separate
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1:      Armbian
Retrieving file: /uInitrd
Retrieving file: /Image
append: root=UUID=a6cf29bd-49ae-4d3b-bf22-800408ae1fba rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtb/amlogic/meson-gxl-s905x-p212.dtb
Moving Image from 0x8080000 to 0x8200000, end=9cd0000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    22783777 Bytes = 21.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 08008000
   Booting using the fdt blob at 0x8008000
   Loading Ramdisk to 7a982000, end 7bf3c721 ... OK
   Loading Device Tree to 000000007a975000, end 000000007a98169c ... OK
"Synchronous Abort" handler, esr 0x96000004
elr: 00000000010656ec lr : 0000000001055038 (reloc)
elr: 000000007dfb46ec lr : 000000007dfa4038
x0 : e14b4287a666c25d x1 : 000000007dfbc290
x2 : 0000000000000010 x3 : 000000007bf54e10
x4 : 0000000000000000 x5 : e14b4287a666c25d
x6 : 0000000001000000 x7 : 0000000000000000
x8 : 0000000000000007 x9 : 0000000000000000
x10: 0000000000000188 x11: 000000007bf409ec
x12: 00000000000000b4 x13: 000000007bf409a8
x14: 000000007a975000 x15: 0000000000000020
x16: 000000007df7a768 x17: 0000000000000000
x18: 000000007bf4cdb0 x19: 000000007af41040
x20: 000000007df4fb18 x21: 000000007dfbc290
x22: 0000000000001000 x23: 000000007bf54d60
x24: 000000007dfdacb8 x25: 0000000001000000
x26: 0000000000000000 x27: 0000000001000000
x28: 0000000000001000 x29: 000000007bf409a0

Code: eb04005f 54000061 52800000 14000006 (386468a3)
Resetting CPU ...

resetting ...
bl31 reboot reason: 0xd
bl31 reboot reason: 0x0
system cmd  1.
</pre>

<p>
	 
</p>

<p>
	Is there any way to restore original firmware?
</p>
]]></description><guid isPermaLink="false">33600</guid><pubDate>Wed, 31 Jan 2024 21:56:24 +0000</pubDate></item><item><title>How to ID the hardware</title><link>https://forum.armbian.com/topic/33706-how-to-id-the-hardware/</link><description><![CDATA[<p>
	Got a TV Box off amazon.  Not real happy with the features as it comes.  So I thought I'd give a try at booting to Armbian and see how that performs.  I have no idea what the hardware is so I'm not sure where to begin at getting a good bootable SD card set up.  The label on the box just says "TV BOX", nothing that I see to ID the thing.
</p>

<p>
	 
</p>

<p>
	Where do I go to see the info I need to start building a usable boot?
</p>

<p>
	 
</p>

<p>
	This is the device I have:
</p>

<p>
	<a href="https://www.amazon.com/dp/B07MJ13MWD?" rel="external nofollow">https://www.amazon.com/dp/B07MJ13MWD</a>
</p>
]]></description><guid isPermaLink="false">33706</guid><pubDate>Sun, 04 Feb 2024 16:58:36 +0000</pubDate></item><item><title>Why install to emmc?</title><link>https://forum.armbian.com/topic/33675-why-install-to-emmc/</link><description><![CDATA[<p>
	Thanks so much, SteeMan. You are my hero! Messing around with Armbian on TVBox is really fun.
</p>

<p>
	 
</p>

<p>
	I saw you and other people discussed about installing Armbian to the onboard <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>. Is there any advantage for doing that? I mean I have a Samsung EVO 128Gb lying around, which should be faster, roomier than the onboard <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>, shouldn't I use it instead of the 16Gb onboard <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>?
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">33675</guid><pubDate>Sat, 23 Dec 2023 02:58:00 +0000</pubDate></item><item><title>Easyview TV | MXQ Android box</title><link>https://forum.armbian.com/topic/33534-easyview-tv-mxq-android-box/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	  
</p>

<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I have recently found two android TV boxes and am interested in getting Armbian running on them versus the very deprecated Android versions they have. Doing a little research, I've found that they're MXQ EasyView TV models and run on ARM processors similar to my Le Potatoes that I've been playing around with for a few months.
</p>

<p>
	 
</p>

<p>
	I've found their webpage, and it's pretty comical. Unfortunately, they don't list the exact ARM processor and/or specs and just looking up MXQ results in newer models only and Easyview barely anything except the mentioned site.
</p>

<p>
	<a href="https://easyviewtv.com/homepage.html" rel="external nofollow">https://easyviewtv.com/homepage.html</a>
</p>

<p>
	 
</p>

<p>
	Now, there does look like there was a project at one point, but unfortunately it is seemingly cancelled? The websites hosting it are no longer available. I was wondering if anybody came across these and successfully got linux running on them or know of any ways to get them rooted? They'd be fantastic mini-pcs to accompany my Le Potatoes.
</p>

<div class="ipsEmbeddedVideo" contenteditable="false">
	<div>
		<iframe allowfullscreen="" frameborder="0" height="113" src="https://www.youtube-nocookie.com/embed/P5dbQvFwBxc?feature=oembed" title="MXQ AMLOGIC S805 - Running Ubuntu Xenial MATE Linux Desktop - Setup Tutorial" width="200"></iframe>
	</div>
</div>

<p>
	 
</p>
]]></description><guid isPermaLink="false">33534</guid><pubDate>Mon, 29 Jan 2024 15:21:26 +0000</pubDate></item><item><title>Use of SD card or EMMC</title><link>https://forum.armbian.com/topic/32750-use-of-sd-card-or-emmc/</link><description><![CDATA[<p>
	@Steeman: thanks so much for a clear and concise instruction! You are my hero!!!
</p>

<p>
	 
</p>

<p>
	By the way, I just want to check with you. There is no reason to run Armbian on <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> card, rite? Because the sdcard nowadays are much faster &amp; larger than those that are available in the old TV Boxes? Thus there is no advantage to install to the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>?
</p>

<p>
	 
</p>

<p>
	Thanks!
</p>
]]></description><guid isPermaLink="false">32750</guid><pubDate>Thu, 21 Dec 2023 02:49:04 +0000</pubDate></item><item><title>Tanix TX3 Mini (Amlogic S905W) Broadcom WiFi issue</title><link>https://forum.armbian.com/topic/28826-tanix-tx3-mini-amlogic-s905w-broadcom-wifi-issue/</link><description><![CDATA[<p>
	Hello guys!
</p>

<p>
	First of all, i couldn't find a topic about the same problem im having, so, if this is a duplicate, just let me know and i'll delete it
</p>

<p>
	 
</p>

<p>
	So, i just installed Armbian Lunar Edge (Kernel 6.2.9) on my box. The WiFi chip is properly recognized, but the firmware for it won't load<br />
	<br />
	This is the dmesg output 
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">[    8.897269] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    8.898654] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    8.899871] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    8.899910] cfg80211: failed to load regulatory.db
[    8.912366] Adding 988264k swap on /dev/zram0.  Priority:5 extents:1 across:988264k SSFS
[    8.993849] systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch.
[    9.000207] brcmfmac: F1 signature read @0x18000000=0x16044330
[    9.017810] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[    9.019051] usbcore: registered new interface driver brcmfmac
[    9.020401] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.amlogic,p281.bin failed with error -2
[    9.035609] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.clm_blob failed with error -2</span></pre>

<p>
	 
</p>

<p>
	Given that the board is recognized, i dont think its a big deal. Still investigating the problem, but until that, can someone give me some tips on how to solve it?
</p>

<p>
	Thanks in advance!
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	EDIT: I am an advanced user, and intend to give official support for this hardware. A lot of people own similar boxes
</p>
]]></description><guid isPermaLink="false">28826</guid><pubDate>Thu, 15 Jun 2023 13:24:50 +0000</pubDate></item><item><title>Cant read sd card after burn</title><link>https://forum.armbian.com/topic/32334-cant-read-sd-card-after-burn/</link><description><![CDATA[<p>
	Hello, i'm trying to burn with balena etcher but my sd card is unreadable with my macbook at the end of burn. I tested all versions from /armbian/dl/aml-s9xx-box/archive. Is there any instructions to burn? thanks
</p>
]]></description><guid isPermaLink="false">32334</guid><pubDate>Sun, 26 Nov 2023 07:56:11 +0000</pubDate></item><item><title>network bridge:  ethernet to wifi (not a wifi hotspot)</title><link>https://forum.armbian.com/topic/31595-network-bridge-ethernet-to-wifi-not-a-wifi-hotspot/</link><description><![CDATA[<p>
	my box is a H96 pro plus TV box, installed Armbian 23.08.0-trunk Lunar.
</p>

<p>
	was working well stand alone, had ethernet and wifi, I decided make use of this box as a network-bridge
</p>

<p>
	I wanted to connect a 3d printer that only has ethernet to wifi, just to transfer files.
</p>

<p>
	 
</p>

<p>
	so finding instructions on this (reverse network bridge?)  was difficult, some say's it can't be done, found one person said he just did it but was for a <abbr title="Raspberry Pi"><abbr title="Raspberry Pi">rpi</abbr></abbr> I think using dhcpcd. 
</p>

<p>
	but anyways when I installed dhcpcd it removed nmcli and now my wifi is disconnected and ethernet is no longer listed.
</p>

<p>
	still messing with it to see if I can get it back, but I attached the script he gave me that supposedly worked for dhcpcd, if anyone wants to check it out.
</p>

<p>
	is there a way to do it with  nmcli? (network-manager)
</p>

<p>
	has anyone done a network bridge to connect a ethernet device to wifi? 
</p>

<p>
	<a class="ipsAttachLink" data-fileext="sh" data-fileid="11284" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=11284&amp;key=70d0bb2c4d8f7a34be38cacab2209dac" rel="">bridge.sh</a>
</p>
]]></description><guid isPermaLink="false">31595</guid><pubDate>Sun, 12 Nov 2023 15:50:50 +0000</pubDate></item><item><title>install armbian mso9385</title><link>https://forum.armbian.com/topic/31455-install-armbian-mso9385/</link><description><![CDATA[<p>
	can any  install armbian mso9385
</p>
]]></description><guid isPermaLink="false">31455</guid><pubDate>Wed, 08 Nov 2023 04:37:48 +0000</pubDate></item><item><title>Is Brazil a new source for TV Boxes?</title><link>https://forum.armbian.com/topic/31269-is-brazil-a-new-source-for-tv-boxes/</link><description><![CDATA[<p>
	From an article at: <a href="https://torrentfreak.com/brazil-regulator-claims-80-of-pirate-tv-boxes-were-blocked-last-week-231030/" rel="external nofollow">https://torrentfreak.com/brazil-regulator-claims-80-of-pirate-tv-boxes-were-blocked-last-week-231030/</a>
</p>

<p>
	 
</p>

<p>
	"Brazil's telecoms regulator Anatel claims that during an operation last week, it successfully blocked around 80% of pirate 'TV boxes' in the country. Estimates from early 2023 suggest that seven million were active in Brazil."
</p>

<p>
	Maybe they could be re-purposed to run Armbian /s
</p>

<p>
	What's your take on this?
</p>
]]></description><guid isPermaLink="false">31269</guid><pubDate>Fri, 03 Nov 2023 02:08:48 +0000</pubDate></item><item><title>Unable to run Armbian on X96Q Tv box (Allwinner sun50iw9 2GiB RAM)</title><link>https://forum.armbian.com/topic/30913-unable-to-run-armbian-on-x96q-tv-box-allwinner-sun50iw9-2gib-ram/</link><description><![CDATA[<p>
	I tried to write different images from the h6 family, for example: Arabian_23.11.0_allwinner_tanix-tx6_bullseye_5.136_server_2023.10.20.img to my SD and USB drive, however, this does not work.<br />
	If you install the SD card and turn it on, then the red LED lights up on the device and that's it.<br />
	The device simply ignores the USB flash drive and loads android. What could be the problem?
</p>
]]></description><guid isPermaLink="false">30913</guid><pubDate>Sat, 21 Oct 2023 20:29:22 +0000</pubDate></item><item><title>MK808B plus / S805 and 50Hz-Display</title><link>https://forum.armbian.com/topic/30840-mk808b-plus-s805-and-50hz-display/</link><description><![CDATA[<p>
	I have install ARMBIAN 5.37 user-built Ubuntu 16.04.7 <abbr title="Long term support">LTS</abbr> 3.10.99 on a MK808b plus.
</p>

<p>
	 
</p>

<p>
	How can i set the Display-Output to <strong>720p 50Hz</strong> - it is necassary for a special purpuse. The MK808b is only use for this prepared purpuse. So i need the fix Display-output
</p>
]]></description><guid isPermaLink="false">30840</guid><pubDate>Tue, 17 Oct 2023 14:34:26 +0000</pubDate></item><item><title>Replace STB OS/Firmware</title><link>https://forum.armbian.com/topic/30792-replace-stb-osfirmware/</link><description><![CDATA[<p>
	I have ANTIK Set Top Box and want to replace it's original OS/Firmware with any common linux/android (linux preferred), because the original OS is locked &amp; proprietary, and i want to use OS that are more flexible.
</p>

<p>
	<br />
	STB brand : Antik<br />
	machine : b2067<br />
	cpu family : sh4<br />
	cpu variant : st40-300<br />
	cpu type : STxH205
</p>

<p>
	 
</p>

<p>
	Is there any OS/firmware that i can use? or any help/guide on how to do this is much appreciated, Thank you.
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2023_10/ANTIKSTB.jpg.9ad77c49182035932759f7bd9d6d81f0.jpg" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="11164" src="https://forum.armbian.com/uploads/monthly_2023_10/ANTIKSTB.jpg.9ad77c49182035932759f7bd9d6d81f0.jpg" data-ratio="55.79" width="837" class="ipsImage ipsImage_thumbnailed" alt="ANTIK STB.jpg"></a></p>]]></description><guid isPermaLink="false">30792</guid><pubDate>Sun, 15 Oct 2023 16:34:57 +0000</pubDate></item><item><title>Formuler Z series</title><link>https://forum.armbian.com/topic/30595-formuler-z-series/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	I have a formuler z alpha.
</p>

<p>
	I think the <abbr title="Graphic processing unit (3D acceleration)">gpu</abbr> is a ARM Cortex A5 (but not sure)
</p>

<p>
	Some have an ARMBIAN version for booting on USB with this model of CPU ?
</p>

<p>
	 
</p>

<p>
	Thank you
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">30595</guid><pubDate>Fri, 06 Oct 2023 21:14:56 +0000</pubDate></item><item><title>Download armbian for M8C amlogic S802</title><link>https://forum.armbian.com/topic/30506-download-armbian-for-m8c-amlogic-s802/</link><description><![CDATA[<p>
	Hello. I won't be able to find the armbian M8C amlogic S802 download file. I want to try to use it. Thank you in advance.
</p>
]]></description><guid isPermaLink="false">30506</guid><pubDate>Mon, 02 Oct 2023 18:47:42 +0000</pubDate></item><item><title>End 2023: which ARM board with better performance than Raspberry (I want 4K) and good Linux support? Which is the flagship of 2023 for TV box?</title><link>https://forum.armbian.com/topic/30230-end-2023-which-arm-board-with-better-performance-than-raspberry-i-want-4k-and-good-linux-support-which-is-the-flagship-of-2023-for-tv-box/</link><description><![CDATA[<p>
	Hi
</p>

<p>
	 
</p>

<p>
	With a web search and in Kodi wiki I found only outdated info.
</p>

<p>
	 
</p>

<p>
	Which ARM board with much better performance than Raspberry (I want 4K streaming) and good Linux support? Which is the flagship of 2023 for TV box?
</p>

<p>
	 
</p>

<p>
	Installation and setup should be easy, like a x86 PC.
</p>

<p>
	 
</p>

<p>
	I am not yet sure if I run LibreElec or armbian
</p>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">30230</guid><pubDate>Fri, 15 Sep 2023 03:54:27 +0000</pubDate></item><item><title>Hk1 RBI&#x2019;s w2 wifi connectivity issues</title><link>https://forum.armbian.com/topic/29866-hk1-rbi%E2%80%99s-w2-wifi-connectivity-issues/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	 
</p>

<p>
	I have an issue with my hk1 box. I cannot connect to WiFi. I see a lot of networks but when I trying to connect it says “couldn’t find &lt;BSSID&gt;”.
</p>

<p>
	 
</p>

<p>
	Tried to set static &amp; DHCP IP, factory reset the box and rebooted the router. When I use the LAN cable it works. <br />
	 
</p>

<p>
	does anyone have any idea how to further troubleshoot this or have some knowledge or experience?
</p>
]]></description><guid isPermaLink="false">29866</guid><pubDate>Mon, 28 Aug 2023 22:18:00 +0000</pubDate></item><item><title>can a hi3719  processer run armbian software</title><link>https://forum.armbian.com/topic/29362-can-a-hi3719-processer-run-armbian-software/</link><description><![CDATA[<p>
	good day guys i am new here i have a android box that is a huawei model ec6108v8 settop box  using a hi3719 processer is there away to  install armbian on it
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">29362</guid><pubDate>Sun, 23 Jul 2023 15:02:02 +0000</pubDate></item><item><title>Two TV boxes</title><link>https://forum.armbian.com/topic/28996-two-tv-boxes/</link><description><![CDATA[<p>
	AdHi all , I'm new here but have just been given 2 X TV boxes and am hopeful one or both might work for Armbian but I don't know what I've got or where to start to be honest <span class="ipsEmoji">😆</span>.
</p>

<p>
	One box says T8 on top and underneath Smart TV BOX quad core T8 V3 S/N 052014120002441 
</p>

<p>
	This one is in a solid metal case . 
</p>

<p>
	The other is in a square ish plastic shell and on top says M8 underneath says OTT TV BOX Android Player Model : M8
</p>

<p>
	<span>Are either of these suitable please ? </span>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">28996</guid><pubDate>Wed, 28 Jun 2023 12:38:48 +0000</pubDate></item><item><title>Want to Install ARMBIAN on Tronsmart Vega S89 Standard.  Please Help.</title><link>https://forum.armbian.com/topic/28789-want-to-install-armbian-on-tronsmart-vega-s89-standard-please-help/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I Want to Install ARMBIAN on Tronsmart Vega S89 Standard.  
</p>

<p>
	Currently it is on Android Kitkat 4.4.2.
</p>

<p>
	Please Help.
</p>

<p>
	Thanx
</p>
]]></description><guid isPermaLink="false">28789</guid><pubDate>Tue, 13 Jun 2023 07:47:04 +0000</pubDate></item><item><title>Amlogic or Rockchip?</title><link>https://forum.armbian.com/topic/26976-amlogic-or-rockchip/</link><description><![CDATA[<p>
	Considering that this is all community supported as always, Is Armbian nowadays in a better shape on Amlogic or Rockchip tv boxes?
</p>
]]></description><guid isPermaLink="false">26976</guid><pubDate>Thu, 02 Mar 2023 22:00:15 +0000</pubDate></item><item><title>S905 failed to boot from emmc</title><link>https://forum.armbian.com/topic/18902-s905-failed-to-boot-from-emmc/</link><description><![CDATA[<p>
	Hello Armbian team. 1st I would like to thank everyone for your great work.<br />
	I've been using a Minix TV box with Armbian 5.41 (kernel 3.14) for many years. Recently I have decide to try Mr. balbes150 build. The system works perfectly from SD, but after installing to <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> the boot process fails to load OS. I would be thankful if someone could point to the right direction.
</p>

<p>
	 
</p>

<p>
	<u>[1] Hardware:</u>
</p>

<p>
	Minix Neo U1 ... S905, 2GB RAM / 16GB Flash. <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">Emmc</abbr></abbr> is Toshiba THGBMFG7C1LBAIL (AFAIK same as Samsung KLMAG2GEND-B031).
</p>

<p>
	 
</p>

<p>
	[2] Software:<br />
	Armbian_20.10_Arm-64_bullseye_current_5.9.0.img.xz<br />
	Using <abbr title="Device tree blob"><abbr title="Device tree blob">DTB</abbr></abbr>  meson-gxbb-vega-s95-meta.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr><br />
	<br />
	<u>Here is my extlinux.conf:</u><br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">LABEL Armbian
LINUX /zImage
INITRD /uInitrd

FDT /dtb/amlogic/meson-gxbb-vega-s95-meta.dtb
APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0</span></pre>

<p>
	<br />
	To install I run the install-aml-s905-<abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>.sh. The only change I made is to replace u-boot.ext in /boot on SD, and the one installed in <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> (/dev/mmcblk1p1) with the one from Mr. hexdump which has serial support enabled, so I could capture the u-boot process info. Both versions - the one in distro from Mr. balbes150, and the one from Mr. hexdump are the same but the later has the serial enabled. Both version produce the same error.<br />
	<br />
	<u>[3] The problem:</u>
</p>

<p>
	Booting from SD has no problems. The process uses the original Amlogic U-Boot "2015".<br />
	During booting from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr> the Amlogic U-BOOT correctly transitions to the new U-BOOT "2020", but that one fails to load the rest of the system,. This where I need some help.<br />
	<br />
	Here is the serial log og a good boot from SD:<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Boot from SD:
--------------

exit_reason:0x06
set vddee to 0x03e8mv
Enter ddr resume
pub training time: 2630
ddr resume done
store restore gp0 pll
cfg15 3b0d000 
cfg15 63b0d000 
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
no sdio debug board detected 
TE: 71706

BL2 Built : 12:06:06, Jun 13 2016. 
gxb g176ecdb - laiyin.mo@droid12-sz

set vcck to 1100 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 792MHz
DDR0: 1024MB(auto)-2T-11
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK. 
Run bl30...
Load bl31 from eMMC, src: 0x00020000, des: 0x1010[0000, size: 0x00013140
Image: gxb_v1.1.3134-b387442 2016-06-16 14:48:44 yun.cai@droid06]
OPS=0x13
d4 13 d6 d1 28 0 66 3 d 34 7f 3b [0.15Load bl33 from eMMC, src: 0x00034000, des: 0x01000000, size: 0x0006af00
8213 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):c813a61
NOTICE:  BL3-1: Built : 14:47:05, Jun 16 2016
INFO:    BL3-1: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2015.01-00018-g6c5824b-dirty (Oct 12 2017 - 18:36:33)

DRAM:  1 GiB
Relocation Offset is: 36f3b000
register usb cfg[1][0] = 0000000037f96ac0
register usb cfg[0][1] = 0000000037f96ae0
register usb cfg[2][0] = 0000000037f96b00
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
MMC:   SDIO Port C: 0, SDIO Port B: 1
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
[mmc_startup] mmc refix success
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
reboot_mode=watchdog_reboot
hpd_state=1
[1080p60hz] is invalid for cvbs.
set hdmitx VIC = 16
config HPLL = 2970
HPLL: 0xc800023d
config HPLL done
j = 4  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1162]
rx version is 1.4 or below  div=10
Net:   Meson_Ethernet
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 width=5760, height=2160

Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
There is no valid bmp file at the given address
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0 
Device: SDIO Port C
Manufacturer ID: 11
OEM: 100
Name: 016G7 
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 14.7 GiB
mmc clock: 40000000
Bus Width: 8-bit DDR
reading s905_autoscript
537 bytes read in 2 ms (261.7 KiB/s)
## Executing script at 01020000
start amlogic old u-boot
## Error: "bootfromsd" not defined
reading boot_android
** Unable to read file boot_android **
** Bad device usb 0 **
reading u-boot.ext
609247 bytes read in 11 ms (52.8 MiB/s)
## Starting application at 0x01000000 ...
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.9.0-arm-64 (root@vbox) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #20.10 SMP PREEMPT Wed Oct 14 12:04:42 MSK 2020
[    0.000000] Machine model: Tronsmart Vega S95 Pro
[    0.000000] efi: UEFI not found.
[    0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!
[    0.000000] Reserved memory: created CMA memory pool at 0x000000002b400000, size 256 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000001000000-0x000000003f934fff]
[    0.000000] NUMA: NODE_DATA [mem 0x3f72b100-0x3f72cfff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000001000000-0x000000003f934fff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000001000000-0x0000000004ffffff]
[    0.000000]   node   0: [mem 0x0000000007300000-0x000000000fffffff]
[    0.000000]   node   0: [mem 0x0000000010200000-0x000000003f934fff]
[    0.000000] Zeroed struct page in unavailable ranges: 203 pages
[    0.000000] Initmem setup node 0 [mem 0x0000000001000000-0x000000003f934fff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv0.2 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] percpu: Embedded 22 pages/cpu s51480 r8192 d30440 u90112
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: ARM erratum 843419
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 242832
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 666780K/987348K available (16188K kernel code, 1308K rwdata, 6464K rodata, 3392K init, 927K bss, 58424K reserved, 262144K cma-reserved)
[    0.000000] random: get_random_u64 called from cache_random_seq_create+0x80/0x150 with crng_init=0
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] irq_meson_gpio: 133 to 8 gpio interrupt mux initialized
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000003] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.000243] Console: colour dummy device 80x25
[    0.000570] printk: console [tty0] enabled
[    0.000640] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.000656] pid_max: default: 32768 minimum: 301
[    0.000739] LSM: Security Framework initializing
[    0.000817] AppArmor: AppArmor initialized
[    0.000863] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.000881] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.002078] rcu: Hierarchical SRCU implementation.
[    0.002795] EFI services will not be available.
[    0.002955] smp: Bringing up secondary CPUs ...
[    0.003365] Detected VIPT I-cache on CPU1
[    0.003417] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.003812] Detected VIPT I-cache on CPU2
[    0.003839] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.004277] Detected VIPT I-cache on CPU3
[    0.004296] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.004340] smp: Brought up 1 node, 4 CPUs
[    0.004361] SMP: Total of 4 processors activated.
[    0.004369] CPU features: detected: 32-bit EL0 Support
[    0.004378] CPU features: detected: CRC32 instructions
[    0.012620] CPU: All CPU(s) started at EL2
[    0.012669] alternatives: patching kernel code
[    0.013518] devtmpfs: initialized
[    0.017907] Registered cp15_barrier emulation handler
[    0.017933] Registered setend emulation handler
[    0.017944] KASLR disabled due to lack of seed
[    0.018167] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.018189] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.024086] xor: measuring software checksum speed
[    0.064108]    8regs     :  3037.000 MB/sec
[    0.104134]    32regs    :  3486.000 MB/sec
[    0.144166]    arm64_neon:  2957.000 MB/sec
[    0.144174] xor: using function: 32regs (3486.000 MB/sec)
[    0.144223] pinctrl core: initialized pinctrl subsystem
[    0.144681] DMI not present or invalid.
[    0.145064] NET: Registered protocol family 16
[    0.146296] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[    0.146369] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.146450] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.146526] audit: initializing netlink subsys (disabled)
[    0.146655] audit: type=2000 audit(0.144:1): state=initialized audit_enabled=0 res=1
[    0.147474] thermal_sys: Registered thermal governor 'step_wise'
[    0.147670] cpuidle: using governor ladder
[    0.147697] cpuidle: using governor menu
[    0.147958] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.148029] ASID allocator initialised with 65536 entries
[    0.148587] Serial: AMBA PL011 UART driver
[    0.168526] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.168549] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.168559] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.168568] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.169999] cryptd: max_cpu_qlen set to 1000
[    0.240277] raid6: neonx8   gen()  2746 MB/s
[    0.308318] raid6: neonx8   xor()  2058 MB/s
[    0.376360] raid6: neonx4   gen()  2812 MB/s
[    0.444408] raid6: neonx4   xor()  2035 MB/s
[    0.512450] raid6: neonx2   gen()  2666 MB/s
[    0.580495] raid6: neonx2   xor()  1894 MB/s
[    0.648543] raid6: neonx1   gen()  2330 MB/s
[    0.716586] raid6: neonx1   xor()  1599 MB/s
[    0.784631] raid6: int64x8  gen()  1908 MB/s
[    0.852694] raid6: int64x8  xor()  1004 MB/s
[    0.920722] raid6: int64x4  gen()  2126 MB/s
[    0.988772] raid6: int64x4  xor()  1073 MB/s
[    1.056819] raid6: int64x2  gen()  1811 MB/s
[    1.124853] raid6: int64x2  xor()   935 MB/s
[    1.192903] raid6: int64x1  gen()  1354 MB/s
[    1.260941] raid6: int64x1  xor()   716 MB/s
[    1.260949] raid6: using algorithm neonx4 gen() 2812 MB/s
[    1.260956] raid6: .... xor() 2035 MB/s, rmw enabled
[    1.260964] raid6: using neon recovery algorithm
[    1.261389] ACPI: Interpreter disabled.
[    1.261809] HDMI_P5V0: supplied by P5V0
[    1.262590] iommu: Default domain type: Translated 
[    1.262775] vgaarb: loaded
[    1.263237] SCSI subsystem initialized
[    1.263544] usbcore: registered new interface driver usbfs
[    1.263577] usbcore: registered new interface driver hub
[    1.263628] usbcore: registered new device driver usb
[    1.263885] pps_core: LinuxPPS API ver. 1 registered
[    1.263894] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti </span><span class="tag">&lt;giometti</span><span class="pln">@</span><span class="atn">linux</span><span class="pln">.</span><span class="atn">it</span><span class="tag">&gt;</span><span class="pln">
[    1.263913] PTP clock support registered
[    1.263943] EDAC MC: Ver: 3.0.0
[    1.264443] FPGA manager framework
[    1.264509] Advanced Linux Sound Architecture Driver Initialized.
[    1.264937] NetLabel: Initializing
[    1.264946] NetLabel:  domain hash size = 128
[    1.264952] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    1.264997] NetLabel:  unlabeled traffic allowed by default
[    1.265367] clocksource: Switched to clocksource arch_sys_counter
[    1.265556] VFS: Disk quotas dquot_6.6.0
[    1.265600] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.265680] FS-Cache: Loaded
[    1.266087] AppArmor: AppArmor Filesystem Enabled
[    1.266637] pnp: PnP ACPI: disabled
[    1.270756] NET: Registered protocol family 2
[    1.271179] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
[    1.271209] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    1.271263] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    1.271362] TCP: Hash tables configured (established 8192 bind 8192)
[    1.271475] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.271504] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.271635] NET: Registered protocol family 1
[    1.271946] RPC: Registered named UNIX socket transport module.
[    1.271956] RPC: Registered udp transport module.
[    1.271964] RPC: Registered tcp transport module.
[    1.271971] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.271983] NET: Registered protocol family 44
[    1.271996] PCI: CLS 0 bytes, default 64
[    1.272152] Trying to unpack rootfs image as initramfs...
[    1.591979] Freeing initrd memory: 9608K
[    1.592768] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    1.594415] Initialise system trusted keyrings
[    1.594547] workingset: timestamp_bits=44 max_order=18 bucket_order=0
[    1.598396] zbud: loaded
[    1.599443] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.599673] FS-Cache: Netfs 'nfs' registered for caching
[    1.600094] NFS: Registering the id_resolver key type
[    1.600122] Key type id_resolver registered
[    1.600130] Key type id_legacy registered
[    1.600200] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.600211] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.600959] FS-Cache: Netfs 'cifs' registered for caching
[    1.601154] Key type cifs.spnego registered
[    1.601168] Key type cifs.idmap registered
[    1.601180] ntfs: driver 2.1.32 [Flags: R/W].
[    1.601644] JFS: nTxBlock = 7332, nTxLock = 58658
[    1.606689] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
[    1.607912] ocfs2: Registered cluster interface o2cb
[    1.608036] OCFS2 User DLM kernel interface loaded
[    1.609294] gfs2: GFS2 installed
[    1.638756] NET: Registered protocol family 38
[    1.638779] Key type asymmetric registered
[    1.638788] Asymmetric key parser 'x509' registered
[    1.638796] Asymmetric key parser 'pkcs8' registered
[    1.638832] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    1.638943] io scheduler mq-deadline registered
[    1.638952] io scheduler kyber registered
[    1.639041] io scheduler bfq registered
[    1.649796] soc soc0: Amlogic Meson GXBB (S905) Revision 1f:c (13:1) Detected
[    1.652917] Serial: 8250/16550 driver, 5 ports, IRQ sharing enabled
[    1.654366] Serial: AMBA driver
[    1.654679] c11084c0.serial: ttyAML6 at MMIO 0xc11084c0 (irq = 12, base_baud = 1500000) is a meson_uart
[    1.654794] serial serial0: tty port ttyAML6 registered
[    1.655077] c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 15, base_baud = 1500000) is a meson_uart
[    2.723248] printk: console [ttyAML0] enabled
[    2.737247] brd: module loaded
[    2.743064] loop: module loaded
[    2.743720] Loading iSCSI transport class v2.0-870.
[    2.745936] iscsi: registered transport (tcp)
[    2.752547] libphy: Fixed MDIO Bus: probed
[    2.755832] VFIO - User Level meta-driver version: 0.3
[    2.759842] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.765383] ehci-pci: EHCI PCI platform driver
[    2.769780] ehci-platform: EHCI generic platform driver
[    2.775022] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.781064] ohci-pci: OHCI PCI platform driver
[    2.785472] ohci-platform: OHCI generic platform driver
[    2.790966] usbcore: registered new interface driver usb-storage
[    2.796716] mousedev: PS/2 mouse device common for all mice
[    2.802705] i2c /dev entries driver
[    2.808475] sdhci: Secure Digital Host Controller Interface driver
[    2.811677] sdhci: Copyright(c) Pierre Ossman
[    2.816097] Synopsys Designware Multimedia Card Interface Driver
[    2.826042] meson-gx-mmc d0072000.mmc: Got CD GPIO
[    2.853688] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq
[    2.881014] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.881911] ledtrig-cpu: registered to indicate activity on CPUs
[    2.887410] meson-sm: secure-monitor enabled
[    2.891706] hid: raw HID events driver (C) Jiri Kosina
[    2.894108] mmc0: new high speed SDHC card at address aaaa
[    2.896689] usbcore: registered new interface driver usbhid
[    2.902546] mmcblk0: mmc0:aaaa SC16G 14.8 GiB 
[    2.907285] usbhid: USB HID core driver
[    2.916300] platform-mhu c883c404.mailbox: Platform MHU Mailbox registered
[    2.916837]  mmcblk0: p1 p2
[    2.927740] no UART detected at 0x1
[    2.931337] NET: Registered protocol family 17
[    2.933081] Key type dns_resolver registered
[    2.937569] registered taskstats version 1
[    2.941164] Loading compiled-in X.509 certificates
[    2.946021] zswap: loaded using pool lzo/zbud
[    2.950428] Key type ._fscrypt registered
[    2.954192] Key type .fscrypt registered
[    2.958068] Key type fscrypt-provisioning registered
[    2.963580] Btrfs loaded, crc32c=crc32c-generic
[    2.980342] Key type encrypted registered
[    2.980388] AppArmor: AppArmor sha1 policy hashing enabled
[    2.998283] meson-drm d0100000.vpu: Queued 2 outputs on vpu
[    2.998779] meson-drm d0100000.vpu: CVBS Output connector not available
[    3.028822] mmc1: new HS200 MMC card at address 0001
[    3.029424] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[    3.029516] mmcblk1: mmc1:0001 016G70 14.7 GiB 
[    3.038358] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[    3.042757] mmcblk1boot0: mmc1:0001 016G70 partition 1 4.00 MiB
[    3.050951] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
[    3.056395] mmcblk1boot1: mmc1:0001 016G70 partition 2 4.00 MiB
[    3.063966] [drm] Initialized meson 1.0.0 20161109 for d0100000.vpu on minor 0
[    3.069502] mmcblk1rpmb: mmc1:0001 016G70 partition 3 4.00 MiB, chardev (241:0)
[    3.085792]  mmcblk1: p1 p2
[    3.150936] random: fast init done
[    3.386060] Console: switching to colour frame buffer device 210x65
[    3.402543] meson-drm d0100000.vpu: [drm] fb0: mesondrmfb frame buffer device
[    3.410712] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[    3.416180] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[    3.422427] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[    3.428250] meson8b-dwmac c9410000.ethernet: no reset control found
[    3.435138] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[    3.441548] meson8b-dwmac c9410000.ethernet:         DWMAC1000
[    3.446705] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[    3.454120] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[    3.461541] meson8b-dwmac c9410000.ethernet: COE Type 2
[    3.466712] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[    3.473704] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[    3.480136] meson8b-dwmac c9410000.ethernet: Normal descriptors
[    3.485947] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[    3.491728] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    3.499662] meson8b-dwmac c9410000.ethernet: device MAC address 32:b2:a9:c7:f4:e6
[    3.507470] libphy: stmmac: probed
[    3.614802] dwc2 c9000000.usb: supply vusb_d not found, using dummy regulator
[    3.616495] dwc2 c9000000.usb: supply vusb_a not found, using dummy regulator
[    3.624723] phy phy-c0000000.phy.0: USB ID detect failed!
[    3.628827] phy phy-c0000000.phy.0: phy poweron failed --&gt; -22
[    3.634670] ------------[ cut here ]------------
[    3.639175] WARNING: CPU: 0 PID: 34 at drivers/regulator/core.c:2089 _regulator_put.part.0+0x154/0x160
[    3.648391] Modules linked in:
[    3.651413] CPU: 0 PID: 34 Comm: kworker/0:1 Not tainted 5.9.0-arm-64 #20.10
[    3.658396] Hardware name: Tronsmart Vega S95 Pro (DT)
[    3.663494] Workqueue: events deferred_probe_work_func
[    3.668576] pstate: 80000005 (Nzcv daif -PAN -UAO BTYPE=--)
[    3.674095] pc : _regulator_put.part.0+0x154/0x160
[    3.678838] lr : regulator_put+0x38/0x50
[    3.682718] sp : ffff80001014bae0
[    3.685995] x29: ffff80001014bae0 x28: ffff800012a07000 
[    3.691257] x27: ffff80001004bcd8 x26: ffff00003dd528c8 
[    3.696518] x25: ffff800012aeb700 x24: ffff00003ddf2c00 
[    3.701779] x23: 0000000000000008 x22: ffff80001014bbb8 
[    3.707041] x21: ffff00003dd15400 x20: ffff800012ad7150 
[    3.712302] x19: ffff000029e75f00 x18: 0000000000000010 
[    3.717563] x17: 0000000000000001 x16: 0000000000000000 
[    3.722824] x15: 0000000000aaaaaa x14: 0000000000000020 
[    3.728086] x13: 00000000ffffffff x12: ffffffffffffffff 
[    3.733347] x11: 0000000000000040 x10: 0000000000000007 
[    3.738608] x9 : 00000000ffffffff x8 : ffffffffffffffe0 
[    3.743869] x7 : ffffffffffffffff x6 : ffffffffffffffff 
[    3.749131] x5 : 0000000000000000 x4 : 0000000000000000 
[    3.754392] x3 : ffff800012ad7520 x2 : ffff00003dd15400 
[    3.759653] x1 : 0000000000000000 x0 : 0000000000000001 
[    3.764915] Call trace:
[    3.768099]  _regulator_put.part.0+0x154/0x160
[    3.771730]  regulator_put+0x38/0x50
[    3.775267]  regulator_bulk_free+0x38/0x58
[    3.779321]  devm_regulator_bulk_release+0x1c/0x28
[    3.784065]  release_nodes+0x1b0/0x228
[    3.787773]  devres_release_all+0x38/0x60
[    3.791740]  really_probe+0x1d8/0x3b0
[    3.795363]  driver_probe_device+0x58/0xb8
[    3.799416]  __device_attach_driver+0x84/0xc8
[    3.803730]  bus_for_each_drv+0x78/0xc8
[    3.807524]  __device_attach+0xf0/0x150
[    3.811319]  device_initial_probe+0x14/0x20
[    3.815459]  bus_probe_device+0x9c/0xa8
[    3.819255]  deferred_probe_work_func+0x74/0xb0
[    3.823742]  process_one_work+0x1a0/0x328
[    3.827706]  worker_thread+0x1f8/0x420
[    3.831416]  kthread+0x140/0x160
[    3.834608]  ret_from_fork+0x10/0x34
[    3.838142] ---[ end trace 53dcfd993148bc4f ]---
[    3.842869] ------------[ cut here ]------------
[    3.847287] WARNING: CPU: 0 PID: 34 at drivers/regulator/core.c:2089 _regulator_put.part.0+0x154/0x160
[    3.856511] Modules linked in:
[    3.859534] CPU: 0 PID: 34 Comm: kworker/0:1 Tainted: G        W         5.9.0-arm-64 #20.10
[    3.867897] Hardware name: Tronsmart Vega S95 Pro (DT)
[    3.872990] Workqueue: events deferred_probe_work_func
[    3.878076] pstate: 80000005 (Nzcv daif -PAN -UAO BTYPE=--)
[    3.883597] pc : _regulator_put.part.0+0x154/0x160
[    3.888340] lr : regulator_put+0x38/0x50
[    3.892219] sp : ffff80001014bae0
[    3.895497] x29: ffff80001014bae0 x28: ffff800012a07000 
[    3.900758] x27: ffff80001004bcd8 x26: ffff00003dd528c8 
[    3.906019] x25: ffff800012aeb700 x24: ffff00003ddf2c00 
[    3.911281] x23: 0000000000000008 x22: ffff80001014bbb8 
[    3.916542] x21: ffff00003dd15400 x20: ffff800012ad7150 
[    3.921803] x19: ffff000029e75000 x18: 0000000000000010 
[    3.927064] x17: 0000000000000001 x16: 0000000000000000 
[    3.932325] x15: 0000000000000004 x14: 0000000000000020 
[    3.937587] x13: 0000000000000000 x12: ffff00003f0ada38 
[    3.942848] x11: ffff00003f0ad918 x10: ffff00000733b698 
[    3.948109] x9 : ffff00000733b690 x8 : 0000000000000001 
[    3.953370] x7 : 0000000000000001 x6 : ffff00003f058900 
[    3.958632] x5 : ffff00000732c8f8 x4 : 0000000000000000 
[    3.963893] x3 : ffff800012ad7520 x2 : ffff00003dd15400 
[    3.969154] x1 : 0000000000000000 x0 : 0000000000000001 
[    3.974415] Call trace:
[    3.976971]  _regulator_put.part.0+0x154/0x160
[    3.981231]  regulator_put+0x38/0x50
[    3.984768]  regulator_bulk_free+0x38/0x58
[    3.988822]  devm_regulator_bulk_release+0x1c/0x28
[    3.993565]  release_nodes+0x1b0/0x228
[    3.997274]  devres_release_all+0x38/0x60
[    4.001241]  really_probe+0x1d8/0x3b0
[    4.004863]  driver_probe_device+0x58/0xb8
[    4.008917]  __device_attach_driver+0x84/0xc8
[    4.013231]  bus_for_each_drv+0x78/0xc8
[    4.017025]  __device_attach+0xf0/0x150
[    4.020820]  device_initial_probe+0x14/0x20
[    4.024961]  bus_probe_device+0x9c/0xa8
[    4.028756]  deferred_probe_work_func+0x74/0xb0
[    4.033241]  process_one_work+0x1a0/0x328
[    4.037207]  worker_thread+0x1f8/0x420
[    4.040917]  kthread+0x140/0x160
[    4.044109]  ret_from_fork+0x10/0x34
[    4.047642] ---[ end trace 53dcfd993148bc50 ]---
[    4.052391] dwc2: probe of c9000000.usb failed with error -22
[    4.058865] dwc2 c9100000.usb: supply vusb_d not found, using dummy regulator
[    4.065085] dwc2 c9100000.usb: supply vusb_a not found, using dummy regulator
[    4.129604] dwc2 c9100000.usb: DWC OTG Controller
[    4.132332] dwc2 c9100000.usb: new USB bus registered, assigned bus number 1
[    4.138380] dwc2 c9100000.usb: irq 39, io mem 0xc9100000
[    4.143740] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.09
[    4.151807] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.158969] usb usb1: Product: DWC OTG Controller
[    4.163622] usb usb1: Manufacturer: Linux 5.9.0-arm-64 dwc2_hsotg
[    4.169662] usb usb1: SerialNumber: c9100000.usb
[    4.174641] hub 1-0:1.0: USB hub found
[    4.177959] hub 1-0:1.0: 1 port detected
[    4.183835] meson-gx-mmc d0070000.mmc: allocated mmc-pwrseq
[    4.214759] scpi_protocol scpi: SCP Protocol legacy pre-1.0 firmware
[    4.225686] simple-framebuffer 3f935000.framebuffer: framebuffer at 0x3f935000, 0x6baa80 bytes, mapped to 0x(____ptrval____)
[    4.234465] simple-framebuffer 3f935000.framebuffer: format=x8r8g8b8, mode=1680x1050x32, linelength=6720
[    4.244038] simple-framebuffer 3f935000.framebuffer: fb1: simplefb registered!
[    4.253465] printk: console [netcon0] enabled
[    4.257599] netconsole: network logging started
[    4.261865] ALSA device list:
[    4.262870] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[    4.264975]   No soundcards found.
[    4.271289] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    4.280134] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    4.280212] Freeing unused kernel memory: 3392K
[    4.287238] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[    4.287943] Run /init as init process
[    4.371901] mmc2: new high speed SDIO card at address 0001
[    4.577431] usb 1-1: new high-speed USB device number 2 using dwc2
[    4.790899] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=32.98
[    4.800919] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    4.807792] usb 1-1: Product: USB2.0 Hub
[    4.812757] hub 1-1:1.0: USB hub found
[    4.816332] hub 1-1:1.0: 4 ports detected
[    5.248354] EXT4-fs (mmcblk0p2): mounted filesystem with writeback data mode. Opts: data=writeback
[    6.128347] systemd[1]: System time before build time, advancing clock.
[    6.233703] NET: Registered protocol family 10
[    6.265211] Segment Routing with IPv6
[    6.311618] systemd[1]: systemd 246.2-1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    6.338737] systemd[1]: Detected architecture arm64.
[    6.411481] systemd[1]: Set hostname to </span><span class="tag">&lt;arm-64&gt;</span><span class="pln">.
[    6.952530] systemd[1]: Queued start job for default target Graphical Interface.
[    6.959474] random: systemd: uninitialized urandom read (16 bytes read)
[    6.967577] systemd[1]: Created slice system-getty.slice.
[    6.976499] random: systemd: uninitialized urandom read (16 bytes read)
[    6.982608] systemd[1]: Created slice system-modprobe.slice.
[    6.991717] random: systemd: uninitialized urandom read (16 bytes read)
[    6.997905] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    7.008755] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    7.019089] systemd[1]: Created slice User and Session Slice.
[    7.028025] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch when bootsplash is active being skipped.
[    7.040173] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    7.052107] systemd[1]: Condition check resulted in Arbitrary Executable File Formats File System Automount Point being skipped.
[    7.062732] systemd[1]: Reached target Local Encrypted Volumes.
[    7.073296] systemd[1]: Reached target Paths.
[    7.082598] systemd[1]: Reached target Remote File Systems.
[    7.092033] systemd[1]: Reached target Slices.
[    7.101479] systemd[1]: Reached target Swap.
[    7.110943] systemd[1]: Reached target System Time Set.
[    7.120943] systemd[1]: Listening on Syslog Socket.
[    7.130926] systemd[1]: Listening on fsck to fsckd communication Socket.
[    7.141888] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    7.153227] systemd[1]: Listening on Journal Audit Socket.
[    7.163596] systemd[1]: Listening on Journal Socket (/dev/log).
[    7.174266] systemd[1]: Listening on Journal Socket.
[    7.184690] systemd[1]: Listening on udev Control Socket.
[    7.194873] systemd[1]: Listening on udev Kernel Socket.
[    7.208111] systemd[1]: Mounting Huge Pages File System...
[    7.221735] systemd[1]: Mounting POSIX Message Queue File System...
[    7.235892] systemd[1]: Mounting Kernel Debug File System...
[    7.246474] systemd[1]: Condition check resulted in Kernel Trace File System being skipped.
[    7.258577] systemd[1]: Starting Restore / save the current clock...
[    7.273114] systemd[1]: Starting Set the console keyboard layout...
[    7.287363] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    7.300527] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
[    7.312037] systemd[1]: Started Nameserver information manager.
[    7.323459] systemd[1]: Reached target Network (Pre).
[    7.338640] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[    7.350066] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[    7.364266] systemd[1]: Starting Load Kernel Modules...
[    7.378189] systemd[1]: Starting Remount Root and Kernel File Systems...
[    7.393197] systemd[1]: Starting Coldplug All udev Devices...
[    7.408859] systemd[1]: Mounted Huge Pages File System.
[    7.413986] EXT4-fs (mmcblk0p2): re-mounted. Opts: commit=600,errors=remount-ro
[    7.428475] systemd[1]: Mounted POSIX Message Queue File System.
[    7.439127] systemd[1]: Mounted Kernel Debug File System.
[    7.450342] systemd[1]: Finished Restore / save the current clock.
[    7.462559] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    7.479294] systemd[1]: Finished Load Kernel Modules.
[    7.491408] systemd[1]: Finished Remount Root and Kernel File Systems.
[    7.504192] systemd[1]: Condition check resulted in FUSE Control File System being skipped.
[    7.515752] systemd[1]: Mounting Kernel Configuration File System...
[    7.530618] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[    7.538817] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[    7.551243] systemd[1]: Starting Load/Save Random Seed...
[    7.565096] systemd[1]: Starting Apply Kernel Variables...
[    7.579180] systemd[1]: Starting Create System Users...
[    7.594236] systemd[1]: Finished Set the console keyboard layout.
[    7.608111] systemd[1]: Mounted Kernel Configuration File System.

Armbian 20.10 Bullseye ttyAML0


arm-64 login: root
Password: 
    _    ____  __  __        __   _  _   
   / \  |  _ \|  \/  |      / /_ | || |  
  / _ \ | |_) | |\/| |_____| '_ \| || |_ 
 / ___ \|  _ &lt;| |  | |_____| (_) |__   _|
/_/   \_\_| \_\_|  |_|      \___/   |_|  
                                         
Welcome to Armbian 20.10 Bullseye with Linux 5.9.0-arm-64

No end-user support: built from trunk &amp; unsupported (bullseye) userspace!

System load:   2%               Up time:       22 min
Memory usage:  11% of 919M      IP:            192.168.2.121
192.168.2.251 192.168.2.240
CPU temp:      44°C            Usage of /:    11% of 14G    

[ General system configuration (beta): armbian-config ]

root@arm-64:~# shutdown now
[ 1384.266963] reboot: Power down
INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON
bl31 reboot reason: 0xd
bl31 reboot reason: 0xd
system cmd  0.
bl30 get wakeup sources!
process command 00000006
bl30 enter suspend!
store restore gp0 pll
cpu clk suspend rate 1536000000
suspend_counter: 1
Enter ddr suspend
first time suspend
process command 00000001
CEC cfg:0x0000
set vddee to 0x0352mv
0891</span></pre>

<p>
	 
</p>

<p>
	Here is the log of the failed boot from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr>:<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Boot from eMMC:
---------------

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
no sdio debug board detected 
TE: 83807

BL2 Built : 12:06:06, Jun 13 2016. 
gxb g176ecdb - laiyin.mo@droid12-sz

set vcck to 1100 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 792MHz
DDR0: 1024MB(auto)-2T-11
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK. 
Run bl30...
Load bl31 from eMMC, src: 0x00020000, des: 0x1010[000, size: 0x00013140
Image: gxb_v1.1.3134-b387442 2016-06-16 14:48:44 yun.cai@droid06]
OPS=0x13
d4 13 d6 d1 28 0 66 3 d 34 7f 3b [0.17Load bl33 from eMMC, src: 0x00034000, des: 0x01000000, size: 0x0006af00
0236 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):c813a61
NOTICE:  BL3-1: Built : 14:47:05, Jun 16 2016
INFO:    BL3-1: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2015.01-00018-g6c5824b-dirty (Oct 12 2017 - 18:36:33)

DRAM:  1 GiB
Relocation Offset is: 36f3b000
register usb cfg[1][0] = 0000000037f96ac0
register usb cfg[0][1] = 0000000037f96ae0
register usb cfg[2][0] = 0000000037f96b00
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
MMC:   SDIO Port C: 0, SDIO Port B: 1
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
[mmc_startup] mmc refix success
[mmc_init] mmc init success
In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
hpd_state=1
[1080p60hz] is invalid for cvbs.
set hdmitx VIC = 16
config HPLL = 2970
HPLL: 0xc800023d
config HPLL done
j = 4  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1162]
rx version is 1.4 or below  div=10
Net:   Meson_Ethernet
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 width=5760, height=2160

Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
There is no valid bmp file at the given address
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0 
Device: SDIO Port C
Manufacturer ID: 11
OEM: 100
Name: 016G7 
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 14.7 GiB
mmc clock: 40000000
Bus Width: 8-bit DDR
reading s905_autoscript
537 bytes read in 3 ms (174.8 KiB/s)
## Executing script at 01020000
start amlogic old u-boot
## Error: "bootfromsd" not defined
reading boot_android
** Unable to read file boot_android **
** Bad device usb 0 **
reading u-boot.ext
521171 bytes read in 10 ms (49.7 MiB/s)
## Starting application at 0x01000000 ...


U-Boot 2020.07-dirty (Oct 24 2020 - 21:14:30 +0200) hexdump-gxbb

Model: hexdump serial u-boot gxbb
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (13:1)
DRAM:  1 GiB
MMC:   mmc@70000: 0, mmc@72000: 1, mmc@74000: 2
In:    serial@4c0
Out:   serial@4c0
Err:   serial@4c0
Net:   
Warning: ethernet@c9410000 (eth0) using random MAC address - 1a:69:e8:d0:6c:88
eth0: ethernet@c9410000
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc2 is current device
** No partition table - mmc 2 **
Speed: 1000, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10</span></pre>

<p>
	 
</p>

<p>
	Here is some info about /dev/mmcblk1:<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">root@arm-64:~# fdisk -l /dev/mmcblk1
Disk /dev/mmcblk1: 14.68 GiB, 15758000128 bytes, 30777344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8509a0e7

Device         Boot   Start      End  Sectors  Size Id Type
/dev/mmcblk1p1        16384  1196031  1179648  576M  b W95 FAT32
/dev/mmcblk1p2      1196032 15235071 14039040  6.7G 83 Linux


root@arm-64:~# e2label /dev/mmcblk1p2
ROOT_EMMC


root@arm-64:~# ls -1 /dev/mmcblk1*
/dev/mmcblk1
/dev/mmcblk1boot0
/dev/mmcblk1boot1
/dev/mmcblk1p1
/dev/mmcblk1p2
/dev/mmcblk1rpmb


root@arm-64:~# lsblk 
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0  14.8G  0 disk 
├─mmcblk0p1  179:1    0   512M  0 part /boot
└─mmcblk0p2  179:2    0  14.2G  0 part /
mmcblk1      179:32   0  14.7G  0 disk 
├─mmcblk1p1  179:33   0   576M  0 part 
└─mmcblk1p2  179:34   0   6.7G  0 part 
mmcblk1boot0 179:64   0     4M  1 disk 
mmcblk1boot1 179:96   0     4M  1 disk 
zram0        254:0    0    50M  0 disk /var/log
zram1        254:1    0 459.9M  0 disk [SWAP]


root@arm-64:~# mount /dev/mmcblk1p1 /mnt/p1
root@arm-64:~# ls -l /mnt/p1
total 55808
-rwxr-xr-x 1 root root     1536 Sep  4 20:16 armbian_first_run.txt.template
-rwxr-xr-x 1 root root    38518 Sep  4 20:16 boot.bmp
-rwxr-xr-x 1 root root   216810 Sep  4 20:16 config-5.9.0-arm-64
drwxr-xr-x 5 root root     4096 Sep  4 20:16 dtb
-rwxr-xr-x 1 root root      174 Sep  4 20:16 emmc_autoscript
drwxr-xr-x 2 root root     4096 Sep  4 20:16 extlinux
-rwxr-xr-x 1 root root  9882610 Sep  4 20:16 initrd.img-5.9.0-arm-64
-rwxr-xr-x 1 root root      537 Sep  4 20:16 s905_autoscript
-rwxr-xr-x 1 root root  5794743 Sep  4 20:16 System.map-5.9.0-arm-64
-rwxr-xr-x 1 root root   609247 Sep  4 20:16 u-boot.emmc
-rwxr-xr-x 1 root root   609247 Sep  4 20:16 u-boot.ext
-rwxr-xr-x 1 root root   609247 Sep  4 20:16 u-boot-s905
-rwxr-xr-x 1 root root   740080 Sep  4 20:16 u-boot-s905x2-s922
-rwxr-xr-x 1 root root   650183 Sep  4 20:16 u-boot-s905x-s912
-rwxr-xr-x 1 root root  9882674 Sep  4 20:16 uInitrd
-rwxr-xr-x 1 root root 28078592 Sep  4 20:16 zImage


root@arm-64:~# mount /dev/mmcblk1p2 /mnt/p2 
root@arm-64:~# ls -l /mnt/p2
total 80
lrwxrwxrwx  1 root root     7 Aug 30  2020 bin -&gt; usr/bin
drwxr-xr-x  2 root root  4096 Sep  4 20:17 dev
drwxr-xr-x 86 root root  4096 Sep  4 20:18 etc
drwxr-xr-x  3 root root  4096 Sep  3 13:24 home
lrwxrwxrwx  1 root root     7 Aug 30  2020 lib -&gt; usr/lib
drwxr-xr-x  2 root root  4096 Oct 14  2020 lib64
drwx------  2 root root 16384 Sep  4 20:16 lost+found
drwxr-xr-x  2 root root  4096 Sep  4 20:17 media
drwxr-xr-x  2 root root  4096 Sep  4 20:17 mnt
drwxr-xr-x  2 root root  4096 Aug 30  2020 opt
drwxr-xr-x  2 root root  4096 Sep  4 20:17 proc
drwx------  6 root root  4096 Sep  4 20:18 root
drwxr-xr-x  2 root root  4096 Sep  4 20:17 run
lrwxrwxrwx  1 root root     8 Aug 30  2020 sbin -&gt; usr/sbin
drwxrwxr-x  2 root root  4096 Oct 14  2020 selinux
drwxr-xr-x  2 root root  4096 Aug 30  2020 srv
drwxr-xr-x  2 root root  4096 Sep  4 20:17 sys
drwxr-xr-x  2 root root  4096 Sep  4 20:17 tmp
drwxr-xr-x 11 root root  4096 Aug 30  2020 usr
drwxr-xr-x 12 root root  4096 Oct 14  2020 var</span></pre>

<p>
	 
</p>

<p>
	I apologize if this is not the correct forum for this. Pls let me know and will move it.
</p>

<p>
	Thank you,
</p>

<p>
	Pista
</p>
]]></description><guid isPermaLink="false">18902</guid><pubDate>Sat, 04 Sep 2021 20:20:02 +0000</pubDate></item><item><title>Beelink GT1 Mini TV Box - DTB file?</title><link>https://forum.armbian.com/topic/17429-beelink-gt1-mini-tv-box-dtb-file/</link><description><![CDATA[<p>
	Hello all,
</p>

<p>
	 
</p>

<p>
	I need some help.
</p>

<p>
	I have a Beelink GT1 Mini TV Box 64GB Gigabit Lan 4 GB Ram.
</p>

<p>
	 
</p>

<p>
	I use this stock firmware: v007P0 stock firmware LPDDR4 version <strong>(SN: 95X2)</strong> for Beelink GT1 Mini TV Box from here.<br />
	<a href="https://beelink-my.sharepoint.com/:u:/g/personal/firmwareservice_beelink_onmicrosoft_com/EQ8GFfRPJopFoKLfJt71qyMB7ZuofgTb_L3_VW3CHO2g2g?e=Hq70yf" rel="external nofollow">https://beelink-my.sharepoint.com/:u:/g/personal/firmwareservice_beelink_onmicrosoft_com/EQ8GFfRPJopFoKLfJt71qyMB7ZuofgTb_L3_VW3CHO2g2g?e=Hq70yf</a><br />
	<a href="https://chinagadgetsreviews.com/download-android-pie-9-v007p0-stock-firmware-for-beelink-gt1-mini-tv-box.html" rel="external nofollow">https://chinagadgetsreviews.com/download-android-pie-9-v007p0-stock-firmware-for-beelink-gt1-mini-tv-box.html</a>
</p>

<p>
	 
</p>

<p>
	I am trying to flash Armbian_20.10_Arm-64_buster_current_5.9.0.img.xz using the <strong>meson-g12a-gt1-mini-a </strong>but I get the error here-below:
</p>

<p>
	I have tried all other <strong>meson-g12a</strong> with same result
</p>

<p>
	Is it because it has LPDDR4 instead of DDR4 ?
</p>

<p>
	Anything I can do to make it work??
</p>

<pre class="ipsCode prettyprint lang-c prettyprinted">
<span class="typ">Supported</span><span class="pln"> API</span><span class="pun">:</span><span class="pln"> </span><span class="lit">3</span><span class="pln">
charge_status </span><span class="lit">2</span><span class="pun">,</span><span class="pln"> charged </span><span class="lit">1</span><span class="pun">,</span><span class="pln"> status SUCCAESS</span><span class="pun">,</span><span class="pln"> capacity </span><span class="lit">100</span><span class="pln">
</span><span class="typ">Finding</span><span class="pln"> update package
</span><span class="typ">Opening</span><span class="pln"> update package
E</span><span class="pun">:</span><span class="pln"> </span><span class="typ">Block</span><span class="pln"> </span><span class="typ">map</span><span class="pln"> file too </span><span class="kwd">short</span><span class="pun">:</span><span class="pln"> </span><span class="lit">3</span><span class="pln">
E</span><span class="pun">:</span><span class="pln"> </span><span class="typ">Map</span><span class="pln"> of </span><span class="str">'@/cache/recovery/block.map'</span><span class="pln"> failed
E</span><span class="pun">:</span><span class="pln"> failed to </span><span class="typ">map</span><span class="pln"> file
</span><span class="typ">Installation</span><span class="pln"> aborted</span></pre>

<p>
	 
</p>

<p>
	Thanks a lot in advance for your help,
</p>

<p>
	 
</p>

<p>
	MoA,
</p>

<p>
	 
</p>

<p>
	Cheers,
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">17429</guid><pubDate>Mon, 05 Apr 2021 08:10:27 +0000</pubDate></item><item><title>how to change kernel amlogic tvbox</title><link>https://forum.armbian.com/topic/26510-how-to-change-kernel-amlogic-tvbox/</link><description><![CDATA[<p>
	dear friend,
</p>

<p>
	im just burn and run armbian firmware on my tvbox.
</p>

<p>
	the firmware from <abbr title="A fork of Armbian that uses Armbian's name without permission.">ophub</abbr>,and i want to change kernel,but a dont know how to change it.
</p>

<p>
	the kernel file contains boot.tar.gz, <abbr title="Device tree blob">dtb</abbr>.tar.gz, modules.tar.gz, header.tar.gz.
</p>

<p>
	i try upload in root folder and run armbian-update,but not work.
</p>

<p>
	thanks b4
</p>
]]></description><guid isPermaLink="false">26510</guid><pubDate>Wed, 08 Feb 2023 05:44:15 +0000</pubDate></item><item><title>Clone eMMC to MicroSD</title><link>https://forum.armbian.com/topic/26297-clone-emmc-to-microsd/</link><description><![CDATA[<p>
	I couldn't find anything on the web, I looked everywhere.<br />
	With the dd command I can of course create a complete image of the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> anywhere, even on a network path, but I can't find anything that allows me to do what the "<abbr title="A type of flash memory"><abbr title="A type of flash memory">nand</abbr></abbr>-sata-install.sh" script does, which formats the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> and populates it with all the contents of the MicroSD, appropriately adapting some files needed for booting.<br />
	It would be many useful to be able to do the exact opposite as well, i.e. clone <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> to MicroSD, which would be useful to have a bootable backup with all the customizations performed on the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>, without having to go through the process of creating an image file.<br />
	I tried modifying the script to do this but could not do it, there is actually an option already there to do this but it doesn't work for me.<br />
	Surely there is someone better than me, I hope, who maybe has already done this.
</p>

<p>
	<a class="ipsAttachLink" data-fileext="sh" data-fileid="9934" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=9934&amp;key=e1033421dae66366e9acf722782b23a1" rel=""><abbr title="A type of flash memory"><abbr title="A type of flash memory">nand</abbr></abbr>-sata-install.sh</a>
</p>
]]></description><guid isPermaLink="false">26297</guid><pubDate>Sat, 28 Jan 2023 10:38:58 +0000</pubDate></item><item><title>Can not boot Armbian from SD Card of X96 Air</title><link>https://forum.armbian.com/topic/25500-can-not-boot-armbian-from-sd-card-of-x96-air/</link><description><![CDATA[<p>
	I have an X96 Air (version with chip wifi RTL8822CS). I installed Amrbian (via flash to SD Card) and run some months, next I install Armbian from SD Card to <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> and run next some months.<br />
	But in a day, it bricked, nothing in screen. And I have to flash stock rom (X96AIR_Q100_20210126-1140.img) via USB Burning Tool. Then my X96 is survive again, I can use it as a TVBox.<br />
	But I try to plug SD Card with many images/versions of Armbian and with/without press reset, it can not boot from SD Card, it still boots to Android TVBox GUI. I try to flash Amrbian to USB stick, try each of three usb ports, it's still impossible boot to Armbian.
</p>

<p>
	So how I have to do now ?
</p>
]]></description><guid isPermaLink="false">25500</guid><pubDate>Sun, 01 Jan 2023 14:40:27 +0000</pubDate></item><item><title>[Experimental] RTL8822CS Driver</title><link>https://forum.armbian.com/topic/25247-experimental-rtl8822cs-driver/</link><description><![CDATA[<p>
	So, im trying to fix the <a href="https://github.com/chewitt/RTL8822CS" rel="external nofollow">RTL8822CS from chewitt</a> by myself now its wo<abbr title="Rockchip">rk</abbr> with kernel 6.0.15
</p>

<p>
	 <img alt="Screenshot-20221224-064211.png" class="ipsImage" data-ratio="60.09" height="384" width="639" src="https://i.ibb.co/qBLGkDq/Screenshot-20221224-064211.png" />
</p>

<p>
	 
</p>

<p>
	yeah its looks ugly &amp; messy, but its wo<abbr title="Rockchip">rk</abbr>s
</p>

<p>
	<img alt="Screenshot-20221224-064809.png" class="ipsImage" data-ratio="39.22" height="251" width="640" src="https://i.ibb.co/f4dP5hm/Screenshot-20221224-064809.png" />
</p>

<p>
	 
</p>

<p>
	If you want to try the driver just tell me....
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">25247</guid><pubDate>Sat, 24 Dec 2022 11:55:19 +0000</pubDate></item><item><title>TV box with 5GHz WiFi that can run Armbian</title><link>https://forum.armbian.com/topic/24891-tv-box-with-5ghz-wifi-that-can-run-armbian/</link><description><![CDATA[<p>
	Is there an Android TV box that can successfully run Armbian?
</p>

<p>
	 
</p>

<p>
	I got two boxes on the hopes that it would wo<abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr> but I failed in my efforts so far
</p>

<p>
	 
</p>

<p>
	1. X98: I found out that Linux kernel doesn't have the .<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> files for this box so it won't wo<abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr> for now. Maybe I can derive it from S905W but I haven't tried it yet.
</p>

<p>
	 
</p>

<p>
	2. X96-Air: I could run Armbian [1] on the SD card but when I tried to install it on the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>, it stopped booting altogether. Now it won't even boot with SD card inserted.
</p>

<p>
	 
</p>

<p>
	Is there an Android box which supports 5GHz wifi that can definitely run Armbian? Thanks!
</p>

<p>
	 
</p>

<p>
	[1]: I used a release from<abbr> <em>a person that uses Armbian's name without permission and wastes Armbian's ressou<abbr title="Release candidate">rc</abbr>es by sending their users to Armbian for support.</em></abbr>
</p>
]]></description><guid isPermaLink="false">24891</guid><pubDate>Wed, 07 Dec 2022 05:14:56 +0000</pubDate></item><item><title>How to get a working LED/VFD front display on Tanix TX3 mini-A?</title><link>https://forum.armbian.com/topic/24888-how-to-get-a-working-ledvfd-front-display-on-tanix-tx3-mini-a/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	Since I'm less than a n<abbr title="Out Of the Box">oob</abbr> in linux, can anyone please help me with the commands that I need to execute the following instructions?
</p>

<p>
	 
</p>

<p>
	Thanks in advance.
</p>

<p>
	 
</p>

<p>
	Instructions:
</p>

<p>
	 
</p>

<p>
	1. Install the <abbr title="Device tree blob">dtb</abbr> file meson-gxl-s905w-tx3-mini-vfd.<abbr title="Device tree blob">dtb</abbr>.gz and boot your tx3 box with this file. (This assumes that you boot from SD/USB so that you don't risk bricking your box.)
</p>

<p>
	 
</p>

<p>
	2. Download the vfd code (module and daemon) tarball vfdd-20181209.tar.xz from a link at the bottom of the page http://www.rvq.fr/linux/tanix-vfd.php and unpack it someplace on your tx3 box.
</p>

<p>
	 
</p>

<p>
	3. Build the vfd module (natively): Install the *.deb package from Balbes/Armbian with linux kernel headers for the kernel you are running. Then, copy the contents of vfdd-20181209/vfdmod/vfdmod/ to some place in the kernel headers tree, say drivers/vfd Go to drivers/vfd and write up a Makefile somewhat like this;
</p>

<p>
	 
</p>

<p>
	    KERNEL_SOU<abbr title="Release candidate">RC</abbr>E := /usr/s<abbr title="Release candidate">rc</abbr>/linux-headers-4.19.7-aml-s9xxx<br />
	    PWD := $(shell pwd)<br />
	    default:<br />
	        ${MAKE} -C ${KERNEL_SOU<abbr title="Release candidate">RC</abbr>E} M=${PWD} modules<br />
	    clean:<br />
	        ${MAKE} -C ${KERNEL_SOU<abbr title="Release candidate">RC</abbr>E} M=${PWD} clean
</p>

<p>
	 
</p>

<p>
	   Run 'make' and build the module vfdmod.ko
</p>

<p>
	 
</p>

<p>
	4. Check that the module loads: insmod vfdmod.ko
</p>

<p>
	 
</p>

<p>
	5. Build the daemon vfdd: Go to the directory vfdd-20181209/ and run make. The daemon executable vfdd should emerge. After inspection/editing of the Makefile in vfdd-20181209/ (e.g. BINDIR, ETCDIR) you can run 'make install' to copy the the daemon executable and configuration file to their proper locations (or do this manually).
</p>

<p>
	 
</p>

<p>
	6. Test the daemon: Check the vfd conf file (default /etc/vfd.conf) and edit according to taste, or leave as-is. Start the daemon with recipe as in vfdd-20181209/vfdd.runit.in If everything is OK some nice little numbers and symbols should now emerge on the front LED display of your tx3 box.
</p>

<p>
	 
</p>

<p>
	Note:
</p>

<p>
	 
</p>

<p>
	The <abbr title="Device tree blob">dtb</abbr> file meson-gxl-s905w-tx3-mini-vfd.<abbr title="Device tree blob">dtb</abbr> (md5sum is fe846c5c3c7903b15c0725c2bd289fe5) is an augmentation of the Balbes/Armbian file meson-gxl-s905w-tx3-mini.<abbr title="Device tree blob">dtb</abbr> where the following definition has been added/compiled in (method; hack to Balbes' Armbian cross compile build environment) to support vfd (as per recipe in vfdd-20181209):
</p>

<p>
	 
</p>

<p>
	    meson-vfd {<br />
	        compatible = "amlogic,aml_vfd";<br />
	        dev_name = "meson-vfd";<br />
	        status = "okay";<br />
	        <abbr title="General purpose input/output">gpio</abbr>s = &lt;&amp;<abbr title="General purpose input/output">gpio</abbr>_ao <abbr title="General purpose input/output">GPIO</abbr>AO_4  <abbr title="General purpose input/output">GPIO</abbr>_ACTIVE_HIGH&gt;,  /* STB */<br />
	            &lt;&amp;<abbr title="General purpose input/output">gpio</abbr> <abbr title="General purpose input/output">GPIO</abbr>DV_27 <abbr title="General purpose input/output">GPIO</abbr>_ACTIVE_HIGH&gt;,  /* CLK */<br />
	            &lt;&amp;<abbr title="General purpose input/output">gpio</abbr> <abbr title="General purpose input/output">GPIO</abbr>DV_26 <abbr title="General purpose input/output">GPIO</abbr>_ACTIVE_HIGH&gt;;  /* DI/DO */<br />
	    };
</p>

<p>
	 
</p>

<p>
	   (A <abbr title="Device tree blob">dtb</abbr> file can easily be decompiled and inspected by decompiling it with <abbr title="Device tree compiler">dtc</abbr>, the device tree compiler.)
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">24888</guid><pubDate>Wed, 07 Dec 2022 04:29:23 +0000</pubDate></item><item><title><![CDATA[chromium browser slowness & crashing in amlogic x96max+ linux tv box]]></title><link>https://forum.armbian.com/topic/24460-chromium-browser-slowness-crashing-in-amlogic-x96max-linux-tv-box/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I have installed latest armbian linux OS into amlogix x96 max+ (S905X3) device.
</p>

<p>
	(op-hub link here)
</p>

<p>
	Would like to run chromium browser and play youtube videos etc., but I see videos are lagging, experiencing slowness and mostly it got crashed.
</p>

<p>
	 
</p>

<p>
	Here is the command I used to run.
</p>

<p>
	<em>chromium-browser --disable-software-rasterizer --disable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-driver-bug-workarounds --disable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-driver-workarounds --disable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-vsync --disable-features=UseOzonePlatform --disable-reading-from-canvas --enable-accelerated-2d-canvas --enable-accelerated-video-decode --enable-accelerated-mjpeg-decode --enable-features=VaapiVideoEncoder,VaapiVideoDecoder,CanvasOopRasterization --enable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-compositing --enable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-rasterization --enable-oop-rasterization --enable-raw-draw --enable-zero-copy --ignore-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-blocklist --use-gl=desktop --num-raster-threads=6</em>
</p>

<p>
	 
</p>

<p>
	<u><strong>Logs:</strong></u>
</p>

<p>
	<em>[13757:13757:1115/170432.940814:ERROR:vaapi_wrapper.cc(3127)] Failed to initialize VAAPI libs<br />
	[13757:13757:1115/170432.962938:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is desktop, ANGLE is <br />
	[13757:13757:1115/170433.003383:ERROR:gl_angle_util_vulkan.cc(17)] Failed to retrieve EGLDisplay<br />
	[13757:13757:1115/170433.003690:ERROR:vulkan_instance.cc(91)] Failed to get vkGetInstanceProcAddr pointer from ANGLE.<br />
	MESA-LOADER: failed to retrieve device information<br />
	MESA-LOADER: failed to retrieve device information<br />
	MESA-LOADER: failed to retrieve device information<br />
	MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)<br />
	failed to load driver: kms_swrast<br />
	MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)<br />
	failed to load swrast driver</em>
</p>

<p>
	 
</p>

<p>
	If I run with sudo, I won't get 'cannot open shared object fil' error but still experiencing the same.
</p>

<p>
	Could you please share some insights on this ?
</p>

<p>
	 
</p>

<p>
	version details in chrome -&gt; <a href="https://ibb.co/TBBwTHN" rel="external nofollow">https://ibb.co/TBBwTHN</a>
</p>

<p>
	<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr> in chrome -&gt; <a href="https://ibb.co/Tmzp86c" rel="external nofollow">https://ibb.co/Tmzp86c</a>
</p>
]]></description><guid isPermaLink="false">24460</guid><pubDate>Wed, 16 Nov 2022 19:46:50 +0000</pubDate></item><item><title>HopToDesk for Armbian on Android TV box</title><link>https://forum.armbian.com/topic/23671-hoptodesk-for-armbian-on-android-tv-box/</link><description><![CDATA[<p>
	We are developing an open source TeamViewer alternative called HopToDesk, it is built for ARM and runs on <abbr title="Raspberry Pi">RPI</abbr> and may work on other ARM-based devices, we hope to find some help testing on Banana Pi or Android TV devices. If anyone could provide us some feedback or point us in the right direction, it would be great.
</p>
]]></description><guid isPermaLink="false">23671</guid><pubDate>Tue, 27 Sep 2022 10:58:37 +0000</pubDate></item><item><title>How to upgrade to Jammy</title><link>https://forum.armbian.com/topic/23618-how-to-upgrade-to-jammy/</link><description><![CDATA[<p>
	sir i installed "Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img"
</p>

<p>
	its working perfectly but i want to upgrade current version of 2022
</p>

<p>
	<strong>version JEMMY </strong>please any one guide me to upgrade from terminal
</p>
]]></description><guid isPermaLink="false">23618</guid><pubDate>Thu, 22 Sep 2022 14:42:34 +0000</pubDate></item><item><title>minix-neo-x8-h-plus dtb file</title><link>https://forum.armbian.com/topic/23494-minix-neo-x8-h-plus-dtb-file/</link><description><![CDATA[<p>
	i have the minix-neo-x8-h-plus running with armbian 21.02.0 bulsseye
</p>

<p>
	when i use the meson8-minix-neo-x8.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> the machine is not booting
</p>

<p>
	when i use meson8m2-mxiii-plus.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>  the machine is running 
</p>

<p>
	accept wifi and <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>. 
</p>

<p>
	 
</p>

<p>
	is there anybody with the correct <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> file for me
</p>
]]></description><guid isPermaLink="false">23494</guid><pubDate>Mon, 12 Sep 2022 18:09:45 +0000</pubDate></item><item><title>Newbie, advice requested, which Android TV box under $30 is good starter?</title><link>https://forum.armbian.com/topic/16736-newbie-advice-requested-which-android-tv-box-under-30-is-good-starter/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I am new to this site, so far I have not been able to find a newbie list of what type of hardware to start with.
</p>

<p>
	I do not have any device yet.
</p>

<p>
	I have been looking at the android tv boxes on amazon, and I want to start with a $30 box, to be able to load linux on it, and have a graphical interface (ie like a Gnome/KDE desktop view) and then be able to install a vnc server, so the device can be controlled remotely.
</p>

<p>
	 
</p>

<p>
	I have two projects in mind:
</p>

<p>
	1. a chromium based browser install, for viewing webpages and playing any videos embedded in those webpages.
</p>

<p>
	2. later on,  perhaps with different more robust hardware?, add the capacity to install a media player type interface, ie Kodi, so my elderly parents could watch home movies, or view photos, and listen to their aac music. The vnc desire/requirement is so that I could connect over the internet and upload new content to their storage device, and assist them with any problems they were having.
</p>

<p>
	 
</p>

<p>
	If this forum has a topic that you can point me to, to understand what types of device I should start looking at, without getting too overwhelmed for a newbie, I would appreciate it.
</p>

<p>
	 
</p>

<p>
	Otherwise, if you know of an Android tv box in the $30 price range that will work for project #1, please recommend it in the reply.
</p>

<p>
	and if you also have recommendations for project #2, i.e. what type of hardware device upgrade should I consider for movie playback (it is not 4k, even 720 or 1080 is good enough), I would also appreciate that, or even your commentary if there is no hardware upgrade needed.
</p>

<p>
	 
</p>

<p>
	Thank you.
</p>
]]></description><guid isPermaLink="false">16736</guid><pubDate>Sun, 10 Jan 2021 21:23:48 +0000</pubDate></item><item><title>S912 Image</title><link>https://forum.armbian.com/topic/19236-s912-image/</link><description><![CDATA[<p>
	What is the latest image available for tv box?
</p>

<p>
	 
</p>

<p>
	I run on my tv box pre compiled debian image bullseye with kernel 5.9 but I have problem with video decode on motioneye.
</p>

<p>
	 
</p>

<p>
	Exist new image with best support for meson <abbr title="Video processing unit (encoding/decoding)">vpu</abbr>/<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>?
</p>
]]></description><guid isPermaLink="false">19236</guid><pubDate>Tue, 09 Nov 2021 13:37:45 +0000</pubDate></item><item><title>Which PC, Mac or Raspberry allows me to virtualize Armbian image?</title><link>https://forum.armbian.com/topic/22972-which-pc-mac-or-raspberry-allows-me-to-virtualize-armbian-image/</link><description><![CDATA[<p>
	I want to virtualize Armbian images created for TV Box. Which computers allow me to do this? Laptop with snapdragon? Mac Mini M1 or M2 (Apple Silicon)? Any Raspberry model? And what virtualization apps to use: QEMU, VirtualBox, VMware, Parallels?
</p>
]]></description><guid isPermaLink="false">22972</guid><pubDate>Wed, 17 Aug 2022 23:09:52 +0000</pubDate></item><item><title>Trying to learn more about u-boot for amlogic devices.</title><link>https://forum.armbian.com/topic/19004-trying-to-learn-more-about-u-boot-for-amlogic-devices/</link><description><![CDATA[<p>
	@SteeMan i want to learn how to compile u-boot from source and use it like balbes did in his armbian boot directory.like how to build the u-boot.ext, boot.ini, aml_autoscript and soo on
</p>
]]></description><guid isPermaLink="false">19004</guid><pubDate>Sun, 26 Sep 2021 05:46:43 +0000</pubDate></item><item><title>Tivion B1100 Smart TV Box</title><link>https://forum.armbian.com/topic/22302-tivion-b1100-smart-tv-box/</link><description><![CDATA[<p>
	HI 
</p>

<p>
	There is Tivion B1100 Smart TV Box, HiSilicon Hi3716C (ARM Cortex A9), 1 ГГц, which Armbian image is suitable for this device and which one to specify <strong><abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr></strong>?
</p>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">22302</guid><pubDate>Thu, 07 Jul 2022 08:20:39 +0000</pubDate></item><item><title>Need help identifying Android TV Box, selecting boot device</title><link>https://forum.armbian.com/topic/21163-need-help-identifying-android-tv-box-selecting-boot-device/</link><description><![CDATA[<p>
	Hey all, trying to throw a Linux distro on an Android TV Box I found at Goodwill.
</p>

<p>
	<br />
	Not too much info on what company makes it, what the specs are etc. -- it's unfortunately too old to connect to the Google Play Store at this point (running android Jellybean).
</p>

<p>
	The only markings on it are on the top of the case saying RBOX, but I have yet to find any other device like it on any site. It's a red and black square case, for what that's worth.
</p>

<p>
	 
</p>

<p>
	I also haven't been able to boot to the BIOS/bootloader menu, even holding the reset button -- all that happens is the little Android mascot says its loading then after a few seconds it "dies" (red triangle-shaped thing above the body) only to reboot again. I can boot to the normal OS just fine, but cant do much once there.
</p>

<p>
	 
</p>

<p>
	As such, I haven't found a way to boot off of a USB stick, SD card, etc. just whatever is built in to it.
</p>

<p>
	 
</p>

<p>
	Any help, advice, or info is greatly appreciated. Thanks!
</p>
]]></description><guid isPermaLink="false">21163</guid><pubDate>Mon, 30 May 2022 21:36:23 +0000</pubDate></item><item><title>How to install armbian on MStar MSO9380 CPU?</title><link>https://forum.armbian.com/topic/21034-how-to-install-armbian-on-mstar-mso9380-cpu/</link><description><![CDATA[<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">今天是个好日子。</font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">有没有人成功地将 Roku Premiere (3920X) 或 Roku Premiere (4620X) 或 Roku Premiere+ (3921X) 或 Roku Premiere+ (4630X) 或 Roku Ultra (4640X) 写入 armbian 或其他 Linux 系统？</font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">碰巧我拥有与上述同一系列的电视板。</font><font style="vertical-align:inherit;">请描述详细步骤。</font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">任何答复表示赞赏。</font></font>
</p>
]]></description><guid isPermaLink="false">21034</guid><pubDate>Sat, 21 May 2022 08:13:18 +0000</pubDate></item><item><title>Tanix TX5 Plus Deluxe(with external antenna) - need to combine 2 dtbs</title><link>https://forum.armbian.com/topic/20249-tanix-tx5-plus-deluxewith-external-antenna-need-to-combine-2-dtbs/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	I have updated my TX5 Plus Deluxe (4GB/64GB,1Gb Eth) to the latest official Android firmware (newton 20201224) and finally managed to start
</p>

<p>
	Armbian_20.10_Arm-64_buster_current_5.9.0.img from USB Flashdisk.
</p>

<p>
	I tested several <abbr title="Device tree blob">DTB</abbr> files for ethernet speed and working soundcard (aplay -l).
</p>

<p>
	Here are some results:
</p>

<p>
	1. started with meson-sm1-sei610-ethfix.<abbr title="Device tree blob">dtb</abbr> recommended for Tanix TX3 (similar box). Result - NO SOUND, 100mb Ethernet
</p>

<p>
	2. next - meson-sm1-sei610-x96maxplus.<abbr title="Device tree blob">dtb</abbr> I found <a href="https://forum.armbian.com/topic/15376-methods-to-fix-x96-max-pluss905x3-gigabit-ethernet-problem/" rel="">here</a>. Result is surprising - Gigabit ethernet WORKING, but no sound.
</p>

<p>
	    This is good news because it's working with original Tanix bootloader (speed confirmed via iperf3).
</p>

<p>
	3. next - meson-sm1-sei610-x96maxplus.<abbr title="Device tree blob">dtb</abbr> from <a href="https://forum.armbian.com/topic/16202-current-status-of-armbian-for-x96-air-p3-464gb-s905x3/" rel="">here</a> - SoundCard WORKING, but only 100mb Ethernet.
</p>

<p>
	root@armhassio:~# aplay -l<br />
	**** List of PLAYBACK Hardware Devices ****<br />
	card 0: SM1SEI610 [SM1-SEI610], device 0: fe.dai-link-0 (*) []<br />
	  Subdevices: 0/1<br />
	  Subdevice #0: subdevice #0<br />
	card 0: SM1SEI610 [SM1-SEI610], device 1: fe.dai-link-1 (*) []<br />
	  Subdevices: 1/1<br />
	  Subdevice #0: subdevice #0<br />
	card 0: SM1SEI610 [SM1-SEI610], device 2: fe.dai-link-2 (*) []<br />
	  Subdevices: 1/1<br />
	  Subdevice #0: subdevice #0
</p>

<p>
	 
</p>

<p>
	I want working both SoundCard and Gigabit ethernet. Could anyone help me combine good parts from those 2 <abbr title="Device tree blob">dtb</abbr> files ?
</p>

<p>
	Maybe it helps some other owners of this tvbox. Thanks a lot in advance.
</p>
]]></description><guid isPermaLink="false">20249</guid><pubDate>Mon, 11 Apr 2022 16:16:32 +0000</pubDate></item><item><title>Old image for Amlogic s905x3 ?</title><link>https://forum.armbian.com/topic/19105-old-image-for-amlogic-s905x3/</link><description><![CDATA[<p>
	Greetings.
</p>

<p>
	I just entered this hobby tonight and read up some on amlogic boxes in these forums. 
</p>

<p>
	 
</p>

<p>
	Im trying to boot armbian to a A95xF3 air with the amlogic s905x3 chip off a SD card but hangs at error message "fail to map file in aml_autoscript".
</p>

<p>
	I guess I have the wrong <abbr title="Device tree blob">dtb</abbr> file configured in ext-linux, I have not tried all <abbr title="Device tree blob">dtb</abbr> files yet but now I have wasted so much time so I try to ask here if there is any easy way booting the amlogic s905x3 chip. There is a couple of youtube videos using files for Rk3399 from 2019 and perhaps they might work as Im not lucky with the last posted ubuntu 20.20 images ?
</p>

<p>
	I did read there is security issues with the old images so perhaps that is not an option. If there is a clear howto for the boot setup I would appreciate a link as there is lots of different methods described at different places making me confused. What I learned of this device is that pressing reset button with tooth pick gives nothing, su reboot update in termux not available allthough claiming to be rooted so only way getting the box to read SD is via the manual software update app. Android build number in the box is 202006121521, android 9.<br />
	<br />
	kindly jhg.
</p>
]]></description><guid isPermaLink="false">19105</guid><pubDate>Thu, 14 Oct 2021 20:20:50 +0000</pubDate></item><item><title>X96 mini Ram 2G / 16 Gm rom - not booted</title><link>https://forum.armbian.com/topic/20095-x96-mini-ram-2g-16-gm-rom-not-booted/</link><description><![CDATA[<p>
	Hi , Thanks for developing armbian , i try very image of armbian but no success in boot .
</p>

<p>
	I Accidental found the image and it was booted successfully on x96mini but another image won't booted. why ?<br />
	i use official armbian was not booted
</p>

<p>
	i use amlogic-s9xxx-armbian github repo was not booted.
</p>

<p>
	why top image wasn't boot but  booted successfully on x96-mini ?
</p>
]]></description><guid isPermaLink="false">20095</guid><pubDate>Fri, 18 Mar 2022 11:14:26 +0000</pubDate></item><item><title>Cannot reset TV Box</title><link>https://forum.armbian.com/topic/20135-cannot-reset-tv-box/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	Hello community. I have a X88 Pro S Android TV Box using chip Rk3318 that I want to run Armbian (<a href="https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/" rel="">steps</a> by <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/1002-jock/?do=hovercard" data-mentionid="1002" href="https://forum.armbian.com/profile/1002-jock/" rel="">@jock</a>) However I haven’t found a way to reset my box. I looks like this box doesn’t have a reset button.
</p>

<p>
	 
</p>

<p>
	If someone can help me to figure this out, I will really appreciate.
</p>

<p>
	Thanks
</p>

<p>
	 
</p>

<p>
	Link of my device images
</p>

<p>
	<a href="https://drive.google.com/file/d/1ka_k2l8_9YrwiZhLnA5YYcR7HS1P6rpY/view?usp=sharing" rel="external nofollow">https://drive.google.com/file/d/1ka_k2l8_9YrwiZhLnA5YYcR7HS1P6rpY/view?usp=sharing</a>
</p>

<p>
	<a href="https://drive.google.com/file/d/1i_hw9qYigArmG6J46lNyYLI557hWjMtY/view?usp=sharing" rel="external nofollow">https://drive.google.com/file/d/1i_hw9qYigArmG6J46lNyYLI557hWjMtY/view?usp=sharing</a>
</p>

<p>
	<a href="https://drive.google.com/file/d/1QG_VKF4hDO2xSjjKKwy3bJMuBcDcFpc6/view?usp=sharing" rel="external nofollow">https://drive.google.com/file/d/1QG_VKF4hDO2xSjjKKwy3bJMuBcDcFpc6/view?usp=sharing</a>
</p>
]]></description><guid isPermaLink="false">20135</guid><pubDate>Wed, 23 Mar 2022 12:52:55 +0000</pubDate></item><item><title>Instalation HA on andoid box with Armbian</title><link>https://forum.armbian.com/topic/20122-instalation-ha-on-andoid-box-with-armbian/</link><description><![CDATA[<p>
	Hi
</p>

<p>
	I installed my HA system on an android box Amlogic S912 Octa core, with armbian, everything works fine until i restart the box.
</p>

<p>
	Box: <a href="https://www.amazon.co.uk/Bqeel-Android-Bluetooth-Amlogic-Output/dp/B078MHCTWT" rel="external nofollow">https://www.amazon.co.uk/Bqeel-Android-Bluetooth-Amlogic-Output/dp/B078MHCTWT</a>
</p>

<p>
	 
</p>

<p>
	After restarting the box I can no longer access the HA, but I can access the box with putty.
</p>

<p>
	 
</p>

<p>
	For everything to work again, I have to delete docker, HA and re-install everything again, but as soon as I remove the power, I am again without access by brower.
</p>

<p>
	 
</p>

<p>
	I think the problem is in some service that is not on startup, but I have no experience with linux and I don’t know how to solve this problem
</p>

<p>
	 
</p>

<p>
	Can anyone help me try to find the problem?
</p>

<p>
	Best Regards
</p>
]]></description><guid isPermaLink="false">20122</guid><pubDate>Mon, 21 Mar 2022 23:18:14 +0000</pubDate></item><item><title>Armbian X96+ HDD USB issue</title><link>https://forum.armbian.com/topic/19997-armbian-x96-hdd-usb-issue/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I have X96+ with armian. I have issue with usb hdd (usb 3.0) on both usb ports (2.0/3.0).Disk have ext4 partition. During hisk work very often disk unmounting (i hear when thisk stoping). In effect the disk is mounted as read-only and of course it generates disk errors that are repairable with fsck.
</p>

<p>
	 
</p>

<p>
	What could be the reason? A badly mounted drive or a sluggish, dying power supply? How I can diagnose this? Any ideas?
</p>

<p>
	 
</p>

<p>
	I simply mounting disk in fstab
</p>

<p>
	 
</p>

<pre class="ipsCode">LABEL=usb-hdd   /media/usb-hdd  ext4            defaults,rw                                0 0</pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">19997</guid><pubDate>Sat, 05 Mar 2022 17:34:12 +0000</pubDate></item><item><title>Manjaro arm on Amlogic Tv box?</title><link>https://forum.armbian.com/topic/19985-manjaro-arm-on-amlogic-tv-box/</link><description><![CDATA[<p>
	Hello
</p>

<p>
	 
</p>

<p>
	is there a chance to run manjaro arm server / desktop on tv box mxq pro 4k amilogic s905x?
</p>

<p>
	 
</p>

<p>
	or how does the process of building such a system look like?
</p>
]]></description><guid isPermaLink="false">19985</guid><pubDate>Thu, 03 Mar 2022 10:07:39 +0000</pubDate></item><item><title>Two different boxes don't reboot sometimes</title><link>https://forum.armbian.com/topic/19967-two-different-boxes-dont-reboot-sometimes/</link><description><![CDATA[<p>
	Hi. I'm trying to use Armbian 20.10 from Balbes and I'm thankfull to you for supporting it. But I have a problem.
</p>

<p>
	 
</p>

<p>
	I have:<br />
	1. X88 pro X3 with u-boot-s905x2-s922 as u-boot.ext and meson-g12a-x96-max-rmii.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> choosen.
</p>

<p>
	2. A95X F3 Air with u-boot-s905x2-s922 as u-boot.ext and meson-sm1-sei610.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>
</p>

<p>
	 
</p>

<p>
	Both of them work. I can connect to them with ssh.<br />
	But I found that sometimes after reboot command both of them do not start again until I plug/unplug them.
</p>

<p>
	I made this little script:
</p>

<pre class="ipsCode">date &gt;&gt; ~/Files/reboots.txt
/sbin/reboot</pre>

<p>
	I put it into a crontab. It executes it each 2 minutes. Both of devices rebooted well for 10-15 times when I tried it first. But after that it takes 3-4 reboots to hang.
</p>

<p>
	During that hanging device is unaccessible through ssh and HDMI output shows nothing. I tried to look into journalctl logs but found that a journal for hanged boot doesn't exist. There are journals for previous boot and for the next after unplugging and nothing in between.
</p>

<p>
	So, I thought that the problem is with u-boot. I connected to X88 with UART adapter.
</p>

<p>
	This is how the end of normal session looks:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">*kernel started*
...
arm-64 login:         *here it asks for a login and password but I just wait*
reboot: Restarting system
*some messages about restarting here*
...
*beggining of a new start here*</span></pre>

<p>
	And this is how the ending of weird session looks:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">*kernel started*
...
arm-64 login:         *here it asks for a login and password but I just wait*</span></pre>

<p>
	Yes, it doesn't show a log for a new start neither a log for ending of previous session. It looks for me like system is hanging not on start but on shutting down.
</p>

<p>
	 
</p>

<p>
	Nobody had such an issue? How it can be fixed? Thanks in advance.
</p>
]]></description><guid isPermaLink="false">19967</guid><pubDate>Tue, 01 Mar 2022 14:49:56 +0000</pubDate></item><item><title>Looking for specs and Linux Distro for an Android TV Box</title><link>https://forum.armbian.com/topic/19930-looking-for-specs-and-linux-distro-for-an-android-tv-box/</link><description><![CDATA[<p>
	Hello, I have an old Android TV Box (affectionately named RBOX) -- having trouble finding any specs or hardware information for it, and I'm trying to see if I can throw on a Linux distro to turn it into a micro-server (either via USB or SD Card).
</p>

<p>
	 
</p>

<p>
	Has anyone ever seen one of these, know what kind of hardware is in it? (CPU, firmware, etc.?) Any reccomendations on which distro to use? I tried Bullseye Armbian to no avail.
</p>
]]></description><guid isPermaLink="false">19930</guid><pubDate>Thu, 24 Feb 2022 18:53:07 +0000</pubDate></item><item><title>7 segments display - openvfd - displaying custom chars?</title><link>https://forum.armbian.com/topic/19907-7-segments-display-openvfd-displaying-custom-chars/</link><description><![CDATA[<p>
	Using openvfd and the recommended settings, the display on my box works for me, but I can always only see the exact time.<br />
	How can I display my own content using openvfd?
</p>
]]></description><guid isPermaLink="false">19907</guid><pubDate>Sun, 20 Feb 2022 21:33:09 +0000</pubDate></item><item><title>Good or bad idea?</title><link>https://forum.armbian.com/topic/19772-good-or-bad-idea/</link><description><![CDATA[<p>
	Hi TV boxes hackers,
</p>

<p>
	 
</p>

<p>
	We are thinking of re-purposing an existing Android TV box into a $30 personal cyber-security monitoring server for your home.
</p>

<p>
	 
</p>

<p>
	Good or terrible idea? What caveats should we pay attention to?
</p>

<p>
	 
</p>

<p>
	We will order directly from the manufacturer so we should be able to save some money (no need for a remote or an HDMI cable) and ensure they all use the same components.
</p>

<p>
	Giving the current chip shortage, it is though to reach a $30 price point without being creative... (we won't take any profit on the hardware)
</p>

<p>
	 
</p>

<p>
	The project will be open source (no code yet).
</p>

<p>
	 
</p>

<p>
	Current status: Armbian running on RK3318 - X88 Pro (thanks <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/1002-jock/?do=hovercard" data-mentionid="1002" href="https://forum.armbian.com/profile/1002-jock/" rel="">@jock</a> !). The performance seems good enough and AI acceleration using the <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> doesn't seem too hard to add but we are still exploring other options.
</p>
]]></description><guid isPermaLink="false">19772</guid><pubDate>Mon, 31 Jan 2022 21:23:10 +0000</pubDate></item><item><title>Repurpose Allwinner A33 Android 4.4.2 Tablet to Linux</title><link>https://forum.armbian.com/topic/19810-repurpose-allwinner-a33-android-442-tablet-to-linux/</link><description><![CDATA[<p>
	G'Day,
</p>

<p>
	I have anold 10" Onix AT-101-1215 tablet that I bought from Aldi in 2016 and would like to tinker with it and attempt to install Linux on it.<br />
	Is this possible?
</p>

<p>
	If so can anyone give me some guidance as how to best do this?
</p>
]]></description><guid isPermaLink="false">19810</guid><pubDate>Sat, 05 Feb 2022 07:01:32 +0000</pubDate></item><item><title>X96 Max 4g (S905x2) with armbian + usb 4 bay hdd enclosure as NAS</title><link>https://forum.armbian.com/topic/19600-x96-max-4g-s905x2-with-armbian-usb-4-bay-hdd-enclosure-as-nas/</link><description><![CDATA[<p>
	Hey Everbody,<br />
	<br />
	as the title suggests, im considering adding an external HDD enclosure to my S905x2 box running armbian to use it as a budget NAS.<br />
	I was considering using Openmedia Vault + 4 Bays Raid 5 via USB 3.0.<br />
	<br />
	Is there anything in principle that would speak against this?<br />
	<br />
	Another question i have: would i need to use an external enclosure with a built in raid controller or can i use any external enclosure and setup the raid via software control (in armbian)??<br />
	<br />
	Also i am not sure if i should go for a cheaper non-brand or maybe something like a QNAP TR-004 that i could (re)use with a real qnap NAS at some point in the future.<br />
	<br />
	Anybody here who has experience with such a setup?<br />
	<br />
	Thanks for reading and sharing your thoughts.
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2022_01/4821_P_1437416502482.jpg.656687cc43f9307eb421c863e8a37a67.jpg" class="ipsAttachLink ipsAttachLink_image"><img data-fileid="8597" src="https://forum.armbian.com/uploads/monthly_2022_01/4821_P_1437416502482.thumb.jpg.f80a6046d0b24302d2f36f89f5778727.jpg" data-ratio="100" width="750" class="ipsImage ipsImage_thumbnailed" alt="4821_P_1437416502482.jpg"></a></p>
<p><a href="https://forum.armbian.com/uploads/monthly_2022_01/x96-max-amlogic-s905x2-android-8-1-4gb-32gb-tv-box--1574132570887.jpg.7afaa42d323fe8d8b5a3c8edc6e64b57.jpg" class="ipsAttachLink ipsAttachLink_image"><img data-fileid="8598" src="https://forum.armbian.com/uploads/monthly_2022_01/x96-max-amlogic-s905x2-android-8-1-4gb-32gb-tv-box--1574132570887.thumb.jpg.a6d837d03dcdf6c55fd6e54937f4c1f7.jpg" data-ratio="100" width="750" class="ipsImage ipsImage_thumbnailed" alt="x96-max-amlogic-s905x2-android-8-1-4gb-32gb-tv-box--1574132570887.jpg"></a></p>]]></description><guid isPermaLink="false">19600</guid><pubDate>Tue, 04 Jan 2022 15:54:04 +0000</pubDate></item><item><title>Open Hour Android TV Chameleon</title><link>https://forum.armbian.com/topic/19560-open-hour-android-tv-chameleon/</link><description><![CDATA[<p>
	I have trouble with Open Hour Android TV Chameleon previously I was going to change to armbian and it didn't work and I also tried burning with firmware T032_AP6330_public_20140915.img to 8 Giga MMC contained in the package for what I'm facing now, is there a solution,.. pls help i want to use Armbian_20.10_Arm-64_bullseye_current_5.9.0.img for this tool,,,
</p>
]]></description><guid isPermaLink="false">19560</guid><pubDate>Sat, 25 Dec 2021 12:09:39 +0000</pubDate></item><item><title>Issues with black screen</title><link>https://forum.armbian.com/topic/19531-issues-with-black-screen/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	Hey everyone, don't tear me up too much, but its been maybe 25 years since I have dabbled with any *nix type environment. 
</p>

<p>
	 
</p>

<p>
	Recently tinkering around, I installed Armbian on my TX3 Mini Android box.  No complaints, feels like I am getting back into the swing of things again.  But for some reason, I cannot figure out how to turn off the screen saver / maybe power managent IE: Black screen.  It goes black after 10 minutes or so and I just wanted to keep it on.  Spent a few days trying things on and off from suggestions I found online, but nothing seems to work.  FYI I dont have xscreensaver installed either.
</p>

<p>
	 
</p>

<p>
	Thanks!
</p>
]]></description><guid isPermaLink="false">19531</guid><pubDate>Fri, 17 Dec 2021 13:23:29 +0000</pubDate></item><item><title>S912 Box, Internal emmc input/output error</title><link>https://forum.armbian.com/topic/19175-s912-box-internal-emmc-inputoutput-error/</link><description><![CDATA[<p>
	Hi there!
</p>

<p>
	I have a Mecool M8S Pro L box with Amlogic S912 3/32GB and 100Mbit ethernet.
</p>

<p>
	I am running the current bullseye and focal image from microsd without any problems.
</p>

<p>
	 
</p>

<p>
	But i am not able to do anything with the internal <abbr title="embedded MultiMediaCard">EMMC</abbr>, fdisk, ddbr and anything else giving an Input/Output error and i am not able to install the image into the internal <abbr title="embedded MultiMediaCard">emmc</abbr> (this is my goal)
</p>

<p>
	 
</p>

<p>
	I tried every gxm* <abbr title="Device tree blob">dtb</abbr> file but none of them making any difference (only some of them are not booting into the linux os, but none can access the internal <abbr title="embedded MultiMediaCard">emmc</abbr>)
</p>

<p>
	 
</p>

<p>
	could anyone give me a hint what to do or does anyone know whats wrong and what to do to get it working?
</p>

<p>
	thanks a lot!
</p>
]]></description><guid isPermaLink="false">19175</guid><pubDate>Thu, 28 Oct 2021 21:05:05 +0000</pubDate></item><item><title>Help a newbie out - resources for choosing a TV box</title><link>https://forum.armbian.com/topic/19078-help-a-newbie-out-resources-for-choosing-a-tv-box/</link><description><![CDATA[<p>
	Hello Armbian'ers,
</p>

<p>
	 
</p>

<p>
	I'm a veteran Debian user and occasional system administrator, but - have zero experience with TV set-top boxes / media streamers. I now find myself in a position of needing one: In a rental apartment, I have a wall-mounted TV with HDMI in but an old, custom, non-upgradable vendor-specific OS and no network connectivity.
</p>

<p>
	 
</p>

<p>
	To be honest - I don't particularly need my box to be ARM-based, nor do I need my OS distribution to be Debian. I mean, that would be the nicest, since my desktop is Devuan Chimaera (~= Debian 11), but I would definitely settle on any reasonable Linux distro.
</p>

<p>
	 
</p>

<p>
	Anyway, my questions:
</p>

<p>
	 
</p>

<p>
	1. How can I educate myself about my different options? Manufacturers (I don't mind ones which are relatively unknown in the west), key features which might not be obvious to a PC user, buyers' guides etc.?
</p>

<p>
	2. If I get some specific recommendation of a TV box - how do I evaluate it (reviews, fine-print, benchmarks, compatibility lists etc.)?
</p>

<p>
	 
</p>

<p>
	I'm not asking you guys to write up an encyclopedia for me as an answer to this question, but rather for a few pointers and directions to follow, to resources off- and maybe on this site.
</p>

<p>
	 
</p>

<p>
	PS - I've read <a href="https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first" rel="">this</a> and it seems quite discouraging regarding boxes with Armbian support - either it's essentially discontinued (AmLogic) or there's missing info :-( 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">19078</guid><pubDate>Fri, 08 Oct 2021 20:18:10 +0000</pubDate></item><item><title>Please help us to make the $30 Android TV box the promising bright future of internet and software freedom</title><link>https://forum.armbian.com/topic/16795-please-help-us-to-make-the-30-android-tv-box-the-promising-bright-future-of-internet-and-software-freedom/</link><description><![CDATA[<p>
	We are currently at a breaking point where cheap Android TV boxes become powerful enough and viable enough to do the following while running Linux:
</p>

<p>
	 
</p>

<p>
	1.  Be a server: self-hosting data, fediverse, home NAS
</p>

<p>
	2. Be a TV box: 1. web browser, 2. other multimedia options, 3. games
</p>

<p>
	3.  Be a makeshift PC replacement (run office applications, photo editing, etc)
</p>

<p>
	 
</p>

<p>
	Concerning #1: If you have followed the news then you have witnessed that censorship is increasing and that the nature of it is most alarming. Over the next years, big tech and politics-driven manipulation of online information will only get worse, until the internet essentially devolves into a kind of TV program suitable for only silent, mindless and conformist consummation. In the wake of this happening, enough people are slowly waking up and realize: We can't just blindly put all our data and digital lives into the hands and dictatiorships of giant companies anymore. That is why we need to step back from those ill relationships and towards alternatives like the fediverse, that have already been worked on for the benefit of the greater good. As more and more ordinary and "technologically helpless" people are turning to the community for solutions, we should have all the answers. 
</p>

<p>
	 
</p>

<p>
	Concerning #2 &amp; #3: Many people have smart TVs now. A lot of them aren't even running Android and they do not support any or proper web browsers in order to lock people into vendor schemes. But even on Android, many apps do only work in a makeshift shorthand manner, meant to be just barely enough to work with on a tiny phone when a PC is not available. Office doesn't work well and can't be used in a productive manner, most uncommon hardware addons like basic game controllers are not working for game emulation, if there are server apps they tend to be unreliable, there are not proper video/photo/music editors, etc. etc. This is absolutely not the case on desktop Linux distributions that run on x86 and ARM virtually all the same.
</p>

<p>
	 
</p>

<p>
	The TV box has evolved away from a dumb DVD player-alike thing with classic remote controls and is moving towards being a mini-PC with mini keyboard remote or full keyboard and mouse as standard, that people need for things they just can't practicably do well enough with their smartphones. In fact nowadays, most ordinary people rather primarily use their smartphones and do not even want to have a real PC around. Like described, Android performs well on smartphones, but the entire ecosystem has always been and will always be far too misfit for the TV environment to exhaust the true potential and benefit a TV box could have in people's lives.
</p>

<p>
	<br />
	Here is were Linux comes in, and this could turn the tide on Linux marketshare: We, the people from the Linux community, are not only providing a solution, with enduser-friendly server application environments like Yonohost or Docker, to the problem of big tech vs. our privacy, freedom and democracy. We also provide an operating system that fills an unfilled market nieche: the TV box as both a media center and mini-PC, a kind of "most things ordinary people often most need but nothing too serious" kind of solution. One that isn't controlled by big tech, and one that is born out of free choice and their choice for freedom. Never again has it been so convincing for people to switch to Linux by their own volition.
</p>

<p>
	 
</p>

<p>
	The Rasperry Pi or similar boards are all in all a good option here. But unfortunately they are neither advertized, nor sold nor priced in a manner that would appeal to and convince the average Joe to buy it. In fact I would rather buy the Rasperry Pi, if I was only buying it for myself: to have it easier.  But I am not thinking of myself here. I am thinking of the bigger picture and the greater good that would come from even lower cost.
</p>

<p>
	 
</p>

<p>
	Think of this: Before the Rasperry Pi existed, you could have simply used an old notebook or a thin client with <abbr title="General purpose input/output"><abbr title="General purpose input/output">GPIO</abbr></abbr> card to do the same job. Yet in the very long era of thin clients, no one was thinking of all the great magical things you can do now with the Rasperry Pi. That is because back then they weren't magical at all at higher price points. When you run the Pi now, it consumes barely any power. Hosting your own data or controlling the doorbell, heating or hydroponic garden over wifi feels like a delight. You have so many awesome possibilites to enriche your life. But when you pay $10 for powering the Pi per month, like you would have paid for an old thin client, all those great things feel rather unpleasant. They aren't so advantageous or helpful anymore and leave a very bad aftertaste. A $30 TV box is about as capable as a Rasperry Pi and the Rasperry Pi is about as capable as some thin client from back in the day. The lower cost is all there was that made all the difference. And it is what opened up widespread use, large communities sourrunding it and so many benefits that just weren't really good benefits at all when the technology was more expensive.
</p>

<p>
	 
</p>

<p>
	That is how a $30 TV box running Linux will be cornerstone technology. And a thin client or Rasperry Pi kit for $100 sadly were not.
</p>

<p>
	 
</p>

<p>
	$30 will currently get you a 4GB/64GB Cortex-A55 with Mali 31 <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr>. Those specs are far than enough.
</p>

<p>
	 
</p>

<p>
	Linux currently has (like it always had) 2% market share on desktops. Something needs to change, not to convince ourselves more that our own logic is sound, but to bring more ordinary "non tech" people in. who are not knowing the same things we do and make decisions based on different premises and imperatives. If we could push Linux up to only 15% market share, then most software companies that currently ignore Linux (like Adobe) would also develop for Linux to make more profit. At this point, Linux would snowball into widespread use because it had more advantages than using Windows. This wouldn't just be a great victory for software freedom and thus our freedom while using software, but it would also lay the foundation for a consciousness on digital freedoms and other cultural freedoms as well, where today only ignorance prevails.
</p>

<p>
	 
</p>

<p>
	What catches ordinary "non tech" people is also impression and convenience. Like a phone just resets and you can sell it, you can plop out your SD card into the next TV box and merely use the internal user-storage of Android for backup files. You can dual-boot Android, just try Linux out, no harm done. It comes fully assembled and doesn't look weird. Believe me to ordinary people who basically know nothing about technology, things like this are huge. Not only but foremost because they can easily imagine how to move forward with and treat it like other things they already have used before (like a phone or TV).
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	I didn't say it will be easy, just that this is how things are and could be. There are several problems to be solved and some are not easy to solve.
</p>

<p>
	 
</p>

<p>
	Like on PCs, Linux doesn't ship pre-installed on Android TV boxes and it needs to be distributed afterwards. Here I could imagine, that people could turn to local computer/Linux clubs to have it done for them for free. Or they could, worst-case, mail their box to someone in their country who will install Linux for them. It is probably the biggest hurde to get people to make this first step. But as people are now losing faith in big corporations, the return to community-driven options is only logical.
</p>

<p>
	 
</p>

<p>
	Then there is the technical side of things. And this is where we come in and I am asking for your help here: As I gathered, virtually all the cheap TV boxes with really good specs are (and always were) Amlogic devices. As you know there are hundreds of devices and they even often require reverse engineering, while the manufacturers don't play ball. So supporting Amlogic in general seems more like a fools errand. **However**, for us to support just one model every 2 years per generation is not: It absolutely is the smartest move we can make for everyone. We make the cheapest and fastest box work smoothly and as good as it gets, as a team effort. And this is the box we recommend as a community, that all people then can buy and profit from.
</p>

<p>
	 
</p>

<p>
	I believe so strongly in the value of this vision and the power and potential of all the converging events described, that I want to create a seperate website, which will serve two purposes: 1. to coordinate the project, provide a better dedicated space for knowledge and development. 2. To describe the idea to ordinary consumer-type people, so that they can easily understand what it is, what their options are in software and hardware and and what advantages they get.  There are many recent technologies from the fediverse and related, like Yunohost and docker, that even most tech-savvy people know nothing about and hence can't draw implications from. A dedicated site would quickly explain all those things, in a carefully thought-through manner to specific audiences, provide demos and tutorials and so forth and thus not be as convoluted and difficult to ingest as the post that you are reading right now on this forum.
</p>

<p>
	 
</p>

<p>
	From what I gathered, there isn't anything happening like that here or elsewhere at all. But admittedly, I haven't searched for it days on end either. I know of Balbes who seemed to be the one-man-army for Amlogic devices but now it seems he has quit? And SteeMan kind of took his place? I have been reading some on the Forum, and learned a few things about the general situation and gained insight to very very few scattered technical details. But there are thousands of pages on this-and-that sourrunding the topic from the last years. And it is totally impossible to work through all of it. This forum is about enduser support mostly, and no seperate dev forum seems to exist there are just bits and pieces here and there.
</p>

<p>
	 
</p>

<p>
	This is why it would be really really helpful if someone very experienced (like Balbes?) could write a crash course for other devs who have not worked much beyond the basics with TV box hardware.
</p>

<p>
	 
</p>

<p>
	This crash course should contain all the endpoints where dev support is needed, the technical nature of the problem, some details around it and maybe even a quick guide how to possibly tackle them. Of course this shouldn't be a lengthy tutorial, and only be as long as the person has time to spare. In essence it should just be the insights and pitfalls in the deciding details that someone with experience has gathered.
</p>

<p>
	 
</p>

<p>
	We could then expand on that crash course and work through all the issues. But let's first see how many people really jump on to this train, or if this will be a one man show. That would be kind of sad.
</p>

<p>
	 
</p>

<p>
	Personally I don't have much experience in hardware hacking and I can't desolder SMD parts or read EPROMs or anything like that (I suppose that isn't required, ever?; hopefully). I did work in IT most of my life, so I have all sorts dev exeperiences and am a Linux expert. I worked with microcontrollers and kernel drivers before, but not much. I dived a bit into uboot and drivers 2 years ago for my current box, but I still have to learn quite some with the hardware specifics. I have a ttl serial dongle of course. I am willing to learn whatever it takes.
</p>

<p>
	 
</p>

<p>
	As for the question of "which box?": Please make a recommendation. I believe the X96 max plus is the best candidate for last year and as a start.
</p>
]]></description><guid isPermaLink="false">16795</guid><pubDate>Sun, 17 Jan 2021 01:56:43 +0000</pubDate></item><item><title>Keyboard doesn't work</title><link>https://forum.armbian.com/topic/19011-keyboard-doesnt-work/</link><description><![CDATA[<p>
	I just installed Armbian on my Android TV Box. When it booted up, it asked me to enter the root password. My issue is that none of my keyboards were recognized and I wasn't able to type the password in. Does anyone know how I can resolve this?
</p>
]]></description><guid isPermaLink="false">19011</guid><pubDate>Mon, 27 Sep 2021 05:49:05 +0000</pubDate></item><item><title>Hk1 box  problem</title><link>https://forum.armbian.com/topic/18990-hk1-box-problem/</link><description><![CDATA[<p>
	<a href="https://dosya.co/irtohgogh4hh/Screenshot_20210917-153104.png.html" rel="external nofollow">https://dosya.co/irtohgogh4hh/Screenshot_20210917-153104.png.html</a><br />
	 
</p>

<p>
	Always waiting at red and blue lights.  Nothing moves.  The device does not turn on.
</p>

<p>
	 
</p>

<p>
	How can I animate this device? Which path should we follow? Please help.
</p>

<p>
	 
</p>

<p>
	 how can i restore the device
</p>

<p>
	 Can you help me please :(((
</p>

<p>
	I don't know much, I'm new I'm joining you for the first time
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">18990</guid><pubDate>Wed, 22 Sep 2021 19:00:03 +0000</pubDate></item><item><title>Help wanted and appreciated to build an updated image for AML s905(x)(2), arm-64, etc...</title><link>https://forum.armbian.com/topic/18967-help-wanted-and-appreciated-to-build-an-updated-image-for-aml-s905x2-arm-64-etc/</link><description><![CDATA[<p>
	Hello everyone,
</p>

<p>
	I would like to build an updated Armbian image for balbes150's arm-64 implementation.<br />
	Image family found here: <a href="https://users.armbian.com/balbes150/arm-64/" rel="external nofollow">https://users.armbian.com/balbes150/arm-64/</a>
</p>

<p>
	 
</p>

<p>
	I have started some work on my personal armbian branch here: <a href="https://github.com/SLAzurin/build-armbian-custom/tree/arm64tv" rel="external nofollow">https://github.com/SLAzurin/build-armbian-custom/tree/arm64tv</a><br />
	Currently, I'm not sure about my progress, there were times I was able to build an image, but the machine wouldn't boot successfully. (using xdarklight's kernel files <a href="https://github.com/xdarklight/linux/tree/meson-mx-integration-5.14-20210718" rel="external nofollow">https://github.com/xdarklight/linux/tree/meson-mx-integration-5.14-20210718</a>)<br />
	At most, it would boot into u-boot, and then hang after trying to start the Linux kernel.
</p>

<p>
	When I try using balbes150's kernel (<a href="https://github.com/150balbes/linux-arm" rel="external nofollow">https://github.com/150balbes/linux-arm)</a>, it would fail to build the armbian image.
</p>

<p>
	 
</p>

<p>
	I'm just a regular software developer so I may not understand hardware related terms that well, sorry in advance.
</p>

<p>
	 
</p>

<p>
	Pointers, or any clues are very much appreciated =)<br />
	<br />
	Edit:
</p>

<p>
	My current hardware is a Nexbox A95x with AML s905x 2gb ram 16gb <abbr title="embedded MultiMediaCard">eMMC</abbr>
</p>
]]></description><guid isPermaLink="false">18967</guid><pubDate>Sat, 18 Sep 2021 04:39:19 +0000</pubDate></item><item><title>Hk1 box help me</title><link>https://forum.armbian.com/topic/18963-hk1-box-help-me/</link><description><![CDATA[<p>
	<a href="https://dosya.co/irtohgogh4hh/Screenshot_20210917-153104.png.html" rel="external nofollow">https://dosya.co/irtohgogh4hh/Screenshot_20210917-153104.png.html</a><br />
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">Hep kırmızı ışıkta beklemek. </font><font style="vertical-align:inherit;">Hiçbir şey hareket etmiyor. </font><font style="vertical-align:inherit;">Cihaz açılmıyor.</font></font>
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">cihazı nasıl geri yükleyebilirim</font></font>
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">Lütfen yardımcı olur musunuz </font></font><span><font style="vertical-align:inherit;"><font style="vertical-align:inherit;">:(((</font></font></span>
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">18963</guid><pubDate>Fri, 17 Sep 2021 15:25:27 +0000</pubDate></item><item><title>S912 Open VPN issues</title><link>https://forum.armbian.com/topic/17345-s912-open-vpn-issues/</link><description><![CDATA[<p>
	HI All,
</p>

<p>
	 
</p>

<p>
	Brand new user to Armbian, and fairly new user to linux here! running Debian bullseye desktop version, downloaded and install about a week ago....
</p>

<p>
	 
</p>

<p>
	First off, loving what Armbian has done to my old S912 box, thanks very much for this fantastic image!
</p>

<p>
	 
</p>

<p>
	i have been able to get it all set mostly the way i would want and have set up a nextpvr back-end server that is working very well feeding other 'kodi' boxes dotted around the house.
</p>

<p>
	 
</p>

<p>
	on to my issue, hopefully it is something easy to address, i have set up openvpn using the network manager gui, and it connects just fine, and 'tun0' shows as connected, however, no traffic appears to actually route through the VPN. if i go to whats my ip, it shows the IP from my ISP regardless to weather the VPN is connected or not.
</p>

<p>
	 
</p>

<p>
	i tried googling for advice, but could not find anything specific for Armbian, i did find lots of differing advise aimed at Debian and Ubuntu. but when i tried to follow some of the advice i either could not find files i was directed to , or didn't get the output in terminal i was expecting, i'm. very new to this.
</p>

<p>
	 
</p>

<p>
	if anyone has any advice i could follow to try to understand why this is happening and how to address it would be very much appreciated.
</p>

<p>
	 
</p>

<p>
	Thanks!
</p>
]]></description><guid isPermaLink="false">17345</guid><pubDate>Tue, 23 Mar 2021 11:58:10 +0000</pubDate></item><item><title>Some questions still remain..</title><link>https://forum.armbian.com/topic/18931-some-questions-still-remain/</link><description><![CDATA[<p>
	Hi everbody,<br />
	last week I bought a TV-Box X96mini 2 GB / 16 GB. After reading the FAQ (thx @SteeMan), it was easy to set up this little box with the image provided by balbes150. (thx @balbes150)<br />
	Most of the hardware is working fine, with the meson-gxl-s095x-p212.<abbr title="Device tree blob">dtb</abbr>, which is found on /boot/<abbr title="Device tree blob">dtb</abbr>/amlogic.<br />
	There is a problem with the lirc support, but using triggerhappy will do the job. Thx @Alexey Woronov, <a href="https://forum.armbian.com/topic/11161-lirc-on-armbian-buster/?tab=comments#comment-83995" rel="">https://forum.armbian.com/topic/11161-lirc-on-armbian-buster/?tab=comments#comment-83995</a><br />
	Another little problem is audio. Basically sound works, but volume from the audio jack is much too low. Only when I'm turning the volume to the max, I'm able to hear something.<br />
	No sound probs using the HDMI output, this works fine.
</p>

<p>
	 
</p>

<p>
	Even after successfully setting up the box, couple of questions remain.
</p>

<p>
	 
</p>

<p>
	About image and uboot
</p>

<ul>
	<li>
		<p>
			If you check /boot/<abbr title="Device tree blob">dtb</abbr>/* there are .<abbr title="Device tree blob">dtb</abbr>-files for other arm-based boards. Does this means, that the installation image (5.9.0) supports all the listed devices?
		</p>
	</li>
	<li>
		<p>
			Is this the one and only installation image for tv-boxes? Where do I get the u-boot files for the other <abbr title="System On a Chip">soc</abbr>-types (Allwinner, Rockchip) from?
		</p>
	</li>
</ul>

<p>
	 
</p>

<p>
	About <abbr title="Device tree blob">dtb</abbr> and <abbr title="Device tree source">dts</abbr>
</p>

<ul>
	<li>
		<p>
			Are <abbr title="Device tree blob">dtb</abbr>-files kernel-specific? I know, that every kernel bring their own set of <abbr title="Device tree blob">dtb</abbr>-files, but what is changing on a <abbr title="Device tree blob">dtb</abbr>-file between the releases?
		</p>
	</li>
	<li>
		<p>
			Is there a method decompiling <abbr title="Device tree blob">dtb</abbr>-files?
		</p>
	</li>
	<li>
		<p>
			Is a <abbr title="Device tree source">dts</abbr>-file kernel-specific?
		</p>
	</li>
	<li>
		<p>
			Does it make sense having a <abbr title="Device tree blob">dtb</abbr>-file extracted from android stock rom (android 9 / Kernel 4.19) to use with provided 5.9.-based image?
		</p>
	</li>
</ul>

<p>
	 
</p>

<p>
	Besides having a server for pyload and a "VPN-Accesspoint" while running a openvpn client to my VPN provider, I also have an useable desktop (browsing and office is fine, multimedia not) which is accessable via RDP.
</p>

<p>
	I tried also an alternate setup: using this tv-box as a tv-box under Linux and kodi. The results were sobering me. Playing a local video file (USB, 1080p) with 5 fps is no fun, playing a internet live stream (720p) with 5 fp<strong>m</strong> is much more like listening to an audiocast, than watching TV. With the cpu frequency left at 1.2 Ghz, system load was over 90% on all cores when kodi was running, bringing up cpu's temperature up to 70°C. Unuseable. Taking this as an experience, I will go on using armbian server image on sd card, having in addition a rescue / backup system for android mods on <abbr title="embedded MultiMediaCard">emmc</abbr>.
</p>

<p>
	To be honnest: no matter, if stock or custom (Android TV9) rom, this box doesn't fullfill my requirements.  <br />
	Even with a limited screenresolution(1080p), video playback is "wacky", sometimes there are "blackouts", when starting a program or altering settings in menu.<br />
	When these "blackouts" lasting more than 5 seconds, my TV loses the "HDMI-handshake" to the box and falls back to it's own menu.
</p>

<p>
	 
</p>

<p>
	So, my last question will be:
</p>

<p>
	Does someone has an android tv-box (built-in bluetooth would be great) with well-working 4k support, which is although "armbian-able"?<br />
	Or, which might be better: Which full supported board does meet my requirements (min. 1080p resolution, proper video and sound playback, BT and WLAN) WITHOUT having active cooling?
</p>

<p>
	 
</p>

<p>
	Thx for your time, reading and answering my newbie questions.
</p>
]]></description><guid isPermaLink="false">18931</guid><pubDate>Sun, 12 Sep 2021 10:33:29 +0000</pubDate></item><item><title>Armbian on CloudnetGo CR19 RK3399 TV Box</title><link>https://forum.armbian.com/topic/18840-armbian-on-cloudnetgo-cr19-rk3399-tv-box/</link><description><![CDATA[<p>
	<a href="http://www.cloudnetgo.com/productinfo/138177.html" rel="external nofollow">http://www.cloudnetgo.com/productinfo/138177.html</a>
</p>

<p>
	Which of the supported boards can this device be compatible with? Can any of the supported configurations be used to build a kernel for this device ?
</p>
]]></description><guid isPermaLink="false">18840</guid><pubDate>Wed, 25 Aug 2021 05:30:30 +0000</pubDate></item><item><title>Saving an old arm box from the dustbin</title><link>https://forum.armbian.com/topic/18809-saving-an-old-arm-box-from-the-dustbin/</link><description><![CDATA[<p>
	Hello all!
</p>

<p>
	 
</p>

<p>
	And no by an old arm box I don't mean a box full of proshetic limbs! :-) .
</p>

<p>
	 
</p>

<p>
	I'm referring to this device:
</p>

<p>
	 
</p>

<p>
	<a href="http://rikomagic.co.uk/linux_mini_pcs.html" rel="external nofollow">http://rikomagic.co.uk/linux_mini_pcs.html</a>
</p>

<p>
	<a href="https://www.cnx-software.com/2014/09/25/rikomagic-announces-mk902ii-le-ubuntu-mini-pc-powered-by-rockchip-rk3288-soc/" rel="external nofollow">https://www.cnx-software.com/2014/09/25/rikomagic-announces-mk902ii-le-ubuntu-mini-pc-powered-by-rockchip-rk3288-<abbr title="System On a Chip"><abbr title="System On a Chip">soc</abbr></abbr>/</a>
</p>

<p>
	 
</p>

<p>
	The device was badged as a "RKM Mk902II" and claims to have a rk3288.
</p>

<p>
	 
</p>

<p>
	Dug it out today (it has sat unused and untouched for quite a while). Found that its plsatic box which has that strange gunk that is applied to to the box to make it look "shiny" has started to break down so it has become sticky. Anyway since I am clearing things out I thought I'd have one last go at booting a different OS on this device.
</p>

<p>
	 
</p>

<p>
	I have never head much luck ever since I bought one of these devices booting it off a microsd card.
</p>

<p>
	 
</p>

<p>
	Something called <a href="http://www.linuxium.com.au/how-tos/runningandroidorlinuxfromansdcardonark3288device-aneasywaytodualboot" rel="external nofollow">linuxium</a> could do this and I have an old 4GB microsd which will boot .... an ancient version of ubuntu. But this was all a long time ago.
</p>

<p>
	 
</p>

<p>
	I did see <a href="https://users.armbian.com/balbes150/rk3288/" rel="external nofollow">here</a> that there is a version of armbian for the rk3288. But it did not boot correctly (no display) but if I look at that armbian image I see there are several .<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> files in /boot/<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> . Snag is - is how can you find out which one your system uses? Is there some kind of special tool?
</p>

<p>
	 
</p>

<p>
	Is it the case that not all rk3288s are exactly the same?
</p>

<p>
	 
</p>

<p>
	(BTW this device is not a firefly device, nor a R69 it is ..... unknown!).
</p>

<p>
	 
</p>

<p>
	Any help much appreciated!
</p>

<p>
	 
</p>

<p>
	ljones
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">18809</guid><pubDate>Sun, 15 Aug 2021 17:39:46 +0000</pubDate></item><item><title>Armbian on B860AV2.1-M with S905L3-B</title><link>https://forum.armbian.com/topic/18854-armbian-on-b860av21-m-with-s905l3-b/</link><description><![CDATA[<p>
	Looks like an interrupt was encountered during startup.This is the TTL startup log.
</p>

<p>
	 
</p>

<p>
	reading u-boot.ext<br />
	650183 bytes read in 376 ms (1.6 MiB/s)<br />
	## Starting application at 0x01000000 ...<br />
	[BL31]: tee size: 0<br />
	[BL31]: tee size: 0<br />
	[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]<br />
	[    0.000000] Linux version 5.9.0-arm-64 (root@vbox) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #20.10 SMP PREEMPT Wed Oct 14 12:04:42 MSK 2020<br />
	[    0.000000] Machine model: Amlogic Meson GXL (S905X) P212 Development Board<br />
	[    0.000000] efi: UEFI not found.<br />
	[    0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!<br />
	[    0.000000] Reserved memory: created CMA memory pool at 0x000000006b400000, size 256 MiB<br />
	[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool<br />
	[    0.000000] NUMA: No NUMA configuration found<br />
	[    0.000000] NUMA: Faking a node at [mem 0x0000000001000000-0x000000007fe5afff]<br />
	[    0.000000] NUMA: NODE_DATA [mem 0x7fa4c100-0x7fa4dfff]<br />
	[    0.000000] Zone ranges:<br />
	[    0.000000]   DMA      [mem 0x0000000001000000-0x000000003fffffff]<br />
	[    0.000000]   DMA32    [mem 0x0000000040000000-0x000000007fe5afff]<br />
	[    0.000000]   Normal   empty<br />
	[    0.000000] Movable zone start for each node<br />
	[    0.000000] Early memory node ranges<br />
	[    0.000000]   node   0: [mem 0x0000000001000000-0x0000000004ffffff]<br />
	[    0.000000]   node   0: [mem 0x0000000007300000-0x000000000fffffff]<br />
	[    0.000000]   node   0: [mem 0x0000000010200000-0x000000007fe5afff]<br />
	[    0.000000] Zeroed struct page in unavailable ranges: 421 pages<br />
	[    0.000000] Initmem setup node 0 [mem 0x0000000001000000-0x000000007fe5afff]<br />
	[    0.000000] psci: probing for conduit method from DT.<br />
	[    0.000000] psci: PSCIv0.2 detected in firmware.<br />
	[    0.000000] psci: Using standard PSCI v0.2 function IDs<br />
	[    0.000000] psci: Trusted OS migration not required<br />
	[    0.000000] percpu: Embedded 22 pages/cpu s51480 r8192 d30440 u90112<br />
	[    0.000000] Detected VIPT I-cache on CPU0<br />
	[    0.000000] CPU features: detected: ARM erratum 845719<br />
	[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 502177<br />
	[    0.000000] Policy zone: DMA32<br />
	[    0.000000] Kernel command line: root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0<br />
	[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)<br />
	[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)<br />
	[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off<br />
	[    0.000000] software IO TLB: mapped [mem 0x3bfff000-0x3ffff000] (64MB)<br />
	[    0.000000] Memory: 1634552K/2041196K available (16188K kernel code, 1308K rwdata, 6464K rodata, 3392K init, 927K bss, 144500K reserved, 262144K cma-reserved)<br />
	[    0.000000] random: get_random_u64 called from cache_random_seq_create+0x80/0x150 with crng_init=0<br />
	[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1<br />
	[    0.000000] rcu: Preemptible hierarchical RCU implementation.<br />
	[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.<br />
	[    0.000000]     Trampoline variant of Tasks RCU enabled.<br />
	[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.<br />
	[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4<br />
	[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0<br />
	[    0.000000] GIC: Using split EOI/Deactivate mode<br />
	[    0.000000] irq_meson_gpio: 110 to 8 <abbr title="General purpose input/output">gpio</abbr> interrupt mux initialized<br />
	[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).<br />
	[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns<br />
	[    0.000003] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns<br />
	[    0.000297] Console: colour dummy device 80x25<br />
	[    0.000723] printk: console [tty0] enabled<br />
	[    0.000826] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)<br />
	[    0.000847] pid_max: default: 32768 minimum: 301<br />
	[    0.000951] LSM: Security Framework initializing<br />
	[    0.001048] AppArmor: AppArmor initialized<br />
	[    0.001107] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)<br />
	[    0.001131] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)<br />
	[    0.002506] rcu: Hierarchical SRCU implementation.<br />
	[    0.003425] EFI services will not be available.<br />
	[    0.003714] smp: Bringing up secondary CPUs ...<br />
	[    0.004286] Detected VIPT I-cache on CPU1<br />
	[    0.004343] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]<br />
	[    0.004880] Detected VIPT I-cache on CPU2<br />
	[    0.004925] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]<br />
	[    0.005451] Detected VIPT I-cache on CPU3<br />
	[    0.005495] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]<br />
	[    0.005567] smp: Brought up 1 node, 4 CPUs<br />
	[    0.005632] SMP: Total of 4 processors activated.<br />
	[    0.005643] CPU features: detected: 32-bit EL0 Support<br />
	[    0.005655] CPU features: detected: CRC32 instructions<br />
	[    0.015524] CPU: All CPU(s) started at EL2<br />
	[    0.015585] alternatives: patching kernel code<br />
	[    0.016870] devtmpfs: initialized<br />
	[    0.022241] Registered cp15_barrier emulation handler<br />
	[    0.022272] Registered setend emulation handler<br />
	[    0.022287] KASLR disabled due to lack of seed<br />
	[    0.022635] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns<br />
	[    0.022669] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)<br />
	[    0.029768] xor: measuring software checksum speed<br />
	[    0.068166]    8regs     :  2373.000 MB/sec<br />
	[    0.108196]    32regs    :  2723.000 MB/sec<br />
	[    0.148236]    arm64_neon:  2310.000 MB/sec<br />
	[    0.148247] xor: using function: 32regs (2723.000 MB/sec)<br />
	[    0.148305] pinctrl core: initialized pinctrl subsystem<br />
	[    0.148844] DMI not present or invalid.<br />
	[    0.149333] NET: Registered protocol family 16<br />
	[    0.150896] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations<br />
	[    0.150963] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations<br />
	[    0.151105] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations<br />
	[    0.151209] audit: initializing netlink subsys (disabled)<br />
	[    0.151429] audit: type=2000 audit(0.148:1): state=initialized audit_enabled=0 res=1<br />
	[    0.152437] thermal_sys: Registered thermal governor 'step_wise'<br />
	[    0.152682] cpuidle: using governor ladder<br />
	[    0.152722] cpuidle: using governor menu<br />
	[    0.153052] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.<br />
	[    0.153143] ASID allocator initialised with 65536 entries<br />
	[    0.153919] Serial: AMBA PL011 UART driver<br />
	[    0.178703] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages<br />
	[    0.178729] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages<br />
	[    0.178742] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages<br />
	[    0.178754] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages<br />
	[    0.180578] cryptd: max_cpu_qlen set to 1000<br />
	[    0.248461] raid6: neonx8   gen()  2143 MB/s<br />
	[    0.316514] raid6: neonx8   xor()  1608 MB/s<br />
	[    0.384579] raid6: neonx4   gen()  2194 MB/s<br />
	[    0.452641] raid6: neonx4   xor()  1593 MB/s<br />
	[    0.520698] raid6: neonx2   gen()  2095 MB/s<br />
	[    0.588756] raid6: neonx2   xor()  1472 MB/s<br />
	[    0.656822] raid6: neonx1   gen()  1827 MB/s<br />
	[    0.724870] raid6: neonx1   xor()  1249 MB/s<br />
	[    0.792929] raid6: int64x8  gen()  1492 MB/s<br />
	[    0.860999] raid6: int64x8  xor()   784 MB/s<br />
	[    0.929033] raid6: int64x4  gen()  1666 MB/s<br />
	[    0.997089] raid6: int64x4  xor()   840 MB/s<br />
	[    1.065149] raid6: int64x2  gen()  1420 MB/s<br />
	[    1.133200] raid6: int64x2  xor()   730 MB/s<br />
	[    1.201251] raid6: int64x1  gen()  1059 MB/s<br />
	[    1.269322] raid6: int64x1  xor()   559 MB/s<br />
	[    1.269332] raid6: using algorithm neonx4 gen() 2194 MB/s<br />
	[    1.269341] raid6: .... xor() 1593 MB/s, rmw enabled<br />
	[    1.269351] raid6: using neon recovery algorithm<br />
	[    1.269859] ACPI: Interpreter disabled.<br />
	[    1.270993] iommu: Default domain type: Translated <br />
	[    1.271253] vgaarb: loaded<br />
	[    1.271849] SCSI subsystem initialized<br />
	[    1.272247] usbcore: registered new interface driver usbfs<br />
	[    1.272297] usbcore: registered new interface driver hub<br />
	[    1.272366] usbcore: registered new device driver usb<br />
	[    1.272767] pps_core: LinuxPPS API ver. 1 registered<br />
	[    1.272780] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti &lt;giometti@linux.it&gt;<br />
	[    1.272803] PTP clock support registered<br />
	[    1.272839] EDAC MC: Ver: 3.0.0<br />
	[    1.273677] FPGA manager framework<br />
	[    1.273775] Advanced Linux Sound Architecture Driver Initialized.<br />
	[    1.274312] NetLabel: Initializing<br />
	[    1.274328] NetLabel:  domain hash size = 128<br />
	[    1.274337] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO<br />
	[    1.274391] NetLabel:  unlabeled traffic allowed by default<br />
	[    1.274892] clocksource: Switched to clocksource arch_sys_counter<br />
	[    1.275156] VFS: Disk quotas dquot_6.6.0<br />
	[    1.275216] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)<br />
	[    1.275355] FS-Cache: Loaded<br />
	[    1.275829] AppArmor: AppArmor Filesystem Enabled<br />
	[    1.276433] pnp: PnP ACPI: disabled<br />
	[    1.281559] NET: Registered protocol family 2<br />
	[    1.282072] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)<br />
	[    1.282125] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)<br />
	[    1.282243] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)<br />
	[    1.282453] TCP: Hash tables configured (established 16384 bind 16384)<br />
	[    1.282611] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)<br />
	[    1.282666] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)<br />
	[    1.282873] NET: Registered protocol family 1<br />
	[    1.283361] RPC: Registered named UNIX socket transport module.<br />
	[    1.283384] RPC: Registered udp transport module.<br />
	[    1.283394] RPC: Registered tcp transport module.<br />
	[    1.283402] RPC: Registered tcp NFSv4.1 backchannel transport module.<br />
	[    1.283419] NET: Registered protocol family 44<br />
	[    1.283439] PCI: CLS 0 bytes, default 64<br />
	[    1.283623] Trying to unpack rootfs image as initramfs...<br />
	[    1.700498] Freeing initrd memory: 9776K<br />
	[    1.701400] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available<br />
	[    1.704821] Initialise system trusted keyrings<br />
	[    1.705015] workingset: timestamp_bits=44 max_order=19 bucket_order=0<br />
	[    1.709764] zbud: loaded<br />
	[    1.711142] squashfs: version 4.0 (2009/01/31) Phillip Lougher<br />
	[    1.711436] FS-Cache: Netfs 'nfs' registered for caching<br />
	[    1.711996] NFS: Registering the id_resolver key type<br />
	[    1.712032] Key type id_resolver registered<br />
	[    1.712042] Key type id_legacy registered<br />
	[    1.712128] nfs4filelayout_init: NFSv4 File Layout Driver Registering...<br />
	[    1.712141] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).<br />
	[    1.713122] FS-Cache: Netfs 'cifs' registered for caching<br />
	[    1.713417] Key type cifs.spnego registered<br />
	[    1.713439] Key type cifs.idmap registered<br />
	[    1.713463] ntfs: driver 2.1.32 [Flags: R/W].<br />
	[    1.714001] JFS: nTxBlock = 8192, nTxLock = 65536<br />
	[    1.718461] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled<br />
	[    1.720042] ocfs2: Registered cluster interface o2cb<br />
	[    1.720254] OCFS2 User DLM kernel interface loaded<br />
	[    1.721930] gfs2: GFS2 installed<br />
	[    1.759867] NET: Registered protocol family 38<br />
	[    1.759898] Key type asymmetric registered<br />
	[    1.759909] Asymmetric key parser 'x509' registered<br />
	[    1.759920] Asymmetric key parser 'pkcs8' registered<br />
	[    1.759973] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)<br />
	[    1.760146] io scheduler mq-deadline registered<br />
	[    1.760160] io scheduler kyber registered<br />
	[    1.760317] io scheduler bfq registered<br />
	[    1.773962] <abbr title="System On a Chip">soc</abbr> soc0: Amlogic Meson Unknown (Unknown) Revision 2a:e (c5:2) Detected<br />
	[    1.777868] Serial: 8250/16550 driver, 5 ports, IRQ sharing enabled<br />
	[    1.779754] Serial: AMBA driver<br />
	[    1.780130] c11084c0.serial: ttyAML6 at MMIO 0xc11084c0 (irq = 12, base_baud = 1500000) is a meson_uart<br />
	[    1.780296] serial serial0: tty port ttyAML6 registered<br />
	[    1.780687] c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 15, base_baud = 1500000) is a meson_uart<br />
	[    2.853887] printk: console [ttyAML0] enabled<br />
	[    2.871082] brd: module loaded<br />
	[    2.878828] loop: module loaded<br />
	[    2.879704] Loading iSCSI transport class v2.0-870.<br />
	[    2.881782] iscsi: registered transport (tcp)<br />
	[    2.889253] libphy: Fixed MDIO Bus: probed<br />
	[    2.891304] VFIO - User Level meta-driver version: 0.3<br />
	[    2.896039] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver<br />
	[    2.901145] ehci-pci: EHCI PCI platform driver<br />
	[    2.905573] ehci-platform: EHCI generic platform driver<br />
	[    2.910836] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver<br />
	[    2.916855] ohci-pci: OHCI PCI platform driver<br />
	[    2.921265] ohci-platform: OHCI generic platform driver<br />
	[    2.926876] usbcore: registered new interface driver usb-storage<br />
	[    2.932547] mousedev: PS/2 mouse device common for all mice<br />
	[    2.938787] i2c /dev entries driver<br />
	[    2.945048] sdhci: Secure Digital Host Controller Interface driver<br />
	[    2.947475] sdhci: Copyright(c) Pierre Ossman<br />
	[    2.951981] Synopsys Designware Multimedia Card Interface Driver<br />
	[    2.971820] meson-gx-mmc d0072000.mmc: Got CD <abbr title="General purpose input/output">GPIO</abbr><br />
	[    2.999412] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq<br />
	[    3.027321] sdhci-pltfm: SDHCI platform and OF driver helper<br />
	[    3.028283] ledtrig-cpu: registered to indicate activity on CPUs<br />
	[    3.033941] meson-sm: secure-monitor enabled<br />
	[    3.038391] gxl-crypto c883e000.crypto: will run requests pump with realtime priority<br />
	[    3.045428] gxl-crypto c883e000.crypto: will run requests pump with realtime priority<br />
	[    3.053514] hid: raw HID events driver (C) Jiri Kosina<br />
	[    3.058489] usbcore: registered new interface driver usbhid<br />
	[    3.063707] usbhid: USB HID core driver<br />
	[    3.068266] platform-mhu c883c404.mailbox: Platform MHU Mailbox registered<br />
	[BL31]: tee size: 0<br />
	[    3.079012] no UART detected at 0x1<br />
	[    3.083501] NET: Registered protocol family 17<br />
	[    3.084215] Key type dns_resolver registered<br />
	[    3.088690] registered taskstats version 1<br />
	[    3.092268] Loading compiled-in X.509 certificates<br />
	[    3.097252] zswap: loaded using pool lzo/zbud<br />
	[    3.101604] Key type ._fscrypt registered<br />
	[    3.105248] Key type .fscrypt registered<br />
	[    3.109119] Key type fscrypt-provisioning registered<br />
	[    3.114829] Btrfs loaded, crc32c=crc32c-generic<br />
	[    3.116964] mmc1: new HS200 MMC card at address 0001<br />
	[    3.124271] mmcblk1: mmc1:0001 Y1P008 7.28 GiB <br />
	[    3.128360] mmcblk1boot0: mmc1:0001 Y1P008 partition 1 4.00 MiB<br />
	[    3.134225] mmcblk1boot1: mmc1:0001 Y1P008 partition 2 4.00 MiB<br />
	[    3.137640] Key type encrypted registered<br />
	[    3.139939] mmcblk1rpmb: mmc1:0001 Y1P008 partition 3 4.00 MiB, chardev (241:0)<br />
	[    3.143648] AppArmor: AppArmor sha1 policy hashing enabled<br />
	[    3.172621] meson-drm d0100000.<abbr title="Video processing unit (encoding/decoding)">vpu</abbr>: Queued 3 outputs on <abbr title="Video processing unit (encoding/decoding)">vpu</abbr><br />
	[    3.198943] meson-dw-hdmi c883a000.hdmi-tx: Unsupported HDMI controller (0d0d:0d:0d)<br />
	[    3.201222] ------------[ cut here ]------------<br />
	[    3.205633] WARNING: CPU: 3 PID: 33 at drivers/regulator/core.c:2089 _regulator_put.part.0+0x154/0x160<br />
	[    3.214847] Modules linked in:<br />
	[    3.217869] CPU: 3 PID: 33 Comm: kworker/3:1 Not tainted 5.9.0-arm-64 #20.10<br />
	[    3.224852] Hardware name: Amlogic Meson GXL (S905X) P212 Development Board (DT)<br />
	[    3.232192] Workqueue: events deferred_probe_work_func<br />
	[    3.237274] pstate: 80000005 (Nzcv daif -PAN -UAO BTYPE=--)<br />
	[    3.242794] pc : _regulator_put.part.0+0x154/0x160<br />
	[    3.247537] lr : regulator_put+0x38/0x50<br />
	[    3.251416] sp : ffff800010143930<br />
	[    3.254694] x29: ffff800010143930 x28: ffff800012a07000 <br />
	[    3.259955] x27: ffff80001010bcd8 x26: 00000000ffffffed <br />
	[    3.265216] x25: ffff00007f325480 x24: ffff00006974d000 <br />
	[    3.270477] x23: 0000000000000010 x22: ffff8000101439e8 <br />
	[    3.275739] x21: ffff00007f279c00 x20: ffff800012ad7150 <br />
	[    3.281000] x19: ffff00007f324900 x18: 0000000000000010 <br />
	[    3.286261] x17: 0000000000006a0c x16: 000000000000698c <br />
	[    3.291522] x15: 00000b4b011a0adc x14: 00000000000002d7 <br />
	[    3.296783] x13: 000000000000032b x12: 0000000000000001 <br />
	[    3.302045] x11: 0000000000000002 x10: 00000000000009c0 <br />
	[    3.307306] x9 : ffff800010143760 x8 : ffff00007f27a620 <br />
	[    3.312567] x7 : ffff00007f279c00 x6 : 0000000000000000 <br />
	[    3.317828] x5 : ffff000069b12a1c x4 : 0000000000000000 <br />
	[    3.323090] x3 : ffff800012ad7520 x2 : ffff00007f279c00 <br />
	[    3.328351] x1 : 0000000000000000 x0 : 0000000000000001 <br />
	[    3.333613] Call trace:<br />
	[    3.336031]  _regulator_put.part.0+0x154/0x160<br />
	[    3.340428]  regulator_put+0x38/0x50<br />
	[    3.343967]  devm_regulator_release+0x14/0x20<br />
	[    3.348279]  release_nodes+0x1b0/0x228<br />
	[    3.351986]  devres_release_group+0x90/0xe8<br />
	[    3.356126]  component_bind_all+0x114/0x260<br />
	[    3.360267]  meson_drv_bind_master+0x364/0x488<br />
	[    3.364664]  meson_drv_bind+0x14/0x28<br />
	[    3.368287]  try_to_bring_up_master+0x168/0x1d0<br />
	[    3.372772]  component_master_add_with_match+0xb4/0x100<br />
	[    3.377947]  meson_drv_probe+0xd4/0x128<br />
	[    3.381742]  platform_drv_probe+0x54/0xa8<br />
	[    3.385709]  really_probe+0xe4/0x3b0<br />
	[    3.389245]  driver_probe_device+0x58/0xb8<br />
	[    3.393299]  __device_attach_driver+0x84/0xc8<br />
	[    3.397613]  bus_for_each_drv+0x78/0xc8<br />
	[    3.401406]  __device_attach+0xf0/0x150<br />
	[    3.405202]  device_initial_probe+0x14/0x20<br />
	[    3.409342]  bus_probe_device+0x9c/0xa8<br />
	[    3.413137]  deferred_probe_work_func+0x74/0xb0<br />
	[    3.417625]  process_one_work+0x1a0/0x328<br />
	[    3.421589]  worker_thread+0x1f8/0x420<br />
	[    3.425300]  kthread+0x140/0x160<br />
	[    3.428491]  ret_from_fork+0x10/0x34<br />
	[    3.432025] ---[ end trace 014dcf72c59e749d ]---<br />
	[    3.436789] meson-drm d0100000.<abbr title="Video processing unit (encoding/decoding)">vpu</abbr>: failed to bind c883a000.hdmi-tx (ops meson_dw_hdmi_ops): -19<br />
	[    3.445329] meson-drm d0100000.<abbr title="Video processing unit (encoding/decoding)">vpu</abbr>: Couldn't bind all components<br />
	[    3.451558] meson-drm d0100000.<abbr title="Video processing unit (encoding/decoding)">vpu</abbr>: master bind failed: -19<br />
	[    3.458691] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found<br />
	[    3.463391] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found<br />
	[    3.469564] meson8b-dwmac c9410000.ethernet: PTP uses main clock<br />
	[    3.475419] meson8b-dwmac c9410000.ethernet: no reset control found<br />
	[    3.482347] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37<br />
	[    3.488760] meson8b-dwmac c9410000.ethernet:     DWMAC1000<br />
	[    3.493875] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported<br />
	[    3.501292] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported<br />
	[    3.508709] meson8b-dwmac c9410000.ethernet: COE Type 2<br />
	[    3.513882] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported<br />
	[    3.520868] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported<br />
	[    3.527328] meson8b-dwmac c9410000.ethernet: Normal descriptors<br />
	[    3.533119] meson8b-dwmac c9410000.ethernet: Ring mode enabled<br />
	[    3.538896] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer<br />
	[    3.547244] libphy: stmmac: probed<br />
	[    3.551570] dwc3-meson-g12a d0078080.usb: USB2 ports: 2<br />
	[    3.555388] dwc3-meson-g12a d0078080.usb: USB3 ports: 0<br />
	[    4.095936] dwc2 c9100000.usb: supply vusb_d not found, using dummy regulator<br />
	[    4.097582] dwc2 c9100000.usb: supply vusb_a not found, using dummy regulator<br />
	[    4.104769] dwc2 c9100000.usb: EPs: 7, dedicated fifos, 712 entries in SPRAM<br />
	[    4.113148] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller<br />
	[    4.116990] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1<br />
	[    4.124670] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f664 hci version 0x100 quirks 0x0000000002010010<br />
	[    4.133884] xhci-hcd xhci-hcd.0.auto: irq 42, io mem 0xc9000000<br />
	[    4.140001] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.09<br />
	[    4.147904] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[    4.155058] usb usb1: Product: xHCI Host Controller<br />
	[    4.159888] usb usb1: Manufacturer: Linux 5.9.0-arm-64 xhci-hcd<br />
	[    4.165752] usb usb1: SerialNumber: xhci-hcd.0.auto<br />
	[    4.171096] hub 1-0:1.0: USB hub found<br />
	[    4.174311] hub 1-0:1.0: 2 ports detected<br />
	[    4.178553] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller<br />
	[    4.183719] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2<br />
	[    4.191294] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed<br />
	[    4.197800] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.<br />
	[    4.205877] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.09<br />
	[    4.213970] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[    4.221126] usb usb2: Product: xHCI Host Controller<br />
	[    4.225955] usb usb2: Manufacturer: Linux 5.9.0-arm-64 xhci-hcd<br />
	[    4.231820] usb usb2: SerialNumber: xhci-hcd.0.auto<br />
	[    4.237098] hub 2-0:1.0: USB hub found<br />
	[    4.240389] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)<br />
	[    4.249999] meson-gx-mmc d0070000.mmc: allocated mmc-pwrseq<br />
	[    4.281059] scpi_protocol scpi: SCP Protocol legacy pre-1.0 firmware<br />
	g[    4.285886] meson-gx-mmc d0070000.mmc: no support for card's volts<br />
	[    4.288014] mmc2: error -22 whilst initialising SDIO card<br />
	et_dvfs_info 002b<br />
	[    4.309444] simple-framebuffer 7fe5b000.framebuffer: framebuffer at 0x7fe5b000, 0x195000 bytes, mapped to 0x(____ptrval____)<br />
	[    4.315076] simple-framebuffer 7fe5b000.framebuffer: format=x8r8g8b8, mode=720x576x32, linelength=2880<br />
	[    4.329817] Console: switching to colour frame buffer device 90x36<br />
	[    4.335109] simple-framebuffer 7fe5b000.framebuffer: fb0: simplefb registered!<br />
	[    4.343255] libphy: mdio_mux: probed<br />
	[    4.354147] libphy: mdio_mux: probed<br />
	[    4.356373] printk: console [netcon0] enabled<br />
	[    4.356495] netconsole: network logging started<br />
	[    4.363272] ALSA device list:<br />
	[    4.366700]   No soundcards found.<br />
	[    4.371641] Freeing unused kernel memory: 3392K<br />
	[    4.395211] Run /init as init process<br />
	[    4.510993] usb 1-2: new high-speed USB device number 2 using xhci-hcd<br />
	[    4.667508] usb 1-2: New USB device found, idVendor=05e3, idProduct=0723, bcdDevice=94.54<br />
	[    4.675234] usb 1-2: New USB device strings: Mfr=3, Product=4, SerialNumber=2<br />
	[    4.691234] usb 1-2: Product: USB Storage<br />
	[    4.693841] usb 1-2: Manufacturer: Generic <br />
	[    4.696434] usb 1-2: SerialNumber: 000000009454<br />
	[    4.702373] usb-storage 1-2:1.0: USB Mass Storage device detected<br />
	[    4.708033] scsi host0: usb-storage 1-2:1.0<br />
	[    4.739959] usbcore: registered new interface driver uas<br />
	[    4.843513] mmc1: tuning execution failed: -5<br />
	[    4.846820] mmc1: tuning execution failed: -5<br />
	[    4.850470] mmc1: tuning execution failed: -5<br />
	[    4.942738] mmc1: tuning execution failed: -5<br />
	[    4.953768] mmc1: tried to HW reset card, got error -5<br />
	[    4.957915] random: fast init done<br />
	[    4.960833] blk_update_request: I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0<br />
	[    5.068676] mmc1: tuning execution failed: -5<br />
	[    5.076918] mmc1: tried to HW reset card, got error -5<br />
	[    5.081092] blk_update_request: I/O error, dev mmcblk1, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0<br />
	[    5.188017] mmc1: tuning execution failed: -5<br />
	[    5.196594] mmc1: tried to HW reset card, got error -5<br />
	[    5.200915] blk_update_request: I/O error, dev mmcblk1, sector 9 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0<br />
	[    5.200948] blk_update_request: I/O error, dev mmcblk1, sector 10 op 0x0:(READ) flags 0x0 phys_seg 6 prio class 0<br />
	[    5.210470] Buffer I/O error on dev mmcblk1, logical block 9, async page read<br />
	[    5.227786] Buffer I/O error on dev mmcblk1, logical block 10, async page read<br />
	[    5.234871] Buffer I/O error on dev mmcblk1, logical block 11, async page read<br />
	[    5.242097] Buffer I/O error on dev mmcblk1, logical block 12, async page read<br />
	[    5.249186] Buffer I/O error on dev mmcblk1, logical block 13, async page read<br />
	[    5.256415] Buffer I/O error on dev mmcblk1, logical block 14, async page read<br />
	[    5.263503] Buffer I/O error on dev mmcblk1, logical block 15, async page read<br />
	[    5.378290] mmc1: tuning execution failed: -5<br />
	[    5.383582] mmc1: tried to HW reset card, got error -5<br />
	[    5.485759] mmc1: tuning execution failed: -5<br />
	[    5.494326] mmc1: tried to HW reset card, got error -5<br />
	[    5.498517] blk_update_request: I/O error, dev mmcblk1boot0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0<br />
	[    5.509407] blk_update_request: I/O error, dev mmcblk1boot1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0<br />
	[    5.521989] blk_update_request: I/O error, dev mmcblk1boot0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0<br />
	[    5.522261] blk_update_request: I/O error, dev mmcblk1boot0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0<br />
	[    5.532201] Buffer I/O error on dev mmcblk1boot0, logical block 0, async page read<br />
	[    5.550216] Buffer I/O error on dev mmcblk1boot0, logical block 1, async page read<br />
	[    5.557783] Buffer I/O error on dev mmcblk1boot0, logical block 2, async page read<br />
	[    5.567337] blk_update_request: I/O error, dev mmcblk1boot1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0<br />
	[    5.567538] blk_update_request: I/O error, dev mmcblk1boot1, sector 1 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 0<br />
	[    5.731217] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9454 PQ: 0 ANSI: 0<br />
	[    5.744982] sd 0:0:0:0: Attached scsi generic sg0 type 0<br />
	[    5.756644] mmc1: tuning execution failed: -5<br />
	[    5.759482] mmc1: tried to HW reset card, got error -5<br />
	[    5.851953] sd 0:0:0:0: [sda] 30785536 512-byte logical blocks: (15.8 GB/14.7 GiB)<br />
	[    5.862491] mmc1: tuning execution failed: -5<br />
	[    5.865457] sd 0:0:0:0: [sda] Write Protect is off<br />
	[    5.868936] mmc1: tried to HW reset card, got error -5<br />
	[    5.879573] sd 0:0:0:0: [sda] No Caching mode page found<br />
	[    5.884156] sd 0:0:0:0: [sda] Assuming drive cache: write through<br />
	[    5.917959]  sda: sda1 sda2<br />
	[    5.932289] sd 0:0:0:0: [sda] Attached SCSI removable disk<br />
	[    6.048871] mmc1: tuning execution failed: -5<br />
	[    6.052330] mmc1: tried to HW reset card, got error -5<br />
	[    6.152616] mmc1: tuning execution failed: -5<br />
	[    6.159164] mmc1: tried to HW reset card, got error -5<br />
	[    6.680812] EXT4-fs (sda2): mounted filesystem with writeback data mode. Opts: data=writeback<br />
	[    7.587906] systemd[1]: System time before build time, advancing clock.<br />
	[    7.700177] NET: Registered protocol family 10<br />
	[    7.734427] Segment Routing with IPv6<br />
	[    7.781966] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)<br />
	[    7.816263] systemd[1]: Detected architecture arm64.<br />
	[    7.865889] systemd[1]: Set hostname to &lt;arm-64&gt;.<br />
	[    8.336479] systemd[1]: /etc/systemd/system/serial-getty@.service.d/override.conf:5: Unknown lvalue 'After' in section 'Service', ignoring<br />
	[    8.353745] systemd[1]: /etc/systemd/system/serial-getty@.service.d/override.conf:5: Unknown lvalue 'After' in section 'Service', ignoring<br />
	[    8.371894] systemd[1]: /etc/systemd/system/getty@.service.d/override.conf:5: Unknown lvalue 'After' in section 'Service', ignoring<br />
	[    8.464881] random: systemd: uninitialized urandom read (16 bytes read)<br />
	[    8.477169] random: systemd: uninitialized urandom read (16 bytes read)<br />
	[    8.481130] systemd[1]: Reached target System Time Synchronized.<br />
	[    8.490569] random: systemd: uninitialized urandom read (16 bytes read)<br />
	[    8.497856] systemd[1]: Created slice system-systemd\x2dfsck.slice.<br />
	[    8.504925] systemd[1]: Reached target Swap.<br />
	[    8.511367] systemd[1]: Started Forward Password Requests to Wall Directory Watch.<br />
	[    8.718019] EXT4-fs (sda2): re-mounted. Opts: commit=600,errors=remount-ro<br />
	[    9.663661] SError Interrupt on CPU3, code 0xbf000002 -- SError<br />
	[    9.663665] CPU: 3 PID: 357 Comm: systemd-udevd Tainted: G        WC        5.9.0-arm-64 #20.10<br />
	[    9.663668] Hardware name: Amlogic Meson GXL (S905X) P212 Development Board (DT)<br />
	[    9.663669] pstate: 00000005 (nzcv daif -PAN -UAO BTYPE=--)<br />
	[    9.663671] pc : el1_sync_handler+0xf8/0x130<br />
	[    9.663672] lr : el1_sync+0x7c/0x100<br />
	[    9.663673] sp : ffff8000103ab750<br />
	[    9.663675] x29: ffff8000103ab750 x28: ffff000068401c00 <br />
	[    9.663678] x27: 0000000000000100 x26: 0000000000000000 <br />
	[    9.663681] x25: 0000000000000001 x24: ffff80000a230270 <br />
	[    9.663685] x23: 0000000080000005 x22: ffff80000a225f08 <br />
	[    9.663688] x21: ffff8000103ab8a0 x20: 0000ffffffffffff <br />
	[    9.663691] x19: ffff00006acf6148 x18: 0000000000000001 <br />
	[    9.663694] x17: 0000000000000001 x16: 0000000000000019 <br />
	[    9.663697] x15: ffff000068402068 x14: ffffffffffffffff <br />
	[    9.663700] x13: 0000000000000000 x12: 0101010101010101 <br />
	[    9.663704] x11: 0000000000000040 x10: ffff800012a37ef8 <br />
	[    9.663707] x9 : ffff800012a37ef0 x8 : ffff00007cc026f0 <br />
	[    9.663710] x7 : 0000000000000000 x6 : 0000000000000000 <br />
	[    9.663713] x5 : ffff00007cc026c8 x4 : ffff800010c06000 <br />
	[    9.663716] x3 : 0000000096000210 x2 : 0000002200000000 <br />
	[    9.663719] x1 : 0000000000000000 x0 : ffff8000103ab760 <br />
	[    9.663723] Kernel panic - not syncing: Asynchronous SError Interrupt<br />
	[    9.663726] CPU: 3 PID: 357 Comm: systemd-udevd Tainted: G        WC        5.9.0-arm-64 #20.10<br />
	[    9.663728] Hardware name: Amlogic Meson GXL (S905X) P212 Development Board (DT)<br />
	[    9.663729] Call trace:<br />
	[    9.663730]  dump_backtrace+0x0/0x1a0<br />
	[    9.663731]  show_stack+0x18/0x28<br />
	[    9.663732]  dump_stack+0xc0/0x11c<br />
	[    9.663734]  panic+0x15c/0x31c<br />
	[    9.663735]  nmi_panic+0x8c/0x90<br />
	[    9.663737]  arm64_serror_panic+0x78/0x84<br />
	[    9.663738]  do_serror+0x78/0x180<br />
	[    9.663739]  el1_error+0x8c/0x108<br />
	[    9.663741]  el1_sync_handler+0xf8/0x130<br />
	[    9.663742]  el1_sync+0x7c/0x100<br />
	[    9.663744]  lima_mmu_init+0x40/0x118 [lima]<br />
	[    9.663745]  lima_device_init+0x1b8/0x5f0 [lima]<br />
	[    9.663746]  lima_pdev_probe+0xa0/0x190 [lima]<br />
	[    9.663748]  platform_drv_probe+0x54/0xa8<br />
	[    9.663749]  really_probe+0xe4/0x3b0<br />
	[    9.663751]  driver_probe_device+0x58/0xb8<br />
	[    9.663752]  device_driver_attach+0x74/0x80<br />
	[    9.663753]  __driver_attach+0x58/0xe0<br />
	[    9.663755]  bus_for_each_dev+0x70/0xc0<br />
	[    9.663756]  driver_attach+0x24/0x30<br />
	[    9.663757]  bus_add_driver+0x14c/0x1f0<br />
	[    9.663759]  driver_register+0x64/0x120<br />
	[    9.663760]  __platform_driver_register+0x48/0x58<br />
	[    9.663762]  lima_platform_driver_init+0x24/0x1000 [lima]<br />
	[    9.663763]  do_one_initcall+0x54/0x1bc<br />
	[    9.663764]  do_init_module+0x54/0x200<br />
	[    9.663766]  load_module+0x1de8/0x23f0<br />
	[    9.663767]  __do_sys_finit_module+0xd8/0xf0<br />
	[    9.663769]  __arm64_sys_finit_module+0x20/0x30<br />
	[    9.663770]  el0_svc_common.constprop.0+0x74/0x1f0<br />
	[    9.663771]  do_el0_svc+0x24/0x90<br />
	[    9.663773]  el0_sync_handler+0x180/0x2f8<br />
	[    9.663774]  el0_sync+0x158/0x180<br />
	[    9.663793] SMP: stopping secondary CPUs<br />
	[    9.663794] Kernel Offset: disabled<br />
	[    9.663796] CPU features: 0x0040002,20002004<br />
	[    9.663797] Memory Limit: none
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	In the Android system can know the <abbr title="Device tree blob">dtb</abbr> file is gxlx2_p291_2g.I extracted the <abbr title="Device tree blob">DTB</abbr> file and put it into the <abbr title="Device tree blob">DTB</abbr> folder. It doesn't seem to start.
</p>
]]></description><guid isPermaLink="false">18854</guid><pubDate>Fri, 27 Aug 2021 10:59:39 +0000</pubDate></item><item><title>Cards on the table: Which boxes have working WiFi?</title><link>https://forum.armbian.com/topic/18843-cards-on-the-table-which-boxes-have-working-wifi/</link><description><![CDATA[<p>
	I figured I’d start a generic chat for this as I’m sure I’m not the only one who wants to know other peoples experiences on this. <br />
	 
</p>

<p>
	I’ve bought and run armbian on a number of boxes (x96, Trongle, a95x) and always run into the same problem, WiFi. I know I am not the only one and I know the reasoning behind it (too many chips to support)
</p>

<p>
	<br />
	But…
</p>

<p>
	 
</p>

<p>
	Has anyone got a build working with WiFi support? Ideally on a board less than $50? <br />
	 
</p>

<p>
	Amlogic, Rockchip, anything? <br />
	 
</p>

<p>
	I’ve never failed to get other aspects working, except WiFi (and Bluetooth) 
</p>

<p>
	 
</p>

<p>
	I know it must be possible, Android builds never seem to fail with WiFi support. <br />
	 
</p>

<p>
	Any feedback is much appreciated. <br />
	 
</p>

<p>
	thank you. 
</p>
]]></description><guid isPermaLink="false">18843</guid><pubDate>Wed, 25 Aug 2021 15:17:33 +0000</pubDate></item><item><title>Armbian on CloudnetGo CR19 RK3399 TV Box</title><link>https://forum.armbian.com/topic/18842-armbian-on-cloudnetgo-cr19-rk3399-tv-box/</link><description><![CDATA[<p>
	CloudnetGo CR19 (http://www.cloudnetgo.com/productinfo/138177.html)
</p>

<p>
	 
</p>

<p>
	Has anyone dealt with this device? Is it possible to install Armbian on it?<br />
	Which of the supported boards can this device be compatible with?
</p>

<p>
	Can any of the supported build configurations be used for this device? Or is it possible to install any of the prebuilt assemblies?
</p>
]]></description><guid isPermaLink="false">18842</guid><pubDate>Wed, 25 Aug 2021 11:48:12 +0000</pubDate></item><item><title>Dead TV box, what do you make out of this log (Tanix TX3 S905X3 4/64)</title><link>https://forum.armbian.com/topic/18465-dead-tv-box-what-do-you-make-out-of-this-log-tanix-tx3-s905x3-464/</link><description><![CDATA[<p>
	Short Story , dead TV box...no Leds,Lights,output...nothing...but serial console works
</p>

<p>
	Any idea of what is wrong
</p>

<p>
	=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.10.06 13:20:30 =~=~=~=~=~=~=~=~=~=~=~=<br />
	SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;<abbr title="embedded MultiMediaCard">EMMC</abbr>:0;READ:0;0.0;CHK:0;<br />
	bl2_stage_init 0x01<br />
	bl2_stage_init 0x81<br />
	hw id: 0x0001 - pwm id 0x00<br />
	bl2_stage_init 0xc0<br />
	bl2_stage_init 0x02
</p>

<p>
	L0:00000000<br />
	L1:00000703<br />
	L2:00008067<br />
	L3:15000020<br />
	S1:00000000<br />
	B2:20282000<br />
	B1:a0f83180
</p>

<p>
	TE: 135603
</p>

<p>
	BL2 Built : 14:57:11, Sep  1 2020. g12a g3c95fed - gongwei.chen@droid11-sz
</p>

<p>
	Board ID = 1<br />
	Set cpu clk to 24M<br />
	Set clk81 to 24M<br />
	Use GP1_pll as DSU clk.<br />
	DSU clk: 1200 Mhz<br />
	CPU clk: 1200 MHz<br />
	Set clk81 to 166.6M<br />
	<abbr title="embedded MultiMediaCard">eMMC</abbr> boot @ 0<br />
	sw8 s<br />
	board id: 1<br />
	Load FIP HDR DDR from <abbr title="embedded MultiMediaCard">eMMC</abbr>, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0<br />
	fw parse done<br />
	PIEI prepare done<br />
	00000000<br />
	<abbr title="embedded MultiMediaCard">emmc</abbr> switch 1 ok<br />
	ddr saved addr:00016000<br />
	Load ddr parameter from <abbr title="embedded MultiMediaCard">eMMC</abbr>, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0<br />
	00000000<br />
	<abbr title="embedded MultiMediaCard">emmc</abbr> switch 0 ok<br />
	fastboot data verify<br />
	result: 255<br />
	Cfg max: 12, cur: 1. Board id: 255. Force loop cfg<br />
	DDR4 probe
</p>

<p>
	LPDDR4_PHY_V_0_1_22-Built : 14:57:16, Sep  1 2020. g12a g3c95fed - gongwei.chen@droid11-sz<br />
	ddr clk to 1320MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 2. Board id: 255. Force loop cfg<br />
	DDR4 probe<br />
	ddr clk to 1320MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 3. Board id: 255. Force loop cfg<br />
	DDR3 probe<br />
	ddr clk to 648MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 4. Board id: 255. Force loop cfg<br />
	DDR3 probe<br />
	ddr clk to 648MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 5. Board id: 255. Force loop cfg<br />
	LPDDR4 probe<br />
	ddr clk to 912MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 6. Board id: 255. Force loop cfg<br />
	LPDDR4 probe<br />
	ddr clk to 912MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 7. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 8. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 9. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 10. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 11. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 12. Bo SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;<abbr title="embedded MultiMediaCard">EMMC</abbr>:0;READ:0;0.0;CHK:0;<br />
	bl2_stage_init 0x01<br />
	bl2_stage_init 0x81<br />
	hw id: 0x0001 - pwm id 0x00<br />
	bl2_stage_init 0xc0<br />
	bl2_stage_init 0x02
</p>

<p>
	L0:00000000<br />
	L1:00000703<br />
	L2:00008067<br />
	L3:15000020<br />
	S1:00000000<br />
	B2:20282000<br />
	B1:a0f83180
</p>

<p>
	TE: 130693
</p>

<p>
	BL2 Built : 14:57:11, Sep  1 2020. g12a g3c95fed - gongwei.chen@droid11-sz
</p>

<p>
	Board ID = 1<br />
	Set cpu clk to 24M<br />
	Set clk81 to 24M<br />
	Use GP1_pll as DSU clk.<br />
	DSU clk: 1200 Mhz<br />
	CPU clk: 1200 MHz<br />
	Set clk81 to 166.6M<br />
	<abbr title="embedded MultiMediaCard">eMMC</abbr> boot @ 0<br />
	sw8 s<br />
	board id: 1<br />
	Load FIP HDR DDR from <abbr title="embedded MultiMediaCard">eMMC</abbr>, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0<br />
	fw parse done<br />
	PIEI prepare done<br />
	00000000<br />
	<abbr title="embedded MultiMediaCard">emmc</abbr> switch 1 ok<br />
	ddr saved addr:00016000<br />
	Load ddr parameter from <abbr title="embedded MultiMediaCard">eMMC</abbr>, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0<br />
	00000000<br />
	<abbr title="embedded MultiMediaCard">emmc</abbr> switch 0 ok<br />
	fastboot data verify<br />
	result: 255<br />
	Cfg max: 12, cur: 1. Board id: 255. Force loop cfg<br />
	DDR4 probe
</p>

<p>
	LPDDR4_PHY_V_0_1_22-Built : 14:57:16, Sep  1 2020. g12a g3c95fed - gongwei.chen@droid11-sz<br />
	ddr clk to 1320MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 2. Board id: 255. Force loop cfg<br />
	DDR4 probe<br />
	ddr clk to 1320MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 3. Board id: 255. Force loop cfg<br />
	DDR3 probe<br />
	ddr clk to 648MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 4. Board id: 255. Force loop cfg<br />
	DDR3 probe<br />
	ddr clk to 648MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 5. Board id: 255. Force loop cfg<br />
	LPDDR4 probe<br />
	ddr clk to 912MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 6. Board id: 255. Force loop cfg<br />
	LPDDR4 probe<br />
	ddr clk to 912MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 7. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 8. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 9. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 10. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 11. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 12. Board id: 0. not match..skip..<br />
	All ddr config failed...<br />
	Reset...<br />
	boot times 0SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;<abbr title="embedded MultiMediaCard">EMMC</abbr>:0;READ:0;0.0;CHK:0;<br />
	bl2_stage_init 0x01<br />
	bl2_stage_init 0x81<br />
	hw id: 0x0001 - pwm id 0x00<br />
	bl2_stage_init 0xc0<br />
	bl2_stage_init 0x02
</p>

<p>
	L0:00000000<br />
	L1:00000703<br />
	L2:00008067<br />
	L3:15000020<br />
	S1:00000000<br />
	B2:20282000<br />
	B1:a0f83180
</p>

<p>
	TE: 135021
</p>

<p>
	BL2 Built : 14:57:11, Sep  1 2020. g12a g3c95fed - gongwei.chen@droid11-sz
</p>

<p>
	Board ID = 1<br />
	Set cpu clk to 24M<br />
	Set clk81 to 24M<br />
	Use GP1_pll as DSU clk.<br />
	DSU clk: 1200 Mhz<br />
	CPU clk: 1200 MHz<br />
	Set clk81 to 166.6M<br />
	<abbr title="embedded MultiMediaCard">eMMC</abbr> boot @ 0<br />
	sw8 s<br />
	board id: 1<br />
	Load FIP HDR DDR from <abbr title="embedded MultiMediaCard">eMMC</abbr>, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0<br />
	fw parse done<br />
	PIEI prepare done<br />
	00000000<br />
	<abbr title="embedded MultiMediaCard">emmc</abbr> switch 1 ok<br />
	ddr saved addr:00016000<br />
	Load ddr parameter from <abbr title="embedded MultiMediaCard">eMMC</abbr>, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0<br />
	00000000<br />
	<abbr title="embedded MultiMediaCard">emmc</abbr> switch 0 ok<br />
	fastboot data verify<br />
	result: 255<br />
	Cfg max: 12, cur: 1. Board id: 255. Force loop cfg<br />
	DDR4 probe
</p>

<p>
	LPDDR4_PHY_V_0_1_22-Built : 14:57:16, Sep  1 2020. g12a g3c95fed - gongwei.chen@droid11-sz<br />
	ddr clk to 1320MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 2. Board id: 255. Force loop cfg<br />
	DDR4 probe<br />
	ddr clk to 1320MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 3. Board id: 255. Force loop cfg<br />
	DDR3 probe<br />
	ddr clk to 648MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 4. Board id: 255. Force loop cfg<br />
	DDR3 probe<br />
	ddr clk to 648MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : End of read enable training<br />
	INFO : End of fine write leveling<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 5. Board id: 255. Force loop cfg<br />
	LPDDR4 probe<br />
	ddr clk to 912MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 6. Board id: 255. Force loop cfg<br />
	LPDDR4 probe<br />
	ddr clk to 912MHz
</p>

<p>
	dmc_version 0001<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : ERROR : Training has failed!<br />
	Check phy result<br />
	INFO : End of initialization<br />
	INFO : ERROR : Training has failed!<br />
	1D training failed<br />
	Cfg max: 12, cur: 7. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 8. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 9. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 10. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 11. Board id: 0. not match..skip..<br />
	Cfg max: 12, cur: 12. Board id: 0. not match..skip..<br />
	All ddr config failed...<br />
	Reset...<br />
	boot times 0
</p>
]]></description><guid isPermaLink="false">18465</guid><pubDate>Wed, 23 Jun 2021 08:26:32 +0000</pubDate></item><item><title>Why stop at u-boot ?</title><link>https://forum.armbian.com/topic/18753-why-stop-at-u-boot/</link><description><![CDATA[<p>
	I am playing with X96 Max+ and it always stops at u-boot if its uart port is not connected . It is said that there is interference from uart port thus u-boot thinks it has received commands. Is that true ?
</p>
]]></description><guid isPermaLink="false">18753</guid><pubDate>Wed, 04 Aug 2021 21:57:16 +0000</pubDate></item><item><title>H96 Max X3 - brcmfmac: brcmf_chip_cores_check: CPU core not detected</title><link>https://forum.armbian.com/topic/18695-h96-max-x3-brcmfmac-brcmf_chip_cores_check-cpu-core-not-detected/</link><description><![CDATA[<p>
	Hello everyone,
</p>

<p>
	 
</p>

<p>
	I am not having any luck with the wifi on the H96 Max X3.
</p>

<p>
	I see posts saying the wifi on this box work with meson-sm1-sei610-ethfix.<abbr title="Device tree blob">dtb</abbr> /  meson-sm1-H96max-X3.<abbr title="Device tree blob">dtb</abbr> or h96max-x2-test-bus80-<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>-volt.<abbr title="Device tree blob">dtb</abbr> but they are not working for me.
</p>

<p>
	I did put the BCM4335C0.hcd in /lib/firmware/brcm and the driver apparently loaded.
</p>

<p>
	 
</p>

<p>
	Everything else seems to be working ok. A few posts mentioned it works with kernel 5.6rc1 and 5.7 but I couldn't find those images.
</p>

<p>
	I tried all the images Mr. Balbes have on <a href="https://users.armbian.com/balbes150/arm-64/" rel="external nofollow">https://users.armbian.com/balbes150/arm-64/</a> and I also tried installing the headers.
</p>

<p>
	 
</p>

<p>
	It works fine with Emulec and Android.
</p>

<p>
	 
</p>

<p>
	I see this message below.. (<strong>brcmf_chip_cores_check: CPU core not detected</strong>) is this the reason wifi is dead?
</p>

<p>
	 
</p>

<p>
	dmesg brcmfmac
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Spoiler</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			[    9.537581] brcmfmac: F1 signature read @0x18000000=0x16024335<br />
			[    9.537842] brcmfmac: brcmf_chip_cores_check: CPU core not detected<br />
			<strong>[    9.537847] brcmfmac: brcmf_sdio_probe_attach: brcmf_chip_attach failed!</strong><br />
			[    9.537852] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed<br />
			[    9.537964] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...<br />
			[    9.538131] brcmfmac: probe of mmc0:0001:3 failed with error -110
		</p>

		<p>
			 
		</p>

		<p>
			[    9.961746] Bluetooth: hci0: BCM: chip id 86<br />
			[    9.962240] Bluetooth: hci0: BCM: features 0x2f<br />
			[    9.963942] Bluetooth: hci0: BCM4335C0<br />
			[    9.963950] Bluetooth: hci0: BCM4335C0 (003.001.009) build 0000<br />
			[    9.965760] Bluetooth: hci0: BCM4335C0 'brcm/BCM4335C0.hcd' Patch<br />
			[   10.811132] Bluetooth: hci0: AMPAK AP6335i BCM4339 37.4MHz CL2 BT4.1 CSP743120-0108<br />
			[   10.811144] Bluetooth: hci0: BCM4335C0 (003.001.009) build 0671
		</p>
	</div>
</div>

<p>
	 
	</p><p>
		and these are the files in /lib/firmware/brcm
	</p>


<p>
	 
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Spoiler</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			bcm4329.hcd                                brcmfmac4339-sdio.txt.old<br />
			BCM4330B1.hcd                              brcmfmac4339-sdio.ZP.txt<br />
			bcm4330.hcd                                brcmfmac43430a0-sdio.bin<br />
			BCM4334B0.hcd                              brcmfmac43430a0-sdio.txt<br />
			BCM4335C0.hcd                              brcmfmac43430-sdio.bin<br />
			BCM43430A1.hcd                             brcmfmac43430-sdio.txt<br />
			bcm43438-sdio.hcd                          brcmfmac43455-sdio.bin<br />
			BCM4345C5.hcd                              brcmfmac43455-sdio.clm_blob<br />
			BCM4356A2.hcd                              brcmfmac43455-sdio.txt<br />
			brcmfmac4329-sdio.bin                      brcmfmac43456-sdio.bin<br />
			brcmfmac4329-sdio.txt                      brcmfmac43456-sdio.txt<br />
			brcmfmac4330-sdio.amlogic,q200-n1.txt      brcmfmac4356-sdio.bin<br />
			brcmfmac4330-sdio.bin                      brcmfmac4356-sdio.clm_blob<br />
			brcmfmac4330-sdio.rockchip,rk3318-box.txt  brcmfmac4356-sdio-nanopi-m4v2.bin<br />
			brcmfmac4330-sdio.txt                      brcmfmac4356-sdio-nanopi-m4v2.txt<br />
			brcmfmac4334-sdio.bin                      brcmfmac4356-sdio.txt<br />
			brcmfmac4334-sdio.rockchip,rk3318-box.txt  brcmfmac4359-sdio.bin<br />
			brcmfmac4335-sdio.bin                      brcmfmac4359-sdio.txt<br />
			brcmfmac4335-sdio.txt                      brcmfmac-ap6330-sdio.bin<br />
			brcmfmac43362-sdio.bin                     brcmfmac-ap6330-sdio.txt<br />
			brcmfmac43362-sdio.txt                     brcmfmac-ap6335-sdio.bin<br />
			brcmfmac4339-sdio.1CK.txt                  brcmfmac-ap6335-sdio.txt<br />
			brcmfmac4339-sdio.bin.old                  config.txt<br />
			brcmfmac4339-sdio.txt
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	 
</p>

<p>
	If anyone can give me a hint... it would be amazing
</p>

<p>
	Thank you, Leco
</p>
]]></description><guid isPermaLink="false">18695</guid><pubDate>Mon, 26 Jul 2021 04:48:21 +0000</pubDate></item><item><title>Error while compiling open vfd driver: ERROR: modpost: "__stack_chk_guard" [/linux_openvfd/driver/openvfd.ko] undefined!</title><link>https://forum.armbian.com/topic/18634-error-while-compiling-open-vfd-driver-error-modpost-__stack_chk_guard-linux_openvfddriveropenvfdko-undefined/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	I'm trying to compile open vfd driver for my tx3 mini tv box.
</p>

<p>
	It's running Armbian buster with kernel version 5.9.0.
</p>

<p>
	Here is what I've done so far.
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		 
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			<br />
			sudo make ARCH=arm64 -C "/usr/src/linux-headers-5.9.0-arm-64" M="/home/dale/linux_openvfd/driver" make: Entering directory '/usr/src/linux-headers-5.9.0-arm-64'<br />
			AR /home/dale/linux_openvfd/driver/built-in.a<br />
			CC [M] /home/dale/linux_openvfd/driver/protocols/i2c_sw.o<br />
			CC [M] /home/dale/linux_openvfd/driver/protocols/i2c_hw.o<br />
			CC [M] /home/dale/linux_openvfd/driver/protocols/spi_sw.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/dummy.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/seg7_ctrl.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/fd628.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/fd650.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/hd44780.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/gfx_mono_ctrl.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/ssd1306.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/pcd8544.o<br />
			CC [M] /home/dale/linux_openvfd/driver/controllers/il3829.o<br />
			CC [M] /home/dale/linux_openvfd/driver/openvfd_drv.o<br />
			/home/dale/linux_openvfd/driver/openvfd_drv.c:43:7: warning: "CONFIG_AMLOGIC_LEGACY_EARLY_SUSPEND" is not defined, evaluates to 0 [-Wundef]<br />
			#elif CONFIG_AMLOGIC_LEGACY_EARLY_SUSPEND<br />
			^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br />
			LD [M] /home/dale/linux_openvfd/driver/openvfd.o<br />
			MODPOST /home/dale/linux_openvfd/driver/Module.symvers<br />
			ERROR: modpost: "__stack_chk_guard" [/home/dale/linux_openvfd/driver/openvfd.ko] undefined!<br />
			make[1]: *** [scripts/Makefile.modpost:111: /home/dale/linux_openvfd/driver/Module.symvers] Error 1<br />
			make[1]: *** Deleting file '/home/dale/linux_openvfd/driver/Module.symvers'<br />
			make: *** [Makefile:1697: modules] Error 2<br />
			make: Leaving directory '/usr/src/linux-headers-5.9.0-arm-64'<br />
			 
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	Any help would be appreciated. Thank you!
</p>
]]></description><guid isPermaLink="false">18634</guid><pubDate>Thu, 15 Jul 2021 09:48:06 +0000</pubDate></item><item><title>Help with installing Armbian 20.04 to EMMC from USB</title><link>https://forum.armbian.com/topic/18574-help-with-installing-armbian-2004-to-emmc-from-usb/</link><description><![CDATA[<p>
	Hi guys,
</p>

<p>
	thanks in advance for helping.
</p>

<p>
	 
</p>

<p>
	I flashed a usb (32G Lexar) with the image <em>Armbian_20.10_Arm-64_buster_current_5.9.0.img.xz </em>
</p>

<p>
	Next I booted up via the "Update&amp;Backup" on a <em>T95K Pro</em> based on <em>Amlogic S912</em> with 16G of internal storage and 2G of ram.
</p>

<p>
	 
</p>

<p>
	After <i>apt-get update </i>and <em>apt-get upgrade </em>I decided to move Armbian from the USB to the internal storage (<abbr title="embedded MultiMediaCard">emmc</abbr>)
</p>

<p>
	So I ran the file "install-aml.sh" getting this output:
</p>

<pre class="ipsCode">Start script create MBR and filesystem
/dev/mmcblk0
Start backup u-boot default
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 4.45454 s, 942 kB/s
Start create MBR and partittion
Start restore u-boot
442+0 records in
442+0 records out
442 bytes copied, 0.00476152 s, 92.8 kB/s
8191+0 records in
8191+0 records out
4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.177546 s, 23.6 MB/s
Done
Start copy system for eMMC.
Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
done.
Cppying BOOT...cp: error writing '/ddbr/install/zImage': No space left on device
done.
Edit init config...sed: couldn't flush /ddbr/install/extlinux/sedVudiPh: No space left on device
done.
done.
Formatting ROOT partition...
/dev/mmcblk0p2 contains a ext4 file system labelled 'ROOT_EMMC'
        last mounted on /ddbr/install on Sun Jul  4 17:10:59 2021
e2fsck 1.44.5 (15-Dec-2018)
ROOT_EMMC: clean, 11/863264 files, 80826/3447552 blocks
done.
Copying ROOTFS.
Copy BIN
Create DEV
Copy ETC
Copy HOME
Copy LIB
Copy LIB64
Create MEDIA
Create MNT
Copy OPT
Create PROC
Copy ROOT
Create RUN
Copy SBIN
Copy SELINUX
Copy SRV
Create SYS
Create TMP
Copy USR
Copy VAR
Copy fstab
*******************************************
Complete copy OS to eMMC
*******************************************
</pre>

<p>
	 
</p>

<p>
	This is the output of <em>lsdisk </em>after running the script
</p>

<p>
	 
</p>

<pre class="ipsCode">root@armbian:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda            8:0    1  29.8G  0 disk
|-sda1         8:1    1   512M  0 part /boot
`-sda2         8:2    1    29G  0 part /
mmcblk0      179:0    0  14.6G  0 disk
|-mmcblk0p1  179:1    0   488M  0 part
`-mmcblk0p2  179:2    0  13.2G  0 part
mmcblk0boot0 179:32   0     4M  1 disk
mmcblk0boot1 179:64   0     4M  1 disk
zram0        254:0    0    50M  0 disk /var/log
zram1        254:1    0 929.2M  0 disk [SWAP]
</pre>

<p>
	 
</p>

<p>
	However, after shutdown system and powered it up without the usb I get the following output:
</p>

<pre class="ipsCode">U-Boot 2020.07-dirty (Jul 26 2020 - 13:24:26 +0200) hexdump-gxl

Model: hexdump usbkbd/hdmi u-boot gxl
SoC: Amlogic Meson GXM (S912) Revision 22:a (82:2)
Net: eth0 ethernet@c9410000
starting USB...
Bus dwx3@c9000000: Register 3000140 NbrPorts 3
Starting the controller 
USB XHCI 1.00
scanning bus dwx3@c9000000 for devices... 1 USB Device(s) found
	scanning usb for storage devices... 0 Storage device(s) found
## Error insterting "stdin" variable, errno=22
Card did not respond to voltage select!
Card did not respond to voltage select!
** No partition table - mmc 1 **
** No partition table - mmc 1 **
Hit any key to stop autoboot: [3-2-1-0]
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
** No partition table - mmc 1 **
MMC Device 2 not found 
no mmc device at solt 2

Device 0: unknown device
ethernet@c9410000 Waiting for PHY auto negotiation to complete........ TIMEOUT!
Could not initialize PHY ethernet@c9410000
missing enviroment variable: pxeuuid
missing enviroment variable: bootfile
Retrieving file: pxelinux.cfg/00000000

*** COMMENT *** LOOPING OVER THESE 6 LINES TO INFINITY ***</pre>

<p>
	 
</p>

<p>
	If I boot up with the usb inserted it goes fine, without it no.
</p>

<p>
	 
</p>

<p>
	Output of <em>ls -ls /dev/</em>
</p>

<pre class="ipsCode">root@armbian:/# ls dev -ls
total 0
0 crw-r--r-- 1 root root     10, 235 Jul  4 17:41 autofs
0 drwxr-xr-x 2 root root         740 Jul  4 17:41 block
0 drwxr-xr-x 2 root root          60 Jan  1  1970 bsg
0 crw-rw---- 1 root disk     10, 234 Jul  4 17:41 btrfs-control
0 drwxr-xr-x 3 root root          60 Jan  1  1970 bus
0 crw-rw---- 1 root video   251,   0 Jul  4 17:41 cec0
0 crw-rw---- 1 root video   251,   1 Jul  4 17:41 cec1
0 drwxr-xr-x 2 root root        3620 Jul  4 17:42 char
0 crw------- 1 root root      5,   1 Jul  4 17:52 console
0 crw------- 1 root root     10,  60 Jul  4 17:41 cpu_dma_latency
0 crw------- 1 root root     10, 203 Jul  4 17:41 cuse
0 drwxr-xr-x 7 root root         140 Jan  1  1970 disk
0 drwxr-xr-x 2 root root          80 Jan  1  1970 dma_heap
0 drwxr-xr-x 3 root root         120 Jul  4 17:41 dri
0 crw-rw---- 1 root video    29,   0 Jul  4 17:41 fb0
0 crw-rw---- 1 root video    29,   1 Jul  4 17:41 fb1
0 lrwxrwxrwx 1 root root          13 Jan  1  1970 fd -&gt; /proc/self/fd
0 crw-rw-rw- 1 root root      1,   7 Jul  4 17:41 full
0 crw-rw-rw- 1 root root     10, 229 Jul  4 17:41 fuse
0 crw------- 1 root root    254,   0 Jul  4 17:41 gpiochip0
0 crw------- 1 root root    254,   1 Jul  4 17:41 gpiochip1
0 drwxr-xr-x 2 root root           0 Feb 14  2019 hugepages
0 crw------- 1 root root     10, 183 Jul  4 17:41 hwrng
0 crw------- 1 root root     89,   0 Jul  4 17:41 i2c-0
0 crw------- 1 root root     89,   1 Jul  4 17:41 i2c-1
0 crw------- 1 root root    248,   0 Jul  4 17:41 iio:device0
0 lrwxrwxrwx 1 root root          12 Jul  4 17:41 initctl -&gt; /run/initctl
0 drwxr-xr-x 3 root root         140 Jul  4 17:41 input
0 crw-r--r-- 1 root root      1,  11 Jul  4 17:41 kmsg
0 crw-rw---- 1 root video   238,   0 Jul  4 17:41 lirc0
0 lrwxrwxrwx 1 root root          28 Feb 14  2019 log -&gt; /run/systemd/journal/dev-log
0 crw-rw---- 1 root disk     10, 237 Jul  4 17:41 loop-control
0 brw-rw---- 1 root disk      7,   0 Jul  4 17:41 loop0
0 brw-rw---- 1 root disk      7,   1 Jul  4 17:41 loop1
0 brw-rw---- 1 root disk      7,   2 Jul  4 17:41 loop2
0 brw-rw---- 1 root disk      7,   3 Jul  4 17:41 loop3
0 brw-rw---- 1 root disk      7,   4 Jul  4 17:41 loop4
0 brw-rw---- 1 root disk      7,   5 Jul  4 17:41 loop5
0 brw-rw---- 1 root disk      7,   6 Jul  4 17:41 loop6
0 brw-rw---- 1 root disk      7,   7 Jul  4 17:41 loop7
0 drwxr-xr-x 2 root root          60 Jul  4 17:41 mapper
0 crw-r----- 1 root kmem      1,   1 Jul  4 17:41 mem
0 brw-rw---- 1 root disk    179,   0 Jul  4 17:41 mmcblk0
0 brw-rw---- 1 root disk    179,  32 Jul  4 17:41 mmcblk0boot0
0 brw-rw---- 1 root disk    179,  64 Jul  4 17:41 mmcblk0boot1
0 brw-rw---- 1 root disk    179,   1 Jul  4 17:41 mmcblk0p1
0 brw-rw---- 1 root disk    179,   2 Jul  4 17:41 mmcblk0p2
0 crw------- 1 root root    241,   0 Jul  4 17:41 mmcblk0rpmb
0 drwxrwxrwt 2 root root          40 Jan  1  1970 mqueue
0 drwxr-xr-x 2 root root          60 Jul  4 17:41 net
0 crw-rw-rw- 1 root root      1,   3 Jul  4 17:41 null
0 crw------- 1 root root     10,  62 Jul  4 17:41 nvme-fabrics
0 crw-r----- 1 root kmem      1,   4 Jul  4 17:41 port
0 crw------- 1 root root    108,   0 Jul  4 17:41 ppp
0 crw-rw-rw- 1 root tty       5,   2 Jul  4 17:54 ptmx
0 drwxr-xr-x 2 root root           0 Jan  1  1970 pts
0 crw------- 1 root root      2,   0 Jul  4 17:41 ptyp0
0 crw------- 1 root root      2,   1 Jul  4 17:41 ptyp1
0 crw------- 1 root root      2,   2 Jul  4 17:41 ptyp2
0 crw------- 1 root root      2,   3 Jul  4 17:41 ptyp3
0 crw------- 1 root root      2,   4 Jul  4 17:41 ptyp4
0 crw------- 1 root root      2,   5 Jul  4 17:41 ptyp5
0 crw------- 1 root root      2,   6 Jul  4 17:41 ptyp6
0 crw------- 1 root root      2,   7 Jul  4 17:41 ptyp7
0 crw------- 1 root root      2,   8 Jul  4 17:41 ptyp8
0 crw------- 1 root root      2,   9 Jul  4 17:41 ptyp9
0 crw------- 1 root root      2,  10 Jul  4 17:41 ptypa
0 crw------- 1 root root      2,  11 Jul  4 17:41 ptypb
0 crw------- 1 root root      2,  12 Jul  4 17:41 ptypc
0 crw------- 1 root root      2,  13 Jul  4 17:41 ptypd
0 crw------- 1 root root      2,  14 Jul  4 17:41 ptype
0 crw------- 1 root root      2,  15 Jul  4 17:41 ptypf
0 brw-rw---- 1 root disk      1,   0 Jul  4 17:41 ram0
0 brw-rw---- 1 root disk      1,   1 Jul  4 17:41 ram1
0 brw-rw---- 1 root disk      1,  10 Jul  4 17:41 ram10
0 brw-rw---- 1 root disk      1,  11 Jul  4 17:41 ram11
0 brw-rw---- 1 root disk      1,  12 Jul  4 17:41 ram12
0 brw-rw---- 1 root disk      1,  13 Jul  4 17:41 ram13
0 brw-rw---- 1 root disk      1,  14 Jul  4 17:41 ram14
0 brw-rw---- 1 root disk      1,  15 Jul  4 17:41 ram15
0 brw-rw---- 1 root disk      1,   2 Jul  4 17:41 ram2
0 brw-rw---- 1 root disk      1,   3 Jul  4 17:41 ram3
0 brw-rw---- 1 root disk      1,   4 Jul  4 17:41 ram4
0 brw-rw---- 1 root disk      1,   5 Jul  4 17:41 ram5
0 brw-rw---- 1 root disk      1,   6 Jul  4 17:41 ram6
0 brw-rw---- 1 root disk      1,   7 Jul  4 17:41 ram7
0 brw-rw---- 1 root disk      1,   8 Jul  4 17:41 ram8
0 brw-rw---- 1 root disk      1,   9 Jul  4 17:41 ram9
0 crw-rw-rw- 1 root root      1,   8 Jul  4 17:41 random
0 drwxr-xr-x 2 root root          60 Jan  1  1970 raw
0 crw-rw-r-- 1 root netdev   10, 242 Jul  4 17:42 rfkill
0 brw-rw---- 1 root disk      8,   0 Jul  4 17:41 sda
0 brw-rw---- 1 root disk      8,   1 Jul  4 17:41 sda1
0 brw-rw---- 1 root disk      8,   2 Jul  4 17:41 sda2
0 crw-rw---- 1 root disk     21,   0 Jul  4 17:41 sg0
0 drwxrwxrwt 2 root root          40 Feb 14  2019 shm
0 crw------- 1 root root     10, 231 Jul  4 17:41 snapshot
0 drwxr-xr-x 3 root root         140 Jul  4 17:41 snd
0 lrwxrwxrwx 1 root root          15 Jan  1  1970 stderr -&gt; /proc/self/fd/2
0 lrwxrwxrwx 1 root root          15 Jan  1  1970 stdin -&gt; /proc/self/fd/0
0 lrwxrwxrwx 1 root root          15 Jan  1  1970 stdout -&gt; /proc/self/fd/1
0 crw-rw-rw- 1 root tty       5,   0 Jul  4 17:41 tty
0 crw--w---- 1 root tty       4,   0 Jul  4 17:41 tty0
0 crw--w---- 1 root tty       4,   1 Jul  4 17:52 tty1
0 crw--w---- 1 root tty       4,  10 Jul  4 17:41 tty10
0 crw--w---- 1 root tty       4,  11 Jul  4 17:41 tty11
0 crw--w---- 1 root tty       4,  12 Jul  4 17:41 tty12
0 crw--w---- 1 root tty       4,  13 Jul  4 17:41 tty13
0 crw--w---- 1 root tty       4,  14 Jul  4 17:41 tty14
0 crw--w---- 1 root tty       4,  15 Jul  4 17:41 tty15
0 crw--w---- 1 root tty       4,  16 Jul  4 17:41 tty16
0 crw--w---- 1 root tty       4,  17 Jul  4 17:41 tty17
0 crw--w---- 1 root tty       4,  18 Jul  4 17:41 tty18
0 crw--w---- 1 root tty       4,  19 Jul  4 17:41 tty19
0 crw--w---- 1 root tty       4,   2 Jul  4 17:41 tty2
0 crw--w---- 1 root tty       4,  20 Jul  4 17:41 tty20
0 crw--w---- 1 root tty       4,  21 Jul  4 17:41 tty21
0 crw--w---- 1 root tty       4,  22 Jul  4 17:41 tty22
0 crw--w---- 1 root tty       4,  23 Jul  4 17:41 tty23
0 crw--w---- 1 root tty       4,  24 Jul  4 17:41 tty24
0 crw--w---- 1 root tty       4,  25 Jul  4 17:41 tty25
0 crw--w---- 1 root tty       4,  26 Jul  4 17:41 tty26
0 crw--w---- 1 root tty       4,  27 Jul  4 17:41 tty27
0 crw--w---- 1 root tty       4,  28 Jul  4 17:41 tty28
0 crw--w---- 1 root tty       4,  29 Jul  4 17:41 tty29
0 crw--w---- 1 root tty       4,   3 Jul  4 17:41 tty3
0 crw--w---- 1 root tty       4,  30 Jul  4 17:41 tty30
0 crw--w---- 1 root tty       4,  31 Jul  4 17:41 tty31
0 crw--w---- 1 root tty       4,  32 Jul  4 17:41 tty32
0 crw--w---- 1 root tty       4,  33 Jul  4 17:41 tty33
0 crw--w---- 1 root tty       4,  34 Jul  4 17:41 tty34
0 crw--w---- 1 root tty       4,  35 Jul  4 17:41 tty35
0 crw--w---- 1 root tty       4,  36 Jul  4 17:41 tty36
0 crw--w---- 1 root tty       4,  37 Jul  4 17:41 tty37
0 crw--w---- 1 root tty       4,  38 Jul  4 17:41 tty38
0 crw--w---- 1 root tty       4,  39 Jul  4 17:41 tty39
0 crw--w---- 1 root tty       4,   4 Jul  4 17:41 tty4
0 crw--w---- 1 root tty       4,  40 Jul  4 17:41 tty40
0 crw--w---- 1 root tty       4,  41 Jul  4 17:41 tty41
0 crw--w---- 1 root tty       4,  42 Jul  4 17:41 tty42
0 crw--w---- 1 root tty       4,  43 Jul  4 17:41 tty43
0 crw--w---- 1 root tty       4,  44 Jul  4 17:41 tty44
0 crw--w---- 1 root tty       4,  45 Jul  4 17:41 tty45
0 crw--w---- 1 root tty       4,  46 Jul  4 17:41 tty46
0 crw--w---- 1 root tty       4,  47 Jul  4 17:41 tty47
0 crw--w---- 1 root tty       4,  48 Jul  4 17:41 tty48
0 crw--w---- 1 root tty       4,  49 Jul  4 17:41 tty49
0 crw--w---- 1 root tty       4,   5 Jul  4 17:41 tty5
0 crw--w---- 1 root tty       4,  50 Jul  4 17:41 tty50
0 crw--w---- 1 root tty       4,  51 Jul  4 17:41 tty51
0 crw--w---- 1 root tty       4,  52 Jul  4 17:41 tty52
0 crw--w---- 1 root tty       4,  53 Jul  4 17:41 tty53
0 crw--w---- 1 root tty       4,  54 Jul  4 17:41 tty54
0 crw--w---- 1 root tty       4,  55 Jul  4 17:41 tty55
0 crw--w---- 1 root tty       4,  56 Jul  4 17:41 tty56
0 crw--w---- 1 root tty       4,  57 Jul  4 17:41 tty57
0 crw--w---- 1 root tty       4,  58 Jul  4 17:41 tty58
0 crw--w---- 1 root tty       4,  59 Jul  4 17:41 tty59
0 crw--w---- 1 root tty       4,   6 Jul  4 17:41 tty6
0 crw--w---- 1 root tty       4,  60 Jul  4 17:41 tty60
0 crw--w---- 1 root tty       4,  61 Jul  4 17:41 tty61
0 crw--w---- 1 root tty       4,  62 Jul  4 17:41 tty62
0 crw--w---- 1 root tty       4,  63 Jul  4 17:41 tty63
0 crw--w---- 1 root tty       4,   7 Jul  4 17:41 tty7
0 crw--w---- 1 root tty       4,   8 Jul  4 17:41 tty8
0 crw--w---- 1 root tty       4,   9 Jul  4 17:41 tty9
0 crw--w---- 1 root tty     244,   0 Jul  4 17:52 ttyAML0
0 crw-rw---- 1 root dialout   4,  64 Jul  4 17:41 ttyS0
0 crw-rw---- 1 root dialout   4,  65 Jul  4 17:41 ttyS1
0 crw--w---- 1 root tty       4,  66 Jul  4 17:41 ttyS2
0 crw-rw---- 1 root dialout   4,  67 Jul  4 17:41 ttyS3
0 crw-rw---- 1 root dialout   4,  68 Jul  4 17:41 ttyS4
0 crw------- 1 root root      3,   0 Jul  4 17:41 ttyp0
0 crw------- 1 root root      3,   1 Jul  4 17:41 ttyp1
0 crw------- 1 root root      3,   2 Jul  4 17:41 ttyp2
0 crw------- 1 root root      3,   3 Jul  4 17:41 ttyp3
0 crw------- 1 root root      3,   4 Jul  4 17:41 ttyp4
0 crw------- 1 root root      3,   5 Jul  4 17:41 ttyp5
0 crw------- 1 root root      3,   6 Jul  4 17:41 ttyp6
0 crw------- 1 root root      3,   7 Jul  4 17:41 ttyp7
0 crw------- 1 root root      3,   8 Jul  4 17:41 ttyp8
0 crw------- 1 root root      3,   9 Jul  4 17:41 ttyp9
0 crw------- 1 root root      3,  10 Jul  4 17:41 ttypa
0 crw------- 1 root root      3,  11 Jul  4 17:41 ttypb
0 crw------- 1 root root      3,  12 Jul  4 17:41 ttypc
0 crw------- 1 root root      3,  13 Jul  4 17:41 ttypd
0 crw------- 1 root root      3,  14 Jul  4 17:41 ttype
0 crw------- 1 root root      3,  15 Jul  4 17:41 ttypf
0 crw------- 1 root root     10, 239 Jul  4 17:41 uhid
0 crw------- 1 root root     10, 223 Jul  4 17:41 uinput
0 crw------- 1 root root     10,  61 Jul  4 17:41 uleds
0 crw-rw-rw- 1 root root      1,   9 Jul  4 17:41 urandom
0 drwxr-xr-x 3 root root          60 Jul  4 17:41 v4l
0 crw-rw---- 1 root tty       7,   0 Jul  4 17:41 vcs
0 crw-rw---- 1 root tty       7,   1 Jul  4 17:41 vcs1
0 crw-rw---- 1 root tty       7,   2 Jul  4 17:41 vcs2
0 crw-rw---- 1 root tty       7,   3 Jul  4 17:41 vcs3
0 crw-rw---- 1 root tty       7,   4 Jul  4 17:41 vcs4
0 crw-rw---- 1 root tty       7,   5 Jul  4 17:41 vcs5
0 crw-rw---- 1 root tty       7,   6 Jul  4 17:41 vcs6
0 crw-rw---- 1 root tty       7, 128 Jul  4 17:41 vcsa
0 crw-rw---- 1 root tty       7, 129 Jul  4 17:41 vcsa1
0 crw-rw---- 1 root tty       7, 130 Jul  4 17:41 vcsa2
0 crw-rw---- 1 root tty       7, 131 Jul  4 17:41 vcsa3
0 crw-rw---- 1 root tty       7, 132 Jul  4 17:41 vcsa4
0 crw-rw---- 1 root tty       7, 133 Jul  4 17:41 vcsa5
0 crw-rw---- 1 root tty       7, 134 Jul  4 17:41 vcsa6
0 crw-rw---- 1 root tty       7,  64 Jul  4 17:41 vcsu
0 crw-rw---- 1 root tty       7,  65 Jul  4 17:41 vcsu1
0 crw-rw---- 1 root tty       7,  66 Jul  4 17:41 vcsu2
0 crw-rw---- 1 root tty       7,  67 Jul  4 17:41 vcsu3
0 crw-rw---- 1 root tty       7,  68 Jul  4 17:41 vcsu4
0 crw-rw---- 1 root tty       7,  69 Jul  4 17:41 vcsu5
0 crw-rw---- 1 root tty       7,  70 Jul  4 17:41 vcsu6
0 drwxr-xr-x 2 root root          60 Jan  1  1970 vfio
0 crw------- 1 root root     10,  63 Jul  4 17:41 vga_arbiter
0 crw------- 1 root root     10, 137 Jul  4 17:41 vhci
0 crw-rw---- 1 root video    81,   0 Jul  4 17:41 video0
0 crw------- 1 root root     10, 130 Jul  4 17:41 watchdog
0 crw------- 1 root root    246,   0 Jul  4 17:41 watchdog0
0 crw-rw-rw- 1 root root      1,   5 Jul  4 17:41 zero
0 brw-rw---- 1 root disk    254,   0 Jul  4 17:41 zram0
0 brw-rw---- 1 root disk    254,   1 Jul  4 17:41 zram1
0 brw-rw---- 1 root disk    254,   2 Jul  4 17:41 zram2
</pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	Any help is really appreciated.
</p>

<p>
	 
</p>

<p>
	Lorenzo (Italy)
</p>
]]></description><guid isPermaLink="false">18574</guid><pubDate>Sun, 04 Jul 2021 15:55:09 +0000</pubDate></item><item><title>Mov Z69 Amlogic s905x can't get Linux running ?.</title><link>https://forum.armbian.com/topic/18508-mov-z69-amlogic-s905x-cant-get-linux-running/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	 everyone need a little bit of support if anyone can help me?
</p>

<p>
	 
</p>

<p>
	So a couple of weeks back i picked up a retro gaming box filled with emulators, roms etc. After a little digging to add emulators, mess with themes, change settings and stuff i find out the box it's self is just a mix of libreelec, emulationstation, kodi with a few modifications, skins added. So i decided to see if the box can run Linux (if it could i could easily get retropie for Linux running on it) which it can and after a little googling and watching a video by the MXQ Project to get Armbian (Lepotato) running on the box (using the tooth pick method) i followed the steps to get it running and tried each one of the <abbr title="Device tree blob">dtb</abbr> files included on in the OS copying it into the root of the SD card, changing the file each time to <abbr title="Device tree blob">dtb</abbr>.img etc. https://krogerfeedback.nl <a href="https://talktosonic.onl" rel="external nofollow">https://talktosonic.onl</a> <a href="https://talktowendys.vip" rel="external nofollow">https://talktowendys.vip</a> <a href="https://whataburgersurvey.onl" rel="external nofollow">https://whataburgersurvey.onl</a>
</p>

<p>
	 
</p>

<p>
	Now the problem is i tested every <abbr title="Device tree blob">dtb</abbr> file and not a single one will boot Linux primarily Ubuntu. I also tried without a <abbr title="Device tree blob">dtb</abbr> file and again it just boots into the libreelec OS which is installed internally on the on board memory. I downloaded libreelec and tried booting a fresh copy from an sd card and it booted fine without me adding a <abbr title="Device tree blob">dtb</abbr> file (one was already included). So i copied out the <abbr title="Device tree blob">dtb</abbr> file and tried running Ubuntu with that file and again nothing happens it boots straight into libreelec.
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	thanks
</p>

<p>
	jackyjoy
</p>
]]></description><guid isPermaLink="false">18508</guid><pubDate>Mon, 28 Jun 2021 13:59:48 +0000</pubDate></item><item><title><![CDATA[How to build an up-to-date armbian ( kernel >= 5.10 ) for S905X3 ?]]></title><link>https://forum.armbian.com/topic/18477-how-to-build-an-up-to-date-armbian-kernel-510-for-s905x3/</link><description><![CDATA[<p>
	I am trying to build an armbian img. with mainline kernels for s905x3 tvboxes ( especially   h96 max x3   and X96_Max_plus )  . However , Since these boxes are not supported by armbian , I am wondering if anyone has even succeeded in building an up-to-date armbian without ethernet/sound issues ? Regards !
</p>
]]></description><guid isPermaLink="false">18477</guid><pubDate>Thu, 24 Jun 2021 14:35:24 +0000</pubDate></item><item><title>Can anyone explains what are the steps for making a TV box works with armbian?</title><link>https://forum.armbian.com/topic/18416-can-anyone-explains-what-are-the-steps-for-making-a-tv-box-works-with-armbian/</link><description><![CDATA[<p>
	Yes, I am new to forum. 
</p>

<p>
	Yes, I searched. 
</p>

<p>
	But I still have questions. 
</p>

<p>
	 
</p>

<p>
	My story: At the beginning of the year (2021) I bought one orange pi zero 2 board at a good price. It was around 18 euro. I am very happy with the small board. So I was think to buy a second one. Turn out due to global chip shortage, the price of the board jump to 27 euro. The price is not attritive for me any more. Then I watched a youtube video. I think a lot of people watch the same video. Armbian install on H6 tv Box. so I bought the 'same' Tv box. Apparently, I did not read the spec carefully. The model I bought it is not with H6 CPU, but with H616 CPU. Yes, all the steps which from youtube wont work with my TV box. Then I found out TV box is not active support by Armbian anyway. Armbian is support more on the <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr>, such as the orange pi zero 2. 
</p>

<p>
	 
</p>

<p>
	here are my questions:
</p>

<ul>
	<li>
		What is big difference between Orangepi zero 2 image and armbian image? if read this page <a href="https://github.com/orangepi-xunlong/orangepi-build" rel="external nofollow">https://github.com/orangepi-xunlong/orangepi-build</a>, it says it based on armbians.
	</li>
	<li>
		As I understaand, to make armbian work on tv box, the first step you need a working u-boot for your tv box. is it possible to dump uboot and <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> file from the android tv box? I can see the android tv box already using u-boot from 2018.
	</li>
	<li>
		if possible to dump u-boot the from android tv box, what are the next steps? build your own armbian images? or same steps like the youtuber video, first burn normal armbian image, then burn u-boot image , then then manually do some tweaks.
	</li>
</ul>

<p>
	 
</p>

<p>
	h616 tv box boot log. 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.06.12 11:46:20 =~=~=~=~=~=~=~=~=~=~=~=
[182]HELLO! BOOT0 is starting!
[185]BOOT0 commit : 904a4b2
[187]set pll start
[190]periph0 has been enabled
[193]set pll end
[195]unknow PMU
[197]PMU: AXP806
[204]vaild para:16  select dram para0
[207]board init ok
[209]DRAM BOOT DRIVE INFO: V0.60
[213]the chip id is 0x5000
[215]chip id check OK
[218]DRAM_VCC set to 1500 mv
[220]DRAM CLK =600 MHZ
[223]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[230]Actual DRAM SIZE =2048 M
[233]DRAM SIZE =2048 MBytes, para1 = 30fb, para2 = 8000000, dram_tpr13 = 6041
[246]DRAM simple test OK.
[249]rtc standby flag is 0x0, super standby flag is 0x0
[254]dram size =2048
[257]card no is 2
[259]sdcard 2 line count 8
[262][mmc]: mmc driver ver 2019-12-19 10:41
[266][mmc]: set f_max to 50M, set f_max_ddr to 50M
[271][mmc]: mmc 2 bias 4
[279][mmc]: ***Try MMC card 2***
[416][mmc]: MMC 5.1
[418][mmc]: HSDDR52/DDR50 8 bit
[421][mmc]: 50000000 Hz
[424][mmc]: 14910 MB
[426][mmc]: ***SD/MMC 2 init OK!!!***
[488]Loading boot-pkg Succeed(index=0).
[492]Entry_name        = u-boot
[501]Entry_name        = monitor
[505]Entry_name        = dtbo
[508]Entry_name        = dtb
[511]tunning data addr:0x4a0003e8
[515]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):b8b5557
NOTICE:  BL3-1: Built : 15:01:11, 2021-01-11
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3
ÿ

U-Boot 2018.05-gdd0276b-dirty (Feb 01 2021 - 10:50:58 +0800) Allwinner Technology

[00.591]CPU:   Allwinner Family
[00.593]Model: sun50iw9
I2C:   ready
[00.598]DRAM:  2 GiB
[00.601]Relocation Offset is: 75ec5000
[00.640]secure enable bit: 0
[00.642]pmu_axp152_probe pmic_bus_read fail
[00.647]PMU: AXP806
[00.648]PMU: pmu_axp806 found
[00.652]dcdce_vol = 3300, onoff=1
[00.656]aldo1_vol = 3300, onoff=1
[00.659]bldo1_vol = 1800, onoff=1
[00.662]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.853]sunxi overlay merged okqv
[00.857]init_clocks:finish
[00.859]drv_disp_init
[00.884]HDMI 2.0 driver init start!
[00.893]__clk_enable: clk is null.
[00.896]hdmi cec clk enable failed!
[00.902]drv_disp_init finish
[00.904]gic: sec monitor mode
[00.907]sunxi flash type@2 not support fast burn key
[00.923]node ir_recovery_key_code4 get failed!
[00.944]flash init start
[00.946]workmode = 0,storage type = 2
[00.949]MMC:	 2
[00.951]mmc driver ver uboot2018:2019-12-13 9:48:00
[00.955]get mem for descripter OK !
[00.960]Set eMMC Power Mode to 1.8V!
[00.964]card2 io is 1.8V.
[00.970]get card2 disable pin fail
[00.973]get sdc_ex_dly_used 2, use auto tuning sdly
[00.977]get sdc_ex_dly_used 2, use auto tuning sdly
[00.982]get sdc2 sdc_boot0_sup_1v8 fail.
[00.987]get card-pwr-gpios faild
[00.989]get card2_boot_para:time_pwroff_ms:use default time_pwroff:200
[00.996]io is 1.8V
[00.997]init mmc 2 clock and io
[01.000]devnum 2, prv bffab350, bdesc bbf0ab6c
[01.004]SUNXI SD/MMC: 2
[01.007]==================== work mode: 0 0, sample_mode:2
[01.012]=============== start mmc_init_boot...
[01.154]MMC version:4
[01.156]mmc_startup: set clock 50000000
[01.160]Best spd md: 4-HS400, freq: 3-100000000
[01.164]already at HSSDR52_SDR25 mode
[01.167]Bus width 8
[01.169]sunxi flash init ok
[01.173]Loading Environment from SUNXI_FLASH... OK
[01.181]no secure os for keybox operation
[01.185]try to burn key
[01.188]read item0 copy0
[01.190]the secure storage item0 copy0 is good
[01.194]no item name key_burned_flag in the map
[01.198]sunxi secure storage has no flag
[01.202]usb burn from boot
delay time 0
weak:otg_phy_config
[01.215]usb prepare ok
[02.018]overtime
[02.022]do_burn_from_boot usb : no usb exist
[02.026]boot_gui_init:start
FAT: Misaligned buffer address (bbe80cb8)
34 bytes read in 4 ms (7.8 KiB/s)
[02.044]get format[40a] for type[4]
[02.047]get format[20b] for type[2]
[02.201][HDMI2.0]CEA VIC=16: [02.203]1920x1080p[02.205]@60 Hz [02.206]16:9, [02.207]8-bpp [02.209]YCbCr-444
[02.210]BT709
[02.211]eotf:SDR_LUMINANCE_RANGE
[02.327]switch device: sel=0, type=4, mode=10, format=1, bits=0, eotf=4, cs=257
[02.334]boot_gui_init:finish
[02.338]bmp_name=bootlogo.bmp
2764856 bytes read in 17 ms (155.1 MiB/s)
[02.374]no item name device_unlock in the map
[02.378]no item name fastboot_status_flag in the map
[02.382]sunxi secure storage has no flag
[02.388]hsddr 2-50000000
[02.390]hs200 5-200000000
[02.392]hs400 4-150000000
[02.395]get max-frequency ok 50000000 Hz
[02.398]0 0 0: 0 0 0
[02.402](weak)update dtb dram start
[02.406]update dtb dram  end
[02.409]update dts
[02.410]no item name rootwait init in the map
** Unrecognized filesystem type **
[02.424]load file(ULI/factory/rootwait init.txt) error.
[02.428]no item name snum in the map
** Unrecognized filesystem type **
[02.441]load file(ULI/factory/snum.txt) error.
[02.445]name in map mac
[02.447]update mac = 481011280498, source:secure
[02.452]no item name wifi_mac in the map
** Unrecognized filesystem type **
[02.464]load file(ULI/factory/wifi_mac.txt) error.
[02.469]no item name bt_mac in the map
** Unrecognized filesystem type **
[02.481]load file(ULI/factory/bt_mac.txt) error.
[02.485]no item name selinux in the map
** Unrecognized filesystem type **
[02.498]load file(ULI/factory/selinux.txt) error.
[02.503]no item name specialstr in the map
** Unrecognized filesystem type **
[02.515]load file(ULI/factory/specialstr.txt) error.
[02.520]name in map hx_flag
[02.523]update hx_flag = 216, source:secure
[02.527]MAC address changed to: 48:10:11:28:04:98
[02.558]update part info
[02.560]key 0
[02.563]cant find rcvy value
[02.568]cant find fstbt value
[02.572]misc partition found
[02.584]update bootcmd
[02.586]serial num is: 2c001415a30109922ce
[02.589]Net:   [02.591]Net Initialization Skipped
[02.594]No ethernet found.
Hit any key to stop autoboot:  0 
[02.607]partinfo: name boot, start 0x2a000, size 0x10000
[02.725]in boot normal mode,pass normal para to cmdline
[02.731]android.hardware = sun50iw9p1
[02.791]Starting kernel ...</span></pre>

<p>
	 
</p>

<p>
	then I tried two images, one from armbians which wont boot. another one is orange pi zero 2 image. at least I see something happens. I know it wont work. because they are different hardwares.
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.06.18 09:19:20 =~=~=~=~=~=~=~=~=~=~=~=
 
U-Boot SPL 2021.01-rc5-armbian (May 06 2021 - 18:50:04 +0000)
DRAM: 1024 MiB
Trying to boot from MMC1
MMC: no card present
spl: mmc init failed with error: -123
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###


[216]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[221]BOOT0 commit : 593cf83
[224]set pll start
[227]periph0 has been enabled
[230]set pll end
[231]unknow PMU
[233]PMU: AXP806
[240]vaild para:1  select dram para0
[244]board init ok
[246]DRAM BOOT DRIVE INFO: V0.52
[249]the chip id is 0x5000
[252]chip id check OK
[254]DRAM_VCC set to 1500 mv
[258]write_leveling error 
[261]read_calibration error 
[265]write_leveling error 
[267]read_calibration error 
[271]write_leveling error 
[274]read_calibration error 
[278]write_leveling error 
[281]read_calibration error 
[285]write_leveling error 
[288]read_calibration error 
[291]write_leveling error 
[294]read_calibration error 
[298]write_leveling error 
[301]read_calibration error 
[305]write_leveling error 
[308]read_calibration error 
[312]write_leveling error 
[315]read_calibration error 
[318]write_leveling error 
[321]read_calibration error 
[324]retraining final error 
[328]write_leveling error 
[331]dx_high 16bit write training error  
[335]dx_high 16bit write training error  
[339]dx_high 16bit write training error  
[344]dx_high 16bit write training error  
[348]dx_high 16bit write training error  
[352]write_training error 
[356]write_leveling error 
[359]dx_high 16bit write training error  
[363]dx_high 16bit write training error  
[367]dx_high 16bit write training error  
[371]dx_high 16bit write training error  
[376]dx_high 16bit write training error  
[380]write_training error 
[384]write_leveling error 
[386]dx_high 16bit write training error  
[391]dx_high 16bit write training error  
[395]dx_high 16bit write training error  
[399]dx_high 16bit write training error  
[403]dx_high 16bit write training error  
[408]write_training error 
[411]write_leveling error 
[414]dx_high 16bit write training error  
[418]dx_high 16bit write training error  
[423]dx_high 16bit write training error  
[427]dx_high 16bit write training error  
[431]dx_high 16bit write training error  
[435]write_training error 
[439]write_leveling error 
[442]dx_high 16bit write training error  
[446]dx_high 16bit write training error  
[450]dx_high 16bit write training error  
[455]dx_high 16bit write training error  
[459]dx_high 16bit write training error  
[463]write_training error 
[467]write_leveling error 
[470]dx_high 16bit write training error  
[474]dx_high 16bit write training error  
[478]dx_high 16bit write training error  
[482]dx_high 16bit write training error  
[487]dx_high 16bit write training error  
[491]write_training error 
[494]write_leveling error 
[497]dx_high 16bit write training error  
[502]dx_high 16bit write training error  
[506]dx_high 16bit write training error  
[510]dx_high 16bit write training error  
[514]dx_high 16bit write training error  
[519]write_training error 
[522]write_leveling error 
[525]dx_high 16bit write training error  
[529]dx_high 16bit write training error  
[534]dx_high 16bit write training error  
[538]dx_high 16bit write training error  
[542]dx_high 16bit write training error  
[546]write_training error 
[550]write_leveling error 
[553]dx_high 16bit write training error  
[557]dx_high 16bit write training error  
[561]dx_high 16bit write training error  
[566]dx_high 16bit write training error  
[570]dx_high 16bit write training error  
[574]write_training error 
[578]write_leveling error 
[581]dx_high 16bit write training error  
[585]dx_high 16bit write training error  
[589]dx_high 16bit write training error  
[593]dx_high 16bit write training error  
[598]dx_high 16bit write training error  
[602]write_training error 
[604]retraining final error 
[609]read_calibration error 
[612]read_calibration error 
[616]read_calibration error 
[620]read_calibration error 
[624]read_calibration error 
[628]read_calibration error 
[632]read_calibration error 
[636]read_calibration error 
[640]read_calibration error 
[644]read_calibration error 
[647]retraining final error 
[651][AUTO DEBUG]16 bit,1 ranks training success!
[658]DRAM CLK =720 MHZ
[660]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[667]Actual DRAM SIZE =1024 M
[669]DRAM SIZE =1024 MBytes, para1 = 30fb, para2 = 4000001, dram_tpr13 = 6041
[683]DRAM simple test OK.
[685]rtc standby flag is 0x0, super standby flag is 0x0
[690]dram size =1024
[693]*****dram handle ok****
[696]card no is 0
[698]sdcard 0 line count 4
[701][mmc]: mmc driver ver 2019-12-19 10:41
[705][mmc]: sdc0 spd mode error, 2
[708][mmc]: set f_max to 50M, set f_max_ddr to 25M
[713][mmc]: mmc 0 bias 0
[721][mmc]: Wrong media type 0x0
[724][mmc]: ***Try SD card 0***
[743][mmc]: HSSDR52/SDR25 4 bit
[747][mmc]: 50000000 Hz
[749][mmc]: 30436 MB
[751][mmc]: ***SD/MMC 0 init OK!!!***
[852]Loading boot-pkg Succeed(index=0).
[856]Entry_name        = u-boot
[865]Entry_name        = monitor
[869]Entry_name        = dtbo
[872]Entry_name        = dtb
[876]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):9fecd83
NOTICE:  BL3-1: Built : 17:08:29, 2020-05-28
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3


U-Boot 2018.05-orangepi (Mar 16 2021 - 10:43:40 +0800) Xunlong Software

[00.953]CPU:   Allwinner H616
[00.956]Model: Orange Pi Zero 2
I2C:   ready
[00.961]DRAM:  1 GiB
Relocation Offset is: 35ec9000
[01.001]secure enable bit: 0
[01.004]PMU: AXP806
[01.008]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[01.190]sunxi overlay merged okqv
[01.194]drv_disp_init
[01.223]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[01.228]drv_disp_init finish
[01.231]gic: sec monitor mode
[01.236]flash init start
[01.238]workmode = 0,storage type = 1
[01.241]MMC:	 0
[01.243]get mem for descripter OK !

card_caps:0x3000000a
host_caps:0x3000003f
[01.279]sunxi flash init ok
[01.283]Loading Environment from FAT... [01.286]get mem for descripter OK !

** Bad device mmc 1 **
Failed (-5)
[01.301]usb burn from boot
delay time 0
weak:otg_phy_config
[01.314]usb prepare ok
[02.117]overtime
[02.121]do_burn_from_boot usb : no usb exist
[02.125]boot_gui_init:start
card_caps:0x3000000a
host_caps:0x3000003f
104 bytes read in 6 ms (16.6 KiB/s)
Set HDMI disp_mode to 1080p60
104 bytes read in 7 ms (13.7 KiB/s)
Set fb0_width to 1280
Set fb0_height to 720
[02.451]boot_gui_init:finish
[02.454]bmp_name=/boot/boot.bmp
230456 bytes read in 17 ms (12.9 MiB/s)
[02.486]update dts
Net:   [02.490]No ethernet found.
Hit any key to stop autoboot:  1  0 
no mmc device at slot 1
card_caps:0x3000000a
host_caps:0x3000003f
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2616 bytes read in 9 ms (283.2 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
104 bytes read in 7 ms (13.7 KiB/s)
8472802 bytes read in 366 ms (22.1 MiB/s)
24125512 bytes read in 1020 ms (22.6 MiB/s)
## Booting kernel from Legacy Image at 41000000 ...
   Image Name:   
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    24125448 Bytes = 23 MiB
   Load Address: 41000000
   Entry Point:  41000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8472738 Bytes = 8.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 497eb000, end 49fff8a2 ... OK
   reserving fdt memory region: addr=48000000 size=1000000
## Linux machid: 00000000, FDT addr: 7be89580

Starting kernel ...</span></pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	I dont need HDMI or Bluetooth or wifi. If usb port and ethernet works, that's good enough for me. 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">18416</guid><pubDate>Fri, 18 Jun 2021 08:58:25 +0000</pubDate></item><item><title>Rockchip or Allwinner TV Box?</title><link>https://forum.armbian.com/topic/18246-rockchip-or-allwinner-tv-box/</link><description><![CDATA[<p>
	Hi! I saw that, even if not officially supported, there is a lot of discussion about armbian on tv boxes. I read that amlogic ones are not really a good choice and rockchip and allwinner ones should be the right choice instead.<br />
	I am thinking to buy a tv box to play with armbian, you know...for fun! But I am quite undecided. Would be an Allwinner H6 the best option or should I buy something with a Rockchip 3229, 3288 or 3388? And moreover, what would be the best choice and why between the Rockchip ones?<br />
	I have already read the thread "<a href="https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first" rel="">Status of Armbian on TV Boxes - Please Read First</a>" but at the moment there are no informations regarding Rockchip and Allwinner.
</p>
]]></description><guid isPermaLink="false">18246</guid><pubDate>Fri, 28 May 2021 17:37:10 +0000</pubDate></item></channel></rss>
