Re: Bug#1033498: installation-reports: Missing FW files not detected on USB stick
Am Sonntag, 26. März 2023, 12:23:48 CEST schrieben Sie:
> [Resent to OP, please send any reply to debian-boot@lists.debian.org]
>
> Hello,
>
> On 26/03/2023 at 10:52, Rainer Dorsch wrote:
> > │ The missing firmware files are:
> > │
> > │ brcm/brcmfmac4330-sdio.solidrun,cubox-i-q.bin
> > │
> > │ brcm/brcmfmac4330-sdio.solidrun,cubox-i-q.bin
> > │
> > │ brcm/brcmfmac4330-sdio.bin brcm/brcmfmac4330-sdio.bin
> > │
>
> (...)
>
> > I copied all files from
> >
> > https://github.com/LibreELEC/brcmfmac_sdio-firmware
> >
> > on a USB-stick (ext3 formated, with vfat I got an error, probably the
> > filenames were not compatible). I selected <Yes> but the same box showed
> > up again and I assume no FW files were found (but it did not say so).
>
> At that stage the installer may not support any filesystem other than
> FAT and ISO 9660. Also the current search algorithm for loose firmware
> files is very poor.
>
> What error did you have with vfat ? I can successfully create files with
> these names on a vfat filesystem so I doubt filenames are the culprit.
Many thanks for your quick response. I looked in it in more detail:
There are many symlinks in the repo and I used Dolphin (KDE filemanager) to
copy the data. It complained and pointed to a potential permission issue, but
reading the error message more carefully reveals that it is not a permission
issue, but it could not copy symlinks.
If I do a cp on bash, the files are copied as (many identical) copies, i.e.
symlinks are not preserved.
I have not yet tested if that resolves the FW not found issue though. It would
have helped me, if the installed would be a little bit more verbose and
reported something like
No non-free FW files found in these directories:
<dir1>
<dir2>
Then it would have become more obvious that the installer cannot see the ext3
formatted USB stick.
Thanks
Rainer
--
Rainer Dorsch
http://bokomoko.de/
Reply to: