On 2025-03-23, Chaz Kettleson <c...@pyr3x.com> wrote:
> On Sun, Mar 23, 2025 at 08:14:56AM -0700, Steve Williams wrote:
>>
>> Following the pkg-readmes/apcupsd:
>>
>>
>> The option with fewest side-effects is to add the following entries to
>> the table in /sys/dev/usb/usb_quirks.c and build a new kernel:
>>
>> { USB_VENDOR_APC, USB_PRODUCT_APC_UPS, ANY, { UQ_BAD_HID }},
>> { USB_VENDOR_APC, USB_PRODUCT_APC_UPS5G, ANY, { UQ_BAD_HID }},
>>
>> If I compile my own kernel with the above settings, and it resolves the
>> problem, will that break "syspatch". Can I keep syspatch compatibility by
>> following any specific steps?
Yes that will break syspatch, you would need to apply patches manually, or
reboot onto an unmodified kernel, syspatch, update /sys and build a new
modified kernel.
> You can create a /etc/bsd.re-config and disable upd/uhidev without
> compiling a new kernel. However, if you use a usb keyboard it will not
> work. I usually just boot -c and disable upd/uhidev, this way I can
> reboot with a working keyboard if I need to.
>
> See bsd.re-config(5)
Might be worth trying just 'disable upd' and see if that's enough to get
apcupsd to run, maybe you'll get lucky..
--
Please keep replies on the mailing list.
