PLEX86  x86- Virtual Machine (VM) Program
 Plex86  |  CVS  |  Mailing List  |  Download  |  Linux  |  Newsgroups

Urgent Xorg translucency problems system unusable


Your Ad Here

Your Ad Here

Working on making a dual boot again, WinXP & Ubuntu 505
Timothy Daniels - Nehmo - Looking up "Active Parbreastion", I get this definition: "The active parbreastion is the parbreastion on the first hard disk which is automatically booted when no boot manager...

Jes Vestervang

Funny that you should mention that. I initially did not have these lines when I first encountered the problem. I then added them after discovering through Google that they had some bearing on translucency capabilities of Xorg (most of the references therein were to Nvidia graphic cards, mine is an Intel). No difference. And as expected, your advice to remove them has not made any difference either.

Another symptom - ctrl+alt+backspace does not seem to kill the x server, and

To cover all bases, my xorg.conf follows. Could it be one of the loaded modules that are causing this problem with the upgraded version of xorg ?

# xorg.conf (Xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cpetc-X11-xorg.confetc-X11-xorg.conf.custom # dpkg-reconfigure xserver-xorg

Section "Files" FontPath "unix-:7100" # local font server # if the local font server has problems, we can fall back on these FontPath "-usr-lib-X11-fonts-misc" FontPath "-usr-lib-X11-fonts-cyrillic" FontPath "-usr-lib-X11-fonts-100dpi-:unscaled" FontPath "-usr-lib-X11-fonts-75dpi-:unscaled" FontPath "-usr-lib-X11-fonts-Type1" FontPath "-usr-lib-X11-fonts-CID" FontPath "-usr-lib-X11-fonts-100dpi" FontPath "-usr-lib-X11-fonts-75dpi" FontPath "-usr-lib-X11-fonts-Gurmukhi" FontPath "-usr-lib-X11-fonts-Mac" FontPath "-usr-lib-X11-fonts-extra" EndSection

Section "Module" Load "bitmap" Load "dbe" Load "ddc" Load "dri" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "record" Load "type1" Load "v4l" Load "vbe" EndSection

Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection

Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "-dev-input-mice" Option "Protocol" "ImPS-2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "-dev-psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" EndSection

Section "Device" Identifier "Intel Corporation 82852-855GM Integrated Graphics Device" Driver "i810" EndSection

Section "Monitor" Identifier "Generic Monitor" Option "DPMS" HorizSync 28-49 VertRefresh 43-72 EndSection

Section "Screen" Identifier "Default Screen" Device "Intel Corporation 82852-855GM Integrated Graphics Device" Monitor "Generic Monitor" DefaultDepth 24 SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection

Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection

Section "DRI" Mode 0666 EndSection

#Section "Extensions" # Option "Composite" "Enable" # Option "RENDER" "Enable" #EndSection

I dare not include the entire Xorg.0.log file as it is humoungous. However, upon perusal, I find some intriguing points :

1 :

X Window System Version 6.9.0 (Debian 6.9.0.dfsg.1-4 20060114230205 David X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: Linux 2.6.15-1-686 i686 ELF Current Operating System: Linux nanak 2.6.12-1-386 #1 Tue Sep 27 12:41:08 JST 2005 i686 to make sure that you have the latest version.

Working on making a dual boot again, WinXP & Ubuntu 508
In comp.os.linux.misc, on Wed 22 February 2006 22:29, Nehmo Possibly not for a couple of reasons...

This version of X was built against a newer version of the kernel than I am running.

2 :

(WW) ****INVALID MEM ALLOCATION**** b: 0xffe80000 e: 0xffefffff correcting

3 :

drmOpenDevice: node name isdev-dri-card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed drmOpenDevice: node name isdev-dri-card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID pci:0000:00:02.0 drmOpenDevice: node name isdev-dri-card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: drmOpenMinor returns 9 drmOpenByBusid: drmGetBusid reports pci:0000:00:02.1 drmOpenDevice: node name isdev-dri-card1 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: drmOpenMinor returns 9 drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 (II) I810(0): drm loaded kernel module for "i915" driver (II) I810(0): drm DRM interface version 1.2 (II) I810(0): drm created "i915" driver at busid "pci:0000:00:02.0"

4:

(WW) I810(0): Extended BIOS function 0x5f05 failed.

5:

(WW) I810(0): PGTBLER is 0xffffffff (WW) I810(0): PRB0CTL (0xffffffff) indicates ring buffer enabled (WW) I810(0): PRB0HEAD (0xffffffff) and PRB0TAIL (0xffffffff) indicate ring buffer not flushed

I include this because a lot of the really strange errors later make references to rings and such.

6 :

(II) I810(0): direct rendering: Enabled ADVANCELPRING: outring (0x7) isn't on a QWord boundary(==) RandR enabled

7 :

ADVANCELPRING: outring (0x2f) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundaryADVANCELPRING: outring (0x17) isn't on a QWord boundaryADVANCELPRING: outring (0x2f) isn't on a QWord boundaryADVANCELPRING: outring (0x47) isn't on a QWord boundaryADVANCELPRING: outring (0x5f) isn't on a QWord boundaryADVANCELPRING: outring (0x77) isn't on a QWord boundaryADVANCELPRING: outring (0x8f) isn't on a QWord boundaryADVANCELPRING: outring (0xa7) isn't on a QWord boundaryADVANCELPRING: outring (0xbf) isn't on a QWord boundaryADVANCELPRING: outring (0xd7) isn't on a QWord boundaryADVANCELPRING: outring (0xef) isn't on a QWord boundaryADVANCELPRING: outring (0x107) isn't on a QWord boundaryADVANCELPRING: outring (0x11f) isn't on a QWord boundaryADVANCELPRING: outring (0x137) isn't on a QWord boundaryADVANCELPRING: outring (0x14f) isn't on a QWord

been using only root account system compromized 502
Thanks for the answer. I found out that the PermitRootLogin line was commented out and that UsePAM was enabled. I attach a copy of the file...

.... (a lot of such errors, sentences not even broken up)

followed by :

ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundary(WW) I810(0): Fixing display offsets. ADVANCELPRING: outring (0x7) isn't on a QWord boundaryADVANCELPRING: outring (0x27) isn't on a QWord boundarySynaptics DeviceOff called (II) I810(0): drm removed 1 reserved context for kernel (II) I810(0): drm unmapping 8192 bytes of SAREA 0xe000b000 at 0xb7965000 ADVANCELPRING: outring (0x7) isn't on a QWord boundary

Now, in all my years of using X, I have never seen such errors. Could it all just be due to the DRI module not loading properly or something like that ?



Your Ad Here

List | Previous | Next

been using only root account system compromized 502

Linux groups from Newsgroups

The #1 Usenet Provider on the Internet

Urgent KDE translucency problems system unusable