This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

OpenCL driver issue with Samsung Chromebook

Hi,

I had an issue with the OpenCL Driver on my Chomebook.

I followed ARM's instruction and successfully boot into Linux. However, I got an error message said that libxcb-dri2.so missing. After install libxcb-dri2.0-dev, I can compile Mali OpenCL SDK sample codes. But they won't be executed correctly under X11 or via fbdev. I past error message below. Any suggestion? Thanks.

> ./hello_world_opencl

OpenCL error: CL_OUT_OF_HOST_MEMORY

Creating an OpenCL context failed. common.cpp:248

Failed to create an OpenCL context. hello_world_opencl.cpp:39

> ldd hello_world_opencl

        libOpenCL.so => /opt/mali/fbdev/libOpenCL.so (0x76efc000)

        libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0x76e4a000)

        libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x76e39000)

        libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76d55000)

        /lib/ld-linux-armhf.so.3 (0x76f07000)

        libmali.so => /opt/mali/fbdev/libmali.so (0x76304000)

        libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x762e9000)

        libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x7627e000)

        librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x76270000)

        libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x76265000)

Parents

0 Chris Varnsverry over 11 years ago in reply to Amit

Hi Amit,
I think we've spoken over email, but for the benefit of others we believe this is due to the udev daemon not being able to pick up the wifi card, probably due to an outdated version. You can either use a USB ethernet dongle, or try a more recent root filesystem, such as Arch or Ubuntu 13.04. We have it working on Arch in the office. It may also be possible to get it working on the existing rootfs we suggest in the guide, but I can't say for sure.
Thanks,
Chris
Cancel
Up 0 Down

Cancel

Reply

0 Chris Varnsverry over 11 years ago in reply to Amit

Hi Amit,
I think we've spoken over email, but for the benefit of others we believe this is due to the udev daemon not being able to pick up the wifi card, probably due to an outdated version. You can either use a USB ethernet dongle, or try a more recent root filesystem, such as Arch or Ubuntu 13.04. We have it working on Arch in the office. It may also be possible to get it working on the existing rootfs we suggest in the guide, but I can't say for sure.
Thanks,
Chris
Cancel
Up 0 Down

Cancel

Children

0 fattire over 11 years ago in reply to Chris Varnsverry
Hmmm interesting. I'm using chrubuntu on the internal mmc-- boots fine w/graphics, sound, etc. though it's not stable enough to test much. Some quick notes for anyone trying it on chrubuntu...
use mmcblk0p7 in the kernel command line instead of the mmcblk1 setting. dd the resulting kernel .img to /dev/mmcblk0p6
for simplicity, I built xf86-video-armsoc right in chrubuntu-- no qemu needed.
the uboot-mkimage package is now u-boot-tools
manually had to add the built kernel modules to /lib/modules/3.8.11...
manually put the xorg libs in /lib/arm-linux-gnueabihf/ Xorg.0.log SEEMS to show them being picked up... once I have network I'll paste it somewhere.
wifi doesn't work as described above, though I did have it working for a second somehow. At least I saw the SSID pop up and say 'connnected' before everything crashed. Problems I found so far wifi have included the regulatory domain not being set as well as the wifi modules not loading. I need the lib80211_crypt_tkip one for example.
I gotta figure this out too:
Really annoying issue: kernel oopses in dw_mci_pre_dma_transfer.isra.13 that apparently takes out the mmc at seemingly random times.
Any thoughts, especially on the kernel crasher? Unfortunately I haven't had enough time to track anything down- doing this in pieces when I get random time.
Cancel
Up 0 Down

Cancel