Hi,
I just wanted to report that F22 works very well on the PcDuino3 Nano. In
fact, I installed the LXDE image, and this is the first time I've seen the
graphical startup screen.
There are a few things to note.
1 - The graphics were at the lowest res and couldn't get any higher. (Was
expecting this)
2 - I haven't tested the SATA yet (need to get the cables)
3 - I am using the pcduino uboot and kernel
So, not 100%, but I'm not expecting that until it's patch hits the
mainstream kernel. (Hoping 4.3)
Thank you to everyone who helped F22 work so well.
Troy Dawson
p.s. I'm planning on trying out the rawhide uboot, I'm very excited about
the 2015.07 uboot. Hopefully will have some time this weekend.
p.p.s. Until the pcduino3 patch makes it in the kernel, here is how to
install fedora on one
http://www.yortnoswad.org/blog/2014/10/29/fedora-on-pcduino3-nano/
I have been working on my pogoplug again that has the F18 from:
https://fedoraproject.org/wiki/Architectures/ARM/PogoplugUSBDisk
It boots just fine PROVIDED that only the F18 usb drive is the only one
in at boot time. If I have my 3Tb drive in at boot time it fails. I
did a google search and claims are made that the usb order is bottom to
top (for the three usb ports on the back, I assume the front is after
them). But even putting my OS drive on the bottom I still fail. What I
am seeing on the serial console is:
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Using egiga0 device
ping failed; host 192.168.128.27 is not alive
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 4 USB Device(s) found
scanning bus for storage devices... READ_CAP ERROR
3 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt
** Unable to read "/rescueme.txt" from usb 0:1 **
where as a 'proper boot after autoboot is:
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt
** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
etc.
It just hangs. I will be having my pogoplug on a ups, but still I
really want it to boot reliablely after a power outage. My printenv in
uboot is:
u-boot>> printenv
arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run
usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:02:FE:7C
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1
0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1;
then run rescue_bootcmd; fi
if_netconsole=ping $serverip
ipaddr=192.168.128.26
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run
rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm
0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2
root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.128.27
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv
stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount
rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000
/boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd
root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 uImage; if
ext2load usb $usb_device 0x1100000 uInitrd; then bootm 0x800000
0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext4
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run
usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb
0x800000 uImage 1; then usb_scan_done=1; echo "Found bootable drive on
usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda3
usb_scan_2=usb=1:1 dev=sdb3
usb_scan_3=usb=2:1 dev=sdc3
usb_scan_4=usb=3:1 dev=sdd3
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root
rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
$usb_custom_params
Environment size: 2575/131068 bytes
u-boot>>
===============
Separately, what are those IP addresses doing there? I do not remember
putting them there, perhaps that is an artifact of the original pogo
linux. The unit is currently on a different subnet than 192.168.128.0,
but I will be moving it back there once I go into production. How do I
remove those addresses?
thank you
Fedora 23 Alpha Release Announcement for aarch64 and POWER
==========================================================
The Fedora 23 Alpha is here, right on schedule for our planned
October final release. Download the prerelease from our Get Fedora
site:
https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/23_Alpha/Se…
What is the Alpha release?
--------------------------
The Alpha release contains all the exciting features of Fedora 23's
editions in a form that anyone can help test. This testing, guided
by the Fedora QA team, helps us target and identify bugs. When
these bugs are fixed, we make a Beta release available. A Beta
release is code-complete and bears a very strong resemblance to the
third and final release. The final release of Fedora 23 is expected
in October.
We need your help to make Fedora 23 the best release yet, so please
take some time to download and try out the Alpha and make sure the
things that are important to you are working. If you find a bug,
please report it – every bug you uncover is a chance to improve the
experience for millions of Fedora users worldwide.
Together, we can make Fedora rock-solid. We have a culture of
coordinating new features and pushing fixes upstream as much as
feasible, and your feedback will help improve not only Fedora but
Linux and free software on the whole.
* https://fedoraproject.org/wiki/Releases/23/Schedule
* https://fedoraproject.org/wiki/How_to_file_a_bug_report
Fedora-Wide Changes
-------------------
Fedora 23 includes a number of changes that will improve all of the
editions. For example, Fedora 23 is making use of compiler flags to
help improve security by "hardening" the binaries against memory
corruption vulnerabilities, buffer overflows, and so on. This is a
"behind the scenes" change that most users won't notice through
normal use of a Fedora edition, but should help provide additional
system security.
Likewise, Fedora 23 has disabled SSL3 and RC4 by default due to
known vulnerabilities in the protocols. This means all applications
that use GNUTLS and OpenSSL libraries have had the SSL3 protocol
and RC4 cipher disabled.
Fedora 23 Alpha also includes support for Unicode 8.0, which
includes new emojis, and improvements in sorting Unicode text and
processing non-ASCII URLs.
Issues and Details
------------------
This is an Alpha release. As such, we expect that you may encounter
bugs or missing features. To report issues encountered during
testing, contact the Fedora QA team via the mailing list or in
#fedora-qa on freenode.
As testing progresses, common issues are tracked on the Common F23
Bugs page. For tips on reporting a bug effectively, read "how to
file a bug report."
* https://fedoraproject.org/wiki/Common_F23_bugs
* https://fedoraproject.org/wiki/How_to_file_a_bug_report
Release Schedule
----------------
The full release schedule is available on the Fedora wiki. The
current schedule calls for a beta release towards the end of
September, and the final release scheduled towards the end of
October.
These dates are subject to change, pending any major bugs or issues
found during the development process.
* https://fedoraproject.org/wiki/Releases/23/Schedule