chain_16
Transcript of chain_16
16AStatus Indicator RAPs
16A Network Controller RAP Y NInstall a new power supply PWB, PL 16.10 Item 8.
4.
from the power supply PWB, The power sup-
6.10 Item 8.
rror” may be displayed on the UI. Reseat the cards, that the cards are undamaged and in their correct ure 3. The error message has cleared.
ssor PWB to Network Controller Faults RAP.
machine, GP 14. The network controller boots
, refer to GP 5.
rive connectors.
k controller. Switch off the machine, then switch on he machine and view the results of the NC POST. a list of tests. Refer to Network Controller Boot
he fault.
network controller disk drive and if faulty, install a
PL 16.10 Item 15.
ller. Perform a power off, power on to reboot the ST. The NC POST results (Network Controller S.
network controller boots up correctly.
PL 16.10 Item 15.
sults (Network Controller Boot sequence) for a fail-
to Network Controller Faults RAP.
A
July 20052-519WorkCentre Pro 275 Family (CC232-WCP275F)
This RAP is to assist with diagnosing faults on the network controller.
Refer to GP 5 Portable Work Station and Tools for information regarding the AltBoot tool that is used to diagnose and repair faults with the network controller.
Initial ActionsMake sure that the machine has no fault or status code other than 16-XXX active and, with the exception of the network controller fault, is working correctly.
ProcedureWARNING
Do not remove the battery from the network controller PWB. Danger of explosion if the battery is installed incorrectly.
WARNINGSwitch off the electricity to the machine, GP 14. Disconnect the power cord from the customer supply while performing tasks that do not need electricity. Electricity can cause death or injury. Moving parts can cause injury.
NOTE: Communication errors between the image processing PWB module and the network controller are covered in the 03-340, 03-416 Image Processing PWB to Network Controller Faults RAP.
Make sure that the external connectors are securely seated and the cables are undamaged.The connections are good.Y N
Reseat the connections. If the power supply cable is damaged, install a new power supply PWB, PL 16.10 Item 8.
Switch off the machine, GP 14 and disconnect the power cord from the wall outlet. Reconnect the power cord and switch on the machine. The network controller does not boot up cor-rectly.Y N
Perform SCP 6 Final Actions.
Figure 1. Check that mains (line) power is available at PJ23 on the power and control module. Mains (line) power is available.Y N
Perform 01C AC Power RAP.
Figure 1. Check that either of the RJ-45 LAN connection LED’s is on.
NOTE: If either of the RJ-45 LEDs are on, supply voltage is available. If the LEDs are off, sup-ply voltage may still be available. Refer to Table 1 for a description of the RJ-45 LEDs.
The CPU cooling fan is running.Y N
Go to Flag 1. Check for +12V between P/J25 pins 1 and 2. +12V present at PJ25 on the network controller PWB.
Install a new CPU fan, PL 16.10 Item
Go to Flag 2 and Flag 3. Check the outputsplies are correct.Y N
Install a new power supply PWB, PL 1
The message ”IP - NC Communication Econnectors and memory module. Ensure positions, refer to Table 2, Figure 2 and FigY N
Perform 03-340, 03-416 Image Proce
Switch off the machine, then switch on the up correctly.Y N
Perform the following:
• Perform a software set download
• Reseat network controller disk d
• Connect the PWS to the networthe machine, GP 14, to reboot tRefer to Table-2 in GP 5, for sequence to identify and repair t
• Using AltBoot (GP 5) check thenew disk drive PL 16.10 Item 5.
• Install a new network controller,
Connect the PWS to the network contromachine and view the results of the NC POBoot sequence) are displayed on the PWY N
Perform a software set download. TheY N
Install a new network controller,
Perform SCP 6 Final Actions.
Use the PWS and check the NC POST reure. A fault is shown.Y N
Perform SCP 6 Final Actions.
Perform 03-340, 03-416 Image Processor
A
WorkCentre Pro 275 Family (CC232-WCP275F)
component location
Memory slot 1
Memory slot 0
Memory slot 2
CPU cooling fan
Hard disk drive
port (RJ-45
Power supply
Firewire ports
July 20052-52016A
Status Indicator RAPs
Figure 1 PJ23 and LAN connection location
Figure 2 NC
Table 1 RJ-45 LAN connector LEDs
LED Colour LED State Indicates
Green Off 10 Mbit / s speed is selected
Green On 100 Mbit / s speed is selected
Yellow Off LAN link is not established
Yellow On (steady state) LAN link is established
Yellow On (brighter and pulsing) The network controller is communicating with another device on the Local Area Network
Table 2 Device allocations
Device Slot Parts List Reference
Not allocated PCI slot 4 -
USB card - optional PCI slot 3 PL 16.10 Item 16
Not allocated PCI slot 2 -
Not allocated PCI slot 1 -
Memory module 256MB Memory slot 0 PL 16.10 Item 9
Memory module- optional Memory slot 1 PL 16.10 Item 9
Memory module- optional Memory slot 2 PL 16.10 Item 9
PJ23 RJ-45 LAN connection LEDs
PCI slot 4
PCI slot 3
PCI slot 2
PCI slot 1
Serial port
USB ports
Ethernet LEDs)
16AStatus Indicator RAPs
July 20052-521WorkCentre Pro 275 Family (CC232-WCP275F)
Figure 3 Circuit diagram
WorkCentre Pro 275 Family (CC232-WCP275F)
network controller HDD.
rrupt statement, suspect no software image on the the network controller HDD, a bad connection from le or a defective network controller HDD, PL 16.10
d up, the machine reboots / resets and the network d reconnect the HDD data ribbon cable PJ5 on the
network control PWB, PL 16.10 Item 1.
_______________________________________
emory)
_______________________________________
the network controller software from the HDD, and Linux custom.
...”, suspect corrupted software on the network con-onnection to the network controller HDD or a defec- Item 5.
_______________________________________
opt
_______________________________________
e boot up and a File System check is being per-
cur during every network controller boot up.
rror messages appear in this section (bad block on controller HDD, PL 16.10 Item 5.
_______________________________________
EST 2004
July 20052-52216A
Status Indicator RAPs
Network Controller Boot sequenceConnect the PWS to the network controller, using the Ethernet cable, GP 4 Network Controller AltBoot S/w Download. Switch the machine off and on, GP 14. Select the AltBoot window on the PWS and monitor the Network controller boot sequence.
NOTE: References to the ESS and the network controller, are to the same item.
Xerox User Flash Firmware
================================
ALTERNATE BOOT Ver 4.0
================================
_________________________________________________________________________
• System ID => e.g. Xerox Denali v1.00
• BIOS ID => e.g. American Megatreats Inc. 0701 03/04/2004
• Board ID => Celestica Denali P 2 CMY123432000378
• uP ID => AMD mobile and Duron (tm) 00800 MHz
• Main Revision +> e.g. 4.1.0
Explanation
• The System BIOS hands off boot up control.
NOTE: The network controller PWB BIOS displays the menu shown.
Critical Checks
• If this menu is not displayed and no beeps are heard, suspect a defective network control-ler PWB or CPU not seated correctly.
• If this menu is not displayed and two beeps are heard, approximately 30 sec. after power on, check the following, GP 7:
– a defective connection between the network controller PWB, PL 16.10 Item 1 and the network controller disk drive, PL 16.10 Item 5.
– a defective network controller disk drive, PL 16.10 Item 5.
• If this menu is not displayed and three beeps are heard repeatedly, suspect a loose, defective or missing network controller memory. Check the memory module connections.
_________________________________________________________________________
Press Any Key For AltBoot Menu (05):..... (04)...... (03):......:(02):...... (01):...... (00):
_________________________________________________________________________
Explanation
• The BIOS displays this interrupt message. Pressing any key within 9 seconds will display the Altboot Options menu.
NOTE: The Altboot Options menu is used when loading network controller software using the Alternate Boot method.
• A single audible beep will be heard when the interrupt time expires.
• The BIOS then probes the bus for the
Critical Checks
• If the boot sequence stops at the intenetwork controller HDD, no power to the network controller HDD to the cabItem 5.
• If the start button appears to be lockecontroller will not boot up. Remove annetwork controller PWB. Install a new
__________________________________
GRUB Loading stage 1.5.
GRUB loading, please wait.....
Press any key to continue.
GRUB version 0.92 (639K / 12928 upper m
__________________________________
Explanation
• The BIOS (Pre boot) attempts to loadhand off the boot up procedure to the
• Critical Checks
• If the boot sequence stops at “loadingtroller HDD, a loss of power, or bad ctive network controller HDD, PL 16.10
__________________________________
Booting Linux CUSTOM
Booting CUSTOM
Linux version 2.4.20-20.9.1 xerox -denali -
__________________________________
Explanation
• The Linux custom has taken over thformed.
NOTE: The File System check will oc
Critical Check
• If the boot sequence stops or if any epartition), suspect a defective network
__________________________________
Setting system clock:Tue NOV 2 07:06:11
16AStatus Indicator RAPs
.Performing fsck on disk ESS removing semaphore files in / tmp / semfiles... done
.
semaphores... done
emfiles... done
rame Buffer
r - Physical address: 0x11a2000
r - Bus address: 0x11a2000
r - Virtual address: 0x40091000
r - Size: 0xea6000
---
ive / save _110204_07:06...
equired processes.
“OPERATION”
n i686
July 20052-523WorkCentre Pro 275 Family (CC232-WCP275F)
/ dev / hda2 clean, 448 / 52224 files, 10535/52211 blocks
/ dev hda1: recovering journal
internal journal ##EXT3
.Start system logger....
Starting kernel logger...
Xerox FrameBuffer Driver....
Successfully installed fbdev Module...
Xerox OHC1 - 1394 NetDevice Driver version: 1.06 (Linux - 2.4.20)
Creating raw devices for / dev / hda
RAMDISK driver initialized: 16 RAM disks of 4896K size 1024 blocksize
* Creating RAM disk / dev / ram0, mounting on / tmp / root
* blocks = 1000, permissions = 777.
This file system will be automatically checked every 22 mounts or 180 days, whichever comes first.
* Creating RAM disk / dev / ram 1, mounting on / tmp semFiles.
* blocks = 1000, permissions = 777.
Writing inode tables: 0 / 1 done
Writing superblocks and filesystem accounting information: done
This file system will be automatically checked every 22 mounts or 180 days, whichever comes first
Starting verification of NURAM: / smart / nvram / nvram _file...
.Successfully verification and set NURAM: smart / nvram / nvram _file
Running / usr / sbin / rpcbind
--------ELT Protocol Module Version: 0.205 build date: Aug 16 20004 10:25:05
---------ESS cleanup of IPC queues--------done
ESS removing leftover shared memory and semaphores... done
Starting / usr / smart / bin / Iftpd...
Running / usr / smart / bin / Iftpd
Starting / usr / smart / bin / trmWinServer...
.Running / usr / smart / bin / trmWinServer
Starting postgresql service: succeeded
Initializing Database...
Succeeded
Start_lakes is beginning
ESS cleanup of IPC queues... done
ESS removing leftover shared memory and
ESS removing semaphores files in / tmp / s
----------Creating Frame Buffer
Executing / usr / smart / bin / lakesCreate F
/ usr / smart / bin / lakesCreateFrameBuffe
/ usr / smart / bin / lakesCreateFrameBuffe
/ usr / smart / bin / lakesCreateFrameBuffe
/ usr / smart / bin / lakesCreateFrameBuffe
---------FrameBuffer Creation Successful --
Collecting ESS files into / tmp / Logs / arch
Cleaning / tmp directory... done
Starting up System Control process
----------The ESS is initialized and starting r
----------Please wait for system to become
Linlks System
Kernal 2.4.20 - 20.9. xerox _denali.opt on a
WorkCentre Pro 275 Family (CC232-WCP275F)
July 20052-52416AStatus Indicator RAPs
Version: #1 Mon Aug 16 10:22:03 EDT 2004
Xerox Corp.
XRX _ 0000aa71017a login: Removing Lakes IPC queues (except SC)
Removing general use / tmp / tmpfiles directory... done
Creating general use / tmp / tmpfiles directory... done
****************************************************************
***************** ESS System is 'OPERATIONAL ******************
****************************************************************
___________________________________
Explanation
• network controller software is loaded and the network controller will now attempt to syn-chronize with the image processing PWB.
___________________________________________________
****************************************************************
******** ESS System 'SYNCHRONIZED' with SYSTEM MANAGER ********
****************************************************************
****************************************************************
************* DIGITAL COPIER PLATFORM 'AVAILABLE *************
****************************************************************
****************************************************************
******************* UI PLATFORM 'AVAILABLE *******************
****************************************************************
_______________________________________
Explanation
• If the four messages are not received check the FireWire cable and the FireWire PWB installed in the image processing PWB module.
_______________________________________