Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
forcedeth has been part of the stock default kernel for about 2 years now. there's nothing interesting about it at all really. infact i didn't think nvidia had anything to do with it at all, and i'm guessing they are simply promoting someone else's kernel code as their own nvnet driver always sucked.
if you're looking to include the forcedeth module within the kernel itself then it'd be a pretty stock rebuild of the standard centos 4.4 kernel, but you'd just toggle the forcedeth options from a module to compiled. that will then recreate exactly the same kernel but including forcedeth. another option is to use an initrd to contain the forcedeth module and leave the original kernel in tact. the pxe / tftp boot process will pull an initrd as well as a kernel image is requested to do so i believe.
forcedeth has been part of the stock default kernel for about 2 years now. there's nothing interesting about it at all really. infact i didn't think nvidia had anything to do with it at all, and i'm guessing they are simply promoting someone else's kernel code as their own nvnet driver always sucked.
if you're looking to include the forcedeth module within the kernel itself then it'd be a pretty stock rebuild of the standard centos 4.4 kernel, but you'd just toggle the forcedeth options from a module to compiled. that will then recreate exactly the same kernel but including forcedeth. another option is to use an initrd to contain the forcedeth module and leave the original kernel in tact. the pxe / tftp boot process will pull an initrd as well as a kernel image is requested to do so i believe.
Hi Chris,
thank you for your reaction!
But if the forcedeth module is in the standard "installation kernel" that is used by anaconda etc. to install CentOS 4.4 on the system why is my network card not supported during the installation, Realtek 8201CL ... ?
So I assume that what you are telling me is true, my append rule must work then:
well no i don't believe that's at all possible. when a nic driver is in the kernel itself then it's automatically loaded, so no modprobe etc... is needed. if you're booting over px then the modules filesystem is not available, and so you can't reach the driver to load it anyway, and if you could reach the driver then you could also reach /etc presumably so would just load the nic driver as part of the standard boot process with modprobe.conf.
whenever i've done PXE, well, THE time i did PXE, i rebuilt the kernel for simplicity in the long run and it worked really well.
well no i don't believe that's at all possible. when a nic driver is in the kernel itself then it's automatically loaded, so no modprobe etc... is needed. if you're booting over px then the modules filesystem is not available, and so you can't reach the driver to load it anyway, and if you could reach the driver then you could also reach /etc presumably so would just load the nic driver as part of the standard boot process with modprobe.conf.
whenever i've done PXE, well, THE time i did PXE, i rebuilt the kernel for simplicity in the long run and it worked really well.
Did you compile the kernel afther the ionstallation or did you compile the kernel before the installation and used it in the installation?
If it is the last one please tell me how or tell me if you have the kernel images somewere available.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.