Accessing BIOS information on a running system

[gaf-mNDKBlG2WHs at public.gmane.org (Jerry Feldman)]

On 03/31/2010 11:01 AM, David Rosenstrauch wrote:
> On 03/31/2010 10:44 AM, Jerry Feldman wrote:
>  =20
>> 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 f=
or
>> 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.
>>    =20
> $ sudo dmidecode -t bios
>
>
>  =20
Thanks, that is exactly what I was looking for. I've used it before, but
I forgot the command.

--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846