Ketil Froyn wrote:
On 2/23/06, Magnus Therning <[EMAIL PROTECTED]> wrote:
My temporary solution was to change the pattern for one of the devices.
My problematic device is a rt2500-based PCI wireless card. I put the
following in a file in /etc/modprobe.d/ :
options rt2500 ifname=wlan%d
That renamed my wireless to wlan0, instead of jumping between eth0 and
eth1.
Maybe something similar is possible with the drivers you're using?
I tried this:
options eth1394 ifname=ieee%d
but it didn't work. I actually think the ifname= parameter is specific to
the rt2500 driver, and I couldn't see that the eth1394 driver had something
similar. But it was worth a shot anyway, I'm getting frustrated...:p
If you do not want to switch to udev, maybe the package 'ifrename' can
ensure a deterministic naming of your network interfaces. I always had
problems when using ethX (as Magnus has also pointed out in his mail)
which I avoided by assigning new names to all interfaces, e.g. "lan0",
"wlan0", "modem" etc. For a while I got lucky by simply determining the
order in which the modules are loaded in /etc/modules (the first one
gets eth0 in that case, etc.) but that does not seem to work anymore
with newer kernels (ca. 2.6.14 and up, I think).
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
