Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

2015-05-06 Thread Ian Campbell
Control: submitter -1 Rick Thomas rbtho...@pobox.com On Wed, 2015-05-06 at 03:00 -0700, Rick Thomas wrote: OK, How will I identify the upload when I see it? The box is running Debian/Sid and I do regular updates. So presumably, I’ll see a “linux-image-3.16.0-4-armmp” package go by sometime

Processed: Re: Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

2015-05-06 Thread Debian Bug Tracking System
Processing control commands: submitter -1 Rick Thomas rbtho...@pobox.com Bug #782364 [src:linux] linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks Changed Bug submitter to 'Rick Thomas rbtho...@pobox.com' from 'Rick Thomas rbtho...@cube.rcthomas.org'

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

2015-05-06 Thread Rick Thomas
OK, How will I identify the upload when I see it? The box is running Debian/Sid and I do regular updates. So presumably, I’ll see a “linux-image-3.16.0-4-armmp” package go by sometime soon? And I’ll know I’ve got it when I see two /dev/rtc* devices? As for “rbtho...@cube.rcthomas.org” — I’m

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

2015-05-06 Thread Ian Campbell
On Sat, 2015-05-02 at 17:21 +0100, Ian Campbell wrote: We typically build RTCs statically (for this sort of reason) so it seems like the right thing for us to do here is to build both in. Which I've now done in SVN. Rick, please test the next upload. Also, Rick, I'm getting messages from my

Processed: limit source to linux, tagging 784344

2015-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' tags 784344 + pending Bug #784344 [src:linux] Buggy DTB causes imx53 SATA failure Added tag(s) pending. thanks

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

2015-05-06 Thread Rick Thomas
On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates I’ll keep an eye out for it. But I don’t have one of the cubox models without the battery-backed RTC, so I won’t be able to test that

Bug#759656: [PATCH] mmc: card: not access RPMB partition for normal read and write

2015-05-06 Thread Sebastian Andrzej Siewior
On 05/06/2015 03:06 PM, Ulf Hansson wrote: On 12 August 2014 at 06:01, Yunpeng Gao yunpeng@intel.com wrote: From: Chuanxiao Dong chuanxiao.d...@intel.com Sorry for the delay and thanks! ah thanks. Is it likely you go via my patches for mmc-utils in the new few days? Kind regards Uffe

Bug#734204: Please set CONFIG_ALIX and CONFIG_LEDS_GPIO

2015-05-06 Thread Bernhard Schmidt
Control: reassign -1 src:linux Control: found -1 3.16.7-ckt9-2 Hi, I have tested this on a current kernel, after setting CONFIG_ALIX=y and CONFIG_LEDS_GPIO=m it works just fine on an ALIX 2D3 filename: /lib/modules/3.16.0-4-586/kernel/drivers/leds/leds-gpio.ko alias:

Processed: Re: Please set CONFIG_ALIX and CONFIG_LEDS_GPIO

2015-05-06 Thread Debian Bug Tracking System
Processing control commands: reassign -1 src:linux Bug #734204 [linux-image-3.2.0-4-486] linux-image-3.2.0-4-486: Please set CONFIG_ALIX and CONFIG_LEDS_GPIO Bug reassigned from package 'linux-image-3.2.0-4-486' to 'src:linux'. No longer marked as found in versions linux/3.2.51-1. Ignoring

Bug#784546: linux: backport of intel/e1000e driver

2015-05-06 Thread Markus Schade
Package: linux Version: 3.16.7-ckt9-3~deb8u1 Severity: wishlist The new Skylake CPUs will come with the new Sunpoint PCH that also brings a new Intel i219 gigabit network chip. The current e1000e driver lacks support for these new NICs. Support for them was added in: commit

Bug#784579: linux-image-3.16.0-4-amd64: Boot process / DRM initialization causes blank console

2015-05-06 Thread Ben Hutchings
Control: retitle -1 [REGRESSION] vmwgfx black screen until X started On Wed, 2015-05-06 at 16:43 -0400, Markus Hamilton wrote: Package: src:linux Version: 3.16.7-ckt9-3~deb8u1 Severity: important The installation has been a Debian 7 system in a VMware Workstation 11 environment which runs

Processed: Re: Bug#784579: linux-image-3.16.0-4-amd64: Boot process / DRM initialization causes blank console

2015-05-06 Thread Debian Bug Tracking System
Processing control commands: retitle -1 [REGRESSION] vmwgfx black screen until X started Bug #784579 [src:linux] linux-image-3.16.0-4-amd64: Boot process / DRM initialization causes blank console Changed Bug title to '[REGRESSION] vmwgfx black screen until X started' from

Bug#784579: linux-image-3.16.0-4-amd64: Boot process / DRM initialization causes blank console

2015-05-06 Thread Hamilton Engineering
If I disable the GRUB_GFXPAYLOAD_LINUX parameter then GRUB does not tell Linux anything. I assume that GRUB (or is it the Linux kernel?) switches back to 80x25 text mode and the whole boot process completes without problems. No black screen. Markus Hamilton. On 5/6/2015 17:46, Ben Hutchings

Bug#776192: mptsas probe failure and crash, probably related to udev timeout

2015-05-06 Thread Stephen Dowdy
This reply is purely to assist any other poor souls like myself who have to suffer the fallout from this problem with a possible non-code-hack-related workaround for *SOME* configurations. We have two mptsas desktop systems one of which failed to boot after Jessie FAI install. The other had

Processed: closing 772983

2015-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: close 772983 3.16.7-ckt4-1 Bug #772983 [src:linux] armel kernel images are close to size limits Marked as fixed in versions linux/3.16.7-ckt4-1. Bug #772983 [src:linux] armel kernel images are close to size limits Marked Bug as done thanks

Bug#784579: linux-image-3.16.0-4-amd64: Boot process / DRM initialization causes blank console

2015-05-06 Thread Markus Hamilton
Package: src:linux Version: 3.16.7-ckt9-3~deb8u1 Severity: important The installation has been a Debian 7 system in a VMware Workstation 11 environment which runs under Windows 7x64 on a HP G61 laptop. There is no display manager installed. Linux just boots to a console login prompt. X11 is

Bug#784601: linux-image-3.16.0-4-powerpc: KMS hangs X after a few seconds with Radeon r300

2015-05-06 Thread Bill Chatfield
Package: src:linux Version: 3.16.7-ckt9-3~deb8u1 Severity: critical Justification: breaks the whole system Dear Maintainer, GDM won't start. It displays the screen with the frowning face with a useless error message. I setup lightdm instead and it will start Mate, but it

Processed: severity of 784601 is important

2015-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: severity 784601 important Bug #784601 [src:linux] linux-image-3.16.0-4-powerpc: KMS hangs X after a few seconds with Radeon r300 Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need

Processed: severity of 784546 is important, tagging 784546

2015-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: severity 784546 important Bug #784546 [linux] linux: backport of intel/e1000e driver Severity set to 'important' from 'wishlist' tags 784546 + patch Bug #784546 [linux] linux: backport of intel/e1000e driver Added tag(s) patch. thanks Stopping