[lucid] [nouveau] blank screen on Dell Latitude E6410 (NVS 3100M [10de:0a6c])
Bug #556872 reported by
Mathieu Trudel-Lapierre
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Ubuntu Kernel Team | ||
Lucid |
Invalid
|
High
|
Seth Forshee |
Bug Description
Using the daily ubuntu desktop image (i386) (10.04 (20100406)), during and after install, the screen remains blank. Rebooting the system with nouveau.modeset=0 seems work around the issue.
Changed in linux (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
affects: | linux (Ubuntu) → xserver-xorg-video-nouveau (Ubuntu) |
Changed in xserver-xorg-video-nouveau (Ubuntu): | |
assignee: | nobody → Canonical Desktop Team (canonical-desktop-team) |
Changed in xserver-xorg-video-nouveau (Ubuntu): | |
assignee: | Canonical Desktop Team (canonical-desktop-team) → Chris Halse Rogers (raof) |
tags: | added: lucid |
Changed in xserver-xorg-video-nouveau (Ubuntu): | |
status: | Incomplete → Triaged |
tags: | added: kernel-graphics kernel-needs-review |
Changed in linux (Ubuntu): | |
assignee: | nobody → Chris Halse Rogers (raof) |
tags: |
added: kernel-candidate kernel-reviewed removed: kernel-needs-review |
Changed in linux (Ubuntu): | |
assignee: | Chris Halse Rogers (raof) → Steve Conklin (sconklin) |
tags: | removed: kernel-candidate |
Changed in linux (Ubuntu): | |
status: | Triaged → Fix Released |
status: | Fix Released → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Fix Committed → Triaged |
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu): | |
assignee: | Steve Conklin (sconklin) → Ubuntu Kernel Team (ubuntu-kernel-team) |
Changed in linux (Ubuntu Lucid): | |
assignee: | Steve Conklin (sconklin) → Ubuntu Kernel Team (ubuntu-kernel-team) |
To post a comment you must log in.
As additional information, while this issue starts at boot and continues on to while in X, this is the resulting Xorg.0.log.