srx

  • Content Count

    26
  • Joined

  • Last visited

About srx

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. 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 p
  3. 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 p
  4. 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 A
  5. 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 moun
  6. 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 whe
  7. 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.
  8. 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 u
  9. 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.
  10. 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 sugges
  11. 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):
  12. 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.
  13. 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.
  14. 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_l
  15. 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.