October 2004 - openSUSE X.org - openSUSE Mailing Lists

X Error of failed request: BadAccess
by Zoltan Szecsei 23 Oct '04

23 Oct '04

Hi Ppl, Please can someone point me to a resource I can use to get help on this issue. I have a (oldish) raster & vector graphics product that I have used successfully up until SuSE SLES8 but on upgrading to SuSE 9.1, I get the errors mentioned below - but only when trying to display a tiff image - the vector side of the package works fine. TIA, Zoltan X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 145 (MIT-SHM) Minor opcode of failed request: 3 (X_ShmPutImage) Serial number of failed request: 194 Current serial number in output stream: 195

1 0

Xorg 6.8.1 and the query command
by Adolph & Sharon Weidanz 22 Oct '04

22 Oct '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all.. I do not know if this is specific to xorg, becuase I just learned about it after the switch... here's what's happening.. While at school, on my laptop using wireless. I did a 'X :2 -query XXX.XXX.usf.edu' It came up with the solaras login with no problems. At home on my wireless network (W/ linksys router) I do the same thing and get just a x windows gray screen and it goes off to never never land. I friend of mine says he had the same problem, but when he connected his laptop directly to his cable connection it worked.. Any ideas .. If needed let me know what log/config parts to send and I will.. Thanks.. - -- Adolph & Sharon Weidanz '78 43' Endeavour Ketch S/V Time To Paws -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBeUmSlC+PSm9+eB0RAk1XAJ9IS8S9vP+m3L+8icyk0mhE1/7DqQCgidJE Ve6gO+bmb/pVKaxVX6m6QOs= =jGTK -----END PGP SIGNATURE-----

1 0

No image on second head
by Joerg Bruehe 18 Oct '04

18 Oct '04

Hi all, I am still fighting with setting up a dual-head installation. As I only got an image that looked "noisy" on the second head (DVI) of my nVidia FX 5200 card, I now installed a Matrox Mileenium G200 SD as a second card, connected my TFT to its VGA (only) output, and configured this (manually). When I now do a "startx -- -layout DualHead", the first screen comes up normally. On the new screen, everything stays blank / black, but its OSD tells a valid resolution: 1280x1024(a)60.2 Before the "startx" and after exiting it (on the first screen), the OSD (on the second)says "no signal". My questions: 1) Is there any configuration file (other than "/etc/X11/XF86Config") that controls for which screens a desktop is started ? 2) Any info about these messages from the X startup log: Symbol drmGetInterruptFromBusID from module /usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved! Symbol drmCtlInstHandler from module /usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved! Symbol drmCtlUninstHandler from module /usr/X11R6/lib/modules/drivers/mga_drv.o is unresolved! Could this be the reason, and where should they be resolved from? I run SuSE 8.2 out-of-the box, with a recent Yast online update. In that test installation I started FVWM only, no KDE. Configuration with "sax2" failed, as the X server it started did not produce a resolution which was acceptable to my 15" TFT (1024x768@60 or fewer pixels). using "xf86cfg" did not help either, although its interface (showing both cards and monitors) looked promising. I attach my X configuration file. The X startup log is too large to pass the list mailer daemon. Regards and thanks, Jörg -- Joerg Bruehe mailto:joerg.bruehe@web.de

1 0

OpenGLOverlay
by Claus Olesen 17 Oct '04

17 Oct '04

I installed the latest of SuSE's ATI fglrx driver (v3.14.1) on my fully YOU updated SuSE 9.1 box with ATI 9600. I also got a camcorder, shot some video, used Kino to import and compress and mplayer to play it. Kino and mplayer are the latest from Packman. With the XVideo extension enabled ("VideoOverlay" "on" in XF86Config) some of the video is blurry particularly along vertical lines as on tall buildings. With OpenGL instead ("OpenGLOverlay" "on" in XF86Config) the problem disappears and CPU usage does not go up much - maybe 5-10%. I think http://www.inb.uni-luebeck.de/~boehme/xvideo_sync.html is about the same problem but the suggested solution is involved. Does anyone know what the drawbacks are to using "OpenGLOverlay"? None of the XF86Config's that I've seen on the web have this option enabled.

1 0

cannot start remote X-application after update to Xfree86 4.4.0
by Alexander Beck-Ratzka 15 Oct '04

15 Oct '04

Hello list, because I've had problems to get my X running on my new PC (it is a DELL...), I have updated my XFree86 to version 4.4.0 recently. However, my problem wasn't solved by this update, but by an BIOS update from DELL. Now everything seems to work fine.... Today I tried to start an X application from a remote Linux computer, after (of course) setting the DISPLAY variable correctly. The X applcation (simply an xterm) didn't come up; instead I got the error message: ######################################cut here##################################### Xlib: connection to "10.56.79.185:0.0" refused by server Xlib: No protocol specified xterm Xt error: Can't open display: 10.56.79.185:0 ######################################cut here##################################### What is the reason for this error, and what must I do to avoid it? I assume that I forgot something after the update. Thank's in advance. Alexander P.S. I am running SuSE Linux 8.2

1 0

ATI fglrx driver: Kernel Oops/ X server crashes when using DRI
by Lenz Grimmer 13 Oct '04

13 Oct '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am trying to enable the ATI "fglrx" driver on my IBM Thinkpad T42 Laptop, which uses an "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]" chip. X.org 6.8.1 works OK using the "radeon" driver module. Some installed package versions: kernel-default-2.6.8-20041012113024 kernel-source-2.6.8-20041012113024 km_fglrx-3.14.1-0.1 fglrx-3.14.1-0.1 xorg-x11-6.8.1-7 (this is on a SUSE 9.2b3 system) I first tried the driver directly from the ATI web site, but it gave me the same results as the one available from ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/suse91/fglrx/3.14.1/ which I tried afterwards. I followed the instructions given in the README from the directory above. Compiling and loading the fglrx.ko module works fine, apart from the following compile warnings (probably harmless): [SNIP] /usr/src/kernel-modules/fglrx/firegl_public.c: In function `__ke_block_all_signals': /usr/src/kernel-modules/fglrx/firegl_public.c:812: warning: passing arg 1 of `block_all_signals' from incompatible pointer type /usr/src/kernel-modules/fglrx/firegl_public.c: In function `__ke_request_irq': /usr/src/kernel-modules/fglrx/firegl_public.c:1903: warning: assignment from incompatible pointer type /usr/src/kernel-modules/fglrx/firegl_public.c: At top level: /usr/src/kernel-modules/fglrx/firegl_public.c:2519: warning: initialization from incompatible pointer type [SNIP] The X server actually starts up, using the fglrx X driver module. However, I do notice the following messages in the kernel messages (notice the ERROR about mtrr allocation): [SNIP] Oct 13 10:29:20 metis kernel: fglrx: no version for "struct_module" found: kernel tainted. Oct 13 10:29:20 metis kernel: fglrx: unsupported module, tainting kernel. Oct 13 10:29:20 metis kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. Oct 13 10:29:20 metis kernel: [fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes. Oct 13 10:29:20 metis kernel: ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11 Oct 13 10:29:20 metis kernel: [fglrx] module loaded - fglrx 3.14.1 [Sep 27 2004] on minor 0 Oct 13 10:29:20 metis kernel: mtrr: 0xe0000000,0x4000000 overlaps existing 0xe0000000,0x2000000 Oct 13 10:29:20 metis kernel: [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22) Oct 13 10:29:20 metis kernel: [fglrx] AGP detected, AgpState = 0x1f000217 (hardware caps of chipset) Oct 13 10:29:20 metis kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. Oct 13 10:29:20 metis kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode Oct 13 10:29:20 metis kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode Oct 13 10:29:20 metis kernel: [fglrx] AGP enabled, AgpCommand = 0x1f000314 (selected caps) Oct 13 10:29:20 metis kernel: [fglrx] free AGP = 256126976 Oct 13 10:29:20 metis kernel: [fglrx] max AGP = 256126976 Oct 13 10:29:20 metis kernel: [fglrx] free LFB = 47165440 Oct 13 10:29:20 metis kernel: [fglrx] max LFB = 47165440 Oct 13 10:29:20 metis kernel: [fglrx] free Inv = 0 Oct 13 10:29:20 metis kernel: [fglrx] max Inv = 0 Oct 13 10:29:20 metis kernel: [fglrx] total Inv = 0 Oct 13 10:29:20 metis kernel: [fglrx] total TIM = 0 Oct 13 10:29:20 metis kernel: [fglrx] total FB = 0 Oct 13 10:29:20 metis kernel: [fglrx] total AGP = 65536 [SNIP] >From /proc/mtrr: reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0x1ff80000 ( 511MB), size= 512KB: uncachable, count=1 reg02: base=0xe0000000 (3584MB), size= 32MB: write-combining, count=1 As soon as I try to start any application that uses OpenGL (e.g. "fgl_glxgears", the X server crashes hard and I am back on the text mode. The X server messages don't really give a hint, apart from the info that it caught a Sig11. However, as soon as I try to read any of the files in /proc/dri/ (which are set up by the flgrx driver), the kernel Oopses with the following output: [SNIP] Oct 13 10:34:43 metis kernel: Unable to handle kernel paging request at virtual address f00003a1 Oct 13 10:34:43 metis kernel: printing eip: Oct 13 10:34:43 metis kernel: e1abdb30 Oct 13 10:34:43 metis kernel: *pde = 00000000 Oct 13 10:34:43 metis kernel: Oops: 0002 [#1] Oct 13 10:34:43 metis kernel: Modules linked in: fglrx ieee80211_crypt_wep ipw2200 ieee80211 ieee80211_crypt joydev sg st sd_mod sr_mod scsi_mod ide_cd cdrom nvram edd cpufreq_userspace speedstep_centrino freq_table thermal processor fan button battery ac snd_pcm_oss snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_pcm ipv6 snd_timer irtty_sir snd sir_dev soundcore snd_page_alloc irda crc_ccitt af_packet arc4 ds usbhid nls_utf8 ntfs subfs firmware_class intel_agp agpgart ehci_hcd uhci_hcd yenta_socket pcmcia_core e1000 evdev usbcore dm_snapshot dm_mod reiserfs Oct 13 10:34:43 metis kernel: CPU: 0 Oct 13 10:34:43 metis kernel: EIP: 0060:[<e1abdb30>] Tainted: PF U VLI Oct 13 10:34:43 metis kernel: EFLAGS: 00010282 (2.6.8-20041012113024-default 20041012113024) Oct 13 10:34:43 metis kernel: EIP is at __ke_down_struct_sem+0x10/0x20 [fglrx] Oct 13 10:34:43 metis kernel: eax: f0000379 ebx: e1aea3e0 ecx: f00003a1 edx: f0000379 Oct 13 10:34:43 metis kernel: esi: d31fdf80 edi: d0ae7000 ebp: e1aea3e0 esp: d3719ef0 Oct 13 10:34:43 metis kernel: ds: 007b es: 007b ss: 0068 Oct 13 10:34:43 metis kernel: Process cat (pid: 7167, threadinfo=d3718000 task=cdccb550) Oct 13 10:34:43 metis kernel: Stack: e1acfdb0 f0000379 00000000 cdccb550 00000010 00000000 000000d0 0000000b Oct 13 10:34:43 metis kernel: c017d040 dfd71dc0 e1acfd70 00000c00 c017d17d 00000c00 d3719f48 e1aea3e0 Oct 13 10:34:43 metis kernel: d31fdf80 416ce8a3 d31fdf80 00000000 00001000 0804de48 00000000 00000000 Oct 13 10:34:43 metis kernel: Call Trace: Oct 13 10:34:43 metis kernel: [<e1acfdb0>] drm_clients_info+0x40/0xb0 [fglrx] Oct 13 10:34:43 metis kernel: [<c017d040>] proc_file_read+0x0/0x260 Oct 13 10:34:43 metis kernel: [<e1acfd70>] drm_clients_info+0x0/0xb0 [fglrx] Oct 13 10:34:43 metis kernel: [<c017d17d>] proc_file_read+0x13d/0x260 Oct 13 10:34:43 metis kernel: [<c017d040>] proc_file_read+0x0/0x260 Oct 13 10:34:43 metis kernel: [<c0151848>] vfs_read+0xa8/0x110 Oct 13 10:34:43 metis kernel: [<c0151971>] sys_read+0x41/0x70 Oct 13 10:34:43 metis kernel: [<c0151947>] sys_read+0x17/0x70 Oct 13 10:34:43 metis kernel: [<c0104c19>] sysenter_past_esp+0x52/0x79 Oct 13 10:34:43 metis kernel: Code: 02 74 01 c3 a1 88 9f ae e1 e9 fd b6 65 de 8d b6 00 00 00 00 8d bc 27 00 00 00 00 8b 44 24 08 8b 54 24 04 c1 e0 04 01 d0 8d 48 28 <ff> 48 28 0f 88 ab 19 00 00 c3 8d b6 00 00 00 00 8b 44 24 08 8b [SNIP] This Oops also occurs by just loading the flgrx kernel module and accessing the files in /proc/dri (without starting X before). Is this a known issue with the fglrx driver and the recent SUSE kernels? Or is anybody else able to reproduce this? I would really like to be able to use the fglrx driver, not only for the 3D acceleration but also for being able to use the TV output or Dual Head configuration... Thanks in advance! Let me know, if you need any additional info. Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz(a)grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr(a)jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFBbQi7SVDhKrJykfIRAs+BAJ9mFH8IKSePqyGmEPy3K0FJN7gX2gCfVflw OtSbCggawc4m+hTf+JIQrdI= =rlpq -----END PGP SIGNATURE-----

2 1

Suse 9.2, X.org and Xinerama
by Ross Miller 12 Oct '04

12 Oct '04

Hello, Has anybody tried to use Xinerama with Suse 9.2 yet? I've been unsuccessful and may have to go back to 9.1. Here's the whole story: Hardware is a P4 with an Intel motherboard. There's an Intel graphics chipset on the motherboard (on the AGP bus) and 2 PCI cards with nVidia Geforce 2 MX chips. With Suse 9.1 (using XFree86), this was working great. I did the install of 9.2 in graphical mode and it made it most of the way through, but after it rebooted, my computer came up into a blank screen. After much fussing and fuming I pulled out the 2 PCI video cards and rebooted. With only the onboard Intel video, the graphical installer came up and the install finished. At this point, I shut down, put the two PCI cards back in and booted back up (into runlevel 3). After logging in, I tried to run sax2 to configure everything. sax2 started, the main screen when blank, screen 2 came out of power-saving mode (the led went from amber to green) but remained blank and screen 3 remained in power-saving mode. At this point everything hung - I had to hit the reset button. Upon rebooting and logging back in, I tried "X -configure" hoping to get something working. No luck: blank screens, monitor 3 still in power-saving mode and this time a continuous and very annoying beep from the computer's internal speaker. Had to hit reset again. I've recompiled X.org from CVS and tried that and I had the same problems. I also tried compiling XFree86 from CVS and installed that - still have the same problems. In summary, I've been completely unsuccessful in getting multiple monitors working on Suse 9.2, but the fact that I had exactly the same problem with X.org and XFree86 is puzzling. Has anyone got any ideas? Thanks, -Ross

3 2

Re: [suse-xfree86] Suse 9.2, X.org and Xinerama
by r.maurizzi＠digitalpha.it 12 Oct '04

12 Oct '04

> I've been completely > unsuccessful in getting multiple monitors working on Suse 9.2, but the > fact that I had exactly the same problem with X.org and XFree86 is > puzzling. Just trying to guess obviously, but did you tried to modprobe the relevant dri module for the intel card? And, if that locks up, to modprobe agpgart module to see if it likes the hardware? Ciao, Roberto!

1 0

Re: [suse-xfree86] java kills xserver
by Markus Scheithauer 08 Oct '04

08 Oct '04

---------- Weitergeleitete Nachricht ---------- Subject: Re: [suse-xfree86] java kills xserver Date: Mittwoch, 29. September 2004 18:45 From: Markus Scheithauer <mymailinlist(a)gmx.de> To: r.maurizzi(a)digitalpha.it Oki, I've deleted fonts.dir and fonts.scale and recreated with SuSEconfig - but - same problem. With #Load "freetype" it works but some programms look like c64 :-) Thanks so far, Markus -------------------------------------------------------

2 2

can't connect to Xvnc with the realvnc viewer
by Jim Faulkner 07 Oct '04

07 Oct '04

Hello, I can only view VNC sessions under Suse 9.1 with the tightvnc distribution's vncviewer program. When I attempt to connect to a Suse 9.1 VNC server with RealVNC's vncviewer program, it just hangs and never asks for a password. VNC is supposed to be a very portable application, that allows any valid client to connect to the server. Is Suse going to produce an update for tightvnc that fixes this problem? thanks, Jim Faulkner

2 1