Just adding some initial thoughts which I've also relayed via IRC/mumble discussions...
It would appear to me that the scope of this issue is much wider than just the the LTS HWE Quantal testing in Precise. Based on comment #4, I'd expect this issue to present for all releases from Natty->Quantal. That being said it would also seem to me that the most obvious workaround in the mean time would be to make sure a monitor is connected. That would at least allow for this system to re-enter the testing pool. I am now however receiving completely contradictory information between this bug report and IRC conversations: >From #ubuntu-kernel on FreeNode: [10:12:56] <ogasawara> hggdh: and just so I have it clear in my head, when exhibiting this issue, the system in question is just connected to a kvm swtich, but no monitor is attached to that switch correct? [10:13:36] <hggdh> ogasawara: the switch does have a monitor [10:28:03] <ogasawara> hggdh: so I wanted to post a comment to the bug, but I'm still a little confused as to where the "if no monitor is connected..." part comes into play then. [10:30:31] <hggdh> ogasawara: the machines connect to a KVM (in this case using a DVI<-> VGA converter; the KVM has a local monitor that allows one to connect and use a system; it also allows one to remotely connect to the KVM, and select a system to work on [10:33:03] <hggdh> amd firepro V5900 prints out a few EDID errors and is done; system can be used from the console. nVidia keeps on printing EDID errors, making console usage impossible (server images, 3.5.0-10, now installing desktop) [10:45:58] <ogasawara> hggdh: so a monitor *is* connected (albeit via a kvm switch) when you're seeing these repeated EDID errors. [10:55:46] <hggdh> ogasawara: indeed [10:56:45] <ogasawara> hggdh: so the bug report then is completely misleading with the title and description being "if no monitor is connected..." [10:57:43] <hggdh> ogasawara: I agree It would be helpful to get a clear and updated bug title and description of what is actually happening. In the mean time, it would seem there might be a proposed patch upstream which may help. I'll try building a test kernel. https://patchwork.kernel.org/patch/1301341/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013270 Title: if no monitor is connected, Nouveau fails to initialise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1013270/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
