Secrets Of BIOS Tweaking
Sivar writes "While most enthusiasts are familiar with some settings that yield significant performance benefits, many other BIOS settings remain poorly described and may unknowingly play a crucial role in system performance and stability. Ars Technica has an excellent article describing some of the most obscure settings, useful not only for performance, but for tweaking stability and hardware compatibility as well."
Just a tip: If you have trouble booting LILO with a USB keyboard try enabling Legacy USB support in the BIOS. It worked for me on a Dell GX240 Optiplex when all I would get is a Keyboard failure notice. You may also have to turn off "halt on error".
"God fights on the side with the best artillery." - Napoleon, Marshal of France - speaking truth to power
Disable that pesky PnP in the BIOS. Could've saved quite a bit of hair pulling on a FreeBSD 4.6.2 install.
THG has had a good BIOS guide as well:
1 /index.html
e x.html
http://www6.tomshardware.com/mainboard/97q1/97010
and also a guide on BIOS tuning:
http://www.tomshardware.com/howto/01q3/010725/ind
THERE IS NO DATA. THERE IS O
Hmm, BIOS means Bandwidth Instantly Obliterated by Slashdot?
I always wondered about the fact that (almost?) no manufacturer supplies a manual describing their BIOS setup in detail. Most of them mumble something like: "you can press DEL to fiddle around with things you will never comprehend during your lifetime" and that's about as much help as you get. They of course also have included this neat *sarcasm;)* help function in most BIOS setups that displays the context sensitive help. I don't know how often i pressed F1 in vain just to see the message: "Help: Enable A-20 Gate. PG UP=on PG DN=off" Stuff like that...
There sure has a reason to be for the lack of good documentation. The best manual uptill now was the one that came with my old ABIT KT7a RAID mobo, but maybe that's because back in those days it was considered a home "tweakers" board. So mr. Phoenix, Award, AMI, if you read this, please o please bundle nice manuals with your BIOS setups for us endusers to use, instead of hoping for great sites like Ars Technica and Tom's Hardware to help us out.
about the memory hole at 16M:
"Sound Blaster Live cards like this to be enabled. It essentially removes 1MB of your RAM, so consider replacing the sound card instead."
Yeah, it would suck to have only 511 megs available. I'm not giving up my SB Live any time soon, at least not till I decide to get Audigy. It does mention that this is for SB16 emulation, but doesnt clarify by saying you only need that if you want legacy DOS soundblaster support. It's actually wrong: SB16 emulation happens transparently, SB16 pseudo-emulated 'mode' requires this. (Booting into plain DOS rather than running in a Win2k/XP console)
On the Video RAM Cache:
"Disable this. You don't want to be wasting the L2 cache on fast video RAM when you have slow system RAM to deal with"
Not every box has a sooper-dooper fast mega-card in it. I have boxes with old Cirrus Logic and Mach64 cards in 'em. And not every PC is equipped with AGP. Enabling this can yield a performance boost on some hardware, a little more detail here would help.
I dont have time to analyse the whole thing.. It got slashdotted before I could make it through, and I'm not a know-it-all techie geek. I just have enough rope to hang myself with, as the saying goes.
But like most 'BIOS' guides I've read, this gives alot of info on 'tweaks', with little mention of the damage that the wrong settings can do. I've seen RAM, PCI and AGP cards get fried because the user unwittingly 'overclocked' it.
They always just tell you what the fastest possible setting is, but never mention "if your hardware doesn't support it, you'll wreck it". Personally I think sacrificing stability for the sake of a 1% theoretical boost in performance is bad mojo.
There's also a disproportionate amount of Soundblaster-bashing going on here. Apparently my SB Lives have been crashing my systems and suffering poor sound latency for the last couple of years. Funny that I never noticed.
I don't need no instructions to know how to rock!!!!
Optimizing your BIOS settings is not enough to prevent your server from being slashdotted...
Replacing your legacy BIOS with LinuxBIOS yeilds the best overall system performance gains.
SPD, ACPI and PCI init and config is still quite a mess these days. Using an open source BIOS allows system performance to be tuned and maximized beyond what the usual legacy BIOS setup screens offer.
Quidquid latine dictum sit altum viditur
The BIOS of the x86 world, in my opinion, is one of the reasons why we struggle but never quite reach a integrated architecture for PCs. Lord knows I've fought with quite a few of them, and hated having to remember to disable this in order to use that, with no guarantee that my change would work all the time.
Shouldn't our computers know what hardware it holds and configure itself automatically nowandays, with little to no user interaction? It would make all that "plug-and-play" stuff that's taken for granted on Macintosh systems, to site an example, true for my PC game box as well.
The technology is already here in the form of Open Firmware, which Apple uses as well as Sun. There is at least one company that has OF implementations for x86, but so long as Intel has a vendor lock on how motherboards are designed for their chips, I don't see this annoying and archaic method of maintaining a board going away any time soon.
OF is configurable enough for crazy whiz kids, if necessary. A better BIOS would make things a lot better for the OS and bring a better experience. Why can't we break out of the BIOS hell? Hadn't we learned the lessons from the Y2k-incompatibilities that some BIOS had, among other headaches?
Vos teneo officium eram periculosus ut vos recipero is.
If I have an obscure Taiwan motherboard, this place almost always has a link to find the latest BIOS for it:
http://www.wimsbios.com/
I'm sure it's old hat for most people here, but some people will probably need it to find their latest bios to use this guide.
"TK-421, why aren't you at your post?"
Go relax with some good ol' Adrian's Rojak Pot.
Strange that the linuxbios link provided above is to a commercial website. Here's the link to the proper linuxbios site, at linuxbios.org.
:wq
Is it under File or Edit? I didnt see it under View or Favorites. I clicked on the Help one but it just laughed at me.
"Back then, we didn't have drivers"
yes we did.
"Long before the term "API" was born"
I have a hardware book on the original 8088 IBM PC published in 1985 that includes specs on the bios and boot loader software, and talks of APIs.
"You could call BIOS ROM routines to handle video, PC speaker beeps, the keyboard, and so forth."
That is, if you only wanted your program to be able to run on that ONE model of PC. To get to hardware, nobody programmed to teh BIOS, they programmed using DOS interrupts.
"Remember, in those days, people didn't build their own systems"
Yes we did. I replaced the mobo on my XT with a 386 mobo. By then the only original components in that box were the case, power supply, and keyboard.
The original 8088 mobo used jumpers and dip switches where we now make the adjustments in BIOS.
Maybe he's a whiz on modern BIOSes, I don't know. But he's sure clueless about primitive PCs. Knowing this, I have to take everything he says with a grain (or whole damned shaker) of salt.
I love the "helpful" BIOS messages...
o ACPATI IEEE 9.0 compatability : ON | OFF
Help -- This settiong turns on or off ACPATI IEEE 9.0 compatability.
o CPU LIMIT PRIMER : FREE | POST | RETRAIN
Help -- This setting sets the primer for the CPU LIMIT
o DARNING PORT FLANGE : WITHIN | OVER | COMPLIANT
Help -- This setting alters the darning on the PORT FLANGE
"Your superior intellect is no match for our puny weapons!"
My SBLive doesn't do any of that nasty latency-related stuff either... but normally you'll only see that on VIA chipsets (it's a well-known issue there) and I run pure Intel chips. And mine works fine so long as its lame-assed DOS emulation is disabled. When that's enabled, it NUKES Windows, and doesn't work anyway.
As to the 15/16MB memory hole, IIRC (and IIUC) when it's enabled, it prevents any DOS program from using memory above that point, because DOS can't jump the gap like a fully protected-mode OS can. If you run big DOS games or databases in real DOS, this can be an issue, in which case the memory hole must be disabled or stuff won't work or will be really slow due to swapping to disk when it runs out of the first 15MB of RAM.
So it doesn't exactly "remove" 1MB of RAM; it limits DOS on your system to a mere 16MB usable RAM, no matter how much physical RAM you have.
Some older memory managers do the same thing.
~REZ~ #43301. Who'd fake being me anyway?
Consider the memory options listed in the article. Do you know what the 15M-16M memory hole is? Autodetect DIMM/PCI Clock? Bank Interleave? The article says Bank Interleave gives you a massive performance benefit, why then have an option to turn it off? What's the point?
Data Integrity Mode? Don't you think it would be nice if your computer knew whether it had ECC ram in it or not? Delay DRAM Read Latch? The article says that if you don't set it right, you can get crashes in your machine. Golly, don't you think manufacturers should just make the computer get it right?
Memory options go on and on and on. The only thing I want to know is that my computer can read whatever memory is installed at the highest reliable speed. I shouldn't have to tweak the no less than two dozen different settings to
get my machine working reliably, and those are just the memory related ones. A similar number awaits in the PCI and AGP configuration settings.
Legitimate uses of the BIOS are perhaps to enable or disable peripherals and to choose boot devices. It might also be nice to have a mode which shows what peripherals are installed. Other than that, I'm perfectly willing to allow the computer to pick out its working parameters. If the resulting computer proves to be unreliable, then the manufacturer should be out of business for making crappy computers.
Rant concluded.
There is much pleasure to be gained in useless knowledge.
I was poking around the Vcore settings on my ASUS board with an Athlon XP 1700 processor. The settings range from the expected 1.675V - 1.85V, but if you hold down the righthand Alt key and then Page Up and Page Down, you get values ranging from 500kV to 1.5MV in 50kV intervals.
Does anyone know why these settings should exist?
Their they're doing there hair.