Thank you Pat and Bluejay for replying.
Late last week, I found the culprit. It was the "cpuspeed". Not sure
why (although I did find a couple of google references from users who
had also had a problem with "cpuspeed"). I ended up making sure my
kickstart script does not install it (basically added a "-cpuspeed" line
to "%packages"), and it works much better now.
I do like the idea of video-recording the screen, I have never tried
that before (a lot of photographing the screen to capture items, but
never tried video-recording it, will have to try that for the next problem).
thanks,
Paul
On 09/19/2011 02:50 PM, Bluejay Adametz wrote:
SCROLLLOCK should let you use PageUP to look at the text that went
zooming past to see if anything interesting is afoot.
Or, if all else fails, try video-recording the screen. I've actually
had some luck doing that with my smartphone in cases where errors fly
off the screen too fast. I was able to catch just enough to get me
pointed in the right direction.
- Bluejay Adametz
Blore's Razor: Given a choice between two theories,
take the one which is funnier.
NOTICE: This message, including any attachments, is only for the use of
the intended recipient(s) and may contain confidential and privileged
information, or information otherwise protected from disclosure by law.
If the reader of this message is not the intended recipient, you are
hereby notified that any use, disclosure, copying, dissemination or
distribution of this message or any of its attachments is strictly
prohibited. If you received this message in error, please contact the
sender immediately by reply email and destroy this message, including all
attachments, and any copies thereof.
