After the – partial – success with the 96Boards Hikey, I tried the Qualcomm Dragonboard 410c, but the June 29 Linux-Next failed to boot successfully, with only one CPU initialising, and MMC errors, and eventual hang…. ……………………….. psci: failed to boot CPU1 (-95) CPU1: failed to boot: -95 CPU1: failed in unknown state : 0x0 psci: failed … Continue reading →
A problem that still plagued the 3.18-rc series of kernel releases now seems to affect 3.17 as well.. I have had two complete system hangs with 3.17.3 and 3.17.4 on my main system in the last two weeks, and thought at first that these were caused by KDE and/or NVIDIA hangs, but then found that I could … Continue reading →
I had tried running kernel 3.10, but encountered several problems.. The KDE desktop would ‘hang’, and the wifi connections (rt2800, using NetworkManager) refused to connect, most of the time, and kmix (sound mixer app) wouldn’t run.. I had tried all the ‘patched’ NVIDIA drivers, and found that the ‘old’ 310.51 driver compiled OK, but didn’t work correctly … Continue reading →
Been trying the ‘released’ version of kernel 3.5 on my Dreamplug, and at first the hang appeared to be due to the fact that 3.5 didn’t detect the Marvell Orion USB controller, but now there is another problem (see Update below..): ‘Good’ boot (3.4.5): mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) Serial: 8250/16550 driver, 2 … Continue reading →
I have been having continuing problems with yum ‘hanging’ on my Dreamplug – through several different versions of Fedora, and numerous kernel updates (currently FC17 and Kernel 3.3..) The Fedora rootfs image did not include any swap, so – after some digging around – I decided to add a ./SWAP file, and activate it… The results (so … Continue reading →