Problem with eth after kernel compilation

dancar · 02-26-2004, 08:44 AM

I'm using Slackware 9.1 and I've just compiled a new kernel. And now the system switched my eth cards. The wireless pcmcia used to be eth0 and now is eth1, and the other way around with the onbord ethernet card.
I edite rc.inet1.conf, and got my wireless working again, but it seems that some applications still try to use eth0.
How can I make the kernel recognise them the way they were before?

TIA,
Daniel Carneiro.

nbitaud · 02-26-2004, 08:48 AM

may be with some alias in your modules.conf(kernel 2.4)/modprobe.conf(kernel 2.6) like

alias eth0 <your wireless module>
alias eth1 <your other card>

NB

dancar · 02-26-2004, 10:59 PM

That didn't work.
For some reason after compiling the kernel, it started to load the modules before rc.inet1 runs, because it doesn't mater if I put the aliases in the modules.conf.
As it says in rc.inet1, it searches for aliases in modules.conf only if there is no modules already loaded.

maroonbaboon · 02-26-2004, 11:24 PM

Do you have an /etc/modules file? The modules in there are loaded automatically at boot time. You can change the order.

dancar · 02-26-2004, 11:33 PM

No I don't.
I do have a modules.devfs, but there is no ethx there.

maroonbaboon · 02-27-2004, 02:27 AM

Are you on kernel 2.4 or 2.6? If on 2.4 you could try loading the modules in /etc/modules. In 2.6 I think it's /etc/modprobe or something like that.

dancar · 02-27-2004, 10:33 AM

That didn't work either
Now, I'm running kernel 2.4.25, but before I'd 2.6.3.
2.6.3 wasn't working very well. It was really slow, so I decided to go back to 2.4, but instead of loading the default kernel for slack 9.1 (2.4.22) I compiled a new 2.4.25.
And that's when this thing happened.