Weird checkerpattern on X

poiu_ytrewq · 2012-06-10 19:10:34

Hello,

I am still quite new to all of arch, but I did about 20 installation now, and most of the times they were fast and easy to setup to a working environment.
But now I stumbled upon this weird checkerpattern all over my screen.
I'm using xf86-video-ati and openbox and the newest xorg-server

I read quite a bit about the ATI support in arch, since before this day i only installed NVidia graphic drivers( nouveau).

My videocard is an Asus EAH 5830, and is fully functional under Windows 7 (but I want to go whole the way and say goodbye to Windows as main OS)

This is the messages it gives when doing `dmesg | egrep "drm|radeon"` :

[    3.106707] [drm] Initialized drm 1.1.0 20060810
[    3.258406] [drm] radeon defaulting to kernel modesetting.
[    3.258410] [drm] radeon kernel modesetting enabled.
[    3.258699] [drm] initializing kernel modesetting (CYPRESS 0x1002:0x689E 0x1043:0x036A).
[    3.258774] [drm] register mmio base: 0xFF5E0000
[    3.258775] [drm] register mmio size: 131072
[    3.259784] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[    3.259787] radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF
[    3.259796] [drm] Detected VRAM RAM=1024M, BAR=256M
[    3.259798] [drm] RAM width 256bits DDR
[    3.259884] [drm] radeon: 1024M of VRAM memory ready
[    3.259886] [drm] radeon: 512M of GTT memory ready.
[    3.259911] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    3.259913] [drm] Driver supports precise vblank timestamp query.
[    3.259961] radeon 0000:01:00.0: irq 69 for MSI/MSI-X
[    3.259972] radeon 0000:01:00.0: radeon: using MSI.
[    3.260019] [drm] radeon: irq initialized.
[    3.260024] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    3.260962] [drm] radeon: ib pool ready.
[    3.261128] [drm] Loading CYPRESS Microcode
[    3.359300] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[    3.359455] radeon 0000:01:00.0: WB enabled
[    3.359459] [drm] fence driver on ring 0 use gpu addr 0x40000c00 and cpu addr 0xffff8801754f4c00
[    3.377118] [drm] ring test on 0 succeeded in 1 usecs
[    3.377627] [drm] ib test on ring 0 succeeded in 0 usecs
[    3.378247] [drm] Radeon Display Connectors
[    3.378249] [drm] Connector 0:
[    3.378250] [drm]   DisplayPort
[    3.378252] [drm]   HPD5
[    3.378254] [drm]   DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
[    3.378256] [drm]   Encoders:
[    3.378257] [drm]     DFP1: INTERNAL_UNIPHY2
[    3.378259] [drm] Connector 1:
[    3.378260] [drm]   HDMI-A
[    3.378262] [drm]   HPD4
[    3.378264] [drm]   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
[    3.378265] [drm]   Encoders:
[    3.378267] [drm]     DFP2: INTERNAL_UNIPHY2
[    3.378268] [drm] Connector 2:
[    3.378270] [drm]   DVI-I
[    3.378271] [drm]   HPD6
[    3.378273] [drm]   DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 0x647c
[    3.378275] [drm]   Encoders:
[    3.378276] [drm]     DFP3: INTERNAL_UNIPHY
[    3.378278] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[    3.378318] [drm] Internal thermal controller with fan control
[    3.378390] [drm] radeon: power management initialized
[    3.563094] [drm] fb mappable at 0xB0142000
[    3.563097] [drm] vram apper at 0xB0000000
[    3.563098] [drm] size 8294400
[    3.563100] [drm] fb depth is 24
[    3.563101] [drm]    pitch is 7680
[    3.563173] fbcon: radeondrmfb (fb0) is primary device
[    4.067957] fb0: radeondrmfb frame buffer device
[    4.067959] drm: registered panic notifier
[    4.067966] [drm] Initialized radeon 2.13.0 20080528 for 0000:01:00.0 on minor 0
[    4.068004] radeon 0000:06:02.0: enabling device (0080 -> 0083)
[    4.068221] [drm] initializing kernel modesetting ([b]RV100[/b] 0x1002:0x515E 0x1043:0x81DE).
[    4.068272] [drm] register mmio base: 0xFF9F0000
[    4.068274] [drm] register mmio size: 65536
[    4.068345] radeon 0000:06:02.0: Invalid ROM contents
[    4.068596] radeon 0000:06:02.0: Invalid ROM contents
[    4.068787] [drm:radeon_get_bios] [b]*ERROR* Unable to locate a BIOS ROM[/b]
[    4.069012] radeon 0000:06:02.0: Card not posted and no BIOS - ignoring
[    4.069230] radeon 0000:06:02.0: Fatal error during GPU init
[    4.069421] [drm] radeon: finishing device.
[    4.069609] [drm] radeon: cp finalized
[    4.069611] radeon 0000:06:02.0: no bo for sa manager
[    4.070012] radeon: probe of 0000:06:02.0 failed with error -22

checkerexample: http://ikzorgvooru.nu/im/black_stripes.jpg

Though i see RV 100 showing up in that log.
In the manual for radeon it says that is the Juniper chip, I saw something about UMS.

So I was wondering if someone could assist me to get rid of the check artifacts (I don't know if artifacts is the correct term here), because that would be greatly appreciated.

ConnorBehan · 2012-06-11 00:29:33

The dmesg you posted says that KMS is failing, so yeah you would be using UMS. And that is not really supported anymore so it could easily be broken without the upstream devs knowing. Can you get the dmesg error to go away by downgrading the kernel? A *dangerous* command you could try to reset your video BIOS and possibly fix it is "vbetool".

Other ideas for what you could specify in the Device section of xorg.conf:
Option "ColorTiling" "false"
Option "AccelMethod" "XAA"

poiu_ytrewq · 2012-06-12 22:09:56

I tried those Options in xorg.conf, that didn't helped much. Also I tried a kernel downgrade 2.6, but also no result.
So i went on a search on how to reset my video BIOS with vbetool, but so far i haven't found a description from which i am for sure my actions wont demolish my video card, since it works fine under Windows.

Can someone elaborate on the usage of the vbetool, and if not, already many thanks for your support. I decided to buy a new pc with a nVidia card. But also I still would like to also have this pc working with arch.
If more information is needed I can give it.

Arch Linux

#1 2012-06-10 19:10:34

Weird checkerpattern on X

#2 2012-06-11 00:29:33

Re: Weird checkerpattern on X

#3 2012-06-12 22:09:56

Re: Weird checkerpattern on X

Board footer