openSUSE X.org January 2005

xorg@lists.opensuse.org

41 participants
31 discussions

Compose Cache in X.Org 6.8.2 RC3 RPMs for SuSE 9.2

by Matthias Hopf

Hi all, about the SuSE X.Org 6.8.2 RC3 RPMs and compose cache: > * SuSE specific changes since RC2: > - added compose cache (details for testing will follow) > [...] The compose cache accelerates program startup times and memory consumption considerably, especially for UTF8 locales. In order to use the compose cache, please create a directory $HOME/.compose-cache , writable only by you. The next X application will create a compose cache entry in this directory which will be used in the future. Compose cache entries expire once a day. Changes in the compose tables are tracked and caches invalidated automatically. Future releases will have a global compose cache, so a .compose-cache directory will only be needed for caching if you have your own compose table. In the meantime, please create the directory for testing and report all compose- and deadkey-related issues. Thanks Matthias -- Matthias Hopf <mhopf(a)suse.de> /-- /-- /-- mat(a)mshopf.de Maxfeldstr. 5 / 90409 Nuernberg \-\ | | \-\ |-- www.mshopf.de Phone +49-911-74053-715 --/ \_/ --/ \-- labs

16 years, 8 months

Observing a problem with a key and fglrx

by Ekkehard.Ellmann＠t-online.de

I am running suse9.2 with a pc104-keyboard. Using fglrx-8.8.25 makes the key for <|> unusable. Running yast -->hardware-->keyboard repaires the key. No idea why but works. Ekkehard

16 years, 8 months

X.Org 6.8.2 RC3 RPMs for SuSE 9.2 available

by Stefan Dirsch

Hi The X.Org Foundation is currently preparing a second maintenance release for version 6.8 of their implementation of the X Window System. The code is presently in the beta testing phase. SUSE will prepare update packages for the latest SUSE Linux version as soon as this release (6.8.2) becomes available. In our efforts to work closely with the X.Org Foundation to make their software even better we would like to invite those users of SUSE Linux who are interested in the X Window System to participate in this beta test. This will give the beta version of 6.8.2 a wider exposure, more testing and allow our users to identify and report problems on their hardware early so they may be fixed for the release. To simplify testing I've built X.Org 6.8.2 RC3 RPMs for SuSE 9.2 and uploaded them for download to ftp://ftp.suse.com/pub/suse/i386/supplementary/X/Xorg/Xorg-X11R6.8.2-RC3/ * Installation instructions can be found in the README (also in this directory). * In case something goes wrong and you need to revert to the original X.Org 6.8.1 RPMs for SuSE 9.2, simply remove the new RPMs with rpm -e <pkg-name> --nodeps and install the old ones from your DVD/CDs with rpm -Uhv <pkg-name> again (RPMs are in /suse/<arch> on the DVD/CD). A package list is in the README. * Notes for testers: Various drivers, modules and other infrastructure got significant updates and need to be thoroughly tested by the community, including: - "radeon" video driver - "nv" (nvidia) video driver - ATI Rage128 video driver - ATI R100 video driver - Intel i810 video driver - Postscript print driver - Xprint infrastructure update - Mesa (OpenGL) update to release 6.2 - libXpm security update (CAN-2004-0914) ... and many many other things... * The full changelog for the X11R6.8.x stable branch can be found under http://cvs.freedesktop.org/xorg/xc/ChangeLog?only_with_tag=XORG-6_8-branch&… * SuSE specific changes since RC1: - reintroduced xf86/xshared/xdevel/xfntscl Provides for SuSE <= 9.2 * SuSE specific changes since RC2: - added support for Intel 915GM (please give it a try; use "sax2 -r -m 0=i810" for configuration) - added compose cache (details for testing will follow) - fixed one powersave related problem - no longer set a blue background for kdm and gdm - xorg-x11-server requires now xorg-x11 (Xserver requires fonts) - no longer disable RenderAccel in radeon driver - Xserver modules are now stripped - added support for about 20 known and up to about 30 unkown nvidia Devices (use "sax2 -r -m 0=nv" for configuration) * Feedback can be discussed on this list as we don't have an open Bugzilla. Please don't contact me directly or thru the regular SUSE feedback channel. I'll try to discuss the feedback on this list. Please note that there won't be any installation or advanced support for these test packages. Should you experience any problems please refer to the above instructions how to revert back to the version of X that has been shipped with SUSE Linux. Please also note that if you download and install a test version we strongly recommend to update to the released version of 6.8.2 once it becomes available. Regards, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------

16 years, 8 months

Athlon 64 Drivers

by Jeffrey Laramie

Hi All I've been trying to get the new ATI drivers working on x86_64 system running 9.1 with limited success. I've been at this for days and have finally got the driver to load after changing the option "UseInternalAGPGART" to "no". If I leave this as "yes" the xserver hangs with a blank screen on startup. However without it I can't get 3d acceleration. Here's what I've got at this point: Changes from configuration defaults Option "UseInternalAGPGART" "no" # BusID "PCI:1:0:0" # vendor=1002, device=4152 (this line will throw error messages in the log but it doesn't seem to change anything either way) fglrxinfo libGL error: drmMap of framebuffer failed display: :0.0 screen: 0 OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.2 (1.4 Mesa 5.0.2) lsmod | grep fglrx fglrx 258528 7 There are no other graphic related modules installed as far as I can tell. I believe I need an AGP module to load if I disable the ATI AGP module, but I can find an AGP module on my system. The truly odd thing here is that the ATI module loads, the driver works (2d), XFree86.0.log shows the fglrx module loading and doesn't appear to have any errors, yet fglrxinfo doesn't see it. I'm open to any and all suggestions. Jeff

16 years, 8 months

solution report: X.Org6.8 driver for ATI Radeon

by Wolfgang Rinnert

Hi all, just a report of my experiences when installing Suse 9.2 on a Toshiba Tecra S1 laptop. The laptop was purchased in early 2004. The graphics card is recognized as: (--) PCI:*(1:0:0) ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] rev 1, Mem @ 0xa8000000/27, 0xe0010000/16, I/O @ 0xc100/8 When the install was through, KDE came up with 640x480, which is definitely not what I expected. (The system is pretty much unusable, even the KDE control center cannot be displayed correctly.) After about a week of unsuccessful tries I found the suse-xfree86 mailing list. I determined that the thread "[suse-xfree86] There is now a X.Org6.8 driver on ATI's website" was for me. Found the fglrx driver on ftp.suse.com. Set up everything according to the README that came with it. But X did not come up. The last 25 lines of Xorg.0.log follow: #----------------------------------------------------------------------------- begin quotation (II) Setting vga for screen 0. (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE Fatal server error: __glXExtensionInit: AddExtensions failed Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. #----------------------------------------------------------------------------- end quotation I went to the web and found the following URLs: http://www.stanchina.net/~flavio/debian/fglrx-archive/msg00120.html http://www.stanchina.net/~flavio/debian/fglrx-archive/msg00122.html The first of these URLs reports the same problem I had, namely X dying unexpectedly with "__glXExtensionInit: AddExtensions failed" The second reports the solution, which at first I could hardly believe, but this was the solution: X depends on the sequence in which the modules are enumerated in Xorg.conf !! See for yourself: #----------------------------------------------------------------------------- begin quotation ... After I tried part of your XF86Config-4 file and experienced the same problem as yours, I tried to see what is different from my working environment and I found out that the problem is in the order modules are loaded in the "Module" section from your config file. Please try the next "Module" section and let us know if it works for you: Section "Module" #Load "pex5" Load "dbe" Load "glx" Load "dri" Load "GLcore" Load "record" Load "extmod" SubSection "extmod" Option "omit xfree86-dga" EndSubSection #Load "xie" Load "freetype" Load "type1" EndSection For example my "Module" section looks like this: Section "Module" Load "dbe" # Double buffer extension Load "extmod" Load "glx" Load "dri" Load "vbe" Load "ddc" Load "xaa" Load "int10" Load "record" #off# Load "xtrap" # Font Modules Load "freetype" Load "type1" # Extra Stuff Load "i2c" EndSection if I enable the "xtrap" extension, X is not starting anymore .. #----------------------------------------------------------------------------- end quotation My kind request is that Suse consider changing sax2 so that this sequence is automatically created (at least in the case that is described in the fglrx-README). Or, even better, if Suse could influence the X.org guys to help make this sequence unimportant! X should better not remind us of the "good" old days, when we were juggling around with the right order of MS-DOS config.sys entries ;-) Hope this helps some people! Best regards, Wolfgang Rinnert wrinnert(a)web.de

16 years, 8 months

Yast hardware problem

by Mitch Martinez

On Sat, 2005-01-29 at 00:00 -0700, Mitch Martinez wrote: > I'm having a problem with yast. > When I do a hardware search Yast/Hardware/Hardware Information it takes > ove the CPU.... anybody have a reason why? > > Machine is : > MB: ASUS K8V Deluxe > CPU: AMD Athlon(tm) 64 Processor 3200+ > MEM: 1540984 kB > VID: G-Force FX5900 128 MB > MON: ViewSonic P810 > OS: SUSE 9.2 Pro > > > > > top - 23:58:35 up 4 days, 14:01, 4 users, load average: 1.11, 1.09, > 0.92 > Tasks: 125 total, 2 running, 123 sleeping, 0 stopped, 0 zombie > Cpu(s): 99.7% us, 0.3% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, > 0.0% si > Mem: 1540984k total, 1530416k used, 10568k free, 77548k buffers > Swap: 2048248k total, 17908k used, 2030340k free, 268448k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 25385 root 25 0 99956 23m 87m R 99.5 1.5 16:05.34 y2base > 6 -- Mitch Martinez <mitch.r.martinez(a)worldnet.att.net>

16 years, 9 months

Mouse event support

by Aaron Williams

There was a patch to Xorg 6.8.1 from Gentoo that added support for using the Linux event mechanism for mouse support. Does anyone know if this was added to 6.8.2? I manually patched my 6.8.1 so as to better support my Logitech mouse. The event mechanism allows me to use more of the buttons. I have the MX1000 mouse which is considered a 12 button mouse. -Aaron

16 years, 9 months

Re: [suse-xfree86] i915 driver on SuSE 9.1, using Intel 865G

by Forest Monsen

On Wed, 05 Jan 2005, Forest Monsen wrote: > Hello, > > It's time to try 3D acceleration on SuSE 9.1. I'm using an Intel 865G chip, > and obtained the i915 driver from Intel's site at > http://support.intel.com/support/graphics/sb/CS-010512.htm I should mention that the whole reason I'm attempting to use the i915 driver, not tested by Intel on SuSE 9.1, is that I'm currently using the i810 driver, but DRI isn't working for me. If anyone can guess what the problem might be, based on the attached output, that would be great too. First, some facts: YaST does report that acceleration is enabled for the card. My XF86Config file does correctly reference the i810 driver in the "Device" section, as well as enabling the 'dri' and 'glx' modules. According to http://www.xfree86.org/~dawes/845driver.html , the 'i810' driver is actually the XFree86 server driver, while the DRI/DRM kernel driver is 'i830'. /sbin/lsmod does show this loaded: ### begin result of /sbin/lsmod | grep 830 ### i830 70208 0 ### end result of /sbin/lsmod | grep 830 ### Below, I'll include my XFree86 config file, as well as the output in /var/log/XFree86.0.log . ### begin selections from XFree86 config file ### # SaX generated XFree86 config file # Created on: 2005-01-06T10:46:01-0800. # # Version: 4.8 # Contact: Marcus Schaefer <sax(a)suse.de>, 2002 [...] Section "Module" Load "dbe" Load "type1" Load "speedo" Load "freetype" Load "extmod" Load "glx" Load "v4l" Load "dri" EndSection [...] Section "Monitor" DisplaySize 360 270 HorizSync 28-107 Identifier "Monitor[0]" ModelName "D8912A HP P920 19-INCH MONITOR" Option "DPMS" VendorName "HEWLETT-PACKARD" VertRefresh 50-160 UseModes "Modes[0]" EndSection [...] Section "Device" BoardName "865 G" BusID "0:2:0" Driver "i810" Identifier "Device[0]" Screen 0 Option "Rotate" "off" VendorName "Intel" EndSection [...] Section "DRI" Group "video" Mode 0660 EndSection ### end selections from XF86config file ### ### begin /var/log/XFree86.0.log ### [...] XFree86 Version 4.3.99.902 (4.4.0 RC 2) Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: SuSE Linux [ELF] SuSE Current Operating System: Linux boogie 2.6.5-7.111.19-default #1 Fri Dec 10 15:10:58 UTC 2004 i686 Build Date: 23 August 2004 Changelog Date: 29 February 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present [...] (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="The XFree86 Project" compiled for 4.3.99.902, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="The XFree86 Project" compiled for 4.3.99.902, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension GLX [...] (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="The XFree86 Project" compiled for 4.3.99.902, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor="The XFree86 Project" compiled for 4.3.99.902, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: "i810" (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor="The XFree86 Project" compiled for 4.3.99.902, module version = 1.3.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.7 [...] (II) I810: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G (II) Primary Device is: PCI 00:02:0 (--) Chipset 865G found (II) resource ranges after xf86ClaimFixedResources() call: [...] (**) I810(0): Depth 16, (--) framebuffer bpp 16 (==) I810(0): RGB weight 565 (==) I810(0): Default visual is TrueColor (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a (II) I810(0): initializing int10 (II) I810(0): Primary V_BIOS segment is: 0xc000 (II) I810(0): VESA BIOS detected (II) I810(0): VESA VBE Version 3.0 (II) I810(0): VESA VBE Total Mem: 8000 kB (II) I810(0): VESA VBE OEM: Intel(r)865G Graphics Chip Accelerated VGA BIOS (II) I810(0): VESA VBE OEM Software Rev: 1.0 (II) I810(0): VESA VBE OEM Vendor: Intel Corporation (II) I810(0): VESA VBE OEM Product: Intel(r)865G Graphics Controller (II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (II) I810(0): Integrated Graphics Chipset: Intel(R) 865G (--) I810(0): Chipset: "865G" (--) I810(0): Linear framebuffer at 0xF0000000 (--) I810(0): IO registers at addr 0xFC400000 (II) I810(0): detected 8060 kB stolen memory. (II) I810(0): I830CheckAvailableMemory: 1205244 kB available (II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM (WW) I810(0): Extended BIOS function 0x5f11 not supported. (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a (II) I810(0): initializing int10 (WW) I810(0): Bad V_BIOS checksum (II) I810(0): Primary V_BIOS segment is: 0xc000 (II) I810(0): VESA BIOS detected (II) I810(0): VESA VBE Version 3.0 (II) I810(0): VESA VBE Total Mem: 12288 kB (II) I810(0): VESA VBE OEM: Intel(r)865G Graphics Chip Accelerated VGA BIOS (II) I810(0): VESA VBE OEM Software Rev: 1.0 (II) I810(0): VESA VBE OEM Vendor: Intel Corporation (II) I810(0): VESA VBE OEM Product: Intel(r)865G Graphics Controller (II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (II) I810(0): Tweak BIOS image to 12288 kB VideoRAM (--) I810(0): Pre-allocated VideoRAM: 8060 kByte (==) I810(0): VideoRAM: 32768 kByte (==) I810(0): video overlay key set to 0x83e (**) I810(0): page flipping disabled (--) I810(0): Maximum frambuffer space: 32616 kByte (==) I810(0): Using gamma correction (1.0, 1.0, 1.0) (II) I810(0): 1 display pipe available. (==) I810(0): Display Info: enabled. [...] (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a (II) I810(0): initializing int10 (II) I810(0): Primary V_BIOS segment is: 0xc000 (II) I810(0): VESA BIOS detected (II) I810(0): VESA VBE Version 3.0 (II) I810(0): VESA VBE Total Mem: 8000 kB (II) I810(0): VESA VBE OEM: Intel(r)865G Graphics Chip Accelerated VGA BIOS (II) I810(0): VESA VBE OEM Software Rev: 1.0 (II) I810(0): VESA VBE OEM Vendor: Intel Corporation (II) I810(0): VESA VBE OEM Product: Intel(r)865G Graphics Controller (II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (==) I810(0): Default visual is TrueColor (II) I810(0): Allocated 128 kB for the ring buffer at 0x0 (II) I810(0): Allocating at least 384 scanlines for pixmap cache (II) I810(0): Initial framebuffer allocation size: 5632 kByte (II) I810(0): Allocated 4 kB for HW cursor at 0x7fff000 (II) I810(0): Allocated 4 kB for Overlay registers at 0x7ffe000 (0x35f85001). (II) I810(0): Allocated 64 kB for the scratch buffer at 0x7fee000 drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: minor is 1 drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed drmOpenDevice: minor is 2 drmOpenDevice: node name is /dev/dri/card2 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed [...] drmOpenDevice: minor is 14 drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: open result is -1, (Unknown error 999) drmOpenDevice: Open failed (II) I810(0): [drm] drmOpen failed (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. (II) I810(0): Updated framebuffer allocation size from 5632 to 8192 kByte (II) I810(0): Updated pixmap cache from 384 scanlines to 1024 scanlines (II) I810(0): 0x83d6d8c: Memory at offset 0x00020000, size 8192 kBytes (II) I810(0): 0x83d6dac: Memory at offset 0x07fff000, size 4 kBytes (II) I810(0): 0x83d6dd0: Memory at offset 0x00000000, size 128 kBytes (II) I810(0): 0x83d6e00: Memory at offset 0x07fee000, size 64 kBytes (II) I810(0): 0x83d6e20: Memory at offset 0x07ffe000, size 4 kBytes (WW) I810(0): Failed to set up write-combining range (0xf0000000,0x8000000) (II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) I810(0): xf86BindGARTMemory: bind key 3 at 0x007df000 (pgoffset 2015) (II) I810(0): xf86BindGARTMemory: bind key 0 at 0x07fff000 (pgoffset 32767) (II) I810(0): xf86BindGARTMemory: bind key 2 at 0x07fee000 (pgoffset 32750) (II) I810(0): xf86BindGARTMemory: bind key 1 at 0x07ffe000 (pgoffset 32766) (WW) I810(0): PGTBL_ER is 0x00000011 (WW) I810(0): Extended BIOS function 0x5f05 failed. (WW) I810(0): Failed to set refresh rate to 98Hz. (II) I810(0): Display plane A is enabled. (II) I810(0): Display plane B is disabled. (II) I810(0): PIPEACONF is 0x80000000 (WW) I810(0): Correcting plane A stride (1280 -> 2048) (II) I810(0): Mode bandwidth is 78 Mpixel/s (II) I810(0): maxBandwidth is 1528 Mbyte/s, pipe bandwidths are 210 Mbyte/s, 0 Mbyte/s (WW) I810(0): Extended BIOS function 0x5f61 not supported. (II) I810(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Horizontal and Vertical Lines Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 16 256x256 slots 5 512x512 slots (==) I810(0): Backing store disabled (==) I810(0): Silken mouse enabled (II) I810(0): Initializing HW Cursor (**) Option "dpms" (**) I810(0): DPMS enabled (II) I810(0): direct rendering: Failed (WW) I810(0): Option "Rotate" is not used (**) RandR enabled (II) Initializing built-in extension MIT-SHM [...] (WW) I810(0): Setting the original video mode instead of restoring the saved state (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 0 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) I810(0): xf86BindGARTMemory: bind key 3 at 0x007df000 (pgoffset 2015) (II) I810(0): xf86BindGARTMemory: bind key 0 at 0x07fff000 (pgoffset 32767) (II) I810(0): xf86BindGARTMemory: bind key 2 at 0x07fee000 (pgoffset 32750) (II) I810(0): xf86BindGARTMemory: bind key 1 at 0x07ffe000 (pgoffset 32766) (WW) I810(0): PGTBL_ER is 0x00000011 (WW) I810(0): Extended BIOS function 0x5f05 failed. (WW) I810(0): Failed to set refresh rate to 98Hz. (II) I810(0): Display plane A is enabled. (II) I810(0): Display plane B is disabled. (II) I810(0): PIPEACONF is 0x80000000 (WW) I810(0): Correcting plane A stride (1280 -> 2048) (II) I810(0): Mode bandwidth is 78 Mpixel/s (II) I810(0): maxBandwidth is 1528 Mbyte/s, pipe bandwidths are 210 Mbyte/s, 0 Mbyte/s (WW) I810(0): Extended BIOS function 0x5f61 not supported. (II) Mouse[1]: ps2EnableDataReporting: succeeded (WW) I810(0): Setting the original video mode instead of restoring the saved state (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 0 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 ### end /var/log/XFree86.0.log ###

16 years, 9 months

graphics on a compaq laptop

by Tim Hanson

I tried getting an answer on suse-linux-e, but no luck. In the two years I have had my Compaq 1500 laptop, I have at various times had Fedora Core 2 and SuSE (various, the last being 9.1, which is on it now). I've never had problems with it until I tried to update to 9.2. Running sax2 brings up a white screen. This is not a totally white screen, I can make out what looks to be the sax2 "accept vs. change" screen. Plugging a second monitor confirms this, 640X480, but on the laptop is very obscure. I had been routinely running 1280x1024, with 16 bit resolution, using the ATI Radeon LW card driver including 3D. The monitor is the generic LCD. The card was the selection given by yast, and the monitor was one I chose. For 9.2, sax2 tried to use the driver for the HS150PK12-A monitor. I've done pretty much everything to defeat that choice. I started sax2 under the -l, -V, -s, and -i options. I tried configuring using the second monitor. I even tried re-installing 9.1, setting up the graphics, and updating to 9.2. No luck on any of this. At present, I have 9.1 back on the system, but I would really like to upgrade, since 9.2 has improved laptop utilities.

16 years, 9 months

resizing/movement of windows impossible

by Wilde Martin

Hi everybody, I am running a SuSE 9.1 desktop machine. My machine worked well for months now, but currently I am unable to move or resize *any* of my windows (only minimize and maximize and close buttons work). It does not make any difference, if it is SuSEs yast window or any of my xterm windows. (all of them opened on a KDE WM). Hope that someone can help me here - it is horrible! Martin

16 years, 9 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE X.org January 2005