Difference between revisions of "Pogo"

From Bloominglabs
Jump to: navigation, search
(Created page with "Pogo is the name of the system we keep running for services in the space. Generally we try to keep it in a running state as much as possible. == Services Pogo provides == * I...")
 
(→‎Services Pogo provides)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
Decommissioned somewhere around 2016. This page is only here for reference purposes. The backups of the code and projects described here probably do exist in a few peoples hands.
 +
 
Pogo is the name of the system we keep running for services in the space. Generally we try to keep it in a running state as much as possible.
 
Pogo is the name of the system we keep running for services in the space. Generally we try to keep it in a running state as much as possible.
  
Line 7: Line 9:
 
* RFID access management (RFID operates independently)
 
* RFID access management (RFID operates independently)
 
* Gateway between RFID system and IRC via doorbot
 
* Gateway between RFID system and IRC via doorbot
−
* Audio and Text annunciation to people within the space
+
* Audio annunciation to people within the space
 +
* Controls scrolling LED sign, access from IRC via SignBot
 +
* X10 Firecracker (serial X10 device control)
 
* LDAP (still experimental)
 
* LDAP (still experimental)
 +
* Minecraft server for a while (kept crashing)
  
 +
== FTDI - /dev/ttyUSBx ordering ==
 +
We have a number of FTDI serial adapters connected to pogo. These allow access to X10 control, the scrolling LED sign, access to the RFID board, etc. To keep the tty devices ordered the same after each reboot some udev rules had to be created.
  
 +
* /etc/udev/rules.d/10-local.rules
  
−
== Notes on pulseaudio setup ==
+
<pre>
−
Previously only a user logged in through X could get audio output on pogo. This is necessary for fun audio stuff like letting the RFID system greet members when they badge into the space.
+
# Run this to find an FTDI adapters serial number:
 +
# udevadm info --name=/dev/ttyUSB1 --attribute-walk | grep -i serial
 +
# More info here: https://forum.sparkfun.com/viewtopic.php?f=14&t=34590
  
−
This is how to get pulseaudio working on pogo so anyone logged in can launch sound from the command line. Note that this is not normally how pulseaudio is supposed to run, in fact the pulseaudio folks explicitly state this is bad and not supported, it's only allowed for strange setups like what we actually need for our use of it on pogo.
+
# Definition for the X10 Firecracker on FTDI /dev/ttyUSB0
 +
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="FTCUSA8R"
  
−
Found part of the fix from this link:
+
# Definition for the RFID system (Arduino)
−
* http://wiki.laptop.org/go/PulseAudio
+
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="A7006QeX"
  
−
<pre>*** PULSEAUDIO: Unable to connect: Access denied</pre>                                                       
+
# Definition for the serial USB interface to the scrolling LCD sign /dev/ttyUSB2
−
aplay: main:545: audio open error: Connection refused                                                       
+
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="FTCBW2W2"
−
This happens because pulseaudio requires authentication before accepting connections to prevent random people from playing audio on your computer. Pulseaudio places a cookie in the home directories of the user running the server. Copy the cookie of the machine you want to send the audio data to, to the home directory of the sender machine. (Alternatively, you may add auth-anonymous=1 to the end of the load-module module-native-protocol-tcp line to disable authentication). You are ready to play networked audio using pulseaudio.
+
−
 
+
−
First verify console kit is installed, there are other ways to use pulseaudio but this is what was working with pulseaudio as of today:
+
−
<pre>rpm -qa | grep -i consolekit
+
−
ConsoleKit-libs-0.4.5-1.fc15.i686
+
−
ConsoleKit-0.4.5-1.fc15.i686
+
−
ConsoleKit-x11-0.4.5-1.fc15.i686
+
 
</pre>
 
</pre>
  
−
First fix from the default install: change this line in /etc/pulse/system.pa to this:
 
−
<pre>
 
−
#load-module module-native-protocol-unix
 
−
load-module module-native-protocol-unix auth-anonymous=1
 
−
</pre>
 
  
−
Also uncomment this line and change to "yes" in /etc/pulse/daemon.pa:
+
== Notes on pulseaudio setup ==
−
<pre>daemonize = yes</pre>
+
There were some pulse audio notes here, but the final fix to get audio working again on pogo was to uninstall pulse-audio. That's it.
  
−
At this point pulseaudio can be started and won't die - should accept audio from any user, and probably over the network as well...
+
= RIP pogo =
−
<pre>/usr/bin/pulseaudio -D --system --disallow-module-loading --disallow-exit</pre>
+
Pogo was retired when we moved to the new space. Poquito (RFID system) is still kicking for now.
  
−
I threw together an init file here: /etc/init.d/pulseaudio
+
[[Category:Hackerspace systems]]
−
Then set it up to start at boot with this:
+
−
<pre>chkconfig --add pulseaudio; chkconfig --level 345 pulseaudio on</pre>
+

Latest revision as of 22:22, 13 November 2019

Decommissioned somewhere around 2016. This page is only here for reference purposes. The backups of the code and projects described here probably do exist in a few peoples hands.

Pogo is the name of the system we keep running for services in the space. Generally we try to keep it in a running state as much as possible.

Contents

[edit] Services Pogo provides

  • Internal webserver/fileserver
  • External webserver via dynamic dns
  • Shell accounts
  • RFID access management (RFID operates independently)
  • Gateway between RFID system and IRC via doorbot
  • Audio annunciation to people within the space
  • Controls scrolling LED sign, access from IRC via SignBot
  • X10 Firecracker (serial X10 device control)
  • LDAP (still experimental)
  • Minecraft server for a while (kept crashing)

[edit] FTDI - /dev/ttyUSBx ordering

We have a number of FTDI serial adapters connected to pogo. These allow access to X10 control, the scrolling LED sign, access to the RFID board, etc. To keep the tty devices ordered the same after each reboot some udev rules had to be created.

  • /etc/udev/rules.d/10-local.rules 
# Run this to find an FTDI adapters serial number:
# udevadm info --name=/dev/ttyUSB1 --attribute-walk | grep -i serial
# More info here: https://forum.sparkfun.com/viewtopic.php?f=14&t=34590

# Definition for the X10 Firecracker on FTDI /dev/ttyUSB0
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="FTCUSA8R"

# Definition for the RFID system (Arduino)
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="A7006QeX"

# Definition for the serial USB interface to the scrolling LCD sign /dev/ttyUSB2
SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="FTCBW2W2"


[edit] Notes on pulseaudio setup

There were some pulse audio notes here, but the final fix to get audio working again on pogo was to uninstall pulse-audio. That's it.

[edit] RIP pogo

Pogo was retired when we moved to the new space. Poquito (RFID system) is still kicking for now.

Retrieved from "http://mail.bloomingtonfools.org/index.php?title=Pogo&oldid=4194"
Personal tools