Hi Paul, Mmmm. OK. I previously had fuse2-2.3.0-2.1.2006mdk ( and libfuse2, libfuse2-devel & libfuse2-static-devel) installed. I've now uninstalled those rpms and have compiled and installed fuse-2.5.3. Then recompiled and installed owfs-2.5-p1.
I'm no expert at interpreting ./configure output, so I've pasted the fuse configure out put below. It does contain two lines which may (or may not) be of relevance. ## checking if FUSE is configured in the kernel... no ## checking if kernel has extended attribute support... yes During "make" of fuse, I get the following initial output: ## Making all in kernel ## make[1]: Entering directory `/backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel' ## make -C /usr/src/linux-2.6.12-25mdk SUBDIRS=/backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel modules ## make[2]: Entering directory `/usr/src/linux-2.6.12-25mdk' ## ## WARNING: Symbol version dump /usr/src/linux-2.6.12-25mdk/Module.symvers ## is missing; modules will have no dependencies and modversions. ## ## CC [M] /backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel/dev.o ## CC [M] /backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel/dir.o ## CC [M] /backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel/file.o ## CC [M] /backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel/inode.o ## LD [M] /backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel/fuse.o ## Building modules, stage 2. ## MODPOST ## CC /backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel/fuse.mod.o ## LD [M] /backup/AllProgs/hardware/ibuttons/fuse-2.5.3/kernel/fuse.ko ## make[2]: Leaving directory `/usr/src/linux-2.6.12-25mdk' There are no indications of actual errors during make. At make install, the lines show below are repeated. ## WARNING: Symbol version dump /usr/src/linux-2.6.12-25mdk/Module.symvers ## is missing; modules will have no dependencies and modversions. If i enter the directory 'examples' (in the fuse directory) and run, say, './hello /mnt/onewire', then the cursor simply moves to the next line. I'm not at all sure what I should expect to see. When I then cd /mnt/onewire and type 'ls', the cursor simply moves to the next line, failing to list anything. Nevertheless, assuming all is well with fuse, I reconfigured, recompiled & reinstalled owfs. That seemed to go flawlessly. Output from ./configure included the lines: ## checking fuse.h usability... yes ## checking fuse.h presence... yes ## checking for fuse.h... yes ## checking for fuse_main in -lfuse... yes ## checking For supported FUSE API version... yes ## checking For FUSE version ... 2.2 or later I then restart owfs with the line: '/opt/owfs/bin/owfs -u --mountpoint /mnt/onewire/ --foreground --error_level=9' and see the following output in shell: CONNECT: fuse mount point: /mnt/onewire/ CALL: PARSENAME path=[] CONNECT: Adapter found: 002/002 DEFAULT: Opened USB DS9490 adapter at 002/002. DATA: DS9490_setup_adapter: done (ret=0) DATA: DS9490_overdrive() DEBUG: Start of directory path= device=00 00 00 00 00 00 00 00 DATA: BUS_first: No data will be returned DEBUG: Selecting a path (and device) path= SN=00 00 00 00 00 00 00 00 last path=01 00 00 00 00 00 00 00 DEBUG: Clearing root branch DATA: DS9490_reset DATA: DS9490_reset: ok DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: DS9490_next_both SN found: 81 3C 67 25 00 00 00 8B DEBUG: BUS_next return = 0 81 3C 67 25 00 00 00 8B CONNECT: Good DS1421 tag found for 002/002 DEFAULT: Set DS9490 002/002 unique id to FFFFFF81 3C 67 25 00 00 00 FFFFFF8B DEBUG: fuse_mnt_opt=[(null)] DEBUG: fuse_open_opt=[(null)] unique: 2, opcode: INIT (26), nodeid: 0, insize: 44 INIT: 1.0 INIT: 7.5 unique: 2, error: 0 (Success), outsize: 24 short read on fuse device DEBUG: owfs: ow_exit(0) DEBUG: owfs: LibClose() CALL: Starting Library cleanup CALL: Closing Cache CALL: Closing input devices CONNECT: Closed USB DS9490 adapter at 002/002. ret=0 CALL: Closing outout devices CALL: Finished Library cleanup DEBUG: owfs: call _exit(0) When I check which processes are running, I find that owfs ran briefly. I guess that's the 'owfs: call_exit(0)' line, shown above. Again, going to /mnt/onewire and typing 'ls' simply moves the cursor to a new prompt (no output). Typing 'tree' gives a "dot" on the next line, then a blank (empty) line, then a line saying '0 directories, 0 files', then a new prompt line. Not sure to do from here, besides uninstalling fuse-2.5.3 and reinstalling the rpm versions of fuse2-2.3. But that would put me back where I started. Mmmmm.... Do you think the warning about 'Module.symvers' is likely to be relavant ? Any insights would be greatly appreciated. Cheers, Andrew fuse-2.5.3 ./configure output ############################################################# Script started, file is Fuse_Installation.txt [EMAIL PROTECTED] fuse-2.5.3]$ ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for fork... yes checking for setxattr... yes checking for fdatasync... yes checking for struct stat.st_atim... yes configure: creating ./config.status config.status: creating fuse.pc config.status: creating Makefile config.status: creating lib/Makefile config.status: creating util/Makefile config.status: creating example/Makefile config.status: creating include/Makefile config.status: creating include/config.h config.status: include/config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands configure: configuring in kernel configure: running /bin/sh './configure' --prefix=/usr/local --cache-file=/dev/null --srcdir=. checking for a BSD-compatible install... /usr/bin/install -c checking if FUSE is loaded as a module... yes checking if FUSE module is from official kernel... no checking kernel source directory... /usr/src/linux-2.6.12-25mdk checking kernel build directory... /usr/src/linux-2.6.12-25mdk checking kernel source version... 2.6.12-25mdk checking if FUSE is configured in the kernel... no checking if kernel has extended attribute support... yes checking whether lookup_instantiate_filp is defined... no checking if this is user mode linux... no configure: creating ./config.status config.status: creating Makefile config.status: creating config.h config.status: config.h is unchanged ############################################################# On Thursday 14 September 2006 03:34, Paul Alfille wrote: > Andrew, > > I'm getting suspicious about your FUSE installation. > Fuse has a few simple test programs (under "examples" in the source code). > Can you try them ans see if they work? > > Paul Alfille > > On 9/13/06, E. Kastelijn <[EMAIL PROTECTED]> wrote: > > Andrew, > > > > Here is my working output: > > > > <start> > > [EMAIL PROTECTED] mnt]# /opt/owfs/bin/owfs -u --mountpoint /mnt/1-wire/ > > --foreground --error_level=9 > > CONNECT: fuse mount point: /mnt/1-wire/ > > CALL: PARSENAME path=[] > > CONNECT: Adapter found: 003/002 > > DEFAULT: Opened USB DS9490 adapter at 003/002. > > DATA: DS9490_setup_adapter: done (ret=0) > > DATA: DS9490_overdrive() > > DEBUG: Start of directory path= device=00 00 00 00 00 00 00 00 > > DATA: BUS_first: No data will be returned > > DEBUG: Selecting a path (and device) path= SN=00 00 00 00 00 00 00 00 > > last path=01 00 00 00 00 00 00 00 > > DEBUG: Clearing root branch > > DATA: DS9490_reset > > DATA: DS9490_reset: ok > > DATA: DS9490_reset > > DATA: DS9490_reset: ok > > DEBUG: DS9490_next_both SN found: 26 95 CD 6C 00 00 00 77 > > DEBUG: BUS_next return = 0 26 95 CD 6C 00 00 00 77 > > 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: DS9490_next_both SN found: 81 30 C6 26 00 00 00 80 > > DEBUG: BUS_next return = 0 81 30 C6 26 00 00 00 80 > > CONNECT: Good DS1421 tag found for 003/002 > > DEFAULT: Set DS9490 003/002 unique id to FFFFFF81 30 FFFFFFC6 26 00 00 00 > > FFFFFF80 > > DEBUG: fuse_mnt_opt=[(null)] > > DEBUG: fuse_open_opt=[(null)] > > unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 > > INIT: 7.6 > > INIT: 7.5 > > unique: 1, error: 0 (Success), outsize: 40 > > </start> > > > > I hope it is of any help. > > > > Cheers, > > > > Egon > > > > > Hi Egon, > > > > > > Glad to help. > > > > > > I'm still facing a few challenges with OWFS myself. Basically, I can > > > start > > > owfs OK but when I use 'ls', I get nothing or if I use 'tree' I just > > > get > > > > a > > > > > "dot". So so far, it's useless to me. > > > > > > My shell output is: > > > > > > </start> > > > [EMAIL PROTECTED] onewire]# /opt/owfs/bin/owfs -u --mountpoint > > > > /mnt/onewire/ > > > > > --foreground --error_level=9 > > > CONNECT: fuse mount point: /mnt/onewire/ > > > CALL: PARSENAME path=[] > > > CONNECT: Adapter found: 002/002 > > > DEFAULT: Opened USB DS9490 adapter at 002/002. > > > DATA: DS9490_setup_adapter: done (ret=0) > > > DATA: DS9490_overdrive() > > > DEBUG: Start of directory path= device=00 00 00 00 00 00 00 00 > > > DATA: BUS_first: No data will be returned > > > DEBUG: Selecting a path (and device) path= SN=00 00 00 00 00 00 00 00 > > > last > > > path=01 00 00 00 00 00 00 00 > > > DEBUG: Clearing root branch > > > DATA: DS9490_reset > > > DATA: DS9490_reset: ok > > > DATA: DS9490_reset > > > DATA: DS9490_reset: ok > > > DEBUG: DS9490_next_both SN found: 81 3C 67 25 00 00 00 8B > > > DEBUG: BUS_next return = 0 81 3C 67 25 00 00 00 8B > > > CONNECT: Good DS1421 tag found for 002/002 > > > DEFAULT: Set DS9490 002/002 unique id to FFFFFF81 3C 67 25 00 00 00 > > > FFFFFF8B > > > DEBUG: fuse_mnt_opt=[(null)] > > > DEBUG: fuse_open_opt=[(null)] > > > unique: 2, opcode: INIT (26), nodeid: 0, insize: 44 > > > INIT: 5.1 > > > INIT: 5.1 > > > unique: 2, error: 0 (Success), outsize: 24 > > > unique: 3, opcode: STATFS (17), nodeid: 0, insize: 36 > > > unique: 3, error: 0 (Success), outsize: 64 > > > </start> > > > > > > I wondered if you could please post the shell output that you get when > > > > you > > > > > enter the line: > > > '/opt/owfs/bin/owfs -u --mountpoint /mnt/1-wire/ --foreground > > > --error_level=9' > > > > > > Thanks, > > > > > > Andrew > > > > > > On Wednesday 13 September 2006 22:44, E. Kastelijn wrote: > > >> Andrew, > > >> > > >> You made me very happy! > > >> This solved my problem and owfs now works fine. > > >> > > >> Strange enough I could not find the option you mentioned in the owfs > > > > man > > > > >> page. ;) > > >> > > >> Thanx again! > > >> > > >> kind regards, > > >> > > >> Egon > > >> > > >> > Hi Egon, > > >> > > > >> > I had that problem with owfs until I includeed '--mountpoint' before > > >> > > >> the > > >> > > >> > directoy (thanks Paul). Have you tried that ? > > >> > > > >> > example: > > >> > /opt/owfs/bin/owfs -u --mountpoint /mnt/1-wire/ --foreground > > >> > --error_level=9 > > >> > > > >> > Cheers, > > >> > > > >> > Andrew > > >> > > > >> > On Wednesday 13 September 2006 15:01, E. Kastelijn wrote: > > >> >> Paul, > > >> >> > > >> >> I untarred the source again and configured with "./configure > > >> >> --disable_swig". This gives me the same results: > > >> >> > > >> >> # /opt/owfs/bin/owfs -u /mnt/1-wire/ --foreground --error_level=9 > > >> >> DEFAULT: Not a "character" device /mnt/1-wire/ > > >> >> DEFAULT: Not a "character" device /mnt/1-wire/ > > >> >> (and many more) > > >> >> > > >> >> I have looked into the source code a little and found the message > > >> >> in owlib/src/c/ow_opt.c on line 393. > > >> >> > > >> >> In my opinion the program sees my target mountpoint as an input > > >> > > >> device. > > >> > > >> >> Does it skip the '-u' parameter somehow? > > >> >> > > >> >> kind regards, > > >> >> > > >> >> Egon > > >> >> > > >> >> ps: > > >> >> The strange thing is: After I have runned owfs, my digitemp > > >> > > >> application > > >> > > >> >> can also not access my sensors anymore. > > >> >> > > >> >> > I'll have to find the location of that libusb dependency. > > >> >> > > > >> >> > For now, configure with "./configure --disable_swig" > > >> >> > > > >> >> > Paul > > >> >> > > > >> >> > On 9/5/06, E. Kastelijn <[EMAIL PROTECTED]> wrote: > > > > ------------------------------------------------------------------------ > > > > >> >>- Using Tomcat but need to do more? Need to support web services, > > >> >> security? > > >> >> Get stuff done quickly with pre-integrated technology to make your > > >> > > >> job > > >> > > >> >> easier Download IBM WebSphere Application Server v.1.0.1 based on > > >> > > >> Apache > > >> > > >> >> Geronimo > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > > >> >> _______________________________________________ > > >> >> Owfs-developers mailing list > > >> >> [email protected] > > >> >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > ------------------------------------------------------------------------- > > > > >> Using Tomcat but need to do more? Need to support web services, > > >> security? > > >> Get stuff done quickly with pre-integrated technology to make your job > > >> easier Download IBM WebSphere Application Server v.1.0.1 based on > > > > Apache > > > > >> Geronimo > > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > > >> _______________________________________________ > > >> Owfs-developers mailing list > > >> [email protected] > > >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > Owfs-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
