[App_rpt-users] limey linux and parallel ports

[Shane Morris]

I feel I should defend myself for the benefit of the group in saying I
felt Jims exasperation. It clearly states on the Limey Linux page,
address http://stats.allstarlink.org/limeylinux/ that "Single image
support for Intel D201GLY2, D945GCLF, D945GCLF2, D945GCLF2D and Igoe
Logic I3386G motherboards using cfimg-i686-supported-1.0.9.tgz."

That would suggest to me that the image is specific for those
motherboards, with drivers also specific to those motherboards. So
running a trimmed down, embedded CF image linux on a AMD64 is not
going to work. Additionally, the page at that address says "Limey
linux is built entirely from sources that the make files in package
downloads as it needs them." which is further evidence of this
trimming down. Why bloat something that has a half gig of CF space
with drivers for a million motherboards you'll never use?

Now, I *know* your system isn't an AMD64, but as Jim put it, its not
one of those systems listed either. So my suggestion of using ACiD was
appropriate, even if I directed you to (not so gently) RTFM. Yes, I
know that ACiD might have bloat too, but its better than not having
drivers for essential pieces of hardware, right?

The reason I *never* picked up Limey is because I didn't possess any
of those boards, nor will I ever think I will. I could've gone ACiD
too, but its a 2.6 based kernel on x86 - my focus is low power ARM. It
turns out, group, that my "low powered" ARM is a little TOO low
powered, right? Ergo, the RaspPi. I suspect the CubieBoard may work
better, owing to its clock speed, and multiple on chip USB, but I'm
not in a position to say, as I'm not a developer of this software.

To my credit, I have gotten a Fit PC-3 now, an AMD APU based system,
and I am anxiously awaiting the image from a fellow New South Welshman
(whose name I don't want to trawl through my mail for at the moment).
There is talk of making the image for ARM, who knows, thats the
future, I don't have a crystal ball. But I do know one thing - what it
says on the Limey Linux page.

I felt Jims exasperation - Jim and I have talked on occasion about the
kernel drivers issue for the RaspPi, and my explanation of it, which
boiled down to "Its a closed source core running open source
software." We now know thats been opened, but as the Institute crows
about it, Allwinner had knocked that one off first - hence my purchase
of a CubieBoard with an Allwinner A10 chip.

In any case, I apologise for not being gentle, but its in plain sight.
I do seem to remember you said something about "No documentation..."
Ummm, I'm not certain how you work that out when I've evidently seen
this page, referenced it, and pasted in the comments under scrutiny
for your benefit. There is no "secret society" here - I had searched
the archives before I posted my question about RaspPi, and found no
comments. Since this is my area, I made others aware of it.

Of course, Jim may have seen many, many more messages of this type,
allowing him to respond the way he did. I'd simply seen it, read it,
and understood it. It don't work unless you have one of those
motherboards. Oh, you're welcome to try, but should we realistically
support such a venture when you are pretty much warned that its not
supported? My dropping of the RaspPi thing is testament to this - and
not everyone knows about the Cubie yet. Hence my acquiring a Fit PC.

Others may see this differently, yourself included, thats the beauty
and joy of a free and open society. But I question the merits of a
venture to support a software designed for a specific purpose,
advertised for that specific purpose, and with limited support, except
the gentle grace (or not so gentle grace) of the community.

In any case, Jims been around these parts longer than me, hes seen
this more than me, I'm only a newcomer myself. I think any kind of
final opinion, intelligent or otherwise, should be left to Jim, if he
was to so wish.

I hope that is of substance enough for you to explain my reaction and
my exasperation.

On Mon, Jan 28, 2013 at 2:10 PM, REDBUTTON_CTRL <jrorke at cogeco.ca> wrote:
> Sounds like you have a simplex radio connected to the node and it by default
> is in full duplex mode.
>
> All new installed nodes are in full duplex repeater mode.
>
> Set duplex =0 in rpt.conf and in usbradio.conf.
>
> the moment the radio hears something it trys to repeat but your radio is
> only half duplex.
>
> Jon VA3RQ
>
>
>
>
>
> On 1/27/2013 9:56 PM, Benjamin L. Naber wrote:
>>
>> Well I'm not sure what rude behavior is all about, but I did get the TX
>> ptt portion working. I used the radio-tune-menu to get the TX audio
>> where the levels should be with an IFR-1600 service monitor and it
>> sounds great. No distortion, good clean audio.
>>
>> What I did figure out is that upon boot, then TX ptt is set to on. Then
>> when I connect via telephone portal, the TX drops, and then rekeys with
>> the node announce info. Then the TX ptt drops until it needs to rekey
>> again.
>>
>> Is this a bug? the TX ptt drive is set to 'on' until the machine tells
>> something to somewhere to enable ptt and output some audio?
>>
>> Now to get the RX to work. I also used the radio-tune-menu to make the
>> RX adjustments, however, it seems I have a quirk that needs to be
>> figured out. As soon as I key my HT, the node receives it and then keys
>> the TX immediately, does the courtesy tone, and drops carrier. I have
>> tried several different configurations under 'carrierfrom' and
>> 'ctcssfrom'. And it seems that if I set it to anything other than 'usb'
>> or 'dsp' it almost acts as if it's in a permanent loopback. After
>> changes are made and saved, I'll reboot the node and it will key up as
>> stated before, then it will wait about a minute, ID, drop carrier, then
>> the node will keyup again, do the no-link courtesy tone, drop carrier,
>> wait about half a second and then do it all over again. And this will
>> continue on until I unplug something. Any ideas?
>>
>> If some one is interested in hearing and intelligently talking to me
>> about this, I routinely monitor the AK4PY-L echolink and W4TVM IRLP
>> node. Or, you can call me.
>>
>> ~Benjamin, KB9LFZ
>>
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users