BTW, we never had any image for rpi2/rpi3 that was using the kernel-generic repo
Ok, the values are set in /etc/yum/vars.
[root@dc03 vars]# ll total 12 -rw-r--r--. 1 root root 6 Dec 5 2016 infra -rw-r--r--. 1 root root 8 Oct 31 10:00 kvariant -rw-r--r--. 1 root root 2 Sep 1 07:02 releasever
Seems that the "kvariant" was last modified end of october, probably by some update or other. I'ver reset it to 'rpi2' and hoping for the best.
On 04/12/17 12:20, Kristján Valur Jónsson wrote:
BTW, we never had any image for rpi2/rpi3 that was using the kernel-generic repoOk, the values are set in /etc/yum/vars.
[root@dc03 vars]# ll total 12 -rw-r--r--. 1 root root 6 Dec 5 2016 infra -rw-r--r--. 1 root root 8 Oct 31 10:00 kvariant -rw-r--r--. 1 root root 2 Sep 1 07:02 releasever
Seems that the "kvariant" was last modified end of october, probably by some update or other. I'ver reset it to 'rpi2' and hoping for the best.
Yes, it's coming from centos-userland-release : rpm -q --scripts centos-userland-release : postinstall scriptlet (using /bin/sh): # Detecting if rpi or generic kernel egrep -q 'BCM2709|BCM2710' /proc/cpuinfo && echo rpi2
/etc/yum/vars/kvariant || echo generic >/etc/yum/vars/kvariant
So normally it's detected correctly and so put the correct rpi2 value for kvariant when installed on a rpi2/rpi3
On 4 December 2017 at 11:51, Fabian Arrotin arrfab@centos.org wrote:
Yes, it's coming from centos-userland-release : rpm -q --scripts centos-userland-release : postinstall scriptlet (using /bin/sh): # Detecting if rpi or generic kernel egrep -q 'BCM2709|BCM2710' /proc/cpuinfo && echo rpi2
/etc/yum/vars/kvariant || echo generic >/etc/yum/vars/kvariant
So normally it's detected correctly and so put the correct rpi2 value for kvariant when installed on a rpi2/rpi3
Funny, my device reports BCM2835. (which indicates that it isn't RPI3 at all). I'm sure they are all in the BCM28xx range, see https://en.wikipedia.org/wiki/Raspberry_Pi also, difference between BCM27xx and BCM28xx: https://raspberrypi.stackexchange.com/questions/840/why-is-the-cpu-sometimes...
On 04/12/17 13:21, Kristján Valur Jónsson wrote:
On 4 December 2017 at 11:51, Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org> wrote:
Yes, it's coming from centos-userland-release : rpm -q --scripts centos-userland-release : postinstall scriptlet (using /bin/sh): # Detecting if rpi or generic kernel egrep -q 'BCM2709|BCM2710' /proc/cpuinfo && echo rpi2 >/etc/yum/vars/kvariant || echo generic >/etc/yum/vars/kvariant So normally it's detected correctly and so put the correct rpi2 value for kvariant when installed on a rpi2/rpi3Funny, my device reports BCM2835. (which indicates that it isn't RPI3 at all). I'm sure they are all in the BCM28xx range, see https://en.wikipedia.org/wiki/Raspberry_Pi also, difference between BCM27xx and BCM28xx: https://raspberrypi.stackexchange.com/questions/840/why-is-the-cpu-sometimes...
-- Kv, Kristján Valur Jónsson, RVX
hmm, interesting ... so you mean that with the raspberrypi2 kernel installed, it was still detecting the rpi3 as BCM2835 ? It wasn't on mine, but if some people confirm that behaviour, we can probably adapt the rpm postinstall scriptlet that way too
Fabian,
This is the output I get in my Raspberry Pi v3:
[root@rpi3 ~]# uname -a Linux rpi3 4.9.50-v7.1.el7 #1 SMP Thu Sep 14 08:17:16 UTC 2017 armv7l armv7l armv7l GNU/Linux
[root@rpi3 ~]# cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 1 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 2 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 3 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
Hardware : BCM2835 Revision : a02082 Serial : 00000000fa9d86a7
I hope that helps. Regards.
On 12/05/2017 07:34 AM, Fabian Arrotin wrote:
On 04/12/17 13:21, Kristján Valur Jónsson wrote:
hmm, interesting ... so you mean that with the raspberrypi2 kernel installed, it was still detecting the rpi3 as BCM2835 ? It wasn't on mine, but if some people confirm that behaviour, we can probably adapt the rpm postinstall scriptlet that way too
On 05/12/17 11:13, Jordi Sanfeliu wrote:
Fabian,
This is the output I get in my Raspberry Pi v3:
[root@rpi3 ~]# uname -a Linux rpi3 4.9.50-v7.1.el7 #1 SMP Thu Sep 14 08:17:16 UTC 2017 armv7l armv7l armv7l GNU/Linux
[root@rpi3 ~]# cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 1 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 2 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 3 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
Hardware : BCM2835 Revision : a02082 Serial : 00000000fa9d86a7
I hope that helps. Regards.
On 12/05/2017 07:34 AM, Fabian Arrotin wrote:
On 04/12/17 13:21, Kristján Valur Jónsson wrote:
hmm, interesting ... so you mean that with the raspberrypi2 kernel installed, it was still detecting the rpi3 as BCM2835 ? It wasn't on mine, but if some people confirm that behaviour, we can probably adapt the rpm postinstall scriptlet that way too
So I booted my rpi3 and confirm that . It seems that we 4.9.x kernels /proc/cpuinfo reports BCM2835 so I'll have to modify the .spec for centos-userland-release to also check for that string and the correctly set the 'kvariant' yum var
So, I made the change to "kvariant", and installed the kernel, but something broke and I had to manually restore the /boot partition with files from another Pi. If anyone needs to fix his install, I recommend to yum reinstall raspberrypi2-kernel-firmware raspberrypi2-firmware and yum reinstall raspberrypi2-kernel-4.9.64
Another thing I noticed is that the config.txt supplied by the CenOS distro sets arm_freq=700 This is disasterous if you are running an RPI3 :) Here is the setup I'm using for my little RPI3 Samba Domain controllers: ---
hdmi_safe=1
#overclock rpi3 moderately #https://github.com/retropie/retropie-setup/wiki/Overclocking total_mem=1024 arm_freq=1300 gpu_freq=500 core_freq=500 sdram_freq=500 sdram_schmoo=0x02000020 over_voltage=2 sdram_over_voltage=2
#minimum video ram gpu_mem=16
#disable wifi and bluetooth dtoverlay=pi3-disable-wifi dtoverlay=pi3-disable-bt
#fast sd card, only for UHS cards #(may prevent booting, have tools on hand to revert this) #dtparam=sd_overclock=100 #boot_delay=2
Hi Kristján,
Tuesday, December 5, 2017, 4:05:15 PM, you wrote:
KVJ> Another thing I noticed is that the config.txt supplied by the CenOS distro sets KVJ> arm_freq=700 KVJ> This is disasterous if you are running an RPI3 :) Here is the KVJ> setup I'm using for my little RPI3 Samba Domain controllers:
could you please elaborate on the arm_freq issue?
best regards --- Michael Schumacher
On 7 December 2017 at 15:22, Michael Schumacher <michael.schumacher@pamas.de
wrote:
Hi Kristján,
Tuesday, December 5, 2017, 4:05:15 PM, you wrote:
KVJ> Another thing I noticed is that the config.txt supplied by the CenOS distro sets KVJ> arm_freq=700 KVJ> This is disasterous if you are running an RPI3 :) Here is the KVJ> setup I'm using for my little RPI3 Samba Domain controllers:
could you please elaborate on the arm_freq issue?
Sure. This setting controls the maximum kernel frequency that the governor will use. However, it overrides the default, which for RPi3 is 1200MHz. In effect, it is throttling the RPi3 to have the same maximum cpu frequency as a RPi1. See https://github.com/retropie/retropie-setup/wiki/Overclocking for details on the settings. It is best to leave the config.txt as bare as possible, only overriding system defaults if there is a reason to.
On 07/12/17 16:49, Kristján Valur Jónsson wrote:
On 7 December 2017 at 15:22, Michael Schumacher <michael.schumacher@pamas.de mailto:michael.schumacher@pamas.de> wrote:
Hi Kristján, Tuesday, December 5, 2017, 4:05:15 PM, you wrote: KVJ> Another thing I noticed is that the config.txt supplied by the CenOS distro sets KVJ> arm_freq=700 KVJ> This is disasterous if you are running an RPI3 :) Here is the KVJ> setup I'm using for my little RPI3 Samba Domain controllers: could you please elaborate on the arm_freq issue?Sure. This setting controls the maximum kernel frequency that the governor will use. However, it overrides the default, which for RPi3 is 1200MHz. In effect, it is throttling the RPi3 to have the same maximum cpu frequency as a RPi1. See https://github.com/retropie/retropie-setup/wiki/Overclocking for details on the settings. It is best to leave the config.txt as bare as possible, only overriding system defaults if there is a reason to.
Thanks for the pointer. When I built the rpi3 image, I used the existing rpi2 image we had, including the config.txt that was used.
From that wiki page, it seems that we're really under what both the pi2/p3 can support, including default values. Maybe we should at least bump this to "default" values (so not overclocking). So arm_freq set to 900 for pi2 and 1200 for pi3
Opinions ?
On 8 December 2017 at 12:36, Fabian Arrotin arrfab@centos.org wrote:
Thanks for the pointer. When I built the rpi3 image, I used the existing rpi2 image we had, including the config.txt that was used.
From that wiki page, it seems that we're really under what both the pi2/p3 can support, including default values. Maybe we should at least bump this to "default" values (so not overclocking). So arm_freq set to 900 for pi2 and 1200 for pi3
Opinions ?
In my opinion, we shuold just leave the arm_freq unset. The kernel will
choose the correct default. The hdmi settings are fine.
You could also replace it with the default from the raspbian distro: https://raw.githubusercontent.com/RPi-Distro/pi-gen/dev/stage1/00-boot-files...
-
Fabian Arrotin -
Jordi Sanfeliu -
Kristján Valur Jónsson -
Michael Schumacher