[Bug 223774] Re: NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
this driver has been removed from Ubuntu, closing it's bugs ** Changed in: xserver-xorg-video-trident (Ubuntu) Status: Confirmed => Won't Fix -- 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
[Bug 223774] Re: NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Changed in: xf86-video-trident Status: Confirmed => Unknown -- 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
[Bug 223774]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-trident/issues/6. -- 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
[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 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
[Bug 223774] Re: [Hardy] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Summary changed: - [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup + [Hardy] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup ** Summary changed: - [Hardy] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup + NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup -- 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
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Tags added: natty -- 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: [HARDY] 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
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Tags removed: natty ** Tags added: lucid -- 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: [HARDY] 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
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Changed in: xserver-xorg-video-trident (Ubuntu) Status: Incomplete = Confirmed -- 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: [HARDY] 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
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
I believe this problem still exists in 10.04 Lucid. My attempts to install 10.04 appear to fail as described in this bug. My computer is a Toshiba 7200CT, and the specs say that the video is a Trident CyberBlade e-4 128-bit graphics accelerator. In xorg.conf it lists BoardName Cyber 9540, which seems to be the correct driver. (The NoDCC work around does not help.) I don't see a way to tag the bug to indicate that it affects Lucid. Would it improve the chances of fixing this bug it I try to install the Natty version of Ubuntu? -- 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: [HARDY] 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
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
This bug report was filed against an old version of Ubuntu. Can you confirm whether this is still an issue in natty? If you don't mind, it would be very helpful if you could update the bug report in launchpad to 'Fix Released' if it is no longer an issue for you, or if it is still occurring under natty, please tag the bug 'natty' so it's easier for us to track. ** Changed in: xserver-xorg-video-trident (Ubuntu) Status: Triaged = New ** Changed in: xserver-xorg-video-trident (Ubuntu) Status: New = Incomplete -- 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: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Changed in: xf86-video-trident Importance: Unknown = Critical -- 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: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Changed in: xf86-video-trident Importance: Critical = Unknown -- 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: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on 30 March 2010. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please feel free to report any other bugs you may find. Thank you. ** Changed in: xserver-xorg-video-trident (Ubuntu Intrepid) Status: Triaged = Won't Fix -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
I realized I had made a mistake, Intrepid Ibex 8.10 will reach EOL on 30 APRIL 2010. Sorry for this. Anyway, I think that one month doesn't make any difference now. -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
I have tested Karmic on the same hardware and still nothing :/ -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Tags added: hardy -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
bug 181176 is the reason why people used NoDDC.. ** This bug is no longer a duplicate of bug 181176 [Hardy Alpha-3] xserver-xorg-core /usr/bin/X goes into infinate loop on Toshiba Satellite 1800 PS181C Trident -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** This bug has been marked a duplicate of bug 181176 [Hardy Alpha-3] xserver-xorg-core /usr/bin/X goes into infinate loop on Toshiba Satellite 1800 PS181C Trident -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
I don't think it makes sense to metnion this in the intrepid release notes, given that this is not a regression from hardy. ** Changed in: ubuntu-release-notes Status: New = Invalid -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
I have tested Intrepid RC and still the same bug :(( -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
And I have tested Intrepid beta and still the same bug :(( Now I try to install Debian Etch. P.S. Can I somehow help to fix this bug? -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
I have tested Intrepid alpha 6 and still the same bug :( -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
Don't think there's a reason to have two upstream tasks on this one. ** Changed in: xorg-server Status: New = Invalid -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Also affects: xorg-server Importance: Undecided Status: New -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
I've forwarded your bug report upstream to https://bugs.freedesktop.org/show_bug.cgi?id=15937. Please subscribe to that bug in case upstream has questions or needs additional information. ** Also affects: xf86-video-trident via https://bugs.freedesktop.org/show_bug.cgi?id=15937 Importance: Unknown Status: Unknown -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Changed in: xf86-video-trident Status: Unknown = Confirmed -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
For the record Debian Etch 'just works' with this laptop. It seems the issue is a regression introduced by new auto-detection in (at least) the Ubuntu version of X.Org -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org No more sea shells: Daniel's Webloghttp://cshore.wordpress.com -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Changed in: xserver-xorg-video-trident (Ubuntu) Importance: Undecided = High Status: Incomplete = Triaged -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
** Changed in: xserver-xorg-video-trident (Ubuntu) Sourcepackagename: xorg = xserver-xorg-video-trident -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
It turns out that the right xorg.conf works (but not the autogenerated from Hardy, and for Gutsy it must be present before the install configures xserver-xorg or it'll hang), provided the NoDDC option is present. I had that option when I tried in Hardy, but I got the xorg.conf wrong (it really sucks that you have no means of generating xorg.conf for cases where autodetection fails; this has been commented on on other bug reports, but you *really* need to do something about this. I would consider myself an advanced user but generating an xorg.conf without prompting (like that of dpkg-reconfigure xserver-xorg in gutsy and before) including not autodetecting, but selecting driver and general monitor type (e.g. 1024x768 @ 60Hz)) is quite more than I want to have to deal with. dpkg-reconfigure doesn't involve learning near as much as writing xorg.conf from scratch). An I forgot to say that I'm using the alternate installer. The xorg.conf I used in gutsy (and hardy when the default one failed) comes from http://michaelminn.com/linux/toshiba1800/ and is as follows: # xorg.conf (X.Org X Window System server configuration file) # # Custom file by Michael Minn Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 EndSection Section Device IdentifierTrident Microsystems CyberBlade/i1 Drivertrident BusIDPCI:1:0:0 Option NoDDC EndSection Section Monitor IdentifierToshLCD OptionDPMS HorizSync 30-71 VertRefresh50-100 EndSection Section Screen IdentifierDefault Screen Monitor ToshLCD DeviceTrident Microsystems CyberBlade/i1 DefaultDepth16 SubSection Display Depth16 Modes1024x768 EndSubSection SubSection Display Depth24 Modes1024x768 EndSubSection SubSection Display Depth16 Modes800x600 EndSubSection SubSection Display Depth24 Modes800x600 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Configured Mouse EndSection Which I changed to : # xorg.conf (X.Org X Window System server configuration file) # # Custom file by Michael Minn Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 EndSection Section Device IdentifierTrident Microsystems CyberBlade/i1 Drivertrident BusID PCI:1:0:0 OptionNoDDC EndSection Section Monitor IdentifierToshLCD OptionDPMS HorizSync 30-71 VertRefresh50-100 EndSection Section Screen IdentifierDefault Screen Monitor ToshLCD DeviceTrident Microsystems CyberBlade/i1 DefaultDepth24 SubSection Display Depth16 Modes1024x768 800x600 EndSubSection SubSection Display Depth24 Modes1024x768 800x600 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Configured Mouse EndSection ** Attachment added: Xorg.0.log.hardy http://launchpadlibrarian.net/14025687/Xorg.0.log.hardy -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] [NEW] [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
Public bug reported: 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 either) 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. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223774] Re: [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup
Please attach your /var/log/Xorg.0.log from after trying to boot Hardy. The one from a working Gutsy would be useful for comparison, as well. ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- [HARDY] NoDDC option doesn't work for trident cyberblade/i1 resulting in system lockup https://bugs.launchpad.net/bugs/223774 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
