Created attachment 2740 [details]
missing firmware errors on cauldron

I'll check first if we have them already and license

CC: (none) => ennael1

I will do this before end of this week

Anne, any news ?

CC: (none) => makowski.mageia

In progress, half of the list done for now

Created attachment 3661 [details]
updated list as of 3.8.3-desktop-2.mga3

I rerun bug #5348 check.pl: there're new missing firmwares.

This is only for modules included in main kernel (x86_64).
There might be a couple drivers only enabled on 32bit or some dkms modules that requires firmwares too

for ueagle, kernel-firmware-nonfree provides some "foobar" files whereas driver looks for "foobar.v2"

See first shot here: https://wiki.mageia.org/en/Firmwares_review

I see b43 : Broadcom Wifi files listed that we can't provide as they are extracted with b43-fwcutter...

CC: (none) => lists.jjorge

Many of them in the list are very old one. This list needs also some work as many kernel modules lists several firmwares they can use, and then they use the one they find.

Decreasing for now the priority

Priority: release_blocker => High

This has priority high and severity critical, bumping it so that it doesn't stay forgotten.

Target Milestone: Mageia 3 => ---
CC: (none) => remi

Created attachment 6399 [details]
updated checker

Created attachment 6400 [details]
updated list as of 3.19.4-desktop-2.mga5

There's now less missing firmware but still quite some

Attachment 2740 is obsolete: 0 => 1
Attachment 3661 is obsolete: 0 => 1

Should this be made release blocker?

I don't think so : there are many false positives, provided by other packages. I mean for zd12xx, we have a rpm with this files, and I have such hardware that works, does the script check for them?

The same for broadcom files.

(In reply to Samuel VERSCHELDE from comment #13)
> Should this be made release blocker?

Heh, we cant block on stuff we have no control over... there is a lot of firmwares out there that has no valid "re-distribution license" for linux distros...

I know one can extract lots of firmwares from windows drivers, but we cant officially redistribute those...

for broadcom, its only now this ~last year they have been pushing firmwares to linux-firmware repo

Same goes for atheros... We are still waiting for a some release that was promised last year and so on...

(In reply to José Jorge from comment #14)
> I don't think so : there are many false positives, provided by other
> packages.

No there's not.

>I mean for zd12xx, we have a rpm with this files, and I have such
> hardware that works, does the script check for them?

No we don't have those firmwares packaged in mga
 
> The same for broadcom files.

No.

(In reply to Thierry Vignaud from comment #16)
> >I mean for zd12xx, we have a rpm with this files, and I have such
> > hardware that works, does the script check for them?
> 
Sorry for the noise, we have zd1211-firmware but nothing for zd1201.
The only firmware I have found in SF.NET is as tmb said : no license.

Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Hi,
This is High priority bug for a good reason.

Making Mageia even better than ever is best direction.
In order to do right thing, this bug should be examined and fixed as soon as possible.

Packagers, please make the status to Assigned when you are working on this.
Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it.

On October 1st 2020, we will drop priority to normal.

Status ?

I think this is an old Bug that has been already fixed?

CC: (none) => ouaurelien, tmb

we already ship the firmwares we are allowed to,

Resolution: (none) => FIXED
Status: NEW => RESOLVED