Rapping up Raring

Sintel-and-Jellyfish gstreamer-and-glmark2-es2
To tie a string around our post about the Linaro Raring images and the post showing how to accelerate video, we’ve put together an image based on Linaro latest Raring ALIP that contains GPU acceleration and the GStreamer binaries for accelerated video playback and camera access.

Jasbir showed that it could be done, and we wanted to make sure that you have an easy way to test things out.

For the impatient

You can download the SD card image from here:
As usual, you can write the SD card image to disk using zcat and dd under Linux. It requires a 4GB card, and can be extracted like so:
~/$ sudo umount /dev/sdc?
~/$ zcat alip-gpu-gstreamer-20131219.img.gz | sudo dd of=/dev/sdc
You can also use Alex Page’s USB Image Tool under Windows.

The details

The photos above show gplay playing the 1080P Sintel Movie by the Blender Foundation and the glmark2-es2 benchmark application.

The image is targeted at our most popular Nitrogen6X or BD-SL-i.MX6 boards with a parallel OV5642 camera. Kernels and library trees for the OV5640 MIPI and Nitrogen6_Lite are available in directories beneath /boot/. If you copy one of these trees to the root folder, you can run with those configurations.

i.e., for nitrogen6x_mipi, you can do this:
~/$ sudo cp -ravf /media/alip/boot/nitrogen6x_mipi/* /media/alip/
~/$ sync && sudo umount /media/alip
and for Nitrogen6_Lite, you can do this:
~/$ sudo cp -ravf /media/alip/boot/nit6xlite/* /media/alip/
~/$ sync && sudo umount /media/alip


We need to give many thanks to Jasbir, who put together notes on i.MX6 GPU acceleration on his blog and helped walk us through the somewhat complicated process of patching the X Server to cooperate with the Vivante GPU. In particular, the DRM library needs patching to match the API version used on the Linaro build (it’s slightly older than what’s used in Yocto).

Jasbir is a real pro, and these are some complicated pieces. We appreciate his support.

As always, let us know how things work for you.


52 Responses to “Rapping up Raring”

  1. uwew December 22, 2013 8:33 am #

    Hello Boundary team,
    Thank you for the great image! I am running it on a Sabre Lite board with a Display connected to LVDS and now I would like to get the touchscreen to work but therefore I would need to compile a kernel module (ads7846). Where can I get the appropriate kernel sources to compile my own modules?

    your directions on how to write the image to disk are not quite right.
    gzcat alip-gpu-gstreamer-20131219.img.gz | dd of=/dev/sdc
    might do the job if you have a 4Gb SD card.

    • uwew December 22, 2013 5:42 pm #

      I guess I figured it out myself.I checked out branch origin/boundary-imx_3.0.35_4.1.0 from git://github.com/boundarydevices/linux-imx6.git, compiled it, installed and it works, perfect!

  2. ericn December 22, 2013 9:33 am #

    Doh! Thanks for the note about the instructions. I must have been tired or distracted when cutting and pasting the example.

    As for how to (re)build the kernel, you can do this on the device itself. The steps are 1) get the kernel, 2) configure for your needs, 3) compile, and 4) install. The currently recommended branch of our kernel tree is boundary-imx_3.0.35_4.1.0, and the normal default configuration is nitrogen6x_defconfig, so the process would be roughly this:

    # 1) get the proper kernel branch
    ~/$ git clone git://github.com/boundtarydevices/linux-imx6
    ~/$ cd linux-imx6
    ~/linux-imx6$ git checkout origin/boundary-imx_3.0.35_4.1.0 -b boundary-imx_3.0.35_4.1.0
    # 2) configure
    ~/linux-imx6$ make nitrogen6x_defconfig
    ~/linux-imx6$ make menuconfig
    ... add your touch screen driver
    # 3) compile
    ~/linux-imx6$ make uImage modules
    # 4) install
    ~/linux-imx6$ cp -fv arch/arm/boot/uImage /boot/
    ~/linux-imx6$ make modules_install

    Since the kernel is quite large and the process quite slow, I recommend cross-compiling the kernel though. The steps in this post show the proper structure, though you should use the new kernel branch.

    Also, recent Ubuntu distributions have a cross-compiler package for gcc-arm-linux-gnueabihf which is perfectly suited to this use. With it, you can do this on your dev machine:

    # 1) get the proper kernel branch
    ~/$ git clone git://github.com/boundtarydevices/linux-imx6
    ~/$ cd linux-imx6
    ~/linux-imx6$ git checkout origin/boundary-imx_3.0.35_4.1.0 -b boundary-imx_3.0.35_4.1.0
    # 2) configure
    ~/linux-imx6$ export ARCH=arm
    ~/linux-imx6$ export CROSS_COMPILE=arm-linux-gnueabihf-gcc
    ~/linux-imx6$ make nitrogen6x_defconfig
    ~/linux-imx6$ make menuconfig
    ... add your touch screen driver
    # 3) compile
    ~/linux-imx6$ make uImage modules

    Step 4 is different though, since you’ll need to copy to your boot media. If you mount the SD card as /media/alip, you can use these steps:

    # 4) install
    ~/linux-imx6$ sudo cp -fv arch/arm/boot/uImage /media/alip/boot/
    ~/linux-imx6$ make INSTALL_MOD_PATH=tmp/modules_install
    ~/linux-imx6$ find tmp/lib/modules/ -type d -exec rm -f {} \;
    ~/linux-imx6$ sudo cp -ravf tmp/lib/modules/* /media/alip/lib/modules/

    Note the use of a staging directory in tmp and the find command to remove symlinks.

    • VarsMolta March 2, 2014 2:14 am #

      When I cross-compile the kernel according to your instructions, I am getting a
      “Unable to read file /boot/uImage” error in uboot.

      I manually tried the following on the stock uImage
      U-Boot > ext2load mmc 1:1 10800000 /boot/nitrogen6x/boot/uImage
      3759420 bytes read

      and it works.

      But when I do
      ext2load mmc 1:1 10800000 /boot/uImage, I get the following:
      invalid extent block
      ** Unable to read file /boot/uImage **

      Am I missing some step in building uImage?

  3. hre1 December 23, 2013 4:45 am #


    i tried to download the above sd image, but your system redirect me always to my login page. there is no problem to download the old images (26.09) but this here fails. can you please guide me what i am doing wrong?

    thanks in advance!

    • ericn December 23, 2013 6:30 am #

      Are you able to login outside of the download page?

      I don’t think that the site requires the use of cookies or uses pop-ups.

      Can you re-try with a different browser?

  4. hre1 December 23, 2013 10:38 am #

    Yes i was able to login from outside of the download page. After restarting my Windows Laptop i could download the image file. I don’t no why, but it is Windows not Linux… ;-)

    Thank you very much for your very fast response!

    P.S. I own a wandboard quad. Can i use the image on this board?

  5. Tom January 6, 2014 11:29 am #

    Does this image support xrandr and screen rotation? xrandr is install in this image but when I try
    to rotate the screen using
    “xrandr -o left” it returns a error message
    X Error of failed request: BadMatch (invalid parameter attributes)
    Major opcode ……. 140 (RANDR)
    Minor opcode …. 2
    Serial number …. 14

    So does this display driver support rotation?
    Is there some configuration I need to change to make it work?

    What I want to do is set the screen resolution to 1080p and have it rotated (portrait) and then test playing 3 movies at the same time on the screen.

    We are looking at using the i.Mx6 for a Digital signage device so I am trying to see how well it performs
    in portrait mode at full resolution.


    • ericn January 6, 2014 12:27 pm #

      Hi Tom,

      The Vivante X11 driver doesn’t support XRANDR extensions, so you’ll need to switch to “fbdev” by editing /etc/X11/xorg.conf like so:

      Section "Device"
          Identifier  "Unaccelerated Framebuffer Device"
          Driver "fbdev"
          Option      "fbdev"     "/dev/fb0"
          Option "Rotate" "CW"
          Option      "HWcursor"  "false"
      Section "ServerFlags"
          Option "BlankTime"  "0"
          Option "StandbyTime"  "0"
          Option "SuspendTime"  "0"
          Option "OffTime"  "0"

      Then restart X like so:

      # /etc/init.d/lightdm restart
      • ericn January 6, 2014 12:30 pm #

        Hi Tom,

        I hit Send before also saying that there is a rotate option for the mfw_v4lsink gstreamer video sink element, but we recommend pre-rotating videos when possible to reduce the memory bandwidth.

        • Tom January 12, 2014 10:01 am #

          Yes that worked – thanks.
          So does this means there is no hardware acceleration or does the freescale driver still provide some acceleration for the Framebuffer?

          So is there anyway in linux to get hardware acceleration and still have rotation support?
          I know the IPU/GPU/VPU support rotation but I am guessing it is not available in Linux?

          I have run the Android build and it seem that at least movie play back is accelerate in portrait mode ( I played 3 movies at the same time on the screen with low cpu usage) but I have not run any test to see if everything else is still accelerated.

          So is this just an issue with X11? Would something like Wayland work with accelerated rotation?
          It seem Wayland is working but not any completed window managers for Wayland.

          Anyway thanks again

          • ericn January 12, 2014 10:53 am

            Hi Tom,

            Right: Xrandr (rotation) is not yet supported with GPU acceleration (see this note on i.MX Community).
            I hope this is addressed in the upcoming 3.10.17 GPU release.

            Android does use the GPU to do rotation quite successfully, but using a completely different architecture.

  6. Bruno January 17, 2014 6:54 am #

    i’m having problems to use the OV5640 camera on Sabre Lite. I load mxc_v4l2_capture and ov5640_camera modules with mprobe command but I’m getting a error message when I try to capture video using the GStreamer:

    gst-launch-0.10 mfw_v4lsrc capture-mode=5 ! mfw_v4lsink
    Setting pipeline to PAUSED ...
    ERROR: Pipeline doesn't want to pause.
    Setting pipeline to NULL ...
    Freeing pipeline ...

    I searched a solution but anything yet.


    • ericn January 17, 2014 8:01 am #

      Hi Bruno,

      What messages do you get out of the kernel (dmesg | grep -i 'ov\|v4l')?

      I assume that you’ve copied over the MIPI kernel and modules as described above, and the command-line you posted should just work.

      The connection to the MIPI camera can be a little finicky. You’ll definitely want to double-check that.

      • Bruno January 17, 2014 10:10 am #

        Hi Eric,

        sorry, the kernels and libraries tree were not copied correctly (now i copied from nitrogen6x_mipi correctly) and it’s running for capture-mode 5 and 4.

        Thanks for the fast help,

      • Bruno January 17, 2014 1:04 pm #


        I need to use OpenCV and it’s only works with standard v4l2, then I thought I could use a webcam for this.
        So, does the kernel support usb cameras? I loaded the uvcvideo module but /dev/video0 isn’t created.


        • ericn January 17, 2014 1:13 pm #

          The kernel should absolutely support uvcvideo, though it isn’t compiled in by default (in nitrogen6x_defconfig).

          Are you seeing the camera using lsusb or cat /proc/bus/usb/devices?

          • Bruno January 17, 2014 4:21 pm


            When I execute lsusb, i see the camera (and others things):
            [pre]Bus 002 Device 004: ID 041e:4034 Creative Technology. LTD Webcam Instant[/pre]

            But when I execute [pre]cat /proc/bus/usb/devices[/pre], i see:
            No such file or directory

            Even when I use a pendrive (I mount it manually), I get the same result with the cat command.

          • ericn January 17, 2014 4:25 pm

            Hi Bruno,

            Some userspaces don’t mount /proc/bus/usb automatically. You can do this by hand like so:

            # mount -t usbfs none /proc/bus/usb
            # cat /proc/bus/usb/devices
            T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
            B:  Alloc=  0/800 us ( 0%), #Int=  2, #Iso=  0
            D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
            P:  Vendor=1d6b ProdID=0002 Rev= 3.00
            S:  Manufacturer=Linux 3.0.35-g8a7f130-dirty ehci_hcd
            S:  Product=Freescale On-Chip EHCI Host Controller
            S:  SerialNumber=fsl-ehci.1
            T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=1.5  MxCh= 0
            D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
            P:  Vendor=046d ProdID=c00e Rev=11.10
            S:  Manufacturer=Logitech
            S:  Product=USB-PS/2 Optical Mouse
            C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 98mA
            I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
            E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

            The nice thing about /proc/bus/usb is the fragment that shows you what driver is claiming a device (see usbhid above). It can tell you whether the USB device id was recognized by the device driver.

            If you have a brand-new camera, it’s possible that the uvcvideo needs an update to include the USB VID/PID pair.

          • Bruno January 17, 2014 4:56 pm

            I did it and I got:

            T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
            D:  Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
            P:  Vendor=041e ProdID=4034 Rev= 1.00
            S:  Manufacturer=Creative Labs  
            S:  Product=WebCam Instant 
            C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=160mA
            I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
            I:  If#= 0 Alt= 1 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS= 128 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
            I:  If#= 0 Alt= 2 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS= 192 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
            I:  If#= 0 Alt= 3 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS= 256 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
            I:  If#= 0 Alt= 4 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS= 384 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
            I:  If#= 0 Alt= 5 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS= 512 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
            I:  If#= 0 Alt= 6 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS= 768 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
            I:  If#= 0 Alt= 7 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
            E:  Ad=81(I) Atr=01(Isoc) MxPS=1023 Ivl=1ms
            E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

            Ok, in this case the camera doesn’t need a driver. What’s next step?


          • ericn January 17, 2014 5:12 pm

            Hi Bruno,

            You always need a driver, and in this case, it looks like you want the GSPCA driver and need to include the “ZC3XX USB Camera Driver” option.

          • Bruno January 18, 2014 6:35 pm

            Hi Ericn,

            finally I got it! I had never compiled a kernel, but following the instruction above (and spending much time with my mistakes) I compiled the kernel with both ov5640 and gspca drivers and the cameras are running correctly.

            Thank you very much,

          • ericn January 18, 2014 9:22 pm

            Glad to hear it!

  7. jung February 14, 2014 2:22 am #

    i am triyng to make the ov5640 CSI camera work
    I followed the instruction of nitrogen6x_mipi copy.
    what do i have to do next ? recompile the kernel ?
    if I just copy the files and boot my Sabre Lite board, gst-lauch returns the same erros as Bruno :

    Setting pipeline to PAUSED …
    ERROR: Pipeline doesn’t want to pause.
    Setting pipeline to NULL …
    Freeing pipeline …

    • ericn February 14, 2014 8:05 am #

      Hi Jung,

      Whose OV5640 camera are you using? We have some fledgling support for a camera on CSI1 (re-mapped EIM pins), but we’re not yet ready to offer that camera.

  8. KaiDa February 26, 2014 6:54 am #

    Hi, I just git my Nitrogen6X and i can’t find a way to use the can and ic2 bus.
    I pretty much looked arround a bit but couldnt figgure out to use it.

    can0 nor ic2 wont show at ifconfig

    can anyone tell me how to use these things?

    my hdmi monitor also just boots to 640×480 even with the stock bootscript.


    • danielo June 4, 2014 8:45 am #

      I have the same problem. I’ve been looking around how to change the configuration for the hdmi but always starts at 640×480, even with:

      [ 17.705] Kernel command line: enable_wait_mode=off video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200 vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p1 mxc_hdmi.only_cea=1

      This is a part of Xorg.0.log.

      [ 17.994] (–) VIVANTE(0): Virtual size is 640×480 (pitch 640)
      [ 17.994] (**) VIVANTE(0): Built-in mode “current”: 25.2 MHz, 31.5 kHz, 60.0
      [ 17.994] (II) VIVANTE(0): Modeline “current”x0.0 25.20 640 656 752 800 4
      80 490 492 525 -hsync -vsync -csync (31.5 kHz b)

      Do you know what to do?

      • ericn June 4, 2014 8:58 am #

        Can you check in /sys for the supported modes on your monitor?

        ~/$ cat /sys/class/graphics/fb0/modes
        • danielo July 16, 2014 4:39 pm #

          It gives me this:
          root@linaro-alip:~# cat /sys/class/graphics/fb0/modes

          • ericn July 16, 2014 4:57 pm

            Hi Danielo,

            I think you’re going to need to hack your boot script to configure things for 1080P here:

            You can use the on-line tool to compile the script here:
            Boot Script Compiler.

            You should be able to just replace the 1280x720 with 1920x1080.

          • danielo July 17, 2014 8:04 am

            Thanks, it works.

  9. VarsMolta March 1, 2014 9:40 pm #

    Can you please point to just the rootfs image for this? And how did you install the gstreamer binaries? I have a custom imx6 board that I’d like to run Raring on. Thanks

    • ericn March 2, 2014 8:42 am #

      We don’t have a tar-ball on-line, so you’ll need to extract that by using the .img.gz file.

      The gstreamer binaries were installed using the steps described in this post.

  10. Bernie March 31, 2014 12:51 am #

    I’m trying to use the ov5642 on a BD-SL-i.MX6 using the image without any changes at all with no success.
    dmesg | grep -i ‘ov\|v4l’
    mxc_v4l2_output mxc_v4l2_output.o: V4L2 device registered as video16
    mxc_v4l2_output mxc_v4l2_output.o: V4L2 device registered as video17
    ov564x_powerdown:powerdown=0, power_gp=0x6
    ov564x_powerdown:powerdown=1, power_gp=0x6
    camera ov5642 is found

    when I run
    gst-launch-0.10 mfw_v4lsrc ! mfw_v4lsink
    it reports:
    MFW_GST_V4LSRC_PLUGIN 3.0.8 build on Oct 3 2013 21:00:55.
    MFW_GST_V4LSINK_PLUGIN 3.0.8 build on Oct 3 2013 18:43:36.
    Setting pipeline to PAUSED …
    ERROR: Pipeline doesn’t want to pause.
    Setting pipeline to NULL …
    Total rendered:0
    Freeing pipeline …
    [—>FINALIZE v4l_sink

    Any ideas on how to get this working would be helpful.

    • rbdaviso@rockwellcollins.com March 31, 2014 4:29 pm #

      Further to my previous comment. I’ve tried the Android 4.3 Jellybean image and the camera works just fine.

      Is there something further that needs to be installed to get gstreamer to work in the raring image?
      Also I forgot to mention that I’m running “gst-launch-0.10 mfw_v4lsrc ! mfw_v4lsink” from within an xterm session. Does that effect it?


      • ericn March 31, 2014 4:39 pm #

        Hi Bernie,

        Sorry that I haven’t had a chance to try and repeat this.

        I suspect that the issue has to do with the ‘capture-mode’ parameter.

        Can you try with “mfw_v4lsrc capture-mode=4″?

        • rbdaviso@rockwellcollins.com March 31, 2014 5:00 pm #

          Hi Eric,

          Running “gst-launch-0.10 mfw_v4lsrc capture-mode=4 ! mfw_v4lsink” return the same result.
          I also tried running with capture-mode[0-5] with the same result.

          when I run the gst-inspect-0.10 mfw_v4lsrc and look at the capture-mode. It talks about ov5640. Is this default data?

          • Bernie July 10, 2014 4:18 pm

            This issue is caused by the camera module not being loaded.

            It can be resolved by running “modprobe mxc_v4l2_capture” which loads the required modules.

  11. Michael April 3, 2014 10:52 pm #


    Thanks for this great image. It runs very nicely on my new nitrogen6x board.

    I am extremely interested in the transparency effect, as I would like to use something like this in my app. However, I do (currently) not understand, how you did this?

    The video is running in the background, right? Windows are on top, but partly translucent (colorkey?). The video is on top of the system background, however. Well, in the end, it is great and exactly what I need.

    However, I cannot reproduce it without lighdm. If I stop lightdm and start X with xinit, I get a black screen with a white xterm window (which is expected). When I then start a video via gplay or gst-launch, it is completely overlayed over everything. The background and the xterm window is invisible. I’d like to have the video in the background and the window on top. Please, comment on how you did this here.

    Thanks a lot


  12. Steven April 18, 2014 6:55 pm #

    Is anyone else seeing high load on this build (top/uptime reports ~4.0)?

    Top shows:
    top – 19:09:15 up 9 min, 2 users, load average: 4.00, 3.40, 1.83
    Threads: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.2 us, 0.3 sy, 0.0 ni, 98.9 id, 0.6 wa, 0.0 hi, 0.0 si, 0.0 st

    As you can see there is only one process running (top) and the cpu utilization is low. So what’s up with the load?

    Any ideas?

  13. Steven April 19, 2014 7:02 pm #

    Hey again folks!

    another day another issue it seems like. This time it is trying to bring up hostapd. something is missing and I can’t figure it out/too blind to see it.

    iw shows AP as a mode for the TiWi module, so I know it can do it. got to be a module problem. But can’t set mode 3.

    When I try to run hostapd it spits out an error and dies:
    BSS count 1, Bwl1271: ERROR command execute failure 16 SSID mask 00:00:00:00:00:00 (0 biwl1271: ERROR PROBE request template failed ts)

    I am a little slow, can someone walk me through the process on getting/configuring/compiling the kernel modules wl12xx so they will work with hostapd?

    I can’t be the only one wanting to use this raring image as an AP can I?

    Thanks for the help!

  14. Snitrog666x April 25, 2014 9:55 am #

    Hi guys, I’m using this image(alip-gpu-gstreamer-20131219.img.gz) on a nitrogen6x devkit ( som + carrier board + mPCIe to PCIe daugher board). It runs successfully, but we got a problem about pcie 16x adapter detection. Please kindly help to give some advice.

    The problem is: there is nothing output for ‘lspci’ when we plugged in a general PCIe 16x device (e.g. a graphics card), however, ‘lspci’ shows correct information when we plugged in a PCIe 1x deivce (e.g. a 1394 board).

    Suppose this devkit should be capable to support PCIe 16x device, right? If so, is this a image reason that we can’t do such detection?

    Appreciate for the help!

  15. aNordal May 22, 2014 3:17 pm #

    Tip: Set the dhclient timeout to 1 (in /etc/dhcp/dhclient.conf), and sed -i “s/auto eth0/allow-hotplug eth0/” /etc/dhcp/dhclient.conf. That reduced my boot time from 2min 15s down to about 15s. I normally don’t boot with eth0 connected.

    Question: I’m not seeing console messages during boot. Maybe plymouth is blocking it. I was able to uninstall plymouth-theme-* stuff, but “plymouth” itself is uninstallable due to hard dependencies… (Btw, plymouth asserts at shutdown.)

  16. aNordal June 15, 2014 3:50 pm #

    This kernel (3.0.35-02855-g3fccb21) lacks a fuse module. I wanted to use sshfs.

  17. steve July 2, 2014 4:41 pm #


    Whats the password? I want to make some changes to the settings. The os keeps asking for a password.

  18. kimokono July 16, 2014 6:07 pm #


    I couldn’t get network using this image. Ethernet does’t work. there are no indicators. I think that there is no LAN driver.

    anybody faced such a problem or can help fixing the issue.

    thank you

  19. ericn July 18, 2014 11:59 am #

    Hello Kimokono,

    This image absolutely supports networking through both Ethernet and (with configuration) WiFi.

    What kind of hardware are you running on?

  20. aNordal July 27, 2014 6:08 am #

    Has Raring gone out of support?
    `aptitude update` fails (with various “W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/raring/“* errors). I have checked my internet connection – using it to post this ;)

    Ideas for the next distro:
    * Don’t forget the “fuse” kernel module!
    * How viable is the mainline kernel now, after the device tree for nitrogen6x got mainlined?
    * Rolling release distro? (I’m a fan of OpenSuse Tumbleweed. I got OpenSuse working on my Hackberry A10, would be glad to help).

    Ethernet & Wifi working fine here (Nitrogen6x). However, NetworkManager (click the tray icon in LXDE) says “Ethernet Network device not managed”. Apparently, it is managed by ifup, at least `sudo ifup eth0` (after inserting the ethernet cable) works for me.

    Btw, I’m impressed with the range of the WiFi (I was out in the garden today).
    Pictures of my Nitrogen6x Laptop on my blog:

    • ericn July 27, 2014 12:14 pm #

      Hi aNordal,

      Yes, Raring is now out of the support window, along with Saucy, and I’m testing the latest Ubuntu (Trusty) now.

      root@nitrogen:~# zcat /proc/config.gz | grep -i FUSE

      Our immediate plans don’t involve any Suse releases, but do also include Debian. Packaging for any one of these is difficult (especially getting the closed-source bits to work properly).

      The main-line kernel is reportedly pretty stable and has a lot of feature, but again, the closed-source acceleration bits are not supported. The folks at Denx have reportedly had GPU-acceleration working, but we haven’t had a chance to spend any time there.

    • ericn July 27, 2014 12:15 pm #

      BTW, your garden looks very appealing.

      It’s over 110F here in the desert of Arizona right now.

    • ericn July 28, 2014 5:20 pm #

      Hi aNordal,

      Note that the Trusty image is now on-line at:


Leave a Reply