Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a Athlon 1.8 dual boot system (win XP and RH8)
What is happening right now:
when pushing the power button: Nothing comes up to the screen
Computer emits intermittent beeps
Does not even reach boot loader
Each time I have to physically reset cmos to be able to boot ant this is getting annoying
The problem will reappear if i shutdown or reboot the compy
Oh and the problem happens from whatever os I shutdown or reboot
Does any of you has an idea about what it could be,
and if so any suggestions about how could i fix this problem.
The number of beeps often tells you the general area where the problem is occuring. Who made the BIOS and how many beeps are you hearing?
Also most viruses that attempt to damage the BIOS or CMOS can usually be detected by standard Windows Antivirus apps like Norton, McAfee, etc, so when you boot into windows run a scan to see if you can indeed find a virus and then just as importantly find out specifically which virus is present. The last point is important, because there are several ways to attack the BIOS/CMOS.
I already tried a scan but i haven't found anything...
And now, unfortunately i am unable to boot my comp. The beep sequence has changed.
The last thing i remember doing before my box died is loading bios failsage settings...
Since i agree this does not give a lot of information i will post some debug
data tomorrow (i have debug facility built-in motherboard)
I will also try to post the exact sound (it might be though cuz of tonality changes)...
Also, I havent reported this before as i thought it was unrelated... but each time i would
clear the cmos, i would see the following message error at startup:
Error CMOS checksum invalid
Press del to enter setup, F1 to load defaults
If you really think your bios has been corrupted you could try downloading the latest version for your board and update it, that should eliminate any problems that a virus has caused.
But ive seen this problem before on older machines where the bios battery has run out of power. So replace the battery first before you try rewriting the bios.
Ok,
I managed to get the thing work twice....
I have an award modular bios v6.0 on a sst chip
I tried to flash, but the program i dled from the motherboard maker (dtk) tend
to freeze.
Also, i scanned once more and the antivirus sw got shut down... virus related off course.
I shutted down a couple of processes and restarted a scan.
The computer violently crashed with on an unhandled instruction causing a blue screen of death.
I was unable to bring it to life since....
#Boot the system and record the number of beeps that the system issues.
Download the service manual for the motherboard from it's manufacturer's web site. Lookup the beep sequence.
#With the system turned off:
Replace the CMOS battery with a fresh one
Remove and replace the memory modules from the system motherboard.*
Close the jumper responsible for clearing the CMOS, turn the system on to clear the CMOS and then turn it off again, restore the jumper to its normal position.
Re-Test.
*Suggested because if the memory modules are not seated soundly the system may boot intermittently or not all.
If still unsuccessful may I suggest:
#Removing all but the most basic cards and devices and repeat the above test.
#If you are using a removable display adapter then change the card out for a basic display adapter.
The system may be prevented from starting up due to a faulty card in the backplane BUS, poorly seated or defective memory modules, faulty CMOS BIOS code, incorrect user BIOS settings (eg. incorrect CPU specifications), faulty FDD,HDD,CDROM, etc.
In a worst case senario, if you have flashed the BIOS and it has failed the system, consider taking the system to a PC repairer and have them physically remove and replace the BIOS.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.