search for: sernum

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

Did you mean: seqnum
2014 Jul 18
0
NUT + devd + FreeBSD
On Mon, Oct 29, 2007 at 9:45 PM, Daniel O'Connor <doconnor at gsoft.com.au> wrote: > I made the following devd script.. > > sh > cd /tmp > fetch > mkdir /usr/local/etc/devd > sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ > device-name "ugen[0-9]+";\ > match
2007 Oct 30
5
NUT + devd + FreeBSD
I made the following devd script.. sh cd /tmp fetch mkdir /usr/local/etc/devd sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ device-name "ugen[0-9]+";\ match "vendor" "0x\1";\ match "product" "0x\2";\ action "chown @RUN_AS_GROUP@
2020 Oct 11
0
Multi UPS Monitoring
...ce (mem stick, triplite ups or disc whatevere) > to a FreeBSD computer (PC, rasp. i386 amd64 whatever) the > computer will show serial numbers with all of; > dmesg > vi /var/log/messages > kill -9 `cat /var/run/devd.pid` ; /sbin/devd -d PS a few rare old devs don't announce a sernum, so you may be partly out of luck esp. in light of post from David Zomaya, Tripp Lite. However newest releases of FreeBSD offer more hub & port no. info than older releases, & presumably smilar on other OS's, so you may be able to extract some differentiating info. Good luck. Cheers,...
2023 Jun 29
0
NUT, Linux and libusb
...an issue discussed in https://github.com/networkupstools/nut/issues/1925 The gist of it is that despite the usbhid-ups driver running as `root` and seeing most of the regular run-time info, in the initial device search it fails to find basic matching info points - the device vendor, product and sernum strings: ```` 0.289953 [D2] Device does not match - skipping 0.289960 [D2] Checking device 8 of 9 (0463/FFFF) 0.311147 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.332348 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.353600 [D1] nut_libusb_open get iMa...
2023 Jun 29
0
NUT, Linux and libusb
...an issue discussed in https://github.com/networkupstools/nut/issues/1925 The gist of it is that despite the usbhid-ups driver running as `root` and seeing most of the regular run-time info, in the initial device search it fails to find basic matching info points - the device vendor, product and sernum strings: ```` 0.289953 [D2] Device does not match - skipping 0.289960 [D2] Checking device 8 of 9 (0463/FFFF) 0.311147 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.332348 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.353600 [D1] nut_libusb_open get iMa...
2012 Jan 17
6
Failing WD desktop drive in mirror, how to identify?
I have a desktop system with 2 ZFS mirrors. One drive in one mirror is starting to produce read errors and slowing things down dramatically. I detached it and the system is running fine. I can''t tell which drive it is though! The error message and format command let me know which pair the bad drive is in, but I don''t know how to get any more info than that like the serial number
2006 Apr 12
1
powerd not behaving with an Asus A8V-MX and Athlon 64 X2 3800+
..., rev 2.00/1.00, addr 1 dev.uhub.4.%driver: uhub dev.uhub.4.%parent: usb4 dev.uhub.5.%desc: Chicony Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 dev.uhub.5.%driver: uhub dev.uhub.5.%location: port=0 dev.uhub.5.%pnpinfo: vendor=0x0472 product=0x0065 devclass=0x09 devsubclass=0x00 release=0x0100 sernum="" dev.uhub.5.%parent: uhub0 dev.ehci.0.%desc: VIA VT6202 USB 2.0 controller dev.ehci.0.%driver: ehci dev.ehci.0.%location: slot=16 function=4 handle=\_SB_.PCI0.EHCI dev.ehci.0.%pnpinfo: vendor=0x1106 device=0x3104 subvendor=0x1106 subdevice=0x3104 class=0x0c0320 dev.ehci.0.%parent: pci0...