Processing commands for cont...@bugs.debian.org:
> Found 914517 linux-image-4.19.0-1-amd64-unsigned
Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset
is set
The source 'linux' and version 'linux-image-4.19.0-1-amd64-unsigned' do not
appear to match any binary
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Dec 2018 21:13:58 +
Source: linux-signed-amd64
Binary: kernel-image-4.19.0-0.bpo.1-amd64-di
nic-modules-4.19.0-0.bpo.1-amd64-di
nic-wireless-modules-4.19.0-0.bpo.1-amd64-di
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Dec 2018 21:13:58 +
Source: linux-signed-i386
Binary: kernel-image-4.19.0-0.bpo.1-686-di nic-modules-4.19.0-0.bpo.1-686-di
nic-wireless-modules-4.19.0-0.bpo.1-686-di
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 30 Dec 2018 21:13:58 +
Source: linux-signed-arm64
Binary: kernel-image-4.19.0-0.bpo.1-arm64-di
nic-modules-4.19.0-0.bpo.1-arm64-di
nic-wireless-modules-4.19.0-0.bpo.1-arm64-di
Package: src:linux
Version: 4.19.13-1
Severity: critical
Justification: breaks the whole system
System boots properly on kernel 4.18 but fails to boot with any versions
(buster sid) of 4.19.
It seems specific to this DELL computer as another laptop DELL is working
properly with 4.19. i did a
I intend to upload linux version 4.19.16-1 to unstable tomorrow
(Thursday 17th). Aside from the upstream stable updates, the pending
changes include:
* Bump ABI to 2
* ipv6: Consider sk_bound_dev_if when binding a socket to an address
(Closes: #918103)
* posix-cpu-timers: Unbreak timer
Processing commands for cont...@bugs.debian.org:
> severity 919498 important
Bug #919498 [src:linux] linux-image-4.19.0-1-amd64: Fails to boot. Inactive
(initramfs) prompt.'Gave up waiting for suspend/resume device'
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
On Wed, 2019-01-16 at 18:03 +1300, Richard Hector wrote:
> Sorry if I missed previous discussion on this.
>
> I seem to only see linux-image-4.19.0-0.bpo.1-amd64-unsigned (and the
> virtual package) for this version? Is that deliberate?
No. The signed packages are built from separate source
Hi,
I am Shivasharan and I work in megaraid_sas driver development team at
Broadcom.
We/Broadcom are trying to figure out the process to update inbox
megaraid_sas/mpt3sas drivers in Debian 9 GCA kernels.
I am not sure if this is the right mailing list to be querying regarding
this. If not, if
9 matches
Mail list logo