[SOLVED] Edge-V: Domain: boot - Unexpected kernel boot parameter in Ubuntu server V20181115

Technical Support
1

I installed the SD/USB Ubuntu server image V20181115 on Edge-V and looking a little bit deeper into the boot kernel parameter with cat /proc/cmdline I found some weird entries:

sdfwupdate storagemedia=sd androidboot.mode=sd console=ttyFIQ0 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyFIQ0 init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00002000@0x00006000(misc),0x00008000@0x00008000(resource),0x0000C000@0x00010000(kernel),0x00010000@0x0001C000(boot),0x00010000@0x0002C000(recovery),0x00038000@0x0003C000(backup),0x00040000@0x00074000(cache),0x00600000@0x000B4000(system),0x00008000@0x006B4000(metadata),0x00000040@0x006BC000(verity_mode),0x00002000@0x006BC040(reserved),0x00000 
earlyprintk console=ttyFIQ0,1500000n8 console=tty0 rw root=UUID=<omitted> rootfstype=ext4 init=/sbin/init rootwait board_type=2 board_type_name=EdgeV androidboot.mode=emmc

My question is why there are a lot of androidboot keys inside the Ubuntu image and if it is possible how can I remove them?

Should I build a custom image with fenix?

2

Problem solved :smiley:

Apparently there is an Android factory image pre-installed that inserts the android boot kernel entries into the boot kernel parameter. I was not aware of it, sorry for that.

After creating a GPT partition on mmcblk1 with LVM2 and XFS and rebooting I got the usual boot kernel parameters, but one androidboot.mode survived.

sdfwupdate storagemedia=sd androidboot.mode=sd earlyprintk console=ttyFIQ0,1500000n8 console=tty0 rw root=UUID=<omitted> rootfstype=ext4 init=/sbin/init rootwait board_type=2 board_type_name=EdgeV
2 Likes