Recently I tried F21 on that board. The result was a bit disappointing...
Apperently Fedora has several issues with that hardware:
- thermal shutdown, after message something like "kernel trap/thermal
- wlcore module error
- some other error, possibly related to swap module /Need to redo testing
here, not captured on logs/
What do You think? What is advisable to do /if any/ in this situation?
I have some time, maybe can provide ssh/vnc access, if somebody is
interested to examine issues.
However, in that case we probably have to do something with that termal
I'm not experienced with specific kernel things that maybe involved.
For this test:
Serial console disconnected
HDMI monitor directly connected to HDMI port (past tests had HDMI/VGA
adapter to KVM switch)
Unpowered USB hub with keybd & mouse
mSD card boot
I loosely timed the boot. The boot starts with various messages and 2
The text disappears but pengiuns remain for 20 sec
The pengiuns disappear and the screen is black for 40 sec
Blacklight comes on for 20 sec
mouse appears for 20 sec
Empty configurator screen appears for 5 sec
Configurator options appear.
So for 40 sec it is: "Hello anyone home". No indication that anything
is happening. At least a wait screen would be nice.
The only video resolution is 1024x768. I was hoping that direct
connected HDMI would offer higher resolution. Seems not?
This is all the tests for today. Most likely.
First time trying to setup my cubietruck/cubieboard3. I used
fedora-arm-installer to fill in an 8GB sd card on my host machine, using
Pop it into my cubietruck, connect via serial console, start it up. Machine
passes uboot fine and boots the initrd, but eventually fails waiting for the
root mount point to show up, and falls back to dracut.
Comparing my boot output to kashyap's, my machine has all the same messages
referencing 'mmc1', but there's nothing about mmc0. mmcblk0 never shows up, so
the boot fails after a timeout.
So I populated a SATA drive in the same way as above, hooked that to the
cubietruck, and it boots successfully. But I still can't access the sdcard
from fedora. The only thing under /sys/block is sda. Tried removing and
re-inserting the sunxi_mmc module, doesn't seem to help. Tried another sd
card, didn't make a difference.
I updated the kernel on the sdcard (by updating /boot on the sata drive,
sticking the sdcard in a USB adapter, rsyncing the contents), booted into the
latest lpae kernel, but still the sdcard isn't detected.
Anyone have any ideas? Googling didn't turn up anything.
If not, is it possible to make the cubietruck boot directly off the sata
drive? Doesn't seem to work for me, but if I can make that work I don't need
to worry about the sdcard.
Is audio support on the Cubietruck through the headphone plug with the
I have been trying to play some wav files and the players are crashing.
If this is the current situation, I will wait until later to test more.
If it is suppose to work, I will work up a crash report.
During the F21 development, it seemed that uboot was very stable. That
is only occationally was an update rolled in. This seems to be the case
now in F22.
The reason I am asking for clearification is that Hans told me that I
can now boot from sata with only uboot on the SD card. So I can take an
old SD card, put uboot on it and only change that when a new uboot is
rolled in. I would pick up a couple sata drives cheap on ebay (back in
the fall, I got 5 80Gb drives for $10/each and free shipping), and dd
the partitions to them for testing.
If uboot is updated frequently with no announcement, that only means
that I build a new uboot SD card with each sata drive image. Just an
extra step, but I would like to know about uboot updates.
(going to start shopping for hdd and ssd drives today)