All you need is to place an empty file named 'ssh' onto the boot (FAT) partition of your SD card (no need to mount ext3). Tested with 2016-11-25-raspbian-jessie-lite.img.
More info about Nov '16 security update: https://www.raspberrypi.org/blog/a-security-update-for-raspbian-pixel/
Quoting the documentation:
As of the November 2016 release, Raspbian has the SSH server disabled by default. You will have to enable it manually.
To enable SSH on machines through console:
Enter sudo raspi-config in the terminal, first select Interfacing Options, then navigate to ssh, press Enter and select Enable or disable ssh server.
To enable ...
You have to use avahi-daemon (zeroconf) if you want to connect via a hostname instead of an IP address. From the Raspberry Pi documentation on RPi Advanced Setup:
Install avahi with the following commands on the Raspberry Pi:
sudo apt-get install avahi-daemon
Update boot startup for avahi-daemon
sudo insserv avahi-daemon
Apply the new configuration with:...
As of the November 2016 release, Raspbian has the SSH server disabled
by default. You will have to enable it manually. This is done using
Enter sudo raspi-config in the terminal, first select Interfacing options, then navigate to ssh, press Enter and select Enable or ...
If you want to login as root using SSH or WinSCP you need to edit the config of SSHD, do this:
Login, and edit this file: sudo nano /etc/ssh/sshd_config
Find this line: PermitRootLogin without-password
Edit: PermitRootLogin yes
Close and save file
reboot or restart sshd service using: /etc/init.d/ssh restart
Set a root password if there isn't one already: ...
Right off the bat, let me say that there is not a way to recover a password (without some actual cracking/hacking which I don't know how to do). Resetting your password is your best bet.
So the first step will be to determine if you have any way to log in to the Raspbery Pi.
If you're able to log in with a user that has 'sudo' rights (this includes SSH... ...
The Raspberry Pi 2 will give BCM2709 hardware and ~1 GB of RAM like this:
pi@raspberrypi:~ $ cat /proc/cpuinfo | grep Hardware
Hardware : BCM2709
pi@raspberrypi:~ $ cat /proc/meminfo | grep MemTotal
MemTotal: 947756 kB
while the Pi 1 reports BCM2708 hardware and definitely less than 1 GB:
pi@raspberrypi:~ $ cat /proc/cpuinfo | grep Hardware
Use the command ncdu. It is a console program to display disc usage. It has a ncurses GUI.
I usually run ncdu -x <some folder>, the x switch is there to not cross filesystem boundaries.
apt-get install ncdu
ncdu man page
Welcome to the world of Pi - you will get many hours of fun from them once you are up and running.
First check with your supplier to see if the version of the operating system they put on the card had ssh enabled - most suppliers do not do this though. If not:
Try ping raspberry.local - it may find it.
Check your router to see if you have a new device
It could be that your Pi is trying to do a reverse DNS lookup of the client's connecting hostname for security reasons, which is okay, but leads to the timeouts if you don't have a working reverse DNS.
when you do finally login, try adding
to your /etc/ssh/sshd_config file, and see if that helps improve things, of course don't forget to reload ...
You can lookup the IP address by hostname. Assuming the hostname of your Pi is "raspberrypi"
Here is how you obtain the IP address using ping command and hostname.
From Linux: ping raspberrypi
From Windows: ping raspberrypi
From OS X: ping raspberrypi.local
In order for the command to work from Windows, you need to have Samba running on your Pi. You can ...
To be able to use a non-compatible realvnc client you have to downgrade the security of the realvnc server to use vnc password authentication.
To be able to to this without a desktop connection open a SSH session:
Edit the config file in /root/.vnc/config.d/vncserver-x11
Add the following lines at the end of the file
If look at the /etc/init.d/skeleton script, in the beginning of it there are two marks : ### BEGIN INIT INFO and ### END INIT INFO.
All the data inside those marks is the configuration for runtime dependences and you can look them up in the Debian Wiki.
Your script is missing these tags and configuration so insserv just uses some defaults.
This is just a ...
ssh is installed but not started by default on runlevel 2,
the default for raspbian.
Rename /etc/rc2.d/ssh/K??ssh to /etc/rc2.d/ssh/S02ssh
The sd card comes with 2 partitions. The 1st is vfat; the 2nd is ext3. You need some utility to access it from macosx.
1st google result for ext2 macosx:
How To Geek has a good article that covers this issue. In a nutshell .local domains are self-reported by each host (via Multicast DNS), and other machines on the network have to listen for them. Windows comes with such a service (LLMNR) however it's non-standard and therefore doesn't work terribly well. Instead you should install Apple's Bonjour service (...
That's a tough one. The WiFi won't automatically connect. So I would try the following:
Image a micro SD card with the Raspbian OS image using Win32DiskImager.
Manually configure your WiFi from another computer. In another computer running Linux (or PC with Live CD) you could edit the following file:
And add the ...
Mount the SD card, go into the file system, and edit /etc/passwd. Find the line starting with "pi" that begins like this:
Get rid of the x; leave the colons on either side. This will eliminate the need for a password.
You probably then want to create a new password by using the passwd command after you log in.
Here are the steps I used (on debian) which you might find useful.
1.Setting Static IP for the Pi.
a.Open the interfaces file using the command
sudo nano /etc/network/interfaces
b.Change the interfaces file to the following (This works for me I am not sure if a few of the lines can be excluded).
iface lo inet loopback
iface eth0 inet static
Try Pi Finder for Mac to discover the RPi's IP with a headless RPi unit.
Though in your edited question, it appears the IP is listed under en0 as 192.168.91.16, assuming that your ifconfig output is coming from the RPi.
In the 6 years since I posted this Answer many things have changed.
macOS Samba support has improved and Apple now uses Samba as its default for file sharing (and afp doesn't work with newer Apple filesytems)
Debian Buster now uses netatalk 3 - which has significant changes, and requires more configuration to do anything useful.
nfs support in much ...
So after a lot of googling I found the codes that setterm should be sending to the tty and these two command unblank the screen every time.
sudo chmod 666 /dev/tty1
echo -ne "\033[9;0]" >/dev/tty1
The only reason I can think of all the other commands (that should have worked) failing was because the Pi is connected via svideo to a tv and not HDMI or a ...
As of November 2016, SSH is disabled by default on raspbian.
The easiest way to get around this is to place a file called "SSH" on the SD card (notice no file extension). SSH will then be enabled.
Adding Notes for users with monitor access from this link:
Apparently, the SSH server is now disabled by default. If there is no
server listening for ...
The easiest way to do this for a headless setup is to create a file named ssh on the boot partition of the SD card. This will enable the SSH daemon immediately after first boot and will be deleted.
Official SSH guide: https://www.raspberrypi.org/documentation/remote-access/ssh/README.md#3-enable-ssh-on-a-headless-raspberry-pi-add-file-to-sd-card-on-another-...
I had the same issues using the wheezy image.
The goal is to have the Pi boot up so you can ssh into it from another system, without having to ever connect a monitor and keyboard.
The problem is that while the SSH service is enabled, as noted above, it hasn't been configured yet, so you can't connect even if networking is running. Here are the tasks to ...
The password isn't actually stored anywhere on the system, a one way hash of it is. This means even if you have the hash, you won't be able to deduce the password.
The hash itself is stored in /etc/shadow. Take the SD card out and stick it in another linux system; any common distro (ubuntu, fedora, arch, etc.) should do. On that system, create a new ...
You are looking for information on running "headless".
There are details on this on the raspberry pi site.
Basically put a file, wpa_supplicant.conf, on the "boot" sector of the sdcard, that you can see from windows, and edit the file to include your wifi credentials:
Following massive botnet attacks in 2016 due to IoT devices being easily hacked with default passwords, Raspbian once again comes with SSH turned off by default (source).
The fix is pretty easy, you just need to create a file in the boot partition (not the directory within the root filesystem) called ssh. To check if you're in the right partition, it ...
You can use a great tool called x2x. This essentially treats the monitor connected to the remote device (the Raspberry Pi) as a second X screen to you existing session as if you had two monitors connected.
Install x2x on both devices:
sudo pacman -S x2x # Arch Linux
sudo apt-get install x2x # Debian/Raspbian
On the Raspberry Pi ...