- #162
old486whizz Hi there,
Could you please send us a picture of SN on the bottom of the PC, we will check if you need to update the BIOS
old486whizz Hi there,
Could you please send us a picture of SN on the bottom of the PC, we will check if you need to update the BIOS
Mine installed pretty fine, but it turned out it was the same build and apparently “the latest”.
Thank you for your reply. If it is the latest BIOS, then no update is needed.
A. Hartmann Regarding the amdgpu power issue for firefox videos I tried using amdgpu.dpm=0 and it worked. Later i decided to switch from grub to systemd-boot and forgot to add this param but found out that I didn’t have the issue anymore.
coatlicue89 Thanks for your help and feedback.
coatlicue89 correction, seems to be failing again after a linux-firmware upgrade so I guess what happened is that when i installed systemd-boot I ended up downgrading the amdgpu driver version.
coatlicue89
Here are some potential solutions:
①. Confirm the driver and firmware status.
Check the currently loaded amdgpu driver version: dmesg | grep amdgpu
Check the installed firmware package version: apt list –installed | grep linux-firmware
②. Synchronize the driver and firmware versions.You can update driver from this website.kernel.org
Hi all.
SER9-AI-9 64Gb/2Tb here.
Same problem in Fedora42 with kernel 6.14.2-300.fc42.
System randomly reboots itself with no apparent cause.
Seems like setting “power_dpm_force_performance_level” to “high” via UDEV worked for me (currently testing).
Having trouble with suspend/resume. Fan goes crazy and system hangs. Hard reset is the only way to restart PC.
Thank you for your support.
Please send us a picture of SN number and BIOS version .
So we would be able to know whether it is latest BIOS and send you files accordingly.
https://mega.nz/#F!yuISGa4I!s1bQQajKwnsEdzjqq4nopQ
support4
Thanks for your reply. I’ve done it on the BIOS update thread.
support4
Thank you. Already upgraded. No more crashes even without kernel or udev parameters.
BTW, i would like to share another bit of info about linux on SER9: if someone else (like me) has an Intel AX200 wifi card, beware that it will never work out of the box cause this controller has problems with pci steering if installed in a x2/x4/x8/x16 pci lanes slot. Seems to me that’s the case.
I wonder if SER9-AI-9 is compatible with an Intel Killer BE200 card.
Still having issues with suspend/resume (full fan speed when suspended, rtl8125 network loss after resume).
Everything else works fine.
Damn…
Seems that Mediatek and Qualcomm are the way to go…
Scrambler
Like you, I have a SER9 64GB and I am trying to upgrade to the T302 BIOS version.
The .docx guide at point 5 says “Start flashing, after the flashing is complete […]”, which seems to imply that the flashing should start automatically as one boots from the USB drive. That’s not what happens to me, though.
What was your experience with the BIOS upgrade?
Guide might be a little misleading.
Flashing does not start automatically when booting from the USB drive. It starts a UEFI shell.
First thing you see is a list of detected filesystems labeled “fs#”.
You have to search for your USB storage media (usually tagged as “Removable BlockDevice”). It may vary and will be labeled as fs1: or fs2: …and so on…
You have to type fs#: (where # is your removable media number - don’t forget the colon symbol) and press ENTER.
The prompt should change from Shell>to fs#:> accordingly.
Type dir and press ENTER to check that you’re inside the correct drive. You should see a file named “flash.nsh”.
If so, type flash and press ENTER, then follow scripted instructions.
The script should flash SERT302.rom automatically.
Reboot when finished and you’re done.
Beware the first reboot may take a while.
profsantini
Hi there
We have tutorial for updating BIOS.
Please send us a picture of SN number and BIOS version .
So we would be able to know whether it is latest BIOS and send you files accordingly.
Here`s how to check your BIOS version:
or try this
https://mega.nz/#F!yuISGa4I!s1bQQajKwnsEdzjqq4nopQ
Scrambler
Yes, that worked. The actual flashing happened after a first reboot, where a menu appeared, and I pressed ENTER on the relevant item (“Start Flashing…” or something, I can’t remember what it said exactly). I assume it was the same for you.
Still, while I can successfully boot into a live USB Linux (e.g., Fedora), after completing the installation, as I get past the bootloader, the screen goes black. I suppose this happens when switching to modesetting. Booting Fedora in “rescue mode” works.
Other people don’t seem to have this issue, so I suspect it must be some issue between the graphics driver and my screen setup (I am connecting a DELL U3425WE through Thunderbolt 4).
support4
I was running the SER9T301 BIOS on a SER9 with SN starting with DHX375.
I performed an update to SER9T302 without any particular issue. However, the provided guide “SER9-T302–Use-USB-to-flash-BIOS-.docx” is incomplete as discussed above.
OK, connecting the monitor through a DisplayPort works. It’s the Thunderbolt 4 that is problematic.