My computer continuously freezes. and I sometimes get this error message when I reboot: "Error 18 : selected cylinder exceeds maximum supported bv bios"lotuseclat79 said:The cardinal rule for flashing a BIOS is - don't try to fix it if it ain't broke!
Flashing a BIOS is very tricky, meaning that if you screw it up, it will cost you at least a new BIOS chip if not a new computer.
So, enlighten us all as to your process for rationalizing why you need to flash your BIOS?
A MSI k8N Neo 4 Platinum is a motherboard.While you are at it, please explain what MSI k2n Neo 4 is so I don't have to look it up. Where did you get the live update that you reference? Why do you not have IE? Where can we look at the instruction manual for the BIOS? Why can you not make a bootable Windows 98/ME boot disk?
And it says you can use the traditional download. It is important that having M$ OS is not a pre-requisite for maintaining a machine and flashing BIOS etc, so I'd complain to the manufacturer if their utility requires M$ Windows. Others have posted work round to get M$ boot disks, should non-Free solution be impossible.lotuseclat79 said:Ok, so you have an AMD 64-bit MB. The live update indicates you need a Windows OS running to install it.
What BIOS do you have (detail)? And, what is the Model Number of your MB?
So how would that effect Linux, when it accesses the HW directly rather than use BIOS calls?What I am most interested in knowing is why your think a BIOS upgrade will solve a problem where the computer freezes (as it probably should for some reason) and says: "Error 18 : selected cylinder exceeds maximum supported by bios"?
Have you tried going into the BIOS (check the bottom of the first screen that shows after you power on to see the keystroke needed to get into the BIOS)? What you should try to find out at this stage of problem solving is "what is the limit of maximum cylinder supported by the BIOS"?
At MSI web page :I'm guessing that was Windows - which Windows version as your posts seem to indicate win98/me?
Linux doesn't use the BIOS calls to access the disk, once it's loaded up. That's the reason you could boot off first 512MB in past, but access all partitions past that BIOS limit, on non-LBA BIOSes.Just because the BIOS supports a limit that has been reached does not mean that the BIOS is not doing its job which it should, or that anything whatsoever is at fault with the BIOS.
I suspect that you loaded Ubuntu without checking whether your MB/BIOS combination (which previously had a version of Windows) adequately is supports Linux (i.e. in the configuration for Windows as applied to Linux) - and, consequently, there may need to be some changes made to your BIOS which will comfortably solve your problem and may not require flashing the BIOS. You need to focus first on making this determination before deciding whether a newly flashed BIOS is the answer to solve your problem.
Well if you build your own system, you may well find you need to flash the BIOS for all kinds of reasons. Having a PC from a name manufacturer is very different. They sort out this stuff for you and will be disapproving if you go and meddle with their stuff.lotuseclat79 said:The only BIOS I ever considered flashing and even bought a flash upgrade for was a VIA board until I found out that the problem I was having was a couple of blown caps on the MB. Since I needed a new MB at the time and my disks had recently been replaced within the 6 months previous, I decided to purchase an entirely new system, chassis, PS and all.
Thought so. I've never needed to change my BIOS settings (excepting which Drive to boot from) to run Linux either, even without specifying anything Linux related.I have never needed to change any BIOS settings to run LInux on my PC. When I purchased it, I specified dual-boot with Windows XP SP2 and Fedora Core 3 on separate 80GB disks with the previous disks slaved to each particular instance of their successor OSes (it came with an Award BIOS and Grub boot loader). It just worked out of the box.
That's releveant to Dr H. when he hasn't got M$ Windows? You just seem to be missing the point in this thread and spreading FUD.Dual-boot is not such a mystery if you follow saikee's links in his signature.
Probably nothing! You can buy a Mobo, CPU, RAM etc and boot a Linux install disk, clean without any taint of non-Free OS.lotuseclat79 said:Ok, going back to check it looks like I mistook what Doc had said about 98/me - but, you have to allow for the question what was there before he loaded Ubuntu?
What could he alter, that would screw up his machine? Lets say RAM timings. Then try "Load Defaults". He's shown signs of "adult" thinking, swapping out PS for instance, which I would suspect with bad disk + bad graphics card.I agree, it appears to be a hardware problem, but the question is whether it is a configuration problem in the BIOS or a deeper hardware problem. Do you know if Doc has fiddled with the BIOS before this problem occured?
Rubbish, as explained before kernel doesn't use the BIOS to write to disk. Don't you think if this were a Dell, he'd have shipped it back by now, or called on their support? Most likely he'd have IE available anyway, and could have re-installed the OS, and run their diagnostic utilities.Once all potential BIOS configuration causes can be ruled out, then a hardware malfuinction is more likely.
The problem domain seems to clearly be an issue between the BIOS and the disk configuration limit, but without Doc's input about what was on the computer before he loaded Ubuntu and whether he made any changes to the BIOS in the course of loading Ubuntu, we are not likely to make very much progress.
Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.
If you're not already familiar with forums, watch our Welcome Guide to get started.
Join over 807,865 other people just like you!