[arm-allstar] RPi2 V1.0 Released!!!
Michael Hebert
mhebert1975 at gmail.com
Mon Apr 13 00:44:29 EST 2015
I receive this error after changing the time zone. I originally used the
script and have manually changed it too.
#date comes back with the correct date and time
[root at kd5dfb_rpi2 ~]# date
Mon Apr 13 00:39:33 CDT 2015
[root at kd5dfb_rpi2 ~]# ls -als /etc/localtime
0 lrwxrwxrwx 1 root root 37 Apr 13 00:37 /etc/localtime ->
../usr/share/zoneinfo/America/Chicago
[root at kd5dfb_rpi2 ~]# timedatectl status
Local time: Mon 2015-04-13 01:37:13 EDT
Universal time: Mon 2015-04-13 05:37:13 UTC
RTC time: n/a
Time zone: America/New_York (EDT, -0400)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2015-03-08 01:59:59 EST
Sun 2015-03-08 03:00:00 EDT
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2015-11-01 01:59:59 EDT
Sun 2015-11-01 01:00:00 EST
[root at kd5dfb_rpi2 ~]# timedatectl set-timezone America/Chicago
[root at kd5dfb_rpi2 ~]# timedatectl status
Local time: Mon 2015-04-13 00:37:47 CDT
Universal time: Mon 2015-04-13 05:37:47 UTC
RTC time: n/a
Time zone: America/Chicago (CDT, -0500)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
*** Error in `timedatectl': double free or corruption (!prev): 0x774d9398
***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x6870c)[0x76e0270c]
/usr/lib/libc.so.6(+0x6e384)[0x76e08384]
/usr/lib/libc.so.6(+0x6ed2c)[0x76e08d2c]
======= Memory map: ========
76d99000-76d9a000 rw-p 00000000 00:00 0
76d9a000-76ec3000 r-xp 00000000 b3:02 25949 /usr/lib/libc-2.20.so
76ec3000-76ed3000 ---p 00129000 b3:02 25949 /usr/lib/libc-2.20.so
76ed3000-76ed5000 r--p 00129000 b3:02 25949 /usr/lib/libc-2.20.so
76ed5000-76ed6000 rw-p 0012b000 b3:02 25949 /usr/lib/libc-2.20.so
76ed6000-76ed9000 rw-p 00000000 00:00 0
76ed9000-76eee000 r-xp 00000000 b3:02 25168 /usr/lib/
libpthread-2.20.so
76eee000-76efd000 ---p 00015000 b3:02 25168 /usr/lib/
libpthread-2.20.so
76efd000-76efe000 r--p 00014000 b3:02 25168 /usr/lib/
libpthread-2.20.so
76efe000-76eff000 rw-p 00015000 b3:02 25168 /usr/lib/
libpthread-2.20.so
76eff000-76f01000 rw-p 00000000 00:00 0
76f01000-76f1d000 r-xp 00000000 b3:02 24710 /usr/lib/libgcc_s.so.1
76f1d000-76f2d000 ---p 0001c000 b3:02 24710 /usr/lib/libgcc_s.so.1
76f2d000-76f2e000 rw-p 0001c000 b3:02 24710 /usr/lib/libgcc_s.so.1
76f2e000-76f34000 r-xp 00000000 b3:02 18777 /usr/lib/librt-2.20.so
76f34000-76f43000 ---p 00006000 b3:02 18777 /usr/lib/librt-2.20.so
76f43000-76f44000 r--p 00005000 b3:02 18777 /usr/lib/librt-2.20.so
76f44000-76f45000 rw-p 00006000 b3:02 18777 /usr/lib/librt-2.20.so
76f45000-76f65000 r-xp 00000000 b3:02 26121 /usr/lib/ld-2.20.so
76f65000-76f66000 rw-p 00000000 00:00 0
76f71000-76f74000 rw-p 00000000 00:00 0
76f74000-76f75000 r--p 0001f000 b3:02 26121 /usr/lib/ld-2.20.so
76f75000-76f76000 rw-p 00020000 b3:02 26121 /usr/lib/ld-2.20.so
76f76000-76fdf000 r-xp 00000000 b3:02 3599 /usr/bin/timedatectl
76fdf000-76fe1000 r--p 00068000 b3:02 3599 /usr/bin/timedatectl
76fe1000-76fe2000 rw-p 0006a000 b3:02 3599 /usr/bin/timedatectl
774d7000-774f8000 rw-p 00000000 00:00 0 [heap]
7e8bc000-7e8dd000 rw-p 00000000 00:00 0 [stack]
7e9da000-7e9db000 r-xp 00000000 00:00 0 [sigpage]
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]
Aborted (core dumped)
[root at kd5dfb_rpi2 ~]#
On Sat, Apr 11, 2015 at 1:18 AM, Doug Crompton <doug at crompton.com> wrote:
>
> We are very happy to announce the release of Allstar on the Raspberry Pi 2
> .
>
> The code has undergone many alpha and beta releases and we feel confident
> that it is ready for production use. Although the look and feel is very
> similar there are several changes from the BBB 1.2.1 release most of which
> are documented below.
>
> A BBB version 1.3 update is in the works and should be out in a few weeks.
>
> What has not changed -
>
> The RPi2 Allstar image is mostly modeled after the BBB. It has the same
> scripted setup and operation will look the same except for the changes
> noted below.
>
> What has changed or is new from the BBB 1.2.1 image -
>
> First of all the RPi2 is computationally faster than the BBB. It boots
> damn fast. You should have Allstar running and radio messages in 10-15
> seconds after power on. It should handle two simplesusb radio nodes.
> usbradio is still NOT recommended and may never be in its current form. See
> future notes below.
>
> We are using the newest ArchLinux kernel and different networking and
> timesync functions then were used on the BBB. No difference should be noted
> at the user level but there are many behind the scene improvements.
>
> There are several new scripts which are described in the scripts how-to
> on the hamvoip.org web page.
>
> The setup routine now also configures simpleusb. There is a small radio
> database that will be expanded with user input in the future. Make sure you
> understand the configuration parameters before changing them
> indiscriminately. If you are moving a radio from another Allstar simpleusb
> configured system the settings including audio levels would be the same on
> the RPi2. So make a note of them before you switch.
>
> simpleusb now includes two new commands, preemphasis to go along with
> the long existing deemphasis and rxaudiodelay to eliminate squelch tails.
> rxaudiodelay takes a value from 0-24. 0 or commenting the line results in
> no delay. Values 1 to 24 are the number of 20ms frames of delay. Typical
> values are from 5-10. Listen on iaxrtp or another local node to hear your
> own squelch tail. It is the tail the node radio creates when you
> immediately unkey not when your radio squelches. Experiment and use the
> minimum value that consistently eliminates the squelch tail.
>
> Allmon2 is pre-installed. See the how-to on the hamvoip.org web page.
>
> The RPi2 does not have a shutdown switch. See the how-to on the web
> page for information on how to add a switch. Software support for a switch
> is built-in to the distribution but it needs to be turned on in
> /usr/local/etc/allstar.env Other methods of shutdown are sending a
> shutdown command using ssh or a HDMI monitor and keyboard or activating
> DTMF control in the rpt.conf functions section. When you halt the processor
> you will need to power cycle to restart. So this is generally not something
> you would want to do remotely. It is a good idea to always properly
> shutdown your system. Unless absolutely necessary don't just pull the power.
>
> GPIO works and the wiringpi GPIO C library and command line functions
> are included. See /usr/src/examples/GPIO/wiringpi for examples.
>
> The weather scripts have been updated. See the weather howto on the web
> page for updates.
>
> All other features except those noted below that are now on the BBB
> 1.2.1 version should work fine on the RPi2.
>
> What does not yet work on the RPi2 -
>
> Automated Wireless Ethernet is not yet implemented. It will be on the
> next version which should be out fairly quickly after the v1.0 release. It
> could be done manually and we may make a script or how-to available in the
> next few weeks.
>
> GPIO control of PTT and COS are also not implemented but will be very
> soon. See future development below.
>
> Future development -
>
> Development is under way to write new channel drivers specifically for
> the BBB and RPi2 using the ALSA rather than the obsolete OSS sound
> interface that is used in the current Allstar. If will be multi-threaded
> with a separate manager thread to handle telemetry. This will allow
> interface to virtually any audio device that can be hooked to the board. We
> also feel that the current usbradio type commands will have a high
> likelihood of working on the RPi2 with the new code and it will also make
> GPIO interfacing for COS, PTT, etc. much easier. It also opens the door to
> use better DSP software packages using the floating point capability of the
> RPi2. Audio noise floor and quality could be even better than it is now. We
> are very excited about the possibilities. You should see test versions of
> these drivers in the next few months.
>
> We will continue to update the BBB code but I can see much more
> development effort going into the RPi2 in the future. For that reason I
> would recommend that any future purchases for new servers be the RPi2
> rather than the BBB. It is also likely we will see the BBB's availability
> go down and cost go up in the future as sales go down. It is hard to
> predict a time line on this so just be aware it could happen. That being
> said if your BBB board is working well and serving your needs there is no
> reason to replace it.
>
> More updates on the web page will happen over the next few weeks, so be
> patient. Some of the updates mentioned above are not yet complete. Also be
> sure to reload web pages and how-to's to make sure you have the current
> version. The RPi2 like the BBB is extremely easy to setup using the
> automated scripts. Just be sure to have all your information together
> before you start - node#, Node PW, IP address and gateway if static, etc.
>
> The direct download link for the RPi2 V1.0 release is:
>
> <http://www.hamvoip.org/RPi2/RPi2_V1.0_Allstar.zip>
> http://www.hamvoip.org/RPi2/RPi2_V1.0_Allstar.zip
>
> This link also appears on the hamvoip.org website.
>
> Thank you for your patience.
>
> Have fun, the RPi2 Allstar Team, WA3DSP, KB4FXC, W0AMN
>
>
>
>
>
> *Visit http://hamvoip.org <http://hamvoip.org> for more information.73
> DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page -
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150413/9c20b330/attachment.html>
More information about the arm-allstar
mailing list