Processing commands for cont...@bugs.debian.org:
> reassign 980784 src:linux 5.10.4-1
Bug #980784 [linux-image-5.10.0-1-amd64] pp_dpm_mclk Always at Maximun gpu
memory clock frecuency
Bug reassigned from package 'linux-image-5.10.0-1-amd64' to 'src:linux'.
No longer marked as found in versions
Processing control commands:
> block 977642 by -1
Bug #977642 [raspi-firmware] 5.10 kernel needs disable_fw_kms_setup=1
977642 was not blocked by any bugs.
977642 was not blocking any bugs.
Added blocking bug(s) of 977642: 980785
--
977642:
In case someone else runs into this:
I have an encrypted LVM partition that contains mount points for root, home,
swap.
Apparently cryptsetup cannot see through the LVM to find the rootfs, and hence
the
error.
I added the `initramfs` option in /etc/crypttab and updated initramfs for
safety,
fixed -1 4.19.160-2
fixed -1 5.10.4-1
thanks
buster:
I just tested with
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.7.0-live+nonfree/amd64/iso-hybrid/
and I was able to connect to two different WPA2 secured access points.
Running Linux was 4.19.0-13-amd64
Package: firmware-nonfree
When an end user want to install firmware for the wireless cards, they
need to know which chip is build into their computer, to get the
correct Debian package name.
If Debian would provide a meta package for all wireless/wlan firmware
packages, the end user only need
Package: src:linux
Version: 5.10.5-1
Followup-For: Bug #980750
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
thank you very much to the debian dev team and the BTS for the speed with which
they diagnosed and solved the problem.
I hope that this solution will be operational and will bring a
Hi Alain,
alain writes:
> I think I finally figured it out, Nicholas.
>
> Here is the report that you asked me (as root), nomodeset enabled
> otherwise, I don't start.
>
> I will submit the idea of vincent (and you too, nicholas) in another bug
> report for the kernel.
Thank you for your
This was probably because of an dying microSD Card where the kernel was
installed.
Because 2 months later also the 4.9.0-13 kernel on hold had boot
problems. [1]
After reinstalling Debian Stretch with 4.9.0-14 on an SSD instead of
microSD (except u-boot) everything runs fine.
[1]
Processing commands for cont...@bugs.debian.org:
> close 979856 5.10.9-1
Bug #979856 [src:linux] linux-image-5.10.0-1-amd64: 5.10.0-1 kernel does not
have the AMDGPU 'DCN 3.0 family' option turned on for Navi 21 support
The source 'linux' and version '5.10.9-1' do not appear to match any binary
Your message dated Thu, 21 Jan 2021 16:08:03 +0100
with message-id
and subject line Re: Bug#980750: linux-image-5.10.0-1-amd64: no compatibility
with new AMD RX 6800 generation graphics cards
has caused the Debian Bug report #980750,
regarding linux-image-5.10.0-1-amd64: no compatibility with
Source: linux
Source-Version: 5.10.9-1
Hi,
On Thu, Jan 21, 2021 at 03:35:15PM +0100, alain wrote:
> Package: src:linux
> Version: 5.10.5-1
> Severity: grave
> Tags: d-i
> Justification: renders package unusable
> X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
>
> hello to all .
>
> this post to
Processing commands for cont...@bugs.debian.org:
> severity 980750 important
Bug #980750 [src:linux] linux-image-5.10.0-1-amd64: no compatibility with new
AMD RX 6800 generation graphics cards
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you
Package: src:linux
Version: 5.10.5-1
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
hello to all .
this post to ask you for help .
it seems indeed that the kernel 5.10.0-1 sid is not yet ready to support the
latest amd graphics cards
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 20 Jan 2021 17:40:43 +0100
Source: linux
Architecture: source
Version: 5.10.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 956951 964845
On Thursday, January 21, 2021 7:31:57 AM EST Bastian Blank wrote:
>> As discussed on the mailing list(s), I'm looking into making a udeb for
>> firmware-ath9k-htc with kernel-wedge.
> You missunderstood something. All the firmware stuff is _only_ shipped
> as deb, not as udeb.
This mail from Ben
Your message dated Thu, 21 Jan 2021 14:10:10 +
with message-id
and subject line Bug#980180: fixed in linux 5.10.9-1
has caused the Debian Bug report #980180,
regarding Missing support for Intel Elkhart Lake Ethernet
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 21 Jan 2021 14:10:10 +
with message-id
and subject line Bug#980214: fixed in linux 5.10.9-1
has caused the Debian Bug report #980214,
regarding linux-image-5.10.0-1-arm64: please enable
CONFIG_CRYPTO_NHPOLY1305_NEON
to be marked as done.
This means that you claim
Your message dated Thu, 21 Jan 2021 14:10:10 +
with message-id
and subject line Bug#980114: fixed in linux 5.10.9-1
has caused the Debian Bug report #980114,
regarding Please enable CONFIG_MFD_AXP20X_I2C on arm64
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 21 Jan 2021 14:10:10 +
with message-id
and subject line Bug#964845: fixed in linux 5.10.9-1
has caused the Debian Bug report #964845,
regarding Please enable CONFIG_SUSPEND in the cloud image kernel
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 21 Jan 2021 14:10:10 +
with message-id
and subject line Bug#973985: fixed in linux 5.10.9-1
has caused the Debian Bug report #973985,
regarding linux: Please enable CONFIG_SERIAL_8250_LPSS
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 21 Jan 2021 14:10:10 +
with message-id
and subject line Bug#972221: fixed in linux 5.10.9-1
has caused the Debian Bug report #972221,
regarding linux: Please enable CONFIG_GPIO_PCA953X_IRQ on armhf
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 21 Jan 2021 14:10:10 +
with message-id
and subject line Bug#970699: fixed in linux 5.10.9-1
has caused the Debian Bug report #970699,
regarding linux: Enable amd_energy driver
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 21 Jan 2021 14:10:09 +
with message-id
and subject line Bug#956951: fixed in linux 5.10.9-1
has caused the Debian Bug report #956951,
regarding CONFIG_DRM_VC4_HDMI_CEC is not enabled
to be marked as done.
This means that you claim that the problem has been dealt with.
I think I finally figured it out, Nicholas.
Here is the report that you asked me (as root), nomodeset enabled
otherwise, I don't start.
I will submit the idea of vincent (and you too, nicholas) in another bug
report for the kernel.
boot.log.xz
Description: application/xz
On Thu, Jan 21, 2021 at 06:28:16AM -0500, John Scott wrote:
> As discussed on the mailing list(s), I'm looking into making a udeb for
> firmware-ath9k-htc with kernel-wedge.
You missunderstood something. All the firmware stuff is _only_ shipped
as deb, not as udeb.
> To avoid clashing with the
Processing control commands:
> close 968181 5.10.5-1
Bug #968181 {Done: Ryutaroh Matsumoto }
[src:linux] missing DRI/DRM support on Raspberry Pi
Ignoring request to alter fixed versions of bug #968181 to the same values
previously set
Bug #968181 {Done: Ryutaroh Matsumoto }
[src:linux] missing
Processing control commands:
> close 968181 5.10.5-1
Bug #968181 [src:linux] missing DRI/DRM support on Raspberry Pi
Marked as fixed in versions linux/5.10.5-1.
Bug #968181 [src:linux] missing DRI/DRM support on Raspberry Pi
Marked Bug as done
> close 968188 5.10.5-1
Bug #968188 [src:linux]
Control: close 968181 5.10.5-1
Control: close 968188 5.10.5-1
968181 missing DRI/DRM support on Raspberry Pi
968188 4K display resolution is not recognized with Raspberry Pi 4B
I confirm that vc4.ko in 5.10.5-1 can show 4K output and it provides
/dev/dri/card0.
The gdm3 display manager and
Processing control commands:
> affects -1 src:open-ath9k-htc-firmware
Bug #980746 [firmware-nonfree] remove ath9k_htc, provided by libre package
firmware-ath9k-htc
Added indication that 980746 affects src:open-ath9k-htc-firmware
--
980746:
Package: firmware-nonfree
Version: 20160110-1
Severity: normal
Control: affects -1 src:open-ath9k-htc-firmware
As discussed on the mailing list(s), I'm looking into making a udeb for
firmware-ath9k-htc with kernel-wedge. Although I've not delved too much into
it yet, I anticipate that being able
Processing commands for cont...@bugs.debian.org:
> reassign 980729 src:linux 5.9.15-1~bpo10+1
Bug #980729 [linux-source-5.9] linux-source-5.9: 5.9.15 crashes regularly with
memory/paging related messages
Bug reassigned from package 'linux-source-5.9' to 'src:linux'.
No longer marked as found in
Processing commands for cont...@bugs.debian.org:
> close 977645 5.10.5-1
Bug #977645 [src:linux] 5.10.x Debian kernel does not boot on raspi 4 with ext4
rootfs and sdcard
Ignoring request to alter fixed versions of bug #977645 to the same values
previously set
Bug #977645 [src:linux] 5.10.x
On Thu, Jan 21, 2021 at 11:08:27AM +0900, Ryutaroh Matsumoto wrote:
> Control: tags -1 + fixed-upstream
>
> Self-compiled 5.10.9 does not show this reported symptom,
> and I assume this is fixed-upstream. Ryutaroh
5.10.9-1 is awaiting currently in NEW for beeing processed. Once that
enters
> On the other hand, vc4.ko gives completely garbled screen to my 4K HDMI
> display, and disable_fw_kms_setup=1 does not help unlike
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977642
I am sorry, with disable_fw_kms_setup=1, vc4.ko works fine.
Without disable_fw_kms_setup=1, vc4.ko gives
34 matches
Mail list logo
