Great.
Thanks again.
Peter
On Sun, Jan 8, 2012 at 3:26 PM, Gregg Levine wrote:
> On Sun, Jan 8, 2012 at 6:02 PM, Peter Hollenbeck
> wrote:
> > Don't know why that didn't dawn on me. Plain as day. I have browsed all
> the
> > pages dealing with adding serial connectors.
> > Thank very much.
> >
On Sun, Jan 8, 2012 at 6:02 PM, Peter Hollenbeck wrote:
> Don't know why that didn't dawn on me. Plain as day. I have browsed all the
> pages dealing with adding serial connectors.
> Thank very much.
> Peter
>
> On Sun, Jan 8, 2012 at 12:48 PM, Gregg Levine
> wrote:
>>
>> On Sun, Jan 8, 2012 at 3
Don't know why that didn't dawn on me. Plain as day. I have browsed all the
pages dealing with adding serial connectors.
Thank very much.
Peter
On Sun, Jan 8, 2012 at 12:48 PM, Gregg Levine wrote:
> On Sun, Jan 8, 2012 at 3:41 PM, Peter Hollenbeck
> wrote:
> > Thanks very, very much.
> > But I s
On Sun, Jan 8, 2012 at 3:41 PM, Peter Hollenbeck wrote:
> Thanks very, very much.
> But I still don't understand why the serial port is needed.
> Peter
>
> On Sun, Jan 8, 2012 at 10:34 AM, p4trykx wrote:
>>
>> Dnia 08-01-2012 o 01:35:09 Peter Hollenbeck
>> napisał(a):
>>
>>
>>> Ah. I am beginnin
Thanks very, very much.
But I still don't understand why the serial port is needed.
Peter
On Sun, Jan 8, 2012 at 10:34 AM, p4trykx wrote:
> Dnia 08-01-2012 o 01:35:09 Peter Hollenbeck
> napisał(a):
>
>
> Ah. I am beginning to get it. I could run owserver and owhttp on the WRT
>> and access the
Dnia 08-01-2012 o 01:35:09 Peter Hollenbeck napisał(a):
Ah. I am beginning to get it. I could run owserver and owhttp on the WRT
and access the data from 192.168.1.xxx:. Correct?
Yes owserver talks directly to the hardware and then you can use many
clients to get/present data from it.
You
Greenbrae, Marin County.
Peter
On Sat, Jan 7, 2012 at 5:00 PM, Jerry Scharf wrote:
> On 01/07/2012 04:35 PM, Peter Hollenbeck wrote:
> > Ah. I am beginning to get it. I could run owserver and owhttp on the
> > WRT and access the data from 192.168.1.xxx:. Correct? Or I can use
> > your rrd me
On Sat, Jan 7, 2012 at 7:35 PM, Peter Hollenbeck wrote:
> Ah. I am beginning to get it. I could run owserver and owhttp on the WRT and
> access the data from 192.168.1.xxx:. Correct? Or I can use your rrd
> method. I had never heard of rrd. I read a bit and will read more.
> Isn't it amazing.
On 01/07/2012 04:35 PM, Peter Hollenbeck wrote:
> Ah. I am beginning to get it. I could run owserver and owhttp on the
> WRT and access the data from 192.168.1.xxx:. Correct? Or I can use
> your rrd method. I had never heard of rrd. I read a bit and will read
> more.
> Isn't it amazing. I am
Ah. I am beginning to get it. I could run owserver and owhttp on the WRT
and access the data from 192.168.1.xxx:. Correct? Or I can use your rrd
method. I had never heard of rrd. I read a bit and will read more.
Isn't it amazing. I am a 75 year old retired computer this-and-that near
San Franci
Dnia 08-01-2012 o 00:22:15 Peter Hollenbeck napisał(a):
> I would like to control a OneWire network from a WRT54G. Have read
> applicable posts on this forum but don't quit get it. Assuming I add one
> or
> two serial ports to the WRT54G, how does one control the OS?
You can user owserver on t
I would like to control a OneWire network from a WRT54G. Have read
applicable posts on this forum but don't quit get it. Assuming I add one or
two serial ports to the WRT54G, how does one control the OS? Using telnet
from another computer?
Thanks for any help.
This is a great forum.
Peter
-
Sorry for this misplaced e-mail, but I just wanted to see if there are
anyone who could give me some ideas about fixing a WRT54G router with
network problems...
My WRT54G (v2) router seem to have died recently... I'm not sure if it's
the bad weather with lightnings and thunder which broke the ne
If you look in /proc/mtd, you see that the flash-erase-size is
detected to 0x1 = 64kb for the mtd4 area.
ewrt ~# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/root 2816 2816 0 100% /
/dev/mtdblock/4320 132 188
Christian,
thanks for the patch, it does the job just fine, /opt now shows 188 1k
blocks available.
What size blocks does JFFS2_RESERVED_BLOCKS_... refer to though? The
patch reduces it from 3 to 1, or 5 to 2 to allow a write, but that still
results in df showing 132 1k blocks as used.
Paul Hilt
The simplest path is to use a regular PC,
for a WRT54G:
There are no guarantees here, you will certainly void any warranties,
you may end up with a WRT54G that is unresponsive and requires more
complex operations to recover it, if at all. However it worked for me,
and seems to have worked for many
Amazon is offering a good price on the WRT54G.
What is the simplest path for a LINUX dumbkoff
to get owfs working ? I have never compiled Linux
source.
Gus Salvatore Calabrese 720.222.1309 GSC
www.omegadogs.com Denver, CO
---
SF.Net
Oops... I'm so sorry for missing a patch to the kernel that I made.
ewrt works good with the current settings, but since my patches add
some more binaries to the flash-memory, there are much less memory
left for the jffs2 file-system.
To solve the problem I patched
ewrt-0.3/src/linux/linux/fs/jf
I built the WRT54G ewrt with owfs (Christan's source) by building ewrt,
patching & rebuilding. It seems to work fine, 1-wire directory and
devices all working etc. The image is about 3.3MB.
I am running this on a WRT54G v3.0.
There is no space on the jffs2 (/opt) partition, it shows as being
moun
There are definitely some kind of memory leak in owserver now which has
to be found. After one week of uptime owserver consumes 4.1Mb resident
memory. When starting up owserver the size is about 540kb.
Just wanted to warn you about this... I will try my very best to find
the problem as soon as po
I found the problem now... It's kind of a problem in the initialization
of pthread. __pthread_initialize() is automatically called when starting
an application. After running daemon() you get a new process id, and
internal pointers and pid's are pointing to the dead process and stack.
It works if
I don't have any ideas, but ever since your first precompile of owfs,
I've been runing in the background without the --foreground flags. I
noticed it in your package originally, but used my own startup scripts
since I've been using OpenWRT instead of BuzBox and now EWRT.
If you can tell me how to
I have tried to make the background startup-option work for the WRT54G
router. I have always had problems with this on my Coldfire processor,
so I have just continued using --foreground without thinking much about
it.
Since daemon() doesn't exist on MMU-less processors, I didn't care much
about it
23 matches
Mail list logo
