[fedora-arm] Fedora 21 on BeagleBoard-xM Rev C

[Scott M. Jones]

Can you try root=/dev/mmcblk0p4 in the boot args?


> On Mar 2, 2015, at 2:18 AM, Sergio Durigan Junior <sergiodj at sergiodj.net> wrote:
> 
>> On Sunday, March 01 2015, Scott M. Jones wrote:
>> 
>> I ran into a problem where the kernel needs to load a vfat module in
>> order to read /boot but the module is on /boot, so it goes to
>> emergency mode. So you need to create a separate vfat partition for
>> MLO and u-boot.img and leave /boot as ext.  Make the vfat partition p1
>> and turn on the bootable flag.  (Or else recompile the kernel with
>> vfat built in, not a module.)
> 
> So, after spending a lot of time struggling with this, I finally managed
> to go back to where I was before: i.e., booting, but not able to mount
> the rootfs.
> 
> Here's how my SDCard looks now:
> 
>  Disk /dev/mmcblk0: 14.9 GiB, 16021192704 bytes, 31291392 sectors
>  Units: sectors of 1 * 512 = 512 bytes
>  Sector size (logical/physical): 512 bytes / 512 bytes
>  I/O size (minimum/optimal): 512 bytes / 512 bytes
>  Disklabel type: dos
>  Disk identifier: 0x00000000
> 
>  Device         Boot   Start     End Sectors  Size Id Type
>  /dev/mmcblk0p1 *         63  144584  144522 70.6M  c W95 FAT32 (LBA)
>  /dev/mmcblk0p2       145408 1144831  999424  488M 83 Linux
>  /dev/mmcblk0p3      1144832 1394687  249856  122M 82 Linux swap / Solaris
>  /dev/mmcblk0p4      1394688 4128767 2734080  1.3G 83 Linux
> 
> In order to finally get a "working" system, I used Arch[GNU/]Linux's
> scripts/u-boot/MLO found at
> <http://archlinuxarm.org/platforms/armv7/ti/beagleboard-xm>.  I don't
> know why, but I couldn't make the Fedora ones work with this setup...
> 
> Anyway, as I said, I'm back to a non-functional system (that, at least,
> shows me errors when booting Linux).  It is still unable to find my root
> file system by LABEL or UUID, and it still shows me *lots* of
> errors/warnings when booting Linux.
> 
> My question now is: does Fedora 21 really work on a BeagleBoard-xM rev
> C?  I'm starting to believe it doesn't (or that my board is somehow
> problematic/broken).
> 
> Any more ideas?  BTW, the uEnv.txt file that I am using is:
> 
>  mmcargs=setenv bootargs console=ttyO2,115200n8 root=LABEL=_/ ro
>  rootwait cgroup_disable=memory fixrtc earlyprintk
> 
>  mmcload=ext2load mmc 0:2 0x80000000 uInitrd-3.17.4-301.fc21.armv7hl;
>  ext2load mmc 0:2 0x88000000
>  dtb-3.17.4-301.fc21.armv7hl/omap3-beagle-xm-ab.dtb; ext2load mmc 0:2
>  0x88080000 vmlinuz-3.17.4-301.fc21.armv7hl
> 
>  uenvcmd=run mmcload; run mmcargs; bootz 0x88080000 0x80000000
>  0x88000000
> 
> And I am not using boot.cmd/boot.scr anymore.
>