Bug#925891: AMD/ATI Carrizo driver incorrectly detected

unmerge 925891 retitle 925891 AMD/ATI Carrizo driver incorrectly detected? thanks Now making the incorrect driver detection a separate issue. All I know is with that minimal install, it somehow assumes the correct driver is present, or it is, but it uses it wrong. See also

Processed: AMD/ATI Carrizo driver incorrectly detected

Processing commands for cont...@bugs.debian.org: > unmerge 925891 Bug #925891 [src:linux] Add nomodeset kernel parameter for recovery boot grub entry Bug #926149 [src:linux] Add nomodeset kernel parameter for recovery boot grub entry Disconnected #925891 from all other report(s). > retitle

Processed (with 2 errors): Re: Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

Processing commands for cont...@bugs.debian.org: > clone 926149 -1 Bug #926149 [src:linux] AMD: Add nomodeset kernel parameter to avoid black screen Bug #925891 [src:linux] Debian Black Screen of Death worse than Microsoft's Blue Screen of Death Failed to clone 926149: Bug is marked as being

Bug#926149: AMD: Add nomodeset kernel parameter to avoid black screen

clone 926149 -1 retitle -1 [AMD/ATI] Carrizo driver incorrectly detected retitle 926149 Add nomodeset kernel parameter for recovery boot grub entry thanks > "BH" == Ben Hutchings writes: BH> However it might be reasonable to add "nomodeset" to the command line BH> in GRUB's "recovery" boot

Bug#926483: marked as done (FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major')

Your message dated Sun, 07 Apr 2019 01:18:02 +0100 with message-id and subject line Re: Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major' has caused the Debian Bug report #926483, regarding FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to

release-notes for buster and the kernel

Dear kernel team, I am reaching out to you as I help to coordinate this release's release-notes. In most release-notes in the past, there have been words about the kernel. For buster, is there anything that is worth mentioning in the notes? We already mention that AppArmor is pulled in via

nfs-utils_1.3.4-2.5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Apr 2019 18:30:39 +0200 Source: nfs-utils Architecture: source Version: 1:1.3.4-2.5 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Bernd Zeimetz Closes: 895381 Changes:

Processing of nfs-utils_1.3.4-2.5_source.changes

nfs-utils_1.3.4-2.5_source.changes uploaded successfully to localhost along with the files: nfs-utils_1.3.4-2.5.dsc nfs-utils_1.3.4-2.5.debian.tar.xz nfs-utils_1.3.4-2.5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#895381: marked as done (rpc.gssd: WARNING: handle_gssd_upcall: failed to find uid in upcall string 'mech=krb5')

Your message dated Sat, 06 Apr 2019 16:49:01 + with message-id and subject line Bug#895381: fixed in nfs-utils 1:1.3.4-2.5 has caused the Debian Bug report #895381, regarding rpc.gssd: WARNING: handle_gssd_upcall: failed to find uid in upcall string 'mech=krb5' to be marked as done. This

Bug#926533: linux-image-armmp-lpae: Fail to mount cryptsetup device: missing aes-xts-plain64 cipher

Package: linux-image-armmp-lpae Version: 4.19+104 Severity: normal Dear Maintainer, after upgrading from 4.9.144-3 to 4.19+104 I am not able to mount cryptsetup devices anymore. # cryptsetup luksOpen /dev/lvm-foo/crypto foo Enter passphrase for /dev/lvm-foo/crypto: device-mapper: reload

Bug#926261: closed by Ben Hutchings (Re: Bug#926261: linux-image-4.19.0-4-amd64: fan continiously spinning above 6900 RPM after resume on lenovo carbon x1 thinkpad with isa adap

Thank you, Bjørn. This regression bug is annoying, it happens at least once per day. I think that Debian instead of hiding/closing such bug will be push more on upstream or try fix by themselves if Debian developers will be Lenovo Thinkpad Carbon X1 owners. :) Karol ‐‐‐ Original Message

Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'

major(dev) is defined as a macro in which is provided by libc6-dev. I don't see that listed as an explicit build dependency, so it's conceivable that it might be present in some build environments but not in others. The configure script tests for it, potentially leading to #define

Re: Why don't we have linux-5.0 instead of 4.19.0-4 which is the running kernel in Debian 'buster' i.e. testing ?

❦ 6 avril 2019 02:14 +00, shirish शिरीष : > Currently we are using 4.19.0-4 according to the lastest updated > systems on buster . > > $ uname -r > 4.19.0-4-amd64 > > I see that 4.20 has been taken out of the archive and the 5.0 is there > but in experimental - > > $ apt-cache policy