home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!pitt.edu!dsinc!netnews.upenn.edu!eniac.seas.upenn.edu!dsimon
- From: dsimon@eniac.seas.upenn.edu (Derron Simon)
- Newsgroups: comp.os.linux
- Subject: CMOS erasure problem w/ 486s and Linux
- Message-ID: <101726@netnews.upenn.edu>
- Date: 12 Dec 92 03:26:00 GMT
- Sender: news@netnews.upenn.edu
- Organization: University of Pennsylvania
- Lines: 35
- Nntp-Posting-Host: eniac.seas.upenn.edu
-
-
- Has this problem been fixed? About a month ago after I posted an article
- mentioning my CMOS had been wiped out by SLS after reboots on my 486 I
- was swamped with replies. Unfortunately they were all requests for a fix.
-
- Has anyone found out what is going on with this? I have a 486/33Mhz machine
- with AMI BIOS. I was told this was an AMI problem, but I have a friend here
- at school who says he occasionally has the same problem on his 386 gateway
- with Phoenix BIOS.
-
- It seems that most of the people who've had problem had the Hard Drive data
- in their CMOS wiped out. Does Linux change anything pertaining to the
- hard drive? I heard from another friend here who hasn't been experiencing
- problems that he saw something about the CMOS pertaining to hard drives
- in the fdisk program... I don't know what this is about, but it sounds
- like a clue.
-
-
- Another common symptom is that it's soft reboots which corrupt the CMOS,
- hardware resets seem to keep it in tact.
-
- PLEASE HELP ME!! I really love Linux and already sold my 386 I had it
- running on for several months.
-
- Thanks in advance,
- Derron Simon
-
-
- P.S. Any help is appreciated, even if it's just a pointer into the code
- so I can fix it myself.
- --
- /* Derron Simon (SEAS 1994) * Anytime I see something screech across a */
- /* dsimon@eniac.seas.upenn.edu * room and latch onto someone's neck, and the */
- /* * guy screams and tries to get it off, I have */
- /* University of Pennsylvania * to laugh, because what _is_ that thing!? */
-