[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Strange behaviour with boottime loading of ipw2200
- From: "darrell pfeifer" <darrellpf gmail com>
- To: "Development discussions related to Fedora Core" <fedora-devel-list redhat com>
- Subject: Re: Strange behaviour with boottime loading of ipw2200
- Date: Fri, 3 Nov 2006 07:28:32 -0800
On 11/3/06, Denis Leroy <denis poolshark org> wrote:
Bill Nottingham wrote:
> Rubin (rubin xs4all nl) said:
>> 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.
>
> Do you have an ifcfg file with the proper HWADDR for the device?
I suffer from the same problem too. In some cases, it's the wireless
that doesn't come up properly, and i have to restart things manually
until it picks it up right. Yes, in my case i have the correct HWADDR
lines in the ifcfg files.
--
fedora-devel-list mailing list
fedora-devel-list redhat com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
The random name seems to be created (by udev?) when the firmware
doesn't load. I suspect it is a timing problem (or the 'failed'
timeout needs to be just a bit longer).
The issue was there for a while a about two months before FC6 release,
disappeared for a bit and got worse just about FC6 release time.
NetworkManager used to deal with the situation just fine, using the
random name when it found it, but is often confused now.
I have a machine that uses IPW2100 and even the module load/unload and
a restart of NM doesn't always fix the problem.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=210780
darrell
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]