Good day.

I have a Compaq Armada m300 running Gentoo. I use a PCMCIA Microsoft (yeah) 
MN-520 WiFi card, and use the orinoco driver. It finds the network and connects 
for a while, but my system keeps on hanging after a while of use, usually on 
heavy network transfer or querying the NIC (iwconfig), and all I can do is 
hard-restart. I get the same prob when using another card, a Linksys, also 
using the orinoco driver, so it's not the card. I get the same problem using 
the 2.4.26 and 2.6.9 kernels.

I'm using pcmcia-cs-3.2.5-r1 and orinoco-0.15-rc2.


Here's what I get from /var/log/messages:

Nov 25 17:33:06 aslan eth1: Station identity 001f:0009:0001:0004
Nov 25 17:33:06 aslan eth1: Looks like an Intersil firmware version 1.4.9
Nov 25 17:33:06 aslan eth1: Ad-hoc demo mode supported
Nov 25 17:33:06 aslan eth1: IEEE standard IBSS ad-hoc mode supported
Nov 25 17:33:06 aslan eth1: WEP supported, 104-bit key
Nov 25 17:33:06 aslan eth1: MAC address 00:50:F2:CD:42:2C
Nov 25 17:33:06 aslan eth1: Station name "Prism  I"
Nov 25 17:33:06 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
Nov 25 17:33:06 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
Nov 25 17:33:06 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
Nov 25 17:33:06 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
Nov 25 17:33:06 aslan eth1: ready
Nov 25 17:33:06 aslan eth1: index 0x01: Vcc 5.0, irq 11, io 0x0100-0x013f
Nov 26 01:33:06 aslan cardmgr[24432]: executing: './network start eth1'
Nov 25 17:33:07 aslan eth1: Error -110 setting multicast list.
Nov 25 17:33:07 aslan eth1: Error -110 setting multicast list.
Nov 25 17:33:07 aslan eth1: Error -110 setting multicast list.
Nov 26 01:33:07 aslan cardmgr[24432]: +  * Bringing eth1 up (192.168.0.16)...  
[ ok ]
Nov 26 01:33:07 aslan cardmgr[24432]: +  *   Setting default gateway 
(192.168.0.1)...  [ ok ]
Nov 25 17:33:07 aslan eth1: New link status: Connected (0001)
Nov 25 17:35:02 aslan NETDEV WATCHDOG: eth1: transmit timed out
Nov 25 17:35:02 aslan eth1: Tx timeout! ALLOCFID=ffff, TXCOMPLFID=ffff, 
EVSTAT=8000
Nov 25 17:35:02 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
Nov 25 17:35:03 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
Nov 25 17:35:03 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
        // a lot more of that
Nov 25 17:35:05 aslan orinoco_lock() called with hw_unavailable (dev=cd4e0000)
Nov 25 17:35:05 aslan eth1: New link status: Connected (0001)
Nov 25 17:35:11 aslan hermes @ IO 0x100: Timeout waiting for command completion.
Nov 25 17:35:11 aslan eth1: Error -110 transmitting packet
        // and at this point it crashes
Nov 26 01:39:59 aslan syslog-ng[5946]: syslog-ng version 1.6.5 starting



According to the Linux PCMCIA HOWTO 
(http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-3.html#ss3.3), section 
3.3 - PCMCIA Network Adapters, under the subsection "Diagnosing problems with 
network adapters", the 4th bullet point: "If your card seems to be configured 
properly, but sometimes locks up, particularly under high load, you may need to 
try changing your socket driver timing parameters." It then refers to the 
Startup options doc 
(http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#startup).

That makes sense, and I'm thinking this means I have to do additional config on 
the timing, and I'd like to know how to do this, and what values to set exactly.

Any ideas? I'm really eager to get this working. It's horribly annoying to have 
to use a LAN cable on an otherwise perfect portable notebook. :-(

Thanks in advance.

-- 
Paolo Vanni M. Ve�egas
Ateneo Campus Network Group (AteneoCNG)
4 BSCS, Ateneo de Manila University
--
Philippine Linux Users' Group (PLUG) Mailing List
[EMAIL PROTECTED] (#PLUG @ irc.free.net.ph)
Official Website: http://plug.linux.org.ph
Searchable Archives: http://marc.free.net.ph
.
To leave, go to http://lists.q-linux.com/mailman/listinfo/plug
.
Are you a Linux newbie? To join the newbie list, go to
http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie

Reply via email to