This isn't a CPU shortage problem, an A20 has plenty of CPU to run Gnome, KDE or any other window manager; you must be having another problem that merely manifest as a process eating all the CPU. What process(es) are consuming all the CPU? Are any logs being flooded with a repeating error message? Gordan On 02/09/15 20:45, Robert Moskowitz wrote: > After 17 min, the gnome login screen came up and I did the login. Now > waiting for the desktop... > > config portion came up after 22 min.... > > 25 min and I am looking at the Gnome desktop. Oh boy. And from the > serial console: > > [ 1163.786222] Bluetooth: Core ver 2.20 > [ 1163.790175] NET: Registered protocol family 31 > [ 1163.794729] Bluetooth: HCI device and connection manager initialized > [ 1163.807801] Bluetooth: HCI socket layer initialized > [ 1163.812808] Bluetooth: L2CAP socket layer initialized > [ 1163.818119] Bluetooth: SCO socket layer initialized > [ 1163.848426] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 1163.853809] Bluetooth: BNEP filters: protocol multicast > [ 1163.861845] Bluetooth: BNEP socket layer initialized > > There is no bluetooth on a C2... > > > # free > total used free shared buff/cache > available > Mem: 1018036 282404 244260 20400 491372 688444 > Swap: 1048572 0 1048572 > > I am changing to: > > systemctl set-default multi-user.target > > then i will install vncserver. > > On 09/02/2015 03:33 PM, Robert Moskowitz wrote: >> So on my Cubieboard2 image I did >> >> yum groupinstall "GNOME Desktop" >> >> After some 800+ packages installed I rebooted. >> >> serial console is working and I am logged into it. >> >> But the monitor is showing just a grey screen with a mouse. No login. >> >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev at centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev >> > > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > https://lists.centos.org/mailman/listinfo/arm-dev