Nut upsdev - Jun 2019 - [EXTERNAL] Re: Fixing Drops With SMART1500LCDXL & USB-HID Driver

On 6/19/19 5:59 AM, Charles Lepple wrote:
>>   
>> “The 62-nut-usbups.rules file looks pretty standard. Do you know if the
changes to 42-usb-hd-pm.rules are needed? It seems like none of the USB devices
would have the right permissions if 62-nut-usbups.rules isn't sufficient
(though this happened in Debian once).”
>>   
>> My means of testing wasn’t the most rigorous, but I did try to use
variable isolation with these changes and some other changes. I could not make
the drops stop without having all 3 of these changes present. I believe a web
search lead me to this udev rule so I’ll dig up the link for context.
> This is starting to make sense, though. The link would be helpful, but no
worries if you can't find it.
>
> I think you mentioned the CentOS version - which kernel version does that
run? ("uname -r" is probably sufficient)
>
>
CentOS 7x uses RedHat's idea of 3.10.0 .. which means it's a heavily 
patched 3.10. And by heavily I mean that in the 4 years since RHEL 7 was 
released, they added tons ( literally thousands ) of backports from 
4.xx, including from 4.18

Latest available kernel in the CentOS 7.6 line is 3.10.0-957.21.2 but 
today we will probably release 3.10.0-957.21.3 which includes the fix 
for TCP SACK.

The public beta of RHEL 7.7 uses 3.10.0-1049 but 7.7 GA will certainly 
use a newer release. I have already in use a beta of 3.10.0-1055



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20190619/868760f7/attachment.html>

Unfortunately I do not use the latest versions of NUT, the driver I
created, solis, was changed, not by me, and now does not work on my
nobreak, which I used to create the driver.

greetings

Silvino B. Magalhaes


Em qua, 19 de jun de 2019 às 03:39, Manuel Wolfshant <
wolfy at nobugconsulting.ro> escreveu:
> On 6/19/19 5:59 AM, Charles Lepple wrote:
>
>
> “The 62-nut-usbups.rules file looks pretty standard. Do you know if the
changes to 42-usb-hd-pm.rules are needed? It seems like none of the USB devices
would have the right permissions if 62-nut-usbups.rules isn't sufficient
(though this happened in Debian once).”
>
> My means of testing wasn’t the most rigorous, but I did try to use variable
isolation with these changes and some other changes. I could not make the drops
stop without having all 3 of these changes present. I believe a web search lead
me to this udev rule so I’ll dig up the link for context.
>
> This is starting to make sense, though. The link would be helpful, but no
worries if you can't find it.
>
> I think you mentioned the CentOS version - which kernel version does that
run? ("uname -r" is probably sufficient)
>
>
>
> CentOS 7x uses RedHat's idea of 3.10.0 .. which means it's a
heavily
> patched 3.10. And by heavily I mean that in the 4 years since RHEL 7 was
> released, they added tons ( literally thousands ) of backports from 4.xx,
> including from 4.18
>
> Latest available kernel in the CentOS 7.6 line is 3.10.0-957.21.2 but
> today we will probably release 3.10.0-957.21.3 which includes the fix for
> TCP SACK.
>
> The public beta of RHEL 7.7 uses 3.10.0-1049 but 7.7 GA will certainly use
> a newer release. I have already in use a beta of 3.10.0-1055
>
>
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20190619/188a8e0a/attachment.html>

On Jun 19, 2019, at 11:56 AM, Silvino Benevides Magalhaes
wrote:
> 
> Unfortunately I do not use the latest versions of NUT, the driver I
created, solis, was changed, not by me, and now does not work on my nobreak,
which I used to create the driver.
> 
> greetings
> 
> Silvino B. Magalhaes
Silvino,

We have had several changes to solis over the years to add new models
(especially after the APC acquisition), and we tried to make sure that the
changes did not break support for other models. However, this is not easy,
especially if we do not have an easy way to test the changes against all
hardware (or emulate in software).

Which versions of the driver worked for you, and which ones did not? Also, what
value of SolisModel does your UPS return? I CC'd some of the other authors.