Asaf Cohen wrote:
Hi all,
I hope I am not "troubling" the readers of this mailing list, but
after a few nights of trying all kinds of work-arounds I was told this
is the place to ask for help.
After a lot of searching, I bought the Edimax EW-7108PCg wireless
card. It should have worked 100% on linux. Indeed, when I first
inserted it and booted up the system I saw the "activity" light on the
card blinking, all looked well, I saw that the rt2500 was loaded, and
even manged to connect to a network - the "link" light turned on, the
dhcp request was answered by the network, I got an IP an DNS entries -
all looked great.
The Technion network required MAC authentication: it identified the
MAC address of my card, asked me for my password (not a "network"
password, just a one confirming I am a student in the Technion) and I
was told that registration for the network is complete, and I have to
restart my computer.
When restarting, the lights on the card did not blink, there was no
activity at all, as if the card is "dead". Moreover, the card somehow
made the whole networking services get "stuck" - I cannot open
system->networking, kill or restart the dhclient, issue iwconfig,
connect using my ethernet - nothing. The computer is 90% stuck.
It is needless to say that if I reboot without the wireless card
everything is working well. Even if I boot from a live CD WITH the
wireless card -all is well, the card is identified and active... (so
the cards works on Ubuntu, after all it is an "pen" driver)
It seams like something in my network configuration/services was
changed after first connecting successfully to the Technion wireless
network and ever since plugging in the wireless card (or booting up
when it is inside) makes the whole system get stuck.
Any ideas?
just one idea : automated graphical administration programs in
linux are still very weak and troublesome they are not an alternative
to learn how to do things manually by running daemons from console
my advise is to forget system->networking and learn about pppd or
whatever is relevant for your connection
i know little about networking but my best guess is
some script in /etc/rc.d in configured badly try to
run your distribution's initial network setup scripts
in slackware it is simply "netconfig" but ubunto must
have very stupidly made the user unaware of that script
by doing the initial setup automatically
Thanks a lot!!!
Asaf.
--------------------------------------------------------------------------
Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an
empty message to [EMAIL PROTECTED]
--------------------------------------------------------------------------
Haifa Linux Club Mailing List (http://www.haifux.org)
To unsub send an empty message to [EMAIL PROTECTED]
