Slashdot Mirror


Finding BIOS Upgrades?

CrazyDwarf asks: "I dug up and old system that my company was about to toss in the dumpster and decided to load Linux on it. My problem: the BIOS will not recognize more than 500 MB of the HDD. I don't have a CD-ROM for this PC. I was looking for a BIOS upgrade download, but AWARD wants me to buy it from some third party. If I could afford to buy it from them, I wouldn't be doing all this, I'd just get a CD-Rom and move on. Where are some good places for me to go find a free (no cost) download to upgrade my BIOS? I have been searching for an hour on Google and have not really found anything."

33 of 83 comments (clear)

  1. How old? by Jester998 · · Score: 4, Informative

    Hmm... depending on how old the system actually is, it might not even HAVE downloadable BIOS updates. IIRC, most 486 systems and even some 586-based systems didn't have Flash ROMs... to upgrade the BIOS, you had to physically replace the BIOS CMOS.

    If the motherboard does, indeed, have a flashable BIOS, then try looking up the part/model number on either the manufacturer's site or Google.

    - Jester

    1. Re:How old? by Pogue+Mahone · · Score: 3, Interesting

      The old MoBos used to have socketed EPROMS for the BIOS - quite easy to replace, as long as you have a programmer. But buy a new device, so that if all goes pear-shaped you can plug the old one back in. Anyway, you don't need your BIOS to recognise more than 500MB. Simply make a small partition (10MB should be enough) at the start of the disk, and put your kernel etc. there. Mount it as /boot. That should work with most good distros. Apart from boot time, a Linux system doesn't need the BIOS. The only exception to this BIOS problem that I know of is with some old caching disk controllers. I have one that has a 2048-cylinder hard limit in the controller, which limits the disk size to about 1 GB. But that was in an absolutely ancient (ca. 10 years old) 486i - all ISA.

      --
      Every bloody emperor has his hand up history's skirt [Peter Hammill/VdGG]
  2. There is an workaround by ljaguar · · Score: 3, Informative

    Boot from floppy.

    Your problem is that you can't _boot_ from a HD larger than 500MB -- because as soon as Linux kernel is loaded, BIOS isn't needed any more anyways. All you need to to is load the kernel somehow and all the limitations of BIOS doesn't exist anymore.

    Then whatever you've got connected to IDE (zip, cdrom, any HD) will work because Linux kernel is up-to-date with things.

    To repeat myself, after Linux kernel is loaded, the kernel takes over. BIOS simply isn't consulted again.

    Of course, some other OS's like DOS still accesses disk through BIOS, so DOS wouldn't work.

    1. Re:There is an workaround by polymath69 · · Score: 2
      Your problem is that you can't _boot_ from a HD larger than 500MB -- because as soon as Linux kernel is loaded, BIOS isn't needed any more anyways.

      Wouldn't it also work to simply put a /boot partition in the first several cylinders of the disk? I think, then, that no floppies would be needed.

      --

      --
      I don't want to rule the world... I just want to be in charge of mayonnaise.
    2. Re:There is an workaround by ninewands · · Score: 4, Informative

      Wouldn't it also work to simply put a /boot partition in the first several cylinders of the disk? I think, then, that no floppies would be needed.

      You are correct sir ...

      It is my understanding that a separate /boot partition will force the kernel down into the part of the disk that the ROM-BIOS can handle. The first 10 MB should give room for multiple kernels, etc.

      Once the kernel is loaded, the IDE drivers will handle the disk at the hardware level and BIOS limitations become moot.

      I've never had to fight with the 500 MB limit, but the kernel handily defeated the 2 GB limit of my old P166-MMX mobo ...

    3. Re:There is an workaround by mclearn · · Score: 2

      I thought that this is what the user-mode (mode 42? 43?) was for. So long as you could put in the correct (or compatible) CHS values, the BIOS would happily churn away, even if the values did not address the entire disk.

    4. Re:There is an workaround by MrResistor · · Score: 2

      It is my understanding that you are the one who is wrong, because you are proscribing to Linux the limitations of DOS.

      DOS uses the BIOS for disk access during normal operation, hence the limitations you describe. Linux uses the BIOS only to load /boot, which should be easily accessable by the BIOS as long as it is a small primary partition in the first cylinders of the drive.

      The hard part will be setting the partitions, which may have to be done on a motherboard that doesn't suffer those limitations.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  3. There's a special boot loader, er disk overlay by hackwrench · · Score: 2

    for hard drives that replaces the bios.

    Relevant Search

    1. Re:There's a special boot loader, er disk overlay by ninewands · · Score: 2

      This sounds like something like Western Digital's "EZ-Bios" ... which even WD's Tech Support recommends that people NOT use unless there is NO other choice.

      Since it is possible to finesse the BIOS limitation with a small /dev/hda1 of say, 10 MB, EZ-Bios and its equivalents sound like A Very Bad Idea(TM).

    2. Re:There's a special boot loader, er disk overlay by PD · · Score: 2

      I used EZ-Disk (I think that's the actual name) and it worked just fine. The Lilo manual said that it was compatible, and my computer was having a lot of trouble seeing the 11.5 gig disk.

      That was a while ago though, I don't know how it would work with a larger disk.

    3. Re:There's a special boot loader, er disk overlay by PD · · Score: 3, Informative

      OK, we were both wrong. It's EZ-Drive

      I found the large disk howto, and it says:

      Linux does support OnTrack Disk Manager since version 1.3.14, and EZ-
      Drive since version 1.3.29. Some more details are given below.


      And then below, it says:

      5. Kernel disk translation for IDE disks

      If the Linux kernel detects the presence of some disk manager on an
      IDE disk, it will try to remap the disk in the same way this disk
      manager would have done, so that Linux sees the same disk partitioning
      as for example DOS with OnTrack or EZ-Drive. However, NO remapping is
      done when a geometry was specified on the command line - so a
      `hd=cyls,heads,secs' command line option might well kill compatibility
      with a disk manager.

      The remapping is done by trying 4, 8, 16, 32, 64, 128, 255 heads
      (keeping H*C constant) until either C

      What that means is that if you're using Linux, you probably don't need this thing. You just put your kernel in the first part of the disk that the BIOS can see and pass the parms to the kernel on the lilo boot line.

      If you're dual booting with Windows, then you probably will need this EZ-Drive. And in that case, you do NOT want to specify the hd parameters to the kernel. The kernel knows about EZ-Drive and will do the right thing.

    4. Re:There's a special boot loader, er disk overlay by PD · · Score: 2

      EZ-Drive has a configuration menu that you can operate.

      You boot from the hard drive, then EZ-Drive loads, then EZ-Drive gives you a menu that you can use to boot off the floppy.

      I don't know about booting from the CD-Rom, but you are almost certainly right about booting from a zip or scsi drive. EZ-Drive is not the best software, but Linux DOES know about it and will do the right thing when it sees it.

    5. Re:There's a special boot loader, er disk overlay by twilightzero · · Score: 2

      Ok, first let me state that I WORK for WD tech support, hence I'm probably the most qualified person to answer this question, also there will be stuff in here that's my opinion and not the one of the company .

      Now, having said that, let me address the issue of EZ-BIOS. I don't know where you heard that we don't reccommend it, but from what I've seen on other posts here a lot of people are basing the descriptions of it on OLD versions of our software (and therefore of EZ-BIOS). We haven't used OnTrack for our software for several years now. What we DO reccommend is not using EZ-BIOS on a system that doesn't need it...that makes sense, doesn't it? Linux with kernel version 2.2 or above (I believe, or is it 2.0? Anyway if you're still running 2.0 or below I would HIGHLY reccommend upgrading), Win2k or Win XP don't need BIOS support, so we tell people don't use it with those OS'es. In cases like that, we just have them set it up in the BIOS as type User, 1023 cylinders, 16 heads, 63 sectors, and mode of Normal (or LBA Mode disabled). This sets the drive up as about 528 MB and allows the BIOS to boot to the drive, load up the kernel/ntldr, and continue on its merry way. Again, we do NOT reccommend EZ-BIOS for use on systems like this because it's not needed.

      On the other hand, anybody with Win9x and a system with a BIOS limit (8.4 or 32 GB limit most often) are probably going to be best off using it. In the over 1 year I've been working here, I think we've had ONE single call with a computer where EZ-BIOS wouldn't work on the system. Now there are other circumstances where EZ-BIOS may have a conflict with another piece of software on the computer. Most software that writes to the boot track or tries to control the boot process is not going to work with it; common culprits include Roxio GoBack, System Commander, and Partition Magic (which writes its own info in the partition tables and basically makes the partitions unreadable by anything else).

      --

      "Christ what a design! I could eat a handful of iron filings and PUKE a better emergency pump than that!"
  4. Pretty old system by MrResistor · · Score: 2, Offtopic

    Old enough, by the sound of things, that running X would likely be painful. You should be able to squeeze a non-GUI install into 500M without too much difficulty. Check out TinyApps for so small distros.

    --
    Under capitalism man exploits man. Under communism it's the other way around.
    1. Re:Pretty old system by david+duncan+scott · · Score: 2
      I don't think TinyApps is what you meant:
      Virtually all of the programs listed here are free of charge and for use under Windows..."How about BeOS, *nix, Amiga, QNX, etc?", I am asked. Those who are comfortable using these operating systems need no such guide as this...
      I did google up some tiny Linux directories here and here, and of course there's TomsRtBt.
      --

      This next song is very sad. Please clap along. -- Robin Zander

    2. Re:Pretty old system by MrResistor · · Score: 2

      You are correct. I remembered TinyApps having links to some Tiny Linux distros, but apparently I remembered wrong.

      Thanks for the real links.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  5. How I find old BIOS by itwerx · · Score: 2, Insightful

    1 - Search Google for your complete mbd model# (in quotes if there's any dashes in it)
    2 - Somewhere in the search results there will be a link or reference to an appropriate file.
    3 - Try to download the file; if you can't then do another search using just that filename (in quotes again).

    This has always worked for me.

    (Aaack! I just replied to an "Ask Slashdot" and told them to use Google!
    And here I swore I'd never reply to another troll...)

  6. Openbios might be tha ticket by Cardhore · · Score: 4, Interesting

    OpenBIOS might work on your board.

    OpenBIOS will be a free portable firmware implementation. The goal is to implement a 100% IEEE 1275-1994 (Referred to as Open Firmware) compliant firmware. Among it's features, Open Firmware provides an instruction set independent device interface. This can be used to boot the operating system from expansion cards without any native binary code. Thus it is OpenBIOS' goal to work on all common platforms, like x86, Alpha, x86-64 and IA-64. Additionally OpenBIOS targets the embedded systems sector, where a sane and unified firmware is a crucial design goal. Open Firmware is found on many servers and workstations and there are several commercial implementations from SUN, Apple, IBM, CodeGen and others. More information on OpenBIOS is available on the About OpenBIOS page

    1. Re:Openbios might be tha ticket by MisterManiac · · Score: 2

      On a similar note, LinuxBIOS is some sort of ubercompressed, stripped-down linux kernel with some hardware-specific instructions that replaces a conventional BIOS, and then can activate a second-level boot loader like LILO. I don't know motherboard models, so I'm not sure if the project is geared more toward servers. The list of supported motherboards is here.

    2. Re:Openbios might be tha ticket by sporktoast · · Score: 3, Funny

      I'm sorry, sometimes it takes me a few tries to understand some things.

      Are you saying that this is some sort of pipe dream or something?

      --
      In a related story, the IRS has recently ruled that the cost of Windows upgrades can NOT be deducted as a gambling loss.
  7. Two alternate solutions by inkfox · · Score: 5, Interesting
    Firstly, you can just boot off a floppy. The BIOS doesn't need to understand the drive, so long as the kernel does.

    Secondly, you can likely boot off the drive if you go into the BIOS configuration and manually specify the correct number of heads and cylinders/sectors and just fib about the number of tracks. If you boot Linux from a small boot partition at the start of the drive, you're likely just fine.

    --
    Says the RIAA: When you EQ, you're stealing bass!
  8. Re:Do what your company was doing. by EllF · · Score: 2

    Who says he planned on using KDE or GNOME? I'm running a 486 laptop without X installed, and it's blazingly fast - and very useful. I write papers on it with vim, print from it, connect to the net via links, check my email, and even play the occasional game of nethack.

    A slightly beefier system sits to my left - a P75, running Ion, which uses very few system resources. It has X installed, and is quite nice for doing development work.

    $200 is still a significant chunk of change - that's two months of food for me, or almost a month's rent, for example. A free system is not something to be turned up - you just don't install the bloatware that most people are clamoring for.

    --
    We who were living are now dying
    With a little patience
  9. The ultimate bios site by mikelobby · · Score: 2, Informative

    Be sure to try Wim' Bios page Click the award or ami bios id link at the top and you will be directed to a page the can identify the motherboard manifacturer based on the bios id (the string of numbers at the bottom of the screen during post). Armed with that knowledge, you can then go to that companies site and look for your particular board. It has helped me locate bios' for no-name boards many times. As an aside, I don't know much about Asian culture, but it seems to me they must know that some of their products are really crappy and thus don't put their company name anywhere on them. --Mike

  10. This guy sells programmed BIOS chips by unitron · · Score: 3, Informative
    Congratulations on not feeding the landfill. To look into replacing the BIOS chip for about $20 go to http://www.tuxshield.com/BIOS_order.htm and use the email at the bottom of the page to contact the guy. This assumes that you don't have a flashable bios chip and replacement is the only way to go. Of course you could be like me and have an old Zeos 486 board that has a flashable bios but they went out of business before writing an updated bios that'll recognize anything over 528. Bummer.

    It sounds as though you're trying to load the Linux CDs on a big hard drive, hook that drive up to the computer temporarily and load Linux on the machine's hard drive from the bigger drive instead of from a CD-ROM drive which you say the machine doesn't have. Consider temporarily installing a CD drive from some other machine and installing from that or temporarily installing a NIC from some other machine and installing via network.

    If I can help you with hard drive questions, get in touch.

    --

    I see even classic Slashdot is now pretty much unusable on dial up anymore.

    1. Re:This guy sells programmed BIOS chips by unitron · · Score: 2

      I suggest that you go to the page I referenced and ask him yourself. How much are you paying for blank chips?

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

  11. BIOS overlays... by adolf · · Score: 4, Insightful

    As some other posters have pointed out, you don't need to have BIOS-level access to the entire hard drive to get the machine to boot properly and run Linux. Just keep the bootable partition within the first 500 megs, and all is dandy.

    However, you might want to use a BIOS overlay, anyway. Makes things easier, and lets you do stuff like run ancient DOS games on the hardware they were meant for, or fire up OS/2 Warp for an old-school look at the future.

    On my 386SL-25 laptop, I'm using IBM's overlay software, which is freely downloadable as a bootable floppy disk image. Most other manufacturers also supply overlay software, free, but it generally requires you to install it on a machine with a drive of the same make; Maxtor's software needs to see a Maxtor drive somewhere in the system, or it will simply refuse to cooperate.

    This works fine with Linux, and has for a very long time. It just recognizes that the drive was partitioned with overlay software, and does the same sector translation on its own.

    I doubt there's even a speed hit.

    I used IBM's software because I have a bunch of their SCSI disks in the machine I was borrowing to do the Linux install with, and Hitachi stands almost alone as a vendor who doesn't supply overlay software of their own. (the laptop, sadly, has no floppy drive, CD-ROM, or other external storage, so I spent most of an evening swapping IDE cables trying to get the thing to boot.)

  12. No dumpsters, please! by fm6 · · Score: 2

    Not unless you like toxic metals in your coffee. Even if it's legal in your locale, it's hardly good citizenship to throw computer hardware into a landfill. If it's beyond use, take it to a recycler. Yes it costs. So does treating cancer.

  13. Re:Do what your company was doing. by MrResistor · · Score: 2

    Where are you living that rent is so high?

    I'm paying $625 for a spacious 2-bedroom appartment with a laundry room. Back when I did the roommate thing my rent was never over $300. $1200 would get me a 2- to 4-bedroom house, depending on location. I'm in California, so even that is a bit inflated compared to other parts of the country.

    $1200 for a 1-bedroom sounds like Bay Area prices to me. You do know that most of the rest of the country is significantly cheaper, don't you?

    --
    Under capitalism man exploits man. Under communism it's the other way around.
  14. Re:On a somewhat related note.... by ONOIML8 · · Score: 2

    "dont bother. anything below a p-66 will be painfully slow."

    Absolutely 100% NOT true! I am running several systems that are 386 and 486 based. I have one system that is a 386DX-40MHz which is running an email to alphanumeric paging gateway and doing some automated housekeeping on a network and the damn thing hums right along.

    I wouldn't want to use X on a 386, that's for sure. And on a 486 I would think twice about it, and run a very lite window manager (not KDE). But then again there are very few reasons to be running X anyway except for a desktop client.

    --
    . Quit playing Monopoly with Bill. Switch to one of many non-Microsoft products today.
  15. And the "death is fun" people chime in... by fm6 · · Score: 2
    Many of the components in coffee, even your pristine pure coffee brewed with organic beans and spring water, are carcinogenic. Perhaps you should stop drinking it.
    So what you're saying is, we can't eliminate all the possible causes of cancer, therefore we shouldn't try to eliminate any, and we especially shouldn't worry about creating new ones. Yeah, that makes sense!
  16. Re:On a somewhat related note.... by ShawnD · · Score: 2, Informative
    Absolutely 100% NOT true! I am running several systems that are 386 and 486 based
    I used to run a 386SX40 as a file server. The BIOS didn't even have a problem with the 20GB and 30GB drives. It has since been replaced by a 100MHz PPC and has also taken on DNS for the home LAN.

    Also note that some older Pentium's overclock well. I have a P75 that runs reliably at 133MHz. Just make sure you have a big heatsink (Like one for a P200 or similar). That may give you the performance you are looking for.

  17. A Fine Vintage BIOS... by fooguy · · Score: 2

    Chances are good that the vendor never updated the BIOS. Some of us remember the glory days when harddrive size had a BIOS limitation.

    You have two options:

    1) Buy a replacement BIOS ROM from someone like Mr. BIOS (yes, I said "Mr. BIOS")

    2) Use a Dynamic Drive Overlay (DDO). A DDO is a piece of software that is, in effect, a bootstrap virus. It loads code in the bootblock that builds a new drive map at boot time. While BIOS only seens four or five hundred megs, a DDO will get you to the next physical barrier (which, if I'm not mistaken is either 2GB or 4GB).

    DDOs were used successfully for a very long time, though I remember avoiding them at the time. They're creepy. Most HD vendors use to offer then for free (WD, Maxtor), you should be able to dig one up on an abandonware site.

    --
    "All I ever wanted was to see Larry Wall give Bill Gates a Perl necklace."
    http://www.eisenschmidt.org/jweisen
  18. Agreement! by twitter · · Score: 2
    I had the same problem. My solution was to use a 500 MB hard disk to boot. It might have worked if I simply partitioned a small boot device on a larger drive but I used the disk I had. The other disk is now a 2 GB, but it could just as well be 20 or 200 GB. The kernel does not use crusty old BIOS routines after boot and can see anything just as well on any machine.

    Making the second drive the home directory was as easy as dropping the hard drive in, formatting it with cfdisk, adding a file system with mkext2fs, coppying my files and changing a single line in /etc/fstab and rebooting. Rebooting was optional. It took way less time than fooling around with a bios upgrade that might or might not work. If ever I need another IDE channel, I've got an old 16 bit card that supposedly gives me one, but two devices are enough for me for now.

    Yep, the 66MHz 486 is still AOK as an ftp server. No GUI needed, never down for anything but power fails, always chugging along but always quiet. Thank you Debian.

    --

    Friends don't help friends install M$ junk.