Closed smoser closed 4 years ago
They are built-in to kernel:
config-4.4.0-148-generic-aarch64:CONFIG_VIRTIO_BLK=y config-4.4.0-148-generic-x86_64:CONFIG_VIRTIO_BLK=y config-4.4.0-148-generic-aarch64:CONFIG_VIRTIO_NET=y config-4.4.0-148-generic-x86_64:CONFIG_VIRTIO_NET=y config-4.4.0-148-generic-aarch64:CONFIG_VIRTIO_PCI=y config-4.4.0-148-generic-x86_64:CONFIG_VIRTIO_PCI=y config-4.4.0-148-generic-aarch64:CONFIG_VFAT_FS=y config-4.4.0-148-generic-x86_64:CONFIG_VFAT_FS=y config-4.4.0-148-generic-aarch64:CONFIG_NLS_CODEPAGE_437=y config-4.4.0-148-generic-x86_64:CONFIG_NLS_CODEPAGE_437=y config-4.4.0-148-generic-aarch64:CONFIG_NLS_ISO8859_1=y config-4.4.0-148-generic-x86_64:CONFIG_NLS_ISO8859_1=y
sr_mod: config-4.4.0-148-generic-aarch64:CONFIG_BLK_DEV_SR=y config-4.4.0-148-generic-x86_64:CONFIG_BLK_DEV_SR=y
sg: config-4.4.0-148-generic-aarch64:CONFIG_CHR_DEV_SG=y config-4.4.0-148-generic-x86_64:CONFIG_CHR_DEV_SG=y
cdrom is built-in due to sr_mod being built-in
qemu_fw_cfg: no idea where it could get from.
modprobe: module cdrom not found in modules.dep
Yeah... ideally the boot wouldn't show these messages. So lets treat this as "don't try to modprobe modules that were known in the build to be built-in".
not sure immediately how i'd do that.
Maybe modprobe should just be muted. We know which kernel goes into image and we know that kernel parts we want are present.
We are doing a boot test of images in c-i now (thanks hrw). Looking at logs from a recent master build (https://travis-ci.com/cirros-dev/cirros/builds/145698266) we see missing modules:
I'm no sure how long logs live on travis, so these links might go missing. Here is a section in the boot of 4.4.0-148.174.
I'm guessing that
grab-kernels
is not getting all the kernel packages. From Ubuntu's kernel package page (linux), we see the following packages for current 4.4. I've removed 'udeb' and dbgsym packages.