Hi,
On Tue, 25 Jan 2011, Cyril Brulebois wrote:
could you please check whether there's something in Xorg.0.log.old?
Maybe the one with no info is a restarted one?
No, it ends up with :
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 14, (OK)
drmOpenByBusid: drmOpenMinor returns 14
drmOpenByBusid: Interface 1.4 failed, trying 1.1
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: Loaded and initialized /usr/lib/dri/mga_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
Could you please also check what's in dmesg, maybe there would be some
clue?
Nothing unusual either :
[drm] Initialized drm 1.1.0 20060810
pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[drm] Initialized mga 3.2.1 20051102 for 0000:01:00.0 on minor 0
agpgart-via 0000:00:00.0: AGP 2.0 bridge
agpgart-via 0000:00:00.0: putting AGP V2 device into 1x mode
pci 0000:01:00.0: putting AGP V2 device into 1x mode
[drm] Initialized card for AGP DMA.
agpgart-via 0000:00:00.0: AGP 2.0 bridge
agpgart-via 0000:00:00.0: putting AGP V2 device into 1x mode
pci 0000:01:00.0: putting AGP V2 device into 1x mode
[drm] Initialized card for AGP DMA.
agpgart-via 0000:00:00.0: AGP 2.0 bridge
agpgart-via 0000:00:00.0: putting AGP V2 device into 1x mode
pci 0000:01:00.0: putting AGP V2 device into 1x mode
[drm] Initialized card for AGP DMA.
The last part is repeated three times because X crashes and is
restarted 3 times before it gives up.
To collect info, you could run the xorg bug script and attach its
output:
/usr/share/bug/xorg/script 3>/tmp/script.log
bash: /usr/share/bug/xorg/script: No such file or directory
Also, you could try with the kernel in experimental (2.6.37), or with
the X stack from experimental.
I'm already running with a custom 2.6.36 kernel from kernel.org.
As using the vesa driver was no viable option (no direct rendering,
no video overlay) I ended up downgrading all xorg packages the the
old lenny versions (I just kept the xserver-xorg control package
from squeeze and rebuild it with relaxed version dependancies so apt
would not complain).
Maybe fbdev would ease the pain?
Better refresh rates than vesa, but still no accelerated 3D rendering
and no video overlay...
Anyways, I did some test with the Matrox G550 card in another system
also in squeeze and it worked fine in that system, with the
same xorg.conf and the same kernel.
I then plugged the card back in the affected system but swapped the
harddisks, and it also worked fine.
Finally, I put the original hard disk back in, upgraded Xorg again
to the squeeze version and the problem reappeared :-(
So, I have something on that disk that is causing trouble. I already
know it's not xorg.conf nor the kernel. And I have the same set of
xserver-* packages on the two systems.
--
Etienne Vogt.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/pine.lnx.4.64.1101260011540.32...@zuul.vogt-bodving.test
