2017-05-09 0:46 GMT+02:00 Peter Robinson <pbrobinson(a)gmail.com>:
>
> What disk image are you using? I believe all the images, definitely the
> minimal, as I use it regularly, have the required plugins and you can use
> the client to configure it.
>
> Details:
> https://nullr0ute.com/2016/09/connect-to-a-wireless-network-
> using-command-line-nmcli/
>
Thanks for your reply.
So, maybe it is the Fedora-Server-armhfp-26 image that doesn't
include NetworkManager-wifi plugin, that lead me to "Error: No Wi-Fi device
found." issuing the "nmcli device wifi rescan" command.
In fact:
[root@localhost ~]# rpm -qa |grep Network
NetworkManager-1.8.0-0.2.rc2.fc26.armv7hl
NetworkManager-team-1.8.0-0.2.rc2.fc26.armv7hl
NetworkManager-libnm-1.8.0-0.2.rc2.fc26.armv7hl
Even if
[root@localhost ~]# iwconfig
...
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
I will try minimal image.
Anyway my question is still valid. Is it a simple task to add packages
before inserting the SD card in the raspberry? Or it requires a lot of work
and skills I don't have?
Thanks
A.

I'm using Fedora 26 on a Raspberry Pi 3.
Is it normal that at each reboot (or shutdown and poweron), the MAC address
of the Ethernet card is each time a different one?
There is a place where to specify the MAC address of the Ethernet card?
Thanks
A.

I am using an imx6 SoM from SolidRun. We have purchased a large number of
these and mostly they work fine.
I tried to update to Fedora 25 and now a few of them won't boot. (most work
fine)
All my SoMs are all supposed to be the same but some must be different.
Both worked fine with an older version of Fedora
Is there any way to just force a boot from MMC1 with no checks?
I tried to update to the u-boot from Fedora 26 just to see if that would
help. It does not.
This is what I get with the "bad" ones
U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from unknown boot device
SPL: Unsupported Boot Device!
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
The ones that boot correctly do this
U-Boot SPL 2016.09.01 (Oct 19 2016 - 14:40:29)
Trying to boot from MMC1
U-Boot 2016.09.01 (Oct 19 2016 - 14:40:29 +0000)
CPU: Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 28C
Reset cause: POR
Board: MX6 Hummingboard
DRAM: 1 GiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment
--
Andrew Gillis
Small Green Computer
603-488-0617

Hi,
I haven't looked into this, but the following merge for 4.12 got flagged for followup:
http://www.spinics.net/lists/kvm/msg149582.html
Others might find this interesting. I guess it boots at EL2 these days then - haven't played with the latest generation much - but I don't know if there are additional weirdness beyond just the interrupt controller setup (which is known to be very odd).
Jon.
--
Computer Architect | Sent from my 64-bit #ARM Powered phone

Running Fedora 26 Minimal (20170504.n.1 compose) inside a kvm virtual
machine, all goes well.
Using it in a Raspberry Pi 3 model B, the boot process is ok, the system is
subsequently functional, but I have an issue with initial setup process: in
other words the systemd initial-setup unit fails to start.
<https://bugzilla.redhat.com/show_bug.cgi?id=1449391>
Please note that I don't use a screen, but I'm connected to the RPi using
the serial connection.
Someone else is facing the same issue?
Thanks
A.