Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: If savagefb instead of vesafb is used on a laptop, there is a horizontal shift of 1 pixel (to the left direction). Version-Release number of selected component (if applicable): kernel-2.6.21-1.3228.fc7 How reproducible: Always Steps to Reproduce: 1. boot laptop in normal mode (no vesafb mode specified) into single user mode 2. modprobe savagefb Actual results: leftmost vertical pixel line is missing Expected results: same result as on vesafb (which is correct) Additional info: Display: 1024x760 Chipset: 01:00.0 VGA compatible controller: S3 Inc. VT8636A [ProSavage KN133] AGP4X VGA Controller (TwisterK) (rev 01) (prog-if 00 [VGA]) Subsystem: Uniwill Computer Corp Unknown device 8003 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 9 Memory at dfe80000 (32-bit, non-prefetchable) [size=512K] Memory at d0000000 (32-bit, prefetchable) [size=128M] Expansion ROM at dfe70000 [disabled] [size=64K] Capabilities: [dc] Power Management version 2 Capabilities: [80] AGP version 2.0 Playing with fbset doesn't help, there is not any reaction if used.
Same happen with kernel-2.6.22.1-33.fc7 Also it occurs that in run level 3 a user can close a started X session, but no longer see console back again.
Hello Peter, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Cheers Chris
Still exists using 2.6.22.4-65.fc7
Have you tried booting with vga=791 as a kernel boot parameter?
For sure, VESA framebuffer mode is working proper, but slow. But for speed-up I tried savagefb.
Found this upstream, unfortunately the reporter's equipment died...
Linker broken so here it is: http://bugzilla.kernel.org/show_bug.cgi?id=6523
Why did you change the component from kernel to xorg-x11-drv-savage?
Unintended. I was scanning the list for xorg drivers in curiosity, saw savage and forgot to change it back. Sorry for the noise.
Peter, Any update on this? The upstream bug hasn't been touched much either.
Issue still exists on latest F8 kernel: 2.6.23.9-85.fc8
I have obtained a Compaq Evo N115 which has this chipset. http://www.smolts.org/show?UUID=450dea0d-6b4c-49a1-b7cb-0fd4dbbd7435 01:00.0 VGA compatible controller: S3 Inc. VT8636A [ProSavage KN133] AGP4X VGA Controller (TwisterK) (rev 01) (prog-if 00 [VGA]) Subsystem: Compaq Computer Corporation Unknown device 0086 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5 Memory at e8100000 (32-bit, non-prefetchable) [size=512K] Memory at f0000000 (32-bit, prefetchable) [size=128M] [virtual] Expansion ROM at e8180000 [disabled] [size=64K] Capabilities: [dc] Power Management version 2 Capabilities: [80] AGP version 2.0 Unfortunately I can't replicate this. Loading the frame buffer results in a machine lockup whilst in X. I am able to ssh in from another machine which shows the following in dmesg: [drm] Initialized drm 1.1.0 20060810 [drm] Initialized savage 2.4.1 20050313 on minor 0 mtrr: base(0xf2000000) is not aligned on a size(0x5000000) boundary agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode savagefb: mapped io at d0000000 savagefb: probed videoram: 16384k savagefb: Detected current MCLK value of 14318 kHz savagefb: mapped framebuffer at d0100000, pbase == f0000000 savagefb v0.4.0_2.6: 16256kB VRAM, using 800x600, 37.878kHz, 60Hz fbcon: TwisterK (fb0) is primary device Console: switching to colour frame buffer device 100x37 fb: S3 TwisterK frame buffer device Loading in runlevel 3 and then starting is successful but the display is drawn correctly. I then tried adding: Option "UseBios" "False" to the Device section in xorg.conf, then starting X (which came up no problem, unlike you reported at the upstream bug) then loading the framebuffer. This gave me a cursor and then locked up the machine. I was again able to ssh in and the same information was displayed. Basically, I don't think this device will ever work correctly with the frame buffer and being so old I wouldn't hold out for an update. FWIW, when I did manage to get the framebuffer working I experienced no noticeable speed increase. I'm attaching my xorg log anyway. I'll re-assign to Dave Airlie who might have more input on it as per: http://fedoraproject.org/wiki/KernelBugTriage
Created attachment 291214 [details] Xorg log with savage frame buffer loaded
Copying in ajax as he may have some input as well...
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still happen on F10
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The issue still exists on F12 with kernel 2.6.31.5-127.fc12 Note that I found a typo in my original posting: Additional info: Display: 1024x768 (not 760) modprobe's local.conf: options savagefb mode_option=1024x768@60 (default would be 800x600) Note also that "fbset -mode right" does not show any change...looks like the "savagefb" module misses an offset option.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.