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

Why Everyone should know vim

Vim is an improved version of Vi, a known text editor available by default in UNIX distributions. Another alternative for modal editors is Emacs but they’re so different that I kind of feel they serve different purposes. Both are great, regardless. I don’t feel vim is necessarily a geeky kind of taste or not. Vim introduced modal editing to me and that has changed my life, really. If you have ever tried vim, you may have noticed you have to press “I” or “A” (lower case) to start writing (note: I’m aware there are more ways to start editing but the purpose is not to cover Vim’s functionalities.). The fun part starts once you realize you can associate Insert and Append commands to something. And then editing text is like thinking of what you want the computer to show on the computer instead of struggling where you at before writing. The same goes for other commands which are easily converted to mnemonics and this is what helped getting comfortable with Vim. Note that Emacs does not have this kind of keybindings but they do have a Vim-like mode - Evil (Extensive Vi Layer). More often than not, I just need to think of what I want to accomplish and type the first letters. Like Replace, Visual, Delete, and so on. It is a modal editor after all, meaning it has modes for everything. This is also what increases my productivity when writing files. I just think of my intentions and Vim does the things for me. Read more

Graphics: Intel and Mesa 18.1 RC1 Released

  • Intel 2018Q1 Graphics Stack Recipe
    Last week Intel's Open-Source Technology Center released their latest quarterly "graphics stack recipe" for the Linux desktop. The Intel Graphics Stack Recipe is the company's recommended configuration for an optimal and supported open-source graphics driver experience for their Intel HD/UHD/Iris Graphics found on Intel processors.
  • Mesa 18.1-RC1 Released With The Latest Open-Source 3D Driver Features
    Seemingly flying under our radar is that Mesa 18.1 has already been branched and the first release candidate issued. While the Mesa website hasn't yet been updated for the 18.1 details, Dylan Baker appears to be the release manager for the 18.1 series -- the second quarter of 2018 release stream.

Exploring Contributors Centrality Over Time

At the end of my previous post we concluded with yet another question. Indeed, on the 2017 KDEPIM contributor network we found out that Christian Mollekopf while being a very consistent committer didn't appear as centrality as we would expect. Yet from the topology he seemed to act as a bridge between the core contributors and contributors with a very low centrality. This time we'll try to look into this and figure out what might be going on. My first attempt at this was to try to look into the contributor network on a different time period and see how it goes. If we take two snapshots of the network for the two semesters of 2017, how would it look? Well, easy to do with my current scripts so let's see! Read more

KDE: Elisa 0.1.1, KDE Plasma 5.13 and More

  • 0.1.1 Release of Elisa
    The Elisa team is happy to announce the first bug fix release for the 0.1 version.
  • KDE Plasma 5.13 Is Making Great Improvements On Its Wayland Support
    KDE Plasma 5.13 that is due for release in June will have a great number of improvements to its Wayland support for allowing the KDE Plasma desktop to work much better on this alternative to the X.Org Server. KDE developer Roman Gilg has provided a nice summary of some of the Wayland improvements in the queue for the Plasma 5.13.0 release due out towards the middle of June.
  • This week in Usability & Productivity, part 15
    I’ve initiated a big project: overhauling KDE Open & Save dialogs for greater usability and productivity.
  • Latte bug fix release v0.7.5
    Latte Dock v0.7.5   has been released containing important fixes and improvements! Hopefullly this is going to be the last stable version for v0.7.x family. During the next months the next stable branch (v0.8.x) is going to appear.