Processing commands for cont...@bugs.debian.org:
reassign 697269 module-assistant,src:linux
Bug #697269 [module-assistant] module-assistant: incompatible with
linux-headers-3.7-trunk-amd64
Bug #697360 [module-assistant] tp-smapi-source: does not recognize 3.7 kernel
headers although they are
Am Sonntag, 6. Januar 2013 schrieb Evgeni Golov:
On Sun, Jan 06, 2013 at 02:16:37PM +0100, Martin Steigerwald wrote:
But the does not recognize the kernel headers issue seems to
persist.
Yeah, but thats a bug in m-a: http://bugs.debian.org/697269, merging.
:) As hoped, no bug in
Package: src:linux
Followup-For: Bug #697635
Dear Maintainer,
Testing a little bit more, hibernate is also affected by the problem.
I've blacklisted the nvidia's module to untaint the kernel and see if that
helps. No luck.
Nicolas
--
To UNSUBSCRIBE, email to
Processing commands for cont...@bugs.debian.org:
# no change required on kernel side
reassign 697269 module-assistant 0.11.4
Bug #697269 [module-assistant,src:linux] module-assistant: incompatible with
linux-headers-3.7-trunk-amd64
Bug #697360 [module-assistant,src:linux] tp-smapi-source: does
Ben,
The following fix is needed in bridge driver in debian 7.0. Do you want me to
open a bug for this and send a patch?
Thanks,
Sarvesh
commit 6caab7b0544e83e6c160b5e80f5a4a7dd69545c7
Author: Sarveshwar Bandi sarveshwar.ba...@emulex.com
Date: Wed Oct 10 01:15:01 2012 +
bridge:
I've been able to narrow this down a bit more. One of my other systems
still had 3.2.0-3-686-pae (3.2.23-1) in its apt archives. This kernel
also boots successfully and does not hang at mdm startup. So, the
problem did not exist in any of the 3.2.0-3 series released to Wheezy,
but was
Package: src:linux
Version: 3.2.35-2
Followup-For: Bug #680737
I'm having the same issue with a Dell Vostro 1500 laptop; specs below.
Gedalya geda...@gedalya.net noted that his/her issue seemed to be related to
brightness and was simply a matter of the brightness being turned all of the
way
On Tue, Jan 08, 2013 at 02:32:01PM +, Bandi,Sarveshwar wrote:
Ben,
The following fix is needed in bridge driver in debian 7.0. Do you want me
to open a bug for this and send a patch?
Please open a bug.
Also (or instead) please ask David Miller to include this in his
stable patch queue
On Tue, Jan 8, 2013 at 11:28:16 -0600, Nathan Schulte wrote:
My issue, and I suspect the author's, is a modesetting issue. Sometimes I
don't experience this issue and I am dropped to a console as expected; most
other times I do experience the issue, and once udev loads my screen flickers
Processing commands for cont...@bugs.debian.org:
unarchive 622231
Bug #622231 {Done: Jonathan Nieder jrnie...@gmail.com} [src:linux] Dell
Latitude E6400: AlpsPS/2 touchpad sometimes misdetected as plain PS/2
Unarchived Bug 622231
thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
found 622231 3.5.5-1~experimental.1
Bug #622231 {Done: Jonathan Nieder jrnie...@gmail.com} [src:linux] Dell
Latitude E6400: AlpsPS/2 touchpad sometimes misdetected as plain PS/2
Marked as found in versions linux/3.5.5-1~experimental.1 and
Package: src:linux
Version: 3.2.35-2
Severity: minor
Upon boot, with no ALSA present (package: alsa-base), the kernel outputs this
harmless message:
Error: Driver 'pcspkr' is already registered, aborting...
This was detailed in bug 495674, and was addressed by a blacklisting of the
snd-pcsp
On Tue, Jan 8, 2013 at 13:28:12 -0600, Nathan Schulte wrote:
On Tue, Jan 8, 2013 at 12:39 PM, Julien Cristau jcris...@debian.org wrote:
Please post a dmesg without the video kernel param, and with drm.debug=6
instead.
As you wish!
Thanks. That seems to detect the SVIDEO as
On 2012-08-19 17:54:48 -0700, Jonathan Nieder wrote:
Therefore closing, but if it happens again, we'll be happy to
revisit it.
The bug occurred twice with 3.5.5-1~experimental.1 (first boot
was after two weeks my laptop was switched off, and another
reboot immediately after). The third (re)boot
On Tue, Jan 8, 2013 at 1:52 PM, Julien Cristau jcris...@debian.org wrote:
Thanks. That seems to detect the SVIDEO as consistently disconnected,
so I don't know why forcing it off makes a difference :/
Attached is the dmesg with drm.debug=6 and video=SVIDEO-1:d
It's interesting that the
On 2012-08-19 17:54:48 -0700, Jonathan Nieder wrote:
Therefore closing, but if it happens again, we'll be happy to
revisit it.
The bug occurred twice with 3.5.5-1~experimental.1 (first boot
was after two weeks my laptop was switched off, and another
reboot immediately after). The third (re)boot
found 680737 3.2.35-2
found 680737 3.7.1-1~experimental.2
quit
Nathan Schulte wrote:
I just want to note that this bug still exists in my version. I will test
newer kernels from experimental, but I suspect they will resolve this issue.
I tried with 3.7-trunk from experimental. It appears
Processing commands for cont...@bugs.debian.org:
found 680737 3.2.35-2
Bug #680737 [src:linux] linux-image-3.2.0-2-amd64: Intel i915: black display
after boot
Ignoring request to alter found versions of bug #680737 to the same values
previously set
found 680737 3.7.1-1~experimental.2
Bug
Apologies for all of the messages; I should have waited and sent one
at a time. Oh well.
Interestingly: I hibernated the machine while booting with the
3.7-trunk kernel without any workarounds. Upon coming back from the
hibernate, the display/console are working as expected.
--
Nate
--
To
Processing commands for cont...@bugs.debian.org:
# different bug
notfound 680737 linux/3.2.35-2, linux/3.7.1-1~experimental.2
Bug #680737 [src:linux] linux-image-3.2.0-2-amd64: Intel i915: black display
after boot
No longer marked as found in versions linux/3.7.1-1~experimental.2 and
# different bug
notfound 680737 linux/3.2.35-2, linux/3.7.1-1~experimental.2
quit
Hi Nate,
Nathan Schulte wrote:
I tried with 3.7-trunk from experimental. It appears the same issue
exists there as well,
Thanks for testing. Please report this upstream following
instructions from
On Wed, Jan 9, 2013 at 12:20 AM, Jonathan Nieder jrnie...@gmail.com wrote:
# different bug
notfound 680737 linux/3.2.35-2, linux/3.7.1-1~experimental.2
quit
Thanks for testing. Please report this upstream
and file a new bug here mentioning the upstream bug number so we can
track it.
Can
Processing commands for cont...@bugs.debian.org:
Version: 1.0.23+dfsg-3
Unknown command or malformed arguments to command.
reassign 615941 alsa-base 1.0.23+dfsg-2
Bug #615941 [linux-2.6] Please don't provide pcspkr
Bug reassigned from package 'linux-2.6' to 'alsa-base'.
Ignoring request to
Nathan Schulte wrote:
Can do. Just curious, what's the reasoning behind filing a different
bug report?
That your symptoms are completely different from Roland's. ;-)
Actually it's much more convenient to track each report separately
even when symptoms overlap except when very confident that
Package: src:linux
Version: 3.2.35-2
Severity: normal
Tags: patch
Hi,
tracking down a bug in wacom, I followed the kernel handbook and got an
error in an outdated sid chroot (python still at 2.6):
cyril@Cygnus:~/linux-3.7.1$ fakeroot make -f debian/rules.gen
binary-arch_i386_none_486
make -f
Package: src:linux
Version: 3.7.1-1~experimental.2
Severity: normal
I'm experiencing an issue with my Intel GM945 (i915 driver) based system; a
Dell Vostro 1500 laptop.
When booting from a fresh install of Debian Sid, as well as with the 3.7 kernel
from experimental, I am usually presented
found 697741 linux/3.2.35-2
quit
I'm not sure how to take care of noting the upstream bug report in the
BTS; I'll leave that to someone with more experience.
--
Nate
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Jonathan Nieder wrote:
That your symptoms are completely different from Roland's. ;-)
Actually it's much more convenient to track each report separately
even when symptoms overlap except when very confident that one fix
will take care of everything.
My symptoms sounded nearly identical to me.
Processing commands for cont...@bugs.debian.org:
found 697741 linux/3.2.35-2
Bug #697741 [src:linux] i915: Black screen/no console with KMS
Marked as found in versions linux/3.2.35-2.
quit
Stopping processing here.
Please contact me if you need assistance.
--
697741:
Nathan Schulte wrote:
I've found a relevant upstream bug report, and I have provided more
details for the report.
https://bugs.freedesktop.org/show_bug.cgi?id=53926#c43
That report is about an LVDS failure. Your output is S-Video. Bugs
are cheap --- please don't be shy about filing a new
30 matches
Mail list logo
