Where did you see instructions for doing this? Apparently this is
disabled on purpose due to spam. Or did you just assume it would work
based on other mailman lists?
On Mon, Jun 11, 2018 at 1:08 PM, Dan Jacobson wrote:
> Can't join the list confirming via email.
> Will get:
>
>
On Mon, Jun 11, 2018 at 1:32 PM, 積丹尼 Dan Jacobson wrote:
> # lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
> 00:05.0 VGA compatible controller: NVIDIA Corporation C51G [GeForce 6100]
> (rev a2) (prog-if 00 [VGA controller])
That's a NV4C or NV4E (i.e. nv4x).
> I.e., no 18.1.1
# lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
00:05.0 VGA compatible controller: NVIDIA Corporation C51G [GeForce 6100] (rev
a2) (prog-if 00 [VGA controller])
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 16, NUMA node 0
Memory at fc00 (32-bit,
Are you on mesa 18.1.0 and using a nv3x/nv4x gpu? If so, update to
18.1.1. If not, provide more information.
The error is that nouveau_dri.so can't be loaded, which means you're
not getting acceleration. You can also make the error go away by
sticking LIBGL_ALWAYS_SOFTWARE=1 into your environment
Can't join the list confirming via email.
Will get:
gabe.freedesktop.org[131.252.210.177] said: 550 5.1.1
: Recipient address rejected: User
unknown in local recipient table (in reply to RCPT TO command)
Can only join via the http confirmation link.
glxgears, chromium etc. run fine.
The problems is these error messages,
$ glxinfo > /dev/null
libGL error: failed to create dri screen
libGL error: failed to load driver: nouveau
How can I make them go away?
I tried everything.
P.S., also /var/log/Xorg.0.log
[37.195] (EE) AIGLX error:
On Mon, Jun 11, 2018 at 11:32:53AM +0200, Nicolas Chauvet wrote:
> 2018-06-11 10:33 GMT+02:00 Thierry Reding :
> > On Sun, Jun 10, 2018 at 01:01:31PM +0200, Nicolas Chauvet wrote:
> >> This allows to have the related MODULE_FIRMWARE tag only
> >> on relevant arch (arm64).
> >> This will saves
2018-06-11 10:33 GMT+02:00 Thierry Reding :
> On Sun, Jun 10, 2018 at 01:01:31PM +0200, Nicolas Chauvet wrote:
>> This allows to have the related MODULE_FIRMWARE tag only
>> on relevant arch (arm64).
>> This will saves about 400k on initramfs when not relevant
>>
>> Signed-off-by: Nicolas Chauvet
On Sun, Jun 10, 2018 at 01:01:31PM +0200, Nicolas Chauvet wrote:
> This allows to have the related MODULE_FIRMWARE tag only
> on relevant arch (arm64).
> This will saves about 400k on initramfs when not relevant
>
> Signed-off-by: Nicolas Chauvet
> ---
>
