SCO OPENSERVER5.0.7 Problem


 
Thread Tools Search this Thread
Operating Systems SCO SCO OPENSERVER5.0.7 Problem
# 1  
Old 02-28-2006
SCO OPENSERVER5.0.7 Problem

Hello all,
I m running SCO Openserver5.0.7 with HP DL760 G2 Machine with 4 Processor and 4GB Memory.We replaced the SERVER Board because it causing some problem.After replacing the system Board we are facing the problem in SCO OPENSERVER5.At the hardware level it showing 4Processor But in OS level it detecting only ONE processor.We also entered the License for 4 processor of SCO.Installed the latest EFS and Manintance pack.Please any one help...How can I resolve this issue.Anyone have Solution for this.
Thanx
Athar
+923332457207
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. SCO

SCO OpenServer 5.0.5 Problem

I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system. Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System... (2 Replies)
Discussion started by: jesmith
2 Replies

2. SCO

Mouse problem in sco 5.0.6

hello i have a problem with mouse in vmware with sco 5.0.6 in graphic mode X11 my mouse move to corner after a while do you have any idea about this problem vmware 6.5.2 vmware 7 (5 Replies)
Discussion started by: kaydream
5 Replies

3. UNIX for Dummies Questions & Answers

vi problem, sco -> redhat

I rlogin from a sco box to a redhat box and run /bin/vi. Pgup, Pgdn, and arrow up/down keys don't work. I enter "export TERM=ansi80x25" and run vi again.Everything works just like I like it. Except the cursor turns into a blinking overscore. When I exit vi and close the connection to redhat,... (2 Replies)
Discussion started by: bussyw
2 Replies

4. SCO

Small Problem with SCO

Help Please , how to shutdown SCO v. 5.0.5 from client pc ( windows xp or 2000 ) ? i have full access from client and i need to shutdown SCO from windows (2 Replies)
Discussion started by: rabih_saleh
2 Replies

5. SCO

Sco 6 copying problem

We are using GTAR for daily copies of our database using Travan cartridges (Tapestor drive)and are having intermittent problems. Some days it does not copy and we can't figure out why. Sometimes it seems to be hanging and a tape status command doesn't return anything. Other times it doesn't copy... (0 Replies)
Discussion started by: Yrr88
0 Replies

6. SCO

sco openserver 5.07 installation problem

Hi everyone, We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies

7. SCO

Problem while installing Unixware 7 SCO

Hi All, I just tried to intall Unix ware SCO version 7 on my computer but when system first boots from the CD The terminal Emulator does not shows texts in correct form; it shows all the text in Obnoxious form which is unable to read. I have ATI Radeon 9000 Graphics card installed on my... (0 Replies)
Discussion started by: monster12
0 Replies

8. UNIX for Dummies Questions & Answers

SCO 5.0.6 installation problem

I tryed to install SCO 5.0.6 OpenServer on P4 2.0 GHz 384 MB ram 40 GB HDD. It booted from the floppy disk, and when it comes to hd_config I got this error: unexpected trap in kernel mode: PANIC: K_trap - kernel mode trap 0x0000000E ** Safe to power off ** Please, what should I do? (1 Reply)
Discussion started by: Guest07
1 Replies

9. Filesystems, Disks and Memory

SCO openserver 5 install problem

Hello all, I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies

10. UNIX for Advanced & Expert Users

SCO 5.05 partition problem

Hardware: IBM 300PL 32MB RAM 60Gig HDD During the phase in SCO installation where I get to partition my hard disk, SCO only seems to see 8Gig out of the 60 that I have. Does anyone out there know of a utility or what I need to do to make the the whole 60Gig available. Thanks (3 Replies)
Discussion started by: budrito
3 Replies
Login or Register to Ask a Question
DMIDECODE(8)						      System Manager's Manual						      DMIDECODE(8)

NAME
dmidecode - DMI table decoder SYNOPSIS
dmidecode [OPTIONS] DESCRIPTION
dmidecode is a tool for dumping a computer's DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description of the system's hardware components, as well as other useful pieces of information such as serial numbers and BIOS revision. Thanks to this table, you can retrieve this information without having to probe for the actual hardware. While this is a good point in terms of report speed and safeness, this also makes the presented information possibly unreliable. The DMI table doesn't only describe what the system is currently made of, it also can report the possible evolutions (such as the fastest supported CPU or the maximal amount of memory supported). SMBIOS stands for System Management BIOS, while DMI stands for Desktop Management Interface. Both standards are tightly related and devel- oped by the DMTF (Desktop Management Task Force). As you run it, dmidecode will try to locate the DMI table. If it succeeds, it will then parse this table and display a list of records like this one: Handle 0x0002, DMI type 2, 8 bytes. Base Board Information Manufacturer: Intel Product Name: C440GX+ Version: 727281-001 Serial Number: INCY92700942 Each record has: o A handle. This is a unique identifier, which allows records to reference each other. For example, processor records usually reference cache memory records using their handles. o A type. The SMBIOS specification defines different types of elements a computer can be made of. In this example, the type is 2, which means that the record contains "Base Board Information". o A size. Each record has a 4-byte header (2 for the handle, 1 for the type, 1 for the size), the rest is used by the record data. This value doesn't take text strings into account (these are placed at the end of the record), so the actual length of the record may be (and is often) greater than the displayed value. o Decoded values. The information presented of course depends on the type of record. Here, we learn about the board's manufacturer, model, version and serial number. OPTIONS
-d, --dev-mem FILE Read memory from device FILE (default: /dev/mem) -q, --quiet Be less verbose. Unknown, inactive and OEM-specific entries are not displayed. Meta-data and handle references are hidden. Mutually exclusive with --dump. -s, --string KEYWORD Only display the value of the DMI string identified by KEYWORD. KEYWORD must be a keyword from the following list: bios-vendor, bios-version, bios-release-date, system-manufacturer, system-product-name, system-version, system-serial-number, system-uuid, base- board-manufacturer, baseboard-product-name, baseboard-version, baseboard-serial-number, baseboard-asset-tag, chassis-manufacturer, chassis-type, chassis-version, chassis-serial-number, chassis-asset-tag, processor-family, processor-manufacturer, processor-ver- sion, processor-frequency. Each keyword corresponds to a given DMI type and a given offset within this entry type. Not all strings may be meaningful or even defined on all systems. Some keywords may return more than one result on some systems (e.g. processor- version on a multi-processor system). If KEYWORD is not provided or not valid, a list of all valid keywords is printed and dmide- code exits with an error. This option cannot be used more than once, and implies --quiet. Mutually exclusive with --type and --dump. -t, --type TYPE Only display the entries of type TYPE. TYPE can be either a DMI type number, or a comma-separated list of type numbers, or a keyword from the following list: bios, system, baseboard, chassis, processor, memory, cache, connector, slot. Refer to the DMI TYPES section below for details. If this option is used more than once, the set of displayed entries will be the union of all the given types. If TYPE is not provided or not valid, a list of all valid keywords is printed and dmidecode exits with an error. Mutually exclusive with --string. -u, --dump Do not decode the entries, dump their contents as hexadecimal instead. Note that this is still a text output, no binary data will be thrown upon you. The strings attached to each entry are displayed as both hexadecimal and ASCII. This option is mainly useful for debugging. Mutually exclusive with --quiet and --string. -h, --help Display usage information and exit -V, --version Display the version and exit DMI TYPES
The SMBIOS specification defines the following DMI types: Type Information ---------------------------------------- 0 BIOS 1 System 2 Base Board 3 Chassis 4 Processor 5 Memory Controller 6 Memory Module 7 Cache 8 Port Connector 9 System Slots 10 On Board Devices 11 OEM Strings 12 System Configuration Options 13 BIOS Language 14 Group Associations 15 System Event Log 16 Physical Memory Array 17 Memory Device 18 32-bit Memory Error 19 Memory Array Mapped Address 20 Memory Device Mapped Address 21 Built-in Pointing Device 22 Portable Battery 23 System Reset 24 Hardware Security 25 System Power Controls 26 Voltage Probe 27 Cooling Device 28 Temperature Probe 29 Electrical Current Probe 30 Out-of-band Remote Access 31 Boot Integrity Services 32 System Boot 33 64-bit Memory Error 34 Management Device 35 Management Device Component 36 Management Device Threshold Data 37 Memory Channel 38 IPMI Device 39 Power Supply Additionally, type 126 is used for disabled entries and type 127 is an end-of-table marker. Types 128 to 255 are for OEM-specific data. dmidecode will display these entries by default, but it can only decode them when the vendors have contributed documentation or code for them. Keywords can be used instead of type numbers with --type. Each keyword is equivalent to a list of type numbers: Keyword Types ------------------------------ bios 0, 13 system 1, 12, 15, 23, 32 baseboard 2, 10 chassis 3 processor 4 memory 5, 6, 16, 17 cache 7 connector 8 slot 9 Keywords are matched case-insensitively. The following command lines are equivalent: o dmidecode --type 0 --type 13 o dmidecode --type 0,13 o dmidecode --type bios o dmidecode --type BIOS FILES
/dev/mem BUGS
More often than not, information contained in the DMI tables is inaccurate, incomplete or simply wrong. AUTHORS
Alan Cox, Jean Delvare SEE ALSO
biosdecode(8), mem(4), ownership(8), vpddecode(8) dmidecode February 2007 DMIDECODE(8)