Just a note to say that I installed the Fedora KDE arm image on my RPi 3
from the link below using a Kingston class 10 SD card and it is running
After the second boot, I opened a console and did a 'dnf update'. With a
fast ethernet connection, it has taken nearly 12 hours to complete. It is
currently in the 'top' shows nothing CPU usage to be 2.3% for the top
process and nothing much for anthing else. The dnf process occasionally
pops up in the top list, using less than 1% of the cpu, though about 18% of
Is there a zombie thread running somewhere ?
I'll investigate further once the update process is complete.
BTW: kudos for bringing Fedora to the RPi platform. I'm so happy not to be
building custom kernels and to be running the same distribution I use on my
other computers. Keep up the good work !
I recently bought a Raspberry Pi and I want to use it as a small server. I installed FC25 on it. The only additional piece of hardware is a bluetooth keyboard/mouse device, which is connected via usb dongle. On the software side I only installed a samba server and opened the related ports with a firewall command.
This installation is working and I can access the shared folder. However after a while - it differs - the server isn't available anymore. No ping is possible, also there is no HDMI signal anymore - the only thing I can do is restart it. I'm keeping the software up to date, but that doesn't solve the problem.
So what I would like to ask is, if there are known stability issues? Or is there something I can check and maybe fix? Maybe I could provide some details (not sure what - log doesn't tell anything usefull) to track down any issue.
I build a CubieTruck image using the installer script with the following
--target=Cubietruck --media=/dev/sdb --norootpass --selinux=OFF
I booted up the image with a UDB keyboard and VGA monitor attached plus
the TTY console.
After I logged into the console as root, I set the root password, and
added myself as a user. I then used this userID to log into the Xfce login.
Next I did 'dnf update' Of course this took time to run. But a VERY
long time between the cleanup and verify phases. During these I got the
Image Name: 4.10.0-0.rc5.git0.1.fc26.armv7hl
Created: Wed Jan 25 10:04:59 2017
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6054568 Bytes = 5912.66 kB = 5.77 MB
Load Address: 00008000
Entry Point: 00008000
Image Name: initramfs
Created: Wed Jan 25 10:05:01 2017
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 16525173 Bytes = 16137.86 kB = 15.76 MB
Load Address: 00000000
Entry Point: 00000000
dracut: Disabling early microcode, because kernel does not support it.
eventually the update finished. The system SEEMS to be working, but
what is with this message?
4.9.2 does not appear to do much good. The blank screen problem
continues, and the
kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out
message still appears in the journal.
The following document my experience:
It is possible there is something odd in my system. (I do not know of such
a thing, but there have been enough iterations of "try this... try that"
to make it difficult to assert I have exactly what one would obtain from a
As before, blacklisting VC4 allows the display to work. My default
target is multi-user, and I can login. I have not tried graphical output.
Has anyone setup subinterfaces like eth0.10, etc? I have a tagged vlan and
I can't get it to see the devices at all, all I ever get when trying to
bring up the interface is:
device does not seem to be present delaying initialization
I had to modprobe 8021q manually, but it doesn't help anyways, even without
tagging it doesn't see anything else except eth0 by itself.
Local time: Tue 2017-01-31 12:49:07 MST
Universal time: Tue 2017-01-31 19:49:07 UTC
RTC time: n/a
Time zone: America/Edmonton (MST, -0700)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time
This mode can not be fully supported. It will create various
with time zone changes and daylight saving time adjustments. The
time is never updated, it relies on external facilities to
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
# timedatectl set-local-rtc 0
Failed to set local RTC: hwclock failed: Child process exited with code 70
BTW, I *LOVE* how timedatectl and nmcli work ! No more hunting around for
obscure commands to set things up from the command line. I couldn't
believe how easy it was to set up wifi from ssh with nmcli ! Love it !
Keep up the good work.
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
Meeting started by pwhalen at 16:00:22 UTC. The full logs are available
* 1) ==== Userspace Status ==== (pwhalen, 16:04:15)
* Mass rebuild to start on Friday Feb 3rd. (pwhalen, 16:06:04)
* Mesa 17.0 RCs have started to land in rawhide, one thing of note it
now has the etnaviv driver which should give accelerated wayland on
imx6 and other vivante devices. (pwhalen, 16:08:11)
* 2) ==== Kernel Status ==== (pwhalen, 16:09:02)
* Latest kernel-4.10.0-0.rc6.git0.1.fc26 (pwhalen, 16:09:13)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=837098
* 3) ==== Bootloader Status ==== (pwhalen, 16:23:29)
* New U-Boot RC expected this week.
* 4) ==== Rawhide Testing ==== (pwhalen, 16:29:56)
* Testing so far(armhfp):
* Testing so far(aarch64):
* AArch64 systems fail to display the grub menu when PXE booted and
instead drop to a grub prompt (BZ#1405208) (pwhalen, 16:31:57)
* 5) == Open Floor == (pwhalen, 16:38:40)
Meeting ended at 16:44:39 UTC.
Action Items, by person
People Present (lines said)
* pwhalen (37)
* pbrobinson (29)
* jlinton (17)
* rric (5)
* hrw (4)
* zodbot (4)
* jonmasters (4)
* yselkowitz (0)
* dmarlin (0)
* ahs3 (0)
* msalter (0)
* dgilmore (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
As I've finally managed to get Fedora 25 booting from a USB attached HDD on a Raspberry Pi (2B) and I wasn't really able to it documented anywhere I'd like to document some of the things I found before I forget.
As the official Fedora support is so new, I haven't seen much discussion, so not really sure who to tell ... The Raspberry Pi page on the Fedora Wiki pointed me here.
The steps I used were very much the same as any of the guides for booting Raspbian from a USB HDD, but a couple of things I had to learn the hard way with Fedora:
1. The boot menu is extlinux and is configured from /boot/extlinux/extlinux.conf. This is where you need to set your root partition to point to the USB HDD partition. This may seem obvious, but considering there is cmdline.txt, /boot/grub/grub.conf and this to choose from it took a little time to figure.
2. The USB controller requires the dwc2 kernel module. This is not included in the default dracut image. It took me many hours to find this but once I rebuilt the image to include this module everything sprung to life.
For reference I used the following configuration:
I hope this is useful to someone and if anyone has suggestions for where to post it, fire away.
Lastly, it seems like a good idea to include the dwc2 module in dracut by default. Considering there are a bunch of other USB modules included (which I think can't do anything useful without the controller being initialised), it seems like an oversight not to include it. What would be the best place to request this?