[Ubuntu-x-swat] [Bug 1101688] Re: xdiagnose does not install properly during a regular update

** Summary changed: - during a regular upgrade of ht updated packages. in Raring + xdiagnose does not install properly during a regular update -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1

[Ubuntu-x-swat] [Bug 1101688] Re: during a regular upgrade of ht updated packages. in Raring

Similar story; regular apt-get update && apt-get upgrade, and bam. No previous (relevant/related) issues. ** Package changed: dpkg (Ubuntu) => xdiagnose (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.l

[Ubuntu-x-swat] [Bug 921321]

I couldn't get the git kernel, so I tried that patch against linux-3.7-rc3. Unfortunately, it didn't change anything in my set up (Elitebook 8530w, NVIDIA Corporation G96M [Quadro FX 770M] card). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xs

[Ubuntu-x-swat] [Bug 921321]

I repeated testing using kernel 3.3.0 RC4, and results are similar: nvapeek (before): e100: 001c1100 e28c: 0100 e104: 72267640 0441474b e280: 4747 After: e100: 001c1100 e28c: 0100 e104: 72267240 0441474b e280: 4747 Compared to the

[Ubuntu-x-swat] [Bug 921321]

There should be a solution to this dilemma, considering that nvidia's binary blob does it correctly. I got the nvapeek results for using the binary blob, and the results I got are: Before e100: 001c1100 e28c: 0100 e104: 72266640 0441474b e280: 4747 After e100