== Getting server to boot to terminal by default == Having problems with usb connection dropping every 1 to 2 days for connected weather station, which then requires a reboot to fix. Looking at running server headless to reduce resources used. To achieve this edit:\\ /etc/default/grub put "text" into the line:\\ GRUB_CMLDLINE_LINUX_DEFAULT="text" Restart Grub: sudo update-grub reboot udisks automounting is running apparently as part of gnome.. no gnome - no automounting Fix ((http://angryelectron.com/ubuntu-server-automount-removable-media/)) is to use udisks-glue sudo apt-get install usbmount udisks udisks-glue git clone https://gist.github.com/5399914.git udisks-glue #(or copy and paste if you don't like git) cd udisks-glue chmod +x udisks-glue sudo cp udisks-glue /etc/init.d/. sudo update-rc.d udisks-glue defaults == wireless connection problems == Having major problems with the wireless connection. Wireless card can be found from command: lspci | grep Network Atheros AR9285 has not good reception of signal - 2-3 bars from 5, but problem is that it drops this signal periodically and also has high packet loss. Followed some instructions at www.xors.me/?p=1069 to install some driver - but I still have problems Seeing some strange loop for wlan running in syslog Dec 26 11:24:58 hal NetworkManager[809]: (wlan0): supplicant interface state: disconnected -> scanning Dec 26 11:24:59 hal wpa_supplicant[901]: Trying to authenticate with 84:a8:e4:64:c4:fc (SSID='Eisenheim' freq=2437 MHz) Dec 26 11:24:59 hal NetworkManager[809]: (wlan0): supplicant interface state: scanning -> authenticating Dec 26 11:24:59 hal kernel: [ 1203.141875] wlan0: authenticate with 84:a8:e4:64:c4:fc (try 1) Dec 26 11:24:59 hal kernel: [ 1203.144098] wlan0: authenticated Dec 26 11:24:59 hal wpa_supplicant[901]: Trying to associate with 84:a8:e4:64:c4:fc (SSID='Eisenheim' freq=2437 MHz) Dec 26 11:24:59 hal kernel: [ 1203.144591] wlan0: associate with 84:a8:e4:64:c4:fc (try 1) Dec 26 11:24:59 hal NetworkManager[809]: (wlan0): supplicant interface state: authenticating -> associating Dec 26 11:24:59 hal kernel: [ 1203.148323] wlan0: RX ReassocResp from 84:a8:e4:64:c4:fc (capab=0x411 status=0 aid=6) Dec 26 11:24:59 hal kernel: [ 1203.148332] wlan0: associated Dec 26 11:24:59 hal wpa_supplicant[901]: Associated with 84:a8:e4:64:c4:fc Dec 26 11:24:59 hal NetworkManager[809]: (wlan0): supplicant interface state: associating -> associated Dec 26 11:24:59 hal NetworkManager[809]: (wlan0): supplicant interface state: associated -> 4-way handshake Dec 26 11:24:59 hal wpa_supplicant[901]: WPA: Key negotiation completed with 84:a8:e4:64:c4:fc [PTK=CCMP GTK=CCMP] Dec 26 11:24:59 hal wpa_supplicant[901]: CTRL-EVENT-CONNECTED - Connection to 84:a8:e4:64:c4:fc completed (reauth) [id=0 id_str=] Dec 26 11:24:59 hal NetworkManager[809]: (wlan0): supplicant interface state: 4-way handshake -> completed This seems to be running constantly - and presumably crashes out every so often because of some small variation in Wifi signal strength and then has some issues reconnecting. What is the purpose of this ? ==== Testing Network Speeds ==== Run on server hal iperf -s dobrien@epicurus [0] ~ > iperf -c hal ------------------------------------------------------------ Client connecting to hal, TCP port 5001 TCP window size: 23.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.3.105 port 33992 connected with 192.168.3.104 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.9 sec 2.38 MBytes 1.83 Mbits/sec dobrien@epicurus [0] ~ > iperf -c raspbmc ------------------------------------------------------------ Client connecting to raspbmc, TCP port 5001 TCP window size: 23.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.3.105 port 60290 connected with 192.168.3.106 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.2 sec 7.62 MBytes 6.24 Mbits/sec