Re: Handling next linux upload to unstable

On Sun, Sep 15, 2024 at 11:08:34PM +0200, Cyril Brulebois wrote: >Steve McIntyre (2024-09-15): >> Kibi: just checking, are you happy for me to call this trixie d-i >> alpha 1? > >As communicated a few times in previous mails already: not at all. Understood, I'm glad I checked. I'll call this some

Re: Handling next linux upload to unstable

Steve McIntyre (2024-09-15): > Kibi: just checking, are you happy for me to call this trixie d-i > alpha 1? As communicated a few times in previous mails already: not at all. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- Release team memb

Bug#1081563: Please consider adding the new Xe Graphics driver for Intel GPUs

On Sun, 2024-09-15 at 21:27 +0200, Petter L. H. Eide wrote: > My understanding is that it is possible to manually trigger the binding (by > adding eg. i915.force_probe=!56a0 xe.force_probe=56a0 as kernel > parameters). Would the fact that its does not bind to hardware by default > not mitigate the

Re: Handling next linux upload to unstable

On Sun, Sep 15, 2024 at 12:31:12AM +0200, Cyril Brulebois wrote: >Steve McIntyre (2024-09-14): >> >> That looks great for me, thanks. > >Then I think my work here is done: > >kibi@respighi:~$ dak ls debian-installer -s testing,unstable -a source >debian-installer | 20240914 | testing

Bug#1081563: Please consider adding the new Xe Graphics driver for Intel GPUs

My understanding is that it is possible to manually trigger the binding (by adding eg. i915.force_probe=!56a0 xe.force_probe=56a0 as kernel parameters). Would the fact that its does not bind to hardware by default not mitigate the experimentalness somewhat? In case you are not aware, there are oth

Processed: limit source to linux, tagging 980555, tagging 1079272, tagging 1079501, tagging 1079755

Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 980555 + pending Bug #980555 [src:linux] Missing ec_sys module Added tag(s) pending. > tags 1079272 + pendin

Bug#1081114: linux: Please enable CONFIG_MT7925E=m, CONFIG_MT7925U=m

Hi Robert, Le 2024-09-08 03:32, Robert Edmonds a écrit : > Package: linux > Severity: wishlist > > Dear maintainers, > > Please enable support for MediaTek Wi-Fi 7 adapters based on the > mt7925 driver. These adapters can be purchased now (e.g. the AzureWave > AW-EB600NF M.2 module) but the driv

Bug#1081114: Current state

Dear maintainers, I just updated to 6.10.9 but unfortunately no mt7925 in the config. My laptop was using zabbly-linux (which provides a mainline kernel for debian) where all was working like a charm. Thought i remove that and go with debian and noticed, the wifi does not work anymore. Thats ho

Re: Is the sh7785lcr kernel still useful?

On Sun, 2024-09-15 at 08:00 +0200, John Paul Adrian Glaubitz wrote: > On Sun, 2024-09-15 at 00:10 +0200, Ben Hutchings wrote: > > I've done a new cross-build here, so you can test the packages from: > > https://people.debian.org/~benh/packages/linux-sh4/ > > Thanks a lot. > > I installed the new

Bug#894906: linux-cpupower: provide a systemd service and a default config file

On Sat, 27 Jul 2024 17:54:34 +0200 Francesco Poli wrote: [...] > I reiterate the request to people from the Debian Kernel Team: could > someone please step in, test the three files, and share his/her insight [...] > ? Dear Debian Kernel Team, this bug needs love, could some of you please spend a

Bug#832609: closing 832609

Hi, On Sun, Sep 15, 2024 at 01:15:11AM +0200, Alban Browaeys wrote: > On Sat, 14 Sep 2024 10:06:28 +0200 Salvatore Bonaccorso > wrote: > > close 832609 1:1.3.4-2 > > thanks > > > > I see that you fixed in 1:1.3.4-2 : >systemd: Don't degrade system state for nfs-clients when krb5 keytab >

Re: Bug#1065416: Bastian's offer in #1065416

Hi Matthias, On Sun, 2024-09-15 at 13:50 +0200, Matthias Klose wrote: > > It is trivial for us to add support for additional architectures once > > they are minimally supported in upstream Linux (we may also require > > that dpkg recognises their triplet; I'm not sure). There is no > > requiremen

Re: Bug#1065416: Bastian's offer in #1065416

On 12.09.24 19:56, Ben Hutchings wrote: On Thu, 2024-09-12 at 12:19 +0200, Helmut Grohne wrote: Hi Ben, Dropping leader@ and community@ from Cc as this is a technical side-track. On Thu, Sep 12, 2024 at 12:38:24AM +0200, Ben Hutchings wrote: On Mon, 2024-09-09 at 02:13 +0200, Ben Hutchings wr

Re: Bug#1065416: Bastian's offer in #1065416

On 12.09.24 11:58, stefa...@debian.org wrote: Hi Ben (2024.09.11_22:38:24_+) While potential solutions to this bug are being discussed, would you please consider removing the Provides from linux-libc-dev? I am open to doing so. [...] I raised this at today's team meeting and it was agree

Bug#1081833: linux-image-6.1.0-25-amd64: regression on linux-image-6.1.0-25.amd64 regular cracks in HDMI sound during playback - 6.1.0-23 works.

Package: src:linux Version: 6.1.106-3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Changing AMD graphic/sound controller board. Sound play back was audible but marred by constant crakcs every

Bug#1081826: linux-libc-dev ships header files not needed for 99% of it's users

Package: linux-libc-dev Version: 6.10.9-1 Severity: important Tags: sid trixie linux-libc-dev started shipping header files not needed for 99% of it's users. The default usage of linux-libc-dev is the availability of the user facing header files for native builds. These make up likely 99% or