Logic Supply CL100 support



We have some NUC factor based logic supply based hardware. It is a Logicsupply CL100

The Intel NUC image seems to work ok, but there is no correct graphics driver loaded for this platform. It should load the i915 module, but that is not available in the Intel NUC image.

What would be the best way to add this driver?


So after some hacking i got the UP image working on this device. This seems to load the i915 module, but still using the

There is still no HW accelerations.

What does work (with HW acces) on both images (NUC/UP) and just plain Ubuntu Server LTS with docker is running a container like this:

docker -H <device ip> run -it --name hw-image --privileged -v /var/run/dbus:/var/run/dbus -v /var/run/udev:/var/run/udev -d  -v /mnt/data/hw-image:/data hw-image startx

Using this Dockerfile

FROM ubuntu

# Install other apt deps
RUN apt-get update && apt-get install -y \
  apt-utils \
  clang \
  xserver-xorg-core \
  xserver-xorg-input-all \
  xserver-xorg-video-fbdev \
  xorg \
  xserver-xorg-video-intel \
  mesa-utils \ 
  mesa-utils-extra \
  fluxbox \
  libexpat-dev && rm -rf /var/lib/apt/lists/*

# Set Xorg and FLUXBOX preferences
RUN mkdir ~/.fluxbox
#RUN echo "xset s off" > ~/.fluxbox/startup && echo "xserver-command=X -s 0 dpms" >> ~/.fluxbox/startup
RUN echo "#!/bin/bash" > /etc/X11/xinit/xserverrc \
  && echo "" >> /etc/X11/xinit/xserverrc \
  && echo 'exec /usr/bin/X -nolisten tcp "$@"' >> /etc/X11/xinit/xserverrc
#  && echo 'exec /usr/bin/X -s 0 dpms -nolisten tcp "$@"' >> /etc/X11/xinit/xserverrc

# Move to app dir
WORKDIR /usr/src/app

# Move package.json to filesystem
COPY ./app/package.json ./

# Install npm modules for the application
#RUN JOBS=MAX npm install --unsafe-perm --production \
#	&& npm cache clean && node_modules/.bin/electron-rebuild

RUN apt-get update  && apt-get install -y \
    firefox \
    chromium-browser \
    fbset \
    mpv \

# Move app to filesystem
COPY ./app ./

## uncomment if you want systemd

# Start app
CMD ["bash", "/usr/src/app/start.sh"]

So what’s going on there?