| View previous topic :: View next topic |
| Author |
Message |
roka
n00b
Joined: 03 Jul 2004
Posts: 18
Location: Bern, Switzerland
|
 Posted: Sat Jul 03, 2004 2:50 pm Post subject: Netgear WG111 usb stick |
 |
|
Is anyone out there running a netgear wg111?
Any hints are appreciated very much.
Roka
[update]
a WG511, prism.org and uberlord's ebuild solved the problem.
Thanks |
|
| Back to top |
|
 |
stagnant
n00b
Joined: 02 Jun 2004
Posts: 16
Location: Boise, Idaho USA
|
| Posted: Tue Aug 10, 2004 3:31 pm Post subject: |
|
|
I have a WG111 and have not been able to get it setup. The first problem I am having is that I do not know which chip it uses. I cracked it open and the chip is covered with a metal plate, which is soldered onto the board.
Anyone out there know which wireless chip this device uses? That should get me to the right place to find a driver/kernel support.
Thanks |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
stagnant
n00b
Joined: 02 Jun 2004
Posts: 16
Location: Boise, Idaho USA
|
| Posted: Tue Aug 10, 2004 5:12 pm Post subject: |
|
|
lspci shows me no mention of the device. Wierd....
I have all the necessary options in my kernel.
| Code: | | tail -f /var/log/messages |
shows me it found the device just fine and hotplug picks it up.
Any other way to see the chip? |
|
| Back to top |
|
|
golloza
Guru
Joined: 14 Mar 2004
Posts: 427
|
| Posted: Tue Aug 10, 2004 7:13 pm Post subject: |
|
|
As the name implies, lspci only lists PCI devices 
emerge usbutils && lsusb |
|
| Back to top |
|
|
roka
n00b
Joined: 03 Jul 2004
Posts: 18
Location: Bern, Switzerland
|
| Posted: Thu Aug 12, 2004 5:57 pm Post subject: Probably a Prism GT |
|
|
lsusb will also not mention the chipset.
It might be a PrismGT, which in this case would be supported by prism54.org. Unfortunately the usb support doesnt seem to be stable yet.
Prism54 forums |
|
| Back to top |
|
|
bluefoxicy
n00b
Joined: 29 Aug 2004
Posts: 2
|
| Posted: Sun Aug 29, 2004 4:38 pm Post subject: |
|
|
I've got the prism54 and prism2_usb drivers and such, can't get this darn thing to work
Can you help me?
lsusb shows bus 001 device 003 ID 0846:4220 NetGear, inc |
|
| Back to top |
|
|
ian!
Bodhisattva
Joined: 25 Feb 2003
Posts: 3829
Location: Essen, Germany
|
| Posted: Sun Aug 29, 2004 5:41 pm Post subject: |
|
|
Moved from 'Networking & Security' because this is a kernel/driver related topic.
_________________
"To have a successful open source project, you need to be at least somewhat successful at getting along with people." -- Daniel Robbins |
|
| Back to top |
|
|
roka
n00b
Joined: 03 Jul 2004
Posts: 18
Location: Bern, Switzerland
|
|
| Back to top |
|
|
porter
Tux's lil' helper
Joined: 29 Jan 2003
Posts: 95
|
| Posted: Wed Sep 01, 2004 9:02 pm Post subject: |
|
|
Fixed this problem by using ndiswrapper. It works by installing the windows inf-file.
| Code: | emerge ndiswrapper
ndiswrapper -i foo.inf
|
_________________
no pain, no gain |
|
| Back to top |
|
|
karr
Tux's lil' helper
Joined: 03 Feb 2004
Posts: 120
Location: albuquerque
|
| Posted: Wed Sep 01, 2004 10:20 pm Post subject: |
|
|
This card uses the madwifi-driver as stated earlier. This driver is masked in portage.
Add this to /etc/portage/package.keywords
| Code: | | net-wireless/madwifi-driver ~x86 |
then
| Code: | | emerge madwifi-driver |
then add an entry for ath0 in /etc/conf.d/net |
|
| Back to top |
|
|
lumbar
n00b
Joined: 31 May 2004
Posts: 4
Location: Osnabrück, Germany
|
| Posted: Mon Jan 17, 2005 11:03 am Post subject: It doesn't work... |
|
|
Hi,
I tried everything: ndiswrapper, update the kernel (now 2.6.10-r4) and madwifi-drivers. I have the WG111 and don't get the wlan0/usb0/ath0-interface... I also don't find a step-by-step-guide. Can you help me? |
|
| Back to top |
|
|
kastenbrot
n00b
Joined: 07 Mar 2005
Posts: 1
|
| Posted: Mon Mar 07, 2005 9:31 pm Post subject: wg111 up and running |
|
|
Hi,
I've got the netgear wg 111 up and running. I'm pretty new to this
whole wireless stuff, nevertheless it works  Maybe this might help
one or two of you, I just did the following steps:
emerge the new baselayout
| Code: |
emerge =baselayout-1.11.9-r1
|
emerge ndiswrapper
| Code: |
emerge =ndiswrapper-0.12-r3
|
install the windows drivers:
IMPORTANT: copy the drivers from your cdrom to your harddisc otherwise
your kernel might hang (in my case it did  ). On my drivers cdrom I've got a
folder called 'ndis5'. I used the drivers in this folder:
| Code: |
# cp -R /mnt/cdrom0/ndis5 /tmp
# ndiswrapper -i /tmp/ndis5/netwg111.inf
# modprobe -i ndiswrapper
|
(now just put ndiswrapper to your /etc/modules.autoload.d/kernel-2.X)
emerge wireless tools:
| Code: |
#emerge wireless-tools
|
now edit your /etc/conf.d/net. here's an example of mine:
| Code: |
#
# use iwconfig and ifconfig
#
modules=( "iwconfig" "ifconfig" )
#
# eth0 and wlan0 ip settings...
#
config_eth0=( "192.168.1.30/24" "1:2:3:4:5:6:7:8a" )
config_wlan0=( "192.168.1.31/24" "1:2:3:4:5:6:7:8b")
#
# set the default gateway
#
routes_eth0=( "default via 192.168.1.1" )
routes_wlan0=( "default via 192.168.1.1" )
|
finally the /etc/conf.d/wireless
| Code: |
#
# set mode for wlan0
#
mode_wlan0="managed"
#
# set essid for wlan0
#
essid_wlan0="my_wirless"
#
# ap is not broadcasting it's SSID
# mac address of ap: 00:11:22:33:44:55
#
mac_essid_001122334455="my_wireless"
#
# wep key for ap
# mac address of ap: 00:11:22:33:44:55
#
mac_key_001122334455="AB99CD88EF77FE88DC99BA000"
#
# WEP key for 'my_wireless'
#
key_my_wireless="AB99CD88EF77FE88DC99BA000"
#
# preferred AP = 'my_wireless'
#
preferred_aps=( "my_wireless" )
|
I hope it helps a bit. |
|
| Back to top |
|
|
|
Kernel & Hardware
