Us Robotics Wireless PCI Card
 

Anyone use this card? USR2216. I cant find what chipset it has in it? Any help is appreciated.

I would like to get G wireless working.

Also, I would liek to use my linux machine as the Acess Point.

Anyone do this?

Thanks

No one is doing this... as far as I know, and I pretty much keep up with things, there is no Linux support for any 802.11g devices currently out there. There is some 802.11a support, but its spotty mostly.

Cheers,

Finegan

Thanks for your reply.

I just ordered 2 dwl-520 with Prism Chipsets(31 bucks each). This Way I can use linux as an AP.

Thanks again.

When you get 'em, try out these drivers:

http://hostap.epitest.fi/

They work brilliantly, and in the case of buggy firmware move WEP off the chip and into userspace.

Cheers,

Finegan

802.11b Drivers (?)
 

I'm way out in left field chasing butterflies on wireless networking, but I found this page of drivers - now if someone could just be helpful and gently point out SOMEthing that'll work with either SOHOware's Netblaster II or the Gigafast 11Mbps USB dongle I'd sure appreciate it!!

Drivers for Wireless Lan Cards

If by Gigafast USB dongle you mean the:

http://www.gigafast.com/products/Wir...I/WE741-UI.htm

WE741-UI

Then yes, its just another atmel chipset device:

http://atmelwlandriver.sourceforge.net/news.html

Its listed on this table:

http://atmelwlandriver.sourceforge.net/usbtable.html

As for the SOHOware's Netblaster II, I have no idea, but if its a USB device, most likely its just another repackaged atmel... got a link to the device?

Cheers,

Finegan

Hi,

I got my cards in dwl-520. I put one in the Linux and one in a PC.
I dont think the Linux is seeing the card correctly.
I have 2 linksys ethernet cards for my existing network.
For some reason it is seeing this D-link card as a linksys.?

Here is lspci

00:00.0 Host bridge: VIA Technologies, Inc. VT8367 [KT266]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8367 [KT333 AGP]
00:0a.0 Network controller: Linksys: Unknown device 8201 (rev 11)
00:0b.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)
00:0c.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)
00:10.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:13.0 VGA compatible controller: Trident Microsystems 3DImage 9750 (rev f3)



Here is what i get trying out the module.

[root@bruce /etc]ssh:# modprobe prism2_pci
/lib/modules/2.4.18-27.8.0/net/prism2_pci.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.18-27.8.0/net/prism2_pci.o: insmod /lib/modules/2.4.18-27.8.0/net/prism2_pci.o failed
/lib/modules/2.4.18-27.8.0/net/prism2_pci.o: insmod prism2_pci failed


Any help is appreciated. I will try the card in a new pci slot first off.

thanks

dlink dwl-520 issues
 

00:0e.0 Network controller: Linksys: Unknown device 8201 (rev 11)
Subsystem: D-Link System Inc: Unknown device 3503
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (16000ns min, 32000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at d800 [size=256]
Region 1: Memory at e5822000 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=100mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-

anyone got any advice? module still wont work with moving the card.

I have no idea what the heck this thing is... I'm going to repost that lspci to the orinoco mailing list. Could you try to modprobe orinoco_pci and see if that puppy will at least load?

Cheers,

Finegan

1/2 way there
 

Fin,

I figured out that this Rev C1 of the dwl-520 card uses the ADMtek 8201 chipset. I sent ADMtek and email and they sent me the source and I loaded the driver 8211.o . I now have a device called eth2 when I do iwconfig.

I can only get the card in ad-hoc and managed mode. No master mode.

I built a bridge (br0) to connect my wired iface eth1, and my wireless eth2, togther as br0.

I now have 5 ifaces when I ifconfig
lo,eth0(outside conn),eth1(inside wired conn),eth2(inside wireless con), br0(bridge so I can speak to wired and wireless at the same time on the same subnet).

1 Major problem.. I cant tlak to my other wireless card sitting 15 feet from me.

Question.. Can I connect directly to a PC without using an Access Point? I hope so, thats why I bougth this dman card in the first place.

Here is iwconfig:

lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

eth2 IEEE 802.11-DS ESSID:"bruce" Nickname:"bruce.yo"
NWID:off/any Mode:Ad-Hoc Frequency:2.412GHz Bit Rate=11Mb/s
Tx-Power=47 dBm Sensitivity:0/65535
Retry limit:3 RTS thr=2346 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

br0 no wireless extensions.

here is ifconfig:


br0 Link encap:Ethernet HWaddr 00:04:5A:7C:0E:F2
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1948 (1.9 Kb) TX bytes:1666 (1.6 Kb)

eth0 Link encap:Ethernet HWaddr (hidden)
inet addr:(hidden) Bcast:255.255.255.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14827 errors:0 dropped:0 overruns:0 frame:0
TX packets:978 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1218512 (1.1 Mb) TX bytes:136496 (133.2 Kb)
Interrupt:5 Base address:0x3000

eth1 Link encap:Ethernet HWaddr 00:04:5A:7C:0E:F2
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:548 dropped:0 overruns:0 carrier:1096
collisions:0 txqueuelen:100
RX bytes:2488 (2.4 Kb) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x5000

eth2 Link encap:Ethernet HWaddr 00:40:05:90:51:9B
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1753 errors:0 dropped:0 overruns:0 frame:0
TX packets:4411 errors:404 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:74769 (73.0 Kb) TX bytes:283042 (276.4 Kb)
Interrupt:5 Base address:0xd800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:89 errors:0 dropped:0 overruns:0 frame:0
TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6362 (6.2 Kb) TX bytes:6362 (6.2 Kb)

---Not sure why eth2 says tx and Rx bytes...not sure who it is talking to?

--Hows the new roomy?
Any help on connecting me wireless will be good.

I am going to send d-link a nasty email about the chipset thing.--Not mentioned on the box anywhere. Of course I only paid 31 bucks each for them.

Got a link to the source? Or can you mail me a copy?

Cheers,

Finegan

Check your mail.

thanks

Rockin' thanks man.

For posterity, I stuck up the source Bruce mailed me at:

http://www.clockwatching.net/~fin/ra...211_src.tar.gz

I'll leave it there until I find it elsewhere, like the ADMtek website for instance, when they bother to put it up...

P.S. You'll have to hack up the Makefile with the directory of your kernel source, and have to have the source installed, it assumes /usr/src/linux-2.4/

Cheers,

Finegan

Yo Man...I still need help. I cant talk to my windows PC using my wireless card. All seems configured correctly, but it wont ping.

Thanks

Hmm... it should work in ad-hoc mode, which is pier to pier with the two machines on the same essid and channel, that's how I ran my network on an orinoco silver, just NATing, not bothering to bridge, an old P1 133 laptop and an early Debian potato.

Cheers,

Finegan