Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 03 Dec 2016 21:20:01 +
Source: firmware-nonfree
Binary: firmware-linux firmware-linux-nonfree firmware-amd-graphics
firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211
firmware-cavium firmware-in
Processing control commands:
> reassign -1 firmware-amd-graphics
Bug #844605 [linux] X11 segfault with AMD GPU since 4.8.x / Firmware issue
Bug reassigned from package 'linux' to 'firmware-amd-graphics'.
No longer marked as found in versions linux/4.8.5-1 and 4.8.7-1.
Ignoring request to alter fix
Control: reassign -1 firmware-amd-graphics
Control: forcemerge -1 838858
On Thu, 17 Nov 2016 16:04:51 +0100 Patrick Matthäi
wrote:
[...]
> dmesg reports a firmware missmatch:
[...]
> [3.262451] radeon :01:00.0: firmware: failed to load
> radeon/bonaire_k_smc.bin (-2)
> [3.262454] rad
Processing control commands:
> severity -1 important
Bug #842458 [src:linux] upgrade-reports: After dist-upgrade from jessie to
testing, kernel doesn't load, not a single message on screen
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #842458 [src:linux] upgrade-reports: After
Control: severity -1 important
Control: tag -1 moreinfo
On Sat, 29 Oct 2016 15:10:01 +0300 Pyotr wrote:
[...]
>* What was the outcome of this action?
> System doesn't load. Instead of "Loading initramfs" just blinking '_'.
That message is no longer printed by default, so this doesn't
Nathan, I'm sorry we didn't answer this report much sooner.
Have you tried upgrading to a newer kernel version, and did that
resolve the problem? The latest version in testing is now 4.8.7-1.
If the latest version has the same problem, does adding the kernel
parameter 'nomodeset' allow the syste
Processing commands for cont...@bugs.debian.org:
> severity 834386 important
Bug #834386 [src:linux] linux-image-4.6.0-1-amd64: Locks hard on boot.
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
834386: http://bugs.debi
Processing commands for cont...@bugs.debian.org:
> tags 834386 + moreinfo
Bug #834386 [src:linux] linux-image-4.6.0-1-amd64: Locks hard on boot.
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
834386: http://bugs.debian.org/cgi-bin/bugreport
On Thu, 10 Nov 2016 21:45:54 +0800 Sharuzzaman Ahmat Raslan wrote:
> Hi Ben,
>
> I'm using Testing, and the package is not in testing yet.
>
> I have seen that the migration to testing was blocked by block-udeb..
>
> Hopefully the package can be migrated to testing soon.
testing now has 4.8.7-
The firmware-nonfree package is non-free because:
- No real source code is provided for the firmware
- Some licences do not permit creation of derivatives, or reverse-
engineering
- Some licences only permit use with a particular manufacturer's
products
- Some licences require presentation of a
Processing commands for cont...@bugs.debian.org:
> tags 842458 + sid stretch
Bug #842458 [src:linux] upgrade-reports: After dist-upgrade from jessie to
testing, kernel doesn't load, not a single message on screen
Added tag(s) stretch and sid.
> tags 770052 + sid stretch
Bug #770052 [src:xvt] xvt:
Ian Campbell writes:
> On Tue, 2016-12-06 at 14:17 +, Ben Hutchings wrote:
>>
>> But perhas we should more explicit in this message, e.g.:
>>
>> "This breaks (e)glibc 2.13 and earlier, which may still be installed in
>> a chroot or container environment based on Debian 7, RHEL/CentOS 6 or
>
Hi Salvatore
Thanks for your help.
Am 2016-12-04 um 06:42 schrieb Salvatore Bonaccorso:
> No that actually is enought, since the commit is is is in upstream
> version 4.9-rc1 and thus already included in the most recent package
> from experimental.
>
> Thanks for testing that. So it looks might
On Wed, 2016-12-07 at 03:16 +0800, 積丹尼 Dan Jacobson wrote:
> Hello, do I just purge these?
> # aptitude search ~o~i~nfirm
> i firmware-amd-graphics
> i firmware-linux
> i firmware-linux-nonfree
> i firmware-misc-nonfree
> i firmware-realtek
> Won't my computer stop working?
Don't remove
Hello, do I just purge these?
# aptitude search ~o~i~nfirm
i firmware-amd-graphics
i firmware-linux
i firmware-linux-nonfree
i firmware-misc-nonfree
i firmware-realtek
Won't my computer stop working?
Hi there,
I sent you an email about some resources on your site, but never heard
back. Is there someone else I should talk to about fixing them?
Thanks,
On Mon, Nov 7, 2016 at 5:33 PM, Catherine Trammell <
c.tramm...@sc-student.org> wrote:
> Hi,
>
> I was just checking out your website and noti
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 846783 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 822671 + cgroupfs-mount
Bug #822671 [initramfs-tools] in
Processing commands for cont...@bugs.debian.org:
> reopen 847154
Bug #847154 {Done: Ian Campbell } [linux-image-amd64]
linux-image-amd64: Disabling vsyscall interface may break docker run
Bug reopened
Ignoring request to alter fixed versions of bug #847154 to the same values
previously set
> tha
On Tue, 2016-12-06 at 14:17 +, Ben Hutchings wrote:
>
> But perhas we should more explicit in this message, e.g.:
>
> "This breaks (e)glibc 2.13 and earlier, which may still be installed in
> a chroot or container environment based on Debian 7, RHEL/CentOS 6 or
> earlier versions."
That's a
On Tue, 2016-12-06 at 10:02 +, Ian Campbell wrote:
> On Tue, 2016-12-06 at 12:56 +0900, Olaf Meeuwissen wrote:
> > You may want to add to the NEWS blurb that disabling the old 'virtual
> > syscall' interface can lead to crashes when trying to run a Docker
> > container. With upstream's docker-
Package: nfs-kernel-server
Version: 1:1.2.8-9
The systemd service unit file for `nfs-kernel-server` incorrectly
reports the service status as "active" even when the NFS server is *not*
running (e.g., empty exports file).
This causes scripts (e.g., Ansible) that use `systemctl status` to check
fo
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 05 Dec 2016 05:02:30 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-rc8 linux-doc-4.9 linux-manual-4.9
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9
libusbip-dev us
Package: src:linux
Severity: wishlist
In the past, admins could get dmesg output without running it as root,
but this is no longer possible:
* security,printk: Enable SECURITY_DMESG_RESTRICT, preventing non-root users
reading the kernel log by default (sysctl: kernel.dmesg_restrict)
(in ch
Your message dated Tue, 06 Dec 2016 10:02:11 +
with message-id <1481018531.4509.120.ca...@debian.org>
and subject line Re: Bug#847154: linux-image-amd64: Disabling vsyscall
interface may break docker run
has caused the Debian Bug report #847154,
regarding linux-image-amd64: Disabling vsyscall
24 matches
Mail list logo
