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+
User avatar
cresfang
Posts: 87
Joined: Mon Aug 29, 2016 11:43 am
Location: Garden of Time

DO NOT UPDATE TO BRANCH=next KERNEL!!

Post by cresfang » Sat Feb 18, 2017 5:11 am

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.
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 » Sat Feb 18, 2017 4:31 pm

will work on this tomorrow, after finalize the running tasks
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 1:05 am

Damm...
Just upgrade the beta RPi3 firmware to Linux 4.9.11-v7+ armv7l
And have the same issue.
Anything related in /usr/bin/local/picofssd or something else which i can change to get it working again?
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
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:11 am

checking
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 1:45 am

Pimaster wrote:checking
Thx...
Reverted back to Linux 4.4.50-v7+ armv7l.
Couldn't find a fix that fast as it's time to have my beauty sleep ;-)
I did notice there where some changes to the i2c in the kernel.
sudo i2cdetect -y 1 did detect something, but the deamon just faild to start and started beeping weird.
Any i2c port reading results in a 0xff output.
For sure i hope it's bug in the kernel so we can report it or is it something complete structural change, what do you think Pimaster?
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
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:53 am

This checking needs to put to work again protocol analyzer over i2c
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:00 am

Pimaster wrote:This checking needs to put to work again protocol analyzer over i2c
Which means? :?: ;)
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
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 2:16 am

nothing, a lot of analysis to see what is going wrong and where (RPi or PIco), nothing to do with ongoing firmware
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:19 am

Pimaster wrote:nothing, a lot of analysis to see what is going wrong and where (RPi or PIco), nothing to do with ongoing firmware
thx...
Meanwhile i also put my question on the raspberry forum to see if they have a answer on what has been changed regarding i2c.
Reverted back to 4.4.50 which is working like a charm.
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 » Tue Feb 21, 2017 5:09 am

@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 :)
Post Reply