the driverdisk option in the .cfg file
Harner Keith-FKH006
Keith.Harner at freescale.com
Thu Jan 11 20:42:28 UTC 2007
Sure,
I get:
*ASSERT: no network device in choosenetworkinterface
*Unable to bring up network
So even though the host will PXE load a kernel it still cannot get to a
network resource?
My goal is to eliminate the need for a driver disk at boot time as we
run XCat and routinely have users reboot to upgrade their workstations.
Thanks,
Keith Harner
Engineering Compute
Phone: 480-413-8625
Pager: 7393862 at skytel.com
-----Original Message-----
From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ray Van Dolson
Sent: Wednesday, January 10, 2007 5:06 PM
To: Discussion list about Kickstart
Subject: Re: the driverdisk option in the .cfg file
On Wed, Jan 10, 2007 at 05:05:23PM -0700, Harner Keith-FKH006 wrote:
> I recently received some new Sun Ultra 20 m2 workstations.
> Our current supported release RHEL3 update 7 does not contain drivers
> for this new hardware.
>
> I attempted to utilize the driverdisk option in the .cfg file and
> point to an NFS exported directory containing all of the needed
drivers.
>
> driverdisk --source=nfs:host_ip:path_to_drivers
>
> For some reason it cannot seem to find the drivers although the path
> is valid and any host can mount it.
>
> What am I missing?
Keith, are you seeing any error messages in any of the console screens
you could share with us?
Ray
_______________________________________________
Kickstart-list mailing list
Kickstart-list at redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list
More information about the Kickstart-list
mailing list