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."
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
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.
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
Got friends?
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!
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.
If tits were wings it'd be flying around.
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.
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.)
Kid-proof tablet..