Package: linux-image-6.12.1+debian+tj
Followup-For: Bug #1076372
X-Debbugs-Cc: tj.iam...@proton.me
This patch ought to enable forcing MDTS for *all* NVME devices. Untested
but applies on master and back to v6.3.7 at least, and builds for
master.
diff --git a/drivers/nvme/host/core.c b/drivers
Package: linux-image-6.12.1+debian+tj
Followup-For: Bug #1076372
X-Debbugs-Cc: tj.iam...@proton.me
I cannot confirm if this tool will work for forcing Gen4 on the Gen5
link since I see some reports that those trying it failed - but I do
suspect they were not using the correct command-line
Package: linux-image-6.12.1+debian+tj
Followup-For: Bug #1076372
X-Debbugs-Cc: tj.iam...@proton.me
I've done some investigative work with the logs and the lspci reports in
an attempt to narrow down potential causes and identify relevant clues.
1. Comparison of the Lexar NM790 PCIe configur
Package: linux-image-6.11.5+debian+tj
Version: 6.11.5-265
Followup-For: Bug #1076372
X-Debbugs-Cc: tj.iam...@proton.me
Thanks for the response - very useful.
I suspect the cause may be a conjunction of several issues that in
themselves are relatively minor.
Observations:
1. That Lexar has the
Package: linux-image-6.11.5+debian+tj
Followup-For: Bug #1076372
X-Debbugs-Cc: tj.iam...@proton.me
Following up from the kernel team discussion this evening that I only
caught the tail-end of I've reviewed this report and have the following
suggestions and observations.
It would be good t
Package: initramfs-tools
Version: 0.143~tj01
Severity: normal
X-Debbugs-Cc: tj.iam...@proton.me
The current ACPI DSDT code cannot possibly work.
1. The path DSDT.aml is stored in is not searched by the kernel
2. Kernel will not over-ride an ACPI table after PID 1 starts
3. File needs to be in an
The reporter "retired" the PC but directly replied to me; copying in for
completeness.
--- Forwarded Message ---
From: Joseph Maher
Date: On Wednesday, 17 July 2024 at 07:22
Subject: Re: Bug#989229: grub-install: warning: Cannot read EFI Boot* variables.
To: Tj
> Th
Source: linux
Followup-For: Bug #989229
X-Debbugs-Cc: tj.iam...@proton.me
Control: tag -1 moreinfo
This is in all probability a system (manufacturer's) firmware bug. The
kernel is doing what it is designed to do; that is, try to recover from
the system's UEFI Runtime Services causing a Page Fault.
Package: linux-image-6.9.7+debian+tj
Followup-For: Bug #1075713
X-Debbugs-Cc: tj.iam...@proton.me
It does help to include the references!
[0] https://gitlab.freedesktop.org/xorg/xserver/-/issues/1714
Package: linux-image-6.9.7+debian+tj
Followup-For: Bug #1075713
X-Debbugs-Cc: tj.iam...@proton.me
This is best fixed in xorg-server. I've opened an upstream issue [0] and
sent the patch to xorg-devel@.
In the meantime here's a patch tested with kernel v6.8.12 and v6.9.7
using
On Monday, 15 July 2024 at 10:22, Thomas Zimmermann wrote:
> We should definitely get your patch into the Xorg upstream.
Working on that now.
On Monday, 15 July 2024 at 07:44, Thomas Zimmermann wrote:
> > See hw/xfree86/fbdevhw/fbdevhw.c::fbdev_open()
> >
> > https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/hw/xfree86/fbdevhw/fbdevhw.c?ref_type=heads#L381
>
>
> Amazing debugging skills!
>
> The patch that causes the regression
Package: linux-image-6.9.7+debian+tj
Followup-For: Bug #1072004
X-Debbugs-Cc: tj.iam...@proton.me
I've completed 10 successful passes of the autopkgtest reproducer with the
proposed
patch in the kernel bugzilla from Dominique Martinet on current
mainline, so with luck that might squeeze
The recent commits to add the parent device path broke Debian's kvm based QA
workers for testing installer ISOs after a kernel upgrade from v6.8.12 to
v6.9.7. For the details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075713
It took some time to track it down since the superficial sym
Package: linux-image-6.9.7+debian+tj
Followup-For: Bug #1075713
X-Debbugs-Cc: tj.iam...@proton.me
After reverting the recent sysfb commits:
linux$ git l -n 15
e932a4281dfd4 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Set
firmware-framebuffer parent device"
c16bbb2e6863d 202
Source: linux
Followup-For: Bug #1075713
X-Debbugs-Cc: tj.iam...@proton.me debian-b...@lists.debian.org
I've inspected the arch-latest amd64 ISO from:
https://get.debian.org/images/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
It is missing drivers/gpu/drm/qxl/qxl.
sort -u
version 6.7.0-rc5+debian+tj
version 6.7.1+debian+tj
version 6.7.4+debian+tj
version 6.8.0+debian+tj
crypto algo self-tests 'alg: ecdh-nist-p256: test failed on vector 2, err=-14
-14 is "EFAULT 14 / Bad address */
and the log shows
Modules linked in: ecdh_generic(+) ...
whe
Source: linux
Severity: normal
Working with a Debian user in Matrix channel #Debian where they report
that the TPM hardware random number generator that was available in
v5.10* series is missing from v6.1* series for the amd64 kernel.
After examining the Kconfig options and the Debian configs I f
atically linked and that worked as expected, switching into graphic
mode, displaying the Ubuntu usplash screen, and giving me a full-screen
1024x768 tty.
TJ.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
in the boot process the driver
module is loaded, and where/how the options are being passed to it.
A reference to a kernel source file where that occurs would assist me
tremendously.
TJ.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
structure.
So, the answer seems to be, if you need specific framebuffer support at
boot-time you'll need to build the kernel with i810, intel_agp, agpgart,
drm, i810 all configured to statically link using the kernel build tool:
make config
TJ.
ld the kernel with i810, intel_agp, agpgart,
drm, i810 all configured to statically link using the kernel build tool:
make config
TJ.
22 matches
Mail list logo
