← Back to team overview

desktop-packages team mailing list archive

[Bug 223774]


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 Desktop
Packages, which is subscribed to xserver-xorg-video-trident in Ubuntu.

  NoDDC option doesn't work for trident cyberblade/i1 resulting in
  system lockup

Status in Release Notes for Ubuntu:
Status in xf86-video-trident:
Status in X.Org X server:
Status in xserver-xorg-video-trident package in Ubuntu:
Status in xserver-xorg-video-trident source package in Intrepid:
  Won't Fix

Bug description:
  In Gutsy it was possible get the display on a Toshiba Satellite 1800
  (which I'm putting together for an group I'm part of) working by
  editing the Device section of of /etc/X11/xorg.conf to have Option
  "NoDDC" "true".  This no longer works in Hardy and thus the laptop is
  a paperweight with Hardy.  (vesa driver doesn't work either, for

  The display adaptor built into the laptop is a Trident CyberBlade/i1

  A fresh install of Hardy does not solve the problem.  Only reverting
  to Gutsy and editing xorg.conf does.

  In fact for Gutsy it is necessary to install an xorg.conf that has
  NoDDC before the initial installation of xserver.org is made or else
  the installer hangs with a blank screen during the configuration of
  that package.

  This makes Ubuntu unsuitable for distribution with this laptop as it'd
  be far too easy for someone to end up with a non-working system, and
  depending on who gets it (it's a donation that's being raffled off), I
  may not be close enough to support the end user in case of trouble.

To manage notifications about this bug go to: