similar to: ULTRA 2000 ULT33046 configuration

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

I've read through the archives http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-August/001550.htmland http://lists.alioth.debian.org/pipermail/nut-upsuser/2006-August/001558.html. Going through the readme, http://eu1.networkupstools.org/doc/2.2.0/INSTALL.html, I made it to step 8 before the problems started. Originally I had used the usb program supplied with the ups from powercom,

>> I setup apcsmart driver on port /dev/ttyUSB0 in ups.conf and check that runing user=root. >> > user=root is only for testing- this may cause other permissions problems later. It looks like the simplest way to handle this on Debian is to add the system 'nut' user to the 'dialout' group: $ sudo adduser nut dialout > I have been meaning to collect some

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> --- VMware

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> --- VMware

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC : vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> ---

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC : vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> ---

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

I'm rsyncing from an linux box to a win2k box with a precompiled version of rsync for win2k. durring the procces he gives me a lotte of the following errors (with different filenames): rename realother/Maildir/cur/.1005882149.8001_0.nyx.wildape,S=3080:2,.001002 -> realother/Maildir/cur/1005882149.8001_0.nyx.wildape,S=3080:2, : No such file or directory I user the command: rsync -cru

I'm trying to copy file from my samsung flip phone. google has informed me of libmtp and gvfs, but it doesn't seem to be helping. [root at localhost yum.repos.d]# mtp-detect libmtp version: 1.0.1 Listing raw device(s) No raw devices found. [root at localhost yum.repos.d]# In case it helps, I did a diff of ls -R from /dev before and after USB connection: [hennebry at localhost dev]$

hi, i've bought a 750VA orvaldi ups http://en.orvaldi.com/index.php/en/product_catalog/product_view/11/162 which holds my hardware (wifi router, cable modem, quad-core with raid and lcd monitor) for ~15 minutes. pretty nice result for a cheap (~57 euro) home ups. in fact, the vendor software for linux is very old (e.g. requires ancient redhat with qt2), requires db9 port while shipped

This patch adds support for virtual IOMMU to the vmxnet3 module. We switch to DMA consistent mappings for anything we pass to the device. There were a few places where we already did this, but using pci_blah(); these have been fixed to use dma_blah(), along with all new occurrences where we've replaced kmalloc() and friends. Also fix two small bugs: 1) use after free of rq->buf_info in

This patch adds support for virtual IOMMU to the vmxnet3 module. We switch to DMA consistent mappings for anything we pass to the device. There were a few places where we already did this, but using pci_blah(); these have been fixed to use dma_blah(), along with all new occurrences where we've replaced kmalloc() and friends. Also fix two small bugs: 1) use after free of rq->buf_info in

>>>>>>>>>>>>>>><<<<<<<<<<<<<<<< Pheno-Mint upsmon # /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.6.1 Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported by usbhid-ups. Please make sure

We can't just do virt_to_phys() on memory that we pass to the device and expect it to work in presence of a virtual IOMMU. We need to add IOMMU mappings for such DMAs to work correctly. Fix that with pci_alloc_consistent() where possible, or pci_map_single() where the mapping is short-lived or we don't control the allocation (netdev). Also fix two small bugs: 1) use after free of

We can't just do virt_to_phys() on memory that we pass to the device and expect it to work in presence of a virtual IOMMU. We need to add IOMMU mappings for such DMAs to work correctly. Fix that with pci_alloc_consistent() where possible, or pci_map_single() where the mapping is short-lived or we don't control the allocation (netdev). Also fix two small bugs: 1) use after free of

Hi, We have been using 1.9.19-prealpha very successfully for over a year and have just started migrating to 2.0.4b, the environment is Sun Sparc running Solaris 2.5.1 and NT 3.51 & 4.0(/sp3). On the servers that have been upgraded, the log files are filling up with some ominous messages, but curiously, users are not reporting any errors at the moment. The following are characteristic of