Raspberry Pi

• Raspberry Pi Homepage
• Raspberry Pi Store

• R-Pi Troubleshooting
• Raspberry Pi fix for HDMI to DVI cable issue

• Getting started with NOOBS
• Raspberry Pi Initial Setup: Headless - no monitor or keyboard needed

• Installing Raspbian from NOOBS without display
• The HTG Guide to Getting Started with Raspberry Pi

Starting up with a new SD card

1. HOW TO INSTALL NOOBS ON AN SD CARD
2. Set language, keyboard and timezone

Updaing Raspbian

• UPDATING AND UPGRADING RASPBIAN

First, update your system's package list by entering the following command:

sudo apt-get update

Next, upgrade all your installed packages to their latest versions with the command:

sudo apt-get dist-upgrade

Generally speaking, doing this regularly will keep your installation up to date, in that it will be equivalent to the latest released image available from http://raspberrypi.org/downloads.

However, there are occasional changes made in the Foundation's Raspbian image that require manual intervention, for example a newly introduced package. These are not installed with an upgrade, as this command only updates the packages you already have installed.

Enable SSH

• ENABLE SSH

Make the device discoverable by name for Windows

sudo apt-get upgrade

sudo apt-get install samba samba-common-bin

Restart the samba:

sudo service smbd restart

Enable Microsoft Remote Desktop clients to connect to Raspberry Pi

sudo apt-get install xrdp

Apparently there is a/are defect(s) which prevent xrdp working with the vncserver.
However it works with tightvncserver.
Also the order of installation of tightvncserver and xrdp seems to be important.
In summary remove the following packages : xrdp, vnc4server, tightvncserver.

sudo apt-get remove xrdp vnc4server tightvncserver

install tightvncserver followed by xrdp

sudo apt-get install tightvncserver

sudo apt-get install xrdp

Printing to Canon inkjet printers

Components

• CUPS
• BJNP - readme at bottom of page explains how to install install

Google cloud printing

• - Chromium User Data Directory

Troubleshooting

View the CUPS error log for debugging and troubleshooting purposes

Edit the /etc/cups/cupsd.conf file, find the section "loglevel" change "info" to "debug" save and exit then restart cups

1. /etc/init.d/cups restart

or for Ubuntu

$ sudo /etc/init.d/cupsys restart then enter this command to view the log

tail -f /var/log/cups/error_log

Misc

• It's working! thx man! the avahi-daemon "manipulation" was the problem. like you have said - Read last post at bottom of page

<google>ENGELSK</google>