Difference between revisions of "MDRS:HAL Development Log"
| Line 27: | Line 27: | ||
#Hostname should be "hal" | #Hostname should be "hal" | ||
#when installing software, it asks for pi or root password (our accounts not listed). Since I didn't know either of them, I had to reset using sudo passwd pi with admin account. | #when installing software, it asks for pi or root password (our accounts not listed). Since I didn't know either of them, I had to reset using sudo passwd pi with admin account. | ||
| − | |||
===Earlier=== | ===Earlier=== | ||
Revision as of 21:56, 14 October 2018
Contents
Development Log of the MDRS Habitat Activity Lexica (HAL)
Developers: James Burk, Ryan Watson, Matt Hopson (MarsChat)
Operating System
Ryan Watson: I have a beta Raspberry Pi image that I've posted up on S3 and I want to invite you to download, write to your SD card and give it a try. It has a very sparse selection of apps:
- Chromium (Can be changed to Firefox, defaults to Chromium so left it alone for now)
- VLC
- Libreoffice (Default in the base image)
- OMX
Users
Default pi user still in effect as admin. Likely disable but not delete, due to potential future needs of having that standard user.
There are two baked in users, an administrative user for possible future tasks and a workstation user:
- U: `admin` / PW: `get_to_mars` - U: `mdrs` / PW: `get_to_mars`
Current Issue List
10/13:
- Hostname should be "hal"
- when installing software, it asks for pi or root password (our accounts not listed). Since I didn't know either of them, I had to reset using sudo passwd pi with admin account.
Earlier
- need to fix sudoers, still is expecting the default `pi` user
- command to disable: sudo passwd --lock pi
- Add Mars related wallpaper by default
- Fixup timezone, initial / ongoing time sync via ntp. Currently defaults to UTC
- Password is currently set during the image build / provision. Can / should be more dynamic
- Dual displays with HDMI output as primary
- add "display_default_lcd=0" to /boot/config.txt
Install walk-thru
The end goal is to write the boot image file to an SD card, configured to boot a Raspberry Pi. There are several possible workflows possible using OSX, Linux or Windows. I will detail a Windows based workflow below and add others as necessary.
Windows 10
1) Download artifact from S3
The zip file artifact is currently located at https://s3.amazonaws.com/watson-builds/image_2018-10-03-razpi-modz-v.5.2.zip and downloadable via browser or other tool.
2) Install image writer utility
I found via the Raspberry Pi forums a utility called etcher written and hosted by resin.io, an IoT company. The utility is straightforward and easy to use. There is no need to extract the img file from the downloaded zip file. This utility can accept the compressed file and write to an SD card.
Download: https://etcher.io/
3) Insert SD card
Before starting Etcher it is helpful to insert the SD card then start the application.
4) When the application is open navigate to the download location and select the still compressed .zip file
5) The SD card should already be selected, if not choose the correct target SD card drive.
6) Flash!
Etcher will begin to write the image to the card. In testing this typically takes about 15 minutes. During the process Windows will notify that the drive has been ejected, or that the card needs to be formatted before use etc. Cancel or dismiss these messages and let Etcher continue. After the write is complete it will verify the write and then software eject the SD card (unmount it from the computer). You can now remove the SD card and place into the RaspberryPi.
