More details please! dmesg? xorg.0.log? lspci output, etc.

find my dmesg enclosed. I use :

X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux marduk 2.6.20-ARCH #1 SMP PREEMPT Sun Apr 8 02:39:03 CEST 2007 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present


Seems bug appear when aiglx is enabled.

lspci & Xorg.0.log

[benoitc@marduk ~]$ lspci
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio Processing Unit (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:04.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
01:08.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01)
01:08.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) (rev 01)
01:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
01:09.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
01:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
01:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a)
01:0b.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)
03:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2)

Try disabling vesafb, nvidia drivers are not happy with that usually.

it changed nothing. Screen suddenly freeze. Maybe it coukld be related on last gnome ? How could I get logs for it ? Seems nautilust lost connection to X display 0:0.

I had some problem before when I use ati card on another screen with nv driver , ati screen suddenly lost X. So maybe it's related to the fact I use a raid1 (mdadm) or LVM ? My root is on the LVM.

I join my xorg.conf to help.

more test this morning :

The scren freeze after whyle. The display become fuzzy. When I go back to the console I have this error messages :
gnome-session lost X display 0:0

the same for other applications.

Fuzzy display would cause me to look at my hardware. Nforce2 boards are from the times when mainboard manufacturers used bad capacitors (yes, even Asus and other A-brands), could you check for that first?

I never had this problem before, and don't have this problem other systems like openbsd with nv or another gnu/linux with nvidia driver. What do you mean exactly by bad capacitors ?

After looking more in logs I see that :

dmesg :
md: md2 stopped.
EXT3 FS on dm-0, internal journal
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1999992k swap on /dev/md1. Priority:-1 extents:1 across:1999992k


and in /var/log/messages.log :

Apr 10 08:29:11 marduk md: raid1 personality registered for level 1
Apr 10 08:29:11 marduk md: bind<sda1>
Apr 10 08:29:11 marduk md: bind<sdb1>
Apr 10 08:29:11 marduk raid1: raid set md0 active with 2 out of 2 mirrors
Apr 10 08:29:11 marduk md: bind<sda2>
Apr 10 08:29:11 marduk md: bind<sdb2>
Apr 10 08:29:11 marduk raid1: raid set md1 active with 2 out of 2 mirrors
Apr 10 08:29:11 marduk md: bind<sda3>
Apr 10 08:29:11 marduk md: bind<sdb3>
Apr 10 08:29:11 marduk raid1: raid set md3 active with 2 out of 2 mirrors

So no more md2, md2 became md3 :
[benoitc@marduk ~]$ cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sdb3[1] sda3[0]
193109248 blocks [2/2] [UU]

md1 : active raid1 sdb2[1] sda2[0]
2000000 blocks [2/2] [UU]

md0 : active raid1 sdb1[1] sda1[0]
248896 blocks [2/2] [UU]

unused devices: <none>



So maybe the probleme is related to pata or raid1 ? I use pata_amd as driver in mkinitcpio to init first raid1. lsmod give me :
[benoitc@marduk ~]$ lsmod | grep ata
sata_sil 8840 0
sata_nv 14980 0
pata_amd 10380 6
libata 94100 3 sata_sil,sata_nv,pata_amd


Hope it could help.

i forgotot to atatch log files in last comment. Here it is.

messages.logs with good upload ?