Strange behaviour with boottime loading of ipw2200

[Joe Harnish]

I see this about 33% of the time.  During the FC6 development process I was
getting an error with udev when I would get __tmp#####... but then after a
few rebuilds of packages that went away.  But the issue has come back.

On 11/3/06, Rubin <rubin at xs4all.nl> wrote:
>
> Hi People,
>
> I noticed something weird with the ipw2200 drivers being autoloaded at
> boot. I have an "alias eth1 ipw2200" line in modprobe.conf.
>
> It used to work without a problem for a couple of days but suddenly I'm
> getting very weird interface names. Instead of "eth1", I'm getting
> "__tmp437329847239" where the number behind tmp is random.
>
> NetworkManager gets sort of confused by this. The interface does work
> though when configged by hand.
>
> Doing "rmmod ipw2200 && modprobe ipw2200" gives the expected "eth1"
> interface name.
>
> I was wondering if anyone has seen this kind of thing before. Maybe it
> is the result of a common misconfiguration? A few searches on google
> didn't show anything, hence my question here.
>
> Kind regards,
>
>
> Rubin.
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20061103/3413a13b/attachment.htm>