Re: [Owfs-developers] segfault in owhttp 2.8p2 accessing BAE /910
I have a cronjob which update the pages at: http://owfs.sourceforge.net/statcvs/2010-11.html The view-source links works correct there. /Christian On Tue, 2010-11-30 at 19:04 -0500, Paul Alfille wrote: Here are the commits: http://www.owfs.org/statcvs/commitlog.html The transition from CVS to SVN doesn't seem seamless based on my reading. I'm willing to use a new tool, just not to researching and performing the transition. Any volunteers? Paul Alfille P.S.: Wasn't it discussed to move to SVN ? it's really quite impossible to follow the commits into CVS and quickly see what changed (might also be rather a sf-issue than a CVS-issue!) -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS roadmap
I found one major bug which needs to be fixed as soon as possible. The
rwlocks have never worked actually!?!
If something will make owfs more stable, it's probably by fixing this
bug. Strange that nobody have seen this before.
void my_rwlock_init(my_rwlock_t * my_rwlock)
{
_MUTEX_INIT(my_rwlock-protect_reader_count);
sem_init((my_rwlock-allow_readers), 0, 1);
sem_init((my_rwlock-no_processes), 0, 1);
my_rwlock-reader_count = 1; // This should be initiated to 0! (we
don't have any readers at startup)
}
Changing the reader_count to 0 will probably result into several
dead-locks, so I haven't changed it yet.
Write-locks will ALWAYS be allowed, even if there are several read-locks
active. Look in the example below:
my_rwlock_read_lock(rwlock);
my_rwlock_read_lock(rwlock);
my_rwlock_read_lock(rwlock);
my_rwlock_write_lock(rwlock);
print(this will be printed!\n);
Paul, do you want to look at this?
/Christian
On Thu, 2010-10-28 at 19:54 +1100, Rob Conway wrote:
Hi,
Just wondering if there was an update on the roadmap for OWFS. It
does everything I want it to do however was just wondering if there
was any significant changes in the pipeline over the next 6 - 12
months.
I would also like to know if the Alias function is OK. I can remember
some time ago there was some kind of caution in using the alias
file.
rob
--
Nokia and ATT present the 2010 Calling All Innovators-North America contest
Create new apps games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
___ Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
--
Nokia and ATT present the 2010 Calling All Innovators-North America contest
Create new apps games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New Release 2.7p39
I have re-built some new packages, but they still say 2.7p38 since configure.ac isn't updated in the repository. http://owfs.sourceforge.net/nslu2/packages/Packages On Sun, 2010-07-18 at 21:06 -0400, brucek wrote: nslu2 packages is still at 2.7p37-1. Any chance you can update it any time soon. Thanks bruce - Original Message - From: Paul Alfille To: owfs-developers Sent: Sunday, July 18, 2010 2:23 PM Subject: [Owfs-developers] New Release 2.7p39 Release OWFS 2.7p39 Major addition is the usb scanning funtion. Command line option -uscan or --usb_scan or --usb_scan=10 Every time interval (default 10 seconds) the OWFS program will scan the USB bus for a new DS9490R adapter and add it to the list of bus masters. Even the case where no USB devices exist at startup will be handled, the program will scan and wait. __ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first __ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New Release 2.7p39
I'm not sure if the Upload failed, but I have uploaded it again, and successfully downloaded these files for example. http://owfs.sourceforge.net/nslu2/packages/owfs_2.7p38-1_armeb.ipk.content http://owfs.sourceforge.net/nslu2/packages/owfs_2.7p38-1_armeb.ipk http://owfs.sourceforge.net/nslu2/packages/Packages http://owfs.sourceforge.net/nslu2/packages/Packages.gz On Mon, 2010-07-19 at 09:22 -0400, brucek wrote: When I run: #ipkg update #ipkg -test upgrade I am getting 404 errors for p38-1 packages. I'm currently running 2.7p32, because I had stability problems with P37 (that was the next posted release?) Thanks Bruce - Original Message - From: Christian Magnusson m...@mag.cx To: OWFS (One-wire file system) discussion and help owfs-developers@lists.sourceforge.net Sent: Monday, July 19, 2010 8:25 AM Subject: Re: [Owfs-developers] New Release 2.7p39 I have re-built some new packages, but they still say 2.7p38 since configure.ac isn't updated in the repository. http://owfs.sourceforge.net/nslu2/packages/Packages On Sun, 2010-07-18 at 21:06 -0400, brucek wrote: nslu2 packages is still at 2.7p37-1. Any chance you can update it any time soon. Thanks bruce - Original Message - From: Paul Alfille To: owfs-developers Sent: Sunday, July 18, 2010 2:23 PM Subject: [Owfs-developers] New Release 2.7p39 Release OWFS 2.7p39 Major addition is the usb scanning funtion. Command line option -uscan or --usb_scan or --usb_scan=10 Every time interval (default 10 seconds) the OWFS program will scan the USB bus for a new DS9490R adapter and add it to the list of bus masters. Even the case where no USB devices exist at startup will be handled, the program will scan and wait. __ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first __ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] downgrade OWFS NSLU2 Unslung
You can always download the old files manually and install them separate with ipkg Something like below... cd /tmp wget http://owfs.sourceforge.net/nslu2/packages/owfs_2.7p32-2_armeb.ipk wget http://owfs.sourceforge.net/nslu2/packages/owlib_2.7p32-2_armeb.ipk wget http://owfs.sourceforge.net/nslu2/packages/owcapi_2.7p32-2_armeb.ipk wget http://owfs.sourceforge.net/nslu2/packages/owshell_2.7p32-2_armeb.ipk kill-owfs ipkg remove owfs owcapi owshell owlib ipkg install owshell_2.7p32-2_armeb.ipk owlib_2.7p32-2_armeb.ipk owcapi_2.7p32-2_armeb.ipk owfs_2.7p32-2_armeb.ipk /Christian The URL has been remove :-( I posted the following information on another topic: I installed this version but experience problems using my LCD display. The problem occurs after using a script or the directory listing. I change the message string (/tmp/1wire/29.50640400/LCD_H/message). I receive the following message when i try to use the directory listing. The 1-wire web server is carefully constrained for security and stability. Your requested device is not recognized. When i try the following command: /opt/etc/init.d/S70owserver start. I can change the message once and then everything stops functioning again. The following problem also occurs: I have a 4 line LCD display and normally i write 4 lines of text. But now the last part of line 4 (about 8 characters) is displayed on the first line. -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS for NSLU2
Oopps. I failed to upload all files to sourceforge. I started to upload the files again. Will be done in a few minutes.. /Christian On Sun, 2010-05-16 at 07:05 +, Eduard wrote: Christian Magnusson mag at mag.cx writes: I have recompiled the latest CVS now, and it's uploaded to the dir: http://owfs.sourceforge.net/nslu2/packages/Packages http://owfs.sourceforge.net/nslu2/packages/owfs_2.7p37-1_armeb.ipk.content etc. /Christian On Sat, 2010-05-15 at 15:37 +, Eduard wrote: Paul Alfille paul.alfille at gmail.com writes: Can you be more specific? Do you mean for the Unslung or similar distro? I think many people install debian onto a hard disk or flash and then just compile it normally. Paul For the Unslung distro. The latest version available is 27p32. Eduard Christian, I receive the following messages after running ipkg update and the ipkg upgrade. I noticed that before you placed the new 2.7p31 package i was unable to do a new OWFS installation because there was no package available? Mesages: # ipkg upgrade Upgrading owcapi on root from 2.7p32-2 to 2.7p37-1... Downloading http://owfs.sourceforge.net/nslu2/packages/./owcapi_2.7p37-1_armeb.i pk Upgrading owfs on root from 2.7p32-2 to 2.7p37-1... Downloading http://owfs.sourceforge.net/nslu2/packages/./owfs_2.7p37-1_armeb.ipk Upgrading owlib on root from 2.7p32-2 to 2.7p37-1... Downloading http://owfs.sourceforge.net/nslu2/packages/./owlib_2.7p37-1_armeb.ip k Upgrading owshell on root from 2.7p32-2 to 2.7p37-1... Downloading http://owfs.sourceforge.net/nslu2/packages/./owshell_2.7p37-1_armeb. ipk Nothing to be done Collected errors: ipkg_download: ERROR: Command failed with return value 8: `wget --passive-ftp -q -P /tmp/ipkg-md9Ei6 http://owfs.sourceforge.net/nslu2/packages/./owcapi_2.7p 37-1_armeb.ipk' Failed to download owcapi. Perhaps you need to run 'ipkg update'? ipkg_download: ERROR: Command failed with return value 8: `wget --passive-ftp -q -P /tmp/ipkg-md9Ei6 http://owfs.sourceforge.net/nslu2/packages/./owfs_2.7p37 -1_armeb.ipk' Failed to download owfs. Perhaps you need to run 'ipkg update'? ipkg_download: ERROR: Command failed with return value 8: `wget --passive-ftp -q -P /tmp/ipkg-md9Ei6 http://owfs.sourceforge.net/nslu2/packages/./owlib_2.7p3 7-1_armeb.ipk' Failed to download owlib. Perhaps you need to run 'ipkg update'? ipkg_download: ERROR: Command failed with return value 8: `wget --passive-ftp -q -P /tmp/ipkg-md9Ei6 http://owfs.sourceforge.net/nslu2/packages/./owshell_2.7 p37-1_armeb.ipk' Failed to download owshell. Perhaps you need to run 'ipkg update'? -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS for NSLU2
It looks like your owserver-process core-dumps when you access that 29.50640400/LCD_H/message file. I'm afraid that I have no such 1-wire device, and it would be best to try gdb/valgrind and debug owserver on a bigger linux-distribution to make sure there are no bad memory accesses. I don't think it's a specific problem for the NSLU2 package when it core-dumps like that. Turn on the core-dumps, and start owserver in the foreground. # ulimit -a # ulimit -c unlimited # ulimit -a # cd /tmp # owserver --foreground --error_level=2 -p 4304 -u (I'm not sure if you srat Try to access the page and see if it create a core-file under /tmp/core* This core-file could be analyzed with gdb, so send it to me if you can re-create it. Tell me how it goes... /Christian On Sun, 2010-05-16 at 14:45 +, Eduard wrote: Christian Magnusson mag at mag.cx writes: Oopps. I failed to upload all files to sourceforge. I started to upload the files again. Will be done in a few minutes.. /Christian I installed this version but experience problems using my LCD display. The problem occurs after using a script or the directory listing. I change the message string (/tmp/1wire/29.50640400/LCD_H/message). I receive the following message when i try to use the directory listing. The 1-wire web server is carefully constrained for security and stability. Your requested device is not recognized. When i try the following command: /opt/etc/init.d/S70owserver start. I can change the message once and then everything stops functioning again. The following problem also occurs: I have a 4 line LCD display and normally i write 4 lines of text. But now the last part of line 4 (about 8 characters) is displayed on the first line. /Eduard -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owserver stops responding
I looked breifly on the source, and I cant find any reason to the hanging
lock in ow_read.c:244.
It should lock the parsedname, read the value, and unlock just after its
finished. I cant see that it could skip this unlock function.
Im afraid I have too much here at work and home to look more into it right
now.
/Christian
From: Patrik Åkerfeldt [mailto:patrik.akerfe...@gmail.com]
Sent: den 11 mars 2010 18:25
To: OWFS (One-wire file system) discussion and help
Subject: Re: [Owfs-developers] owserver stops responding
Thanks for the reply,
Here's the output from gdb:
Thread 3 (Thread 0x473f0940 (LWP 24920)):
#0 0x003c0300c21f in sem_timedwait () from /lib64/libpthread.so.0
#1 0x004047ee in Handler (file_descriptor=14) at handler.c:249
#2 0x2ba23185266b in ServerProcessHandler (arg=0x27dc6c0) at
ow_net_server.c:158
#3 0x003c030062f7 in start_thread () from /lib64/libpthread.so.0
#4 0x003c028d1e3d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x47df1940 (LWP 24921)):
#0 0x003c0300c888 in __lll_mutex_lock_wait () from
/lib64/libpthread.so.0
#1 0x003c030088a5 in _L_mutex_lock_107 () from /lib64/libpthread.so.0
#2 0x003c03008333 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3 0x2ba231850466 in LockGet (pn=0x47df1048) at ow_locks.c:189
#4 0x2ba231858cad in FS_r_given_bus (owq=0x47df1020) at ow_read.c:244
#5 0x2ba231858fc2 in FS_read_distribute (owq=0x47df1020) at
ow_read.c:207
#6 0x2ba2318597ec in FS_read_postparse (owq=0x47df1020) at
ow_read.c:110
#7 0x0040332c in ReadHandler (hd=0x473efec0, cm=0x47df10e0,
owq=0x47df1020)
at read.c:84
#8 0x00403ff7 in DataHandler (v=value optimized out) at
data.c:133
#9 0x003c030062f7 in start_thread () from /lib64/libpthread.so.0
#10 0x003c028d1e3d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x2ba231d322c0 (LWP 14327)):
#0 0x003c0300dba8 in do_sigwait () from /lib64/libpthread.so.0
#1 0x003c0300dc4d in sigwait () from /lib64/libpthread.so.0
#2 0x2ba231852179 in ServerProcess (HandlerRoutine=0x404350 Handler,
Exit=0x402050 ow_exit) at ow_net_server.c:349
#3 0x0040223b in main (argc=8, argv=0x7fff792bf808) at
owserver.c:162
I hope this will explain things.
-Patrik
2010/3/10 Christian Magnusson m...@mag.cx
It really seems like a dead-lock in the code + It seems a bit strange that
the handler_count inside the brackets are not incremented one by one.
This means that you have multiple applications polling the device
I would
guess 5-10 shell-scripts filling up the request queue/capacity.
# ps ef | grep owserver
Find the process id of owserver.
Halt the execution with gdb.
# gdb /opt/owfs/bin/owserver p 12345
(show backtrace for all running threads with gdb)
$ thread apply all bt
Press return to scroll down all pages and copy the result here. It will show
if any thread are hanging in a lock-call.
I will be on vacation until Sunday, but Im sure Paul can trace down the
problem if the gdb-output show some obvious hanging.
/Christian
From: Patrik Åkerfeldt [mailto:patrik.akerfe...@gmail.com]
Sent: den 10 mars 2010 18:57
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] owserver stops responding
I have the same problem with owfs-2.7p31. Although the output is slightly
different:
DEBUG: handler.c:SingleHandler(317) NOPING handler {165}
/26.6447E700/temperature
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {170}
/26.6447E700/vis
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {153}
/26.6447E700/temperature
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {161}
/26.6447E700/temperature
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {157}
/26.6447E700/vis
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {156}
/26.6447E700/vis
I would really appreciate some help in this matter.
-Patrik
Den 10 mars 2010 11.49 skrev Patrik Åkerfeldt patrik.akerfe...@gmail.com:
No, wrong conclusion of me. I removed the /temperature polling and let the
vis reading remain but it still hangs.
I will try the latest version of owfs instead.
-Patrik
Den 10 mars 2010 11.46 skrev Patrik Åkerfeldt patrik.akerfe...@gmail.com:
Could it be that I poll the same device (26.6447E700) on different
readings (temperature and vis) at the same time? And that it some how hangs?
Polling is made from bash scripts invoked using crontab at the same
intervall.
-Patrik
Den 9 mars 2010 21.29
Re: [Owfs-developers] owserver stops responding
It really seems like a dead-lock in the code + It seems a bit strange that
the handler_count inside the brackets are not incremented one by one.
This means that you have multiple applications polling the device
I would
guess 5-10 shell-scripts filling up the request queue/capacity.
# ps ef | grep owserver
Find the process id of owserver.
Halt the execution with gdb.
# gdb /opt/owfs/bin/owserver p 12345
(show backtrace for all running threads with gdb)
$ thread apply all bt
Press return to scroll down all pages and copy the result here. It will show
if any thread are hanging in a lock-call.
I will be on vacation until Sunday, but Im sure Paul can trace down the
problem if the gdb-output show some obvious hanging.
/Christian
From: Patrik Åkerfeldt [mailto:patrik.akerfe...@gmail.com]
Sent: den 10 mars 2010 18:57
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] owserver stops responding
I have the same problem with owfs-2.7p31. Although the output is slightly
different:
DEBUG: handler.c:SingleHandler(317) NOPING handler {165}
/26.6447E700/temperature
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {170}
/26.6447E700/vis
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {153}
/26.6447E700/temperature
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {161}
/26.6447E700/temperature
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {157}
/26.6447E700/vis
CALL: handler.c:SingleHandler(273) sem_timedwait timeout time=0.101
(timeout=100 ms)
DEBUG: handler.c:SingleHandler(317) NOPING handler {156}
/26.6447E700/vis
I would really appreciate some help in this matter.
-Patrik
Den 10 mars 2010 11.49 skrev Patrik Åkerfeldt patrik.akerfe...@gmail.com:
No, wrong conclusion of me. I removed the /temperature polling and let the
vis reading remain but it still hangs.
I will try the latest version of owfs instead.
-Patrik
Den 10 mars 2010 11.46 skrev Patrik Åkerfeldt patrik.akerfe...@gmail.com:
Could it be that I poll the same device (26.6447E700) on different
readings (temperature and vis) at the same time? And that it some how hangs?
Polling is made from bash scripts invoked using crontab at the same
intervall.
-Patrik
Den 9 mars 2010 21.29 skrev Patrik Åkerfeldt patrik.akerfe...@gmail.com:
I've been adding a new device to my 1-wire network that I regularly poll (a
solar sensor + temp from hobby-boards). Since then (I think!), owserver
seems to stop responding after a while. Sometimes it takes 6-10h before it
hangs and sometimes just a couple of minutes.
The last time I started owserver with --error_level=9 and this is the output
when owserver is malfunctioning:
DEBUG: to_client.c:ToClient(63) Send delay message
DEBUG: handler.c:SingleHandler(239) NOPING handler {43}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(229) PING handler {51}
/26.6447E700/temperature
DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0 offset=0
DEBUG: to_client.c:ToClient(63) Send delay message
DEBUG: handler.c:SingleHandler(239) NOPING handler {53}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(239) NOPING handler {55}
/26.6447E700/vis
DEBUG: handler.c:SingleHandler(239) NOPING handler {60}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(239) NOPING handler {59}
/26.6447E700/vis
DEBUG: handler.c:SingleHandler(229) PING handler {57}
/26.6447E700/temperature
DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0 offset=0
DEBUG: to_client.c:ToClient(63) Send delay message
DEBUG: handler.c:SingleHandler(239) NOPING handler {47}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(239) NOPING handler {45}
/26.6447E700/vis
DEBUG: handler.c:SingleHandler(239) NOPING handler {49}
/26.6447E700/vis
DEBUG: handler.c:SingleHandler(239) NOPING handler {43}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(239) NOPING handler {51}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(239) NOPING handler {53}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(239) NOPING handler {55}
/26.6447E700/vis
DEBUG: handler.c:SingleHandler(239) NOPING handler {60}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(239) NOPING handler {59}
/26.6447E700/vis
DEBUG: handler.c:SingleHandler(239) NOPING handler {57}
/26.6447E700/temperature
DEBUG: handler.c:SingleHandler(229) PING handler {47}
/26.6447E700/temperature
DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0 offset=0
I
Re: [Owfs-developers] owfs (owserver) on DNS-323. Will not runin the background.
FYI, Look at this old patch/workaround in asterisk which solved the problem
with daemon() and uClibc.
https://dev.openwrt.org/browser/packages/net/asterisk-1.6.x/patches/200-ucli
bc-daemon.patch?rev=14304
/Christian
-Original Message-
From: Roseen, Göran [mailto:goran.ros...@software-innovation.se]
Sent: den 8 mars 2010 12:54
To: OWFS (One-wire file system) discussion and help
Subject: Re: [Owfs-developers] owfs (owserver) on DNS-323. Will not runin
the background.
Thanks for the tip! I have uClibc 0.9.28, which dates back to 2007, so it
might very well be the problem.
I have tried to build it from recent sources, but ran across i a lot of
minor issues concerning the unusual layout of the device (I do the compiling
ON the device itself). But I'll try some more, or maybe I'll just try the
daemon function in owlib instead. I'll be back later and report what
happens.
Göran Roseen
Från: Christian Magnusson [mailto:m...@mag.cx]
Skickat: sö 2010-03-07 10:21
Till: 'OWFS (One-wire file system) discussion and help'
Ämne: Re: [Owfs-developers] owfs (owserver) on DNS-323. Will not runin the
background.
I guess your uClibc version contain a bug which result into a non-working
daemon() function. (since it call wrong fork() function).
Do you know exactly which UCLIBC version you have? There is a workaround to
define the daemon() function within the owlib, and that might be possible
for you. Otherwise you probably need to patch uClibc and recompile
everything for your NAS.
The old bug in uClibc is caused by a faulty libc_hidden_proto to fork().
+--- uClibc.org/libc/unistd/daemon.c2009-07-14 11:09:20.0 +0200
uClibc/libc/unistd/daemon.c2009-08-06 10:21:57.0 +0200
+@@ -54,7 +54,7 @@
+ libc_hidden_proto(dup2)
+ libc_hidden_proto(setsid)
+ libc_hidden_proto(chdir)
+-libc_hidden_proto(fork)
++/* libc_hidden_proto(fork) */
+
+ int daemon( int nochdir, int noclose )
+ {
/Christian
From: Paul Alfille [mailto:paul.alfi...@gmail.com]
Sent: den 6 mars 2010 22:06
To: OWFS (One-wire file system) discussion and help
Subject: Re: [Owfs-developers] owfs (owserver) on DNS-323. Will not run in
the background.
On Sat, Mar 6, 2010 at 1:18 PM, Roseen, Göran
goran.ros...@software-innovation.se wrote:
Hi all,
I have a DLink DNS-323 Network Attached Storage, and besides storing stuff
on it, it is a perfect little server for things you want to keep running 24
hours. Like the WRT54G, but with a lot more storage.
Any idea what distribution you are using? Especially what C library. It
looks like the handling of glibc and uclibc on matters like fork and daemon
are different.
I downloaded owfs-2.7p28 and ran ./configure and make install, and
hey! It compiled with no errors!
I then tried to run owserver with a test adapter. It started three
threads in the background that I can see with ps ax, but owdir shows
nothing.
Then I tried running owserver in the foreground, and that works
fine! It works nicely with -u and owget gives me the temperature on a
connected sensor.
(I haven't got Fuse, so I don't intend to run owfs. Configure
detected this nicely.)
I see a line of code in owserver.c, saying something about special
treatment of exit() on the wrt54, compiled in with the macro __UCLIBC__.
Perhaps this is needed on the DNS-323 too. I do have uclibc on the machine,
but I am not sure if the library path is set correctly. And I can't see
anything in ./configure or the Makefiles referring to this macro.
The code to go into the background is in modules/owlib/src/c/daemon.c
Does anyone have any ideas on how I can go on debugging? I tried
running with verbose output redirected to a file, but when running in the
background I don't get any output at all.
Are there any messages posted to syslog?
__ Information från ESET NOD32 Antivirus, version av
virussignaturdatabas 4921 (20100306) __
Meddelandet har kontrollerats av ESET NOD32 Antivirus.
http://www.esetscandinavia.com
__ Information från ESET NOD32 Antivirus, version av
virussignaturdatabas 4921 (20100306) __
Meddelandet har kontrollerats av ESET NOD32 Antivirus.
http://www.esetscandinavia.com http://www.esetscandinavia.com/
__ Information från ESET NOD32 Antivirus, version av
virussignaturdatabas 4926 (20100308) __
Meddelandet har kontrollerats av ESET NOD32 Antivirus.
http://www.esetscandinavia.com
__ Information från ESET NOD32 Antivirus, version av
virussignaturdatabas 4926 (20100308) __
Meddelandet har kontrollerats av ESET NOD32 Antivirus.
http://www.esetscandinavia.com
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune
Re: [Owfs-developers] Problems building 2.7p29 on OpenBSD. Was 2.7p26
If getline is not available, you should check the presence with #ifndef HAVE_GETLINE /* getline compat function */ #endif Since in src/include/config.h will look something like this /* #undef HAVE_GETLINE */ #if ! HAVE_GETLINE might fail on some systems since the variable isnt defined. /Christian From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: den 2 mars 2010 02:48 To: OWFS (One-wire file system) discussion and help Subject: Re: [Owfs-developers] Problems building 2.7p29 on OpenBSD. Was 2.7p26 Ok, found an implementation of getline at http://www.koders.com/c/fid7449041983F5893CBF13458C88271146BA685037.aspx?s=p rintf tht seems to do the trick. I'll put it in. Paul On Mon, Mar 1, 2010 at 8:34 PM, Paul Alfille paul.alfi...@gmail.com wrote: Another BSD vs Gnu fight. The gnu getline is far better than using fgets. Perhaps there is a compatible replacement function to use if getline isn't available. __ Information från ESET NOD32 Antivirus, version av virussignaturdatabas 4907 (20100302) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] 2.7p29 for NSLU available ?
I recompiled the latest packages yesterday, but I haven't tried them myself though. http://owfs.sourceforge.net/nslu2/packages/Packages http://owfs.sourceforge.net/nslu2/packages/owfs_2.7p30-1_armeb.ipk http://owfs.sourceforge.net/nslu2/packages/owlib_2.7p30-1_armeb.ipk etc. /Christian -Original Message- From: Eitel Dignatz [mailto:dign...@dignatz.de] Sent: den 1 mars 2010 23:48 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] 2.7p29 for NSLU available ? Hi Thomas, On Montag 01 März 2010, Thomas Süß wrote: is the version 2.7p29 for NSLU available? I've try the update over ipkg, but the current version is p28. I need the p29 version for the BAE device. Can't tell about 2.7p29, but generally speaking, you can build owfs without problems on the SLUG itself when you run Debian/NSLU2 (Lenny). I have done that in the past with owfs-2.7p26 and older versions. Fell free to call me on the phone, if you like. Just make sure your PBX does not suppress your Caller ID or else my Asterisk will play games with you :-) Regards Eitel Dignatz Dignatz Consulting Schleissheimer Strasse 87 D-80797 Muenchen Germany phone +49 (0)89 - 129 59 97 dign...@dignatz.de http://www.dignatz.de -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information från ESET NOD32 Antivirus, version av virussignaturdatabas 4907 (20100302) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com __ Information från ESET NOD32 Antivirus, version av virussignaturdatabas 4910 (20100302) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] BAE docs/man?
Sorry for my laziness, but is there any documentation about all OWFS-files to control the BAE-chip? I could of course try to read the source, but for me it's not obvious what 910/duty1 controls etc... Anyone who can guide me a bit through the files? /Christian ./910 ./910/adc ./910/adcan ./910/adcap ./910/adcc ./910/adctotn ./910/adctotp ./910/alan ./910/alap ./910/alarm ./910/alarmc ./910/alcps ./910/alct ./910/cnt ./910/cntc ./910/count ./910/cps ./910/date ./910/duty1 ./910/duty2 ./910/duty3 ./910/duty4 ./910/maxan ./910/maxap ./910/maxcps ./910/out ./910/outc ./910/ovruncnt ./910/pc0 ./910/pc1 ./910/pc2 ./910/pc3 ./910/period1 ./910/period2 ./910/pio ./910/pioc ./910/resetcnt ./910/rtcc ./910/selectcnt ./910/stalledcnt ./910/tpm1c ./910/tpm2c ./910/udate ./910/usera ./910/userb ./910/userc ./910/userd ./910/usere ./910/userf ./910/userg ./910/userh ./910/useri ./910/userj ./910/userk ./910/userl ./910/userm ./910/usern ./910/usero ./910/userp ./address ./alias ./bootstrap_version ./chip_type ./command ./crc8 ./device_type ./device_version ./eeprom ./eeprom/erase.ALL ./eeprom/erase.0 ./eeprom/erase.1 ./eeprom/memory ./eeprom/page.ALL ./eeprom/page.0 ./eeprom/page.1 ./family ./firmware ./firmware/function ./id ./localtype ./locator ./memory ./present ./r_address ./r_id ./r_locator ./type ./version ./writebyte __ Information fran ESET NOD32 Antivirus, version av virussignaturdatabas 4900 (20100227) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] BAE docs/man?
Ok... That datasheet describes everything needed. /Christian From: Pascal Baerten [mailto:pascal.baer...@gmail.com] Sent: den 27 februari 2010 17:26 To: OWFS (One-wire file system) discussion and help Subject: Re: [Owfs-developers] BAE docs/man? hi Chritian, See the datasheet: http://www.brain4home.eu/attachments/BAE0910%20datasheet.pdf particularly on page 10 you will find the register list with description. just forget about writebyte which was used for testing. Pascal 2010/2/27 Christian Magnusson m...@mag.cx Sorry for my laziness, but is there any documentation about all OWFS-files to control the BAE-chip? I could of course try to read the source, but for me it's not obvious what 910/duty1 controls etc... Anyone who can guide me a bit through the files? /Christian ./910 ./910/adc ./910/adcan ./910/adcap ./910/adcc ./910/adctotn ./910/adctotp ./910/alan ./910/alap ./910/alarm ./910/alarmc ./910/alcps ./910/alct ./910/cnt ./910/cntc ./910/count ./910/cps ./910/date ./910/duty1 ./910/duty2 ./910/duty3 ./910/duty4 ./910/maxan ./910/maxap ./910/maxcps ./910/out ./910/outc ./910/ovruncnt ./910/pc0 ./910/pc1 ./910/pc2 ./910/pc3 ./910/period1 ./910/period2 ./910/pio ./910/pioc ./910/resetcnt ./910/rtcc ./910/selectcnt ./910/stalledcnt ./910/tpm1c ./910/tpm2c ./910/udate ./910/usera ./910/userb ./910/userc ./910/userd ./910/usere ./910/userf ./910/userg ./910/userh ./910/useri ./910/userj ./910/userk ./910/userl ./910/userm ./910/usern ./910/usero ./910/userp ./address ./alias ./bootstrap_version ./chip_type ./command ./crc8 ./device_type ./device_version ./eeprom ./eeprom/erase.ALL ./eeprom/erase.0 ./eeprom/erase.1 ./eeprom/memory ./eeprom/page.ALL ./eeprom/page.0 ./eeprom/page.1 ./family ./firmware ./firmware/function ./id ./localtype ./locator ./memory ./present ./r_address ./r_id ./r_locator ./type ./version ./writebyte __ Information fran ESET NOD32 Antivirus, version av virussignaturdatabas 4900 (20100227) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Pascal www.brain4home.eu __ Information från ESET NOD32 Antivirus, version av virussignaturdatabas 4900 (20100227) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] PIO problem using NSLU2 (Unslung) , HB 8 channel I/O (DS2408) and owfs - 2.7p21-1
I have built new packages for NSLU2. The repository is at: http://owfs.sourceforge.net/nslu2/packages/Packages http://owfs.sourceforge.net/nslu2/packages/owlib_2.7p28-1_armeb.ipk etc.. -rw-r--r-- 1 root root 8578 2010-01-23 08:35 owcapi_2.7p28-1_armeb.ipk -rw-r--r-- 1 root root733 2010-01-23 08:36 owcapi_2.7p28-1_armeb.ipk.content -rw-r--r-- 1 root root 57542 2010-01-23 08:35 owfs_2.7p28-1_armeb.ipk -rw-r--r-- 1 root root 1396 2010-01-23 08:36 owfs_2.7p28-1_armeb.ipk.content -rw-r--r-- 1 root root 221171 2010-01-23 08:35 owlib_2.7p28-1_armeb.ipk -rw-r--r-- 1 root root430 2010-01-23 08:36 owlib_2.7p28-1_armeb.ipk.content -rw-r--r-- 1 root root 10497 2010-01-23 08:35 owshell_2.7p28-1_armeb.ipk -rw-r--r-- 1 root root428 2010-01-23 08:36 owshell_2.7p28-1_armeb.ipk.content /Christian -Original Message- From: Eduard Freeman [mailto:dra...@gmail.com] Sent: den 22 januari 2010 15:11 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] PIO problem using NSLU2 (Unslung) , HB 8 channel I/O (DS2408) and owfs - 2.7p21-1 Paul, the current version works on the desktop but the version on the NSLU2 doesn't. A newer version sounds great, when will this be available for the NSLU2? Eduard Freeman -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information från ESET NOD32 Antivirus, version av virussignaturdatabas 4798 (20100122) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com __ Information från ESET NOD32 Antivirus, version av virussignaturdatabas 4798 (20100122) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] any succes with building latest owfs on latest openbsd ?
There was a new introduced typo on owshell/src/c/getaddrinfo.c which caused an open c-comment and a compilation problem. http://owfs.cvs.sourceforge.net/viewvc/owfs/owfs/module/owshell/src/c/getadd rinfo.c?r1=1.9 http://owfs.cvs.sourceforge.net/viewvc/owfs/owfs/module/owshell/src/c/getad drinfo.c?r1=1.9r2=1.10 r2=1.10 I also moved the resolv.h include after sys/types.h which seems to be needed. Can you try again? /Christian From: Mads Hjorth [mailto:ma...@mac.com] Sent: den 19 oktober 2009 11:05 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] any succes with building latest owfs on latest openbsd ? I switched to autoconf 2.62 ... And get the error if gcc -DHAVE_CONFIG_H -I. -I. -I../../../../src/include -I../include -I../../../owlib/src/include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -DNO_NESTED_FUNCTIONS -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT getaddrinfo.o -MD -MP -MF .deps/getaddrinfo.Tpo -c -o getaddrinfo.o getaddrinfo.c; then mv -f .deps/getaddrinfo.Tpo .deps/getaddrinfo.Po; else rm -f .deps/getaddrinfo.Tpo; exit 1; fi getaddrinfo.c:82:37: missing terminating ' character *** Error code 1 during config I noticed checking resolv.h usability... no checking resolv.h presence... yes configure: WARNING: resolv.h: present but cannot be compiled configure: WARNING: resolv.h: check for missing prerequisite headers? configure: WARNING: resolv.h: see the Autoconf documentation configure: WARNING: resolv.h: section Present But Cannot Be Compiled configure: WARNING: resolv.h: proceeding with the preprocessor's result configure: WARNING: resolv.h: in the future, the compiler will take precedence checking for resolv.h... yes my /home/download/owfs/module/owlib/src/c/getaddrinfo.c is last modified on Oct 17 23:24 Any ideas? On Monday, October 19, 2009, at 04:08AM, Paul Alfille paul.alfi...@gmail.com wrote: --- --- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers I am using a vmware virtual machine with openbsd 4.5 automake 1.9 and autoconf 2.62. Paul On Sun, Oct 18, 2009 at 4:44 PM, Mads Hjorth ma...@mac.com wrote: Thanks for looking at this. I don't know how many are using openbsd for 1-wire stuff. Not enough for it to be put into a port or packages yet. But maybe we could get this to work and get it into a openbsd package... Could you please confirm that we are using similar bootstrap/build environment I am on AUTOMAKE_VERSION=1.9 and AUTOCONF_VERSION=2.59... What are you using? I also spot a difference regarding use of pthreads. I am building on a Soekris-box that was setup originally as Qemu virtual i386 machine. I don't know if that would make a difference. Mads On Oct 18, 2009, at 19:30 , Paul Alfille wrote: That's strange. Under (I presume) the same conditions: if /bin/sh ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../../src/include -I../include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -I/usr/local/include -g -O2 -DNO_NESTED_FUNCTIONS -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT getaddrinfo.lo -MD -MP -MF .deps/getaddrinfo.Tpo -c -o getaddrinfo.lo getaddrinfo.c; then mv -f .deps/getaddrinfo.Tpo .deps/getaddrinfo.Plo; else rm -f .deps/getaddrinfo.Tpo; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I../../../../src/include -I../include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -I/usr/local/include -g -O2 -DNO_NESTED_FUNCTIONS -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT getaddrinfo.lo -MD -MP -MF .deps/getaddrinfo.Tpo -c getaddrinfo.c -fPIC -DPIC -o .libs/getaddrinfo.o ... i.e. No errors. I notice that the Actual command is different. Basically I compiled everything successfully, then touched
Re: [Owfs-developers] any succes with building latest owfs on latest openbsd ?
BTW: I just downloaded OpenBSD 4.6, installed it under VMware, and successfully compiled everything auto-detected from the configure-script. Hopefully it works with OpenBSD 4.5 as well. Starting owserver -fake=10, and owget works. I haven't tried any real adapter though. /Christian From: Christian Magnusson [mailto:m...@mag.cx] Sent: den 19 oktober 2009 14:14 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] any succes with building latest owfs on latest openbsd ? There was a new introduced typo on owshell/src/c/getaddrinfo.c which caused an open c-comment and a compilation problem. http://owfs.cvs.sourceforge.net/viewvc/owfs/owfs/module/owshell/src/c/getadd rinfo.c?r1=1.9 http://owfs.cvs.sourceforge.net/viewvc/owfs/owfs/module/owshell/src/c/getad drinfo.c?r1=1.9r2=1.10 r2=1.10 I also moved the resolv.h include after sys/types.h which seems to be needed. Can you try again? /Christian From: Mads Hjorth [mailto:ma...@mac.com] Sent: den 19 oktober 2009 11:05 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] any succes with building latest owfs on latest openbsd ? I switched to autoconf 2.62 ... And get the error if gcc -DHAVE_CONFIG_H -I. -I. -I../../../../src/include -I../include -I../../../owlib/src/include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -g -O2 -DNO_NESTED_FUNCTIONS -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT getaddrinfo.o -MD -MP -MF .deps/getaddrinfo.Tpo -c -o getaddrinfo.o getaddrinfo.c; then mv -f .deps/getaddrinfo.Tpo .deps/getaddrinfo.Po; else rm -f .deps/getaddrinfo.Tpo; exit 1; fi getaddrinfo.c:82:37: missing terminating ' character *** Error code 1 during config I noticed checking resolv.h usability... no checking resolv.h presence... yes configure: WARNING: resolv.h: present but cannot be compiled configure: WARNING: resolv.h: check for missing prerequisite headers? configure: WARNING: resolv.h: see the Autoconf documentation configure: WARNING: resolv.h: section Present But Cannot Be Compiled configure: WARNING: resolv.h: proceeding with the preprocessor's result configure: WARNING: resolv.h: in the future, the compiler will take precedence checking for resolv.h... yes my /home/download/owfs/module/owlib/src/c/getaddrinfo.c is last modified on Oct 17 23:24 Any ideas? -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Improved network performance
I made a fix to owserver, where some code was limiting 1 request per 200ms! when persistent connections were used. (Eg. Owserver-owserver or Owfs -owserver configurations) I added a timed semaphore which should fix the unnecessary delay between two requests within the same persistant connection. /Christian -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Improved network performance
Here is some comparison between the performance before and after the latest changes. # /opt/owfs/bin/owserver --foreground --error_level=3 --fake=10 -p 5000 # /opt/owfs/bin/owfs --foreground --error_level=3 -s 5000 /tmp/2 Old code. It takes 2.37 seconds to read 6 fake devices! # time cat 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 91.3027 81.9695 35.9095 55.2485 57.943 45.2576 real0m 2.37s user0m 0.02s sys 0m 0.00s After introducing the semaphore to improve the speed.. It takes 0.04 seconds to read 6 fake devices! # time cat 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 10.67C6697351FF/temperature 77.5767 28.8379 32.9642 18.9751 98.43630.357857 real0m0.004s user0m0.000s sys 0m0.004s /Christian From: Christian Magnusson [mailto:m...@mag.cx] Sent: den 3 oktober 2009 09:42 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Improved network performance I made a fix to owserver, where some code was limiting 1 request per 200ms! when persistent connections were used. (Eg. Owserver-owserver or Owfs -owserver configurations) I added a timed semaphore which should fix the unnecessary delay between two requests within the same persistant connection. /Christian -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] [Fwd: OWFS/owfs.spec]
I have looked a bit on it... and adding mandriva version-suffixes is perhaps
not what we want.
%mkrel is not available in older releases either.
Look at http://wiki.mandriva.com/en/Policies/Release_Tag
There are some notes that mkrel could be defined manually if it doesn't
exists
# define the mkrel macro if it is not already defined
%{?!mkrel:%define mkrel(c:) %{-c:0.%{-c''}.}%{!?''with''unstable:%(perl -e
'$''=%{1};m/(.\''')(\\d+)$/;$rel=${2}-1;re;print $1$rel;').\
%{?subrel:%subrel}%{!?subrel:1}.%{?distversion:%distversion}%{?!distversion:
%(echo $[%{mdkversion}/10])}}%{?''with_unstable:\
%{1}}%{?distsuffix:%distsuffix}%{?!distsuffix:mdk}}
%define rel 6
Release: %mkrel %rel
But this define doesn't work on my older build-servers... Don't know what
to do really...
I'll continue to look at it a bit and see if I can merge some of the changes
without breaking anything else.
/Christian
-Original Message-
From: Serg Oskin [mailto:s...@oskin.ru]
Sent: den 8 juli 2009 16:14
To: owfs-developers@lists.sourceforge.net
Subject: [Owfs-developers] [Fwd: OWFS/owfs.spec]
Sorry, at this moment I am leaving for vacation. :)
Serg.
--8-
Date: Wed, 8 Jul 2009 15:16:56 +0200
Message-ID: 330b51fc0907080616j180ffb62h32d39ca9ed847...@mail.gmail.com
Subject: OWFS/owfs.spec
From: Rafał Prasał rafal.pra...@gmail.com
To: s...@oskin.ru
Hello
I've managed to build OWFS package for Mandriva Cooker(unstable
version of Mandriva Linux Distro). Maybe You will find it helpfull for
owfs.spec improvement.
Apriopriate Patch you may find here
http://piorun.ds.pg.gda.pl/~rav/RPM/OWFS/owfs.spec.patch
Main Differences
* packager ;]
* man pages ara in lzma not gz
* static libraries were not built so I've removed them
* many distros use `%mkrel release`
ow-perl:
* requires perl
* buildrequires perl-devel
* removed from packagement %{perl_sitearch}/auto/OW/OW.bs
ow-php
* requires php-cli
* buildrequires php-cli
--
Pozdrawiam, Rafał Prasał
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] LinkUSB
I have successfully used the kernel-module ftdi_sio on foxboards which supports usb-serial chips. It's easy to compile and include into the firmware. I haven't tried LinkUSB myself, but it should be possible to use as I see it. Only start owserver -d /dev/ttyUSB0 and it will open the serial port in 9600 baud which should be correct. If other speed is preferred, then we need to patch the serial-port startup-code. /Christian -Original Message- From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: den 8 juli 2009 19:15 To: William C. Farmer Cc: i...@ibuttonlink.com; Jonathan Starke; owfs-developers Subject: Re: [Owfs-developers] LinkUSB As I recall, the FoxBoard is an embedded computer (Axis etrax cpu) from an Italian company (http://foxlx.acmesystems.it/?id=5) that runs linux. It looks like several build systems are available, many based on fairly modern kernels. uClibc, openmwrt, are all supported by owfs, and specifically, there are instructions on loading owfs on the FoxBoard (http://foxlx.acmesystems.it/?id=29). The LinkUSB is a serial LINK combined with a serial/usb adapter. To owfs (and linux in general) there should be a kernel module that supports that serial/USB adapter and presents the port as /dev/ttyUSBn (see the dmesg output for the specific port details). OWFS will treat the LinkUSB as a normal LINK, but use the ttyUSBn port as the serial port. OWFS can treat the LINK as either a simulated DS2480B-based adapter) or use the native ascii interface. The ascii interface should be more forgiving of poor serial/USB support. Now does linux, and specifically the foxboard distributions, support this serial/USB chip? I don't know. I don't have a Link/USB to test and haven't heard reports on it's function under linux. Paul Alfille On Wed, Jul 8, 2009 at 10:34 AM, William C. Farmerbfar...@wcfa.com wrote: Ask the OWFS guys. Paul is pretty responsive. I dont even know what a Foxboard is. Bill Farmer From: Jonathan Starke [mailto:jonat...@entry.co.za] Sent: Wednesday, July 08, 2009 5:49 AM To: i...@ibuttonlink.com Subject: LinkUSB Hi Info, Do you know when you will LinkUSB 1-Wire interfaces in stock again? I would like to order one of these. Do you know if the LinkUSB device is compatible with owfs on the Foxboard? Thnx Jonathan -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Two owserver problems
I added a simple semaphore to limit number of concurrent connections to 10 + 10 queued connection due to listen(). It may need some tuning or possibility to change with some command-line parameters perhaps. A read-timeout could perhaps also be added to avoid users to do multiple telnet owserver 4304 and only lock the slots without using them. If there are no command-bytes read for 1 second after the accept() or something similar, it would be best for owserver to automatically close the connection and free it for other users. This will protect owserver from being flooded with too many requests. Is this ok for you all? /Christian -Original Message- From: Christian Magnusson [mailto:m...@mag.cx] Sent: den 10 juni 2009 19:36 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Two owserver problems Right now we seldom have more than 1 connecting request in the listen-queue at a time... mostly since the code _very_ quickly accepts all connections and removes them from the queue. I'm sure nobody would notice any difference if the listen-queue was lowered from 10 to 1 in the current source. Adding that semaphore which limits the total number of concurrent connections + allowing 10 in queue, would fix most problems I guess. /Christian -Original Message- From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: den 10 juni 2009 12:50 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Two owserver problems On Wed, Jun 10, 2009 at 2:37 AM, Christian Magnussonm...@mag.cx wrote: Listen() in ow_net_server.c handles #1 automatically, more or less... It's set to handle 10 requests today, and according to the man-pages you see this: If a connection request arrives when the queue is full, the client may receive an error with an indication of ECONNREFUSED or, if the underlying protocol supports retransmission, the request may be ignored so that a later reattempt at connection succeeds. Now that you mention it, this does sound familiar. Perhaps I'm misinterpreting my test results. Back to the analysis... Paul -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Two owserver problems
Oops, I forgot there are already exists a timeout for 10 seconds while reading from the network interfaces. So that will automatically free up the semaphore if flooded with unused connections. So, what is a suitable limitation when reading from a remoteserver? Should it be allowed to do 10, 20 or 50 concurrent requests? As I can see, something must be really wrong if it increase over 20 concurrent requests for one single 1-wire adapter. /Christian -Original Message- From: Christian Magnusson [mailto:m...@mag.cx] Sent: den 6 juli 2009 11:29 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Two owserver problems I added a simple semaphore to limit number of concurrent connections to 10 + 10 queued connection due to listen(). It may need some tuning or possibility to change with some command-line parameters perhaps. A read-timeout could perhaps also be added to avoid users to do multiple telnet owserver 4304 and only lock the slots without using them. If there are no command-bytes read for 1 second after the accept() or something similar, it would be best for owserver to automatically close the connection and free it for other users. This will protect owserver from being flooded with too many requests. Is this ok for you all? /Christian -Original Message- From: Christian Magnusson [mailto:m...@mag.cx] Sent: den 10 juni 2009 19:36 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Two owserver problems Right now we seldom have more than 1 connecting request in the listen-queue at a time... mostly since the code _very_ quickly accepts all connections and removes them from the queue. I'm sure nobody would notice any difference if the listen-queue was lowered from 10 to 1 in the current source. Adding that semaphore which limits the total number of concurrent connections + allowing 10 in queue, would fix most problems I guess. /Christian -Original Message- From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: den 10 juni 2009 12:50 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Two owserver problems On Wed, Jun 10, 2009 at 2:37 AM, Christian Magnussonm...@mag.cx wrote: Listen() in ow_net_server.c handles #1 automatically, more or less... It's set to handle 10 requests today, and according to the man-pages you see this: If a connection request arrives when the queue is full, the client may receive an error with an indication of ECONNREFUSED or, if the underlying protocol supports retransmission, the request may be ignored so that a later reattempt at connection succeeds. Now that you mention it, this does sound familiar. Perhaps I'm misinterpreting my test results. Back to the analysis... Paul -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Two owserver problems
Trying to do something like this will not crash owserver anymore... #!/bin/bash while [ 1 ]; do /opt/owfs/bin/owget /uncached/10.01/temperature sleep 0.1 done The conversion will take about 1 second, but the script tries to restart a new conversion after 0.1 seconds... This will of course not start until the first conversion is done due to all other existing bus- and device-locks. This means that there will be many started owget processes, but they will never be able to hang owserver. After a while you will only receive an error from owget which says something like: ServerRead: Error receiving data on /uncached/FF.0001/temperature /Christian -Original Message- From: Steinar Midtskogen [mailto:stei...@latinitas.org] Sent: den 6 juli 2009 15:24 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Two owserver problems [Christian Magnusson] So, what is a suitable limitation when reading from a remoteserver? Should it be allowed to do 10, 20 or 50 concurrent requests? As I can see, something must be really wrong if it increase over 20 concurrent requests for one single 1-wire adapter. 10 or 20 is probably fine, and 50 sounds too much unless someone can give a realistic scenario which could require that. I guess, 50+ devices on one 1-wire adapter is realistic, and a lazy programmer (like me) could write a program that queries all of them simultaniously once in a while leaving the queueing to owserver. But I think it's ok if many of the queries then fail. The most important thing is to make owserver less likely to crash. Currently, I can make owserver crash very easily. I can retest with your changes to see if it helps. -- Steinar -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Install of owfs 2.7p22
You are installing the new binaries in /opt/owfs/bin/ But you probably have some old installation in /usr/bin/ or /usr/local/bin/. Try which to see which binary you have in your path. # which owhttpd And also try to specify the full path. # /opt/owfs/bin/owhttpd -V Try find out which libraries are used when loading the application: # ldd /opt/owfs/bin/owhttpd # ldd /usr/bin/owhttpd # ldd /usr/local/bin/owhttpd Remove the old installation to make sure you only use the latest version. /Christian -Original Message- From: William Brown [mailto:mahi...@earthlink.net] Sent: den 3 juli 2009 03:57 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Install of owfs 2.7p22 Today I tried to compile and link owfs 2.7p22, restart computer. Everthing seemed to be ok, libow and owfs bin programs had today's date, owfs lib links all point to version 22, but when I did owhttpd -V it shows owfs 2.7p14. I have 3 versions in owfs lib 14, 21, 22. owhttpd -V owhttpd version: 2.7p14 libow version: 2.7p14 Any idea what I did wrong? make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/home/wgb/owfs-2.7p22/module/owhttpd' make[3]: Leaving directory `/home/wgb/owfs-2.7p22/module/owhttpd' make[2]: Leaving directory `/home/wgb/owfs-2.7p22/module/owhttpd' Making install in owserver make[2]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver' make[3]: Entering directory `/home/wgb/owfs-2.7p22' make[3]: Leaving directory `/home/wgb/owfs-2.7p22' Making install in src make[3]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver/src' make[4]: Entering directory `/home/wgb/owfs-2.7p22' make[4]: Leaving directory `/home/wgb/owfs-2.7p22' Making install in include make[4]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver/src/include' make[5]: Entering directory `/home/wgb/owfs-2.7p22' make[5]: Leaving directory `/home/wgb/owfs-2.7p22' make[5]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver/src/include' make[6]: Entering directory `/home/wgb/owfs-2.7p22' make[6]: Leaving directory `/home/wgb/owfs-2.7p22' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver/src/include' make[4]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver/src/include' Making install in c make[4]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver/src/c' make[5]: Entering directory `/home/wgb/owfs-2.7p22' make[5]: Leaving directory `/home/wgb/owfs-2.7p22' make[5]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver/src/c' make[6]: Entering directory `/home/wgb/owfs-2.7p22' make[6]: Leaving directory `/home/wgb/owfs-2.7p22' test -z /opt/owfs/bin || mkdir -p -- /opt/owfs/bin /bin/bash ../../../../libtool --mode=install /usr/bin/install -c 'owserver' '/opt/owfs/bin/owserver' /usr/bin/install -c .libs/owserver /opt/owfs/bin/owserver make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver/src/c' make[4]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver/src/c' make[4]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver/src' make[5]: Entering directory `/home/wgb/owfs-2.7p22' make[5]: Leaving directory `/home/wgb/owfs-2.7p22' make[5]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver/src' make[6]: Entering directory `/home/wgb/owfs-2.7p22' make[6]: Leaving directory `/home/wgb/owfs-2.7p22' make[5]: Nothing to be done for `install-exec-am'. make[5]: Nothing to be done for `install-data-am'. make[5]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver/src' make[4]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver/src' make[3]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver/src' make[3]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver' make[4]: Entering directory `/home/wgb/owfs-2.7p22' make[4]: Leaving directory `/home/wgb/owfs-2.7p22' make[4]: Entering directory `/home/wgb/owfs-2.7p22/module/owserver' make[5]: Entering directory `/home/wgb/owfs-2.7p22' make[5]: Leaving directory `/home/wgb/owfs-2.7p22' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver' make[3]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver' make[2]: Leaving directory `/home/wgb/owfs-2.7p22/module/owserver' Making install in owfs make[2]: Entering directory `/home/wgb/owfs-2.7p22/module/owfs' make[3]: Entering directory `/home/wgb/owfs-2.7p22' make[3]: Leaving directory `/home/wgb/owfs-2.7p22' Making install in src make[3]: Entering directory `/home/wgb/owfs-2.7p22/module/owfs/src' make[4]: Entering directory `/home/wgb/owfs-2.7p22' make[4]: Leaving directory `/home/wgb/owfs-2.7p22' Making install in c make[4]: Entering directory `/home/wgb/owfs-2.7p22/module/owfs/src/c'
[Owfs-developers] minor cache-bug
I noticed that there is probably some minor bug in the cache-timeout... I
did some tests with adding a test-device which worked as a clock.
The device had files like second, minute, hour, hhmmss, mmdd etc.
All timeout values were set to fc_second, which should cache the values for
one second.
The time-data were fetched with:
time_t t = time(NULL);
struct tm *tm = localtime(t);
and then I returned tm-tm_sec when reading the file
F1./second
The problem was that reading the second-file inside a loop, I only got
even or odd seconds, eg. It was cached 2 seconds instead of 1.
Changing a compare-operator in ow_cache.c fixed the problem, and I can't see
any other side effects.
In ow_cache.c:Cache_Get_Common()
- if (duration[0] = 0) {
+ if (duration[0] 0) { // should probably be , since
fc_second cache for 2 seconds...
/Christian
--
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Two owserver problems
Right now we seldom have more than 1 connecting request in the listen-queue at a time... mostly since the code _very_ quickly accepts all connections and removes them from the queue. I'm sure nobody would notice any difference if the listen-queue was lowered from 10 to 1 in the current source. Adding that semaphore which limits the total number of concurrent connections + allowing 10 in queue, would fix most problems I guess. /Christian -Original Message- From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: den 10 juni 2009 12:50 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Two owserver problems On Wed, Jun 10, 2009 at 2:37 AM, Christian Magnussonm...@mag.cx wrote: Listen() in ow_net_server.c handles #1 automatically, more or less... It's set to handle 10 requests today, and according to the man-pages you see this: If a connection request arrives when the queue is full, the client may receive an error with an indication of ECONNREFUSED or, if the underlying protocol supports retransmission, the request may be ignored so that a later reattempt at connection succeeds. Now that you mention it, this does sound familiar. Perhaps I'm misinterpreting my test results. Back to the analysis... Paul -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Bug report?
I've noticed that the best solution seems to be to use libtoolize to install the correct libtool. cvs co owfs cd owfs libtoolize -c -f -i # (copy force install flags) ./bootstrap ; ./configure ; make all install -Original Message- From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: den 30 maj 2009 00:11 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Bug report? Yes, I've has the same problem with the hateful libtool. If ever an example of awkward design and unmaintainable code... Anyways, Christian Magnusson came to my rescue: - I have seen this on Ubuntu 8.10 as well... Copy your local libtool to the installation directory and bootstrap again. cp /usr/bin/libtool src/scripts/install/ltmain.sh ./bootstrap ; ./configure ; make -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS forgets chips after a while.
I haven't follows all latest updates, but I found one pointer bug in
ow_presence.c:ReCheckPresence()
CheckThisConnection() should not have an integer as in input-argument, it
should be a connection_in pointer.
I haven't checked in the fix, but this might fix the problem. Perhaps Paul can
verify if this is how it was supposed to work.
/Christian
RCS file: /cvsroot/owfs/owfs/module/owlib/src/c/ow_presence.c,v
retrieving revision 1.29
diff -u -r1.29 ow_presence.c
--- ow_presence.c 23 May 2009 19:25:54 - 1.29
+++ ow_presence.c 24 May 2009 12:33:52 -
@@ -95,7 +95,8 @@
int ReCheckPresence(struct parsedname *pn)
{
int bus_nr;
-
+ struct connection_in *in;
+
if (NotRealDir(pn)) {
return 0;
}
@@ -106,14 +107,16 @@
}
if (KnownBus(pn)) {
- if ( CheckThisConnection(pn-known_bus-index,pn) = 0 ) {
+ in = find_connection_in(pn-known_bus-index);
+ if ( CheckThisConnection(in,pn) = 0 ) {
return pn-known_bus-index ;
}
}
if (Cache_Get_Device(bus_nr, pn) == 0) {
+ in = find_connection_in(bus_nr);
LEVEL_DEBUG(Found device on bus %d\n,bus_nr);
- if ( CheckThisConnection(bus_nr,pn) = 0 ) {
+ if ( CheckThisConnection(in, pn) = 0 ) {
SetKnownBus(bus_nr, pn);
return bus_nr ;
}
-Original Message-
From: Jan Kandziora [mailto:j...@gmx.de]
Sent: den 24 maj 2009 12:47
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS forgets
chips after a while.
Am Samstag, 23. Mai 2009 schrieb Paul Alfille:
Jan, can you try again? I've cleaned up the handling of device
presence, I think any read/write error was causing problems. Still, I
don't have your setup to test.
Now I get a segmentation fault in the client application after 10 minutes.
Please see the new owserver log (10 times ok, one time fail).
Kind regards
Jan
--
Linux, Playboy Edition: nichts als die nackte Kommandozeile...
--
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing,
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, Big Spaceship. http://www.creativitycat.com
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS forgets chips after a while.
I made two minor updates to the CVS... There was some debug-code in OW_power() which always returned 1, and that doesn't work for unpowered 1-wire buses. Also one compilation was fixed when --disable-cache was used. /Christian From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: den 18 maj 2009 13:05 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS forgets chips after a while. I really appreciate the time and effort you spend testing and filing bug reports! Paul On Mon, May 18, 2009 at 2:26 AM, Jan Kandziora j...@gmx.de wrote: Am Montag, 18. Mai 2009 schrieb Paul Alfille: Jan, I'm still analyzing your logs. I did find a bug in the simultaneous/single code, and fixed it in the CVS. Can you try a quick test of the newest code to see if the problem persists? The problem is still there. Please see the new log (10 times ok, last time failed). Kind regards Jan -- beta test, v: To voluntarily entrust one's data, one's livelihood and one's sanity to hardware or software intended to destroy all three. In earlier days, virgins were often selected to beta test volcanos. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] New problem introduced
Some new problems were recently introduced when listing directories with owdir and owfs when multiple owservers are started. Paul, Do you have any quick ideas where to fix it? /Christian # /opt/owfs/bin/owserver -p 4305 --fake=10 # /opt/owfs/bin/owserver -p 4304 -s 4305 # /opt/owfs/bin/owfs -s 4304 /mnt/1wire # /opt/owfs/bin/owdir -s 4304# This looks almost correct /10.67C6697351FF /bus.0 /settings /system /statistics /structure (shouldn't /simultaneous be listed in this root-directory as well?) # /opt/owfs/bin/owdir -s 4304 bus.0 # This directory listing is wrong (duplicate /bus.0 parts and /interface as well) bus.0/interface /bus.0/bus.0/interface /bus.0/bus.0/10.67C6697351FF /bus.0/bus.0/simultaneous /bus.0/bus.0/alarm # ls -l /mnt/1wire/ total 0 drwxrwxrwx 1 root root 8 2009-04-21 16:30 10.67C6697351FF drwxr-xr-x 1 root root 8 2009-04-21 16:26 bus.0 drwxr-xr-x 1 root root 8 2009-04-21 16:26 settings drwxr-xr-x 1 root root 8 2009-04-21 16:26 statistics drwxr-xr-x 1 root root 30 2009-04-21 16:26 structure drwxr-xr-x 1 root root 8 2009-04-21 16:26 system (shouldn't /simultaneous be listed in this root-directory as well?) -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS on Ubuntu 8.04 adn 8.10
Just some notice about the needed packages to compile all packages under Ubuntu 8.10. libusb++-dev is not needed. You need the /usr/bin/php binary as well. sudo apt-get install php5-cli Every packages on the same row will be... sudo apt-get install cvs autoconf automake libtool libfuse-dev libusb-dev swig php5 php5-dev php5-cli python-dev libperl-dev tcl-dev cvs -d:pserver:anonym...@owfs.cvs.sourceforge.net:/cvsroot/owfs login # (no password) cvs -d:pserver:anonym...@owfs.cvs.sourceforge.net:/cvsroot/owfs co owfs cd owfs # If libtool fails during the compilation, you need to overwrite src/scripts/install/ltmain.sh with your own local libtool. cp /usr/bin/libtool src/scripts/install/ltmain.sh ./bootstrap ./configure make all install /Christian -Original Message- From: William Brown [mailto:mahi...@earthlink.net] Sent: Tuesday, February 24, 2009 7:14 AM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] OWFS on Ubuntu 8.04 adn 8.10 The old how to guides work just fine. All that needs to be fixed is the version of libtool for Ubuntu 8.10. I'm inclined not to muddy the waters. This guide of Pauls' works for Ubuntu 8.10 Here's the steps for OWFS. Basic ubuntu install and added lots of fluff. Then for OWFS --- sudo apt-get install cvs sudo apt-get install autoconf sudo apt-get install automake sudo apt-get install libtool # For filesystem (FUSE) sudo apt-get install libfuse-dev # For USB support sudo apt-get install libusb-dev sudo apt-get install libusb++-dev # For languages sudo apt-get install swig sudo apt-get install php5 sudo apt-get install php5-dev sudo apt-get install python-dev sudo apt-get install libperl-dev sudo apt-get install tcl-dev cvs -d:pserver:anonym...@owfs.cvs.sourceforge.net:/cvsroot/owfs login # (no password) cvs -d:pserver:anonym...@owfs.cvs.sourceforge.net:/cvsroot/owfs co owfs cd owfs ./bootstrap ./configure make sudo make install Paul Alfille wrote: Daniel Klaussen has been working on an Ubuntu guide for OWFS (along with SAMBA hints) at: http://sites.google.com/a/klaussen.com/owfs/ He would like feedback. On Mon, Feb 16, 2009 at 5:25 PM, William Brown mahi...@earthlink.net mailto:mahi...@earthlink.net wrote: Glad I could help. Matthias Urlichs wrote: Hi, William Brown: Eureka, problem solved. It was libtool. Owfs generates a libtool that is incompatible for Ubuntu 8.10. I noticed a different in the size of the libtools(209.2KB vs 269KB). I deleted the generated version and linked to /usr/bin/libtool and everthing compiled/linked, including swig. Back in busines with OWFS 2.7p14. Mmh, thanks for the info, I'll fix the libtool stuff in the next version of the package. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net mailto:Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information from ESET NOD32 Antivirus, version of virus signature database 3883 (20090224)
Re: [Owfs-developers] Interesting Device
The SheevaPlug development kit is available now for $100. But how much is it for one extra unit? Does anyone know? It feels a bit limited to only have 1USB port and 1 network interface on the device, but sure. It wouldn't be any problem to use it for owfs and an USB-adapter, drawing some graphs with temploggerd or something similar. /Christian From: Paul Alfille [mailto:paul.alfi...@gmail.com] Sent: Wednesday, February 25, 2009 10:00 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Interesting Device I don't know of any ports, yet, but it looks very enticing. There is a writeup on Linux Devices as well.: http://www.linuxdevices.com/news/NS9634061300.html Sounds like the processor is ARM-based (88F6281) which OWFS has been ported to in the past. The RAM (512M) is more than enough. It looks like there is both USB and (with some fiddling) serial ports, as well as some GPIO pins and a spare serial line for the hardware inclined. If there is interest, we could access the GPIO pins with w1 or write support directly. Most impressively, there is complete documentation freely available, as well as instructions for linux installation and cross compiling. Paul Alfille On Wed, Feb 25, 2009 at 3:12 PM, Donald J. Organ IV dor...@donaldorgan.com wrote: Does anyone know if OWFS will work on this device?? http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheev aplug.jsp -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information from ESET NOD32 Antivirus, version of virus signature database 3889 (20090225) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Interesting Device
You have always Asus WL-500W which has 2 USB ports, WLAN 802.11n, and 4 LAN ports. I built my own firmware for this at: http://home.mag.cx/openwrt/kamikaze-svn-asus/ In my case I have one 8Gb memory stick and the TV-decoder connected via the USB ports. (Uploading 14 days of EPG channel information) I have tried a DS9490 1-wire adapter and OWFS on it, and that works good as well. /Christian -Original Message- From: Mark Cheeseman [mailto:m...@cheeseman.org] Sent: Thursday, February 26, 2009 5:29 AM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Interesting Device Gregg C Levine wrote: Or even as a replacement for the NSLU2 from LinkSys.. Speaking of replacements, has anyone found a replacement for the ASUS WL-HDD? It's been discontinued, and I haven't found anything similar that can run OpenWRT (and of course owfs) that has WLAN, LAN and USB ports (I don't need the IDE for my application). Anything similar that I can see on the OpenWRT hardware page is also discontinued. -Mark -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information from ESET NOD32 Antivirus, version of virus signature database 3890 (20090226) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3890 (20090226) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] segfault in 2.7p14 owfs, owserver
There is certainly a bug here... DirblobInit((in-connin.usb.alarm)) and usb.main is never called!?! (or set to NULL at least) But in ow_w1.c we can see: /* Initialize dir-at-once structures */ DirblobInit((in-connin.w1.main)); DirblobInit((in-connin.w1.alarm)); I guess this should be fixed... Paul, could you add it? /Christian -Original Message- From: Martin [mailto:mar...@pr41.sk] Sent: Wednesday, February 18, 2009 8:46 AM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] segfault in 2.7p14 owfs, owserver The easiest solution is to add --nozero to the command line. Confirmed, it solves the crash at start-up. If you can figure out your avahi version, I can do some testing and produce a definitive fix. It is avahi-0.6.21. I do not use avahi, no avahi daemon is running. Also I will have to upgrade soon, because Fedora 8 reached end of life status (no updates) recently on January. === However it seems like there are two unrelated problems. There is still a crash on exit: # ./owserver --nozero --foreground --error_level=9 -u -p 5500 ... start-up DEBUG: Output device 0 setup done. ... normal work ... ctrl-C DEBUG: ServerProcess: break signo=2 DEBUG: ow_net_server.c:ServerProcess() shutdown initiated DEBUG: Shutting down 0 of 1 thread 1108834640 DEBUG: exit_handler: for signo=15, errno 0, code -6, pid=12375, self=1108834640 main=140650822334192 DEBUG: exit_handler: shutdown already in progress. signo=15, self=1108834640, main=140650822334192 DEBUG: ServerProcessAccept shutdown_in_progress 5500 [1108834640] accept 0 DEBUG: ServerProcessAcceptUnlock: unlock 1108834640 DEBUG: ServerProcessAcceptUnlock: unlock 1108834640 done DEBUG: ServerProcessAccept 5500[1108834640] unlock 0 DEBUG: ServerProcessAccept 5500[1108834640] shutdown_in_progress 0 return DEBUG: ServerProcessOut = 1108834640 CLOSING (5500) DEBUG: Server out: Normal exit. DEBUG: pthread_kill (0 of 1) tid=1108834640 signo=15 rc=0 [Success] DEBUG: ow_net_server.c:ServerProcess() all threads cancelled DEBUG: ow_net_server.c: join 1108834640 DEBUG: ow_net_server.c: join 1108834640 done DEBUG: ow_net_server.c:ServerProcess() shutdown done DEBUG: ServerProcess done DEBUG: ow_exit 0 CALL: Starting Library cleanup CALL: Clear Cache CALL: Closing input devices /bin/bash: line 1: 12375 Segmentation fault (core dumped) ./owserver --nozero --foreground --error_level=9 -u -p 5500 and the backtrace: #0 0x00383a675edb in free () from /lib64/libc.so.6 #1 0x003b16642822 in DirblobClear (db=0x1a2f7f0) at ow_dirblob.c:73 #2 0x003b16640471 in FreeIn (now=0x1a2f500) at ow_connect.c:193 #3 0x003b16640673 in FreeInAll () at ow_connect.c:261 #4 0x003b1664d984 in LibStop () at ow_lib_stop.c:28 #5 0x003b1664d78b in LibClose () at ow_lib_close.c:22 #6 0x00401d4e in ow_exit (e=0) at owserver.c:52 #7 0x00401ed8 in main (argc=7, argv=0x7fffda4f3bd8) at owserver.c:164 Thanks, Martin Harvey -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information from ESET NOD32 Antivirus, version of virus signature database 3865 (20090218) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3865 (20090218) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Current sensors
Does anyone have experience of 1-wire Current sensors? I found some sensors here: http://www.homechip.com/catalog/product_info.php?products_id=73 http://www.homechip.com/catalog/product_info.php?products_id=73osCsid=88f1 c38977839e9aad52bde5c007c8c9 osCsid=88f1c38977839e9aad52bde5c007c8c9 http://www.ibuttonlink.com/ms-tc.aspx but I would like to measure more than 20A. Are there any other known sensors with 1-wire interface available? While browsing around I found lots of sensors here. but not with any 1-wire interface of course. http://www.process-controls.com/Bestek/functional_devices_xseries.html http://www.cprbestek.com/pdf/functional/RIBXK420_SERIES.pdf This might be useful since it deliver 4-20mA which could be measured with a DS2438 over the resistor or something similar. I just wanted to ask you anyway so I don't need to invent the wheel again. Perhaps there are some existing device/circuit which could be bought. /Christian -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] general protection
I have tried to stress-test owserver as much as I can here on different platforms, and I can't reproduce the errors. Can you start with the debug-output from all pthread-calls as well.. /usr/sbin/owserver -p 30003 -d /dev/ttyS0 -t 30 --foreground --fatal_debug --fatal_debug_file=/tmp/owserver_fatal If /tmp/owserver_fatal.pid is created and filled with debug-messages, then some pthread-calls are failing on your server. BTW: I will be on vacation between December 24th to 31'th, so I will not be able to do much more on this after tonight. /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Tuesday, December 23, 2008 12:11 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection If I run owserver as daemon, he was in such cases crashed. If I run well valgrind ... /usr/sbin/owserver -p 30003 -d /dev/ttyS0 -t 30 --foreground he continues to work. According to my experience this is also a sign of memory leaks. This is beginning to occur when owserver started simultaneously use several (4-6) clients, rather than 1-2 as before. Serg. I'm pretty clue-less why you get this error-message when memcpy((pn-lock), (opaque-key), sizeof(struct devlock *)); is called. ==00:01:31:14.563 2670== Invalid read of size 8 ==00:01:31:14.563 2670==at 0x4C568B7: LockGet (ow_locks.c:193) ==00:01:31:14.563 2670==by 0x4C5D8A1: FS_r_given_bus (ow_read.c:231) ==00:01:31:14.563 2670==by 0x4C5DB01: FS_read_distribute (ow_read.c:193) But... your owserver didn't seem to crash now? Is the major problem fixed now? I have checked in some various fixed some minutes ago, but nothing special that should affect this issue. /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Monday, December 22, 2008 7:50 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection I later corrected this. :) But this did not help. :( Serg. Sorry... I made a typo in the code... the memcpy row should look like this: memcpy((pn-lock), (opaque-key), sizeof(struct devlock *)); Forgot to get the pointer's to the variables, and therefore it ended up with a segmentation fault instead... Can you try to change the row and recompile with memcpy again? /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Monday, December 22, 2008 12:13 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Now running CVS-version on 9:30 UTC 2008-12-22 ... Results of file attachments. Serg. Serg. Hi Serg, Interesting log-files... It seems that your compiler generate wrong code... ==00:06:33:57.651 2275== Invalid read of size 8 ==00:06:33:57.651 2275==at 0x4C56559: LockGet (ow_locks.c:195) ==00:06:33:57.651 2275== Address 0x5A0D750 is 0 bytes inside a block of size 32 free'd ==00:06:33:57.651 2275==at 0x4A0541E: free (vg_replace_malloc.c:233) ==00:06:33:57.651 2275==by 0x30D8ED02B6: tdelete (in /lib64/libc-2.5.so) tsearch() seem to return a pointer to opaque, but pn-lock = opaque-key results Invalid read of size 8... ? I have made some changes in the code, and that might fix the problem. Size of struct devlock might have be unknown at some places and I have moved around the definitions a bit. Can you checkout the latest CVS-version and try it? If this doesn't work, you can try to edit module/owlib/src/c/ow_locks.c and change two rows... pn-lock = (struct devlock *)opaque-key; /* Serg: Invalid read of size 8 */ /* Why should a pointer compare fail? Unaligned memory? Perhaps try to copy the pointer with memcpy() instead. Will this help? */ //memcpy(pn-lock, opaque-key, sizeof(struct devlock *)); Comment out the row pn-lock = and uncomment memcpy instead Will this work for better for you? It should remove the warning of Invalid read of size 8 at least, and perhaps everything will work then as well. BTW: Which platform are you using? I have a feeling that your source isn't compiled with -m64, even if it should be... Could you look at the host_cpu in config.log and uname -a # grep host_cpu cvs/owfs/config.log # uname -a /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Saturday, December 20, 2008 10:33 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Ctrl-C pressed. Tried - the result of old. Version: from CVS at Dec 20 2008 12:00 UTC. Message in /tmp/owfs_fatal I received only once during the kill owserver_pid: ow_connect.c:322 mutex_destroy failed rc=16 [Device or resource busy] Serg. __ Information from ESET NOD32 Antivirus, version of virus signature database 3709 (20081220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __
Re: [Owfs-developers] general protection
Paul, I have tried to find any possible memory leaks in the flow below, but I can't find any reason to the memory leak. ==00:01:38:06.536 20943== 360,480 (278,560 direct, 81,920 indirect) bytes in 1,741 blocks are definitely lost in loss record 5 of 5 ==00:01:38:06.536 20943==at 0x4A05809: malloc (vg_replace_malloc.c:149) ==00:01:38:06.536 20943==by 0x3C52A52FBE: FS_OWQ_from_pn (ow_parseobject.c:87) ==00:01:38:06.536 20943==by 0x3C52A530AC: FS_OWQ_create_sibling (ow_parseobject.c:53) ==00:01:38:06.536 20943==by 0x3C52A58AFB: FS_r_sibling_F (ow_sibling.c:49) ==00:01:38:06.536 20943==by 0x3C52A27C7B: FS_slowtemp (ow_1820.c:282) ==00:01:38:06.536 20943==by 0x3C52A53FAC: FS_read_lump (ow_read.c:472) ==00:01:38:06.536 20943==by 0x3C52A542F4: FS_r_local (ow_read.c:427) ==00:01:38:06.536 20943==by 0x3C52A54967: FS_r_given_bus (ow_read.c:232) ==00:01:38:06.536 20943==by 0x3C52A54B01: FS_read_distribute (ow_read.c:193) ==00:01:38:06.536 20943==by 0x3C52A55223: FS_read_postparse (ow_read.c:109) ==00:01:38:06.536 20943==by 0x402AAD: ReadHandler (read.c:86) ==00:01:38:06.536 20943==by 0x40339A: DataHandler (data.c:125) ==00:01:38:06.508 20943== ERROR SUMMARY: 21 errors from 1 contexts (suppressed: 4 from 1) ==00:01:38:06.508 20943== ==00:01:38:06.508 20943== 21 errors in context 1 of 1: ==00:01:38:06.508 20943== Invalid read of size 8 ==00:01:38:06.508 20943==at 0x3C52A4D8B7: LockGet (ow_locks.c:193) ==00:01:38:06.508 20943==by 0x3C52A548A1: FS_r_given_bus (ow_read.c:231) ==00:01:38:06.508 20943==by 0x3C52A54B01: FS_read_distribute (ow_read.c:193) ==00:01:38:06.508 20943==by 0x3C52A55223: FS_read_postparse (ow_read.c:109) ==00:01:38:06.508 20943==by 0x402AAD: ReadHandler (read.c:86) ==00:01:38:06.508 20943==by 0x40339A: DataHandler (data.c:125) ==00:01:38:06.508 20943==by 0x30DA6062F6: start_thread (in /lib64/libpthread-2.5.so) ==00:01:38:06.509 20943==by 0x30D8ED1E3C: clone (in /lib64/libc-2.5.so) ==00:01:38:06.509 20943== Address 0x61A3430 is 0 bytes inside a block of size 32 free'd ==00:01:38:06.509 20943==at 0x4A0541E: free (vg_replace_malloc.c:233) ==00:01:38:06.509 20943==by 0x30D8ED02B6: tdelete (in /lib64/libc-2.5.so) ==00:01:38:06.509 20943==by 0x3C52A4D763: LockRelease (ow_locks.c:209) ==00:01:38:06.509 20943==by 0x3C52A5498B: FS_r_given_bus (ow_read.c:238) ==00:01:38:06.509 20943==by 0x3C52A54B01: FS_read_distribute (ow_read.c:193) ==00:01:38:06.509 20943==by 0x3C52A55223: FS_read_postparse (ow_read.c:109) ==00:01:38:06.509 20943==by 0x402AAD: ReadHandler (read.c:86) ==00:01:38:06.509 20943==by 0x40339A: DataHandler (data.c:125) ==00:01:38:06.509 20943==by 0x30DA6062F6: start_thread (in /lib64/libpthread-2.5.so) ==00:01:38:06.509 20943==by 0x30D8ED1E3C: clone (in /lib64/libc-2.5.so) The result seems to be that LockGet() and LockRelease() fails as well It might be generated by a un-successful temp-reading, and therefore the memory isn't allocated and free'd correctly at some points. I have to go home now, and I won't be able to look more into this until next year. /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Tuesday, December 23, 2008 4:10 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Running: /usr/bin/valgrind --time-stamp=yes --leak-check=full --leak-resolution=high --log-file=/tmp/owserver.log --trace-children=yes --undef-value-errors=yes --verbose /usr/sbin/owserver -p 30003 -d /dev/ttyS0 -t 30 --foreground --fatal_debug --fatal_debug_file=/tmp/owserver_fatal Not after you see the Invalid read of size 8, or after Ctrl-C file /tmp/owserver_fatal* is not created. Serg. I have tried to stress-test owserver as much as I can here on different platforms, and I can't reproduce the errors. In my case, the owserver used (by owread) 2xNagios every minute and 2xCacti (2 threads each) every 5 minutes. As shown in the logs, this error does not occur immediately, but after a while, in the latter case through 11 hours. In order to avoid a hardware error, I tried to completely change the server - it did not help. Can you start with the debug-output from all pthread-calls as well.. /usr/sbin/owserver -p 30003 -d /dev/ttyS0 -t 30 --foreground --fatal_debug --fatal_debug_file=/tmp/owserver_fatal If /tmp/owserver_fatal.pid is created and filled with debug-messages, then some pthread-calls are failing on your server. --fatal_debug I added to /etc/sysconfig/owserver, but forgot to add when run by valgrind. Now add ... BTW: I will be on vacation between December 24th to 31'th, so I will not be able to do much more on this after tonight. When owserver runs through valgrind, the system performs its functions... :) Merry Christmas! :) Serg. /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Tuesday, December 23, 2008 12:11 PM
Re: [Owfs-developers] general protection
Ahh... so you compiled the binaries on a i386 server, and used them on your x86_64 server? That would explain the strange errors with the data-sizes on some internal structures. /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Monday, December 22, 2008 11:23 AM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Hi Christian, # grep host_cpu config.log host_cpu='x86_64' # uname -a Linux srv71.netflow.ru 2.6.18-92.1.22.el5 #1 SMP Fri Dec 5 09:28:22 EST 2008 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.2 (Tikanga) Version 2.7p7 I tried to compile for i386 and run on x86_64 - received general protection. Now running CVS-version on 9:30 UTC 2008-12-22 ... Serg. Hi Serg, Interesting log-files... It seems that your compiler generate wrong code... ==00:06:33:57.651 2275== Invalid read of size 8 ==00:06:33:57.651 2275==at 0x4C56559: LockGet (ow_locks.c:195) ==00:06:33:57.651 2275== Address 0x5A0D750 is 0 bytes inside a block of size 32 free'd ==00:06:33:57.651 2275==at 0x4A0541E: free (vg_replace_malloc.c:233) ==00:06:33:57.651 2275==by 0x30D8ED02B6: tdelete (in /lib64/libc-2.5.so) tsearch() seem to return a pointer to opaque, but pn-lock = opaque-key results Invalid read of size 8... ? I have made some changes in the code, and that might fix the problem. Size of struct devlock might have be unknown at some places and I have moved around the definitions a bit. Can you checkout the latest CVS-version and try it? If this doesn't work, you can try to edit module/owlib/src/c/ow_locks.c and change two rows... pn-lock = (struct devlock *)opaque-key; /* Serg: Invalid read of size 8 */ /* Why should a pointer compare fail? Unaligned memory? Perhaps try to copy the pointer with memcpy() instead. Will this help? */ //memcpy(pn-lock, opaque-key, sizeof(struct devlock *)); Comment out the row pn-lock = and uncomment memcpy instead Will this work for better for you? It should remove the warning of Invalid read of size 8 at least, and perhaps everything will work then as well. BTW: Which platform are you using? I have a feeling that your source isn't compiled with -m64, even if it should be... Could you look at the host_cpu in config.log and uname -a # grep host_cpu cvs/owfs/config.log # uname -a /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Saturday, December 20, 2008 10:33 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Ctrl-C pressed. Tried - the result of old. Version: from CVS at Dec 20 2008 12:00 UTC. Message in /tmp/owfs_fatal I received only once during the kill owserver_pid: ow_connect.c:322 mutex_destroy failed rc=16 [Device or resource busy] Serg. __ Information from ESET NOD32 Antivirus, version of virus signature database 3709 (20081220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3709 (20081220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information from ESET NOD32 Antivirus, version of virus signature database 3710 (20081222) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3710 (20081222) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] general protection
Sorry... I made a typo in the code... the memcpy row should look like this: memcpy((pn-lock), (opaque-key), sizeof(struct devlock *)); Forgot to get the pointer's to the variables, and therefore it ended up with a segmentation fault instead... Can you try to change the row and recompile with memcpy again? /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Monday, December 22, 2008 12:13 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Now running CVS-version on 9:30 UTC 2008-12-22 ... Results of file attachments. Serg. Serg. Hi Serg, Interesting log-files... It seems that your compiler generate wrong code... ==00:06:33:57.651 2275== Invalid read of size 8 ==00:06:33:57.651 2275==at 0x4C56559: LockGet (ow_locks.c:195) ==00:06:33:57.651 2275== Address 0x5A0D750 is 0 bytes inside a block of size 32 free'd ==00:06:33:57.651 2275==at 0x4A0541E: free (vg_replace_malloc.c:233) ==00:06:33:57.651 2275==by 0x30D8ED02B6: tdelete (in /lib64/libc-2.5.so) tsearch() seem to return a pointer to opaque, but pn-lock = opaque-key results Invalid read of size 8... ? I have made some changes in the code, and that might fix the problem. Size of struct devlock might have be unknown at some places and I have moved around the definitions a bit. Can you checkout the latest CVS-version and try it? If this doesn't work, you can try to edit module/owlib/src/c/ow_locks.c and change two rows... pn-lock = (struct devlock *)opaque-key; /* Serg: Invalid read of size 8 */ /* Why should a pointer compare fail? Unaligned memory? Perhaps try to copy the pointer with memcpy() instead. Will this help? */ //memcpy(pn-lock, opaque-key, sizeof(struct devlock *)); Comment out the row pn-lock = and uncomment memcpy instead Will this work for better for you? It should remove the warning of Invalid read of size 8 at least, and perhaps everything will work then as well. BTW: Which platform are you using? I have a feeling that your source isn't compiled with -m64, even if it should be... Could you look at the host_cpu in config.log and uname -a # grep host_cpu cvs/owfs/config.log # uname -a /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Saturday, December 20, 2008 10:33 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Ctrl-C pressed. Tried - the result of old. Version: from CVS at Dec 20 2008 12:00 UTC. Message in /tmp/owfs_fatal I received only once during the kill owserver_pid: ow_connect.c:322 mutex_destroy failed rc=16 [Device or resource busy] Serg. __ Information from ESET NOD32 Antivirus, version of virus signature database 3709 (20081220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3709 (20081220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com - - ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers __ Information from ESET NOD32 Antivirus, version of virus signature database 3710 (20081222) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3710 (20081222) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] general protection
Hi Serg, Interesting log-files... It seems that your compiler generate wrong code... ==00:06:33:57.651 2275== Invalid read of size 8 ==00:06:33:57.651 2275==at 0x4C56559: LockGet (ow_locks.c:195) ==00:06:33:57.651 2275== Address 0x5A0D750 is 0 bytes inside a block of size 32 free'd ==00:06:33:57.651 2275==at 0x4A0541E: free (vg_replace_malloc.c:233) ==00:06:33:57.651 2275==by 0x30D8ED02B6: tdelete (in /lib64/libc-2.5.so) tsearch() seem to return a pointer to opaque, but pn-lock = opaque-key results Invalid read of size 8... ? I have made some changes in the code, and that might fix the problem. Size of struct devlock might have be unknown at some places and I have moved around the definitions a bit. Can you checkout the latest CVS-version and try it? If this doesn't work, you can try to edit module/owlib/src/c/ow_locks.c and change two rows... pn-lock = (struct devlock *)opaque-key; /* Serg: Invalid read of size 8 */ /* Why should a pointer compare fail? Unaligned memory? Perhaps try to copy the pointer with memcpy() instead. Will this help? */ //memcpy(pn-lock, opaque-key, sizeof(struct devlock *)); Comment out the row pn-lock = and uncomment memcpy instead Will this work for better for you? It should remove the warning of Invalid read of size 8 at least, and perhaps everything will work then as well. BTW: Which platform are you using? I have a feeling that your source isn't compiled with -m64, even if it should be... Could you look at the host_cpu in config.log and uname -a # grep host_cpu cvs/owfs/config.log # uname -a /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Saturday, December 20, 2008 10:33 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Ctrl-C pressed. Tried - the result of old. Version: from CVS at Dec 20 2008 12:00 UTC. Message in /tmp/owfs_fatal I received only once during the kill owserver_pid: ow_connect.c:322 mutex_destroy failed rc=16 [Device or resource busy] Serg. __ Information from ESET NOD32 Antivirus, version of virus signature database 3709 (20081220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3709 (20081220) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] general protection
I noticed Paul made some minor changes to the mutexes and this might fix your problem. I'm adding some wrapper functions to all mutexes which will make it possible to log any error-codes from the mutex-calls. I guess the first failing mutex-call will log a readable error, and the second error will generate a segmentation fault before being able to log the error. No pthread-calls handling mutexes _should_ return any errors if the code is working, but it could be useful to make it possible to turn on logging for those failing calls. It will of course generate some more stack-usage, but it shouldn't be noticeable. Compiling with --disable-debug should remove all extra wrapper functions. I really need this feature with uClibc-0.9.29 which seems to have a broken libpthread. It could be used on any system to make sure all mutexes are working as they should... I was thinking of something like this to turn on the debug-output. ./owserver --fatal_debug --fatal_debug_file /tmp/owfs_fatal --fatal_debug will log all errors to stderr or syslog depending on --error_print --fatal_debug_file /tmp/owfs_fatal will also log all errors to a file /tmp/owfs_fatal.pid I have checked in the changes to the CVS, and I hope this will show if there are more existing bugs with the mutexes. /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Thursday, December 18, 2008 4:44 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Unfortunately, I can not devote enough time, but I will strongly contribute to solving this problem. Hi All! version 2.7p11 # dmesg ... owserver[18546] general protection rip:2b88f97f76c0 rsp:53b29dc8 error:0 owserver[20757] general protection rip:2b13e1c026c0 rsp:4e8f1dc8 error:0 Sometimes this happens, starting with version 2.7p4. # file core.15352 core.15352: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'owserver' # gdb /usr/sbin/owserver core.15352 GNU gdb Red Hat Linux (6.5-37.el5_2.2rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-redhat-linux-gnu...Using host libthread_db library /lib64/libthread_db.so.1. Reading symbols from /usr/lib64/libow-2.7.so.11...Reading symbols from /usr/lib/debug/usr/lib64/libow-2.7.so.11.0.0.debug...done. done. Loaded symbols for /usr/lib64/libow-2.7.so.11 Reading symbols from /usr/lib64/libusb-0.1.so.4...done. Loaded symbols for /usr/lib64/libusb-0.1.so.4 Reading symbols from /lib64/libm.so.6...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /lib64/libdl.so.2...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libpthread.so.0...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libc.so.6...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgcc_s.so.1...done. Loaded symbols for /lib64/libgcc_s.so.1 Core was generated by `/usr/sbin/owserver -p 30003 -d /dev/ttyS0 -t 30'. Program terminated with signal 11, Segmentation fault. #0 0x2b88f97f76c0 in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 (gdb) (gdb) bt #0 0x2b88f97f76c0 in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x2b88f911e506 in LockRelease (pn=0x53b2a058) at ow_locks.c:194 #2 0x2b88f912504c in FS_r_given_bus (owq=0x53b2a040) at ow_read.c:238 #3 0x2b88f912514f in FS_read_distribute (owq=0x53b2a040) at ow_read.c:193 #4 0x2b88f91255ef in FS_read_postparse (owq=0x53b2a040) at ow_read.c:109 #5 0x0040278e in ReadHandler (hd=0x51325f00, cm=0x53b2a0e0, owq=0x53b2a040) at read.c:86 #6 0x00403025 in DataHandler (v=value optimized out) at data.c:124 #7 0x2b88f97f42f7 in start_thread () from /lib64/libpthread.so.0 #8 0x2b88f9ad9e3d in clone () from /lib64/libc.so.6 (gdb) # gdb /usr/sbin/owserver core.19785 GNU gdb Red Hat Linux (6.5-37.el5_2.2rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-redhat-linux-gnu...Using host libthread_db library /lib64/libthread_db.so.1. Reading symbols from /usr/lib64/libow-2.7.so.11...Reading symbols from /usr/lib/debug/usr/lib64/libow-2.7.so.11.0.0.debug...done. done. Loaded symbols for
Re: [Owfs-developers] general protection
Sorry... There are some calls to pthread_cancel() to kill the accept-thread, but it's not working as it was supposed to do... I'll take quick look at it. /Christian -Original Message- From: Christian Magnusson [mailto:m...@mag.cx] Sent: Friday, December 19, 2008 2:55 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection I noticed one problem at once when cleaning up the processes... There are no process-list and pthread_cancel() is never called to stop all running threads when you press Ctrl-C. This means that one thread has locked the connection_out-accept_mutex, and the FreeOut() function fails to destroy this mutex. [r...@magpc owfs]# /opt/owfs/bin/owserver --nozero -p 5001 --fake 10,28 --foreground --fatal_debug ^C DEFAULT: ow_connect.c:322 DEFAULT: mutex_destroy failed rc=16 [Device or resource busy] It's not any big problem, but we should perhaps have a list of all running threads and try to free all resources a bit cleaner. What do you think Paul? Isn't it worth to have better control over all running threads? /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Friday, December 19, 2008 2:08 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection I can try it on Saturday-Sunday... Serg. I noticed Paul made some minor changes to the mutexes and this might fix your problem. I'm adding some wrapper functions to all mutexes which will make it possible to log any error-codes from the mutex-calls. I guess the first failing mutex-call will log a readable error, and the second error will generate a segmentation fault before being able to log the error. No pthread-calls handling mutexes _should_ return any errors if the code is working, but it could be useful to make it possible to turn on logging for those failing calls. It will of course generate some more stack-usage, but it shouldn't be noticeable. Compiling with --disable-debug should remove all extra wrapper functions. I really need this feature with uClibc-0.9.29 which seems to have a broken libpthread. It could be used on any system to make sure all mutexes are working as they should... I was thinking of something like this to turn on the debug-output. ./owserver --fatal_debug --fatal_debug_file /tmp/owfs_fatal --fatal_debug will log all errors to stderr or syslog depending on --error_print --fatal_debug_file /tmp/owfs_fatal will also log all errors to a file /tmp/owfs_fatal.pid I have checked in the changes to the CVS, and I hope this will show if there are more existing bugs with the mutexes. /Christian -Original Message- From: Serg Oskin [mailto:s...@oskin.ru] Sent: Thursday, December 18, 2008 4:44 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] general protection Unfortunately, I can not devote enough time, but I will strongly contribute to solving this problem. Hi All! version 2.7p11 # dmesg ... owserver[18546] general protection rip:2b88f97f76c0 rsp:53b29dc8 error:0 owserver[20757] general protection rip:2b13e1c026c0 rsp:4e8f1dc8 error:0 Sometimes this happens, starting with version 2.7p4. # file core.15352 core.15352: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'owserver' # gdb /usr/sbin/owserver core.15352 GNU gdb Red Hat Linux (6.5-37.el5_2.2rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-redhat-linux-gnu...Using host libthread_db library /lib64/libthread_db.so.1. Reading symbols from /usr/lib64/libow-2.7.so.11...Reading symbols from /usr/lib/debug/usr/lib64/libow-2.7.so.11.0.0.debug...done. done. Loaded symbols for /usr/lib64/libow-2.7.so.11 Reading symbols from /usr/lib64/libusb-0.1.so.4...done. Loaded symbols for /usr/lib64/libusb-0.1.so.4 Reading symbols from /lib64/libm.so.6...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /lib64/libdl.so.2...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libpthread.so.0...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libc.so.6...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgcc_s.so.1...done. Loaded symbols for /lib64/libgcc_s.so.1 Core was generated by `/usr/sbin/owserver -p 30003 -d /dev/ttyS0 -t 30'. Program terminated with signal 11, Segmentation fault. #0 0x2b88f97f76c0 in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 (gdb) (gdb) bt #0 0x2b88f97f76c0
Re: [Owfs-developers] My latest experience...
I have added some more debug-output, and especially for the writev() commands. I noticed the middle owserver sends 3 blocks, 24+29+16 bytes, but the owserver which has the connected adapter never reads the Token bytes, and therefore it's 16 bytes left on the network which is treated as a new package. The payload is therefore later read as -2105066691 and that's a part of the unread token bytes. (12 0C 00 00 82 87 3B 3D 00 00 00 00 00 00 00 00) I'm not fully updated of the usage of the antiloop bytes and it's usage, so could you take a look at it Paul? /Christian Trying to read the fake sensor with owread. # owread -s 5001 /10.67C6697351FF/temperature # ./module/owserver/src/c/.libs/owserver --nozero --fake 10,28 -p 5000 --foreground --error_level=9 --error_print=2 ... DEBUG: DataHandler: FS_ParsedName_destroy done DEBUG: DataHandler: cm.ret=0 DEBUG: ToClient payload=0 size=0, ret=0, sg=0x105 offset=0 Writev byte buffer ionr=1/1 length=24 --000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 05 --016: 00 00 00 00 00 00 00 00 DEBUG: DataHandler: done DEBUG: OWSERVER tcp connection persistence -- reusing connection now. DEBUG: NetRead attempt 24 bytes Time:(10,0) Byte buffer NETREAD, length=24 --000: 12 0C 00 00 82 87 3B 3D 00 00 00 00 00 00 00 00 --016: 00 00 00 00 00 00 00 1D ..;= DEBUG: tcp_read n=24 nleft=0 n-nleft=24 DEBUG: FromClient payload=-2105066691 size=0 type=0 sg=0x0 offset=29 DEBUG: FromClient (no servermessage) payload=-2105066691 size=0 type=0 sg=0x0 offset=29 DEBUG: OWSERVER handler done [r...@home owfs]# ./module/owserver/src/c/.libs/owserver --nozero -s 5000 -p 5001 --foreground --error_level=9 --error_print=2 DEBUG: main_threadid = 3210545184 DEBUG: ServerProcessOut = 3210542000 DEBUG: ServerProcessAccept 5001[3210542000] try lock 0 DEBUG: ServerProcessAccept 5001[3210542000] locked 0 DEBUG: NetRead attempt 24 bytes Time:(10,0) DEBUG: ServerProcessAccept = 3210542000 CLOSING DEBUG: ServerProcessAccept 5001[3210542000] try lock 0 DEBUG: ServerProcessAccept 5001[3210542000] locked 0 Byte buffer NETREAD, length=24 --000: 00 00 00 00 00 00 00 1D 00 00 00 02 00 00 01 02 --016: 00 00 1F A0 00 00 00 00 DEBUG: tcp_read n=24 nleft=0 n-nleft=24 DEBUG: FromClient payload=29 size=8096 type=2 sg=0x102 offset=0 DEBUG: FromClient (no servermessage) payload=29 size=8096 type=2 sg=0x102 offset=0 DEBUG: NetRead attempt 29 bytes Time:(10,0) Byte buffer NETREAD, length=29 --000: 2F 31 30 2E 36 37 43 36 36 39 37 33 35 31 46 46 --016: 2F 74 65 6D 70 65 72 61 74 75 72 65 00 /10.67C6697351FF/temperature. DEBUG: tcp_read n=29 nleft=0 n-nleft=29 CALL: DataHandler: parse path=/10.67C6697351FF/temperature DEBUG: FS_OWQ_create of /10.67C6697351FF/temperature CALL: PARSENAME path=[/10.67C6697351FF/temperature] DEBUG: Cache_Get_Device 10 67 C6 69 73 51 FF 8D DEBUG: Get from cache sn 10 67 C6 69 73 51 FF 8D pointer=(nil) index=-1 size=4 DEBUG: value not found in cache DETAIL: Checking presence of /10.67C6697351FF/temperature CALL: SERVER(0)PRESENCE path=/10.67C6697351FF/temperature DEBUG: ToServer path=/10.67C6697351FF/temperature DEBUG: ToServer tokens=1 DEBUG: ToServer payload=29 size=0 type=6 SG=105 offset=0 Writev byte buffer ionr=1/3 length=24 --000: 00 00 00 00 00 00 00 1D 00 00 00 06 00 00 01 05 --016: 00 00 00 00 00 00 00 00 Writev byte buffer ionr=2/3 length=29 --000: 2F 31 30 2E 36 37 43 36 36 39 37 33 35 31 46 46 --016: 2F 74 65 6D 70 65 72 61 74 75 72 65 00 /10.67C6697351FF/temperature. Writev byte buffer ionr=3/3 length=16 --000: 12 0C 00 00 82 87 3B 3D 00 00 00 00 00 00 00 00 ..;= DEBUG: NetRead attempt 24 bytes Time:(2,0) Byte buffer NETREAD, length=24 --000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 05 --016: 00 00 00 00 00 00 00 00 DEBUG: tcp_read n=24 nleft=0 n-nleft=24 DEBUG: Cache_Add_Device 10 67 C6 69 73 51 FF 8D bus=0 DEBUG: Add to cache sn 10 67 C6 69 73 51 FF 8D pointer=(nil) index=-1 size=4 CALL: Read message DEBUG: ReadHandler: DEBUG: ReadHandler: From Client sm-payload=29 sm-size=8096 sm-offset=0 DEBUG: ReadHandler: call FS_read_postparse on /10.67C6697351FF/temperature DEBUG: READ_POSTPARSE /10.67C6697351FF/temperature DEBUG: READ_POSTPOSTPARSE /10.67C6697351FF/temperature DEBUG: FS_r_given_bus OWQ OneWireQuery structure of /10.67C6697351FF/temperature OneWireQuery size=8096 offset=0, extension=0 Byte buffer OneWireQuery buffer, length=8096 --000: 0B 00 00 00 01 00 00 00 7C 11 3F 00 00 00 00 00 --016: 07 00 00 00 00 00 00 00 81 50 41 00 0C 00 00 00 --032: 00 00 00 00 0B 00 00 00 04 00 00 00 DC 11 3F 00 --048: 00 00 00 00 07 00 00 00 00 00 00 00 E7 4E 41 00
[Owfs-developers] My latest experience...
I have had lots of problems with my 1-wire sensors lately, and I first thought it was related to bad wires or sensors. but after I upgraded to the latest 2.7p11 last night, all sensors are working perfect again. sort of. but only for local readings from the owserver which has the adapter connected. There seem to be some bugs in the network-reading between 2 owserver-processes right now.. Look on the setup and tests below. Router(192.168.3.1) with owserver/owfs and 1-wire adapter. r...@router:/# owserver -P /var/run/owserver.pid -d /dev/tts/1 -p 4304 r...@router:/# owfs -P /var/run/owfs.pid -s 4304 /tmp/1wire r...@router:/# cat /tmp/1wire/bus.0/bus.0/interface/settings/name DS9097U My server(192.168.3.2) with owserver running... [r...@home root]# /opt/owfs/bin/owserver --nozero -P /var/run/owserver.pid -s 192.168.3.1:4304 -p 4304 [r...@home root]# owdir -s 4304 /10.A2284800 /10.E2C746000800 /10.1A9246000800 /10.061847000800 /10.762047000800 /10.E54347000800 /10.4D8746000800 /10.6D015800 /10.5D1947000800 /10.233B4800 /10.B3E166000800 /10.2BD346000800 /1F.7DC20200 /FF.72020100 /FF.71020100 /bus.0 /settings /system /statistics /structure (works all the time..) [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.4375 Reading values from the remote-owserver on the router works every time.. But when I try to read the values from the local owserver (which connects to the router's owserver adapter) I never get two successful reads in a row. [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Data error on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature I also noticed very much difference in speed/response-time when owfs read the values from the first or second owserver. [r...@home root]# /opt/owfs/bin/owfs --nozero -P /var/run/owfs.pid -s 192.168.3.1:4304 /mnt/1wire [r...@home root]# cat /mnt/1wire/FF.72020100/counters.ALL (delay 0.1 seconds) 0, 0, 0, 0(delay 0.01 second before cat returns) [r...@home root]# cat /mnt/1wire/FF.72020100/counters.ALL (delay 0.1 seconds) 0, 0, 0, 0(delay 0.01 second before cat returns) [r...@home root]# kill `cat /var/run/owfs.pid` [r...@home root]# /opt/owfs/bin/owfs --nozero -P /var/run/owfs.pid -s 192.168.3.2:4304 /mnt/1wire [r...@home root]# cat /mnt/1wire/FF.72020100/counters.ALL (delay 1 second) 0, 0, 0, 0(delay 1 second before cat returns) [r...@home root]# cat /mnt/1wire/FF.72020100/counters.ALL (delay 1 second) 0, 0, 0, 0(delay 1 second before cat returns) I haven't traced down the problem yet. but there must be some bug in the code. Have anyone else seem problems like this? /Christian -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/___ Owfs-developers mailing
Re: [Owfs-developers] My latest experience...
BTW: I was able to re-produce the read-bug with just a fake adapter. [r...@home owfs]# owserver --fake 10,28 -p 5000 [r...@home owfs]# owserver -s 5000 -p 5001 [r...@home owfs]# owdir -s 5001 /10.67C6697351FF /28.4AEC29CDBAAB /bus.0 /settings /system /statistics /structure This fails every second time or something. [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature Error receiving data on /10.67C6697351FF/temperature [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature 36.4784 [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature Error receiving data on /10.67C6697351FF/temperature [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature 51.3401 [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature Error receiving data on /10.67C6697351FF/temperature [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature 95.223 [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature Error receiving data on /10.67C6697351FF/temperature [r...@home owfs]# owread -s 5001 /10.67C6697351FF/temperature 91.6195 This works. [r...@home owfs]# owread -s 5000 /10.67C6697351FF/temperature 63.5712 [r...@home owfs]# owread -s 5000 /10.67C6697351FF/temperature 71.7297 [r...@home owfs]# owread -s 5000 /10.67C6697351FF/temperature 14.1603 [r...@home owfs]# owread -s 5000 /10.67C6697351FF/temperature /Christian From: Christian Magnusson [mailto:m...@mag.cx] Sent: Wednesday, December 17, 2008 7:04 PM To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] My latest experience... I have had lots of problems with my 1-wire sensors lately, and I first thought it was related to bad wires or sensors. but after I upgraded to the latest 2.7p11 last night, all sensors are working perfect again. sort of. but only for local readings from the owserver which has the adapter connected. There seem to be some bugs in the network-reading between 2 owserver-processes right now.. Look on the setup and tests below. Router(192.168.3.1) with owserver/owfs and 1-wire adapter. r...@router:/# owserver -P /var/run/owserver.pid -d /dev/tts/1 -p 4304 r...@router:/# owfs -P /var/run/owfs.pid -s 4304 /tmp/1wire r...@router:/# cat /tmp/1wire/bus.0/bus.0/interface/settings/name DS9097U My server(192.168.3.2) with owserver running... [r...@home root]# /opt/owfs/bin/owserver --nozero -P /var/run/owserver.pid -s 192.168.3.1:4304 -p 4304 [r...@home root]# owdir -s 4304 /10.A2284800 /10.E2C746000800 /10.1A9246000800 /10.061847000800 /10.762047000800 /10.E54347000800 /10.4D8746000800 /10.6D015800 /10.5D1947000800 /10.233B4800 /10.B3E166000800 /10.2BD346000800 /1F.7DC20200 /FF.72020100 /FF.71020100 /bus.0 /settings /system /statistics /structure (works all the time..) [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.1:4304 /10.2BD346000800/temperature 18.4375 Reading values from the remote-owserver on the router works every time.. But when I try to read the values from the local owserver (which connects to the router's owserver adapter) I never get two successful reads in a row. [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Data error on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature 18.4375 [r...@home root]# owread -s 192.168.3.2:4304 /10.2BD346000800/temperature Error receiving data on /10.2BD346000800/temperature I
Re: [Owfs-developers] owfs in background - fuse hangs
I'm pretty sure that you have compiled your kamikaze-distribution to use uClibc-0.9.29... libpthread in this version is _very_ broken, and I have told the kamikaze-developers about this problem. Enter the menuconfig and change the uClibc-version and try to recompile everything with uClibc-0.9.28.x. Many other applications under the package/feeds are broken when you use that latest uClibc-version, and there are no reason to use this latest version. /Christian -Original Message- From: Andreas Seidler [mailto:[EMAIL PROTECTED] Sent: Thursday, October 30, 2008 3:13 AM To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] owfs in background - fuse hangs Hi, Today i build owfs packages (2.7p7) for OpenWrt (kamikaze/x86 with kernel_2.6.25). owhttpd and owserver works fine. owfs too, but sadly only with the --foreground option. Without this option owfs fork to background and fuse seems to hang.. I testet with fuse 2.7.3 and some older versions (2.7.0) and with ofws 2.7p4 too; same props. strace says nothing exceptional, just fuse hangs but i wonder why it works fine if owfs running in foreground? regards tetzlav - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] --disable-mt not working
I just noticed that -disable-mt didn't work in 2.7p6. Some typos in the code, and owftd is now disabled automatically if -disable-mt is used. since it requires pthread. I checked in the changes to the CVS. I also made some changes to configure-script yesterday. I managed to get owtcl to work on my Asus WL-500W router (with tcl8.6a2). It finally worked after I compiled owfs without multithread-support. Not sure why libow crashed. The signal handler in owlib.c was called when I tried ::OW::get /. in owfs/module/swig/tcl/example/test.tcl Output with error_level=9 gave me this: CALL: PARSENAME path=[/28.4AEC29CDBAAB] DEBUG: Cache_Get_Device 28 4A EC 29 CD BA AB 95 DEBUG: Get from cache sn 28 4A EC 29 CD BA AB 95 pointer=(nil) index=-1 size=4 DEBUG: value not found in cache DETAIL: Checking presence of /28.4AEC29CDBAAB DEBUG: Signal handler for 1, errno 0, code 128, pid=0, self=0 DEBUG: Signal handler for 1, errno 0, code 128, pid=0, self=0 Strace of the tclsh-process gave me this. write(1, \nDirectory-listing of / (return ..., 39 Directory-listing of / (return string)) = 39 write(1, \n, 1 ) = 1 write(2, DEBUG: , 9 DEBUG: )= 9 write(2, FS_OWQ_create of /\n, 19FS_OWQ_create of / )= 19 write(2,CALL: , 9 CALL: )= 9 write(2, PARSENAME path=[/]\n, 19PARSENAME path=[/] )= 19 write(2, DEBUG: , 9 DEBUG: )= 9 write(2, In FS_dir(/)\n, 13In FS_dir(/) ) = 13 write(2,CALL: , 9 CALL: )= 9 write(2, DIRECTORY path=/\n, 17DIRECTORY path=/ ) = 17 time(NULL) = 1221118587 pipe([4715800, 18]) = 3 clone(child_stack=0x482938, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND) = 2846 write(4, \260\234\345*u\377\177\20\347G\0\340\177\340*\300w\334..., 148) = 148 rt_sigprocmask(SIG_SETMASK, NULL, ~[HUP INT QUIT ILL TRAP IOT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM USR1 USR2 CHLD PWR WINCH URG IO STOP TSTP CONT TTIN TTOU VTALRM PROF XCPU XFSZ RT_1 RT_2 RT_3 RT_4 RT_5 RT_6 RT_7 RT_10 RT_12 RT_14 RT_16 RT_18 RT_20 RT_25 RT_27 RT_29 RT_31 RT_32 RT_33 RT_35 RT_36 RT_37 RT_38 RT_39 RT_40 RT_41 RT_42 RT_43 RT_44 RT_45 RT_46 RT_47 RT_48 RT_49 RT_50 RT_51 RT_52 RT_53 RT_54 RT_55 RT_56 RT_57 RT_58 RT_59 RT_60 RT_61 RT_62 RT_63 RT_64 RT_65 RT_66 RT_69 RT_74 RT_78 RT_80 RT_81 RT_82 RT_83 RT_84 RT_89 RT_91 RT_93], 16) = 0 write(4, \0\0\0\0\0\0\0\0\0\0\0\0\314a\343*\370u\377\177\0\0\0\200..., 148) = 148 rt_sigprocmask(SIG_SETMASK, NULL, [RT_0], 16) = 0 rt_sigsuspend([RT_0] DEBUG: Cache_Get_Dir 00 00 00 00 00 00 00 00 DEBUG: unfinished ... --- SIGRT_0 (Unknown signal 32) @ 0 (0) --- ... rt_sigsuspend resumed ) = -1 EINTR (Interrupted system call) sigreturn(Segmentation fault It seems to be some thread-problem with tclsh and the owtcl module. but since it worked when I disabled multithreading in owfs, I probably don't look more into the problem. It works for all other platforms. Tclsh is compiled without thread-support as default, but I don't think this is the problem. I have compiled tclsh on my NSLU2 without thread-support, and owtcl works there. /Christian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] --disable-mt not working
It was something with the thread support in tclsh. When I compiled tcl with --enable-threads, owtcl worked with threads as well. But tclsh hanged when the script is supposed to exit. I needed to patch tcl a bit to call _exit() instead of exit(). -#define TclpExit exit +#define TclpExit _exit Now it works as it should. It's possible to use owtcl on Asus-routers as well. /Christian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: NSLU2 and OWFS
OWFS will work on other Unslung 6.10 supported devices. It's just a matter of setting up the cross-compile environment and compile it. I could try to compile it for other platforms if you have more exact information about the device you are going to use, but I can't try to run it myself though. The hardest part is to compile fuse and fix the kernel-modules, but if you only need owserver, owhttpd and owshell it's absolutely not a problem /Christian -- Forwarded message -- From: Joaquim Manuel Medeira Rodrigues [EMAIL PROTECTED] Date: Thu, Sep 4, 2008 at 4:44 AM Subject: NSLU2 and OWFS To: [EMAIL PROTECTED] Hi, I've been looking to your 'NSLU2 and OWFS' excelent page on 'http://owfs.sourceforge.net/' and i would like to ask you some questions: - Do you think that owfs packages will work on other Unslung 6.8 supported devices like Iomega NAS 100d, D-Link DSM-G600, Freecom FSG-3 and others, basically the devices listed on http://www.nslu2-linux.org/? (As long as they have usb ports :) ) - There are some examples on 'http://owfs.sourceforge.net/'. Were you able to read and write to the network without any problems or does it have any limitation? (acess is always trasparent to the devices as long as you can see them)? - I'm considering buying the NSLU2 but basically i would like to know if i could consider other similar devices. Thanks Joaquim - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] A/D read problems
Ah. So that's the problem to my problem with the LCD displays. Reading counter.ALL failed when I read through owfs, but worked when I used owread. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 21 juli 2008 04:44 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] A/D read problems Found the error. Fixed in the CVS and will be fixed in the next release. Thanks for the report. Paul Alfille On Sun, Jul 13, 2008 at 3:26 PM, Tim Sailer [EMAIL PROTECTED] wrote: I had just noticed that over the last few weeks, my weather station stopped reporting wind direction from the quad A/D converter. Thinking it was my station that finally failed, I took the whole mast down, put the spare station in place and mounted it all back up. Bad idea. Things are still broken. volt.ALL reports and error, while reading each A/D channel works: [EMAIL PROTECTED]:~$ /opt/owfs/bin/owread 20.F8B7/volt.ALL -s 10.0.0.32:4304 Data error on 20.F8B7/volt.ALL [EMAIL PROTECTED]:~$ /opt/owfs/bin/owread 20.F8B7/volt.A -s 10.0.0.32:4304 4.65038 Any ideas? This is using a newish SVN copy (in the last month or so). - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS1923
There has obviously been some problem with the code since the bus-read/write
operations in OW_w_mem() has been split up into multiple operations with
lots of debug-output.
/* Re-read scratchpad and compare */
/* Note: location of data has now shifted down a byte for E/S register
*/
//ret = BUS_select(pn) || BUS_send_data( p,3,pn) || BUS_readin_data(
p[3],1+rest+2,pn) || CRC16(p,4+rest+2) || memcmp(p[4], data, size) ;
ret = BUS_select(pn);
ret = BUS_send_data(p, 1, pn);
ret = BUS_readin_data(p[1], 3 + rest, pn);
ret = CRC16(p, 4 + rest); // this fails according to your tests...
ret = memcmp(p[4], data, size);
The read/write buffers and lengths are not the same in the first expression
compared to the following rows... Perhaps it's just some typos when it was
split down into multiple lines.
I don't have any working DS1923 at home so I can't test the code. The
CRC-check should be fixed and not removed to make sure we don't break any
more DS1923 devices by sending them into a hanging state with the oscillator
turned off.
Paul, do you have any DS1923 devices at home?
/Christian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael
D. Petersen
Sent: den 29 juni 2008 06:06
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] DS1923
Found the source of the problem, but I'm not sure why it is a problem.
ow_1923.c (OW_w_mem):
ret = CRC16(p, 4 + rest);
if (ret) {
printf(OW_w_mem: crc err1\n);
}
The CRC16 fails, causing the read of temperature and humidity to
fail. I was feeling brave, so I simply changed the CRC16 call to the
following:
ret = 0;
That worked! Both temperature and humidity appear to read back with
reasonable values.
As a little background, this write routine is called as part of
OW_oscillator to make sure the oscillator is enabled before a read
operation (presumably to prevent the latchup condition in this
part). Not sure why the CRC fails, but the write seems to
work. Hopefully someone else can help explain that.
Michael
At 07:57 PM 6/28/2008, Michael D. Petersen wrote:
What is the latest level of support for the DS1923? The list of
devices (http://owfs.org/index.php?page=standard-devices) says there
is no support, but when I plugged one into the bus, it was
recognized. However, both the temperature and humidity files are
unreadable (yes, I did make sure the RTC was running). Just curious
if this is truly the current state of things.
Thanks,
Michael
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fedora Core 9 - DS9490R problem
According to the log, you receive a ETIMEDOUT (110) error after reading/writing to the usb-adapter. DEBUG: Selecting a path (and device) path=/10.008350010800/temperature SN=10 00 83 50 01 08 00 7B last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: error sending reset ret=-110 DEBUG: Transaction select = 1 DEBUG: Selecting a path (and device) path=/10.008350010800/temperature SN=10 00 83 50 01 08 00 7B last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset Your usb-interface seem to have problem after the write-error happens, and I think this is some kind of hardware or kernel-problem in your computer. The default is to use the usb_flextime speed, but you might try to use the slower regular time instead and see if this works better for you. # owserver -u --usb_regulartime # owfs -s 4304 /mnt/1wire You should now see that flexible timing isn't used. # cat /mnt/1wire/bus.0/bus.0/interface/settings/flexible_timing 0 Can you try it and see if it works better for you? Also check dmesg for usb-errormessages if it happens again. It could be good to know what your kernel says about the usb-interface and the errors. It should be possible to just unload the usb-modules and reload them again if the problem happens again. # /sbin/rmmod ehci_hcd # /sbin/rmmod ohci_hcd # /sbin/rmmod uhci_hcd # /sbin/modprobe uhci_hcd # /sbin/modprobe ohci_hcd # /sbin/modprobe ehci_hcd # /sbin/lsusb And hopefully you can use the usb-adapter again. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cristi Tudora Sent: den 15 juni 2008 19:09 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Fedora Core 9 - DS9490R problem 2. I only have one sensor (DS18s20). I tryed to read temperature and temphigh. The same thing is happening. After error, I can't see the 10.* device, not even 81.* device. Here is a ls -l /mnt/1-wire: drwxr-xr-x 1 root root 8 2008-06-15 19:59 bus.0 drwxr-xr-x 1 root root 8 2008-06-15 19:59 settings drwxr-xr-x 1 root root 8 2008-06-15 19:59 statistics drwxr-xr-x 1 root root 30 2008-06-15 19:59 structure drwxr-xr-x 1 root root 8 2008-06-15 19:59 system drwxr-xr-x 1 root root 8 2008-06-15 19:59 uncached 3. I tryed owfs and owhttp. Same error. 4. ./owfs version: 2.7p4 libow version: 2.7p4 Here is the log from initial owfs start: ./owfs -u1 -m /mnt/1-wire --foreground --error_level=9 CONNECT: fuse mount point: /mnt/1-wire CALL: PARSENAME path=[] CONNECT: Adapter found: 001/002 DEFAULT: Opened USB DS9490 adapter at 001/002. DATA: DS9490_setup_adapter: done (ret=0) DEBUG: Start of directory path= device=00 00 00 00 00 00 00 00 DEBUG: Selecting a path (and device) path= SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Index 0 DEBUG: Got 16 bytes from USB search DEBUG: DS9490 directory gulp. Adding element 0:10 00 83 50 01 08 00 7B DEBUG: DS9490 directory gulp. Adding element 1:81 B3 50 29 00 00 00 82 DEBUG: DS9490_next_both SN found: 10 00 83 50 01 08 00 7B DEBUG: BUS_next return = 0 10 00 83 50 01 08 00 7B DEBUG: Selecting a path (and device) path= SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Index 1 DEBUG: DS9490_next_both SN found: 81 B3 50 29 00 00 00 82 DEBUG: BUS_next return = 0 81 B3 50 29 00 00 00 82 CONNECT: Good DS1421 tag found for 001/002 DEFAULT: Set DS9490 001/002 unique id to 81 B3 50 29 00 00 00 82 DEBUG: fuse_mnt_opt=[(null)] DEBUG: fuse_open_opt=[(null)] unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.9 flags=0x000b max_readahead=0x0002 INIT: 7.8 flags=0x0001 max_readahead=0x0002 max_write=0x0002 unique: 1, error: 0 (Success), outsize: 40 ... --- OneWireQuery done DEBUG: Cache_Get 10 00 83 50 01 08 00 7B size=8 IsUncachedDir=0 DEBUG: Get from cache sn 10 00 83 50 01 08 00 7B pointer=0x1692ec index=0 size=8 DEBUG: value not found in cache DEBUG: Cache_Get_Internal 10 00 83 50 01 08 00 7B size=1 DEBUG: Get from cache sn 10 00 83 50 01 08 00 7B pointer=0x169148 index=-2 size=1 DEBUG: value not found in cache DEBUG: Selecting a path (and device) path=/10.008350010800/temperature SN=10 00 83 50 01 08 00 7B last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: error sending reset ret=-110 DEBUG: Transaction select = 1 DEBUG: Selecting a path (and device) path=/10.008350010800/temperature SN=10 00 83 50 01 08 00 7B last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset And here is the output of repetitive cat for temphigh: Sun Jun 15 19:45:52 2008 75 Sun Jun 15 19:45:53 2008 75 Sun Jun 15 19:45:54 2008 75 Sun Jun 15 19:45:56
[Owfs-developers] Lots of configure/Makefile updates
I tried to find the problem why the swig/python module didn't work on my 64bit desktop with python2.5, and I finally found the problem. Global is a reserved variable-name, so I had to rename it to Globals instead. All shared libraries are now compiled with -fPIC to generate position independent code as well. This should be done long time ago to generate correct code, and it's strange nobody has complained about it before. I hope I didn't break anything after the updates. It works on both my old 32bit desktop with python2.2 and x86_64 desktop with python2.5. /Christian - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Lots of configure/Makefile updates
I don't think so. I'm building everything with Cygwin on windows now as well. and it seems to work fine. Owserver, owshell and owhttpd works at least. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 17 juni 2008 15:40 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Lots of configure/Makefile updates So after we fix the alarm bug, are there any outstanding issues before a new release? Paul On Tue, Jun 17, 2008 at 9:16 AM, Christian Magnusson [EMAIL PROTECTED] wrote: Global is a reserved variable-name, so I had to rename it to Globals instead. All shared libraries are now compiled with -fPIC to generate position independent code as well. This should be done long time ago to generate correct code, and it's strange nobody has complained about it before. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] BUG: read /alarm
I can only confirm that I could replicate the bug on my server too. The remote-owserver seems to hang (mutex problem?) after clearing the alarms. The owserver didn't respond to other new connections. Had to kill the process and restart owserver to access the 1-wire adapter again. BTW: I added set_error_level and set_error_print to owcapi to make it possible to change the debug-output after calling init(). Could be useful if you temporary want to enable or disable the debug output in a script. $ perl use OW ; OW::init(-s 3000); OW::set_error_level(9); OW::set_error_print(2); my $res = OW::get(/alarm) or die; $ tclsh % package require ow; % ::OW::init -s 3000 % ::OW::set_error_level 9; % ::OW::set_error_print 2; % ::OW::get /alarm /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Serg Oskin Sent: den 7 juni 2008 17:06 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] BUG: read /alarm Hi, I found such a mistake: $ tclsh % package require ow; % ::OW::init -s 3000 % ::OW::get /alarm 28.2CCD8000/,28.86BF8000/ % # ...Clear all alarms... % ::OW::get /alarm pause of ~2 seconds I/O error % Similar for perl: $ perl use OW ; OW::init(-s 3000); my $res = OW::get(/alarm) or die; print $res\n; ^D pause of ~2 seconds Died at - line 5. $ tclsh (or perl) with --error_level=9 --error_print=2 : DEBUG: FS_OWQ_create of /alarm CALL: PARSENAME path=[/alarm] DEBUG: In FS_dir(/alarm) CALL: DIRECTORY path=/alarm DEBUG: ALARM directory CALL: SERVER(0)DIR path=/alarm path_busless=/alarm pause of ~2 seconds by tcp_read CONNECT: TIMEOUT after 0 bytes DEBUG: Return from ALARM is -5 DEBUG: FS_dir_both out ret=-5 DEBUG: FS_OWQ_destroy of /alarm DEBUG: ParsedName_destroy /alarm owserver with --error_level=9 --error_print=2 : DEBUG: OWSERVER tcp connection persistence -- reusing connection now. DEBUG: FromClient payload=7 size=0 type=4 sg=0x105 offset=0 DEBUG: Persistence requested CALL: owserver: parse path=/alarm DEBUG: FS_OWQ_create of /alarm CALL: PARSENAME path=[/alarm] CALL: Directory message (one at a time) CALL: DirHandler: pn-path=/alarm DEBUG: OWSERVER SpecifiedBus=0 path=/alarm DEBUG: In FS_dir_remote(/alarm) CALL: DIRECTORY path=/alarm DEBUG: ALARM directory DEBUG: Selecting a path (and device) path=/alarm SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: BUS_next return = -5 00 00 00 00 00 00 00 00 DEBUG: FS_alarmdir BUS_first_alarm = -5 DEBUG: Return from ALARM is -5 DEBUG: FS_dir_both out ret=-5 DEBUG: FS_OWQ_destroy of /alarm DEBUG: ParsedName_destroy /alarm DEBUG: RealHandler: FS_ParsedName_destroy done DEBUG: RealHandler: cm.ret=-5 DEBUG: RealHandler: done pause of ~2 seconds DEBUG: OWSERVER tcp connection persistence -- reusing connection now. DEBUG: OWSERVER handler done Sorry, no time now to seek the cause. :( - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Make for owfs fails with invalid Python installation
If you would have used --disable-owpython, then it will skip the ownet/python directory (not --disable-python) /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lyle Giese Sent: den 9 juni 2008 02:35 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Make for owfs fails with invalid Python installation I tried to search the archives for this and came up empty. I started to play with OWFS after purchasing some sensors from www.hobby-boards.com and came upon an issue with OWFS 2.7p4. I am installing on a system running OpenSuSE 10.3 (i386). I untarred OWFS and ran configure with no options. Then make. No problems so far. Then make install. It dies when entering modules/ownet/python with: error: invalid Python installation: unable to open /usr/lib/python2.5/config/Makefile (no such file or directory) I don't need or want python modules, so I figure this is something I don't want or need. I retried running configure with the option of --disable-python, with no change, same error. I went into module/ownet and edited the Makefile by changing ENABLE_PYTHON = true to false on line 119 and ENABLE_OWPYTHON = true to false on line 110. No change, still errors out in make install. I went into module/ownet again and edited the Makefile by commenting out line 302: OWNET_SUBDIRPYTHON = python Now make install works and I get owfs and everything I really need to make this work. I know this is not the proper way to do this, but I have no use for the python modules as I am a perl man myself. But thought I should mention this issue here since I could not find anything in the list archives. Thanks, Lyle Giese LCR Computer Services, Inc. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: [Owfs-forums] [owfs - Help] Unable to build
I'm downloading debian and will try to compile owfs now. Are all 3 DVD images needed to install a simple desktop with gcc? /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 10 juni 2008 18:38 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Fwd: [Owfs-forums] [owfs - Help] Unable to build -- Forwarded message -- From: SourceForge.net [EMAIL PROTECTED] Date: Tue, Jun 10, 2008 at 11:48 AM Subject: [Owfs-forums] [owfs - Help] Unable to build To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5020950 By: simonhobson I'm trying to build OWFS on a Debian Etch box. At first I was unable to configure - getting the same message. Googling for the error message came up with hints that this is related to including header files in the wrong order. I edited /usr/local/owfs-2.7p4/module/owlib/src/include/ow.h and moved the includes for time.h and sys/time.h to before sys/stat.h and this allowed configure to run. However, compile still fails. Can anyone suggest where to look next ? Config options are : Current configuration: Deployment location: /opt/owfs Compile-time options: Caching is enabled USB is enabled I2C is DISABLED HA7Net is DISABLED Multithreading is enabled Parallel port DS1410E is DISABLED TAI8570 barometer is enabled Thermocouple is enabled Zeroconf/Bonjour is DISABLED Debug-output is enabled Profiling is DISABLED Module configuration: owlib is enabled owshell is enabled owfs is enabled owhttpd is DISABLED owftpd is DISABLED owserver is DISABLED ownet is DISABLED ownetlib is DISABLED owtap is DISABLED owmon is DISABLED owcapi is DISABLED swig is DISABLED owperl is DISABLED owphp is DISABLED owpython is DISABLED owtcl is DISABLED LibUSB and LibFUSE are as follows : # dpkg -l libusb* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++---== == ii libusb-0.1-4 0.1.12-5 userspace USB programming library ii libusb-dev 0.1.12-5 userspace USB programming library development files un libusb0 none (no description available) # dpkg -l libfuse* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++---== == ii libfuse-dev 2.7.1-2~bpo40+1 Filesystem in USErspace (development files) ii libfuse2 2.7.1-2~bpo40+1 Filesystem in USErspace library The point where the build fails is : make[4]: Entering directory `/usr/local/owfs-2.7p4/module/owfs/src/c' gcc -DHAVE_CONFIG_H -I. -I../../../../src/include-I../include -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=26 -I/usr/include/linux -I../../../owlib/src/include -L../../../owlib/src/c -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -pthread -g -O2 -MT owfs.o -MD -MP -MF .deps/owfs.Tpo -c -o owfs.o owfs.c In file included from /usr/include/sys/stat.h:105, from ../../../owlib/src/include/ow.h:101, from ../include/owfs.h:19, from owfs.c:18: /usr/include/bits/stat.h:70: error: field 'st_atim' has incomplete type /usr/include/bits/stat.h:71: error: field 'st_mtim' has incomplete type /usr/include/bits/stat.h:72: error: field 'st_ctim' has incomplete type In file included from /usr/include/sys/types.h:266, from ../../../owlib/src/include/ow.h:105, from ../include/owfs.h:19, from owfs.c:18: /usr/include/bits/pthreadtypes.h:50: error: expected specifier-qualifier-list before 'size_t' In file included from ../../../owlib/src/include/ow.h:108, from ../include/owfs.h:19, from owfs.c:18: /usr/include/sys/times.h:37: error: expected specifier-qualifier-list before 'clock_t' /usr/include/sys/times.h:49: error: expected
Re: [Owfs-developers] Fwd: [Owfs-forums] [owfs - Help] Unable to build
I downloaded Debian 4.0r3, and I did not have much problem at all. Remember to install all packages which are needed to compile. # apt-get update # apt-get install gcc build-essential libtool automake libusb-dev And eventual some optional packages to build everything in owfs.. # apt-get install swig python-dev php5 php5-dev tcl8.4-dev Everything build without any errors after these installations. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Magnusson Sent: den 11 juni 2008 18:34 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Fwd: [Owfs-forums] [owfs - Help] Unable to build I'm downloading debian and will try to compile owfs now. Are all 3 DVD images needed to install a simple desktop with gcc? /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 10 juni 2008 18:38 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Fwd: [Owfs-forums] [owfs - Help] Unable to build -- Forwarded message -- From: SourceForge.net [EMAIL PROTECTED] Date: Tue, Jun 10, 2008 at 11:48 AM Subject: [Owfs-forums] [owfs - Help] Unable to build To: [EMAIL PROTECTED] Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=5020950 By: simonhobson I'm trying to build OWFS on a Debian Etch box. At first I was unable to configure - getting the same message. Googling for the error message came up with hints that this is related to including header files in the wrong order. I edited /usr/local/owfs-2.7p4/module/owlib/src/include/ow.h and moved the includes for time.h and sys/time.h to before sys/stat.h and this allowed configure to run. However, compile still fails. Can anyone suggest where to look next ? Config options are : Current configuration: Deployment location: /opt/owfs Compile-time options: Caching is enabled USB is enabled I2C is DISABLED HA7Net is DISABLED Multithreading is enabled Parallel port DS1410E is DISABLED TAI8570 barometer is enabled Thermocouple is enabled Zeroconf/Bonjour is DISABLED Debug-output is enabled Profiling is DISABLED Module configuration: owlib is enabled owshell is enabled owfs is enabled owhttpd is DISABLED owftpd is DISABLED owserver is DISABLED ownet is DISABLED ownetlib is DISABLED owtap is DISABLED owmon is DISABLED owcapi is DISABLED swig is DISABLED owperl is DISABLED owphp is DISABLED owpython is DISABLED owtcl is DISABLED LibUSB and LibFUSE are as follows : # dpkg -l libusb* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++---== == ii libusb-0.1-4 0.1.12-5 userspace USB programming library ii libusb-dev 0.1.12-5 userspace USB programming library development files un libusb0 none (no description available) # dpkg -l libfuse* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++---== == ii libfuse-dev 2.7.1-2~bpo40+1 Filesystem in USErspace (development files) ii libfuse2 2.7.1-2~bpo40+1 Filesystem in USErspace library The point where the build fails is : make[4]: Entering directory `/usr/local/owfs-2.7p4/module/owfs/src/c' gcc -DHAVE_CONFIG_H -I. -I../../../../src/include-I../include -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=26 -I/usr/include/linux -I../../../owlib/src/include -L../../../owlib/src/c -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -pthread -g -O2 -MT owfs.o -MD -MP -MF .deps/owfs.Tpo -c -o owfs.o owfs.c In file included from /usr/include/sys/stat.h:105, from ../../../owlib/src/include/ow.h:101, from ../include/owfs.h:19, from owfs.c:18: /usr/include/bits/stat.h:70: error: field 'st_atim' has incomplete type /usr
Re: [Owfs-developers] checking fuse.h usability... no
I guess you are missing the fuse-devel package. yum install fuse-devel Can you search for the error-text in the fuse-include-files? # grep -i present but cannot be compiled /usr/include/fuse* /usr/include/fuse/* Which file contains the text, and why is the #waring statements printed? /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boyan Biandov Sent: den 23 maj 2008 21:10 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] checking fuse.h usability... no Is it even possible to compile OWFS under FC9? I am getting an endless nightmare of errors, fuse comes with FC9 but when I download owfs-2.7p4 and run ./configure it can not see fuse. When specifying the path to fuse.h directly I get: configure: WARNING: fuse.h: present but cannot be compiled configure: WARNING: fuse.h: check for missing prerequisite headers? configure: WARNING: fuse.h: see the Autoconf documentation configure: WARNING: fuse.h: section Present But Cannot Be Compiled configure: WARNING: fuse.h: proceeding with the preprocessor's result configure: WARNING: fuse.h: in the future, the compiler will take precedence checking for fuse.h... yes checking for fuse_main in -lfuse... No Downloading fuse itself bombs out because its already present as a module hence building it is impossible Is there at least ONE installation out there with owfs compiled successfully under FC9? I will be happy to switch to any other distro, I am NOT married to FC9. I just need to know what works Thanks Boyan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] lrint() changes
Did the code crash when there were negative temperatures using the old function? BYTE data = BYTE_MASK((int) (T + .49)); // round off /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Collinge Sent: den 11 maj 2008 01:16 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] lrint() changes I only used that for a quick fix to a problem connected with the 1821 returning negative temperatures and causing a crash. I agree that it's not worth creating a dependency for so I would be happy to code it into the 1821 support if you give me a few days to code and test. On Sat, May 10, 2008 at 1:00 PM, Christian Magnusson [EMAIL PROTECTED] wrote: We have to make some more changes in configure.ac after lrint() is used in ow_1821.c. This function is located in libm.so, and this is the first dependency to this library. I think it's a waste of memory to add a new dynamic library if we only use one single function in it from owlib.. Especially on the embedded systems. Anyway. the dependency could be added with this row in configure.ac. AC_SEARCH_LIBS(lrint, m, AC_DEFINE(HAVE_LRINT, 1, [Define if you have lrint])) I have added some changes in the CVS to make this check. /Christian - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao ne ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] lrint() changes
We have to make some more changes in configure.ac after lrint() is used in ow_1821.c. This function is located in libm.so, and this is the first dependency to this library. I think it's a waste of memory to add a new dynamic library if we only use one single function in it from owlib.. Especially on the embedded systems. Anyway. the dependency could be added with this row in configure.ac. AC_SEARCH_LIBS(lrint, m, AC_DEFINE(HAVE_LRINT, 1, [Define if you have lrint])) I have added some changes in the CVS to make this check. /Christian - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] lrint() for embedded...
I just tried to compile the changes I made for openwrt with uClibc, and I noticed that lrint doesn't exist in libm.so. The patch I made works and revert the behavior to the old rounding code.. When configure is run, it can't find lrint() and HAVE_LRINT is undefined. checking for vsnprintf... yes checking for library containing dlopen... -ldl checking for library containing lrint... no checking for library containing nanosleep... none required /Christian - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New ipkg-packages
They are now available at http://owfs.sourceforge.net/nslu2/packages/ . /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 10 april 2008 06:19 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New ipkg-packages Hi, Please let me know when the patch is available in 'ipkg' form for the nslu2. Or, if available in CVS in the meantime, and someone knows how to install on nslu2 from CVS, please let me know. Thank you. Steve J. - Original Message From: Christian Magnusson [EMAIL PROTECTED] To: owfs-developers@lists.sourceforge.net Sent: Wednesday, April 9, 2008 9:45:31 AM Subject: Re: [Owfs-developers] New ipkg-packages I'm trying to build everything now. Are the latest changes stable now? I tried it 2 days ago, and then I got lots of errors with the sidetap changes. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 9 april 2008 12:49 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New ipkg-packages It's probably easier to get Christian to make a new package, or to help you set up a build environment so you can stay at the cutting edge. Paul Alfille On Wed, Apr 9, 2008 at 1:56 AM, [EMAIL PROTECTED] wrote: Still trying to install owfs from CVS. Ok, I tried to install the latest via ipkg(does complete install - very simple), but the bug fix wasn't in ipkg. So, I have to do it the CVS way. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New ipkg-packages
You seemed to have an old owlib installed on you nslu2. I'm not sure how Paul wants to solve that /bus.0/uncached/uncached/ directory. but it should be fixed to make it possible to do a complete directory listing with find or owcapi. The example module/swig/perl5/example/test.pl loops forever since there are unlimited uncached directories as well.. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 7 april 2008 08:28 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New ipkg-packages Here's my packages installed: # ipkg list_installed | grep ow owcapi - 2.7p4-2 - 1-wire CAPI library and includes owfs - 2.7p4-2 - 1-Wire filesystem (http://owfs.sf.net) owlib - 2.7p2-1 - 1-wire library owshell - 2.7p4-2 - 1-wire shell utilities oww - 0.82.1-1 - Oww reads from a DalSemi/AAG weather station. I removed them all and installed #ipkg install owfs owlib owshell # ipkg list_installed | grep ow owfs - 2.7p4-2 - 1-Wire filesystem (http://owfs.sf.net) owlib - 2.7p4-2 - 1-wire library owshell - 2.7p4-2 - 1-wire shell utilities # # owfs -V owfs version: 2.7p4 libow version: 2.7p4 # Now, I have the problem with recursive directory structure: # pwd /tmp/1wire/bus.0/uncached/uncached/uncached/uncached/uncached/uncached/uncac hed/ uncached/uncached/uncached/uncached/uncached/uncached # I thought this problem was fixed in p4? Not sure where to go from here. Steve J. - Original Message From: Christian Magnusson [EMAIL PROTECTED] To: owfs-developers@lists.sourceforge.net Sent: Monday, April 7, 2008 12:57:33 AM Subject: Re: [Owfs-developers] New ipkg-packages You are missing the packate owlib-2.7p4-2 .. Can you see which packages you have installed? # ipkg list_installed | grep ow owfs - 2.7p4-2 - 1-Wire filesystem (http://owfs.sf.net http://owfs.sf.net/ ) owlib - 2.7p4-2 - 1-wire library owshell - 2.7p4-2 - 1-wire shell utilities Try to uninstall and re-installed it. # ipkg remove owfs owlib owshell # ipkg install owfs owlib owshell /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 7 april 2008 07:07 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New ipkg-packages Has anyone installed this for the NSLU2? I tried, but I am missing the library 'libow-2.7.so http://libow-2.7.so/ .4' Here are the errors I get when installing # run-owfs owserver: error while loading shared libraries: libow-2.7.so http://libow-2.7.so/ .4: cannot open shar ed object file: No such file or directory owfs: error while loading shared libraries: libow-2.7.so http://libow-2.7.so/ .4: cannot open shared o bject file: No such file or directory owhttpd: error while loading shared libraries: libow-2.7.so http://libow-2.7.so/ .4: cannot open share d object file: No such file or directory owftpd: error while loading shared libraries: libow-2.7.so http://libow-2.7.so/ .4: cannot open shared object file: No such file or directory # Steve - Original Message From: Christian Magnusson [EMAIL PROTECTED] To: owfs-developers@lists.sourceforge.net Sent: Saturday, April 5, 2008 4:04:36 PM Subject: [Owfs-developers] New ipkg-packages Sorry for taking so long to compile new packages for openwrt and nslu2.. I have made major changes in my firewall, since I have installed an ipsec-tunnel to the dev-server where I make most my builds on. And that resulted only lots of scripts-errors and network-problems when I tried to upload all packages. anyway. I have compiled lots of new packages from the latest CVS-version owfs-2.7p4. NSLU2 http://owfs.sourceforge.net/nslu2/packages/ Whiterussian RC5 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/packages/ Whiterussian 0.9 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/0.9/packages/ Kamikaze 7.07 (brcm-2.4 with 2.4.34 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze/packages/ Kamikaze 7.07 (brcm47xx-2.6 with 2.6.22 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze-2.6/packages/ Kamikaze 7.07 (mips with 2.6.22 kernel, uClibc-0.9.28) (for routers such as Atheros) http://owfs.sourceforge.net/openwrt/kamikaze-2.6-atheros/packages/ Midge (adm5120 with 2.4.32 kernel, uClibc-0.9.28) (for routers such as Edimax BR6104KP, http://midge.vlad.org.ua/wiki/SupportedDevices) http://owfs.sourceforge.net/openwrt/midge/packages/ Kamikaze 7.09 (brcm-2.4 with 2.4.34 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd, ASUS-WL500W) http://owfs.sourceforge.net/openwrt/kamikaze-7.09-asus/packages/ /Christian
Re: [Owfs-developers] New ipkg-packages
It still seem to be a bug in the CVS-source which I checked out 2 days ago. Paul, do you want to look at it when you have time? # owserver fake 10 p # owfs s 127.0.0.1: /mnt/1wire2 This will show a duplicate uncache-directory. [EMAIL PROTECTED] ~]# ls -l /mnt/1wire2/bus.0/uncached/ total 0 drwxrwxrwx 1 root root 8 Apr 7 20:29 10.67C6697351FF/ drwxr-xr-x 1 root root 8 Apr 7 20:29 alarm/ drwxr-xr-x 1 root root 8 Apr 7 20:29 interface/ drwxr-xr-x 1 root root 8 Apr 7 20:29 settings/ drwxrwxrwx 1 root root 8 Apr 7 20:29 simultaneous/ drwxr-xr-x 1 root root 8 Apr 7 20:29 statistics/ drwxr-xr-x 1 root root 30 Apr 7 20:29 structure/ drwxr-xr-x 1 root root 8 Apr 7 20:29 system/ drwxr-xr-x 1 root root 8 Apr 7 20:29 uncached/ ß The uncached is always showed when /bus.x is used in the path-name. This will now show a duplicate uncached-path [EMAIL PROTECTED] ~]# ls -l /mnt/1wire2/uncached/ total 0 drwxrwxrwx 1 root root 8 Apr 7 20:31 10.67C6697351FF/ drwxr-xr-x 1 root root 8 Apr 7 20:29 alarm/ drwxr-xr-x 1 root root 8 Apr 7 20:29 bus.0/ drwxr-xr-x 1 root root 8 Apr 7 20:29 settings/ drwxrwxrwx 1 root root 8 Apr 7 20:31 simultaneous/ drwxr-xr-x 1 root root 8 Apr 7 20:29 statistics/ drwxr-xr-x 1 root root 30 Apr 7 20:29 structure/ drwxr-xr-x 1 root root 8 Apr 7 20:29 system/ But adding bus.0 will show uncached again [EMAIL PROTECTED] ~]# ls -l /mnt/1wire2/uncached/bus.0/ total 0 drwxrwxrwx 1 root root 8 Apr 7 20:31 10.67C6697351FF/ drwxr-xr-x 1 root root 8 Apr 7 20:29 alarm/ drwxr-xr-x 1 root root 8 Apr 7 20:29 interface/ drwxr-xr-x 1 root root 8 Apr 7 20:29 settings/ drwxrwxrwx 1 root root 8 Apr 7 20:31 simultaneous/ drwxr-xr-x 1 root root 8 Apr 7 20:29 statistics/ drwxr-xr-x 1 root root 30 Apr 7 20:29 structure/ drwxr-xr-x 1 root root 8 Apr 7 20:29 system/ drwxr-xr-x 1 root root 8 Apr 7 20:29 uncached/ ß /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 7 april 2008 09:17 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New ipkg-packages My current owlib version is: owlib - 2.7p4-2 - 1-wire library Is that still the old library? Before I re-installed (per your directions) I did have an old version (owlib - 2.7p2-1 - 1-wire library). Yes..doing a 'find / -name ow* -print gives a output that goes on forever Is this directory problem a current bug(do you see it on your system?), or just a bug with my version(s)? Steve J. - Original Message From: Christian Magnusson [EMAIL PROTECTED] To: owfs-developers@lists.sourceforge.net Sent: Monday, April 7, 2008 2:05:59 AM Subject: Re: [Owfs-developers] New ipkg-packages You seemed to have an old owlib installed on you nslu2 Im not sure how Paul wants to solve that /bus.0/uncached/uncached/ directory but it should be fixed to make it possible to do a complete directory listing with find or owcapi. The example module/swig/perl5/example/test.pl loops forever since there are unlimited uncached directories as well.. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 7 april 2008 08:28 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New ipkg-packages Here's my packages installed: # ipkg list_installed | grep ow owcapi - 2.7p4-2 - 1-wire CAPI library and includes owfs - 2.7p4-2 - 1-Wire filesystem (http://owfs.sf.net http://owfs.sf.net/ ) owlib - 2.7p2-1 - 1-wire library owshell - 2.7p4-2 - 1-wire shell utilities oww - 0.82.1-1 - Oww reads from a DalSemi/AAG weather station. I removed them all and installed #ipkg install owfs owlib owshell # ipkg list_installed | grep ow owfs - 2.7p4-2 - 1-Wire filesystem (http://owfs.sf.net http://owfs.sf.net/ ) owlib - 2.7p4-2 - 1-wire library owshell - 2.7p4-2 - 1-wire shell utilities # # owfs -V owfs version: 2.7p4 libow version: 2.7p4 # Now, I have the problem with recursive directory structure: # pwd /tmp/1wire/bus.0/uncached/uncached/uncached/uncached/uncached/uncached/uncac hed/ uncached/uncached/uncached/uncached/uncached/uncached # I thought this problem was fixed in p4? Not sure where to go from here. Steve J. - Original Message From: Christian Magnusson [EMAIL PROTECTED] To: owfs-developers@lists.sourceforge.net Sent: Monday, April 7, 2008 12:57:33 AM Subject: Re: [Owfs-developers] New ipkg-packages You are missing the packate owlib-2.7p4-2 . Can you see which packages you have installed? # ipkg list_installed | grep ow owfs - 2.7p4-2 - 1-Wire filesystem (http://owfs.sf.net http://owfs.sf.net/ ) owlib - 2.7p4-2 - 1-wire library owshell - 2.7p4-2 - 1-wire shell utilities Try to uninstall and re-installed it # ipkg remove owfs owlib owshell # ipkg install owfs owlib
Re: [Owfs-developers] New ipkg-packages
You are missing the packate owlib-2.7p4-2 .. Can you see which packages you have installed? # ipkg list_installed | grep ow owfs - 2.7p4-2 - 1-Wire filesystem (http://owfs.sf.net) owlib - 2.7p4-2 - 1-wire library owshell - 2.7p4-2 - 1-wire shell utilities Try to uninstall and re-installed it. # ipkg remove owfs owlib owshell # ipkg install owfs owlib owshell /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 7 april 2008 07:07 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New ipkg-packages Has anyone installed this for the NSLU2? I tried, but I am missing the library 'libow-2.7.so.4' Here are the errors I get when installing # run-owfs owserver: error while loading shared libraries: libow-2.7.so.4: cannot open shar ed object file: No such file or directory owfs: error while loading shared libraries: libow-2.7.so.4: cannot open shared o bject file: No such file or directory owhttpd: error while loading shared libraries: libow-2.7.so.4: cannot open share d object file: No such file or directory owftpd: error while loading shared libraries: libow-2.7.so.4: cannot open shared object file: No such file or directory # Steve - Original Message From: Christian Magnusson [EMAIL PROTECTED] To: owfs-developers@lists.sourceforge.net Sent: Saturday, April 5, 2008 4:04:36 PM Subject: [Owfs-developers] New ipkg-packages Sorry for taking so long to compile new packages for openwrt and nslu2.. I have made major changes in my firewall, since I have installed an ipsec-tunnel to the dev-server where I make most my builds on. And that resulted only lots of scripts-errors and network-problems when I tried to upload all packages. anyway. I have compiled lots of new packages from the latest CVS-version owfs-2.7p4. NSLU2 http://owfs.sourceforge.net/nslu2/packages/ Whiterussian RC5 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/packages/ Whiterussian 0.9 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/0.9/packages/ Kamikaze 7.07 (brcm-2.4 with 2.4.34 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze/packages/ Kamikaze 7.07 (brcm47xx-2.6 with 2.6.22 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze-2.6/packages/ Kamikaze 7.07 (mips with 2.6.22 kernel, uClibc-0.9.28) (for routers such as Atheros) http://owfs.sourceforge.net/openwrt/kamikaze-2.6-atheros/packages/ Midge (adm5120 with 2.4.32 kernel, uClibc-0.9.28) (for routers such as Edimax BR6104KP, http://midge.vlad.org.ua/wiki/SupportedDevices) http://owfs.sourceforge.net/openwrt/midge/packages/ Kamikaze 7.09 (brcm-2.4 with 2.4.34 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd, ASUS-WL500W) http://owfs.sourceforge.net/openwrt/kamikaze-7.09-asus/packages/ /Christian - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS+arm cross compilation problem !!!
I fixed some problem in the CVS now. Had problem to cross-compile everything. Made some changes in many Makefiles which should add the correct defines in all cases. sem.h was missing in a src/include/Makefile.am as well. Found a bug in rwlock.h, which results into semaphore.h is never used.. since HAVE_SEMAPHORE is used. (should be HAVE_SEMAPHORE_H) Is this done by purpose to test the replacement semaphores perhaps?? It builds correct for me now at least. Haven't tried the binaries yet though. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 31 mars 2008 15:33 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] OWFS+arm cross compilation problem !!! Great. OWNet (C library) uses a subset of the full owlib. (Basically just the parameter parsing and networking parts). Unfortunately that means it's code can look similar, but out of sync with owlib, and compilation errors can be confusing. Paul Alfille On Sun, Mar 30, 2008 at 9:21 AM, Sven Geggus [EMAIL PROTECTED] wrote: If nothing else, try to add --disable-ownet to the ./configure options OK, tried the latter which at least gave me a successful compilation. I will have to check now, if this actually works :) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS+arm cross compilation problem !!!
That __pthread_initial_thread_bos is really some ugly hack by me but it was necessary on several platforms with older uclibc-0.9.28 versions at least.. The mutexes didnt work after daemon() was called if __pthread_initial_thread_bos wasnt cleared and _pthread_initialize() was called a second time. I wrote some comments in the code about this /* Have to re-initialize pthread since the main-process is gone. * * This workaround will probably be fixed in uClibc-0.9.28 * Other uClibc developers have noticed similar problems which are * trigged when pthread functions are used in shared libraries. */ Perhaps they have fixed the problem in uclibc-0.9.29, and we could perhaps make some ifdefs to remove that re-initialization if uclibc = 0.9.29. I guess its possible to add something like this to skip the initialize() call for newer uclibcs.. -- owlib.c #if ((__UCLIBC_MAJOR__ 16)+(__UCLIBC_MINOR__ 8)+(__UCLIBC_SUBLEVEL__) 0x00091D) extern char *__pthread_initial_thread_bos; void __pthread_initialize(void); #endif - #if ((__UCLIBC_MAJOR__ 16)+(__UCLIBC_MINOR__ 8)+(__UCLIBC_SUBLEVEL__) 0x00091D) __pthread_initial_thread_bos = NULL; __pthread_initialize(); #endif -- /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 20 mars 2008 11:39 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] OWFS+arm cross compilation problem !!! Sounds like that combination of configuration parameters excluded some variable declarations. I'll fix. Is this against 2.7p4? Paul Alfille On Thu, Mar 20, 2008 at 5:14 AM, greg h [EMAIL PROTECTED] wrote: hello, I try to cross compile owfs with uclibc toolchain (arm-linux-gcc-4.2.1, uclibc-0.9.29). 1- ./configure --target=arm-linux --build=i386-linux --host=arm-linux --with-fuseinclude=/home/grp62/bus/fuse-2.7.3/temp/include/ --with-fuselib=/home/grp62/bus/fuse-2.7.3/temp/lib/ --prefix=/home/grp62/bus/owfs-2.7p4/temp/ --disable-owperl --disable-owphp --disable-owpython --disable-owtcl --disable-usb --disable-parport --disable-tai8570 --disable-ha7 --disable-thermocouple 2- make owlib.c: In function 'LibStart': owlib.c:58: error: '__pthread_initial_thread_bos' undeclared (first use in this function) owlib.c:58: error: (Each undeclared identifier is reported only once owlib.c:58: error: for each function it appears in.) owlib.c:59: warning: implicit declaration of function '__pthread_initialize' owlib.c:63: warning: implicit declaration of function 'pthread_mutexattr_settype' make[5]: *** [owlib.lo] Erreur 1 I made a test by disabling the multithreading (--disable-mt ) but i got the following error: ow_connect.c: In function 'FreeIn': ow_connect.c:126: error: 'struct connection_in' has no member named 'bus_mutex' make[5]: *** [ow_connect.lo] Erreur 1 Any ideas ? thanks in advance _ Envoyé avec Yahoo! Mail http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http:/us.rd.yahoo.com/e vt=52420/*http:/fr.docs.yahoo.com/mail/overview/index.html . La boite email la plus appreciée au monde. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Working Openwrt/Freewrt setup Anybody?
I bought a WL500w some time ago, and I have built owfs-packages for the kamikaze 7.09 distribution at http://openwrt.org/ . There were no working image for the WL500w due to some hardware changes... and that makes it impossible for me to use the original firmware image at http://downloads.openwrt.org/kamikaze/7.09/brcm-2.4/openwrt-brcm-2.4-squashf s.trx If you have a WL500g or WL500gd, you should be able to use the image above. Note: If you want to use the wireless support on WL500, you have to use the 2.4-kernel. The 2.6-kernel doesn't support this on brcm right now. You should then be able to use the owfs-packages at: http://owfs.sourceforge.net/openwrt/kamikaze/packages/ /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sven Geggus Sent: den 18 mars 2008 22:39 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Working Openwrt/Freewrt setup Anybody? Hi there, I need to setup an Asus WL500g Deluxe with 1-wire support USB _and_ working wireless LAN (station mode). I suppose that a binary distribution is not enough, because I would also need to compile a custom application using owcapi and a cross-compiler. Debian would also be an option, but the Kernel on http://wpkg.org/Running_Debian_on_ASUS_WL-500G_deluxe does not support wireless lan and unfortunately I was unable to compile a newer one. Any hints? Sven -- The American news-media is no longer a news source; it is a cheerleading squad. (unknown source) /me is [EMAIL PROTECTED], http://sven.gegg.us/ on the Web - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Working Openwrt/Freewrt setup Anybody?
They are compiled against Whiterussian RC5. Libc is older in this distribution and they will not work on Kamikaze-installations. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sven Geggus Sent: den 19 mars 2008 10:20 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Working Openwrt/Freewrt setup Anybody? Paul Alfille [EMAIL PROTECTED] wrote: http://owfs.org/index.php?page=asus-wirelesswim-heirman http://owfs.org/index.php?page=wl-hdd Concerning the packages on http://owfs.sourceforge.net/openwrt/packages/; What Version of Openwrt are they for? Sven -- .. this message has been created using an outdated OS (UNIX-like) with an outdated mail- or newsreader (text-only) :-P /me is [EMAIL PROTECTED], http://sven.gegg.us/ on the Web - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Yet another build quirk with owtcl.
You can't have it running in both normal installed environment AND in a fakeroot. Have you seen any other dynamic linked applications which work this way? It's NOT possible to have a working library at /fakeroot/usr/lib64/owtcl-0.2/ow-0.2.so if you compile it like. # ./configure # make DESTDIR=/fakeroot install If you want to use your installation under the directory /fakeroot, you should tell configure with --prefix instead. # ./configure --prefix=/fakeroot # make install /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Kandziora Sent: den 16 februari 2008 00:23 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Yet another build quirk with owtcl. Am Freitag, 15. Februar 2008 23:59 schrieb Serg Oskin: Hmm.. Try make clean before make... rpmbuild even does rm..., tar xzf owfs-tar.gz, ./bootstrap etc.. But ok, I build it by hand again. Show output ldd ow-0.2.so... linux-gate.so.1 = (0xb7fba000) libtcl8.4.so = /usr/lib/libtcl8.4.so (0xb7ee) libow-2.7.so.3 = /home/jan/cvs/owfs.new/module/owlib/src/c/.libs/libow-2.7.so.3 (0xb7e84000) libowcapi-2.7.so.3 = /home/jan/cvs/owfs.new/module/owcapi/src/c/.libs/libowcapi-2.7.so.3 (0xb7e8) libdl.so.2 = /lib/libdl.so.2 (0xb7e7c000) libpthread.so.0 = /lib/libpthread.so.0 (0xb7e63000) libc.so.6 = /lib/libc.so.6 (0xb7d35000) libm.so.6 = /lib/libm.so.6 (0xb7d0f000) libusb-0.1.so.4 = /usr/lib/libusb-0.1.so.4 (0xb7d06000) /lib/ld-linux.so.2 (0x8000) Hmm. It seems a compile run by hand works as expected but within a fakeroot environment it doesn't. I will investigate this further tomorrow. G'night. Jan -- F: Wieviele Surrealisten braucht man, um eine Glühlampe einzuschrauben? A: Zwei. Einer hält die Giraffe fest und der andere füllt die Badewanne mit buntem Werkzeug. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] compiling 2.7p3
I have fixed this problem in the CVS some time ago... /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 16 februari 2008 11:06 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] compiling 2.7p3 Hi @all, I try to compile owfs 2.7p3 and I get the error: ---snip--- ow_multicast.c: In function `FS_FindHA7': ow_multicast.c:40: error: `AI_NUMERICSERV' undeclared (first use in this function) ow_multicast.c:40: error: (Each undeclared identifier is reported only once ow_multicast.c:40: error: for each function it appears in.) make[4]: *** [ow_multicast.lo] Error 1 make[4]: Leaving directory `/usr/src/BUILD/owfs-2.7p3/module/owlib/src/c' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/src/BUILD/owfs-2.7p3/module/owlib/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/BUILD/owfs-2.7p3/module/owlib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/BUILD/owfs-2.7p3/module' make: *** [all-recursive] Error 1 ---snip--- the variable AI_NUMERICSERV is not defined and only used in owfs-2.7p3/module/owlib/src/c/ow_multicast.c. When I delete this variable in ow_multicast.c, I can compile owfs. Why is this variable in the source code? Build System: debian etch Regards Andreas -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.web.de/de/entertainment/games/free - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: 1wire hardware
I have successfully built owfs for WL-500W with Kamikaze-7.09 and 2.4.34-kernel. I haven't copied these packages to any accessible repository yet though. I got stuck with the incomplete perl-packages in Kamikaze, and then I re-wrote all Makefiles to get a full perl-installation on an external memory-stick. However. my older packages built for Kamikaze 7.07 located at http://owfs.sourceforge.net/openwrt/kamikaze/packages/ should work for you. They are compiled against kernel-2.4.34 and use the same libc as Kamikaze-7.09. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 16 februari 2008 13:00 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Fwd: 1wire hardware -- Forwarded message -- From: Marco Tozzini [EMAIL PROTECTED] Date: Feb 16, 2008 4:16 AM Subject: Re: 1wire hardware To: Paul Alfille [EMAIL PROTECTED] Cc: Marco Tozzini [EMAIL PROTECTED] Hi Paul Sorry for delay in reply I found some problem running OWFS under Openwrt kamikaze 7.09 and ASUS WL500gP packages for 7.07 works also for 7.09 but only for kernel 2.6 I need kernel 2.4 to make wifi working too (there is still nod driver for broadcom wifi on asus and kernel 2.6) I try to compile OWFS for 7.09 but OWFS has a strange (FOR ME) configuration way and I'm not able to figure out how to do a complete compilation I wonder if you can address me to how to compile the owfs also for kamikaze 7.09 (I think the same way you did for 7.07 is enough good) Thanks Ciao Marco P.S. I'm using OWFS on ASUS WL500gP and it works good also with internal serial port (2.4 = /dev/tts/1 or 2.6 = /dev/ttyS1) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] rrdtool takes extremely long time to generate images for temploggerd on NSLU2 running Debian
Hi Willard, I have seen this before actually... and I think I know the reason as well... The problem seem to occur during these circumstances: You have a new installed box and reboot it. Owfs-processes is started Temploggerd is started. It scans the 1-wire bus and creates the html-files and rrd-files. Temploggerd is now working good without any long delays. Time is set to correct date by ntpclient. (From year 2000 to 2008) Temploggerd is now hanging since all rrdtools are taking extremely long time. It seems like rrdtool has problem to rotate away old data from year 2000 and insert new values created year 2008. I have managed to solve the hanging by: kill-temploggerd rm /path/temperature.rrd run-temploggerd Try to make sure the date is correct before starting temploggerd in the rc-scripts. Eg. The clock should not only be set in a cronjob. Ntpclient has to be called before temploggerd's rc-startup script. Can you verify if you have stumbled into the same problem as I have experienced before. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Willard Korfhage Sent: den 17 januari 2008 05:37 To: OWFS Developers List Subject: [Owfs-developers] rrdtool takes extremely long time to generate images for temploggerd on NSLU2 running Debian I put owfs and temploggerd on an NSLU2 running Debian 4.0r2. Owfs is working, but I couldn't get any of the temploggerd web pages. I traced the problem down to the rrdtool graph function, and for certain parameters it takes a terribly long time to generate pages. Temploggerd generates a cgi file that has an RRD::GRAPH tag to generate the graph image, and that includes instructions to print out the average, min, max and last. I ran the equivalent by running rddtool graph by hand, printing out only the max. It turns out that a graph that includes PRINT:2629A88000tempe:MAX:%5.1lf C makes it take 37 minutes to generate the image. If I remove that instruction, it takes 5.7 seconds to generate the image. I tried the version of rrdtools installed by aptitude (1.2.15), and even compiled the latest (1.2.26), and both act the same. Interestingly enough, the print directives work fine on my NSLU2 unit running Unslung 6.8. Some difference between big- and little-ending versions? Willard - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Compiling OWFS on ARM Issue
Are you cross-compiling the binaries, or do you compile it native on the
board?
Googling on the Verneed record gives me some other users with the same
problem. It's more likely to be a libc-bug but you can try some things.
Can you copy the binary and library to /tmp and try to start it from there?
(Setting LD_LIBRARY_PATH to use the copied library)
cd /tmp/
cp /opt/owfs/bin/owserver /tmp/
cp /opt/owfs/lib/libow* /tmp/
export LD_LIBRARY_PATH=/tmp
ldd /tmp/owserver
./owserver -h
Does owserver in the tmp-directory work after this test?
export LD_LIBRARY_PATH=/opt/owfs/lib
ldd /opt/owfs/bin/owserver
/opt/owfs/bin/owserver -h
Does it work when LD_LIBRARY_PATH is set to /opt/owfs/lib ?
Do you have any possibility to use different libc versions? Perhaps you
care cross-compiling against one version, and try to run the compiled binary
against another libc-version?
/Christian
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frank
Sent: den 7 januari 2008 20:12
To: owfs-developers@lists.sourceforge.net
Subject: [Owfs-developers] Compiling OWFS on ARM Issue
Hi everyone,
I am trying to build and compile owfs for the Technologic TS-7800 SBC
(http://www.embeddedarm.com/epc/ts7800-spec-h.htm) . It is an ARM-based
board running Debian Linux (Sarge).
I'm not sure where the problem is yet (owfs or the SBC), so the question I'd
like to ask this group is if this message means anything to anyone.
owserver: error while loading shared libraries:
/opt/owfs/lib/libow-2.7.so.2: unsupported version 0 of Verneed record
I doubt the problem is directly with owfs since I was able to compile,
install, and run the exact same source on my Ubuntu box. Is there something
I could look for in the config.log? owfs was compiled on the target
machine, so everything it builds should be correct. But who knows.
Has anyone seen anything like this before?
For reference, below is a copy of the message I sent this morning to the
Technologic newsgroup.
Thanks,
-Frank
===
I'm trying to compile owfs (http://www.owfs.org) for my TS-7800 and
hitting some issues.
First off, I **think** fuse is supposed to be part of the kernel based
on the version of the TS kernel supplied. I cannot verify that though.
Before I realized fuse was supposed to be part of the kernel, I did
compile version 2.7.2, but it would not load at startup ('Loading fuse
module failed!').
Second, I've gone under the assumption that fuse **is** part of the
kernel, and just compiled owfs to see what would happen. Configure does
find the fuse files (headers, etc).
When I run owfs, I get:
/opt/owfs/bin/owserver: error while loading shared libraries:
/opt/owfs/lib/libow-2.7.so.2: unsupported version 0 of Verneed record
I guess I don't understand how I'm getting an unsupported version when I
compiled this stuff on the 7800 (i.e. not using crosstools).
Is there anything in the config.log that I could be looking at?
Any ideas?
Thanks,
-Frank
Holland, PA
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: What I did exactly now
The output of ps was certainly not showing the whole line... and I'm pretty
sure the script
didn't mount the 1wire filesystem in /tmp/ since the default is to use
/tmp/1wire/ on the NSLU2.
/Christian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthias
Urlichs
Sent: den 6 januari 2008 06:16
To: owfs-developers@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Subject: Re: [Owfs-developers] Fwd: What I did exactly now
Hi,
owfs -P /opt/var/run/owfs.pid -s 4304 /tmp/
Umm, /tmp is for temporary files. Don't mount owfs there.
Your system *will* behave in strange and interesting ways ...
ps ax | grep ow
If you have pstree installed, it shows quite nicely whether the
processes are related.
# pstree | grep ow
|-owserver---owserver---owserver
This is OK (owserver is idle)
|-owserver---owserver---2*[owserver]
OK too (one client is connected).
|-owserver---2*[{owserver}]
On i386/ia64 with glibc, the same thing looks slightly different.
|-owserver
|-owserver
Here, on the other hand, something's seriously broken. :-/
ps axf does the same thing vertically.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
Leave no stone unturned.
-- Euripides
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: What I did exactly now
The default mount-point on the NSLU2 is /mnt/1wire/ . This means that you should look under that directory if you want to find your devices. (ps didn't should the whole path) Finally to test on the NSLU: ls -l /tmp/1wire/ echo 1 /tmp/1wire/05.24202C00/PIO echo 0 /tmp/1wire/05.24202C00/PIO /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 6 januari 2008 05:55 To: owfs-developers@lists.sourceforge.net; [EMAIL PROTECTED] Subject: [Owfs-developers] Fwd: What I did exactly now Hello Bernd, We're getting closer to a solution, I suspect. Seeing multiple copies of the program is an artifact of how Linux handles threads. They are threads of the same program, each ready to process data. So to summarize, you have OWFS installed on an NSLU and can see DS18B20s and DS2405s on the line. You can read temperature, but haven't been able to switch the DS2405. From your laptop, you should be able to see the network: URL: 192.168.1.77:3001 (this is only a guess, the configuration file should have the correct port) If you can install the owshell programs on your laptop, you can try (on your laptop) owdir -s 192.168.1.77:4304 / to see all the devices. to switch the DS2405, type owwrite -s 192.168.1.77:4304 05.24202C00/PIO 1 or owwrite -s 192.168.1.77:4304 05.24202C00/PIO 0 You can also run these commands on the NSLU: owdir owwrite 05.24202C00/PIO 1 owwrite 05.24202C00/PIO 0 Finally to test on the NSLU: ls /tmp echo 1 /tmp/05.24202C00/PIO echo 0 /tmp/05.24202C00/PIO What we're doing to trying to see if the problem is just the owhttpd program (earlier version didn't handle PIO values properly) or owserver itself. Paul Alfille On Jan 5, 2008 5:44 PM, [EMAIL PROTECTED] wrote: Hello Paul! When I login, it says: Welcome to Unslung V2.3R63-uNSLUng-6.8-beta BusyBox v0.60.4 (2005.03.22-06:52-) Built-in shell (ash) Then, I typed what you say (ps ax | grep ow), and these things are running: 414 root 1196 S /usr/sbin/CheckPowerButton = I guess, this is because of the ow in the word Power. 460 root 3936 S owserver -P /opt/var/run/owserver.pid -u -p = This line three times, with different numbers, e.g. 469. Then: 476 root 4460 S owfs -P /opt/var/run/owfs.pid -s 4304 /tmp/ = This line also 3 times. 486 root 5972 S owftpd -P /pt/var/run/owftpd.pid -s 4304 = This line also 3 times. 497 root 3892 S owhttpd -P /opt/var/run/owhttpd.pid -s 4304 = This line also 3 times. And then of course: 530 ttyp0 root 2668 S grep ow Does this help you? What can I do next? Many, many thanks, Bernd --- antwort auf --- von:: Paul Alfille an:: cettl betreff:: Re: What I did exactly now datum:: 05.01.08 01:09 I guess the first question is whether owserver and owhttpd were already started by the initialization scripts. When you telnet in to the NSLU, can you type: ps ax | grep ow that should show you all the running ow... programs. Paul Alfille - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New owfs/temploggerd ipk packages.
The source is available at: http://downloads.sourceforge.net/owfs/temploggerd-1.3.8.tar.gz And also in the CVS-tree... http://owfs.cvs.sourceforge.net/owfs/temploggerd/ /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregg C Levine Sent: den 31 december 2007 17:43 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] New owfs/temploggerd ipk packages. Hello! Good to know. However is the source code for the temploggerd kit available? And where would it be posted to? -- Gregg C Levine [EMAIL PROTECTED] The Force will be with you always. Obi-Wan Kenobi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Magnusson Sent: Monday, December 31, 2007 2:56 AM To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] New owfs/temploggerd ipk packages. Hi all, I just wanted to tell you have I compiled lots of ipk-builds today. The owfs-ipk-packages are updated to version 2.7p2. I have also made some updates to temploggerd, and the current version is now 1.3.8. Temploggerd can now use the owshell-commands instead of fuse+owfs to collect data. Whiterussian RC5 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/packages/ Whiterussian 0.9 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/0.9/packages/ Kamikaze 7.07 (brcm-2.4 with 2.4.34 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze/packages/ Kamikaze 7.07 (brcm47xx-2.6 with 2.6.22 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze-2.6/packages/ Kamikaze 7.07 (atheros-mips with 2.6.21 kernel, uClibc-0.9.28) (for routers such as Atheros) http://owfs.sourceforge.net/openwrt/kamikaze-2.6-atheros/packages/ Midge (adm5120 with 2.4.32 kernel, uClibc-0.9.28) (for routers such as Edimax BR6104KP, http://midge.vlad.org.ua/wiki/SupportedDevices) http://owfs.sourceforge.net/openwrt/midge/packages/ NSLU2, Unslung 6.8 http://owfs.sourceforge.net/nslu2/packages/ Openslug 3.10 http://owfs.sourceforge.net/nslu2/openslug/packages/ Tell me if you have problem to install and use any packages. BTW: I have change the default-port to 4304 in the startup-scripts as well. /Christian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] New owfs/temploggerd ipk packages.
Hi all, I just wanted to tell you have I compiled lots of ipk-builds today. The owfs-ipk-packages are updated to version 2.7p2. I have also made some updates to temploggerd, and the current version is now 1.3.8. Temploggerd can now use the owshell-commands instead of fuse+owfs to collect data. Whiterussian RC5 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/packages/ Whiterussian 0.9 (brcm, 2.4.30 kernel, uClibc-0.9.27) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/0.9/packages/ Kamikaze 7.07 (brcm-2.4 with 2.4.34 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze/packages/ Kamikaze 7.07 (brcm47xx-2.6 with 2.6.22 kernel, uClibc-0.9.28) (for routers such as WRT54G(S), ASUS-WL500gd) http://owfs.sourceforge.net/openwrt/kamikaze-2.6/packages/ Kamikaze 7.07 (atheros-mips with 2.6.21 kernel, uClibc-0.9.28) (for routers such as Atheros) http://owfs.sourceforge.net/openwrt/kamikaze-2.6-atheros/packages/ Midge (adm5120 with 2.4.32 kernel, uClibc-0.9.28) (for routers such as Edimax BR6104KP, http://midge.vlad.org.ua/wiki/SupportedDevices) http://owfs.sourceforge.net/openwrt/midge/packages/ NSLU2, Unslung 6.8 http://owfs.sourceforge.net/nslu2/packages/ http://owfs.sourceforge.net/nslu2/packages/ Openslug 3.10 http://owfs.sourceforge.net/nslu2/openslug/packages/ Tell me if you have problem to install and use any packages. BTW: I have change the default-port to 4304 in the startup-scripts as well. /Christian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2480 Cannot detect DS2480 or LINK interface in 2.7
It seems like a calloc() fails in your case... Did you run out of memory in
your box?
The only way FS_ParsedName_destroy() is called from FS_OWQ_create(), is if
calloc() returns a null-pointer...
Also... Perhaps pn-selected_filetype-ag-elements 0 for some reason?
Thread 1 (process 9294):
#0 0xb7dd7f38 in free () from /lib/tls/libc.so.6
#1 0xb7dd9ddf in malloc () from /lib/tls/libc.so.6
#2 0xb7ddd620 in strdup () from /lib/tls/libc.so.6
#3 0xb7f08263 in FS_ParsedName_destroy () from /usr/lib/libow-2.7.so.1
#4 0xb7f08fe7 in FS_OWQ_create () from /usr/lib/libow-2.7.so.1
#5 0x0804a4b4 in ?? ()
#6 0xb7ead0bd in start_thread () from /lib/tls/libpthread.so.0
#7 0xb7e3dace in clone () from /lib/tls/libc.so.6
/* Create the Parsename structure and load the relevant fields */
int FS_OWQ_create( const char * path, char * buffer, size_t size, off_t
offset, struct one_wire_query * owq )
{
struct parsedname * pn = PN(owq) ;
LEVEL_DEBUG(FS_OWQ_create of %s\n,path) ;
if ( FS_ParsedName(path,pn) ) return -ENOENT ;
OWQ_buffer(owq) = buffer ;
OWQ_size( owq) = size ;
OWQ_offset(owq) = offset ;
if ( pn-extension == EXTENSION_ALL pn-type != ePN_structure ) {
OWQ_array(owq) = calloc((size_t)
pn-selected_filetype-ag-elements, sizeof(union value_object)) ;
if (OWQ_array(owq) == NULL ) {
FS_ParsedName_destroy( pn ) ;
return -ENOMEM ;
}
} else {
OWQ_I(owq) = 0 ;
}
return 0 ;
}
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2480 Cannot detect DS2480 or LINK interface in 2.7
I debugged the code before... and I found a pretty serious bug where void *Tree[6] was defined, but it should be 7 elements in that array. I have fixed this in the CVS, so perhaps this could result into some overwritten memory. /Christian - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2480 Cannot detect DS2480 or LINK interface in 2.7
I think it would be more interesting to look at a core-file. Could you try to generate a core-file and send the output from gdb too? [EMAIL PROTECTED] mag]# tcsh [EMAIL PROTECTED] mag]# limit coredumpsize unlimited (if you are using bash, it should work with ulimit -c unlimited) [EMAIL PROTECTED] mag]# /opt/owfs/bin/owserver --foreground --error_print=2 --error_level=4 -p 4304 -u (wait for owserver to crash, and core-file should be created) [EMAIL PROTECTED] mag]# gdb /opt/owfs/bin/owserver core.12345 (gdb) thread apply all bt And now gdb should show backtrace for all threads which were running... /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Weber Sent: den 19 december 2007 11:04 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] DS2480 Cannot detect DS2480 or LINK interface in 2.7 Hi Paul, OK, it crashed again this morning. I attach the logfile, I guess the problem manifests itself in the repetition of Dec 19 08:47:48 archive OWFS[22354]: Transaction Delay 50 Dec 19 08:47:48 archive OWFS[22354]: Transaction readin = 0 Dec 19 08:47:48 archive OWFS[22354]: Transaction end = 0 I will go back to an older version to see if there is any difference there... Uh, in vers 2.4p1 I get the 'short circuit' error. Michael On Dec 17, 2007 11:38 PM, Paul Alfille [EMAIL PROTECTED] wrote: Do you have any hints about what in pwserver is causing a crash? What type of traffic? Paul Alfille On Dec 17, 2007 4:42 PM, Michael Weber [EMAIL PROTECTED] wrote: Tilman, Everything works now for me. Both with 2.7p1, also the cvs version after Paul made the changes to the 2480 setup code. 2.6p8 also always worked for me (have you tried?) and I still use the 2.4p1 every now and then as reference. I now found out what is causing the troubles on our 1wire-bus: Other electronics (namely a direct-driven telescope), which come close and across the bus wire. Will sort that out next year (use module-sized computers Matrix-500 close to the sensors instead of long wires). Our owserver daemon is crashing freuqently now. That was not the case when we still used 2.4. Michael On Dec 17, 2007 8:47 PM, Tilman Glotzner [EMAIL PROTECTED] wrote: Dear Paul, Also comparing your circuit with the one on page 25 of the DS2480B manual http://datasheets.maxim-ic.com/en/ds/DS2480B.pdf you have the POL pin at ground, and they have it at +VDD. Could you have polarity reversed? The RS232 level converter normally work inverted. Please also take a look at page 25 of the SD2480B manual. The POL pin apparently needs to be connected to ground. I will give a shot though, and test. Also I'm embarrassed to admit that msec_read is no longer implemented (despite being in the man page). It is now --timeout_serial As just the easiest test, can you try with that parameter? (Still, using your exact command line worked for me as well). Result as expected -- no change in behavior. Did Michael is dongle to work ? If so, do you happen to know what he did to make it work ? Thanks Tilman Express yourself instantly with MSN Messenger! MSN Messenger -- --- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marke tplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Dr. Michael Weber Astrophysikalisches Institut Potsdam An der Sternwarte 16 D-14482 Potsdam Tel: 0331 7499 632 Fax: 0331 7499 200 email: [EMAIL PROTECTED] - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marke tplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- --- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marke tplace ___ Owfs-developers mailing list
Re: [Owfs-developers] owfs python wrapper
I have made some updates to the python-module and makefiles now. It seems to work on all platforms I have tested right now, except FC7/x64. I'm not sure why, since the _OW.so can't use contents in libow.so... such as the Global-struct. It must be some bug in Fedoras configuration. Ubunto 6.06.1-amd64 works though.. # uname -a Linux vm-got01 2.6.15-29-amd64-server #1 SMP Mon Sep 24 17:31:58 UTC 2007 x86_64 GNU/Linux # module/swig/python/examples/tree.py --fake=10,10 Simulated-Random - / DS18S20 - /10.67C6697351FF DS18S20 - /10.4AEC29CDBAAB # module/swig/python/examples/temperature.py --fake=10,10 /10.67C6697351FF 36.4784 /10.4AEC29CDBAAB 51.3401 Download and try the latest CVS version... /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Magnusson Sent: den 17 december 2007 22:53 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] owfs python wrapper The tree-structure have changed a bit lately, and /system/adapter/name.0 is replaced with /bus.0/interface/settings/name. Patches need to be done in module/swig/python/ow/__init__.py, but it's not only the change above which is needed... I'm no guru at python, but I'll see if I find any obvious patches which needs to be done. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthias Fuchs Sent: den 17 december 2007 22:12 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] owfs python wrapper Hi, I am just doing my first experiments with owfs-2.7p1 and its python wrapper. Before I start with my problem: owserver with owhttpd works fine and I can access my three DS1820 sensors. When using the python wrapper to get a list of the owfs structure I took a look into the tree.py example and encountered this issue: [EMAIL PROTECTED]:~/owfs-2.7p1/module/swig/python/examples$ python Python 2.5.1 (r251:54863, May 2 2007, 16:56:35) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2 Type help, copyright, credits or license for more information. import ow ow.init(/dev/ttyUSB0) s = ow.Sensor(/) Traceback (most recent call last): File stdin, line 1, in module File usr/lib/python2.5/site-packages/ow/__init__.py, line 258, in __init__ File usr/lib/python2.5/site-packages/ow/__init__.py, line 401, in useCache File usr/lib/python2.5/site-packages/ow/__init__.py, line 146, in _get ow.exUnknownSensor: '/system/adapter/name.0' Shouldn't that work? Python is 2.5.1 under ubuntu 7.06, SWIG Version is 1.3.31 and owfs version is 2.7p1. Either there is something wrong or I misunderstood something. Any hint? Thanks Matthias - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owfs will not start automatically on openwrt (WRT54GL V1.1)
Good to hear that it automatically starts now. I have no idea what it could be... I read some about freifunk, and they seemed to revert to uclibc-0.9.27 8th Aug 2006 to make it compatible to whiterussian rc5. Perhaps you had some old friefunk version which was created before that date? Right now I'm re-compiling all my packages, and you will soon find some new version 2.7p1 which is built from the current cvs. Perhaps this will work better with your serial adapter. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dl5ark Sent: den 17 december 2007 14:21 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] owfs will not start automatically on openwrt (WRT54GL V1.1) Hi, the problem is (partially) solved: I have reinstalled the newest freifunk-firmware from http://download.berlin.freifunk.net/ipkg/_g+gl/ (openwrt-g-freifunk-1.6.22-de.bin). In the next step i am installing again owfs from http://home.mag.cx/openwrt/0.9/packages/ . When i use my first serial (RS232) DS9097-Adapter (passive), also the newest version (and previous) will now automatically run. I can?t say if this is an problem with the previous firmware or what else. But one little problem is always there: When i use my other serial (RS232) DS9097U (with DS2480B) Adapter, i can only use owfs_2.6p6-6_mipsel.ipk and owlib_2.6p6-6_mipsel.ipk, newer versions will not work for me because i never see sensor-contents. Is there a known problem with the DS9097U-Support? Holger - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owfs python wrapper
The tree-structure have changed a bit lately, and /system/adapter/name.0 is replaced with /bus.0/interface/settings/name. Patches need to be done in module/swig/python/ow/__init__.py, but it's not only the change above which is needed... I'm no guru at python, but I'll see if I find any obvious patches which needs to be done. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthias Fuchs Sent: den 17 december 2007 22:12 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] owfs python wrapper Hi, I am just doing my first experiments with owfs-2.7p1 and its python wrapper. Before I start with my problem: owserver with owhttpd works fine and I can access my three DS1820 sensors. When using the python wrapper to get a list of the owfs structure I took a look into the tree.py example and encountered this issue: [EMAIL PROTECTED]:~/owfs-2.7p1/module/swig/python/examples$ python Python 2.5.1 (r251:54863, May 2 2007, 16:56:35) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2 Type help, copyright, credits or license for more information. import ow ow.init(/dev/ttyUSB0) s = ow.Sensor(/) Traceback (most recent call last): File stdin, line 1, in module File usr/lib/python2.5/site-packages/ow/__init__.py, line 258, in __init__ File usr/lib/python2.5/site-packages/ow/__init__.py, line 401, in useCache File usr/lib/python2.5/site-packages/ow/__init__.py, line 146, in _get ow.exUnknownSensor: '/system/adapter/name.0' Shouldn't that work? Python is 2.5.1 under ubuntu 7.06, SWIG Version is 1.3.31 and owfs version is 2.7p1. Either there is something wrong or I misunderstood something. Any hint? Thanks Matthias - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owfs will not start automatically onopenwrt (WRT54GL V1.1)
Some new packages are available at the repositories now. Can you try it? # ipkg update # ipkg install owfs owlib /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Holger Rose Sent: den 17 december 2007 22:46 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] owfs will not start automatically onopenwrt (WRT54GL V1.1) Hello Christian, thanks for your fast answer. On my next reinstall i will test the newer versions of owfs again with the DS9097U. Holger -- From: Christian Magnusson [EMAIL PROTECTED] Sent: Monday, December 17, 2007 8:57 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] owfs will not start automatically onopenwrt(WRT54GLV1.1) Good to hear that it automatically starts now. I have no idea what it could be... I read some about freifunk, and they seemed to revert to uclibc-0.9.27 8th Aug 2006 to make it compatible to whiterussian rc5. Perhaps you had some old friefunk version which was created before that date? Right now I'm re-compiling all my packages, and you will soon find some new version 2.7p1 which is built from the current cvs. Perhaps this will work better with your serial adapter. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dl5ark Sent: den 17 december 2007 14:21 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] owfs will not start automatically on openwrt (WRT54GL V1.1) Hi, the problem is (partially) solved: I have reinstalled the newest freifunk-firmware from http://download.berlin.freifunk.net/ipkg/_g+gl/ (openwrt-g-freifunk-1.6.22-de.bin). In the next step i am installing again owfs from http://home.mag.cx/openwrt/0.9/packages/ . When i use my first serial (RS232) DS9097-Adapter (passive), also the newest version (and previous) will now automatically run. I can?t say if this is an problem with the previous firmware or what else. But one little problem is always there: When i use my other serial (RS232) DS9097U (with DS2480B) Adapter, i can only use owfs_2.6p6-6_mipsel.ipk and owlib_2.6p6-6_mipsel.ipk, newer versions will not work for me because i never see sensor-contents. Is there a known problem with the DS9097U-Support? Holger - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owfs will not start automatically on openwrt (WRT54GL V1.1)
I haven't seen this problem before... Does any of the ow-processes start when you restart your WL-500GP? Or is it only the process owfs which doesn't start completely? Also... Can you look if the module fuse is loaded just after starting up your router? This should be done in the startup-script just before owfs is started. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Holger Rose Sent: den 12 december 2007 17:51 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] owfs will not start automatically on openwrt (WRT54GL V1.1) Hi, i use ofws with a WL-500GP without problems (freifunk firmware). Now i have installed owfs on a WRT54GL V1.1 (also freifunk firmware (http://download.berlin.freifunk.net/ipkg/_g+gl/) - owfs packages from http://home.mag.cx/openwrt/0.9/packages/) and when i start it with run-owfs all is o.k., i can walk through the bus in /tmp/1wire and the sensors. (fuse init (API version 7.2), fuse distribution version: 2.4.2). BUT i see it only when i start run-owfs manually. When i will start it automatically (ENABLESTARTUP=1 in /etc/default/owfs, owftpd, owhttpd, owserver (0644)) i will see the /tmp/1wire directory, but nothing in it. I see no error. When i start it with run-owfs manually again, all is o.k.. The path /usr/bin/run-owfs (0755) is o.k. and the path to /etc/init.d/S70owserver, S80owfs, S80owhttpd, S80owftpd (0755) [start force] is also without a problem. Is this a authorizations-problem (under openwrt?)? Do you know this problem? What can i do? I use owfs_2.6p6-6_mipsel.ipk owlib_2.6p6-6_mipsel.ipk from http://home.mag.cx/openwrt/0.9/packages/, the owfs_2.6p6-7_mipsel.ipk owlib_2.6p6-7_mipsel.ipk will have problems with my LCD, any other newer version did not work for me under openwrt, because i also never see sensor-contents in my /tmp/1wire directory (not the same error as above, here (newer versions) i see the directories, not the sensors; in my premium problem i see nothing in the 1wire directory). Thanks for your help! Holger - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] php_ow
I fixed it in the cvs.. diff -u -r1.29 globals.c --- module/owlib/src/c/globals.c7 Oct 2007 22:57:32 - 1.29 +++ module/owlib/src/c/globals.c4 Nov 2007 07:10:14 - @@ -53,7 +53,7 @@ #endif .opt = 0 , -.progname = One Wire File System , +.progname = NULL , // One Wire File System , Can't allocate here since it's freed .want_background = 1 , .now_background = 0 , -Original Message- From: [EMAIL PROTECTED] [mailto:owfs- [EMAIL PROTECTED] On Behalf Of Thomas Berg Sent: den 3 november 2007 12:37 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] php_ow Hi, I´ve recently compiled owfs with php support and dosen´t get it to work. If I try to run a sample I get this error php owphp_test.php *** glibc detected *** free(): invalid pointer: 0xb6fbe0b0 *** Aborted running on debian etch with PHP5 PHP-script looks like ?php require load_php_OW.php; init( localhost:3001 ); //get( /10.301639010800/present ); finish(); ? and load_php_OW.php is not modified at all. Any ideas? Regards, Thomas Detta E-postbrev har kontrollerats avseende virus. --- -- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Support for Louis Swart's LCD interface broken in latest version of owfs?
What kind of router is it? The USB adapter have changed to use flexible speed, and that could effect you if you have an Asus router. On the other hand, you can always change the setting with: # echo 0 /tmp/1wire/bus.0/system/adapter/overdrive.0 (Regular speed which was used before) # echo 1 /tmp/1wire/bus.0/system/adapter/overdrive.0 (Flexible speed) # echo 2 /tmp/1wire/bus.0/system/adapter/overdrive.0 (Overdrive speed) The serial-port and adapter hasn't changed since 2.6p1. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 6 oktober 2007 06:59 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Support for Louis Swart's LCD interface broken in latest version of owfs? I see that we use different timing (Flexible speed) currently rather than back in 2.6p1 I'll test to see if this is the problem. Paul Alfille On 10/5/07, Erik Freiholtz [EMAIL PROTECTED] wrote: Hi! I've been using Louis Swart's LCD interfaces for years. When trying to use the interface with one of the later versions of owfs (2.6p6 2.6p7) the LCD interface is not found at all. Everything is fine in 2.6p1, I have not tried p2,p3,p4 or p5. Since I use the displays on openwrt-routers it is a little bit tricky to use an old version. I've searched the mailing lists and the web, but I can't even find anyone mention this problem, is this a known bug? Best Regards Erik Freiholtz - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owfs 2.6p7 causing trouble with LCD_H
You can always download the packages manually with wget (or ipk directly) from the directory: http://owfs.sourceforge.net/openwrt/kamikaze/packages/ ipkg remove owlib owfs owshell ipkg install http://owfs.sourceforge.net/openwrt/kamikaze/packages/owfs_2.6p6-8_mipsel.ip k http://owfs.sourceforge.net/openwrt/kamikaze/packages/owlib_2.6p6-8_mipsel.i pk /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Allen Sent: den 5 oktober 2007 05:23 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] owfs 2.6p7 causing trouble with LCD_H I'd like to revert back, but I can't seem to find a p6 ipk for OpenWRT kamikaze. I'm trying to build my own, but I'm running into some issues with the kamikaze build system and p6. In case somebody can help me out, the lines I'm getting that are causing the error are the following: /usr/bin/install -c -d /usr/bin /usr/bin/install -c -m 755 owtap.tcl /usr/bin/owtap /usr/bin/install: cannot create regular file `/usr/bin/owtap': Permission denied On 10/4/07, Gregg C Levine [EMAIL PROTECTED] wrote: Hello! Eric, like you I'm an ordinary user, and sometimes a developer. Of hardware. So I suggest you revert back to the working version for your OpenWRT enabled LinkSys box, and continue with it. However unless you do your own development for the unit, and can make your own binaries then I would suggest to debug the issue and naturally report back here with the obvious solutions and a properly formatted patch. Paul we've got a problem here with these. While I do not use the LCD interface routines, I will be ready to be able to test 2.6p7 for this ongoing issue, naturally talking to regular One-Wire hardware. I'll know more in a few more days. -- Gregg C Levine [EMAIL PROTECTED] The Force will be with you. Always. Obi-Wan Kenobi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Allen Sent: Thursday, October 04, 2007 11:05 PM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] owfs 2.6p7 causing trouble with LCD_H I tried p6 and p7 on the Intel mac. p6 works fine, p7 doesn't. On 10/4/07, Gregg Levine mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On 10/4/07, Eric Allen [EMAIL PROTECTED] wrote: I just tried upgrading to owfs 2.6p7 on my OpenWRT linksys box and discovered that the LCD_H interface to a Hobby Boards LCD now produces garbled output. Clear seems to work the first time, but that's about all the success I can get. I can confirm the same behavior on my mac using the USB 1-wire dongle. 2.6p6 works fine. -Eric Hello! Eric here's an odd suggestion. Try using 2.6p7 on your Mac. Now is this Mac an Intel family member or one of the surviving PowerPC family members? -- Gregg C Levine [EMAIL PROTECTED] This signature was once found posting rude messages in English in the Moscow subway. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems?Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Shell scripts and OWFS
Ok... I was almost sure that Whiterussian RC5 and 0.9 used the same libc and kernel... But there are perhaps some changes between them anyway. This might cause the crashes you have stumbled into. Can you use the other repository which is compiled against the Whiterussian 0.9 source? Update you /etc/ipkg.conf and add the URL: http://owfs.sourceforge.net/openwrt/0.9/packages/ Those packages might work better for you... The latest version is 2.6p6-11 now. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:owfs- [EMAIL PROTECTED] On Behalf Of C4Vette Sent: den 24 september 2007 22:07 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Shell scripts and OWFS Sorry, but still no go. Did all you mentioned to reinstall. Did more testing and found out that the limit is 24 chars. Any more via a 'cat' or 'echo' and owserver dies. Now I know the limit its no big deal; can script to keep within limit. The testfile I used: ABC123456789012345678 aaabbbccc Hardware: ASUS WL500g-Premium OS: OpenWrt White Russian - With X-Wrt Extensions 0.9 Linux 2.4.30 #1 Thu Feb 22 13:58:48 EST 2007 Christian Magnusson-2 wrote: That 2.6p9 at http://owfs.sourceforge.net/openwrt/packages/ contained the fix. Are you sure you have updated the files correctly? Remember that you have to stop all processes before you update the library and binaries. # kill-owfs # (make sure all ow* processes are gone) # ipkg update # ipkg install owlib owfs # (edit /etc/default/owserver) # run-owfs BTW: Can you tell me again which hardware you use, and which distribution you are running on your router? /Christian -- View this message in context: http://www.nabble.com/Shell-scripts-and- OWFS-tf4221305.html#a12867264 Sent from the OWFS - Dev mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Shell scripts and OWFS
BTW: you need to give the -force-reinstall flag to install the same version again... # ipkg -force-reinstall install owfs owlib /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:owfs- [EMAIL PROTECTED] On Behalf Of Christian Magnusson Sent: den 24 september 2007 13:22 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Shell scripts and OWFS That 2.6p9 at http://owfs.sourceforge.net/openwrt/packages/ contained the fix. Are you sure you have updated the files correctly? Remember that you have to stop all processes before you update the library and binaries. # kill-owfs # (make sure all ow* processes are gone) # ipkg update # ipkg install owlib owfs # (edit /etc/default/owserver) # run-owfs BTW: Can you tell me again which hardware you use, and which distribution you are running on your router? /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:owfs- [EMAIL PROTECTED] On Behalf Of C4Vette Sent: den 23 september 2007 21:23 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Shell scripts and OWFS Installed 2.6p6-9 of owlib and owfs. When cat file to 'screen16' owserver still dies. An echo string to 'line16.x' is fine but the same cmd to 'screen16' just blanks the complete LCD but owserver does NOT die. Still owserver 'zombies' when catting e.g. /tmp/passwd but that has to do (I think) with chars it doesn't support because a 'plain' ascii test- file doesn't give any problems. So, what remains: - /FF./screen16 doesn't work at all - cat of file can zombie owserver Ed Christian Magnusson-2 wrote: Paul found a bug, and I have re-compiled the packages. Try the newest packages again. /Christian -- View this message in context: http://www.nabble.com/Shell-scripts- and- OWFS-tf4221305.html#a12849583 Sent from the OWFS - Dev mailing list archive at Nabble.com. - -- -- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers --- -- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: Project to connect WGT634U to 1-wire
I don't have Steve Morgan's address, so could you forward it Paul? I think the problem with FTDI serial adapter could be solved my starting owserver with parameter -8bit. The FTDI adapter doesn't seem to like the 6-bit communication. # owserver -8bit -d /dev/usb/tts/0 -p 3002 Could you try that and tell us if it works? /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 20 september 2007 23:19 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Fwd: Project to connect WGT634U to 1-wire -- Forwarded message -- From: Morgan, Steve H Date: Sep 20, 2007 4:39 PM Subject: Project to connect WGT634U to 1-wire I'm interested in using your library to connect a Netgear WGT634U to a 1-wire temp sensor. I have OPENWRT working fine but have issues with getting the 1-wire connected to the box. Do you recommend using the DS9097 or do you recommend using a DS9490 USB adapter. I have tried to connect a FTDI serial adapter to the Netgear WGT634U and then the DS9097 and just can't seem to get data over the 1-wire interface. I was hoping to get this working and put a how-to out there for others. Is it possible to get some help? Stephen Morgan Enterprise Systems - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Shell scripts and OWFS
Seems to be a buffer overwrite or something. It crash on my wrt54g router now too... [EMAIL PROTECTED]:/etc/default# owread -s 3002 10.061847000800/temperature 28.8125 [EMAIL PROTECTED]:/etc/default# owread -s 3002 FF.71020100/version Error receiving data on FF.71020100/version (owserver crash) [EMAIL PROTECTED]:/etc/default# kill-owfs [EMAIL PROTECTED]:/etc/default# run-owfs [EMAIL PROTECTED]:/etc/default# owwrite -s 3002 FF.71020100/line16.0 test (owserver crash) I have to debug it on my linux-server since I don't have gdb on the router. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:owfs- [EMAIL PROTECTED] On Behalf Of C4Vette Sent: den 17 september 2007 19:40 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Shell scripts and OWFS @ Christian, did an update of the package but still the same problem: owserver becomes a 'zombie'-ps when I 'cat' to FF./screen16. Also when I echo a too long string to screen16 or even line16.[01] the display blanks and won't accept anything until a restart of owserver. For the record; previous version I tried was 2.6p6-7 and today 2.6p6-8 of owfs, owlib and owshell and the box is running whiterussian rc5, 0.9 Works fine if I restrict the output to a max of 16 chars to line16.0 and 16.1 Ed Christian Magnusson-2 wrote: I have compiled the latest cvs-version for WRT54G/Asus (whiterussian rc5, 0.9 and kamikaze). You didn't say which distribution you have. But you might use http://owfs.sourceforge.net/openwrt/packages/ http://owfs.sourceforge.net/openwrt/0.9/packages/ http://owfs.sourceforge.net/openwrt/kamikaze/packages/ depending on your setup. /Christian -- View this message in context: http://www.nabble.com/Shell-scripts-and- OWFS-tf4221305.html#a12740914 Sent from the OWFS - Dev mailing list archive at Nabble.com. --- -- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] MIPS vs MIPSEL in OWFS
BTW: Replacing DTR with Vcc(+resistance) doesn't work as I suggested. DTR should be between -3 -- -15 when the rs232-port is open and ready. This means that you have to use one max3232 pin for converting the Vcc to the negative signal which is a logical 1. /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:owfs- [EMAIL PROTECTED] On Behalf Of suman- Sent: den 16 september 2007 06:15 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] MIPS vs MIPSEL in OWFS Yes, Christian, serial interface in my AP is in TTL level, where I can use MAX3232 with DS9097 (or DS2480 directly as pointed out by njh) for 12v-to-3.3v conversion. Thanks for your (and njh's) useful information ... I will try out these hacks soon! But ... before trying it on AP, I tried it on my PC if I can pull out any information, which I failed. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] MIPS vs MIPSEL in OWFS
BTW: isn't your serial interface in TTL levels? Then you have to get a converter, such as MAX3232 http://www.maxim-ic.com/quick_view2.cfm/qv_pk/1068 to connect the ds9097 adapter. Otherwise the signal level will be inverted to the 1-wire devices. The signal is inverted in terms of electrical polarity. e.g. a ttl low will generate a positive voltage on the RS232 TX output pin, a ttl high will generate a negative RS232 TX. In the http://www.piclist.com/techref/io/serial/rs232sigs.htm rs232 standard, a low electrical level (-3 to -15 volts) is defined as a logic 1, or 'on' or 'high' and is referred to as 'marking.' I guess it would be possible to add logic to read/write inverted levels in OWFS, but that will require lots of re-writing. It's better to make sure you have RS232-levels on your pins. Read some more about serial-console cable at: http://wiki.openwrt.org/OpenWrtDocs/Hardware/Netgear/WGT634U#head-6128a64e71 f6af2e38e2b1e0066d8b3c08d62d2a /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 15 september 2007 07:25 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] MIPS vs MIPSEL in OWFS Lets be systematic. DS9097 or DS9097U Any problems with permissions? (root?) Try running with --error_level=9 --foreground and look at the starting messages. Paul Alfille On 15 Sep 2007 01:05:34 -, suman sarkar [EMAIL PROTECTED] wrote: I tried some voltage sensing with DS2781K Maxim chip, which is connected to a DS9097 serial adapter through RJ11. I've installed all necessary software, but not been able to pull out any information from the mounted directory (/mnt/1wire). My laptop's serial port is set to baud rate 9600. Here is what I did: owfs -d /dev/ttyS0 /mnt/1wire. This command does not give any error, and only creates a 1wire directory, where I can see subdirectories: bus.0, settings, structure, statistics, system, and uncached. Even cat /dev/ttyS0 does not show any information on ttyS0 port. So, I am at a loss ... Is DS2781K a owfs supported device ... or am I missing something? Any help will be helpful. http://adworks.rediff.com/cgi-bin/AdWorks/click.cgi/www.rediff.com/signatur e-home.htm/[EMAIL PROTECTED]/1411820_1405315/1411271/1?PARTNER=3OAS_QUERY= null+target=new+ Error! Filename not specified. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Shell scripts and OWFS
I have compiled the latest cvs-version for WRT54G/Asus (whiterussian rc5, 0.9 and kamikaze). You didn't say which distribution you have. But you might use http://owfs.sourceforge.net/openwrt/packages/ http://owfs.sourceforge.net/openwrt/0.9/packages/ http://owfs.sourceforge.net/openwrt/kamikaze/packages/ depending on your setup. /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: den 15 september 2007 23:14 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Shell scripts and OWFS It needs special compiling, as Gregg says, for the OpenWRT platform. You're right, it's probably better to wait a few days for the code to be prepared for the OpenWRT distribution. Paul Alfille On 9/15/07, C4Vette [EMAIL PROTECTED] wrote: So the 'trouble' is: I'm very thankfull for your effort and would very much like to try the fix but don't like the risc of messing with my box due to my ignorance. Will the fix make it automaticcaly to the new version-release anyway or does it depend on my findings? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] MIPS vs MIPSEL in OWFS
Of course... but I just thought that it was more likely that suman had a max3232 at home, compared to a ds2450 :) The problem should be the signal level in this case. The original drawing at http://owfs.sourceforge.net/adapters.html#Serial requires that you connect the components to a RS232 serial interface (with -15 to 15 Volt). If you are going to connect the 1-wire devices to some TTL levels, then you can find some reference designs at http://pdfserv.maxim-ic.com/en/an/app132.pdf . They don't describe how to connect to a serial TTL port, since they recommend you to use a DS2450B chip. This is to control the slewrate and provide clean signals on the 1-wire bus. Connecting TX to the 1-wire data provide any good signal, and it differs from TTL interface to TTL interface. If you have _very_ small 1-wire network, you might be able to talk to the devices with just 2 resistors if you are lucky. It really depends on how the TX-signal behaves on your serial TTL interface. I can't guarantee that it works for you, but you might try this simple design. +5V-+ | 2200ohm | RX(TTL)-+-- 1-wire data | TX(TTL)--100ohm-+ GND --- 1-wire ground All other people should ignore this schema... It's not recommended to use it. Buy real 1-wire adapter and connect it to a rs232 interface or USB interface instead /Christian -Original Message- From: [EMAIL PROTECTED] [mailto:owfs- [EMAIL PROTECTED] On Behalf Of njh Sent: den 15 september 2007 17:02 To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] MIPS vs MIPSEL in OWFS On Sat, 15 Sep 2007, Christian Magnusson wrote: BTW: isn't your serial interface in TTL levels? Then you have to get a converter, such as MAX3232 However, the Max232 uses a fair amount of power to drive the charge pumps, which you would then just be throwing away. If you just used a DS2480 directly you can connect to TTL level signals avoiding two max232 type level shifters. The DS2480 has a polarity select pin which allows you to ensure the phase is correct. http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2923 njh --- -- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Re :Re: Re :Re: Re :Re: MIPS vs MIPSEL in OWFS
The original schema looks like this. DTR - GND schottky diods, resistance and zener diods. RXD - TXD - But if you are going to replace DTR with Vcc, I think you should add an extra resistance just after Vcc. Otherwise you might break your router if you short Vcc with GND. (+ there will be some mA through the 3.9V zener which requires the resistance to avoid short-circuit). Vcc 100ohm GND + original schema.. RXD - TXD - I don't think you wrote this in your reply. Does anyone else agree with this? /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of suman sarkar Sent: den 13 september 2007 02:28 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Re :Re: Re :Re: Re :Re: MIPS vs MIPSEL in OWFS OK, Christian ... first of all, thanks for your valuable input. If I understand it correctly, only 4 pins (2,3,4,5) of standard DB-9 are used to build an equivalent DS9097 circuit for 1-wire chips, of which DTR (pin 4) connects to 1-wire Data (probably DQ for Maxim 1-wire chip), and RXD (pin 2) connects to 1-wire GND (probably P- for Maxim 1-wire chip). So, with those diodes and resistors in the picture (protection circuit for the 1-wire chip), I've decided to build my own little circuit for 4-pin for my board (and not using off-the-shelf 9-pin DS9097). Conceptually it should work (help me if I am missing anything): DTR (of DB9) is equivalent to Vcc (my board), RX and TX (of DB9) are equivalent to TX and RX (my board), respectively, and GND to GND, of course with an equivalent protection circuit, as shown in the picture. With this (1-wire chip with my own circuit for 4-pin serial above, which I presume will be equivalent to DS9097), I guess owfs would be able to see and mount the /dev/ttyS0, and would NOT complain: Could not detect DS9097. Any input from you will be useful before I jump into it. Another question: what about the other pins of DB9 as shown in the picture? Are they left open, especially handshaking pins like RTS/CTS (pin 7/8)? Thanks. On Wed, 12 Sep 2007 20:16:55 +0200 owfs-developers@lists.sourceforge.net wrote Shouldn't you be able to use Maxim's reference design of a passive 9097 adapter? DTR is there to supply 1-wire bus with power since it's high when serial-port is opened. This could be replaced with Vcc I think. Perhaps an extra 100ohm (just after Vcc) to protect it from short-circuit would be good too. The DTR pin is probably short-protected on all serial-interfaces, but Vcc on your board is probably not. Look at the drawing at: http://owfs.sourceforge.net/adapters.html#Serial Picture: http://owfs.sourceforge.net/adapters/adapter.gif /Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of suman sarkar Sent: den 12 september 2007 01:59 To: owfs-developers@lists.sourceforge.net Subject: [Owfs-developers] Re :Re: Re :Re: MIPS vs MIPSEL in OWFS Hi Christian, Here are some clarifications re: Meraki AP's serial interface. This interface is NOT a regular 9-pin interface (DB9) as you see in WRT54G. It has only 4 pins: Vcc, Tx, Rx, and GND. OWFS can only support DS9097 serial adapter, I presume, which has a regular 9-pin serial configuration. So, any Maxim sensor chip (which is DS2781K in our case), with DS9097 serial adapter CAN NOT be directly fed to the AP's 4-pin interface. It needs some tweaking, I guess. Any suggestion regarding how to make it compatible with a 4-pin interface? Thanks. http://adworks.rediff.com/cgi-bin/AdWorks/click.cgi/www.rediff.com/signatur e-home.htm/[EMAIL PROTECTED]/1436607_1430041/1436126/1?PARTNER=3OAS_QUERY= null%20target=new%20 cashback_rediff_signatureli_578x38 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
