I decided to give another shot at installing the RP on its own and may have more data. First I tried from KUAL:
Quote:
[2016-12-30 @ 21:44:52 +0000] :: [MRPI r13359] - Beginning the processing of package 'Update_rp_20131220.N_install.bin' (rp 20131220.N I) . . .
--
Running 'run.ffs' for 'rp 20131220.N I' (Update_rp_20131220.N_install.bin) @ Fri, 30 Dec 2016 21:44:53 +0000
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
mount: /dev/mmcblk0p2 already mounted or /mnt/mmc/ busy
mount: according to mtab, /dev/mmcblk0p2 is mounted on /mnt/mmc
Hu oh... Got return code 1 . . . 
|
Then I tried via ";log mrpi" in the global search:
Quote:
[2016-12-30 @ 21:50:25 +0000] :: [MRPI r13359] - Beginning the processing of package 'Update_rp_20131220.N_install.bin' (rp 20131220.N I) . . .
--
Running 'run.ffs' for 'rp 20131220.N I' (Update_rp_20131220.N_install.bin) @ Fri, 30 Dec 2016 21:50:25 +0000
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
mount: /dev/mmcblk0p2 already mounted or /mnt/mmc/ busy
mount: according to mtab, /dev/mmcblk0p2 is mounted on /mnt/mmc
Hu oh... Got return code 1 . . .
|
In both cases I got a notice about a mounting error. This was not present in the log when running multiple installs. Perhaps this gives a clue to the solution?
In case it helps, I have kterm 2.3 installed for diagnostic purposes.
Dave