Ok, done. Well, I didn't try installing your package on the live CD system (I'd be surprised if that's possible), but I made a jaunty alpha 3 install on a disk partition that has no valuable data. I had to use the "alternate" install CD for this: Installation with the "desktop" CD totally fails without "safe graphics mode" (the CD boots to a shell prompt, without any indication of how to start an installation) and crashes even in "safe graphics mode", probably due to an xserver bug, as follows: The installation appears to proceed ok until after "importing documents and setting". Then the screen goes black, the monitor goes into power save mode (this happens even if I am moving the mouse curser at that moment), then there is some brief cdrom drive activity, then everything is silent. I believe that this is an xserver bug because when I first booted by successfully installed jaunty alpha 3 system (installed with the "alternate" install CD) and booted for the first time, I didn't use the "text" boot option, then the following happened: I got a warning popup about "low resolution graphics mode", where IIRC I clicked "cancel"... I got a message "stand by for one minute while the display restarts", then the screen went black in the same manner again with the monitor going into power save mode.
Then I remembered your advice to boot with "text" as an additional boot parameter, so I did that, and successfully tested your package -- both the tormod3 and the tormod4 version. Results were identical. startx works, although the resolution is still unpleasantly low IMO. I'm attaching the Xorg.0.log from running startx using the tormod4 version. Thank you for your work on this bug! ** Attachment added: "Xorg.0.log from running startx after having installed xserver-xorg-video-savage_2.2.1+git20081230.aea0496f-0ubuntu0tormod4_i386.deb on jaunty alpha 3" http://launchpadlibrarian.net/21548721/Xorg.0.log -- install failure (regression) with ProSavageDDR graphics chipset https://bugs.launchpad.net/bugs/217004 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
