element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Blog New Raspbian version "Pixel"
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
GPIO Pinout
Raspberry Pi Wishlist
Comparison Chart
Quiz
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: balearicdynamics
  • Date Created: 4 Jan 2017 5:48 PM Date Created
  • Views 3397 views
  • Likes 4 likes
  • Comments 19 comments
Related
Recommended
  • operating system
  • jessie pixel
  • keyboard
  • ssh disabled
  • hdmi
  • ssh access
  • remote access
  • jessie
  • warning
  • sudo_open
  • configuration
  • mouse
  • raspberry pi 3

New Raspbian version "Pixel"

balearicdynamics
balearicdynamics
4 Jan 2017

I decided to write this post due a silly trap that to be honest I think should be avoided in next updated of the raspbian pixel version. The last official downloadable version at the date is the 2016-11-25-raspbian-jessie.img

 

Here and there there are tons of posts of users that are not able to connect via SSH to a fresh raspbain installation on a PI3 of this version; I had the same problem too and tried to solve the problem thinking to the most common issues like removing the .ssh/known_hosts, check and double check the device IP address etc.

My fault is that I have not read the pixel version release notes, but IMHO the bigger fault is what they wrote in the release notes of this version. Don't forget that the Raspberry PI 3B like the previous models as well is primarily an embedded Linux device headless, it borns headless and any further element to be added to the original system - I mean keyboard, mouse, screen at least - should be considered something extra, not provided with the original hardware.

 

The consideration is: if I am a newbie and I buy a Raspberry Pi 3B then I install the last, modern and updated native operating system on the device, I must be able to run and access to it without to be obliged to buy or have in-house a keyboard, a mouse and a HDMI device. Absolutely not! Instead the problem is just this as you can read in the few lines above, the release notes referred to the mentioned release.

2016-11-25: 
* SSH disabled by default; can be enabled by creating a file with name "ssh" in boot partition
* Prompt for password change at boot when SSH enabled with default password unchanged
* Adobe Flash Player included * Updates to hardware video acceleration in Chromium browser
* Greeter now uses background image from last set in Appearance Settings rather than pi user
* Updated version of Scratch
* Rastrack option removed from raspi-config and Raspberry Pi Configuration
* Ability to disable graphical boot splash screen added to raspi-config and Raspberry Pi Configuration
* Appearance Settings dialog made tabbed to work better on small screens
* Raspberry Pi Configuration now requires current password to change password
* Various small bug fixes
* Updated firmware and kernel

The only possible workaround is to install a previous version (I suggest the 2016-05-27-raspbian-jessie.img image) then update/upgrade the system to the pixel version that - hopefully - should not change the previous installation settings, including the ssh accessibility from the LAN.

  • Sign in to reply

Top Comments

  • Jan Cumps
    Jan Cumps over 9 years ago in reply to beacon_dave +3
    Yes, that's how to do it. Works perfectly (meanwhile, @self keeps the rant for himself that he wants to post in each discussion about the Pi guys deciding to shut down SSH instead of enforcing a default…
  • clem57
    clem57 over 9 years ago +2
    I have blogged elsewhere that a file called "ssh" with nothing in it gives 1 time access to SSH. When the boot up occurs, the file is deleted to prevent another attempt( That does not stop another try…
  • beacon_dave
    beacon_dave over 9 years ago in reply to balearicdynamics +2
    How about taking an Arduino Micro and turning it into a USB HID macro playback device so as to replay the necessary mouse and keyboard input into one of the R-Pi USB ports so as to turn on the SSH / VNC…
  • balearicdynamics
    balearicdynamics over 9 years ago in reply to beacon_dave

    The image below shows finally the Pi full screen desktop on the Macbook pro. As its native resolution is 1680x1050 I have put 256 Kb of GPU memory and the hdmi mode set to the corresponding resolution from hdmi group 2 in /boot/config.txt and no HDMI screen attached to the Raspberry. To be honest, a guy that just buy the PI and power it for the first time I think he can have serious problems to manage this setup.

     

    Enrico

    image

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • balearicdynamics
    balearicdynamics over 9 years ago in reply to Jan Cumps

    By default the only annoying thing is that it is shown that the ssh is enabled and this is unsecure, with the default password that is suggested to be changed... Nothing else.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Jan Cumps
    Jan Cumps over 9 years ago in reply to balearicdynamics

    But did you change the default password?

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • balearicdynamics
    balearicdynamics over 9 years ago in reply to beacon_dave

    This page is not fully explanatory but the concept is correct. Without the HDMI monitor attached you get a VNC viewer a very low resolution. You should force in the /boot/config.txt the parameters that output the display at the desired resolution.

    I have set a test with 1024 x 768 and it worked as expected. On Linux.org in the wiki section dedicated to the raspberry you can find a more clear explanation on how the config.txt file works: R-Pi configuration file - eLinux.org

    while here RPiconfig - eLinux.org  you find a clear explanation and effect of every parameter. For the case of the video settings follow the part dedicated to HDMI groupt 1 and group 2.

     

    Enrico

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • beacon_dave
    beacon_dave over 9 years ago in reply to beacon_dave

    It looks like you can also create a local EDID file and tell /boot/config.txt to use that data instead of the EDID from a monitor.

    https://www.raspberrypi.org/documentation/configuration/config-txt.md

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube