When it comes up? Are you invoking dhcp manually or from a script?

dhcpcd eth1

will usually knock it out. Some of these cards are just grumpy about grabbing dhcp leases regardless, so if all else fails:

ifconfig eth1 192.168.1.X up
route add default gw 192.168.1.1
ping 192.168.1.1

Also, if you are running RH or one of the other sysV init monkeys, you can script all of this into /etc/sysconfig/network-scripts/ifcfg-eth1, or fiddle with it under /etc/pcmcia/wireless.conf, or be a raging slacker like me and just stick the commands in /etc/rc.d/rc.local

Cheers,

Finegan

Well I never..... the wireless card that NetGear told me wouldn't work in *nix is working a treat

Thanks finegan - you are an absolute amazing man!
(BTW, looked at the farm - OMG! and I thought my 6 was bad!)

Hi

I have finally got my MA401 working so it sees the AP MR314
gw and the light is on permanently .

But dhcpcd eth0 just times out.

Therefore I tried doing these commands but at the end I couldn't ping an internet address.

Can anyone see what has gone wrong?

My networking in Linux is weak so bear with me.

Tia

Dre

linux:~ # ifconfig eth0 192.168.0.3 up
linux:~ # ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:30:AB:11:67:59
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::230:abff:fe11:6759/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:8 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:16852 (16.4 Kb)
Interrupt:3 Base address:0x100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:94 errors:0 dropped:0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7868 (7.6 Kb) TX bytes:7868 (7.6 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

linux:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 * 255.255.255.0 U 0 0 0
eth0
linux:~ # route add default gw 192.168.0.1
linux:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 * 255.255.255.0 U 0 0 0
eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0
eth0
linux:~ # ping 194.202.213.54
PING 194.202.213.54 (194.202.213.54) from 192.168.0.3 : 56(84) bytes of data. From 192.168.0.3: icmp_seq=1 Destination Host Unreachable From 192.168.0.3 icmp_seq=1 Destination Host Unreachable From 192.168.0.3 icmp_seq=2 Destination Host Unreachable From 192.168.0.3 icmp_seq=3 Destination Host Unreachable From 192.168.0.3 icmp_seq=4 Destination Host Unreachable From 192.168.0.3 icmp_seq=5 Destination Host Unreachable From 192.168.0.3 icmp_seq=6 Destination Host Unreachable

--- 194.202.213.54 ping statistics ---
7 packets transmitted, 0 received, +7 errors, 100% loss, time 6027ms , pipe 3 linux:~ # linux:~ #

By the way I am using Suse 8.1 should this help.



Funkyrasta

funkyrasta,

some of these questions may sound stupid, but bear with me:

A) what set of drivers are you using?
B) is WEP anywhere in this mess at all?
C) The LEDs on pcmcia cards don't really mean as much under linux wireless as that's a whole extra level of goop for the driver maintainer to bother with. They may mean something, but not the same as in windows. Solid might just mean the device is up and on, not necessarily linked.
D) Make certain your wireless router (I'm not familiar with the model), hasn't got any obnoxious features like, it won't forward packets unless it handed out a dhcp lease. This is rare, but there are a few.
E) If this is running on orinoco_cs, what's "iwconfig eth0" say?
F) Regardless of all of this, can you paste in the last 20 or so lines of "dmesg"

Cheers,

Finegan

Hi Finegan,

I'm be back with this info of the tomorrow night...

Thx for the reply ...

I've being pulling my hair out trying to work out howto get the card to work...

funkyrasta,

some of these questions may sound stupid, but bear with me:

A) what set of drivers are you using?

Module Size Used by Not tainted
snd-pcm-oss 44928 0 (autoclean)
snd-mixer-oss 12728 0 (autoclean) [snd-pcm-oss]
videodev 5600 0 (autoclean)
ide-cd 28388 0 (autoclean)
cdrom 26400 0 (autoclean) [ide-cd]
isa-pnp 29664 0 (unused)
usbserial 18492 0 (autoclean) (unused)
parport_pc 25544 1 (autoclean)
lp 6656 0 (autoclean)
parport 22528 1 (autoclean) [parport_pc lp]
ipv6 138964 -1 (autoclean)
snd-maestro3 13580 0
snd-pcm 63328 0 [snd-pcm-oss snd-maestro3]
snd-timer 11524 0 [snd-pcm]
snd-ac97-codec 26628 0 [snd-maestro3]
snd 31300 0 [snd-pcm-oss snd-mixer-oss snd-maestro3 snd-pcm snd-timer snd-ac97-codec]
soundcore 3396 0 [snd]
af_packet 12904 1 (autoclean)
orinoco_cs 4488 1
orinoco 29912 0 [orinoco_cs]
hermes 5700 0 [orinoco_cs orinoco]
ds 6436 4 [orinoco_cs]
yenta_socket 9536 2
pcmcia_core 40448 0 [orinoco_cs ds yenta_socket]
joydev 5600 0 (unused)
evdev 4352 0 (unused)
input 3168 0 [joydev evdev]
usb-uhci 21612 0 (unused)
usbcore 56768 1 [usbserial snd usb-uhci]
nls_iso8859-1 2812 1 (autoclean)
nls_cp437 4316 1 (autoclean)
vfat 9620 1 (autoclean)
fat 30584 0 (autoclean) [vfat]
reiserfs 179536 7
lvm-mod 62976 31

B) is WEP anywhere in this mess at all?

Yes - In Winblows98 I use 128 Bit encryption.

C) The LEDs on pcmcia cards don't really mean as much under linux wireless as
that's a whole extra level of goop for the driver maintainer to bother with.
They may mean something, but not the same as in windows. Solid might just mean
the device is up and on, not necessarily linked.

Ok understood

D) Make certain your wireless router (I'm not familiar with the model), hasn't
got any obnoxious features like, it won't forward packets unless it handed out a
dhcp lease. This is rare, but there are a few.

No it does not I have to tell it explicitly by allowing a mac address access in it table.

E) If this is running on orinoco_cs, what's "iwconfig eth0" say?

linux:~ # iwconfig eth0
eth0 IEEE 802.11-DS ESSID:"Fireless" Nickname:"funky"
Mode:Managed Frequency:2.412GHz Access Point: 00:30:AB:0C:2D:AD
Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry min limit:8 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality:92/92 Signal level:5/153 Noise level:111/153
Rx invalid nwid:0 Rx invalid crypt:30 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

linux:~ #



F) Regardless of all of this, can you paste in the last 20 or so lines of
"dmesg"

Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 00:04.0
PCI: Sharing IRQ 11 with 00:04.1
PCI: Sharing IRQ 11 with 01:01.0
PCI: Found IRQ 11 for device 00:04.1
PCI: Sharing IRQ 11 with 00:04.0
PCI: Sharing IRQ 11 with 01:01.0
Yenta IRQ list 0498, PCI irq11
Socket status: 30000010
Yenta IRQ list 0498, PCI irq11
Socket status: 30000006
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0820-0x08ff: clean.
cs: IO port probe 0x0800-0x080f: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x158-0x15f 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hermes.c: 5 Apr 2002 David Gibson <hermes@gibson.dropbear.id.au>
orinoco.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
eth0: Station identity 001f:0003:0000:0008
eth0: Looks like an Intersil firmware version 0.08
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key
eth0: MAC address 00:30:AB:11:67:58
eth0: Station name "Prism I"
eth0: ready
eth0: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
PCI: Found IRQ 5 for device 00:08.0
PCI: Sharing IRQ 5 with 00:08.1
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver

Tia

Funkyrasta

All I can tell is that if you're using 128-bit encryption under windows and your router is set for it... uh, from your iwconfig reading, you're not using encryption under linux. You've got a signal, an associated AP, everything looks kosher.

To enable the encryption:

iwconfig eth0 enc 1234567890123

That's it, with a BS key as an example anyway.

Prism2 cards and the orinoco drivers haven't exactly jelled beautifully lately, you might want to turn of encryption at the router and try everything over open air just to make certain its an enc issue.

Cheers,

Finegan

I am a real newbie I have a netgear ma401 network card I ran that ident command disgussed before and found it is actully a ma401ra I nead to know how to install drivers the network I use this on has no wep

The NetGear cards just aren't appearing in the config files for pcmcia-cs yet, apparently using this hack worked for another ma401ra user under the orinoco modules, which come onboard, its just a matter of putting that entry into /etc/pcmcia/config and restarting pcmcia... or at least it should be.

Cheers,

Finegan

if you want to get dhcp working on the device...you need to run dhclient, dhcpcd, dhcpxd, or pump. Currently, I use dhcpcd. I've heard that dhclient is the best one out of all of them, but it doesn't really matter to me. Once you have that, depending on what you're using for distribution, you just need to edit a script file in /etc/sysconfig/network-scripts and make sure that /etc/rc.d/init.d/network is setup properly to handle it. if-up and if-down call ifcfg-ethXX for whatever device you specify.
Hope this helps...
Aaron

PS: I'm doing this from my laptop. I use an Orinoco AP...I forget the model...it's just an Orinoco Silver card.

hi, i'm also new to linux. and boy did i have fun updating mozilla yesterday. anyway, i'm running a ma401 netgear wireless nic on rh8, and with some help from this forum and another website, i was able to get it up and running nicely. however, like someone else in this thread, i'm getting this failure on bootup:

I only get one beep and on the boot up it "failed" to activate the Orinoco_cs driver on eth0 because the device does not seem to be present......delay initilizaiton.

anyway, is there a way i can get rid of this failure that any of you know of? this thread has been most helpful, but if you can help me get rid of this error it would be awesome.

Hi all,

Boy am I glad I stumbled onto this list !!
I have MDK 9.0 (w/ lots of updates from cooker) and could not get my Netgear MA401RA going with drakconf (the config tool).

The EXTREMELY valuable pointer given by jhover (regarding adding entries to /etc/pcmcia/config file) did the trick for me. You folks are the greatest!

This is what I did for the benefit of those are still exploring this issue with Mandrake 9.0:
- update your initscripts rpm (I have ver 7.02-3mdk) -- this may or may not be necessary but doesn't hurt because I read couple posts about problem with the scripts.
- make sure that wireless-tools rpm is installed (doing this with urpmi makes things simple)
- add the following to /etc/pcmcia/config file in the wireless card section:

card "NETGEAR MA401RA Wireless PC"
manfid 0x000b, 0x7300
bind "orinoco_cs"

NOTE: get the numbers for manfid by typing 'cardctrl ident' and punch the corresponding values.

- shutdown off pcmcia: /etc/rc.d/init.d/pcmcia stop
- pop out the card
- turn on pcmcia: /etc/rc.d/init.d/pcmcia start
- pop the card in (yes, you are hot pluging the card and don't worry)
- listen to the sweet sound of two high beeps
- iwconfig should list the card
- now setup rest of the networking using drakconf tool (Networking).
- this time drakconf tool (ie. Mandrake Control Center) should list both cards and allow you to configure everything in each of the ethernet devices.

PS: I haven't made it home yet to test out the wifi connection (esp. w/ WEP) but geting this far was a BIG step for me. Control Centre appears to have all the entry fields for enabling WEP so hopefully that part of it should be smooth sailing (fingers crossed).

Cheers,
Thas

I have Redhat 6.2, with the latest kernel from Redhat for 6.2, 2.2.22-6.2.3, I have pcmcia_cs 3.1.34. Driver loaded when the system startup... cardctl works fine... the problem is when I start network (activating eth0) with it, the whole system freezes. I am doing this on Libretto 50CT... Anyone can give some pointer on what i did wrong? thanks in advance.

p.s. I have MA401RA and using orinoco_cs driver for it.

orinoco_cs went through some changes aroung v0.9, maybe 0.6 (the two old stable ones that were common used releases), I can't remember which. The module will compile right on older kernels, but uses some aspect of 2.4.10 and greater that will cause it to hork on an earlier kernel. I assume this is the drvier that came with pcmcia-cs as the in-kernel modules didn't start until 2.4.3, and I don't think was backported into the 2.2.x series.

dmesg will tell you which version you're running, and really if it isn't at least .9b, its not going to work right with an MA401RA anyway... Honesdtly, there's got to be a way to get a 3 year old distro release to work with that card, but its going to be a headache. A freeze like that probably won't log errors right, but hopefully you can get something off of /var/log/syslog, or messages, or a running dmesg... something might have the choke. There are memory conflicts you can get from pcmcia-cs, might want to check /etc/pcmcia/config... those are the first things that come to mind. All in all, I say keep hacking at it, but really its probably going to be a lot of getting your hands dirty, maybe more than its worth.

Cheers,

Finegan