Hello, I apologize for the string of emails. Is there a way in the loader source to force it to scan for the network devices. Here is a part of the anaconda log from the original fc3 rescue cd and the rescue cd with my compiled loader. /* Original rescue cd */ ~ ~ * load module set done * waiting for usb to become stable... * 2 seconds. * modules to insert hid keybdev * module(s) hid keybdev not found * load module set done * no firewire controller found * no pcic controller found * probing buses * finished bus probing * modules to insert tg3 aacraid * loaded tg3 from /modules/modules.cgz * loaded aacraid from /modules/modules.cgz * inserted /tmp/tg3.ko * inserted /tmp/aacraid.ko * load module set done * trying to mount CD device hda * 2075984 kB are available * mntloop loop0 on /mnt/runtime as /tmp/ramfs/stage2.img fd is 12 ~ ~ /* Rescue cd created with a a compiled loader from the anaconda sources */ /* I am using kickstart */ ~ ~ * load module set done * waiting for usb to become stable... * 2 seconds. * modules to insert hid keybdev * module(s) hid keybdev not found * load module set done * no firewire controller found * no pcic controller found * probing buses * finished bus probing * modules to insert aacraid * loaded aacraid from /modules/modules.cgz * inserted /tmp/aacraid.ko * load module set done * getting kickstart file * getting kickstart file from first CDROM * getFileFromBlockDevice(hda, /tmp/ks.cfg) * Searching for file on path /tmp/mnt//tmp/ks.cfg * file copied to /tmp/ks.cfg * setting up kickstart * location = /mnt/source * trying to mount CD device hda ~ ~ As you see the only difference is the network. I have compiled the loader sources on an FC2 machine. Would that be a probable cause for not detecting the network devices, may be a newer libkudzu is necessary? Any help is greatly appreciated. Thanks, Sameer ----- Original Message ----- From: "Sameer Kamat" <sameer@xxxxxxxxxxxxx> To: <anaconda-devel-list@xxxxxxxxxx> Sent: Thursday, November 11, 2004 4:02 PM Subject: Follow up: loader modprobe network However if I do an insmod tg3.ko it then creates the eth* devices and configures the network fine. I am confused why it cannot detect the network and configure it in the first place. Thanks, Sameer. ----- Original Message ----- From: "Sameer Kamat" <sameer@xxxxxxxxxxxxx> To: <anaconda-devel-list@xxxxxxxxxx> Sent: Thursday, November 11, 2004 3:38 PM Subject: loader modprobe network Hi, I recompiled the loader using anaconda version 10.1.0.2. When I put this new loader on the fc3 rescue cd, it fails to configure the network. If I type modprobe tg3 at the prompt it gives an error modprobe: could not parse modules.dep Would anyone please let me know what has changed in the loader of Fedora Core 3 and what I should do to get the networking to work? Are the anaconda 10.1 sources not up to date or am I missing something? lspci does show the Broadcom cards. /proc/net/dev shows only lo. Using the standard FC3 rescue cd seems to configure find the network cards just fine. Please advise. Thanks, Sameer. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list