On Thu, 2005-01-27 at 15:09 -0700, Mike Hoy wrote:
> I went over to Craig White's place and after about an hour and a half we
> got the card working. Well actually he got it working, I was all out of
> ideas.
>
> The bottom line:
>
> ditch Kwifimanager!
>
> kwifimanager is probably a useful tool for searching for available
> wireless nets but it was not helpful for troubleshooting this problem.
>
>
> Go directly to Network Configuration (in Gnome: Applications > System
> Settings > Network)
> and setup your wireless card. Activate it. Specific instructions here
> are hard to give as it depends on your situation. By choosing this
> little application the wireless was no problem at all. I later set it up
> to start at boot up and now wifi just works when the computer turns on.
>
> Network was only useful 'AFTER' kudzu identified and put module
> into /etc/modprobe.conf.
>
> ifup and ifdown work as well.
>
> modprobe.conf has:
> alias eth2 orinoco_cs
>
> also if necessary run:
> kudzu
> from command line and configure your netgear wifi card.
>
> kudzu identified the hardware
> and wrote the entry:
>
> alias eth1 orinoco_cs
>
> in modprobe.conf
>
> if you start without wireless card in slot, it may run kudzu. Best to
> tell it to do nothing otherwise, it will remove entry from modprobe.conf
>
> I wish I could give you a nice step by step but we tried so many things
> So fast I only really remember the bottom line.
----
just a bit of oversight here - cuz I did see what worked.
I have no clue why Mike didn't get it to work before - it should have
been a piece of cake. It would have been a piece of cake if I hadn't for
the fun of it, inserted an encryption key and turned on encryption when
I bought the wireless AP and then promptly turned wireless off.
When Mike came over, I turned the Wireless AP on and 'assumed' that
encryption was off. Duh - after a little over an hour with nothing
working at all, we realized that encryption was actually on.
Anyway, dissecting Mike's message above - I guess his point was to leave
a trail of how he solved problem but I didn't feel his above message was
gonna get anyone closer to the solution...
He say's - ditch kwifimanager - I say, who knows...It's just not a tool
that interests me much.
I had him run kudzu - a program apparently unique to redhat which probes
for hardware either without entry in /etc/modprobe.conf and entries
in /etc/modprobe.conf that aren't detected in hardware. Normally, kudzu
runs at startup. For some reason, kudzu wasn't tossing up alerts about
newly found hardware at startup when the card was inserted (kudzu
running before pcmcia initialization?). Once booted, logged in and
acquiring root shell, a manual run of kudzu located Netgear card,
identified the module as orinoco_cs and assigned it to the next
available ethernet device (in his case, eth1), and finally, wrote the
entry into /etc/modprobe.conf
Once properly located, the Gnome Network Manager allowed us to add a new
profile which identified the eth1 as a wireless device, we set it to
automatically locate the wireless channel (it selected the closest AP -
mine) and bound it to the physical device (the Netgear #MA401).
et voila
Craig
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)