Nut upsuser - Sep 2019 - raspberry pi and tripplite_usb

i have a OMNIVS1500XL
i have used nut for several years on a full sized pc with no problems
i am trying to get nut working with this ups on a raspberry pi
i tried with a pi 3b running raspbian stretch
i tried with a pi 3b running raspbian buster
i tried plugging the usb cable straight into the pi
i tried using a powered usb hub
i tried rebuilding nut from the source package
all caused the pi to crash after 1/2 days
the crash report always begins with
"Unable to handle kernel paging request at virtual address 30343153"
any suggestions

On Tue, Sep 10, 2019 at 9:40 AM <grumpy at mailfence.com> wrote:
> i have a OMNIVS1500XL
> i have used nut for several years on a full sized pc with no problems
> i am trying to get nut working with this ups on a raspberry pi
> i tried with a pi 3b running raspbian stretch
> i tried with a pi 3b running raspbian buster
> i tried plugging the usb cable straight into the pi
> i tried using a powered usb hub
> i tried rebuilding nut from the source package
> all caused the pi to crash after 1/2 days
> the crash report always begins with
> "Unable to handle kernel paging request at virtual address
30343153"
>
I have two Tripp-Lites at 2 different sites: a SMART2200NET (via serial)
and a SMART2200VS (via USB). Each has a Raspberry Pi 3B acting as the NUT
master for their respective environments. The RPis have run Jesse, Stretch
and now Buster & have been very stable for me. I've always used the
Raspbian packaged version of NUT. Since you've validated the UPS and NUT
with another system, makes it look like the RPi might have an issue--I
wonder about the SD card, might it be the cause of your issues? Most of my
RPis are using SanDisk Extreme 16GB (SDSQXNE-016G-GN6MA) SD cards which
have seemed to be rock solid.

--Larry

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com
           Minneapolis, Minnesota       www.FahnoeTech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190910/4596ab28/attachment.html>

On Sep 10, 2019, at 10:40 AM, grumpy at mailfence.com
wrote:
> 
> i have a OMNIVS1500XL
> i have used nut for several years on a full sized pc with no problems
> i am trying to get nut working with this ups on a raspberry pi
> i tried with a pi 3b running raspbian stretch
> i tried with a pi 3b running raspbian buster
The “unable to handle kernel paging request” points to a kernel driver issue.
What if you try the following suggestion?

https://github.com/raspberrypi/linux/issues/2977#issuecomment-519444888

A useful bit of information would be the output of “lsusb -v -d 09ae:”

Another thing to try is one of the libusb-1.0 branches in Git:
https://github.com/networkupstools/nut/issues/300

One of the branches towards the end of the issue should work. 

Some details on rebuilding from Git are here:
https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu

You will need the libusb-1.0 header package as well. 

https://github.com/raspberrypi/linux/issues/2977#issuecomment-519444888
https://github.com/raspberrypi/
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190910/8431eaf0/attachment.html>

On Tue, 10 Sep 2019, Charles Lepple wrote:
> On Sep 10, 2019, at 10:40 AM, grumpy at mailfence.com wrote:
>>
>> i have a OMNIVS1500XL
>> i have used nut for several years on a full sized pc with no problems
>> i am trying to get nut working with this ups on a raspberry pi
>> i tried with a pi 3b running raspbian stretch
>> i tried with a pi 3b running raspbian buster
>
> The “unable to handle kernel paging request” points to a kernel driver
issue. What if you try the following suggestion?
>
> https://github.com/raspberrypi/linux/issues/2977#issuecomment-519444888
>
> A useful bit of information would be the output of “lsusb -v -d 09ae:”
>
> Another thing to try is one of the libusb-1.0 branches in Git:
https://github.com/networkupstools/nut/issues/300
>
> One of the branches towards the end of the issue should work.
>
> Some details on rebuilding from Git are here:
https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu
>
> You will need the libusb-1.0 header package as well.
>
well after a few weeks of piddle'n i have a solution
building with libusb-1.0 yielded the same results
system crashes
dwc2 works but restricts usb performance
that was not acceptable for the pi i wanted to connect to
so i set up a raspberry pi zero w with dwc2 just for monitoring the ups
i am guessing this driver is not used enough for the author to update