Your message dated Wed, 11 Sep 2024 21:51:14 +0200
with message-id
and subject line Re: firmware-nonfree: [i915] With 20240709-2, the external
monitors randomly blank for 2-3 seconds (regression)
has caused the Debian Bug report #1080492,
regarding firmware-nonfree: [i915] With 20240709-2, the
Source: firmware-nonfree
Version: 20240709-2
Severity: important
First, some context: I have a Dell laptop with 2 external monitors
connected via a dock. With 6.8+ Linux kernels, one of the external
monitors randomly blanks for 2-3 seconds (no such issue with earlier
kernels); not always the same
On Mon, 29 Jul 2024 14:47:57 +0200 =?UTF-8?Q?Dylan_A=C3=AFssi?=
wrote:
As we now have a new version of firmware-nonfree
in deb/testing, is there a backport planned?
I'm willing to prepare the package if no one is against it.
I'm supporting this request. My new notebook needs
firmware-nonfree 20240709-1 is marked for autoremoval from testing on 2024-08-31
It (build-)depends on packages with these RC bugs:
1074798: a56: ftbfs with GCC-14
https://bugs.debian.org/1074798
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master
Hello,
As we now have a new version of firmware-nonfree
in deb/testing, is there a backport planned?
I'm willing to prepare the package if no one is against it.
Best regards,
Dylan
firmware-nonfree 20240610-1 is marked for autoremoval from testing on 2024-08-23
It (build-)depends on packages with these RC bugs:
1074798: a56: ftbfs with GCC-14
https://bugs.debian.org/1074798
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master
Processing commands for cont...@bugs.debian.org:
> affects 1076539 + src:firmware-nonfree
Bug #1076539 [src:initramfs-tools] plymouth: Updating plymouth fails with "No
space left on device"
Added indication that 1076539 affects src:firmware-nonfree
>
End of message, stopping processing here.
Ple
Your message dated Mon, 15 Jul 2024 20:45:46 +
with message-id
and subject line Bug#1064229: fixed in firmware-nonfree 20240610-1
has caused the Debian Bug report #1064229,
regarding firmware-nonfree: CVE-2023-35061
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 15 Jul 2024 20:45:46 +
with message-id
and subject line Bug#1051892: fixed in firmware-nonfree 20240610-1
has caused the Debian Bug report #1051892,
regarding firmware-nonfree: CVE-2022-27635 CVE-2022-36351 CVE-2022-38076
CVE-2022-40964 CVE-2022-46329
to be marked as
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1057040 + pending
Bug
On Monday, 1 July 2024 09:17:43 CEST Diederik de Haas wrote:
> On zondag 30 juni 2024 22:33:03 CEST you wrote:
> > I don't know the details anymore, but I recently ran into an interesting
> > problem though as the 'physical' firmware file was put in the atheros
> > packages instead of a link to the
On zondag 30 juni 2024 22:33:03 CEST you wrote:
> I don't know the details anymore, but I recently ran into an interesting
> problem though as the 'physical' firmware file was put in the atheros
> packages instead of a link to the place of the qcom-soc package. Could be a
> PEBKAC issue, but you mi
Your message dated Sun, 30 Jun 2024 22:21:09 +0200
with message-id <74779691.Lv8qgiQ7IQ@bagend>
and subject line Re: firmware-nonfree: Important changes coming up with
upstream version 20230919
has caused the Debian Bug report #1061321,
regarding firmware-nonfree: Important changes coming u
On Mon, 22 Jan 2024 15:42:48 +0100 Diederik de Haas
wrote:
> Source: firmware-nonfree
> Version: 20230625-2
> Severity: important
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I'm currently working on an update for upstream version 20230919,
based
>
Control: retitle -1 firmware-nonfree: CVE-2023-35061
Hi Ben,
On Sun, Jun 30, 2024 at 08:42:32PM +0200, Ben Hutchings wrote:
> On Sun, 18 Feb 2024 20:45:07 +0100 Salvatore Bonaccorso
> wrote:
> > Source: firmware-nonfree
> > Version: 20230625-2
> > Severity: important
>
Processing control commands:
> retitle -1 firmware-nonfree: CVE-2023-35061
Bug #1064229 [src:firmware-nonfree] firmware-nonfree: CVE-2023-35061
CVE-2023-34983 CVE-2023-33875 CVE-2023-32651 CVE-2023-32644 CVE-2023-32642
CVE-2023-28720 CVE-2023-28374 CVE-2023-26586 CVE-2023-25951
Changed
On Sun, 18 Feb 2024 20:45:07 +0100 Salvatore Bonaccorso
wrote:
> Source: firmware-nonfree
> Version: 20230625-2
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
> Hi,
>
> The following vulnerabilities were pub
Your message dated Sun, 30 Jun 2024 14:45:45 +
with message-id
and subject line Bug#1035505: fixed in firmware-nonfree 20230625-3~exp3
has caused the Debian Bug report #1035505,
regarding firmware-nonfree: debian/bin/gencontrol.py fails on spaces and
backslashes
to be marked as done.
This
firmware-nonfree 20230625-2 is marked for autoremoval from testing on 2024-07-05
It (build-)depends on packages with these RC bugs:
890601: firmware-linux-free: firmware-linux-free uses prebuilt blobs instead of
building from source
https://bugs.debian.org/890601
This mail is generated by
Source: firmware-nonfree
Version: 20230625-2
Severity: wishlist
Tags: patch
This is the same bug as #1069571 (firmware-linux-free). The
update-initramfs trigger is activated procedurally and in postinst only.
Hence, removing a firmware package does not update the initramfs. I
propose activating
Source: firmware-nonfree
Version: 20230210-5
Severity: wishlist
Tags: patch
Hello.
The source package builds with the attached changes (2 to 10), and
debdiff finds no difference in the resulting debs for
firmware-{linux,linux-nonfree,qcom-media} (testing do_extra in gencontrol.py)
firmware
On maandag 22 januari 2024 15:42:48 CET you wrote:
> I'm currently working on an update for upstream version 20230919, based
> upon MR86 (Release 20230804) [1], which itself is based upon MR85
> (Update to 20230625) [2] and I'm running into some major issues:
>
> 1) Salsa's CI now always fails as
Source: firmware-nonfree
Version: 20230625-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerabilities were published for firmware-nonfree.
They are addressed in the linux-firmware/20231211 upstream version.
CVE-2023
Source: firmware-nonfree
Version: 20230625-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for firmware-nonfree.
CVE-2023-4969[0]:
| A GPU kernel can read sensitive data from another GPU kernel
://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/87
> 3) Upstream commit a0142c57045701b7557c3060af5c4246c420e4d8 titled
>"ath10k/WCN3990: move wlanmdsp to qcom/sdm845" would mean moving
>entries from ``debian/config/atheros`` to ``debian/config/qcom-soc`
Source: firmware-nonfree
Version: 20230625-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm currently working on an update for upstream version 20230919, based
upon MR86 (Release 20230804) [1], which itself is based upon MR85
(Update to 20230625) [2] and I'm ru
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1058991 + pending
Bug
#
# bts-link upstream status pull for source package firmware-nonfree
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #1057656 (http
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1040185 + pending
Bug
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1043099 + pending
Bug
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1053856 + pending
Bug
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1057039 + pending
Bu
Source: firmware-nonfree
Followup-For: Bug #1035505
X-Debbugs-Cc: didi.deb...@cknow.org, 1029...@bugs.debian.org, k...@debian.org
Control: forwarded -1
https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/65
Control: tags -1 patch
Please find an updated attempt to handle spaces
Processing control commands:
> forwarded -1
> https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/65
Bug #1035505 [src:firmware-nonfree] firmware-nonfree: debian/bin/gencontrol.py
fails on spaces and backslashes
Set Bug forwarded-to-address to
'https://salsa
Source: firmware-nonfree
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security
Hi,
The following vulnerabilities were published for firmware-nonfree, all
fixed in linux-firmware/20230804 :
CVE-2022-27635[0]:
| Improper access control for some Intel(R) PROSet/Wireless WiFi
#
# bts-link upstream status pull for source package firmware-nonfree
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #1042818 (http
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1040012 + pending
Bug #10
ch at:
https://salsa.debian.org/diederik/firmware-nonfree/-/merge_requests/1
Cheers,
James
Cyril Brulebois (2023-05-04):
> The problem is the next stage, distributing the relevant files into the
> appropriate binary packages. That part is controlled by the defines, and
> that's what needs to be adjusted (file format and/or how it's used).
>
> A quick look suggests files_orig isn't set
at I created:
https://salsa.debian.org/diederik/firmware-nonfree/-/commits/add-rpi-symlinks/
And this is the Salsa CI job (extract source) that failed:
https://salsa.debian.org/diederik/firmware-nonfree/-/jobs/4187253
At the end of the output I found the `debian/rules debian/control-real`
comm
(debian/20230210-5), you'll find need to unpack the upstream tarball:
tar xf ../firmware-nonfree_20230210.orig.tar.xz --strip 1
Then generate stuff:
(unstable-amd64-devel)kibi@tokyo:~/debian-kernel/firmware-nonfree.git
(sid)$ ./debian/rules debian/control
mkdir -p debian/build
prin
Source: firmware-nonfree
Followup-For: Bug #1035505
X-Debbugs-Cc: didi.deb...@cknow.org, 1029...@bugs.debian.org, k...@debian.org
Looks like a silently-handled exception here:
https://salsa.debian.org/kernel-team/firmware-nonfree/-/blob/9f189a7f81d40694ee71a36906de5637dada950f/debian/bin
Source: firmware-nonfree
Followup-For: Bug #1035505
X-Debbugs-Cc: didi.deb...@cknow.org, 1029...@bugs.debian.org, k...@debian.org
Hey Diederik,
I think that the edits to 'debian/config/brcm80211/defines' may be the cause
of the space-escaping issue (noticed that in your fork on Salsa).
Source: firmware-nonfree
Version: 20230210-5
Severity: normal
X-Debbugs-Cc: 1029...@bugs.debian.org, k...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
While trying to prepare a MR to fix bug #1029843, I encountered a
failure which seems to be `gencontrol.py`'s inability to
Hi,
On Mon, May 01, 2023 at 06:36:01PM +0200, Cyril Brulebois wrote:
> Hi,
>
> Salvatore Bonaccorso (2023-04-30):
> > [ Other info ]
> > As beeing the firmware-nonfree package, I'm explicitly CC'ing as well
> > Cyril on this pre-approval request.
>
&
Hi,
Salvatore Bonaccorso (2023-04-30):
> [ Other info ]
> As beeing the firmware-nonfree package, I'm explicitly CC'ing as well
> Cyril on this pre-approval request.
Thanks for that.
> Furthermore the attached debdiff still contains the UNRELEASED
> changelog entry, w
-nonfree
Dear release team,
Please unblock package firmware-nonfree
[ Reason ]
A piuparts run from Andreas found that we had broken symlink for
two firmware files in firmware-brcm80211, cf. #1035282. The reason was
that we missed a rename back in upstream 20220411, included in the
upload in Debian as
On Sat, 2023-04-22 at 16:33 +0200, Ben Hutchings wrote:
> Dear Backports Team,
>
> I have just uploaded two firmware packages to bullseye-backports:
> - firmware-nonfree
> - open-ath9k-htc-firmware
I've got a rather small /boot (235 MB, ext2), and trying to upgrade
firmware
Dear Backports Team,
I have just uploaded two firmware packages to bullseye-backports:
- firmware-nonfree
- open-ath9k-htc-firmware
The ath9k_htc firmware previously provided as a binary in firmware-
nonfree -> firmware-atheros is now built from source by open-ath9k-htc-
firmware -> fi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: firmware-nonf...@packages.debian.org, Cyril Brulebois
, car...@debian.org
Control: affects -1 + src:firmware-nonfree
Hi Release Team,
Please unblock package firmware-nonfree
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1032608 + pending
Bu
Your message dated Tue, 7 Feb 2023 15:07:50 +0100
with message-id
and subject line Re: Bug#1030778: firmware-nonfree: source package has
disappeared from testing and unstable archives
has caused the Debian Bug report #1030778,
regarding firmware-nonfree: source package has disappeared from
Source: firmware-nonfree
Version: 20210315-3
Severity: important
Tags: ftbfs
On the tracker page for the "firmware-nonfree" source package, we read that
the testing and unstable versions should be 20221214-5 and 20230117-2,
respectively:
https://tracker.debian.org/pkg/firmware-nonf
On 03.02.23 16:50, Adrian Bunk wrote:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable
https://buildd.debian.org/status/logs.php?pkg=firmware-nonfree&arch=all
https://buildd.debian.org/status/package.php?p=firmware-nonfree
&quo
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable
https://buildd.debian.org/status/logs.php?pkg=firmware-nonfree&arch=all
https://buildd.debian.org/status/package.php?p=firmware-nonfree
"Section: contrib/misc" at the la
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1029708 + pending
Bu
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1026391 + pending
Bug #1026
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1025132 + pending
Bug #1025
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1024881 + pending
Bug
Source: firmware-nonfree
Source-Version: 20221012-1
Hi
On Mon, Nov 21, 2022 at 09:43:48PM +, Stefan Pietsch wrote:
> On 08.04.21 11:50, Stefan Pietsch wrote:
> > On 30.03.21 13:35, maximilian attems wrote:
> > > reopen 963025
> > > found -1 20210315-2
> &
On 08.04.21 11:50, Stefan Pietsch wrote:
On 30.03.21 13:35, maximilian attems wrote:
reopen 963025
found -1 20210315-2
tags -1 moreinfo
stop
[18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: G W
5.10.0-5-amd64 #1 Debian 5.10.24-1
[18661.586029] Hardware name: LENOVO 20N200
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1023289 + pending
Bug #
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1016945 + pending
Processing commands for cont...@bugs.debian.org:
> limit source firmware-nonfree
Limiting to bugs with field 'source' containing at least one of
'firmware-nonfree'
Limit currently set to 'source':'firmware-nonfree'
> tags 1023240 + pending
Bu
On Saturday, 29 October 2022 10:59:21 CEST Salvatore Bonaccorso wrote:
> > It was based on that log that I did most/all my recent bug closing.
>
> The files are present in the source and copied to debian/build/install
> . But they are then not installed in any of the produced binary
> packages in
gt; Indeed. How come it 'still' shows up in firmware-nonfree's build log?
> https://buildd.debian.org/status/fetch.php?pkg=firmware-nonfree&arch=all&ver=20220913-1&stamp=1666990396&raw=0
>
> It was based on that log that I did most/all my recent bug closing.
://buildd.debian.org/status/fetch.php?pkg=firmware-nonfree&arch=all&ver=20220913-1&stamp=1666990396&raw=0
It was based on that log that I did most/all my recent bug closing.
signature.asc
Description: This is a digitally signed message part.
Hi,
> Version: 20220913-1
>
> On Saturday, 12 February 2022 21:40:30 CEST Sebastian Andrzej Siewior wrote:
> > Version: 20210818-1
> >
> > The orig contains already the AMD SEV firmware in the amd folder:
> > | $ ls -lh amd
> > | 33K Aug 18 13:08 amd_sev_fam17h_model0xh.sbin
> > | 43K Aug 18 13:
Your message dated Sat, 29 Oct 2022 01:14:09 +0200
with message-id <2150816.NgBsaNRSFp@bagend>
and subject line Re: Bug#1005400: firmware-nonfree: Please package AMD SEV
firmware.
has caused the Debian Bug report #1005400,
regarding firmware-nonfree: Please package AMD SEV firmware.
to be
Your message dated Fri, 28 Oct 2022 19:20:40 +
with message-id
and subject line Bug#1020962: fixed in firmware-nonfree 20220913-1
has caused the Debian Bug report #1020962,
regarding firmware-nonfree is too old for 12Gen Intel CPU
to be marked as done.
This means that you claim that the
Your message dated Fri, 28 Oct 2022 19:20:40 +
with message-id
and subject line Bug#1009316: fixed in firmware-nonfree 20220913-1
has caused the Debian Bug report #1009316,
regarding firmware-nonfree: Please consider to update this package and its
binaries
to be marked as done.
This means
Package: firmware-linux-nonfree
Version: 20210818-1
Followup-For: Bug #1019854
X-Debbugs-Cc: schissdra...@rmm.li
I support this request. It's way too much work to get debian testing/unstable
working on new Hardware, since way too many firmwares are missing.
Took me forever to get the installer fin
Package: firmware-nonfree
Version: 20210818-1
On a Lenovo X1 Nano Gen2 various Intel hardware fails to load the
binary blobs. Here is an example of this:
```
eneufeld@eneufeld-x1nano-v2:~/power_stat$ zgrep kernel
/var/log/syslog.1.gz | grep "failed to load"
...
Sep 19 19:58:25 eneufeld
Package: firmware-nonfree
Version: 20210818-1
Severity: wishlist
X-Debbugs-Cc: tansuanyinliao8...@gmail.com
Dear Maintainer,
After I install nonfree firmware I notice that firmware missing warnings
appeared (for intel iwlwifi). I search the missing firmwares and find them in
Linux kernel
-team/firmware-nonfree/-/merge_requests/23
[1] https://lists.debian.org/73fc8ae7-9bc1-00de-ed8e-fd8848198...@debian.org
#
# bts-link upstream status pull for source package firmware-nonfree
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #1002553 (http
Hello,
The Linux-firmware-nonfree (https://tracker.debian.org/pkg/firmware-nonfree)
has been no update about one year. Please update it.
I have submit a new bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011410.
Thanks!
firmware-nonfree 20210818-1 is marked for autoremoval from testing on 2022-06-30
It (build-)depends on packages with these RC bugs:
1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183,
CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192
https://bugs.debian.org
Your message dated Mon, 16 May 2022 16:01:49 +0200
with message-id
and subject line Re: Bug#1011048: firmware-nonfree: Fails to build without
linux-support but linux-support isn't listed in Build-Depends
has caused the Debian Bug report #1011048,
regarding firmware-nonfree: Fails to
For what it's worth, I've done exactly that (installed the entire
suite of firmware packages from the testing repo) and as best I can
tell it has cured the problem I was having. Specifically after some
period of time of the laptop being up, the fan would speed up from
~2200RPM to ~3600RPM for no ap
Then that is what I will do, thank you!
On Wed, Apr 20, 2022 at 1:41 PM Diederik de Haas wrote:
>
> On Wednesday, 20 April 2022 16:05:24 CEST Kevin P. Fleming wrote:
> > If it's not possible for the firmware packages to be included in the
> > backports repo then I can configure my system to grab
On Wednesday, 20 April 2022 16:05:24 CEST Kevin P. Fleming wrote:
> If it's not possible for the firmware packages to be included in the
> backports repo then I can configure my system to grab them from
> 'testing', although at that point there may not be any value in using
> the kernel packages fr
I'm using Bullseye but with the kernel from bullseye-backports, both
to help testing and also because it handles my Lenovo docking station
better than the 5.10 kernel does.
While trying to track down some strange suspend+CPU fan behavior, I
noticed that when the kernel initializes the i915 iGPU, i
Package: firmware-nonfree
Version: 20210818-1
Severity: normal
Hi,
The orig contains already the AMD SEV firmware in the amd folder:
| $ ls -lh amd
| 33K Aug 18 13:08 amd_sev_fam17h_model0xh.sbin
| 43K Aug 18 13:08 amd_sev_fam17h_model3xh.sbin
Could this be please package? I have an AMD box
firmware-nonfree 20210818-1 is marked for autoremoval from testing on 2022-01-24
It is affected by these RC bugs:
998749: firmware-misc-nonfree: i915 freezes randomly in X especially when
playing videos
https://bugs.debian.org/998749
This mail is generated by:
https://salsa.debian.org
Source: firmware-nonfree
Followup-For: Bug #962038
Dear Maintainer and reporter,
I spoke to Phil and Serge about this issue as a bluez-firmware maintainer.
As written here[0], they seem like no plan to manage with linux-firmware.
(I think it is a good choice to manage with linux-firmware with
Hi Ben,
Ben Hutchings (2021-07-27):
> [ Reason ]
> The binary packages built from firmware-nonfree currently do not
> provide the necessary metadata for the installer to determine whether
> they are likely to be needed in the installed system.
>
> [ Impact ]
> Desktop inst
Ola Lundqvist wrote:
> I only briefly looked at the CVEs.
If you haven't even looked the issues properly don't waste other people's time.
Hi Moritz
I only briefly looked at the CVEs. I relied on that front-desk had
considered that the package needs to be fixed.
This means that we need to fix both the kernel and the firmware-nonfree
packages to fix the problems.
The question remains however, do you think these are important enough
On Mon, May 17, 2021 at 11:54:05AM +0200, Ola Lundqvist wrote:
> Hi firmware-nonfree maintainers
>
> I have a question from an LTS perspective about the possible security
> updates we have for the firmware-nonfree package.
>
> You can find them here:
> https://security-track
Hi firmware-nonfree maintainers
I have a question from an LTS perspective about the possible security
updates we have for the firmware-nonfree package.
You can find them here:
https://security-tracker.debian.org/tracker/source-package/firmware-nonfree
I can see that all the related CVEs are
On 30.03.21 13:35, maximilian attems wrote:
reopen 963025
found -1 20210315-2
tags -1 moreinfo
stop
[18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: GW
5.10.0-5-amd64 #1 Debian 5.10.24-1
[18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W (1.59
) 11
Processing commands for cont...@bugs.debian.org:
> found 963025 20210315-2
Bug #963025 [firmware-iwlwifi] firmware-iwlwifi: Microcode SW error detected /
9000-pu-b0-jf-b0-46.ucode
Marked as found in versions firmware-nonfree/20210315-2.
> tags 963025 moreinfo
Bug #963025 [firmware-i
sions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions firmware-nonfree/20210315-1~exp1.
> found -1 20210315-2
Failed to add found on -1: The 'bug' parameter ("-1") to
Debbugs::Control::set_found did not pass regex check
.
reopen 963025
found -1 20210315-2
tags -1 moreinfo
stop
> [18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: GW
> 5.10.0-5-amd64 #1 Debian 5.10.24-1
> [18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W
> (1.59 ) 11/29/2019
Please could you upgrade the
On 16.03.21 17:34, Debian FTP Masters wrote:
> Source: firmware-nonfree
> Source-Version: 20210315-1~exp1
> Done: maximilian attems
>
> We believe that the bug you reported is fixed in the latest version of
> firmware-nonfree, which is due to be installed in the Debian FTP arch
Hello,
uploading 20210315-2 now with several important fixes.
Once it has again enough unstable exposure will ask for unblock.
There is a known issue with Raspberry Pi 4 5 Ghz wlan,
which has no known solution yet.
best,
signature.asc
Description: PGP signature
Dear release team,
> thank you for unblocking 20210208-4 firmware-nofree.
this landed in testing. (:
> > or have it together with latest 20210315-1, which includes thoses fixes,
> > but adds more support for intel iwlwifi/bluetooth and AMD green sardine
> > support - (gpu seen on current lenovo
thank you for unblocking 20210208-4 firmware-nofree.
> or have it together with latest 20210315-1, which includes thoses fixes,
> but adds more support for intel iwlwifi/bluetooth and AMD green sardine
> support - (gpu seen on current lenovo laptops)?
the latest hardware support with 20210315 is
> 20210208-4 upload happening now.
Would debian-release prefer a bug report pushing that into testing
or have it together with latest 20210315-1, which includes thoses fixes,
but adds more support for intel iwlwifi/bluetooth and AMD green sardine
support - (gpu seen on current lenovo laptops)?
pl
1 - 100 of 401 matches
Mail list logo
