Difference between revisions of "Beagleboard inittab and modules"

From Steak Wiki
Jump to navigationJump to search
 
Line 27: Line 27:
 
#/root/disable_leds.sh #optional
 
#/root/disable_leds.sh #optional
 
exit 0}}
 
exit 0}}
 +
 +
{{cat|/root/disable_leds.sh|
 +
#!/bin/bash
 +
#/sys/class/leds/beagleboard\:\:usr0
 +
#echo none > /sys/class/leds/beagleboard\:\:usr0/trigger
 +
#echo none > /sys/class/leds/beagleboard\:\:usr1/trigger
 +
echo none > /sys/class/leds/beaglebone\:green\:usr0/trigger
 +
echo none > /sys/class/leds/beaglebone\:green\:usr1/trigger
 +
echo none > /sys/class/leds/beaglebone\:green\:usr2/trigger
 +
echo none > /sys/class/leds/beaglebone\:green\:usr3/trigger}}
  
  

Latest revision as of 04:06, 27 August 2020

Contents of /etc/modules

# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. g_ether

Contents of /etc/rc.local

#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. [ -d /etc/boot.d ] && run-parts /etc/boot.d ip link set usb0 up #/root/disable_leds.sh #optional exit 0

Contents of /root/disable_leds.sh

#!/bin/bash #/sys/class/leds/beagleboard\:\:usr0 #echo none > /sys/class/leds/beagleboard\:\:usr0/trigger #echo none > /sys/class/leds/beagleboard\:\:usr1/trigger echo none > /sys/class/leds/beaglebone\:green\:usr0/trigger echo none > /sys/class/leds/beaglebone\:green\:usr1/trigger echo none > /sys/class/leds/beaglebone\:green\:usr2/trigger echo none > /sys/class/leds/beaglebone\:green\:usr3/trigger


Contents of /etc/inittab

# /etc/inittab: init(8) configuration. # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin --force # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin --force # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # NOTE: only one of these is actually needed. Comment out extras after first boot. T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100 T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100 T2:23:respawn:/sbin/getty -L ttyS2 115200 vt100 T3:23:respawn:/sbin/getty -L ttyO0 115200 vt100 T4:23:respawn:/sbin/getty -L ttyO1 115200 vt100 T5:23:respawn:/sbin/getty -L ttyO2 115200 vt100 # # or on a USB serial line #U0:23:respawn:/sbin/getty -L ttyUSB0 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 # Example for systemd-nspawn # Only /dev/console exists inside nspawn, so we need a getty on that. # Also make sure to comment out the gettys on tty* above. #C0:2345:respawn:/sbin/getty -8 --noclear --keep-baud console 115200,38400,9600