RE: Manually bring up NICs not found at install and/or rebuilding Kernel
High, On Fri, 31 Aug 2001, John Purser wrote: Some success! Great! The command I used was modprobe eepro100 and both NIC's came up. I'm running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up exactly the same way because of formatting differences. So where should I put the modprobe info to load it at boot and where should I configure the ethernet cards? I suggest you do it the right way (though the utilities). Run 'modconf' before you have insmodded the modeles. Select in modconf the desired module and it will be loaded at boot. Then edit /etc/network/interfaces to configure the cards: iface eth0 inet static address 192.168.1.254 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 iface eth1 inet static address 10.0.0.150 netmask 255.255.255.0 network 10.0.0.0 Greetz, Sebastiaan Thanks, John Purser -Original Message- From: John Purser [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2001 06:03 To: 'Sebastiaan' Cc: 'debian users' Subject: RE: Manually bring up NICs not found at install and/or rebuilding Kernel Okay, so I want to load a module. I've got about 15 windows open trying to find what module I need and all I'm finding is information on drivers. What module do I need to support Intel Pro/100B PCI cards? Thanks, John Purser -Original Message- From: Sebastiaan [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2001 05:59 To: John Purser Cc: 'debian users' Subject: Re: Manually bring up NICs not found at install and/or rebuilding Kernel High, Hello, I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither one recognizes the PCI NICs. Red Hat and W2K get them first try but I don't want either one on this box. During the last attempted install of Woody I tried using the Configure Network alternative but was told that there were no NIC's found which means I have to load different modules in the kernel before I can configure. So either I dynamically load the modules or I have to rebuild my kernel or someone gives me another option. QUESTIONS: Is there any way to bring up my NIC's without rebuilding my Kernel? Which NIC's are you trying to load? You might want to do it manually. After the installation process has installed device drivers on the computer, swap to the second console and activate it. There you go to /target/lib/modules/2.4.9 (or something), look for your module and insmod it manually. When that works, go back to the first console and continue to configure your network. After installation you may want to run 'modconf' or edit /etc/modules to make the module auto load. Would there be any advantage to installing potato and upgrading to Woody? Potato doesn't recognize my NIC's either but at least tasksel works. AFAIK, this has nothing to do with tasksel. You do not have to install additional packages if you want to make a NIC work. Greetz, Sebastiaan Thanks for the help. John Purser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Manually bring up NICs not found at install and/or rebuilding Kernel
High, Hello, I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither one recognizes the PCI NICs. Red Hat and W2K get them first try but I don't want either one on this box. During the last attempted install of Woody I tried using the Configure Network alternative but was told that there were no NIC's found which means I have to load different modules in the kernel before I can configure. So either I dynamically load the modules or I have to rebuild my kernel or someone gives me another option. QUESTIONS: Is there any way to bring up my NIC's without rebuilding my Kernel? Which NIC's are you trying to load? You might want to do it manually. After the installation process has installed device drivers on the computer, swap to the second console and activate it. There you go to /target/lib/modules/2.4.9 (or something), look for your module and insmod it manually. When that works, go back to the first console and continue to configure your network. After installation you may want to run 'modconf' or edit /etc/modules to make the module auto load. Would there be any advantage to installing potato and upgrading to Woody? Potato doesn't recognize my NIC's either but at least tasksel works. AFAIK, this has nothing to do with tasksel. You do not have to install additional packages if you want to make a NIC work. Greetz, Sebastiaan Thanks for the help. John Purser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Manually bring up NICs not found at install and/or rebuilding Kernel
Okay, so I want to load a module. I've got about 15 windows open trying to find what module I need and all I'm finding is information on drivers. What module do I need to support Intel Pro/100B PCI cards? Thanks, John Purser -Original Message- From: Sebastiaan [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2001 05:59 To: John Purser Cc: 'debian users' Subject: Re: Manually bring up NICs not found at install and/or rebuilding Kernel High, Hello, I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither one recognizes the PCI NICs. Red Hat and W2K get them first try but I don't want either one on this box. During the last attempted install of Woody I tried using the Configure Network alternative but was told that there were no NIC's found which means I have to load different modules in the kernel before I can configure. So either I dynamically load the modules or I have to rebuild my kernel or someone gives me another option. QUESTIONS: Is there any way to bring up my NIC's without rebuilding my Kernel? Which NIC's are you trying to load? You might want to do it manually. After the installation process has installed device drivers on the computer, swap to the second console and activate it. There you go to /target/lib/modules/2.4.9 (or something), look for your module and insmod it manually. When that works, go back to the first console and continue to configure your network. After installation you may want to run 'modconf' or edit /etc/modules to make the module auto load. Would there be any advantage to installing potato and upgrading to Woody? Potato doesn't recognize my NIC's either but at least tasksel works. AFAIK, this has nothing to do with tasksel. You do not have to install additional packages if you want to make a NIC work. Greetz, Sebastiaan Thanks for the help. John Purser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Manually bring up NICs not found at install and/or rebuilding Kernel
Some success! The command I used was modprobe eepro100 and both NIC's came up. I'm running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up exactly the same way because of formatting differences. So where should I put the modprobe info to load it at boot and where should I configure the ethernet cards? Thanks, John Purser -Original Message- From: John Purser [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2001 06:03 To: 'Sebastiaan' Cc: 'debian users' Subject: RE: Manually bring up NICs not found at install and/or rebuilding Kernel Okay, so I want to load a module. I've got about 15 windows open trying to find what module I need and all I'm finding is information on drivers. What module do I need to support Intel Pro/100B PCI cards? Thanks, John Purser -Original Message- From: Sebastiaan [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2001 05:59 To: John Purser Cc: 'debian users' Subject: Re: Manually bring up NICs not found at install and/or rebuilding Kernel High, Hello, I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither one recognizes the PCI NICs. Red Hat and W2K get them first try but I don't want either one on this box. During the last attempted install of Woody I tried using the Configure Network alternative but was told that there were no NIC's found which means I have to load different modules in the kernel before I can configure. So either I dynamically load the modules or I have to rebuild my kernel or someone gives me another option. QUESTIONS: Is there any way to bring up my NIC's without rebuilding my Kernel? Which NIC's are you trying to load? You might want to do it manually. After the installation process has installed device drivers on the computer, swap to the second console and activate it. There you go to /target/lib/modules/2.4.9 (or something), look for your module and insmod it manually. When that works, go back to the first console and continue to configure your network. After installation you may want to run 'modconf' or edit /etc/modules to make the module auto load. Would there be any advantage to installing potato and upgrading to Woody? Potato doesn't recognize my NIC's either but at least tasksel works. AFAIK, this has nothing to do with tasksel. You do not have to install additional packages if you want to make a NIC work. Greetz, Sebastiaan Thanks for the help. John Purser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Manually bring up NICs not found at install and/or rebuilding Kernel
On Fri, Aug 31, 2001 at 06:23:01AM -0600, John Purser wrote: | Some success! | | The command I used was modprobe eepro100 and both NIC's came up. I'm The driver/module is eepro100 :-). Driver and kernel module are basically synonomous. | running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up | exactly the same way because of formatting differences. | | So where should I put the modprobe info to load it at boot and where should | I configure the ethernet cards? In /etc/modutils/some name you like put alias eth0 eepro100 alias eth1 eepro100 and run 'update-modules'. update-modules will grab info from everything in /etc/modutils and write it to /etc/modules.conf (and overwrite any changes you may have made to /etc/modules.conf). Also you need to configure the interfaces in /etc/network/interfaces. Include a line that says auto eth0 and auto eth1 to bring up the interfaces at boot time. The alias line tells the kernel to use the 'eepro100' module whenever something tries to access either 'eth0' or 'eth1'. HTH, -D
Re: Manually bring up NICs not found at install and/or rebuilding Kernel
John Purser([EMAIL PROTECTED]) is reported to have said: Hello, I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither one recognizes the PCI NICs. Red Hat and W2K get them first try but I don't want either one on this box. During the last attempted install of Woody I tried using the Configure Network alternative but was told that there were no NIC's found which means I have to load different modules in the kernel before I can configure. So either I dynamically load the modules or I have to rebuild my kernel or someone gives me another option. I used potato, with Bunk's 2.4.x packages, as a stepping stone to woody and had minimal problems in the upgrade. I think that the 2.4.x packages made that possible. QUESTIONS: Is there any way to bring up my NIC's without rebuilding my Kernel? Only if a 'grep /usr/src/linux/.config' or if that isn't there a grep of the config in /boot shows CONFIG_EEXPRESS_PRO=y or =m If not, then the only way is to rebuild the kernel (Usually a smart move anyway as the stock kernel has much more compiled in then most users require). The smaller kernel the better. I've found a .deb file called kernel-source-2.4.6_2.4.6-1_all.deb at E:\pool\main\k\kernel-source-2.4.6 on the first CD. Is this my Kernel Source? If so how do I install this file. My Kernel compiling instructions assume I'm starting with a .bz2 file. Any tips/suggestions on rebuilding my Kernel? I am running kernel-2.4.9 on both potato and woody. Each of then has this in /usr/src/linux/Documentation/Configure.help: EtherExpress PRO/100 support CONFIG_EEPRO100 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet) card, say Y and read the Ethernet-HOWTO, available from http://www.linuxdoc.org/docs.html#howto . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called eepro100.o. If you want to compile it as a module, say M here and read Documentation/modules.txt as well as Documentation/networking/net-modules.txt. Either compile the kernel using the Debian Way, with make kpkg or the old fashioned way -make dep ; make clean ; make bzImage There are many posts on just how to do this in the archives or by doing a google search. Running Debian is much different then running Red Hat or W2k. You have to be willing to learn things other then clicking on a button. You will be much wiser in the long run. -- You have a tendency to feel you are superior to most computers ___
Re: Manually bring up NICs not found at install and/or rebuilding Kernel
* John Purser ([EMAIL PROTECTED]) [010831 10:34]: Some success! The command I used was modprobe eepro100 and both NIC's came up. I'm running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up exactly the same way because of formatting differences. So where should I put the modprobe info to load it at boot and where should I configure the ethernet cards? See dman's reply for what you should do now. For future reference (and for other readers) you can get your NIC up and running in the initial installation procedure at the point where it asks you to choose which kernel modules you want to load. choose eepro100 (in your case, or whatever your NIC is in other readers' cases) under the 'net' category, and it will be loaded instantly (so that you can complete the install via http or ftp) and set up to load at every boot automatically. -- Vineet http://www.anti-dmca.org Unauthorized use of this .sig may constitute violation of US law. echo Qba\'g gernq ba zr\! |tr 'a-zA-Z' 'n-za-mN-ZA-M' pgpU4zUthM5W5.pgp Description: PGP signature