Showing posts with label raspbian. Show all posts
Showing posts with label raspbian. Show all posts

Thursday, March 28, 2024

Repositories for Raspbian (Debian Stretch) no longer supported



This is a note on the Raspbian release, but probably will need a similar action for any other ones so expired support
/etc/apt/sources.list
comment out "raspbian" entry and add "legacy" one.
-- old
deb http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi
-- should be
deb http://legacy.raspbian.org/raspbian/ stretch main contrib non-free rpi

need to do apt-update

--30--

Wednesday, January 3, 2024

How to change raspbian / Raspberry pi OS user name

Change user name
https://raspberrytips.com/change-raspberry-pi-username/
https://www.scaler.com/topics/how-to-change-username-in-linux/

allow ssh login for root via ssh
sudo vi /etc/ssh/sshd_config
#PermitRootLogin prohibit-password
PermitRootLogin yes

set password on root
passwd root 

logout of all instances of old user
ssh to host as root

change user name
usermod -l newusername oldusername 

change user directory
usermod -d /home/new_username -m new_username


--30--

Monday, January 24, 2022

broken atomic modeset userspace detected, disabling atomic messages on raspberry pi

Occurs when running headless and no screen resolution set (never had a display attached). 

in  dmesg command log (from kernel)

 pi@pi1: $ sudo raspi-config 


 --30--

Thursday, February 20, 2020

Tuesday, November 26, 2019

Raspbian upgrade process and notes


Upgrade Raspbian releases
https://www.raspberrypi.org/documentation/raspbian/updating.md


sudo apt update
sudo apt full-upgrade 


Check Raspberry pi release
https://www.meccanismocomplesso.org/en/how-to-for-raspberry-checking-the-raspbian-version-update-upgrade/

cat /etc/os-release

make sure lsb_release is installed

sudo apt-get -y install lsb_release
lsb_release -a

--30--

Wednesday, August 29, 2018

mount Raspbian image and modify it


Notes on modifying a raspbian image to add ssh support and
preset for local wifi, so image can be dumped onto sd and be
ready to run.

https://ra...ypi.stackex.../how-can-i-mount-a-raspberry-pi-linux-distro-image

My settings:

fdisk partition info
Device                           Boot  Start      End Sectors  Size Id Type
2018-06-27-...stretch.img1       8192   96663   88472 43.2M  c W95 FAT32 (LBA)
2018-06-27-...stretch.img2      98304 9420799 9322496  4.5G 83 Linux
 
1st partition 512 * 8192 = 4194304
2nd partition 512 * 98204 = 50331648

boot:
mount -v -o offset=4194304 -t vfat 2018-06-27-raspbian-stretch.img /mnt
linux:
mount -v -o offset=50331648 -t ext4 2018-06-27-raspbian-stretch.img /mnt


You can't mount the image as a whole because it actually contains two partitions and a boot sector. However, you can mount the individual partitions in the image if you know their offset inside the file. To find them, examine the image as a block device with fdisk -l whatever.img. The output should include a table like this:
Device         Boot     Start       End  Blocks  Id System
whatever.img1            8192    122879   57344   c W95 FAT32 (LBA)
whatever.img2          122880   5785599 2831360  83 Linux
These are the two partitions. The first one is labelled "FAT32", and the other one "Linux". Above this table, there's some other information about the device as a whole, including:
Units: sectors of 1 * 512 = 512 bytes
We can find the offset in bytes by multiplying this unit size by the Start block of the partition:
  • 1st partition 512 * 8192 = 4194304
  • 2nd partition 512 * 122880 = 62914560
These can be used with the offset option of the mount command. We also have a clue about the type of each partition from fdisk. So, presuming we have directories /mnt/img/one and /mnt/img/two available as mount points:
mount -v -o offset=4194304 -t vfat whatever.img /mnt/img/one
mount -v -o offset=62914560 -t ext4 whatever.img /mnt/img/two
If you get an "overlapping loop" error here, your version of mount requires you to specify the size as well as the offset of the first partition. Unmount that, and use the number of blocks (57344) * 512 (= 29360128):
mount -v -o offset=4194304,sizelimit=29360128 \
    -t vfat whatever.img /mnt/img/one  
The second partition doesn't need a sizelimit since there's nothing after it in the image.
You can now access the two partitions. If you do not intend to change anything in them, use the -r (read-only) switch too. If you do change anything, those changes will be included in the .img file.
Note that the first partition is probably mounted on /boot in the second partition when the system is running.

-30-

Friday, July 20, 2018

chromecast type operation to a pi from a phone


https://pimylifeup.com/raspberry-pi-chromecast/
Raspberry Pi Chromecast
In this Raspberry Pi Chromecast tutorial, we will be showing you how you can set up your Raspberry Pi to act as a Chromecast device. While we can’t implement the same protocol that Chromecast relies on we can replicate this on the Raspberry Pi.
We replicate its behavior by using two key pieces of software on the Raspberry Pi. The first of these pieces of software is omxplayer. This software handles the video and audio files that are cast to our Raspberry Pi.
Our second piece of software is the OpenMax, Image viewer. We utilize this piece of software to handle images sent to the device.
Lastly, we rely on an Android application called Raspicast. This application is what we will utilize to cast videos, songs, and images to the Raspberry Pi.
While this setup does have a lot of similarities to Chromecast it’s important to remember that it isn’t Chromecast. There are some functionalities that the Raspicast software can’t do but Chromecast can.

Equipment List

Below are all the pieces of equipment that we made use of for this Raspberry Pi Chromecast tutorial.
Recommended:
Raspberry Pi 2 or 3
Micro SD Card
Ethernet Cord (Recommended) or Wifi dongle (Pi 3 has Wifi inbuilt)
Android powered mobile phone or tablet
Optional:
Raspberry Pi Case

Setting up Raspbian to operate as a Chromecast

1. Now before we get started with setting up our Raspberry Pi as a Chromecast-like device, we must first ensure that our Raspberry Pi is actually up to date and that we have the latest package list.
We can update our Raspberry Pi by running the following two commands on it.
sudo apt-get update
sudo apt-get upgrade
2. For this tutorial, we will require to use GIT and Make. While these packages should be pre-installed on Raspbian, we will run the command below just to make sure they are.
To ensure this is installed just run the following command on the Raspberry Pi.
sudo apt-get install git make -y
3. With our Raspberry Pi now up to date, we need first to make sure we have OMXPlayer installed, while Raspbian usually comes with this installed we will make sure it exists anyway.
The reason we need OMXPlayer is so that it can handle video and audio processing for any video or audio files that we cast to our Raspberry Pi Chromecast.
One advantage of OMXPlayer to other video and audio players is that it was designed specifically for the Raspberry Pi’s GPU meaning it offers some of the best performance, something that is critical for any files that are cast.
Run the following command to install OMXPlayer on to your Pi.
sudo apt-get install omxplayer -y
4. With OMXPlayer now installed to our Raspberry Pi, we need to move onto setting up the next piece of the pie. While we now have a piece of software ready that can handle our video and audio files we still need something that can handle images.
For the task of handling images on our Raspberry Pi Chromecast, we will be installing a piece of software that is called OpenMax Image Viewer.
OpenMax Image Viewer is a must for this project as it is a GPU accelerated image viewer explicitly designed for the Raspberry Pi’s GPU, meaning we can display any images as fast as possible and reduce the load on the Raspberry Pi’s CPU.
To begin the process of setting up OpenMax Image Viewer, we must first clone its code repository from Github.
Just run the following two commands on your Raspberry Pi to clone this repository to your Raspberry Pi.
cd ~
git clone https://github.com/HaarigerHarald/omxiv.git
5. With the OpenMax Image viewers code now cloned to our Raspberry Pi, we must now install a couple more packages.
These two packages that we need are libjpeg8-dev and libpng12-dev. These packages contain development libraries for the PNG format and the JPEG format, both which are required to compile the code.
Let’s download and install these packages to our Raspberry Pi by running the following command.
sudo apt-get install libjpeg8-dev libpng12-dev
Note: If for some reason Raspbian fails to find the packages, try reunning sudo apt-get update.
6. We can now finally proceed on to the steps to compiling and installing OpenMax Image viewer to our Raspberry Pi Chromecast device.
To start off, we must first change into the directory where we cloned our code, do this by running the following command on our Raspberry Pi.
cd ~/omxiv
7. Now that we are in the right directory we need to initialize the compiling process now. Compiling will give us the files we need to run the OpenMax Image Viewer software for our Raspberry Pi Chromecast device.
Thanks to the make software, compiling the code is a very simple and straightforward process.
To do this run the following two commands on the Raspberry Pi.
make iclient
make
8. With the OpenMax Image Viewer now compiled, there is one last command we must utilize.
This last command is what will setup OpenMax on our Raspberry Pi so that it is available to the general operating system.
Type the following command into the terminal on your Raspberry Pi, and you will be all set to proceed to the next section of our guide.
sudo make install
9. Now the last thing we need to do is grab our Raspberry Pi’s local IP address.
Run the following command to grab to do it, make sure the ‘I‘ is capitalized otherwise this command won’t work correctly.
hostname -I

Using Raspicast to cast to the Raspberry Pi

1. With our Raspberry Pi now setup to act like a Chromecast, we now need to download an app to our Android device.
This application is Raspicast. Raspicast is the piece of software that will allow us to cast images and videos from our Android devices to the Raspberry Pi.
Either search up “Raspicast” on the Google Play Store or go to the following URL to go directly to the Raspicast on your Google Play from this link.
Download, install and run the Raspicast application.
2.  You should now be greeted with the following screen. This screen will ask you to enter your SSH details as it will use these to talk to your Raspberry Pi.
If you haven’t already set up SSH on your Raspberry Pi, then you should do this now as it is required for the Raspicast software to talk with it.
Raspicast Screenshot
2. Once you have entered the correct information, you should now be able to cast videos, song, and images from your Android device to the Raspberry Pi.
We hope by the end of this Raspberry Pi Chromecast tutorial you should now be able to cast any video, images or audio files from your phone to your Raspberry Pi like a Chromecast using the Raspicast software. If you have any thoughts, feedback or anything else then be sure to head over to the forums

Saturday, June 23, 2018

Add On Screen Keyboard to Raspberry Pi 7' or other screen


if a touch screen rpi is large enough to use an on screen keyboard, this is how to install and enable it.

https://www.raspberrypi.org/forums/viewtopic.php?t=14719

The discussion above mentions the matchbox keyboard, and doesn't mention installing it.

As of the April 2018 raspbian, the matchbox keyboard is not included in the installed goods.  And for good reason, since it is only useful for touch screens.  It could be used with a mouse only system, but would of course be a bit painful.

to install it:
sudo apt-get -y install matchbox-keyboard

to execute it:
sudo matchbox-keyboard

To add it to a desktop

create a file on the Desktop called keyboard.sh

write in the file
#!/bin/bash
matchbox-keyboard

Then open a terminal and
write :
cd Desktop
chmod +x keyboard.sh

Now you can double click the file and your keyboard will appear.

-30-

Sunday, April 15, 2018

Installing lamp and webmin on raspbian


Another writeup on installing a lamp server setup on a Raspberry Pi.  Probably need a 3 or 3+ to have any real justification, YMMV



sudo groupadd -f -g33 www-data
sudo apt-get update
sudo apt-get install apache2 php5 libapache2-mod-php5
sudo apt-get install mysql-server mysql-client php5-mysql
sudo apt-get  install  phpmyadmin
sudo apt-get install perl libnet-ssleay-perl openssl libauthen-pam-perl \
libpam-runtime libio-pty-perl apt-show-versions python 
 

webmin:

mkdir webmin
cd webmin
wget http://prdownloads.sourceforge.net/webadmin/webmin-1.580.tar.gz
gunzip webmin-1.580.tar.gz
tar xf webmin-1.580.tar
cd webmin-1.580
sudo ./setup.sh /usr/local/webmin
 
http://yourPiipaddress:10000 
 

*****************
another install page for raspbian
*****************
http://www.instructables.com/id/Adding-Webmin-to-manage-a-Raspberry-Pi/

-30-

Monday, March 12, 2018

Setting up motion camera software on raspbian


Raspbian has gotten the motion daemon integrated in, but all is not smooth yet.

you need to enable the raspberry pi camera with configuration changes to be sure that it is enabled.

0.0 create a boot media with latest raspbian, write on windows as needed

0.1 for newest stretch version of raspberry pi, enable wifi if necessary.
0.1a   with the media mounted on the creation host
0.1a.1   touch /boot/ssh to make sure ssh is enabled after boot
0.1a.2   put in wpa_supplicant.conf as needed

0.9 log in once booted up

1. sudo apt-get update

2. sudo apt-get -y install motion

3. in raspi-config
3a   set timezone
3b   set hostname
3c   enable camera
3d   resize media if using standard initial raspbian release image from 1.5mb

4.  change /etc/motion/motion.conf
4a.  change to allow non local control page access 8080
4b.  change to allow non local camera stream access 8081
4c.  change to run daemon if started manually

5. add  bcm2835-v4l2 to /etc/modules to get
5a. change /etc/default/motion to auto start
5b. set to get systemctl to start @ boot   sudo systemctl enable motion
5c. change permissions on /var/log/motion/motion so daemonized motion can access it
5d. change permissions on /var/lib/motion directory so daemonized motion can access it

6a. sudo systemctl enable motion
6b. sudo service motion start

7.  some reboots will be required.

00 optional

00.1  command;
          vcgencmd get_camera
       will show whether camera is supported and detected

Note for headless setup

on the boot volume (on system creating boot media)

Must be done before first boot.  Will not work subsequently (for the ssh enable)

touch /boot/ssh

Create wireless connection if need be.  This is the only way to start a pi zerow headless.
Contents of /etc/wpa_supplicant/wpa_supplicant.conf:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
    ssid="YOUR_SSID_HERE"
    psk="YOUR_SECRET_PASSPHRASE_HERE"
    id_str="SOME_DESCRIPTIVE_NAME"
}
 
 

Another page setup

 
https://www.instructables.com/id/How-to-Make-Raspberry-Pi-Webcam-Server-and-Stream-/ 
 
 
Maximum resolutions
 
V1  2592 × 1944 pixels
V2  3280 × 2464 pixels
 
 

--30--

Monday, January 15, 2018

wicd-curses curses wifi manager


A few locations discuss headless setup of the raspberry pi for bringing up such as the rpi zero W which can be made to boot up completely disconnected, due to the presence of wifi on the board.

However it would be nice to be able to add an additional Wifi net to connect to for such as when one wants to run the board on additional networks.

My use case is to have a pocket board which runs Linux and can tether if needed to a cell phone wifi for network access.

https://raspberrypi.stackexchange.com/questions/11631/how-to-setup-multiple-wifi-networks

sudo apt-get install wicd-curses

will install a curses utility to manipulate the wifi connections.

Shell in a box on the raspberry pi

Raspian's Debian distribution repositories contain the shell in a box distribution.

sudo apt-get -y install shellinabox

will install the package.

access it via

https://<ip or name>:4200/

unless the port is configured to other port.  Since this is intended for remote management, the access to the demon is via encrypted https connection.  There are topics about  configuring this for non encrypted access, but one might as well do telnet if that is turned off.

Tagged with ssh as it is a similar access method if configured with encrypted shell access.

Here is a discussion:

http://sysmatt.blogspot.com/2014/11/manage-your-raspberry-pi-with-shell.html

good page on configuring shell in a box:  Local only, different port, etc.

https://www.tecmint.com/shell-in-a-box-a-web-based-ssh-terminal-to-access-remote-linux-servers/

Wednesday, August 30, 2017

Installing s-tui and pre-requisites

s-tui is a nice terminal graphic performance monitor, showing utilization, frequency and system temperature. 

Here is an article about s-tui

https://linoxide.com/monitoring-2/s-tui-terminal-tool-monitoring-cpu-temperature-linux/

and the GIThub link

https://github.com/amanusk/s-tui

It is installable with pip, so pip must be installed.

To do that, first install pip

sudo apt-get install -y python-setuptools python-dev build-essential

then pull in pip

sudo easy_install pip

next one can install s-tui

pip install s-tui

It's been tried out on raspberry pi, raspian, and on ubuntu 16.04 on intel.

It needs work on armbian, at least on the orangepi zero system.


Saturday, August 26, 2017

Raspberry pi zero headless setup

5/21/2019, another setup for headless.  Includes how to do multiple WIFI ssids

https://core-electronics.com.au/tutorials/raspberry-pi-zerow-headless-wifi-setup.html

Note:  at end of this, remember to change power save setting

https://www.gaggl.com/2017/08/set-up-a-raspberry-pi-zero-headless/

credit to leo gaggl

If you are using the GUI (Raspian full download) and want to connect your RPi Zero to a keyboard and monitor there are probably easier ways to do this. These notes are for people that want to use a headless (no monitor and GUI) setup ready to connect to your RPi after first boot via SSH from another terminal.

Download Raspbian Lite

wget -O raspbian-lite-latest.zip https://downloads.raspberrypi.org/raspbian_lite_latest
Download link: https://www.raspberrypi.org/downloads/raspbian/

Write Image to SD Card

dd bs=4M if=2017-08-16-raspbian-stretch-lite.img of=/dev/sdb
After this step there should be 2 additional mounts (if not mount the 2 SD card partitions manually).

Set up network interfaces

Create a new config file for the wireless interface.
cd etc/network/interfaces.d/
vim wlan0.conf

Add the following to the new file (if you want to use DHCP – change to static if you want to fix the IP):
auto wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Set up connection details for local wireless network

vim etc/wpa_supplicant/wpa_supplicant.conf
Check the file and ensure the network settings are as per the Wireless Network you are connecting to.

country=AU
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
ssid="SSID"
psk=HASHED_PSK_VALUE
}

 
country=US
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
    ssid="your_real_wifi_ssid"
    scan_ssid=1
    psk="your_real_password"
    key_mgmt=WPA-PSK
}


You could use the clear-text PSK passphrase but I prefer not to do that in configuration files. Create a PSK hash using ‘wpa_passphrasethis older article
There could be other config values you might need depending on the network you are connecting to. More info: https://linux.die.net/man/5/wpa_supplicant.conf.

Ensure there are DNS Servers configured

sudo vim etc/resolv.conf
Add the following to the new file (or your own nameservers):
# Google's public DNS servers
nameserver 8.8.8.8
nameserver 8.8.4.4

Enable SSH Access

Create an ssh empty file in the mounted boot partition. This is necessary to enable SSH access as SSH is by default disabled on more recent versions of Raspbian.
cd boot/
sudo touch ssh

Boot RPi

Boot the Rpi by powering up and after ~30secs you should be able to connect to the IP assigned. Check your router or ise ‘nmap’ or similar to check the assigned IP:
sudo nmap -p22 -sV 10.1.1.0/24
Default login details are
UID: pi
PWD: rasbperry
My normal further setup steps for RPi 3 are here.
EDIT [2017-08-21]: One of the things necessary on later RPi’s is to turn off power saving mode on the WLAN interface.
sudo iw dev wlan0 set power_save off

Raspberry Pi forum entry link for headless setup

https://www.raspberrypi.org/forums/viewtopic.php?t=191252 

Another headless setup page


https://hackernoon.com/raspberry-pi-headless-install-462ccabd75d0

--30--

Thursday, September 8, 2016

Output from installing Chrome Browser on Rasbian


Rather than clutter the instructional notes, pasting the mess that came out of the install here.

There are a number of recommended installs called out by the install procedure at the end as the browser is installed.  Need to see if any of them are needed as a followup.



wget -qO - http://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -
echo "deb http://dl.bintray.com/kusti8/chromium-rpi jessie main" | sudo tee -a /etc/apt/sources.list
sudo apt-get update
sudo apt-get install chromium-browser rpi-youtube -y

pi@raspberrypi:~/work/chrome $ sudo apt-get update
Ign http://dl.bintray.com jessie InRelease
Get:1 http://dl.bintray.com jessie Release.gpg [821 B]                                                
Get:2 http://dl.bintray.com jessie Release [5,186 B]                                                                       
Hit http://mirrordirector.raspbian.org jessie InRelease                                                   
Get:3 http://dl.bintray.com jessie/main armhf Packages [5,182 B]                                          
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages                                                
Hit http://archive.raspberrypi.org jessie InRelease                                 
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages                   
Hit http://archive.raspberrypi.org jessie/main armhf Packages 
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages       
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages                        
Ign http://dl.bintray.com jessie/main Translation-en_GB                                 
Ign http://dl.bintray.com jessie/main Translation-en              
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB  
Ign http://archive.raspberrypi.org jessie/main Translation-en     
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
Ign http://archive.raspberrypi.org jessie/ui Translation-en       
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB                                                    
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en                                                       
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB                                                       
Ign http://mirrordirector.raspbian.org jessie/main Translation-en                                                          
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_GB                                                   
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en                                                      
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_GB                                                        
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en                                                           
Fetched 11.2 kB in 14s (756 B/s)                                                                                           
Reading package lists... Done
pi@raspberrypi:~/work/chrome $ sudo apt-get install chromium-browser rpi-youtube -y
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following extra packages will be installed:
  chromium-browser-l10n chromium-codecs-ffmpeg-extra geoclue-2.0 kweb libjavascriptcoregtk-1.0-0 libmbim-glib4
  libmbim-proxy libmm-glib0 libqmi-glib1 libwebkitgtk-1.0-0 libwebkitgtk-1.0-common menu modemmanager
Suggested packages:
  webaccounts-chromium-extension unity-chromium-extension adobe-flashplugin menu-l10n
The following NEW packages will be installed:
  chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra geoclue-2.0 kweb libjavascriptcoregtk-1.0-0
  libmbim-glib4 libmbim-proxy libmm-glib0 libqmi-glib1 libwebkitgtk-1.0-0 libwebkitgtk-1.0-common menu modemmanager
  rpi-youtube
0 upgraded, 15 newly installed, 0 to remove and 73 not upgraded.
Need to get 74.5 MB of archives.
After this operation, 243 MB of additional disk space will be used.
Get:1 http://mirrordirector.raspbian.org/raspbian/ jessie/main libjavascriptcoregtk-1.0-0 armhf 2.4.9-1~deb8u1+rpi1 [1,190 kB]
Get:2 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main chromium-codecs-ffmpeg-extra armhf 51.0.2704.79-0ubuntu0.14.04.1.1121 [801 kB]
Get:3 http://mirrordirector.raspbian.org/raspbian/ jessie/main libmbim-glib4 armhf 1.10.0-2.1 [53.5 kB]
Get:4 http://mirrordirector.raspbian.org/raspbian/ jessie/main libmm-glib0 armhf 1.4.0-1 [135 kB]
Get:5 http://mirrordirector.raspbian.org/raspbian/ jessie/main libqmi-glib1 armhf 1.10.2-2 [302 kB]
Get:6 http://mirrordirector.raspbian.org/raspbian/ jessie/main libwebkitgtk-1.0-common all 2.4.9-1~deb8u1+rpi1 [451 kB]
Get:7 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main chromium-browser armhf 51.0.2704.79-0ubuntu0.14.04.1.1121 [58.3 MB]
Get:8 http://mirrordirector.raspbian.org/raspbian/ jessie/main libwebkitgtk-1.0-0 armhf 2.4.9-1~deb8u1+rpi1 [6,262 kB]     
Get:9 http://mirrordirector.raspbian.org/raspbian/ jessie/main geoclue-2.0 armhf 2.1.10-2 [61.4 kB]                        
Get:10 http://mirrordirector.raspbian.org/raspbian/ jessie/main libmbim-proxy armhf 1.10.0-2.1 [6,464 B]                   
Get:11 http://mirrordirector.raspbian.org/raspbian/ jessie/main menu armhf 2.1.47 [358 kB]                                 
Get:12 http://mirrordirector.raspbian.org/raspbian/ jessie/main modemmanager armhf 1.4.0-1 [465 kB]                        
Get:13 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main chromium-browser-l10n all 51.0.2704.79-0ubuntu0.14.04.1.1121 [3,246 kB]
Get:14 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main kweb armhf 1.7.4-1 [2,869 kB]                                
Get:15 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main rpi-youtube armhf 5.1.0-1 [2,562 B]                          
Fetched 74.5 MB in 27s (2,668 kB/s)                                                                                        
Selecting previously unselected package chromium-codecs-ffmpeg-extra.
(Reading database ... 126549 files and directories currently installed.)
Preparing to unpack .../chromium-codecs-ffmpeg-extra_51.0.2704.79-0ubuntu0.14.04.1.1121_armhf.deb ...
Unpacking chromium-codecs-ffmpeg-extra (51.0.2704.79-0ubuntu0.14.04.1.1121) ...
Selecting previously unselected package chromium-browser.
Preparing to unpack .../chromium-browser_51.0.2704.79-0ubuntu0.14.04.1.1121_armhf.deb ...
Unpacking chromium-browser (51.0.2704.79-0ubuntu0.14.04.1.1121) ...
Selecting previously unselected package chromium-browser-l10n.
Preparing to unpack .../chromium-browser-l10n_51.0.2704.79-0ubuntu0.14.04.1.1121_all.deb ...
Unpacking chromium-browser-l10n (51.0.2704.79-0ubuntu0.14.04.1.1121) ...
Selecting previously unselected package libjavascriptcoregtk-1.0-0:armhf.
Preparing to unpack .../libjavascriptcoregtk-1.0-0_2.4.9-1~deb8u1+rpi1_armhf.deb ...
Unpacking libjavascriptcoregtk-1.0-0:armhf (2.4.9-1~deb8u1+rpi1) ...
Selecting previously unselected package libmbim-glib4:armhf.
Preparing to unpack .../libmbim-glib4_1.10.0-2.1_armhf.deb ...
Unpacking libmbim-glib4:armhf (1.10.0-2.1) ...
Selecting previously unselected package libmm-glib0:armhf.
Preparing to unpack .../libmm-glib0_1.4.0-1_armhf.deb ...
Unpacking libmm-glib0:armhf (1.4.0-1) ...
Selecting previously unselected package libqmi-glib1:armhf.
Preparing to unpack .../libqmi-glib1_1.10.2-2_armhf.deb ...
Unpacking libqmi-glib1:armhf (1.10.2-2) ...
Selecting previously unselected package libwebkitgtk-1.0-common.
Preparing to unpack .../libwebkitgtk-1.0-common_2.4.9-1~deb8u1+rpi1_all.deb ...
Unpacking libwebkitgtk-1.0-common (2.4.9-1~deb8u1+rpi1) ...
Selecting previously unselected package libwebkitgtk-1.0-0:armhf.
Preparing to unpack .../libwebkitgtk-1.0-0_2.4.9-1~deb8u1+rpi1_armhf.deb ...
Unpacking libwebkitgtk-1.0-0:armhf (2.4.9-1~deb8u1+rpi1) ...
Selecting previously unselected package geoclue-2.0.
Preparing to unpack .../geoclue-2.0_2.1.10-2_armhf.deb ...
Unpacking geoclue-2.0 (2.1.10-2) ...
Selecting previously unselected package libmbim-proxy.
Preparing to unpack .../libmbim-proxy_1.10.0-2.1_armhf.deb ...
Unpacking libmbim-proxy (1.10.0-2.1) ...
Selecting previously unselected package menu.
Preparing to unpack .../archives/menu_2.1.47_armhf.deb ...
Unpacking menu (2.1.47) ...
Selecting previously unselected package modemmanager.
Preparing to unpack .../modemmanager_1.4.0-1_armhf.deb ...
Unpacking modemmanager (1.4.0-1) ...
Selecting previously unselected package kweb.
Preparing to unpack .../kweb_1.7.4-1_armhf.deb ...
Unpacking kweb (1.7.4-1) ...
Selecting previously unselected package rpi-youtube.
Preparing to unpack .../rpi-youtube_5.1.0-1_armhf.deb ...
Unpacking rpi-youtube (5.1.0-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for dbus (1.8.20-0+deb8u1) ...
Processing triggers for install-info (5.2.0.dfsg.1-6) ...
Setting up chromium-codecs-ffmpeg-extra (51.0.2704.79-0ubuntu0.14.04.1.1121) ...
Setting up chromium-browser (51.0.2704.79-0ubuntu0.14.04.1.1121) ...
Setting up chromium-browser-l10n (51.0.2704.79-0ubuntu0.14.04.1.1121) ...
Setting up libjavascriptcoregtk-1.0-0:armhf (2.4.9-1~deb8u1+rpi1) ...
Setting up libmbim-glib4:armhf (1.10.0-2.1) ...
Setting up libmm-glib0:armhf (1.4.0-1) ...
Setting up libqmi-glib1:armhf (1.10.2-2) ...
Setting up libwebkitgtk-1.0-common (2.4.9-1~deb8u1+rpi1) ...
Setting up libwebkitgtk-1.0-0:armhf (2.4.9-1~deb8u1+rpi1) ...
Setting up geoclue-2.0 (2.1.10-2) ...
Setting up libmbim-proxy (1.10.0-2.1) ...
Setting up menu (2.1.47) ...
Setting up modemmanager (1.4.0-1) ...
Processing triggers for menu (2.1.47) ...
Setting up kweb (1.7.4-1) ...
Preparing kweb environment ...

... looking for programs needed by or recommended for Minimal Kiosk Browser
found: lxterminal
found: xpdf for better PDF support (recommended: evince!)
found: omxplayer
for use with omxplayerGUI you should always get the latest version
from http://omxplayer.sconde.net/
youtube-dl not found. It is needed for web video support.
you will be asked for automatic installation of the optimal version later on

uget download manager not found. It is highly recommended for downloads.
Install it with:
sudo apt-get install uget

if you want to use Minimal Kiosk Browser without starting the desktop,
you need the light weight task bar tint2. Install it with:
sudo apt-get install tint2

xterm not found. It can be optionally used for playing video full screen without GUI.
If you want to make use of this option, you must install it with:
sudo apt-get install xterm

Some programs needed to use all features of Minimal Kiosk Browser are not installed.
Follow the install recommendations above.

You do not have youtube-dl from github installed.
It is needed for best web video support.
Do you want to install it now? (y)ycloning git version of youtube-dl ...
Cloning into 'youtube-dl'...
remote: Counting objects: 72550, done.
remote: Compressing objects: 100% (68/68), done.
remote: Total 72550 (delta 38), reused 0 (delta 0), pack-reused 72482
Receiving objects: 100% (72550/72550), 39.98 MiB | 4.57 MiB/s, done.
Resolving deltas: 100% (52730/52730), done.
Checking connectivity... done.

creating symbolic link
compiling modules ...
Done. To update youtube-dl run update-ytdl (there are new updates almost daily)
Setting up rpi-youtube (5.1.0-1) ...
Processing triggers for libc-bin (2.19-18+deb8u4) ...
Processing triggers for dbus (1.8.20-0+deb8u1) ...
Processing triggers for menu (2.1.47) ...
pi@raspberrypi:~/work/chrome $

Chrome on Raspberry pi


notes for now to pass links over to the pi session.  rdp doesn't pass links

https://www.raspberrypi.org/forums/viewtopic.php?t=121195

Essence is to pull the binary for chrome from another site:

wget -qO - http://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -
echo "deb http://dl.bintray.com/kusti8/chromium-rpi jessie main" | sudo tee -a /etc/apt/sources.list
sudo apt-get update
sudo apt-get install chromium-browser rpi-youtube -y


a later version here:
 
http://kusti8.github.io/RPi-chromium/ 

Here is the output of the install included in this post

http://jim-st.blogspot.com/2016/09/output-from-installing-chrome-browser.html