-
Notifications
You must be signed in to change notification settings - Fork 5.2k
4.9 | /proc/cpuinfo always shows Hardware = BCM2835 #2008
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is an unintended but unavoidable consequence of using less downstream, Pi-specific code in newer kernels. I suggest you use /proc/device-tree/model (human readable) or extract the information you need from the Revision field of /proc/cpuinfo. There is a bit in the revision number indicating that it's in the new format: if it's set then the CPU type is in another group of bits, otherwise it must be a 2708. |
Thanks for the info 👍 I've made the switch to using revision codes for board detection: I'll mark as closed, [dupe] of raspberrypi/firmware#705 |
popcornmix |
Uh oh!
There was an error while loading. Please reload this page.
As title, in
4.9.27
,/proc/cpuinfo
always showsBCM2835
forHardware
info. Confirmed with:In
4.4.50
BCM2709
(incorrect?https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2836/README.md https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2837/README.md)BCM2708
(incorrect? https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2835/README.md)This is an issue for us, as we use the that information to determine which RPi is actually running, and, how we optimize for those devices (minus cpu core detection
$(nproc --all)
for software installs such as php-fpm thread count).https://github.com/Fourdee/DietPi/issues/936#issuecomment-301055299
Any chance we could see a possible fix for correct
Hardware
information, reported in/proc/cpuinfo
?Revision codes do seem to be correct in
4.9.27
: https://github.com/Fourdee/DietPi/blob/master/dietpi/misc/rpi_boardinfoThe text was updated successfully, but these errors were encountered: