The title says most all, the system would start to act as though it was powering up. The LED would come on for a second and the fans would start. The fans stayed on, but the LED went right back off and the system didn’t seem to POST, or show anything on the onboard video. This is a Gateway gt4022 with a 64 bit AMD processor and I think was Media Center edition of Windows XP. Anyway, I pulled the memory and CPU hoping to hear some sort of BIOS beep code, but no such luck. I pulled everything at one point with the exception of the power to the main board. It still gave the same symptoms. I tried another power supply just in case, same…. So, as I started to read online it seems that the motherboard in these Gateway gt4022’s may be a problem….
Tag: bios
-
Boot up freeze/sluggishness with ubuntu 6.06.1 install cd (on 64bit AMD hardware)
I thought I had written about this once before, but when I searched the site to find the solution I had come across before, I couldn’t find my post…. so, sorry if this is a duplication, but I’ve run into this on some AMD 64-bit based system boards. The most recent was based on the nvidia nforce4 chipset. Essentially in booting from either the alternative install cd or livecd for Ubuntu/kubuntu/edubuntu/xubuntu…. there is a freeze in the boot process. It goes for 30 seconds or more looking as though it’s hard frozen, but it does eventually manage to load the installer.
-
Booting from CD when a systems BIOS won’t let you
Along the way on my permissions nightmare last night, I made matters worse by changing permissions on a fairly important file. In order to fix that I was going to need to reboot from a boot disk. The only problem was boot floppys typically don’t come with reiserfs support (only the boot cds I’ve found have that.) AND my server has for some time refused to boot from the CD. Now, the BIOS will let you choose CD as the first boot device but it promptly decides that there is a “BIOS checksum mismatch” and reloads the defaults which leaves you booting from floppy, then hard drive…. Now, I’ve changed the CMOS battery twice within a 2 month span and I think the longest things lasted were about a week before it reverted to that “BIOS checksum mismatch” (For those of you smart enough to suggest I replace the CMOS battery.) Now, it could be that the battery I replaced with had expiired it’s shelf life already I suppose. But….
-
Flashing bios pain in the neck….
One of the “project machines” I’ve had that’s been retired from other service was to become a “storage server” this week. The twin 250GB drives had arrived and I was ready to setup a RAID1 array (mirroring essentially…) in software and use Ubuntu 6.06 as the base operating system. I had already wiped the other drive and removed the drive, plugged in the new ones (master on the primary and secondary channels) and…. BIOS only reads 136GB. Shoot…. it was a relatively recent system (maybe 3 years…) SO…. BIOS update was my best bet I thought.
-
Recovering lost files
There’s an article at linux.com that gives a good overview of using testdisk and PhotoRec. Testdisk should be able to recover at the partition level and PhotoRec should be able to just pull the files out of a damaged partition. Truth is Hard drives fail in a number of different ways and some of those can give the same error messages. Not too long ago my brother had a laptop hard drive failure, it gave a “no partition found” kind of error message. We talked about a utility such as ghost4linux (g4l) which includes dd_rescue which does a remarkable job with failing disks.
-
BIOS based rootkits coming soon….
There have been a couple stories out of the “Blackhat federal” conference in the last couple days. Brian Krebs at the Security Fix gives a good overview. One of the more troubling notes is the possibility of creating a rootkit that can hide itself in a systems BIOS. Security Focus has some detail on this as well.
-
BIOS Beep Codes
One of the nice things about working on computers is that when it comes to the raw hardware of a system, the engineers have designed a way to communicate what’s wrong (even if it’s just a general idea) even when the hardware has a pretty serious problem. When a computer boots it goes through a POST *(Power On Self Test). This POST process basically is the BIOS (Software embedded in the hardware of the system that exists whether or not an Operating System like Windows is installed) “waking up and testing the hardware.”