Thanks:
0
Dislikes:
0
-
Updating the Boot Flash 8850/510dp
hi
I'm Updating the Boot Flash for 510dp
in hyperterminal show
-------------------------------------------------------------------------------
Accxes Version: 12.7 Build: 114 Type: 8850/510Configuring for xpci
Creating directory: /dev/ifVIII_0/ ... OK
Creating device: /dev/ifVIII_0/iot ... OK
Creating device: /dev/ifVIII_0/aha ... OK
Creating directory: /dev/ifP19X_0/ ... OK
Creating device: /dev/ifP19X_0/iot ... OK
Creating device: /dev/ifP19X_0/aha ... OK
Creating device: /dev/ifP19X_0/duart ... OK
Loading module: xpcimod ... OK
Increasing kernel thread priorities...
Calling chrt on SSH Daemon (PID 3590 PRI 99) ... OK
Calling chrt on init Daemon (PID 1 71) ... OK
Calling chrt on udevd Daemon (PID 501 PRI 71) ... OK
Calling chrt on ksoftirqd/0 Daemon (PID 4 PRI 71) ... OK
Calling chrt on events/0 Daemon (PID 9 PRI 71) ... OK
Calling chrt on knodemgr_d Daemon (PID 1167 PRI 71) ... OK
Calling chrt on khpsbpkt Daemon (PID 395 PRI 71) ... OK
Calling chrt on kswapd0 Daemon (PID 189 PRI 40) ... OK
Calling chrt on kblockd/0 Daemon (PID 55 PRI 40) ... OK
Calling chrt on pdflush Daemon (PID 187 PRI 40) ... OK
Calling chrt on pdflush Daemon (PID 188 PRI 40) ... OK
Calling chrt on kjournald Daemon (PID 450 PRI 40) ... OK
Calling chrt on kjournald Daemon (PID 1894 PRI 40) ... OK
Calling chrt on kjournald Daemon (PID 1895 PRI 40) ... OK
Calling chrt on kjournald Daemon (PID 1896 PRI 40) ... OK
Calling chrt on kjournald Daemon (PID 1898 PRI 40) ... OK
Calling chrt on syslogd Daemon (PID 3448 PRI 40) ... OK
Calling chrt on klogd Daemon (PID 3451 PRI 40) ... OK
Calling chrt on kauditd Daemon (PID 472 PRI 40) ... OK
Calling chrt on ata/0 Daemon (PID 442 PRI 40) ... OK
Calling chrt on aio/0 Daemon (PID 240 PRI 40) ... OK
Calling chrt on khelper Daemon (PID 11 PRI 40) ... OK
Calling chrt on Kernel acpid Daemon (PID 57 PRI 40) ... OK
Calling chrt on acpid Daemon (PID 3577 PRI 40) ... OK
Calling chrt on khub Daemon (PID 160 PRI 40) ... OK
Calling chrt on kseriod Daemon (PID 162 PRI 40) ... OK
Calling chrt on SCSI Error Handler(0) Daemon (PID 448 PRI 40) ... OK
Calling chrt on SCSI Error Handler(1) Daemon (PID 449 PRI 40) ... OK
Calling chrt on kthread Daemon (PID 2 PRI 40) ... OK
Calling chrt on ACPI Notify Daemon (PID 58 PRI 40) ... OK
Calling chrt on cqueue/0 Daemon (PID 155 PRI 40) ... OK
Calling chrt on USB Suspend Daemon (PID 157 PRI 40) ... OK
Calling chrt on ATA Hotplug Daemon (PID 444 PRI 40) ... OK
Calling chrt on XFS Daemon (PID 3635 PRI 4) ... OK
Calling chrt on Device-Mapper Multipath Daemon (PID 1839 PRI 40) ... OK
Calling chrt on D-Bus Daemon (PID 3494 PRI 40) ... OK
Calling chrt on Automount Daemon (PID 3557 PRI 40) ... OK
Calling chrt on xinet Daemon (PID 3601 PRI 27) ... OK
Calling chrt on HAL Daemon (PID 3668 PRI 40) ... OK
Calling chrt on HAL Runner Daemon (PID 3669 PRI 40) ... OK
Calling chrt on HAL ACPI Daemon (PID 3676 PRI 40) ... OK
Calling chrt on HAL Keyboard Daemon (PID 3683 PRI 40) ... OK
Calling chrt on HAL Keyboard Daemon (PID 3686 PRI 40) ... OK
Bump Priority: No HAL Storage Daemon found
Configuring virtual memory parameters...
vm.dirty_background_ratio = 1
vm.dirty_expire_centisecs = 100
vm.dirty_ratio = 100
vm.dirty_writeback_centisecs = 50
vm.swappiness = 100
vm.vfs_cache_pressure = 110
RTNETLINK answers: Invalid argument
Checking for JBOSS threads...
JBOSS not running.
Validating that all needed modules are installed.
raw1394 module found.
ohci1394 module found.
Pausing to allow driver initialization.
testlibraw call SUCCEEDED. Checking for Xerox Wide Format scanner.
Firewire card found: nodes = 1, driver = ohci1394
Waiting 5 seconds for "P."
Scanner vendor ID = 0x002981ec
Scanner text leaf = Linux - ohci1394
Xerox Wide Format scanner NOT found.
Make sure scanner is connected.
Check firewire cable and back of scanner for "P."
Firewire test completed SUCCESSFULLY.
DDS Enabled.
<launchAccxes> No license support for tpr2! Launching without
mke2fs 1.39 (29-May-2006)
Accxes Version: 12.7 Build: 114 Type: 8850/510
Wind/U Error (252): Function wuRunRegistryDaemon - Can not find file windu_regi.
Wind/U Error (256): Failed to spawn a private registry daemon on host System.Acs
Wind/U Error (248): Failed to connect to the registry on server System.Accxes
./rhino.bin: RLIMIT_NOFILE now set to cur 1024 max 1024
MSGQ initialized.
FTP initialized.
(t61130448: tRootTask): Logging started
(t61130448: tRootTask): chdir to /home/accxes/ successful
(t61130448: tRootTask): /dev/ifP19X_0/duart open failed.
(t61130448: tRootTask): Make sure xpci module and interface card is installed p.
Unloading module: xpcimod ... OK
Re-spawning AccXES...
Loading module: xpcimod ... OK
./rhino.bin: RLIMIT_NOFILE now set to cur 1024 max 1024
MSGQ initialized.
FTP initialized.
(t19592912: tRootTask): Logging started
(t19592912: tRootTask): chdir to /home/accxes/ successful
(t19592912: tRootTask): /dev/ifP19X_0/duart open failed.
(t19592912: tRootTask): Make sure xpci module and interface card is installed p.
Unloading module: xpcimod ... OK
Re-spawning AccXES...
Loading module: xpcimod ... OK
./rhino.bin: RLIMIT_NOFILE now set to cur 1024 max 1024
MSGQ initialized.
FTP initialized.
(t18372064: tRootTask): Logging started
(t18372064: tRootTask): chdir to /home/accxes/ successful
(t18372064: tRootTask): /dev/ifP19X_0/duart open failed.
(t18372064: tRootTask): Make sure xpci module and interface card is installed p.
Unloading module: xpcimod ... OK
Re-spawning AccXES...
Loading module: xpcimod ... OK
./rhino.bin: RLIMIT_NOFILE now set to cur 1024 max 1024
MSGQ initialized.
FTP initialized.
(t50988512: tRootTask): Logging started
(t50988512: tRootTask): chdir to /home/accxes/ successful
(t50988512: tRootTask): /dev/ifP19X_0/duart open failed.
(t50988512: tRootTask): Make sure xpci module and interface card is installed p.
Too many re-spawns...stopping
-------------------------------------------------------------------------------------
few minute
------------------------------------
xEROX FreeFlow Accxes Controller
Install CD Version: 4.3 Build: 142
Kernel 2.6.22.9-61.fc6 on an i686
Accxes Version: 12.7 Build: 114 Type: 8850/510
System login:
---------------------------------------------------
help me plz
to Using the Diagnostics procedure, using the serial connection. appears to “Boot>”
Last edited by walidcharifi; 11-02-2014 at 04:07 PM.
-
Technician
- Rep Power
- 17
Re: Updating the Boot Flash 8850/510dp
Good evening! Faced with the same problem! How did you solve this problem?
-
Technician
- Rep Power
- 17
Re: Updating the Boot Flash 8850/510dp
Good evening! Faced with the same problem! How did you solve this problem?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks