Ah, and right. This value can be modified in order to reflect a known
working kernel. Or "point" to a known working kernel. If you know what
you're doing . . . Which is not very simple to explain but not overly hard
either. For instance:

$ ls /boot/
SOC.sh                        config-4.4.14-ti-r34
initrd.img-4.4.14-ti-r34      uboot
System.map-4.4.14-ti-r34      config-4.4.14-ti-rt-r34
initrd.img-4.4.14-ti-rt-r34   vmlinuz-4.4.14-ti-r34
System.map-4.4.14-ti-rt-r34   config-4.4.8-ti-r22
initrd.img-4.4.8-ti-r22       vmlinuz-4.4.14-ti-rt-r34
System.map-4.4.8-ti-r22       config-4.4.9-bone-rt-r10
initrd.img-4.4.9-bone-rt-r10  vmlinuz-4.4.8-ti-r22
System.map-4.4.9-bone-rt-r10  dtbs
uEnv.txt                      vmlinuz-4.4.9-bone-rt-r10


$ ls /boot/dtbs/
4.4.14-ti-r34  4.4.14-ti-rt-r34  4.4.8-ti-r22  4.4.9-bone-rt-r10

As you can see I have the possibility to load any of these 4 kernel
directory "trees" that I show listed in my last command. simply by editing
the "uname_r" parameter in the /boot.uEnv.txt file.

On Mon, Sep 19, 2016 at 3:07 PM, William Hermans <yyrk...@gmail.com> wrote:

> On Mon, Sep 19, 2016 at 2:53 PM, Dennis Lee Bieber <wlfr...@ix.netcom.com>
> wrote:
>> On Sun, 18 Sep 2016 21:19:49 -0700 (PDT), Viswadeep Sarangi
>> <deepun.d...@gmail.com> declaimed the
>> following:
>>         {I was running late getting to work and missed this part}
>> >The contents of the FAT partition include :
>> >- a "dtbs" directory, which contains a lot of .dtb files
>> >- uEnv.txt
>> >- zImage file
>> >
>>         If the card isn't booting off the SD card, you might have to
>> examine
>> that uEnv.txt file for things that may be erroneous, since (as I
>> understand
>> things) it defines some of the stuff used by u-Boot to get to the rest of
>> the OS.
> At minimum:
> $ cat /boot/uEnv.txt | grep uname
> uname_r=4.4.14-ti-r34
> This is needed in order to find. . . I forget off the top of my head, but
> for instance, it refers to the kernel version you wish to run. So without
> this set, the default 1st stage uEnv.txt file wont know where to look for
> the kernel, and probably the board file device tree overlay.
> This is really easy to check on a Linux system, but would require
> *something* in order for Windows to read ext4 file systems.

For more options, visit http://beagleboard.org/discuss
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to