kms etc ati nouveau intel

[Sebastian Glita]

Ok, I attached more, as you asked.

Thanks,
Sebastian
>> user at localhost /root # dmesg
>
>Please attach the full output.

[   16.052092] REISERFS (device dm-4): using ordered data mode
[   16.052093] reiserfs: using flush barriers
[   16.059598] REISERFS (device dm-4): journal params: device dm-4, size 8125, journal first block 66, max trans len 256, max batch 225, max commit age 30, max trans age 30
[   16.060574] REISERFS (device dm-4): checking transaction log (dm-4)
[   16.107586] REISERFS (device dm-4): Using r5 hash to sort names
[   19.088916] atl2 0000:03:00.0: irq 40 for MSI/MSI-X
[   19.502076] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[   21.657168] wlan0: authenticate with 00:14:d1:a9:4c:d9
[   21.666284] wlan0: send auth to 00:14:d1:a9:4c:d9 (try 1/3)
[   21.668155] wlan0: authenticated
[   21.668189] b43 ssb0:0: wlan0: disabling HT as WMM/QoS is not supported
[   21.669093] wlan0: associate with 00:14:d1:a9:4c:d9 (try 1/3)
[   21.671561] wlan0: RX AssocResp from 00:14:d1:a9:4c:d9 (capab=0x411 status=0 aid=3)
[   21.672031] wlan0: associated
[  171.545390] ata5.00: disabled
[  171.547399] cdrom: issuing MRW background format suspend
[ 4066.542870] atl2 0000:03:00.0: irq 40 for MSI/MSI-X
[18117.905491] atl2 0000:03:00.0: irq 40 for MSI/MSI-X
[20102.327916] [drm:r100_bandwidth_update] *ERROR* You may not have enough display bandwidth for current mode
If you have flickering problem, try to lower resolution, refresh rate, or color depth
[20102.327933] divide error: 0000 [#1] PREEMPT SMP 
[20102.327939] Modules linked in: acpi_cpufreq mperf b43 atl2 snd_hda_codec_realtek snd_hda_intel snd_hda_codec sr_mod cdrom ohci_hcd ehci_hcd snd_hwdep asus_laptop input_polldev sparse_keymap microcode [last unloaded: pata_atiixp]
[20102.327961] Pid: 7450, comm: Xorg Not tainted 3.6.10-pf #2 ASUSTeK Computer Inc. F5R                 /F5R       
[20102.327964] EIP: 0060:[<c1357a75>] EFLAGS: 00210246 CPU: 0
[20102.327966] EAX: 78000000 EBX: f5d48000 ECX: 00000000 EDX: 00000000
[20102.327968] ESI: 00000010 EDI: 78000000 EBP: 00000000 ESP: dce2f974
[20102.327970]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[20102.327972] CR0: 80050033 CR2: b75f4830 CR3: 17249000 CR4: 000007d0
[20102.327975] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[20102.327977] DR6: ffff0ff0 DR7: 00000400
[20102.327980] Process Xorg (pid: 7450, ti=dce2e000 task=e4d61310 task.ti=dce2e000)
[20102.327981] Stack:
[20102.327983]  c1645b8d c16f5528 c0099400 c8f8e250 c1594cb4 00001000 00000000 00150852
[20102.327990]  00007000 00000000 00000000 c1594cb4 0003a000 00150852 f5d4e020 00000004
[20102.327997]  00000000 00011fb4 0001c000 00000000 00001000 00046c00 00200082 00200082
[20102.328005] Call Trace:
[20102.328007]  [<c1594cb4>] ? 0xc1594cb4
[20102.328007]  [<c1594cb4>] ? 0xc1594cb4
[20102.328007]  [<c134282e>] ? 0xc134282e
[20102.328007]  [<c1342951>] ? 0xc1342951
[20102.328007]  [<c134297c>] ? 0xc134297c
[20102.328007]  [<c1282581>] ? 0xc1282581
[20102.328007]  [<c1343cc4>] ? 0xc1343cc4
[20102.328007]  [<c134189b>] ? 0xc134189b
[20102.328007]  [<c12f7a98>] ? 0xc12f7a98
[20102.328007]  [<c12f87f2>] ? 0xc12f87f2
[20102.328007]  [<c130872e>] ? 0xc130872e
[20102.328007]  [<c12fc4ea>] ? 0xc12fc4ea
[20102.328007]  [<c130844f>] ? 0xc130844f
[20102.328007]  [<c12fc18e>] ? 0xc12fc18e
[20102.328007]  [<c10d2c75>] ? 0xc10d2c75
[20102.328007]  [<c101ef09>] ? 0xc101ef09
[20102.328007]  [<c101f082>] ? 0xc101f082
[20102.328007]  [<c10d319a>] ? 0xc10d319a
[20102.328007]  [<c102da2a>] ? 0xc102da2a
[20102.328007]  [<c159560c>] ? 0xc159560c
[20102.328007] Code: 03 7c 24 30 31 ed 0f a4 fd 0d c1 e7 0d 89 f8 89 ea 89 d5 89 c7 31 c9 85 d2 74 0c 89 d0 31 d2 f7 74 24 24 89 d5 89 c1 89 ea 89 f8 <f7> 74 24 24 89 ca 89 c7 89 d5 83 c7 01 83 d5 00 0f ac ef 01 89
[20102.328007] EIP: [<c1357a75>]  SS:ESP 0068:dce2f974
[20102.328136] ---[ end trace 02176b0bd0d52620 ]---


>
>BTW, as you can get information about the crash with dmesg, it's not a

>panic but at most an oops. :)


I see.


>
>
>> [   445.074] (II) AIGLX: Loaded and initialized r300
>> [   445.074] (II) GLX: Initialized DRI2 GL provider for screen 0
>
>The log file ends here?


Yes, [Xorg] process cannot be stopped.

>
>
>> I also knew a couple of years ago that AIGLX didn't work for Xpress
>> 200M chipset, so I actually disabled this flag (but simplified back
>> now, as mentioned), but it kept bringing it ON... 
>
>Disabling AIGLX is no longer very useful, as the server side GLX
>implementation depends on the *_dri.so driver for many things now. By
>disabling AIGLX, the server and client side implementations of GLX may
>end up using different *_dri.so, which may cause incompatibility issues.
>
>AIGLX should have worked fine on your card for a long time, certainly
>with KMS/DRI2.
>


>
>-- 
>Earthling Michel Dänzer           |                   http://www.amd.com
>Libre software enthusiast         |          Debian, X and DRI developer
>
>
>