[fedora-arm] Re: Connect to hidden wifi networks at boot.

>The router of the wifi network uses DHCP to give IP to connected >devices. Configure the DHCP server to allocate a fixed IP address to the RPi (based on its MAC address, which is now constant). Then you will know what address to use with ssh. ___ arm

[fedora-arm] Re: Raspberry Ugrade to ARM Fedora 30

> Dear All, to upgrade a Raspberry 3 I executed this commands > > sudo dnf -y upgrade --refresh > sudo dnf -y install dnf-plugin-system-upgrade > sudo dnf -y system-upgrade download --releasever=30 > sudo dnf -y system-upgrade reboot > > after the reboot dnf fails. Is anyone else having

[fedora-arm] Re: possible errors in generation of some arm7hl packages.

>I don't think it's a kernel problem, possibly a dnf cache issue, I too think it is not likely to be a kernel problem. A dnf cache problem also seems unlikely - each try retrieved new copies of the package files from a mirror, then failed in the same way. After the reboot, I think the dnf cache

[fedora-arm] Re: possible errors in generation of some arm7hl packages.

I tried again, with the same results for the three packages: kexec-tools-2.0.17-2.fc28.armv7hl.rpm httpd-2.4.33-5.fc28.armv7hl.rpm brltty-5.6-10.fc28.armv7hl.rpm I rebooted the Raspberry Pi and now the upgrade works smoothly. The kernel where it did not work was:

[fedora-arm] Re: aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

> I can manually configure my Raspberry Pi model 3B-plus on-board wired > Ethernet port to operate. It is indeed only DHCP configuration that > fails, but only with the on-board device; DHCP configuration of a USB > wired Ethernet port works fine. > > Have you tried the 4.16.0-300 kernel

[fedora-arm] aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

I can manually configure my Raspberry Pi model 3B-plus on-board wired Ethernet port to operate. It is indeed only DHCP configuration that fails, but only with the on-board device; DHCP configuration of a USB wired Ethernet port works fine. Curious.

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

>Why disable SELinux? It does not provide any significant value for my Raspberry Pi computer intended for use as an embedded system or in a DACS role, where network security is important but a simple (root or user) local privilege scheme is fine. The goals of SELinux are important, but its rocky

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

I used Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz and can boot successfully on my Raspberry Pi model 3B-plus. I used: fedora-arm-image-installer --target=rpi3 --media=/dev/sdi --norootpass --resizefs --selinux=off --image=fedora/F28/Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz to

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

See Peter Robinson's post on March 23, 2018, at 10:42 PM that details how to copy the Raspberry Pi device tree file for the model 3+. ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: F28 GNOME graphical login screen not displayed on Raspberry Pi 3.

https://bugzilla.redhat.com/show_bug.cgi?id=1561184 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] F28 GNOME graphical login screen not displayed on Raspberry Pi 3.

After booting an image such as Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz on a Raspberry Pi model 3, the First Boot process completes, but no graphical login screen appears. The system becomes unresponsive after a graphical pointer arrow is displayed (on top of whatever text was

[fedora-arm] Re: Raspberry Pi 3+

>I tried an image I has never used before >(Fedora-KDE-armhfp-28-20180325.n.0-sda.raw.xz). And it works. Good to hear. It seems only gdm (or maybe gnome-shell) is broken (fails to display the graphical login screen.) I just tried the LXDE image Fedora-LXDE-armhfp-28-20180325.n.0-sda.raw.xz and

[fedora-arm] Re: Raspberry Pi 3+

Did you change the default boot target from graphical.target to mult-user.target? That is what I had to do to avoid the problem with graphical login to my RPi. Of course, without a working network connection, you might feel it is not worth the bother, but my machine boots OK to a text console

[fedora-arm] Re: Raspberry Pi 3+

Thank you, Peter Robinson, your instructions worked beautifully. Perhaps this will not work with the aarch64 version used by Tomáš Frolík, but you already explained in an earlier post why there is little reason to use that on a Raspberry Pi. I used the following to install on a SD card:

[fedora-arm] Re: Fedora-Workstation-armhfp-28-20180319.n.0

>There is an accepted blocker for selinux issues on the disk images, SELINUX=permissive in my case, therefore I believe that should not be the problem here. >Workstation is a bit sluggish with 1G of RAM. Yes, but if I access the machine with ssh (and do not use the local graphical desktop) it

[fedora-arm] Re: Fedora-Workstation-armhfp-28-20180319.n.0

Using a Raspberry Pi model 3. 28-20180319 boots fine to multi-user, but fails to start the graphical desktop. A pointer is displayed (in the middle of the text screen containing the last of the boot messages), but the graphical login screen does not appear. The same Raspberry Pi with the same

[fedora-arm] Re: Fedora-Workstation-armhfp-28-20180319.n.0

>Which device? I'm presuming a RPi of some sort Sorry. Yes, a Raspberry Pi model 3 (not the new 3+). >I suspect [a monitor with a HDMI interface] Just so. OK, a little cryptic, but innocuous. Thank you. ___ arm mailing list --

[fedora-arm] Fedora-Workstation-armhfp-28-20180319.n.0

Problem or just noise? "dnf upgrade" succeeded today (260+ packages updated, seems like a lot for a one-day-old build, but this may simply be a busy time.) System was booted to multi-user target after upgrade, this message was generated at login time (but login succeeded, and journalctl captured

[fedora-arm] Re: Raspberry Pi 3+

>I'm undecided whether I want to do the related work to get this support >into F-27. With F28 beta just a week or two away, I suggest that is the appropriate target. ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to

[fedora-arm] Raspberry Pi 3+

F27 will not boot on the new Model 3+. Green LED blinks 4 times (medium), then 4 times (fast), then repeats. The colored splash screen is displayed. Might this be just a device tree problem? Raspbian journal contains a line: raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B

[fedora-arm] Re: what do i have to do to enable spi on fedora 27 on a raspberry pi

You might try Fedberry. I uncommented "dtparam=spi=on" in /boot/config.txt and now see the /dev/spidev0.0 and /dev/spidev0.1 devices. The GPIO devices (gpiochip0, gpiochip1, and gpiochip2) are present by default, without any special configuration. With F27, uncertain about what device tree

[fedora-arm] Re: Exactly how slow is Fedora 27 on an RP3 ? dnf update takes hours ?

It is definitely a good idea to check the system journal. If something wrong is recorded there, there are likely many instances logged to cause hours of unexpected delay. I find it better to use ssh to connect to my RPi than to suffer its slow graphics performance. Time information for a 'dnf

[fedora-arm] Re: Summary of Fedora on Odroid XU4

>This is where I put my grumpy hat on. Not grumpy, and it is no slur to call you realistic. (I would even venture to think you optimistic.) Thank you for cogent words about the Peter Robinson world. ___ arm mailing list -- arm@lists.fedoraproject.org

[fedora-arm] Re: Installing Updated Kernel on Raspberry Pi

"dnf upgrade" has installed many new kernels on my Raspberry Pi. ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Help about install version 26

If nothing looks more promising, try a different display. I have experienced a problem that resembles yours when I tried to use a modern Dell 4K resolution (8 megapixel) display with my RPi 3. An older display (without 4K capability) works. I have not tried my high resolution display recently,

[fedora-arm] Re: Fedora ARM Installer

>compressed *.raw.xz images which must be unpacked (at least under >windows) to write on SD card. https://en.wikipedia.org/wiki/XZ_Utils provides links to programs that should expand the .xz file on a Windows system. The expanded file is what must be copied to a SD card and used in an ARM

[fedora-arm] Re: RPi 3 extremely slow with F25. Extremely !

If the slowdown is due to log writes, what is written into your journal? It may be awkward to access the journal using the RPi, but move the SD card to another Fedora system (many laptops have flash card readers built in, or use a USB device) and a "smoking gun" may be obvious. The journal

[fedora-arm] Re: F26 Python LC_CTYPE=C complaint.

I understood, will report as you suggested later today. Too many balls in the air right now. >The display and initial-setup should come up even with the module >blacklisted (perhaps not on workstation, not tested there), you lose some >performance but it should be very usable. I did want to

[fedora-arm] Re: F26 Python LC_CTYPE=C complaint.

>>> In order to boot F26 on a Raspberry Pi, it is necessary to blacklist the >>> vc4 module to avoid a kernel failure >>> (https://bugzilla.redhat.com/show_bug.cgi?id=1387733). This means the >> >>Hopefully this is no longer the case. On the 20170416 nightly images[1] I >>didn't need to blacklist

[fedora-arm] Re: F26 Python LC_CTYPE=C complaint.

>> In order to boot F26 on a Raspberry Pi, it is necessary to blacklist the >> vc4 module to avoid a kernel failure >> (https://bugzilla.redhat.com/show_bug.cgi?id=1387733). This means the > >Hopefully this is no longer the case. On the 20170416 nightly images[1] I >didn't need to blacklist on my

[fedora-arm] F26 Python LC_CTYPE=C complaint.

Running on Raspberry Pi 3, with updates to April 19: [ryniker@RPi3-2 ~]$ uname -a Linux RPi3-2 4.11.0-0.rc5.git0.1.fc26.armv7hl #1 SMP Mon Apr 3 21:06:36 UTC 2017 armv7l armv7l armv7l GNU/Linux [ryniker@RPi3-2 ~]$ /usr/bin/python3.6 --version Python detected LC_CTYPE=C: LC_ALL & LANG coerced to

[fedora-arm] Re: Raspberry Pi 3 B Gpio

>Yes, there's python3-libsoc which should support the RPi. libsoc uses the old, deprecated sysfs interface to access GPIO resources from user space. I wrote a Python module to use the newer, file descriptor ioctl interface. See: http://ryniker.org/raspberrypi/Fedora/gpiofd.py I welcome

[fedora-arm] Re: Fedora Server image - where is newaliases

newaliases is part of the sendmail package. exim does not use the binary (compiled) alias data that newaliases creates for sendmail, but exim provides a newaliases file that does nothing so that users who install exim do not have to change any scripts they may have that modify the aliases file

[fedora-arm] kernel 4.9.2-200.fc25.armv7hl

Additional problem on Raspberry Pi (model 3): there is no: /sys/class/gpio This does exist with the 4.8.15-300 kernel, but it has problems: [root@RPi3-1 gpiochip970]# echo 993 >/sys/class/gpio/export [root@RPi3-1 gpiochip970]# echo 1 > /sys/class/gpio/gpio993/value bash: echo: write error:

[fedora-arm] kernel 4.9.2-200.fc25.armv7hl

4.9.2 does not appear to do much good. The blank screen problem https://bugzilla.redhat.com/show_bug.cgi?id=1387733 continues, and the kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out message still appears in the journal. The following document my experience:

[fedora-arm] Re: Raspberry Pi 2 - are post-install steps required?

Thank you, that provides a welcome solution. The Fedora case is slightly different: [ryniker@RPi3-1 ~]$ ls /sys/class/gpio export gpiochip970 unexport [ryniker@RPi3-1 ~]$ cat /sys/class/gpio/gpiochip970/base 970 Now the following works (at least there is no complaint; I

[fedora-arm] Re: Raspberry Pi 2 - are post-install steps required?

I believe GPIO is broken because the Raspbery Pi hardware platform is not correctly recognized, but I have not had available time to look carefully. [root@RPi3-1 ryniker]# uname -a Linux RPi3-1 4.8.4-301.fc25.armv7hl #1 SMP Tue Oct 25 02:01:39 UTC 2016 armv7l armv7l armv7l GNU/Linux Simple test

[fedora-arm] Re: Fedora 25 Candidate RC-1.3 for AArch64 Available Now!

Firefox (firefox.x86_64 49.0.2-1.fc24 @updates) complains (create an exception to allow Fedora to access the site)... https://arm.koji.fedoraproject.org/compose/25/Fedora-25-20161117.0/compose/ Peer’s Certificate issuer is not recognized. HTTP Strict Transport Security: false HTTP Public Key

[fedora-arm] Re: F25: black monitor on RPi 2

Sylvain Pasche on Tue, 25 Oct 2016 21:47:40 wrote: >My current workaround is just to blacklist vc4 (if that can help someone): >echo blacklist vc4 > /etc/modprobe.d/blacklist-vc4.conf That gives me a console on my RPi3, eliminates the "i2c-bcm2835 3f805000.i2c: i2c transfer

[fedora-arm] Re: F25 beta failure with RPi-3

Two more trials without any improvement: Using kernel-4.9.0-0.rc2.git0.2.fc26 does not help. I had no reason to think it would, but now that ssh to my RPi3 works well, it was easy to try. Changing the display to a Dell P2415Q (3840x2160 resolution, HDMI input) does not help. Again,

[fedora-arm] Re: F25 beta failure with RPi-3

Peter Robinson on Tue, 25 Oct 2016 10:23:13 wrote: >There's a new 4.8.4-301.fc25 kernel that I think should fix this issue No improvement with this new kernel. I set default to multi-user.target in an attempt to avoid any X11 confusion. After several screens of boot

[fedora-arm] Re: F25 beta failure with RPi-3

Peter Robinson wrote on Sat, 22 Oct 2016 15:18:00: >Can you just provide the output of dmesg? Yes, below, but it was a chore. How does one execute dmesg when there is no accessible user? The system boots far enough to initialize the Ethernet connection, and sshd is

[fedora-arm] F25 beta failure with RPi-3

Boots (a few screens of messages) but fails to run first boot user setup. There appears to be some confusion about the output display (HDMI connection) though it worked through u-boot and beyond the switch to framebuffer for additional line output. Journalctl output (from the 2016.10.18 nightly)