Hi all,

Well, LOL, I figured out why when I upgrade to 2.16 series kernels I don't have internet.

My pc has two on-board NIC's and I also have a pci-ethernet NIC. I allways use the PCI-NIC as it is seen correctly by this pc when I boot Windows 98 or Windows XP. Those other two NIC's don't get seen properly. No biggie, except until I did this kernel upgrade.

Now in my last kernel the PCI-Based network card was seen as eth0 and that was what I used for my everyday internet. Just that network card.

Now I upgraded and it's seen by Linux as eth1. But I want to use a maual IP setting on there of 192.168.1xx.xx

How do I force my computer now to disregard eth0 and use eht1 with a manually specified IP address.

Linux is "odd" in the fact that in my bios I have the two on-board NIC's turned off, bu t somehow Linux turns them on. It wasn't a big deal until now.

I can get DHCP to work on eth1 but I can't force an IP on it.

Thank you in advance.

first question....
uninstall..or remove...
the distro's i have used all have that ability..
just make sure you keep the right one...eth0 or eth1 is irrelevent once you only have one ethernet...i have one only eth1, did that a while back when i was reconfiguring something and its just stayed that way(not messing with something that works)...

second...linux only looks at bios at boot to find where the drive is...
after that no more lookey...unlike windows that rellies on it...

You can force your card to have eth0 by adding a line to "/etc/modprobe.conf" that says
where <your_ethernet_driver> is the name of the kernel module that the network card uses.

Or you start an editor like vi or pico (or whatever other editor you like) and open up In there you will find the network configuration parameters that you've once set using netconfig. You'll see stuff filled in at the positions
you can transfer these values to the block below that with the variables that have [1] at the end - these are the configuration parameters for eth1.

Eric

Consider this a virtual "bump" on the "alias eth0 <modulename>" since that's about the only way to make this happen with Slackware's init scripts now. You used to be able to add an ether= line to the kernel boot parameters that would specify something unique to enough of the cards (like an IO port address) but that stopped working well when people stopped using ISA cards.

Now it's basically luck as to which cards are detected first (although they tend to be detected in the same order).

As a last-ditch scenario (or maybe a first-run if you're short on IRQs!) you could also just go into the BIOS and disable the on-board NICs.

Adjusting /etc/rc.d/rc.modules to force a module load order works for me. YMMV

With 2.6.x you might want to prepare to just let udev deal with things (they'll be modprobed in the order they're enumerated on the PCI bus). I don't know how Patrick's going to resolve the inet1 script with the way udev can/will initialize network cards but he's going to need to at some point.

What if you don't load your network cards as modules and you build the nic support right into the kernel? Then how could you re-arrange the nics?

Thanks

That would have to use the kernel command-line.

How would I go abouts doing that? I am sure if somebody pointed me in the right direction, I could figure out the rest.

Thanks

Hi all,

I'm going to guess here Cereal, maybe you pass it at /etc/rc.d/rc.local?

Maybe someone here get back to you soon .

Bye the way thanks guys the advice worked, no more swapping wires