I have a serious problem and I don't now if it's related to kernel or opensource drivers. I'm using Xubuntu 13.04, I have a Mobility Radeon HD 3650 card and I use the latest version of the kernel (3.12) with DPM activated and the Oibaf PPA. Often, the screen freezes, goes black and then turns on again but there are graphical glitches (distortions and other things) and the system is unresponsive, then I have to do a forced shutdown. Does anyone else have the same problem?
Thanks in advance.
-
Lucky that your HD6870 works with RBE. Using it on my Sapphire HD6850 causes blue screens in Windows and radeon not to load at all in Linux. Shame, because that was my prefered method of managing fan speeds for my cards (and forcing overclocks).Leave a comment:
-
The problem might be the BIOS fan values.
Catalyst seems to ignore high minimum fan values and forces it's own.
Minimum BIOS settings for my GigaByte 6870 Windforce was 70%, had to modify it with the Radeon Bios Editor from TechPowerUp to silence the card with the opensource driver.
Leave a comment:
-
After testing radeon.dpm=1 on the latest batch of LiveCDs featuring the 3.11 kernel (openSUSE 13.1 beta 1, Ubuntu 13.10 beta 2), it seems the fan on my Gigabyte HD7770 OC doesn't care much for it an spins at full speed. Is an HDD install required, in order to pull in some extra tidbits? The /lib/firmware/radeon folder seemed to be in order...Leave a comment:
-
The driver works very well on A8-5500 APU with the HD 7560D IGP. I get the same temperatures (at least from what "sensors" tells me) as with fglrx and just about the same graphics performance in games I USE - dont start with benchmarks or the like, for what I USE its better than fglrx.
Opengl, hw decoding works as it should, Steam/Source games do much better than with fglrx. VDPAU works well in mplayer - i do get some corruption here and there, but if i restart the playback, it goes away.
Its a better experience compared to fglrx - the video playback is vsynced, no tearing. VDPAU is implemented in most video players (and will even be in vlc 2.1 AFAIK), unlike xvba which, i hear, gets phased out even from xbmc, the only player that supported it (in a special branch that is) because of the fglrx devs "deafness" - they will focus on radeon/vdpau instead.
Now, the bad:
The problem is that it frezes the computer after a few hours of use. I tried tons of kernel compile options, kernel boot options to no avail so far.
Now i use the latest git kernel (linus' git) combined with git://people.freedesktop.org/~agd5f/linux, drm-fixes-3.12 branch. Also i compile the latest mesa from git. So far (since 3.11 rc2 if i remember correctly) i have freezes with radeon.
- I noticed that using radeon with dpm makes the CPU throttle hard when it shouldnt (with both ondemand and conservative governors) - for example during kernel compile with 4 threads the clock speeds (nominally its 3.2GHz, turbo 3.7, effectively turbo is ~3.5GHz) go as low as 1.8 GHz sometimes (cpuinfo says 3.2 GHz, but cpufreq-aperf says 1.88-2 GHz, so its some internal downclocking, not the governors fault). Sometimes they keep up 3.2-3.29 the whole time at the same temperatures (fglrx always uses frequencies above the nominal clock speed, even if with a wee bit, with the same thermals - 50-55C).
- If i use the ondemand governor the CPU is kept at its maximum voltage level (1.34v) after i log in. If i do a dpms off/on on the monitor, the voltage starts changing between its limits as it is required (0.9-1.34v). Also, adding acpi=strict to the kernel boot parameters and using the conservative governor, this problem goes away.
At bootup, i get this oops-like "info" (noticed with the recent kernels, if the framebuffer console is initialized):
Once i unticked something from the framebuffer suport in the kernel config and i got a blank screen until X loaded (and even after that no console) and this "info" wasnt in the dmesg. But nonetheless the computer froze. Also i got the impression that when compiling the clock speeds were kept higher (most of the time were just as with fglrx).Code:[ 9.621693] resource map sanity check conflict: 0xc0480000 0xc1487fff 0xc0000000 0xc04fffff BOOTFB [ 9.621699] ------------[ cut here ]------------ [ 9.621708] WARNING: CPU: 3 PID: 439 at arch/x86/mm/ioremap.c:171 __ioremap_caller+0x2d8/0x370() [ 9.621713] Info: mapping multiple BARs. Your kernel is fine. [ 9.621716] Modules linked in: joydev hid_generic kvm_amd snd_hda_codec_realtek usbhid hid kvm snd_hda_codec_hdmi radeon(+) crc32c_intel ttm drm_kms_helper snd_hda_intel ghash_clmulni_intel aesni_intel snd_hda_codec aes_x86_64 drm snd_hwdep ablk_helper evdev uvcvideo videobuf2_vmalloc acpi_cpufreq videobuf2_memops psmouse cryptd videobuf2_core snd_pcm lrw processor gf128mul thermal_sys snd_page_alloc videodev ohci_pci snd_seq glue_helper snd_seq_device media k10temp pcspkr serio_raw snd_timer snd ohci_hcd i2c_algo_bit soundcore i2c_piix4 i2c_core button ext4 crc16 jbd2 mbcache dm_mod sg sd_mod sr_mod cdrom crc_t10dif crct10dif_common ahci libahci libata ehci_pci microcode scsi_mod ehci_hcd xhci_hcd r8169 mii usbcore usb_common [ 9.621792] CPU: 3 PID: 439 Comm: modprobe Not tainted 3.12.0-rc2+ #6 [ 9.621796] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A85X-D3H, BIOS F1 10/09/2012 [ 9.621817] 0000000000000009 ffff880036e81840 ffffffff814914a7 ffff880036e81888 [ 9.621825] ffff880036e81878 ffffffff810460e7 ffffc90011a80000 00000000c1488000 [ 9.621831] 00000000c0480000 0000000000000010 00000000000c1488 ffff880036e818d8 [ 9.621838] Call Trace: [ 9.621846] [<ffffffff814914a7>] dump_stack+0x45/0x56 [ 9.621853] [<ffffffff810460e7>] warn_slowpath_common+0x87/0xb0 [ 9.621858] [<ffffffff810461c7>] warn_slowpath_fmt+0x47/0x50 [ 9.621863] [<ffffffff81039c38>] __ioremap_caller+0x2d8/0x370 [ 9.621868] [<ffffffff81039e0e>] ioremap_wc+0x2e/0x30 [ 9.621877] [<ffffffffa03d3580>] ttm_bo_kmap+0x230/0x260 [ttm] [ 9.621918] [<ffffffffa0429886>] radeon_bo_kmap+0x66/0xa0 [radeon] [ 9.621959] [<ffffffffa0485238>] radeon_sa_bo_manager_start+0x98/0x1e0 [radeon] [ 9.622000] [<ffffffffa042a634>] radeon_vm_manager_init+0xe4/0x120 [radeon] [ 9.622040] [<ffffffffa04800bc>] cayman_startup+0x16ac/0x1760 [radeon] [ 9.622080] [<ffffffffa0480c59>] cayman_init+0x199/0x2b0 [radeon] [ 9.622109] [<ffffffffa040ed0a>] radeon_device_init+0x6da/0x7f0 [radeon] [ 9.622140] [<ffffffffa0410ca9>] radeon_driver_load_kms+0x89/0x1d0 [radeon] [ 9.622151] [<ffffffffa035cb5f>] drm_get_pci_dev+0x12f/0x300 [drm] [ 9.622181] [<ffffffffa040d175>] radeon_pci_probe+0xa5/0xd0 [radeon] [ 9.622187] [<ffffffff81289386>] local_pci_probe+0x46/0x80 [ 9.622192] [<ffffffff812895c1>] pci_device_probe+0x101/0x110 [ 9.622199] [<ffffffff81345222>] driver_probe_device+0x72/0x230 [ 9.622204] [<ffffffff8134547b>] __driver_attach+0x9b/0xa0 [ 9.622209] [<ffffffff813453e0>] ? driver_probe_device+0x230/0x230 [ 9.622215] [<ffffffff81343435>] bus_for_each_dev+0x55/0x90 [ 9.622220] [<ffffffff81344d49>] driver_attach+0x19/0x20 [ 9.622226] [<ffffffff8134489c>] bus_add_driver+0xfc/0x280 [ 9.622231] [<ffffffff81345aaf>] driver_register+0x5f/0xf0 [ 9.622237] [<ffffffffa0543000>] ? 0xffffffffa0542fff [ 9.622243] [<ffffffff81288517>] __pci_register_driver+0x47/0x50 [ 9.622253] [<ffffffffa035ce4a>] drm_pci_init+0x11a/0x130 [drm] [ 9.622259] [<ffffffffa0543000>] ? 0xffffffffa0542fff [ 9.622288] [<ffffffffa0543097>] radeon_init+0x97/0xb5 [radeon] [ 9.622294] [<ffffffff81000302>] do_one_initcall+0x112/0x160 [ 9.622299] [<ffffffff8103b433>] ? set_memory_nx+0x43/0x50 [ 9.622308] [<ffffffff810ad999>] load_module+0x1d59/0x2530 [ 9.622313] [<ffffffff810aa2b0>] ? show_initstate+0x50/0x50 [ 9.622319] [<ffffffff810ae20e>] SyS_init_module+0x9e/0xc0 [ 9.622324] [<ffffffff8149c5e2>] system_call_fastpath+0x16/0x1b [ 9.622328] ---[ end trace c48a216262ec6d3b ]---
Hardware is A8-5500 APU on a Gigabyte F2A85X-D3H mobo with 4 GB of RAM, Debian Testing 64-bit with Xfce 4.10.
I did file a bug report ( https://bugs.freedesktop.org/show_bug.cgi?id=67800 ).
Note: The hardware is most likely fine since i never get any of the above issues with fglrx.Leave a comment:
Leave a comment: