Quoting: appetrosyanLiam, Thanks for removing the comment explaining what the terminology means. I really appreciate it when I don't even know whom I've offended and how.

The original 5 comments were completely going off the road in regards to what this was about, due to my own confusion and how I wrote it. Hence their removal and the re-posting of this article.

View this comment - View article - View full comments

Quoting: red193The distinction is already made, except using the terminology of CPU/socket instead of core/CPU.

Except it isn't. Did you even read the linked statistics page? "Number of CPUs" - show me where there's any kind of distinction in that.

I always find this sort of thing amusing, how a few people seem to just latch onto something so specific like this rather than talk about the actual topic at hand ;)

View this comment - View article - View full comments

Quoting: red193

Quoting: liamdawe

Quoting: red193To the linux kernel, a multicore CPU is effectively multiple CPUs and is treated as such. Running lscpu on any distro will result in showing CPU(s):x where x is the number of what people would traditionally call cores. This is because a core is effectively it's own CPU sharing cache with other cores in the same way multiple sockets would share memory, and can act independently.

We can talk about the technical details of stuff like that all we want, they likely just mean cores and they need to make it clear. Already spoken to them about this :)

The usage is correct, that's all I'm saying.

I get what you're saying, but what I'm saying is this just isn't the "normal" way to describe it. As I said, I already spoke to them about this and from what they said it was supposed to say cores but that got lost somewhere so they will be updating it.

View this comment - View article - View full comments

Quoting: red193To the linux kernel, a multicore CPU is effectively multiple CPUs and is treated as such. Running lscpu on any distro will result in showing CPU(s):x where x is the number of what people would traditionally call cores. This is because a core is effectively it's own CPU sharing cache with other cores in the same way multiple sockets would share memory, and can act independently.

We can talk about the technical details of stuff like that all we want, they likely just mean cores and they need to make it clear. Already spoken to them about this :)

View this comment - View article - View full comments

Quoting: razing32Let me guess
Still needs a fix like previous ones since it starts in a black screen ? :P

Works without a single issue for me.

View this comment - View article - View full comments

Quoting: Oli

Then reboot.

Seems a bit redundant. The first commands handles this session The second and third handle future sessions. Just run all three once and get on with your life.

Sure, meant more as in when you reboot it will be fine. Did a slight reword to make it clearer.

View this comment - View article - View full comments

Quoting: BeamboomBut the case of;

a lot of games were crashing to the desktop

that was only related to the issue with the controller? So after this fix there was no more crashing to the desktop?

Bingo. A bunch of Unity games completely crashed to the desktop with the Steam Controller turned on without blacklisting it.

Edit: Spelling.

View this comment - View article - View full comments

Quoting: abelthorneIt still appears as a preorder on Steam and Humble, is it really out yet?

Strange. It's available on GOG right now. They might not be for another hour or two.

View this comment - View article - View full comments

Quoting: KeyrockThe title of this article could also use quick a fix. :P

Yeah, I'm that guy.

/hides

Well then. That was embarrassing.

View this comment - View article - View full comments

Quoting: JungleRobbaThe writer of the module is aware of the issue and seems to be working on a fix:
https://github.com/ValveSoftware/steam-for-linux/issues/5645#issuecomment-429647198 [External Link]

Thanks, added a note about it.

View this comment - View article - View full comments