System is a HP Zbook 15, i9-9880H, 64GB RAM, 2TB SATA HDD with a T2000
Mobile GPU, Gentoo is installed.
I keep seeing the following:
Feb 21 14:49:13 cobalt kernel: nouveau :01:00.0: fifo: fault 00
[VIRT_READ] at 00019000 engine 0f [ce0] client 20 [HUB/HSCE0]
reason 02 [PTE] on channel
Hardware:
X399 Taichi
AMD Threadripper 1920X
Asus Radeon 5700XT
16GB of RAM
Software:
Gentoo
libdrm 2.4.100
mesa 19.2.7
amdgpudrmfb in use
I'm getting a lot of these OOPS in the log as below. Is there anything
I can do to help fix this?
Thanks,
Alex
Dec 15 10:16:53 titanium kernel: --
The patch below is needed to prevent building mesa with libdrm <
2.4.24.
Regards,
Alex
diff --git a/configure.ac b/configure.ac
index 6662b8a..ad9eb01 100644
--- a/configure.ac
+++ b/configure.ac
@@ -18,7 +18,7 @@ AC_CONFIG_AUX_DIR([bin])
AC_CANONICAL_HOST
dnl Versions for external dependenci
The patch below is needed to prevent building mesa with libdrm <
2.4.24.
Regards,
Alex
diff --git a/configure.ac b/configure.ac
index 6662b8a..ad9eb01 100644
--- a/configure.ac
+++ b/configure.ac
@@ -18,7 +18,7 @@ AC_CONFIG_AUX_DIR([bin])
AC_CANONICAL_HOST
dnl Versions for external dependenc
Hi!
After experiencing the exact same problem with two other distributions
(Fedora 15 and Ubuntu Natty), and again with Gentoo, I'm now asking
whether anyone has experienced the same problems with the NV11 chipset.
Symptoms:
First my Xorg.0.log:
(only the last few lines included)
[70.626] (
Hi!
After experiencing the exact same problem with two other distributions
(Fedora 15 and Ubuntu Natty), and again with Gentoo, I'm now asking
whether anyone has experienced the same problems with the NV11 chipset.
Symptoms:
First my Xorg.0.log:
(only the last few lines included)
[70.626] (
As this has now happened twice in the last two weeks, I thought I'd
write this up.
This morning I came back to my laptop to find it had locked up, even ssh
couldn't gain access to the machine. I rebooted the machine and tried to
start X. X refused to start, so I looked at the logs where it locked
As this has now happened twice in the last two weeks, I thought I'd
write this up.
This morning I came back to my laptop to find it had locked up, even ssh
couldn't gain access to the machine. I rebooted the machine and tried to
start X. X refused to start, so I looked at the logs where it locked
On Wed, 2010-04-21 at 20:38 -0400, Alex Deucher wrote:
> On Wed, Apr 21, 2010 at 6:26 PM, Alex Buell
> wrote:
> > On Thu, 2010-04-22 at 07:55 +1000, Dave Airlie wrote:
> >> > I'd like to step up for that, it'd let me learn a lot. I have
> >> already
>
On Wed, 2010-04-21 at 20:38 -0400, Alex Deucher wrote:
> On Wed, Apr 21, 2010 at 6:26 PM, Alex Buell
> wrote:
> > On Thu, 2010-04-22 at 07:55 +1000, Dave Airlie wrote:
> >> > I'd like to step up for that, it'd let me learn a lot. I have
> >> already
>
On Wed, 2010-04-21 at 20:38 -0400, Alex Deucher wrote:
> > Any further reading would be tremendously helpful.
> >
>
> It should be pretty easy to get kms going with r128 by integrating it
> into the radeon drm and ddx. The hard part will be porting the r128
> 3D driver to kms. Also, kms support
On Wed, 2010-04-21 at 20:38 -0400, Alex Deucher wrote:
> On Wed, Apr 21, 2010 at 6:26 PM, Alex Buell wrote:
> > On Thu, 2010-04-22 at 07:55 +1000, Dave Airlie wrote:
> >> > I'd like to step up for that, it'd let me learn a lot. I have
> >> already
> &
On Wed, 2010-04-21 at 20:38 -0400, Alex Deucher wrote:
> On Wed, Apr 21, 2010 at 6:26 PM, Alex Buell wrote:
> > On Thu, 2010-04-22 at 07:55 +1000, Dave Airlie wrote:
> >> > I'd like to step up for that, it'd let me learn a lot. I have
> >> already
> &
On Wed, 2010-04-21 at 20:38 -0400, Alex Deucher wrote:
> > Any further reading would be tremendously helpful.
> >
>
> It should be pretty easy to get kms going with r128 by integrating it
> into the radeon drm and ddx. The hard part will be porting the r128
> 3D driver to kms. Also, kms support
On Thu, 2010-04-22 at 07:55 +1000, Dave Airlie wrote:
> > I'd like to step up for that, it'd let me learn a lot. I have
> already
> > extracted the r128 and its DRI from the 2.6.32 kernel tree and built
> > them as modules and they both work just fine, with the binary
> firmware.
> > What's involve
On Wed, 2010-04-21 at 16:02 -0400, Matt Turner wrote:
> On Wed, Apr 21, 2010 at 3:51 PM, Alex Buell
> wrote:
> > Does the r128 dri driver supports KMS in the kernel on PPC? I've a G3
> > iMac 600 here working very well with OpenGL but was wondering if it
> > could
Does the r128 dri driver supports KMS in the kernel on PPC? I've a G3
iMac 600 here working very well with OpenGL but was wondering if it
could support KMS, in which case it would be quite nice.
Thanks
--
http://www.munted.org.uk
One very high maintenance cat living here.
On Thu, 2010-04-22 at 07:55 +1000, Dave Airlie wrote:
> > I'd like to step up for that, it'd let me learn a lot. I have
> already
> > extracted the r128 and its DRI from the 2.6.32 kernel tree and built
> > them as modules and they both work just fine, with the binary
> firmware.
> > What's involve
On Wed, 2010-04-21 at 16:02 -0400, Matt Turner wrote:
> On Wed, Apr 21, 2010 at 3:51 PM, Alex Buell wrote:
> > Does the r128 dri driver supports KMS in the kernel on PPC? I've a G3
> > iMac 600 here working very well with OpenGL but was wondering if it
> > could sup
Does the r128 dri driver supports KMS in the kernel on PPC? I've a G3
iMac 600 here working very well with OpenGL but was wondering if it
could support KMS, in which case it would be quite nice.
Thanks
--
http://www.munted.org.uk
One very high maintenance cat living here.
__
On Tue, 2010-04-20 at 18:02 +0100, Alex Buell wrote:
> On Tue, 2010-04-20 at 11:38 -0500, Bridgman, John wrote:
> > There might be a clue in the dmesg output.
> >
> > This is looking less like a mesa dev issue - is there a better list for
> > this ?
>
>
On Tue, 2010-04-20 at 11:38 -0500, Bridgman, John wrote:
> There might be a clue in the dmesg output.
>
> This is looking less like a mesa dev issue - is there a better list for this
> ?
I'll move it over to the dri-dev mailing list.
Thanks
> > -Original Mess
On Tue, 2010-04-20 at 18:02 +0100, Alex Buell wrote:
> On Tue, 2010-04-20 at 11:38 -0500, Bridgman, John wrote:
> > There might be a clue in the dmesg output.
> >
> > This is looking less like a mesa dev issue - is there a better list for
> > this ?
>
>
On Tue, 2010-04-20 at 11:38 -0500, Bridgman, John wrote:
> There might be a clue in the dmesg output.
>
> This is looking less like a mesa dev issue - is there a better list for this
> ?
I'll move it over to the dri-dev mailing list.
Thanks
> > -Original Mess
Machine in question has a R128 card w/ 16MB of RAM. Recently I realised
that the xorg server wasn't loading the r128 DRI driver at all, so I
rebuilt the modules necessary (dri.ko and r128.ko), loaded them, then
started the X server.
At this point the display went blank and I found this in the Xor
Machine in question has a R128 card w/ 16MB of RAM. Recently I realised
that the xorg server wasn't loading the r128 DRI driver at all, so I
rebuilt the modules necessary (dri.ko and r128.ko), loaded them, then
started the X server.
At this point the display went blank and I found this in the Xor
On Thu, 2010-04-15 at 13:58 +0100, Alex Buell wrote:
> Celestia 1.6.0 again shows corrupted rendering on planets, other parts
> rendered correctly with the latest git pull on the nvfx-next-5 tree.
>
> Yesterday's nvfx-next tree worked perfectly.
With today's nvfx-next
Celestia 1.6.0 again shows corrupted rendering on planets, other parts
rendered correctly with the latest git pull on the nvfx-next-5 tree.
Yesterday's nvfx-next tree worked perfectly.
--
http://www.munted.org.uk
One very high maintenance cat living here.
On Thu, 2010-04-15 at 13:58 +0100, Alex Buell wrote:
> Celestia 1.6.0 again shows corrupted rendering on planets, other parts
> rendered correctly with the latest git pull on the nvfx-next-5 tree.
>
> Yesterday's nvfx-next tree worked perfectly.
With today's nvfx-next
Celestia 1.6.0 again shows corrupted rendering on planets, other parts
rendered correctly with the latest git pull on the nvfx-next-5 tree.
Yesterday's nvfx-next tree worked perfectly.
--
http://www.munted.org.uk
One very high maintenance cat living here.
___
30 matches
Mail list logo
