Thanks I’ll check it out. I ended up running eac in bottles and it worked 100%. I guess I assumed (without any real reason) that EAC would have issues low level accessing the cdrom drive through wine - but that turned out to not be true at all. It just worked flawlessly, so I just keep doing what I like - EAC

But I am playing around with these alternatives-never know, I may like one of these better ;)

Thanks for the recommendation!

Agreed. I broke arch multiple times over the years. Once I learned to read the arch news, pay attention to the pacman log, and not just “yay - update complete” my way through updates - it’s been pretty solid for years. More so than the “stable, noob friendly distros”

I updated two PCs yesterday and both were fairly far behind in updates. My main rig was without issue (it was about 4 weeks since last updated). A secondary pc that was a couple of months behind did have a weird issue with the mirrors being offline or something. This was using the default mirror lists. Pac-Man couldn’t find the repositories. Ran reflector and everything was fine again. I’m thinking the issue didn’t have anything to do with pacman.

Anyways - the pacman upgrade was uneventful (which was good)

Ah I see, #5 is just the header you’re using. You aren’t using 5 total. That makes more sense.

I don’t even have L-connect installed, but I did once upon a time. Maybe I changed a setting there and forgot about it, but I don’t think so. Either way it’s probably worth checking that your bios is set to “PWM” for that header, and that L-connect is set to “enable MB PWM Sync” under the fan/pump profile page. (Just from googling). Look for settings to turn off any L-connect interaction - forcing it to pay attention to the fan header?

I’m wondering if your controller is somehow set to ignore the header pins and run from just the usb port/L-connect. And maybe on a power cycle, your mobo thinks there’s no fan?

I dunno - I’m shooting in the dark now though. All I know is that my controller always shows up as a single fan, and all the attached fans run at the same speed - whatever the header calls for. No software installed, all wired connections are made, exhibits this same behavior regardless of OS, power cycles, reboots, etc.

Sorry I’m not more help - it’s frustrating when things that should “just work” don’t.

Oh! Did you plug in BOTH SATA connectors? I think one is for rgb and the other is for fan speed. Maybe that’s screwing things up?

“Fan 5 isn’t recognized”. This confuses me. Wouldn’t your motherboard only recognize the controller? For example I’m using two controllers. My motherboard sees a single cpu fan (the controller with 3 daisy chained fans on one port), and it sees a second chassis fan (the second controller with a 3 pack on one port, another three pack on the second port, and a single fan on the third port).

10 fans, 2 controllers, mobo only sees 2 “fans”. Here’s a video showing exactly how I wired mine up, and the type of fans and controllers (maybe we don’t have the same parts).

https://m.youtube.com/watch?v=0wPi_zNzKF4

Hmmm…. I’ve got those exact fans and the controller that comes with them - 10 fans to be specific, and they really haven’t given me any trouble at all. There are three sets of 3 daisy chained, and one single fan. They connect to a relatively new asus board. I’m running arch and openrgb from the aur.

The fans doing fan things (spinning), that just works. They ramp up and down based on the case fan connector from the mobo. One three pack is on the radiator to an aio cooler and that triplet ramps up and down based on the fan speed header for the cpu.

The LIGHTS are a different story. If I cycle power completely, they do the default rainbow puke when started back up. OpenRGB required a little configuration and playing around to get the number of lights correct, and synching properly-but it worked. (I can get you my settings in openRGB if that helps avoid the trial and error). Because my mobo still supplies power when I power down, the lights hold their last pattern when I reboot.

So in my experience-those fans spin without any software and light up at least rainbow puke without any software. You only need software to get different colors or to just override the fan header and set a manual speed.

I’m wondering what your computer/mobo is doing to stop that. Weird.

I trust Apple more than Google. May be misplaced faith, but that’s the primary reason.

Agreed there were native linux games written for linux, but remind me because I forgot - I believe Doom had been ported or something. Because I remember running it both at home in linux and I remember people running it in the computer labs off the Unix mainframe.

I went to college in 93, and they ran a Unix mainframe with thin clients connected to it in the computer labs.

I didn’t really know much about any computers then, but I learned quick and had nerdy friends teach me a lot. Home computers ran DOS, but this fancy thing called Linux had entered the scene and nerds played with it.

I remember it being a bear. My comp sci roommate did most of the work, but he’d dole out mini projects to me to help him out. You had to edit text files with your exact hardware parameters or else it wouldn’t work. Like resolutions, refresh rates, IRQs, mouse shit, printer shit - it was maddening. And then you’d compile that all for hours. And it always failed. Many hardware things just weren’t ever going to work.

Eventually we got most things working and it was cool as beans. But it took weeks - seriously. We were able to act as a thin client to the mainframe and run programs right from our apartment instead of hauling ourselves to the computer lab. Interestingly, on Linux, that was the first time I had ever gotten a modem and a mouse working together. It was either/or before that.

It was both simultaneously horrific and fantastic at the same time. By the time windows 95 rolled out, the Unix mainframe seemed old and archaic. All the cool kids were playing Warcraft 2 and duke nukem 3D.

You really can’t get bluer than mass ri conn and vt

Southern nh and southern me are basically Boston suburbs. As you go north it gets more red. But not like sc (I have family in sc and outside of the blue cities - ya they are pretty maga stupid). They are more “leave me alone red” as opposed to “my pastor said abortion is bad and I like to make fun of the gays”

I mean there’s maga idiots everywhere-but honestly things might even tip a little too blue in southern New England.

There hasn’t been “bitter cold” in the northeast for a decade. Climate change is a bitch. We barely get snow anymore - 2015 was a banger, but it’s been dustings since.

I’ve actually had someone thumb their nose at linux because of that name. “You mean the hat OS? The one those weird guys use? No thanks.” I’m paraphrasing but ya, that association is there for some people.

The real kick in the nuts is that Sonos is quite handy if you’re looking for whole house audio. Or it used to be.

Decent speakers that run over WiFi and don’t require knocking holes in walls. Could stream from your NAS, from a line in jack from a tv, or bridge your “real” stereo to your sonos products.

But they keep breaking all the things one by one. At this point I’m just waiting for someone to hack the speakers so I can use them with a foss alternative.

Excellent, that makes sense. I’ll try that command tonight at home, see what it does, and report back. I kind of want to know what it’s doing just because I’m curious.

I say a relay, but I agree with you - I couldn’t imagine a relay being used. But whatever it is on my desktop, it sounds just like a traditional ice cube relay clicking - and it’s quite loud. But I have no idea what it is. I’m not sure I’ve ever had a computer that made that noise before. My laptop makes no such noise obviously.

I did some more digging on this last night. I’m more confused now than I was before, and I don’t know what it’s doing.

The arch wiki defines three states, suspend to ram (sleep), suspend to disk(hibernate), and a hybrid suspend(presumably what my steam deck does).

First there is the “turn off the display” behavior. Doing anything brings the monitor back alive and I’m presented with the Lock Screen.

Second is what I believe to be sleep. This happens when I select “suspend” from the menu or leave it alone for a very long time. This mode doesn’t happen soon (maybe at all) if the computer is doing stuff. It appears to be in a lower power state-but I can’t say why I think that (maybe it’s just because the fans aren’t running? I dunno). Wiggling the mouse or doing anything wakes it back up.

Third is another state. It’s just like the above state, except it will not wake up with mouse movement, or clicking keys on a Bluetooth keyboard. I must push a key on the keyboard, the power button, or open the lid. It’s weird because it responds to things other than the power button.

Interestingly, my desktop behaves exactly the same way. But what’s interesting on the desktop is that I can hear a power relay clicking on from this third state. It’s distinctly different than the 2nd state - exhibiting power cutoff, but still responding to the keyboard.

Neither computer enters any other state even after days of being left alone.

So I dunno. Are modes 2 and 3 like two versions of sleep, and hibernate never activates? Or is state three hibernation but it responds to things it shouldn’t?

I have no idea. But now that I’ve played with it some more - I don’t want to say hibernate is working because I don’t know what it’s doing. All I know is that it has the above three behaviors which are consistent with my desktop machine.

The article doesn’t say/clarify. Was it some crap HP software that performs driver updates, and it decided to force a bios flash? Or was it windows update itself?

If it was windows itself, holy crap, that’s a serious over reach on Microsoft’s part. Like “this is insanity windows needs to be removed” bad.

HA! True. Remember when Google was always right and always exactly what you were looking for?

Pepperidge Farms remembers.

It was a couple hours. Just like on my desktop, wiggling the mouse wakes it from sleep, but not so in whatever that second state is when it’s left for longer. It definitely was something other than sleep. What it was - I’ll let you guys decide. Whether it behaves long term with fans in a laptop bag, that I don’t know - I haven’t had enough run time with it.

I’m just sharing a positive experience. If I see it misbehave I’ll be sure to update the thread with reality. But so far, it really is behaving much better than I expected.

I left I alone, it went off. I came back and wiggled the mouse, nothing happened. I pressed the enter key snd it came back to life -same behavior as my desktop.

Did it again, this time I tried closing the lid and opening it - it sprung to life when the lid opened.

You’re right - not the most thorough tests, but that’s what I did/saw.