has anyone flashed and booted test-only-not-for-production-BBB-eMMC-flasher-2013.05.12.img.xz?

GoogleGroups
21

Just click on “CLOSE” to make the box go away.

Gerald

22

there is no "CLOSE" button ... oh, wait, i hit "Cancel" and, after
quite a pause, i was asked about Language choice. so it's going
through a firstboot process? that makes sense. so i answered that and
... back to long pause with empty grey screen in middle of display.

  this never happened with any of the earlier flasher images ... oh,
wait, empty grey square just got larger ... asking me for "Languages"
and giving me only one choice, "English (United States)", so i'll
select that and press "OK" and ... (another long pause) ... back to
small grey square ... it seems like it's going through a standard
firstboot process but it's ***interminably*** slow about it.

  i'll just let it run and see what happens while i work on something
else...

rday

23

I couldn’t remember the exact wording. My sincerest apologies!

It happens to me all the time. It seems to get triggered by hitting the reset button instead of shutting down. As I said, it happens to me all the time. An annoyance but currently way down my list of annoyances.

I never login. I never mess with languages.

Gerald

24

currently, dmesg is generating a new message every 10 seconds:

[ 763.156913] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 773.188192] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 783.219442] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 793.250590] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 803.281935] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 813.313701] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 823.344448] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
[ 833.375684] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 1 to 1
... etc ...

   is that expected as part of "drm.debug=7"?

rday

25

I have no idea. I have never seen it before. Must be a new feature.

Gerald

26

gaaaah ... i rebooted one more time and got the desktop just fine. i
have no idea what all that was about before. desktop still has the
jitter so, at this point, i think i'll just put this aside and take a
break.

rday

27

I have no idea as well.

Gerald