Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.88 and 1.89

version 1.88, 2018/11/06 13:31:59 version 1.89, 2018/11/06 13:51:04
Line 98  Once you have rpi.img.gz (or rpi_inst),  Line 98  Once you have rpi.img.gz (or rpi_inst), 
  - gunzip rpi.img.gz   - gunzip rpi.img.gz
  - dd if=rpi.img of=/dev/disk1   - dd if=rpi.img of=/dev/disk1
   
 ### Serial Console  ## Console approaches
   
   The standard approach is to use a USB keyboard and an HDMI monitor for installation.
   
 By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, first mount the FAT32 partition and then  ### Serial Console
 edit cmdline.txt and remove '"console=fb"'.  
   
  - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".  By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, mount the FAT32 partition on another system and edit cmdline.txt and remove '"console=fb"'.
   
    In Kermit, the command is "set flow none".   - Most (all?) USB-to-TTL serial adapters have wires for Tx, Rx and ground, and not RTS/CTS or other flow control lines.   Thus, your terminal program (or terminal) must be configured to not require flow control; a symptom of misconfiguration is that you see console output, but cannot type anything.  If so, adjust your serial console application's flow control settings to "none".
   
    In minicom, run "minicom -s" and set hardware flow control to "no"     - In Kermit, the command is "set flow none".
      - In minicom, run "minicom -s" and set hardware flow control to "no".
   
 ### Enabling ssh  ### Enabling ssh for installation without any console
   
 If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address, you will have to wait for the partition resizing and reboot.  If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, you can edit the configuration of a uSD card before booting.   On another computer, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address (e.g. from DHCP server logs), you will have to wait for the partition resizing and reboot.
   
 ### Installation with sshramdisk image  ### Installation with sshramdisk image
   
 build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:  build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console, when built for earmv6hf.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:
   
    - Connect an Ethernet cable from the RPI to a LAN with a DHCP server, and another host you can use for ssh.
    - Power on the RPI, and wait.  Watch the logs on the DHCP server, and find the IP address assigned to the RPI.
    - Use ssh to login to the address you found with user "sysinst", and password "netbsd".
    - When installing, ensure that you enable DHCP and ssh, so that you can log in again after the system is installed.
   
  - Ensure that you have a lan with a DHCP server.  \todo Verify that the above is accurate and sufficient.
  - Connect an Ethernet cable from the RPI to the LAN.  
  - After starting DHCP client, SSH login to with user "sysinst", and password "netbsd".  
    - Be careful to note the ip address given during DHCP so you don't lose your connection  
    - Also for after the sysinst is done and the system reboots  
  - sysinst started!  
   
 ## Installation via ebijun's image  ## Installation via ebijun's image
   

Removed from v.1.88  
changed lines
  Added in v.1.89


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb