- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] ACID CD install boot failure
by Joe Bryant 17 Aug '11

17 Aug '11

David, The picture on my original post shows the exact point where the Centos boot stops, and reboots the machine. Not very far into it. The hard drive is a standard 60 gig IDE. From: shawpbx(a)gmail.com [mailto:shawpbx@gmail.com] On Behalf Of David KE6UPI Sent: Sunday, August 14, 2011 11:18 AM To: jbryant(a)bellsouth.net Subject: Re: [App_rpt-users] ACID CD install boot failure How far does the boot go? Does it stop loading initrd.img? Are you using IDE or SATA drives? I have installed CentOS then used the install files from ACID and that does work. If you are using SATA that might be the problem.. David On Sat, Aug 13, 2011 at 10:19 PM, Joe Bryant <jbryant(a)bellsouth.net> wrote: No, there are none. From: shawpbx(a)gmail.com [mailto:shawpbx@gmail.com] On Behalf Of David KE6UPI Sent: Saturday, August 13, 2011 10:36 PM To: jbryant(a)bellsouth.net Subject: Re: [App_rpt-users] ACID CD install boot failure Do you have any pci cards installed? David On Sat, Aug 13, 2011 at 9:55 AM, Joe Bryant <jbryant(a)bellsouth.net> wrote: All, I have a 2002 vintage, VIA EPIA Mini-ITX box (C3 Eden 800Mhz processor). It has 512 MB RAM, and a 60Gig hard drive. The ACID / CentOS install CD, will not complete the boot process, it goes into a loop. At the point shown in this picture: http://www.qsl.net/k4bry/mini-itx_boot-fail.jpg , the screen goes dark, and the box reboots into the CD again. The CD is good, it was used on my first install with no problems. I have manipulated the BIOS settings for several hours, with no change in the result. It may be caused by a lack of enough RAM, but I Don't know. If there is documentation on the minimum requirements for an ACID install, I can't find it. If I try to find RAM to take it to the 1 Gig maximum, it is likely to cost more than this old Motherboard is worth. After no progress with this, to see if it was hardware failure, I installed the Kubuntu-10.04-Alternate-i386 version of Ubuntu, GUI and all, without a hitch. It runs very slowy, which is to be expected, but it does run. Does anyone see an obvious problem, or have any idea what I should try next? I have a second box with the same Motherboard, It would be nice and cheap, if I could get them both working. Thanks for any help. Joe Bryant K4BRY _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Re: [App_rpt-users] ACID CD install boot failure
by Joe Bryant 14 Aug '11

14 Aug '11

No, there are none. From: shawpbx(a)gmail.com [mailto:shawpbx@gmail.com] On Behalf Of David KE6UPI Sent: Saturday, August 13, 2011 10:36 PM To: jbryant(a)bellsouth.net Subject: Re: [App_rpt-users] ACID CD install boot failure Do you have any pci cards installed? David On Sat, Aug 13, 2011 at 9:55 AM, Joe Bryant <jbryant(a)bellsouth.net> wrote: All, I have a 2002 vintage, VIA EPIA Mini-ITX box (C3 Eden 800Mhz processor). It has 512 MB RAM, and a 60Gig hard drive. The ACID / CentOS install CD, will not complete the boot process, it goes into a loop. At the point shown in this picture: http://www.qsl.net/k4bry/mini-itx_boot-fail.jpg , the screen goes dark, and the box reboots into the CD again. The CD is good, it was used on my first install with no problems. I have manipulated the BIOS settings for several hours, with no change in the result. It may be caused by a lack of enough RAM, but I Don't know. If there is documentation on the minimum requirements for an ACID install, I can't find it. If I try to find RAM to take it to the 1 Gig maximum, it is likely to cost more than this old Motherboard is worth. After no progress with this, to see if it was hardware failure, I installed the Kubuntu-10.04-Alternate-i386 version of Ubuntu, GUI and all, without a hitch. It runs very slowy, which is to be expected, but it does run. Does anyone see an obvious problem, or have any idea what I should try next? I have a second box with the same Motherboard, It would be nice and cheap, if I could get them both working. Thanks for any help. Joe Bryant K4BRY _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

ACID Installation Problem
by Howard Small 13 Aug '11

13 Aug '11

Hi All I installed the ACID on a Toshiba Tecra A3 without any problems except that it does not install a driver for the Ethernet adapter (at least that is what I think is the problem). When I look at my DHCP server it is giving an ip address to the Tecra but after the installation reboot when it gets to the section where it checks the ip address at eth0 it fails and the installation cannot proceed. There is only one led on the Ethernet socket alight. I am fine on Windows but linux??? So how do I address this problem? Thanks Howard VK4BS

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 30, Issue 12
by nuhtrue＠gmail.com 13 Aug '11

13 Aug '11

I also forgot to mention, since the Astro Saber and XTS3000 are basically the same radio, differences in Host rev could definitely make a difference, all other things being the same. Bob KK6RQ

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 30, Issue 12
by nuhtrue＠gmail.com 13 Aug '11

13 Aug '11

Do the Astro Saber and XTS flashcodes both have the same MDC values? Bob KK6RQ On Aug 13, 2011 9:00am, app_rpt-users-request(a)ohnosec.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > Today's Topics: > 1. MDC Status Reply not working with XTS model radios (Tony KT9AC) > 2. Re: MDC Status Reply not working with XTS model radios > (Paul J. Agamata) > 3. Re: MDC Status Reply not working with XTS model radios > (=?utf-8?B?VG9ueSBLVDlBQw==?=) > ---------------------------------------------------------------------- > Message: 1 > Date: Fri, 12 Aug 2011 21:18:56 -0500 > From: Tony KT9AC kt9ac(a)ameritech.net> > To: app_rpt-users(a)ohnosec.org > Subject: [App_rpt-users] MDC Status Reply not working with XTS model > radios > Message-ID: 4E45DF10.60001(a)ameritech.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > This might not be a widely-used feature, but I wanted to post it here > first versus directly to Jim (to follow the rules). > There is a feature within App_rpt where you can send MDC1200 status > messages and have commands acted upon. I've used a MCS2000 mobile and > Astro Saber successfully for a very fast and efficient control method. > Recently I sold my Astro Saber and bought an XTS3000. I can still send > MDC statuses and get them acted upon, but no longer get the "ACK" back > from Allstar. > No changes in software and the logs show the op=46 like before and the > proper Unit ID and status sent...so I'm at a loss of why Allstar stops > trying to ACK these statuses for this one type of radio (my mobile still > works fine). Debug suggestions and code testing welcome. > Thanks, > Tony > ------------------------------ > Message: 2 > Date: Fri, 12 Aug 2011 16:25:27 -1000 > From: "Paul J. Agamata" > To: Tony KT9AC kt9ac(a)ameritech.net>, "app_rpt-users(a)ohnosec.org" > app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] MDC Status Reply not working with XTS > model radios > Message-ID: > Content-Type: text/plain; charset="us-ascii" > I have the same issues between two radios. My XTS-5000 responds properly > but my XTS-3000 does not. I'll do some digging this weekend to see where > the issue is. Because my XTS-5000 functions properly, it's probably a > codeplug issue. > Paul > On 8/12/11 4:18 PM, "Tony KT9AC" kt9ac(a)ameritech.net> wrote: > >This might not be a widely-used feature, but I wanted to post it here > >first versus directly to Jim (to follow the rules). > > > >There is a feature within App_rpt where you can send MDC1200 status > >messages and have commands acted upon. I've used a MCS2000 mobile and > >Astro Saber successfully for a very fast and efficient control method. > >Recently I sold my Astro Saber and bought an XTS3000. I can still send > >MDC statuses and get them acted upon, but no longer get the "ACK" back > >from Allstar. > > > >No changes in software and the logs show the op=46 like before and the > >proper Unit ID and status sent...so I'm at a loss of why Allstar stops > >trying to ACK these statuses for this one type of radio (my mobile still > >works fine). Debug suggestions and code testing welcome. > > > >Thanks, > >Tony > > > >_______________________________________________ > >App_rpt-users mailing list > >App_rpt-users(a)ohnosec.org > >http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > ------------------------------ > Message: 3 > Date: Fri, 12 Aug 2011 21:38:41 -0500 > From: "=?utf-8?B?VG9ueSBLVDlBQw==?=" kt9ac(a)ameritech.net> > To: "=?utf-8?B?UGF1bCBKLiBBZ2FtYXRh?=" , > "=?utf-8?B?YXBwX3JwdC11c2Vyc0BvaG5vc2VjLm9yZw==?=" > app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] MDC Status Reply not working with XTS > model radios > Message-ID: 416407.82154.qm(a)smtp107.sbc.mail.bf1.yahoo.com> > Content-Type: text/plain; charset="utf-8" > Thanks Paul. > ----- Reply message ----- > From: "Paul J. Agamata" > Date: Fri, Aug 12, 2011 9:25 pm > Subject: [App_rpt-users] MDC Status Reply not working with XTS model > radios > To: "Tony KT9AC" kt9ac(a)ameritech.net>, "app_rpt-users(a)ohnosec.org" > app_rpt-users(a)ohnosec.org> > I have the same issues between two radios. My XTS-5000 responds properly > but my XTS-3000 does not. I'll do some digging this weekend to see where > the issue is. Because my XTS-5000 functions properly, it's probably a > codeplug issue. > Paul > On 8/12/11 4:18 PM, "Tony KT9AC" kt9ac(a)ameritech.net> wrote: > >This might not be a widely-used feature, but I wanted to post it here > >first versus directly to Jim (to follow the rules). > > > >There is a feature within App_rpt where you can send MDC1200 status > >messages and have commands acted upon. I've used a MCS2000 mobile and > >Astro Saber successfully for a very fast and efficient control method. > >Recently I sold my Astro Saber and bought an XTS3000. I can still send > >MDC statuses and get them acted upon, but no longer get the "ACK" back > >from Allstar. > > > >No changes in software and the logs show the op=46 like before and the > >proper Unit ID and status sent...so I'm at a loss of why Allstar stops > >trying to ACK these statuses for this one type of radio (my mobile still > >works fine). Debug suggestions and code testing welcome. > > > >Thanks, > >Tony > > > >_______________________________________________ > >App_rpt-users mailing list > >App_rpt-users(a)ohnosec.org > >http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >

1 0

ACID CD install boot failure
by Joe Bryant 13 Aug '11

13 Aug '11

All, I have a 2002 vintage, VIA EPIA Mini-ITX box (C3 Eden 800Mhz processor). It has 512 MB RAM, and a 60Gig hard drive. The ACID / CentOS install CD, will not complete the boot process, it goes into a loop. At the point shown in this picture: http://www.qsl.net/k4bry/mini-itx_boot-fail.jpg , the screen goes dark, and the box reboots into the CD again. The CD is good, it was used on my first install with no problems. I have manipulated the BIOS settings for several hours, with no change in the result. It may be caused by a lack of enough RAM, but I Don't know. If there is documentation on the minimum requirements for an ACID install, I can't find it. If I try to find RAM to take it to the 1 Gig maximum, it is likely to cost more than this old Motherboard is worth. After no progress with this, to see if it was hardware failure, I installed the Kubuntu-10.04-Alternate-i386 version of Ubuntu, GUI and all, without a hitch. It runs very slowy, which is to be expected, but it does run. Does anyone see an obvious problem, or have any idea what I should try next? I have a second box with the same Motherboard, It would be nice and cheap, if I could get them both working. Thanks for any help. Joe Bryant K4BRY

1 0

Re: [App_rpt-users] MDC Status Reply not working with XTS model radios
by Tony KT9AC 13 Aug '11

13 Aug '11

Thanks Paul. ----- Reply message ----- From: "Paul J. Agamata" <Sysman(a)Xceptions.COM> Date: Fri, Aug 12, 2011 9:25 pm Subject: [App_rpt-users] MDC Status Reply not working with XTS model radios To: "Tony KT9AC" <kt9ac(a)ameritech.net>, "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> I have the same issues between two radios. My XTS-5000 responds properly but my XTS-3000 does not. I'll do some digging this weekend to see where the issue is. Because my XTS-5000 functions properly, it's probably a codeplug issue. Paul On 8/12/11 4:18 PM, "Tony KT9AC" <kt9ac(a)ameritech.net> wrote: >This might not be a widely-used feature, but I wanted to post it here >first versus directly to Jim (to follow the rules). > >There is a feature within App_rpt where you can send MDC1200 status >messages and have commands acted upon. I've used a MCS2000 mobile and >Astro Saber successfully for a very fast and efficient control method. >Recently I sold my Astro Saber and bought an XTS3000. I can still send >MDC statuses and get them acted upon, but no longer get the "ACK" back >from Allstar. > >No changes in software and the logs show the op=46 like before and the >proper Unit ID and status sent...so I'm at a loss of why Allstar stops >trying to ACK these statuses for this one type of radio (my mobile still >works fine). Debug suggestions and code testing welcome. > >Thanks, >Tony > >_______________________________________________ >App_rpt-users mailing list >App_rpt-users(a)ohnosec.org >http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

MDC Status Reply not working with XTS model radios
by Tony KT9AC 13 Aug '11

13 Aug '11

This might not be a widely-used feature, but I wanted to post it here first versus directly to Jim (to follow the rules). There is a feature within App_rpt where you can send MDC1200 status messages and have commands acted upon. I've used a MCS2000 mobile and Astro Saber successfully for a very fast and efficient control method. Recently I sold my Astro Saber and bought an XTS3000. I can still send MDC statuses and get them acted upon, but no longer get the "ACK" back from Allstar. No changes in software and the logs show the op=46 like before and the proper Unit ID and status sent...so I'm at a loss of why Allstar stops trying to ACK these statuses for this one type of radio (my mobile still works fine). Debug suggestions and code testing welcome. Thanks, Tony

2 1

Authentication issue / server down?
by Lu Vencl 12 Aug '11

12 Aug '11

I just build my next node, and can't see to get registered.. I also noticed the dial in # is not working as well. I have waited at least 4 hours and still nothing. Anyone know if there might be an issue? Thanks Lu, KA4EPS

4 4

Re: [App_rpt-users] Switching from chan_usbradio to chan_simpleusb
by K&R Yoksh 12 Aug '11

12 Aug '11

----- Original Message ----- > Date: Thu, 11 Aug 2011 12:43:19 -0700 (PDT) > From: Tony KT9AC > Subject: [App_rpt-users] Switching from chan_usbradio to chan_simpleusb > > Is there a simple way to change a node from chan_usbradio to > chan_simpleusb? I have updated my system to do the PL encoding itself and > would like to remove the burden of generating PL from the URI. > > Sorry I can't seem to find an easy way to switch it over in the docs. > > Tony > Hello Tony, I've been using simpleusb for a little while, and find that it works quite well. Here are some hints to switch over to Simpleusb: 1) In rpt.conf, change your rxchannel to: rxchannel=SimpleUSB/usb2211 2) Copy usbradio.conf to simpleusb.conf 3) At a prompt, type simpleusb-tune-menu. Adjust your audio levels, etc for each fob, then select W to write the settings to simpleusb_tune_usbxxxx.conf 73 and good luck, Kyle Yoksh K0KN Olathe, KS Allstar 2210-2215

1 0