![]() the DEBUG=1 option might do that for you actually, been a while since i had to debug anything since Intel is all i've got. usually you can get the android initramdisk to at least find the main storage and mount a rw rootfs for dumping your dmesg and logcat logs to something more persistent than a tmpfs mounted to the initrd's filesystem. might have to grab some defconfig file from a blissROM repo instead. you could have a bootstrapping problem trying to get it to come up enough that you can grab proc/config.gz to try a new kernel flipping on any AMD stuff the blissROM/AOSPx86 configs left off. in theory some of the more framebuffery backends are a fairly standard interface that old hardware may be compatible with. look at all the hwcomposer/drm/drmfb kernel args in the syslinux/grub.cfg files and try them all, and maybe even try combinations not in the cfg files. ggroups 2019 post from mauro mentions AMD might work with minigbm stuff ripped out of chromeOS and some drmfb repo's readme mentions radeon support. ![]() It's possible but you'll have to try it yourself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |