On Tue, 2012-04-10 at 19:10 +0200, Thomas Lange wrote:
> Hi,
>
> when using dracut (017-1) instead of initramfs-tools on a wheezy
> machine /var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst creates
> and complains about a dangling symlink /initrd.img. This is because
> dracut creates a initrd
Package: linux-2.6
Version: 3.2.9-1
Severity: normal
After using Internet connection through a USB ID 12d1:1436 device and sharing
the connection to eth0/atl1c interface for tens of minutes, I removed the USB
device. A few seconds later I noticed the eth0/atl1c interface hung. I
unplugged and plug
Hi,
when using dracut (017-1) instead of initramfs-tools on a wheezy
machine /var/lib/dpkg/info/linux-image-3.2.0-2-amd64.postinst creates
and complains about a dangling symlink /initrd.img. This is because
dracut creates a initrd file called initramfs-3.2.0-2-amd64.img. This
is properly detected
Hello Jonathan,
... Am I correct in assuming 3.3 works fine on your machine? Cheers,
Jonathan
Yes, this bug seems to be fixed in linux-image-3.3.0-trunk-amd64
(3.3-1~experimental.1).
Kind regards,
Jakob
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "u
Processing commands for cont...@bugs.debian.org:
> severity 668274 important
Bug #668274 [linux-2.6] linux-image-3.2.0-2-amd64: Intel Core i3-2310M (HD
3000) / i915: Black screen at boot
Severity set to 'important' from 'normal'
> # * [x86] drm/i915: mask transcoder select bits before setting the
severity 668274 important
# * [x86] drm/i915: mask transcoder select bits before setting them on LVDS
tags 668274 + patch pending
quit
WEARENOTALONE wrote:
> when I try to boot the current kernel 3.2 from debian wheezy||sid,
> my notebook screen goes black. Switching to another tty doesn't
> help
Package: linux-2.6
Version: 3.2.14-1
Severity: normal
Dear Maintainers,
when I try to boot the current kernel 3.2 from debian wheezy||sid, my notebook
screen goes black. Switching to another tty doesn't help, but the system is
still usable e.g. via ssh. This bug is already known and fixed upstre
Replacing the ath5k driver code with the updated code from Linux 3.4-rc1 fixes
this problem for me.
(Specifically drivers/net/wireless/ath/ath5k/ath5k.h, base.c and phy.c - nothing else changed from
3.3.0)
On 02/04/12 14:36, Debian Bug Tracking System wrote:
Thank you for the additional info
On 04/10/2012 04:48 AM, Ben Hutchings wrote:
It's also possible that the problem could be on the display side, since
video is usually displayed differently from other graphics. Are you
able to play video files successfully? Can mplayer show the webcam
video properly if you use the option '-vo x
9 matches
Mail list logo
