Yes, this explains it.
I modified my omit kernel module hook and it works like a charm.
Thank You so much Bastian!
This bug report can be closed.
On Mon, Jan 29, 2024 at 12:02 AM Bastian Blank wrote:
> Hi Safir
>
> On Sun, Jan 28, 2024 at 11:21:05PM +, Safir Secerovic wrote:
> > I have a
Hi Safir
On Sun, Jan 28, 2024 at 11:21:05PM +, Safir Secerovic wrote:
> I have a custom hook that omits a kernel module being built into an initrd
> image.
So it is a bug in your hook itself?
> Until kernels 6.6 and above, the hook does not seem to take effect.
> The module is not omitted
Upon further testing with XanMod Kernel [1], version 6.7.2, initramfs-tools
package is
functioning properly.
So, this bug could be attributed to official Debian kernel images, 6.6 and
6.7 (in experimental).
I guess this bug could be closed now, and a new bug against
linux-image-amd64/etc.. could
Package: initramfs-tools
Version: 0.142
Severity: important
I have a custom hook that omits a kernel module being built into an initrd
image.
Until kernels 6.6 and above, the hook does not seem to take effect.
The module is not omitted from initrd image...
On Linux kernel 6.5 and below the
Processing commands for cont...@bugs.debian.org:
> forward 1061525 https://savannah.gnu.org/bugs/index.php?65151
Unknown command or malformed arguments to command.
> block 1061525 by 1060256
Bug #1061525 [bcachefs-tools] does not boot from multi-device root filesystems
1061525 was not blocked by
Hi
I have one small last minute modification: don't use main, but release.
Overall I did not see any voices against the concept itself. Nor did I
see any counter proposals to the layout.
This means:
- The current sid branch will end with 6.6 and be cleaned up later
- No more merges will be done
After a test, the patch at
https://gitlab.freedesktop.org/drm/amd/-/issues/3122#note_2252835
is working fine on my side.
Many thanks to Diederik!
Le dim. 28 janv. 2024 à 15:00, Diederik de Haas
a écrit :
>
> Patrice,
>
> On Sunday, 28 January 2024 11:44:59 CET Linux regression tracking (Thorsten
Processing commands for cont...@bugs.debian.org:
> notfound 1061680 6.6.9
Bug #1061680 [src:linux] linux-image-armmp: Add modules to better support Tegra
Chromebooks
The source 'linux' and version '6.6.9' do not appear to match any binary
packages
No longer marked as found in versions
Processing control commands:
> tag -1 moreinfo
Bug #1061680 [src:linux] linux-image-armmp: Add modules to better support Tegra
Chromebooks
Added tag(s) moreinfo.
--
1061680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 moreinfo
On Sunday, 28 January 2024 17:23:15 CET Alex wrote:
> Various Tegra K1 Chromebooks exist such as the Acer CB5-311, which are
> capable of booting Debian with an unmodified kernel. However there are a
> few missing modules which are needed for full functionality.
>
> On
Patrice,
On Sunday, 28 January 2024 11:44:59 CET Linux regression tracking (Thorsten
Leemhuis) wrote:
> On 27.01.24 14:14, Salvatore Bonaccorso wrote:
> > In Debian (https://bugs.debian.org/1061449) we got the following
> > quotred report:
> >
> > On Wed, Jan 24, 2024 at 07:38:16PM +0100,
On Sun, Jan 28, 2024 at 11:06:53AM +0100, Steinar H. Gunderson wrote:
> I'm a bit unsure how this would work; unless you manually set
> rootfstype=bcachefs on the GRUB command line, I think this is autodetected
> from fstype (in klibc-utils), which doesn't understand bcachefs right now?
On 27.01.24 14:14, Salvatore Bonaccorso wrote:
>
> In Debian (https://bugs.debian.org/1061449) we got the following
> quotred report:
>
> On Wed, Jan 24, 2024 at 07:38:16PM +0100, Patrice Duroux wrote:
>>
>> Giving a try to 6.7, here is a message extracted from dmesg:
>> [4.177226]
Processing commands for cont...@bugs.debian.org:
> forwarded 1061449
> https://lore.kernel.org/regressions/zbub0ywxeet3y...@eldamar.lan/T/#u
> https://gitlab.freedesktop.org/drm/amd/-/issues/3122
Bug #1061449 [src:linux] linux-image-6.7-amd64: a boot message from amdgpu
Changed Bug
Package: klibc-utils
Version: 2.0.12-1
Severity: normal
Tags: upstream patch
Hi,
fstype should autodetect bcachefs, not the least because bcachefs filesystems
may require other treatment of UUID mounts (#1060411, #1061525). I've attached
a simple patch.
-- System Information:
Debian Release:
On Wed, Jan 10, 2024 at 09:34:18PM +0100, antonio wrote:
> The problem is in the file "/usr/share/initramfs-tools/scripts/functions" and
> depends on the "get_fstype" and "resolve_device" functions that cannot locate
> or determine the file system (since bcachefs uses the form
>
Hi John,
On Sun, Jan 28, 2024 at 12:43:33AM -0800, John Johansen wrote:
> On 12/30/23 20:24, Mathias Gibbens wrote:
> > On Sat, 2023-12-30 at 16:44 +0100, Salvatore Bonaccorso wrote:
> > > John, did you had a chance to work on this backport for 6.1.y stable
> > > upstream so we could pick it
On 12/30/23 20:24, Mathias Gibbens wrote:
On Sat, 2023-12-30 at 16:44 +0100, Salvatore Bonaccorso wrote:
John, did you had a chance to work on this backport for 6.1.y stable
upstream so we could pick it downstream in Debian in one of the next
stable imports? Cherry-picking 1cf26c3d2c4c
18 matches
Mail list logo
