Creating The SGX Driver For Ubuntu 14.04

[Nick Apperley]

Been trying to compile the SGX driver for Ubuntu 14.04 so that a sample JavaFX 8 program can run, which requires OpenGLES 2.0 support from the video driver. So far various methods have been used in an attempt to create the driver without any luck. At the moment the most promising method on the JavaFX 8 on BeagleBone Black (SGX driver problem?) thread has hit a major hurdle. Getting the following errors when building the video driver:

make BUILD=release OMAPES=8.x PM_RUNTIME=1 all

building the sgx kernel modules...

make[1]: Entering directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make[1]: Leaving directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make[1]: Entering directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make -C /home/a_user/repos/bbb_kernel/kernel M=`pwd` 

make[2]: Entering directory `/home/a_user/repos/bbb_kernel/kernel'

  ERROR: Kernel configuration is invalid.

         include/generated/autoconf.h or include/config/auto.conf are missing.

         Run 'make oldconfig && make prepare' on kernel src to fix it.

  WARNING: Symbol version dump /home/a_user/repos/bbb_kernel/kernel/Module.symvers

           is missing; modules will have no dependencies and modversions.

  LD      /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/built-in.o

  CC [M]  /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.o

In file included from <command-line>:0:0:

/home/a_user/repos/bbb_kernel/kernel/include/linux/kconfig.h:4:32: fatal error: generated/autoconf.h: No such file or directory

 #include <generated/autoconf.h>

                                ^

compilation terminated.

make[4]: *** [/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.o] Error 1

make[3]: *** [/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/bufferclass_ti] Error 2

make[2]: *** [_module_/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM] Error 2

make[2]: Leaving directory `/home/a_user/repos/bbb_kernel/kernel'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make: *** [buildkernel] Error 2

[Nick Apperley]

Link to BeagleBone Black (SGX driver problem?) thread.

[Robert Nelson]

Don't make me waste time by hardcoding some random check in
"./sgx_build_modules.sh" that you didn't run "./build_kernel.sh"
first..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

[Nick]

Where do I find build_kernel.sh file? Can't find the file via a Nemo search. Exactly which kernel are you referring to? I am using the kernel referred to in this eLinux page.

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/vHmA5ZuYoHw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robert Nelson]

On Mon, Jun 16, 2014 at 5:01 PM, Nick <napp...@gmail.com> wrote:
> Where do I find build_kernel.sh file? Can't find the file via a Nemo search.
> Exactly which kernel are you referring to? I am using the kernel referred to
> in this eLinux page.

Okay, so you aren't following the directions from the first post in
that thread you posted..

Look at your error:

> ERROR: Kernel configuration is invalid.
> include/generated/autoconf.h or include/config/auto.conf are missing.
> Run 'make oldconfig && make prepare' on kernel src to fix it.

Either, KERNEL_INSTALL_DIR is setup wrong, or you haven't run "make
ARCH=arm zImage modules dtbs" on your kernel sources yet.

[Nick]

Ran make ARCH=arm zImage modules dtbs but encountered errors. Below are the error messages:

gcc: error: unrecognized argument in option ‘-mabi=aapcs-linux’

gcc: note: valid arguments to ‘-mabi=’ are: ms sysv

gcc: error: unrecognized command line option ‘-mlittle-endian’

gcc: error: unrecognized command line option ‘-mno-thumb-interwork’

gcc: error: unrecognized command line option ‘-mthumb’

make[1]: *** [kernel/bounds.s] Error 1

make: *** [prepare0] Error 2

[Robert Nelson]

On Mon, Jun 16, 2014 at 5:42 PM, Nick <napp...@gmail.com> wrote:
> Ran make ARCH=arm zImage modules dtbs but encountered errors. Below are the
> error messages:
>
> gcc: error: unrecognized argument in option ‘-mabi=aapcs-linux’
> gcc: note: valid arguments to ‘-mabi=’ are: ms sysv
> gcc: error: unrecognized command line option ‘-mlittle-endian’
> gcc: error: unrecognized command line option ‘-mno-thumb-interwork’
> gcc: error: unrecognized command line option ‘-mthumb’
> make[1]: *** [kernel/bounds.s] Error 1
> make: *** [prepare0] Error 2

make ARCH=arm CC=yadaya zImage modules dtbs

Just a heads up, I'm not planning to walk you thru every step. As it's
futile, it only works in qt with the embedded stack.

[Nick]

Ran make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage dtbs which is working so far. Don't know how long it will take to compile the kernel on a Core 2 Duo laptop though.

[Nick]

Received the following error messages while compiling the kernel modules:

net/wireless/regdb.c:1551:1: error: expected expression before ‘const’

 const struct ieee80211_regdomain *reg_regdb[] = {

 ^

make[2]: *** [net/wireless/regdb.o] Error 1

make[1]: *** [net/wireless] Error 2

make: *** [net] Error 2

[Robert Nelson]

On Mon, Jun 16, 2014 at 7:14 PM, Nick <napp...@gmail.com> wrote:
> Received the following error messages while compiling the kernel modules:
>
> net/wireless/regdb.c:1551:1: error: expected expression before ‘const’
> const struct ieee80211_regdomain *reg_regdb[] = {
> ^
> make[2]: *** [net/wireless/regdb.o] Error 1
> make[1]: *** [net/wireless] Error 2
> make: *** [net] Error 2

fixed

https://github.com/beagleboard/kernel/commit/47045103571894cd516e6af6e6780d594c59cfcc

[Nick]

Thanks. Encountered errors when trying to build the video driver using make BUILD=release OMAPES=8.x PM_RUNTIME=1 all. Below is the output:

building the sgx kernel modules...

make[1]: Entering directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make[1]: Leaving directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make[1]: Entering directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make -C /home/a_user/repos/bbb_kernel/kernel M=`pwd` 

make[2]: Entering directory `/home/a_user/repos/bbb_kernel/kernel'

  LD      /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/built-in.o

  CC [M]  /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bc_cat.o

  LD [M]  /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/bufferclass_ti/bufferclass_ti.o

  LD      /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/built-in.o

  CC [M]  /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_displayclass.o

  CC [M]  /home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.o

/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c: In function ‘OMAPLFBWaitForVSync’:

/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:7: error: implicit declaration of function ‘register_vsync_cb’ [-Werror=implicit-function-declaration]

       if (register_vsync_cb((vsync_callback_t)grpx_irq_wait_handler, &completion, psDevInfo->uiFBDevID) != 0)

       ^

/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:30: error: ‘vsync_callback_t’ undeclared (first use in this function)

       if (register_vsync_cb((vsync_callback_t)grpx_irq_wait_handler, &completion, psDevInfo->uiFBDevID) != 0)

                              ^

/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:30: note: each undeclared identifier is reported only once for each function it appears in

/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:47: error: expected ‘)’ before ‘grpx_irq_wait_handler’

       if (register_vsync_cb((vsync_callback_t)grpx_irq_wait_handler, &completion, psDevInfo->uiFBDevID) != 0)

                                               ^

/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:716:7: error: implicit declaration of function ‘unregister_vsync_cb’ [-Werror=implicit-function-declaration]

       if (unregister_vsync_cb((vsync_callback_t)grpx_irq_wait_handler , &completion, psDevInfo->uiFBDevID) != 0)

       ^

/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:716:49: error: expected ‘)’ before ‘grpx_irq_wait_handler’

       if (unregister_vsync_cb((vsync_callback_t)grpx_irq_wait_handler , &completion, psDevInfo->uiFBDevID) != 0)

                                                 ^

cc1: some warnings being treated as errors

make[4]: *** [/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.o] Error 1

make[3]: *** [/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux] Error 2

make[2]: *** [_module_/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM] Error 2

make[2]: Leaving directory `/home/a_user/repos/bbb_kernel/kernel'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/a_user/Graphics_SDK_5_01_00_01/GFX_Linux_KM'

make: *** [buildkernel] Error 2

[Robert Nelson]

Fixed that in my v3.13.x tree:

https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.13/patches/sgx/0005-hack-port-da8xx-changes-from-ti-3.12-repo.patch

[Nick]

BBB is currently running Ubuntu 14.04 with the 3.13 kernel. Is it possible to just install the SGX module to the BBB once the module is built?

[Nick]

Tried building the kernel maintained by Robert Nelson using the build_kernel file and ended up with a failed dependency check error. Below is the output:

+ Detected build host [Linux Mint 17 Qiana]

+ host: [i686]

+ git HEAD commit: [03ed3adc765644274981c461d25d1e576adceeff]

Dependency check skipped, you are on your own.

-----------------------------

Unrecognized deb based system:

-----------------------------

Please cut, paste and email to: bugs@rcn-ee.com

-----------------------------

git: 03ed3adc765644274981c461d25d1e576adceeff

uname -m

i686

lsb_release -a

LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:core-4.1-ia32:core-4.1-noarch:security-4.0-ia32:security-4.0-noarch:security-4.1-ia32:security-4.1-noarch

Distributor ID: LinuxMint

Description: Linux Mint 17 Qiana

Release: 17

Codename: qiana

-----------------------------

* Failed dependency check

[Nick]

Does build_kernel.sh correctly detect a PC running Ubuntu 14.04? Linux Mint 17 uses Ubuntu 14.04 as its base.

[William Hermans]

Linux mint and Linux mint debian edition are probably the two worst distro's to use for cross compiling. I recommend using Debian as the cross compile system, but I also run Debian on my Beaglebone Black.
The thing is, you're going to run into loads of trouble if you don't.

I suppose Ubuntu could work too, but Linux mint is based off of Debian testing ( at least for Debian edition ), and the packages used between stable, and testing are often not the same. So, you can use Debian as your cross system, *OR* you're going to be on your own. No one on this group is going to make a full time job of helping you do what you want to achieve.

 
That's not me being a smart-ass or being funny. That is the cold hard truth.

Dependency check skipped, you are on your own.

-----------------------------

Unrecognized deb based system:

-----------------------------

The above says it all.

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...@googlegroups.com.

[William Hermans]

Also, for what it is worth. If you have a problem using Debian as your desktop system, that is fine. You can use virtualbox to run Debian in a VM. Which works perfectly fine, and is also exactly what I do.

[Robert Nelson]

On Mon, Jun 16, 2014 at 8:34 PM, Nick <napp...@gmail.com> wrote:
> Tried building the kernel maintained by Robert Nelson using the build_kernel
> file and ended up with a failed dependency check error. Below is the output:
>
> + Detected build host [Linux Mint 17 Qiana]
> + host: [i686]
> + git HEAD commit: [03ed3adc765644274981c461d25d1e576adceeff]
> Dependency check skipped, you are on your own.
> -----------------------------
> Unrecognized deb based system:
> -----------------------------

> Please cut, paste and email to: bu...@rcn-ee.com

> -----------------------------
> git: 03ed3adc765644274981c461d25d1e576adceeff
> uname -m
> i686
> lsb_release -a
> LSB Version:
> core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:core-4.1-ia32:core-4.1-noarch:security-4.0-ia32:security-4.0-noarch:security-4.1-ia32:security-4.1-noarch
> Distributor ID: LinuxMint
> Description: Linux Mint 17 Qiana
> Release: 17
> Codename: qiana
> -----------------------------
> * Failed dependency check

all synced up:

https://github.com/RobertCNelson/bb-kernel/commit/5b1bee1b83112928ff4cecc0fb343ee5d5c7f72b

(i really should have had all the scripts in a separate repo 5 years
ago, but it's easy to sync up with meld.. ;) )

[Robert Nelson]

Atleast Mint is staying on 14.04 for awhile now, they are
traditionally a little laggy on naming their release, so i didn't know
it was equal to trusty till around this date:

https://github.com/RobertCNelson/stable-kernel/commit/9eb0b648e3d274bb23e6a595245ded6939cc4c4d

[William Hermans]

Well, you know I am not a big fan of Ubuntu. My own personal experiences with it was several years ago, and it wound up going similar to how it seems to be going for Nick here. Which is why l left Angstrom in the ditch over a year ago.

e.g. I do not want an OS that argues with me, or wants to fight at every step i take in a custom direction.

--
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...@googlegroups.com.

[Robert Nelson]

On Mon, Jun 16, 2014 at 9:05 PM, William Hermans <yyr...@gmail.com> wrote:
> Well, you know I am not a big fan of Ubuntu. My own personal experiences
> with it was several years ago, and it wound up going similar to how it seems
> to be going for Nick here. Which is why l left Angstrom in the ditch over a
> year ago.
>
> e.g. I do not want an OS that argues with me, or wants to fight at every
> step i take in a custom direction.

Yeah, i still remember their last great release... Maverick.. Moved
everything to debian shortly after..

[Nick]

My own experience with Ubuntu 12.04 on a Tecra M9 wasn't pleasant when it came to the stability of the NVidia GPU using the open source driver. Every so often X Server would freeze either at the login screen or when logging in, if that wasn't the case then it may occur with the next reboot. Using the official NVidia driver was far, far, far worse with X Server freezing once every 10 seconds every time the laptop was running.

Since switching to Linux Mint 17 on the Tecra absolutely no problems have occurred with the stability of the NVidia GPU regardless of the driver used.

[William Hermans]

Nick,

That's good to hear. The problems I experienced were concerning iSCSI, and Xen running on the same system. I literally spent a week setting everything up only to have the whole setup fail silently on the last step. No recourse, no mention of this problem anywhere. This was back when Ubuntu 11 was new, and I think I was using 10.10 at the time. Needless to say I was seriously miffed after spending all this time on this task. In the end, sadly I wound up using Windows with Microsoft's initiator software. But at least It worked

Passed this, at least back then, and at least 1-2 new iteration of Ubuntu afterwards. Ubuntu's upgrade path was horrendous. Often breaking good, working installs, assuming it did not flat out fail to begin with. Then the last debacle that I bothered reading about. Putting google search on your desktop ? So when you search for files on your system you get results off the internet too ? Desktop adwords anyone ? At least this is what I read what was proposed . . .

Anyway, if you like Mint for a desktop I say more power to you. Just dont expect it to be a Swiss army knife of distro's. I would seriously suggest you put Debian in a VM as a support system for the beaglebone black. at the very least. Then, leave it as CLI only ( no X or any unnecessary stuff like that ). Your source building life should become much simpler / easier / better in the long run.

[Nick]

Ran build_kernel.sh again and have a Ncurses based screen shown with the title .config - Linux/arm 3.13.10 Kernel Configuration. What kernel configuration options need to be set?

[Robert Nelson]

On Jun 16, 2014 9:37 PM, "Nick" <napp...@gmail.com> wrote:
>
> Ran build_kernel.sh again and have a Ncurses based screen shown with the title .config - Linux/arm 3.13.10 Kernel Configuration. What kernel configuration options need to be set?

None, the defaults are setup in the repo. But it's still to show to easily change things.

> 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...@googlegroups.com.

[Nick]

William,

Some good advise to take on board for any future software build/support tasks for the BBB. Any issues that I need to be aware of when running Debian as a virtual machine in VirtualBox?

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/vHmA5ZuYoHw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

[John Syn]

I¹ve had issues with Ubuntu in the past, but I have to say 14.04 is pretty
good. I¹ve had no issues since I installed it back in April. On the other
hand, I had several problems trying to get Debian stable or Debian testing
working on my machine with Nvidia GTX670 with 3 x 30 Inch 2560x1600
monitors. I reverted back to Ubuntu 14.04 and I¹m really happy with it.

Regards,
John

>
>Regards,
>
>--
>Robert Nelson
>http://www.rcn-ee.com/
>

[William Hermans]

NIck, only that you need an sdcard reader that is supported as a USB device. That is so virtualbox can recognize it then present it the underlying OS. I forget the exact keywords I used to find the solution for setting it up also, but it was something like" how to sdcard in virtualbox". But there are instructions out there.

You'll also need enough diskspace ( around 30-40GB ) to "play" around with. Depending on what you want to achieve. Then some fairly decent ( basics ) knowledge where networking is concerned.

Once setup though, it is pretty much a regular system in every / most aspect. At least where usage is concerned.

[Nick]

Ubuntu 14.04 is certainly justified with using the code word "trusty".

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/vHmA5ZuYoHw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

[William Hermans]

The above written by me was with compiling uboot / the kernel in mind. There are defeinately other ways around this however. If the host system has access to these files, and the sdcard media( and you have the know how / ability to be creative ), then the sdcard "issue" I mentioned above is a non issue.

[Nick]

I do have a Transcend USB 2 microSD/SD reader/writer which works in Linux Mint. Hopefully VirtualBox will recognise the device.

[William Hermans]

Oh, one last thing I nearly forgot to mention. Use Debian Wheezy i386, and not the x64 variant. I usually start with the netinst ISO personally, but I am not afraid of the command line, and know exactly how I want Debian installed.

At the end where the installer asks which additional packages you want installed, deselect *EVERYTHING*, as it will install several packages of the same type crapping up the system.

then once you login for the first time issue

# apt-get update

# apt-get install sudo // if you want sudo

# apt-get install openssh-server

From here on, you should be able to ssh from your host to configure /  maintenance / use  the VM.

[Nick]

Have successfully built and installed the kernel to the BBB. The BBB is now using the new kernel however I see that glxinfo is reporting that the SGI (software video) driver is still being used.

[Nick]

Oops, I see that there is a script that needs to be executed to build the SGX video driver.

[Nick]

SGX video driver has been built successfully. How do I install the SGX module to the BBB?

[Robert Nelson]

On Jun 16, 2014 11:17 PM, "Nick" <napp...@gmail.com> wrote:
>
> SGX video driver has been built successfully. How do I install the SGX module to the BBB?

Copy the sgx tarball under deploy to your rootfs. Then sudo tar xf filename.tar -c /

cd /opt/gfxinstall/ (not 100% on the spelling)
Sudo ./install-sgx.sh
Reboot

And that's as far as we get, as we have no xorg, etc...

[Nick]

I'm assuming you are referring to GFX_5.01.01.01.tar.gz as the file to copy over to the BBB?

[Robert Nelson]

On Jun 16, 2014 11:29 PM, "Nick" <napp...@gmail.com> wrote:
>
> I'm assuming you are referring to GFX_5.01.01.01.tar.gz as the file to copy over to the BBB?

Heap that file, it contains the kernel modules, blob, etc.

[Nick]

Extracted the file that was copied over to the BBB and ran the installer. Encountered a file not found type error. Below is the error message:

chmod: cannot access '/etc/init.d/sgx-startup.conf': No such file or directory

[Robert Nelson]

On Mon, Jun 16, 2014 at 11:47 PM, Nick <napp...@gmail.com> wrote:
> Extracted the file that was copied over to the BBB and ran the installer.
> Encountered a file not found type error. Below is the error message:
>
> chmod: cannot access '/etc/init.d/sgx-startup.conf': No such file or
> directory

That's odd:

lsb_release -si should have came back with Ubuntu (it's like i never
test ubuntu anymore. ;) )

https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.13/3rdparty/sgx-install.sh#L178

Do the last part by hand..

sudo cp -v /opt/gfxinstall/scripts/sgx-startup-ubuntu.conf
/etc/init/sgx-startup.conf
sudo chown root:root /etc/init/sgx-startup.conf
sudo chmod +x /etc/init.d/sgx-startup.conf

Reboot..

[Nick]

Robert,

The instructions in the last post did the trick with loading the driver (omaplfb), thanks :)  However I have no clear way of telling if hardware rendering is being used. Running glxinfo reveals SGI once again :(   Is there an alternative CLI tool around that can provide details about the video driver that is used?

[Robert Nelson]

On Jun 17, 2014 12:11 AM, "Nick" <napp...@gmail.com> wrote:
>
> Robert,
>
> The instructions in the last post did the trick with loading the driver (omaplfb), thanks :)  However I have no clear way of telling if hardware rendering is being used. Running glxinfo reveals SGI once again :(   Is there an alternative CLI tool around that can provide details about the video driver that is used?

That's as far as I got.. What you have now is all that John needed to run qt 5.1 in ews? mode. I also think it's enough for Wayland egl mode, but don't have much to show for that yet either. So, that's as far as we got.

> 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...@googlegroups.com.

[Nick]

Ran glxgears and the tool reported an average of 32 FPS which is average. Before loading the driver the average was 28 FPS. CPU load is still around 100%, something seems a bit off......

[Nick Apperley]

Strange that the sample JavaFX 8 program still doesn't work even though it requires EGL 2.0 support from the video driver. Still getting the same errors like the following for example:

ant -f /home/a_user/NetBeans_Projects/JavaFX_Test -Dremote.platform.rp.target=linuxarmvfphflt-15 -Dremote.platform.password=***** -Dremote.platform.rp.filename=linuxarmvfphflt -Dremote.platform.java.spec.ver=18 run-remote

init:

Deleting: /home/a_user/NetBeans_Projects/JavaFX_Test/build/built-jar.properties

deps-jar:

Updating property file: /home/a_user/NetBeans_Projects/JavaFX_Test/build/built-jar.properties

compile:

Detected JavaFX Ant API version 1.3

jfx-deployment:

jar:

Connecting to xxx.xxx.xxx.xxx:22

cmd : mkdir -p '/home/ubuntu/NetBeans_Projects/JavaFX_Test/dist'

Connecting to xxx.xxx.xxx.xxx:22

done.

profile-rp-calibrate-passwd:

Connecting to xxx.xxx.xxx.xxx:22

cmd : cd '/home/ubuntu/NetBeans_Projects/JavaFX_Test'; '/home/ubuntu/ejre-1.8.0_fx/bin/java'  -Dfile.encoding=UTF-8   -jar /home/ubuntu/NetBeans_Projects/JavaFX_Test/dist/JavaFX_Test.jar 

libEGL warning: DRI2: xcb_connect failed

libEGL warning: DRI2: xcb_connect failed

libEGL warning: GLX: failed to load GLX

eglInitialize failed!

Graphics Device initialization failed for :  es2

Error initializing QuantumRenderer: no suitable pipeline found

[Robert Nelson]

Well, the demos: /opt/gfxsdkdemos/ogles2/

work:

https://plus.google.com/106813818225399872098/posts/ZC9TEYjJNfP

[Nick Apperley]

Tried running one of the demos remotely (via SSH) and ended up with error messages being spitted out (aka crash 'n' burn) like the following:

===========================================================

ubuntu@arm:/opt/gfxsdkdemos/ogles2$ ./OGLES2MagicLantern 

Can't open keypad input device (/dev/input/event0)

libEGL warning: DRI2: xcb_connect failed

libEGL warning: DRI2: xcb_connect failed

libEGL warning: GLX: failed to load GLX

Exit message has been set to: "PVRShell: Unable to initialise EGL

".

PVRShell: EGL Error (EGL_NOT_INITIALIZED)

InitAPI failed!

PVRShell: Unable to initialise EGL

===========================================================

Very similar error messages when trying to run the sample JavaFX 8 program remotely (via SSH). Robert can you please confirm if you can run one of the SGX demos (eg Magic Lantern) successfully, and post the results from running the fbset -i and es2_info commands (locally).

[Nick Apperley]

Ran a different demo locally and had different error messages appearing like the following:

=========================================================

ubuntu@arm:/opt/gfxsdkdemos/ogles2$ ./OGLES2ChameleonMan 

Can't open keypad input device (/dev/input/event0)

libEGL warning: DRI2: failed to authenticate

PVRShell: EGL 1.4 initialized

Exit message has been set to: "PVRShell: Unable to create surface

".

InitAPI failed!

PVRShell: Unable to create surface

=========================================================

When trying to run the sample JavaFX 8 program locally the same error message appears:

    libEGL warning: DRI2: failed to authenticate

I have a theory that if OpenGL ES 2.0 can be initialised successfully in one program then the sample JavaFX 8 program will run successfully.

[Robert Nelson]

On Tue, Jun 17, 2014 at 6:29 PM, Nick Apperley <napp...@gmail.com> wrote:
> Tried running one of the demos remotely (via SSH) and ended up with error
> messages being spitted out (aka crash 'n' burn) like the following:
>
> ===========================================================
> ubuntu@arm:/opt/gfxsdkdemos/ogles2$ ./OGLES2MagicLantern
> Can't open keypad input device (/dev/input/event0)
> libEGL warning: DRI2: xcb_connect failed
> libEGL warning: DRI2: xcb_connect failed
> libEGL warning: GLX: failed to load GLX
> Exit message has been set to: "PVRShell: Unable to initialise EGL
> ".
> PVRShell: EGL Error (EGL_NOT_INITIALIZED)
> InitAPI failed!
> PVRShell: Unable to initialise EGL

This happens when the mesa libegl.so get's installed..

Fixup with:

sudo cp -v /usr/lib/libEGL.so /usr/lib/arm-linux-gnueabihf/libEGL.so
sudo cp -v /usr/lib/libGLESv2.so /usr/lib/arm-linux-gnueabihf/libGLESv2.so

> ===========================================================
>
> Very similar error messages when trying to run the sample JavaFX 8 program
> remotely (via SSH). Robert can you please confirm if you can run one of the
> SGX demos (eg Magic Lantern) successfully, and post the results from running
> the fbset -i and es2_info commands (locally).

[Nick Apperley]

Did install the mesa-dev type packages including mesa-dev-extra, which has the OpenGL ES 2.0 utilities (eg es2_info, es2gears).

[Nick Apperley]

Updated the OpenGL ES libraries so that the SGX ones are used. Ran the Magic Lantern demo again locally and ended up with different error messages appearing like the following:

====================================================

ubuntu@arm:/opt/gfxsdkdemos/ogles2$ ./OGLES2MagicLantern 

Can't open keypad input device (/dev/input/event0)

Exit message has been set to: "PVRShell: Unable to initialise EGL

".

PVRShell: EGL Error (EGL_BAD_ALLOC)

InitAPI failed!

PVRShell: Unable to initialise EGL

====================================================

Do wonder if the SGX video driver was built properly.

[John Syn]

From: Nick Apperley <napp...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Tuesday, June 17, 2014 at 5:00 PM
To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Creating The SGX Driver For Ubuntu 14.04

Did install the mesa-dev type packages including mesa-dev-extra, which has the OpenGL ES 2.0 utilities (eg es2_info, es2gears).

Here is what I do to run QT5.1.1 on V3.12

/etc/init.d/335x-demo

reboot

insmod /lib/modules/3.12.5-bone10.4/extra/pvrsrvkm.ko

insmod /lib/modules/3.12.5-bone10.4/extra/omaplfb.ko

/etc/init.d/rc.pvr start

/opt/gfxsdkdemos/ogles2/OGLES2ChameleonMan

The demo works fine. 

Regards,

John

On Wednesday, 18 June 2014 11:51:53 UTC+12, RobertCNelson wrote:

This happens when the mesa libegl.so get's installed..

Fixup with:

sudo cp -v /usr/lib/libEGL.so /usr/lib/arm-linux-gnueabihf/libEGL.so
sudo cp -v /usr/lib/libGLESv2.so /usr/lib/arm-linux-gnueabihf/libGLESv2.so

> ===========================================================
>
> Very similar error messages when trying to run the sample JavaFX 8 program
> remotely (via SSH). Robert can you please confirm if you can run one of the
> SGX demos (eg Magic Lantern) successfully, and post the results from running
> the fbset -i and es2_info commands (locally).

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

--

[Nick Apperley]

Both omaplfb and pvrsrvkm modules are already loaded. Also the rc.pvr daemon is automatically started during boot. Where is 335x-demo on Ubuntu 14.04?

[John Syn]

From: Nick Apperley <napp...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>

Date: Tuesday, June 17, 2014 at 5:33 PM

To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Creating The SGX Driver For Ubuntu 14.04

Both omaplfb and pvrsrvkm modules are already loaded. Also the rc.pvr daemon is automatically started during boot. Where is 335x-demo on Ubuntu 14.04?

I have attached a copy. It may not be suitable for your system so you may have to make modifications. 

[John Syn]

From: Nick Apperley <napp...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>

Date: Tuesday, June 17, 2014 at 5:33 PM

To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Creating The SGX Driver For Ubuntu 14.04

Both omaplfb and pvrsrvkm modules are already loaded. Also the rc.pvr daemon is automatically started during boot. Where is 335x-demo on Ubuntu 14.04?

I suspect that Robert’s installer would have already done this setup, but if this is any help, this is what it does:

oot@arm:~# /etc/init.d/335x-demo 

0x10205

release8.x

installing 8.x SGX release user libraries

Installing PowerVR Consumer/Embedded DDK 'sgxddk_1.10@2359475' on target

File system installation root is /

Uninstalling existing version sgxddk_1.10@2359475

Uninstallation completed.

boot script rc.pvr -> /etc/init.d/rc.pvr

kernel module pvrsrvkm.ko -> /lib/modules/3.12.5-bone10.4/extra/pvrsrvkm.ko

kernel module omaplfb.ko -> /lib/modules/3.12.5-bone10.4/extra/omaplfb.ko

shared library libGLES_CM.so -> /usr/lib/libGLES_CM.so.1.10.2359475

shared library libusc.so -> /usr/lib/libusc.so.1.10.2359475

shared library libGLESv2.so -> /usr/lib/libGLESv2.so.1.10.2359475

shared library libglslcompiler.so -> /usr/lib/libglslcompiler.so.1.10.2359475

shared library libIMGegl.so -> /usr/lib/libIMGegl.so.1.10.2359475

shared library libEGL.so -> /usr/lib/libEGL.so.1.10.2359475

shared library libpvr2d.so -> /usr/lib/libpvr2d.so.1.10.2359475

shared library libpvrPVR2D_BLITWSEGL.so -> /usr/lib/libpvrPVR2D_BLITWSEGL.so.1.10.2359475

shared library libpvrPVR2D_FLIPWSEGL.so -> /usr/lib/libpvrPVR2D_FLIPWSEGL.so.1.10.2359475

shared library libpvrPVR2D_FRONTWSEGL.so -> /usr/lib/libpvrPVR2D_FRONTWSEGL.so.1.10.2359475

shared library libpvrPVR2D_LINUXFBWSEGL.so -> /usr/lib/libpvrPVR2D_LINUXFBWSEGL.so.1.10.2359475

shared library libsrv_um.so -> /usr/lib/libsrv_um.so.1.10.2359475

shared library libsrv_init.so -> /usr/lib/libsrv_init.so.1.10.2359475

shared library libPVRScopeServices.so -> /usr/lib/libPVRScopeServices.so.1.10.2359475

binary pvrsrvctl -> /usr/local/bin/pvrsrvctl

binary sgx_init_test -> /usr/local/bin/sgx_init_test

binary services_test -> /usr/local/bin/services_test

binary sgx_blit_test -> /usr/local/bin/sgx_blit_test

binary sgx_clipblit_test -> /usr/local/bin/sgx_clipblit_test

binary sgx_flip_test -> /usr/local/bin/sgx_flip_test

binary sgx_render_flip_test -> /usr/local/bin/sgx_render_flip_test

binary pvr2d_test -> /usr/local/bin/pvr2d_test

shader glsltest1_vertshader.txt -> /usr/local/bin/glsltest1_vertshader.txt

shader glsltest1_fragshaderA.txt -> /usr/local/bin/glsltest1_fragshaderA.txt

shader glsltest1_fragshaderB.txt -> /usr/local/bin/glsltest1_fragshaderB.txt

Installation complete!

You may now reboot your target.

[Nick]

Still getting the same errors when running the Magic Lantern demo again.

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/vHmA5ZuYoHw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

[John Syn]

From: Nick <napp...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Date: Tuesday, June 17, 2014 at 6:01 PM

To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Creating The SGX Driver For Ubuntu 14.04

Still getting the same errors when running the Magic Lantern demo again.

I’m running Debian. If I don’t run /etc/init.d/rc.pvr, I get the same error you get.

root@arm:/opt/gfxsdkdemos/ogles2# ./OGLES2ChameleonMan 

Can't open keypad input device (/dev/input/event0)

Exit message has been set to: "PVRShell: Unable to initialise EGL

".

PVRShell: EGL Error (EGL_BAD_ALLOC)

InitAPI failed!

PVRShell: Unable to initialise EGL

root@arm:/opt/gfxsdkdemos/ogles2# /etc/init.d/rc.pvr start

Loaded PowerVR consumer services.

root@arm:/opt/gfxsdkdemos/ogles2# ./OGLES2ChameleonMan 

Can't open keypad input device (/dev/input/event0)

PVRShell: EGL 1.4 initialized

Regards,

John

[Nick Apperley]

Restarted the rc.pvr daemon without any issues. Ran the demo (Magic Lantern) again and ended up with the following errors:

ubuntu@arm:/opt/gfxsdkdemos/ogles2$ ./OGLES2MagicLantern 

Can't open keypad input device (/dev/input/event0)

PVRShell: EGL 1.4 initialized

Exit message has been set to: "PVRShell: Unable to create surface

".

InitAPI failed!

PVRShell: Unable to create surface

[Nick Apperley]

Have a funny feeling that I am getting very close to remotely running the sample JavaFX 8 program without any issues. Currently the following errors occur when running the sample JavaFX 8 program remotely, provided the rc.pvr daemon on the BBB is running:

============================================================================================

Connecting to xxx.xxx.xxx.xxx:22

cmd : cd '/home/ubuntu/NetBeans_Projects/JavaFX_Test'; '/home/ubuntu/ejre-1.8.0_fx/bin/java'  -Dfile.encoding=UTF-8   -jar /home/ubuntu/NetBeans_Projects/JavaFX_Test/dist/JavaFX_Test.jar 

eglCreateWindowSurface failed! eglGetError 12291

eglMakeCurrent failed - 12297

Failed to create EGLContext

Graphics Device initialization failed for :  es2

Error initializing QuantumRenderer: no suitable pipeline found

java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found

============================================================================================

Seems as though the create surface problem is related to the issues with trying to run any of the SGX EGL2 demos.

[John Syn]

From: Nick Apperley <napp...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>

Date: Tuesday, June 17, 2014 at 7:11 PM

To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Creating The SGX Driver For Ubuntu 14.04

Have a funny feeling that I am getting very close to remotely running the sample JavaFX 8 program without any issues. Currently the following errors occur when running the sample JavaFX 8 program remotely, provided the rc.pvr daemon on the BBB is running:

============================================================================================

Connecting to xxx.xxx.xxx.xxx:22

cmd : cd '/home/ubuntu/NetBeans_Projects/JavaFX_Test'; '/home/ubuntu/ejre-1.8.0_fx/bin/java'  -Dfile.encoding=UTF-8   -jar /home/ubuntu/NetBeans_Projects/JavaFX_Test/dist/JavaFX_Test.jar 

eglCreateWindowSurface failed! eglGetError 12291

eglMakeCurrent failed - 12297

Failed to create EGLContext

Graphics Device initialization failed for :  es2

Error initializing QuantumRenderer: no suitable pipeline found

java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found

============================================================================================

Seems as though the create surface problem is related to the issues with trying to run any of the SGX EGL2 demos.

Since this is related to SGX, I recommend that you post a question on Texas Instruments E2E forum. 

Regards,

John

On Wednesday, 18 June 2014 13:55:34 UTC+12, Nick Apperley wrote:

Restarted the rc.pvr daemon without any issues. Ran the demo (Magic Lantern) again and ended up with the following errors:

ubuntu@arm:/opt/gfxsdkdemos/ogles2$ ./OGLES2MagicLantern 

Can't open keypad input device (/dev/input/event0)

PVRShell: EGL 1.4 initialized

Exit message has been set to: "PVRShell: Unable to create surface

".

InitAPI failed!

PVRShell: Unable to create surface

--

[Nick Apperley]

Created a new thread on the TI E2E forum for anyone that is interested in tracking the issue.

[John Syn]

From: Nick Apperley <napp...@gmail.com>
Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>

Date: Tuesday, June 17, 2014 at 7:43 PM

To: "beagl...@googlegroups.com" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Creating The SGX Driver For Ubuntu 14.04

Created a new thread on the TI E2E forum for anyone that is interested in tracking the issue.

I would post another entry describing the problem you are having with the SGX demo. That way it is easier for TI to isolate the issue.

Regards,

John

On Wednesday, 18 June 2014 14:19:31 UTC+12, john3909 wrote:

Since this is related to SGX, I recommend that you post a question on Texas Instruments E2E forum. 

Regards,

John

[Nick Apperley]

Created a new thread on the TI E2E forum in relation to the surface errors when trying to run the Magic Lantern demo. Received a very unhelpful reply from TI yesterday. See that there are a few people who have issues with the TI Graphics SDK on the BBB that are receiving official support from TI.

[Igor Cherepinsky]

If you ever find a solution to this, could you post to this forum. I've tried different kernels and I am getting the same error as you are  "unable to create a surface", can't run demo apps either. I think it had to do with a framebuffer that we are using. I am using tilcdc framebuffer (with a 7" BB-VIEW LCD). I am not sure if these drivers require da8xx-fb driver. TI was absolutely of no help.

[Robert Nelson]

On Wed, Jun 18, 2014 at 3:38 PM, Nick Apperley <napp...@gmail.com> wrote:
> Created a new thread on the TI E2E forum in relation to the surface errors
> when trying to run the Magic Lantern demo. Received a very unhelpful reply
> from TI yesterday. See that there are a few people who have issues with the
> TI Graphics SDK on the BBB that are receiving official support from TI.

Well.. You may not like my answer right now.. Just tested my 14.04
build... getting:

PVRShell: EGL Error (EGL_BAD_ALLOC)

Works just fine in Debian Jessie (which i was testing yesterday)

[John Syn]

That is really weird. Works fine for me on Debian with V3.12 kernel.

Regards,
John

>
>Regards,
>
>--
>Robert Nelson
>http://www.rcn-ee.com/
>

[Robert Nelson]

On Wed, Jun 18, 2014 at 4:58 PM, John Syn <john...@gmail.com> wrote:
>
> On 6/18/14, 2:42 PM, "Robert Nelson" <robert...@gmail.com> wrote:
>
>>On Wed, Jun 18, 2014 at 3:38 PM, Nick Apperley <napp...@gmail.com>
>>wrote:
>>> Created a new thread on the TI E2E forum in relation to the surface
>>>errors
>>> when trying to run the Magic Lantern demo. Received a very unhelpful
>>>reply
>>> from TI yesterday. See that there are a few people who have issues with
>>>the
>>> TI Graphics SDK on the BBB that are receiving official support from TI.
>>
>>Well.. You may not like my answer right now.. Just tested my 14.04
>>build... getting:
>>
>>PVRShell: EGL Error (EGL_BAD_ALLOC)
>>
>>Works just fine in Debian Jessie (which i was testing yesterday)
> That is really weird. Works fine for me on Debian with V3.12 kernel.

Yeap, very weird.. Pop-in my debian image, same (built) kernel/sgx
modules copied over, works on debian, fails on ubuntu.

[William Hermans]

Has anyone compared kernel configs ?

[Robert Nelson]

On Wed, Jun 18, 2014 at 5:43 PM, William Hermans <yyr...@gmail.com> wrote:
> Has anyone compared kernel configs ?

It's the "same" kernel build.

I was cleaning up the sgx patchset from v3.13.x today, doing all my
testing on debian. Created a new ubuntu image and copied my working
just fine kernel zImage/modules/blob libs over. ;)

[Nick Apperley]

Robert,

Did you check to see if the rc.pvr daemon is running before running one of the demos? Did have the PVRShell: EGL Error (EGL_BAD_ALLOC) error but managed to resolve it by restarting the rc.pvr daemon. Really weird that the daemon doesn't start automatically during boot up.

[Robert Nelson]

On Wed, Jun 18, 2014 at 6:54 PM, Nick Apperley <napp...@gmail.com> wrote:
> Robert,
>
> Did you check to see if the rc.pvr daemon is running before running one of
> the demos? Did have the PVRShell: EGL Error (EGL_BAD_ALLOC) error but
> managed to resolve it by restarting the rc.pvr daemon. Really weird that the
> daemon doesn't start automatically during boot up.

You know me, i wrote my own:

ubuntu:
https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.13/3rdparty/sgx-startup-ubuntu.conf

debian:
https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.13/3rdparty/sgx-startup-debian.sh

[Nick Apperley]

Oh that's right, the rc.pvr daemon was already running but needed to be given the equivalent of a reboot in order to avoid the EGL_BAD_ALLOC error.

[Nick Apperley]

Do the SGX demos work on Debian 7.5 with the 3.13.9-bone9 kernel?

On Thursday, 19 June 2014 09:42:40 UTC+12, RobertCNelson wrote:

[Robert Nelson]

On Wed, Jun 18, 2014 at 7:55 PM, Nick Apperley <napp...@gmail.com> wrote:
> Do the SGX demos work on Debian 7.5 with the 3.13.9-bone9 kernel?

You'll need "3.13.11-bone10" it's out being built right now..

http://rcn-ee.homeip.net:81/dl/farm/deb/

I'm working on a write up, to make it easy to install to a bunch of boards.

[Nick Apperley]

Is the new kernel going to be uploaded to http://rcn-ee.net/? Which website is hosting the guides/documentation?

[Robert Nelson]

On Wed, Jun 18, 2014 at 8:05 PM, Nick Apperley <napp...@gmail.com> wrote:
> Is the new kernel going to be uploaded to http://rcn-ee.net/? Which website
> is hosting the guides/documentation?

Correct, it'll be on rcn-ee.net as it's done building..

The docs will be under an sgx section:

http://elinux.org/BeagleBoardDebian

[Nick Apperley]

Tried running the Magic Lantern demo on Debian 7.5 with the 3.13.11-bone10 kernel (newly built) but had the same problems appear (Unable to create surface).

[Nick Apperley]

Does the default kernel used by Debian Jessie include the SGX video driver?

On Thursday, 19 June 2014 13:16:27 UTC+12, RobertCNelson wrote:

[Robert Nelson]

On Wed, Jun 18, 2014 at 8:59 PM, Nick Apperley <napp...@gmail.com> wrote:
> Tried running the Magic Lantern demo on Debian 7.5 with the 3.13.11-bone10
> kernel (newly built) but had the same problems appear (Unable to create
> surface).

Here's my step by step:

pc:
wget https://rcn-ee.net/deb/microsd/wheezy/bone-debian-7.5-console-2014-06-05-2gb.img.xz
unzx bone-debian-7.5-console-2014-06-05-2gb.img.xz
sudo dd if=bone-debian-7.5-console-2014-06-05-2gb.img of=/dev/sdX

beaglebone:
wget https://rcn-ee.net/deb/wheezy-armhf/v3.13.11-bone10/install-me.sh
sudo /bin/bash install-me.sh
(reboot)

pc:
git clone https://github.com/RobertCNelson/bb-kernel.git
cd bb-kernel/
git checkout origin/am33x-v3.13 -b tmp
./build_kernel.sh
./sgx_build_modules.sh

copy GFX_5.01.01.01.tar.gz (under ./deploy) to beaglebone
(wget http://192.168.0.10/GFX_5.01.01.01.tar.gz)

beaglebone:
sudo tar xfv GFX_5.01.01.01.tar.gz -C /

cd /opt/gfxinstall/
sudo ./sgx-install.sh
sudo reboot

debian@arm:~$ lsmod | grep omaplfb
omaplfb 12065 0
pvrsrvkm 178782 1 omaplfb

cd /opt/gfxsdkdemos/ogles2/
./OGLES2ChameleonMan

Can't open keypad input device (/dev/input/event0)
PVRShell: EGL 1.4 initialized

Watch guy running around...

[Robert Nelson]

Full debian write up is here now:

http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black

Now back to getting it working on ubuntu.

[Robert Nelson]

>
> Full debian write up is here now:
>
> http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black
>
> Now back to getting it working on ubuntu.

Okay, 14.04 now works too... I dropped the upstart script, and just
set it up as a classic sysv script. (as upstart is dead anyways.. :) )

https://github.com/RobertCNelson/bb-kernel/commit/b85a31c36df733bcb8b69c196322a67774e1ab7f

todo: systemd version...

[Nick Apperley]

Ubuntu 14.04 still uses Upstart by default even though Systemd is already installed.

[Robert Nelson]

On Thu, Jun 19, 2014 at 4:45 PM, Nick Apperley <napp...@gmail.com> wrote:
> Ubuntu 14.04 still uses Upstart by default even though Systemd is already
> installed.

and it also has an sysv compatibility layer. ;)

[Nick Apperley]

Encountered difficulties with building the SGX modules. File not found type errors with sgx-startup-debian.sh and sgx-startup-ubuntu.conf in bb-kernel/3rdparty. Did you know that the certificate for rcn-ee.net has expired?

[Jesse Forgues]

Same here "cp: cannot stat `/home/avb/sgx/bb-kernel/3rdparty/sgx-startup-debian.sh': No such file or directory"

tail of end of log:

exporting necessary variables and installing...

########################################################

Please ensure that PSP Linux kernel is re-built atleast once,

Please refer online guide for further details.

########################################################

creating directories...

copying startup files...

copying user space graphics libraries to target file system...

copying install information to target file system...

`/home/avb/sgx/bb-kernel/ignore/ti-sdk-pvr/Graphics_SDK/gfx_rel_es8.x/bufferclass_ti.ko' -> `/home/avb/sgx/bb-kernel/deploy/8.x/opt/gfxmodules/gfx_rel_es8.x/bufferclass_ti.ko'

`/home/avb/sgx/bb-kernel/ignore/ti-sdk-pvr/Graphics_SDK/gfx_rel_es8.x/omaplfb.ko' -> `/home/avb/sgx/bb-kernel/deploy/8.x/opt/gfxmodules/gfx_rel_es8.x/omaplfb.ko'

`/home/avb/sgx/bb-kernel/ignore/ti-sdk-pvr/Graphics_SDK/gfx_rel_es8.x/pvrsrvkm.ko' -> `/home/avb/sgx/bb-kernel/deploy/8.x/opt/gfxmodules/gfx_rel_es8.x/pvrsrvkm.ko'

cp: cannot stat `/home/avb/sgx/bb-kernel/3rdparty/sgx-startup-debian.sh': No such file or directory

[Nick Apperley]

Just for reference with Debian on BBB where would the following be located:

• rc.pvr daemon
• Startup script for SGX driver (sgx-startup-debian.sh)

Been trying to find the 2 mentioned files. Running lsmod | grep omaplfb doesn't return any results. Rather bizarre considering that the SGX install was successful (no errors displayed), or so I thought.

[Nick Apperley]

Resolved the issue on Debian by creating /etc/init/sgx-startup.sh file which contains the following:

=====================================================

#!/bin/sh -e

### BEGIN INIT INFO

# Provides:          sgx-startup.sh

# Required-Start:    $local_fs

# Required-Stop:     $local_fs

# Default-Start:     2 3 4 5

# Default-Stop:      0 1 6

# Short-Description: Start daemon at boot time

# Description:       Enable service provided by daemon.

### END INIT INFO

case "$1" in

start)

if [ -d /sys/devices/ocp.*/56000000.sgx ] ; then

echo "sgx: Starting PVR"

modprobe -q pvrsrvkm

# Delete the device for PVR services device and recreate with the

# correct major number.

#

pvr_maj=$(grep "pvrsrvkm$" /proc/devices | cut -b1,2,3)

if [ -e /dev/pvrsrvkm ] ; then

rm -f /dev/pvrsrvkm

fi

mknod /dev/pvrsrvkm c $pvr_maj 0

chmod 666 /dev/pvrsrvkm

if [ -f /usr/local/bin/pvrsrvctl ] ; then

/usr/local/bin/pvrsrvctl --start --no-module

modprobe -q omaplfb

fi

fi

;;

reload|force-reload|restart)

if [ -d /sys/devices/ocp.*/56000000.sgx ] ; then

echo "sgx: Restarting PVR"

fi

;;

stop)

exit 0

;;

*)

echo "Usage: /etc/init.d/sgx-startup.sh {start|stop|reload|restart|force-reload}"

exit 1

;;

esac

exit 0

=====================================================

Once the file was created the SGX daemon was started by running the following:

    sudo sh /etc/init/sgx-startup.sh

Run one of the SGX demos (eg Magic Lantern) and volla! :)

[Nick Apperley]

Now when I try to run the sample JavaFX 8 program (locally or remotely) different error messages appear like the following:

=======================================================

Connecting to xxx.xxx.xxx.xxx:22

cmd : cd '/home/debian/NetBeans_Projects//JavaFX_Test'; '/home/debian/ejre-1.8.0_fx/bin/java'  -Dfile.encoding=UTF-8   -jar /home/debian/NetBeans_Projects//JavaFX_Test/dist/JavaFX_Test.jar 

eglGetConfigAttrib failed!

Graphics Device initialization failed for :  es2

Error initializing QuantumRenderer: no suitable pipeline found

=======================================================

Getting very close towards the end goal (?). Spotted in the EGL ApI Docs by chance that the eglGetConfigAttrib function according to the description, "return information about an EGL frame buffer configuration". Discovered indirectly from the docs that JavaFX needs direct access to the frame buffer and doesn't require X Server to be running. Right now I am assuming that JavaFX can now create an EGL surface but cannot obtain configuration information for the frame buffer which is needed to render everything else graphics wise, hence an exception (error) is thrown/displayed.

I suspect that the SGX driver is being very naughty by withholding vital frame buffer configuration information needed for graphics rendering. Is TI going to properly fix this serious issue?

[Robert Nelson]

Sorry guys

https://github.com/RobertCNelson/bb-kernel/commit/ba1d4658a604cf7dfab70999ff4c7bc7f7d72c48

[Jesse Forgues]

Don't be sorry man, your doing the heavy lifting!

Thanks for the fix...

[Nick Apperley]

Robert,

Thank you for helping out, highly appreciated. Now I am at a difficult position where the ball is in TI's court with properly implementing the EGL 2 APIs. No JavaFX programs can be run on the BBB via the frame buffer until that issue is resolved. At least the SGX demos are working fine now so there is some hope on getting the GPU utilised throughout the OS (Debian, Ubuntu etc).

[Robert Nelson]

On Thu, Jun 19, 2014 at 9:30 PM, Nick Apperley <napp...@gmail.com> wrote:
> Robert,
>
> Thank you for helping out, highly appreciated. Now I am at a difficult
> position where the ball is in TI's court with properly implementing the EGL
> 2 APIs. No JavaFX programs can be run on the BBB via the frame buffer until
> that issue is resolved. At least the SGX demos are working fine now so there
> is some hope on getting the GPU utilised throughout the OS (Debian, Ubuntu
> etc).

Does it make any difference if you force eglfb mode?

java -Djavafx.platform=eglfb -jar xyz

(i couldn't get it to work with minecraft, it still wanted x11..)

[Nick Apperley]

Made no difference adding the -Djavafx.platform=eglfb VM parameter. Not highly knowledgeable about Minecraft but does the game use Java2D?

[Nick Apperley]

Found an Oracle article on getting JavaFX 8 to work on a Beagleboard-xM which may be relevant to the BBB. In the article DirectFB is used for graphics rendering however it is done in software, which may be BRUTAL performance wise. Might be worth trying the DirectFB method which could work for other technologies that require EGL 2 support (eg Kivy for Python).

[Nick Apperley]

Managed to successfully install DirectFB (specified omap for the video driver) on the BBB. However when I tried to run the sample JavaFX 8 program the following errors appeared:

cmd : cd '/home/debian/NetBeans_Projects//JavaFX_Test'; '/home/debian/ejre-1.8.0_fx/bin/java'  -Dfile.encoding=UTF-8 -Djavafx.platform=directfb  -jar /home/debian/NetBeans_Projects//JavaFX_Test/dist/JavaFX_Test.jar 

   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.7.4 |~~~~~~~~~~~~~~~~~~~~~~~~~~

        (c) 2012-2013  DirectFB integrated media GmbH

        (c) 2001-2013  The world wide DirectFB Open Source Community

        (c) 2000-2004  Convergence (integrated media) GmbH

      ----------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2014-05-06 20:02) 

(*) Direct/Memcpy: Using libc memcpy()

(*) Direct/Thread: Started 'Fusion Dispatch' (1924) [MESSAGING - OTHER/0] <8388608>...

(!) System/DevMem: Please supply 'video-phys = 0xXXXXXXXX' and 'video-length = XXXX' options!

(!) DirectFB/Core: Could not initialize 'system_core' core!

    --> An invalid argument has been specified

 (!!!)  *** UNIMPLEMENTED [fusion_dispatch] *** [fusion.c:3935]

DFB error, code 422552497, at /HUDSON/workspace/8.0/label/linux-arm-30/rt/modules/graphics/src/main/native-glass/lens/wm/screen/dfbScreen.c <287>:

May 06, 2014 8:24:24 PM com.sun.glass.ui.lens.LensApplication _initialize

SEVERE: 1923 dfbScreen.c:335 glass_application_initialize: Failed to initialize DirectFB

May 06, 2014 8:24:24 PM com.sun.glass.ui.lens.LensApplication _initialize

SEVERE: 1923 LensWindowManager.c:114 lens_wm_initialize: glass_application_initialize() failed

May 06, 2014 8:24:24 PM com.sun.glass.ui.lens.LensApplication$4 run

SEVERE: Display failed initialization

Exception in thread "Lens Event Thread" 

java.lang.RuntimeException: Display failed initialization

at com.sun.glass.ui.lens.LensApplication$4.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

[Nick Apperley]

Reinstalled DirectFB with the video driver set to none. Ran the sample JavaFX 8 program with similar errors showing up again:

cmd : cd '/home/debian/NetBeans_Projects//JavaFX_Test'; '/home/debian/ejre-1.8.0_fx/bin/java'  -Dfile.encoding=UTF-8 -Djavafx.platform=directfb  -jar /home/debian/NetBeans_Projects//JavaFX_Test/dist/JavaFX_Test.jar 

   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.7.4 |~~~~~~~~~~~~~~~~~~~~~~~~~~

        (c) 2012-2013  DirectFB integrated media GmbH

        (c) 2001-2013  The world wide DirectFB Open Source Community

        (c) 2000-2004  Convergence (integrated media) GmbH

      ----------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2014-05-06 21:02) 

(*) Direct/Memcpy: Using libc memcpy()

(*) Direct/Thread: Started 'Fusion Dispatch' (30490) [MESSAGING - OTHER/0] <8388608>...

(!) System/DevMem: Please supply 'video-phys = 0xXXXXXXXX' and 'video-length = XXXX' options!

(!) DirectFB/Core: Could not initialize 'system_core' core!

    --> An invalid argument has been specified

 (!!!)  *** UNIMPLEMENTED [fusion_dispatch] *** [fusion.c:3935]

DFB error, code 422552497, at /HUDSON/workspace/8.0/label/linux-arm-30/rt/modules/graphics/src/main/native-glass/lens/wm/screen/dfbScreen.c <287>:

May 06, 2014 9:19:26 PM com.sun.glass.ui.lens.LensApplication _initialize

SEVERE: 30489 dfbScreen.c:335 glass_application_initialize: Failed to initialize DirectFB

May 06, 2014 9:19:26 PM com.sun.glass.ui.lens.LensApplication _initialize

SEVERE: 30489 LensWindowManager.c:114 lens_wm_initialize: glass_application_initialize() failed

May 06, 2014 9:19:26 PM com.sun.glass.ui.lens.LensApplication$4 run

SEVERE: Display failed initialization

This time when running the sample program locally a segmentation fault message appears. Thought it might be useful to display the frame buffer info (via fbset -i):

Frame buffer device information:

    Name        : 

    Address     : 0x9e900000

    Size        : 2621440

    Type        : PACKED PIXELS

    Visual      : TRUECOLOR

    XPanStep    : 1

    YPanStep    : 1

    YWrapStep   : 0

    LineLength  : 2560

    Accelerator : No

Just realised that I installed an experimental version of DirectFB from the 1.7 branch. Will try a stable one from the 1.6 branch. Hopefully that will do the trick.

[Jesse Forgues]

The "Running Man" demo on my BBB in case anyone wanted to watch the demo: https://dl.dropboxusercontent.com/u/82765462/BBB/BBB_OpenGL_RunningMan.mp4

[Jesse Forgues]

MagicLantern Demo: https://dl.dropboxusercontent.com/u/82765462/BBB/BBB_OpenGL_MagicLantern.mp4

[Nick Apperley]

Going to rebuild DirectFB with the following:

=============================================

./configure --with-inputdrivers=none \

--with-gfxdrivers=gles2,omap,pvr2d \

--enable-egl \

--without-tools --disable-static \

--prefix=/usr

=============================================

When the configure was done the following message appeared:

*** gl egl packages not found -- Building without EGL support.

Which gl egl packages is DirectFB referring to?  Noticed during the configure stage that DirectFB has picked up the omap video driver, which I am assuming is used on the BBB and not the pvr2d one.

[Nick Apperley]

Discovered that pvr2d should be specified as the video driver when building DirectFB. Rebuilding DirectFB with the following:

===============================================

./configure --with-inputdrivers=none \

        --with-gfxdrivers=pvr2d,gles2 \

        --enable-egl --enable-pvr2d \

        --without-tools --disable-static \

        --prefix=/usr

===============================================

Below are the options used by DirectFB:

==========================================================

Build options:

  Version                   1.6.3

  Linux powered             yes

  Install prefix            /usr

  Config files in           /usr/etc

  Build shared libs         yes

  Build static libs         no

  Module directory          ${exec_prefix}/lib/directfb-1.6-0

  CPPFLAGS                  -D_REENTRANT 

  CFLAGS                    -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-strict-aliasing -Werror-implicit-function-declaration -O2 -g2 -ffast-math -pipe  -D_GNU_SOURCE  -std=gnu99 -Werror-implicit-function-declaration

  LDFLAGS                   

  LIBS                      -ldl -lrt -lpthread 

  DYNLIB                    -ldl

  RTLIB                     -lrt

  THREADFLAGS               -D_REENTRANT

  THREADLIB                 -lpthread

Misc options:

  Multi Application Core    no

  Fusion Kernel Device      N/A

  Fusion message size       16384

  Fluxed args size          1024

  One (IPC)                 no

  Voodoo (network support)  no

  Pure Voodoo (net only)    no

  Debug supported           yes

  Debug enabled             no

  Trace support             no

  MMX support               no

  SSE support               no

  Network support           yes

  Include all strings       yes

  Software Rendering        yes

  Smooth SW Scaling         no

  Dithering                 none

  Dithering 565             none

  zlib compression          no                 

  Using setsockopt          yes

Building Tests              no

Building Tools              no

Building System Modules:

  Linux FBDev support       yes

  Generic /dev/mem support  yes

  Mesa/DRM/KMS support      no                 

  PVR2D                     yes                

  EGL                       no                  

  X11 support               no                  

  X11/VDPAU support         no             

  OSX support               no                  

  SDL support               no                  

  VNC support               no                  

Building Window Manager Modules:

  Default                   yes

  UniQuE                    no

Building Image Provider Modules:

  GIF                       yes

  JPEG                      yes                 -ljpeg

  PNG                       no                   

  Imlib2                    no                

  PNM                       yes

  SVG                       no                   

  BMP                       yes

  JPEG2000                  no             

  MPEG2                     yes

Building Video Provider Modules:

  GIF                       yes

  Video4Linux               yes (v2: no)

  MNG                       no                  

  Gstreamer                 no (v1: no)        

    with FusionSound        no

Building Font Modules:

  FreeType2                 no                  

  LinoType                  no                  

  Default font              yes

Building Graphics Drivers:

  3Dfx Voodoo               no

  ATI Mach64                no

  ATI Rage 128              no

  ATI Radeon                no

  Cirrus EP9X               no

  Intel i810                no

  Intel i830                no

  Matrox                    no

  NeoMagic                  no

  NSC Geode                 no

  nVidia                    no

  PVR2D                     yes

  PXA 3xx                   no

  Renesas SH7722/SH7723     no

  S3 Savage                 no

  SiS 315                   no

  TI Davinci                no

  TI OMAP                   no

  TVIA CyberPro             no

  VIA CLE266                no

  VIA UniChrome             no

  VMWare                    no

  VDPAU                     no

  --

  OpenGL                    no (GLX: no)

  OpenGL ES 2.0             yes (Mesa:  no, PVR2D: yes)

                                         -DGLES2_PVR2D  

Building Input Drivers:

  DBox2 Remote              no

  DreamBox Remote           no

  Dynapro Touchscreen       no

  ELO Touchscreen           no

  Gunze Touchscreen         no

  H3600 Touchscreen         no

  Input Hub                 no

  Joystick                  no

  Keyboard                  no

  Linux Input               no

  LiRC                      no

  MuTouch touchscreen       no

  Zytronic touchscreen      no

  PS/2 Mouse                no

  Serial Mouse              no

  SonyPI Jogdial            no

  tslib                     no                  

  ucb1x00 Touchscreen       no

  WM97xx Touchscreen        no

 

PNG support is missing - many applications won't work correctly!  

FreeType2 support is missing - many applications won't work correctly!

==========================================================

Need some help on getting DirectFB to detect the EGL library(?) used by the system during the configuration process.