4:15 p.m.
I have a Beagleboard XM rev B and needed a VFAT boot partition in order
to boot. Will these be provided for F21 and are they still needed?
http://mirror.pnl.gov/fedora/linux/releases/21/Images/armhfp/
Thanks,
Scott
6:54 p.m.
On Wed, Dec 10, 2014 at 10:15 PM, Scott M. Jones <scott(a)aprr.org> wrote:
I have a Beagleboard XM rev B and needed a VFAT boot partition in
order
to boot. Will these be provided for F21 and are they still needed?
The VFAT images are no longer provided. It should be possible, like on
the OMAP4/am33xx devices, to write the uboot to an offset on the root
of the drive, there's about 2mb left free at the beginning of the ARM
images to enable this, and get uboot to work. I've looked very briefly
at this on my xM and started to read docs to see if there was any
difference between the SoCs but I've not got very far as I've had
other more pressing things.
Peter
7:50 p.m.
On Wed, Dec 10, 2014 at 6:54 PM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Wed, Dec 10, 2014 at 10:15 PM, Scott M. Jones
<scott(a)aprr.org> wrote:
> I have a Beagleboard XM rev B and needed a VFAT boot partition in order
> to boot. Will these be provided for F21 and are they still needed?
The VFAT images are no longer provided. It should be possible, like on
the OMAP4/am33xx devices, to write the uboot to an offset on the root
of the drive, there's about 2mb left free at the beginning of the ARM
images to enable this, and get uboot to work. I've looked very briefly
at this on my xM and started to read docs to see if there was any
difference between the SoCs but I've not got very far as I've had
other more pressing things.
RAW mode wasn't introduced till the omap4's bootrom. However there
are now patches to boot the beagle/beaglexm (omap34xx/dm3730) from
extX via u-boot. But, there's not enough sram for both vfat & extX so
it's a choice you need to make.
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
2:20 a.m.
On Thu, Dec 11, 2014 at 1:50 AM, Robert Nelson <robertcnelson(a)gmail.com> wrote:
On Wed, Dec 10, 2014 at 6:54 PM, Peter Robinson
<pbrobinson(a)gmail.com> wrote:
> On Wed, Dec 10, 2014 at 10:15 PM, Scott M. Jones <scott(a)aprr.org> wrote:
>> I have a Beagleboard XM rev B and needed a VFAT boot partition in order
>> to boot. Will these be provided for F21 and are they still needed?
>
> The VFAT images are no longer provided. It should be possible, like on
> the OMAP4/am33xx devices, to write the uboot to an offset on the root
> of the drive, there's about 2mb left free at the beginning of the ARM
> images to enable this, and get uboot to work. I've looked very briefly
> at this on my xM and started to read docs to see if there was any
> difference between the SoCs but I've not got very far as I've had
> other more pressing things.
RAW mode wasn't introduced till the omap4's bootrom. However there
are now patches to boot the beagle/beaglexm (omap34xx/dm3730) from
extX via u-boot. But, there's not enough sram for both vfat & extX so
it's a choice you need to make.
Oh interesting, so that means we can put the u-boot/MLO on a ext4
/boot partition (partition 1) and have it work? If not how does this
work?
Peter
8:29 a.m.
On Tue, Dec 16, 2014 at 2:20 AM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Thu, Dec 11, 2014 at 1:50 AM, Robert Nelson
<robertcnelson(a)gmail.com> wrote:
> On Wed, Dec 10, 2014 at 6:54 PM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> On Wed, Dec 10, 2014 at 10:15 PM, Scott M. Jones <scott(a)aprr.org> wrote:
>>> I have a Beagleboard XM rev B and needed a VFAT boot partition in order
>>> to boot. Will these be provided for F21 and are they still needed?
>>
>> The VFAT images are no longer provided. It should be possible, like on
>> the OMAP4/am33xx devices, to write the uboot to an offset on the root
>> of the drive, there's about 2mb left free at the beginning of the ARM
>> images to enable this, and get uboot to work. I've looked very briefly
>> at this on my xM and started to read docs to see if there was any
>> difference between the SoCs but I've not got very far as I've had
>> other more pressing things.
>
> RAW mode wasn't introduced till the omap4's bootrom. However there
> are now patches to boot the beagle/beaglexm (omap34xx/dm3730) from
> extX via u-boot. But, there's not enough sram for both vfat & extX so
> it's a choice you need to make.
Oh interesting, so that means we can put the u-boot/MLO on a ext4
/boot partition (partition 1) and have it work? If not how does this
work?
Build u-boot with "CONFIG_SPL_EXT_SUPPORT" enabled:
http://git.denx.de/?p=u-boot.git;a=commit;h=592f922261993bad8cfb96395342e...
Here's the notes:
http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/196158
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
2:24 p.m.
On 12/16/14 9:29 AM, Robert Nelson wrote:
On Tue, Dec 16, 2014 at 2:20 AM, Peter Robinson
<pbrobinson(a)gmail.com> wrote:
> On Thu, Dec 11, 2014 at 1:50 AM, Robert Nelson <robertcnelson(a)gmail.com>
wrote:
>> On Wed, Dec 10, 2014 at 6:54 PM, Peter Robinson <pbrobinson(a)gmail.com>
wrote:
>>> On Wed, Dec 10, 2014 at 10:15 PM, Scott M. Jones <scott(a)aprr.org>
wrote:
>>>> I have a Beagleboard XM rev B and needed a VFAT boot partition in order
>>>> to boot. Will these be provided for F21 and are they still needed?
>>>
>>> The VFAT images are no longer provided. It should be possible, like on
>>> the OMAP4/am33xx devices, to write the uboot to an offset on the root
>>> of the drive, there's about 2mb left free at the beginning of the ARM
>>> images to enable this, and get uboot to work. I've looked very briefly
>>> at this on my xM and started to read docs to see if there was any
>>> difference between the SoCs but I've not got very far as I've had
>>> other more pressing things.
>>
>> RAW mode wasn't introduced till the omap4's bootrom. However there
>> are now patches to boot the beagle/beaglexm (omap34xx/dm3730) from
>> extX via u-boot. But, there's not enough sram for both vfat & extX so
>> it's a choice you need to make.
>
> Oh interesting, so that means we can put the u-boot/MLO on a ext4
> /boot partition (partition 1) and have it work? If not how does this
> work?
Build u-boot with "CONFIG_SPL_EXT_SUPPORT" enabled:
http://git.denx.de/?p=u-boot.git;a=commit;h=592f922261993bad8cfb96395342e...
Here's the notes:
http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/196158
I've tried to recompile u-boot and I don't have it working yet. Using
the latest git clone I've tried this for configs/omap3_beagle_defconfig:
CONFIG_SPL=y
CONFIG_SYS_EXTRA_OPTIONS="NAND"
CONFIG_SPL_EXT_SUPPORT=y
CONFIG_SPL_FAT_SUPPORT=n
+S:CONFIG_ARM=y
+S:CONFIG_OMAP34XX=y
+S:CONFIG_TARGET_OMAP3_BEAGLE=y
and also this:
CONFIG_SPL=y
CONFIG_SYS_EXTRA_OPTIONS="NAND"
+S:CONFIG_ARM=y
+S:CONFIG_OMAP34XX=y
+S:CONFIG_TARGET_OMAP3_BEAGLE=y
+S:CONFIG_SPL_EXT_SUPPORT=y
+S:CONFIG_SPL_FAT_SUPPORT=n
Is this the right way to turn off FAT support? Neither way boots to a
u-boot prompt.
Also, the working F20 image starts partition 1 on cylinder 1953:
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 1953 41015 39063 19.1M c W95 FAT32 (LBA)
/dev/sdb2 41016 1041015 1000000 488.3M c W95 FAT32 (LBA)
/dev/sdb3 1041016 61497343 60456328 28.8G 83 Linux
whereas for F21 it starts on 2048.
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 1001471 999424 488M 83 Linux
/dev/sdc2 1001472 2001953 1000482 488.5M 83 Linux
/dev/sdc3 2001954 9814453 7812500 3.7G 83 Linux
Fdisk doesn't let me change it to before 2048. Does MLO need to be on
the disk before sector 2048?
Thanks,
Scott
7:14 p.m.
Success!!
For U-boot I found I needed to change include/configs/omap3_beagle.h
instead of configs/omap3_beagle_defconfig and added:
#define CONFIG_SPL_EXT_SUPPORT
#undef CONFIG_SPL_FAT_SUPPORT
However, I could not get MLO to load from any ext partition on the SD
card. I went back to adding a new VFAT slice and now I'm just using the
"stock" MLO/u-boot.img from /usr/share/uboot/beagle.
I did: fdisk -c=dos /dev/(device) and added a partition from sectors 32
to 2047. I deleted other partitions first and recreated them so that
the VFAT partition is slice 1. Then I copied MLO and u-boot.img to the
VFAT slice and added the uEnv.txt I was using with F20 and a few small
changes, and it boots now.
Now running F21 LXDE on Beagleboard XM rev B. Tried KDE but it is
really slow...
Problems:
- The boot process was hanging after complaining about not able to
enumerate USB devices. After a few minutes it went into emergency mode
(root shell on initramfs). After booting several times I finally got to
a multi-user login. Once I ran yum update and booted from the new
kernel, this problem disappeared.
- LXDE GUI logout doesn't work; nothing happens. Shutdown and restart
from the GUI are OK. Killing LXDM is the workaround.
On 1/20/15 3:24 PM, Scott M. Jones wrote:
On 12/16/14 9:29 AM, Robert Nelson wrote:
> On Tue, Dec 16, 2014 at 2:20 AM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> On Thu, Dec 11, 2014 at 1:50 AM, Robert Nelson <robertcnelson(a)gmail.com>
wrote:
>>> On Wed, Dec 10, 2014 at 6:54 PM, Peter Robinson <pbrobinson(a)gmail.com>
wrote:
>>>> On Wed, Dec 10, 2014 at 10:15 PM, Scott M. Jones <scott(a)aprr.org>
wrote:
>>>>> I have a Beagleboard XM rev B and needed a VFAT boot partition in
order
>>>>> to boot. Will these be provided for F21 and are they still needed?
>>>>
>>>> The VFAT images are no longer provided. It should be possible, like on
>>>> the OMAP4/am33xx devices, to write the uboot to an offset on the root
>>>> of the drive, there's about 2mb left free at the beginning of the
ARM
>>>> images to enable this, and get uboot to work. I've looked very
briefly
>>>> at this on my xM and started to read docs to see if there was any
>>>> difference between the SoCs but I've not got very far as I've
had
>>>> other more pressing things.
>>>
>>> RAW mode wasn't introduced till the omap4's bootrom. However there
>>> are now patches to boot the beagle/beaglexm (omap34xx/dm3730) from
>>> extX via u-boot. But, there's not enough sram for both vfat & extX
so
>>> it's a choice you need to make.
>>
>> Oh interesting, so that means we can put the u-boot/MLO on a ext4
>> /boot partition (partition 1) and have it work? If not how does this
>> work?
>
> Build u-boot with "CONFIG_SPL_EXT_SUPPORT" enabled:
>
> http://git.denx.de/?p=u-boot.git;a=commit;h=592f922261993bad8cfb96395342e...
>
> Here's the notes:
>
> http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/196158
I've tried to recompile u-boot and I don't have it working yet. Using
the latest git clone I've tried this for configs/omap3_beagle_defconfig:
CONFIG_SPL=y
CONFIG_SYS_EXTRA_OPTIONS="NAND"
CONFIG_SPL_EXT_SUPPORT=y
CONFIG_SPL_FAT_SUPPORT=n
+S:CONFIG_ARM=y
+S:CONFIG_OMAP34XX=y
+S:CONFIG_TARGET_OMAP3_BEAGLE=y
and also this:
CONFIG_SPL=y
CONFIG_SYS_EXTRA_OPTIONS="NAND"
+S:CONFIG_ARM=y
+S:CONFIG_OMAP34XX=y
+S:CONFIG_TARGET_OMAP3_BEAGLE=y
+S:CONFIG_SPL_EXT_SUPPORT=y
+S:CONFIG_SPL_FAT_SUPPORT=n
Is this the right way to turn off FAT support? Neither way boots to a
u-boot prompt.
Also, the working F20 image starts partition 1 on cylinder 1953:
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 1953 41015 39063 19.1M c W95 FAT32 (LBA)
/dev/sdb2 41016 1041015 1000000 488.3M c W95 FAT32 (LBA)
/dev/sdb3 1041016 61497343 60456328 28.8G 83 Linux
whereas for F21 it starts on 2048.
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 1001471 999424 488M 83 Linux
/dev/sdc2 1001472 2001953 1000482 488.5M 83 Linux
/dev/sdc3 2001954 9814453 7812500 3.7G 83 Linux
Fdisk doesn't let me change it to before 2048. Does MLO need to be on
the disk before sector 2048?
Thanks,
Scott
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
3377
days inactive
3425
days old
6 comments
3 participants
participants (3)
-
Peter Robinson -
Robert Nelson -
Scott M. Jones