srx

I would also like to ask for headers. I think headers should be part of image. At least as long as kernel and headers are not downloadable via package manager (I hope we can soon get kernel/headers from a repository, so we do not need to install new image to get fresh kernel - this unified image is a step towards that goal). Otherwise it is impossible to compile modules. It is not very efficient to compile full custom kernel just so that you can add one little module. It takes ages. And it is somewhat difficult to replace a kernel. Or please provide kernel headers as separate download for every image version if you do not want to make it part of the image. I really do not understand why kernel headers are not included.

I've spent hours today playing with dtb parameters and whatnot. So far nothing. Yes, Android dtb and dtb in this image are different. But I can not just copy-paste it. It is all related and pretty difficult to understand. All I have is dmesg saying that SD card appeared, it is detected. Even partitions are detected and then it dissapears. But why it dissapears? SDXC card seems to appear, then dissapear, then appear again... [ 88.606168] mmc0: new high speed SDHC card at address aaaa [ 88.607742] mmcblk0: mmc0:aaaa SP32G 29.7 GiB [ 88.610100] mmcblk0: p1 p2 [ 89.637741] mmc0: card aaaa removed [ 89.731537] mmc0: error -84 whilst initialising SD card [ 90.824315] mmc0: error -84 whilst initialising SD card [ 91.912485] mmc0: error -84 whilst initialising SD card Keeps repeating the last message about once per second. /.../ Another card: [ 441.699628] mmc0: new high speed SDXC card at address aaaa [ 441.701190] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.706375] mmcblk0: unable to read partition table [ 441.707109] mmc0: card aaaa removed [ 441.709786] udevd[2335]: inotify_add_watch(7, /dev/mmcblk0, 10) failed: No such file or directory [ 441.815132] mmc0: new high speed SDXC card at address aaaa [ 441.816655] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.819250] mmcblk0: p1 p2 [ 441.890260] blk_update_request: I/O error, dev mmcblk0, sector 124735472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 441.957930] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.031386] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.034128] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 EDIT: The same card/image/kernel that gives endless -84 errors boots just fine in another device. I just changed dtb to match hardware and started it up in Nexbox A95X (s905x/2GB/8GB). No errors, starts just fine. In A95X F3 Air (S905x3/4GB/32GB) still no luck. I have no time to do more research at the moment. Maybe I'll try again next weekend.

I've spent hours today playing with dtb parameters and whatnot. So far nothing. Yes, Android dtb and dtb in this image are different. But I can not just copy-paste it. It is all related and pretty difficult to understand. All I have is dmesg saying that SD card appeared, it is detected. Even partitions are detected and then it dissapears. But why it dissapears? SDXC card seems to appear, then dissapear, then appear again... [ 88.606168] mmc0: new high speed SDHC card at address aaaa [ 88.607742] mmcblk0: mmc0:aaaa SP32G 29.7 GiB [ 88.610100] mmcblk0: p1 p2 [ 89.637741] mmc0: card aaaa removed [ 89.731537] mmc0: error -84 whilst initialising SD card [ 90.824315] mmc0: error -84 whilst initialising SD card [ 91.912485] mmc0: error -84 whilst initialising SD card Keeps repeating the last message about once per second. /.../ Another card: [ 441.699628] mmc0: new high speed SDXC card at address aaaa [ 441.701190] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.706375] mmcblk0: unable to read partition table [ 441.707109] mmc0: card aaaa removed [ 441.709786] udevd[2335]: inotify_add_watch(7, /dev/mmcblk0, 10) failed: No such file or directory [ 441.815132] mmc0: new high speed SDXC card at address aaaa [ 441.816655] mmcblk0: mmc0:aaaa SR64G 59.5 GiB [ 441.819250] mmcblk0: p1 p2 [ 441.890260] blk_update_request: I/O error, dev mmcblk0, sector 124735472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 441.957930] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.031386] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 442.034128] blk_update_request: I/O error, dev mmcblk0, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 It is meson-gx-mmc driver that handles sd card as far as I understand.

Well, SD card is not faulty. I have tried several and none work. Most give the same -84 error, some give random IO errors. But none work. Same card on same system in USB reader boots just fine. Same card on same system when running Android works just fine. Same cards and same kernel work fine on different hardware/dtb. From that we know that: Card is ok. This specific hardware is ok and can read the card (works in andorid and bootloader). This specific kernel can read card on different hardware (works on RK3328 A5X Max - but not S905x3 A95X F3 Air). It does not work with specific hardware+dtb+kernel combo. Same problem with s9xxx image and 5.3 kernel. So what can be the problem? Some sort of bug in kernel that only appears on specific hardware. Incompatible reader and kernel driver. Problem with DTB - maybe this hardware needs a different dtb to describe card reader. Could be a small detail - different voltage setup, different clock setup, etc. I am not competent enough to look into kernel source and understand what the problem could be. I can understand most of the code - but I do not have the knowledge of card reader hardware specifics and how to program it. When it comes to dtb, it is difficult to understand what 4000 lines of text actually do. And this is highly hardware specific and I do not know what hardware expects. So again, difficult to see if something is wrong. I've run different tv boxes from sd card for a few years now. This is the first one that does not work from sd.

Here is A95X F3 Air dtb from android. I can not really understand how dtb describes hardware (yet...), so I have really hard time to understand if anything important is different. And it is not like it is just few lines... it is pretty long file. So not something you can understand in few minutes. https://hastebin.com/leluzuhado.pl Maybe someone who understands it can have a look and see if there is important difference in SD card section vs meson-g12a-* dtb files. For whatever reason I can not use any SD cards in linux. It will not even boot up past ROOTFS mounting point. All I get is different error messages. But at the same time bootloader can access SD cards just fine, to read kernel/ramdisk. Also Android can access SD cards just fine, no problems. Problem is only when linux kernel tries to access SD card and then it fails. I think I have tried most if not all meson-g12a-* and meson-g12b-* dtb files and while they all boot to kernel, none have been able to read SD card. And some have other problems like network not working.

mmc1: error -84 whilst initialising SD card Could it be related to DTB and SD voltage regulation or something like that? I have a faint memory of reading about it somewhere. Something like using non-standard/strange regulators that need different setup. I do not have much time or motivation to dig very deep. But if I can find some time I will look at DTB and compare SD card voltages on different devices. Could be as simple as fixing some numbers in DTB to get right voltage. But I would not bet on it. EDIT: SD voltage seems ok - 3.3V I measured A5X Max box where all cards work and that has also 3.3V. I also measured in Android and in Linux (well... initramfs console) to make sure that kernel does not change voltage - and it does not. It stays at 3.3V.

Mine is: VER_1.0 20170730 - and works with both unified image (5.5 kernel) and rk3328 image (both 4.4 and 5.3 kernel versions) Even if you install fresh image. No need to do the magic I described somewhere before. That magic was so that I do not need to do full wipe/install just for trying new kernel.

I am trying to run Armbian_20.02.0-rc1.036_Arm-64_buster_current_5.5.0-rc6_desktop_20200205.img on A95X F3 Air (S905x3, 4GB/32GB). Kernel loads to a point where it needs to mount ROOTFS and then there is infinite loop of error messages and I am dropped to initramfs console. error messages keep coming about once per second. mmc1: error -84 whilst initialising SD card I have tried several DTB files but every single one I tried ends up like this. This box has mt7668rsn module for WiFi/BT and as far as I understand it is connected over SDIO. Can that somehow screw it up? Kernel looks for SD card and is stuck on some strange SDIO implemetation? Or is SDIO device referenced by mmc[0-9] at all? Not sure how SDIO works on kernel level. I keep trying. And I will try "-next"/"-dev" image also. Maybe it works better. And I might try S9xxx image too. EDIT: Booting from USB works. But for whatever reason console is cyan instead of black when booting from usb. Looks like kernel does not like my Sandisk Extreme Pro 32GB microsd card. It reads kernel just fine and boots kernel. But when kernel tries to read sdcard, there are errors and it fails. Transend Premium 128GB card gives the same error. Sandisk Extreme Pro 64GB card gives the same error. Kingston Canvas Select Plus 64GB card gives lot of different IO errors and also fails. I have used that same cards with different images from this forum on S905/RK3328/S905x2 devices without problems so far. Not sure what is wrong with this device. I also have problem with S9xxx image and 5.3 kernel. Same problems. I just can not get SD card to work. Any ideas? EDIT2: Cards work fine in Android. So reader is ok and can read those cards. Bootloader also reads kernel from all of those cards just fine. There is something wrong with kernel mmc driver maybe? Some sort of comatibility issue?

I use default dtb. rk3328-box.dtb or something like that on my A5X Max and it works (except wifi and bluetooth). I have not been able to boot with x96 dtb-s. So every A5X max might not be the same. Mine is quite old oversion, bough over a year ago. Play around, try different rk3328 dtb files and see how they work.

I see that RK3328 in my A5X max is getting really hot. It is just touch under 50°C at idle. At the same time S905X2 in my Mecool KM9 box is running much cooler. About 35°C at idle. When compiling kernel (make -j4), temps go up to 72°C+ and then it crashes. S905X2 tops at about 53°C and keeps going. Not sure if my RK3328 (28nm) box has bad cooling or is S905X2(12nm) just so much more efficient. Looks like I need to look at cooling first before I try anything else. That could solve my crashing issues. But at the moment I would suggest to go with S905X2 boxes. Price is about the same.

Yandex disk link in 1st post. There are 4.4 and 5.3.0 versions. Two different folders. There is also unified image with 5.5 kernel in this thread (that I am running currently):

Thanks for pointing me to that. I have not read the whole thread and missed that bit. As I understand, I have to add that block to dtb? I decompiled dtb, added that bit, recompiled. I hope I got it right - at least it booted I am running unified image with 5.5 kernel now. It still crashed before dtb update. I hope it works better now. We will see in few days if it is stable or not. If that fix works I think it should be included in images. Saves a lot of trouble for many people.

Looks like 5.3 has the same crashing problem, it just took longer to get there (unless of course it is hardware issue that causes it). My A5X max just crashed again. Storage gone, nothing works. Shell is accessible but nothing works, everything gives "not found" or I/O error. Even reboot, init 6 or crtl+alt+del does not work. Only way is to pull the plug. And as storage is gone, no logs to diagnose the problem. This time I got 4 days uptime before it crashed. I guess I will try unified image next. It has 5.5.0 rc2 kernel.

Default dtb works for me. /dtb/rockchip/rk3328-box.dtb I have not tried others. No WiFi, no bluetooth. but everything else seems to work. I actually did not do full install of new image. I took only /boot and /lib/modules/5.3.0-rk3328-tv/ from new image to get 5.3 kernel. This is something I am not very happy about actually. There is no easy way to update kernel I know about. I do not want to backup everything, flash whole new image and then restore everything just to get fresh kernel. I used Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img for new kernel. Just ungzip it and mount with offsets mkdir /mnt/boot mkdir /mnt/root mount -o offset=16777216 Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img /mnt/boot mount -o offset=285212672 Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img /mnt/root to find correct offsets: #> fdisk -l Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img Disk Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img: 1.9 GiB, 1992294400 bytes, 3891200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x757e269e Device Boot Start End Sectors Size Id Type Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img1 32768 557055 524288 256M e W95 FAT16 (LBA) Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img2 557056 3891199 3334144 1.6G 83 Linux Multiply partition Start with Sector size 32768 x 512 = 16777216 = Offset for partition 1, /boot Second partition is rootfs And then you can copy /mnt/boot to /boot and /mnt/usr/lib/modules/5.3.0-rk3328-tv/ to /lib/modules/5.3.0-rk3328-tv/ make sure your dtb is correct in /boot/exlinux/extlinux.conf Check extlinux.conf to see if root filesystem detection is changed (root=LABEL=ROOTFS). If it is, change extlinux.conf to match your conf or update your conf to mach extlinux.conf. either way works. reboot and you should boot to new kernel if everything was done correctly and DTB works. If not, take your SD to some other computer and fix it. Of course this could be much easier. I would like to see it as deb package or at least tarball that I can just untar. Maybe we can get kernel update packages somehow? And some sort of bootloader (like grub, lilo, syslinux, etc) would be awesome, so you can install new kernel beside old one and if new does not boot, you have fallback option. Not sure if that is possible.

New 5.3 kernel seems to be better than old 4.4. I tried image with 4.4 kernel version and it kept crashing with IO errors at least once a day. I could not get any logs because it was just like storage suddenly disconnected or something like that. Nothing worked. Not even reboot. I tried different SD cards but no change. Now I have image with 5.3 kernel and so far I have 3 days uptime and no problems/crashes yet. I am running it on A5X Max with 4GB ram from SD card.