Sure thing. Attached!
** Attachment added: nvidia-bug-report.log.gz
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/901386/+attachment/2729452/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is
3vi1, Can you provide system information and attach file by running
nvidia-bug-report.sh as root?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
Ubuntu 3.2
Thanks everyone for confirming the fix in Ubuntu. I'm opening an
upstream task for Alberto to track the work with NVIDIA. Meanwhile I'm
closing out the Ubuntu task.
If there are any remaining issues left as a consequence of this change
please file new bug reports.
** Also affects:
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
Ubuntu 3.2 kernels vs.
@Bryce:
Sure, I'll bring this up in the next call.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
Ubuntu 3.2 kernels vs. nvidia-current vs GTX 560 (Mainline
With 3.2.0-10 I can boot normally without adding iommu=off.
(But it was necessary to reinstall the nvidia drivers, before that I couldn't
boot)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I can confirm that I too am able to boot 3.2.0-10 without adding
intel_iommu=off.
I did *not* have to reinstall any drivers like Sander though.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
On 01/20/2012 09:29 PM, Bryce Harrington wrote:
Based on the last comment, and the original reporter's comment #16 it
sounds like this might now be worked around in the distro. Can someone
confirm the original reported problem (failure to boot) is resolved?
@Bryce -- Confirmed here, after
Based on the last comment, and the original reporter's comment #16 it
sounds like this might now be worked around in the distro. Can someone
confirm the original reported problem (failure to boot) is resolved?
Comment #17 suggests there may be secondary problems (which may or may
not be a
Same for me with Quadro FX 770M, Precise 64bit, an Linux 3.2.0.2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
Ubuntu 3.2 kernels vs. nvidia-current vs GTX 560
For those that need intel_iommu=off, it looks like it's been fixed
w/this change * [Config] Disable CONFIG_INTEL_IOMMU_DEFAULT_ON:
---
linux (3.2.0-10.17) precise; urgency=low
[ Andy Whitcroft ]
* Revert SAUCE: overlayfs -- fs: limit filesystem stacking depth
* Revert SAUCE:
Hi,
This affects me, although with slightly different symptoms to other
reporters.
The current (18th Jan 2012) kernel nvidia-current driver in precise
doesn't work - after the kernel boots I'm stuck with a black screen. I
can't switch to any of the terminals, or do anything other than hold
down
Has anyone had any luck with newer kernels than 3.2rc4?
No luck here. As of 3.2.0.9 I still have to disable intel_iommu in grub
to get it to work, even with the new 290.10 nvidia-current packages.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
It was my mistake earlier. I used my own compile of the 3.2 kernel with
IOMMU all disabled as I only have a Core2 Duo that doesn't support
IOMMU. I have to use the intel_iommu=off with any build of the 3.2 or
3.2.1 kernel wether from ubuntu sources or kernel.org. On 12.10 and
11.10. Using any
I just tried 3.2.0.9 and it still does not work..
Has anyone had any luck with newer kernels than 3.2rc4?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
Ubuntu
I have this problem too.
My videocard is Nvidia Quadro FX 3800.
Adding intel_iommu=off to grub parameters indeed solves this problem
temporarily...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I can confirm Haitao's workaround as well. I added intel_iommu=off and
was then able to boot 3.2.0-6 without issue.
Thanks Haitao!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Looks like I have to back off the without issue in my previous
statement. I just noticed that the USB3.0 devices attached to my Marvel
88SE91xx adapter are not being seen when I use this workaround. Of
course, at this point I'm assuming it's caused by the work around and
not an entirely separate
I found the blank screen is actually caused busy xorg process. And there
are huge number of error like below in kern.log. Add intel_iommu=off to
kernel boot option and now it works perfectly.
Dec 24 13:28:54 ainur kernel: [ 420.863224] DMAR:[DMA Read] Request device
[01:00.0] fault addr
Just tested and found that acpi=off lets me boot the 3.2.0-6 too - and
it works fine with the nvidia-current drivers. Too bad it means my
i980x is treated single-core.
I'm not sure you'll find the trouble in a diff of the more recent
mainline configs - both mainline rc5 and rc6 don't work for me
Same issue here, Quadro FX 770M 512M. (mainline rc6 doesn't work either)
The acpi=off tricks works for me too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
I did a custom compile of 3.2.0-6 with no nouveau driver at all, then
purged all nvidia debs and in single mode ran the nvidia binary with the
--uninstall option and deleted my xorg.conf file. Rebooted and installed
the nvidia binary in single mode then rebooted again and have 3.2
kernel along
Further troubleshooting lead me to acpi=off being a solution. Just not a
good one. I'll take a look at the .config file that's default with 3.2
and compare to the latest ubuntu .config later. Or pull the config out
of a working 3.2 deb and compare to the new ones. Something must have
changed in
This is happening to me with a 9600M GS 512MB. Tried with a fresh daily
ISO install of precise, and it also happens on my 11.10 install with the
newer 3.2 kernel packages applied. I have also purged nvidia-current and
tried with the binaries from nvidia of 290.10, 290.06 and 285.05.09. If
I
I forget to mention that my system doesn't drop to a TTY. It just goes
to a black screen, then the backlight eventually turns off. No matter
which nvidia driver or in 12.04 or 11.10. I know it's with the video
driver as I disabled lightdm to boot to a command prompt, then run
startx manually and
Unfortunately, There isn't much more we can do on the kernel side
because of the proprietary nature of this package. Since we can't look
at the code and figure out what's wrong and fix. I'll re-assign to the
nvidia-current package.
** Package changed: linux (Ubuntu) = nvidia-graphics-drivers
Also, Ubuntu 12.04(Precise) will pick up this fix automatically if you
confirm its fixed upstream.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/901386
Title:
Ubuntu 3.2
27 matches
Mail list logo
