I am running raspberry pi3B and with lastest fedora 28 (with kernel 4.16.0-300.fc28.aarch64)
I read from the unicorn Hat that I need to activate SPI using raspi-config ( for raspbian only)
So I tried to do it manually .. and that's when everything did not go so well :)
I understood that I have to tune /boot/efi/config.txt file adding
I guess I have also to add a dtoverlay line but I don't which one ...
----- Mail original -----
> De: "Peter Robinson" <pbrobinson(a)gmail.com>
> À: "Ludovic Hirlimann - wargame" <debellum(a)free.fr>
> Envoyé: Lundi 30 Avril 2018 15:51:19
> Objet: Re: [fedora-arm] Re: RPI 3b+ Support ?
> On Mon, Apr 30, 2018 at 2:48 PM, Ludovic Hirlimann - wargame
> <debellum(a)free.fr> wrote:
> >> > black with no more green light blinking.
> >> By selection menu you mean grub? How are you connected? Via HDMI?
> >> If
> >> so do you get the penguins?
> > Yes Grub - I use HDMI yes + mouse and French keyboard.
> > I don't see pinguins.
> What was the file name of the image you used?
> You'd normally get some output until the vc4 driver loaded, it
> wouldn't usually go straight blank.
> > Ludo
> > ps any debuging I can turn on to get logs for you guys ?
i have a inet 3f tablet (pov protab 255xxl) and managed to get fedora 27 running on the board with a inet1 dtb,
The kernel from the initial image boots and everything (except for the touchscreen) works.
this is version 4.13.3-300.fc27.amv7hl,
i also installed version 4.13.9-300.fc27.amv7hl,
and these also work fine,
Then i updated to the latest fedora 27 kernel 4.15.15-300.fc27.armv7hl and this kernel starts booting, but then the screen goes blank, and i cannot login via ssh either,
the same happened with a self compiled kernel 4.17.0-0.rc0.git0.300.fc27.armv7hl with lima drivers patched.
I have tried to find the serial port pins on the board, but could not locate them, also kernel versions 4.14 i have not tried yet because i cannot find them precompiled.
Are there any parameters i can change to try to make it boot, or get more output in the process? Or a link to documentation :)
Whole boot process is OK until:
[ OK ] Mounted /boot.
[ OK ] Mounted /boot/efi.
[ OK ] Reached target Local File Systems.
Starting Restore /run/initramfs on shutdown...
Starting Import network configuration from initramfs...
Starting Rebuild Journal Catalog...
Starting Rebuild Dynamic Linker Cache...
Starting Tell Plymouth To Write Out Runtime Data...
[ OK [ 39.871989] audit: type=1130 audit(1520306229.519:93): pid=1
uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
] Started Restore /run/initramfs on shutdown.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Rebuild Journal Catalog.
[ OK ] Started Import network configuration from initramfs.
[ OK ] Started Rebuild Dynamic Linker Cache.
Starting Update is Completed...
Starting Create Volatile Files and Directories...
[ OK ] Started Update is Completed.
[ OK ] Started Create Volatile Files and Directories.
Starting Security Auditing Service...
[ OK ] Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Listening on SSSD Secrets Service responder socket.
[ OK ] Started dnf makecache timer.
[ OK ] Reached target Timers.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Listening on Open-iSCSI iscsiuio Socket.
[ OK ] Listening on Open-iSCSI iscsid Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Login Service...
[ OK ] Started D-Bus System Message Bus.
[ OK ] Started Hardware RNG Entropy Gatherer Daemon.
Starting Initial Setup configuration program...
[ OK ] Started Secure Boot DBX (blacklist) updater.
Starting NTP client/server...
[ OK ] Reached target sshd-keygen.target.
Starting firewalld - dynamic firewall daemon...
On some boots is displayed FAIL on NTP and firewalld services but
except this nothing more happens.
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
Peter sorry for the confusion and thank you for the prompt reply
in your reply to Fri, Mar 23, 2018 at 11:28 AM, Tomáš Frolík
"Once it's running if you update the kernel to rc6 you should be
running just fine. One other thing to note is there's some different
bits needed for the wifi. I'm going to put all of those, inc the one
needed for the original Pi3, into an rpm but I've not had a chance to
do that as yet. Give me a day or so and I'll likely get that done."
This is what I was enquiring about. I have fedora 28 beta running on a
Raspberry pi 3B+ all good but no wifi.
Regards Chris Hall
I've become used to using kickstart files to automate my Fedora
installs to VMs and bare-metal x86 hardware. I'm getting started with
Fedora on ARM and am wondering if there is something similar to create
custom disk images. The closest I've found is the page on creating ARM
Is that still the way to go, or is there a better approach?