Has any work been done for the BPI-R2? I saw a note that the 4.11
kernel supports it.
Before I buy one (I want to work with the LAN multiport), I wish to know
if I stand a chance getting at least F26 beta working on it.
In /usr/share/uboot, I am only seeing a Bananapi uboot, not one for each
of the BPi boards. But in
Also, since it has sata, can it boot off the sata like the Cubieboards
(put no partitions and only uboot on mSD).
Just experienced a failed upgrade from Fedora 24 to Fedora 25 in a chroot environment on a android tablet. From what I understand these are coming from glibc not supporting specific android kernel. Not sure if there is something that can be done, but at least I am making a note about it.
Tablet is using Android 4.0.3 and uname -r gives "3.0.8+".
Just a note to say that I installed the Fedora KDE arm image on my RPi 3
from the link below using a Kingston class 10 SD card and it is running
After the second boot, I opened a console and did a 'dnf update'. With a
fast ethernet connection, it has taken nearly 12 hours to complete. It is
currently in the 'top' shows nothing CPU usage to be 2.3% for the top
process and nothing much for anthing else. The dnf process occasionally
pops up in the top list, using less than 1% of the cpu, though about 18% of
Is there a zombie thread running somewhere ?
I'll investigate further once the update process is complete.
BTW: kudos for bringing Fedora to the RPi platform. I'm so happy not to be
building custom kernels and to be running the same distribution I use on my
other computers. Keep up the good work !
I came up from x86 world, and found there is no grub on ARM installation, thus no file like /etc/default/grub where I could place some kernel arguments, that will be automatically attached to all newly installed kernels while updates are comming in. I've found it a great place to pass arguments like "elevator=noop".
Does extlinux (which I assume is grub equivalent on ARM) support such defaults ?
A whole bunch of RAS infrastructure patches recently went upstream. Can
I ask that those present from the ARM server vendors (or interested
other parties) assist in figuring out the userspace components so that
we can get these into future Fedora?
Computer Architect | Sent from my Fedora powered laptop
I installed fedora 26 minimal and performed a dnf update.
In the console I get a lot of times the following message:
[ 1631.798299] i2c-bcm2835 3f805000.i2c: i2c transfer timed out
I'm connected to the raspberry via serial console (enable_uart=1 and so on).
Is there a way to add packages (dumb question, I know: install RPMs inside
the SD card) from my PC and before inserting the SD card in the Raspberry?
Something like a cross platform rpm installation. Maybe not.
My question arises from this fact: I'm unable to use the ethernet
interface. I have only a wifi connection. So while I'm able to copy the
related file into /lib/firmware/brcm/brcmfmac43430-sdio.txt during the SD
card setup, I am still unable to use the wifi once booted the raspberry up,
due to the lack of networkmanager wifi plugin and wpasupplicant.
Do you have some hints? This is not so critical, it is just a curiosity.
Somehow I can retrieve an ethernet connection to install the required
Month ago I've been able successfully boot my pine64 on top of almost
regular fedora resources:
All what is really needed to add ATF patches to u-boot.
As I've been a bit busy in last month I was not able to finish my
uboot-tools.spec aftr it was updated to 2017.05 to propose necessary
changes (will try to do this in next two weeks).
Only other issue which I found are:
1) u-boot cannot boot out of regular vmlinuz and before reboot is
necessary unpack it to uImage file and change entry in
/boot/extlinux/extlinux.conf. If someone can provide some other way
how to boot from vmlinuz I would be happy to see it
2) during boot is reported OOPS and I've reported it in
3) rtl8192cu eth driver seems has no possibility to pass in params MAC
address and after each reboot and as long as someone will be using
DHCP with dynamic IP assignment after each reboot pine will be with
Nevertheless in last +week I was not able regularly update my pine64
and when I've done update yesterday I found that kernel
4.11.0-0.rc8.git4.1.fc27 and 4.11.0-1.fc27 no longer boots and last
kernel which I have which is booting is 4.11.0-0.rc6.git3.1.fc27.
Something introduced after 4.11.0-0.rc6.git3.1.fc27 now is causing
that Fedora kernel no longer boots on pine64. Simple after loading
kernel there is no even single line of kernel messages.
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
Thanks - indeed I had already disabled via that command.
Computer Architect | Sent from my 64-bit #ARM Powered phone
> On May 1, 2017, at 19:16, Dan Callaghan <dcallagh(a)redhat.com> wrote:
> Excerpts from Jon Masters's message of 2017-04-29 15:03 -04:00:
>>> On 04/29/2017 12:58 PM, Dennis Gilmore wrote:
>>>> El sáb, 29-04-2017 a las 02:40 -0400, Jon Masters escribió:
>>>> This was a different issue - mirrorlist entries don't work on the
>>>> test compose but Beaker doesn't know not to create a "fedora-updates"
>>>> repo. I turned that off at the distro level on my server.
>>> The issue is that beaker is using metalink urls but saying they are --
>>> mirrorlist the fix is to make beaker use --metalink instread of --
>>> mirrorlist. its a change in anaconda/pykickstart simplifying code
>> Anyone on the Beaker team want to comment on the best fix to
>> kickstarts/default for this?
> I haven't looked closely yet. I think it is a compatibility break in
> Anaconda (but maybe intentional). We can fix the kickstart templates in
> Beaker. In the short term, workaround is to set "no_updates_repos"
> ksmeta in your recipes or at the distro level.
> Dan Callaghan <dcallagh(a)redhat.com>
> Senior Software Engineer, Products & Technologies Operations
> Red Hat