Sorry. X86-64 bit.
I can also downgrade my version to compare.
On Feb 16, 2014 11:23 PM, "Roberto Spadim" <robe...@spadim.com.br> wrote:
> ?!!?!?!? where you get a onewire using x64 hardware?
>
>
> 2014-02-17 0:53 GMT-03:00 Paul Alfille <paul.alfi...@gmail.com>:
>
>> Ahha, the problem for me was that kernel module ds2490 wasn't being
>> install automatically.
>>
>> Now w1 works well (for me X64 kernel 3.11 Ubuntu 13.10)
>>
>> The startup debugging output is:
>>
>> paul@gateway:~$ sudo /opt/owfs/bin/owfs --debug -m 1wire --w1
>> DEBUG MODE
>> libow version:
>> 2.9p2
>> CONNECT: owfs.c:(96) fuse mount point: 1wire
>> DEBUG: ow_avahi_link.c:(71) Avahi support: libavahi-client loaded
>> successfully
>> ... ...
>> CALL: ow_parsename.c:(99) path=[]
>> DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated adapters)
>> DEBUG: fuse_line.c:(82) Added FUSE option 0 OWFS
>> DEBUG: ow_w1_list.c:(54) Sending w1 bus master list message DEBUG:
>> fuse_line.c:(82) Added FUSE option 1 1wire
>>
>> DEBUG: fuse_line.c:(82) Added FUSE option 2 -o
>> DEBUG: fuse_line.c:(82) Added FUSE option 3 direct_io
>> DEBUG: fuse_line.c:(82) Added FUSE option 4 -f
>> DEBUG: fuse_line.c:(82) Added FUSE option 5 -d
>> DEBUG: owfs.c:(121) fuse_mnt_opt=[(null)]
>> DEBUG: ow_w1_send.c:(132) Netlink send -----------------
>> DEBUG: owfs.c:(123) fuse_open_opt=[(null)]
>> NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=5 seq=0|1 pid=30310
>> CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0
>> W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0
>> W1_NETLINK_CMD: NULL w1c field
>> NULL data
>> DEBUG: ow_w1_send.c:(143) NETLINK sent seq=1
>> DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
>> DEBUG: ow_w1_parse.c:(113) Wait to peek at message
>> DEBUG: ow_w1_parse.c:(121) Pre-parse header: 16 bytes len=52 type=3
>> seq=0|1 pid=0
>> DEBUG: ow_w1_parse.c:(142) Netlink read -----------------
>> NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=0|1 pid=0
>> CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=0 len=16 flags=229
>> W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=4 id=15066597
>> W1_NETLINK_CMD: NULL w1c field
>> Byte buffer Data, length=4
>> --000: 01 00 00 00
>> <....>
>> DEBUG: ow_w1_dispatch.c:(88) Netlink message directed to root W1 master
>> DEBUG: ow_w1_dispatch.c:(126) Sending this packet to root bus
>> DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
>> DEBUG: ow_w1_parse.c:(113) Wait to peek at message
>> DEBUG: ow_w1_parse.c:(121) Pre-parse header: 16 bytes len=48 type=3
>> seq=0|1 pid=0
>> DEBUG: ow_w1_parse.c:(142) Netlink read -----------------
>> NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=0 seq=0|1 pid=0
>> CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0
>> W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0
>> W1_NETLINK_CMD: NULL w1c field
>> NULL data
>> DEBUG: ow_w1_dispatch.c:(88) Netlink message directed to root W1 master
>> DEBUG: ow_w1_dispatch.c:(126) Sending this packet to root bus
>> DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
>> DEBUG: ow_w1_parse.c:(113) Wait to peek at message
>> DEBUG: ow_w1_scan.c:(54) Netlink (w1) list all bus masters
>> DEBUG: ow_w1_list.c:(64) W1 List 1 masters
>> DEBUG: ow_w1_addremove.c:(55) Setup structure for w1_bus_master1
>> DEBUG: ow_w1_addremove.c:(80) Request master be added: w1_bus_master1.
>> DEBUG: ow_add_inflight.c:(26) Request master be added: w1_bus_master1
>> DEBUG: ow_w1_scan.c:(54) Netlink (w1) list all bus masters
>> DEBUG: ow_w1_list.c:(64) W1 List 0 masters
>> FUSE library version: 2.9.2
>> nullpath_ok: 0
>> nopath: 0
>> utime_omit_ok: 0
>> unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
>> INIT: 7.22
>> flags=0x0000f7fb
>> max_readahead=0x00020000
>> INIT: 7.19
>> flags=0x00000011
>> max_readahead=0x00020000
>> max_write=0x00020000
>> max_background=0
>> congestion_threshold=0
>> unique: 1, success, outsize: 40
>>
>> And a file listing is:
>> 7E.182100001000 7E.872500001000 7E.E52500001000 alarm bus.1
>> simultaneous structure uncached
>> 7E.5E2000001000 7E.922300001000 81.090330000000 bus.0 settings
>> statistics system
>>
>>
>> (I've been working on EDS devices).
>>
>> So we differ on several features:
>> 1. CPU architecture
>> 2. Bus master
>> 3. Kernel version
>> 4. OWFS version
>>
>> As a first pass -- could you upgrade your OWFS to the current version?
>> That would simplify further testing.
>>
>> Paul Alfille
>>
>>
>> On Sun, Feb 16, 2014 at 10:32 PM, Paul Alfille <paul.alfi...@gmail.com>wrote:
>>
>>> Ok, on a desktop machine with a USB adapter (also supported by w1) I get:
>>>
>>> paul@gateway:~$ sudo /opt/owfs/bin/owfs --debug -m 1wire --w1
>>> DEBUG MODE
>>> libow version:
>>> 2.9p2
>>> CONNECT: owfs.c:(96) fuse mount point: 1wire
>>> DEBUG: ow_avahi_link.c:(71) Avahi support: libavahi-client loaded
>>> successfully
>>> ... (Avahi support lines not shown) ...
>>> CALL: ow_parsename.c:(99) path=[]
>>> DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated
>>> adapters)
>>> DEBUG: fuse_line.c:(82) Added FUSE option 0 OWFS
>>> DEBUG: ow_w1_list.c:(54) Sending w1 bus master list message
>>> DEBUG: fuse_line.c:(82) Added FUSE option 1 1wire
>>> DEBUG: fuse_line.c:(82) Added FUSE option 2 -o
>>> DEBUG: fuse_line.c:(82) Added FUSE option 3 direct_io
>>> DEBUG: fuse_line.c:(82) Added FUSE option 4 -f
>>> DEBUG: fuse_line.c:(82) Added FUSE option 5 -d
>>> DEBUG: owfs.c:(121) fuse_mnt_opt=[(null)]
>>> DEBUG: ow_w1_send.c:(132) Netlink send -----------------
>>> DEBUG: owfs.c:(123) fuse_open_opt=[(null)]
>>> NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=5 seq=0|1 pid=29419
>>> CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0
>>> W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0
>>> W1_NETLINK_CMD: NULL w1c field
>>> NULL data
>>> DEBUG: ow_w1_send.c:(143) NETLINK sent seq=1
>>> DEBUG: ow_w1_dispatch.c:(173) Dispatch loop
>>> DEBUG: ow_w1_parse.c:(113) Wait to peek at message
>>> FUSE library version: 2.9.2
>>> nullpath_ok: 0
>>> nopath: 0
>>> utime_omit_ok: 0
>>> unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
>>> INIT: 7.22
>>> flags=0x0000f7fb
>>> max_readahead=0x00020000
>>> INIT: 7.19
>>> flags=0x00000011
>>> max_readahead=0x00020000
>>> max_write=0x00020000
>>> max_background=0
>>> congestion_threshold=0
>>> unique: 1, success, outsize: 40
>>>
>>> So at least I see some of the W1 messages. As you found, the slaves are
>>> not seen. Curiouser and curiouser.
>>>
>>> I'll investigate.
>>>
>>> Paul
>>>
>>>
>>>
>>> On Sun, Feb 16, 2014 at 5:59 PM, Jim Lill <j...@jimlill.com> wrote:
>>>
>>>>
>>>> I found that power up sequence of stuff on a hub can be important
>>>>
>>>> On 2/13/2014 8:55 AM, Howell, Larry (Contractor) wrote:
>>>> > Hi list,
>>>> >
>>>> > I'm a new owfs user with questions about why I'm not seeing any slave
>>>> devices in the owfs directory. I'm an embedded software engineer working
>>>> on a project that will use DS2430A or DS2431, and DS2505 slave devices to
>>>> store run-time and configuration data. I'm building everything from
>>>> source, including fuse-2.9.2 and owfs-v2.8p15, and have installed them
>>>> under Linux 2.6.35 running on a Freescale i.MX53 (ARM Cortex-A8) CPU. This
>>>> CPU has an integrated 1-wire bus master (OWIRE), which I'm controlling with
>>>> the kernel w1.ko driver. I've mounted owfs at /mnt/1wire with "owfs --w1
>>>> /mnt/1wire" and the directory structure is similar what is described in the
>>>> owfs documentation. When I list /mnt/1-wire/, no device appears in the
>>>> owfs directory structure. It doesn't make any difference if I specify a
>>>> slave device or not when owfs is mounted. A DS2505 and a DS2431 device
>>>> have been connected, one at a time, to the 1-wire bus. In each case, the
>>>> device appears in the /sys/devices/w1\ bus\ master/ directory, but never in
>>>> the owfs directory. It seems likely I'm probably doing something
>>>> incorrectly, but I haven't had any success in discovering the error. Any
>>>> pointers or suggestions would be appreciated very much.
>>>> >
>>>> > Thanks,
>>>> >
>>>> > Larry Howell
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Android apps run on BlackBerry 10
>>>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>>>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>>>> Get your Android app in front of a whole new audience. Start now.
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Owfs-developers mailing list
>>>> Owfs-developers@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Android apps run on BlackBerry 10
>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>> Get your Android app in front of a whole new audience. Start now.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Owfs-developers mailing list
>> Owfs-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>
>
> --
> Roberto Spadim
> SPAEmpresarial
> Eng. Automação e Controle
>
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience. Start now.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
