When will source : https://fedoraproject.org/wiki/Architectures/ARM/F22/Installation
'--target=TARGET - target board [A10-OLinuXino-Lime|A20-OLinuXino-Lime|A20-OLinuXino-Lime2|A20-OLinuXino_MICRO|Bananapi|Bananapro|beaglebone|Cubieboard|Cubieboard2|Cubietruck|Mele_A1000|Mini-X|none|novena|panda|riotboard|trimslice|wandboard_dl|wandboard_quad|wandboard_solo] '
Include the PI2 please?
Looking forward to install FC22 on the PI2 Thankyou
Adrian ... vk4tux
On Sun, May 31, 2015 at 11:54 AM, Adrian vk4tux@bigpond.com wrote:
When will source : https://fedoraproject.org/wiki/Architectures/ARM/F22/Installation
'--target=TARGET - target board [A10-OLinuXino-Lime|A20-OLinuXino-Lime|A20-OLinuXino-Lime2|A20-OLinuXino_MICRO|Bananapi|Bananapro|beaglebone|Cubieboard|Cubieboard2|Cubietruck|Mele_A1000|Mini-X|none|novena|panda|riotboard|trimslice|wandboard_dl|wandboard_quad|wandboard_solo] '
Include the PI2 please?
Looking forward to install FC22 on the PI2 Thankyou
When we have it working, we're working ATM to get a remix done, and upstream support in F-23.
On Sun, 2015-05-31 at 20:54 +1000, Adrian wrote:
Include the PI2 please?
Looking forward to install FC22 on the PI2 Thankyou
Adrian,
Peter having stated the intention to support the Pi2B via a remix for F22 and "officially" in F23, removes the need for me to make my F22 Pi2B images available.
I did come up with a 21->22 "upgrade" solution, following your emails, (fedup refusing to play nice without an initramfs image), but documenting this now is just going to result in the hordes of users of the F21 images switching to my F22 SC repo for the life-cycle of F22, which puts my "real" work at risk, having not been able to find anyone who would take over hosting when made aware of the numbers involved.
So sit tight and wait for the F22 remix from Peter, that's my advice.
In any case, I'm probably only a few days away from finishing the conversion of the remainder of SC packages to Debian/Ubuntu, at which point the Fedora SC repos won't see any further updates anyway.
Regards
Clive
Clive, Thankyou for what you have done so far, My amateur radio images have never been so successful as with your current FC21 image base I have built on with my packages etc.
I will see if there is any way to discover what you have with fedup to keep it running. I consider PI2 support to be a top priority for any platform supporting arm.
It will dominate the market.
Adrian ... vk4tux
On 01/06/15 00:00, Clive Messer wrote:
On Sun, 2015-05-31 at 20:54 +1000, Adrian wrote:
Include the PI2 please?
Looking forward to install FC22 on the PI2 Thankyou
Adrian,
Peter having stated the intention to support the Pi2B via a remix for F22 and "officially" in F23, removes the need for me to make my F22 Pi2B images available.
I did come up with a 21->22 "upgrade" solution, following your emails, (fedup refusing to play nice without an initramfs image), but documenting this now is just going to result in the hordes of users of the F21 images switching to my F22 SC repo for the life-cycle of F22, which puts my "real" work at risk, having not been able to find anyone who would take over hosting when made aware of the numbers involved.
So sit tight and wait for the F22 remix from Peter, that's my advice.
In any case, I'm probably only a few days away from finishing the conversion of the remainder of SC packages to Debian/Ubuntu, at which point the Fedora SC repos won't see any further updates anyway.
Regards
Clive
On Mon, 2015-06-01 at 00:12 +1000, Adrian wrote:
I will see if there is any way to discover what you have with fedup to keep it running.
I'd rather you didn't do that! ;) Just sit tight for the moment and give Peter the time he needs, for what although will still be a remix, I suspect will be viewed by many as a "semi-official" release, at the point a Fedora/Redhat person is responsible for producing it.
I consider PI2 support to be a top priority for any platform supporting arm.
It will dominate the market.
LOL. The Pi has already dominated, love it or loathe it. There is no argument based on unit sales. 5 million or so sold, last time I looked at numbers. I think the second most popular piece of hardware in terms of sales, something like 220k units sold, for the BeagleBone. Most of the other "alternatives" have sales in the low, or tens of thousands. Not that unit sales should be the "yard stick" for deciding if something should be supported or not, but in the case of the Pi, it is somewhat difficult to ignore its popularity.
Regards
Clive
Distro sync to FC22 successfully done with the ultix image ;
Screenshot from PI2 via VNC.
http://vk4tux.duckdns.org/PI2FC22.jpg
Image link will be posted soon
Adrian ... vk4tux
On 02/06/15 07:05, Adrian wrote:
Distro sync to FC22 successfully done with the ultix image ;
Screenshot from PI2 via VNC.
http://vk4tux.duckdns.org/PI2FC22.jpg
Image link will be posted soon
Adrian ... vk4tux _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
I note the network dhcp lease/mac address fix works now. A router assigned IP lock works, whereas in FC21 it did not, and the nm IPV4 needed a manual IP set on the PI2.
With FC22 here it seems not necessary.I will try kernel 4 with it.
On Tue, 2015-06-02 at 07:51 +1000, Adrian wrote:
With FC22 here it seems not necessary.I will try kernel 4 with it.
Adrian,
For stability, you might want to stick with 3.18 branch for the moment. Don't know whether it was specific to my 4.0.4 build or generically applicable to the rpi-4.0.y tree, and I haven't had time to investigate further, but I was experiencing some random lock-ups with rpi-4.0.y tree, hence the F22 raspberrypi-kernel rpms I made remain in "unstable" repo.
PS. Please, if you release any images yourself, do not point back (repo package pre-installed) to the SC repo. I've been given another warning this morning, that if bandwidth demands increase again, (which they did again last night courtesy of some moron repeatedly running a recursive wget all night long on the entire 5Gig repo), it'll be taken offline.
Regards
Clive
If you are interested I would be happy to host the repo on my server. I have unlimited bandwidth.
-Andrew
On Tue, Jun 2, 2015 at 9:30 AM, Clive Messer clive.m.messer@gmail.com wrote:
On Tue, 2015-06-02 at 07:51 +1000, Adrian wrote:
With FC22 here it seems not necessary.I will try kernel 4 with it.
Adrian,
For stability, you might want to stick with 3.18 branch for the moment. Don't know whether it was specific to my 4.0.4 build or generically applicable to the rpi-4.0.y tree, and I haven't had time to investigate further, but I was experiencing some random lock-ups with rpi-4.0.y tree, hence the F22 raspberrypi-kernel rpms I made remain in "unstable" repo.
PS. Please, if you release any images yourself, do not point back (repo package pre-installed) to the SC repo. I've been given another warning this morning, that if bandwidth demands increase again, (which they did again last night courtesy of some moron repeatedly running a recursive wget all night long on the entire 5Gig repo), it'll be taken offline.
Regards
Clive
Clive Messer clive.m.messer@gmail.com
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
I did some testing
http://vk4tux.duckdns.org/PI2FC22_top.jpg
plasmashell has settled down nicely after ;
Installing
Install dbus-c++-0.9.0-8.fc22.armv7hl @updates Install dbus-c++-devel-0.9.0-8.fc22.armv7hl @updates Install dbus-c++-ecore-0.9.0-8.fc22.armv7hl @updates Install dbus-c++-glib-0.9.0-8.fc22.armv7hl @updates Install dbus-devel-1:1.8.18-1.fc22.armv7hl @updates Install dbus-doc-1:1.8.18-1.fc22.noarch @updates Install dbus-glib-devel-0.104-1.fc22.armv7hl @fedora Install dbus-java-2.7-17.fc22.armv7hl @fedora Install dbus-java-javadoc-2.7-17.fc22.armv7hl @fedora Install dbus-python-devel-1.2.0-7.fc22.armv7hl @fedora Install dbus-qt3-0.9-13.fc22.armv7hl @fedora Install dbus-qt3-devel-0.9-13.fc22.armv7hl @fedora Install dbus-sharp-1:0.7.0-12.fc22.armv7hl @fedora Install dbus-sharp-devel-1:0.7.0-12.fc22.armv7hl @fedora Install dbus-sharp-glib-0.5.0-10.fc22.armv7hl @fedora Install dbus-sharp-glib-devel-0.5.0-10.fc22.armv7hl @fedora Install dbusmenu-qt-devel-0.9.2-8.fc22.armv7hl @fedora Install dbusmenu-qt5-devel-0.9.3-0.3.20140604bzr.fc22.armv7hl @fedora
with improved reliability, and I have not had an issue since, still using;
[root@raspi2 yum.repos.d]# uname -a Linux raspi2 4.0.4-503.20150528git28f888d.fc22.armv7hl.bcm2709 #1 SMP PREEMPT Fri May 29 00:48:23 BST 2015 armv7l armv7l armv7l GNU/Linux
> With FC22 here it seems not necessary.I will try kernel 4 with it. Adrian, For stability, you might want to stick with 3.18 branch for the moment. Don't know whether it was specific to my 4.0.4 build or generically applicable to the rpi-4.0.y tree, and I haven't had time to investigate further, but I was experiencing some random lock-ups with rpi-4.0.y tree, hence the F22 raspberrypi-kernel rpms I made remain in "unstable" repo.
Il giorno mar, 02/06/2015 alle 07.05 +1000, Adrian ha scritto:
Distro sync to FC22 successfully done with the ultix image ;
Great!
What is the best way to install f22 on RPI2? There are some howto?
Many thanks
On Sun, 31 May 2015 15:00:10 +0100 Clive Messer clive.m.messer@gmail.com wrote:
Peter having stated the intention to support the Pi2B via a remix for F22 and "officially" in F23,
Does this mean that the performance problems we have been discussing https://www.raspberrypi.org/forums/viewtopic.php?p=729713#p729713 are solved?
-- Johan