similar to: PA-RISC (hppa) video cards init failure loading the device driver kernel module

Dear Ilia, this page summarize all the possible options of the "nouveau" kernel module: https://nouveau.freedesktop.org/wiki/KernelModuleParameters/ I will test the options that you have suggested as soon as possible. Try a PCI video card is a very good advice because the AGP/FX1(chipset) is on the top of the "usual suspects" list; unfortunately the c8000 has 3.3 PCI slots

The very same option list, but for the "radeon" kernel module: http://xorg.freedesktop.org/wiki/RadeonFeature/#index4h2 Simone Mannori - Italy On 4 April 2016 at 05:56, Simone Mannori <simone.mannori at gmail.com> wrote: > Dear Ilia, > > this page summarize all the possible options of the "nouveau" kernel module: > >

Not sure about the radeon issue, but "DRM: GPU lockup - switching to software fbcon" basically means "the CPU isn't able to submit commands, or the GPU isn't executing the commands". Basically the GPU can only have so many commands outstanding [well, command buffers], and we hit that limit. >From what I understand, PA-RISC has a "funny" architecture that

Hello, since few weeks i have problems with the command: doveadm expunge -A mailbox Trash savedbefore 7d => kernel: doveadm[11609]: segfault at 10 ip b75f146a sp bf856ad0 error 4 in libdovecot.so.0.0.0[b7585000+c8000] but for a single user it's works fine: doveadm expunge -u test at vtlx.de mailbox Trash savedbefore 30h I hope there is a solution for this. with regards Mario --

Sylvain CANOINE wrote: > Could you share your whole Xorg.0.log ? Do you use a custom xorg.conf, or > custom xorg.conf.d files ? Opensource Ati driver, ou proprietary blobs ? Thank you for your interest. I am running CentOS-7 installed from CentOS-7-x86_64-LiveKDE-1503.iso and later upgraded to CentOS-7.2. The only packages I have installed have been from CentOS and Epel repos. I'm sure

This machine is running CentOS 5.3, fully updated Linux mavis.localdomain 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:19:18 EDT 2009 i686 athlon i386 GNU/Linux. Video is an ATI Radeon 9000. X froze overnight and attempts to restart it fail. I tried an old kernel (2.6.18-92.1.22.el5) before realizing that root can start X and a virgin user can start X. I still can't use my original user name.

Hello, I saw in the CentOS 6.6 release notes that the Xorg ABI has changed but that "This should not concern anyone who uses the default drivers shipped with CentOS." I'm using the ATI drivers in Base but X still fails when I boot a CentOS 6.6 kernel. I was hoping this is a known problem that would get fixed with a kernel update but I'm still having problems with the

>.. And KMS modesetting works properly now in Xen dom0! My onboard ATI Radeon is the following: > # lspci -v | grep VGA  11:04.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) (prog-if 00   [VGA controller]) Environment :  Xen 4.0.1-rc6 & 2.6.32.19 on top of F13 ( .config attached) [root@fedora13 ~]# lspci -v | grep VGA 01:00.0 VGA compatible controller: ATI

Hi guys, Well let's face it AGP is a total headache to maintain and dead for at least 10+ years. We have a lot of x86 specific stuff in the architecture independent graphics memory management to get the caching right, abusing the DMA API on multiple occasions, need to distinct between AGP and driver specific page tables etc etc... So the idea here is to just go ahead and remove the support

Am 23.07.2014 12:52, schrieb Daniel Vetter: > On Wed, Jul 23, 2014 at 12:13 PM, Christian K?nig > <christian.koenig at amd.com> wrote: >>> And the dma-buf would still have fences belonging to both drivers, and it >>> would still call from outside the driver. >> >> Calling from outside the driver is fine as long as the driver can do >> everything

Unfortunately AGP is still to widely used as we could just drop support for using its GART. Not using the AGP GART also doesn't mean a loss in functionality since drivers will just fallback to the driver specific PCI GART. For now just deprecate the code and don't enable the AGP GART in TTM even when general AGP support is available. Please comment, Christian.

http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=4d60422 also broken with this commit

> -----Original Message----- > From: Maarten Lankhorst [mailto:maarten.lankhorst at canonical.com] > Sent: Wednesday, July 09, 2014 8:30 AM > To: airlied at linux.ie > Cc: thellstrom at vmware.com; nouveau at lists.freedesktop.org; linux- > kernel at vger.kernel.org; dri-devel at lists.freedesktop.org; > bskeggs at redhat.com; Deucher, Alexander; Koenig, Christian >

Hi Christian Am 11.05.20 um 19:17 schrieb Christian K?nig: > AGP is deprecated for 10+ years now and not used any more on modern hardware. > > Old hardware should continue to work in PCI mode. > > Signed-off-by: Christian K?nig <christian.koenig at amd.com> > --- > drivers/gpu/drm/radeon/Makefile | 4 +- > drivers/gpu/drm/radeon/evergreen.c | 7 -

Joe Perches (2): drm: Use pr_cont where appropriate gpu: drm: Convert printk(KERN_<LEVEL> to pr_<level> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 3 +- drivers/gpu/drm/amd/amdgpu/amdgpu_afmt.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 4 +-

Hey Jeremy, Please pull from devel/pat (based off your xen/dom0/core tree) which has one patch: Konrad Rzeszutek Wilk (1): xen/pat: make pte_flags(x) a pvops function. which is neccessary for the drivers/gpu/drm/radeon driver to work properly with AGP based cards (which look to be the only ones that try to set WC on pages). Also please pull from devel/kms.fixes-05 (based off your

Am 23.07.2014 08:40, schrieb Maarten Lankhorst: > op 22-07-14 17:59, Christian K?nig schreef: >> Am 22.07.2014 17:42, schrieb Daniel Vetter: >>> On Tue, Jul 22, 2014 at 5:35 PM, Christian K?nig >>> <christian.koenig at amd.com> wrote: >>>> Drivers exporting fences need to provide a fence->signaled and a fence->wait >>>> function,

Am 19.05.2014 15:35, schrieb Maarten Lankhorst: > op 19-05-14 14:30, Christian K?nig schreef: >> Am 19.05.2014 12:10, schrieb Maarten Lankhorst: >>> op 19-05-14 10:27, Christian K?nig schreef: >>>> Am 19.05.2014 10:00, schrieb Maarten Lankhorst: >>>> [SNIP] >>>> The problem here is that the whole approach collides with the way >>>>

Am 22.07.2014 17:42, schrieb Daniel Vetter: > On Tue, Jul 22, 2014 at 5:35 PM, Christian K?nig > <christian.koenig at amd.com> wrote: >> Drivers exporting fences need to provide a fence->signaled and a fence->wait >> function, everything else like fence->enable_signaling or calling >> fence_signaled() from the driver is optional. >> >> Drivers

> Regardless of the fence implementation, why would it be a good idea to do a full lockup recovery when some other driver is > calling your wait function? That doesn't seem to be a nice thing to do, so I think a timeout is the best error you could return here, > other drivers have to deal with that anyway. The problem is that we need to guarantee that the lockup will be resolved