Displaying 4 results from an estimated 4 matches for "primax".
Did you mean:
prima
2025 May 11
2
UPS configuration issue?
...port = auto
vendorid = 0001
productid = 0000
bus = 002
protocol = hunnox
subdriver = hunnox
The UPS is Digitech 650va
[root at mustang ups]# lsusb
Bus 001 Device 005: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth
Bus 001 Device 006: ID 0461:4e70 Primax Electronics, Ltd
Bus 001 Device 003: ID 04ca:007d Lite-On Technology Corp.
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda...
2014 Mar 18
2
USB to Ethernet problem
...b
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0b95:772b ASIX Electronics Corp. AX88772B
Bus 001 Device 004: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 001 Device 005: ID 0a5c:21bc Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR
Bus 001 Device 006: ID 0c45:643e Microdia
Bus 002 Device 003: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138 Card Reader Controller
[root at gpcentospc1 ~]# ping 192.168.1.1
PI...
2012 Jun 28
8
GPLPV, clock drift and PVUSB in Windows XP HVM
1. Shouldn''t the GPLPV drivers take care of the (bad) clock drift I''m experiencing in my Windows XP HVM? Or is there some other way around this problem that I haven''t been able to find on Google? How can I tell if the GPLPV drivers are active? I''ve added the /gplpv switch to the boot.ini file and the virtual NIC is definitely using the GPLPV version but other
2006 Oct 16
1
Uneven CPU speed with CentOS 4.4 on a Mac Pro
Hi list,
I've recently managed to install CentOS 4.4 on an Apple Mac Pro.
Functionality-wise everything works great, but when trying to benchmark
the system, I don't get stable runtimes, they differ by more than 30%.
For example a benchmark run with our PDE solving code takes between 500
and 800 s on the completely unloaded machine.
Suspicious kernel output (complete output attached):