As I've finally managed to get Fedora 25 booting from a USB attached HDD on a Raspberry Pi (2B) and I wasn't really able to it documented anywhere I'd like to document some of the things I found before I forget.
As the official Fedora support is so new, I haven't seen much discussion, so not really sure who to tell ... The Raspberry Pi page on the Fedora Wiki pointed me here.
The steps I used were very much the same as any of the guides for booting Raspbian from a USB HDD, but a couple of things I had to learn the hard way with Fedora:
1. The boot menu is extlinux and is configured from /boot/extlinux/extlinux.conf. This is where you need to set your root partition to point to the USB HDD partition. This may seem obvious, but considering there is cmdline.txt, /boot/grub/grub.conf and this to choose from it took a little time to figure.
2. The USB controller requires the dwc2 kernel module. This is not included in the default dracut image. It took me many hours to find this but once I rebuilt the image to include this module everything sprung to life.
For reference I used the following configuration:
I hope this is useful to someone and if anyone has suggestions for where to post it, fire away.
Lastly, it seems like a good idea to include the dwc2 module in dracut by default. Considering there are a bunch of other USB modules included (which I think can't do anything useful without the controller being initialised), it seems like an oversight not to include it. What would be the best place to request this?
Hi Jeremy, all,
I was just catching up with some folks and we discussed the status of
48-bit VA support. It seems to me that it would make most sense to have
an official coordination effort between those vendors/community members
who are interested, to ensure that they help with the necessary package
updates ahead of the kernel, and work with a test kernel to identify any
additional packages or issues that need resolving. I believe it would
make most sense to have a Fedora feature page (or something less grand,
but similar in concept) tracking this for F26, with the deps.
Perhaps Jeremy can update us on the status, and then he and others can
help drive this forward (someone should nominate themselves as the ring
leader too). I spoke with Cavium earlier today, and I know they'll be
keen to help. I know Qualcomm had expressed interest during our IRC
meetings in helping out. To that end, I'm copying at least those I know
so far who are interested here.
Computer Architect | Sent from my Fedora powered laptop
Current rawhide fedora image is using xfs has a bit higher memory
requirements than btrfs so I've started thinking about migration of my
current image to new root fs on new card.
Looking on partition table on rawhide image served by fedora I see:
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 61439 59392 29M c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 61440 1060863 999424 488M 83 Linux
/dev/mmcblk0p3 1060864 2060287 999424 488M 82 Linux swap / Solaris
/dev/mmcblk0p4 2060288 15126527 13066240 6.2G 82 Linux swap / Solaris
Q1: for what is this fat32 first partition?
Q2: is it possible to install uboot files from /boot on btrfs? (on x86 and
grub it is no problem with this)
Q3: seems someone done porting of the grub to arm so why there is n grub2
package in fedora?
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*
I've problems with using GPIO from python. It just throws some memory
error and dumps. I'm not familiar with C/dumps and so on, so I did not
yet start to try to get details of it.
One thing I noticed is different content of /proc/cpuinfo between
Raspbian and Fedora 25.
Thus my interpretation is that if Fedora reports a bit different
hardware then some calls to some methods might fail.
Am I missing some step that should be done after install?
It could be some mutation of FAQ: about support for HATs.
But I would love clear statement, which would point that it just does
not work out-of-the-box and there is/isn't way to manually fix it for
someone who is not C/kernel developer.
As for me support for HATs and support to set GPIO pin 18 to HIGH state
are slightly different things. But maybe they have same root cause.
Is there any chance nowadays of getting Fedora ARM running on cheap
Allwinner 7" Android tablets that ship with Android 5.1 ?
I am thinking of the likes of
7" Android Tablet
Android 5.1.1 operating system
Quad-core processor up to 1.2Ghz
8GB Internal Flash Memory
Further digging reveals:
CPU Allwinner A23
Would booting Linux be a pain like it was discussed here about three years
ago, or are there more mature solutions wrt replacing unlocking/replacing
bootloader or booting from external usb flash drive?
During times of Universal Deceit, telling the truth becomes a revolutionary
- George Orwell
I'm trying to understand if it is possible, and if yes then how, to enable
I2C and SPI.
On Raspbian one had to edit config.txt, but here overlays directory on
partition is empty.
Is there somewhere documented how to populate folder?
FAQ on https://fedoraproject.org/wiki/Raspberry_Pi is a bit unclear for me,
when it says no support for HATs.
It describes that some manual steps are required. That's fine, however I'm
not kernel developer,
I just play with some simple sensors. Using simple python scripts.
Is a quick answer to such usage: "Not yet"?
Right now Fedora 25 installed nicely on PI, and works great as Fedora box,
imap server, some www page.