Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#948712: raspi-firmware: Please add support for Raspebrry Pi4
231 views
Skip to first unread message
Christian Marillat
Jan 12, 2020, 9:10:03 AM1/12/20
to
Package: raspi-firmware
Version: 1.20190925-1
Severity: normal
Dear Maintainer,
I'm still unable to use a Debian kernel for my Rasebrry Pi 4 as this package
doesn't have support for Pi4 :
Setting up raspi-firmware (1.20190925-1) ...
Error: missing /boot/firmware, did you forget to mount it?
dpkg: error processing package raspi-firmware (--configure):
installed raspi-firmware package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
raspi-firmware
E: Sub-process /usr/bin/dpkg returned an error code (1)
Also note that Pi4 is able to boot from an ext4 partition and don't need /boo/firmware.
(Bug report done from an Intel machine)
Christian
-- System Information:
Debian Release: bullseye/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.93 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Version: 1.20190925-1
Severity: normal
Dear Maintainer,
I'm still unable to use a Debian kernel for my Rasebrry Pi 4 as this package
doesn't have support for Pi4 :
Setting up raspi-firmware (1.20190925-1) ...
Error: missing /boot/firmware, did you forget to mount it?
dpkg: error processing package raspi-firmware (--configure):
installed raspi-firmware package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
raspi-firmware
E: Sub-process /usr/bin/dpkg returned an error code (1)
Also note that Pi4 is able to boot from an ext4 partition and don't need /boo/firmware.
(Bug report done from an Intel machine)
Christian
-- System Information:
Debian Release: bullseye/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.93 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Gunnar Wolf
Mar 13, 2020, 9:40:03 PM3/13/20
to
Hello,
As far as I understand, the CPU in the RPi4 is a *completely*
different beast from the ones in the rest of the family. It seems it
will not require a binary firmware loader anymore!
Right now, it is not *yet* bootable using the stock Linux kernel, but
there are people working on its support. I have asked them to update
this bug when our kernel can boot on RPi4.
As far as I understand, the CPU in the RPi4 is a *completely*
different beast from the ones in the rest of the family. It seems it
will not require a binary firmware loader anymore!
Right now, it is not *yet* bootable using the stock Linux kernel, but
there are people working on its support. I have asked them to update
this bug when our kernel can boot on RPi4.
Christian Marillat
Jul 30, 2020, 12:00:03 AM7/30/20
to
On 29 juil. 2020 15:40, Lucas Nussbaum <lu...@debian.org> wrote:
> Version: 1.20200212-1
>
> Hi,
>
> raspi-firmware now supports RPI4. (I could not find the exact version
> where this was fixed, but at least it's fixed in the version above)
I'm not talking about files itself but how firmware are installed under
Debian.
With a rpi4 we don't need a /boot/firmware partition in vfat format as
rpi4 are able to boot from ext4.
Here is the original bug report :
,----
Christian
> Version: 1.20200212-1
>
> Hi,
>
> raspi-firmware now supports RPI4. (I could not find the exact version
> where this was fixed, but at least it's fixed in the version above)
I'm not talking about files itself but how firmware are installed under
Debian.
With a rpi4 we don't need a /boot/firmware partition in vfat format as
rpi4 are able to boot from ext4.
Here is the original bug report :
,----
| >> Setting up raspi-firmware (1.20190925-1) ...
| >> Error: missing /boot/firmware, did you forget to mount it?
| >> dpkg: error processing package raspi-firmware (--configure):
| >> installed raspi-firmware package post-installation script subprocess returned error exit status 1
| >> Errors were encountered while processing:
| >> raspi-firmware
| >> E: Sub-process /usr/bin/dpkg returned an error code (1)
| >>
| >> Also note that Pi4 is able to boot from an ext4 partition and don't need /boo/firmware.
`----
| >> Error: missing /boot/firmware, did you forget to mount it?
| >> dpkg: error processing package raspi-firmware (--configure):
| >> installed raspi-firmware package post-installation script subprocess returned error exit status 1
| >> Errors were encountered while processing:
| >> raspi-firmware
| >> E: Sub-process /usr/bin/dpkg returned an error code (1)
| >>
| >> Also note that Pi4 is able to boot from an ext4 partition and don't need /boo/firmware.
Christian
Lucas Nussbaum
Jul 30, 2020, 6:40:03 AM7/30/20
to
retitle 948712 raspi-firmware: no need for /boot/firmware in vfat with RPI4 (ext4 is supported)
thanks
Hi Christian,
On 30/07/20 at 00:14 +0200, Christian Marillat wrote:
> On 29 juil. 2020 15:40, Lucas Nussbaum <lu...@debian.org> wrote:
>
> > Version: 1.20200212-1
> >
> > Hi,
> >
> > raspi-firmware now supports RPI4. (I could not find the exact version
> > where this was fixed, but at least it's fixed in the version above)
>
> I'm not talking about files itself but how firmware are installed under
> Debian.
>
> With a rpi4 we don't need a /boot/firmware partition in vfat format as
> rpi4 are able to boot from ext4.
OK, I'm retitling the bug to clarify that it's not about RPI4 support
per se, but rather not using /boot/firmware, since the RPI4 can boot
from ext4.
Lucas
thanks
Hi Christian,
On 30/07/20 at 00:14 +0200, Christian Marillat wrote:
> On 29 juil. 2020 15:40, Lucas Nussbaum <lu...@debian.org> wrote:
>
> > Version: 1.20200212-1
> >
> > Hi,
> >
> > raspi-firmware now supports RPI4. (I could not find the exact version
> > where this was fixed, but at least it's fixed in the version above)
>
> I'm not talking about files itself but how firmware are installed under
> Debian.
>
> With a rpi4 we don't need a /boot/firmware partition in vfat format as
> rpi4 are able to boot from ext4.
per se, but rather not using /boot/firmware, since the RPI4 can boot
from ext4.
Lucas
Christian Marillat
Jul 30, 2020, 7:00:03 AM7/30/20
to
On 30 juil. 2020 12:36, Lucas Nussbaum <lu...@debian.org> wrote:
[...]
> OK, I'm retitling the bug to clarify that it's not about RPI4 support
> per se, but rather not using /boot/firmware, since the RPI4 can boot
> from ext4.
Thanks.
Christian
[...]
> OK, I'm retitling the bug to clarify that it's not about RPI4 support
> per se, but rather not using /boot/firmware, since the RPI4 can boot
> from ext4.
Christian
Elliott Mitchell
Nov 23, 2020, 10:40:04 PM11/23/20
to
reopen 948712
quit
There should be a rather obvious use case where absent /boot/firmware is
quite appropriate. For someone needing a copy of the firmware, but using
other tools to build the boot area.
Notably one might use raspi-firmware to retrieve start*.elf/fixup*.dat.
Then add u-boot-rpi for second stage bootloader. Next grub-efi-arm* for
third stage. Lastly flash-kernel to glue all the pieces together.
Not one of these requires the existance of /boot/firmware. In fact, not
one of these needs the installation of dosfstools.
Perhaps the raspi-firmware package should be split into pieces so as to
allow merely installing the actually required portions?
(raspi-firmware-bin which depends upon: raspi1-firmware-bin,
raspi2-firmware-bin, raspi3-firmware-bin, and raspi4-firmware-bin?)
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+...@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
quit
There should be a rather obvious use case where absent /boot/firmware is
quite appropriate. For someone needing a copy of the firmware, but using
other tools to build the boot area.
Notably one might use raspi-firmware to retrieve start*.elf/fixup*.dat.
Then add u-boot-rpi for second stage bootloader. Next grub-efi-arm* for
third stage. Lastly flash-kernel to glue all the pieces together.
Not one of these requires the existance of /boot/firmware. In fact, not
one of these needs the installation of dosfstools.
Perhaps the raspi-firmware package should be split into pieces so as to
allow merely installing the actually required portions?
(raspi-firmware-bin which depends upon: raspi1-firmware-bin,
raspi2-firmware-bin, raspi3-firmware-bin, and raspi4-firmware-bin?)
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+...@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Adam Borowski
Jul 11, 2022, 8:00:03 PM7/11/22
to
Pinebook Pro also wants this firmware, and it's definitely not a raspi,
and it doesn't have /boot/firmware either.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ What kind of a drug are "base" and "red pill"? I think acid is
⢿⡄⠘⠷⠚⠋⠀ LSD, which would make base... ? Judging from the behaviour of
⠈⠳⣄⠀⠀⠀⠀ those "based and redpilled", something nasty.
and it doesn't have /boot/firmware either.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ What kind of a drug are "base" and "red pill"? I think acid is
⢿⡄⠘⠷⠚⠋⠀ LSD, which would make base... ? Judging from the behaviour of
⠈⠳⣄⠀⠀⠀⠀ those "based and redpilled", something nasty.
Diederik de Haas
Jul 12, 2022, 6:50:04 AM7/12/22
to
On dinsdag 12 juli 2022 01:47:21 CEST Adam Borowski wrote:
> Pinebook Pro also wants this firmware, and it's definitely not a raspi,
> and it doesn't have /boot/firmware either.
Is this about the /lib/firmware/brcm/brcmfmac434* files?
> Pinebook Pro also wants this firmware, and it's definitely not a raspi,
> and it doesn't have /boot/firmware either.
IMO, that group of files shouldn't be part of this package, but be moved to
another firmware package, perhaps firmware-brcm80211?
Adam Borowski
Jul 12, 2022, 2:30:03 PM7/12/22
to
The idea of moving these files to another package seems good; steev proposed
firmware-linux, firmware-brcm80211 would be a more specific fit.
Both packages are maintained by debian...@l.d.o, could you folks
comment please?
Karl O. Pinc
Jul 12, 2022, 6:50:03 PM7/12/22
to
Hi,
In the FWIW catagory, I'm following this thread beacuse
installed Debian (11) on an RPI4B using the Debian installer.
Following the instructions:
https://wiki.debian.org/RaspberryPi4?action=show&redirect=InstallingDebianOn%2FRaspberryPi%2FRaspberry+Pi+4#Using_EFI_Firmware_and_the_regular_Debian_Installer
and following the link to:
https://forums.raspberrypi.com/viewtopic.php?t=282839
What I found, I think, was that /boot/firmware does not then exist on
the resulting system. I _believe_ I solved the issue by creating a
symlink. (Maybe to /boot/UEFI/firmware/ ??)
All this was some time ago and I will have to (eventually)
go back and look at my notes and report back. (I'd put off
reporting anything until I'd figured out something that worked.
By then I'd forgotten about this thread and was just reminded
by the recent emails.)
I'm not even 100% certain that the rpi firmware package
is relevant. But I think so, to get wireless working.
Here's hoping that this is useful feedback and not noise.
Regards,
Karl <k...@karlpinc.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
In the FWIW catagory, I'm following this thread beacuse
installed Debian (11) on an RPI4B using the Debian installer.
Following the instructions:
https://wiki.debian.org/RaspberryPi4?action=show&redirect=InstallingDebianOn%2FRaspberryPi%2FRaspberry+Pi+4#Using_EFI_Firmware_and_the_regular_Debian_Installer
and following the link to:
https://forums.raspberrypi.com/viewtopic.php?t=282839
What I found, I think, was that /boot/firmware does not then exist on
the resulting system. I _believe_ I solved the issue by creating a
symlink. (Maybe to /boot/UEFI/firmware/ ??)
All this was some time ago and I will have to (eventually)
go back and look at my notes and report back. (I'd put off
reporting anything until I'd figured out something that worked.
By then I'd forgotten about this thread and was just reminded
by the recent emails.)
I'm not even 100% certain that the rpi firmware package
is relevant. But I think so, to get wireless working.
Here's hoping that this is useful feedback and not noise.
Regards,
Karl <k...@karlpinc.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
Ben Hutchings
Jul 13, 2022, 4:10:04 AM7/13/22
to
On Tue, 2022-07-12 at 20:18 +0200, Adam Borowski wrote:
> On Tue, Jul 12, 2022 at 12:45:11PM +0200, Diederik de Haas wrote:
> > On dinsdag 12 juli 2022 01:47:21 CEST Adam Borowski wrote:
> > > Pinebook Pro also wants this firmware, and it's definitely not a raspi,
> > > and it doesn't have /boot/firmware either.
> >
> > Is this about the /lib/firmware/brcm/brcmfmac434* files?
> >
> > IMO, that group of files shouldn't be part of this package, but be moved to
> > another firmware package, perhaps firmware-brcm80211?
>
> Yeah, that.
>
> The idea of moving these files to another package seems good; steev proposed
> firmware-linux, firmware-brcm80211 would be a more specific fit.
> Both packages are maintained by debian...@l.d.o, could you folks
> comment please?
So long as those files are in linux-firmware.git, it should be fine to
> On Tue, Jul 12, 2022 at 12:45:11PM +0200, Diederik de Haas wrote:
> > On dinsdag 12 juli 2022 01:47:21 CEST Adam Borowski wrote:
> > > Pinebook Pro also wants this firmware, and it's definitely not a raspi,
> > > and it doesn't have /boot/firmware either.
> >
> > Is this about the /lib/firmware/brcm/brcmfmac434* files?
> >
> > IMO, that group of files shouldn't be part of this package, but be moved to
> > another firmware package, perhaps firmware-brcm80211?
>
> Yeah, that.
>
> The idea of moving these files to another package seems good; steev proposed
> firmware-linux, firmware-brcm80211 would be a more specific fit.
> Both packages are maintained by debian...@l.d.o, could you folks
> comment please?
ship them in firmware-brcm80211. If they aren't, they should be added
there first.
Ben.
--
Ben Hutchings
friends: People who know you well, but like you anyway.
Diederik de Haas
Jul 13, 2022, 1:10:03 PM7/13/22
to
On woensdag 13 juli 2022 09:58:29 CEST Ben Hutchings wrote:
> > > Is this about the /lib/firmware/brcm/brcmfmac434* files?
>
> > > Is this about the /lib/firmware/brcm/brcmfmac434* files?
>
> So long as those files are in linux-firmware.git, it should be fine to
> ship them in firmware-brcm80211. If they aren't, they should be added
> there first.
https://github.com/raspberrypi/linux/issues/4723 seems relevant.
> ship them in firmware-brcm80211. If they aren't, they should be added
> there first.
I didn't dive into it too much, but AFAICT you need to convince the RPi folks
to upstream those files.
Good luck with that!
0 new messages