Hi William,
I got it working. It seemed that I forgot that my e2fsprogs version was
greater then 1.43.
As mentioned in the guide (do'h bangs head against table)
Create the ext4 filesystem:
1. For e2fsprogs < 1.43:
mkfs.ext4 /dev/sdX1
2. For e2fsprogs >= 1.43:
mkfs.ext
Damn.. You have been busy whilst I was away.
The uEnv mentioned in my previous post was one when I tried to mount the
boot as a fat 16 image, so in that setup there where two partitions. The
uEnv that I have currently and that is the default Arch Linux Uenv only has
one line:
Correction:
loaduimage=if ext4load mmc 0:2 ${loadaddr} /boot/zImage; then setenv mmcdev
0; else setenv mmcdev 1; if test $mmc0 = 1; then setenv mmcroot
/dev/mmcblk1p2 rw; fi; ext4load mmc 1:2 ${loadaddr} /boot/zImage; fi
*should be:*
loaduimage=if ext4load mmc 0:1 ${loadaddr} /boot/zImage; then se
So . . .
mmcroot=/dev/mmcblk0p2 rw
*should be:*
mmcroot=/dev/mmcblk0p*1* rw
loadfdt=ext4load mmc ${mmcdev}:2 ${fdtaddr} /boot/dtbs/${fdtfile}
*should be:*
loadfdt=ext4load mmc ${mmcdev}:*1* ${fdtaddr} /boot/dtbs/${fdtfile}
loaduimage=if ext4load mmc 0:2 ${loadaddr} /boot/zImage; then setenv mmcd
By the way, ${uname_r} is defined in the second stage uEnv.txt file that
comes with recent debian images. But It does not look as though the people
at ARCH uses this file structure. So while these paths should be similar,
they're going to be slightly different for you. But if you look at the
uEnv,t
Here, here is a stage one uEnv.txt file fro the latest official debian
image. Note the differences in disk / partition assingment. But otherwise
this uses the same layout for what I can tell as those ARCH instructions
imply.
william@beaglebone:~/dev$ cat /uEnv.txt
##These are needed to be complian
Ok, actually looking at those instructions. They're wrong for that uEnv.txt
file you have.
uenvcmd=run findfdt; if test $board_name = A335BNLT; then i2c mw 0x24 1
0x3e; setenv mmcdev 1; mmc dev ${mmcdev}; if mmc rescan; then setenv mmc1
1;else setenv mmc1 0;fi;fi;setenv mmcdev 0; mmc dev ${mmcdev}
No the arch image is on ext4 partition where the u-boot is created using:
dd if=mnt/boot/MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k
dd if=mnt/boot/u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k
This is new for me as well.
Op woensdag 13 juli 2016 22:39:42 UTC+2 schreef Will
Is that mount on partition 2 ?
On Wed, Jul 13, 2016 at 1:35 PM, Jelle Spijker
wrote:
> drwxr-xr-x 2 root root 4.0K Jul 1 03:57 dtbs
> -rw-r--r-- 1 root root 74K Jun 8 2015 MLO
> -rw-r--r-- 1 root root 389K Jun 8 2015 u-boot.img
> -rw-r--r-- 1 root root 104 Jul 13 22:03 uEnv.txt
> -rwx
drwxr-xr-x 2 root root 4.0K Jul 1 03:57 dtbs
-rw-r--r-- 1 root root 74K Jun 8 2015 MLO
-rw-r--r-- 1 root root 389K Jun 8 2015 u-boot.img
-rw-r--r-- 1 root root 104 Jul 13 22:03 uEnv.txt
-rwxr-xr-x 1 root root 5.2M Jul 1 03:57 zImage
Op woensdag 13 juli 2016 22:22:38 UTC+2 schreef Wil
So . . . put sdcard into another Linux machine. Then . . .
sudo mount /dev/sdxx /media/rootfs
ls /media/rootfs/boot
What output do you get ?
On Wed, Jul 13, 2016 at 1:16 PM, Jelle Spijker
wrote:
> Hello,
>
> I'm trying to install Arch on my BBB rev C. using the described method on
> https://ar
Hello,
I'm trying to install Arch on my BBB rev C. using the described method on
https://archlinuxarm.org/platforms/armv7/ti/beaglebone-black but it can't
find my zImage, whilst it is present in the boot folder. It hangs while the
two outer LEDS are on with the following message. I also poste
12 matches
Mail list logo
