Red Hat Bugzilla – Bug 121766
Cannot change resolution and refresh rate on S3 Savage/IX in Toshiba Satellite Pro 4300
Last modified: 2007-11-30 17:10:41 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040422
Description of problem:
After installing Fedora Core 2 and upgrading all components to Test 3
via yum everything seemed fine. The install was done undocked. I later
docked the laptop. Still fine. I changed the monitor under display
settings to match the external Compaq V70 monitor I was using and
rebooted. Now the display is stuck at what looks like 640x480. The
changes do get written to xorg.conf but there are errors in the Xorg log.
(EE) SAVAGE(0): vm86() syscall generated signal 11.
(EE) SAVAGE(0): Failed to fetch any BIOS modes. Disabling BIOS.
When removed from the docking station the laptop display only displays
640x480 as well and the refresh rate is far to low.
I'll attach the Xorg log.
Thanks for the help.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Change monitor to an external monitor set resolution to 1024x768
Actual Results: Display @ 640x480
Expected Results: Display @ 1024x768
Created attachment 99716 [details]
Xorg Log File
I just installed FC2 Test 3 and I've had a similar problem with my
GeForce FX 5900. The problem seems to be related to the nv driver as
when I select the VESA driver the resolution will change (however the
refresh rate is stuck at 60, ouch my eyes!) The weird thing is the nv
driver worked FINE on my initial boot (right after I selected 1024x768
and Millions of Colors), up until the Display section of FirstBoot.
This only gave me the option of 640x480 or 800x600. It doesn't matter
which I select, it will only display 640x480. The applet that handles
Xorg config also automatically reverts me to the nv driver after I
select the VESA driver, so I get stuck in low res land again.
I've had a similar problem while trying to run FC2 Test 3 on an IBM
Thinkpad T23 with a Savage/IX.
Whether I specify 'Generic LCD 1024x768' or 'Generic Monitor
1024x768', I'm limited to 640x480 at a very low refresh rate.
The Display applet gives me choices of '800x600' and '640x480' only,
but no matter what I choose the resolution stays at what looks like
640x480. Similarly to Tim, the driver seemed to work fine at first
(ie. looked to be running at 1024x768), right up until FirstBoot started.
Four more people with the same problem on firstname.lastname@example.org
today about this.
This is a bug in system-config-display, not xorg-x11
Here is my post:
I got the same problem with my Nvidia Geforce 4, except that half the
time it was in 1024x768, half the time in 640x480.
It appears that the new system-config-display doesn't enable the hard
coded screen settings in your /etc/X11/xorg.conf. Instead, it relies
on DCC probes. My monitor/card combination has some problem, and the
DCC Probe fails half the time. To work around this, edit
/etc/X11/xorg.conf and look in the Monitor section. Uncomment the
HorizSync and the VertRefresh lines.
### Uncomment if you don't want to default to DDC:
VendorName "Monitor Vendor"
ModelName "Lite-On A1770NSL"
DisplaySize 320 240
### Uncomment if you don't want to default to DDC:
HorizSync 30.0 - 69.0
VertRefresh 50.0 - 120.0
Im having the same issue on an older box with a ati mach 64 card, my
resoution will not change either, as it is stuck on 640X480. Hopefully
this issue can get fixed soon, and I can get back to high res land. :)
bug 121855 is a duplicate of this
Uncommenting HorizSync and VertRefresh on my Voodoo 3 2000 PCI got my
screen back up to 1024x768, but now the login screen is using a TINY
font that is unreadable!! Not a biggie, but just thought I'd mention
it. Anyone know how I might edit this to a larger font? Using the
default bluecurve login page.
> (EE) SAVAGE(0): vm86() syscall generated signal 11.
> (EE) SAVAGE(0): Failed to fetch any BIOS modes. Disabling BIOS.
This problem is a kernel bug which breaks vm86(), and is fixed in
the latest rawhide kernel. This kernel bug will affect all video
drivers which make calls into the VESA BIOS, including savage, nv,
radeon, vesa, and other drivers. A vast array of problems can
arise depending on what the driver is using the BIOS for, since
any call will potentially fail. Please upgrade to the latest kernel
and see if this resolves the issue.
If the problem persists, it is possible that you may also be
experiencing bug #120950. Please try the workaround in that report
as well to see if the issue is resolved. If everyone else CC'd on
this report could also test that and report back, that would be
helpful information as well.
Uncommenting the DDC lines seems to have resolved the problem.
I also had some other video issues where it looked like there was
static on the screen but that was resoled when I upgraded to to Kernel
2.6.5-1.350. Thanks for all the help!
Ok, thanks for the update Greg!
*** This bug has been marked as a duplicate of 120950 ***
I have the same poblem (stuck with 640x480 resolution) on my
Thinkpad T22 (Savage 1/X).
As per the suggestion above, I upgraded the kernel to the latest
It did not resolve the Display issue. I still get the : "vm86()
syscall generated signal 11" errors.
As well as upgrading kernel, did you modify your xorg.conf as per
If you see anything concerning vm86() errors in your log file, it
is a kernel bug in the kernel you are running. In such case, please
file a new bug report against the kernel component, and attach your
kernel log, X server log, and full details to the report, and the
output of "rpm -qa | grep ^kernel" and also "uname -a", and a kernel
engineer can review the report and determine what action is necessary
to resolve the problem.
Thanks for testing.
In my case, the kernel upgrade did not fix the problem.
But creating a new, clean config file fixed the vm86 errors.
When I upgraded from an earlier version, the xorf.conf did not get
I had to follow the comment 4 suggestion to configure the X server
resolution to > 640x480 (such as 1024x768).
Thanks for all your suggestions.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.