From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021128
Description of problem:
When I start X (startx) on my laptop (IBM Thinkpad T22), the screen goes blank
and stays that way until I hit Ctrl-Alt-Backspace. I can still switch between
virtual consoles as if X were running. The driver used is "savage" and the
boardname is "S3 Savage/MX", just like it is in Psyche. I tried the XF86Config
file from Psyche, but the results were the same.
FWIW, I could only do a text install of Phoebe. The standard install just has a
bunch of "junk" on the screen.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: Blank screen.
Expected Results: Graphics
Ctrl-Alt-BS drops back to the console.
The same thing happens on a T23 during the install process,
identified by S3's id program as "SuperSavage/IXC SDR (584)".
(++) Log file: "/dev/null", Time: Tue Dec 24 01:13:43 2002
(++) Using config file: "/tmp/XF86Config.test"
(EE) Failed to load module "glx" (modules does not exist, 0)
(EE) SAVAGE(0): Failed to fetch any BIOS modes. Disabling BIOS.
error opening security policy file /etc/X11/xserver/SecutiryPolicy
Could not init font path element unix/:7100, removing from list!
cat: //.Xauthority: No such file or directory
On T21 (Savage MX I think) X does start but has really bad distortions in the
picture (mouse movements cause all sorts of random flickering around the screen)
with same exact configuration where RH8.0 worked flawlessly. Dropping bpp from
24 to 16 seems to fix it however.
Hmm, it's possible I suppose that the new Xcursor code has messed up the
Savage driver somehow. I don't have Savage hardware personally though to
investigate. Could each of you please attach your X server config file
and log file as separate individual uncompressed file attachments to the
bug report? I will contact the Savage driver maintainer and pass along
to him the information you provide. Hopefully it's nothing major.
Also, could each of you try using the option "swcursor" in your config file,
and if that does not work, please try using "hwcursor". These options
go in the Device section of the config file as documented in the XF86Config
Thanks in advance.
Created attachment 88949 [details]
This is with hwcursor turned on. Everything else is the same.
Created attachment 88950 [details]
XF86 Log file with swcursor
Log file with swcursor enabled.
Created attachment 88951 [details]
XF86 log with hwcursor
Log file with hwcursor enabled.
Created attachment 89037 [details]
T23 - XF86Config
Created attachment 89038 [details]
T23 - XFree86 log file with HWCursor on
Created attachment 89039 [details]
T23 - XFree86 log file with SWCursor on
First seen in XFree86-126.96.36.199-0.20021126.8 and still broken in
Hmm, something funny with T21: it *did* work the first time I tried but not
after that (X starts up but with blank / screwed up screen). Adding "noaccel"
option "fixes" it. Additionally with "hwcursor" or without it the mouse cursor
does show but it also shows the original X shaped cursor in the middle of the
screen (which however vanishes by itself sooner or later, haven't been able to
figure out when/why). Adding "swcursor" option fixes the cursor issue. This on
all XFree86 versions from the phoebe-version up to XFree86-188.8.131.52-20021230.3
Tryed Phoebe 2 (8.0.93) and the X-based install works (though there's a lot of
flicker), but I still cannot start X after logging in. Just sits at a blank
screen until I hit CTRL-ALT-BACKSPACE.
I'm currently awaiting the release of the savage driver 1.1.27t
source code from Tim Roberts for this issue. hopefully it won't be
Any status on this bug and if the driver has been released?
(hehe, try to help now I'm pushy? LOL)
I haven't heard back an email response from the Savage driver author,
and there is no Savage driver update released yet, so I'm assuming that
he is busy with non-XFree86 related things currently and that the
driver is unmaintained.
I am changing the Savage/MX variants to use the "vesa" driver for our
next release. If 'vesa' doesn't work, then the hardware is considered
unsupported, and only hardware that works with the 'savage' driver is
*** This bug has been marked as a duplicate of 80346 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.