Jul 262013
 

Ab sofort bieten wir mit der LibreOffice Edition eine Auswahl von drei Raspberry Pi Kits mit dem LibreOffice Logo auf dem Gehäuse des beliebten Mikrocomputers.

libreoffice-pi-array

Alle Raspberrys sind von Werk aus mit drei Kühlkörpern ausgestattet:

libreoffice-vormontiertes-coolkit

Wir haben drei Kits zusammengestellt:

LibreOffice Raspberry Essentials Kit

Dieses Kit enthält den Raspberry im LibreOffice Gehäuse, eine 8 GB Class 4 SD Karte und ein 1 A Netzteil – falls alles andere (HDMI Kabel, WiFi Stick, …) bereits bei Ihnen vorhanden ist, eine exzellente Wahl. Klicken Sie hier, um das LibreOffice Raspberry Essentials Kit im Shop anzuschauen.

LibreOffice Raspberry Fun Kit

It takes two to Tango – zwei Ampere. Mit diesem Netzteil sind Sie beim Übertakten mit guten Sicherheitsreserven unterwegs. Das Netzteil wird mit vier international passenden Steckeraufsätzen ausgeliefert, so dass Sie Ihren Raspberry in einer Vielzahl von Staaten ohne Probleme direkt anschließen können. Zusätzlich enthält das Kit noch einen vier-Port USB Hub mit eigenem Netzteil, einen USB WLAN-Adapter, und eine größere 16 GB SD Karte. Klicken Sie hier um das Fun Kit im Shop anzuschauen.

LibreOffice Raspberry Complete Kit

Dieses Kit enthält wirklich eine Komplettaustattung: Zusätzlich zum Fun Kit sind hier ein hochwertiger ASUS 21,5’’ Full-HD Monitor, und die Logitech K400 Funktastatur mit eingebautem Touchpad enthalten. Den Raspberry können Sie mit unserem VESA Kit bequem hinten am Monitor befestigen.

complete-kit

Klicken Sie hier um das Complete Kit im Shop anzusehen.

Mit jedem gekauften Kit spenden Sie automatisch 5 € an die Document Foundation, die hinter LibreOffice steht.

Jul 252013
 

Anbei das Schaltbild für einen 5V Regulator.

Am Eingang können 7-18V anliegen. Am Ausgang bekommt ihr immer 5V. Ihr könnt auch mehrere parallele Ausgänge bauen.

13-07-25

Zum USB-Kabel:

Wenn ihr das USB-Kabel aufschneidet, werdet ihr 4 (oder mehr) bunte Einzelkabel finden. Das rote ist eure Spannungsversorgung, das schwarze die Masse.

Quellen:
http://www.flytron.com/camera-transmitter-shutter/93-tiny-5volt-regulator.html

 Posted by at 1:44 pm
Jul 232013
 

Update

We have released dfreerdp (FreeRDP for the DirectFB backend) as a package for the Raspberry Pi. Please go to our new blog post to get it!

Intro

RDP is a convenient way to connect to Windows and also other operating systems with RDP host software, e.g. Linux. RDP transmits display information more efficiently than VLC, as it sees the structure of the screen and it’s elements. It also allows to transmit audio information both ways – playback and recording, share printers, drives, and more. As it is an extensible protocol, efficient video / multimedia playback can be implemented – and has been implemented, albeit apparently only in Windows Media Player.

The Raspberry Pi is a low-power device, with Full-HD (and audio) capable HDMI output.

FreeRDP is a mighty utility to connect to RDP servers, and utilize many of their possibilities. It even supports the video extensions for RDP (in RDP lingo: video redirection virtual channel extension) with ffmpeg. Don’t get your hope up too high right now, though: while theoretically feasible in software, it still would have to be written for both the Raspberry AND the host (it is not a “plug & forget” solution, but the software run on the server has to support it specifically).

The current state: A marriage made in heaven?

Not quite. FreeRDP is easily installed, and used from an X session. But it is … agonizingly slow. Audio playback is in a bad state.

The problem: X adds a very high overhead to any application, but even more so a graphics intensive, such as FreeRDP. Even super-charging the Raspberry Pi with overclocking, Class 10 SD cards, a beefy power supply, etc. will NOT solve this problem! An RDP client compiled specifically for Wayland might, but this is still some way off.

Solution

FreeRDP can be compiled to draw to the Direct Frame Buffer. This eliminates all of the overhead, which X would add. This is perfect for people really trying to use the Raspberry as Windows / RDP thin client. It will work in FullHD resolution (over the local network), with sufficient performance (and 16 bit color depth).

Kudos are in order to the Tao of Mac blog, which had the idea, and the instructions to get me up and running. You rock!

We will release a hardware & software package RDP client, based on the Raspberry, really soon now. If you’re interested, hit me up in the comments.

Step-by step instructions

With all that out of the way, let’s jump into the instructions!

Preparation

We suggest to use a Class 10 SD card, with ample space for the installation & build of the packages (8 GB Class 10 seems sensible). Install the newest Raspbian image, set up your locale and keyboard layout, aptitude update and aptitude upgrade.

Install the necessary packages:

aptitude install build-essential git-core cmake libssl-dev libx11-dev libxext-dev libxinerama-dev libxcursor-dev libxdamage-dev libxv-dev libxkbfile-dev libasound2-dev libcups2-dev libxml2 libxml2-dev libxrandr-dev libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libavutil-dev libavcodec-dev libcunit1-dev libdirectfb-dev xmlto doxygen libxtst-dev

This should take quite a while.

Download the FreeRDP package (use a sensible location, we will be compiling there later. If in doubt, a sub-folder in your home folder is OK):

wget https://github.com/FreeRDP/FreeRDP/archive/1.0.2.tar.gz

You might also consider checking out the 1.0.3 pre-release version. It might turn stable in a couple of months.

Set up the build environment – this is analoguous to ./configure seen in many other compilations:

cmake -DCMAKE_BUILD_TYPE=Release  -DWITH_FFMPEG=OFF -DWITH_XINERAMA=OFF -DWITH_XCURSOR=OFF -DWITH_DIRECTFB=ON -DCMAKE_INSTALL_PREFIX=~/freerdp

A couple of hints for this:

  • You might want to adjust the –DCMAKE_INSTALL_PREFIX to something more suitable – if you compile as root, it will install the application and the libraries into the folder /root/freerdp otherwise.
    A good choice could be /usr – this way the binaries and libraries will be in the normal search path.
  • turning off FFMPEG means turning off virtual video extension. As discussed before, this is of limited use anyway, right now. But some experimenting might be interesting. FreeRDP also is built modularized on top of FFMPEG, so exchanging that for an omxplayer-like code thingy SHOULD be feasible.
  • Xinerama – is an X extension which allows X applications to span two or more displays a one large virtual display.

Check for the output of this command. It will tell you about skipped options and missed packages. It should find DirectFB amongst others (Found DirectFB: /usr/lib/arm-linux-gnueabihf/libdirectfb.so).

  • pulseaudio: this is a sound server, and another layer on ALSA. It is network capable. Users report varying mileage with pulseaudio and good playback quality. We have tested without the pulseaudio package, future tests will show whether there is an advantage in using it.
  • pcsc – this is for smart card support, most likely you will not need it
  • CUnit – a lightweight system for writing, administering and running unit tests in C – most likely you will not need this, either.

Compile the DirectFB RDP client:

cd client/DirectFB/
make

#optionally 
sudo make install

#for sound support
cd ../../channels/drdynvc
make
sudo make install
cd ../rdpsnd
make
sudo make install

This is all – but this will take quite a while (some hours).

Set up some configuration files

Edit your /etc/udev/rules.d/99-input.rules to be:

SUBSYSTEM=="input", GROUP="input", MODE="0660"
KERNEL=="tty[0-9]*", GROUP="root", MODE="0666"
KERNEL=="mice", MODE="0666"
KERNEL=="fb0", OWNER="root", MODE="0660"

The first line should aready be in the file, add the other three lines.

Optional, but recommended: Edit your /boot/config.txt to contain the following settings:

framebuffer_width=1920
framebuffer_height=1080
framebuffer_depth=16
# for other stuff
gpu_mem=128

arm_freq=800
disable_overscan=1
hdmi_drive=2
hdmi_ignore_edid=0xa5000080

This will

  • set your resolution as fixed [framebuffer_width, framebuffer_height] – be sure to adjust to your needs!
  • set bit depth to 16 – as we will connect to the RDP server using this depth for better performance.
  • ignore anything the monitor will tell the Raspberry – it might lead to blurry edges, otherwise [hdmi_ignore_edid=0xa5000080]
  • overclock the raspberry just a little [arm_freq=800]
  • disable the overscan – remove the black area around the display output on modern LCD monitors [disable_overscan=1]
  • set up the HDMI output to be a real HDMI output and carry audio – this will fix “no sound output” problems [hdmi_drive=2] don’t use this if you connect your Raspberry via DVI or VGA to the monitor

Edit /etc/fb.modes and add a new mode:

# Added as per taoofmac instructions
mode "1920x1080-24p"
   geometry 1920 1080 1920 1080 32
   timings 13468 148 638 36 4 44 5
endmode

You will have to adjust this if you use a different resolution than FullHD. The original article at Tao of Mac has some more resolution examples for you.

Create a new file /etc/directfbrc with the following contents:

system=fbdev
autoflip-window
desktop-buffer-mode=auto
vt-switching
graphics-vt
no-deinit-check
no-motion-compression
no-translucent-windows
memcpy=arm
mode=1920x1080
depth=16
dma
hardware
# for the moment, we need DirectFB's own cursor sprite
cursor

Reboot.

 

Usage

If you specified –DCMAKE_INSTALL_PREFIX to be /usr, you should be able to use FreeRDP DirectFB client without any path prefix, else just prepend your path:

dfreerdp -u "user name" -p secret_password_here -f -g 1920x1080 -x l -z --disable-full-window-drag  --gdi hw --plugin rdpsnd --data alsa --  host:port

Be sure to adjust this command:

  • “user name” should be your user name. If it contains a space, you should keep the quotation marks, else you can loose them.
  • secret_password_here should be your password, obviosly.
  • -g specifies the geometry. Adjust, as necessary.
  • -x = experience (l for LAN), will enable different bells and whistles. You might want to modify that, or use a more finegrained control of which features to enable, and which to disable
  • -z enable compression (useful)
  • –gdi hw – I’m not sure whether this is really necessary
  • –plugin rdpsnd –data alsa —  – this will enable remote sound output on the Raspberry. Drdynvc is said to have better quality, but I could not get it to work unfortunately. And, yes, the trailing double dashes are part of this option.
  • server:port – can be specified as domain or IP adress. The :port can be omitted, if you are connecting to the default RDP port (3389)

If you want sound output on the remote machine, use the –o switch.

 

FAQ

What about keyboard layout?

It will work exactly as you see your keyboard input on the Raspberry console itself. Even the Windows key should work. If your layout does not work on the Raspberry console, consider setting it up using raspi-config

Will this work over WLAN?

Sure it will. Just adjust your WiFi dongle for optimum throughput and latency (yes, literally change its position, tilt, etc. until you find the best performance spot!)

We recommend you the following packes for graphical / console adjustment of Wireless settings:

aptitude install wicd wicd-gtk wicd-curses

Will Skype work?

Not tested yet – enlighten us Smile This will need microphone redirection, too.

Will forwarding of devices work?

Not tested yet – inform us about usb printers, thumb drives, etc.

How can I test sound output on the Raspberry?

aplay /usr/share/scratch/Media/Sounds/Vocals/Singer2.wav -v -V mono

Will performance over WAN networks be OK?

Yes, pretty much – sound output will suffer (a lot), but the GUI will still be quite usable. You might want to adjust the flags to disable some eye candy.

Why do the browsers “stutter” during scrolling?

In my understanding: Unfortunately browsers need a very high degree of control over their screen outputs, and thus they render it themselves, instead of letting Windows do it – RDP sees browser output as image, which is retransmitted when scrolling. Playing with image compression options might alleviate this problem a bit.

Will accessing Linux hosts over RDP work?

Not out of the box – you will need to install an X to RDP conversion software.

In a very quick and rough test, a connection set up by the Scarygliders X11 RDP O Matic as a server backend did not work reliably enough (it was installed on a Pentium IV Linux server). It might do so with some tuning.

Or another backend / solution might do the trick. Looking forward to your input Smile

 

Known problems

  • Flash (isn’t it always on some list?) – will deliver horrible audio performance, native players (Foobar2000) will be OK, though.
  • Video playback – don’t even dream of playing YouTube videos over an RDP connection … the time is not ready yet, the software not written. Care to join a noble cause?
  • WLAN performance will depend on WLAN throughput and latency. The orientation of your dongle – especially nano dongles – will be very important. It can be tuned to a decent performance state, though.
  • I can’t get the new / style switches to work with FreeRDP, fallback to the legacy – switches for now.
  • Sound output: only rdpsnd works, –plugin drdynvc –data tsmf:audio:alsa:plughw:0,0 — will not work – maybe this is a configuration issue, though and some other parameters need to be passed. Drdynvc is said to have better quality. The issue might be with servers with no sound card drivers installed. I did not find an easy solution to this, and I am looking forward to your suggestions.
  • Connection to Linux RDP server compiled with X11 RDP O Matic is not stable for me.

References & further reading

Jul 232013
 

Hintergrund

Auf dem Raspberry Pi befindet sich “von Werk aus” kein grafischer Netzwerk-Manager. Es ist also die Kommandozeile gefragt, was manchmal unbequem, lästig oder mit Fehlern verbunden sein kann.

Wir stellen in diesem Artikel daher kurz vor, wie man unter Raspbian mit Wicd einen grafischen Netzwerk-Manager aktiviert.

Installation

Öffnen Sie LXTerminal und installieren Sie die benötigten Pakete:

sudo aptitude update
sudo aptitude install wicd wicd-gtk wicd-curses

Nutzung

Nach Neustart von X erscheint in Ihrer Notification Area rechts unten ein neues Icon. Durch Klick auf dieses Icon können Sie sowohl LAN, als auch WLAN Netzwerke mit einer Vielzahl von Möglichkeiten verwalten.

Wicd-Icon

Durch Rechtsklick auf das Icon, und Auswahl von “Connection Info” kann man seine aktuelle IP Adresse herausfinden:

wicd-show-ipadress

Alternativ kann Wicd auch aus dem Menü gestartet werden:

Wicd-start

Wicd zeigt die verfügbaren Funknetzwerke an:

wicd-manager

Durck Klick auf “Connect” kann man sich zu einem Netzwerk verbinden. Falls es eine Passwort-Eingabe erfordert, weist Wicd den Nutzer darauf hin, und öffnet den “Properties” Dialog.

Für die meisten Netzwerke wird es hier nur erforderlich sein, den Preshared Key einzugeben. Wählen Sie aus dem Menü “WPA 1/2 (Passphrase)”, und geben Sie Ihren Preshared key ein.

wpa-properties-dialogue

Nach Klick auf OK drücken Sie erneut “Connect” um sich mit dem Funknetzwerk zu verbinden. Der Erfolg wird in der Statuszeile unten angezeigt:

wicd-connected

WLAN Konfiguration unter der Konsole

Mit Wicd kann man die Funknetzwerkeinstellungen auch unter der Konsole – ohne X Session – verwalten. Geben Sie dazu einfach ein:

sudo wicd-curses

wicd-curses

wicd-curses wird mit der Tastatur bedient. Das Menü unten zeigt die möglichen Eingaben an.

Mit Pfeiltaste nach rechts wird der aktuell ausgewählte Eintrag bearbeitet. Hier kann man die IP Einstellungen, die DNS Einstellungen und den Preshared Key eingeben. Außerdem kann festgelegt werden, dass eine Verbindung zu diesem Netzwerk automatisch hergestellt werden soll. Mit F10 bestätigt man die Einstellungen. Anschließend kann man Q drücken, um wicd-curses zu verlassen.

Weiterführende Informationen & Quellen

Jul 182013
 

Taking pictures is savoring life intensely, every hundredth of a second. (Marc Riboud)

raspberry-pi-kamera-vorbestellen

Die Raspberry Pi Kamera – in den Stückzahlen die Sie wollen, ist sofort lieferbar, in unserem Shop. Kaufen Sie nur die Kamera, oder vielleicht gleich ein praktisches Kit dazu.

Sonderaktion: Rabatt für unsere Vorbesteller

Für alle die über unser Formular vorbestellt haben bieten wir als Dankeschön einen Rabatt in Höhe von 3,50 € pro Kameramodul – Sie sparen sich so die Versandkosten für das erste Modul. Wenn Sie mehr bestellen, sparen Sie mehr – unabhängig davon, wieviel Sie bei der Vorbestellung (bis 17.07.2013 24:00) angegeben haben – bestellen Sie jetzt, wieviel Sie wirklich haben möchten.

Diese Rabattaktion läuft bis nächsten Freitag, 26.07.2013, Mitternacht. Danach können wir leider die Vorbestellungen auch nicht mehr bevorzugt behandeln.

Jul 142013
 

Nach Berichten mehrerer Kunden sind die von uns in diversen Kits mitausgelieferten HDMI / DVI Adapter mit bestimmten Monitoren nicht kompatibel. Wir bitten betroffene Kunden uns zu kontaktieren, wir tauschen die Adapter gegen ein anderes Modell (von Logilink) kostenfrei aus. Auf dem betroffenen Adapter ist kein Herstellername angegeben, es handelt sich um einen HDMI female / DVI male Adapter.

Unsere Devise ist: proaktiv handeln, und Probleme für unsere Kunden zu minimieren. Wir entschuldigen uns für die Umstände, und danken den Kunden die sich gemeldet haben.

Jul 032013
 

That’s what we all want to see – a functioning, lightning-fast modern browser on the Raspberry Pi.

Some resources I collected on the web look pretty promising.

XWayland server

The XWayland server has already been demoed, although not released to the broad public yet. We have seen Midori (or Chromium?) and LibreOffice running on top of it. Pretty smoothly, it seems.

This SHOULD be available soon and support all “classical” X software.

The future: Webkit

The company Igalia, amongst many others, is working to allow WebKitGTK+ run on a Wayland backend.

WebKit is the base of the most modern browsers (even Opera started to use it, AFAIK. One notable exception of course is Microsoft with it’s Trident engine. I bet we will grow old to see it arrive on the Raspberry, though).

Epiphany, the default web browser of GNOME, is based on WebKit. Chromium is also based on WebKit.

Igalia has a blog, in which these two entries seem the most interesting to me:

Briefly, this post outlines why it would be a good thing to have the Core IV GPU of the Raspberry do the heavy lifting of layer-composition, instead of the CPU (which could focus on JavaScript, for instance …)

The post explains some background, has a YouTube demo video of Epiphany running under Wayland (showing off some 3D effects) and goes on to outline the current state of the work. “GTK3 is already providing a Wayland backend, WebKitGTK+ needs to use GTK3 only”.

Most notably, full screen video playback (GStreamer) and plugins may be problematic. We all can / should live without Flash by now, which will probably never get ported to GTK3. Adobe’s phasing Flash out, too. HTML5 is the way to go!

As GNOME is betting huge on Wayland, and Epiphany is its flagship browser, it is only a matter of time until Webkit-based browsers (Midori, Chromium, …) WILL be available for the Raspberry Pi.

More Information

is one of the few good collections of the current state of Wayland support. Not everything applies to the Raspberry of course, but we can “feel, see and touch the future” here. GTK+ support seems to be complete – which is quite promising for many applications. It also lists the all-important browsers. Apparently Chromium removed Wayland support?? It was added back in in a fork / patch it seems, this is already one year old.

On the Wayland mailing list it was shared, that Midori has finished preliminary support for Wayland. This is news as of the end of April 2013, and will probably take some time to come to the Raspi. Will midori be the first browser we use with Wayland?

Webkit-clutter seems to be another possible approach to Weston. (Clutter is apparently another application toolkit, an alternative to GTK+). As we all know Collabora is the company behind the Weston/Wayland software on the Pi, we may expect something from this, too. Here’s some more background info on Clutter & Webkit.

Meanwhile:

This video shows a comparison of several browsers available on the Pi. Netsurf does not run JavaScript, this is where the huge performance gains when rendering arise from. Chromium was apparently no easy task to compile for a Raspberry, but it works now – albeit quite slow. We’re not taking it for granted Winking smile

 

Gomoto’s Browser

This is an interesting light-weight WebKit-based browser. Supporting JavaScript, CSS, etc – yet the code is so short you can easily read it, modify it, and recompile it. In fact I have experimented with it tonight.

Read the following thread to obtain more information

Or go directly to Google Code Homepage of “minimal-web-browser”. Download the browser package or the source.

Installation instructions:

  • wget the omxgtk package
  • aptitude install xterm
  • dpkg –i omxgtk_0.1_rc3_armhf.deb
  • wget the web package
  • dpkg –I web_1.0-6_rc3_armhf.deb

now you can start the browser from an X session with “web”.

This browser CAN ALSO SUPPORT YOUTUBE PLAYBACK! You need to create a shell script to support this, and install youtube-dl. The author also added Radio playback.

Guenter Kreidl has built a Minimal Kiosk Browser on the base of Gomoto’s browser. Look at this Raspberry Pi forum thread to find out more. It looks quite promising, incorporating some interesting features (have a look at the README he attached to a post).

FireFox OS for Raspberry Pi

A guy called Philipp Wagner has released a FireFox-based software stack for the Raspberry Pi, which operates without using the X server! It is a mixture of Linux and OpenGL which he runs on top of.

Apparently, right now, there is no input support for mouse / keyboard, but this could be great for digital signage-class systems.

If you like his work, you can get him something nice from his Amazon wishlist Winking smile

I’ll be testing the performance of the FireFox OS after I post this, and will report back in the comments.

Jul 032013
 

Using a Raspberry Pi as a router with AICCU / SIXXS is possible, but there are a couple of “gotchas”.

How-To

Get IPv6 tunnel

Go to SixXS and get your tunnel. (Free) This will be enough to connect the Raspberry via IPv6 to the Internet. If you want to bring other machines online, too, you will need to request and set up a subnet.

(This is in progress)

Add routing for local network

Now, you need to add the routing for the local network. We will assume that the network interface you want to add it to is “br0” (most probably this will be either eth0 or wlan0 for you!). Also, that the /64 network assigned to you by SiXXS is 2001:db8:384e:8888::/64

ip route add 2001:db8:384e:8888::/64 dev br0

Basically, this tells your Raspberry, if traffic is for machines in this network, it should not be forwarded through the SiXXS tunnel, but rather it should be sent out through br0. As I have said before, adjust br0 to eth0 / wlan0 if necessary.

(Note: this should be set up permanently as post-up rule).

Some Cool Things to do with IPv6

Copy Files from one host to another

scp -6 pi@[2001:db8:384e:8888:ba27:ebff:fe18:bb4c]:/scripts/ctemp.rb /webroot/temp/ctemp.rb

This will copy the file “/scripts/ctemp.rb” from the host 2001:db8:384e:8888… to /webroot/temp/ctemp.rb on the local computer, using the username “pi” on the remote computer. Yes, you will be able to do this into your home network, if IPv6 is set up correctly! Never again files forgotten at home Smile

Q & A

Can I have a “normal” router which is separate from the Raspberry for IPv4 routing?

Yes. This is the purpose of the whole idea – the Raspberry acting as “IPv6 gateway” on your local network.

What is 2001:db8::?

This is a special prefix used for documentation purposes. Your real adress will have different numbers / letters in it.

What kind of speed can I expect?

OK, please lower your expectations right now. Maybe there is optimisation potential, but here’s our first quick test:

image

We used ipv6-test.com/speedtest to run the test.

Optimization WordPress Plugins & Solutions by W3 EDGE