I finally submitted this problem with the vesa driver as bug 414330
half an hour ago, using the ubuntu-bug program.
On Sat, Aug 15, 2009 at 10:20 PM, Peter Belew wrote:
> I've been unable to report the bug on the vesa driver - Launchpad
> won't let me report any new bugs!
>
> BTW this system is se
I've been unable to report the bug on the vesa driver - Launchpad
won't let me report any new bugs!
BTW this system is set up to triple-boot into XP, Ubuntu, and FreeBSD
7.1. I just set up Xorg and Gnome on the FreeBSD partition - and the
vesa driver on that behaves the same way - the system locks
Tormod - installing your savage driver solved the problem. After
installing it, I disabled Xorg running at runlevel 2 by renaming the
symlink to gdm in /etc/rc2.d and restarting the system (with the reset
button this time), then booting and determining that 'reboot' works
properly from the shell, w
Thanks, Tormod - I just downloaded
xserver-xorg-video-
savage_2.3.1~git20090813.36ab23a9-0ubuntu0tormod~hardy_i386.deb
to my laptop ... is that the right one?
I'll install it once I get back to that system.
On Fri, Aug 14, 2009 at 11:37 AM, Tormod Volden wrote:
> Peter, I updated the Hardy xs
Peter, I updated the Hardy xserver-xorg-video-savage package on
https://launchpad.net/~tormodvolden/+archive/ppa to the latest version,
so you can try it (I haven't tested it myself).
--
install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You rec
I recently did a new installation on the gBox computer mentioned above.
It now runs hardy 8.04.3 LTS with a vesa driver - I installed it by
installing first 6.06.1 LTS (in safe mode with screen resolution
specified explicitly) then upgrading. This system works, but crashes
when switching to a text
The patch that was reported to fix the startup failure in this bug
report is now included in Jaunty, so I am closing the bug. Please reopen
if the same failure persists, but file new bugs for other bugs.
xserver-xorg-video-savage (1:2.2.1-4ubuntu2) jaunty; urgency=low
* Cherry-pick 0fae48235841
Hugh,
what I did is that I installed from the Ubuntu 8.10 server CD. IIRC I then
installed GNOME manually with apt-get (which of course pulled in X11) and used
an old xorg.conf file.
--
install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You
Is there a fix for Intrepid? I'm trying to install Mythbuntu 8.10 and
have hit this problem. I duplicated the problem with Ubuntu 8.10.
(For what it is worth, Fedora 10 has this problem too.)
--
install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217
I can confirm that your patch
(xserver-xorg-video-savage_2.2.1+git20081230.aea0496f-0ubuntu0tormod4_i386.deb)
fix the startup problem.
Today I installed jaunty on a pc with a S3 ProSavage8 (KM266/KL266) graphic
card and X didn't start. So I search on launchpad for a bug report and found
this on
Yes, you can install the driver on the live CD (explained in comment 26)
but installing Jaunty is good also.
You get poor resolution because the EDID information from the monitor
can not be retrieved, and X falls back to conservative settings. You
will need to add sync ranges to your xorg.conf man
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
12 matches
Mail list logo
