Problem with wireless on FC5

[Garrett Mitchener]

I also had this problem: I booted my T42 today and the wireless didn't work.
>From what I see, there was some conflict between the ipw2200 entries that I
set up manually way back when and some sort of automatic detection mechanism
that must be new to FC5.  I got it to work like this --

I copied all the /etc/sysconfig/network/ directories to a backup location,
just in case.  Then I used the GUI tool (system-config-network) to delete
all references to my ipw2200.  Then I saved those settings.  Then I went to
the Devices tab and clicked the New button on the tool bar and went through
the wizard and it detected my ipw2200 and such and I was able to configure
it.  (For some reason if you go to the Hardware tab and click New, you get a
series of dialogs that don't list the ipw2200 driver, go figure...)  It
wanted to call the wireless interface dev4960 so I let it -- it was called
eth1 on my system before.  I have no idea why it picked the name dev4960.
But after all that, it now works.  I rebooted and it seems to continue to
work after rebooting.

If I was going to debug this, I'd look into where the dev4960 name came from
and see if maybe there's a race condition between programs competing to
automatically configure wireless ethernet.

-wgm

On 4/18/06, Paul Goodman <lancherider at hotmail.com> wrote:
>
> >There is a bug which can be worked around by adding the following line
> >to /etc/modprobe.conf
> >
> >  install ipw2200 /sbin/modprobe -q eth0; /sbin/modprobe --ignore-install
> >ipw2200
> >
> >Once done reboot and see if it works.
>
> Still no luck. Thanks for the tip.
>
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/users/attachments/20060418/e2cc9381/attachment-0002.html