accessing one's tower system specifications

[kato40]

Hi Russell:
Here is part of the "System " info ,more will be availabla as soon as I can copy from leafpad to this site.
Identification
Vendor: ‎VIA Technologies, Inc.

Description: ‎VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE

Media class: ‎IDE interface

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎0

PCI device #: ‎15

PCI function #: ‎1

PCI revision: ‎0x07

Vendor ID: ‎0x1106

Device ID: ‎0x0571

Sub vendor ID: ‎0x1043

Sub device ID: ‎0x80ed

Misc
Module: ‎pata_via

Identification
Vendor: ‎VIA Technologies, Inc.

Description: ‎VT8237A SATA 2-Port Controller

Media class: ‎IDE interface

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎0

PCI device #: ‎15

PCI function #: ‎0

PCI revision: ‎0x80

Vendor ID: ‎0x1106

Device ID: ‎0x0591

Sub vendor ID: ‎0x1043

Sub device ID: ‎0x80ed

Misc
Module: ‎sata_via

kato40

[kato40]

Hi Russell:
Here is part of the "System " info ,more will be availabla as soon as I can copy from leafpad to this site.
Identification
Vendor: ‎VIA Technologies, Inc.

Description: ‎VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE

Media class: ‎IDE interface

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎0

PCI device #: ‎15

PCI function #: ‎1

PCI revision: ‎0x07

Vendor ID: ‎0x1106

Device ID: ‎0x0571

Sub vendor ID: ‎0x1043

Sub device ID: ‎0x80ed

Misc
Module: ‎pata_via

Identification
Vendor: ‎VIA Technologies, Inc.

Description: ‎VT8237A SATA 2-Port Controller

Media class: ‎IDE interface

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎0

PCI device #: ‎15

PCI function #: ‎0

PCI revision: ‎0x80

Vendor ID: ‎0x1106

Device ID: ‎0x0591

Sub vendor ID: ‎0x1043

Sub device ID: ‎0x80ed

Misc
Module: ‎sata_via

kato40

kato40, I noticed your last post was in November 2010 so I'm wondering if you have been able to update the system since then?  Are you able to boot PCLinuxOS at all? 

Re: drives , there seems to be 2 different types ,IDE and SATA.

[kato40]

Hi Russell:
Here is more,
Name: ‎L1-Cache

Installed size: ‎128 kB

Type: ‎Cache

Name: ‎L2-Cache

Installed size: ‎1024 kB

Type: ‎Cache

Name: ‎L3-Cache

Installed size: ‎0 kB

Type: ‎Cache

Name: ‎L3-Cache

Installed size: ‎0 kB

Type: ‎Cache

Name: ‎L3-Cache

Installed size: ‎0 kB

Type: ‎Cache

Identification
Processor ID: ‎1

Vendor: ‎AuthenticAMD

Model name: ‎AMD Athlon(tm) 64 X2 Dual Core Processor 3600+

Cpuid family: ‎15

Model: ‎107

Model stepping: ‎1

Cpuid level: ‎1

Performances
Frequency (MHz): ‎1900.000

Cache size: ‎512 KB

Bogomips: ‎3799.39

Cores
Cores: ‎2

Core ID: ‎0

Physical ID: ‎0

ACPI ID: ‎0

Siblings: ‎2

Misc
Flags: ‎fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch

Write protection: ‎Yes

Identification
Processor ID: ‎2

Vendor: ‎AuthenticAMD

Model name: ‎AMD Athlon(tm) 64 X2 Dual Core Processor 3600+

Cpuid family: ‎15

Model: ‎107

Model stepping: ‎1

Cpuid level: ‎1

Performances
Frequency (MHz): ‎1900.000

Cache size: ‎512 KB

Bogomips: ‎3799.46

Cores
Cores: ‎2

Core ID: ‎1

Physical ID: ‎0

ACPI ID: ‎1

Siblings: ‎2

Misc
Flags: ‎fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch

Write protection: ‎Yes

Identification
Processor ID: ‎2

Vendor: ‎AuthenticAMD

Model name: ‎AMD Athlon(tm) 64 X2 Dual Core Processor 3600+

Cpuid family: ‎15

Model: ‎107

Model stepping: ‎1

Cpuid level: ‎1

Performances
Frequency (MHz): ‎1900.000

Cache size: ‎512 KB

Bogomips: ‎3799.46

Cores
Cores: ‎2

Core ID: ‎1

Physical ID: ‎0

ACPI ID: ‎1

Siblings: ‎2

Misc
Flags: ‎fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch

Write protection: ‎Yes

kato40

[russell.eberhardt]

Sorry, the above doesn't help.  If the drives don't show up in BIOS they won't show up in PCC.

If they do show up in BIOS then they should also show up in PCC like this:

Except you should have sr0 and sr1.

Russell.

[kato40]

G'day Russell:
Thanks very much for your "update " link. I managed to update my Pclinux LXDE 2010 with 602 updates.
Now ,I can concentrate on my other niggly problems.
kato40

[kato40]

Hi:
Since this last post ,I opened the tower ,and noticed both drives are using the same type of wide ribbon cable, IDE ? This little matter prevent updating to the latest PC Lunux OS 2011 .
Thanking you,
kato40

[Hootiegibbon]

Hi:
Since this last post ,I opened the tower ,and noticed both drives are using the same type of wide ribbon cable, IDE ? This little matter prevent updating to the latest PC Lunux OS 2011 .
Thanking you,
kato40

Using IDE cables will not prevent the use of PCLinuxOS , If you are having issues with the most recent iso's please start a NEW thread, along with factual detail as to what is preventing you from installing and any errors or warnings present on a verbose boot.

Jase

[kato40]

Hi Russell:
I just noticed that there is no cd listed.
Strange
kato40

[kjpetrie]

Almost certainly, the problems you have will relate to the IDE connections and designations of your drives.

Each IDE interface can accept two drives, identified by the terms "master" and "Slave". They don't indicate any particular relationship between the drives - it's just the popular term to distinguish the two. On most chipsets a slave drive can only be used if a master is also present on the same cable. It is very important that the drives are correctly identified. There are two mechanisms for doing this - jumpers and cable select. Every drive will have a jumper on the back which selects master, slave, or (usually) cable select.

The first requirement is that the cables are fitted the right way round, with the motherboard end connected to the motherboard. The second is that the drives are in the correct position for the type of cable used, and the third is that the jumpers on the drives match their position on the cable. See here for full instructions: http://www.mikeshardware.com/howtos/howto_connect_ide_hd.html

I suspect once you have them fitted correctly your drives will be recognised.