Mesa isn't update to date

  • Done
  • quality assurance status badge
Details
6 participants
  • Barnabás Béres
  • Guillaume Le Vaillant
  • Marius Bakke
  • Maxim Cournoyer
  • Tobias Geerinckx-Rice
  • romulasry
Owner
unassigned
Submitted by
romulasry
Severity
normal
R
R
romulasry wrote on 10 Nov 2020 21:29
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
QpwETrJLfWziZlJJfdKWGAnruuuG48XBStA8ALALV27dXmhYxgS5T1zzmNmd_fDs5ago8HGDCT68cfzLHnXTCYUqukPDJw-RDXBeBEGjM4I=@protonmail.com
Mesa 20.2.2 is released

November 6, 2020


Also it would be nice to see it built with lllvm 11

Sent with [ProtonMail](https://protonmail.com) Secure Email.
Attachment: file
B
B
Barnabás Béres wrote on 11 Nov 2020 12:40
(address . 44558@debbugs.gnu.org)
CAOcmTtcMwk85h+ftZsVp=X6hERtXXdvrhuhBDV-kRMfAu=QnVw@mail.gmail.com
Hi,
I think this email went to the wrong place, because you only sent a "bug
report" not a patch. I think it's better to send these kind of things to
bug-guix@gnu.org

Best regards,
Barnabas Beres
Attachment: file
T
T
Tobias Geerinckx-Rice wrote on 11 Nov 2020 13:24
(address . 44558@debbugs.gnu.org)
87k0ushyi7.fsf@nckx
Hullo!

Barnabás Béres ???
Toggle quote (6 lines)
> I think this email went to the wrong place, because you only
> sent a "bug
> report" not a patch. I think it's better to send these kind of
> things to
> bug-guix@gnu.org

Does your mail client mark it as a patch? Strange. I've deleted
the original, but bug-guix@ delivered the list copy to my inbox
and I don't see ‘patches’ in the header.

That said, it's not really a bug report either, or the bug is
missing...

Romulasry, are you suffering from specific Mesa 20.0.7 problems
that 20.2.2 might fix? Please let us know. An otherwise working
package not being at the latest upstream version isn't a bug.

romulasry via Bug reports for GNU Guix ???
Toggle quote (2 lines)
> Mesa 20.2.2 is released

The core-updates branch updates Mesa to 20.1.9. Would you like to
submit a (tested) core-updates patch updating it to 20.2.2?

Toggle quote (2 lines)
> Also it would be nice to see it built with lllvm 11

Same for this! All help is appreciated.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX6vYEA0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW150dEBAIG6EHKR/axJFhjwN5H/JDtRIodN71N34lBMVAP9
0oASAP9R64pYVNfS4Oexq95KEcq+SvajdtkKLpBW9irVWugrAw==
=J0Vt
-----END PGP SIGNATURE-----

B
B
Barnabás Béres wrote on 11 Nov 2020 14:08
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
CAOcmTtdUCj5H3jWQ6cAXoRjVXaQtcUTNLFPHGrAMHWTK0LBcOw@mail.gmail.com
Yes it marked as a patch

Tobias Geerinckx-Rice <me@tobias.gr> ezt írta (id?pont: 2020. nov. 11.,
Sze, 13:24):

Toggle quote (36 lines)
> Hullo!
>
> Barnabás Béres ???
> > I think this email went to the wrong place, because you only
> > sent a "bug
> > report" not a patch. I think it's better to send these kind of
> > things to
> > bug-guix@gnu.org
>
> Does your mail client mark it as a patch? Strange. I've deleted
> the original, but bug-guix@ delivered the list copy to my inbox
> and I don't see ‘patches’ in the header.
>
> That said, it's not really a bug report either, or the bug is
> missing...
>
> Romulasry, are you suffering from specific Mesa 20.0.7 problems
> that 20.2.2 might fix? Please let us know. An otherwise working
> package not being at the latest upstream version isn't a bug.
>
> romulasry via Bug reports for GNU Guix ???
> > Mesa 20.2.2 is released
>
> The core-updates branch updates Mesa to 20.1.9. Would you like to
> submit a (tested) core-updates patch updating it to 20.2.2?
>
> > Also it would be nice to see it built with lllvm 11
>
> Same for this! All help is appreciated.
>
> Kind regards,
>
> T G-R
>


--
Barnus
Attachment: file
T
T
Tobias Geerinckx-Rice wrote on 11 Nov 2020 14:25
(name . Barnabás Béres)(address . beresbarnus03@gmail.com)(address . 44558@debbugs.gnu.org)
87h7pwhvp1.fsf@nckx
Barnabás Béres ???
Toggle quote (2 lines)
> Yes it marked as a patch

Thanks for letting me know. That shouldn't happen, but I can't
say more without knowing more about your MUA and veering
off-topic.

I can say only that it was sent to bug-guix[0], not
guix-patches[0], and never had [PATCH] in the topic. Both Web
interfaces and emacs-debbugs agree.

A mystery,

T G-R

[0]:
[1]:
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX6vmSg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15ijkBAMeYKPaQT0YmHqfNCaviXU7TJqXuUAvzIjd4mqvZ
CPdEAQC0qKh5AhWXTigztmYq7CKxoXfaQlahS493UknO7Vq8AQ==
=2JmK
-----END PGP SIGNATURE-----

B
B
Barnabás Béres wrote on 11 Nov 2020 14:55
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)(address . 44558@debbugs.gnu.org)
CAOcmTtcc6rcSe6gxzvmcc=MGWpaEXx6MUckcAKHYevn18YBMTQ@mail.gmail.com
Thanks for the feedback!

Tobias Geerinckx-Rice <me@tobias.gr> ezt írta (id?pont: 2020. nov. 11.,
Sze, 14:25):

Toggle quote (21 lines)
> Barnabás Béres ???
> > Yes it marked as a patch
>
> Thanks for letting me know. That shouldn't happen, but I can't
> say more without knowing more about your MUA and veering
> off-topic.
>
> I can say only that it was sent to bug-guix[0], not
> guix-patches[0], and never had [PATCH] in the topic. Both Web
> interfaces and emacs-debbugs agree.
>
> A mystery,
>
> T G-R
>
> [0]:
> https://lists.gnu.org/archive/html/bug-guix/2020-11/threads.html
> [1]:
> https://lists.gnu.org/archive/html/guix-patches/2020-11/threads.html
>

Best Regards,
Barnabas Beres
Attachment: file
G
G
Guillaume Le Vaillant wrote on 12 Nov 2020 17:26
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
87361eilrv.fsf@yamatai
Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:

Toggle quote (10 lines)
> Romulasry, are you suffering from specific Mesa 20.0.7 problems that 20.2.2
> might fix? Please let us know. An otherwise working package not being at the
> latest upstream version isn't a bug.
>
> romulasry via Bug reports for GNU Guix ???
>> Mesa 20.2.2 is released
>
> The core-updates branch updates Mesa to 20.1.9. Would you like to submit
> a (tested) core-updates patch updating it to 20.2.2?

Hi,

Mesa 20.2 brings direct OpenGL rendering support for Nvidia RTX 20xx
graphic cards with the nouveau driver, whereas with our current version
these cards have to use LLVMpipe.
I tested the update quickly on my local staging branch using glxgears
and vlc, and it worked fine. When reading a video the CPU usage dropped
from 30% to 2%, which is nice.
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCX61iRA8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9azQEAjGFAVfc8NnF5naRov1jrP2PoGsCtJOcWQ9la
RFmClHQBAItAYIURaQTWzGdARcr9eNSHioIEYtBrkcVf2onvBgv2
=ueWc
-----END PGP SIGNATURE-----

M
M
Marius Bakke wrote on 12 Nov 2020 22:27
87wnyqb706.fsf@gnu.org
Guillaume Le Vaillant <glv@posteo.net> writes:

Toggle quote (21 lines)
> Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:
>
>> Romulasry, are you suffering from specific Mesa 20.0.7 problems that 20.2.2
>> might fix? Please let us know. An otherwise working package not being at the
>> latest upstream version isn't a bug.
>>
>> romulasry via Bug reports for GNU Guix ???
>>> Mesa 20.2.2 is released
>>
>> The core-updates branch updates Mesa to 20.1.9. Would you like to submit
>> a (tested) core-updates patch updating it to 20.2.2?
>
> Hi,
>
> Mesa 20.2 brings direct OpenGL rendering support for Nvidia RTX 20xx
> graphic cards with the nouveau driver, whereas with our current version
> these cards have to use LLVMpipe.
> I tested the update quickly on my local staging branch using glxgears
> and vlc, and it worked fine. When reading a video the CPU usage dropped
> from 30% to 2%, which is nice.

That is great news.

The current 'staging' branch is just about ready for merge[*], so a Mesa
update will have to wait until the next round.

However, I think libGL is fairly ABI-stable, so you may be able to
"graft" this version in the mean time, like in commit
fdd883509301845ddb4dc90e70e58b469afb5441.

[*] gst-plugins-good fails on armhf and i686, not sure what to do about
-----BEGIN PGP SIGNATURE-----

iQFDBAEBCgAtFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl+tqMoPHG1hcml1c0Bn
bnUub3JnAAoJEKKgbfKjOlT6aeEIAMT6lLZLoFjCc64JcdCVLlhg3Awx+X7Ute57
fKEL7BrtbwsTw6S6TE7mVpm7/pRzwCQTbAzZoYOFXgOuyRqQK6kUOHnrtemevG4P
4TBEnz4gXrjTF3IQD9bKs9Wm9/TsK5KhQ6lb+v3qWvQbP3QB9tWTa3x17KwTkCzO
aVHJT8ZbOV7SwONF9HUGaJb9or2j614meBAEx+UdMujHLsBxdYxMzcTY/xmm1qbZ
NWEbBnI0I4ua/8LNaJHd3+WD1PRDKrnSosTu2ybYYSCsNBCLFl9itHKvaveIt6e0
M0F3sLc3jkZLG0VuZY3/Wv+mHC6vIh8JHCbWYfSUPGbkymxVrEw=
=VckC
-----END PGP SIGNATURE-----

G
G
Guillaume Le Vaillant wrote on 13 Nov 2020 14:56
(name . Marius Bakke)(address . marius@gnu.org)
87pn4h8imz.fsf@yamatai
Marius Bakke <marius@gnu.org> skribis:

Toggle quote (35 lines)
> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:
>>
>>> Romulasry, are you suffering from specific Mesa 20.0.7 problems that 20.2.2
>>> might fix? Please let us know. An otherwise working package not being at the
>>> latest upstream version isn't a bug.
>>>
>>> romulasry via Bug reports for GNU Guix ???
>>>> Mesa 20.2.2 is released
>>>
>>> The core-updates branch updates Mesa to 20.1.9. Would you like to submit
>>> a (tested) core-updates patch updating it to 20.2.2?
>>
>> Hi,
>>
>> Mesa 20.2 brings direct OpenGL rendering support for Nvidia RTX 20xx
>> graphic cards with the nouveau driver, whereas with our current version
>> these cards have to use LLVMpipe.
>> I tested the update quickly on my local staging branch using glxgears
>> and vlc, and it worked fine. When reading a video the CPU usage dropped
>> from 30% to 2%, which is nice.
>
> That is great news.
>
> The current 'staging' branch is just about ready for merge[*], so a Mesa
> update will have to wait until the next round.
>
> However, I think libGL is fairly ABI-stable, so you may be able to
> "graft" this version in the mean time, like in commit
> fdd883509301845ddb4dc90e70e58b469afb5441.
>
> [*] gst-plugins-good fails on armhf and i686, not sure what to do about
> it yet: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/803

I'll try this grafting trick, thanks for the pointer.

I saw that issue 803 of gst-plugin-good has been closed with patch
2ce5909f; are there other things blocking the merge of the 'staging'
branch into 'master'?
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCX66QpA8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j+/AAD/UlLhCM3igPcgao7v7VeqDPgfXBckiQV6iEH+
bfODlxgBAIGSyodAXHVkpuGkvI9kXiPZ/7KEVu/Gp71OJUaJ0mPT
=EKH7
-----END PGP SIGNATURE-----

M
M
Marius Bakke wrote on 13 Nov 2020 16:49
(name . Guillaume Le Vaillant)(address . glv@posteo.net)
87lff5b6km.fsf@gnu.org
Guillaume Le Vaillant <glv@posteo.net> writes:

Toggle quote (4 lines)
> I saw that issue 803 of gst-plugin-good has been closed with patch
> 2ce5909f; are there other things blocking the merge of the 'staging'
> branch into 'master'?

Now 'gst-plugins-bad' fails on i686:


There are not a lot of packages depending on it, so maybe it can be
ignored. However 'gnome' is one of the affected packages (through
'cheese').

Other than these I don't know any serious regressions, but it's hard to
tell because Cuirass has not been very cooperative:

-----BEGIN PGP SIGNATURE-----

iQFDBAEBCgAtFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl+uqvoPHG1hcml1c0Bn
bnUub3JnAAoJEKKgbfKjOlT6J8QH/jmZVEpmsph819nTLnWPWharpu/40c3vAL6z
oKN0WKfDDqOmLn/G8KcXt1xNp7vn3Jl/yAkKHXx/RJc8a8e74k6qZh9xxNbwrMsU
v1kffUa8oT+XRulNqtQxobeIZAyCAS37ubg6ytFKAIxysele2Vvb7crAMbmCRzbR
EZw1pMtC3jG2vpvkGeyDnPNq/1lyEnSqTUq0r4HI0/AStqzs96InK/VI89ATH6Fy
ldeSnTSXmG+uuhdc9CQvZYHhyXI/y1U4o5cNz3NcP53NQIlu7enLcSIcZuvCpPBM
/OzVSuTDksDzS/0oCIsUmgB4xkuFnl+yqgyP4OpfB3cl3+sFcDg=
=jJg9
-----END PGP SIGNATURE-----

M
M
Maxim Cournoyer wrote on 14 Nov 2021 02:26
(name . Marius Bakke)(address . marius@gnu.org)
87czn3il39.fsf@gmail.com
Hello,

Marius Bakke <marius@gnu.org> writes:

Toggle quote (19 lines)
> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> I saw that issue 803 of gst-plugin-good has been closed with patch
>> 2ce5909f; are there other things blocking the merge of the 'staging'
>> branch into 'master'?
>
> Now 'gst-plugins-bad' fails on i686:
>
> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1463
>
> There are not a lot of packages depending on it, so maybe it can be
> ignored. However 'gnome' is one of the affected packages (through
> 'cheese').
>
> Other than these I don't know any serious regressions, but it's hard to
> tell because Cuirass has not been very cooperative:
>
> https://ci.guix.gnu.org/jobset/staging-staging

The soon to be merged core-updates-frozen has a recent mesa (21.2.4).

Closing.

Thanks for the report!

Maxim
Closed
?