CPU core is only recognized one

[kometchtech]

Hello,

In the following environments of Cubietruck, a problem which the CPU core is not recognized only one has occurred.
 

$ hostnamectl 
   Static hostname: dns02.kometch.local
         Icon name: computer
           Chassis: n/a
        Machine ID: 609e2bf4c5884368b36018d67982759e
           Boot ID: 4faccf729c4042fc87013cb82494b486
  Operating System: Debian GNU/Linux 8 (jessie)
            Kernel: Linux 4.1.6-sunxi
      Architecture: arm

$ cat /proc/cpuinfo 
processor       : 0
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 16.42
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc07
CPU revision    : 4

Hardware        : Allwinner sun7i (A20) Family
Revision        : 0000
Serial          : 0000000000000000

Is this Will known issues?

Best regards.

[kometchtech]

kernel related packages as follows.

~$ dpkg -l | grep linux-
ii  linux-dtb-next-sunxi              4.3                       armhf        Linux DTB, version 4.2.0-sunxi
ii  linux-firmware-image-next-sunxi   4.3                       armhf        Linux kernel firmware, version 4.2.0-sunxi
ii  linux-headers-next-sunxi          4.3                       armhf        Linux kernel headers for 4.2.0-sunxi on armhf
rc  linux-image-4.1.2-cubietruck      4.0                       armhf        Linux kernel, version 4.1.2-cubietruck
rc  linux-image-next-cubietruck       4.1                       armhf        Linux kernel, version 4.1.4-cubietruck
ii  linux-image-next-sunxi            4.3                       armhf        Linux kernel, version 4.2.0-sunxi
ii  linux-jessie-root-next-cubietruck 4.3                       armhf        Various root file system tweaks for ARM boards
ii  linux-libc-dev:armhf              3.16.7-ckt11-1+deb8u3     armhf        Linux support headers for userspace development
ii  linux-u-boot-cubietruck           4.3                       armhf        Uboot loader 2015.07.

[Igor]

remove 

linux-u-boot-cubietruck 

 

linux-image-4.1.2-cubietruck 

linux-image-next-cubietruck 

 

 

and install linux-u-boot-cubietruck-next

 

reboot and you'll be fine.

[kometchtech]

Advice Thank you.

CPU is I now two visible.

$ cat /proc/cpuinfo 
processor       : 0
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 27.78
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc07
CPU revision    : 4

processor       : 1
model name      : ARMv7 Processor rev 4 (v7l)
BogoMIPS        : 27.78
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc07
CPU revision    : 4

Hardware        : Allwinner sun7i (A20) Family
Revision        : 0000
Serial          : 1651664104825a69

[kometchtech]

Armbian_4.4_Cubietruck_Debian_jessie_3.4.109 also are experiencing the same symptoms.

How do I how to solve this case?

kometch@dns02:~$ cat /proc/cpuinfo 

Processor       : ARMv7 Processor rev 4 (v7l)

processor       : 0

BogoMIPS        : 957.05


processor       : 1

BogoMIPS        : 830.00


Features        : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt 

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x0

CPU part        : 0xc07

CPU revision    : 4


Hardware        : sun7i

Revision        : 0000

Serial          : 1651664104825a69

Chipid          : 16516641-80485072-56544848-04825a69

[Igor]

For kernel 3.4.10x you need to update boot loader not containing "next" in the name.

apt-get install  linux-u-boot-cubietruck

[bombobrudi]

I had the same problem, but now with version 4.5 with kernel 4.2.3 the problem is gone.

[luca219]

i had the same problem,

 

Linux cubietruck 3.4.104-sunxi #1 SMP PREEMPT Fri Oct 17 16:13:30 CEST 2014 armv7l GNU/Linux

[root@hosts]# apt-get install  linux-u-boot-cubietruck

Reading package lists... Done

Building dependency tree

Reading state information... Done

E: Unable to locate package linux-u-boot-cubietruck

 

Processor       : ARMv7 Processor rev 4 (v7l)

processor       : 0

BogoMIPS        : 956.47

 

processor       : 1

BogoMIPS        : 832.55

 

Features        : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt

CPU implementer : 0x41

CPU architecture: 7

CPU variant     : 0x0

CPU part        : 0xc07

CPU revision    : 4

 

Hardware        : sun7i

Revision        : 0000

Serial          : 0000000000000000

Chipid          : 1651660d-80485686-52574848-078114f4

[luca219]

I found this is correct?

 

 

apt-cache search u-boot*

dfu-util - Device firmware update (DFU 1.0) USB programmer

u-boot - A boot loader for embedded systems

u-boot-tools - companion tools for Das U-Boot bootloader

uboot-envtools - read/modify the environment for the U-Boot boot loader (transitional package)

uboot-mkimage - generate kernel image for U-Boot (transitional package)

x-loader-omap3-beagle - Board initialization helper for TI OMAP 3 Beagle boards

x-loader-omap3-igepv2 - Board initialization helper for IGEP v2 and v3 boards

x-loader-omap3-overo - Board initialization helper for Gumstix Overo boards

x-loader-omap4-panda - Board initialization helper for TI OMAP 4 Panda boards

[Igor]

nope, wrong. read documentation regarding kernel upgrade, you have older image so you need to add repository first.

 

More info:

http://www.armbian.com/kernel/

[luca219]

sorry Igor, I do not want to waste your time.

i have add repo

echo "deb http://apt.armbian.com $(lsb_release -cs) main" > /etc/apt/sources.list.d/armbian.list
apt-key adv --keyserver keys.gnupg.net --recv-keys 0x93D6889F9F0E78D5
apt-get update

and install

apt-get install  linux-u-boot-cubietruck

after reboot I do not understand what happened

 

any suggestion?

 

solved sorry

[Rui Ribeiro]

This thread is showing a problem I have seen in ARM....what is exactly the cause in the first instance for the Serial to be 000000?

[tkaiser]

This thread is showing a problem I have seen in ARM....what is exactly the cause in the first instance for the Serial to be 000000?

 

With Allwinner SoCs the SID is used to create a serial number from. And obviously with some kernels this fails.

 

When you have the most recent sunxi-tools installed you can read out the SID this way too.

[Rui Ribeiro]

Thanks kaiser. I got lost in that sunxi link. It talks it can be used as a serial for the device, and then talks about known values? So it is a unique number, or not?

[tkaiser]

Thanks kaiser. I got lost in that sunxi link. It talks it can be used as a serial for the device, and then talks about known values? So it is a unique number, or not?

 

The SID is unique but has to be readout differently on different SoCs. And sometimes drivers seem to fail (see the list with zeroed SIDs in linux-sunxi wiki)