Am 02.06.2022 23:26, schrieb Markus Kolb:
Am 2. Juni 2022 13:42:54 UTC schrieb Markus Kolb :
[...]
https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
https://salsa.debian.org/kernel
Am 2. Juni 2022 13:42:54 UTC schrieb Markus Kolb :
>Because the kernel.org 5.10.113 with my stripped down config is running
>successful,
>I've rebuilt this kernel.org 5.10.113 with the Debian config
>/boot/config-5.10.0-14-amd64 via make oldconfig.
>There are some difference
Am 02.06.2022 17:27, schrieb Ben Hutchings:
On Thu, 2022-06-02 at 15:42 +0200, Markus Kolb wrote:
[...]
there is introduced the kernel config option
INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF
but it is not handled anywhere in the code.
It is handled implicitly. When that config symbol is enabled
Because the kernel.org 5.10.113 with my stripped down config is running
successful,
I've rebuilt this kernel.org 5.10.113 with the Debian config
/boot/config-5.10.0-14-amd64 via make oldconfig.
There are some differences between kernel.org and Debian in the config,
I've put the config diff bug-1
Am 01.06.2022 13:34, schrieb Diederik de Haas:
On Wednesday, 1 June 2022 13:23:26 CEST Diederik de Haas wrote:
The current version in Sid/Unstable is 5.17.11-1 and it would be
useful if
you could test that as well.
In the screenshot you sent to the bug report, I saw mentions of an USB
hub.
Package: src:linux
Version: 5.10.113-1
Severity: important
Dear Maintainer,
I've updated an older typewriter computer from Stretch to Buster and
from there to Bullseye.
The kernel linux-image-4.19.0-20-amd64 from Buster works.
This one is used at the moment for reportbug!
But anything from the
David Miller wrote on 03.05.2012 07:11:
From: Markus Kolb
Date: Thu, 03 May 2012 06:57:39 +0200
I'll build it during next rainy day and will report its success
after some usage ;-)
Thank you.
Works without any problem for me.
So maybe this patch will be included in the official ke
David Miller schrieb:
>From: Bjørn Mork
>Date: Thu, 26 Apr 2012 14:35:10 +0200
>
>> The same comments as for v1 regarding testing applies. This is build
>> tested only. Should go through some functional testing before being
>> applied.
>
>Well? Is anyone gonna test this?
I'll build it duri
On Wed, 11 Jan 2012 11:35:16 +0100, Oliver Neukum wrote:
Am Mittwoch, 11. Januar 2012, 11:29:57 schrieb Markus Kolb:
Is it really a broken union descriptor?
There is all information but the original cdc_ether code can only
handle union descriptor which starts with 0.
That is something e.g. the
On Wed, 11 Jan 2012 09:44:03 +0100, Oliver Neukum wrote:
Am Mittwoch, 11. Januar 2012, 09:36:56 schrieb Iker Salmón San
Millán:
2012/1/11 Bjørn Mork
> if you have the patience to test yet-another-patch.
>
>
> Bjørn
>
Yes, I do, but:
2012/1/11 Oliver Neukum said:
>You are trying something sub
Package: linux-image-2.6.16-1-686
Version: 2.6.16-12
Followup-For: Bug #361197
I've no sound, too. It is very boring ;(
__
ACPI: PCI Interrupt :00:08.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ
5
never read ISV3 and ISV4 from AC'97
ACPI: PCI interrupt for device :00:08.0 disable
Package: initrd-tools
Version: 0.1.80
Severity: important
I've called mkinitrd -o initrd.img in /boot directory and no initrd.img
is created there.
I've seen with mkinitrd -k ... that the image file is created in the
mkinitrd working directory /tmp/mkinitrd.../initrd/
With absolut outfile definiti
Package: kernel
Severity: serious
Tags: sarge, sid
Hello,
I get a strange behavior from time to time when running xMule on a Linux
kernel.
At the moment it is
Linux angus 2.4.26-1-686 #1 Sat May 1 18:04:05 EST 2004 i686 GNU/Linux
2.6.5-4
But I've seen this with 2.4.x kernels before, too.
xMule is
13 matches
Mail list logo
