wi (Lucent) panics on ifconfig wi0 up
know...@aloha.com
with FreeBSD 7. Over the weekend I redid my Fujitsu T-1010 hard drive,
Vista upgrade to Win7, FreeBSD upgrade (fresh install) to 8.0, and added
Ubuntu 9.10. Struggling to get either boot0 or Ubuntu's grub to see all
three, thought I would install grub from ports since it ought to have the
menu info for FreeBSD.Seems odd that Ubuntu's automatic grub menu generator
sees Win7 but misses FreeBSD, maybe my partition scheme is messed up.
While manually fiddling with ifconfig my system would panic, consistently,
on ifconfig wi0 up. This is a fresh install, no changes to KMs, no proc
file system, just straight out of the box. Is there something I need to
configure to get the wi driver working? The card is recongnized when
inserted, the basic entry appears in the ifconfig listing.
Gary Dunn
Open Slate Project
Paul B Mahol
That is obiously bug, introduced with VAPs.
Do not touch wi at all, create wlan first:
# ifconfig wlan create wlandev wi0
Now you can do with wlan0 what you did with wi0 in older versions.
--
Paul B Mahol
know...@aloha.com
Thanks, Paul. That fixed the panic. I read the man page for rc.conf and it
does indeed say that cloning is mandatory in 8.0. The man page for wlan was
not very helpful; ifconfig page is a gem but sooooo complicated.
I still cannot connect to my network.
ifconfig wlan0 ssid MYNET
sets the ssid but
ifconfig wlan0 up
does nothing ... no carrier. It will go up with ssid unspecified (-), but then
ifconfig wlan0 scan
hangs until I do ctrl-C, and a "list scan" completes with no output.
Perhaps this is due to more 8.0 newness -- ignorence on my part. Any
suggestion about what to read?
My network uses no encryption but blocks on MAC address. Any chance the
wlan is fiddling with this? The address displays correctly in ifconfig.
Tonight I can try opening up the access point.
Thanks in advance!
--
Gary Dunn, Honolulu
o...@aloha.com
http://openslate.net/
http://e9erust.blogspot.com/
Sent from a Newton 2100 via Mail V
Paul B Mahol
wi(4) is buggy, if it just works on 7.X fill PR, i dont have card so
can not fix it.
>
> Thanks in advance!
> --
> Gary Dunn, Honolulu
> o...@aloha.com
> http://openslate.net/
> http://e9erust.blogspot.com/
> Sent from a Newton 2100 via Mail V
>
>
>
>
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> To unsubscribe, send any mail to "freebsd-mobil...@freebsd.org"
>
--
Paul B Mahol
know...@aloha.com
OK, I filed PR kern/143074. I sure it it wasn't operator error!! In the
meantime I'll try ndis again on the built-in Intel 5100AGN, which did not
work under 7.x. I'll also plug in my Tivo USB wifi, just for fun. I also
have a CAT-5 top wifi thingy I used on a Play Station 2, that might get me
on-line.
Thanks for your help.
Gary Dunn
Honolulu
Torfinn Ingolfsen
If you haven't tried it already, perhaps you should try the new iwb driver?
See http://forums.freebsd.org/showthread.php?t=8041&highlight=5100
HTH
--
Regards,
Torfinn Ingolfsen
Rui Paulo
You mean "iwn" and that's available on stable/8.
Regards
--
Rui Paulo
Doug Barton
> ifconfig wlan0 ssid MYNET
>
> sets the ssid but
>
> ifconfig wlan0 up
>
> does nothing ... no carrier.
You want to up the wlan0 interface first thing, otherwise you will get
weirdness. When testing manually I can usually do:
ifconfig wlan0 up ssid blah
with a good success rate, but if you're still having problems with that
then you may have to do it as;
ifconfig wlan0 up
ifconfig wlan0 ssid blah
Also, if you're testing with a lot of different configurations I find it
useful to completely reset the thing each time, otherwise, once again,
weirdness. I use the attached script (which I think I've cleaned up
enough to make it usable for you). After you run this you should be able
to do 'ifconfig wlan0 up' and start fresh.
Also, please be aware that wi cards are very limited, and since they are
not in wide use anymore the code hasn't had a lot of love and attention
in recent years.
Good luck,
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
Gary Dunn
A big "mahalo" to Rui, Torfinn, Paul, and everyone else who helped with
this. What a great community.
I was just about to fire up my ndis driver when I read this snippet
about iwn, so I installed csup and upgraded to 8.0 stable. Works like a
charm!
Added this to /boot/loader:
ifnfw_load="YES"
if_iwn_load="YES"
Here is what I added to my rc.conf (my home ssid is Oz):
# msk0 is built-in Ethernet
ifconfig_msk0="DHCP"
# iwn0 is built-in wifi
wlans_iwn0="wlan0"
ifconfig_wlan0="DHCP ssid=Oz"
--
Gary Dunn, Honolulu
o...@aloha.com
http://openslate.net/
http://e9erust.blogspot.com/
Sent from Slate001
M. Warner Losh
Paul B Mahol <one...@gmail.com> writes:
: > My network uses no encryption but blocks on MAC address. Any chance the
: > wlan is fiddling with this? The address displays correctly in ifconfig.
: > Tonight I can try opening up the access point.
:
: wi(4) is buggy, if it just works on 7.X fill PR, i dont have card so
: can not fix it.
I've stopped even testing wi cards that I have... I've got a bunch
just laying around. Ever since I moved to WPA for my home network, I
don't have much use for them :(
Warner
Gary Dunn
Thanks for taking time to reply. As it turns out, the help on how to use
the built-in WiFi with iwn and wlan fixed the problem. My Lucent Gold
card is now exclusively for my Newton MP2100 -- one antique deserves
another. I should take a look at wpa_supplicant.
--
Gary Dunn, Honolulu
o...@aloha.com
http://openslate.net/
http://e9erust.blogspot.com/
Sent from Slate001