Jump to content

Search the Community

Showing results for 'tv'.

Didn't find what you were looking for? Try searching for:

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Volunteering opportunities
  • Part time jobs

Categories

  • Official giveaways
  • Community giveaways
  • Raffles

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

Matrix

Mastodon

IRC

Website URL

XMPP/Jabber

Skype

Github

Discord

Location

Interests

Found 1535 results

  1. jock
    ­DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Thank you! This thread is to give stable and mature long-term range support to rk3318/rk3328 found in many tv boxes in Armbian project as Community Supported Configuration (CSC). The current work is mainlined into Armbian project, but your mileage may vary; most recent developments live on my personal fork on github -> here <- Important notes: is just a personal opinion, but apparently widely supported, that rk3318 chip is not an official rockchip part. They probably are scrap rk3328 parts which have not passed conformance tests but are sold anyway to tv boxes manufacturers. They don’t reach the same operating frequency of the rk3328, have much higher leakage currents (and thus higher temperatures) and often the boards they are installed on are low quality with low quality components, in fact a very very common issue is the eMMC failure due to bad parts and bad soldering. So said, I personally suggest not to buy any rk3318 tv box, but instead find a properly supported SBC (Single Board Computer) if you need a reliable product. In the unfortunate case you already have such product, this thread may help you have some fun with them. What works: • Works on RK3318 and RK3328 TV boxes with DDR3 memories • Mainline u-boot • Mainline ATF provided as Trusted Execution Environment • All 4 cores are working • Ethernet • Serial UART (configured at stock 1.5Mbps) • Thermals and frequency scaling • OTG USB 2.0 port (also as boot device!) • EHCI/OHCI USB 2.0 ports and XHCI USB 3.0 ports • MMC subsystem (including , SD and sdio devices) • Hardware video acceleration (fully supported via RKMPP on legacy kernel, support via hantro and rkvdec kernel driver on mainline) • Various WIFI over SDIO are supported • Full acceleration on legacy kernel and mainline kernel • U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal ; you can install u-boot (and the whole system) in the internal and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the clock pin on the PCB. The procedure is explained here for rk322x, but for rk3318/28 is the same. In most of the rk3318/28 boards, shorting the clock pin is difficult or impossible because eMMC are BGA chips with no exposed pins. Pay double attention when burning something on the internal flash memory and always test first the image booting from the sdcard to be sure it works before burning anything in internal flash. This is a list of posts where forum users have been able to spot the eMMC clock pin to trigger the maskrom mode: H96 Max+ (board signature: RK3318_V1.4) by @Gausus X88 PRO 10 (board signature: X88_PRO_B) by @mathgaming HK1 Max (board signature YX_RK3318) by @Constantin Gatej Ninkbox N1 Max RK3318 by @enigmasphinx Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Legacy kernel: If you need multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to /TVB/ boards and select "rk3318-box" from the list. Prebuilt images: Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Multitool: Multitool - A small but powerful image for RK3318/RK3328 TV Box maintenance. Download it from here Quick installation instructions on eMMC: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in , the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal flash; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal ; Congratulations, Armbian is running from SD Card! Tutorial - How to install Armbian on your TV Box (by @awawa) : https://www.hyperhdr.eu/2022/01/tv-box-mania-i-part-x88-pro-10.html A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal The Multitool does not boot / How to burn image directly on eMMC: Some boards have the sdcard attached to an auxiliary (called also sdmmc_ext or external) controller which is not the common one. Forum findings declare that those boards are not able to boot from sdcard with stock firmware and they neither do in maskrom mode: the stock firmware always boots even if you put the multitool on sdcard. In such case, burning images directly on eMMC is the only way to have a working Armbian installation. You can follow these instructions by @fabiobassa to burn images directly on eMMC: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=130453 Notes and special hardware: Script to change DDR memory frequency here Wireless chip AP2734, SP2734, HY2734C and similars: they are clones of AmPAK AP6334 which is combo wifi + bluetooth of broadcom BCM4334/B0 chips. You may need a special nvram file, instructions by @paradigman are here Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk3318 into armbian would not have begun without his support! @hexdump for his precious support in early testing, ideas and suggestions @MX10.AC2Nfor his patience in testing mxq-rk3328-d4 board support All the rockhip64 maintainers at Armbian project who have done and do most of the work to support the platform
  2. Nico059
    Dear All, First I would like to thanks all the contributors to armbian, What a great OS for our small SBC ! Context: I run succesfully latest Armbian on a X9T 4K TV Box (amlogic s912) from SD Card 2GB (following instructions here The Problem: I would like to run armbian from emmc (16GB on this box) for better reliability and performance. So, I run the install-aml.sh script, I had some error (no boot.ini ...), but the process seems to finish successfully Next Reboot: It's seems my boot partition is Not OK ... something missing ... For reference See bellow for reference the succesfull boot from the sdcard If I boot from SDCard, I can inspect the /boot and root partition on emmc, everything seems ok On the emmc partition, the /boot/extlinux/extlinux.conf is correctly modified: extlinux.conf LABEL Armbian LINUX /Image INITRD /uInitrd #FDT /dtb/amlogic/meson-gxbb-p200.dtb #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb FDT /dtb/amlogic/meson-gxm-q200.dtb #FDT /dtb/amlogic/meson-g12a-x96-max.dtb #FDT /dtb/amlogic/meson-g12b-odroid-n2.dtb append root=LABEL=ROOT_EMMC 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 And the disk partion on the emmc fdisk -l /dev/mmcblk1 Disk /dev/mmcblk1: 14.64 GiB, 15724445696 bytes, 30711808 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: 0x09170000 Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 1953792 2953215 999424 488M c W95 FAT32 (LBA) /dev/mmcblk1p2 2955264 30711807 27756544 13.2G 83 Linux If you can help me .... Thx in advance Nico
  3. jock
    DISCLAIMERS (PLEASE READ): Everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. THIS POST explains very well the troubles with TV Boxes and why they are not suitable for everyone Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Following the recent thread on LibreElec forum about an unofficial image for rk3229 devices, I would like to make public the work made by me and @fabiobassa about bringing rk322x support to armbian. The project is now in -> mainline Armbian <- development fork -> here <- This first page and the last 3 or 4 pages of the thread are enough to get up to date with recent developments. Many useful experiences are scattered through the thread, but the most important things are collected here in the first page, so please read it carefully! Mainline kernel is fully supported and will receive most support in the future. Legacy kernel 4.4 is deprecated, but is kept around only for special purposes. What works: Should boot and work flawlessy on all boards with RK3228a, RK3228b and RK3229, with either DDR2 and DDR3 memories. Mainline u-boot Proprietary OPTEE provided as Trusted Execution Environment (needed for DRAM frequency scaling) All 4 cores are working Ethernet Serial UART (configured at 115200 bps, not 1.5Mbps!) Thermals, CPU and DRAM frequency scaling OTG USB 2.0 port (also as boot device!) EHCI/OHCI USB 2.0 ports MMC subsystem (including eMMC, SD and sdio devices) Hardware video acceleration NAND is available only on legacy kernel. To fully boot from NAND, use the Multitool and its steP-nand installation (instructions are below) Various WIFI over SDIO are supported (SSV6051P, SSV6256P, ESP8089, Realtek chips, etc...), ssv6256p driver is available only on legacy kernel Full GPU acceleration U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal eMMC; you can install u-boot (and the whole system) in the internal eMMC and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the eMMC clock pin on the PCB. Here there is the procedure, but you can also google around if you get stuck on a faulty bootloader, the technique is pretty simple and requires a simple screwdriver. There are however some unfortunate cases (expecially newer boards) where shorting the eMMC clock pin is difficult or impossibile, like eMMC or eMCP BGA chips with no exposed pins. In those cases pay double attention when burning something on the internal eMMC/eMCP and always test first the image from the sdcard to be sure it works before burning anything on eMMC/eMCP. Some useful links with pins, pads or procedures for some boards: Generic procedure for boards with non-BGA eMMC MXQPRO_V71 - eMCP H20 - eMCP ZQ01 - eMCP NAND vs eMMC vs eMCP difference: RK3228 and RK3229 tv boxes comes with three different flash memory chips: eMMC, NAND and eMCP. It does not depend upon the market name of the tv box and neither the internal board; manufacturers put whatever they find cheaper when they buy the components. NAND chip is just the non-volatile memory eMMC chip contains both the non-volatile memory plus a controller. eMCP chip contains the non-volatile memory, a controller for the non-volatile memory (like eMMC), but also contains a bank of DDR SDRAM memory on the same physical chip. The difference is very important, because eMMC and eMCP are far easier to support at various levels: the controller deals with the physical characteristics of the non-volatile memory, so the software has no to deal with. NAND chips instead are harder to support, because the software is required to deal with the physical characteristics and non-standard things that depends upon the NAND manufacturer. If you have a NAND chips you're unlucky because mainline kernel currently cannot access it, but also because you need special care and instructions explained later. You can discover if you have a NAND, eMMC or eMCP chip looking on the board are reading the signature on the flash memory chip. The Multitool (see later) also can detect which chip you have onboard: the program will warn you at startup if you have a NAND chip. NAND bootloader upgrade: IMPORTANT: don't do this is you have an eMMC or eMCP; skip this paragraph if you are unsure too! For very expert people who are having issues when (re)booting images, there is the chance to upgrade the bootloader on NAND. The NAND bootloader is nothing else than a regular idbloader (see official rockchip documentation) but contains some bits to correctly access the data on your flash memory. Upgrading requires to erase the existing flash content, in the worst case will require you to follow the Unbrick procedure above or restore an older but more compatible bootloader. If you are not mentally ready to overcome possible further issues, don't do this! The detailed instructions and the binaries are available at this post Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Deprecated legacy kernel: multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post An effective tutorial from @Hai Nguyen on how to configure a box as a hi-quality music player using an USB audio card, and controlling it via remote control is available in this post Brief explanation about kernel naming: current kernel is the mainline LTS kernel version, most maintained and tested. This is the suggested version for production devices. If you don't know what to pick, pick this. legacy kernel (version 4.4) is provided by manufacturer; it is deprecated, unmaintained and not suggested. edge kernel is the development mainline kernel version, with experimental features and drivers; usually stable but perhaps suitable for production devices. You can switch from one kernel flavour to another using armbian-config or manually via apt. Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to CSC/TVB/EOL boards and select "rk322x-box" from the list. Download prebuilt images from the following links: Archive builds (GPG-signed) - https://imola.armbian.com/dl/rk322x-box/archive/ SUGGESTED - Nightly built from trunk each week by Armbian servers (GPG-signed) - https://github.com/armbian/community Old images provided by me (unsigned and outdated) - https://users.armbian.com/jock/rk322x/armbian/stable Archived/older images: https://armbian.hosthatch.com/archive/rk322x-box/archive/ Multitool: The Multitool is a small but powerful tool to do quick backup/restore of internal flash, but also burn images and general system rescue and maintenance via terminal or SSH. Compressed images will be uncompressed on fly. Multitool - A small but powerful image for RK322x TV Box maintenance (instructions to access via network here) Quick installation instructions on eMMC: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC, etc... Run sudo armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed and configured! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in eMMC, the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions on NAND: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian legacy kernel image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn Armbian image via steP-nand" from the menu, then select the destination device (usually rknand0) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, etc... Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Alternative: you can install the bootloader in NAND and let it boot from SD Card or USB: Download a copy of the Multitool and burn it on an SD card; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; RECOMMENDED: make a backup of the existing firmware with "Backup flash" menu option; Choose "Install Jump Start for Armbian" menu option: the Jump Start uses the internal NAND to boot from external SD Card or external USB Stick; Follow the general instructions to boot from SD Card below, skip the first erase eMMC step. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC or NAND, etc... Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal eMMC; Congratulations, Armbian is running from SD Card! A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian or just the bootloader in the eMMC or the Jump Start on internal NAND, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal eMMC Installation (without SD card, board with eMMC) If you have no sd card slot and your board has an eMMC, you can burn the armbian image directly on the internal eMMC using rkdeveloptool and a male-to-male USB cable: Download your preferred Armbian image from Armbian download page and decompress it. Download the rk322x bootloader: rk322x_loader_v1.10.238_256.bin Download a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everything went well, run lsusb: you should see a device with ID 2207:320b Run sudo rkdeveloptool rd 3 (if this fails don't worry and proceed to next step) Run sudo rkdeveloptool db rk322x_loader_v1.10.238_256.bin Run sudo rkdeveloptool wl 0x0 image.img (change image.img this with the real Armbian image filename) Unplug the power cord Done! Installation (without SD card, board with NAND) If you are in the unfortunate case you can't use an SD card for installation and your board has a NAND chip, you still have an option to use the quick Multitool installation steps via USB. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b Run sudo rkdeveloptool wl 0x4000 u-boot-main.img (download u-boot-main.img.xz , don't forget to decompress it!) Unplug the power cord Now you can follow the instructions on how to install on eMMC/NAND via SD card, just use instead an USB stick to do all the operations and plug it into the USB OTG port. Once you reboot, USB OTG port will be used as a boot device. NOTE: NAND users without SD slot may be unhappy to know that it will be difficult to do extra maintenance with Multitool in case something breaks in the installed Armbian system: installing u-boot-main.img makes the installed system unbootable because it is missing the NAND driver. Alternative backup, restore and erase flash for EXPERTS: These backup, restore and erase flash procedures are for experts only. They are kept here mostly for reference, since the Multitool is perfectly able to do same from a very comfy interface and is the suggested way to do maintenance. Backup: Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b change directory and move into rkbin/tools directory, run ./rkdeveloptool rfi then take note of the FLASH SIZE megabytes (my eMMC is 8Gb, rkdeveloptool reports 7393 megabytes) run ./rkdeveloptool rl 0x0 $((FLASH_SIZE * 2048)) backup.data (change FLASH_SIZE with the value you obtained the step before) once done, the internal eMMC is backed up to backup.data file Restore: first we have to restore the original bootloader, then restore the original firmware. Running rkdeveloptool with these switches will accomplish both the jobs: ./rkdeveloptool db rk322x_loader_v1.10.238_256.bin Downloading bootloader succeeded. ./rkdeveloptool ul rk322x_loader_v1.10.238_256.bin Upgrading loader succeeded. ./rkdeveloptool wl 0x0 backup.data Write LBA from file (100%) Download here: Erase the flash memory: clearing the internal eMMC/NAND memory makes the SoC look for external SD Card as first boot option. If there isn't any suitable SD Card, the SoC enters maskrom mode, which can then be used for full eMMC/NAND access using rkdeveloptool. This is perfectly fine if your box has an eMMC flash memory. NOTE: In case you have a NAND flash memory this option is however discouraged. The original bootloader contains some special parameters to correctly access the data. Clearing the flash memory will probably garbage the NAND data and restoring the bootloader may require some special instructions. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the board Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b run ./rkdeveloptool ef and wait a few seconds once done, the internal eMMC is erased and the device will boot from the sdcard from now on Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk322x into armbian would not have begun without his support! Justin Swartz, for his work and research to bring mainline linux on rk3229 (repository here) @knaerzche for his great contribution to libreelec support and mainline patches @Alex83 for his patience in testing the NAND bootloader upgrade procedure on his board @Jason Duhamell for his generous donation that allowed researching eMCP boards and esp8089 wifi chip
  4. Andyroo
    Hi there, I'm currently working on installing armbian onto my h96 max tv box (labelled as an rk3318 externally and in software, but the internal board is marked as an rk3328), and like many others here, I am having difficulty getting hdmi to work using the rk3318 build found at https://github.com/armbian/community/releases. I can access and control the box over ssh either over ethernet or wifi once configured, however I definitely need functional hdmi output for the use case of this device. The hdmi output works perfectly fine in both the bootloader, the stock android OS, and the bootable multitool, but once armbian boots, I completely lose hdmi signal on a standard 1080p monitor. My linux experience is intermediate at best (I daily drive Mint and am not very familiar with in-depth hardware configuration like armbian requires), so I am looking for assistance with a few things: I'd like to confirm that I am indeed meant to use the rk3318 build and not the rk3328 one, as while both the device case and the output of cat /proc/cpuinfo claim that this device has an rk3318, the marking on the board states it is an rk3328. I would rather not remove the heatsink to check the chip's markings directly, as I doubt that I have the means to reattach the heatsink once it is removed. If there is another recommended build that has working hdmi for this device or would perform better, please let me know. When/if I am on the right image/build for this device, I unfortunately do not have much knowledge on how hdmi would be enabled/initialised. I have seen others in this thread mentioning doing so, but i cannot find any mention of how this is done. Assuming hdmi is eventually functional, I did have a look through the different options in rk3318-config and armbian-config, but I am unsure how to best use the information printed on the board to select the optimal options in these tools for my system. The wifi did work without needing to select anything special, which is good. I did not test bluetooth or notice the front LED panel working at all, though. Thank you in advance for any help you can provide, and thanks to Jock for porting this neat little distro to this hardware. It's been fun to tinker around with so far. Attached are images of the board and label, and I can provide any other images or output of commands if further information is needed.
  5. alienxz77b
    Hello, sorry for my very bad english. I recently I bought a TV box with an h618 processor And I want to install Linux to make it a server but I only find images for the h616 processor, can I install one of these images on my TV box? It seems that the h616 processor and the h618 procesador are almost the same Thanks :D
  6. stanelie
    Hello. I have this MX10 Box S android TV box, it works well with the latest Armbian community build (Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img). However, I have this specific binary that is 64bit that I would like to run on my box and this build of armbian is 32bit only. Is there a 64bit build of armbian for rk322x anywhere? Thanks!
  7. stanelie
    Hello. I am trying to have this new(?) tv box built around a RK3228A cpu detect the correct resolution of my monitor. In U-boot, I get a correct full HD 1920x1080p resolution. However, as soon as the U-Boot passes to the kernel, it switches to 1024x768. How can I correct this? If I can't correct the detection of EDID, can I force it? I've tried to add this to /boot/armbianEnv.txt, but it did not work : extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080@60 Any ideas? Thanks!
  8. k405
    @Benedito Portela thanks for reply I have another gigabit router that works, but It doesnt have Fiber optics and tnelefone. Idk If this is useful. I contacted my provider because they don't offer access to the router. They said all ports are on automatic and it only works at 100/1000 Mbps. I've tried everything, even changing the TV Box's speed negotiation, but it doesn't support it. The only way that works is to put a device between it and the main router.
  9. stanelie
    Here is the debug boot log : [ 0.000000] Booting Linux on physical CPU 0xf00 [ 0.000000] Linux version 6.12.37-current-rockchip (build@armbian) (arm-linux-gnueabihf-gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #1 SMP Thu Jul 10 14:05:15 UTC 2025 [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Generic RK322x Tv Box board [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 16 MiB at 0xbf000000 on node -1 [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000060000000-0x000000009fffffff] [ 0.000000] HighMem [mem 0x00000000a0000000-0x00000000bfffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000060000000-0x00000000683fffff] [ 0.000000] node 0: [mem 0x0000000069200000-0x00000000bfffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000060000000-0x00000000bfffffff] [ 0.000000] On node 0, zone Normal: 1536 pages in unavailable ranges [ 0.000000] OF: reserved mem: Reserved memory: No reserved-memory node in the DT [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv65535.65535 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.0 [ 0.000000] percpu: Embedded 15 pages/cpu s29068 r8192 d24180 u61440 [ 0.000000] pcpu-alloc: s29068 r8192 d24180 u61440 alloc=15*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Kernel command line: earlyprintk root=UUID=87d2bf72-4b91-4d33-8f77-284fa91fc3a7 console=ttyS2,115200n8 console=tty1 rootwait rootfstype=ext4 splash=verbose consoleblank=0 loglevel=1 ubootpart=569f1cc4-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080@60 drm.debug=0x4 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory [ 0.000000] Unknown kernel command line parameters "earlyprintk splash=verbose ubootpart=569f1cc4-01 cgroup_enable=memory cgroup_memory=1", will be passed to user space. [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 389632 [ 0.000000] allocated 1572864 bytes of page_ext [ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 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.000002] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.000021] Switching to timer-based delay loop, resolution 41ns [ 0.001537] Console: colour dummy device 80x30 [ 0.001574] printk: legacy console [tty1] enabled [ 0.001762] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.001796] CPU: Testing write buffer coherency: ok [ 0.001884] pid_max: default: 32768 minimum: 301 [ 0.002012] LSM: initializing lsm=capability,yama [ 0.002094] Yama: becoming mindful. [ 0.002310] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.002344] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.004354] /cpus/cpu@f00 missing clock-frequency property [ 0.004428] /cpus/cpu@f01 missing clock-frequency property [ 0.004463] /cpus/cpu@f02 missing clock-frequency property [ 0.004497] /cpus/cpu@f03 missing clock-frequency property [ 0.004521] CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00 [ 0.007200] Setting up static identity map for 0x60100000 - 0x60100060 [ 0.007577] rcu: Hierarchical SRCU implementation. [ 0.007598] rcu: Max phase no-delay instances is 1000. [ 0.008328] Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level [ 0.009570] smp: Bringing up secondary CPUs ... [ 0.011116] CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01 [ 0.013024] CPU2: thread -1, cpu 2, socket 15, mpidr 80000f02 [ 0.014710] CPU3: thread -1, cpu 3, socket 15, mpidr 80000f03 [ 0.014982] smp: Brought up 1 node, 4 CPUs [ 0.015018] SMP: Total of 4 processors activated (192.00 BogoMIPS). [ 0.015035] CPU: All CPU(s) started in SVC mode. [ 0.016494] Memory: 1486080K/1558528K available (16384K kernel code, 1300K rwdata, 9104K rodata, 1024K init, 458K bss, 53660K reserved, 16384K cma-reserved, 507904K highmem) [ 0.017485] devtmpfs: initialized [ 0.031052] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 [ 0.031485] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.031534] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.033000] pinctrl core: initialized pinctrl subsystem [ 0.035570] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.038008] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.038970] audit: initializing netlink subsys (disabled) [ 0.039543] audit: type=2000 audit(0.036:1): state=initialized audit_enabled=0 res=1 [ 0.040877] thermal_sys: Registered thermal governor 'step_wise' [ 0.041077] cpuidle: using governor ladder [ 0.041190] cpuidle: using governor menu [ 0.041683] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.041713] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.045970] /i2s1@100b0000: Fixed dependency cycle(s) with /codec@12010000 [ 0.046140] /codec@12010000: Fixed dependency cycle(s) with /i2s1@100b0000 [ 0.058852] /vop@20050000: Fixed dependency cycle(s) with /hdmi@200a0000 [ 0.059013] /i2s0@100c0000: Fixed dependency cycle(s) with /hdmi@200a0000 [ 0.059132] /hdmi@200a0000: Fixed dependency cycle(s) with /i2s0@100c0000 [ 0.059245] /hdmi@200a0000: Fixed dependency cycle(s) with /vop@20050000 [ 0.072919] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.073819] rockchip-gpio 11110000.gpio: probed /pinctrl/gpio@11110000 [ 0.074717] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.075377] rockchip-gpio 11120000.gpio: probed /pinctrl/gpio@11120000 [ 0.075968] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.076561] rockchip-gpio 11130000.gpio: probed /pinctrl/gpio@11130000 [ 0.077258] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.077875] rockchip-gpio 11140000.gpio: probed /pinctrl/gpio@11140000 [ 0.085807] /spdif@100d0000: Fixed dependency cycle(s) with /spdif-out [ 0.085959] /spdif-out: Fixed dependency cycle(s) with /spdif@100d0000 [ 0.086699] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible. [ 0.157193] raid6: neonx8 gen() 509 MB/s [ 0.225373] raid6: neonx4 gen() 732 MB/s [ 0.293582] raid6: neonx2 gen() 735 MB/s [ 0.361776] raid6: neonx1 gen() 602 MB/s [ 0.429982] raid6: int32x8 gen() 191 MB/s [ 0.498182] raid6: int32x4 gen() 199 MB/s [ 0.566457] raid6: int32x2 gen() 241 MB/s [ 0.634668] raid6: int32x1 gen() 250 MB/s [ 0.634686] raid6: using algorithm neonx2 gen() 735 MB/s [ 0.702770] raid6: .... xor() 546 MB/s, rmw enabled [ 0.702788] raid6: using neon recovery algorithm [ 0.704572] iommu: Default domain type: Translated [ 0.704629] iommu: DMA domain TLB invalidation policy: strict mode [ 0.709665] SCSI subsystem initialized [ 0.710037] usbcore: registered new interface driver usbfs [ 0.710113] usbcore: registered new interface driver hub [ 0.710210] usbcore: registered new device driver usb [ 0.710442] mc: Linux media interface: v0.10 [ 0.710536] videodev: Linux video capture interface: v2.00 [ 0.710720] pps_core: LinuxPPS API ver. 1 registered [ 0.710735] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.710768] PTP clock support registered [ 0.713955] Bluetooth: Core ver 2.22 [ 0.714071] NET: Registered PF_BLUETOOTH protocol family [ 0.714088] Bluetooth: HCI device and connection manager initialized [ 0.714110] Bluetooth: HCI socket layer initialized [ 0.714126] Bluetooth: L2CAP socket layer initialized [ 0.714170] Bluetooth: SCO socket layer initialized [ 0.714376] NetLabel: Initializing [ 0.714389] NetLabel: domain hash size = 128 [ 0.714401] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.714541] NetLabel: unlabeled traffic allowed by default [ 0.716025] clocksource: Switched to clocksource arch_sys_counter [ 0.716561] VFS: Disk quotas dquot_6.6.0 [ 0.716627] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.734747] NET: Registered PF_INET protocol family [ 0.735150] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.829855] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 0.829940] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.830302] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.830426] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 0.830797] TCP: Hash tables configured (established 8192 bind 8192) [ 0.831023] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.831127] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.831578] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.834711] Trying to unpack rootfs image as initramfs... [ 0.836190] Initialise system trusted keyrings [ 0.836798] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 0.836919] zbud: loaded [ 0.838518] SGI XFS with ACLs, security attributes, realtime, scrub, quota, fatal assert, debug enabled [ 1.130118] xor: measuring software checksum speed [ 1.134399] arm4regs : 774 MB/sec [ 1.139665] 8regs : 630 MB/sec [ 1.144950] 32regs : 626 MB/sec [ 1.148071] neon : 1067 MB/sec [ 1.148109] xor: using function: neon (1067 MB/sec) [ 1.148140] async_tx: api initialized (async) [ 1.148163] Key type asymmetric registered [ 1.148180] Asymmetric key parser 'x509' registered [ 1.148436] bounce: pool size: 64 pages [ 1.148613] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 242) [ 1.149266] io scheduler mq-deadline registered [ 1.149302] io scheduler kyber registered [ 1.149377] io scheduler bfq registered [ 1.556569] Freeing initrd memory: 8756K [ 1.560194] ledtrig-cpu: registered to indicate activity on CPUs [ 1.566071] dma-pl330 110f0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 1.566123] dma-pl330 110f0000.dma-controller: DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16 [ 1.571349] Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled [ 1.578535] printk: legacy console [ttyS2] disabled [ 1.579334] 11030000.serial: ttyS2 at MMIO 0x11030000 (irq = 38, base_baud = 1500000) is a 16550A [ 1.580263] printk: legacy console [ttyS2] enabled [ 1.587196] rockchip-vop 20050000.vop: Adding to iommu group 0 [ 1.591157] usbcore: registered new interface driver udl [ 1.592989] brd: module loaded [ 1.604785] loop: module loaded [ 1.608234] tun: Universal TUN/TAP device driver, 1.6 [ 1.608732] CAN device driver interface [ 1.610064] rk_gmac-dwmac 30200000.ethernet: IRQ eth_wake_irq not found [ 1.610098] rk_gmac-dwmac 30200000.ethernet: IRQ eth_lpi not found [ 1.610117] rk_gmac-dwmac 30200000.ethernet: IRQ sfty not found [ 1.610322] rk_gmac-dwmac 30200000.ethernet: PTP uses main clock [ 1.610662] rk_gmac-dwmac 30200000.ethernet: clock input or output? (output). [ 1.610693] rk_gmac-dwmac 30200000.ethernet: TX delay(0x26). [ 1.610712] rk_gmac-dwmac 30200000.ethernet: RX delay(0x11). [ 1.610754] rk_gmac-dwmac 30200000.ethernet: integrated PHY? (yes). [ 1.616088] rk_gmac-dwmac 30200000.ethernet: init for RMII [ 1.652669] rk_gmac-dwmac 30200000.ethernet: User ID: 0x10, Synopsys ID: 0x35 [ 1.652727] rk_gmac-dwmac 30200000.ethernet: DWMAC1000 [ 1.652749] rk_gmac-dwmac 30200000.ethernet: DMA HW capability register supported [ 1.652765] rk_gmac-dwmac 30200000.ethernet: RX Checksum Offload Engine supported [ 1.652779] rk_gmac-dwmac 30200000.ethernet: COE Type 2 [ 1.652797] rk_gmac-dwmac 30200000.ethernet: TX Checksum insertion supported [ 1.652811] rk_gmac-dwmac 30200000.ethernet: Wake-Up On Lan supported [ 1.652957] rk_gmac-dwmac 30200000.ethernet: Normal descriptors [ 1.652977] rk_gmac-dwmac 30200000.ethernet: Ring mode enabled [ 1.652992] rk_gmac-dwmac 30200000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 1.677755] usbcore: registered new interface driver rt2500usb [ 1.677890] usbcore: registered new interface driver rt73usb [ 1.677980] usbcore: registered new interface driver rt2800usb [ 1.678061] usbcore: registered new interface driver cdc_ether [ 1.678157] usbcore: registered new interface driver rndis_host [ 1.679282] dwc2 30040000.usb: supply vusb_d not found, using dummy regulator [ 1.679532] dwc2 30040000.usb: supply vusb_a not found, using dummy regulator [ 1.701461] dwc2 30040000.usb: DWC OTG Controller [ 1.701556] dwc2 30040000.usb: new USB bus registered, assigned bus number 1 [ 1.701629] dwc2 30040000.usb: irq 44, io mem 0x30040000 [ 1.702067] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12 [ 1.702097] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.702116] usb usb1: Product: DWC OTG Controller [ 1.702132] usb usb1: Manufacturer: Linux 6.12.37-current-rockchip dwc2_hsotg [ 1.702148] usb usb1: SerialNumber: 30040000.usb [ 1.703363] hub 1-0:1.0: USB hub found [ 1.703469] hub 1-0:1.0: 1 port detected [ 1.708644] usbcore: registered new interface driver usb-storage [ 1.710262] ehci-platform 300c0000.usb: EHCI Host Controller [ 1.710335] ehci-platform 30080000.usb: EHCI Host Controller [ 1.711082] usbcore: registered new interface driver iforce [ 1.711316] usbcore: registered new interface driver xpad [ 1.711316] ohci-platform 300e0000.usb: Generic Platform OHCI controller [ 1.711630] usbcore: registered new interface driver usbtouchscreen [ 1.711681] ehci-platform 30080000.usb: new USB bus registered, assigned bus number 3 [ 1.711681] ehci-platform 300c0000.usb: new USB bus registered, assigned bus number 2 [ 1.711837] ohci-platform 300a0000.usb: Generic Platform OHCI controller [ 1.711881] ehci-platform 30100000.usb: EHCI Host Controller [ 1.712537] ohci-platform 300e0000.usb: new USB bus registered, assigned bus number 4 [ 1.712588] ohci-platform 300a0000.usb: new USB bus registered, assigned bus number 5 [ 1.712690] ehci-platform 30100000.usb: new USB bus registered, assigned bus number 6 [ 1.712742] ohci-platform 30120000.usb: Generic Platform OHCI controller [ 1.713205] i2c_dev: i2c /dev entries driver [ 1.713410] ohci-platform 30120000.usb: new USB bus registered, assigned bus number 7 [ 1.714175] ohci-platform 300e0000.usb: irq 49, io mem 0x300e0000 [ 1.715620] ohci-platform 300a0000.usb: irq 48, io mem 0x300a0000 [ 1.716792] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@lists.linux.dev [ 1.718127] Bluetooth: HCI UART driver ver 2.3 [ 1.718169] Bluetooth: HCI UART protocol H4 registered [ 1.718184] Bluetooth: HCI UART protocol ATH3K registered [ 1.718278] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.718470] ehci-platform 30080000.usb: irq 45, io mem 0x30080000 [ 1.718510] Bluetooth: HCI UART protocol Broadcom registered [ 1.718658] usbcore: registered new interface driver bfusb [ 1.718814] usbcore: registered new interface driver btusb [ 1.719120] ohci-platform 30120000.usb: irq 50, io mem 0x30120000 [ 1.719646] ehci-platform 30100000.usb: irq 47, io mem 0x30100000 [ 1.720683] sdhci: Secure Digital Host Controller Interface driver [ 1.720714] sdhci: Copyright(c) Pierre Ossman [ 1.720726] Synopsys Designware Multimedia Card Interface Driver [ 1.720909] ehci-platform 300c0000.usb: irq 46, io mem 0x300c0000 [ 1.721454] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.721622] hid: raw HID events driver (C) Jiri Kosina [ 1.722359] usbcore: registered new interface driver usbhid [ 1.722398] usbhid: USB HID core driver [ 1.722956] dwmmc_rockchip 30000000.mmc: IDMAC supports 32-bit address mode. [ 1.723087] rockchip-dfi 11210000.dfi: dfi initialized, dram type: 0x6, channels: 1 [ 1.723936] dwmmc_rockchip 30000000.mmc: Using internal DMA controller. [ 1.724089] dwmmc_rockchip 30000000.mmc: Version ID is 270a [ 1.724219] dwmmc_rockchip 30000000.mmc: DW MMC controller at irq 51,32 bit host data width,256 deep fifo [ 1.724661] dwmmc_rockchip 30000000.mmc: Got CD GPIO [ 1.724701] dwmmc_rockchip 30010000.mmc: IDMAC supports 32-bit address mode. [ 1.724992] dwmmc_rockchip 30020000.mmc: IDMAC supports 32-bit address mode. [ 1.726553] dwmmc_rockchip 30010000.mmc: Using internal DMA controller. [ 1.726607] dwmmc_rockchip 30010000.mmc: Version ID is 270a [ 1.726720] dwmmc_rockchip 30010000.mmc: DW MMC controller at irq 52,32 bit host data width,256 deep fifo [ 1.727046] dwmmc_rockchip 30010000.mmc: allocated mmc-pwrseq [ 1.727051] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 (8000000f) counters available [ 1.727081] mmc_host mmc1: card is non-removable. [ 1.727587] dwmmc_rockchip 30020000.mmc: Using internal DMA controller. [ 1.727630] dwmmc_rockchip 30020000.mmc: Version ID is 270a [ 1.727724] dwmmc_rockchip 30020000.mmc: DW MMC controller at irq 53,32 bit host data width,256 deep fifo [ 1.728187] mmc_host mmc2: card is non-removable. [ 1.728216] ehci-platform 30080000.usb: USB 2.0 started, EHCI 1.00 [ 1.728726] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12 [ 1.728770] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.728791] usb usb3: Product: EHCI Host Controller [ 1.728807] usb usb3: Manufacturer: Linux 6.12.37-current-rockchip ehci_hcd [ 1.728824] usb usb3: SerialNumber: 30080000.usb [ 1.730118] hub 3-0:1.0: USB hub found [ 1.730501] hub 3-0:1.0: 1 port detected [ 1.731351] NET: Registered PF_INET6 protocol family [ 1.734443] Segment Routing with IPv6 [ 1.734583] In-situ OAM (IOAM) with IPv6 [ 1.734814] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 1.736185] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 1.737121] NET: Registered PF_PACKET protocol family [ 1.737197] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 1.737217] can: controller area network core [ 1.737290] NET: Registered PF_CAN protocol family [ 1.737718] Bluetooth: RFCOMM TTY layer initialized [ 1.737775] Bluetooth: RFCOMM socket layer initialized [ 1.737832] Bluetooth: RFCOMM ver 1.11 [ 1.737864] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 1.737886] Bluetooth: HIDP socket layer initialized [ 1.738362] Key type dns_resolver registered [ 1.738760] ThumbEE CPU extension supported. [ 1.738797] Registering SWP/SWPB emulation handler [ 1.740111] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 1.740157] ehci-platform 30100000.usb: USB 2.0 started, EHCI 1.00 [ 1.740288] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 1.740633] usb usb6: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12 [ 1.740667] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.740688] usb usb6: Product: EHCI Host Controller [ 1.740705] usb usb6: Manufacturer: Linux 6.12.37-current-rockchip ehci_hcd [ 1.740721] usb usb6: SerialNumber: 30100000.usb [ 1.742226] hub 6-0:1.0: USB hub found [ 1.742341] hub 6-0:1.0: 1 port detected [ 1.752147] ehci-platform 300c0000.usb: USB 2.0 started, EHCI 1.00 [ 1.752947] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12 [ 1.752993] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753014] usb usb2: Product: EHCI Host Controller [ 1.753030] usb usb2: Manufacturer: Linux 6.12.37-current-rockchip ehci_hcd [ 1.753047] usb usb2: SerialNumber: 300c0000.usb [ 1.754834] hub 2-0:1.0: USB hub found [ 1.754958] hub 2-0:1.0: 1 port detected [ 1.759358] registered taskstats version 1 [ 1.759781] Loading compiled-in X.509 certificates [ 1.772947] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.12 [ 1.773012] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.773037] usb usb4: Product: Generic Platform OHCI controller [ 1.773056] usb usb4: Manufacturer: Linux 6.12.37-current-rockchip ohci_hcd [ 1.773073] usb usb4: SerialNumber: 300e0000.usb [ 1.773199] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.775696] hub 4-0:1.0: USB hub found [ 1.775777] mmc1: new high speed SDIO card at address 0001 [ 1.776303] hub 4-0:1.0: 1 port detected [ 1.778355] zswap: loaded using pool zstd/zbud [ 1.779650] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.12 [ 1.779706] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.779726] usb usb5: Product: Generic Platform OHCI controller [ 1.779743] usb usb5: Manufacturer: Linux 6.12.37-current-rockchip ohci_hcd [ 1.779761] usb usb5: SerialNumber: 300a0000.usb [ 1.780820] Key type .fscrypt registered [ 1.780861] Key type fscrypt-provisioning registered [ 1.781113] hub 5-0:1.0: USB hub found [ 1.781252] hub 5-0:1.0: 1 port detected [ 1.782665] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.12 [ 1.782715] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.782735] usb usb7: Product: Generic Platform OHCI controller [ 1.782752] usb usb7: Manufacturer: Linux 6.12.37-current-rockchip ohci_hcd [ 1.782769] usb usb7: SerialNumber: 30120000.usb [ 1.783091] Btrfs loaded, zoned=no, fsverity=no [ 1.783970] hub 7-0:1.0: USB hub found [ 1.784189] hub 7-0:1.0: 1 port detected [ 1.848557] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0) [ 1.849018] mmc2: new high speed MMC card at address 0001 [ 1.850668] mmcblk2: mmc2:0001 QN16MB 7.28 GiB [ 1.854231] mmcblk2: p1 [ 1.855672] mmcblk2boot0: mmc2:0001 QN16MB 4.00 MiB [ 1.859480] mmcblk2boot1: mmc2:0001 QN16MB 4.00 MiB [ 1.862788] mmcblk2rpmb: mmc2:0001 QN16MB 512 KiB, chardev (239:0) [ 1.976094] Key type encrypted registered [ 1.988215] usb 1-1: new full-speed USB device number 2 using dwc2 [ 1.995738] inno-hdmi-phy 12030000.hdmi-phy: error -ENXIO: IRQ index 0 not found [ 1.996292] inno-hdmi-phy 12030000.hdmi-phy: phy_flag is: 0 [ 1.999254] rockchip-drm display-subsystem: bound 20050000.vop (ops 0xb1189588) [ 1.999438] dwhdmi-rockchip 200a0000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 1.999758] dwhdmi-rockchip 200a0000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.000383] dwhdmi-rockchip 200a0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (inno_dw_hdmi_phy2) [ 2.001885] dwhdmi-rockchip 200a0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.002350] [drm:__drm_connector_init] cmdline mode for connector HDMI-A-1 1920x1080@60Hz [ 2.002454] rockchip-drm display-subsystem: bound 200a0000.hdmi (ops 0xb118d904) [ 2.003642] rockchip-drm display-subsystem: [drm:drm_sysfs_connector_add] [CONNECTOR:47:HDMI-A-1] adding connector to sysfs [ 2.003976] rockchip-drm display-subsystem: [drm:drm_sysfs_connector_hotplug_event] [CONNECTOR:47:HDMI-A-1] generating connector hotplug event [ 2.004124] [drm] Initialized rockchip 1.0.0 for display-subsystem on minor 0 [ 2.004171] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [ 2.004230] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:47:HDMI-A-1] [ 2.004283] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:47:HDMI-A-1] status updated from unknown to connected [ 2.004378] rockchip-drm display-subsystem: [drm:drm_sysfs_hotplug_event] generating hotplug event [ 2.184813] usb 1-1: New USB device found, idVendor=045e, idProduct=0745, bcdDevice= 6.76 [ 2.184878] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.184899] usb 1-1: Product: Microsoft® 2.4GHz Transceiver v8.0 [ 2.184915] usb 1-1: Manufacturer: Microsoft [ 2.194119] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 as /devices/platform/30040000.usb/usb1/1-1/1-1:1.0/0003:045E:0745.0001/input/input0 [ 2.224332] EDID block 0 (tag 0x00) checksum is invalid, remainder is 198 [ 2.224372] rockchip-drm display-subsystem: [drm:connector_bad_edid] [CONNECTOR:47:HDMI-A-1] EDID is invalid: [ 2.224424] [00] BAD 00 ff ff ff ff ff ff 00 04 69 fd 22 01 37 02 00 [ 2.224438] [00] BAD 2b 15 01 03 80 30 1b 78 2a 2a c5 a4 56 4f 9e 28 [ 2.224451] [00] BAD 00 50 54 b7 ef 00 d1 c0 81 40 81 80 95 00 b3 00 [ 2.224463] [00] BAD 71 4f 81 c0 81 00 02 3a 80 18 71 38 2d 40 58 2c [ 2.224476] [00] BAD 45 00 dc 0c 11 00 00 1e 00 00 00 ff 00 42 41 4c [ 2.224488] [00] BAD 4d 54 46 31 34 35 31 35 33 0a 00 00 00 fd 00 32 [ 2.224501] [00] BAD 4b 18 53 11 00 0a 20 20 20 20 20 20 00 00 00 fc [ 2.224513] [00] BAD 00 41 53 55 53 20 56 53 32 32 38 0a 20 20 01 b7 [ 2.225478] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "640x480": 60 25175 640 656 752 800 480 490 492 525 0x40 0xa (BAD) [ 2.225529] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "848x480": 60 33750 848 864 976 1088 480 486 494 517 0x40 0x5 (BAD) [ 2.225568] rockchip-drm display-subsystem: [drm] User-defined mode not supported: "1920x1080": 60 172780 1920 2040 2248 2576 1080 1081 1084 1118 0x20 0x6 [ 2.225598] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "1920x1080": 60 172780 1920 2040 2248 2576 1080 1081 1084 1118 0x20 0x6 (BAD) [ 2.225642] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:47:HDMI-A-1] probed modes: [ 2.225678] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] Probed mode: "1024x768": 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa [ 2.225721] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] Probed mode: "800x600": 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5 [ 2.225763] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] Probed mode: "800x600": 56 36000 800 824 896 1024 600 601 603 625 0x40 0x5 [ 2.225805] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] enabled? yes [ 2.225849] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] Not using firmware configuration [ 2.225881] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] looking for cmdline mode [ 2.225911] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] looking for preferred mode, tile 0 [ 2.225941] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] Found mode 1024x768 [ 2.225969] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] picking CRTCs for 4096x4096 config [ 2.226002] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CRTC:45:crtc-0] desired mode 1024x768 set (0,0) [ 2.226043] rockchip-drm display-subsystem: [drm:__drm_fb_helper_initial_config_and_unlock] test CRTC 0 primary plane [ 2.226088] rockchip-drm display-subsystem: [drm:drm_fbdev_dma_driver_fbdev_probe] surface width(1024), height(768) and bpp(32) [ 2.236082] rockchip-drm display-subsystem: [drm:drm_mode_addfb2] [FB:50] [ 2.242643] Console: switching to colour frame buffer device 128x48 [ 2.249949] hid-generic 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-30040000.usb-1/input0 [ 2.266243] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 Mouse as /devices/platform/30040000.usb/usb1/1-1/1-1:1.1/0003:045E:0745.0002/input/input1 [ 2.267284] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control as /devices/platform/30040000.usb/usb1/1-1/1-1:1.1/0003:045E:0745.0002/input/input2 [ 2.271583] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device [ 2.272078] rockchip-drm display-subsystem: [drm:drm_fb_helper_hotplug_event] [ 2.272203] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [ 2.272257] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:47:HDMI-A-1] [ 2.272638] of_cfs_init [ 2.272752] of_cfs_init: OK [ 2.321368] hid-generic 0003:045E:0745.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-30040000.usb-1/input1 [ 2.337205] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control as /devices/platform/30040000.usb/usb1/1-1/1-1:1.2/0003:045E:0745.0003/input/input3 [ 2.393210] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 System Control as /devices/platform/30040000.usb/usb1/1-1/1-1:1.2/0003:045E:0745.0003/input/input5 [ 2.394900] hid-generic 0003:045E:0745.0003: input,hiddev96,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-30040000.usb-1/input2 [ 2.490255] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 2.513688] EDID block 0 (tag 0x00) checksum is invalid, remainder is 198 [ 2.513765] rockchip-drm display-subsystem: [drm:connector_bad_edid] [CONNECTOR:47:HDMI-A-1] EDID is invalid: [ 2.513828] [00] BAD 00 ff ff ff ff ff ff 00 04 69 fd 22 01 37 02 00 [ 2.513847] [00] BAD 2b 15 01 03 80 30 1b 78 2a 2a c5 a4 56 4f 9e 28 [ 2.513860] [00] BAD 00 50 54 b7 ef 00 d1 c0 81 40 81 80 95 00 b3 00 [ 2.513876] [00] BAD 71 4f 81 c0 81 00 02 3a 80 18 71 38 2d 40 58 2c [ 2.513888] [00] BAD 45 00 dc 0c 11 00 00 1e 00 00 00 ff 00 42 41 4c [ 2.513901] [00] BAD 4d 54 46 31 34 35 31 35 33 0a 00 00 00 fd 00 32 [ 2.513916] [00] BAD 4b 18 53 11 00 0a 20 20 20 20 20 20 00 00 00 fc [ 2.513940] [00] BAD 00 41 53 55 53 20 56 53 32 32 38 0a 20 20 01 b7 [ 2.514854] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "640x480": 60 25175 640 656 752 800 480 490 492 525 0x40 0xa (BAD) [ 2.514958] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "848x480": 60 33750 848 864 976 1088 480 486 494 517 0x40 0x5 (BAD) [ 2.515047] rockchip-drm display-subsystem: [drm] User-defined mode not supported: "1920x1080": 60 172780 1920 2040 2248 2576 1080 1081 1084 1118 0x20 0x6 [ 2.515079] rockchip-drm display-subsystem: [drm:drm_mode_prune_invalid] Rejected mode: "1920x1080": 60 172780 1920 2040 2248 2576 1080 1081 1084 1118 0x20 0x6 (VIRTUAL_X) [ 2.515130] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:47:HDMI-A-1] probed modes: [ 2.515204] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] Probed mode: "1024x768": 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa [ 2.515256] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] Probed mode: "800x600": 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5 [ 2.515299] rockchip-drm display-subsystem: [drm:drm_helper_probe_single_connector_modes] Probed mode: "800x600": 56 36000 800 824 896 1024 600 601 603 625 0x40 0x5 [ 2.515344] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] enabled? yes [ 2.515395] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] Not using firmware configuration [ 2.515431] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] looking for cmdline mode [ 2.515483] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] looking for preferred mode, tile 0 [ 2.515516] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CONNECTOR:47:HDMI-A-1] Found mode 1024x768 [ 2.515546] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] picking CRTCs for 1024x768 config [ 2.515588] rockchip-drm display-subsystem: [drm:drm_client_modeset_probe] [CRTC:45:crtc-0] desired mode 1024x768 set (0,0) [ 2.526055] rockchip-drm display-subsystem: [drm:drm_client_dev_hotplug] fbdev: ret=0 [ 2.537979] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 2.540563] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' [ 2.540754] clk: Disabling unused clocks [ 2.540998] PM: genpd: Disabling unused power domains [ 2.544535] Freeing unused kernel image (initmem) memory: 1024K [ 2.545305] Run /init as init process [ 2.545335] with arguments: [ 2.545347] /init [ 2.545359] earlyprintk [ 2.545370] with environment: [ 2.545379] HOME=/ [ 2.545389] TERM=linux [ 2.545399] splash=verbose [ 2.545410] ubootpart=569f1cc4-01 [ 2.545421] cgroup_enable=memory [ 2.545431] cgroup_memory=1 [ 2.548179] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid [ 3.534285] rk_gmac-dwmac 30200000.ethernet end0: renamed from eth0 [ 4.200467] EXT4-fs (mmcblk2p1): mounted filesystem 87d2bf72-4b91-4d33-8f77-284fa91fc3a7 ro with writeback data mode. Quota mode: none. [ 4.742875] systemd[1]: System time before build time, advancing clock. [ 4.786705] systemd[1]: systemd 252.38-1~deb12u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) [ 4.786850] systemd[1]: Detected architecture arm. [ 4.794711] systemd[1]: Hostname set to <rk322x-box>. [ 5.040997] dw-apb-uart 11030000.serial: forbid DMA for kernel console [ 6.235862] systemd[1]: Queued start job for default target graphical.target. [ 6.285959] systemd[1]: Created slice system-getty.slice - Slice /system/getty. [ 6.292737] systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe. [ 6.298346] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty. [ 6.302571] systemd[1]: Created slice user.slice - User and Session Slice. [ 6.304498] systemd[1]: Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch. [ 6.306231] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch. [ 6.310274] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point. [ 6.311776] systemd[1]: Expecting device dev-ttyS2.device - /dev/ttyS2... [ 6.312895] systemd[1]: Expecting device sys-subsystem-net-devices-wlan1.device - /sys/subsystem/net/devices/wlan1... [ 6.314021] systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes. [ 6.315299] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes. [ 6.317065] systemd[1]: Reached target paths.target - Path Units. [ 6.318279] systemd[1]: Reached target remote-fs.target - Remote File Systems. [ 6.319179] systemd[1]: Reached target slices.target - Slice Units. [ 6.320528] systemd[1]: Reached target swap.target - Swaps. [ 6.321812] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes. [ 6.324574] systemd[1]: Listening on syslog.socket - Syslog Socket. [ 6.327737] systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket. [ 6.329864] systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe. [ 6.333579] systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket. [ 6.336332] systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log). [ 6.339139] systemd[1]: Listening on systemd-journald.socket - Journal Socket. [ 6.342097] systemd[1]: Listening on systemd-networkd.socket - Network Service Netlink Socket. [ 6.345265] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket. [ 6.347577] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket. [ 6.350078] systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages). [ 6.392957] systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System... [ 6.405914] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System... [ 6.408791] systemd[1]: sys-kernel-tracing.mount - Kernel Trace File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/tracing). [ 6.426013] systemd[1]: Starting fake-hwclock.service - Restore / save the current clock... [ 6.445172] systemd[1]: Starting keyboard-setup.service - Set the console keyboard layout... [ 6.462477] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes... [ 6.482338] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs... [ 6.501344] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... [ 6.541538] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 6.568875] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore... [ 6.597664] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse... [ 6.624402] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop... [ 6.633571] systemd[1]: netplan-ovs-cleanup.service - OpenVSwitch configuration for cleanup was skipped because of an unmet condition check (ConditionFileIsExecutable=/usr/bin/ovs-vsctl). [ 6.635856] systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root). [ 6.658033] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules... [ 6.682483] systemd[1]: Starting systemd-network-generator.service - Generate network units from Kernel command line... [ 6.684562] fuse: init (API version 7.41) [ 6.707461] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... [ 6.759355] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... [ 6.819418] systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System. [ 6.835177] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System. [ 6.852474] systemd[1]: Finished fake-hwclock.service - Restore / save the current clock. [ 6.868339] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes. [ 6.883963] systemd[1]: modprobe@configfs.service: Deactivated successfully. [ 6.886599] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs. [ 6.901591] systemd[1]: modprobe@dm_mod.service: Deactivated successfully. [ 6.903917] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. [ 6.904733] EXT4-fs (mmcblk2p1): re-mounted 87d2bf72-4b91-4d33-8f77-284fa91fc3a7 r/w. [ 6.932289] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 6.934824] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [ 6.950309] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. [ 6.952740] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. [ 6.967737] systemd[1]: modprobe@fuse.service: Deactivated successfully. [ 6.970509] systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse. [ 6.985545] systemd[1]: modprobe@loop.service: Deactivated successfully. [ 6.987943] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. [ 7.003440] systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules. [ 7.018229] systemd[1]: Finished systemd-network-generator.service - Generate network units from Kernel command line. [ 7.033299] systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems. [ 7.048487] systemd[1]: Reached target network-pre.target - Preparation for Network. [ 7.150273] systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System... [ 7.177375] systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System... [ 7.186320] systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). [ 7.207503] systemd[1]: Starting systemd-random-seed.service - Load/Save Random Seed... [ 7.221472] systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. [ 7.236367] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables... [ 7.260573] systemd[1]: Starting systemd-sysusers.service - Create System Users... [ 7.330514] systemd[1]: Finished keyboard-setup.service - Set the console keyboard layout. [ 7.350029] systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control File System. [ 7.362299] systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System. [ 7.596443] systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables. [ 7.676481] systemd[1]: Finished systemd-sysusers.service - Create System Users. [ 7.729777] systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev... [ 7.784179] systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices. [ 7.854608] systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev. [ 7.865899] systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems. [ 7.908963] systemd[1]: Mounting tmp.mount - /tmp... [ 7.935113] systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files... [ 7.955696] systemd[1]: Mounted tmp.mount - /tmp. [ 7.966550] systemd[1]: Reached target local-fs.target - Local File Systems. [ 8.005809] systemd[1]: Starting armbian-zram-config.service - Armbian ZRAM config... [ 8.041138] systemd[1]: Starting console-setup.service - Set console font and keymap... [ 8.102165] systemd[1]: Starting systemd-binfmt.service - Set Up Additional Binary Formats... [ 8.137016] systemd[1]: Finished console-setup.service - Set console font and keymap. [ 8.206868] systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 272 (systemd-binfmt) [ 8.232197] random: crng init done [ 8.249009] systemd[1]: Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System... [ 8.273466] systemd[1]: Finished systemd-random-seed.service - Load/Save Random Seed. [ 8.285768] systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). [ 8.286491] systemd[1]: systemd-machine-id-commit.service - Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id). [ 8.329852] systemd[1]: Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System. [ 8.371793] systemd[1]: Finished systemd-binfmt.service - Set Up Additional Binary Formats. [ 8.429868] systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files. [ 8.521900] systemd[1]: Starting systemd-networkd.service - Network Configuration... [ 8.569563] zram: Added device: zram0 [ 8.573033] zram: Added device: zram1 [ 8.576864] zram: Added device: zram2 [ 8.905905] systemd[1]: Found device dev-ttyS2.device - /dev/ttyS2. [ 9.128868] zram0: detected capacity change from 0 to 1514648 [ 9.246736] Adding 757320k swap on /dev/zram0. Priority:5 extents:1 across:757320k SS [ 9.463515] dw_wdt 110a0000.watchdog: No valid TOPs array specified [ 9.573447] rk3288-crypto 100a0000.cypto-controller: will run requests pump with realtime priority [ 9.573706] rk3288-crypto 100a0000.cypto-controller: Register ecb(aes) as ecb-aes-rk [ 9.573899] rk3288-crypto 100a0000.cypto-controller: Register cbc(aes) as cbc-aes-rk [ 9.573961] rk3288-crypto 100a0000.cypto-controller: Register ecb(des) as ecb-des-rk [ 9.573995] rk3288-crypto 100a0000.cypto-controller: Register cbc(des) as cbc-des-rk [ 9.574029] rk3288-crypto 100a0000.cypto-controller: Register ecb(des3_ede) as ecb-des3-ede-rk [ 9.574065] rk3288-crypto 100a0000.cypto-controller: Register cbc(des3_ede) as cbc-des3-ede-rk [ 9.574101] rk3288-crypto 100a0000.cypto-controller: Register sha1 as rk-sha1 [ 9.574140] rk3288-crypto 100a0000.cypto-controller: Register sha256 as rk-sha256 [ 9.574177] rk3288-crypto 100a0000.cypto-controller: Register md5 as rk-md5 [ 9.601478] zram1: detected capacity change from 0 to 102400 [ 9.696782] lima 20000000.gpu: gp - mali400 version major 1 minor 1 [ 9.697206] lima 20000000.gpu: pp0 - mali400 version major 1 minor 1 [ 9.697469] lima 20000000.gpu: pp1 - mali400 version major 1 minor 1 [ 9.697566] lima 20000000.gpu: l2_cache0 64K, 4-way, 64byte cache line, 64bit external bus [ 9.724305] lima 20000000.gpu: bus rate = 300000000 [ 9.724370] lima 20000000.gpu: mod rate = 300000000 [ 9.732972] [drm] Initialized lima 1.1.0 for 20000000.gpu on minor 1 [ 9.832883] rk3228-codec 12010000.codec: spk_depop_time use default value. [ 9.846722] rockchip-iep 20070000.iep: Adding to iommu group 1 [ 9.849318] rockchip-rga 20060000.rga: HW Version: 0x04.01 [ 9.852777] rockchip_vdec: module is from the staging directory, the quality is unknown, you have been warned. [ 9.855759] rkvdec 20030000.video-codec: Adding to iommu group 2 [ 9.862538] rockchip-iep 20070000.iep: Device rockchip-iep registered as /dev/video0 [ 9.871528] rockchip-rga 20060000.rga: Registered rockchip-rga as /dev/video1 [ 9.901063] systemd[1]: Finished armbian-zram-config.service - Armbian ZRAM config. [ 9.906203] hantro-vpu 20020000.video-codec: Adding to iommu group 3 [ 9.921274] hantro-vpu 20020000.video-codec: registered rockchip,rk3399-vpu-enc as /dev/video3 [ 9.931196] hantro-vpu 20020000.video-codec: registered rockchip,rk3399-vpu-dec as /dev/video4 [ 10.018602] systemd[1]: Starting armbian-ramlog.service - Armbian memory supported logging... [ 10.056821] rk_gmac-dwmac 30200000.ethernet end0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 10.084624] systemd[1]: Started systemd-networkd.service - Network Configuration. [ 10.139812] rk_gmac-dwmac 30200000.ethernet end0: PHY [stmmac-0:00] driver [Rockchip integrated EPHY] (irq=POLL) [ 10.148254] rk_gmac-dwmac 30200000.ethernet end0: No Safety Features support found [ 10.148390] rk_gmac-dwmac 30200000.ethernet end0: PTP not supported by HW [ 10.161502] rk_gmac-dwmac 30200000.ethernet end0: configuring for phy/rmii link mode [ 10.245628] bFWReady == _FALSE call reset 8051... [ 10.251796] Registered IR keymap rc-rk322x-tvbox [ 10.361283] IR NEC protocol handler initialized [ 10.397007] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 10.397857] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 10.398516] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input6 [ 10.561893] EXT4-fs (zram1): mounted filesystem ba64ee27-d707-469d-a07c-e9950a485bb0 r/w without journal. Quota mode: none. [ 10.816713] systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch. [ 10.977894] systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... [ 11.166737] systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status. [ 11.378730] systemd[1]: Found device sys-subsystem-net-devices-wlan1.device - /sys/subsystem/net/devices/wlan1. [ 11.423829] systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages). [ 11.425058] systemd[1]: sys-kernel-tracing.mount - Kernel Trace File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/tracing). [ 11.465523] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... [ 11.491753] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore... [ 11.522134] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop... [ 11.549397] systemd[1]: Started netplan-wpa-wlan1.service - WPA supplicant for netplan wlan1. [ 11.560846] systemd[1]: systemd-machine-id-commit.service - Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id). [ 11.571626] systemd[1]: modprobe@dm_mod.service: Deactivated successfully. [ 11.576874] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. [ 11.601230] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. [ 11.605609] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. [ 11.619506] systemd[1]: modprobe@loop.service: Deactivated successfully. [ 11.622547] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. [ 11.635852] systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). [ 11.636764] systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. [ 11.797559] systemd[1]: Finished armbian-ramlog.service - Armbian memory supported logging. [ 11.933916] systemd[1]: Starting systemd-journald.service - Journal Service... [ 12.256824] rk_gmac-dwmac 30200000.ethernet end0: Link is Up - 100Mbps/Full - flow control off [ 12.445746] systemd[1]: Started systemd-journald.service - Journal Service. [ 12.572926] systemd-journald[501]: Received client request to flush runtime journal. [ 13.548872] ------------[ cut here ]------------ [ 13.548918] WARNING: CPU: 0 PID: 503 at net/wireless/nl80211.c:19591 cfg80211_ch_switch_notify+0x1e4/0x1e8 [ 13.548976] Modules linked in: snd_soc_hdmi_codec ir_nec_decoder snd_soc_spdif_tx gpio_ir_recv snd_soc_audio_graph_card2 8189es cpufreq_dt snd_soc_simple_card_utils hantro_vpu rockchip_vdec(C) dw_hdmi_i2s_audio rockchip_rga v4l2_jpeg rockchip_iep v4l2_vp9 v4l2_h264 videobuf2_dma_contig v4l2_mem2mem dw_hdmi_cec snd_soc_rk3228 snd_soc_rockchip_spdif snd_soc_rockchip_i2s snd_soc_core lima gpu_sched rockchip_thermal snd_pcm_dmaengine snd_pcm snd_timer rk_crypto snd soundcore dw_wdt crypto_engine zram zsmalloc binfmt_misc fuse gpio_keys [ 13.549307] CPU: 0 UID: 0 PID: 503 Comm: RTW_CMD_THREAD Tainted: G C 6.12.37-current-rockchip #1 [ 13.549336] Tainted: [C]=CRAP [ 13.549343] Hardware name: Generic DT based system [ 13.549353] Call trace: [ 13.549364] dump_backtrace from show_stack+0x18/0x1c [ 13.549399] r7:60010013 r6:60010013 r5:b132e5f0 r4:00000000 [ 13.549405] show_stack from dump_stack_lvl+0x5c/0x70 [ 13.549426] dump_stack_lvl from dump_stack+0x18/0x1c [ 13.549449] r7:00000009 r6:00004c87 r5:b0fe1b60 r4:b141ee8c [ 13.549453] dump_stack from __warn+0x84/0xe4 [ 13.549472] __warn from warn_slowpath_fmt+0x188/0x190 [ 13.549492] r7:b0fe1b60 r6:b141ee8c r5:00000000 r4:00000000 [ 13.549497] warn_slowpath_fmt from cfg80211_ch_switch_notify+0x1e4/0x1e8 [ 13.549516] r8:f2241e60 r7:b974d800 r6:b59d6800 r5:00000000 r4:b59d7800 [ 13.549521] cfg80211_ch_switch_notify from rtw_cfg80211_ch_switch_notify+0x10c/0x154 [8189es] [ 13.550454] r9:00000985 r8:b59d6a20 r7:00000000 r6:00000000 r5:00000985 r4:f202f000 [ 13.550464] rtw_cfg80211_ch_switch_notify [8189es] from rtw_chk_start_clnt_join+0x260/0x39c [8189es] [ 13.551327] r9:f202bba1 r8:00000000 r7:f2241f1a r6:f2241f19 r5:b3f51000 r4:f202b000 [ 13.551337] rtw_chk_start_clnt_join [8189es] from join_cmd_hdl+0x248/0x358 [8189es] [ 13.552011] r10:af28b058 r9:f202bba1 r8:af28b730 r7:f202bace r6:f202b661 r5:f202b662 [ 13.552019] r4:f202b000 [ 13.552024] join_cmd_hdl [8189es] from rtw_cmd_thread+0x158/0x418 [8189es] [ 13.552606] r9:f1977ec0 r8:b5472040 r7:f1977f0c r6:f1977ee0 r5:f1977000 r4:b5a2d1c0 [ 13.552613] rtw_cmd_thread [8189es] from kthread+0xe8/0x104 [ 13.552845] r10:00000000 r9:f19818f8 r8:b51de7c0 r7:f1977000 r6:af1b7e30 r5:b5472040 [ 13.552850] r4:b5697040 [ 13.552854] kthread from ret_from_fork+0x14/0x28 [ 13.552871] Exception stack(0xf2241fb0 to 0xf2241ff8) [ 13.552884] 1fa0: 00000000 00000000 00000000 00000000 [ 13.552894] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 13.552902] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 13.552912] r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:b014b998 r4:b5697040 [ 13.553251] ---[ end trace 0000000000000000 ]--- [ 15.288478] systemd-journald[501]: Received client request to relinquish /var/log/journal/ab96d43e6b5f4482985ef7d75c79e4f6 access.
  10. Maxxim
    A guide to installing Armbian on the H96 Max V11 (RK3318_V1.4 blue PCB) What you will need Your H96 Max V11 TV box with the power supply and the HDMI cable that came with it; A TV or a monitor with an HDMI port; A wired USB keyboard (or a wireless one with a USB dongle); An Ethernet cable to connect to a router on your home network that has Internet access; A Micro SD card (minimum 1GB, more if you're going to back up Android on your box before overwriting it with Armbian); A USB card reader for Micro SD cards; A Windows PC connected to your home network; Installation steps Download the experimental Armbian image (kernel 5.19.15 and libreelec patches — alas, that's the latest version that works correctly with our box) and a copy of the Multitool; Burn the Multitool on the SD card using Rufus (no need to change any settings, just click "SELECT" and locate multitool.img.xz or drag and drop the file on Rufus and then click "START"); Connect your TV box to the TV or monitor, connect the keyboard, plug in the Multitool SD card and then plug in the power cord; Wait a minute (while SD card partitions are being resized) for the Multitool main menu to appear, then select "Shutdown"; Unplug the power cord and the SD card, then plug the SD card into your PC. Two new drives should appear, labeled BOOTSTRAP and MULTITOOL. If you see both, skip the next step. If you only see the BOOTSTRAP, proceed to the next step; Start Disk Management (press Win+X, K). Scroll down the list of disks (use the scrollbar, because mouse wheel doesn't work there) to locate your SD card, and on the MULTITOOL partition right-click, then press C, and click "Add", "OK"; Open the MULTITOOL drive in Windows Explorer (or your favorite file manager) and copy the downloaded Armbian image to the images folder; Safely remove (eject) the SD card, plug it into the TV box and plug in the power cord. The Multitool main menu will appear in a few seconds; If you don't care about stock Android firmware on your TV box, skip the next step. If you want to back up the Android firmware, proceed to the next step; In the Multitool main menu select "Backup flash" and click through (there will be only one option). Name your backup file. Wait for the backup to finish. The backup file will be saved to the backups folder on the SD card's MULTITOOL partition; Now it's time to replace Android with Armbian. In the Multitool main menu select "Burn image to flash" and click through (there will be only one option). Wait for the process to complete, then in the main menu select "Shutdown"; Unplug the power cord and the SD card, then replug the power cord. Wait a few minutes for Armbian to get everything ready for its first launch, and then follow the initial setup prompts; You will be taken to the login prompt. Log in with the name/password for the regular user you've created; Connect your TV box to your home network router with an Ethernet cable; In Armbian, enter the command sudo cat /run/motd.dynamic and note the IP address assigned by the router to the TV box; Now you will need to connect to your TV box on the home network via the SSH protocol. If you're running Windows 10 or later, press Win+X, I, Enter. A PowerShell/Terminal window will open. Enter the following command, substituting the words in angle brackets with actual values: ssh <IP address from the previous step> -l <name for the regular user>. Type yes at the prompt asking if you really want to connect to this unknown host. At the next prompt that appears, enter the password for the regular user you've created. Skip the next step; If you're running an older version of Windows, you will need to download PuTTY, an SSH and Telnet client, set up an SSH connection to your TV box with the IP address above and log in with the name/password for the regular user; Now it's time to fix the settings for the Wi-Fi chip that doesn't work out of the box on the H96 Max V11. To delete the old settings, copy the command sudo rm -f /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt and paste it by right-clicking in the SSH window, then press Enter; To create the new settings file, enter (copy-paste) the command sudo nano /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt The nano text editor will open with a new empty file; Now open this small text file (a copy of nvram_2734c.txt from this forum topic), press Ctrl-A to select all text in it, then Ctrl-C to copy it to the clipboard; Switch to the SSH window, right-click to paste the copied text to nano then press Ctrl-S to save and Ctrl-X to exit; Enter (or copy-paste) the command sudo reboot -f to reboot Armbian. After that you can either close the SSH window and proceed with the physical console or start a new SSH session once Armbian has restarted; Enter (or copy-paste) the command sudo apt update && sudo apt install armbian-config After the update and installation is completed, run armbian-config to configure various software and hardware settings (including Wi-Fi). It is recommended to select "Freeze" in System settings to disable Armbian kernel upgrades because our kernel is compiled with custom patches enabling HDMI output on H96 Max V11 to work properly that are unavailable in other kernel versions.
  11. sicxnull
    Currently working on a build for this device. It boots and is about 90% functional on 6.6 and 6.7 Kernel https://github.com/sicXnull/armbian-build/tree/X96Q-TVBOX-LPDDR3 Working - Desktop - Ethernet - Wifi Not working - DTS could use some work. Right now it does not detect internal EMMC so installing to EMMC is not an option. - Likely other things i've missed. I've uploaded two images to my git. Full w/Mate Desktop Minimal/Server Feel free to compile this yourself if you don't trust my images, it's encouraged. Changes are on the X96Q-TVBOX-LPDDR3 Branch Full W/Desktop ./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm Minimal/Server ./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm
  12. Hqnicolas
    🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! This Armbian adventure was summarized in my Public Github Repository. H96 MAX V56 RK3566 8gb Ram SD-Card unofficial images: Tutorial SD-Card Version v0.5 ARMBIAN BETA unofficial H96 MAX V56 RK3566 8gb EMMC Chainloader to mainline HotnikQ unofficial images: Tutorial EMMC Version V0.7 ARMBIAN BETA unofficial H96 MAX V56 RK3566 8gb EMMC Mainline Boot Hzdm unofficial images: Tutorial EMMC Version v0.8 ARMBIAN unofficial H96 MAX V56 RK3566 8gb EMMC Mainline Boot Hzdm unofficial images: Tutorial EMMC Version v0.9 ARMBIAN BETA unofficial H96 MAX V56 RK3566 8gb EMMC Chainloader to mainline HotnikQ unofficial images: Tutorial EMMC Version v1.0 ARMBIAN unofficial H96 MAX V56 RK3566 8gb EMMC Hzdm Mainline Boot Custom unofficial images: Tutorial Build Your own Armbian EMMC unofficial image H96 MAX V56 RK3566 EMMC Raspiblitz HotnikQ unofficial images: Tutorial Build Raspiblitz on EMMC Armbian Bullseye unofficial H96 MAX V56 RK3566 8gb EMMC Hzdm Mainline Boot unofficial images: Tutorial Build Your own V1.1 Armbian EMMC unofficial image H96 MAX V56 RK3566 8gb Vendor Kernel 5.1.16 Tutorial Build Your own Armbian Rockchip Kernel vendor Kernel 5.1.16 Armbian Joshua Riek Ubuntu Rockchip Images kernel 5.1 H96 MAX V56 RK3566 8gb Vendor Kernel 6.1.43 Tutorial Build Your own Armbian Rockchip Kernel vendor Kernel 6.1.43 Armbian Joshua Riek Ubuntu Rockchip Images Kernel 6.1 H96 MAX V56 RK3566 8gb EMMC Ning Mainline Kernel: Armbian EMMC official image Armbian Desktop Gnome kernel The Latest official Debian BookWorm Server Kernel Minimal The Latest official Desktop Test Images: Pre-Build Desktop 22.04 Armbian Test Image (PT-BR) Community Official Images: Armbian_community_25.2.0-trunk.410_H96-tvbox-3566_bookworm_current_6.12.11_minimal.img.xz Armbian_community_25.2.0-trunk.410_H96-tvbox-3566_noble_current_6.12.11_gnome_desktop.img.xz Bleding Edge images: Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_noble_edge_6.13.0_cinnamon_desktop.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_jammy_edge_6.13.0_cinnamon_desktop.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_bookworm_edge_6.13.0_cinnamon_desktop.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_noble_edge_6.13.0_minimal.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_bookworm_edge_6.13.0_minimal.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_jammy_edge_6.13.0_minimal.tar.xz Joshua-Riek Vendor Images: Joshua-Riek-ubuntu-22.04-preinstalled-desktop-arm64-h96max-v56 Joshua-Riek-ubuntu-22.04-preinstalled-server-arm64-h96max-v56 Joshua-Riek-ubuntu-24.04-preinstalled-desktop-arm64-h96max-v56 Joshua-Riek-ubuntu-24.04-preinstalled-server-arm64-h96max-v56 Software description: V0.5 = @armbian The Armbian SD card image "Compiled From Armbian Project" V0.8 = @hzdm Project with Mainline Bootloader "Boot the 64gb Emmc Armbian with Mainline Rockchip" V0.9 = @hzdm Release Mainline Bootloader "Boot the 32gb and 64gb Emmc Armbian with Mainline Rockchip" V1.0 = @hotnikq The Armbian SD card inside the Android Legacy Rockchip Image "Two Original Glued Images: Android boot for Linux" V1.2 = @ning Release Device Tree and Bootloader to longterm 6.6.27 Kernel "Boot with Mainline Rockchip" V1.3 = @Hqnicolas Github PR Enable h96 Rk3566 TV-Box device for Kernel 6.8 V1.4 = @pocosparc Github PR Enable OpenVFD and IR controller V1.5 = @dfahren Github PR Update U-boot 2025.01 for Kernel 6.12+ Video drivers: https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html Wifi Driver: https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view?usp=sharing UEFI: https://github.com/hqnicolas/h96v56_uefi/releases/tag/v1.2.1 Or Just Live install Wifi Driver: cd /lib/firmware/brcm/ sudo wget https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml/raw/master/firmware/brcm/fw_bcm4335b0_ag.bin sudo ln -s fw_bcm4335b0_ag.bin brcmfmac4335-sdio.h96-TVbox,rk3566.bin sudo reboot now nmcli dev wifi sudo rmmod brcmfmac_wcc brcmfmac brcmutil modprobe brcmfmac Topic description: This topic aims to demonstrate the path taken to the Armibian EMMC solution. In our path we create a lot of ready-to-use ROM files, some users burn an use this images without learning with the Linux compilation process. the name of the topic is efforts but that's no effort at all, you should try compile your own images. Device Capability Test: Using Rockchip SoCs NPU. Drivers: https://github.com/rockchip-linux/rknpu2 User Guide: https://github.com/rockchip-linux/rknpu2/blob/master/doc/Rockchip_RKNPU_User_Guide_RKNN_API_V1.4.0_EN.pdf OpenCV: https://opencv.org/blog/2022/11/29/working-with-neural-processing-units-npus-using-opencv/ A discussion on Reddit: https://www.reddit.com/r/OrangePI/comments/12b3jmj/accessing_the_npu_on_the_orange_pi/ Transformers models: https://github.com/usefulsensors/useful-transformers Usage: https://www.crowdsupply.com/useful-sensors/ai-in-a-box/ Usage: https://youtu.be/pN8mKZ5wpdQ
  13. c0rnelius
    I've seen this HDMI issue on some SM1 units, "TV Boxes". There is a REVERT floating around which resolves it, but was not accepted. https://lore.kernel.org/linux-arm-kernel/001401db8ed4$392ef030$ab8cd090$@martijnvandeventer.nl/T/ I've been currently using it on 6.12.y. I have no clue if the current STABLE kernel also has this problem. REVERT-clk-meson-g12a-Fix-kernel-warnings-when-no-display-attached.patch
  14. Igor
    - there are several revisions of Rock64 and not all work so the problem is similar to cheap TV boxes, which are assembled from random hardware parts - released images (at least Debian minimal) work on my revision, however I didn't test HDMI output Try attaching serial console to see where it stops, check if it gets up on the network ... perhaps its "just" broken HDMI.
  15. stanelie
    My switch correctly negotiates a 100mbps speed, and I also tried forcing it to 100mbps. In both cases, it links (LED on the switch is on and info from the switch says it is correctly negotiates 100mbps), and I see the TV box send a request for DHCP, and I see the answer from my DHCP server, but it stops there, I get no IP assigned in my interface. Setting a static IP on the interface also fails. I think I will start a new thread about this issue to better track this bug.
  16. stanelie
    I have the same issue with my tv box (RK3228A, the same one @Benedito Portela uses, only wireless lan works, the wired ethernet port does not work. It is present, the kernel sees the interface (end0), it detects the cable being plugged in, it even requests an IP address from DHCP, but it never takes it. I've tried to force it with a static IP, but I get no connectivity with that.
  17. k405
    Good evening, I managed to complete the installation of my R29 without any problems, but it simply isn't recognized by my gigabit router. It works on my other secondary router, but I need it on my main one. I can also connect directly through my Ethernet notebook. I saw that it could be a problem with the router not accepting 10 Mbps, but ethtool says the TV Box is working at 100 Mbps. I don't know what else to try.
  18. Lucas de Andrade
    Hello, I have a MXQ Pro 5G 4K TV Box with Allwinner H616 and the motherboard IK316-EMCP_V4.1. I am looking for a server (CLI only) version of the Armbian image for this device. The previously shared Google Drive links in this topic are no longer working. Could someone please provide a new download link (Google Drive, MEGA, etc.) for the latest server image compatible with my device? If there are any specific instructions for booting or the correct DTB file, please let me know. Thank you very much! Best regards, Luska1331 BTW: I generated this message with the help of Copilot because I don't speak English very well.
  19. stanelie
    I modified the armbianEnv.txt file : verbosity=1 extraargs=coherent_pool=2M bootlogo=false overlay_prefix=rk322x fdtfile=rk322x-box.dtb rootdev=UUID=87d2bf72-4b91-4d33-8f77-284fa91fc3a7 rootfstype=ext4 extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080@60 drm.debug=0x4 overlays= usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u This is apparently preventing the tv box from booting, I lost access. I will have to flash it again with the multitool to get back in, and this will have to wait on monday, since I was remoting into it at the office. Thanks for your help!
  20. stanelie
    Yes, The 1920x1080.bin file comes with Armbian. I use the multitool to flash https://github.com/armbian/community/releases/download/25.8.0-trunk.309/Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img.xz , this is the latesst build. On a Libre Renegade board I have (rk3328 CPU instead of rk3228 for this TV box), I have the same issue where it reverts to 1024x768, and adding the line extraargs=drm.edid_firmware=edid/1920x1080.bin to armbianEnv.txt fixes the issue, with the Armbian provided 1920x1080.bin file. To me, since it works fine under U-Boot, this hints at an Armbian bug.
  21. s-petersen
    TV Box Name MXQ MBX Model M201 CPU (example: amlogic s805 Meson 8B 4 cores 1.5 Ghz Armbian build file name:Armbian_5.67_Aml-s805_Ubuntu_bionic_default_3.10.108_desktop_20181207 DTB file used: Kernel Version:3.10.108 #14 SMP preenpt Distribution Installed (focal, buster, etc):Bionic Working Ethernet not tested Max Ethernet Speed that works (100/1000): Does wifi work Yes sort of, makes breaks connection continually, it will download updates Does bluetooth work (Yes/No):NA I don't know if the box has it Does HDMI audio work (Yes/No):Not tested Additional Comments (provide any additional information you feel is important): Headphone audio works although it is not perfect. Keyboard and mouse work fine, I have no remote to test Sound:AML8AUDIO Video playback is slow, I'm not sure if accelerated video is working Video:Mali-450 MP Booted fine, and updated fine 815 available memory
  22. Pita Bread
    I have installed Armbian community images several times on different tv boxes that have an Amlogic S905x3, and usually there was no sound ♫. I wanted to get sound out of the tv box. So, I purchased a generic USB sound card audio dongle from Aliexpress for about $2 to $3 USD. (see attached photo). The USB audio device is described in Linux as a Texas Instruments PCM2902 Audio Codec (USB PnP Sound Device device 0 USB Audio), and when you run the command lsusb you will see the id numbers 08bb:2902. However, the specific hardware chip in the device that you receive may be different. I updated the databases for repositories by running sudo apt update -y and installed necessary packages to support the USB audio device and to use a graphical desktop such as XFCE4, for example: sudo apt install -y smplayer alsa-base alsa-oss alsa-tools alsa-utils alsamixergui pulseaudio pavucontrol pavumeter You can use smplayer or vlc or another as long as it is modern media player or audio player. Now make a backup copy of these two text files /etc/modules and /etc/modprobe.d/alsa-base.conf and save the backup copies in your home directory. Without quotes, edit the text file /etc/modules and write “snd-usb-audio” at the end of the file. Also, edit the text file /etc/modprobe.d/alsa-base.conf and change a few things. Put a hash # symbol in front of every “options snd-usb-audio index=-2” that you see in the file /etc/modprobe.d/alsa-base.conf . I found two of them. Add these two lines of text to the bottom of /etc/modprobe.d/alsa-base.conf without quotes. "alias snd-card-0 snd-usb-audio" "options snd-usb-audio index=0" Make sure that your user is in the 'audio' group. Run the usermod command against a regular user (not root) that you want to use often. And reboot. sudo usermod -a G audio {username here} sudo reboot Login to the graphical desktop, open the volume control program by clicking on the panel Applications, Multimedia, PulseAudio Volume Control. Click the Configuration tab at the far right of the volume control program and change the profile to Analog Stereo. * Important – now connect a headset, earphone, or amplifier to the 3.5mm (⅛’’) 🎧 headphone receptacle on the USB audio dongle and play some sounds, music or youtube. You can use wav audio files in the directory /usr/share/sounds/alsa/ if you don't have an internet connection.
  23. Tomas Catone
    TV Box Name: Sunvell T95Z plus Octagon shaped box (I wrote it before – but Beware – apparently a lot of variants) CPU Amlogics S912 Armbian build file name: Armbian_community_25.8.0-trunk.277_Aml-s9xx-box_noble_current_6.12.34 DTB file used: meson-gxm-t95z-plus.dtb – (my other T95z uses meson-gxm-vega-s96.dtb) Kernel Version: 6.12.34 Distribution Installed (focal, buster, etc): Noble Working Ethernet (Yes/No): Yes Max Ethernet Speed that works (100/1000): Not sure how to determine... Does wifi work (Yes/No): No Does bluetooth work (Yes/No): Not tested Does HDMI audio work (Yes/No): Yes Additional Comments (provide any additional information you feel is important): This is my second T95z plus box build. Using as headless server and both seem solid. Confirming what others have said – the build is different inside. This has a different wifi card and eemc. I have a 3rd T95z plus that has the dreaded NAND chip too. Having fun and learning. Using as a simple NAS now with a ZFS pool and works just fine.
  24. Muhammad Hanis Irfan Mohd Zaid
    I've got this Android TV stick: https://shopee.com.my/RUBY-Smart-TV-24-Inch-Android-TV-Murah-TV-32-Inch-WiFi-4K-HDR-LED-Television-WiFi-Youtube-Netfli-i.1246310125.27851733843 Tried to run a progressive web app (PWA) and just learned that PWA is not supported by Android TV OS. I've found that since it's just a SBC, I can install any other OS on it and stumbled upon Armbian. Since I'm new, I would like to know what images is supported with this board and any related guides to install it. This board has 1 full HDMI port, 1 USB type A port for data, and 1 USB type C port for power only (this is just my assumption). No SD card slot. I just need it to be able to run a modern and latest browser to run the PWA. Thanks for all the help 😀
  25. Алексей Торопов
    One more tv-box, HK1 Rbox. It hase an HK2735M chip Almost all things works, but WiFi can't connect to 5G, while 2.4 work fine. It see 5G AP, but connection fail. @transpeed-8k618-t:~$ dmesg | grep brcmfmac [ 7.019181] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4335-sdio for chip BCM4335/1 [ 7.019857] usbcore: registered new interface driver brcmfmac [ 7.094608] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4335-sdio.clm_blob failed with error -2 [ 7.094631] brcmfmac mmc2:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac4335-sdio.clm_blob [ 9.242828] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 9.242856] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 9.243349] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4335/1 wl0: Mar 24 2013 20:36:01 version 6.30.171.24.20 (B0 Station/P2P) PS: Okay, that's fixed. I just changed the channel on the router, it works with channel less than 40
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept