BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Accessing BIOS information on a running system
- Subject: Accessing BIOS information on a running system
- From: darose-prQxUZoa2zOsTnJN9+BGXg at public.gmane.org (David Rosenstrauch)
- Date: Wed, 31 Mar 2010 11:01:23 -0400
- In-reply-to: <4BB35FCC.400-mNDKBlG2WHs@public.gmane.org>
- References: <4BB35FCC.400@blu.org>
On 03/31/2010 10:44 AM, Jerry Feldman wrote: > I have 2 Intel whitebox systems and one system is beeping (4 beeps). I'm > not sure what exactly the 4 beeps mean as I don't have a BIOS manual for > the system (Intel Whitebox). I do have access to 2 similar running > systems, but I don't really know what the motherboard or BIOS is. This > particular system has been unwell for a while since it was reporting > only 3 CPUs out of 4. If it is memory, I can probably fix that since I > have a bunch of 1GB sticks. > > In any case, before I accidentally drop the system out the window onto > the Riverside station, I want to try to figure out exactly what the 4 > beep error code means on this system, but I need to know whose BIOS is > in there. $ sudo dmidecode -t bios HTH, DR
- References:
- Accessing BIOS information on a running system
- From: gaf-mNDKBlG2WHs at public.gmane.org (Jerry Feldman)
- Accessing BIOS information on a running system
- Prev by Date: Fwd: [FSF] Why I'm rejecting your email attachment: for freedom and the good of the web!
- Next by Date: Accessing BIOS information on a running system
- Previous by thread: Accessing BIOS information on a running system
- Next by thread: Accessing BIOS information on a running system
- Index(es):