Temperature from DS18B20

No, Igor, I am offending purely destroyed and shameful OS which tries to work, but it can’t.
And you have your own financial reasons to put it that way and you will never do anything positive about that. Everybody knows that. You are doomed to failure. Forever.

I am in IT since 1985 and I am judging a substitute (Armbian) of a Linux OS. Because I can. I spent month with Armbian and I will never come back to it. Your advertising of this system in my posts is not welcome.

I will be using everything else than Armbian and I will much more happy with my choice - I know that now and I will know that later.

Don’t offend yourself by defending poor OS. That means if you defend it - you have reasons for that defence.

I put you in ignore state as I cannot handle that much loads of bs.

Features that doesn’t work in this shameful OS, doesn’t work in any other. This means you are bashing all open source community work. You have no rights to do that.

This FAQ can unblind you a bit:
https://docs.armbian.com/User-Guide_FAQ/

… except in OS that is build with a proprietary kernel that makes you happy, but is not acceptable by many, but for other reasons. If you don’t understand that, perhaps you need to do some education. You think you are too old for that? You think you know it all? Do you think people that knew how to assemble computer in 1995 doesn’t require update on primer reality? I have 10 years of experiences with embedded Linux out of 30 years of Linux. I was running Unix server before Linus released Linux. But I understand my limits - there are a lot smarter people then me in the group that is making that shameful OS. And around that. Which is again - your only alternative. How the only alternative be such a big shit? Perhaps there is something you don’t understand?

Its dirty cheap to provide “non shameful OS” with the same static smelly hardware interface, where all chip hardware function works but many other features doesn’t. That doesn’t make one professional and the other one amateur. While the truth is right the opposite. Its always a trade and with Armbian, this is stated clearly - you should know what you are getting. Armbian is a build system first. HW functions are HW vendor expenses and their responsibility, not from shameful OS. If you can’t get that, there is really waste of time discussion with you.

You are clearly not a customer, since you expect others to waste money for your problems. You purchased hardware and you want top software support for your money even most of the software is community work. Good luck … I don’t care what OS you will use. But if you will be bashing our community work, I will say speak up.

https://si.linkedin.com/in/igorpecovnik

O Stuard, what do you do for living?

Nothing as disabled now for 20 years, but never was a professional bull shitter either.

I see. Makes sense.

These opinions are my own and not of the imaginary man in the sky” or do you like “Opinions are my own and not the views of my employer” better?

I never served as politician or similar and I am not paid to provide opinions. See? Both of us are just amateur bull shitters :wink: Professionals are quiet and does the job.

Imagine that random people that are not your friends, have no intention to become, not your clients to be, would every day fight with you to steal your time for their purpose. Because they are just lazy, disrespectful, stupid, … This BS you are referring to is defending, fighting, reasoning, clarification, … its a part of the job people say and this is unlikely to change. Regardless of what you or me thinks about all this.

I have been struggling to get DS18B20 sensors working on a new Rock 4C+ board, using the latest Radxa Ubuntu Focal release and 4.4.194-11-rk3399 kernel (and a whole heap of other distros/kernels). Sensors confirmed working with same setup on a Pi4B.

On 4C+ the sensor is detected and listed under /sys/bus/w1/devices/ however on reading w1_slave the data returned is corrupt/invalid, eg

ff ff ff ff ff ff ff ff ff : crc=c9 NO
00 00 00 00 00 00 00 00 00 t=-62

After much searching and head banging, I came across a hint in another forum (for a different board) that cpu frequency scaling may be an issue… further experimentation has led me to insert the following line into /etc/rc.local which seems to resolve the issue with reading 1-wire DS18B20 sensors, for me at least :slight_smile:

echo 600000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq

@Stephen I’ve seen you reply to a number of related issues/queries, may be of interest.

1 Like