Bug#720528: nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series)

> Control: tag -1 moreinfo > > On Sat, 23 Aug 2014 22:53:48 -0700 Ben Hutchings > wrote: > > On Sat, 2014-08-23 at 20:14 -0700, Andres Cimmarusti wrote: > > > Let me re-state: worked with debian 3.9, broke with debian 3.11 (but > > > works with Ubuntu vanill

Bug#720528: nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series)

.. > On Sun, 2014-04-27 at 11:13 -0400, Andres Cimmarusti wrote: >> found 720528 linux/3.13.10-1 linux/3.11.10-1 >> notfound 720528 linux/3.12.9-1 linux/3.9.6-1 >> thanks > [...] > > So this worked in 3.9, broke in 3.11, worked in 3.12, broke again in > 3.13? That

Bug#720528: nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series)

found 720528 linux/3.13.10-1 linux/3.11.10-1 notfound 720528 linux/3.12.9-1 linux/3.9.6-1 thanks >From the forum: For the issues what I mentioned earlier in this thread, that we reproduced in-house and investigated : "This is not an Nvidia bug. On affected notebooks Nvidia driver depends on ACPI

Bug#699406: linux-image-3.2.0-4-amd64: HD Audio early patching ignored

Package: src:linux Version: 3.2.35-2 Severity: normal Due to BIOS issues, a lot of systems advertise several HDMI pins even though physically only one is reachable. In my case, a LC2131 (SP13R) laptop shows the following available pins: $ aplay -l List of PLAYBACK Hardware Devices car

Bug#660111: multiple, non-physically accesible, HDMI devices

On 09/29/2012 01:47 PM, Jonathan Nieder wrote: Shouldn't we consider reverting 384a48d71520 (ALSA: hda: HDMI: Support codecs with fewer cvts than pins, 2011-06-01) in wheezy if userspace hasn't caught up with the new order of things? I haven't looked deeply into this or tried it, but it seems at

Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)

> You're correct; even if the information is there, it isn't advertised in > pavucontrol. I should probably implement that... > (If you're using Ubuntu 12.04, you will have a new sound settings UI that > hides unavailable devices. For upstreaming of this UI please see the > gnome-cc list.) > > What

Bug#641749: package libmtp-runtime breaks AR3011 Bluetooth

> I also found that removal of the "libmtp-runtime" package (version > 1.1.2-2) solved the problem with my AR3011 Bluetooth device. > (AMD64 CPU, Linux v3.2) > > After reading here: > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/714862/comments/43 > > https://bugs.launchpad.net/u

Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)

On Sun, Jun 10, 2012 at 8:25 PM, Andres Cimmarusti wrote: >> Andres, do you know of relevant commit ids?  Can you describe the >> difference in behavior between 3.2.19-1 and 3.4.1-1~experimental.1 and >> whether it's worth backporting these changes? > > I will try the

Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)

> Andres, do you know of relevant commit ids?  Can you describe the > difference in behavior between 3.2.19-1 and 3.4.1-1~experimental.1 and > whether it's worth backporting these changes? I will try the kernel from experimental and let you know if the changes are worth while. Unfortunately I have

Bug#660111: Bug#664653 pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default

> Do we still need to make kernel changes for wheezy, or does the new PA > together with the current kernel package (version 3.2.19-1) avoid this > problem? PA 2.0 can handle all the HDMI outputs advertised by the kernel, but one has to try all of them using pavucontrol to find the "correct" one.

Bug#660111: Bug#664653 pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default

fixed 664653 2.0-3 thanks As I reported earlier, version 2.0 of pulseaudio can handle multiple HDMI outputs. Bug# 664653 is completely fixed. I've tested it successfully in my computer. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble?

Re: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

> James Leddy writes[1]: > >> This turned out to be a problem with the firmware. It should be fixed by this >> modification to the firmware: >> >> http://comments.gmane.org/gmane.linux.kernel/1262485 > > Reassigning to firmware-atheros, but keeping the libmtp bug too in > case an appropriate Breaks

Bug#660111: Bug#664653 pulseaudio: pa can't handle multiple HDMI devices -- chooses wrong default

tags 664653 fixed-upstream thanks Pulseaudio upstream version 1.99.1 (or master, specifically after commit e02cb7fb2e7865affed612693935c7fd698e3a6b) contains all the necessary bits to allow the user to select from several HDMI devices advertised by the kernel. Please consider packaging. Andres

Bug#660111: multiple, non-physically accesible, HDMI devices

> Could you file a new report against pulseaudio summarizing the problem > and your suggested fix and mentioning > for background? Done, see bug report: http://bugs.debian.org/664653 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subje

Bug#660111: multiple, non-physically accesible, HDMI devices

retitle 660111 multiple, non-physically accesible, HDMI devices affects 660111 + pulseaudio tags 660111 + fixed-upstream wheezy thanks >> (but correct me if I'm wrong). However, I think Debian has decided to >> go with 3.2 kernel for the next stable release. This means no >> kcontrols. How is this

Bug#660111: [alsa-devel] multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB

Hello again, On Sat, Mar 3, 2012 at 9:43 PM, David Henningsson wrote: > On 03/04/2012 12:36 AM, Andres Cimmarusti wrote: >>> >>> There is active work going on in this area. In fact, I just posted a >>> patch >>> to the PA mailinglist [1]. And yes, we

Bug#660111: [alsa-devel] multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB

> There is active work going on in this area. In fact, I just posted a patch > to the PA mailinglist [1]. And yes, we already have it in Ubuntu 11.10 (to > probe multiple hdmi devices for Intel and NVidia), and the main reason it > took until now to upstream that patch, was the decision to switch j

Bug#660111: multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB

First of all, thank you for your feedback. It's been quite helpful / insightful > The biggest problem is that PA checks only the first HDMI device. > In that sense, this is no regression in the kernel side, although I > know it's annoying. I agree this seems more like a shortcoming of pulseaudio.

Bug#622707: Closing bug as invalid

622707-done thanks I'm closing this bug as invalid. The problem was hardware related. I tested this by installing Lenny on the laptop (which used to work without any problems), yet the same behavior was observed. Shortly after testing I had to replace the laptop because of hardware malfunction. T

Bug#660111: multiple, non-physically accesible, HDMI devices listed for Intel IbexPeak ALC269VB

reference, this is the original Debian bug report: http://bugs.debian.org/660111 Best Regards, Andres Cimmarusti 384a48d71520ca569a63f1e61e51a538bedb16df is the first bad commit commit 384a48d71520ca569a63f1e61e51a538bedb16df Author: Stephen Warren Date: Wed Jun 1 11:14:21 2011 -0600

Bug#660111: [3.0 -> 3.1.8 regression] intel ibexpeak hdmi no sound out

Found the first bad commit. It was the one you suspected all along! I will submit this issue upstream. Thanks for your invaluable help and demos! Cheers Andres 384a48d71520ca569a63f1e61e51a538bedb16df is the first bad commit commit 384a48d71520ca569a63f1e61e51a538bedb16df Author: Stephen Warren

Bug#660111: [3.0 -> 3.1.8 regression] intel ibexpeak hdmi no sound out

> To be clear, are you saying "git bisect" told you that 76531d4166 was > the first bad commit? Not exactly. I told you I got confused on how to use git-bisect, so I didn't use it (I didn't understand how is it supposed to check each commit, when another kernel is running). I simply used your firs

Bug#660111: [3.0 -> 3.1.8 regression] intel ibexpeak hdmi no sound out

Thanks for the git crash course. I did not look at 'git-bisect' too much. It is more systematic, but how to test each commit confused me some. I found the patch that brings about the problem. It turns out it happened quite early in the 3.1 kernel merge window. This the commit that changes things:

Bug#660111: [3.0 -> 3.1.8 regression] intel ibexpeak hdmi no sound out

> Perhaps v3.1-rc2~4^2~47^2~89 (ALSA: hda: HDMI: Support codecs with > fewer cvts than pins, 2011-07-01) is the problematic patch.  Can you > check this guess, like so? That patch that you mention is included in the 3.0.x kernels as the matter of fact. Thus I don't think it would have caused the p

Bug#660111: [3.0 -> 3.2.4 regression] intel ibexpeak hdmi no sound out

retitle 660111 [3.0 to 3.1 regression] HDMI 3 devices instead of 1 quit > Can you narrow down the regression range by a bisection search > through kernels at to find the first > broken one? I installed two kernels from snapshots. Using date 2012-02-01 I was able to p

Bug#660111:

retitle 660111 ALC269VB HDMI 3 devices detected instead of 1 quit -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAH=dYrGWKM6ax0Er-0RKx5JqHJXzJk0mew=xzoTxJv=voae..

Bug#660111: more info

retitle 660111 [linux-image-3.2] ALC269VB HDMI single physical port -> multiple devices detected quit After some online searching for this card's codec alc269vb I found several reports (some very old...) of the problem in Arch Linux: https://bbs.archlinux.org/viewtopic.php?id=133222 They point t

Bug#641749: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

I believe I have finally narrowed down the problem. It lies in the 'libmtp-runtime' package with the command 'mtp-probe' (only present in wheezy or newer). I'm not sure what this is doing to my system, but when the package mentioned is installed, it "messes" up my atheros bluetooth device so that

Bug#641749: ath3k_load_firmware: Can't change to loading configuration err

There's only silence in the linux-kernel and linux-bluetooth mailing lists... At this point there is only one thing I haven't tried because I can't at the moment. One of the differences between Wheezy and Squeeze in terms of, say the 3.1.x, kernel is that in Squeeze I compile it with gcc 4.4.5, b

Bug#641749: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

of udev to the one found in Debian squeeze (version 164) as well as usb-modeswitch (also tried upgrading to the latest versions in Debian unstable), but this has yielded no progress and no clues at all...the error messages remain the same. Help debugging this issue would be most welcome. Best R

Bug#641749: ath3k_load_firmware: Can't change to loading configuration err

Hi there > Yes, no ideas here, either.  Please contact > linux-blueto...@vger.kernel.org, cc-ing linux-ker...@vger.kernel.org > and either me or this bug log so we can track it. I've spotted something odd that may give us some light as to why it's not working and I wanted to discuss it here befor

Bug#641749: ath3k_load_firmware: Can't change to loading configuration err

Hi Jonathan, > I'd like to narrow down the difference even more.  So, here are some > ideas: > >  1. Can you reproduce this with a squeeze kernel?  (I'm guessing it >    lacks support since it doesn't include commit >    v2.6.33-rc7~20^2~3^2~1, "Bluetooth: Add DFU driver for Atheros >    Bluetooth

Bug#641749: bug 641749 update

Hi, I've been successfully using a "pristine" 3.0.x kernel on the same laptop atop Debian Squeeze (using the firmware-atheros packages from backports and/or testing). I have no problems loading the AR3011 bluetooth module firmware and system restarts appropriately. I started doing this since 3.0.

Bug#641749: firmware-atheros doesn't load for Atheros AR3011

> The reason why it works in Ubuntu with kernel 2.6.38 is because they > patched their kernel: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/720949 > https://launchpadlibrarian.net/68723624/0002-UBUNTU-SAUCE-Revert-Bluetooth-Add-new-PID-for-Athero.patch Actually this patch is already in

Bug#641749: firmware-atheros doesn't load for Atheros AR3011

Hey, I just found more information >> This device is rather peculiar. I currently have a dual boot with >> Ubuntu 11.04. In Ubuntu, using kernel 2.6.38 the device works >> correctly as expected. The bluetooth LED turns on and everything. In >> Debian, however, running either my vanilla kernel 3.0.

Bug#641749: firmware-atheros doesn't load for Atheros AR3011

> This device is rather peculiar. I currently have a dual boot with > Ubuntu 11.04. In Ubuntu, using kernel 2.6.38 the device works > correctly as expected. The bluetooth LED turns on and everything. In > Debian, however, running either my vanilla kernel 3.0.4 or official > Debian kernel 3.0.0-1-am

Bug#641749: firmware-atheros doesn't load for Atheros AR3011

> This error message indicates a communication failure with the device > after the firmware has been loaded from disk but before it has been > transferred into the device.  So it's not a problem with the firmware > but with the driver or the hardware. I see. > Did this hardware work with a previo

Bug#641749: firmware-atheros doesn't load for Atheros AR3011

Package: firmware-atheros Version: 0.33 Severity: important Dear Maintainer, This is my device: Bus 001 Device 003: ID 0cf3:3000 Atheros Communications, Inc. AR3011 Bluetooth (no firmware) It does not turn on and kern.log shows following errors: [9.335184] ath3k_load_firmware: Can't chang

Bug#588602: xserver-xorg-video-radeon: xpress 200m 5955 => resume from suspend fails with KMS enabled

Sorry for not reporting back sooner. This bug was actually fixed for squeeze. Thus it's been fixed in testing and did for quite sometime. You can close this On Jul 30, 2011 5:05 AM, "Moritz Mühlenhoff" wrote: > On Mon, May 31, 2010 at 05:15:41PM -0400, Andres Cimmarusti wrote: &

Bug#586270: linux-image-2.6.32-5-686: evo n610c compaq laptop fails to go into suspend mode

> Sorry for the late followup. It is I who should be sorry for not reporting back as soon as this was fixed. > Does this still occur with more recent kernels, i.e. the final Squeeze kernel > or > more recent versions from backports/testing/sid? Squeeze is running very well on this laptop. Suspe

Bug#622707: bug 622707 seems resolved upstream

Just a little update: > Sync problems and lagging seems gone once I pass the options > "i8042.nomux" to the kernel. This is true for the synaptics touchpad, but it causes a terrible problem: I started using Linux on this laptop since I started with Linux in 2008 with Ubuntu 8.04 based on the 2.6

Bug#622707: bug 622707 seems resolved upstream

Hi, this is the upstream kernel bug report I submitted: https://bugzilla.kernel.org/show_bug.cgi?id=33652 Sync problems and lagging seems gone once I pass the options "i8042.nomux" to the kernel. The "query no synaptics" error message still shows up in Xorg.0.log. But the kernel developer pointed

Bug#618979: same here

I have the same issue. System is overall slow (I thought 2.6.38 was supposed to have major performance improvements including the famous desktop latency patch!). I'm running gnome with no desktop effects using radeon open source drivers. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.d

Bug#611827: xserver-xorg-input-evdev: mice and touchpad losing sync and lagging (MORE INFO)

Allright, so I have been running for days the 2.6.37 kernel from experimental with no problems. My touchpad is working just fine. This bug is really affecting me in the 2.6.32. It was working fine, but there was an update that messed it up...perhaps a backport? I say this only because the people f

Bug#611827: xserver-xorg-input-evdev: mice and touchpad losing sync and lagging (MORE INFO)

This is the contents of my Xorg.log. It seems the appropriate synaptics module is being unloaded... perhaps this is causing the issue? (II) LoadModule: "evdev" (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so (II) Module evdev: vendor="X.Org Foundation" compiled for 1.7.6.901, module

Bug#605204: linux-image-2.6.32-5-amd64: hp dv5035nr laptop: failed suspend make X crash

> It sounds like the radeon driver is not properly restoring power to the > LCD when the suspend process is aborted. > > Could you test Linux 2.6.36 as packaged in experimental? > I've been trying to reproduce it with linux 2.6.36 (+ the dbg package), but I have gotten no problem. In fact, I have

Bug#583968: xserver-xorg-video-radeon: xpress 200m 5955 => resume from suspend fails with KMS enabled

> Patch seems to be > http://article.gmane.org/gmane.comp.video.dri.devel/48108 Yes this patch works. It's been applied upstream since version 2.6.35. Could this be backported to squeeze's kernel? I have been using the patch on vanilla kernels 2.6.32, 2.6.33, 2.6.34 and 2.6.35 successfully. Thank

Bug#583933: Bug # 583933: xserver-xorg-video-radeon: Latest radeon + KMS ASIC bug error message

uot;Alex Deucher" Cc: "Andres Cimmarusti" , xorg-driver-...@lists.x.org Date: Friday, July 16, 2010, 10:33 AM On 07/16/2010 09:53 AM, Alex Deucher wrote: > On Fri, Jul 16, 2010 at 12:45 AM, Andres Cimmarusti > http://us.mc507.mail.yahoo.com/mc/compose?to=andrescimmaru...@yahoo.com

Bug#588602: Bug#: 588601, 588602: xpress 200m 5955 => resume from suspend fails with KMS enabled

I dedicated a large portion of the day to finding a clue to this one. Following this advice: http://lxr.linux.no/#linux+v2.6.34.1/Documentation/power/s2ram.txt I was able to extract a trace from the failed resume process: Magic number: 0:981:799 hash matches drivers/base/power/main.c:523 pci :

Bug#586270: linux-image-2.6.32-5-686: evo n610c compaq laptop fails to go into suspend mode

Package: linux-2.6 Version: 2.6.32-15 Severity: important Tags: sid squeeze After recent updates, I can no longer successfully go into suspend moved with this laptop. The kernel log shows several backtraces. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-15) (b..

Bug#583924: linux-image-2.6.32-5-amd64: udevd-work and kernel names disagree

Package: linux-2.6 Version: 2.6.32-14 Severity: minor Tags: sid squeeze I keep getting this message at boot time: udevd-work[377]: kernel-provided name 'uinput' and NAME= 'input/uinput' disagree, please use SYMLINK+= or change the kernel to provide the proper name For a similar bug: http://bugs.

Bug#574555: linux-image-2.6.32-3-amd64: 2.6.32 kernel oops: Pid: 1700, comm: irq/21-b43 Not tainted 2.6.32-3-amd64

Package: linux-2.6 Version: 2.6.32-9 Severity: normal I've been regularly getting a kernel oops that leaves this trace (IMPORTANT: this doesn't happen with kernel 2.6.33, I thought it would be solved in upstream release 2.6.32.9): Mar 18 15:56:58 debturion kernel: [10281.468122] WARNING: at /b

Bug#537879: linux-image-2.6.26-2-amd64/686: reloads b43-phy0

in Squeeze...but the problem remains in Debian plain stable. 2010/3/1 Moritz Muehlenhoff > On Tue, Jul 21, 2009 at 10:21:19AM -0400, Andres Cimmarusti wrote: > > Package: linux-image-2.6.26-2-amd64 > > Version: 2.6.26-17 > > Severity: normal > > > > This doesn&#