I think the original bug report here (NoDCC causes hang) has been fixed.
I am currently testing the trident driver on an ancient laptop here, and
it has many bugs, but this isn't one of them. The "vesa" mode doesn't
work, and most importantly auto-detection doesn't work. Manually writing
your own Xorg configuration and assigning driver as "trident" however,
works fine.
What you need is:
Driver "trident"
Option "AccelMethod" "EXA"
At that point you get the proper response from Xorg:
(WW) TRIDENT(0): Option "NoDCC" is not used
So it simply skips NoDCC in the config file and in turn skips the hang.
I will be opening another bug report regarding detection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/223774
Title:
NoDDC option doesn't work for trident cyberblade/i1 resulting in
system lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/223774/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
