[Nut-upsuser] Zigor on Mac Os X
mark at helenandmark.org
Tue Sep 25 13:25:22 UTC 2012
Small update, to make life a pain.
If you run the blazers_usb with a few -D's, then --- it works, and it doesn't loose its connection with the UPS
(makes debugging that problem a little bit of a pain, but there you go, if you want it to work, add some debug :-) )
On 24 Sep 2012, at 14:35, Charles Lepple wrote:
> On Sep 24, 2012, at 6:15 AM, Mark Burton wrote:
>> Sep 24 12:11:16 Marks-iMac kernel: USBF: 1122.116 [0xffffff801a1ed400] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0xfd100000)
> Does this message look like it is referring to the UPS or the card reader? (Check for 0xfd100000 in ioreg output, I think.)
>> Sep 24 12:11:22 Marks-iMac kernel: com_apple_driver_AppleUSBCardReaderUMC:: Stop::Controller Reset
>> Sep 24 12:11:23 Marks-iMac kernel: USBF: 1128.982 [0xffffff801a1ed400] The IOUSBFamily has successfully enumerated the device.
>> Sep 24 12:11:23 Marks-iMac kernel: USBMSC Identifier (non-unique): 000000009833 0x5ac 0x8403 0x9833
>> If I stop and re-start the drivers - everything works again, ONCE.
>> I _think_ related to this - it's not exactly ideal to have to unplug, and re-plug the USB cable each time I restart my machine - so I'm GUESSING I have an issue still with the NUTDummy mechanism, but I'm not sure I know what it could be…
> Well... if it is showing similar problems (in particular, not updating) with both the built-in UPS support and with NUT (plus the kext), I would suspect a hardware problem. (The dummy kext probably wouldn't work halfway. The fact that NUT could connect initially means that the kext did its job by preventing the other drivers from binding to the device first.)
> To narrow things down, is there a way you can check this UPS against another computer, or try a different UPS?
> Charles Lepple
> clepple at gmail
More information about the Nut-upsuser