Jump to content

skylined45

Members
  • Posts

    20
  • Joined

  • Days Won

    1

skylined45 last won the day on August 22 2021

skylined45 had the most liked content!

Reputation

11 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So I received an ax1200i in Jan 2020 as a gift, and had to RMA it because it was randomly shutting down/restarting. The new unit worked fine for a few months and is now doing the same thing, but Corsair is refusing to RMA again because I did not have the original receipt (see above - it was a gift) for the first RMA. Hoping anyone has maybe found a fix for this issue - I had some custom cables made for ~$130 that are now useless because they aren't compatible with very many other PSUs. Pretty lame, all in it's over $400 on a piece of equipment that is supposed to have a lengthy warranty that I can's use after a year and a half. I am positive it is the PSU - several other PSUs work fine in the machine. My system specs are a 9900k on a gigabyte z390 aorus master board, 4x16gb 3200mhz corsair vengeance ram, 3080 founder's edition, several m.2 SSDs and a single 2.5" SSD, 4TB external HDD, all watercooled (loop not AIO). It passes the self-test and does not exhibit any operational issues until it decides to turn itself off and on again - it does seem to happy after using the PC for a bit (so maybe heat related?) but also happens sometimes after a cold boot. The link module shows the PSU in iCUE just fine, wattage readings, etc all align with HWinfo so no weird software/hardware issues that I can see. iCUE is fully updated, PSU is set to single rail, and using 2 distinct cables for both CPU socket power and GPU power. I really hope I can get this thing working again - this whole issue has really soured me on Corsair products.
  2. Don't I risk frying the whole CoPro if I do this while power is on? Nope, I uninstalled HWInfo completely and am not running any others in the background, though a few are currently installed. I'd be more inclined to think it was software related if it wasn't specifically ports 3 and 5 that aren't recognizing fans, no matter which fan is hooked up to them.
  3. Bumping this - I removed HWInfo and the performance tab stays put now, but the compro is only recognizing 4 fans. Doesn't want to see anything plugged into port 3 or 5. I've set the pinout to 4-pin and auto; 4-pin at least shows the fans at 0 RPM, but auto doesn't show the fans at all. I've narrowed it down to the compro not recognizing any fan connected to ports 3 and 5. I've removed all other connections from the compro - USB, LED fans on ports 1, 2, 4, 6, temp sensors - nothing seems to get ports 3 and 5 to recognize and control fans. Is it possible to just have 2 of the 6 fan control ports burn out?
  4. Just bumping this - fans are plugged into the CoPro which is plugged directly into a USB header on my motherboard. I still do not have any fans showing up to edit a fan curve in my CoPro.
  5. I don't use any splitters and the commander pro is connected directed to a USB header on my motherboard, and powered by its own SATA connection. I just recently updated iCUE and that didn't fix; neither did a fresh uninstall/install.
  6. So my commander pro does not always show my fans as available to control. I haven't changed anything in my hardware to cause this - they just started sort of blinking in and out in the UI and not they do not show up at all. The firmware is up to date. The only items I see in the Commander Pro list is graphing, lighting setup, lighting channel 1 and 2. The Performance tab pops up every now and then, with only 2 fans available, and then blinks away. Any ideas? Edit - my most recent log may show some issues but I do not know how to read it! 2020-04-04T18:09:15 I cue.init: iCUE version: 3.27.68 2020-04-04T18:09:15 I cue.init: Updates server: https://www3.corsair.com/software/CUE_V3/ 2020-04-04T18:09:15 I cue.init: Build type: Public Release 2020-04-04T18:09:15 I cue.init: Applicaiton ID: 29304 2020-04-04T18:09:15 W cue.locale: Cannot find dir for qt *.qm files 2020-04-04T18:09:15 I cue.init.font: Using Regular text font family: "Open Sans" 2020-04-04T18:09:15 I cue.init.font: Using Title text font family: "Gotham Bold" 2020-04-04T18:09:16 I cue.hid_device_detector: Start worker thread. 2020-04-04T18:09:16 I cue.devices.enum.hid: Leaving working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session disallowed. 2020-04-04T18:09:16 I cue.devices.enum.router: Leaving working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session disallowed. 2020-04-04T18:09:16 I cue.devices.enum.clink: Leaving working state. 2020-04-04T18:09:16 I cue.plugin: Trying to load library: "C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/plugins/ASUS/asus_motherboard_plugin.dll" 2020-04-04T18:09:16 I cue.plugin: Library is loading, will check if it's plugin: "ASUS/asus_motherboard_plugin.dll" 2020-04-04T18:09:16 I cue.plugin: Trying to load library: "C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/plugins/Lenovo/CUEPlugin.dll" 2020-04-04T18:09:16 I cue.plugin: Library is loading, will check if it's plugin: "Lenovo/CUEPlugin.dll" 2020-04-04T18:09:16 I cue.plugin: Trying to load library: "C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/plugins/OriginPC/CUEOPCPlugin.dll" 2020-04-04T18:09:16 I cue.plugin: Library is loading, will check if it's plugin: "OriginPC/CUEOPCPlugin.dll" 2020-04-04T18:09:16 I cue.devices.enum.phost: Leaving working state. 2020-04-04T18:09:16 W cue.plugin: Processing already finished 2020-04-04T18:09:16 W cue.plugin: Processing already finished 2020-04-04T18:09:16 W cue.plugin: Processing already finished 2020-04-04T18:09:16 I cue.profiles.folders.tree: Profile order deserialization started: "C:\\Users\\skylined45\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder" 2020-04-04T18:09:16 I cue.profiles.folders.tree: Profile order deserialization finished: "C:\\Users\\skylined45\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder" 2020-04-04T18:09:16 I cue.actions.macro.win: Init time: 0.402395 (init: 1e-07 reset: 0.0019598 ) 2020-04-04T18:09:16 I cue.devices.enum.dram: Leaving working state. 2020-04-04T18:09:16 I cue.ro_helpers: LLAccessIpcClient(0x1dd94c88) Start connecting to host QUrl("tcp://127.0.0.1:58508") 2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:16 I cue.ro_helpers: LLAccessIpcClient(0x1dd94c88) Successfully connected to host node at QUrl("tcp://127.0.0.1:58508") 2020-04-04T18:09:16 W cue.library: Actions load failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:16 I cue.llaccess: Controller 0 : Bus capabilities: 7 Max block size: 32 2020-04-04T18:09:16 I cue.llaccess: Northbridge: Intel Coffee Lake 2020-04-04T18:09:16 I cue.llaccess: Southbridge: Z390 2020-04-04T18:09:16 I cue.llaccess: Slot count: 4 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter 2020-04-04T18:09:16 I cue.session: Locked changed to false 2020-04-04T18:09:16 I cue.session: Local changed to true 2020-04-04T18:09:16 I cue.session.win: Will notify 'connected changed to' with delay 2020-04-04T18:09:17 I cue.hw_profile.manager: Start worker thread. 2020-04-04T18:09:17 C cue.button_content_storage: "Loading of devices properties failed!" Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:17 C cue.button_content_storage: "Loading of library property failed!" Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:17 C cue.buttons_lib: "Loading of buttons library failed!" Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:17 W cue.screens.data_provider: Widget data storage failed: Could not detect cereal root node - likely due to empty or invalid input 2020-04-04T18:09:17 I cue.core.init_ui: Starting UI. 2020-04-04T18:09:17 W QObject::connect(MobileServerSettingsModel, ProgramSettingsModel): invalid null parameter 2020-04-04T18:09:19 W qrc:/qml/delegate/MarkLinedAssignmentListDelegate.qml:22:23: Invalid property assignment: int expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. 2020-04-04T18:09:19 W MainWindow_QMLTYPE_560(0x2c3ffeb0) must be a top level window. 2020-04-04T18:09:19 W MainWindow_QMLTYPE_560(0x2c3ffeb0) must be a top level window. 2020-04-04T18:09:19 W Model size of -1 is less than 0 2020-04-04T18:09:20 W libpng warning: iCCP: known incorrect sRGB profile 2020-04-04T18:09:20 W qrc:/qml/ui/assignment/HorizontalTouchScreenAssignmentView.qml:153: TypeError: Cannot read property 'activeItemIndex' of null 2020-04-04T18:09:20 W qrc:/qml/ui/TouchscreenElementsInfo.qml:89:2: QML ColumnLayout: Possible anchor loop detected on vertical anchor. 2020-04-04T18:09:20 W qrc:/qml/ui/accordion/ButtonsLibraryAccordionItem.qml:258:2: QML Connections: Cannot assign to non-existent property "onCurrentIndexChanged" 2020-04-04T18:09:20 W libpng warning: iCCP: known incorrect sRGB profile 2020-04-04T18:09:20 W libpng warning: iCCP: known incorrect sRGB profile 2020-04-04T18:09:20 I cue.session: Connected changed to true 2020-04-04T18:09:20 I cue.sdk: Entering working state, session connected. 2020-04-04T18:09:20 I cue.sdk: Starting router. 2020-04-04T18:09:20 I cue.sdk.device_watcher: Start prepare RestoreDeviceOrderState 2020-04-04T18:09:20 I cue.sdk.device_watcher: Finish prepare RestoreDeviceOrderState 2020-04-04T18:09:20 I cue.clink.device.hw_lightings: Working state about to change, lock hw lights preview. 2020-04-04T18:09:20 I cue.sdk.automation.server: User session about to be unlocked. Starting a listening 2020-04-04T18:09:20 I cue.sdk.automation.server: Successfully started listening 2020-04-04T18:09:20 I cue.devices.enum.hid: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2020-04-04T18:09:20 W cue.hid_device_detector: Device detector already disabled. 2020-04-04T18:09:20 I cue.devices.enum.router: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2020-04-04T18:09:20 I cue.devices.enum.clink: Entering working state. 2020-04-04T18:09:20 I cue.devices.enum.phost: Entering working state. 2020-04-04T18:09:20 I cue.devices.enum.dram: Entering working state. 2020-04-04T18:09:20 I cue.clink.device.hw_lightings: Entering working state, unlock and disable hw lights preview. 2020-04-04T18:09:20 C cue.plugin.aura_sdk_controller: Failed call to create instance of AuraSdk with HRESULT: "0xFFFFFFFF80040154" 2020-04-04T18:09:20 I cue.plugin: Received deviceStatusChanged 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=c76, pid=161f) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=424, pid=274a) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Device vid=1b1c pid=c10 ignored by HidDeviceEnumerator 2020-04-04T18:09:20 I cue.devices: Device vid=1b1c pid=c0b ignored by HidDeviceEnumerator 2020-04-04T18:09:20 I cue.devices: Device vid=1b1c pid=c0b ignored by HidDeviceEnumerator 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=48d, pid=8297) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=48d, pid=8297) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found. 2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=262a, pid=1100) not found. 2020-04-04T18:09:21 I cue.devices.dram: Module created (0:58) CMW32GX4M2C3200C16 Slot: 0 2020-04-04T18:09:21 I cue.devices.dram: Module created (0:59) CMW32GX4M2C3200C16 Slot: 1 2020-04-04T18:09:21 I cue.devices.dram: Module created (0:5a) CMW32GX4M2C3200C16 Slot: 2 2020-04-04T18:09:21 I cue.devices.dram: Module created (0:5b) CMW32GX4M2C3200C16 Slot: 3 2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:58]" 2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:59]" 2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:5a]" 2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:5b]" 2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::SetDpiBrightnessLevel 2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::GetAutoDetectedLedChannelTypes 2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::GetConnectedLedChannelCounts 2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::GetLightingMode 2020-04-04T18:09:21 I cue.sdk.device_watcher: Dram counts: 4 ; Serial: "vid<1b1c>pid<000004>serial<VENGEANCERGBPRO>index<0>" 2020-04-04T18:09:21 I cue.lightings.direct_player: Started lighting worker in 0x1b88 2020-04-04T18:09:21 I cue.devices: Device insertion processing complete for VENGEANCE RGB PRO (vid=1b1c, pid=403) 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::SetDpiBrightnessLevel 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetAutoDetectedLedChannelTypes 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetConnectedLedChannelCounts 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetLightingMode 2020-04-04T18:09:21 I cue.lightings.direct_player: Started lighting worker in 0x2850 2020-04-04T18:09:21 I cue.devices: Device insertion processing complete for Lighting Node Pro (vid=1b1c, pid=c0b) 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::SetDpiBrightnessLevel 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetAutoDetectedLedChannelTypes 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetConnectedLedChannelCounts 2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetLightingMode 2020-04-04T18:09:22 I cue.lightings.direct_player: Started lighting worker in 0x1a74 2020-04-04T18:09:22 I cue.devices: Device insertion processing complete for Commander Pro (vid=1b1c, pid=c10) 2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::SetDpiBrightnessLevel 2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetAutoDetectedLedChannelTypes 2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetConnectedLedChannelCounts 2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetLightingMode 2020-04-04T18:09:22 I cue.lightings.direct_player: Started lighting worker in 0x15f4 2020-04-04T18:09:22 I cue.devices: Device insertion processing complete for Lighting Node Pro (vid=1b1c, pid=c0b) 2020-04-04T18:09:22 W cue.devices.enum.demo: Registration of device with unsupported DemoUsbId: (vid=0, pid=0) 2020-04-04T18:09:22 I cue.sdk.device_watcher: Start prepare WorkingStateState 2020-04-04T18:09:22 I cue.sdk.device_watcher: Finish prepare WorkingStateState 2020-04-04T18:09:22 C cue.firmware.index: Skipping package: "VENGEANCERGBPRO" requires other version of CUE: QJsonValue(string, "<3.24") current is: 3.27.68 2020-04-04T18:09:22 I cue.firmware.index: "VENGEANCE RGB PRO" no newer FW version was found, selecting package with maximal verion 2020-04-04T18:09:22 I cue.firmware.index: "VENGEANCE RGB PRO" no newer FW version was found, package: QJsonObject({"integrity":"sha512-CrrQmeGiZTuy5TEx/IOj3vDVYLztlQUrf7fodKm5xCYHRb6ldwci4N+t+cNxGUNQz4vtifbcYaiTYGm7fwYkIQ==","provides":{"application":"1.02.64"},"release-date":"2019-05-17T15:07:00.000Z","requires":{"software":">=3.24"},"source":"VENGEANCERGBPRO_pr4.zip","version":"2.0"}) 2020-04-04T18:09:22 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2020-04-04T18:09:22 I cue.firmware.index: "Lighting Node Pro" firmware update, expected version: 0.10.4 same version found, on device: bootloader: 3.0 firmware: 0.10.4 2020-04-04T18:09:22 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2020-04-04T18:09:22 I cue.firmware.index: "Commander Pro" firmware update, expected version: 0.9.212 same version found, on device: bootloader: 0.5 firmware: 0.9.212 2020-04-04T18:09:22 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2020-04-04T18:09:22 I cue.firmware.index: "Lighting Node Pro" firmware update, expected version: 0.10.4 same version found, on device: bootloader: 3.0 firmware: 0.10.4 2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<2>" 2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<3>" 2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<4>" 2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<5>" 2020-04-04T18:09:23 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::CommitHwSettings 2020-04-04T18:17:52 W qrc:/qml/collection/ColorPicker.qml:42: TypeError: Cannot call method 'updateCurrentColor' of null 2020-04-04T18:17:52 W qrc:/qml/collection/ColorPicker.qml:48: TypeError: Cannot call method 'updateCurrentColor' of null 2020-04-04T18:17:52 I cue.models.present_device: Lighting mode changed to SW for "VENGEANCE RGB PRO" 2020-04-04T18:17:52 W qrc:/qml/ui/settings/DeviceSettings.qml:233:7: Unable to assign [undefined] to double 2020-04-04T18:17:52 W qrc:/qml/delegate/TabViewTabDelegate.qml:21: TypeError: Cannot read property 'top' of null
  7. Thanks however doing this did not yield any different results. I moved all three fans to a new machine (with 9 working LL120s hooked up to it, all working fine) and connected all three at once and still got the same results. I guess I can try to connect them individually to see if there is just one culprit...
  8. Anyone have any ideas what could be causing this and what I might be able to do to fix them? https://i.imgur.com/SQ8QzMP Fans are set to 'rainbow' profile, and are intermittently blinking as if a random LED is just turning off and on again. I have 3 LL120 fans in this build and all are doing this. I swapped the LNP and RGB hub with known working devices and the fans still do this. I put the fans in a separate build with known working devices and the fans continue to spaz out. I reinstalled iCUE - did not help. I unfortunately bought these from Amazon Renewed with a 90-day warranty and am guessing my Corsair warranty doesn't cover this, since I was not the original buyer. Hoping someone can help me figure this out!
  9. You’re whining that people are giving feedback about the product compatibility in the thread about product compatibility.
  10. Expressing disappointment in the limited functionality of a product isn’t entitlement, and Corsair obviously welcomes the feedback. It’s typically better then customers just disappearing. Your ‘be grateful for what you get’ mentality in a thread meant for community feedback seems, uh, a little misplaced. I mean, I shouldn’t have to hook up my fans to a windows machine to get them to display the default rainbow coloration out of the box. It’s obvious the LNPs firmware can be preloaded to do this on its own.
  11. I think the original post is updated with what is supported. There is community software that's been developed to support keyboards as well. As far as I can tell though there is nothing that supports internals - fans, light strips, anything else attached to the LNP, AIO coolers, etc.
  12. So i ended up putting the hackintosh right up against another windows machine I have, plugged the lighting node pro into the USB socket and sata power on the windows machine in some unholy RGB transfusion, ran iCUE on the windows machine and set the lighting effect I wanted, updated the firmware, unhooked it all and now the fans run the last setting used while booted to osx. Without having to dual boot windows. So that’s a thing I did. Please add support for the fans in OS X.
  13. After building a hackintosh for my wife and buying more LL120 fans (now 12 total between our two computers), this was also disappointing to me to read. Doesn't seem like it has changed in months, either. Any updates on future support for MacOS and LL120/Lighting Node Pro?
  14. So I upgraded to a Z390 aorus pro from gigabyte (to go with a new 9900k) and everything is working fine. Looks like a conflict between the motherboard and the LNP. Thanks for the help - hope anyone else struggling with this issue with these components can find this and rest assured knowing it's just a compatibility issue.
  15. So I have a micro USB cable plugged into the lighting node pro, to a working port on my back i/o panel. The port works fine - it detects a wired mouse, iphone, etc. The cable also works with other devices. iCUE, USB tree and USBDeview do not see the lighting node pro. I've turned off fast startup in windows and in my bios. xHCI is not a controller I can turn on or off but my bios says it detects 3 items as xHCI. All my USB ports are enabled in bios. Beginning to think either the lighting node just won't ever be recognized by this mobo, or the node itself is bad. I'll have a new mobo by Friday and will test it with it... hope that's the issue!
×
×
  • Create New...