<x-flowed>Hello leaf-hardware!

I'm not sure how many people are subscribed yet, so I cc'ed it to 
linux-router. Kinda defeats the purpose, doesn't it? damn. Well 
PCMCIA people, get over to leaf-hardware! I apologize for cross 
posting such a long message.

On thursday, I got my wavelan card up and working with the following

#insmod pcmcia_core.o
#insmod tcic.o irq_list=5,7,9,10
#insmod ds.o
#insmod wvlan_cs.o
#cardmgr

everything would work great! Well, pinging working, and that's all I 
had setup. The reason for the irq_list=5,7,9,10 was because without 
it, the machine froze as per

<http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single 
/PCMCIA-HOWTO.html#ss3.3>

So I added them, and everything worked great.


Since then, I have moved the machine, and switched keybards to a 
different (also AT, the ones with the big plugs) keyboard and a 
different monitor. Same wavelan card, same pc104 modules.

Now, when I startup the machine on the new keyboard, and perform the 
above set of insmod commands, everything works fine. When I execute 
cardmgr, i get

wvlan_cs: Initialization Failed!

BUT(!) I get the two high beeps that are customary for a proper 
initialization. So I run ifconfig, and sure enough, there is eth0, IP 
10.0.1.2. Confused, I ping 10.0.1.2. Success. I try to ping another 
machine, 10.0.1.3. No Succes. And about 5 seconds after the failed 
ping, I get the following message.

wvlan_cs: eth0 Tx timed out! Resetting card.
wvlan_cs: Initialization Failed!

Mmmm...yummy. And after 5 more seconds, it repeats itself. Now, If I 
run the ping command for a little bit (15 seconds), the keyboard 
kicks out and the caps lock and num lock start flashing. 
Hmmm....Hmmmm...

After a reboot, I perform the insmods+cardmgr and I check for 
abnormalities in ifconfig.

eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
           inet addr:10.0.1.2  Bcast:10.0.1.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  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:100
           Base address:0x100

Damn. After some testing, I realize that with this keyboard I no 
longer need irq_list= to be set. probing works. This is bad because 
it's different.

What might /var/log/messages hold?

Jan  5 22:45:38 embedded kernel: Linux PCMCIA Card Services 3.1.24
Jan  5 22:45:38 embedded kernel:   kernel build: 2.2.16-doc #9 Mon 
Jan 22 10:17:28 EST 2001
Jan  5 22:45:38 embedded kernel:   options:  [pci] [cardbus]
Jan  5 22:46:07 embedded kernel: Databook TCIC-2 PCMCIA probe: 
DB86072, 2 sockets
Jan  5 22:46:07 embedded kernel:   irq list (scanned) = 5,7,11,14 
sktirq is irq 11, status change on irq 14
Jan  5 22:46:55 embedded kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.6
Jan  5 22:46:55 embedded kernel: wvlan_cs: (c) Andreas Neuhaus 
<[EMAIL PROTECTED]>
Jan  5 22:47:10 embedded kernel: cs: IO port probe 0x0c00-0x0cff: 
excluding 0xc00-0xc27 0xc40-0xc47 0xc60-0xc67 0xc80-0xc97 0xca0-0xca7 
0xcc0-0xcd7 0xcf0-0xcf7
Jan  5 22:47:10 embedded kernel: cs: IO port probe 0x0800-0x08ff: 
excluding 0x800-0x827 0x840-0x847 0x860-0x867 0x880-0x897 0x8a0-0x8a7 
0x8c0-0x8d7 0x8f0-0x8f7
Jan  5 22:47:10 embedded kernel: cs: IO port probe 0x0100-0x04ff: 
excluding 0x1f0-0x1f7 0x378-0x37f 0x3f0-0x427 0x440-0x447 0x460-0x467 
0x480-0x497 0x4a0-0x4a7 0x4c0-0x4d7 0x4f0-0x4f7
Jan  5 22:47:10 embedded kernel: cs: IO port probe 0x0a00-0x0aff: 
excluding 0xa40-0xa4f 0xaf8-0xaff
Jan  5 22:47:10 embedded kernel: cs: memory probe 0x0d0000-0x0dffff: 
excluding 0xd8000-0xdffff
Jan  5 22:47:10 embedded kernel: cs: memory probe 0x0c0000-0x0cffff: 
excluding 0xc0000-0xc7fff
Jan  5 22:47:10 embedded kernel: wvlan_cs: index 0x01: Vcc 5.0, irq 
5, io 0x0100-0x013f
Jan  5 22:47:10 embedded kernel: wvlan_cs: Registered netdevice eth0
Jan  5 22:47:10 embedded kernel: wvlan_cs: MAC address on eth0 is 00 
00 00 00 00 00
Jan  5 22:47:10 embedded kernel: wvlan_cs: Initialization failed!

Can anyone make sense of this? I sent the mail to andy, as well. 
Might the memory errors be because I only have 8 MBs? But it worked 
before, with the other keyboard!!! Now please take note: the only 
difference is the keyboard!

I have tested the system with my other wavelan card, and I get the same errors.

Also, the cardmgr I am using is 3.1.14, copied from the WRIP package, 
because the cardmgr that compiled on my k6/2.2.15 along with the 
modules i am using returns a "Segmentation Fault." So do all the 
other binary tools from the pcmcmia-cs package. They work fine on my 
k6/2.2.15 but not on this embedded system which is 486/2.2.16. I 
would say that this could be the cause, if it weren't for the fact 
that everything worked with the other keyboard, which I don't have 
access to until monday, and I need to get work done!

Here are my /proc/interrupts and /proc/ioports at boot time

            CPU0
   0:       7862          XT-PIC  timer
   1:        218          XT-PIC  keyboard
   2:          0          XT-PIC  cascade
   6:         10          XT-PIC  floppy
  13:          1          XT-PIC  fpu
NMI:          0

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
02f8-02ff : serial(set)
03c0-03df : vga+
03f0-03f5 : floppy
03f7-03f7 : floppy DIR
03f8-03ff : serial(set)


Does anyone have ANY clue how to fix this? I want my other keyboard!!

/johan ugander
---
.  . . .. ...________________S I G.
   name:   Johan Ugander
   school: AEDT2002
   email:  [EMAIL PROTECTED]
   icq:    4330752
.  . . .. ..._____________________.

_______________________________________________
Leaf-hardware mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-hardware
</x-flowed>

Reply via email to