BBB-eMMC Changes in uEnv.txt not considered

Hello,

I have a beagleboard black and flashed it yesterday to BBB-eMMC-flasher-2013.06.20.img. After fiddling around with it a little while (disable root ssh, creating an account for myself, stting up ntpd and timezone, disabling gdm an cloud9 startup)

I wanted the dmesg output whitout the drm debug:

[drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2

looking around on the net I found that I had to edit my uEnv.txt and remove the drm.debug=7 option

so I typed

cat /proc/cmdline >> /boot/uEnv.txt

and edited /boot/uEnv.txt to:

root@beaglebone:~# cat /boot/uEnv.txt
optargs=console=ttyO0,115200n8 quiet root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait
root@beaglebone:~#

but I stil got the drm debug output after rebooting

also after rebooting the cmdline stay’s the same:
root@beaglebone:~# cat /proc/cmdline
console=ttyO0,115200n8 quiet drm.debug=7 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait
root@beaglebone:~#

it looks like the /boot/uEnv.txt is not considered while booting from eMMc (the internal memory)

Should I reflash the image from sd but edit the uEnv.txt on the sdCard first? (to me it looks like this)

Can anyone help me with this?

btw I boot from the internal eMMC and there is no micro sdCard inserted

You are editing the wrong uEnv.txt. The uEnv.txt file in /boot is put
there as a trap for new users (as far as I can tell).

You need to mount the FAT partition of the EMMC, and edit *THAT*
uEnv.txt file. The FAT partition will frequently be mounted as
/media/BEAGLEBONE, but you should check the output of mount, df, and
fdisk -l to make *SURE* you are editing the proper file.

that would be my understanding as well. i'm looking at the env on my
BBB, and it contains this:

bootdir=/boot
bootenv=uEnv.txt
...
fdtfile=am335x-boneblack.dtb
...
loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootenv}
loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
...

which i interpret (unless i'm misreading something badly) that the
uEnv.txt file is read from the FAT partition, but the fdt file is read
from the root filesystem under /boot. am i reading that correctly?

rday

p.s. you could, of course, change u-boot's environment to read
uEnv.txt from /boot, correct? i haven't done that, just want to make
sure there's nothing magic about that.

You where right, thank you.

/media/Beaglebone did not exist
and df did not show the mounted fat partition
fdisk -l showed all partitions :
fdisk -l

Disk /dev/mmcblk0: 1920 MB, 1920991232 bytes
255 heads, 63 sectors/track, 233 cylinders, total 3751936 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
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 63 144584 72261 c W95 FAT32 (LBA)
/dev/mmcblk0p2 144585 3743144 1799280 83 Linux

Disk /dev/mmcblk0boot1: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2048 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

Disk /dev/mmcblk0boot0: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders, total 2048 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

so I mounted the first partition

mkdir /mnt/fatpartition
mount /dev/mmcblk0p1 /mnt/fatpartition
edited uEnv.txt and removed the drm debug option ( vi /mnt/fatpartition/uEnv.txt)
unmounted /dev/mmcblk0p1 (umount /mnt/fatpartition)
removed the mount point (rmdir /mnt/fatpartition)
and rebooted … et voila… no more drm debug messsages in dmesg

Thank you!

i may be about to make a total fool of myself for asking this, but
is there a way to tweak u-boot to read from the uEnv.txt file under
/boot (which i think would be more convenient if you're playing
around) if you don't have access to the serial console to allow you
to stop in u-boot to adjust and save the environment?

  currently, on shipping BBBs, the env contains:

...
bootdir=/boot
bootenv=uEnv.txt
...
loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootenv}
...

so on a normal boot, u-boot will read its additional environment from
uEnv.txt in the FAT partition. so far, so good. so if you boot fully
to linux, you can make sure the FAT partition is mounted, and you can
edit that uEnv.txt to add some customization.

  but how could you tell u-boot to, instead, consult /boot/uEnv.txt
instead? if you simply edited the one under the FAT partition, well,
then it's already been consulted. the obvious solution would be to
change:

loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootenv}

to:

loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootdir}/${bootenv}

but, again, simply adding that to uEnv.txt wouldn't seem to make any
difference as uEnv.txt has already been sourced.

  am i missing something obvious? the ideal solution for me would be
for u-boot to read *both* files but, again, can i make that happen
with no access to the serial port and no ability to stop in u-boot?

rday