search for: 0e0f

...ups.timer.shutdown: -1 ups.vendorid: 051d ============================================= lsusb shows this info about usb bus: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ============================================= usb-devices returns this: T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 D:...

...ups.timer.shutdown: -1 ups.vendorid: 051d ============================================= lsusb shows this info about usb bus: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ============================================= usb-devices returns this: T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 D:...

...01-27 17:38:56 +0100 x86_64 x86_64 x86_64 GNU/Linux joavma01:/usr/local/ups/bin # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 051d:0003 American Power Conversion UPS Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub joavma01:/usr/local/ups/bin # usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=02.06 S: Manufacturer=Linux 2.6.32.54-0.3-default ehci_hcd S:...

...o the same server, total of 3 UPSes. I see from nut documentation that for driver blazer_usb I can specify a Bus parameter. root at nagios:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 046: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 002 Device 085: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 002 Device 098: ID 0665:5161 Cypress Semiconductor USB to Seria...

...ups.timer.shutdown: -1 ups.vendorid: 051d ============================================= lsusb shows this info about usb bus: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ============================================= usb-devices returns this: T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 D:...

...n_GB.UTF-8/en_GB.UTF-8/en_GB.UTF-8/C/en_GB.UTF-8/en_GB.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base The same behaviour occurs under R 2.15.1 on a Linux server. In case the attached file is somehow corrupted, here is a hexdump: 00000000: 0b0c 0e0f 1011 1213 1415 1617 1819 1a1b ................ 00000010: 1c1d 1e1f 2021 2223 2425 2627 2829 2a2b .... !"#$%&'()*+ 00000020: 2c2d 2e2f 3031 3233 3435 3637 3839 3a3b ,-./0123456789:; 00000030: 3c3d 3e3f 4041 4243 4445 4647 4849 4a4b <=>?@ABCDEFGHIJK 00000040: 4c4d 4e4f 5051 525...

...rs usb_os_find_devices: Found 002 on 002 usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Bus 002 Device 002: ID 0e0f:0002 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub =========================================== From: Greg Sent: Thursday, May 07, 2009 9:22 PM To: Arnaud Quette Cc: Kjell Claesson ; nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115...

...1.114853] pci 0000:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 63.008 Gb/s with 8.0 GT/s PCIe x8 link) [ 1.115022] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 1.115125] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 [ 1.115184] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] [ 1.119065] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 1.119120] pci 0000:00:00.0: BAR 9: assigned [mem 0x600000000-0x60bffffff 64bit pref] [ 1.119151] pci 0000:00:00.0: BAR 8:...

...tput of the log files: dmesg: usbcore: registered new driver rndis_host usbcore: registered new driver cdc_acm drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters lsusb: Bus 002 Device 002: ID 0421:0359 Nokia Mobile Phones Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 I will need the phone to send SMS (Nagios). Can someone help me to get this thing running? Thx Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lis...

...CIe bandwidth, > > limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 63.008 > > Gb/s with 8.0 GT/s PCIe x8 link) > > [ 1.115022] pci 0000:01:00.0: vgaarb: VGA device added: > > decodes=io+mem,owns=none,locks=none > > [ 1.115125] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 > > [ 1.115184] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > > [ 1.119065] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > > [ 1.119120] pci 0000:00:00.0: BAR 9: assigned [mem > > 0x600000000-0x60bffffff 64bit pref]...

..._GB.UTF-8 > attached base packages: [1] stats graphics grDevices utils > datasets methods base > The same behaviour occurs under R 2.15.1 on a Linux > server. > In case the attached file is somehow corrupted, here is a > hexdump: > 00000000: 0b0c 0e0f 1011 1213 1415 1617 1819 1a1b > ................ 00000010: 1c1d 1e1f 2021 2223 2425 2627 > 2829 2a2b .... !"#$%&'()*+ 00000020: 2c2d 2e2f 3031 3233 > 3435 3637 3839 3a3b ,-./0123456789:; 00000030: 3c3d 3e3f > 4041 4243 4445 4647 4849 4a4b <=>?@ABCDEFG...

...13] pci 0000:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x1 link at 0000:00:01.0 (capable of 32.000 Gb/s with 5 GT/s x8 link) > > [ 6.483463] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none > > [ 6.483556] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 > > [ 6.483648] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > > [ 6.485344] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > > [ 6.485368] pci_bus 0000:00: 1-byte config write to 0000:00:01.0 offset 0x1a may corrupt adjacen...

...ving this as a fallback if it comes up again. Below is output from the virtual machine: [npg at localhost ~]$ uname -r 3.10.0-957.el7.x86_64 [npg at localhost ~]$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 014: ID 09ae:2012 Tripp Lite Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [npg at localhost ~]$ upsd -V Network UPS Tools upsd 2.7.2 [npg at localhost ~]$ upsc TrippLiteUPS battery.charge: 100 battery.runtime: 3840 b...

...0: 4.000 Gb/s available PCIe bandwidth, > limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 63.008 > Gb/s with 8.0 GT/s PCIe x8 link) > [ 1.115022] pci 0000:01:00.0: vgaarb: VGA device added: > decodes=io+mem,owns=none,locks=none > [ 1.115125] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 > [ 1.115184] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > [ 1.119065] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > [ 1.119120] pci 0000:00:00.0: BAR 9: assigned [mem > 0x600000000-0x60bffffff 64bit pref] > [ 1.119151]...

Ok, so I have made some progress that seems to suggest the initial “fix” I stumbled upon isn’t required. I haven’t yet worked backwards to figure out reasons why our customers have had similar complaints or solve the problem on the CentOS VM yet, but that is on the todo list. I am hoping it ends up just being not enabling the service on startup, but I can’t say that explains away all the symptoms

...6.483313] pci 0000:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x1 link at 0000:00:01.0 (capable of 32.000 Gb/s with 5 GT/s x8 link) > [ 6.483463] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none > [ 6.483556] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 > [ 6.483648] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > [ 6.485344] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > [ 6.485368] pci_bus 0000:00: 1-byte config write to 0000:00:01.0 offset 0x1a may corrupt adjacent RW1C bits &gt...

...> limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 63.008 > > > Gb/s with 8.0 GT/s PCIe x8 link) > > > [ 1.115022] pci 0000:01:00.0: vgaarb: VGA device added: > > > decodes=io+mem,owns=none,locks=none > > > [ 1.115125] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 > > > [ 1.115184] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > > > [ 1.119065] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > > > [ 1.119120] pci 0000:00:00.0: BAR 9: assigned [mem > > > 0x600000000-0x6...

...00:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x1 link at 0000:00:01.0 (capable of 32.000 Gb/s with 5 GT/s x8 link) > > > [ 6.483463] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none > > > [ 6.483556] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 > > > [ 6.483648] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > > > [ 6.485344] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > > > [ 6.485368] pci_bus 0000:00: 1-byte config write to 0000:00:01.0 offset 0x1a may...

...00:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x1 link at 0000:00:01.0 (capable of 32.000 Gb/s with 5 GT/s x8 link) > > > [ 6.483463] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none > > > [ 6.483556] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 > > > [ 6.483648] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > > > [ 6.485344] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 > > > [ 6.485368] pci_bus 0000:00: 1-byte config write to 0000:00:01.0 offset 0x1a may...

Hi to all. I'm experimenting with running a https://www.zotac.com/us/product/graphics_card/geforce%C2%AE-gt-710-1gb-pcie-x-1 card on an Nvidia Jetson TX2 arm64 device. Possible? Linux kernel aarch64 5.6.10. Because Nvidia did not list drivers for this architecture, I'm experimenting with a nouveau driver. The Jetson TX2 has a default driver for the host1x framebuffer for output from the