DO NOT UPDATE TO BRANCH=next KERNEL!!

Support for the UPS PIco HV3.0A, HV3.0B and HV3.0B+, as also Terminal Block products, SD images also for updated hardware HV3.0A/B/B+
tater
Posts: 16
Joined: Wed Feb 08, 2017 7:49 am

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by tater » Tue Feb 21, 2017 5:16 am

Ok, long shot, but heck, maybe it's a clue (apologies if it's totally wrong and misleading):
Pull request back in november for 4.9-rc4:
https://lkml.org/lkml/2016/11/19/298

The following changes since commit bc33b0ca11e3df467777a4fa7639ba488c9d4911:

Linux 4.9-rc4 (2016-11-05 16:23:36 -0700)

are available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current

for you to fetch changes up to ad092de60f865c1ad94221bd06d381ecea446cc8:

i2c: i2c-mux-pca954x: fix deselect enabling for device-tree (2016-11-19 21:49:29 +0100)

----------------------------------------------------------------
Alex Hemme (1):
i2c: i2c-mux-pca954x: fix deselect enabling for device-tree

Linus Walleij (1):
i2c: mux: fix up dependencies

Peter Rosin (1):
i2c: Documentation: i2c-topology: fix minor whitespace nit

Wei Yongjun (1):
i2c: digicolor: use clk_disable_unprepare instead of clk_unprepare

Wolfram Sang (1):
i2c: mux: demux-pinctrl: make drivers with no pinctrl work again

Documentation/i2c/i2c-topology | 4 ++--
drivers/i2c/Kconfig | 1 -
drivers/i2c/busses/i2c-digicolor.c | 2 +-
drivers/i2c/muxes/Kconfig | 1 +
drivers/i2c/muxes/i2c-demux-pinctrl.c | 22 ++++++++++++++++++++--
drivers/i2c/muxes/i2c-mux-pca954x.c | 4 ++--
6 files changed, 26 insertions(+), 8 deletions(-)
[unhandled content-type:application/pgp-signature]
User avatar
Pimaster
Site Admin
Posts: 1615
Joined: Fri Sep 14, 2012 9:50 am

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by Pimaster » Tue Feb 21, 2017 1:56 pm

It is Greek to me, not understand anything, sorry, please explain :-)
Warmest Regards
PiM
---
Designing with Mentor Graphics PADS - www.pads.com
Please read and follow the PiForum rules
http://www.forum.pimodules.com/viewtopic.php?f=13&t=196
---
User avatar
Siewert30SW
Posts: 193
Joined: Fri Jan 06, 2017 9:06 pm
Location: The Netherlands
Contact:

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by Siewert30SW » Tue Feb 21, 2017 2:23 pm

tater wrote:@Siewert,
Go to lkml.org and raise a fuss. Heck, email Linus himself.
It is commandment #1: "The kernel shall not break userspace!!"
I'm serious. He'll go nuts and drag someone through broken glass :)
What are you talking about...
Setup:
- RPi3 - PIco HV3.0A / Domo Beta 3.9XXX / RFXtrx433E / Aeotec Gen5
- RPi3 - PIco HV3.0A / PiHole / PiVPN / NAS / Print Server
- Youless Elec&Gas
- FI9803P Cams
- KD101 detectors
- Zwave & KaKu

MyDomoticz scripts: @GitHub
PIco UPS Toolkit: @GitHub
User avatar
Siewert30SW
Posts: 193
Joined: Fri Jan 06, 2017 9:06 pm
Location: The Netherlands
Contact:

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by Siewert30SW » Tue Feb 21, 2017 8:42 pm

Pimaster wrote:nothing, a lot of analysis to see what is going wrong and where (RPi or PIco), nothing to do with ongoing firmware
Just curious ;-)
Isn't it better to follow the kernel device tree structure feature.
All kernels since the end of December are using this tree.
Means i lot less hassle and more user friendly.
Haven't looked that deep into it yet but looks like the PIco UPS is better of with this and saves issues like we've seen lately.
Setup:
- RPi3 - PIco HV3.0A / Domo Beta 3.9XXX / RFXtrx433E / Aeotec Gen5
- RPi3 - PIco HV3.0A / PiHole / PiVPN / NAS / Print Server
- Youless Elec&Gas
- FI9803P Cams
- KD101 detectors
- Zwave & KaKu

MyDomoticz scripts: @GitHub
PIco UPS Toolkit: @GitHub
tater
Posts: 16
Joined: Wed Feb 08, 2017 7:49 am

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by tater » Wed Feb 22, 2017 1:44 am

Lkml.org is the Linux kernel mailing list; the ongoing discussion between kernel developers.
What I posted was a commit by one of them back in the fall, which changed some i2c things in the 4.9-rc8 version.
I'm not an i2c expert, which is why i say it might be a long shot, but it looked like it could be relevant.

It is also policy of the kernel developers that they do not break userspace.
In other words, if that commit changed kernel things that you were relying upon for your application to work, then that commit is a no-no (even if those "things" were bug fixes).

Anyway, just trying to help. I'll tie off the side discussion now :)
alexsh1
Posts: 83
Joined: Wed Nov 02, 2016 4:46 am

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by alexsh1 » Wed Feb 22, 2017 1:48 am

cresfang wrote:to those who got various weird problem with you new shiny PIco, I advise to try using new raspbian installation.

DO NOT RUN: BRANCH=next rpi-update !!!!

The experimental kernel will generate all those weird issue.
Also, all i2cget command you sent to PIco will return 0xff if you use this experimental kernel.

Wait till PiMaster confirm.

Generally speaking the command rpi-update should never be run on the RPi unless you develop a kernel or a RPI developer.
User avatar
Siewert30SW
Posts: 193
Joined: Fri Jan 06, 2017 9:06 pm
Location: The Netherlands
Contact:

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by Siewert30SW » Wed Feb 22, 2017 1:54 am

alexsh1 wrote:
cresfang wrote:to those who got various weird problem with you new shiny PIco, I advise to try using new raspbian installation.

DO NOT RUN: BRANCH=next rpi-update !!!!

The experimental kernel will generate all those weird issue.
Also, all i2cget command you sent to PIco will return 0xff if you use this experimental kernel.

Wait till PiMaster confirm.

Generally speaking the command rpi-update should never be run on the RPi unless you develop a kernel or a RPI developer.
I know...
Although i'm not a kernel or Rpi dev is still need the beta kernels.
As some features for my home automation run smoother or are only featured when running the beta kernels.
Setup:
- RPi3 - PIco HV3.0A / Domo Beta 3.9XXX / RFXtrx433E / Aeotec Gen5
- RPi3 - PIco HV3.0A / PiHole / PiVPN / NAS / Print Server
- Youless Elec&Gas
- FI9803P Cams
- KD101 detectors
- Zwave & KaKu

MyDomoticz scripts: @GitHub
PIco UPS Toolkit: @GitHub
User avatar
cresfang
Posts: 87
Joined: Mon Aug 29, 2016 11:43 am
Location: Garden of Time

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by cresfang » Wed Feb 22, 2017 5:11 am

tater wrote:Ok, long shot, but heck, maybe it's a clue (apologies if it's totally wrong and misleading):
Pull request back in november for 4.9-rc4:
https://lkml.org/lkml/2016/11/19/298
so indeed they changed something in the i2c section that breaks userspace... :evil:

yeah, next kernel is smoother than the stable.... beta always better in my case.... :D
User avatar
Siewert30SW
Posts: 193
Joined: Fri Jan 06, 2017 9:06 pm
Location: The Netherlands
Contact:

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by Siewert30SW » Wed Feb 22, 2017 1:03 pm

tater wrote:Lkml.org is the Linux kernel mailing list; the ongoing discussion between kernel developers.
What I posted was a commit by one of them back in the fall, which changed some i2c things in the 4.9-rc8 version.
I'm not an i2c expert, which is why i say it might be a long shot, but it looked like it could be relevant.

It is also policy of the kernel developers that they do not break userspace.
In other words, if that commit changed kernel things that you were relying upon for your application to work, then that commit is a no-no (even if those "things" were bug fixes).

Anyway, just trying to help. I'll tie off the side discussion now :)
thx for the clarification... ;)
Setup:
- RPi3 - PIco HV3.0A / Domo Beta 3.9XXX / RFXtrx433E / Aeotec Gen5
- RPi3 - PIco HV3.0A / PiHole / PiVPN / NAS / Print Server
- Youless Elec&Gas
- FI9803P Cams
- KD101 detectors
- Zwave & KaKu

MyDomoticz scripts: @GitHub
PIco UPS Toolkit: @GitHub
User avatar
Siewert30SW
Posts: 193
Joined: Fri Jan 06, 2017 9:06 pm
Location: The Netherlands
Contact:

Re: DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by Siewert30SW » Thu Feb 23, 2017 10:21 pm

For those who still want to run the branch=next kernel or beta 4.9 kernel.
Add dtparam=i2c1_baudrate=10000 to your /boot/config.txt
After reboot it should work, no guarantee but on my side it is working...
Setup:
- RPi3 - PIco HV3.0A / Domo Beta 3.9XXX / RFXtrx433E / Aeotec Gen5
- RPi3 - PIco HV3.0A / PiHole / PiVPN / NAS / Print Server
- Youless Elec&Gas
- FI9803P Cams
- KD101 detectors
- Zwave & KaKu

MyDomoticz scripts: @GitHub
PIco UPS Toolkit: @GitHub
Post Reply