I have the 424cc cpu in case that makes a difference. Honestly, it sounds like a motherboard issue vs a memory module unless you weren't 100% sure the modules you tested were good.
Fujitsu Futro S920 Thin Client as opnsense firewall
- Thread starter frauhottelmann
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
You write about S920 again, I'm confused.. does your device really say "S920" on the label?
I think the Futro model with the AMD G-Series GX-424CC is a S930, not S920, but there seem to be mixed results and descriptions on the internet. At least the Fujitsu spec sheet lists the AMD G-Series GX-424CC as being used in an S930, maybe the other websites got it all wrong, could be, I am not 100% sure. My S930 has AMD G-Series GX-424CC (quad core), while all my S920 are dual cores (AMD G-Series GX-222CC).
Data Sheet FUJITSU Thin Client FUTRO S930 (using AMD G-Series GX-424CC):
EDIT: Correction, the AMD G-Series GX-424CC is indeed listed for both models, weird! o)
support.ts.fujitsu.com
I think the Futro model with the AMD G-Series GX-424CC is a S930, not S920, but there seem to be mixed results and descriptions on the internet. At least the Fujitsu spec sheet lists the AMD G-Series GX-424CC as being used in an S930, maybe the other websites got it all wrong, could be, I am not 100% sure. My S930 has AMD G-Series GX-424CC (quad core), while all my S920 are dual cores (AMD G-Series GX-222CC).
Data Sheet FUJITSU Thin Client FUTRO S930 (using AMD G-Series GX-424CC):
EDIT: Correction, the AMD G-Series GX-424CC is indeed listed for both models, weird! o)
Fsas Technologies Support pages EUROPE
Erfahre mehr über Fsas Technologies: Unsere Mission, Werte und Standorte. Wir stehen für Innovation, Nachhaltigkeit und Qualität.
support.ts.fujitsu.com
Sorry, could you explain how to use all the cores ? which is the OS ? Do you know if a bare metal Router Os by mikrotik would be 4 cores capable ?
@tbfutro22 @Samir @boerni666 Guys, thank you so much for your help with the RAM. The list of modules that you use in your S920s was very helpful. As I mentioned previously, I bought RAM from @tbfutro22's list, and this model works perfectly. I can confirm that I found an incompatible RAM module for the S920. Once again, many thanks for your help.
Yes, it is the s920 which did come with a 424cc in certain models. In fact, what's interesting about the s930 is that it looks almost exactly like an s920, almost like Fujitsu just changed the name and that's it. I even have two s920s and they're both 424cc.You write about S920 again, I'm confused.. does your device really say "S920" on the label?
I think the Futro model with the AMD G-Series GX-424CC is a S930, not S920, but there seem to be mixed results and descriptions on the internet. At least the Fujitsu spec sheet lists the AMD G-Series GX-424CC as being used in an S930, maybe the other websites got it all wrong, could be, I am not 100% sure. My S930 has AMD G-Series GX-424CC (quad core), while all my S920 are dual cores (AMD G-Series GX-222CC).
Data Sheet FUJITSU Thin Client FUTRO S930 (using AMD G-Series GX-424CC):
EDIT: Correction, the AMD G-Series GX-424CC is indeed listed for both models, weird! o)
View attachment 42323Fsas Technologies Support pages EUROPE
Erfahre mehr über Fsas Technologies: Unsere Mission, Werte und Standorte. Wir stehen für Innovation, Nachhaltigkeit und Qualität.
Unfortunately I cannot help you, I did not use "EditCMOS" yet, but maybe you can give some more details?
At what exact step do you get the error?
What exact command are you using?
Did you boot FreeDos from USB or floppy disk or ISO or something else?
If I remember correctly, there also is a setting in the BIOS to allow flashing the BIOS, maybe toggling that or some other related setting does the trick?!
At what exact step do you get the error?
What exact command are you using?
Did you boot FreeDos from USB or floppy disk or ISO or something else?
If I remember correctly, there also is a setting in the BIOS to allow flashing the BIOS, maybe toggling that or some other related setting does the trick?!
I was update BIOS, and then I start to update a value with EditCMOS.exe
After this command I got that information:
I was boot FreeDOS from USB.
When I check the PCI from live boot (Fedora) after update BIOS I got that info:
Is this a Gen 2 PCI Express network card ? Or ?
Also, I doesn't install a 4x1GB ethernet card when I try update EditCMOS.exe and when I check on live boot the info about PCI, so mayby is problem or I have PCIE Gen 2 speed?
Last edited:
So, if you successfully updated the BIOS, the flash protection is obviously not enabled.
I can't tell if the commands you used tell you the current PCI Gen mode the port is running in or if you only get what mode the PCI card is capable of.
I checked my PCI Gen setting with a read/write test on a PCIe NVME drive, if you get around 2000mb/s, you are running Gen2 mode (in the 4x slot).
I can't tell if the commands you used tell you the current PCI Gen mode the port is running in or if you only get what mode the PCI card is capable of.
I checked my PCI Gen setting with a read/write test on a PCIe NVME drive, if you get around 2000mb/s, you are running Gen2 mode (in the 4x slot).
And please insert a PCIe Gen 2 capable card into the PCIe Slot or mini-pcie socket.
I think the only onboard component using PCIe is the 1gbit Ethernet, and even that still uses PCIe Gen 1 if the editCMOS hack is used.
Maybe just run:
If we see sth like this:
we can tell.
A 4x1GB utilizing a PCIe x4 Gen 1 Interface should also just run fine without the EditCMOS hack. It still got 2.5GT per Lane
I think the only onboard component using PCIe is the 1gbit Ethernet, and even that still uses PCIe Gen 1 if the editCMOS hack is used.
Maybe just run:
Code:
sudo lspci -vv | grep -E 'LnkCap'
Code:
LnkCap: Port #5, Speed 5GT/s, Width x4, ASPM not supportedA 4x1GB utilizing a PCIe x4 Gen 1 Interface should also just run fine without the EditCMOS hack. It still got 2.5GT per Lane
Ok, I plugged a 2x1GB ethernet card Intel Pro 1000.
Then I try to use EditCMOS but error was the same.
I install a linux (Fedora only because I got that quickly on my USB).
And I try your command.
I got that from
Code:
sudo lspci -vv | grep -E 'LnkCap'
What this mean ? Because I am little bit confuse...there is Supported Link Speeds: 2.5-5GT/s but I don't know what this mean and how I can check what port is related to NIC card ?
BTW! You use an Intel PRO 1000. I can see that there is an Card installed which uses the x4 Width, is that the Card?
Intel PRO 1000 is quite old! it would use the x4 width, but still run only with PCIe 1.1. It would never show LnkCap of 5GT/s
also, PCIe Gen 1 is quite sufficient for an Dual Port 1Gbit Card utilizing an x4 interface.
Intel PRO 1000 is quite old! it would use the x4 width, but still run only with PCIe 1.1. It would never show LnkCap of 5GT/s
also, PCIe Gen 1 is quite sufficient for an Dual Port 1Gbit Card utilizing an x4 interface.
I changed bios options "after power restore" to disabled, set disabled to wake on lan/usb.. and still when I run shutdown -h now or poweroff command, my futro would shutdown and in a 1-2 seconds start booting. Am I missing something?
EDIT: upgraded bios, played with settings - now it stays shutdown when I expect it to
EDIT: upgraded bios, played with settings - now it stays shutdown when I expect it to
Last edited:
I also get your error message when using FreeDOS v1.4. I used regular MS-DOS before and running EditCMOS.exe worked fine, so that FreeDOS might not be compatible?! I was not aware of any compatibility issues and without much thinking, I overwrote my existing MS-DOS USB drive with that FreeDOS. I installed that from the FreeDOS Live-ISO, which was a hassle already, but now it seems, I have to get that MS-DOS onto the USB drive again. Not sure how I did that some years ago, bummer! o)
I just wanted to have a "better" DOS which would allow me to edit files with "edit.exe" and TAB auto-completion when switching directories. That did not work out (correction: That actually works all fine now, but the Fujitsu executables don't seem to run anymore, so.. not really a win!).