search for: cua0

Displaying 7 results from an estimated 7 matches for "cua0".

Did you mean: cfa0
2005 Nov 11
2
Powerware 9125 - bcmxcp - shutdown problem
Hi, just through setting up nut-2.0.2 I ran into a shutdown problem. As I have already spend some time on it and don't know any further, I like to ask for advice. Situation: Powerware 9125 serially connected using /dev/cua0 nut compiled and installed fine system shall - broadcast a message and shut down if ups on battery for 30+ s - wait 120 s - broadcast another message - give system 120 s to shut down, then power off bcmxcp is running as /usr/bin/bcmxcp -a PW9125 with ups.conf [PW9125] driver = bcmxcp port = /dev/c...
2004 Oct 09
0
zoom flash upgrade via serial port with wine
Wine version: Wine 20040914 Config:....... [serialports] "Com1" = "/dev/cua0, 38400" "Com2" = "/dev/ttyS1, 38400" "Com3" = "/dev/ttyS2, 38400" "Com4" = "/dev/modem, 38400" I added the 38400's later. I have been trying to run a zoom modem flash upgrade application on Linux with wine (No native windows so...
2017 Feb 13
0
Bug with zlib version checking for zlib >= 1.2.10, R version 3.3.2
...NIX-ALIKE * The configure check for the zlib version is now robust to versions longer than 5 characters, including 1.2.10. in SVN r71889 (2017-01-03): https://github.com/wch/r-source/commit/a0fe05ce9d0937ad2334bb370785cb22c71e592b /Henrik On Sun, Feb 12, 2017 at 3:51 PM, Justin Bed? <cu at cua0.org> wrote: > > Hi, > > Posting here as bugzilla is closed to registration. > The zlib version checking code does not handle double digits for the > patch version in the semantic versioning scheme. Consequently, a > ./configure fails when using a zlib version ? 1.5.10. I sug...
2017 Feb 12
2
Bug with zlib version checking for zlib >= 1.2.10, R version 3.3.2
Hi, Posting here as bugzilla is closed to registration. The zlib version checking code does not handle double digits for the patch version in the semantic versioning scheme. Consequently, a ./configure fails when using a zlib version ? 1.5.10. I suggest something like the following patch: --- a/m4/R.m4 +++ b/m4/R.m4 @@ -3116,7 +3116,7 @@ int main() { #ifdef ZLIB_VERSION /* Work around Debian
2002 Feb 23
2
wine-users digest, Vol 1 #1005 - 6 msgs
...quot; "midimap.drv" = "builtin, native" "wnaspi32" = "builtin" "icmp" = "builtin" [fonts] "Resolution" = "96" "Default" = "-adobe-times-" [serialports] "Com1" = "/dev/cua0" "Com2" = "/dev/cua1" "Com3" = "/dev/cua2" "Com4" = "/dev/cua3" [parallelports] "Lpt1" = "/dev/lp0" "LPT1:" = "|lpr" [WinMM] "Drivers" = "wineoss.drv" "WaveMapper&qu...
2008 Aug 11
0
Nouveau takes 100% CPU on startx but does not show anything on GeForce FX 5200
..." # Option "Protocol" "MouseMan" # Option "Device" "/dev/mouse2" # EndSection # # Section "InputDevice" # Identifier "spaceball" # Driver "magellan" # Option "Device" "/dev/cua0" # EndSection # # Section "InputDevice" # Identifier "spaceball2" # Driver "spaceorb" # Option "Device" "/dev/cua0" # EndSection # # Section "InputDevice" # Identifier "touchscreen0" # Driver "microtouch&...
2005 Oct 26
1
Error message with fbt::copen:entry probe
All, The attached script is causing the following error message ... bash-3.00# ./zmon_bug.d dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry): invalid address (0xfd91747f) in predicate at DIF offset 120 dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry): invalid address (0xfef81a3f) in predicate at DIF offset 120 Any ideas? thxs Joe --