Sender: |
|
Date: |
Wed, 19 Sep 2007 15:54:10 +0200 |
MIME-version: |
1.0 |
Reply-To: |
|
Content-type: |
text/plain; format=flowed; charset=ISO-8859-1 |
Subject: |
|
From: |
|
In-Reply-To: |
|
Content-transfer-encoding: |
7BIT |
Comments: |
|
Parts/Attachments: |
|
|
On 19/09/07 15:39, Honest Guvnor wrote:
..
> Any other thoughts or pointers gratefully received.
(not related to SL5, but hope it helps nevertheless)
* check the alternative console screens (assuming you have a physical
console), Alt-F3, Alt-F4. These may have error messages about the
network interface (not) being brought up, and mode information wherefrom
the Kickstart file is supposed to be retrieved.
* Suggest to add the following kernel command line options to your mknbi:
text debug ksdevice=link ks=whereveryourksfilelives
ksdevice=link tells it to use whatever device currently has a link, this
includes waiting for such a link to come up. Some drivers take a while
to (re-)establish network connectivity, even if the machine just booted
successfully over the net.
ks=URL should remove the guesswork based on DHCP bootfile parameters.
I'd actually start with http:// (just plunk the KS file on some web
server in the vicinity)
regards
Jan
|
|
|