CentOS - Jun 2017 - test builds on private server updates (kernel)

Hallo Hughes,

thanks to let me know. It is good that you have a focus on LTS 4.9.
 
Unfortunately it is so that the new graphics cards from amd to today are not
served in the opensource.
That's why I'm experimenting with the latest stable versions and what is
so.

My laptop has done the linux-firmware update well, it is nevertheless one of the
newest.

The kernel and appropriate firmware is unfortunately only the one side of a
driver when it comes to graphics cards.

The hardware decoding works only sometimes. On CentOS in the moment not (Radeon
/ Intel),
but that is not synonymous the focus of a server system. This happens to me also
with the
original packages.

I give my homework free in the thought that it might help somebody out there.

Sincerely

Andy

Am Samstag, den 10.06.2017, 05:52 -0500 schrieb Johnny
Hughes:
> On 06/10/2017 05:17 AM, Andreas Benzler wrote:
> > Hello Everyone,
> > 
> > 
> > Because my tests on AMD and Intel, I had to update the linux firmware.
> > Update comes from the upstream fedora packet and also works on centos
with new kernel.
> > 
> > linux-firmware-20170605-74.git37857004.el7.centos.noarch
> > 
> 
> If people want an experimental kernel and linux-firmware that lives in
> the centos namespace, we have this:
> 
> 
> http://mirror.centos.org/altarch/7/experimental/
> 
> There are i386 and x86_64 kernels there.
> 
> Currently we are tracking the 4.9 LTS kernel branch and the fedora
> linux-firmware mentioned above.
> 
> This is also the kernel that we use in the armhfp (32 bit Arm) SIG.
> 
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos

On 06/10/2017 08:47 AM, Andreas Benzler wrote:
> Hallo Hughes,
> 
> thanks to let me know. It is good that you have a focus on LTS 4.9.
>  
> Unfortunately it is so that the new graphics cards from amd to today are
not served in the opensource.
> That's why I'm experimenting with the latest stable versions and
what is so.
> 
> My laptop has done the linux-firmware update well, it is nevertheless one
of the newest.
> 
> The kernel and appropriate firmware is unfortunately only the one side of a
driver when it comes to graphics cards.
> 
> The hardware decoding works only sometimes. On CentOS in the moment not
(Radeon / Intel),
> but that is not synonymous the focus of a server system. This happens to me
also with the
> original packages.
> 
> I give my homework free in the thought that it might help somebody out
there.
> 

No problem at all, and thanks for posting.  It might indeed help others.

If you take a look at the git repo for the linux-firmware, you can see
the actions that make that installable on both CentOS-7 and also for
CentOS-6 in the xen kernel tree (a couple of obsoletes and some other
minor changes).

https://git.centos.org/summary/sig-altarch!linux-firmware.git

Keep up the good work.

> Am Samstag, den 10.06.2017, 05:52 -0500 schrieb Johnny Hughes:
>> On 06/10/2017 05:17 AM, Andreas Benzler wrote:
>>> Hello Everyone,
>>>
>>>
>>> Because my tests on AMD and Intel, I had to update the linux
firmware.
>>> Update comes from the upstream fedora packet and also works on
centos with new kernel.
>>>
>>> linux-firmware-20170605-74.git37857004.el7.centos.noarch
>>>
>>
>> If people want an experimental kernel and linux-firmware that lives in
>> the centos namespace, we have this:
>>
>>
>> http://mirror.centos.org/altarch/7/experimental/
>>
>> There are i386 and x86_64 kernels there.
>>
>> Currently we are tracking the 4.9 LTS kernel branch and the fedora
>> linux-firmware mentioned above.
>>
>> This is also the kernel that we use in the armhfp (32 bit Arm) SIG.
>>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20170610/b8ff9373/attachment-0001.sig>

Sorry Hughes,

got some questions. 

I have the feeling that I do a lot wrong. Today I sent a mailing post
at fedora where it is also about btrfs under fedora.

In time when i write the mail i forward it my patch for fedora 25
pretransaction & snapper.yp, with the hope of feedback.

https://lists.fedoraproject.org/archives/list/devel at lists.fedoraproject
.org/thread/NLFYHW3IEJHSFBUOEAVHDHBVTL7TOHYZ/

Sometimes I don't know where to push the information.

on https://copr.fedorainfracloud.org/coprs/andybe/CentOS7Python34/

I release a ticket because snapper gui do not build on there repo.
Local with mock or without it never fails. No response.

Since yesterday learned how to use snapper against the dbus api. What
is the better way in my opinion. After some rest i will do it first on
centos and it back into fedora "dnf" later on.

It looks to me as if in a Fedora release little movement. If someone
wants to upgrade something you simply move it there gladly times on the
next release. This generates a high unwilling something at all a
working release to submit an improvement. This is a lot better under
Centos, although Redhat is very slow with its update cycles.

Too bad the feedback is not as good as under Centos.

In principal there are to many ways to push errors or improvments on
each (centos, redhat, fedora) distros.

Or am I doing something wrong. Is there anything I can do better?

It is hopefully not that I care 3 various Linux (This time
Arch/Manjaro, Fedora, Centos). It helps to get ideas.

Thanks for advice.

Sincerely

Andy