The original bug is fixed since early March by an discover-data update.
** Changed in: discover-data (Ubuntu)
Sourcepackagename: xorg => discover-data
Status: Confirmed => Fix Released
--
Wrong driver used after installing herd2 on M2NPV-VM
https://bugs.launchpad.net/bugs/79210
You receiv
** Changed in: xorg (Ubuntu)
Sourcepackagename: discover-data => xorg
--
Wrong driver used after installing herd2 on M2NPV-VM
https://bugs.launchpad.net/bugs/79210
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
I have the same motherboard, and just installed Feisty Fawn. I can
confirm that it picked "nv" driver for X, but the X server display was
mangled (or black), and - got me to an unreadable/mangled
console. It looked a lot like UPC codes. I was able to chroot into the
partition and install the bin
I am sorry. My computer is in for repair. Anyone else with the same
motherboard?
--
Wrong driver used after installing herd2 on M2NPV-VM
https://launchpad.net/bugs/79210
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Herd 3 was recently released for testing. Could you possibly check what
driver is used with it? Thanks in advance.
** Changed in: xorg (Ubuntu)
Sourcepackagename: xorg => discover-data
Importance: Undecided => Medium
Assignee: Brian Murray => (unassigned)
Status: Needs Info => Con
Here it is!
** Attachment added: "lspci -vv"
http://librarian.launchpad.net/6017229/lscpi
--
Wrong driver used after installing herd2 on M2NPV-VM
https://launchpad.net/bugs/79210
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug report. Could you please include the output of
'lspci -vv' and possibly /var/log/Xorg.0.log showing the vesa driver
being chosen? Thanks.
** Changed in: Ubuntu
Sourcepackagename: None => xorg
Assignee: (unassigned) => Brian Murray
Status: Unconfirmed => Needs Info
