Jump to content

Search the Community

Showing results for 'insecure mode'.

  • 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

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

  1. 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 <- 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 images from the following: 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 images (August 2021 and before): 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
  2. ­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 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: Archived images - built by Armbian servers and GPG-signed: https://imola.armbian.com/dl/rk3318-box/archive/ Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Stables provided by me (unsigned): https://users.armbian.com/jock/rk3318/ 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
  3. Hello, I have roughly 30 Orange Pi 5 here in the office setting up for deploying in the field. NVMe boot is working great after using 'nand-sata-install' to flash the MTD. But sometimes (rarely, but happens), when issuing a reboot of Armbian, after full kernel shutdown, the player does not boot back up. Power light is on, no activity blinking LED. Network link and activity blinking. Just won't boot. Requires physically disconnecting power for a few seconds then re-plug to get to boot. I have watchdog set in Armbian and tested that works. So this seems to be before Linux kernel has taken control. Is there any way to enable any logging or debug mode on the bootloader to try to get some logs or anything to help see what's happening? Thanks.
  4. Hi! So the problem is when I configure wifi hotspot using hostapd, isc-dhcp-server, and ifupdown, I'm able to start the AP, connect to it, and ping. However, the moment any device connects to the AP the serial console gets spammed with this message around once a second: protocol 0000 is buggy, dev wlan0 This happens on the unofficial Armbian build (from the Armbian OrangePi Zero3 page), DietPi, and the official OrangePi Debian build. The wireless band doesn't matter. Kernel version: 6.1.31-sun50iw9. I tried to set up the AP with NetworkManager, but couldn't manage to connect to it. Probably DHCP issues that I couldn't resolve. I haven't run the AP for a prolonged period, only like 1hour. So I'm not sure if this has any effect on the performance and stability. Could somebody suggest if this is something to worry about or just a harmless warning?
  5. I have IQAir AirVision pro and i'm try to reverse engineer it it uses uboot sunxi (allwinner) was following this video according to video i need to know where flash chip is mapped in to memory then use md print whole firmware then used https://github.com/nmatt0/firmwaretools/blob/master/parse-uboot-dump.py to convert to firmware as he used bdinfo to get address (which is not present), what i do? Is there any way through which i can extract frimware from device? (like using FEL Mode) also found https://github.com/zador-blood-stained/h3-fel-mass-storage is it possible do same on Allwinner A33 logs https://xdaforums.com/attachments/boot-txt.6083991/ https://xdaforums.com/attachments/depthcharge-print_all-txt.6084119/ https://xdaforums.com/attachments/uboot_sunxi_printenv-txt.6083992/ https://xdaforums.com/attachments/uboot_more-info-txt.6084356/
  6. Maybe we can bundle our effords regarding a working S805 image? I also have hundreds of new TV sticks (not boxes) with an Amlogic S805 (Meson 8B). The original Android ROM has the codename stvm8b. Currently I only have a working Android 4.2.2 image with a patched kernel for real 1080p output which can be flashed using TWRP onto the internal eMMC. I really would love to get some kind of more recent and non-Android image up and running. It's a real struggle to get any custom images as most links are dead already which makes it more complicated. Currently I have full UART access to the device and I'm able to interact with the uBoot shell. I also see the full kernel output of the working Android image and have a root shell there. But as others already pointed out kernel 3.10 is way to old to be used in production. So "porting" a more recent kernel would be great. My main goal is to get a Linux image up and running on the box which makes it still useful as device for digital signage or as a small webserver. Some more details on the hardware: ro.product.name=stvm8b ro.product.device=stvm8b ro.product.board=stvm8b ro.product.cpu.abi=armeabi-v7a ro.board.platform=meson8 uBoot output dropping to shell: QA5:A;SVN:B72;POC:1FF;STS:0;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0; no sdio debug board detected TE : 76654 BT : 15:34:06 May 13 2015 ##### VDDEE voltage = 0x044c CPU clock is 792MHz DDR mode: 32 bit mode DDR size: 1GB (auto) DDR check: Pass! DDR clock: 636MHz with 2T mode DDR pll bypass: Disabled DDR init use : 14831 us HHH Boot From SDIO C SD_boot_type: 00000002 card_type: 00000003 0x0000009f ucl decompress...pass 0x12345678 Boot from internal device 1st eMMC on SDIO C TE : 301370 System Started U-Boot Version: 2011.03-ad3b84b(20150513.153356) clr h-ram DRAM: 1 GiB relocation Offset is: 2feb4000 show partition table: part: 0, name : logo, size : 2000000 part: 1, name : recovery, size : 2000000 part: 2, name : misc, size : 2000000 part: 3, name : boot, size : 2000000 part: 4, name : system, size : 40000000 part: 5, name : cache, size : 20000000 part: 6, name : backup, size : 20000000 part: 7, name : data, size : end aml_card_type=0x0 MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6 [mmc_register] add mmc dev_num=1, port=2, if_type=6 SDIO Port B: 0, SDIO Port C: 1 power init out reg=c110804c,value=dfffffff IR init done! register usb cfg[0][1] = 3ff6c19c register usb cfg[0][2] = 3ff6c184 NAND: EMMC BOOT: not init nand do not init nand : cause boot_device_flag without nand get_boot_device_flag: init_ret -1 get_boot_device_flag EMMC BOOT: Emmckey: Access range is illegal! [mmc_init] SDIO Port C:1, if_type=7, initialized OK! [mmc_get_partition_table] skip cache partition. Partition table get from SPL is : name offset size flag =================================================================================== 0: bootloader 0 400000 0 1: reserved 2400000 4000000 0 2: cache 6c00000 20000000 2 3: env 27400000 800000 0 4: logo 28400000 2000000 1 5: recovery 2ac00000 2000000 1 6: misc 2d400000 2000000 1 7: boot 2fc00000 2000000 1 8: system 32400000 40000000 1 9: backup 72c00000 20000000 1 10: data 93400000 13ec00000 4 mmc read lba=0x12000, blocks=0x1 mmc read lba=0x12001, blocks=0x1 mmc_read_partition_tbl: mmc read partition OK! eMMC/TSD partition table have been checked OK! i=0,register --- emmc_key MMC BOOT, emmc_env_relocate_spec : env_relocate_spec 59 set_storage_device_flag: store 2 bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Multi dtb tool version: v2 . Multi dtb detected, support 5 dtbs. aml_dt soc: stvm8b platform: dongle variant: 1g dtb 0 soc: stvm8b plat: dongle vari: 1g dtb 1 soc: stvm8b plat: dongle vari: 512m dtb 2 soc: stvm8b plat: normal vari: 1g dtb 3 soc: stvm8b plat: normal vari: 1gcm dtb 4 soc: stvm8b plat: normal vari: 512mcm Find match dtb: 0 vpu clk_level in dts: 3 set vpu clk: 182150000Hz, readback: 182150000Hz(0x701) Net: Meson_Ethernet init suspend firmware done. (ret:0) cvbs trimming.1.v5: 0xa0, 0x0 preboot new... check board version... bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Hardware version information has been written and the check is successful hdmi tx power init mode = 8 vic = 16 set HDMI vic: 16 mode is: 8 viu chan = 1 config HPLL config HPLL done reconfig packet setting done Hit Enter key to stop autoboot -- : 1 tstc enter exit abortboot: 1 The original name was "MyGica ATV185" and each device has a Quad-Core processor (Cortex A5, 1 GHz), 1 GB RAM, 8 GB internal eMMC storage, a WIFI module, 1x USB2.0, 1x microSD slot, 1x HDMI plug and 1x microUSB as power supply. The device should be the same like the ODroid C1 Would love to participate in the process of creating a useful image for the S805 platform and especially for this piece of hardware.
  7. Just to demonstrate what such a concern would mean for the distribution of my choice: The only thing in OS space that is really device-specific is the devicetree, which describes how the device is wired. For the linux kernel, it is only relevant that the corresponding drivers for the components listed in the devicetree are also built using the necessary options. Since the drivers for the rk3568 SoC are the same as for the rk3566 SoC (they are wired differently only through the devicetree), there is no need for any special action in this case. So all I'm missing is a mainline binding compliant devicetree, and I'm done. Now all that's missing is a firmware that can start the OS of choice. And this contains device-specific code that can't be copied from another device, and must be built specifically for this device. Fortunately, everything necessary has already been posted on the U-Boot mailing list. The devicetree used still has shortcomings, but it is a start. In order to verify the handling of different binary bloobs with my build system, I already build the firmware regularly. It's also included in my provided firmware uploads, but I haven't communicated it as I don't own an ODROID-M1S and therefore can't verify its functionality. For me, the conlusion means: - Install the firmware dd bs=512 seek=64 conv=notrunc,fsync if=odroid-m1s-rk3566/u-boot-rockchip.bin of=/dev/${entire-device-to-be-used} - run the ODROID-M1S in UMS mode and tranfer my current image to a NVME - Since there is no proper mainline devietree, I would use the one that falls off during the firmware build and copy it in cp /somewhere/rk3566-odroid-m1s.dtb /usr/lib/modules/linux/dtb/rockchip/rk3566-odroid-m1s.dtb And I'm ready to rumble. The same should be able to work with an Armbian ODROID-M1 image.
  8. armbian-install is meant to be used inside the running Armbian system from microSD card. It copies itself to NVMe or eMMC or whatever options are available and can be utilized. This tool does not work "offline". Anyway. I never did something like that by myself but maybe you find some hints when you google for keywords like "h616 fel sunxi-fel emmc". fel mode seems something like Rockchips maskrom to utilized the rkdevtool. Maybe Allwinner has something similar
  9. Hello, I am a new user and have downloaded Armbian on LePotato AML-S905X-CC. I am looking for a way to get Firefox to start up in kiosk mode with a specified website, but can't seem to do it. Does anyone know how I can get Firefox to start up in kiosk mode with a specified website?
  10. This PR enables kernel modules for various USB Gadget applications for rockchip 32 bit platforms (rk322x, rk3288) for both current 6.6 and edge 6.7 kernels. Also provides a bunch of patches to address issues with rk322x, whose peripheral mode does not really well with dwc2 driver yet. A couple of patches are self-produced after trial-and-error sessions, another pair are imported from rockchip 5.10 kernel and substitutes an older patch with a bit more refined code (see the "debounce" patch). edit: the patches addressing the rk322x issues probably are worth also for rk3318 and rk3328, since the controller is the very same with similar issues. During my tests, I quickly checked an rk3318 device and found it has the same behaviour (disconnection, system freeze, ...). I will do further tests and, in case, import the same patches for rockchip64 too. Jira reference number AR-2096 How Has This Been Tested? [x] Installed on live rk322x system, tested mass storage :heavy_check_mark:, ethernet :heavy_check_mark:, uac1/2 :negative_squared_cross_mark: [x] Installed on live rk3288 system in OTG mode, tested mass storage :heavy_check_mark:, uac1/2 :heavy_check_mark: For sake of curiosity, iperf3 run on rk322x in ethernet gadget mode: Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  11. @kalekulan I had the same. When I upgraded emmc can't boot anymore. It doesn't get detected when plugged to usb by itself. SD card still works tho you can try to force boot it. Put the jumper on the mask rom mode, and place a bootable sdcard, then plugged it to USB. It might help if you can monitor the serial port. The sdcard will boot but it will detect the eMMC mode and the eMMC will be detected by the pc. Then you can do the usual dd'ing. EDIT: with the eMMC booting now, it still don't get detected by the pc when you plug it in, but atleast it boot now. And somehow it just shutdown on me just now, over temperature. only got mariadb and freeradius running on it. My tiny rpi copper heatsink is most likely no enough.
  12. Well, I downloade and built a new armbian on my OPI 5. I selected the "vendor kernel" and I changed the dwc3 dual role to host only. The kernel that was built was 6.1.43, and I could finally see the missing USB port. I am right now rebuilding the "edge kernel" with the same host only mode, and will check and report back. So, a fall in the forward direction....... Gullik
  13. Hello, I apologize for my bad English. I have a NanoPi R6S and a NanoPC T6. Both Nano devices have Armbian images. Both devices use a processor: CPU Model: Rockchip RK3588 Number of Cores: Quad-core ARM Cortex-A76 + Quad Core Cortex-A55 Frequency: Cortex-A76 (up to 2.4GHz), Cortex-A55 (up to 1.8GHz) A few things struck me On NanoPi R6S in the dts file, the frequency of A76 cores is up to 2.4GHz you can see the frequencies at which each core works cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2352000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2352000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2256000 408000 600000 816000 1008000 1200000 1416000 1608000 1800000 2016000 2208000 2256000 governors: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil conservative ondemand userspace powersave performance schedutil On NanoPi T6 in the dts file, the frequency of A76 cores is up to 2.2GHz - I fixed it /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies - this is missing. /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_governors - this is missing, having instead cat /sys/devices/system/cpu/cpuidle/available_governors ladder menu teo NanoPi R6S is currently running kernel 5.10.110-rockchip-rk3588 NanoPC T6 is currently running kernel 6.8.0-rc6-edge-rockchip-rk3588 I also noticed differences in CPU cache. NanoPI R6S Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 3 Vendor ID: ARM Model: 0 Model name: Cortex-A55 Stepping: r2p0 CPU max MHz: 2352.0000 CPU min MHz: 408.0000 BogoMIPS: 48.00 L1d cache: 256 KiB L1i cache: 256 KiB L2 cache: 1 MiB L3 cache: 3 MiB Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1: Mitigation; __user pointer sanitization Vulnerability Spectre v2: Vulnerable: Unprivileged eBPF enabled Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp NanoPC T6 Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: ARM Model name: Cortex-A55 Model: 0 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping: r2p0 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp Model name: Cortex-A76 Model: 0 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping: r4p0 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp Caches (sum of all): L1d: 384 KiB (8 instances) L1i: 384 KiB (8 instances) L2: 2.5 MiB (8 instances) L3: 3 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-7 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1: Mitigation; __user pointer sanitization Spectre v2: Vulnerable: Unprivileged eBPF enabled Srbds: Not affected Tsx async abort: Not affected When using the command: cpufreq-info NanoPI R6S cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:76.72%, 600 MHz:6.69%, 816 MHz:0.31%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:16.29% (11087717) analyzing CPU 4: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.35 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.35 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.35 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.33%, 600 MHz:1.13%, 816 MHz:0.40%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.35 GHz:13.14% (2586948) analyzing CPU 5: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.35 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.35 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.35 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.33%, 600 MHz:1.13%, 816 MHz:0.40%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.35 GHz:13.14% (2586948) analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:92.30%, 600 MHz:0.44%, 816 MHz:0.16%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.26 GHz:7.10% (1012245) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:92.30%, 600 MHz:0.44%, 816 MHz:0.16%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:0.00%, 2.21 GHz:0.00%, 2.26 GHz:7.10% (1012245) NanoPC T6 cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 4: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 5: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 6: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 7: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. The CPU driver appears to be missing. When using the command: cpu-info NanoPI R6S cpu-info Packages: 0: Unknown Microarchitectures: 4x Cortex-A76 4x Cortex-A55 Cores: 0: 1 processor (0), ARM Cortex-A76 1: 1 processor (1), ARM Cortex-A76 2: 1 processor (2), ARM Cortex-A76 3: 1 processor (3), ARM Cortex-A76 4: 1 processor (4), ARM Cortex-A55 5: 1 processor (5), ARM Cortex-A55 6: 1 processor (6), ARM Cortex-A55 7: 1 processor (7), ARM Cortex-A55 NanoPC T6 cpu-info Packages: 0: Unknown Microarchitectures: 8x Cortex-A55 Cores: 0: 1 processor (0), ARM Cortex-A55 1: 1 processor (1), ARM Cortex-A55 2: 1 processor (2), ARM Cortex-A55 3: 1 processor (3), ARM Cortex-A55 4: 1 processor (4), ARM Cortex-A55 5: 1 processor (5), ARM Cortex-A55 6: 1 processor (6), ARM Cortex-A55 7: 1 processor (7), ARM Cortex-A55 My question is the following. Are the differences because of the dts file or because of the kernel. Anyone else using a NanoPC T6 and would like to help fix this? At the moment, I'm not using NanoPC T6 as a server yet, and I have the opportunity to experiment. It will be used as a small server for graphics, tftp and others. Is there any additional information needed. Regards,
  14. Hello everyone, My university recently purchased a few hundred of these RK3288-based tablets. They're used to display room schedules, control printer confiurations, and control TV inputs throughout our engineering and computer science buildings. The buildings are littered with them; you can't walk 10 feet in any direction without passing one mounted on the wall. Given that they have cameras and microphones, and they run an ancient Android, maybe this wasn't a great idea... Anyway, the no-name eMMC on these things tends to go bad pretty quickly, and the board has no microSD slot, so SD booting is not an option. The university has given me access to a few dozen broken tablets to see if I can get them booting from USB. RK3288 doesn't support USB booting, so my plan is to place a U-Boot on the eMMC that is capable of loading Linux and an Armbian rootfs from USB storage, and mark the eMMC as read-only within Linux. This way, the flash shouldn't wear out any further, and the tablets can remain usable. You can get the tablets into mask ROM mode by grounding the resistors next to the eMMC. From here, flashing the eMMC is straightforward with rkdeveloptool. Upstream U-Boot images compiled with the rk3288-firefly and rk3288-vyasa defconfigs will boot on the device! (To build an image that can be flashed to the base of the eMMC, follow the instructions in U-Boot's README.rockchip under the section titled "Booting from an SD card on RK3288 with TPL," but dd into a file instead of a block device, then flash the file.) Here's what the boot output looks like with the firefly defconfig: U-Boot TPL 2024.04-rc4-00026-g6ec096a711 (Mar 19 2024 - 14:15:48) Returning to boot ROM... U-Boot SPL 2024.04-rc4-00026-g6ec096a711 (Mar 19 2024 - 14:15:48 -0400) U-Boot 2024.04-rc4-00026-g6ec096a711 (Mar 19 2024 - 14:15:48 -0400) SoC: Rockchip rk3288 Reset cause: RST Model: Firefly-RK3288 DRAM: 2 GiB Core: 226 devices, 26 uclasses, devicetree: separate MMC: mmc@ff0c0000: 1, mmc@ff0f0000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Model: Firefly-RK3288 Net: Warning: ethernet@ff290000 (eth0) using random MAC address - 8a:21:c0:47:39:e5 eth0: ethernet@ff290000 starting USB... Bus usb@ff540000: USB DWC2 Bus usb@ff580000: USB DWC2 scanning bus usb@ff540000 for devices... 2 USB Device(s) found scanning bus usb@ff580000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 ethernet@ff290000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff290000 ethernet@ff290000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff290000 => Here's the boot output when booting the vyasa defconfig: U-Boot TPL 2024.04-rc4-00026-g6ec096a711 (Mar 19 2024 - 14:16:13) Returning to boot ROM... U-Boot SPL 2024.04-rc4-00026-g6ec096a711 (Mar 19 2024 - 14:16:13 -0400) Expected image is not found. Trying to start U-Boot U-Boot 2024.04-rc4-00026-g6ec096a711 (Mar 19 2024 - 14:16:13 -0400) SoC: Rockchip rk3288 Reset cause: unknown reset Model: Amarula Vyasa-RK3288 DRAM: 2 GiB Core: 210 devices, 22 uclasses, devicetree: separate MMC: mmc@ff0c0000: 1, mmc@ff0f0000: 0 Loading Environment from MMC... Card did not respond to voltage select! : -110 *** Warning - No block device, using default environment In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Model: Amarula Vyasa-RK3288 Net: Error: ethernet@ff290000 No valid MAC address found. No ethernet found. starting USB... Bus usb@ff540000: USB DWC2 Bus usb@ff580000: USB DWC2 scanning bus usb@ff540000 for devices... 2 USB Device(s) found scanning bus usb@ff580000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 No ethernet found. No ethernet found. => This is promising and exciting, but USB host functionality doesn't work in either of these two builds You can see in the boot output that it scans for USB devices, but doesn't see any storage devices, even though I had a USB flash drive plugged into the board during both of those boot attempts. I have also tried using a micro-USB to USB-A OTG adapter and plugging the flash drive in there, but that doesn't work either. I think it's safe to assume that this USB issue is something to do with either the defconfigs or the device trees for the firefly and vyasa. I would love to hear if anyone has any input on how I can get USB working within U-Boot. I have extracted the device tree from the Android bootimg that came with the tablet, and have attached it (decompiled), in case that's helpful. Thanks, Ben rk3288-noname.dts
  15. Hi. I testing out different images for my DIY NAS project. My plan is to use the Orangepi3b board with armbian bookworm and OMV. I have built images from armbian github, (main,trunk) the edge 6.7.10 kernel is working great. But I do get some Iperf3 retries when sending from Opi3b. From Opi3b 60-70MB/s To Opi3b 110MB/s. With Orangepi own bookworm image I have 110/110 and no retries. The same with Joshua Riek's Ubuntu server image, no retries and 110/110. Orangepi3b armbian with 6.7.10 kernel orangepi@orangepi3b:~$ iperf3 -c 192.168.10.197 -f M Connecting to host 192.168.10.197, port 5201 [ 5] local 192.168.10.155 port 56514 connected to 192.168.10.197 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 74.5 MBytes 74.5 MBytes/sec 217 19.8 KBytes [ 5] 1.00-2.00 sec 75.9 MBytes 75.9 MBytes/sec 218 11.3 KBytes [ 5] 2.00-3.00 sec 79.1 MBytes 79.1 MBytes/sec 200 25.5 KBytes [ 5] 3.00-4.00 sec 73.3 MBytes 73.3 MBytes/sec 225 29.7 KBytes [ 5] 4.00-5.00 sec 79.1 MBytes 79.1 MBytes/sec 210 33.9 KBytes [ 5] 5.00-6.00 sec 77.8 MBytes 77.8 MBytes/sec 211 86.3 KBytes [ 5] 6.00-7.00 sec 77.4 MBytes 77.4 MBytes/sec 202 36.8 KBytes [ 5] 7.00-8.00 sec 76.1 MBytes 76.1 MBytes/sec 207 73.5 KBytes [ 5] 8.00-9.00 sec 75.0 MBytes 75.0 MBytes/sec 222 12.7 KBytes [ 5] 9.00-10.00 sec 73.3 MBytes 73.3 MBytes/sec 239 11.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 761 MBytes 76.1 MBytes/sec 2151 sender [ 5] 0.00-10.04 sec 760 MBytes 75.7 MBytes/sec receiver Orangepi3b Ubuntu with 6.1 kernel ubuntu@ubuntu:~$ iperf3 -R -c 192.168.10.197 -f M Connecting to host 192.168.10.197, port 5201 Reverse mode, remote host 192.168.10.197 is sending [ 5] local 192.168.10.154 port 42888 connected to 192.168.10.197 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 112 MBytes 112 MBytes/sec [ 5] 1.00-2.00 sec 112 MBytes 112 MBytes/sec [ 5] 2.00-3.00 sec 112 MBytes 112 MBytes/sec [ 5] 3.00-4.00 sec 112 MBytes 112 MBytes/sec [ 5] 4.00-5.00 sec 112 MBytes 112 MBytes/sec [ 5] 5.00-6.00 sec 112 MBytes 112 MBytes/sec [ 5] 6.00-7.00 sec 112 MBytes 112 MBytes/sec [ 5] 7.00-8.00 sec 112 MBytes 112 MBytes/sec [ 5] 8.00-9.00 sec 112 MBytes 112 MBytes/sec [ 5] 9.00-10.00 sec 112 MBytes 112 MBytes/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.04 sec 1.10 GBytes 112 MBytes/sec 1 sender [ 5] 0.00-10.00 sec 1.10 GBytes 112 MBytes/sec receiver So to see if the vendor kernel was different I built with the new 6.1.43-vendor-rk35xx kernel, but It will not boot. build command: ./compile.sh build BOARD=orangepi3b BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=bookworm J=4 It seems to be something with power to the NPU. ? "rockchip-pm-domain fdd90000.power-management:power-controller: failed to get ack on domain 'npu', target_idle = 0, target_ack = 0, val=0x6" uart log attachment kernelpanic.log
  16. mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot those patches are a mess, hopefully I'll find time to squash soon mekotronics 3588: squash u-boot patches same as before but not touching the same file twice+ View the full article
  17. I've been using Armbian for developing an image for running on some custom hardware based on an Allwinner S3 (SoC with a single arm v7 core and 128mb ram) and it has been really helpful. My system now runs the software it was built for, and i love having complete Debian for development, maintenance and debugging. However I would like to have the option of making the system more like an embedded system most of the time : for most of its life it's running a custom application that gets video from a camera, h264 encodes it and sends it and some other data out over a data link. When it's in this mode it would be great if it was more like a buildroot type system, ideally with a nice short boot time. However some of the time i want to keep the possibility of a user booting into full Linux as I'm running now. How would you go about this? at the moment I'm looking at creating a custom systemd target with as little as possible for embedded. Does that make sense?
  18. I have done a firmware update on my Compulab Utilite Pro using u-boot compiled from source. However something went wrong, leaving me with a bricked board. In the manual it is mentioned, that the iMX6 has 2 boot-modes. The recovery-mode can be configured by switching some pin to a high-level. On the PCB I can not find any jumper, that allows me to do so. Question: Does anybody know how to switch the Compulab Utilite Pro to the recovery-mode? Thanks in advance
  19. Hi guys, so actually I am the one who knows quite a lot about X96Q :p : 1. As Khadas said: there are counterfeits based on rk 3228A with a S905W (in fact "S" is not an actual "S") mark on the chip. It's performance is really poor, its 32bit CPU and its not worth working with 2. Market is full of other-kind-of-fake fake boxes - 1g RAM 8g ROM versions are being sold under 2g 16g tag, with very little tools for an average user to prove it's not an actual 2g16g version. 3. There are many different revisions of X96Q boards, with different types of RAM, differenct clock settings and its really hard to just get the image of an OS. Up to my knowledge, there is no other working OS than the one made by github user named warpme. Its an Arch Linux distro and its quite decent. It has some drawback though, and I am in constant touch with an author, working on some commercial solution that utilizes these boxes. In the version available on github, there is no LAN support, eMMC installation and an AP mode. Besides that, it works just fine Here You may try to find a release suitable for You: https://github.com/warpme/miniarch Please note, that
  20. When I run the Linux kernel on the Odroid XU4 board, it enters a loop with this error during boot: U-Boot 2017.05-00008-g6a9ddb8303-dirty (May 19 2020 - 19:48:01 +0900) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 29.7 GiB mmc_init: -5, time 4 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 reading /boot.ini 2401 bytes read in 4 ms (585.9 KiB/s) ## Executing script at 43e00000 reading config.ini 6911 bytes read in 5 ms (1.3 MiB/s) ini: Imported macaddr as 00:1e:06:61:7a:39 ini: Imported vout as hdmi ini: Imported HPD as true ini: Imported cecenable as false ini: Imported disable_vu7 as false ini: Imported ddr_freq as 825 ini: Imported overlay_resize as 16384 ini: Imported overlay_profile as ini: Imported overlays as spi0 i2c0 i2c1 uart0 No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! reading zImage 7299952 bytes read in 490 ms (14.2 MiB/s) reading exynos5422-odroidxu4.dtb 88559 bytes read in 11 ms (7.7 MiB/s) reading overlays/spi0.dtbo 691 bytes read in 5 ms (134.8 KiB/s) reading overlays/i2c0.dtbo 224 bytes read in 5 ms (43 KiB/s) reading overlays/i2c1.dtbo 226 bytes read in 5 ms (43.9 KiB/s) reading overlays/uart0.dtbo 227 bytes read in 6 ms (36.1 KiB/s) Kernel image @ 0x40008000 [ 0x000000 - 0x6f6370 ] ## Flattened Device Tree blob at 44000000 Booting using the fdt blob at 0x44000000 reserving fdt memory region: addr=44000000 size=2c000 Using Device Tree in place at 44000000, end 4402efff Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 6.1.77+ (odroid@odroid) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP PREEMPT Wed Mar 6 17:56:35 -03 2024 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=30c5387d [ 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: Hardkernel ODROID XU4 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 128 MiB at 0x00000000b6800000 [ 0.000000] Samsung CPU ID: 0xe5422001 [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000040000000-0x000000006fffffff] [ 0.000000] HighMem [mem 0x0000000070000000-0x00000000be9fffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x00000000be9fffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000be9fffff] [ 0.000000] Running under secure firmware. [ 0.000000] percpu: Embedded 17 pages/cpu s39124 r8192 d22316 u69632 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 516928 [ 0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0 HPD=true vout=hdmi e [ 0.000000] hdmi: using HDMI mode [ 0.000000] Unknown kernel command line parameters "false HPD=true vout=hdmi", 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] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 1903668K/2074624K available (12288K kernel code, 1139K rwdata, 2940K rodata, 2048K init, 363K bss, 39884K reserved, 131072K cma-reserved, 1157120K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] Switching to timer-based delay loop, resolution 41ns [ 0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000002] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [ 0.000032] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 57 [ 0.001509] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.001535] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.001555] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001572] Ignoring duplicate/late registration of read_current_timer delay [ 0.002351] Console: colour dummy device 80x30 [ 0.003109] printk: console [tty1] enabled [ 0.003176] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000) [ 0.003223] CPU: Testing write buffer coherency: ok [ 0.003313] pid_max: default: 32768 minimum: 301 [ 0.003464] LSM: Security Framework initializing [ 0.003658] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.003711] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.005467] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100 [ 0.006882] cblist_init_generic: Setting adjustable number of callback queues. [ 0.006928] cblist_init_generic: Setting shift to 3 and lim to 1. [ 0.007116] cblist_init_generic: Setting adjustable number of callback queues. [ 0.007151] cblist_init_generic: Setting shift to 3 and lim to 1. [ 0.007359] Setting up static identity map for 0x40200000 - 0x40200060 [ 0.007711] ARM CCI driver probed [ 0.008305] Exynos MCPM support installed [ 0.008707] rcu: Hierarchical SRCU implementation. [ 0.008734] rcu: Max phase no-delay instances is 1000. [ 0.010012] smp: Bringing up secondary CPUs ... [ 0.011171] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101 [ 0.012478] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102 [ 0.013707] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103 [ 0.014902] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.014919] CPU4: detected I-Cache line size mismatch, workaround enabled [ 0.014927] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.015018] CPU4: Spectre BHB: enabling loop workaround for all CPUs [ 0.016286] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.016300] CPU5: detected I-Cache line size mismatch, workaround enabled [ 0.016307] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.017624] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.017638] CPU6: detected I-Cache line size mismatch, workaround enabled [ 0.017645] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.018922] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.018937] CPU7: detected I-Cache line size mismatch, workaround enabled [ 0.018945] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable [ 0.019180] smp: Brought up 1 node, 8 CPUs [ 0.019244] SMP: Total of 8 processors activated (384.00 BogoMIPS). [ 0.019276] CPU: All CPU(s) started in HYP mode. [ 0.019297] CPU: Virtualization extensions available. [ 0.020752] devtmpfs: initialized [ 0.042523] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 0.042807] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.042850] futex hash table entries: 2048 (order: 5, 131072 bytes, linear) [ 0.045974] pinctrl core: initialized pinctrl subsystem [ 0.048866] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.052562] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 0.054296] audit: initializing netlink subsys (disabled) [ 0.054571] audit: type=2000 audit(0.050:1): state=initialized audit_enabled=0 res=1 [ 0.055157] thermal_sys: Registered thermal governor 'step_wise' [ 0.055436] cpuidle: using governor menu [ 0.055910] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.055941] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.185987] EXYNOS5420 PMU initialized [ 0.292725] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible. [ 0.294707] fbcon: Taking over console [ 0.296476] iommu: Default domain type: Translated [ 0.296501] iommu: DMA domain TLB invalidation policy: lazy mode [ 0.296909] usbcore: registered new interface driver usbfs [ 0.296979] usbcore: registered new interface driver hub [ 0.297050] usbcore: registered new device driver usb [ 0.297807] s3c-i2c 12c70000.i2c: slave address 0x00 [ 0.297837] s3c-i2c 12c70000.i2c: bus frequency set to 378 KHz [ 0.298170] s3c-i2c 12c70000.i2c: i2c-0: S3C I2C adapter [ 0.298383] s3c-i2c 12c80000.i2c: slave address 0x00 [ 0.298412] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz [ 0.298719] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter [ 0.299209] mc: Linux media interface: v0.10 [ 0.299295] videodev: Linux video capture interface: v2.00 [ 0.299921] Advanced Linux Sound Architecture Driver Initialized. [ 0.301010] clocksource: Switched to clocksource mct-frc [ 0.301481] VFS: Disk quotas dquot_6.6.0 [ 0.301559] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.315803] NET: Registered PF_INET protocol family [ 0.316073] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.317886] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 0.317937] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.318036] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.318132] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 0.318434] TCP: Hash tables configured (established 8192 bind 8192) [ 0.318557] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.318617] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.318871] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.318931] NET: Registered PF_XDP protocol family [ 0.320817] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available [ 0.322010] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available [ 0.324097] Initialise system trusted keyrings [ 0.324437] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 0.333908] romfs: ROMFS MTD (C) 2007 Red Hat, Inc. [ 0.421548] NET: Registered PF_ALG protocol family [ 0.421584] Key type asymmetric registered [ 0.421605] Asymmetric key parser 'x509' registered [ 0.421839] bounce: pool size: 64 pages [ 0.421992] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 0.422397] io scheduler mq-deadline registered [ 0.422425] io scheduler kyber registered [ 0.422681] io scheduler bfq registered [ 0.424520] samsung-pinctrl 13400000.pinctrl: Failed to create device link (0x180) with soc [ 0.426837] samsung-usb2-phy 12130000.phy: supply vbus not found, using dummy regulator [ 0.427839] exynos5_usb3drd_phy 12100000.phy: supply vbus not found, using dummy regulator [ 0.428032] exynos5_usb3drd_phy 12100000.phy: supply vbus-boost not found, using dummy regulator [ 0.428460] exynos5_usb3drd_phy 12500000.phy: supply vbus not found, using dummy regulator [ 0.428634] exynos5_usb3drd_phy 12500000.phy: supply vbus-boost not found, using dummy regulator [ 0.436864] dma-pl330 3880000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.436898] dma-pl330 3880000.dma-controller: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 0.439976] dma-pl330 121a0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.440008] dma-pl330 121a0000.dma-controller: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.443083] dma-pl330 121b0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.443116] dma-pl330 121b0000.dma-controller: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.444270] dma-pl330 10800000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.444300] dma-pl330 10800000.dma-controller: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32 [ 0.461998] dma-pl330 3880000.dma-controller: PM domain MAU will not be powered off [ 0.533568] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.536218] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 124, base_baud = 0) is a S3C6400/10 [ 0.536771] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 125, base_baud = 0) is a S3C6400/10 [ 1.553526] printk: console [ttySAC2] enabled [ 1.560131] exynos-trng 10830600.rng: Exynos True Random Number Generator. [ 1.567245] exynos-mixer 14450000.mixer: Adding to iommu group 0 [ 1.574772] exynos-drm-g2d 10850000.g2d: Adding to iommu group 1 [ 1.581147] exynos-rotator 11c00000.rotator: Adding to iommu group 2 [ 1.587248] exynos-scaler 12800000.scaler: Adding to iommu group 3 [ 1.593888] exynos-scaler 12810000.scaler: Adding to iommu group 4 [ 1.600295] exynos-scaler 12820000.scaler: Adding to iommu group 5 [ 1.607009] exynos-drm-gsc 13e00000.video-scaler: Adding to iommu group 6 [ 1.613211] exynos-drm-gsc 13e00000.video-scaler: drm gsc registered successfully. [ 1.620298] exynos-drm-gsc 13e10000.video-scaler: Adding to iommu group 7 [ 1.627466] exynos-drm-gsc 13e10000.video-scaler: drm gsc registered successfully. [ 1.652020] brd: module loaded [ 1.654773] usbcore: registered new device driver r8152-cfgselector [ 1.659902] usbcore: registered new interface driver r8152 [ 1.665405] usbcore: registered new interface driver cdc_ether [ 1.671186] usbcore: registered new interface driver cdc_subset [ 1.677065] usbcore: registered new interface driver r8153_ecm [ 1.685749] phy phy-12130000.phy.6: phy_power_on was called before phy_init [ 1.691276] exynos-ehci 12110000.usb: EHCI Host Controller [ 1.696714] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1 [ 1.704845] exynos-ehci 12110000.usb: irq 133, io mem 0x12110000 [ 1.731064] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00 [ 1.735818] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 1.743876] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.751068] usb usb1: Product: EHCI Host Controller [ 1.755880] usb usb1: Manufacturer: Linux 6.1.77+ ehci_hcd [ 1.761370] usb usb1: SerialNumber: 12110000.usb [ 1.766665] hub 1-0:1.0: USB hub found [ 1.769693] hub 1-0:1.0: 3 ports detected [ 1.774988] phy phy-12130000.phy.6: phy_power_on was called before phy_init [ 1.780583] exynos-ohci 12120000.usb: USB Host Controller [ 1.786000] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2 [ 1.793806] exynos-ohci 12120000.usb: irq 133, io mem 0x12120000 [ 1.865293] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01 [ 1.872132] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.879280] usb usb2: Product: USB Host Controller [ 1.884074] usb usb2: Manufacturer: Linux 6.1.77+ ohci_hcd [ 1.889502] usb usb2: SerialNumber: 12120000.usb [ 1.894774] hub 2-0:1.0: USB hub found [ 1.897855] hub 2-0:1.0: 3 ports detected [ 1.904077] UDC core: dbgp: couldn't find an available UDC [ 1.908531] mousedev: PS/2 mouse device common for all mice [ 1.915382] i2c_dev: i2c /dev entries driver [ 1.943247] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV [ 1.960292] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV [ 1.979785] vdd_sd: Bringing 3300000uV into 2800000-2800000uV [ 2.049199] s5m-rtc s2mps14-rtc: registered as rtc0 [ 2.054487] s5m-rtc s2mps14-rtc: setting system clock to 2000-01-01T00:00:08 UTC (946684808) [ 2.061844] s2mps11-clk s2mps11-clk: DMA mask not set [ 2.076557] exynos-tmu 10060000.tmu: More trip points than supported by this TMU. [ 2.082622] exynos-tmu 10060000.tmu: 2 trip points should be configured in polling mode. [ 2.092426] exynos-tmu 10064000.tmu: More trip points than supported by this TMU. [ 2.098440] exynos-tmu 10064000.tmu: 2 trip points should be configured in polling mode. [ 2.108348] exynos-tmu 10068000.tmu: More trip points than supported by this TMU. [ 2.114407] exynos-tmu 10068000.tmu: 2 trip points should be configured in polling mode. [ 2.124320] exynos-tmu 1006c000.tmu: More trip points than supported by this TMU. [ 2.130338] exynos-tmu 1006c000.tmu: 2 trip points should be configured in polling mode. [ 2.140250] exynos-tmu 100a0000.tmu: More trip points than supported by this TMU. [ 2.146302] exynos-tmu 100a0000.tmu: 6 trip points should be configured in polling mode. [ 2.155544] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled [ 2.163331] device-mapper: uevent: version 1.0.3 [ 2.167537] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com [ 2.191451] sdhci: Secure Digital Host Controller Interface driver [ 2.196199] sdhci: Copyright(c) Pierre Ossman [ 2.201064] Synopsys Designware Multimedia Card Interface Driver [ 2.208067] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode. [ 2.208115] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode. [ 2.220477] dwmmc_exynos 12220000.mmc: Using internal DMA controller. [ 2.224492] s5p-secss 10830000.sss: s5p-sss driver registered [ 2.226796] dwmmc_exynos 12220000.mmc: Version ID is 250a [ 2.232750] dwmmc_exynos 12200000.mmc: Using internal DMA controller. [ 2.234102] hid: raw HID events driver (C) Jiri Kosina [ 2.238124] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 144,64 bit host data width,64 deep fifo [ 2.244291] dwmmc_exynos 12200000.mmc: Version ID is 250a [ 2.264162] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 145,64 bit host data width,64 deep fifo [ 2.268759] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 2.275936] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq [ 2.292675] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp [ 2.297970] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp [ 2.304571] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp [ 2.305514] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 2.312086] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp [ 2.327451] exynos-ppmu: new PPMU device registered 10d00000.ppmu (ppmu-event3-dmc0-0) [ 2.335102] exynos-ppmu: new PPMU device registered 10d10000.ppmu (ppmu-event3-dmc0-1) [ 2.342974] exynos-ppmu: new PPMU device registered 10d60000.ppmu (ppmu-event3-dmc1-0) [ 2.350839] exynos-ppmu: new PPMU device registered 10d70000.ppmu (ppmu-event3-dmc1-1) [ 2.361081] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_0 not found [ 2.367518] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_1 not found [ 2.375591] exynos5-dmc 10c20000.memory-controller: DMC initialized, in irq mode: 0 [ 2.384755] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0) [ 2.394797] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s [ 2.397011] mmc0: new ultra high speed SDR104 SDHC card at address aaaa [ 2.407340] NET: Registered PF_PACKET protocol family [ 2.409624] mmcblk0: mmc0:aaaa SE32G 29.7 GiB [ 2.412797] NET: Registered PF_KEY protocol family [ 2.422627] Key type dns_resolver registered [ 2.426187] mmcblk0: p1 p2 [ 2.426754] Registering SWP/SWPB emulation handler [ 2.434051] registered taskstats version 1 [ 2.437817] Loading compiled-in X.509 certificates [ 2.443116] Key type .fscrypt registered [ 2.446464] Key type fscrypt-provisioning registered [ 2.457336] Key type encrypted registered [ 2.588749] exynos-chipid 10000000.chipid: cpu0 opp0, freq: 1500 missing [ 2.594193] exynos-chipid 10000000.chipid: cpu4 opp0, freq: 2100 missing [ 2.600762] exynos-chipid 10000000.chipid: Exynos: CPU[EXYNOS5800] PRO_ID[0xe5422000] REV[0x1] Detected [ 2.617722] OF: graph: no port node found in /soc/hdmi@14530000 [ 2.624147] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations [ 2.630520] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0e7bc8c) [ 2.637165] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0e7c26c) [ 2.643884] exynos-drm-g2d 10850000.g2d: The Exynos G2D (ver 4.1) successfully registered. [ 2.651958] exynos-drm exynos-drm: bound 10850000.g2d (ops 0xc0e7d27c) [ 2.658441] exynos-rotator 11c00000.rotator: The exynos rotator has been probed successfully [ 2.666855] exynos-drm exynos-drm: bound 11c00000.rotator (ops 0xc0e7db08) [ 2.673723] exynos-scaler 12800000.scaler: The exynos scaler has been probed successfully [ 2.681842] exynos-drm exynos-drm: bound 12800000.scaler (ops 0xc0e7e250) [ 2.688607] exynos-scaler 12810000.scaler: The exynos scaler has been probed successfully [ 2.696755] exynos-drm exynos-drm: bound 12810000.scaler (ops 0xc0e7e250) [ 2.703526] exynos-scaler 12820000.scaler: The exynos scaler has been probed successfully [ 2.711662] exynos-drm exynos-drm: bound 12820000.scaler (ops 0xc0e7e250) [ 2.718396] exynos-drm-gsc 13e00000.video-scaler: The exynos gscaler has been probed successfully [ 2.727314] exynos-drm exynos-drm: bound 13e00000.video-scaler (ops 0xc0e7eb24) [ 2.734594] exynos-drm-gsc 13e10000.video-scaler: The exynos gscaler has been probed successfully [ 2.743425] exynos-drm exynos-drm: bound 13e10000.video-scaler (ops 0xc0e7eb24) [ 2.791131] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 2.838676] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 2.878753] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 2.907827] Console: switching to colour frame buffer device 180x56 [ 2.973325] exynos-drm exynos-drm: [drm] fb0: exynosdrmfb frame buffer device [ 2.984476] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0 [ 3.004351] mali 11800000.gpu: GPU identified as 0x0620 r0p1 status 0 [ 3.010719] mali 11800000.gpu: Protected mode not available [ 3.018316] mali 11800000.gpu: Probed as mali0 [ 3.026735] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 3.030849] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 3 [ 3.039677] xhci-hcd xhci-hcd.8.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 3.048138] xhci-hcd xhci-hcd.8.auto: irq 153, io mem 0x12000000 [ 3.054235] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller [ 3.059294] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 4 [ 3.066981] xhci-hcd xhci-hcd.8.auto: Host supports USB 3.0 SuperSpeed [ 3.073679] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 3.081733] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.088855] usb usb3: Product: xHCI Host Controller [ 3.093692] usb usb3: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.099147] usb usb3: SerialNumber: xhci-hcd.8.auto [ 3.105733] hub 3-0:1.0: USB hub found [ 3.108240] hub 3-0:1.0: 1 port detected [ 3.113412] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.120627] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 3.128666] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.135843] usb usb4: Product: xHCI Host Controller [ 3.140461] usb usb4: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.148036] usb usb4: SerialNumber: xhci-hcd.8.auto [ 3.153685] hub 4-0:1.0: USB hub found [ 3.157741] hub 4-0:1.0: 1 port detected [ 3.169399] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 3.175224] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5 [ 3.183781] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010 [ 3.193572] xhci-hcd xhci-hcd.9.auto: irq 154, io mem 0x12400000 [ 3.200100] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 3.205886] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6 [ 3.213785] xhci-hcd xhci-hcd.9.auto: Host supports USB 3.0 SuperSpeed [ 3.220664] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 3.229213] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.236762] usb usb5: Product: xHCI Host Controller [ 3.241897] usb usb5: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.247575] usb usb5: SerialNumber: xhci-hcd.9.auto [ 3.253145] hub 5-0:1.0: USB hub found [ 3.257072] hub 5-0:1.0: 1 port detected [ 3.261543] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.269904] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 3.278421] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.285801] usb usb6: Product: xHCI Host Controller [ 3.290803] usb usb6: Manufacturer: Linux 6.1.77+ xhci-hcd [ 3.292505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 3.294925] usb usb6: SerialNumber: xhci-hcd.9.auto [ 3.314476] hub 6-0:1.0: USB hub found [ 3.318373] hub 6-0:1.0: 1 port detected [ 3.324905] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling [ 3.330709] s3c-rtc 101e0000.rtc: registered as rtc1 [ 3.340796] exynos-bus: new bus device registered: soc:bus-wcore ( 88700 KHz ~ 532000 KHz) [ 3.345656] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 3.348273] exynos-bus: new bus device registered: soc:bus-noc ( 66600 KHz ~ 111000 KHz) [ 3.370263] exynos-bus: new bus device registered: soc:bus-fsys-apb (111000 KHz ~ 222000 KHz) [ 3.379488] exynos-bus: new bus device registered: soc:bus-fsys2 ( 75000 KHz ~ 200000 KHz) [ 3.388608] exynos-bus: new bus device registered: soc:bus-mfc ( 83250 KHz ~ 333000 KHz) [ 3.397524] exynos-bus: new bus device registered: soc:bus-gen ( 88700 KHz ~ 266000 KHz) [ 3.406667] exynos-bus: new bus device registered: soc:bus-peri ( 66600 KHz ~ 66600 KHz) [ 3.411109] usb 3-1: new high-speed USB device number 2 using xhci-hcd [ 3.419851] exynos-bus: new bus device registered: soc:bus-g2d ( 83250 KHz ~ 333000 KHz) [ 3.431814] exynos-bus: new bus device registered: soc:bus-g2d-acp ( 66500 KHz ~ 266000 KHz) [ 3.440249] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 3.440969] exynos-bus: new bus device registered: soc:bus-jpeg ( 75000 KHz ~ 300000 KHz) [ 3.460397] exynos-bus: new bus device registered: soc:bus-jpeg-apb ( 83250 KHz ~ 166500 KHz) [ 3.469573] exynos-bus: new bus device registered: soc:bus-disp1-fimd (120000 KHz ~ 200000 KHz) [ 3.478997] exynos-bus: new bus device registered: soc:bus-disp1 (120000 KHz ~ 300000 KHz) [ 3.487932] exynos-bus: new bus device registered: soc:bus-gscl-scaler (150000 KHz ~ 300000 KHz) [ 3.497582] exynos-bus: new bus device registered: soc:bus-mscl ( 84000 KHz ~ 666000 KHz) [ 3.508589] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 3.535680] ALSA device list: [ 3.539420] #0: ODROID-XU4 [ 3.544075] Waiting for root device UUID=e139ce78-9841-40fe-8823-96a304a09859... [ 3.605856] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=22.23 [ 3.615230] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.623491] usb 3-1: Product: USB2.0 Hub [ 3.628491] usb 3-1: Manufacturer: GenesysLogic [ 3.682358] hub 3-1:1.0: USB hub found [ 3.689564] hub 3-1:1.0: 2 ports detected [ 3.751499] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd [ 3.794759] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616, bcdDevice=22.23 [ 3.805887] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.815965] usb 4-1: Product: USB3.0 Hub [ 3.822775] usb 4-1: Manufacturer: GenesysLogic [ 3.858309] hub 4-1:1.0: USB hub found [ 3.863915] hub 4-1:1.0: 2 ports detected [ 4.061238] usb 3-1.1: new low-speed USB device number 3 using xhci-hcd [ 4.206144] usb 3-1.1: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00 [ 4.221958] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.233307] usb 3-1.1: Product: USB Optical Mouse [ 4.238474] usb 3-1.1: Manufacturer: Logitech [ 4.371238] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd [ 4.391069] usb 3-1.2: new low-speed USB device number 4 using xhci-hcd [ 4.412822] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00 [ 4.422627] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 4.431336] usb 6-1: Product: USB 10/100/1000 LAN [ 4.437514] usb 6-1: Manufacturer: Realtek [ 4.443094] usb 6-1: SerialNumber: 000001000000 [ 4.536824] usb 3-1.2: New USB device found, idVendor=1a2c, idProduct=2d23, bcdDevice= 1.10 [ 4.549773] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.559722] usb 3-1.2: Product: USB Keyboard [ 4.564096] usb 3-1.2: Manufacturer: USB [ 4.677461] r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd [ 4.733246] r8152 6-1:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw failed with error -2 [ 4.742982] r8152 6-1:1.0: unable to load firmware patch rtl_nic/rtl8153a-3.fw (-2) [ 4.793138] r8152 6-1:1.0 eth0: v1.12.13 [ 4.939315] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 5.000498] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 5.060339] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 5.119528] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 5.459354] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 5.522765] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 5.578951] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 5.635751] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 5.979379] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.042260] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 6.098485] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 6.157505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 6.498761] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 6.556671] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 6.612113] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 6.668707] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250) [ 7.009370] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63) [ 7.070667] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84) [ 7.126100] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125) [ 7.183829] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
  21. Hello, i'm using Armbian 23.11 Jammy-amazingfated Gnome. Kernel 5.10 If to seek a couple of times in h264 1080p BD remux'es it will cause system restart. Any video players are affected. Tried mpv, vlc, kodi and others. Problem affect just h264 1080p remuxes, that typically are 30..40 Gb, smaller h264 or even larger h265 files seem to work fine. I tried fresh install of armbian, where no rkmpp is installed, then h264 files plays/seeks fine, in software mode of course. Once I did sudo update/upgrade, that also installs rkmpp and other rockchip stuff, then videos start to play with rkmpp and problem is back. I've tried disabling hw decoding as workaround , weird, but it seems it's not possible to do in any player. In mpv : hwdec=no , or pressing ctrl+h has no affect, can't get rid of rkmpp decoder. Ive tried all possible commands related to this, from official mpv documentation, but nothing helps to disable rkmpp . This is probably another issue. Disabling buggy h264_rkmpp_decoder could be good workaround, as cpu is easily capable do play 1080p in sw, but can't find a way to do this, no matter i try, pls help. Especially looking for solution for mpv
  22. Hello, I'm currently having trouble getting Kodi to run smoothly on my RADXA RockPi 5B. Despite having set up Kodi multiple times before, I'm facing some challenges this time around. Here's what I've done so far: Installed the Armbian_community_24.5.0-trunk.168_Rock-5b_jammy_vendor_6.1.43_gnome_desktop.img.xz image onto a micro SD card for my RockPi 5B. Followed the instructions provided on the Armbian website for the RockPi 5B (https://www.armbian.com/rock-5b/). While Armbian boots up fine and I can start Kodi, I encounter a few issues: - The screen resolution is initially incorrect when Kodi starts up. To fix this, I have to navigate blindly to the video settings, switch to windowed mode, then back to full screen. However, this fix doesn't persist after a restart. - Additionally, the version of Kodi ( https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy/main arm64 kodi-bin arm64 2:20.2+dfsg-4+gles1 ) I have seems incomplete. It lacks the default Kodi repo, and I can't add any other due to missing dependencies. I would greatly appreciate any assistance or insights into what might be going wrong here. Thank you for your help.
  23. Description This is a follow-up on this PR https://github.com/armbian/build/pull/6376 and this comment https://github.com/armbian/build/pull/6376#issuecomment-1987147291 It's more of an idea, since I tried rewrite-uboot-patches and noticed the following: Board NanoPi-R6S has 5 U-Boot patches in total (legacy/u-boot-raxda-rk3588). Using ./compile.sh BOARD=nanopi-r6s BRANCH=edge rewrite-uboot-patches has the following patch summary: Summary: u-boot patching: 5 total patches; 5 applied; 2 with problems; 2 needs_rebase However, instead of only rewriting/rebasing the 2 patches, it modifies all 5 patches slightly (see example below). This means your git working tree quickly gets cluttered with these modified-without-any-real-changes patch files. And you'll have to either figure out which patches were changed/rebased if you only want to commit those, or commit all and make it harder to see the actual changes (I think?). Example of a patch file getting modified even if the patch stays the same: (Notice the lines/hunks did not get changed, only the metadata) git diff patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch | cat diff --git a/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch b/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch index 38f1a5a..b8e16cd 100644 --- a/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch +++ b/patch/u-boot/legacy/u-boot-radxa-rk3588/0001-Add-defconfig-and-dtb-of-nanopi6.patch @@ -1,18 +1,16 @@ -From 70d65e65db965295ddd23d5db752aad1c035c205 Mon Sep 17 00:00:00 2001 +From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Muhammed=20Efe=20=C3=87etin?= <efectn@protonmail.com> Date: Sat, 15 Apr 2023 23:12:17 +0300 -Subject: [PATCH] Add defconfig and dtb of nanopi6 +Subject: Add defconfig and dtb of nanopi6 --- - arch/arm/dts/rk3588s-nanopi-r6s.dts | 126 ++++++++++++++++ - configs/nanopi-r6s-rk3588s_defconfig | 217 +++++++++++++++++++++++++++ + arch/arm/dts/rk3588s-nanopi-r6s.dts | 126 ++++++ + configs/nanopi-r6s-rk3588s_defconfig | 217 ++++++++++ 2 files changed, 343 insertions(+) - create mode 100644 arch/arm/dts/rk3588s-nanopi-r6s.dts - create mode 100644 configs/nanopi-r6s-rk3588s_defconfig diff --git a/arch/arm/dts/rk3588s-nanopi-r6s.dts b/arch/arm/dts/rk3588s-nanopi-r6s.dts new file mode 100644 -index 0000000000..4899e23fa3 +index 000000000000..4899e23fa3aa --- /dev/null +++ b/arch/arm/dts/rk3588s-nanopi-r6s.dts @@ -0,0 +1,126 @@ @@ -144,7 +142,7 @@ index 0000000000..4899e23fa3 +}; diff --git a/configs/nanopi-r6s-rk3588s_defconfig b/configs/nanopi-r6s-rk3588s_defconfig new file mode 100644 -index 0000000000..19bae55629 +index 000000000000..19bae5562928 --- /dev/null +++ b/configs/nanopi-r6s-rk3588s_defconfig @@ -0,0 +1,217 @@ @@ -366,5 +364,5 @@ index 0000000000..19bae55629 +CONFIG_OPTEE_V2=y +CONFIG_OPTEE_ALWAYS_USE_SECURITY_PARTITION=y -- -2.39.2 +Armbian How I tried to solve this The information if a patch needs rebasing is already there, so I tried to solve this by introducing a new option REWRITE_PATCHES_NEEDING_REBASE in addition to the existing REWRITE_PATCHES. Why an additional option? I didn't want to break anything (took me some hours already to figure out where the actual patch rewriting happes and to understand their logic, so I'm not confident to change what REWRITE_PATCHES does on its own 😅) Maybe there will be some reason when you want to actually rewrite all patches even if they don't need rebasing? If it's not an issue, I could also just remove the additional option REWRITE_PATCHES_NEEDING_REBASE and instead make this the default behaviour for REWRITE_PATCHES. How Has This Been Tested? [x] Run the same command as earlier: ./compile.sh BOARD=nanopi-r6s BRANCH=edge rewrite-uboot-patches and only the 2 patches that needed rebasing were modified [x] Compiled a board image to check if nothing got broken: ./compile.sh build BOARD=nanopi-r5c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article
  24. Hello, I've started a project where I'd like to setup a Bananapi M5 with two wifi adapters to use in hotel room for example. So one wifi adapter will connect to the hotel wifi, and the other will be in access point mode with dhcp for my devices to connect to. I think the proper terminology is AP-STA. So I have purchased one Comfast CF-953AX which uses the mt7921au chipset (0e8d:7961) to test in access point mode as it supports this: Supported interface modes: * managed * AP * AP/VLAN * monitor * P2P-client * P2P-GO The issue I have come across is the hostapd fails to start: nl80211: Failed to start radar detection: -22 (Invalid argument) I think I've tracked it down to the wifi region not being set: sudo iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) sudo iw reg reload command failed: No data available (-61) ..and you cannot set it, I think this post may explain it better than me: https://forum.odroid.com/viewtopic.php?t=44942 Is there a way to set the wifi region? Thanks
  25. because the android stock bootloader allows to boot from sdcard if you package the bootloader on sdcard using the rockchip proprietary tools. The android stock bootloader is loaded first (because it is on emmc), but then it check for specific bits on sdcard; if found, it passes control to the sdcard Multitool and libreelec image bootloaders are made with proprietary tools, instead armbian uses a bootloader made with opensource u-boot tools and thus is not recognized as a boot device from stock bootloader. Mainline u-boot supports dtb overlays, USB and PXE boot - in addition to other basic features - that are not supported in stock android bootloader. To test the image before burning it on eMMC: if you burn an image that does not boot, you may soft-brick your board and then it would be required to short eMMC clock pin to enter maskrom mode and clean the eMMC flash to restore functionality. If you have a R29, R2B or H20 board, led-conf7 overlay is essential to get stable operation. Here is a post on how to activate it manually via multitool on eMMC or plugging the sdcard in your PC and editing the file (ignore the part on copying things around, they are now already in place).
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines