On Thu, 20 Jul 2006, Marwan Sultan wrote:

Hello Garrett,
Hello doug,

In http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html it doesnot explain how to setup ugen0 device or any wireless device for a client, insted it says
"First, make sure your system can see the wireless card:"

However, in ifconfig -a
it doesnot show any wireless device as you wrote Garrett, but the firewire and nic device,
then how come in the dmesg it can read the ugen0

However, anyone can give me a steps of how to showup my wireless device?
I tried to add the following in /boot/loader.conf

but it doesnt load my device and ifconfig -a will show the same

Will you please, help me setting my wireless device up?
any configuration i should do?

You did not mention Garrett's reference: http://www.bsdforums.org/forums/archive/index.php/t-27794.html. If may be that your card requires you to manually load the firmware as did the Intel card on my laptop. At some point RTFM becomes a necessity. Here is the road map I followed:

1) Make sure the hardware works. The easiest way to do this is to boot to
   windows. If you make your system a FreeBSD only, thats a whole other thread.

2) Make sure your card is in the supported list. If it is and ugen is the
   appropriate drive: man ugen.

3) google your card by name and chipset. The things you find for Linux and the
   other BSDs will probably be helpful at the driver level.

4) The output from dmesg and pciconf -v may help. Turning on verbose mode in
   boot may also help.

5) Search the archives on the freebsd mobile and hardware lists. Search
   questions for ugen in the subject.

6) If all the above fails there is a drive that runs the native windows drivers.
   Project evil I think on sourceforge.

I personally favor running the generic kernel and using kldload and kldstat to figure out what drivers you really need, then loading them at boot time with loader.conf.

As I do not have any laptops that use ugen I can not give you specific advise. I hope the above is sorta what you were looking for and helps. You never mentioned what laptop you have, I assume HP from the dmesg. The HP site might actually help, they support FreeBSD, or so I have been told.



Marwan Sultan wrote:
Hello gurus,

Can someone help me setting up my wireless device on my laptop
im on 6.1R, I tried to do as instructed on handbook, but no luck.
My laptop suppose to be the client, and i have a netgear wireless modem router up and running. How to make the freebsd see the router have the ip, and make the device up?

from dmesg
ugen0: Broadcom Corp HP Integrated Module

The following is the output of ifconfig -a
# ifconfig -a

       inet6 fe80::603f:2ff:fe6c:4184%fwe0 prefixlen 64 scopeid 0x1
       inet netmask 0xff000000 broadcast
       ether 62:3f:02:6c:41:84
       ch 1 dma 0
       inet6 fe80::216:d4ff:fe01:617e%fxp0 prefixlen 64 scopeid 0x2
       inet netmask 0xffffff00 broadcast
       ether 00:16:d4:01:61:7e
       media: Ethernet autoselect (100baseTX <full-duplex>)
       status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
       inet netmask 0xff000000

the following is in /etc/rc.conf  (i think there is something wrong)


the following is compiles in the kernel
wl As i have been told that fwe0 is not the wireless device, then how to show it up?
compiled the kernel to some modifications as i wrote here, but no luck,
Will kindly someone help me, as im new to wireless and bsd.

fwe0 is your ethernet over IEEE1394 (firewire) connection. According to the information above you don't have your wireless interface even present, ie ugen0 was not present in the ifconfig output you have listed above.


Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to