device-google-oak: disable extra initfs

With this commented out, /boot is mount-able again.

Details in this issue: #3279 (comment 454237)

added 1 commit

• 20350d9f - device-google-oak: disable extra initfs

Compare with previous version

added 1 commit

• 6980373c - device-google-oak: disable extra initfs

Compare with previous version

mentioned in issue #3279 (closed)

changed the description

approved this merge request

added chromeos initramfs type::fix labels

requested review from @craftyguy

@adamthiede thanks for the patch, but I don't think we actually want to do this. Does this chromebook have a small bootloader boot partition (32MB?), so we need to use initramfs-extra to make sure that the kernel+initramfs always fit?

The first partition is indeed 32MB.

$ lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINTS
mtdblock0     31:0    0    4M  0 disk  
mmcblk0      179:0    0 58.2G  0 disk  
├─mmcblk0p1  179:1    0   32M  0 part  
├─mmcblk0p2  179:2    0  256M  0 part  /boot
└─mmcblk0p3  179:3    0   58G  0 part  
  └─root     253:0    0 57.9G  0 crypt /.snapshots
                                       /var
                                       /srv
                                       /root
                                       /home
                                       /
mmcblk0boot0 179:32   0    4M  1 disk  
mmcblk0boot1 179:64   0    4M  1 disk  

The device boots either way, with this enabled or disabled, it's just that it doesn't mount boot properly if it's enabled.

yeah this is a workaround for '/boot isn't mounted', but I think we should figure out why it's not mounting and fix that problem and not work around it like this since I think it can cause problems later if kernel+initramfs are too big (this is happening on x64cros devices right now...)

Also it's possible this "/boot not automounted" problem affects other devices too, and we don't want to get rid of initramfs-extra on everything (some really need it)

mentioned in merge request !5751 (merged)

closed