lprot
lprot
> I think it should be fixed at Lazarus level (TSynEdit). It is not correct to add a such cm_* commands to DC. It is a MacBook Air only problem,...
> I think it should be fixed at Lazarus level (TSynEdit). It is not correct to add a such cm_* commands to DC. It is a MacBook Air only problem,...
> [@lprot](https://github.com/lprot) > > please take a photo of your keyboard Hi @rich2014 
Some additional info: 1. This is Allwinner A133 device. The bootloader does not check/use vbmeta. I can generate vbmeta with: `python3 avbtool.py make_vbmeta_image --flags 2 --output vbmeta` then burn with...
> try to simply `unpack` and then `repack` your boot.img with `magiskboot` without any modification. If it does not work, try `unpack -n` and then `repack -n`.   ...
> So the problem is from compression? try `unpack -n`, `mv ramdisk.cpio ramdisk.cpio.gz`, `gzip -d ramdisk.cpio.gz`, `gzip -9 ramdisk.cpio`, `mv ramdisk.cpio ramgisk.cpio.gz`, `repack -n`. > > Try different compression ratio,...
> what??? It's expected for magiskboot to gzip with `-9` because magiskboot will add more files into ramdisk, resulting in a large ramdisk. If magisk does not pack with `-9`,...
> But magiskboot does not add name into gzipped ramdisk... then problem is not with the compression?
> that's why I want you to test if your device boots with different compression levels of manually compressed ramdisk (with `-n`). Prepared boot6.img, boot7.img, boot9.img this way: `./magiskboot unpack...
I am continuing to investigate this further: 1. ./magiskboot unpack -n boot.img produces ramdisk.cpio with the 758638 bytes size 2. ./magiskboot unpack -n boot9.img produces ramdisk.cpio with the 758090 bytes...