By the way, my problems can be resolved with a few things.
1) Explicitly end pre/post/packages sections with %end, and most of
the errors will go away.
2) Using nomodeset as a kernel flag because (in my case, nouveau)
barfs on this hardware, causing the black screen I described.
- Rich
2011/8/2
On Thu, Jul 28, 2011 at 9:32 AM, Troy Dawson daw...@fnal.gov wrote:
On 07/27/2011 05:23 PM, Rich wrote:
Hi all,
I've got questions about two different failure modes I experienced
while trying to kickstart SL6.1 on some hardware to play with.
First, when I kickstarted it on this hardware, it
I am unsurprised to report that SL 6.0 with the identical kickstart
file also stops on In interactive step timezone, can't continue
- Rich
On Tue, Aug 2, 2011 at 12:14 PM, Rich rerc...@pha.jhu.edu wrote:
On Thu, Jul 28, 2011 at 9:32 AM, Troy Dawson daw...@fnal.gov wrote:
On 07/27/2011 05:23
Can you post the top half of your kickstart file, up to the Packages
section.
If you want, you can xxx out anything you think is private.
Troy
On 08/02/2011 11:33 AM, Rich wrote:
I am unsurprised to report that SL 6.0 with the identical kickstart
file also stops on In interactive step
=== x86_64.dss.private ===
network --bootproto=dhcp
nfs --server xxx --dir /export/d0/kickstart/sl60/x86_64/
logging --host=xxx --level=debug
skipx
selinux --disabled
firewall --disabled
install
keyboard us
lang en_US.UTF-8
FWIW, the systems I'm having this problem with are Zotac IONITX-A-U
boards
(http://www.zotacusa.com/zotac-ionitx-a-u-atom-n330-1-6ghz-dual-core-mini-itx-intel-motherboard.html).
Since, as I described, loading the forcedeth driver in SL61 makes
/sbin/loader SIGSEGV, I would not be surprised if it
On 07/27/2011 05:23 PM, Rich wrote:
Hi all,
I've got questions about two different failure modes I experienced
while trying to kickstart SL6.1 on some hardware to play with.
First, when I kickstarted it on this hardware, it immediately
hardlocked (display black, keyboard unresponsive with no
