1 |
Dirk Heinrichs wrote: |
2 |
> Am Samstag 20 Juni 2009 09:06:51 schrieb Konstantinos Agouros: |
3 |
> |
4 |
>> Hi, |
5 |
>> |
6 |
>> I have a box that serves as a firewall and thus has different NICs. |
7 |
>> However when booting I run into a problem: |
8 |
>> |
9 |
>> One of the NICs needs the de4x5 driver another the tulip one. Udev |
10 |
>> loads tulip first, which then tries to claim the card the needs de4x5 |
11 |
>> but this does not work. So I have to manually set things straight after- |
12 |
>> wards. Is there a way to force it to first load de4x5 and then tulip? |
13 |
>> /etc/modules.autoload.d seems to be used too late. |
14 |
>> |
15 |
> |
16 |
> You can let udev assign persistant names to your network interfaces. |
17 |
> |
18 |
> # cat /etc/udev/rules.d/10-local.rules |
19 |
> KERNEL=="eth*", ATTRS{address}=="00:1c:25:1a:ee:0c", NAME="lan0" |
20 |
> KERNEL=="wlan*", ATTRS{address}=="00:1e:4c:37:39:41", NAME="wlan0" |
21 |
> |
22 |
> Then create the appropriate symlinks for them in /etc/init.d. |
23 |
> |
24 |
> HTH... |
25 |
> |
26 |
> Dirk |
27 |
> |
28 |
|
29 |
Could he not just build the modules into the kernel and then not have to |
30 |
worry about the loading at all? Heck, the only module I use is nvidia |
31 |
but it is not a "in kernel" option. |
32 |
|
33 |
Just a though. He may have a reason for using modules. |
34 |
|
35 |
Dale |
36 |
|
37 |
:-) :-) |