Am 03.05.2016 um 04:30 schrieb Juliean Galak:
> It is my understanding that owserver 2.8 doesn't play well with w1.
> I may be wrong on this, but I couldn't get it to work.
>
To state again:
Older owserver et al. do work well with Linux < 3.16rc1. Then, a small
change had been introduced in Linux
It is my understanding that owserver 2.8 doesn't play well with w1. I may be
wrong on this, but I couldn't get it to work.
Juliean.
Sent from my iPad
> On May 2, 2016, at 5:08 PM, Jan Kandziora wrote:
>
>> Am 02.05.2016 um 22:48 schrieb Juliean Galak:
>> Ah! I'm not running Jessie, I'm runn
Am 02.05.2016 um 22:48 schrieb Juliean Galak:
> Ah! I'm not running Jessie, I'm running Wheezy. Under Jessie, I couldn't
> get even w1 by itself to work (I'm also not sure the software I'm planning
> on running works under Jessie).
>
This doesn't explain why you have problems with the owserver-2
Three wires is fine for me.
Do you by chance have a step-by-step procedure for getting this to work,
from a clean install?
Maybe I need to try under Jessie rather than Wheezy...
Thanks,
Juliean.
On Mon, May 2, 2016 at 4:56 PM, John Bass wrote:
> Hello,
>
> I have w1 working under Jessie, usin
Hello,
I have w1 working under Jessie, using either parasitic or all three wires...
Have owfs running only with 3 wires, however no joy under parasitic
John
Sent from my iPhone
On 2 May 2016, at 21:51, Juliean Galak mailto:jga...@gmail.com> > wrote:
Ah! I'm not running Jessie, I'm running Wh
Ah! I'm not running Jessie, I'm running Wheezy. Under Jessie, I couldn't
get even w1 by itself to work (I'm also not sure the software I'm planning
on running works under Jessie).
Juliean.
On Mon, May 2, 2016 at 4:44 PM, Jan Kandziora wrote:
> Am 02.05.2016 um 21:43 schrieb Juliean Galak:
> >
Am 02.05.2016 um 21:43 schrieb Juliean Galak:
>
> Before I do that, what version of Raspbian are you running on the Pi1? If
> it's anything earlier than Wheezy, the solution may not be applicable.
>
It runs the minimal Jessie image from Raspbian packaged at 2016-03-18.
That is, Linux-4.1.19.
But
Jan,
Before I do that, what version of Raspbian are you running on the Pi1? If
it's anything earlier than Wheezy, the solution may not be applicable.
>From what I've heard from others, the earlier kernel versions that run on
the Pi1 didn't have any problems with w1 and owfs coexisting. It was on
Am 30.04.2016 um 22:59 schrieb Jan Kandziora:
> whether the testing repo is there with priority 300. Then
>
> $ sudo apt-get update -t testing owserver owhttpd ow-shell
>
Ah, wrong. Of course it has to read:
$ sudo apt-get install -t testing owserver owhttpd ow-shell
Kind regards
Jan
Am 28.04.2016 um 22:39 schrieb Juliean Galak:
> On Thu, Apr 28, 2016 at 4:20 PM, Jan Kandziora wrote:
>
>> Am 28.04.2016 um 19:53 schrieb Juliean Galak:
>>>
>>> Ok, I found owhttpd.init in that archive, in the rpm/src directory, and
>>> copied it to /etc/init.d/ I then rebooted. No apparent chan
Am 28.04.2016 um 22:39 schrieb Juliean Galak:
> Still doesn't seem to work:
>
> pi@raspberrypi ~/owfs-3.1p1/src/rpm $ sudo service owhttpd start
> owhttpd: unrecognized service
>
> When you say "installing" that file, do you mean simply copying it, with
> "cp", or something more involved? (Sorry
On Thu, Apr 28, 2016 at 4:20 PM, Jan Kandziora wrote:
> Am 28.04.2016 um 19:53 schrieb Juliean Galak:
> >
> > Ok, I found owhttpd.init in that archive, in the rpm/src directory, and
> > copied it to /etc/init.d/ I then rebooted. No apparent change - owhttpd
> > doesn't seem to be running.
> >
>
Am 28.04.2016 um 19:53 schrieb Juliean Galak:
>
> Ok, I found owhttpd.init in that archive, in the rpm/src directory, and
> copied it to /etc/init.d/ I then rebooted. No apparent change - owhttpd
> doesn't seem to be running.
>
You have to activate the service. Installing that file should make the
On Thu, Apr 28, 2016 at 1:38 PM, Jan Kandziora wrote:
> Am 28.04.2016 um 18:19 schrieb Juliean Galak:
> >
> > I am using the debian package.
> >
> > Doing "ls /etc/init.d/" shows me owserver, but nothing about owhttpd.
> Do I
> > need to copy owhttpd.init into that directory? If so, where do I f
Am 28.04.2016 um 18:19 schrieb Juliean Galak:
>
> I am using the debian package.
>
> Doing "ls /etc/init.d/" shows me owserver, but nothing about owhttpd. Do I
> need to copy owhttpd.init into that directory? If so, where do I find it?
>
I extracted it from
http://http.debian.net/debian/pool/m
On Thu, Apr 28, 2016 at 9:01 AM, Jan Kandziora wrote:
> Am 28.04.2016 um 04:15 schrieb Juliean Galak:
> >>> and through a web page.
> >>>
> >> You need the owhttpd to do this. Or you implement it your own.
> >>
> >
> > owhttpd is what I want, but I can't figure out how to start it. "sudo
> > ser
Am 28.04.2016 um 04:15 schrieb Juliean Galak:
>>> and through a web page.
>>>
>> You need the owhttpd to do this. Or you implement it your own.
>>
>
> owhttpd is what I want, but I can't figure out how to start it. "sudo
> service owhttpd start" doesn't work - it says no such service. Before, it
On Wednesday 27 Apr 2016 15:33:07 Juliean Galak wrote:
> Debian's apt-get system installs version 2.8, which doesn't seem to work
> well with w1. It was suggested to me that downloading and building 3.1
> would resolve the issue. I've done so, and it appears to have built
> successfully, but I c
On Wed, Apr 27, 2016 at 10:04 PM, Jan Kandziora wrote:
> Am 28.04.2016 um 03:19 schrieb Juliean Galak:
> > Thanks for the quick reply! I installed the recommended package and
> > everything seemed to install correctly and the owserver started ok.
> >
> > I'd like to be able to access the owfs in
Am 28.04.2016 um 03:19 schrieb Juliean Galak:
> Thanks for the quick reply! I installed the recommended package and
> everything seemed to install correctly and the owserver started ok.
>
> I'd like to be able to access the owfs in two ways - through the file
> system,
>
Ah, don't do this. Really
Thanks for the quick reply! I installed the recommended package and
everything seemed to install correctly and the owserver started ok.
I'd like to be able to access the owfs in two ways - through the file
system, and through a web page. In the past versions of OWFS, that was
enabled by default
Am 27.04.2016 um 21:33 schrieb Juliean Galak:
>
> Debian's apt-get system installs version 2.8, which doesn't seem to work
> well with w1. It was suggested to me that downloading and building 3.1
> would resolve the issue. I've done so, and it appears to have built
> successfully, but I can't fi
If this isn't the right forum for this, I apologize, but I've been banging
my head against this for months and can't seem to resolve it.
I'm trying to run OWFS over the w1 kernel module on a Raspberry Pi 2
running the 3.1 (Wheezy) kernel. (I need to use the w1 module for
compatibility with other
I guess I should have been more specific, sorry for that.
On Raspberry Pi everything works OK with I2C to 1-Wire chips (e.g.
DS2482), the problem is only with the w1 kernel module when the DS18B20
thermometer is connected directly to the GPIO pins of Raspberry Pi.
It is possible to read tempera
I was unaware of the aliases you mentioned, but included with those I
know already:
i2c=i2c_arm=i2c1
i2c_vc=i2c0
Thus, including dtparam=i2c and dtparam=i2c_arm or dtparam=i2c1 is
redundant, as are dtparam=i2c_vc and dtparam=i2c0.
NB, be careful with i2c0. It's really only there to service the
Yes this is related to device tree, I hit it a few weeks back with a new
install. After a lot of digging around I got an answer on the Pi forum,
things have changed and you now need to add
dtparam=i2c1=on
dtparam=i2c0=on
to the end of /boot/config.txt for details see
http://www.raspberrypi.or
I should have looked first. These are w1 driver/owfs issues which I have
no knowledge of. I CAN confirm that owfs works great on RPi2 with an i2c
master, as I mentioned.
C
On 2/23/2015 12:37 AM, Jaroslav SOBOTA wrote:
> Hi everybody,
> I have problems getting OWFS running on Raspberry Pi and ac
I'm running 2.9p5 on with RPi2, DS2483, DS18B20s with no complications.
The only trick is getting the i2c bus up and recognized, but that's just
a matter of putting 'dtparam=i2c=on' in /boot/config.txt (and rebooting
on change). They switched from blacklist alone to using device tree to
selecti
Hi everybody,
I have problems getting OWFS running on Raspberry Pi and according to
the Raspberry Pi forums I'm not alone. It seems that the problems
occurred after Raspbian switched to device tree but I'm no Linux expert.
Can you please have a look at the following posts? Any help would be
wel
29 matches
Mail list logo
