Bug#929098: linux-image-4.19.0-5-amd64: No graphics with Radeon Vega 1.0

Package: src:linux Version: 4.19.37-3 Severity: important Dear Maintainer, I upgraded to linux-image-4.19.0-5-amd64 from 4.19.0-4-amd64. Previously the system booted, loaded the driver module (I think amdgpu) and everything was fine. After the upgrade the boot process gets to about the point th

linux-signed-amd64_4.19.37+3_source.changes ACCEPTED into unstable

Mapping sid to unstable. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 15 May 2019 23:07:16 +0100 Source: linux-signed-amd64 Binary: kernel-image-4.19.0-5-amd64-di nic-modules-4.19.0-5-amd64-di nic-wireless-modules-4.19.0-5-amd64-di nic-shared-modules-4.19.0-5

Processing of linux-signed-amd64_4.19.37+3_source.changes

linux-signed-amd64_4.19.37+3_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_4.19.37+3.dsc linux-signed-amd64_4.19.37+3.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#929077: linux-image-4.19.0-4-amd64: cannot successfully resume from hibernate with nouveau driver unless I pass 'nomodeset'

Oh, and, for clarity: this did not happen before installing the non-free nouveau firmware.

Bug#929077: linux-image-4.19.0-4-amd64: cannot successfully resume from hibernate with nouveau driver unless I pass 'nomodeset'

Package: src:linux Version: 4.19.28-2 Severity: normal I'm running an x86_64 PC with an Nvidia GTX 960 (aka GM206). Using the nouveau driver. Running fully up-to-date buster. If I hibernate, on an attempted resume the system hangs up with black monitors. I can ping it, but I can not ssh in (the

linux-signed-i386_4.19.37+3_source.changes ACCEPTED into unstable

Mapping sid to unstable. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 15 May 2019 23:07:16 +0100 Source: linux-signed-i386 Binary: kernel-image-4.19.0-5-686-di nic-modules-4.19.0-5-686-di nic-wireless-modules-4.19.0-5-686-di nic-shared-modules-4.19.0-5-686-di

Processing of linux-signed-i386_4.19.37+3_source.changes

linux-signed-i386_4.19.37+3_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_4.19.37+3.dsc linux-signed-i386_4.19.37+3.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed (with 5 errors): bug 864320: multiple critical problems booting

Processing commands for cont...@bugs.debian.org: > clone 864320 -1 Bug #864320 [base] multiple critical problems booting Bug 864320 cloned as bug 929060 > reassign -1 initramfs-tools Bug #929060 [base] multiple critical problems booting Bug reassigned from package 'base' to 'initramfs-tools'. Igno

linux-signed-arm64_4.19.37+3_source.changes ACCEPTED into unstable

Mapping sid to unstable. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 15 May 2019 23:07:16 +0100 Source: linux-signed-arm64 Binary: kernel-image-4.19.0-5-arm64-di nic-modules-4.19.0-5-arm64-di nic-wireless-modules-4.19.0-5-arm64-di nic-shared-modules-4.19.0-5

bug 864320: multiple critical problems booting

clone 864320 -1 reassign -1 initramfs-tools retitle -1 update-initramfs silently failed to change \ initrd/conf/conf.d/cryptroot > 4. > > one of my goals is to set up a new drive as a backup -- with > accessibility fixed as much as possible -- in case there are > problems booting to my main drive

Processing of linux-signed-arm64_4.19.37+3_source.changes

linux-signed-arm64_4.19.37+3_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_4.19.37+3.dsc linux-signed-arm64_4.19.37+3.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)