Update:
I finally managed to get the image to the card and successfuly run it. Maybe it's beacuse new version was released (25 Beta 1.1), because I tried all ways you suggested. (And yes, I was on Fedora wiki before, like on all RPi pages from F18, nothing helped me.)
So, now I have:
However it runs anaconda installation at the beginning, so it can't be fast deployed like other RPi OS distros. Either way it need configuration, so I will make my own image later.
The second thing is, that it feels like it runs slow - comapared to Raspbian or CentOS I tried on the same RPi3B.
Is it just a feeling or it is something known?
Thanks for replies!
--
I finally managed to get the image to the card and successfuly run it. Maybe it's beacuse new version was released (25 Beta 1.1), because I tried all ways you suggested. (And yes, I was on Fedora wiki before, like on all RPi pages from F18, nothing helped me.)
So, now I have:
OS: Fedora 25 Server Beta 1.1
FORMAT: compressed *.raw file
INSTALLATION: decompression
dd bs=4M if="/path/image.raw" of=/dev/mmcblk0; sync
However it runs anaconda installation at the beginning, so it can't be fast deployed like other RPi OS distros. Either way it need configuration, so I will make my own image later.
The second thing is, that it feels like it runs slow - comapared to Raspbian or CentOS I tried on the same RPi3B.
Is it just a feeling or it is something known?
Thanks for replies!
On Thu, Oct 13, 2016 at 11:27 AM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote:
>> >> > Trying to fix that by blacklisting vc4 (to make things continue on
>> >> > simplefb, due to vc4 not yet supporting dsi) doesn't work for some
>> >> > reason with the F25 beta image ...
>> >
>> > ... without success.
>>
>> Not a usecase I've tried, have you tried blacklisting the vc4 module
>> in something like "/etc/modprobe.d/vc4.conf"?
>
> Yes. Even tried to remove vc4.ko from the filesystem, suspecting that
> blacklisting didn't work for some reason. Didn't help.
I suspect then something is getting powered off because it doesn't
think it's needed. Will investigate.
>> We might also need to add the touchscreen driver to the kernel. I'm
>> not sure what is in the HW from the touchscreen PoV, I'll see if I can
>> find out.
>
> For touch to actually work yes, driver from rpi tree @ github must be
> ported over. IIRC it's connected via i2c.
>
> Display output doesn't need the touch driver though.
Sure, but I wasn't sure exactly what you were after.
Peter
_______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
