Aeternus

Yeah I just unplugged stuff from the Commander passthrough and I'll hold out for 1.2.0.2 at this point.

Yeah so it isn't working again this morning. Disconnects over and over.

Asus just this morning released BIOS Version 3401 Beta for my Dark Hero x570 board: ROG CROSSHAIR VIII DARK HERO BIOS 3401 "- Update AMD AM4 AGESA V2 PI 1.2.0.1 Patch A - Fix USB connectivity issue I installed it and so far everything is working perfectly. Windows actually detected Lighting Node Core and iCUE is working exactly as expected. For me, I could get it to SOMETIMES work if I changed my PCIE to Gen 3 and 4 but would always fail the next morning on a cold boot (USB sounds over and over and over), so I guess my real test is tomorrow morning, but so far this looks extremely promising.

https://www.pcmag.com/news/amd-locates-root-cause-of-usb-issues-on-b550-x570-motherboards?amp=true FYI ^ this is promising, hope it actually works but this is what we've all been waiting for.

I mean... you can go into system sounds and just disable the USB sound entirely. I was going to do that but the LEDs flashing between disconnects was equally as annoying.

I have an x570 Dark Hero and I've tried pretty much everything. Chipset updates, Beta BIOS versions, setting PCIE & NVME to 3.0, setting it to 4.0. Sometimes it will work all day without issue, and then after a cold boot, it will disconnect over and over. At this point, I unplugged everything from the Commander Pro USB ports and I'm only using my mobo 2.0 ports. Had anyone tried an internal 3.0 to 2.0 adapter to avoid using a hub?

That's exactly what I've been thinking of doing, except things plugged directly into my USB 2.0 headers work perfectly fine. I have my Commander Pro and Commander Core plugged into my two mobo USB 2.0 headers and they work fine and have never once disconnected on x570. So I might get the adapter you linked and plug my Lighting Node Core into it (since it's currently plugged into my Co Pro and using that as a USB hub is where I'm having my issues).

There is also a new sata-powered NZXT USB 2.0 hub but one of the comments says that on Gigabyte x570 they're getting our disconnect problem. Although, on the older molex-powered one people dont seem to have the same problem? Regardless, I think I'll only go straight into the Mobo. I wonder if something like https://www.amazon.com/WYMECT-Motherboard-Header-Extension-Splitter/dp/B07NTL8179/ would work or if there would be lesser functionality because it's cheap and is cutting a corner somewhere.

Ok and after shutting down the the night (after working fine all day), I powered up this morning and it was disconnecting more than ever. This is total insanity, I'm throwing in the towel. I think I'm going to sacrifice my front USB 3.0 and just get an internal 3.0 to 2.0 adapter unplug my H1000i entirely and not connect it, and connect my Lighting Node Core directly to mobo with the adapter. FWIW I dont think this is any sort of issue with my Corsair products, based off everything going on with this I'm convinced it's a driver/software issue with x570.

Also, coming back to mention that I started getting USB disconnects again. I had all my lanes set for 4.0 so I changed them to 3.0. No issues so far but we'll see how long this lasts.

Oh sorry I didn't realize that. So Commander Pro, when plugged into a USB 2.0 port on the mobo, is never even detected in iCUE at all? Have you tried to RMA it yet? That's definitely a different issue than the x570 thing.

But for devices connected directly to motherboard USB port, those work fine? Although I think you just said that even your Co Pro fan speeds are acting weird and presumably that is plugged into a USB 2.0 slot? If I were in your position, knowing that you have your board functionally set up the same as mine, I would probably: 1) Completely blow iCUE away just delete it entirely. Plug in nothing except Commander Pro to a USB 2.0 port on the mobo directly. Reinstall iCue, ensure that fan speed is working correctly by making a couple of quick custom profiles. On my other PC which is uhhh.... Intel 2066? Occasionally the pre-set profiles of Quiet, Balanced, and Extreme wouldn't work right. In fact, once after an iCUE update I had the same problem where the speeds would be all over the place, Quiet ran at extreme speeds, etc. So I just set my own custom curves and that worked perfectly. 2) Plug in any LED header components to the 2 LED ports to Commander Pro. Make sure it's picking those up properly. E.g. if you're using a Corsair lighting strip, connect it (since it connects directly to CoPro) and make sure you can control the ARGB. 3) Plug in one thing that connects to a Co Pro USB headers. If it doesnt work, try connecting it directly to a Motherboard USB 2.0 port... does iCUE recognize it? It should, since this takes the USB forwarding issue totally out of the equation. 4) If iCue is fine, meaning that items plugged directly into the Mobo are detected, but Co Pro still gives you problems, I would personally throw in the towel and explore other options like a PCI expansion slot internal USB card, and USB 2.0 splitter cable that goes directly to the mobo, or I would re-purpose a USB 3.0 Gen 1 or Gen 2 slot and get a 2.0 adapter to use that for direct connection. I know it's not ideal, but I would rather give up some front panel I/O functionality to have this working until it somehow gets sorted out. 5) Consider RMA of Co Pro if you're still having big control problems with the speed issue because that's 100% a Co Pro thing. Edit - make sure in between plugging or unplugging stuff from Commander Pro you shut down. I speak.......from experience.

Hey dread, I actually just came in here to say that I updated my Dark Hero to the latest Beta Version 3202 drivers (AGESA 1.2.0.0) and so far I "don't have any issues". So I flashed bios, set optimized defaults, shutdown and plugged my stuff back into Commander Pro, and I had exactly the same problem. Actually it was worse, the rate at which stuff was disconnecting and reconnecting was almost comical. I restarted, set all of my PCIE and NVME lanes to 3.0 (they were set to AUTO after the BIOS update/default optimizations) and the issue went away. I restarted again, set the lanes to 4.0 (in ASUS it's listed as GEN 4) and the issue still hasn't returned. I shut down entirely, removed power, held power button to purge, plugged power back in, started back up, and the issue still hasn't come back. I won't get too excited because this problem has been hard to tack down, and as you can see above I thought it was fixed, but then came back... but so far this feels promising. Basically I get into Windows, hear one USB connect sound, and the fans kick into the proper lighting profiles that I had set (since the Lighting node core is connected to one of the Co Pro USB ports.) Fan speed control is correct too. I have two custom profiles for 65% speed and 100% speed and they're responding properly. So just to recap what's working for me so far: 1) Updated chipset drivers from ASUS with whatever the most recent version listed was 2) Updated BIOS to Beta Version 3202 (AGESA V2 PI 1.2.0.0). These were released 1/14/2021 3) Set all my lanes to anything that is NOT AUTO, both Gen 3 and Gen 4 work I'll report back in a couple days if this still works, or I'll report back as soon as it stops working.

Totally unrelated but which motherboard are you using? I have exact same case and fan setup, was such a pleasure to build in :)

I installed whatever the latest download chipset drivers are and it didn't resolve. Interestingly, yesterday this worked for a little while after starting up. PC made the USB disconnect/reconnect sound about 10 times but it ultimately "caught" and worked for the rest of the night. This morning after booting up I let it disconnect/reconnect for about 10 minutes but it never caught on so I ended up just shutting down and unplugging the two USB 2.0 devices on Commander since I had to start working.

ASUS Crosshair VIII Dark Hero (x570) AMD 5900x EVGA 3090 FTW3 Ultra I havent manually installed my chipset drivers because the date of the newest chipset driver is older than the date of the BIOS version it shipped with so presumably it's the newest version as well.

Nevermind, problem came back this morning. I even set PCIE back to auto, rebooted, then back to 3.0, and it's doing the same repeated disconnect. How stupid and annoying...worked perfectly fine all day yesterday.

Just to (hopefully) close the loop here, I did this: https://forum.corsair.com/v3/showthread.php?p=1077538#post1077538 and I've had 0 problems so far. I went into bios, found my PCIE config, set all PCIE slots to Gen 3 (it was previously set on auto so presumably defaulting to Gen 4/4.0) and this issue went away entirely. Everything that is plugged into my Commander Pro USB ports is now being detected and controllable through iCUE so it resolved my issue entirely. I have a 3090, but a 3090 doesnt even come close to bandwidth saturating 3.0 so not running in 4.0 isnt a problem at all - I left my M2 slots set for Auto.

Holy crap this actually worked for me. I set all my x570 Dark Hero PCIE slots to 3.0 and the entire issue with the 2 USB ports on Commander Pro not working went away. When the system powers on, I hear one single USB connect sound and everything is detected as it should be in iCUE. It's been about 25 minutes and I restarted twice and no issues yet.

You mean it came with a Commander Core? Commander Pro and Commander Core are 2 separate things. Assuming you meant Commander Core, how is it connected? Is it plugged into a 2.0 slot on your motherboard?

So initially, it just didn't work at all. Commander Pro itself works, I can control fan speeds and stuff like that, but the 2.0 ports didn't work (so my Lighting Node Core and PSU weren't detected). I was messing around in BIOS and had to Clear CMOS, and after rebooting after the clear, the ports actually started working (so my PSU was showing up and reporting and I was able to control lighting effects through my Lighting Node Core). However, the system would constantly make USB disconnect/reconnect sound and I could see the PSU and LNC disappearing in iCUE every time this happened. So it's like the PC saw these things, it worked, and then said oh no no you cant do this and disabled it, and it just keeps fighting back and forth. I ultimately just disconnected both the USB cables from Commander Pro to make it stop. Haven't tried the NZXT hub yet.

Really? A quick search online says that some people have had luck using the internal hub, I don't think I've seen anyone say that the NZXT one didn't work for them. I see in the other thread you said it didn't work for you, which board do you have?

I cleared CMOS and every started working as it should but it just USB disconnect/reconnects over and over and over which it looks like a bunch of other people have mentioned. Guess I'll need the NZXT hub :/

What chipset are you guys using for your AMD 5000s? I'm using a x570 Dark Hero and nothing connected to my Commander Pro USB ports is being detected.

Also, in Device Manager I see an error for "Unknown USB Device (Device Descriptor Request Failed)" under USB Controllers but I don't know if that's referring to CoPro or not.