similar to: Assertion ''l1e_get_pfn(MAPCACHE_L1ENT(hashent->idx)) == hashent->mfn'' failed at domain_page.c:203

Hey I wanted to try my hand at doing some GPU passthrough so on my ASUS M5A97 which in the pass worked with an older BIOS (but said BIOS had issues after S3 suspend) - but with a BIOS the PCI passthrough does not work. That is due to:: (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization

On 10/30/2017 03:19 PM, Alexa Catalin wrote: > System: Cenots Linux 6.9 > Application: nut-2.7.5-0.20170613gitb1314c6? [with usb 0.1 from distro] > Device:??Mustek PowerMust 1060 LCD > Comunication log file: dump.txt > > We are looking at the possibility of successful communicating with > this device UPS?Mustek PowerMust 1060 LCD. > > PS: wolfy on the list gives me

System: Cenots Linux 6.9 Application: nut-2.7.5-0.20170613gitb1314c6 [with usb 0.1 from distro] Device: Mustek PowerMust 1060 LCD Comunication log file: dump.txt We are looking at the possibility of successful communicating with this device UPS Mustek PowerMust 1060 LCD. PS: wolfy on the list gives me assistance and i can install any new compiled nut version from sources. Thanks, Catalin.

OK, from this build I get the following: # /usr/local/ups/bin/usbhid-ups -a ups -DDDD Network UPS Tools - Generic HID driver 0.53 (v2.7.4-603-gb14c3b42.7.4.1) USB communication driver 0.37 0.000000 [D1] debug level is '4' 0.001299 [D1] upsdrv_initups... 0.001450 [D2] nut_libusb_open: checking device 1 of 1. 0.033333 [D2] nut_libusb_open: - VendorID: 09ae.

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

So... determining that FD is to be reaped proved hard. Internet lore suggests fcntl() and poll() on the FD, but it just seems valid to them. The errno is also usually not raised (once I saw a "111: Connection refused" though). So the best dumb idea so far is to bail out if we spent the whole loop (128 attempts) and only got zero-sized read replies and no errors.

So... determining that FD is to be reaped proved hard. Internet lore suggests fcntl() and poll() on the FD, but it just seems valid to them. The errno is also usually not raised (once I saw a "111: Connection refused" though). So the best dumb idea so far is to bail out if we spent the whole loop (128 attempts) and only got zero-sized read replies and no errors.

Hello On 06/14/2017 03:32 PM, Arnaud Quette wrote: > > > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro > <mailto:wolfy at nobugconsulting.ro>> wrote: > >> > >> > If that matters, the OS is a fully updated CentOS 6.9 >> and this (latest stable ) version of nut was packaged by me. >>

On 06/19/2017 11:02 AM, Manuel Wolfshant wrote: > Thank a lot ! > Now, conclusions after attempting builds ( with no docs included since > attempting to enable them triggers the errors related to missing or > too old tools mentioned by me in an earlier message ) > - building against libsub 1.0 triggers the following 2 errors : > nutdrv_qx-nutdrv_qx.o: In function

Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x

I am experiencing some problems at working with lists at high level. In the following "coef" contains the original DWT coefficients organized in a list. Thorugh applying the following two commands: coef.abs <- lapply(unlist(coef,recursive=FALSE,use.names =TRUE),abs) coef.abs.sorted <- sort(unlist(coef.abs),decreasing=TRUE) I get vector "coef.abs.sorted" containing

Dear R-list members, I've had a hard time trying to solve a non-linear system (nls) of equations which structure for the equation i, i=1,...,4, is as follows: f_i(d_1,d_2,d_3,d_4)-k_i(l,m,s) = 0 (1) In the expression above, both f_i and k_i are known functions and l, m and s are known constants. I would like to estimate the vector d=(d_1,d_2,d_3,d_4) which is solution

Also, just in case - are you in a virtualized environment? Is there (intentional or not) USB pass-through to the UPSes? My hint is, we had cases where a host or guest grabbed the device but it was not apparent from the part of system running NUT. Jim On Fri, Mar 24, 2023, 23:23 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Sounds like some other program is holding the port. Have

After "No device" error the driver does not seem to be able to communicate with the UPS (as seen before with the port build): # /usr/local/ups/bin/usbhid-ups -a ups -DDDD -u root Network UPS Tools - Generic HID driver 0.53 (v2.7.4-603-gb14c3b42.7.4.1) USB communication driver 0.37 0.000000 [D1] debug level is '4' 0.002560 [D1] upsdrv_initups... 0.002748

=BE=B4=C6=F4=D5=DF=A3=BA =A1=B0=B5=DA=CB=C4=BD=EC=B1=B1=BE=A9=B3=AF=D1=F4=B9=FA=BC=CA=C9=CC=CE=F1= =BD=DA=A1=B1=BD=AB=D3=DA2003=C4=EA10=D4=C2=D4=DA=B1=B1=BE=A9=BE=D9=B0=EC=A1= =A3=BD=EC=CA=B1=A3=AC=B9=FA=BC=D2=C1=EC=B5=BC=C8=CB=A1=A2=CD=E2=B9=FA=D5=FE= =D2=AA=BA=CD=C0=B4=D7=D4=C3=C0=A1=A2=B5=C2=A1=A2=B7=A8=A1=A2=B0=C4=B4=F3=C0=

Sounds like some other program is holding the port. Have you stopped other NUT drivers for the device (e.g. via auto-resuscitating services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)? On Fri, Mar 24,

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)