e100 vs eepro100

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> The problem is in trying to get kickstart to load
> RH's e100 driver on initial boot. If I add the device e100
> line to my ks.cfg
> file, it will load the driver, but it will also load the
> eepro100 driver
> and use it! This does me no good whatsoever! How can I override this
> functionality?? Is it possible to do this on the append line
> on syslinux?

ks=floppy noprobe
(this forces the loader to not probe)

Then, in your kickstart file, put in device lines for everything you
need, in the order you want them probed/found.

Or, as suggested, change eepro100 to e100 in bootnet.img's pcitable.

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer
Dell Linux Solutions
www.dell.com/linux
#2 Linux Server provider with 17% in the US and 14% Worldwide (IDC)!
#3 Unix provider with 18% in the US (Dataquest)!





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux