Public bug reported:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
- source: boot-assets/
target: /
pi4-usb-writable:
schema: mbr
structure:
- name: writable
type: 83
filesystem: ext4
filesystem-label: writable
size: 650M
role: system-data
this creates two separate img files for a Pi image ... one for SD to
hold the boot files, one for USB that carries the rootfs ...
sadly our kernel will then not find the writable partition because it
lacks support for usb disks (usb-storage seems to be there but not
sufficient)
adding the following to a re-built kernel snap makes everything work
(verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys)
- CONFIG_ENCLOSURE_SERVICES=y
- CONFIG_SCSI_SAS_ATTRS=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_UAS=y
can we please have these either built into the kernel or added to the
initrd as modules ?
** Affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: Confirmed
** Description changed:
when using a gadget.yaml like:
volumes:
- pi4-system-boot:
- schema: mbr
- bootloader: u-boot
- structure:
- - type: 0C
- filesystem: vfat
- filesystem-label: system-boot
- size: 512M
- content:
- - source: boot-assets/
- target: /
- pi4-usb-writable:
- schema: mbr
- structure:
- - name: writable
- type: 83
- filesystem: ext4
- filesystem-label: writable
- size: 650M
- role: system-data
+ pi4-system-boot:
+ schema: mbr
+ bootloader: u-boot
+ structure:
+ - type: 0C
+ filesystem: vfat
+ filesystem-label: system-boot
+ size: 512M
+ content:
+ - source: boot-assets/
+ target: /
+ pi4-usb-writable:
+ schema: mbr
+ structure:
+ - name: writable
+ type: 83
+ filesystem: ext4
+ filesystem-label: writable
+ size: 650M
+ role: system-data
-
- this creates two separate img files for a Pi image ... one for SD to hold the
boot files, one for USB that carries the rootfs ...
+ this creates two separate img files for a Pi image ... one for SD to
+ hold the boot files, one for USB that carries the rootfs ...
sadly our kernel will then not find the writable partition because it
lacks support for usb disks (usb-storage seems to be there but not
sufficient)
adding the following to a re-built kernel makes everything work
(verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys)
- - CONFIG_ENCLOSURE_SERVICES=y
- - CONFIG_SCSI_SAS_ATTRS=y
- - CONFIG_USB_STORAGE=y
- - CONFIG_USB_UAS=y
+ - CONFIG_ENCLOSURE_SERVICES=y
+ - CONFIG_SCSI_SAS_ATTRS=y
+ - CONFIG_USB_STORAGE=y
+ - CONFIG_USB_UAS=y
- can we please have these aither built into the kernel or added to the
+ can we please have these either built into the kernel or added to the
initrd as modules ?
** Summary changed:
- USB support missing in initrd makes booting with writable on USB impossible
+ USB support missing in initrd makes booting core with writable on USB
impossible
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881623
Title:
USB support missing in initrd makes booting core with writable on USB
impossible
Status in linux-raspi2 package in Ubuntu:
Confirmed
Bug description:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
- source: boot-assets/
target: /
pi4-usb-writable:
schema: mbr
structure:
- name: writable
type: 83
filesystem: ext4
filesystem-label: writable
size: 650M
role: system-data
this creates two separate img files for a Pi image ... one for SD to
hold the boot files, one for USB that carries the rootfs ...
sadly our kernel will then not find the writable partition because it
lacks support for usb disks (usb-storage seems to be there but not
sufficient)
adding the following to a re-built kernel snap makes everything work
(verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys)
- CONFIG_ENCLOSURE_SERVICES=y
- CONFIG_SCSI_SAS_ATTRS=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_UAS=y
can we please have these either built into the kernel or added to the
initrd as modules ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881623/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
