Bug#981586: Bullseye armhf kernel for Raspberry Pi 4b does not boot

2021-03-16 Thread João Ricardo Sares Teles de Matos
Analysis showed that it does reach init-top. But when usbcore and usbhid are loaded, peripherals like mouse and keyboard are not at all detected. When later usbhid, usb_storage and uas should be started, they do not work either and the root file device is not detected. What you wrote implies t

Bug#984691: /etc/kernel/postinst.d/z50-raspi-firmware: generated cmdline.txt root parameter broken when using Btrfs

2021-03-07 Thread João Ricardo Sares Teles de Matos
Package: raspi-firmware Version: 1.20210111+ds-2 Severity: important File: /etc/kernel/postinst.d/z50-raspi-firmware Dear Maintainer, (Note: a solution is provided below) When using a Btrfs filesystem as /, the root= parameter generated by the z50-raspi-firmware script is incorrect due to the

Bug#977694: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd

2021-03-06 Thread João Ricardo Sares Teles de Matos
I ran into this issue while trying to migrate the root filesystem into a btrfs subvolume on an USB hard drive. I'm also using a Raspberry Pi 4B. I followed Ryutaroh's advice of loading the reset_raspberrypi module, as follows: > echo reset_raspberrypi >/etc/initramfs-tools/modules > update-in

Bug#958748: lilv: liblilv-dev could be marked Multi-Arch: same

2020-04-24 Thread João Ricardo Sares Teles de Matos
Source: lilv Severity: important Dear Maintainer, The package tracker page for lilv notes that liblilv-dev could be marked Multi- Arch: same I'm encountered this because I'm trying to cross-build ffmpeg for i386 on amd64 and it requires livlilv-dev:i386 but I already had liblilv-dev:amd64 instal