Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
LGA775 is too old, period.
Basically needs to be something like this as a minimum:
AMD FX4 series or better
Intel 2nd Gen Core or better
Pentium 4 is socket 478. And last I had my 478 build booted it launched steam in windows.
There are many s775 users on steam.
S775 isnt the issue here, and if it is its a steam issue and not his. They are the ones claiming it should run on a pentium 4 not this guy.
Sadly op I cant help you for linux. But as you said it worked yesterday, you meet listed minimums and thus it *should* be working...
I do know there are a couple linux users here maybe one can offer more insight.
I tried looking up minimums, but its near impossible. They dont list it publicly in the about section or the support section that I could find, and any googling leads you to minimums to Index, minimums for HL:A, or minimums for a game on steam called minimum...
I posted on the steam discussions board, maybe we can get a straight responce, as I am now super curious.
https://support.steampowered.com/kb_article.php?ref=4090-RTKZ-4347&l=
So yeh...
Still no solution for the OP, but we def know his system *should* work...
I guess the questions I would ask:
1) Is the linux install somehow causing it by misreading CPU flags?
2) If we can find that the OS is not at fault is the steam client then at fault for not detecting it?
3) Is it an Intel issue, they claim the CPU has the flag (cx16) but if neither steam or the OS see it whats the cause?
But it *should* work :/
The processor I have on the machine is Intel® Xeon(R) CPU E5450 @ 3.00GHz × 4
I don't really know what to do. It's the only thread on the internet with the same problem.
https://forums.linuxmint.com/viewtopic.php?t=272079
Sorry about the SSE 4.X comment, I was thinking games... Steam still works fine on LGA-775, Socket 939, FM2, AM2, AM3 stuff
So now we know it's Valve's fault. I tried starting Steam from several Linux distributions on the same machine and got the same result. Probably they made some mistake while packaging the latest update of Steam so that now a variety of processors don't work with Steam on Linux.
The two main questions are - when will it be fixed and will it be fixed at all?
As of now, the only option is switching to Windows.
FFS, Valve!
PS - Do you know where can this issue be reported?
Issues related to Steam Client directly, van be seen, discussed and reported here: https://steamcommunity.com/groups/SteamClientBeta
The link you've shared is about a different problem.
Cause poeple don't need Windows and why should they go through the hassles of installing two systems instead of just installing one system and not bother?
And if Valve keeps ♥♥♥♥♥♥♥ up like that maybe people will need to install Windows alongside Linux just in case something like this happens.
But did you try the what they tried? The steam client from the Linux app manager, or whatever it's called in your distro.
Specifically this:
https://forums.linuxmint.com/viewtopic.php?t=272079
Post #3 ~ Rene refers to the flatpak from the Linux software manager as a.work around.
But please look through all that. For example many Linux distros no longer have any 32bit libraries, which Steam Client requires, but that can be manually added back...
sudo apt-get install libnvidia-gl-390:i386
Ok, tried installing Flatpak on my distro but there are some issues with it. I think it's easier to install Windows at this point. No money from me to Valve until they fix that issue