I made a brief survey tonight among members of a LUG I am in.
One person tried to figure out how to change the mouse pointer, and gave
up after trying for a while.
His teenage son managed to find the dialog, with a fair amount of
prompting from me.
Another person, who is very familiar with Fedor
I mentioned above that I experienced a crash in Firefox while changing a
mouse pointer. Actually what I was doing was trying to start this bug
report and experimenting with changing mouse pointers from the theme
dialog, and trying to see what would happen if I changed the pointer in
one theme, then
See Gnome Bugzilla - Bug no. 537128 - 'mouse pointer themes missing' - I
added to that. I'll look for other existing Gnome bug reports as well.
--
Mouse pointer selection has become confusing under Gnome 2.22.3 under hardy
https://bugs.launchpad.net/bugs/259195
You received this bug notification
I also filed a new usability bug on Gnome's Bugzilla, number 548714.
--
Mouse pointer selection has become confusing under Gnome 2.22.3 under hardy
https://bugs.launchpad.net/bugs/259195
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Two cycles ago? This only appeared in Ubuntu LTS with the recent
release. So people using LTS have only had a few weeks to notice the
change, and possibly suggest changes.
Discussed at length? This did not involve Ubuntu LTS users, as far as I
know.
This hasn't appeared in Debian stable yet.
Des
** Attachment added: "Xorg.0.log - intrepid - booting VESA from text mode"
http://launchpadlibrarian.net/21551780/Xorg.0.log
--
Screen mode with 0 Hz refresh rate with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
and Samsung SyncMaster 570S tft
https://bugs.launchpad.net/bugs/320313
You received
Public bug reported:
Binary package hint: xserver-xorg-driver-vesa
While investigating bug # 294899, on both intrepid and a development
version of jaunty, I typically booted a desktop live CD into text mode,
selecting the vesa driver, then, after possibly changing the xorg.conf
file (or not) I oc
I just filed the 0 Hz screen mode on "vesa' - # 320313 - first against
"intrepid" I will then reproduce it with "jaunty"
--
No signal with Samsung SyncMaster 570s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I repeated the same steps, booting the development version of Jaunty
this time.
The results were identical, including the 848x480 mode with 0 Hz
refresh.
I neither case did I actually try to use that mode! I only tried the
848x600 and 800x60 modes, in fact.
I did put the Option "ModeDebug" "true
I have attached the output of "xrandr --verbose", run under jaunty as
user "ubuntu", after the X server has started.
This shows the screen modes as described above.
** Attachment added: "output of xrandr --verbose"
http://launchpadlibrarian.net/21574849/xrandr.txt
--
Screen mode with 0 Hz re
One note - after I try to shut down or log out from X, the screen goes
into an unsupported mode - the "Video mode not supported" message pops
up on the Samsung display. So I end by having to reset the cpu to
restart and remove the CD.
A note about the 848x600 mode - initially, the left side of the
I tried the same experiment with the Jaunty alpha-3 desktop disk.
(Previous Jaunty experiments were done with the alpha-2 disk).
There is something new:
A message box pops up when changing screen modes:
=
"Could not apply the selected configuration"
"Method i
I tried to get the UniChrome driver to work on my Averatec 3280
yesterday; the end result was a grey screen with pieces of the round
"waiting" cursor stuck at edges of the screen...
On Sun, Jan 25, 2009 at 8:28 PM, Aeb1barfo wrote:
> I had to back off the UniChrome driver and use the via driver o
>
>
> " I PINK, therefore I HAM "
>
> --- On Mon, 1/26/09, Peter Belew wrote:
> From: Peter Belew
> Subject: Re: [Bug 296142] Re: Installer fails to recognize display on
> Averatec 3280
> To: aeb1ba...@yahoo.com
> Date: Monday, January 26, 2009, 7:19 AM
>
To add to information I've posted above:
My Averatec 3280 laptop is now a dual-boot system - my primary OS is
Debian:
Linux 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686 GNU/Linux
Debian GNU/Linux 5.0
xserver-xorg-video-openchrome 1:0.2.902+svn5 X.Org X server -- VIA
display driver
I'm
Bug #186103 gives some information on the original xorg.conf file from
an earier attempt to run Ubuntu on this system. I didn't provide an
Xorg.0.log file then.
--
Installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/296142
You received this bug notification beca
My current installation on this Averatec 3200 is the second Linux on
the system. I have set it up to boot in text mode (by renaming the gdm
symlink in /etc/rc2.d from S30gdm to K30gdm. Then I type 'startx' to
start the X server.
I am still having problems getting the right driver for VIA to work,
Here is the /var/log/Xorg.0.log file from using the vesa driver, started
with 'startx', see the xorg.conf file in the previous comment.
** Attachment added: "xorg.0.log - running vesa"
http://launchpadlibrarian.net/21666307/Xorg.0.log
--
Installer fails to recognize display on Averatec 3280
h
Here's another experiment: I booted the jaunty alpha-3 CD in text mode,
then mounted a disk volume and created a directory to save the resulting
xorg.conf and the soon-to-be generated /var/log/Xorg.0.log file in. I
opened a second console (ctl-alt-F2) and changed to the new directory in
both consol
I just tried again to boot the 9.04 'jaunty' CD - I was unable to get
a console with ctrl-alt-F1, trying several times before and after the
screen started displaying the little windows saying the current screen
mode. Apparently the driver is trying a number of modes, and doesn't
get feedback from t
Oh, good. I was wondering whether there was a way to boot in text
mode. That will make it MUCH easier to proceed!
Also removing the splash progress bar might help, I'll see.
I'll be home in a couple of hours to try this! Then I can try either
the new driver, or my old xorg.conf file, or both. I e
I made some progress - I was able to boot into text mode after
modifying the boot parameters - adding 'text' and removing the
'splash', and specifying the vesa mode.
At this point, I was able copy files to this system from another, using
scp.
I then copied the experimental driver and my old xorg
Here is the log, trying to startx with the driver on the Jaunty alpha
disk.
As I said above, I was unable to install the driver under development:
xserver-xorg-video-savage_2.2.1+git20081117.aea0496f-
0ubuntu0tormod_i386.deb
** Attachment added: "Xorg.0.log 14 Jan 2009"
http://launchpadlib
Oops - I'll download the right driver and try again. Actually I'm not
sure what IS the right version..
On Thu, Jan 15, 2009 at 1:45 AM, Tormod Volden wrote:
> Thanks for the log. Well, you picked the wrong (Intrepid) version from
> the PPA, that's why you get the xserver-xorg-video-4 conflict.
>
I went back to trying the 8.10 Intrepid live CD - using 'text' and
eliminating 'splash' in the boot line enables it to boot in text mode,
then using the old xorg.conf from 7.04 enables X to start.
On Wed, Jan 14, 2009 at 3:49 PM, Tormod Volden wrote:
> If you add "text" to the boot parameters (th
Thanks! I'll download that tonight or tomorrow, and try it. I suspect
it will work. And I'll post my results.
It's good this is going upstream - this problem affects not only
Ubuntu and Debian, but Fedora as well, when I've tried recent live
CDs. Probably several other distros, including Gentoo. I
I can't find the file. Could you send me the exact URL for the page it's
on?
On Thu, Jan 15, 2009 at 2:26 PM, Tormod Volden wrote:
> The right version for Jaunty would be xserver-xorg-video-savage -
> 1:2.2.1+git20081230.aea0496f-0ubuntu0tormod . On the PPA page there is a
> column called "Series
The nearest file I find is
xserver-xorg-video-savage_2.2.1+git20081230.aea0496f-0ubuntu0tormod_i386.deb
(96.6 KiB)
On Thu, Jan 15, 2009 at 2:26 PM, Tormod Volden wrote:
> The right version for Jaunty would be xserver-xorg-video-savage -
> 1:2.2.1+git20081230.aea0496f-0ubuntu0tormod . On the PP
With that driver, I was able to startx ok!
The only glitch was that the user-switcher applet wouldn't start (or
kept stopping each time I clicked on the popup which announced that it
was failing).
I'll attach the log file here.
** Attachment added: "Xorg.0.log - jaunty"
http://launchpadlibrar
That was the wrong xorg.conf file.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
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
Here is the latest xorg.conf that works with the 9.04 driver
The log file shows complaints about things like nonexistent fonts,
nothing serious.
The real remaining issue, in my opinion, is whether the installer will
recognize which driver to use, and set up the right screen mode, and
when that wi
Here is the latest xorg.conf that works with the 9.04 driver
The log file shows complaints about things like nonexistent fonts,
nothing serious.
The real remaining issue, in my opinion, is whether the installer will
recognize which driver to use, and set up the right screen mode, and
when that wi
Here's the xorg.conf file - we seem to have some problem getting the
right files! :)
** Attachment added: "xorg.conf - jaunty"
http://launchpadlibrarian.net/21273903/xorg.conf
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bu
This Xorg.0.log file was generated as requested - with no xorg.conf
file.
There was no crash - no screen was found, as the log file says, so
console 1 stayed in text mode.
Putting in the old xorg.conf (as in the previous posting) allows X to
start.
** Attachment added: "Xorg.0.log - no xorg.conf
I was finally able to boot the live CD, by booting in text mode with the
display selection set to vesa.
Then I had to run startx to start the vesa X server.
After that it is possible to click on the install icon and install.
after rebooting, there were some difficulties getting the X server to
s
I tried the new debug package containing a screen driver. It was able to start
X , arriving at a screen resolution of 848x600 at 61 Hz.
Once I started, the user switcher was aborted (as usual) I suspect that is due
to my starting with 'startx' rather than a login.
Trying to switch screen modes,
The date in the log file is in UTC - I hadn't set the time zone.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This evening I repeated the experiment, this time with my old xorg.conf
file containing explicit driver settings, such as:
Section "Device"
Identifier "S3 Inc. VT8375 [ProSavage8 KM266/KL266]"
Driver "savage"
BusID "PCI:1:0:0"
Option
I think the xorg.conf generated when the system started up in failsafe
mode specifies "vesa" just because the system was started in failsafe
mode. So I should have changed "vesa" to "savage".
Now my xorg.conf with all the screen parameters does specify "savage",
so the right driver would have been
output of "lspci -vvnn"
system is now running Debian 5.0.
** Attachment added: "output of "lspci -vvnn""
http://launchpadlibrarian.net/21095460/lspci-vvnn.txt
--
Installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/296142
You received this bug notification be
The previous run of lspci was done in user mode - Here I re-did that as
root, providing a bit more information about the video controller, for
example.
** Attachment added: "output of "lspci -vvnn" run as root"
http://launchpadlibrarian.net/21095503/lspci-vvnn.txt
--
Installer fails to recogn
So I should download the normal Jaunty live CD, boot in failsafe vesa
mode, also have your downloaded driver on my HD. How do I install your
driver from where it is?
Peter
On Sun, Jan 11, 2009 at 3:28 PM, Tormod Volden wrote:
> Please also add
> Option "ModeDebug" "true"
> to the Device sectio
I can't get the Jaunty CD to boot into X, even in 'safe' mode.
The Samsung Syncmaster display won't accept any of the modes the driver
tries.
Peter
On Sun, Jan 11, 2009 at 12:04 PM, Tormod Volden
wrote:
> This certainly looks wrong in your original log file:
> (II) SAVAGE(0): Configured Monitor
1) I tried first editiing the original xorg.conf, changing 'vesa' to
'savage'.
2) Then I tried the above way: booting with "text", but not specifying
safe mode.
In each case, a compatible screen mode was not found, and the X server
failed to start.
Here, I have attached the log file for the fi
Log file for second case
** Attachment added: "Xorg.0.log for second case"
http://launchpadlibrarian.net/21440895/Xorg.0.log4
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
B
Thanks!
Now I'm going to revisit bug #255561 - which refers to the same Samsung
display but a different display card on a Dell machine.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 212510 ***
https://bugs.launchpad.net/bugs/212510
Although I originally reported this on a 'duplicate' bug thread, this
should be separate as it is on different hardware from other reporters.
That 'duplicate' was reported fixed - since this is still a problem
*** This bug is a duplicate of bug 212510 ***
https://bugs.launchpad.net/bugs/212510
Oh, dear - I'll have to test without the kvm switch - quite an
inconvenience, but I should do that.
On Mon, Jan 19, 2009 at 3:50 PM, Tormod Volden wrote:
> *** This bug is a duplicate of bug 212510 ***
>
I just ran the 2.2.1+git20081230.aea0496f-0ubuntu0tormod3 driver, and it
started into 800x600 mode (with allowable modes
800x600, 640x480, ). At the moment I have the monitor plugged directly
into the gBox computer. I'll retry with the kvm switch.
** Attachment added: "Xorg.conf using the
I got the same resolutions with the monitor plugged back into the kvm
switch. Another log appended!
"MiniView" 2-port KVM
** Attachment added: "Xorg.0.log - Jaunty - using kvm switch now."
http://launchpadlibrarian.net/21493740/Xorg.0.log
--
No signal with Samsung SyncMaster 750s and ProSava
When I connected without the KVM switch, I used no special cables or
adapters - the monitor's cable was plugged directly into the gBox
computer.
By the way I haven't recorded the output of the get-edid | parse-edid on
the gBox - I couldn't install those for Jaunty and the installed system
on that
I don't think the KVM switch has anything to do with the problem. The
same monitor and KVM switch are used with the gBox computer for which
bug # 294899 was reported, and I was able to get similar results for the
initial resolution whether I was connecting the monitor through the KVM
switch or conn
I am attaching the output of
get-edid | parse-edid > edid.txt 2>&1
while the KVM switch is NOT attached.
Note that there is no difference - the KVM does not affect the output.
** Attachment added: "edid results without KVM switch attached"
http://launchpadlibrarian.net/21512527/edid-nokvm.
The gBox computer is a dual-boot between Windows XP and Debian 5.0.
I actually don't remember the exact procedure I followed when
installing Windows, but it was no problem. For Debian, after this
started happening, It was necessary to use an old xorg.conf file.
On Wed, Jan 21, 2009 at 1:12 PM, To
On the Debian 5.0 machine (gBox) it turns out that sh is just a symlink
to bash, whereas on Ubuntu it's a symlink to dash.
Here's the screen output from running get-edid:
billy:~# get-edid > edid.bin
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10
This page gives the supported modes for this Samsung TFT monitor:
http://www.pcstats.com/articleview.cfm?articleid=610&page=5
Resolution Freq Hor. Freq Ver. Pixel Clock Standard
640x350 31.5kHz 70Hz25.2MHz VGA
720x400 31.5kHz 70Hz
Here's an Xorg.0.log file from booting Knoppix 5.1 on this gBox
computer.
Available screen modes in the knoppix utility for switching modes were
1024x768, 800x600, 640x480, all around 75 Hz.
** Attachment added: "Xorg.0.log - billy, knoppix"
http://launchpadlibrarian.net/21527089/Xorg.0.log.gb
Here's the xorg.conf file running Knoppix 5.1 on the gBox
** Attachment added: "xorg.conf file - knoppix on gbox"
http://launchpadlibrarian.net/21527165/xorg.conf-gbox-knoppix
--
No signal with Samsung SyncMaster 570s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug
How do I build this? Should I build this under Jaunty or is an earlier
Ubuntu Ok for the build?
Also, should I still file the bug about the 0 Hz scan under the VESA
driver, and should I use the default xorg.conf or none at all for that
test? - I'm not positive about which I did for that test.
On
I followed those instructions on my Averatec 3280, and it seems to
work now (I am still booting into text mode and using 'startx' to
start the X server. The only problem I have now is that X starts in a
very high res screen mode that doesn't work properly on this system -
the screen contents are m
Here is the xorg.conf file again
** Attachment added: "xorg.conf file with resolution specifications"
http://launchpadlibrarian.net/22311036/xorg.conf
--
Installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/296142
You received this bug notification because you
After restoring the normal S30gdm symlink in /etc/rc2.d, I find that
Ubuntu now boots normally into a 1024x768 screen.
Thanks to j.eason for pointing out the instructions for building the
openchrome driver!
--
Installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/
Also the newly-built driver solves the problem of the screen flashing in
multiple colors when the X server shuts down. This is the first time
this has stopped with either Ubuntu or Debian on this laptop!
--
Installer fails to recognize display on Averatec 3280
https://bugs.launchpad.net/bugs/2961
This also works in Debian 5.0 (lenny) on the same laptop (dual boot into
either Linux) - I recompiled the driver in that system too.
An essential thing here is that the system properly recognized the video
controller and that reasonable screen modes are set up in xorg.conf.
Here, I did that manua
I have just tried booting the Ubuntu 9.04 Beta CD (as a live CD) on this
Averatec 3280 laptop. There is a significant improvement in the
situation, but it is not quite perfect. What happens is that a large
range of resolutions, above and below the optimum resolution of 1024x768
for the LCD display
Note that the 1024x768 resolution setting shows as having a 0 Hz refresh
rate.
I've attached the Xorg.0.log as it was before I changed the screen
resolution.
** Attachment added: "Xorg.0.log before changing resolution to 1024x768"
http://launchpadlibrarian.net/25503213/Xorg.0.log.20090415
--
Here is the Xorg.0.log after the screen resolution was changed from
1600x1200 to 1024x768.
Note that the driver actually changes the refresh rate to 60 Hz,
according to the log.
** Attachment added: "Xorg.0.log after changing resolution to 1024x768"
http://launchpadlibrarian.net/25503396/Xorg.
*** This bug is a duplicate of bug 271138 ***
https://bugs.launchpad.net/bugs/271138
This appears to have been fixed in the Ubuntu 9.04 Beta release - that
worked fine on both the Jetway systems I have. Also an unreported
problem in which the systems didn't start with consistent screen
resolut
I was able to boot the Ubuntu 9.04 Beta live (desktop) CD, and X came
up properly.
However, screen resolutions were limited to 800x600, 640x480, 400x300,
and 320x240.
I have attached the Xorg.0.log file.
I expect to try to use an old xorg.conf file, to force the 1024x768
mode supported by the S
I tried using an xorg.conf file which specifies screen resolutions up to
1024x768, and that didn't work - the Samsung display just kept
showing its "display resolution not supported" popup all over the
screen.
So possibly the fixed driver for 8.x versions hasn't been incorporated
into 9.04 Beta
Should I file a separate bug in the resolution issue (for 9.04 beta) -
that I can't get the display to run at 1024x768?
On Thu, Apr 16, 2009 at 12:20 AM, Tormod Volden
wrote:
> What is the fixed driver for 8.x versions? The fix for this bug is in
> Jaunty with -savage 1:2.2.1-4ubuntu2.
>
> ** Bug
I have tried the live CD for the 9.04 beta. This boots properly, but
initially allows only screen resolutions 800x600 and below.
However, I can edit /etc/X11/xorg.conf, as attached below, to specify
specific screen resolutions, including the desired 1024x768 resolution,
log out, and log back in,
Actually, I was in error regarding the resolution. I used the wrong
procedure for getting a modified xorg.conf to work.
Editing the xorg.conf file, logging out, then logging back in sets the
resolution to 1024x768 (see also bug 255561, with the same monitor but a
different computer and display car
Adding display-resolution parameters to xorg.conf allows one to select
resolution from a specified list. In this case, I have specified
1024x768, 800x600,and 640x480.
There is still an anomaly - 720x576 and 720x480 show up - both showing 0
Hz.
I've attached the new xorg.conf.
** Attachment added
Public bug reported:
The link below in the manual page for 'mount' is dead:
Mount options for reiserfs
Reiserfs is a journaling filesystem. The reiserfs mount options are
more fully described at http://www.namesys.com/mount-options.html.
The owner of this URL, Hans Reiser, is i
Fortunately, much of Reiser's company's site is archived at:
http://web.archive.org/web/20071023172417/www.namesys.com/
and
http://web.archive.org/web/20071010003927/www.namesys.com/mount-
options.html
is apparently the page referenced in the man page for 'mount'.
Hopefully, someone is maintai
Public bug reported:
Binary package hint: xserver-xorg-video-ati
I am able to make video work on this system running the 6.06 LTS
live/desktop CD, manually selecting the screen resolution.
But I am unable to get Xorg to work under later releases. In this case,
I installed 8.10 using the alternat
Result of lspci -vv
** Attachment added: "lspci -vv output"
http://launchpadlibrarian.net/30089592/lspci.txt
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because you are a member of Ubuntu
Bugs, w
lsmod output
** Attachment added: "lsmod output"
http://launchpadlibrarian.net/30089614/lsmod.txt
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
xorg.conf file based on one generated running 6.06 LTS
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/30089711/xorg.conf
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because you a
xorg.conf.new - generated on FreeBSD 7.1 using command
Xorg -configure
on the same system.
Running the same command on Ubuntu crashed.
** Attachment added: "xorg.conf.new from FreeBSD"
http://launchpadlibrarian.net/30089746/xorg.conf.new
--
Xorg won't start on PC with ATI Technologies In
Xorg.0.log - from trying to run with vesa driver.
** Attachment added: "Xorg.0.log - running vesa"
http://launchpadlibrarian.net/30089776/Xorg.0.log
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification be
Xorg.0.log - trying to use ati driver
** Attachment added: "Xorg.0.log - running ati driver"
http://launchpadlibrarian.net/30092974/Xorg.0.log2
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because
I have just installed Ubuntu 7.10 on this system. On starting the
installer, I specified the screen resolution as 1024x768x24. The
installation went well, though this system is slow by today's
standards.
Now I am doing an online upgrade to 8.04 LTS. I'm not sure what driver
was selected. In the mo
In my case, the upgrade to 8.04 after the installation of 7.10 went
well. The display driver selected in xorg.conf is 'vesa'.
On Wed, Aug 12, 2009 at 12:28 AM, Peter Belew wrote:
> I have just installed Ubuntu 7.10 on this system. On starting the
> installer, I specified the scre
** Attachment added: "ApportLog.txt"
http://launchpadlibrarian.net/30441542/ApportLog.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/30441543/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30441544/Dependencies.txt
** Attachment
It turns out I had actually built an openchrome driver some time ago
(I have to look at my Launchpad email to determine the date) in order
to deal with this or a related problem.
At any rate, I downloaded the current sources from the OpenChrome
server, copied in the patched via_driver.c file, and
Please see my comments in bug #296142 regarding my earlier installation
of the openchrome driver (in both ubuntu and debian).
Also, I tried the live CD for Karmic Koala 9.10, and the only real
problem with display is that it also chooses a too-high resolution for
the screen, so that only the upper
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
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
and back, reboot, etc properly.
I'll submit that as a bug against the vesa driver. (Actually I didn't
try the savage driver that comes with 8.04 LTS - I understand the
fixes didn't get into a release before Jaunty).
On Fri, Aug 14, 2009 at 2:16 PM, Peter Belew wrote:
> Thanks, T
the system locks up on
exiting from Gnome. I haven't tried the savage driver on that system,
if it has one.
On Fri, Aug 14, 2009 at 6:22 PM, Peter Belew wrote:
> Tormod - installing your savage driver solved the problem. After
> installing it, I disabled Xorg running at runlevel 2 by renaming
Public bug reported:
Binary package hint: xserver-xorg-video-vesa
System with S3 ProSavage8 running 8.04.3 LTS crashes on logout
The 8.04.3 LTS system runs Ok, but crashes when switching to a text
console, when logging out (to change users), or when shutting down. (See
below)
This is the same s
** Attachment added: "lspci --vv output"
http://launchpadlibrarian.net/30381465/lspci.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30381466/Dependencies.txt
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving gr
** Attachment added: "lsmod output"
http://launchpadlibrarian.net/30381507/lsmod.txt
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are a m
** Attachment added: "/var/log/messages"
http://launchpadlibrarian.net/30381619/messages
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are
Information about file system usage
** Attachment added: "fdisk and df output"
http://launchpadlibrarian.net/30381714/fdisk.txt
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You receive
** Attachment added: "/var/log/kern.log"
http://launchpadlibrarian.net/30381742/kern.log
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/30381853/Xorg.0.log
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are a me
** Attachment added: "xorg.conf - using vesa driver"
http://launchpadlibrarian.net/30381801/xorg.conf
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification be
101 - 200 of 909 matches
Mail list logo
