| View previous topic :: View next topic |
| Author |
Message |
Stu L Tissimus
Veteran
Joined: 08 Jun 2003
Posts: 1339
Location: NJ, 5 minutes from NYC
|
 Posted: Tue May 25, 2004 4:33 am Post subject: NetGear WG511 Installation Guide |
 |
|
Okay - Installing this was surprisingly easy for me, but I've decided that I might as well post this for those of you not having luck with your Netgear card.
1. Requirements
----------------------------------------------------------------------------------
2. Setting up your kernel
To use a PCMCIA WLAN card, you must enable : | Code: | Code maturity level options --->
Prompt for development and/or incomplete code/drivers
Select only drivers expected to compile cleanly
Select only drivers that don't need
compile-time external firmware
Bus options (PCI, PCMCIA, EISA, MCA, ISA) --->
Support for hot-pluggable devices
Generic Driver Options --->
Hotplug firmware loading support
Device Drivers --->
Networking Support --->
Wireless LAN (Non-Ham Radio) --->
Wireless Lan drivers
Bus options (PCI, PCMCIA, EISA, MCA, ISA) --->
PCMCIA/CardBus support --->
PCMCIA/CardBus support (m or y)
CardBus yenta-compatible bridge support (m or y) |
Also, to use a Prism54-based card, you will need to enable | Code: |
Device Drivers --->
Networking Support --->
Wireless Lan (Non-Ham Radio) --->
Intersil Prism GT/Duette/Indigo PCI/Cardbus |
It's nice to see that you don't need to do any annoying external compilation of the Prism54 driver - It comes in a nice package for you with any kernel at 2.6.5 or higher. Now, recompile your kernel by doing: | Code: | | make modules modules_install bzImage |
and copying arch/i386/boot/bzImage back to /boot. Do not reboot your machine yet.
----------------------------------------------------------------------------------
3. Install UberLord's wireless script
Uberlord has made a simply amazing script for us - It automatically connects to the closest access point by executing
etc/init.d/net.eth0 start . You all have no idea how annoying it must have been to create this script. So, let's all give Mr. Uuberlord a nice big 'ol round of applause. 
Now, let's get to installing this baby. It should be pretty straightforward to most of you - Go to his website, and download net-wireless/wireless-config-0.4.4.ebuild. Put this in /usr/local/portage/net-wireless/wireless-config . Turn into a superuser, and execute ebuild /usr/local/portage/net-wireless/wireless-config/wireless-config-0.4.4.ebuild digest . Then, you may proceed to install it as if it were any normal ebuild - ACCEPT_KEYWORDS="~x86" emerge wireless-config ! (NOTE: You need to have your Portage Overlay directory enabled. Search the forums on how to do this.) There will be some messages that pop up at the end of the installation - Follow them!
----------------------------------------------------------------------------------
4. Install the firmware
The Prism54 cipset is, indeed, very weird. The way I understand it, firmware is actually loaded straight onto the card from the machine. Not a very orthodox way of doing things. So, you will need the firmware installed on the computer. You must obtain the 1.0.4.3.arm file - There is a link to it in the Requirements section. Now, download this, and move it into /usr/lib/hotplug/firmware . Rename it to "isl3890". installing the firmware wasn't as hard as you thought it would be, huh? 
----------------------------------------------------------------------------------
5. Edit /etc/conf.d/net
This part is relatively simple. Open up /etc/conf.d/net with Nano, or Vim, or whatever your favorite text editor is. Now, make sure these lines are in it: | Code: | iface_eth0="dhcp"
gateway="eth0/192.168.0.1" |
and you should be set to go! Just reboot your computer, and start the net.eth0 script.
----------------------------------------------------------------------------------
I hope this helps!
Stu L Tissimus.
_________________
old outdated sig |
|
| Back to top |
|
 |
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Tue May 25, 2004 10:28 am Post subject: |
|
|
thanks a lot, Stu L Tissimus 
I've been looking all over for this in the past few months.
I too have a netgear WG511 card.
It looks great, and I will give it a try soon 
*bump* up the thread  |
|
| Back to top |
|
|
Stu L Tissimus
Veteran
Joined: 08 Jun 2003
Posts: 1339
Location: NJ, 5 minutes from NYC
|
| Posted: Tue May 25, 2004 4:49 pm Post subject: |
|
|
Thanks, Beast! Tell me if it works for you.
_________________
old outdated sig |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed May 26, 2004 12:28 pm Post subject: |
|
|
hi dude,
the beast reporting back
just reinstall gentoo whole night yesterday, and  yes your installation guide works without a hassle , got it setup and surf in a few minutes
thanks a lot, man.
I'm not using the UeberLord's script though, it looks too complicated  .
So I rewrote a simplier auto script, (stripped down from prism54.org gentoo forum's)
prism54script
---------------------------------------------------------------------
| Code: |
#!/bin/bash
# script name: prism54script
# script location: /etc/hotplug/pci/
# replace the script name to: prism54
# and: chmod a+x prism54
# description: my prism54 autostart script
# auth: beastmaster
# for restart: /etc/hotplug/pci/prism54
# version: 0.2
# /etc/init.d/net.eth1 start # optional, it's for eth0 auto start
# you can always just do dhcpcd eth0 later
ifconfig eth1 up # wake up eth1 (wireless network slot)
#sleep 1
echo "---I AM EXECUTING:----------------------------------"
echo "iwconfig eth1 mode Managed"
iwconfig eth1 mode Managed # as client mode
echo "---I AM EXECUTING:----------------------------------"
echo "iwlist eth1 scan"
iwlist eth1 scan
# just to see what essid access points are available there
# you can change access point network manually later.
# just do iwconfig eth1 essid nameofessidofyourchoice
sleep 1 # pause 1 second, the beast needs to see
echo "---I AM EXECUTING:----------------------------------"
# with static wireless network:
# should manually add your own key (for accessing encrypted wireless network) here:
# iwconfig eth1 key xyzMYkey123
# iwconfig eth1 essid nameOfTheEssid
# above, should replace nameOfTheEssid to your choice
# or just do: dhcpcd, let it auto-start/configure
echo "dhcpcd eth1"
dhcpcd eth1 # auto detect network for eth1
|
------------------------------------------------------------
Last edited by beastmaster on Sat May 29, 2004 9:39 pm; edited 2 times in total |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed May 26, 2004 12:43 pm Post subject: |
|
|
and another thing, tested in gentoo-dev-source-2.6.5-r1 version, it works.
the installation guide doesn't only work for Netgear WG511 Card exclusively, it works with any Intersil Prism GT/Duette/Indigo based wireless cards too.
*bump up* |
|
| Back to top |
|
|
jarealist
Apprentice
Joined: 07 Oct 2002
Posts: 228
|
| Posted: Fri May 28, 2004 9:36 am Post subject: |
|
|
| Just another "Thank You"! Just purchased a Netgear WGB511 54 Mbps Cable/DSL Wireless Router package (WGR614 Router and WG511 Card). Your How-To made my day as I haven't been able to get the ipw2100 driver to work on my Sony Vaio yet. |
|
| Back to top |
|
|
funklord
Tux's lil' helper
Joined: 29 May 2004
Posts: 78
|
| Posted: Sat May 29, 2004 8:49 pm Post subject: |
|
|
I followed your instructions pretty much, and all seemed well but I'm having problems getting the card to work exactly right. I think it might be related to this part:
| Code: | Generic Driver Options --->
Hotplug firmware loading support |
When I look at this part in the kernel configuration, I don't have an option to select it, only three dashes ("---") instead of "[ ]" or "( )". Could this be a problem? Do I have to enable something else before I can enable this?
Thanks for the great guide! |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Sat May 29, 2004 9:37 pm Post subject: |
|
|
are you using kernel gentoo-dev-source 2.6.5-r1 or u are using some others?
generally 2.6.5 + works,
if that option can't be selected, just leave it there and compile |
|
| Back to top |
|
|
d0wn_under
Guru
Joined: 13 Mar 2003
Posts: 300
Location: Sheffield, England
|
| Posted: Fri Jun 04, 2004 11:22 pm Post subject: problems |
|
|
I am having some problems getting the WG511. I have followed your instructions but when I put the card in or when I boot I get the following lines in dmesg
prism54: Unknown symbol release_firmware
prism54: Unknown symbol request_firmware
I have put the firmware from your link into the right directory, I have tried it with the module from the kernel and from the prism54 site but with no luck.
Anyone any ideas?
uname -a gives:
Linux tasslehoff 2.6.5-gentoo-r1 #1 SMP Fri May 28 22:16:06 GMT 2004 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
and lspci:
02:00.0 Network controller: Harris Semiconductor: Unknown device 3890 (rev 01) |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Fri Jun 04, 2004 11:27 pm Post subject: |
|
|
did you rename the firware to isl3890?
and set it to executable? just some thoughts |
|
| Back to top |
|
|
d0wn_under
Guru
Joined: 13 Mar 2003
Posts: 300
Location: Sheffield, England
|
| Posted: Fri Jun 04, 2004 11:38 pm Post subject: |
|
|
It was isl3890 already but I made it executable (doesn't mention that in instructions) and it didn't help.
Extra info, modprobe prism54 gives:
FATAL: Error inserting prism54 (/lib/modules/2.6.5-gentoo-r1/kernel/drivers/net/wireless/prism54/prism54.ko): Unknown symbol in module, or unknown parameter (see dmesg)
the dmesg lines are show in the previous message
Both with the original kernel module and with the one from the prism54 site. |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Sat Jun 05, 2004 12:12 am Post subject: |
|
|
did you compile prism54 as a module?
look inside /lib/modules/2.6.5-gentoo-r1/kernel/drivers/net/wireless/prism54/
and see if it's there |
|
| Back to top |
|
|
d0wn_under
Guru
Joined: 13 Mar 2003
Posts: 300
Location: Sheffield, England
|
| Posted: Sat Jun 05, 2004 1:00 pm Post subject: |
|
|
ye, its there. The modprobe must be finding it or I would be getting a "module not found" error.
Any other ideas? |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Sat Jun 05, 2004 4:27 pm Post subject: |
|
|
what kernel version do you have?
perhaps you can use my kernel config file. |
|
| Back to top |
|
|
d0wn_under
Guru
Joined: 13 Mar 2003
Posts: 300
Location: Sheffield, England
|
| Posted: Sat Jun 05, 2004 7:16 pm Post subject: |
|
|
for my kernel version, see the uname -a posted above.
I would post my .config file, but I don't think that would be appreciated |
|
| Back to top |
|
|
d0wn_under
Guru
Joined: 13 Mar 2003
Posts: 300
Location: Sheffield, England
|
| Posted: Sat Jun 05, 2004 9:01 pm Post subject: It works! |
|
|
I recompiled the kernel to add sound support, rebooted and the card lights came on and I had network!
All I changed in the kernel was adding the sound card module!
Wow |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Sat Jun 05, 2004 9:19 pm Post subject: |
|
|
| Quote: |
I recompiled the kernel to add sound support, rebooted and the card lights came on and I had network!
All I changed in the kernel was adding the sound card module!
|
didn't know sound chip module had things to do with the "networking" conflict .
but it's all worked out for u, |
|
| Back to top |
|
|
d0wn_under
Guru
Joined: 13 Mar 2003
Posts: 300
Location: Sheffield, England
|
| Posted: Sat Jun 05, 2004 9:47 pm Post subject: |
|
|
I haven't got sound working yet but at least I have full networking now.
Cheers for trying to help, don't you just love/hate it when things suddenly start working and you have no idea why! |
|
| Back to top |
|
|
tam
Guru
Joined: 04 Mar 2003
Posts: 569
|
| Posted: Tue Jun 15, 2004 12:21 pm Post subject: |
|
|
| beastmaster wrote: |
I'm not using the UeberLord's script though, it looks too complicated .
So I rewrote a simplier auto script, (stripped down from prism54.org gentoo forum's)
prism54script
|
I tried to use your script, but it's not executed when I insert the WG511. Can you help? |
|
| Back to top |
|
|
d0wn_under
Guru
Joined: 13 Mar 2003
Posts: 300
Location: Sheffield, England
|
| Posted: Tue Jun 15, 2004 1:13 pm Post subject: |
|
|
| Mine is working and I'm happy to post any config files if anyone wants to see any. I don't know 100% why it is working so I can't offer much more help than that. |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 23, 2004 11:24 am Post subject: |
|
|
| tam wrote: | | beastmaster wrote: |
I'm not using the UeberLord's script though, it looks too complicated .
So I rewrote a simplier auto script, (stripped down from prism54.org gentoo forum's)
prism54script
|
I tried to use your script, but it's not executed when I insert the WG511. Can you help? |
hi tam, make sure that you add "prism54" or "prism54script" to rc.conf or any bootup script when linux boots up.
|
|
| Back to top |
|
|
tam
Guru
Joined: 04 Mar 2003
Posts: 569
|
| Posted: Wed Jun 23, 2004 11:35 am Post subject: |
|
|
Hi!
Just a few minutes ago I solved my problem. I have re-emerged prism54 driver, also I have updated to the latest gentoo-dev kernel. Any or combination of this has solved the problem.
The prism54 script in /etc/hotlug/pci is executed now when I insert my WG511. |
|
| Back to top |
|
|
beastmaster
Apprentice
Joined: 24 May 2004
Posts: 230
|
| Posted: Wed Jun 23, 2004 7:04 pm Post subject: |
|
|
| ah cool |
|
| Back to top |
|
|
MikePikeFL
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 78
|
| Posted: Sun Jun 27, 2004 6:29 pm Post subject: |
|
|
I finally got this working... after hours of work and messing around, I had to change my WEP configuration on the WAP and all the other wireless devices to use the default "first index" for the WEP key... I was trying to use the third. It works fine in windows, and LOOKS like it SHOULD work fine in linux, but no dice.
At least I have wlan with my new WG511 now. Anyone know what you have to do to get airsnort to work? And what about renaming the device to "wlan0" like the ndiswrapper driver I had for my previous card? It makes life much easier when dealing with the docking station! A simple "alias wlan0 prism54" in /etc/modules.d/aliases does not work!
Thanks! |
|
| Back to top |
|
|
Stu L Tissimus
Veteran
Joined: 08 Jun 2003
Posts: 1339
Location: NJ, 5 minutes from NYC
|
| Posted: Mon Jun 28, 2004 6:01 am Post subject: |
|
|
Heh, nice to know it worked for everybody else. If you have any problems, just ask!
_________________
old outdated sig |
|
| Back to top |
|
|
|
Kernel & Hardware
