Package: src:linux
Version: 3.2.41-2
Severity: important
Dear Maintainer,
Before last upgrade to linux-image-3.2.0-4-amd64 I was able to reach 1280x1024
without problem. Now, the kernel seams to switch early in gfx mode and set the
resolution to 1024x768. Xorg keeps the same resolution. Notice
Control: tag -1 patch moreinfo
Cyril Brulebois k...@debian.org (10/04/2013):
Patches (preferably tested ;)) against src:debian-installer to update
package lists for armhf/{mx5,vexpress} are more than welcome. Also,
(I know I'm asking a lot), “fast is good”.
Ben Hutchings kindly sent some
On Fri, Apr 5, 2013 at 10:23 AM, Robin Hill ro...@robinhill.me.uk wrote:
On Thu Apr 04, 2013 at 10:13:05 +0200, Maik Zumstrull wrote:
I've managed to find a configuration on my home desktop where a
particular RAID array is barely usable.
I used to have the same issues on one of my machines.
Processing control commands:
reassign -1 src:linux 3.2.39-2
Bug #705168 [linux-image] Wheezy fails to boot after 2013-04-05 update
Warning: Unknown package 'linux-image'
Bug reassigned from package 'linux-image' to 'src:linux'.
No longer marked as found in versions 3.2.0-4-amd64.
Ignoring
Control: reassign -1 src:linux 3.2.39-2
Barry Fishman barry_fish...@acm.org writes:
Package: linux-image
Version: 3.2.0-4-amd64
I'm reassigning this to src:linux, with version set to wheezy's
src:linux version.
When booting the system, I see about 8 lines of boot messages and then
the
Hi,
Not having this bug fixed, *3 years* after this bug has been filled, is
unacceptable.
If you don't have time to maintain this package, please fill an RFA. No
init script is not only annoying, it renders the package unusable in its
current state.
Thomas Goirand (zigo)
--
To UNSUBSCRIBE,
Hi,
Please find attached to this mail, a working init script (thanks to
jcristau for sharing what he hacked). Also, please consider fixing this
bug in Wheezy (for example, through wheezy-proposed-updates).
If I don't hear from you, I will ask the release team if this patch may
be considered for
Qiu Shengming 11300240010 at fudan.edu.cn writes:
Package: src:linux
Version: 3.2.39-2~bpo60+1
Severity: important
Hardware: Dell Insprion N4120 w/ Intel HD Graphics 3000 AMD Radeon HD 6630M.
Symptom: With Linux version 3.2.39-2~bpo60+1 everything works. However, with
3.2.41-2~bpo60+1
On Thu, Apr 11, 2013 at 11:22:37PM +0800, Thomas Goirand wrote:
Hi,
Not having this bug fixed, *3 years* after this bug has been filled, is
unacceptable.
If you don't have time to maintain this package, please fill an RFA. No
init script is not only annoying, it renders the package
On Fri Apr 12 2013 01:00:12 AM CST, Ben Hutchings b...@decadent.org.uk wrote:
I don't deny that the lack of an init script is at best a nuisance,
but it certainly doesn't render the package unusable.
Right, I over-stated it.
Thomas
--
To UNSUBSCRIBE, email to
Processing commands for cont...@bugs.debian.org:
fixed 703813 3.8.5-1~experimental.1
Bug #703813 [src:linux] 3.8.3 breaks mode connected output handling on intel
GM45
Marked as fixed in versions linux/3.8.5-1~experimental.1.
thanks
Stopping processing here.
Please contact me if you need
I have a Radeon HD 4670 graphics card.
If I add the option radeon.modeset=0 to the linux boot command the
system will boot successfully and run fine. Of cource the graphics
runs very slow.
Could the problems be in changes to the radeon driver KMS code?
--
Barry Fishman
--
To UNSUBSCRIBE,
On 11/04/13 10:54, Geoff Crompton wrote:
I've also built a 3.2.39 kernel with some patches stripped. This kernel
still does exhibit the problem, suggesting the patches I stripped out
are not responsible. Those patches are:
bugfix/x86/drm-i915-kick-any-firmware-framebuffers-before-claim.patch
found 703468 linux/3.5.5-1~experimental.1
fixed 703468 linux/3.6.4-1~experimental.1
tags 703468 + upstream patch moreinfo
quit
Geoff Crompton wrote:
works 3.6.4
fails 3.5.5-1
[...]
Hope that is helpful, what is the next step?
Very much so! Thanks for this work.
00:02.0 Display controller
Hey, I've been getting this bug every so often (a couple times a month) for the
past couple of months. I don't know how to reproduce it, other than it is as
Mario has mentioned; It seems to only happen when resuming from suspend.
There's another panic (might be the same one) I get when resuming
15 matches
Mail list logo
