Neat tip to force a fsch on the root partition on next reboot (from: http://raspberrypi.stackexchange.com/questions/3289/checking-sdcard-for-errors-unmount-problem )
sudo touch /forcefsckScheduling scripts to run at boot on Raspbian (Raspberry Pi)
There’s always a dozen ways to do anything on Linux, and I was looking for a quick and easy way to run a script at startup on Raspbian on a Raspberry Pi.
I found this post:
http://raspberrypi.stackexchange.com/questions/8734/execute-script-on-start-up
which has a number of good suggestions, but the quickest and easiest approach is probably to add a @reboot entry to crontab, as suggested in this post here.
Amateur Radio related uses for your Raspberry Pi
Here’s a collection of Amateur Radio and other general radio related possible uses and ideas for using a Raspberry Pi. Some of these ideas could be used in connection with each other, or just solo.
This list is a collection of ideas for the basis of an upcoming presentation; more on that later. Right now, a collection of links for reference.
Simple:
- as a simple/cheap Logging computer:
Easy:
- ADS-B aircraft transponder receiver (http://www.rtl-sdr.com/adsb-aircraft-radar-with-rtl-sdr/)
Slightly more involved:
- APRS tracker (mobile APRS – ping beacon packets with location)
- Software Defined Radio using RTL USB dongle and rtl-sdr (https://www.kevinhooke.com/2014/07/26/installing-rtl-sdr-and-dump1090-on-a-raspberry-pi-to-receive-ads-b-signals/)
- CW progation beacon transmitter (http://hackaday.com/2013/01/25/raspberry-pi-used-as-a-beacon-transmitter/)
- APRS i-gate (internet gateway for APRS data)
- WSPR transmitter / WspryPi / TAPR Whispering Raspberries QRP Tx Shield
More involved:
- Soundcard based Packet Packet TNC, using Direwolf: https://github.com/wb2osz/direwolf
- Hardware Packet Radio using a TNC-Pi add on board
- RadWav SDR transceiver add-on board $150: http://www.radwav.com/index.html
- QTSDR – SDR transceiver (https://github.com/ha7ilm/qtcsdr)
Other links with more ideas:
Redirecting console output to a PiTFT screen
I just got a neat 3.8″ PiTFT from Adafruit. Followed the easy setup instructions in the tutorial and it seems I can either startx and get an X Windows desktop on the device, or display the tty1 console to the device on boot.
The trouble with the easy setup is it’s not clear what the scripts actually configured to get it working.
For X Windows, it seems this is the relevant part:
export FRAMEBUFFER=/dev/fb1
startx
For the console on boot, adding this section to the line in /boot/cmdline.txt following rootwait:
fbcon=map:10 fbcon=font:VGA8x8
The docs for fbcon here suggest that map:10 will map /dev/fb1 then /dev/fb0 in a repeating pattern across each tty, eg fb1 -> tty1, fb0 – > tty2, fb1 -> tty3 etc
The part I’m missing right now is how to switch the tty mappings on the fly, or how to map a specific console the to the buffer. This post I think is asking similar questions to what I’m trying to do.
If I want to map output on tty2 to the fb for the PiTFT, I wonder if it would be like this:
fbcon=map:01
I’ll try it and see…