Control: tag -1 moreinfo
On Sat, 28 Sep 2024 03:09:54 + gabriel wrote:
> Package: src:linux
> Version: 6.11-1~exp1
>
> ipu6 mipi camera drivers were not part of previous kernels, now they have
> been upstreamed.
> After upgrading kernel to 6.11 the ipu6 kernel modules are loaded, however
> t
Package: systemd
Version: 256.5-1
Severity: normal
X-Debbugs-Cc: debian-kernel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I build a custom (arm64) kernel based on Debian's config and in that I
disabled debug info, which in turn disabled ``CONFIG_DEBUG_INFO_BTF``.
Build was
Control: reopen -1
Control: retitle -1 Please extend NEWS to clarify what users can and should do
On Saturday, 27 July 2024 11:30:37 CEST Dan Jacobson wrote:
> Yes. The news item needs to warn:
>
> ** Warning: if you take no action, upon the next boot you might
> 1. Not be able to network.
> 2. N
On Saturday, 27 July 2024 10:54:22 CEST Dan Jacobson wrote:
> That's exactly what happened to me.
> Not all users automatically install recommends.
Those users are ofc allowed to make that choice, but they then also accept the
consequences that go with it.
What you asked for is exactly how it wa
Control: found -1 6.3.7-1
On Friday, 26 July 2024 10:49:00 CEST Stefan wrote:
> The complete sentence is:
>
> oldest non-working kernel is 6.3.7 (package linux-image-6.3.0-1-amd64),
> 6.3.5 (latest version of package package linux-image-6.3.0-0-amd64) works.
Excellent, that narrows down the 'sus
On Wednesday, 24 July 2024 19:25:56 CEST Ben Hutchings wrote:
> On Wed, 2024-07-24 at 11:19 +0200, Diederik de Haas wrote:
> > On Wednesday, 24 July 2024 05:09:51 CEST Ben Hutchings wrote:
> > > The agenda is here:
> > > https://salsa.debian.org/kernel-team/meetings/-/wi
Control: found -1 6.9.7-1~bpo12+1
On Wednesday, 24 July 2024 17:24:44 CEST Stefan wrote:
> I ran a few other tests:
>
> 1. tried package "linux-image-6.1.0-22-amd64": works
> 2. tried package "linux-image-6.9.7+bpo-amd64": does not work
Via https://snapshot.debian.org/package/linux-signed-amd64/
On Wednesday, 24 July 2024 13:21:36 CEST Vincent Lefevre wrote:
> On 2024-07-24 10:58:24 +0200, Diederik de Haas wrote:
> > Uninstalling firmware YOU DON'T NEED is a perfectly valid solution.
>
> How can one do that? I mean, get only the Nvidia firmware for my
> part
On Wednesday, 24 July 2024 05:09:51 CEST Ben Hutchings wrote:
> The agenda is here:
> https://salsa.debian.org/kernel-team/meetings/-/wikis/20240724
> (note we are unlikely to get through all the bugs).
>
> Please reply to this message if you want to add items.
There are a number of open MRs whic
On Sunday, 21 July 2024 13:13:23 CEST Simon John wrote:
> Realistically we need a fix for whatever happened here and it can't be
> any of:
>
> * remove plymouth or firmware (not practical for desktop)
Plymouth is not the problem. It turns out it's installed on my laptop and I
don't have this p
Control: reassign -1 src:initramfs-tools 0.142
Control: fixed -1 0.143
On Friday, 19 July 2024 20:05:52 CEST Diederik de Haas wrote:
> Control: tag -1 moreinfo
>
> On Friday, 19 July 2024 17:27:39 CEST Diederik de Haas wrote:
> They are symlinks in the firmware-nvidia-graphics pa
Control: tag -1 moreinfo
On Friday, 19 July 2024 17:27:39 CEST Diederik de Haas wrote:
> Today I learned something new and that is that plymouth includes
> GPU modules AND their firmware in the initramfs.
And learned something else via https://bugs.debian.org/1076582#37 :
On vrijdag 1
Control: tag -1 pending
On Friday, 28 June 2024 08:47:52 CEST Diederik de Haas wrote:
> Control: tag -1 patch
>
> I submitted a MR to fix this bug with my changes here:
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/1109
And that MR has been merged into master and
Control: affects -1 firmware-nvidia-graphics
On Friday, 19 July 2024 17:56:30 CEST Chris Hofstaedtler wrote:
> Control: retitle -1 initramfs-tools: duplicates nvidia firmware files
>
> On Fri, Jul 19, 2024 at 04:43:47PM +0200, Diederik de Haas wrote:
> > > In any case, the u
Control: severity -1 important
On Thursday, 18 July 2024 10:54:48 CEST Diederik de Haas wrote:
> Control: severity -1 minor
>
> On 18 Jul 2024 09:43:38 +0200 Bastian Venthur wrote:
> > Package: plymouth
> > Version: 24.004.60-2
> > Severity: important
> >
[ not including debian-release for this ]
On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote:
> On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote:
> > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote:
> > > When upgrading the firmware:
> > >
&
[ adding debian-release to the list for some troubling observations ]
On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote:
> On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote:
> > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote:
> > > When upgr
Control: tag -1 moreinfo
On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote:
> When upgrading the firmware:
>
> [...]
> Setting up firmware-intel-graphics (20240610-1) ...
> Setting up firmware-iwlwifi (20240610-1) ...
> Setting up firmware-misc-nonfree (20240610-1) ...
> Setting up firm
On Thursday, 18 July 2024 11:11:23 CEST Laurent Bigonville wrote:
> Well you change expectation from users that have firmware-misc-nonfree
> installed by pulling that huge package
I fail to see how. If those files weren't split into their own packages, the
updated/new firmware-misc-nonfree would'
Control: severity -1 minor
On 18 Jul 2024 09:43:38 +0200 Bastian Venthur wrote:
> Package: plymouth
> Version: 24.004.60-2
> Severity: important
> X-Debbugs-Cc: vent...@debian.org
>
> Dear Maintainer,
>
> trying to update plymouth fails with "No space left on device":
>
> sudo aptitude -u
> Pe
On Tuesday, 16 July 2024 07:16:29 CEST Thomas Goirand wrote:
> I have a Legion Pro 7 laptop, which I made my company buy because
> it has 16 cores, so I can build stuff faster. I love the hardware,
> but it produces no sound: sound board is supported, but it looks
> like the current Debian kernel d
On Wednesday, 12 June 2024 15:59:27 CEST Diederik de Haas wrote:
> On Tuesday, 11 June 2024 09:01:20 CEST Diederik de Haas wrote:
> > I already have a local branch to add preliminary support for the OpenWrt
> > One router [1] [2] which uses the same SoC :-)
>
> I was wrong.
On Monday, 1 July 2024 17:17:46 CEST Nathan MALO wrote:
> It seems to me that it is working as expected !
Awesome :-)
signature.asc
Description: This is a digitally signed message part.
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
>
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
On Saturday, 4 February 2023 22:12:24 CEST Salvatore Bonaccorso wrote:
> Hi,
>
> On Wed, Feb 01, 2023 at 09:20:57PM -0600, Gunnar Wolf wrote:
> > Hi!
> >
> > Diederik de Haas dijo [Tue, Jan 31, 2023 at 10:33:41PM +0100]:
> > > > Would they fit into a sepa
Control: reassign -1 src:linux
Control: forcemerge -1 1093998
On Sunday, 30 June 2024 06:07:55 CEST Dan Jacobson wrote:
> Package: linux-image-amd64
>
> dpkg: warning: while removing linux-image-6.8.11-amd64, directory
> '/lib/modules/6.8.11-amd64' not empty so not removed # ls -l
> /lib/modules/
On Friday, 28 June 2024 19:40:50 CEST Mario Limonciello wrote:
> > As this will normally be a headless system, I'm actually looking if I can
> > turn the GPU off, *unless* there's an HDMI cable plugged in.
> > So (at least for now), the GPUs only function is to have a display when I
> > need it for
On Friday, 28 June 2024 19:24:58 CEST Mario Limonciello wrote:
> On 6/28/2024 12:05, Diederik de Haas wrote:
> > On Friday, 28 June 2024 18:37:06 CEST Mario Limonciello wrote:
> >> On 6/28/2024 11:18, Diederik de Haas wrote:
> >>>> I don't think so. I
On Friday, 28 June 2024 18:37:06 CEST Mario Limonciello wrote:
> On 6/28/2024 11:18, Diederik de Haas wrote:
> >> I don't think so. I've never heard of this actually used in a desktop
> >> board. It's for mobile designs AFAIK.
> >
> > I can unde
On Friday, 28 June 2024 17:49:40 CEST Mario Limonciello wrote:
> On 6/28/2024 10:41, Diederik de Haas wrote:
> > On Monday, 5 February 2024 15:47:08 CEST Nate wrote:
> >> AMD has introduced a feature called Power Management Framework.
> >
> > With the upload of 6.9.
On Monday, 5 February 2024 15:47:08 CEST Nate wrote:
> AMD has introduced a feature called Power Management Framework.
> See here for more info: https://www.phoronix.com/news/AMD-PMF-Linux-Driver
>
> It seems that this module is not included in the Debian Linux Kernel.
With the upload of 6.9.7 th
Control: tag -1 patch
On Wednesday, 26 June 2024 03:04:15 CEST Leith Bade wrote:
> Diederik provided me with a new v6.10 kernel build to try:
> [0.00] Linux version 6.10-rc5+unreleased-arm64 (
> debian-kernel@lists.debian.org) (aarch64-linux-gnu-gcc-13 (Debian
> 13.2.0-25) 13.2.0, GNU ld (
Control: reopen -1
Control: found -1 6.8.9-1
Control: found -1 6.9.2-1~exp1
On Thursday, 23 May 2024 17:33:47 CEST Vincent Blut wrote:
> Le 2024-05-23 17:12, Nathan MALO a écrit :
> > Thank you very much for enabling those two features in the kernel.
> > Your work is much appreciated !
> >
> > Ma
On Saturday, 22 June 2024 13:02:24 CEST Pierre Tomon wrote:
> Control: tags -1 + fixed-upstream
>
> This bug is now fixed upstream.
>
> Commit: 7926d51f73e0 - scsi: sd: Use READ(16) when reading block zero on
> large capacity disks Releases: v6.1.95, v6.6.35 and v6.9.6
That's awesome. Great work
On Monday, 24 June 2024 14:10:18 CEST Leith Bade wrote:
> On 24 Jun 2024 at 20:32, Diederik de Haas wrote:
> > > This likely due to my unfamiliarity with building the Debian kernel.
>
> I will eventually manage to figure it out. Part of the problem is that
> there is a lo
On Monday, 24 June 2024 14:43:38 CEST Leith Bade wrote:
> On Mon, 24 Jun 2024 at 22:10, Leith Bade wrote:
> > > After inspecting the /lib/firmware directory, it seems the APT package
> > >
> >> > "firmware-misc-nonfree" has firmware for older MediaTek chips, but is
> >> > missing files for ant MT
On Monday, 24 June 2024 07:10:48 CEST Leith Bade wrote:
> I finished my first round of testing the new kerned on my BPI-R3 board.
This is more extensive testing then I normally see. Nice :-)
> This likely due to my unfamiliarity with building the Debian kernel.
Given your interest (similar to mi
Control: found -1 6.6.15-1
On Friday, 21 June 2024 13:41:38 CEST Christoph Berg wrote:
> I just had the same problem on linux-image-6.6.15-amd64.
Updating found version accordingly.
> > It seems to me that at least with purging that file should be removed
> > and subsequently the ``/lib/modules/
Source: linux
Version: 6.9.2-1
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When removing or 'even' purging a linux-image- package, it
reports the following issue:
rmdir: failed to remove '/lib/modules/': Directory not empty
The reason for that is that there's still a ``modul
On Thu, 29 Oct 2020 14:22:16 +0100 Axel Beckert wrote:
> Package: firmware-linux-free
> Version: 20200122-1
>
> now that "iw" dropped the dependency on "crda" (see
> https://bugs.debian.org/972994), "wireless-regdb" gets uninstalled, too,
> as it was only pulled in via dependency by crda, at leas
On Sunday, 16 June 2024 15:20:05 CEST Leith Bade wrote:
> I need to work out how to submit these fixes to the Linux device tree
> maintainers.
My experience is primarily/only with Rockchip based devices/SoCs and their
upstream development process, but it may help wrt MediaTek's.
- If you think s
On Thursday, 13 June 2024 23:00:51 CEST Leith Bade wrote:
> Excellent, hopefully we can get the DTS stuff from OpenWrt upstreamed into
> Linux for the OpenWrt and BPI-R3.
I have (thus far) found one possible oddity, but otherwise it looks ok AFAICT
for BPI-R3. When that's done, the OpenWrt One sh
On Thursday, 13 June 2024 13:55:40 CEST Diederik de Haas wrote:
> > Banana Pi released a public version of the MT7986 manual which has all the
> > various register memory locations documented, though some stuff is
> > missing.
>
> Only after writing the previous line, I r
On Wednesday, 12 June 2024 23:45:30 CEST Leith Bade wrote:
> Also, has a public version of the MT7981 Reference Manual been published?
I have no idea. I have not searched and actually don't know much/anything
about MediaTek devices in general.
All I'm using is what is described in the DTS file in
On Wednesday, 12 June 2024 23:40:41 CEST Leith Bade wrote:
> Ideally if in your new kernel build you enable support for MT7981, MT7986,
> MT7988 at the same time that would be nice.
I'll only add support for the MT7986 in my kernel build as that one can be
tested (by you) to actually work as inte
On Tuesday, 11 June 2024 09:01:20 CEST Diederik de Haas wrote:
> I already have a local branch to add preliminary support for the OpenWrt One
> router [1] [2] which uses the same SoC :-)
I was wrong.
$ grep ".dtsi" arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts
#inclu
On Tuesday, 11 June 2024 12:26:17 CEST Leith Bade wrote:
> For the record the issues I noticed are (comparing with U-boot and OpenWRTs
> versions of the device tree files):
> - mt7986a.dtsi is missing entry for the SNFI / SNAND interface to load
> https://github.com/torvalds/linux/blob/83a7eefedc9b
Hi,
On Tuesday, 11 June 2024 08:02:41 CEST Leith Bade wrote:
> I have a Bananapi BPI-R3 board which uses the Mediatek MT7986 ARM64 SoC for
> its CPU. This is a router focussed board and currently has good support in
> the OpenWRT distribution and in the upstream Linux for a few years. The
> device
Hi,
On Saturday, 8 June 2024 10:31:39 CEST Salvatore Bonaccorso wrote:
> here is the start of the thread to collect potential
> agenda points for the next meeting.
I'd like to propose the following item:
- Adapting the Debian build scripts for the tools build framework
In the upstream `tools` di
Control: tag -1 moreinfo
On Friday, 7 June 2024 11:27:43 CEST Michael Kesper wrote:
> With kernel 6.7.12-amd64, no GUI is getting started, also no console
> gets opened automatically (boot seems to "hang"). External monitors
> (connected via USB HUB) stay blank.
> With kernel 6.6 everything works
On Wednesday, 29 May 2024 03:22:50 CEST Mark Pearson wrote:
> >> X-Debbugs-Cc: mpearson-len...@squebb.ca
> > ...
> > The MR for it (1062) has just been merged into master.
>
> Awesome - thanks! I did scan the bugs before submitting but missed that one.
> Apologies. Should I close this issue then a
Control: forcemerge -1 1071551
On Tuesday, 28 May 2024 20:20:11 CEST Mark Pearson wrote:
> Package: src:linux
> Version: 6.8.11-1
> Severity: important
> X-Debbugs-Cc: mpearson-len...@squebb.ca
>
> Dear Maintainer,
>
> Please enable the CONFIG_PINCTRL_METEORLAKE kernel option. This is needed to
On Thursday, 23 May 2024 17:33:47 CEST Vincent Blut wrote:
> We are just lacking a configuration symbol. Diederik, starting with
> linux 6.8 AMD PMF requires TEE. Do you want me to send a MR?
Sure.
Bit surprised it wouldn't be automatically selected though.
signature.asc
Description: This is a di
On Thursday, 23 May 2024 09:59:52 CEST Eduardo Casais wrote:
> 4) Determining whether the bug was introduced by the passage from kernel
> 5.10.0 to 6.1.0, or whether it was an error introduced between releases
> of image 6.1.0-*.
>
> Attempted resolution:
>
> I looked at the image versions availa
Control: reassign -1 r8125-dkms
On Tuesday, 21 May 2024 10:41:54 CEST Pierpaolo Toniolo wrote:
> Was installing the linux-image-6.8.9-amd64 and it's fellow linux-
> headers-6.8.9-headers.
> At modules creation with dkms I got an error building module r8125 (package
> r8125-dkms)
Which is a proble
On Monday, 20 May 2024 21:07:49 CEST Salvatore Bonaccorso wrote:
> - I did read you cannot trigger with 5.15. If you build 6.1.90 from
> upstream without Debian patches I assume you can trigger the issue
> likewise? If so could you bisect the changes introducing the issue?
If the test with the
On Monday, 20 May 2024 12:41:48 CEST Ben Hutchings wrote:
> > - Can I do anything for you?
>
> My top priority would be more computing resources for Salsa, and
> particularly for CI runners.
+1
That was the first thing that came to my mind too, but it felt out of place for
me to suggest that. I
On Friday, 17 May 2024 15:08:17 CEST Development EasyNet wrote:
> I will try. Meanwhile I was troubleshooting this issue for some time and
> I notice a change in FRRouting between 9.1 and 10.0.
> Before 10.0 FRRouting was installing the routes in kernel using the
> destination interface of the rout
Control: tag -1 moreinfo
On 15 May 2024 16:08:27 +0200 Development EasyNet wrote:
> Package: linux-image
> Version: 6.6.15-2 and 6.7.12-1
>
> I'm facing for some time a strange behavior of the route-leak. It happen
> on both IPv4 and IPv6.
> Configuration used: Debian Trixie, Kernel 6.7.12 with
Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/3343
signature.asc
Description: This is a digitally signed message part.
On Friday, 17 May 2024 03:36:35 CEST Forest wrote:
> A git bisect reveals it to be fixed by this commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=
> f7a59018953910032231c0a019208c4b0a4a8bc3
> > maple_tree: make mas_erase() more robust
> >
> > mas_erase() may
Hi Mark,
On Tuesday, 7 May 2024 19:30:59 CEST Mark Pearson wrote:
> > I already mentioned that MR 85 is a BIG one (but the only one which needs
> > to go through NEW), which in turn means that reviewing takes more then 10
> > minutes (to put it mildly).
> >
> > The updates after that are indicati
On Tuesday, 7 May 2024 15:49:45 CEST Mark Pearson wrote:
> > As I see it, the primary problem is the lack of people actively
> > contributing to the Debian kernel team's work. In general.
>
> Interesting read, and combined with my notes to Didier - is this something
> where I and some in my team c
On Tuesday, 7 May 2024 08:25:23 CEST Didier 'OdyX' Raboud wrote:
> What I did back then to try to help getting the firmware package in better
> shape was to dive in the (complex) packaging and try to produce "ready-to-
> merge" merge-requests for new upstream releases, fixes, etc, then pinging
> Be
Control: merge -1 1070353
On Saturday, 4 May 2024 16:56:10 CEST Kurt Meyer wrote:
> Package: src:linux
> Version: 6.7.12-1
> Severity: important
>
> * What led up to the situation?
>
> Booting with the linux-image-6.7.12-amd64 kernel results in Wi-Fi not
> working and Wi-Fi isn't even an option
Control: reassign -1 src:firmware-nonfree 20230625-2
On Friday, 26 April 2024 07:36:16 CEST Martin-Éric Racine wrote:
> Package: src:linux
> Version: 6.7.7-1
> Severity: normal
>
> W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module
> i915 W: Possible missing firmware /lib/fi
Control: forwarded -1 https://github.com/util-linux/util-linux/issues/2867
https://lore.kernel.org/all/20240328-mips_save_syscall-v1-1-9e1d62d69...@flygoat.com/
On Thursday, 25 April 2024 22:10:12 CEST Chris Hofstaedtler wrote:
> reassign 1068365 src:linux
> affects 1068365 src:util-linux
> thank
Control: tag -1 -moreinfo +upstream
Control: forwarded -1
https://lore.kernel.org/linux-bluetooth/CADRbXaDqx6S+7tzdDPPEpRu9eDLrHQkqoWTTGfKJSRxY=ht...@mail.gmail.com/
On Monday, 22 April 2024 10:32:00 CEST Jeremy Lainé wrote:
> Over the weekend I reported the issue to the linux-bluetooth mailing
>
tch and build a kernel.
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
describes a procedure with which you can apply (the attached) patches
HTH>From 21f7e476d0afe832f6656b917b976c6efe6b24f3 Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Tue, 16
makes the 6.7 kernel work properly again, we
likely have found the culprit for the kernel oops/panic.
Can you first try the Testing (6.6.15) kernel and if that works try
applying the attached patches to the 6.7 kernel?>From 407672343a738ede6f5e955e3afa57d16b37f4e6 Mon Sep 17 00:00:00 2001
From:
On Monday, 15 April 2024 10:41:55 CEST Eric Valette wrote:
> Why is there no 6.6 up-to-date kernel pushed in testing as well? Do you
> plan to wait until 6.6 enter stable? When?
Nothing gets 'pushed' to Testing. Packages *transition* to Testing when
several conditions are met. https://tracker.deb
On Wednesday, 10 April 2024 15:32:02 CEST Cyril Brulebois wrote:
> Cyril Brulebois (2024-04-10):
> > Salvatore Bonaccorso (2024-04-10):
> > > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > > > Does the problem go away if you revert t
Hi Cyril,
On Tuesday, 9 April 2024 01:06:43 CEST Cyril Brulebois wrote:
> Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64
> leads to losing some SMART information, at least as queried by munin (in
> Debian 12) when it comes to sensors.
Does the problem go away if you rever
Control: forcemerge -1 1054889
On Monday, 8 April 2024 10:44:12 CEST dada007 wrote:
> I had an earlier report with this bug
No need to have 2 bugs for the same problem, thus merging
signature.asc
Description: This is a digitally signed message part.
, restart clients).
>
> (3) Instead I will try first to use debian testing on a different NUC, but
> this will take some time.
>
> 2. April 2024 20:28, "Diederik de Haas" schrieb:
> > On Tuesday, 2 April 2024 19:54:41 CEST J. Pfennig wrote:
> >> Package: src
On Tuesday, 2 April 2024 19:54:41 CEST J. Pfennig wrote:
> Package: src:linux
> Version: 6.1.76-1
> Severity: important
> Tags: upstream
I am/was inclined to remove that tag, but the problem is likely caused by
firmware which is too old for the 'backported' patches that upstream applied.
> The d
On Tuesday, 19 March 2024 11:52:29 CET Josua Mayer wrote:
> May I ask if you are analyzing dts manually, or whether you are aware
> of an automatic tool?
Analyses is done by a MUCH improved scripts based upon what I came up with a
while ago:
https://salsa.debian.org/kernel-team/linux/-/merge_requ
Hi,
Since https://bugs.debian.org/863290 (2017) the Debian kernel has had a
patch to warn about the use of RAID 5/6 with BTRFS.
That bug mentions "It looks like there's a consensus that such a warning
should live in the kernel rather than userland"
Via [1] and [2] it seems userland did get a warn
om
you), ECC support should already work with the Stable 6.1 kernel (or newer).
> > Am 07.03.24 um 13:34 schrieb Diederik de Haas:
> >> On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> >>
> >>> LX2160 SoC early silicon revisions have a pci-e gener
Hi Josua,
On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> LX2160 SoC early silicon revisions have a pci-e generation 4 controller.
> It requires a different driver from newer gen-3 silicon.
>
> This affects the SolidRun Honeycomb Workstation which
> is otherwise fully supported in
Control: clone -1 -2
Control: retitle -2 Additional support for SolidRun HoneyComb
On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> LX2160 SoC early silicon revisions have a pci-e generation 4 controller.
> It requires a different driver from newer gen-3 silicon.
>
> This affects th
Control: tag -1 moreinfo
On Saturday, 24 February 2024 14:16:53 CET Harald Dunkel wrote:
> Package: firmware-iwlwifi
> Version: 20230625-2
>
> The source URL mentioned in the copyright file doesn't work anymore.
Which URL do you mean?
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-f
Control: reassign -1 src:linux 5.10.178-1
On Wednesday, 10 May 2023 15:41:44 CET Christian Kiss wrote:
> Package: firmware-amd-graphics
> Version: 20210315-3
>
> kernel.log reports that radeon: 1 quad pipes, 2 z pipes initialized.
> the gpu an rv530 has atleast double to 4 of these each.
>
> th
Control: tag -1 moreinfo
On Mon, 10 May 2021 18:13:43 + static wrote:
> Package: firmware-realtek
> Version: 20210315-2
>
> I am trying to install from scratch firmware-edu-bullseye-DI-rc1-amd64-
> BD-1.iso (also tried on debian-bullseye-DI-rc1-amd64-DVD-1.iso but interface
> is not detecte
Control: tag -1 moreinfo
On 20 Jan 2020 22:32:26 +0100 Patrice Duroux wrote:
> Package: firmware-iwlwifi
> Version: 20190717-2
>
> I am reporting this «exception» here without being sure this is the right
> package or if it has been already reported (not easy to check).
>
> [ 48.335755] -
On Fri, 17 Jan 2020 17:24:14 +0200 Sicelo wrote:
> Package: firmware-ti-connectivity
> Version: 20190717-2
>
> Please include TIInit_10.6.15.bts [1], which is needed for bluetooth on
> the Motorola Droid 4 and similar boards. Similar files are already part
> of the debian package, and the licence
Control: retitle -1 firmware-iwlwifi: Please update to version 20230804
On Sunday, 11 February 2024 18:56:23 CET Diederik de Haas wrote:
> It could/might be there would be some improvement somewhere with newer
> firmware, but as long as things keep working that is fine.
> Consequen
Control: tag -1 moreinfo
On Saturday, 3 February 2024 17:33:32 CET Aly Ghobashy wrote:
> Package: firmware-amd-graphics
> Version: 20230210-5
>
>* What led up to the situation?
> opening a video file with VLC
>* What exactly did you do
> video file to open normally.
>*
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
On Tuesday, 20 February 2024 09:22:06 CET Ben Mesman | Spark Narrowcasting
wrote:
> mmc: sdhci-pci-o2micro: Fix a warm reboot issue that disk can't be
> detected by BIOS
> ...
> Link:
> https://lore.kernel.org/r/20240203102908.4683-1-fredaibayhubt...@126.com
>
> I'm still waiting for the p
On Tuesday, 13 February 2024 17:59:55 CET Mario Limonciello wrote:
> > I think it's important to facilitate people having f.e. the following
> > combos:
> > - Intel CPU with AMD GPU
> > - AMD CPU with Nvidia GPU
> > - AMD CPU with AMD GPU (discrete or integrated)
> >
> > Preferably without having
On Monday, 12 February 2024 21:25:35 CET Mario Limonciello wrote:
> > My logic was that this is about AMD TEE (Trusted Execution Environment),
> > which I *assumed* is part of/tied to the CPU. This thought is based on
> > that on ARM platforms, you also have a TEE and that is part of the CPU
> > (a
On Monday, 12 February 2024 19:38:12 CET Henrique de Moraes Holschuh wrote:
> On Fri, Feb 2, 2024, at 13:50, Diederik de Haas wrote:
> > This is about "AMD Platform Management Framework TA", which seems to be
> > about AMD CPU features. The first (and only
Control: forwarded -1
https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/
On Monday, 12 February 2024 12:56:45 CET Arno Lehmann wrote:
> Reported upstream, see
>
> https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0d2a@its-lehm
> ann.de/T/#u
Excellen
100, Diederik de Haas пишет:
> > Control: tag -1 moreinfo
> >
> > On Saturday, 10 February 2024 17:41:43 CET Nikolay Sabelnikov wrote:
> > > Package: linux-image-amd64
> > > Version: 6.1.76-1
> > >
> > > > update-initramfs: Generating /boot/in
Control: tag -1 moreinfo
On Saturday, 10 February 2024 17:41:43 CET Nikolay Sabelnikov wrote:
> Package: linux-image-amd64
> Version: 6.1.76-1
>
> > update-initramfs: Generating /boot/initrd.img-6.1.0-18-amd64
> > W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for
> > module a
Control: reassign -1 firmware-iwlwifi 20230625-2
Control: retitle -1 firmware-iwlwifi: Please update to version 20230919
On Sunday, 11 February 2024 16:34:16 CET Miguel Angel Rojas wrote:
> > While 'annoying', this is expected behavior. It tries to load the newest
> > (-83)
> Yes, this is the expe
Hi Miguel,
On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote:
> I forgot to include you the dmesg as promised:
>
> [2.235947] iwlwifi :00:14.3: enabling device ( -> 0002)
> [2.237778] iwlwifi :00:14.3: Detected crf-id 0x1300504, cnv-id
> 0x80401 wfpm id 0x8030
On Sunday, 11 February 2024 11:11:53 CET Miguel Angel Rojas wrote:
> My bad. Let me explain again. Taking into account the firmware errors:
>
>- Realtek messages are fixed now. There are no actions to be done here.
Good.
>- iwlwifi: If you are still working on a new version containing th
1 - 100 of 741 matches
Mail list logo
