Jump to content

hexdump

Members
  • Posts

    457
  • Joined

  • Last visited

Everything posted by hexdump

  1. @embedder_dev - if you want to seriously put some work into making armbian work with those, maybe have a look at the xdarklight tree: https://github.com/xdarklight/linux - the branch meson-mx-integration-6.2-20221226 is quite close to v6.1-lts (see: https://github.com/hexdump0815/linux-mainline-and-mali-generic-stable-kernel/blob/lts-v6.1/misc.m8x/patches/xdl-vs-mainline-v6.1.49.patch ) or you try to get one of the latest branches working - this tree even has hdmi support for the old meson8 socs and might be a good start for bringing up armbian support for those socs if case you want to invest some time into it - good luck
  2. one thing to keep in mind is that the warpme tree and its patches on github has not been updated for a few months now except for the changelog and readme changes - all other changes which are in the last miniarch images are not available online so far ...
  3. @Gunjan Gupta - there was some effort to adjust an existing mainline driver to support xr819 as well two years ago or so - it started about here: https://oftc.irclog.whitequark.org/linux-sunxi/2021-06-22#30028495 and then moved on over the next days etc. - seaching for cw1200 seems to bring up more - maybe it might be more useful to look into this direction instead of bsp sources ... maybe it is interesting/helpful to read through that a bit update: this seems to be some tree with the changes discussed on irc back then: https://github.com/jernejsk/linux-1/commits/h616-test best wishes - hexdump
  4. @jock - that not booting with a clean emmc reminds me a bit on the rk3328 box i have which has the sd card connected to the wrong mmc port and thus cannot boot from sd card - it works with a workaround to install some special u-boot in emmc which then boots from sd card via extlinux.conf or boot.scr ... can it be that those rk3528 boxes are similar?
  5. ok - typical tv box hardware then - you never know what you really get
  6. you never know what you really get with tv box hardware, but the q+ so far was allwinner h6 and not h616, so maybe you are trying the image for the wrong soc in the end. also there is no need to press the button inside the av port - allwinner devices boot by default from sd card, so just write the image to an sd card, insert it and power on the box and then it should either boot (if everything is fine) or not (if not) ... good luck
  7. there is no open source support for rk3528 there yet, so no chance to get anything working - warpme has started to work on it for the minimyth2 project, but even that is in very early stages and i think still very far to be really useable ... so no way to run armbian or linux on such boxes currently ...
  8. @adrian0541 - s905x3 is sm1, s905x2 is g12a, s905x is gxl and so on ...
  9. i think "ipv6.disable=1" added to the kernel cmdline should work
  10. not sure if it is related, but there was something similar in the past - see:
  11. @Lavacat - that sounds like the x7(5G) box i have here ... the 12v power supply seems to work, but i'm not sure how healthy it is over time - it might be better to get a 5v/2a as usual if easily possible ... also do not expect the audio of the box to work well with linux as it seems to be somewhat broken as well for those boxes the s905l2 is - as far as i found out - a s905w with parts of the gpu disabled and if that is not taken care of the kernel will panic at boot - this was my ugly hack to make it work: https://github.com/hexdump0815/linux-mainline-and-mali-generic-stable-kernel/blob/master/misc.av8/dtb/meson-gxl-s905l2-x7-5g.dts not sure if @SteeMan might want to add something like this to his armbian builds as well? best wishes and good luck - hexdump
  12. @sfx2000 - you might have a look at this: https://github.com/hexdump0815/imagebuilder/issues/130#issuecomment-1453574856 - this is about getting another rk3288 chromebox booting - from there you can maybe see what needs to be added to armbian to get it supported there as well best wishes - hexdump
  13. @Z11ntal33r - do you maybe run your odroid n2 with cpu overclocking? this can sometimes result in such random errors - otherwise maybe try to lower the max cpu freq via /sys/devices/system/cpu/cpufreq to check if it runs more stable in such a case.
  14. @Slash402 - it is not uncomming for chinese android tv boxes to have fake specs - one cannot really trust anything, from ram to emmc sizes, emmc vs. nand and even sometimes a different soc is inside than what is printed on the box
  15. @stut - here i wrote down quite a bit of information about how to build mainline u-boot for amlogic s905x/w devices - see: https://github.com/hexdump0815/u-boot-misc/blob/master/readme.gxl - you might try the ones i built (see the july 18 2020 releases of that github repo) - gunzip all the files with boot-amlogic_gxl_*.gz and then dd them to an sd card and try to boot them one by one with serial console and a hdmi monitor connected (some have serial console and some hdmi) - if you are lucky one of them maybe gives you a working mainline u-boot you can boot from sd card good luck and best wishes - hexdump
  16. i think the arm version of the surface pro 9 is close to the devkit - surface pro x is an older design using a snapdragon 8cx gen2 (i think) and not the gen3 the devkit is using and which is a very different soc
  17. @hartraft - there are two kernel options for mglru: CONFIG_LRU_GEN=y and CONFIG_LRU_GEN_ENABLED=y - the first is to have mglru built into the kernel and the second is to have it enabled by default - if they are not in your kernel config it might be required to rebuild the kernel with them (or at least the first) enabled
  18. @SteeMan - interesting, i did not know about ampart, but as you said: for s905 it is better to still just run from sd card as trying to boot from emmc is quite complicated and risky to brick the device
  19. @DWP - running s905 from emmc is very complex and far from easy - you can have a look at this thread to get an idea about this topic:
  20. but be careful with such scripts and check them by hand to make sure they do not touch the emmc low level or your created partitions ... for copying over "rsync -axADHSX --no-inc-recursive --delete /source/ /target" always worked well for me - be careful with the "--delete" and note that the source should have a "/" appended and the target not if you want target to be a 1:1 copy of source good luck and best wishes - hexdump
  21. @winnt5 - maybe start with data only and see if you can handle it well from an sd-card booted system and then maybe move on from there ... maybe you can just partition everything from cache on (i.e. after its starting poiint if there is nothing reserved/hidden inbetween - better double check the layout a few times) as you like it as all those should be android partitions and not related to boot ... there is always a chance that something goes wrong and you brick the box - maybe do a dd dump of the full device beforehand ... in the end you are on your own if you play around with this
  22. @winnt5 - any partitioning tool should like fdisk, gdisk etc. - just make sure you are creating an mbr partition table and not gpt and best is to some detailed mode if available in the tool used to be able to hit the block numbers of the data partition exactly good luck and best wishes - hexdump
  23. @winnt5- you could boot and run from usb and from there create a btrfs filesystem with zstd compression on emmc data, rsync everything over, adjust fstab in it for btrfs and try that - i'm using zstd comressed btrfs root for years now (not with armbian) and it works very stable and saves close to half of the space - another option is to run from usb and put a swap partition or file to emmc - i think swapping/paging is most proably the reason for the performance problems you see when running from usb. good luck and best wishes - hexdump
  24. @winnt5 - it is quite normal that you do not see any partitions on emmc from the android system, as that uses hardcoded partitioning and not a normal mbr or gpt partition table ... also what @SteeMansays can be true: that there is no emmc at all in the box but just nand - this is easy to find out: just run "fdisk -l" on the box and if you can see another mmcblk device besides your sd card then you most probably have proper emmc. in case you have real emmc there are two options: the safe one to not touch emmc at all to not break your locked bootloader or the risky one to write an mbr partition table to the emmc which only covers the data partition of android - do not even think about touching any other partition/area besides the large data partition at the end of the emmc as some of the other partitions might be magic and required for booting (holding the dtb or other stuff required to boot - amlogic boxes are horrible in this direction) ... for that you would need to find out at which sector the user data partition starts from android (some math required maybe) and you should double check that the first 512bytes on emmc are empty via "hexdump -C" (i.e. writing the mbr there will not overwrite anything else) ... it worked for me at least on a mii s905x box with locked bootloader but there is no guarantee that it will work for you as well - so better chooese the safe option if you prefer to keep the box working for sure ... there might even be a way in the middle to hardcode a partition covering the data partition are also with a mainline kernel - for that reasearching about mtdparts might be a good idea - never tried that myself - this way you at least would not have to write a partition table to emmc ... just for completeness: this thread might be interesting to read as well as on s905 it is very complicated as well as bootloader and partition table overlap for the emmc case and some people were quite creative trying to overcome this - best wishes and good luck - hexdump
  25. not sure if its related, but it might be worth to give this kernel patch a try: https://patchwork.kernel.org/project/linux-amlogic/patch/20221116143523.2126-1-the.cheaterman@gmail.com/ ...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines