On May 5, 2020 7:51:38 AM GMT-03:00, Ben Hutchings wrote:
>On Tue, 2020-05-05 at 07:23 -0300, Rogério Brito wrote:
>> Package: src:linux
>> Version: 5.6.7-1
>> Severity: wishlist
>>
>>
>> Hi Ben and others.
>>
>> Can the staging (or the more mature Samsung) exfat be enabled? It
>would
>> surely
Hi
It looks like there is a patch available that fixes the issue:
https://patchwork.kernel.org/patch/9757475/
Maybe that can be applied to the current Debian kernel as well.
Erik
signature.asc
Description: This is a digitally signed message part
Thanks Raymond for your quick and accurate answer. Fortunately, I am in a much
better position than what you describe in your blog entry, I had kernel n-1
and n installed, when trying to install n+1.
I removed my oldest kernel version (n-1) which resolved the issue. I shold
have created a large
> From: Ben Hutchings
> Sent: Saturday, May 9, 2020 5:20 PM
>
> On Thu, 2020-05-07 at 14:23 +0100, Pete Batard wrote:
> [...]
>
> > If Debian 11 was planning to continue to use a 4.x kernel, I could see
> > some point in splitting the patch and ensuring, so that it *might* be
> > easier to main
Source: linux
Version: 5.6.7-1
Severity: wishlist
It's very difficult to write architecture independent code in Debian for
image-generation and other kernel-related tasks due to missing meta packages
that can be used. For example:
- in image generation code, we need to have a hardcoded list of ke
On Sun, 2020-05-10 at 15:50 +0200, Rainer Dorsch wrote:
> Thanks Raymond for your quick and accurate answer. Fortunately, I am in a
> much
> better position than what you describe in your blog entry, I had kernel n-1
> and n installed, when trying to install n+1.
>
> I removed my oldest kernel
Dear developers,
there is a little thing, I want to correct: The described behaviour also
appears on my Acer Notebook, which is same way partitioned, but is running 64-
bit (amd64). Same kernel-version, same behaviour. So it might be a problem in
the sources.
Thank you for your help.
Best gega
Package: src:linux
Version: 4.19.118-2
Severity: normal
Dear Maintainer,
it is likely that this is not a direct kernel issue, but it worked with the -8
version without any problems. If you can advice where to look for the issue,
that would be already helpful.
It is weird that mkinitramfs repor
Package: src:linux
Version: 5.6.7-1
Severity: wishlist
Hi,
can you please enable CONFIG_INTEL_TXT=y on x86? I am in the process
of packaging tboot for Debian (#803180) and it would be nice if users
would not need to rebuild their kernels for this.
I have used Debian kernels rebuilt with CONFIG_
On 5/10/20 3:27 PM, Ben Hutchings wrote:
>> In any case, the kernel package now fails to build due to a missing symbol
>> in the
>> Infiniband core driver (see below). A simple workaround is to disable
>> Infiniband
>> support which allows me to build the kernel package normally (which I did and
Your message dated Sun, 10 May 2020 14:38:34 +0100
with message-id
and subject line Re: Bug#960181: pigz: abort: write error on (No space
left on device)
has caused the Debian Bug report #960181,
regarding pigz: abort: write error on (No space left on device)
to be marked as done.
This means t
Source: linux
Version: 5.6.7-1
Hi,
Please enable CONFIG_BCM2711_THERMAL (Support for thermal sensors on
Broadcom BCM2711 SoCs). This is used by the Raspberry Pi 4.
example output:
# cat /sys/class/thermal/thermal_zone0/temp
41868
- Lucas
On 2020-05-10 4:59 a.m., Rainer Dorsch wrote:
It is weird that mkinitramfs reports no space left on device, but df does not confirm
this. So it might be "another" device (like initramfs?). I am aware that I
include a virtualbox module with dkms
df does, in a fashion confirm it. It shows 91% in
On Sun, 2020-05-10 at 12:38 +0200, John Paul Adrian Glaubitz wrote:
> (Please keep me CC'ed, I'm not subscribed to debian-kernel@)
>
> Hi!
>
> src:linux hasn't been building on sh4 in the past for a while now due to
> objdump
> locking up during the build.
>
> However, this problem has recently
On 10/05/20 at 14:22 +0200, Bjørn Mork wrote:
> Bjørn Mork writes:
>
> > Note that I found that I had to remove the cma=xx option raspi-firmware
> > wants to put into the cmdline.txt. This messed up mailbox access to the
> > firmware, and took several drivers/devices with it in the fall. Don't
Bjørn Mork writes:
> Note that I found that I had to remove the cma=xx option raspi-firmware
> wants to put into the cmdline.txt. This messed up mailbox access to the
> firmware, and took several drivers/devices with it in the fall. Don't
> think the SD card was one one them. But still worth t
(Please keep me CC'ed, I'm not subscribed to debian-kernel@)
Hi!
src:linux hasn't been building on sh4 in the past for a while now due to objdump
locking up during the build.
However, this problem has recently vanished, I assume maybe because the bug was
fixed in binutils.
In any case, the kern
Lucas Nussbaum writes:
> On 09/05/20 at 20:44 +0200, Bjørn Mork wrote:
>> Please enable CONFIG_PCIE_BRCMSTB on arm64.
>>
>> The Raspberry Pi 4 has a VL805 xhci controller connected to the
>> PCIe bus on the SoC. All USB ports are connected to this controller.
>> CONFIG_PCIE_BRCMSTB is therefore
Hi Bjørn,
On 09/05/20 at 20:44 +0200, Bjørn Mork wrote:
> Please enable CONFIG_PCIE_BRCMSTB on arm64.
>
> The Raspberry Pi 4 has a VL805 xhci controller connected to the
> PCIe bus on the SoC. All USB ports are connected to this controller.
> CONFIG_PCIE_BRCMSTB is therefore necessary for USB su
19 matches
Mail list logo
