Bug#476876: lspci output must be delayed
As you will note, the original date of this report is now several months past. I had to have something that would work, and finally I pulled the S3 card and put in a Matrox II which is working properly with Alpha etch. I can put the S3 back in and get the lspci output for you, but it will be a few days before I can do so. The card itself and the bus it goes into is working, as OpenVMS on the same system does correctly initialize and use the display with the S3 card in place.
Bug#477682: Bug #477682 : Contents of xorg.conf and Xorg.0.log
Not sure why bugreport omitted these, but they are attached. xorg.conf Description: Binary data X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12) Current Operating System: Linux archie 2.6.18-5-alpha-generic #1 Thu Dec 20 06:26:30 UTC 2007 alpha Build Date: 13 August 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Apr 24 09:07:45 2008 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Monitor0 (**) | |--Device S3 Trio 64 (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/misc. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/misc). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/100dpi/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/100dpi/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/75dpi/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/75dpi/). (WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/100dpi. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/100dpi). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/75dpi. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/75dpi). (WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType. (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) No APM support in BIOS or kernel (II) Loader magic: 0x120266138 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:03:0: chip 1011,0019 card , rev 30 class 02,00,00 hdr 00 (II) PCI: 00:07:0: chip 1080,c693 card , rev 00 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1080,c693 card , rev 00 class 01,01,80 hdr 80 (II) PCI: 00:07:2: chip 1080,c693 card , rev 00 class 01,01,00 hdr 80 (II) PCI: 00:07:3: chip 1080,c693 card , rev 00 class 0c,03,10 hdr 80 (II) PCI: 00:14:0: chip 1011,0024 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 01:04:0: chip 1077,1020 card , rev 05 class 01,00,00 hdr 00 (II) PCI: 01:09:0: chip 5333,8811 card , rev 00 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:20:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x8000 - 0x80ff (0x100) IX[B] [1] -1 0 0x8400 - 0x84ff (0x100) IX[B] [2] -1 0 0x8800 - 0x88ff (0x100) IX[B] [3] -1 0 0x8c00 - 0x8cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0x0900 - 0x09bf (0xc0) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0x09c0 - 0x09cf (0x10) MX[B] (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x1) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x1) MX[B] (--) PCI:*(1:9:0) S3 Inc. 86c764/765
Bug#476876: Bug #476876 : Additional information, ROM BIOS address
As noted before, lspci -v returns the BIOS address for the S3 Trio as 09c10 [disabled] However, setpci -s 01:09.0 ROM_ADDRESS returns 8080 I do not know why this contradiction occurs. I decided to try setting the BIOS address register to match the address reported by lspci (and by the S3 driver.) I used the following command: setpci -s 01:09.0 ROM_ADDRESS=9c10 Both commands now report the same address for the BIOS, and lspci no longer says it is disabled. Unfortunately, the S3 driver still fails in the same manner, with the same symptoms. The only difference is that the error messages about the insufficient address space and V_BIOS not found have disappeared. The S3 Trio 64 BIOS banner appears on the screen when X is invoked, then the screen blanks and the same meaningless pattern of pixels is displayed. The keyboard and mouse are still disabled and the system must be rebooted in order to recover control. When the system is rebooted, the BIOS address register on the card is set back to 8080 and must again be altered to re-enable the video BIOS. I'm guessing this may be a plug and play issue, since the card was an early plug and play device. Probably a workaround for the BIOS address would be to insert a setpci somewhere in the system initialization. While this trick with setpci does not solve the S3 driver issues, it does let the VESA driver work with the card. Where previously that driver also said V_BIOS not found and would just exit with no usable screens found it now will operate at 800x600 16bpp. There are lightning flashes when the keyboard or mouse are used, but otherwise it appears to work. The flashing screen is not very usable, however, and getting the S3 driver to work would still be preferable and probably faster performance as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476876: Bug #476876 : Additional information, addressing conflicts?
On suggestions received elsewhere, I tried this with Option noaccel set, but it made no difference. The results, and the meaningless pixel pattern on the screen, remained the same. On another suggestion, I tried the vesa driver, which probably should work with this card as well. That driver (current version is the same for both etch and lenny as far as I can tell) also insists that the V_BIOS is not found and that there are no usable modes. It doesn't even try to initialize the display. I notice in the Xorg.0.log for both drivers that the driver reports the BIOS address as 8080. However, the lspci command reports it as 09c1. In the available resource listing, the 8080 address block always appears, but 09c1 does not. Is there an address translation going on that is not quite working? The setpci command, when used to query the ROM address register of the 86C764/765 chipset, returns 8080 rather than the 09c1 returned by lspci. There were several similar bug reports in the freedesktop.org reporting system dating to late 2006 and early 2007, but they are all reported as fixed. These involved missing assigns or equates in the source code. Is it possible that those fixes never filtered into the Alpha source stream? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476876: Bug #476876 : Additional information, still fails after upgrade to lenny/testing levels
As suggested in earlier response, I first did a full update of the Debian etch level system. A number of major components were replaced, but none were in the x11 area. The problem persisted as reported. This morning I installed xserver-xorg-video-s3 from lenny/testing by using aptitude to include all dependencies and recommended upgrades. This replaced tzdata, locale, libc6.1, xserver-xorg-core, and xserver-xorg-video-s3 with newer versions from the testing release level. The problem with the S3 Trio 32/64 card still persists as reported. Some slight improvements are evident, such as the fact that Xorg -configure now successfully finds the mouse where it did not do so in the past. (It's on /dev/psaux and is an ordinary PS/2 protocol mouse, so I don't know what the problem was with that.) In any case, running the new version of X still causes the screen to fill with random pixels in a static pattern, and locks or disables the keyboard and mouse. The only way to recover console control is by a reboot. Just hazarding a guess from the appearance of the pixels on the screen, there is a memory mapping or buffering error such that values are being loaded in some arrangement other than what the S3 chip expects (but admittedly, I'm far from expert at debugging video hardware issues.) Examination of /var/log/Xorg.0.log after a reboot shows at least a suggestion of a memory mapping error: Requesting insufficient memory window!: start: 0x9c0 end: 0x9cf size 0x80 (EE) Cannot find empty range to map base to (EE) s3(0): Cannot read V_BIOS (5) This occurs in spite of the fact that the correct video card RAM size and address have been deduced from a probe, and the correct BIOS location and size derived from PCI data. I am appending /etc/X11/xorg.conf and /var/log/Xorg.0.log to this message. Note that I also tried with a default depth of 8 bits, which produces a different pattern on the screen but still the same failure. If more specific information would help, please advise and I will do my best to provide it. --/etc/X11/xorg.conf follows--- Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /etc/X11/rgb ModulePath /usr/lib/xorg/modules FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/cyrillic FontPath /usr/share/fonts/X11/100dpi/:unscaled FontPath /usr/share/fonts/X11/75dpi/:unscaled FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Load record Load xtrap Load glx Load dri Load extmod Load dbe Load GLcore EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol PS/2 Option Device /dev/psaux EndSection Section Monitor Identifier Monitor0 VendorName Leading Edge (Daewoo) ModelName CMC-1414BA HorizSync 30-64 VertRefresh 50-90 ModeLine 1024x768 65 1024 1056 1208 1272 768 774 777 802 ModeLine 640x480 28 640 656 752 792 480 490 492 519 ModeLine 800x600 40 800 840 968 1056 600 601 605 628 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option noaccel # [bool] #Option swcursor # [bool] #Option slow_dram_refresh # [bool] #Option slow_dram # [bool] #Option slow_edodram # [bool] #Option slow_vram # [bool] Identifier Card0 Driver s3 VendorName S3 Inc. BoardName 86c764/765 [Trio32/64/64V+] BusID PCI:1:9:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 16 SubSection Display Viewport 0 0 Depth 8 Modes800x600 640x480 EndSubSection SubSection Display Viewport 0 0 Depth 15 Modes800x600 640x480 EndSubSection SubSection Display Viewport 0 0 Depth 16 Modes800x600 640x480 EndSubSection SubSection Display Viewport 0 0 Depth 24
Bug#476876: xserver-xorg-video-s3: S3 server crash/lockup with S3 Trio 64+
The Alpha BIOS itself doesn't enable or disable anything, so I'm not sure what I could do there. I'm not really sure what [disabled] means in the lspci output anyway. It also reports that the SCSI controller BIOS is disabled, but that is working fine. I have kept Etch up to date, but only with the stable configuration. The Xorg server shows a compile date in January of 2008, which really doesn't seem that old, but I suppose I might be able to install something from the testing or unstable packages. I tried switching to a different video card, ELSA Gloria L, that has an S3ViRGE chip, but that gives similar results, even though it seems to want the s3virge driver or possibly the glint (it has two 3DLabs coprocessors on it.) The ELSA card works with Windows NT on this box, but not with OpenVMS so I swapped back to the S3 Trio. On Sat, Apr 19, 2008 at 6:24 PM, Brice Goglin [EMAIL PROTECTED] wrote: Gary Phillips wrote: Package: xserver-xorg-video-s3 Version: 1:0.4.1-5 Severity: critical Justification: breaks the whole system Digital Alpha PWS433au with 1GB RAM, Debian 4.0 (etch) S3 Trio 64+ video card (which works on this hardware with both Windows NT 4.0 and OpenVMS 8.3) Whether manually configured or set up with Xorg -configure, when X is run the display fills with random colored pixels, keyboard and mouse are disabled, and machine must be rebooted in order to recover control. When X is run with -probeonly, the only error it reports is Unable to find V_BIOS. When lspci -v is run, it reports that the Video ROM is present but [disabled]. Is there anything to configure in the Alpha BIOS or whatever to help this? Can something more recent than Etch? The S3 driver is been a bit updated since Etch, and the Xserver is much more recent. Trying Xorg fro; testing might be good, for instance. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
