[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Fri Apr 22 08:52:54 2005 -->
- <!--x-from-r13: puneevtyvfgf ng oryyfbhgu.arg (Qnyiva Vneevtna) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Defective BIOS? -->
- <li><em>date</em>: Fri Apr 22 08:52:54 2005</li>
- <li><em>from</em>: charriglists at bellsouth.net (Calvin Harrigan)</li>
- <li><em>in-reply-to</em>: <<a href="msg00530.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00530.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] Defective BIOS?</li>
> One of my older machines has windows on /dev/hda and redhat on
> /dev/hdd. It suddenly refused to boot the /dev/hda. Will only boot
> redhat from a floppy. When I do "/sbin/lilo -t" it tells me
> "Warning: BIOS drive 0x82 may not be accessible"
> Initially I thought it was the physical drive, so I tried 3 (three)
> different
> drives on /dev/hda, all with the same result, so I am tending to
> believe that the problem is actually were the message says that it is,
> in the BIOS.
> When I try to put the boot record on /dev/hdd I get the same message.
> Replacing the 3 volt battery does no good (old one still had over 3
> volt after nine years!)
> Curious thing is that I can mount /dev/hda from /dev/hdd just fine.
> Does the BIOS prevent me from accessing the boot sector in /dev/hda?
> The mobo is probably a pirated item from china, but the BIOS chip is
> an AWARD, and is probably tailored to fit the mobo, might be hard to
> find a replacement.
> Any pointers? What is BIOS drive 0x82? Is it actually the BIOS? Can it
> be fixed?
> Thanks in advance for any help. Cor van Dijk
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
>
Do bios(e{s}) just up an go bad? Wouldn't it fail checksum on boot up?
I would clear the bios by taking out the battery and let it sit
overnight(unplugged as well). The settings might have gotten fowled
up. Then set everything up from scratch again. Given the age of the
board I'm not sure if it supports it, but there might be boot sector
protection turned on in the bios.
Calvin...
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00558" href="msg00558.html">[ale] Defective BIOS?</a></strong>
<ul><li><em>From:</em> rsj at radio.org (Randal Jarrett)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00530" href="msg00530.html">[ale] Defective BIOS?</a></strong>
<ul><li><em>From:</em> cor.angela at mindspring.com (Cor van Dijk)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00545.html">[ale] SuperMicro Power Down</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00547.html">[ale] professional groups / associations</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00712.html">[ale] Defective BIOS?</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00558.html">[ale] Defective BIOS?</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00546"><strong>Date</strong></a></li>
<li><a href="threads.html#00546"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>