Thank you for taking the time to report this bug and helping to make Ubuntu
better.
We are closing this bug report because it lacks the information we need to
investigate the problem, as described in the previous comments. Please reopen
it if you can give us the missing information, and don't
** Tags added: feisty
--
Feisty doesn't recognice 3D Blaster Savage4 graphics
https://bugs.launchpad.net/bugs/97296
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
[This is an automatic notification.]
Hi kranebitt,
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and
your problem may have been
Are you still having problems in versions later than Feisty?
--
Feisty doesn't recognice 3D Blaster Savage4 graphics
https://bugs.launchpad.net/bugs/97296
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: xserver-xorg-video-savage (Ubuntu)
Sourcepackagename: xorg = xserver-xorg-video-savage
Importance: Undecided = High
Status: New = Triaged
--
Feisty doesn't recognice 3D Blaster Savage4 graphics
https://bugs.launchpad.net/bugs/97296
You received this bug notification
** Changed in: xorg (Ubuntu)
Status: Needs Info = Unconfirmed
--
Feisty doesn't recognice 3D Blaster Savage4 graphics
https://bugs.launchpad.net/bugs/97296
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Please attach your /var/log/Xorg.0.log, /etc/X11/xorg.conf and the
output of 'sudo lspci -vvnn',
There is a change the savage driver works with it. You could try editing
the xorg.conf and change the Driver in Device section to savage.
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) =
SUDO LSPCI -vvnn output:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT82C693A/694x [Apollo
PRO133x] [1106:0691] (rev 02)
Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8023]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR-
xorg.0.log:
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: Linux Ubuntu
Current Operating System: Linux desktop 2.6.20-13-generic #2 SMP Sun Mar 25
00:21:25 UTC 2007 i686
Build Date: 27 March 2007
Before
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type man /etc/X11/xorg.conf at
11 matches
Mail list logo
