Bug#980205: #980205 installation missing "non free" drivers.

2021-03-04 Thread maximilian attems
On Thu, Mar 04, 2021 at 10:08:39AM -0800, Dave Dyer wrote:
> 
> I no longer have the (damaged and useless) installation attempt
> that led to this report.   I recall that when I succeeded in
> supplying brcmfmac43340-sdio.bin, the next installation attempt
> presented the same type of error message, asking for brcmfmac43340-sdio.txt

missing brcmfmac43340-sdio.txt depends on the device, see for example
https://bugs.debian.org/982579

-- snipp
> [   10.534664] brcmfmac mmc2:0001:1: Direct firmware load for  
> brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt failed with error -2
> [   10.551207] brcmfmac mmc2:0001:1: firmware: failed to load 
> brcm/brcmfmac43430-sdio.txt (-2)
--

if you have still the device around let us know, otherwise
the bug report will closed.

 
> I found a file with that name on github, and there was some evidence
> that it worked.  I believe it's attacked to the bug report thread.

I relooked for it but didn't see the error log message.
thank you for your prompt reply.

-- 
maks


signature.asc
Description: PGP signature


Bug#980205: #980205 installation missing "non free" drivers.

2021-03-04 Thread Dave Dyer


I no longer have the (damaged and useless) installation attempt
that led to this report.   I recall that when I succeeded in
supplying brcmfmac43340-sdio.bin, the next installation attempt
presented the same type of error message, asking for brcmfmac43340-sdio.txt

I found a file with that name on github, and there was some evidence
that it worked.  I believe it's attacked to the bug report thread.

--

At 06:10 AM 3/4/2021, maximilian attems wrote:
>tags 980205 moreinfo
>thanks
>
>
>> Yes.   brcm/brcmfmac43340-sdio.bin is not currently part of the package
>> either, and I think there's no logic to copy .txt files even if they
>> are present.
>
>The file you mentioned is the ancient firmware that got updated with
>the cypress one fixing amongst other things (CVE-2019-15126):
>
> Link: brcm/brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin
>
>This symlink is inside of firmware-brcm80211_20210208-3_all.deb
>(shipped in unstable and soon in testing).
>
>
>Now the open question is which configuration file where you missing,
>could you please post the error message of that?
>Without the filename/path of the needed config this report will not
>help to improve the firmware packages.
>
>
>thank you + kind regards
>
>-- 
>maks



Bug#980205: #980205 installation missing "non free" drivers.

2021-03-04 Thread maximilian attems
tags 980205 moreinfo
thanks


> Yes.   brcm/brcmfmac43340-sdio.bin is not currently part of the package
> either, and I think there's no logic to copy .txt files even if they
> are present.

The file you mentioned is the ancient firmware that got updated with
the cypress one fixing amongst other things (CVE-2019-15126):

 Link: brcm/brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin

This symlink is inside of firmware-brcm80211_20210208-3_all.deb
(shipped in unstable and soon in testing).


Now the open question is which configuration file where you missing,
could you please post the error message of that?
Without the filename/path of the needed config this report will not
help to improve the firmware packages.


thank you + kind regards

-- 
maks



Bug#980205: #980205 installation missing "non free" drivers.

2021-01-20 Thread Holger Wansing
Control: reassign -1 firmware-nonfree
Control: retitle -1 firmware: missing txt file for brcm/brcmfmac43340-sdio.bin

Dave Dyer  wrote:
> At 05:40 AM 1/18/2021, Holger Wansing wrote:
> >> 3) in my particular case, the driver is brcm/brcmfmac43340-sdio.bin, which
> >> *also* requires a text file, brcm/brcmfmac43340-sdio.txt.  I know this 
> >> because
> >> I figured out case 2B and got the installer to accept the .bin; it then
> >> it mentions the need for the .txt file.  (Again, thanks, it would have
> >> been impossible to proceed without this key information).  However,
> >> there's apparently no way to get the installer to accept the .txt
> >> file in the same way that it finds the .bin.
> >
> >Hmm, looking into the package firmware-brcm80211
> >(https://packages.debian.org/buster/firmware-brcm80211)
> >there is no such txt file there.
> >So I wonder where you found such file?
> 
> Github + Google.  And the file I found works.

So this txt file will need to be added to firmware-brcm80211 package, too?

Re-assigning there.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#980205: #980205 installation missing "non free" drivers.

2021-01-20 Thread Dave Dyer


Yes.   brcm/brcmfmac43340-sdio.bin is not currently part of the package
either, and I think there's no logic to copy .txt files even if they
are present.

At 04:39 PM 1/20/2021, Holger Wansing wrote:
>Control: reassign -1 firmware-nonfree
>Control: retitle -1 firmware: missing txt file for brcm/brcmfmac43340-sdio.bin
>
>Dave Dyer  wrote:
>> At 05:40 AM 1/18/2021, Holger Wansing wrote:
>> >> 3) in my particular case, the driver is brcm/brcmfmac43340-sdio.bin, which
>> >> *also* requires a text file, brcm/brcmfmac43340-sdio.txt.  I know this 
>> >> because
>> >> I figured out case 2B and got the installer to accept the .bin; it then
>> >> it mentions the need for the .txt file.  (Again, thanks, it would have
>> >> been impossible to proceed without this key information).  However,
>> >> there's apparently no way to get the installer to accept the .txt
>> >> file in the same way that it finds the .bin.
>> >
>> >Hmm, looking into the package firmware-brcm80211
>> >(https://packages.debian.org/buster/firmware-brcm80211)
>> >there is no such txt file there.
>> >So I wonder where you found such file?
>> 
>> Github + Google.  And the file I found works.
>
>So this txt file will need to be added to firmware-brcm80211 package, too?
>
>Re-assigning there.
>
>
>Holger
>
>
>-- 
>Holger Wansing 
>PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#980205: #980205 installation missing "non free" drivers.

2021-01-18 Thread Dave Dyer
At 05:40 AM 1/18/2021, Holger Wansing wrote:


>Dave Dyer  wrote (16 Jan 2021 04:09:02 UTC):
>> Installing on an old x86 cpu which requires "non free" drivers, the
>> installer correctly quotes the needed driver's name.  Bravo. but...
>> 
>> 1) it suggests adding removable media, which is basically impossible
>> in the context of the installer running from a memory stick
>
>Why? You can simply plug in a second USB stick to the PC.

My old device had only 1 usable usb port, and plug/replug didn't
work.  I eventually did try doing the installation with a usb
hub.   I don't think that worked either, because the message
still referred to the .bin file.   AFAIK nothing worked except
installing the driver in the .img 


>> 2) it doesn't tell you in what path on the media to place the driver.
>> I still don't know what path would be appropriate if I could figure out how
>> and where to mount an additional memory stick where it would be seen,
>> but if (instead) I go back and insert the file on the installer stick
>> memory stick, it apparently has to go in /firmware
>
>That's documented in the installation-guide, see
>https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s04.html

In the cellar, past the sign that says "beware of the leopard"

You could at least put that link into the message that
included the name of the driver.


>> 3) in my particular case, the driver is brcm/brcmfmac43340-sdio.bin, which
>> *also* requires a text file, brcm/brcmfmac43340-sdio.txt.  I know this 
>> because
>> I figured out case 2B and got the installer to accept the .bin; it then
>> it mentions the need for the .txt file.  (Again, thanks, it would have
>> been impossible to proceed without this key information).  However,
>> there's apparently no way to get the installer to accept the .txt
>> file in the same way that it finds the .bin.
>
>Hmm, looking into the package firmware-brcm80211
>(https://packages.debian.org/buster/firmware-brcm80211)
>there is no such txt file there.
>So I wonder where you found such file?

Github + Google.  And the file I found works.


>> 4) a workaround, if you can complete the installation without
>> the network working, is to copy both files into /lib/firmware/ and
>> magically the network will work.
>> 
>> --
>> 
>> This whole process is very user unfriendly - especially for for 
>> the case of a novice user (I'm not) trying to install linux for
>> the first time.  Rather than trying to put the whole book of 
>> possibilities in the installer, how about if such messages were
>> accompanied by links pointing to detailed explanations.
>
>As already mentioned above, reading the installation-guide might have 
>helped.

Might have.  And a helpful link in the messages from the installer
might have helped.

The missing .txt (inability to find) is definitely a bug, the rest
is a matter of making the process better than it is.

Thanks for your attention -  



Bug#980205: #980205 installation missing "non free" drivers.

2021-01-18 Thread Holger Wansing



Dave Dyer  wrote (16 Jan 2021 04:09:02 UTC):
> Installing on an old x86 cpu which requires "non free" drivers, the
> installer correctly quotes the needed driver's name.  Bravo. but...
> 
> 1) it suggests adding removable media, which is basically impossible
> in the context of the installer running from a memory stick

Why? You can simply plug in a second USB stick to the PC.

> 2) it doesn't tell you in what path on the media to place the driver.
> I still don't know what path would be appropriate if I could figure out how
> and where to mount an additional memory stick where it would be seen,
> but if (instead) I go back and insert the file on the installer stick
> memory stick, it apparently has to go in /firmware

That's documented in the installation-guide, see
https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s04.html

> 3) in my particular case, the driver is brcm/brcmfmac43340-sdio.bin, which
> *also* requires a text file, brcm/brcmfmac43340-sdio.txt.  I know this because
> I figured out case 2B and got the installer to accept the .bin; it then
> it mentions the need for the .txt file.  (Again, thanks, it would have
> been impossible to proceed without this key information).  However,
> there's apparently no way to get the installer to accept the .txt
> file in the same way that it finds the .bin.

Hmm, looking into the package firmware-brcm80211
(https://packages.debian.org/buster/firmware-brcm80211)
there is no such txt file there.
So I wonder where you found such file?

> 4) a workaround, if you can complete the installation without
> the network working, is to copy both files into /lib/firmware/ and
> magically the network will work.
> 
> --
> 
> This whole process is very user unfriendly - especially for for 
> the case of a novice user (I'm not) trying to install linux for
> the first time.  Rather than trying to put the whole book of 
> possibilities in the installer, how about if such messages were
> accompanied by links pointing to detailed explanations.

As already mentioned above, reading the installation-guide might have 
helped.


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076