Language Selection

English French German Italian Portuguese Spanish

BIOS Flash update under linux.

Filed under
Linux

I figured it was finally time to do a BIOS update on one of my main Linux boxes. The MSI NF 980-G65 AMD motherboard came with an AMI BIOS dated September 2009. This MSI motherboard is based on the NVidia NForce 980a chipset, and has built-in NVidia GeForce 8300 video (which I do not use).

Powering up this system has always been a little flaky, requiring a couple of reset-button presses before it would boot into Linux (it would hang at the BIOS splash screen). After boot-up, the system always ran great.

Alright, so on to the BIOS update. MSI has the live update online program which requires, of course, Microsoft Windows, and the Internet Explorer browser. Well, I don't have these on this system, and don't want to put them on it.

In the AMI BIOS setup program, I see the M-Flash option. I try this, but can't get it to work. Some research on the Internet indicates that it's very likely you'll wreck your BIOS using M-Flash anyway, so that's out.

After googling about, I finally go to this site to see how to flash a motherboard bios from linux with no DOS, no MS Windows, and no floppy-drive.

This technique involves getting a freedos DOS floppy boot image, mounting this floppy image temporarily using mount loop, copying the flash exe and rom files to the mouted floppy image, and burning this to a CD. So you end up with a bootable DOS CD with your two flashing files on it. You then boot your computer from the CD and flash your motherboard.

This all works fine, and I flash the motherboard with the new BIOS version.

Upon reboot, the system seems sluggish, and I can't boot into a GUI. After reading the error messages when I try startx, I see that the nvidia blob driver is trying to use the built-in NVidia card rather than my slotted PCI-E NVidia GeForce 460 card.

Back into the BIOS setup--set the PCI-E as primary, and disable the SLI hybrid setting.

OK, reboot, and I now have a GUI. But it's incredibly sloooooow. It's so slow, I can't re-size a konsole terminal. Turning off desktop effects compositing helps a little, but I finally see what everyone is complaining about with slow NVidia-KDE4 performance. But come on! After all, this is an NVidia GeForce GTX 460 256-bit memory 1024 GDDR5 ram card here. I spent over $200 on this card because I use the system for video editing.

I go to the KDE NVidia performance tuning site and read all the info. I copy and paste this stuff into the device section of my /etc/X11/xorg.conf file:
------------------------------------------------
Option "RenderAccel" "true"
Option "UseEvents" "false"
Option "TripleBuffer" "1"
Option "DamageEvents" "1"
Option "BackingStore" "1"
Option "PixmapCacheSize" "70000"
Option "OnDemandVBlankInterrupts" "true"
-------------------------------------------------

Reboot, and this does the trick! My system performance is back to normal. But, remembering back when I built this box, I bought very fast rated memory, so I went back into the BIOS setup and optimized the RAM timings. Now, I have a system faster than I ever had before. And the icing on the cake is, it's very, very stable. Boot problems are gone. No freezes or lockups.

It is a mystery to me why the BIOS update initially screwed-up the NVidia video performance.

More in Tux Machines

Linux 4.14-rc2

I'm back to my usual Sunday release schedule, and rc2 is out there in all the normal places. This was a fairly usual rc2, with a very quiet beginning of the week, and then most changes came in on Friday afternoon and Saturday (with the last few ones showing up Sunday morning). Normally I tend to dislike how that pushes most of my work into the weekend, but this time I took advantage of it, spending the quiet part of last week diving instead. Anyway, the only unusual thing worth noting here is that the security subsystem pull request that came in during the merge window got rejected due to problems, and so rc2 ends up with most of that security pull having been merged in independent pieces instead. Read more Also: Linux 4.14-rc2 Kernel Released

Manjaro Linux Phasing out i686 (32bit) Support

In a not very surprising move by the Manjaro Linux developers, a blog post was made by Philip, the Lead Developer of the popular distribution based off Arch Linux, On Sept. 23 that reveals that 32-bit support will be phased out. In his announcement, Philip says, “Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture. The decision means that v17.0.3 ISO will be the last that allows to install 32 bit Manjaro Linux. September and October will be our deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging will no longer require that from maintainers, effectively making i686 unsupported.” Read more

Korora 26 'Bloat' Fedora-based Linux distro available for download -- now 64-bit only

Fedora is my favorite Linux distribution, but I don't always use it. Sometimes I opt for an operating system that is based on it depending on my needs at the moment. Called "Korora," it adds tweaks, repositories, codecs, and packages that aren't found in the normal Fedora operating system. As a result, Korora deviates from Red Hat's strict FOSS focus -- one of the most endearing things about Fedora. While you can add all of these things to Fedora manually, Korora can save you time by doing the work for you. Read more

BackSlash Linux Olaf

While using BackSlash, I had two serious concerns. The first was with desktop performance. The Plasma-based desktop was not as responsive as I'm used to, in either test environment. Often times disabling effects or file indexing will improve the situation, but the desktop still lagged a bit for me. My other issue was the program crashes I experienced. The Discover software manager crashed on me several times, WPS crashed on start-up the first time on both machines, I lost the settings panel once along with my changes in progress. These problems make me think BackSlash's design may be appealing to newcomers, but I have concerns with the environment's stability. Down the road, once the developers have a chance to iron out some issues and polish the interface, I think BackSlash might do well targeting former macOS users, much the same way Zorin OS tries to appeal to former Windows users. But first, I think the distribution needs to stabilize a bit and squash lingering stability bugs. Read more