Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bob]

Well........perhaps I was a bit too optimistic.  If I am a glutton for punishment (and you appear to be more correct about that than I was willing to consider), my current device seems more than up to the task.  Last night, I put a fresh Jessie image on a 64G card, booted the 'bone right up, expanded the file system on the card to its full size, and installed JRMC21.  The MC window still opens as a white patch, although it does have the blue strip across the top now.  So I went into /etc/X11/xorg.conf and changed the default depth from 16 to 24 in the "screen" section, resulting in brick city once again.  A web search reveals many such posts, so it's not just me or my device.  It appears that changing that value really messes something up.

Yet another fresh image on a fully reformatted card brought everything back to life with a white MC window once again. I haven't yet left it open and looked on my main MC PC or JRemote to see if the 'bone's instance is working.  If it is, I'm fine running headless and will leave it alone. That's tonight's entertainment.   

There has to be somewhere other than the X11 conf file where you set the depth. The hardware has to boot with 24 bit support or the conf file won't be able to make it work.
That's the point of the parameters in the Rpi's boot.txt file.

[newbluesman]

As expected, it shows up as a zone in MC on my primary PC, and it's controllable both from there are from JRemote. So I'm not even going to bother trying to find the configuration file that will allow me to change the default bit depth for the display to 24.  If anyone lets me know what it is and where it is, I'll go in and give it a shot - but I run the 'bone headless anyway, so this isn't a problem. In fact, it may have been happening all along - the HDMI output didn't work when I first got it, so I never put it on a display. There were apparently a lot of early problems with the video drivers that have been fixed in recent software updates.

Thanks for the input!!

David

[newbluesman]

From Robert Nelson on the Beaglebone Black forum and one of the most experienced authorities on the 'bone in the universe:  "This is a hardware limitation of the beaglebone black in it's default state... The HDMI framer chip used is only wired to the am335x in 16bit mode" - 'nuf said!  That's why it won't boot when the X11 conf file is changed to 24 from 16.

So I'll set MC on the Beaglebone Black with TightVNC and run it headless (which I did without difficulty last year). We live and learn. 

[mwillems]

Bob, is there an .88 build coming for arm?  I only ask because my pi's are still back at .83 due to the library server bug in .85.

[bob]

Bob, is there an .88 build coming for arm?  I only ask because my pi's are still back at .83 due to the library server bug in .85.

Yes, it just takes longer to build and we found one more thing we want to change first. I'm thinking later today...

[bob]

Bob, is there an .88 build coming for arm?  I only ask because my pi's are still back at .83 due to the library server bug in .85.

Ready to DL.
See the comment in the top build about the calling of external programs...