Active threads

@JuanEsf Yep, here it is a080ed7128c898bec1cad6ec68c57bae159169d2fa06fb18008100ad63e4445c

You are right, this is a strange DTS issue. U-Boot is working, but the kernel can't initialize the SD card, which is why it drops to the initramfs shell. Unfortunately, I can't reproduce this specific error myself, but I agree with your analysis. I suspect this is the same reason why newer U-Boot versions initially failed to boot for me. I will start working on fixing the DTS next week. Thanks for finding this bug!

@Igor@amazingfate Can someone look at this issue please ? I am wondering if this is possibly affecting a large number targets or whether its just BananaPi-M7 / rockchip64 ? I have tried on another monitor also and am getting a black screen. On doing an `apt-get upgrade` on ssh terminal I happened to loose by HDMI display. AFAICT It looks like Ubuntu 'backgraded' gnome v46 (in Nobel release, and also in my older unofficial image) to v44. https://armbian.atlassian.net/jira/software/c/projects/AR/issues/AR-2702?jql=project %3D "AR" ORDER BY created DESC

Hi, I'm facing the same issue with my BananaPI-M1 running ARMbian and I have another one bPI-M1 running ArchARM which is suffering exactly for the same issue (bPI is not supposed to be supported but it working pretty well but this HDMI issue and the miss of AXP209 exposition). I'm a bit lost about the current status : is the upstream 6.15 (or upcoming 6.16) already patched/corrected ? @eselarm The link seems dead 🙂

Thanks, I'll pursue with the thread you mentioned.

If you guys want Bionic, I can remove stretch, and link it. You should try to download stretch again, and try a different SD card before anything else.

Just noticed I was not up to date, I did a armbian-upgrade and still no change. Here is an updated paste : https://paste.armbian.de/loderavavi

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

I backuped the boot dir. So I don't need booting from Sd-card, armbian-install will format emmc and copy from where the boot dir? Afterward it moves the system to emmc. If I am running armbian-config there's a message "Warning: The current OS (bookworm) is not supported or not listed" it's the latest version "Armbian 21.02.1 stable 6.12.32-current-rockchip64 (Debian bookworm)" apt-get install armbian-config armbian-config is already the newest version (25.8.0-trunk.330.0708.120916) I can't see any option to install/update system

Balena etcher and rufus burned sd card into small partitions and i cant put there 2.2gb image file how to make multitool partition more then 300mb to fit image there?

@remlei I've tried several different versions of rkdevtool, and I also tried under linux with rkflashtool and with the official rockchip flash tool, it all failed. @Benedito Portela Are you able to flash the original loader back? If so, which file do you use? My rkdumper dump does not seem to have the loader included.

Hi Guillame, github won't let me create a pull request as there is no content. I think you can't create a pull request if there is no code in the repository Kind regards, Mark

Raspberry images are compatible from 3b up to 5b

Hello everyone, I have the same situation. On versions 6.х.х the built-in wifi and bluetooth do not work, but the board is compatible with a 7inch HDMI LCD 1024x600 Pixel monitor. But in kernel versions 5.х.х wifi and bluetooth work, but do not work with a 7inch HDMI LCD monitor. That's how things are, just keep up with the news with new patches or builds.

What wifi do you have? Did you run rk3318-config to configure the device tree overlays for your board properly? The intent of rk3318-config script is to avoid the users tinkering with the DTS, but requires to know the board name printed on the silkscreen of the board itself. The commercial box name, instead, is often useless or misleading.

@ScoreABSM https://github.com/armbian/build/pull/8368

You're welcome. Checkout its plugins, called 'modules' https://www.webmin.com/cgi-bin/search_third.cgi?modules=1 and https://www.niemueller.de/project/webmin/ but some may be outdated. I haven't installed this but I will soon when I tell myself to stop watching addictive adventure and "challenge" videos on youtube, haha

The latest 6.16.RC3 kernel breaks the Intel PCI Wifi drivers. Was working in 6.15 without issue: [ 5.321789] iwlwifi 0004:41:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz [ 5.329839] iwlwifi 0004:41:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 5.330430] iwlwifi 0004:41:00.0: loaded firmware version 77.864baa2e.0 cc-a0-77.ucode op_mode iwlmvm [ 5.587350] iwlwifi 0004:41:00.0: Detected RF HR B3, rfid=0x10a100 [ 5.653139] iwlwifi 0004:41:00.0: base HW address: 04:ed:33:54:7e:d2 [ 5.716280] iwlwifi 0004:41:00.0 wlP4p65s0: renamed from wlan0 [ 8.890717] iwlwifi 0004:41:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1 [ 8.890759] WARNING: CPU: 6 PID: 1203 at drivers/net/wireless/intel/iwlwifi/mvm/mld-mac.c:37 iwl_mvm_mld_mac_ctxt_cmd_common+0x158/0x1e4 [iwlmvm] [ 8.890778] Modules linked in: sunrpc iwlmvm pwm_fan display_connector mac80211 rk805_pwrkey libarc4 snd_soc_hdmi_codec snd_soc_core hantro_vpu snd_compress rockchip_vdec2(C) snd_pcm_dmaengine v4l2_vp9 rk_crypto2 iwlwifi v4l2_jpeg rockchip_rga snd_pcm sm3_generic v4l2_h264 libsm3 videobuf2_dma_contig v4l2_mem2mem videobuf2_dma_sg snd_timer videobuf2_memops videobuf2_v4l2 snd videodev joydev panthor soundcore cfg80211 videobuf2_common drm_gpuvm drm_exec mc rfkill gpu_sched drm_shmem_helper cpufreq_dt zram binfmt_misc sch_fq_codel dm_mod autofs4 realtek phy_rockchip_samsung_hdptx phy_rockchip_usbdp fusb302 tcpm typec rtc_pcf8563 dwmac_rk nvmem_rockchip_otp stmmac_platform stmmac rockchip_rng rng_core pcs_xpcs rockchipdrm dw_hdmi_qp dw_hdmi cec dw_mipi_dsi analogix_dp drm_display_helper drm_dp_aux_bus [ 8.891251] iwlwifi 0004:41:00.0: Microcode SW error detected. Restarting 0x0. [ 8.891978] iwlwifi 0004:41:00.0: Start IWL Error Log Dump: [ 8.892489] iwlwifi 0004:41:00.0: Transport status: 0x0000004B, valid: 6 [ 8.892494] iwlwifi 0004:41:00.0: Loaded firmware version: 77.864baa2e.0 cc-a0-77.ucode [ 8.892499] iwlwifi 0004:41:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL

Hello, would you be able to share the ISO you used along with the modified DTBs? @Aleqssandro Farias

Hi Werner! I'd like to have them, but I have the feeling that my Armbian image and the SPI U-boot won't... (even with the settings enabled, if that's the thing.) On the other hand, I've got the non-verbose startup logs. Tell me what I can do, I'll recompile in due course. 🙂 partial-logs.txt

OK, I did it. USB does not work when uploading a new image.

Oh, that's sad, I didn't realize this, the rk322x cpu datasheet mentions 64bit a lot, I thought it was. Thanks!

I can provide all necessary files,for the linux development for AM9.

Hi @faxe2110, or any other user, how are you? I'm working on a project with an Amlogic S805-based TV box and found your forum posts about custom Armbian images, particularly older versions like 5.67 with Debian Stretch and kernel 3.10.108. Unfortunately, the links you shared are no longer available, and I was wondering if you still have any of those files, or if you could give me some guidance on how to generate them. I'd greatly appreciate any help you can provide! Greetings from Argentina, Ricardo

Maybe, but maybe the issue won't occur then. If you want it reproducable, first for yourself, make a complete image of that USB stick on other large storage device and use that as 'master problem disk'. I have an old PC with 3x 4T HDD Btrfs multidevice formatted for such cases. Btrfs can make reflink copies or do RW snapshots, so easy and fast to create a slightly modified image. There is gddrescue to make initial copy from USB-stick. Also this is a USB-stick in an SBC, all sorts of power issues might also be a root cause. You can use nbd-server and nbd-client to make large/huge images available via network, I do that for my BananaPi M1 (8T HDD). In the past for Btrfs kernel development itself for example, there was/is? a metadata only imager tool, so in case of a complex filesystem bug, you can share only meta data, the data is actually zeroed/sparse. But you need a good extra Linux computer, Windows exFAT handling makes little sense. Best to also test/use the image with a generic Debian Bookworm/Trixie computer, I use a Armbian virtual machine for such a case, running on RPi4 (if 32-bit) or ROCK5B (64-bit only). They can use NBD (as client). AFAIR you can use the sunxi kernel directly in a KVM, at least did something with a NanoPi-NEO image (same kernel as well).