Next-in-Thread Next Message

Question BreezeCom/Raylink PCMCIA Does Not Configure on Toshiba Tecra 

Forum: PCMCIA on Toshiba laptops
Date: 1999, Dec 08
From: John Turkovich <turkovich@draper.com>

I'm an application developer who is trying to host a BreezeCom SA-PC PCMCIA card
on a Toshiba Tecra running Linux. The card is recognized but does not configure.
I've determined that an interrupt occurs while configuration is occurring.
I'm using a device driver developed by Corey Thomas, which I located on the Web.
Thanks for the work Cory.
Some sort of memory violation interrupt occurs while executing ray_cs.o.
I believe ray_init was trying to execute memcpy_fromio at the time.
I'm not sure, but I think so.

I've reviewed many web pages associated with Linux, PCMCIA cards, and
Toshiba laptops - most notably works of David Hinds, Corey Thomas and
associated as well as derivative works. A lot of good progress has been made.
I acknowledge that these sites discourage the use of Toshiba laptops
 while trying to develop a PCMCIA driver for Linux, but I'm stuck with the Toshiba.
I'm not a developer of device drivers, but my high level applications depend on them.

Can anyone provide some insight to how I might solve my problem?
Below is information about the state of my system.

1) System Hardware
Toshiba Tecra 730CDT
BreezeCom SA-PC (aka Raytheon Raylink)

2) Software
Mandrake 6.1
Linux kernel via uname -rv: 2.2.13-7mdk #1 Wed Sep 15 18:02:18 CEST 1999
PCMCIA Card Services 3.1.0 from Corey Thomas

3) Changes to /etc/pcmcia Files
3.1) Two sections were added to /etc/pcmcia/config
The first section is:
device "ray_cs"
  class "network" module "ray_cs"

The second section is:
card "RayLink PC Card WLAN Adapter"
  version "RAYTHEON"
#  manfid 0x01a6, 0x0000
  bind "ray_cs"
Note: I commented the manfid line and replaced with version.

3.2) Changes to /etc/pcmcia/config.opts
I just added "source ./ray_cs.opts at the end of the file.
The following lines are in the file.
I include them because they may be helpful.
#
# System resources available for PCMCIA devices
#
include port 0x100-0x4ff, port 0x1000-0x17ff
include memory 0xc0000-0xfffff
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
#
# Extra port range for IBM Token Ring
#
include port 0xa00-0xaff

3.3) Addition of ray_cs.opts to /etc/pcmcia
The uncommented contents of ray_cs.opts is:
module "ray_cs" opts "bc=1 pc_debug=4 essid=ESSID1 hop_dwell=128 beacon_period=256 translate=1 net_type=1"

4) cardctl Queries
> cardctl ident
Socket 0:
  no product info available
Socket 1:
  product info: "RAYTHEON", "RayLink PC Card WLAN Adapter", "Version 4.82 Dec 97"
  manfid: 0x01a6, 0x0000
  function: 6 (network)

> cardctl status
Socket 0:
  no card
Socket 1:
  5V 16-bit PC Card
  function 0: [ready]

>cardctl config
Socket 0:
  not configured
Socket 1:
  Vcc 5.0V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 3 [exclusive] [level]
  function 0:
    config base 0x0f00
      option 0x41 status 0x00 copy 0x00
  memory 0x0000-0x7fff @ 0x000d1000 [wait] [8bit]
  memory 0x8000-0xbfff @ 0x000d9000 [wait] [8bit]
  memory 0x0000-0x0fff @ 0x000dd000 [attr] [wait] [8bit]

>cardctl scheme
Current scheme: 'default'.

> cat /proc/interrupts
           CPU0       
  0:    7175608          XT-PIC  timer
  1:       7898          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:     839140          XT-PIC  ray_cs
  8:          1          XT-PIC  rtc
 11:         11          XT-PIC  i82365
 12:     131077          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:     420126          XT-PIC  ide0
 15:          5          XT-PIC  ide1
NMI:          0

5) System Log Messages
Below are pertinent messages from my /var/log/messages system log.
Five sections from the system messages log follow.
Eac section is delimited by ============ <comment> ===============.
The first section contains a a few messages as my system hung yesterday followed by
messages associated with a restart of the system.
The next two sections contain messages emitted when I inserted and removed a 3COM EtherLink III card.
I can connect to my local network with using the 3COM PCMCIA card.
The next section contains messages emitted when I insert the BreezeCom SA-PC card.
I've set the pc-debug level to 4. I also inserted a number of my own printk statements
to help isolate the problem.
Finally, the system hangs when I remove the BreezeCom SA-PC card.
===================== System Shutdown and Restart from Yesterday ===========================
Dec  7 17:42:09 maryland -- MARK --
Dec  7 17:51:45 maryland PAM_pwdb[494]: (kde) session closed for user root
Dec  7 17:51:55 maryland kernel: ray_event(0x000008) 
Dec  7 18:01:34 maryland syslogd 1.3-3: restart.
Dec  7 18:01:34 maryland syslog: syslogd startup succeeded
Dec  7 18:01:34 maryland syslog: klogd startup succeeded
Dec  7 18:01:34 maryland kernel: klogd 1.3-3, log source = /proc/kmsg started.
Dec  7 18:01:34 maryland kernel: Inspecting /boot/System.map-2.2.13-7mdk
Dec  7 18:01:35 maryland kernel: Loaded 5998 symbols from /boot/System.map-2.2.13-7mdk.
Dec  7 18:01:35 maryland kernel: Symbols match kernel version 2.2.13.
Dec  7 18:01:35 maryland kernel: Loaded 49 symbols from 2 modules.
Dec  7 18:01:35 maryland kernel: Linux version 2.2.13-7mdk (root@kenobi.mandrakesoft.com) (gcc version 2.95.1 19990816 (release)) #1 Wed Sep 15 18:02:18 CEST 1999 
Dec  7 18:01:35 maryland kernel: Detected 149693808 Hz processor. 
Dec  7 18:01:35 maryland kernel: Console: colour VGA+ 80x25 
Dec  7 18:01:35 maryland kernel: Calibrating delay loop... 59.60 BogoMIPS 
Dec  7 18:01:35 maryland kernel: Memory: 30808k/32896k available (1044k kernel code, 416k reserved, 568k data, 60k init) 
Dec  7 18:01:35 maryland kernel: VFS: Diskquotas version dquot_6.4.0 initialized 
Dec  7 18:01:35 maryland kernel: CPU: Intel Pentium 75 - 200 stepping 0c 
Dec  7 18:01:35 maryland kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. 
Dec  7 18:01:35 maryland kernel: Checking 'hlt' instruction... OK. 
Dec  7 18:01:35 maryland kernel: Intel Pentium with F0 0F bug - workaround enabled. 
Dec  7 18:01:35 maryland kernel: POSIX conformance testing by UNIFIX 
Dec  7 18:01:35 maryland kernel: PCI: PCI BIOS revision 2.10 entry at 0xfd49e 
Dec  7 18:01:35 maryland kernel: PCI: Using configuration type 1 
Dec  7 18:01:35 maryland kernel: PCI: Probing PCI hardware 
Dec  7 18:01:35 maryland kernel: Linux NET4.0 for Linux 2.2 
Dec  7 18:01:35 maryland kernel: Based upon Swansea University Computer Society NET3.039 
Dec  7 18:01:35 maryland kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. 
Dec  7 18:01:35 maryland kernel: NET4: Linux TCP/IP 1.0 for NET4.0 
Dec  7 18:01:35 maryland kernel: IP Protocols: ICMP, UDP, TCP, IGMP 
Dec  7 18:01:35 maryland kernel: Initializing RT netlink socket 
Dec  7 18:01:35 maryland kernel: Starting kswapd v 1.5  
Dec  7 18:01:35 maryland kernel: Detected PS/2 Mouse Port. 
Dec  7 18:01:35 maryland kernel: Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled 
Dec  7 18:01:35 maryland kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A 
Dec  7 18:01:35 maryland kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A 
Dec  7 18:01:35 maryland kernel: pty: 256 Unix98 ptys configured 
Dec  7 18:01:35 maryland kernel: apm: BIOS version 1.2 Flags 0x02 (Driver version 1.9) 
Dec  7 18:01:35 maryland kernel: Real Time Clock Driver v1.09 
Dec  7 18:01:35 maryland kernel: RAM disk driver initialized:  16 RAM disks of 4096K size 
Dec  7 18:01:35 maryland kernel: hda: TOSHIBA MK2101MAN, ATA DISK drive 
Dec  7 18:01:35 maryland kernel: hdc: TOSHIBA CD-ROM XM-1402B, ATAPI CDROM drive 
Dec  7 18:01:35 maryland kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 
Dec  7 18:01:35 maryland kernel: ide1 at 0x170-0x177,0x376 on irq 15 
Dec  7 18:01:35 maryland kernel: hda: TOSHIBA MK2101MAN, 2067MB w/128kB Cache, CHS=525/128/63 
Dec  7 18:01:35 maryland kernel: hdc: ATAPI 6X CD-ROM drive, 128kB Cache 
Dec  7 18:01:35 maryland kernel: Uniform CDROM driver Revision: 2.55 
Dec  7 18:01:35 maryland kernel: Floppy drive(s): fd0 is 1.44M 
Dec  7 18:01:35 maryland kernel: FDC 0 is an 8272A 
Dec  7 18:01:35 maryland kernel: md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 
Dec  7 18:01:35 maryland kernel: scsi : 0 hosts. 
Dec  7 18:01:35 maryland kernel: scsi : detected total. 
Dec  7 18:01:35 maryland kernel: Partition check: 
Dec  7 18:01:35 maryland kernel:  hda: hda1 hda2 < hda5 hda6 hda7 > 
Dec  7 18:01:35 maryland kernel: VFS: Mounted root (ext2 filesystem) readonly. 
Dec  7 18:01:35 maryland kernel: Freeing unused kernel memory: 60k freed 
Dec  7 18:01:35 maryland kernel: Adding Swap: 36252k swap-space (priority -1) 
Dec  7 18:01:35 maryland kernel: WaveLAN init_module(): doing device probing (bad !) 
Dec  7 18:01:35 maryland kernel: Specify base addresses while loading module to correct the problem 
Dec  7 18:01:35 maryland kernel: WaveLAN init_module(): no device found 
Dec  7 18:01:35 maryland atd: atd startup succeeded
Dec  7 18:01:38 maryland kernel: Linux PCMCIA Card Services 3.1.0 
Dec  7 18:01:38 maryland kernel:   kernel build: 2.2.13-7mdk #1 Wed Sep 15 18:02:18 CEST 1999 
Dec  7 18:01:38 maryland kernel:   options:  [pci] [cardbus] [apm] [pnp] 
Dec  7 18:01:38 maryland kernel: PnP: PNP BIOS installation structure at 0x800f8dd0 
Dec  7 18:01:38 maryland kernel: PnP: PNP BIOS version 1.0, entry at f0000:9a42, dseg at 0 
Dec  7 18:01:38 maryland kernel: Intel PCIC probe:  
Dec  7 18:01:38 maryland kernel:   Intel i82365sl B step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets 
Dec  7 18:01:38 maryland kernel:     host opts [0]: none 
Dec  7 18:01:38 maryland kernel:     host opts [1]: none 
Dec  7 18:01:38 maryland kernel:     ISA irqs (scanned) = 3,4,5,7,9,10,11,12 status change on irq 11 
Dec  7 18:01:37 maryland crond: crond startup succeeded
Dec  7 18:01:37 maryland pcmcia: Starting PCMCIA services:
Dec  7 18:01:37 maryland pcmcia:  modules
Dec  7 18:01:39 maryland kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Dec  7 18:01:39 maryland kernel: cs: IO port probe 0x0100-0x04ff: clean. 
Dec  7 18:01:39 maryland kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Dec  7 18:01:38 maryland pcmcia:  cardmgr.
Dec  7 18:01:38 maryland cardmgr[345]: starting, version is 3.1.0
Dec  7 18:01:39 maryland cardmgr[345]: watching 2 sockets
Dec  7 18:01:39 maryland rc: Starting pcmcia succeeded
Dec  7 18:01:40 maryland inet: inetd startup succeeded
Dec  7 18:01:40 maryland lpd: lpd startup succeeded
Dec  7 18:01:40 maryland keytable: Loading keymap: 
Dec  7 18:01:41 maryland keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/us.kmap.gz
Dec  7 18:01:42 maryland keytable: Loading system font: 
Dec  7 18:01:42 maryland rc: Starting keytable succeeded
Dec  7 18:01:43 maryland sendmail: sendmail startup succeeded
Dec  7 18:01:44 maryland gpm: gpm startup succeeded
Dec  7 18:01:44 maryland sound: Starting sound configuration: 
Dec  7 18:01:44 maryland sound: sound
Dec  7 18:01:44 maryland sound: 
Dec  7 18:01:44 maryland rc: Starting sound succeeded
Dec  7 18:01:45 maryland PAM_pwdb[450]: (su) session opened for user xfs by (uid=100)
Dec  7 18:01:47 maryland PAM_pwdb[450]: (su) session closed for user xfs
Dec  7 18:01:47 maryland xfs: xfs startup succeeded
Dec  7 18:01:47 maryland linuxconf: Linuxconf final setup
Dec  7 18:01:50 maryland rc: Starting linuxconf succeeded
Dec  7 18:01:50 maryland rc: Starting local succeeded
Dec  7 18:02:10 maryland PAM_pwdb[494]: (kde) session opened for user root by (uid=0)
Dec  7 18:02:41 maryland modprobe: can't locate module sound-slot-0
Dec  7 18:02:43 maryland modprobe: can't locate module sound-service-0-3
Dec  7 18:03:47 maryland cardmgr[345]: initializing socket 1
Dec  7 18:03:48 maryland kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Dec  7 18:03:47 maryland cardmgr[345]: socket 1: 3Com 3c562/3c563 Ethernet/Modem
Dec  7 18:03:48 maryland cardmgr[345]: executing: 'insmod /lib/modules/2.2.13-7mdk/pcmcia/3c589_cs.o'
Dec  7 18:03:48 maryland cardmgr[345]: executing: 'insmod /lib/modules/2.2.13-7mdk/pcmcia/serial_cs.o'
Dec  7 18:03:48 maryland kernel: eth0: 3Com 3c562, io 0x300, irq 3, hw_addr 00:60:97:EF:E1:E1 
Dec  7 18:03:48 maryland kernel:   8K FIFO split 5:3 Rx:Tx, auto xcvr 
Dec  7 18:03:48 maryland kernel: tty02 at 0x03e8 (irq = 3) is a 16550A 
Dec  7 18:03:48 maryland cardmgr[345]: executing: './network start eth0'
Dec  7 18:03:50 maryland cardmgr[345]: + route: netmask doesn't match route address
Dec  7 18:03:50 maryland cardmgr[345]: + Usage: route [-nNvee] [-FC] [<AF>]           List kernel routing tables
Dec  7 18:03:50 maryland cardmgr[345]: +        route [-v] [-FC] {add|del|flush} ...  Modify routing table for AF.
Dec  7 18:03:50 maryland cardmgr[345]: + 
Dec  7 18:03:50 maryland cardmgr[345]: +        route {-h|--help} [<AF>]              Detailed usage syntax for specified AF.
Dec  7 18:03:50 maryland cardmgr[345]: +        route {-V|--version}                  Display version/author and exit.
Dec  7 18:03:50 maryland cardmgr[345]: + 
Dec  7 18:03:50 maryland cardmgr[345]: +         -v, --verbose            be verbose
Dec  7 18:03:50 maryland cardmgr[345]: +         -n, --numeric            dont resolve names
Dec  7 18:03:50 maryland cardmgr[345]: +         -N, --symbolic           resolve hardware names
Dec  7 18:03:50 maryland cardmgr[345]: +         -e, --extend             display other/more information
Dec  7 18:03:50 maryland cardmgr[345]: +         -F, --fib                display Forwarding Information Base (default)
Dec  7 18:03:50 maryland cardmgr[345]: +         -C, --cache              display routing cache instead of FIB
Dec  7 18:03:50 maryland cardmgr[345]: + 
Dec  7 18:03:50 maryland cardmgr[345]: +   <AF>=Use '-A <af>' or '--<af>' Default: inet
Dec  7 18:03:50 maryland cardmgr[345]: +   List of possible address families (which support routing):
Dec  7 18:03:50 maryland cardmgr[345]: +     inet (DARPA Internet) ax25 (AMPR AX.25) netrom (AMPR NET/ROM) 
Dec  7 18:03:50 maryland cardmgr[345]: +     ipx (Novell IPX) ddp (Appletalk DDP) 
Dec  7 18:03:51 maryland cardmgr[345]: executing: './serial start ttyS2'
Dec  7 18:03:51 maryland kernel: eth0: flipped to 10baseT 
====================== Inserting 3COM EtherLink III card ===========================
Dec  8 12:10:33 maryland cardmgr[345]: initializing socket 1
Dec  8 12:10:33 maryland cardmgr[345]: socket 1: 3Com 3c562/3c563 Ethernet/Modem
Dec  8 12:10:33 maryland cardmgr[345]: executing: 'insmod /lib/modules/2.2.13-7mdk/pcmcia/3c589_cs.o'
Dec  8 12:10:33 maryland cardmgr[345]: executing: 'insmod /lib/modules/2.2.13-7mdk/pcmcia/serial_cs.o'
Dec  8 12:10:33 maryland kernel: eth0: 3Com 3c562, io 0x300, irq 3, hw_addr 00:60:97:EF:E1:E1 
Dec  8 12:10:33 maryland kernel:   8K FIFO split 5:3 Rx:Tx, auto xcvr 
Dec  8 12:10:33 maryland kernel: tty02 at 0x03e8 (irq = 3) is a 16550A 
Dec  8 12:10:33 maryland cardmgr[345]: executing: './network start eth0'
Dec  8 12:10:34 maryland cardmgr[345]: + route: netmask doesn't match route address
Dec  8 12:10:34 maryland cardmgr[345]: + Usage: route [-nNvee] [-FC] [<AF>]           List kernel routing tables
Dec  8 12:10:34 maryland cardmgr[345]: +        route [-v] [-FC] {add|del|flush} ...  Modify routing table for AF.
Dec  8 12:10:34 maryland cardmgr[345]: + 
Dec  8 12:10:34 maryland cardmgr[345]: +        route {-h|--help} [<AF>]              Detailed usage syntax for specified AF.
Dec  8 12:10:34 maryland cardmgr[345]: +        route {-V|--version}                  Display version/author and exit.
Dec  8 12:10:34 maryland cardmgr[345]: + 
Dec  8 12:10:34 maryland cardmgr[345]: +         -v, --verbose            be verbose
Dec  8 12:10:34 maryland cardmgr[345]: +         -n, --numeric            dont resolve names
Dec  8 12:10:34 maryland cardmgr[345]: +         -N, --symbolic           resolve hardware names
Dec  8 12:10:34 maryland cardmgr[345]: +         -e, --extend             display other/more information
Dec  8 12:10:34 maryland cardmgr[345]: +         -F, --fib                display Forwarding Information Base (default)
Dec  8 12:10:34 maryland cardmgr[345]: +         -C, --cache              display routing cache instead of FIB
Dec  8 12:10:34 maryland cardmgr[345]: + 
Dec  8 12:10:34 maryland cardmgr[345]: +   <AF>=Use '-A <af>' or '--<af>' Default: inet
Dec  8 12:10:34 maryland cardmgr[345]: +   List of possible address families (which support routing):
Dec  8 12:10:34 maryland cardmgr[345]: +     inet (DARPA Internet) ax25 (AMPR AX.25) netrom (AMPR NET/ROM) 
Dec  8 12:10:34 maryland cardmgr[345]: +     ipx (Novell IPX) ddp (Appletalk DDP) 
Dec  8 12:10:34 maryland cardmgr[345]: executing: './serial start ttyS2'
Dec  8 12:10:35 maryland kernel: eth0: flipped to 10baseT 
====================== Removing 3COM EtherLink III card ===========================
Dec  8 12:11:24 maryland kernel: tty02 unloaded 
Dec  8 12:11:24 maryland cardmgr[345]: shutting down socket 1
Dec  8 12:11:24 maryland cardmgr[345]: executing: './network stop eth0'
Dec  8 12:11:24 maryland cardmgr[345]: executing: './serial stop ttyS2'
Dec  8 12:11:24 maryland cardmgr[345]: executing: 'rmmod 3c589_cs'
Dec  8 12:11:25 maryland cardmgr[345]: executing: 'rmmod serial_cs'
========= Inserting BreezeCom SA-PC (aka Raytheon Raylink) card ===================
Dec  8 12:13:07 maryland cardmgr[345]: initializing socket 1
Dec  8 12:13:07 maryland cardmgr[345]: socket 1: RayLink PC Card WLAN Adapter
Dec  8 12:13:07 maryland cardmgr[345]: executing: 'insmod /lib/modules/2.2.13-7mdk/pcmcia/ray_cs.o bc=1 pc_debug=4 essid=ESSID1 hop_dwell=128 beacon_period=256 translate=1 net_type=1'
Dec  8 12:13:07 maryland kernel:  $Id: ray_cs.c,v 1.67 1999/10/24 15:12:12 corey Exp $ - Corey Thomas corey@world.std.com 
Dec  8 12:13:07 maryland kernel: raylink init_module register_pcmcia_driver returns 0x0 
Dec  8 12:13:07 maryland kernel: ray_attach() 
Dec  8 12:13:07 maryland kernel: ray_attach link = 81a7c800,  dev = 81a7c920,  local = 80bab800, intr = 8284b8ec 
Dec  8 12:13:07 maryland kernel: ray_cs ray_attach calling ether_setup.) 
Dec  8 12:13:07 maryland kernel: ray_cs ray_attach calling CardServices(RegisterClient...) 
Dec  8 12:13:07 maryland kernel: ray_event(0x000004) 
Dec  8 12:13:07 maryland kernel: ray_config entered. 
Dec  8 12:13:07 maryland kernel: ray_config(0x81a7c800) 
Dec  8 12:13:07 maryland kernel: ray_cs Detected: RAYTHEON RayLink PC Card WLAN Adapter Version 4.82 Dec 97 
Dec  8 12:13:07 maryland kernel: sram=800d1000 Set up 32k window for shared memory (transmit and control completed. 
Dec  8 12:13:07 maryland kernel: rmem=800d9000 Set up 16k window for shared memory (receive buffer) completed. 
Dec  8 12:13:07 maryland kernel: amem=800dd000 Set up window for attribute memory completed. 
Dec  8 12:13:07 maryland kernel: ray_config sram=800d1000 
Dec  8 12:13:07 maryland kernel: ray_config rmem=800d9000 
Dec  8 12:13:07 maryland kernel: ray_config amem=800dd000 
Dec  8 12:13:07 maryland kernel: ray_init(0x81a7c920) 
Dec  8 12:13:07 maryland kernel: Unable to handle kernel paging request at virtual address c00d1300 
Dec  8 12:13:07 maryland kernel: current->tss.cr3 = 01a97000, %cr3 = 01a97000 
Dec  8 12:13:07 maryland kernel: *pde = 00000000 
Dec  8 12:13:07 maryland kernel: Oops: 0000 
Dec  8 12:13:07 maryland kernel: CPU:    0 
Dec  8 12:13:08 maryland kernel: EIP:    0010:[<828499bf>] 
Dec  8 12:13:08 maryland kernel: EFLAGS: 00010286 
Dec  8 12:13:08 maryland kernel: eax: 00000001   ebx: 80bab800   ecx: 00000008   edx: 00000000 
Dec  8 12:13:08 maryland kernel: esi: c00d1300   edi: 80bab8e4   ebp: 80bab800   esp: 81b7f88c 
Dec  8 12:13:08 maryland kernel: ds: 0018   es: 0018   ss: 0018 
Dec  8 12:13:08 maryland kernel: Process cardmgr (pid: 345, process nr: 16, stackpage=81b7f000) 
Dec  8 12:13:08 maryland kernel: Stack: 81b7f8c8 8284983c 81a7c920 81a7c800 00000004 81a7c920 80bab800 8284abff  
Dec  8 12:13:08 maryland kernel:        81b7f8d8 81b7f8d8 81a7c920 00000085 81b7fad8 00000000 81b20000 00000106  
Dec  8 12:13:08 maryland kernel:        000dd000 00001000 000001f4 54594152 4e4f4548 79615220 6b6e694c 20435020  
Dec  8 12:13:08 maryland kernel: Call Trace: [<8284983c>] [<8284abff>] [prune_dcache+0/268] [<8281bc2c>] [<8281ad3d>] [<8281abef>] [<8281d88a>]  
Dec  8 12:13:08 maryland kernel:        [RCSid+23040/23552] [unregister_proc_table+116/136] [unregister_proc_table+100/136] [vsprintf+752/796] [unregister_proc_table+44/136] [printk+293/364] [printk+349/364] [<8284a145>]  
Dec  8 12:13:08 maryland kernel:        [<82824aa0>] [<828198e1>] [<8282bbbf>] [vsprintf+752/796] [<8284b8ec>] [printk+293/364] [<8281ad62>] [<8284dd20>]  
Dec  8 12:13:08 maryland kernel:        [<82849269>] [<82850360>] [<8284a071>] [<8282f390>] [<8282f3b4>] [<8282fb2b>] [alloc_skb+125/240] [sock_def_readable+45/56]  
Dec  8 12:13:08 maryland kernel:        [sock_def_readable+28/56] [unix_stream_sendmsg+632/668] [rw_swap_page_base+844/916] [sock_sendmsg+115/152] [do_munmap+930/1096] [dput+239/348] [pipe_read_release+76/84] [schedule+322/636]  
Dec  8 12:13:08 maryland kernel:        [__fput+74/84] [release+234/276] [fput+23/104] [sys_wait4+621/752] [sys_ioctl+367/396] [common_interrupt+24/32] [system_call+52/64]  
Dec  8 12:13:08 maryland kernel: Code: f3 a5 66 a5 a4 8a 83 e4 00 00 00 3c 80 74 24 25 ff 00 00 00  
========= Removing BreezeCom SA-PC (aka Raytheon Raylink) card ===================
SYSTEM HANGS!!!

6) Contents of /proc/modules
> more /proc/modules
ray_cs                 30064   0 (unused)
sound                  65240   0 (autoclean) (unused)
soundcore               3748   3 (autoclean) [sound]
soundlow                 304   0 (autoclean) [sound]
ds                      6056   1 [ray_cs]
i82365                 28808   2
pcmcia_core            51904   0 [ray_cs ds i82365]
vfat                   11036   0 (unused)
fat                    32960   0 [vfat]

7) Contents of /proc/bus/pccard Files
> more /proc/bus/pccard/*/exca
::::::::::::::
/proc/bus/pccard/00/exca
::::::::::::::
83 b2 40 40 00 b8 00 00 00 00 01 00 00 00 01 00
00 00 00 00 00 00 00 0f 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
::::::::::::::
/proc/bus/pccard/01/exca
::::::::::::::
83 ef d0 63 00 b8 0f 00 00 00 01 00 00 00 01 00
d0 00 d0 80 30 7f 00 0f d1 00 d8 c0 2f 3f 00 00
d9 00 dc c0 2f 3f 00 00 dd 00 dd c0 23 7f 00 00
00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00

> more /proc/bus/pccard/ioport
0000-000f : pnp 02
0020-0021 : pnp 03
0024-0025 : pnp 0a
002e-002f : pnp 0a
0040-0043 : pnp 04
0060-0060 : pnp 07
0061-0061 : pnp 05
0064-0064 : pnp 07
0070-0071 : pnp 09
0080-0080 : pnp 0a
0081-0083 : pnp 02
0084-0086 : pnp 0a
0087-0087 : pnp 02
0088-0088 : pnp 0a
0089-008b : pnp 02
008c-008e : pnp 0a
008f-008f : pnp 02
00a0-00a1 : pnp 03
00b0-00b2 : pnp 0a
00c0-00df : pnp 02
00e0-00ef : pnp 0a
00f0-00ff : pnp 06
0120-0127 : pnp 17
0170-0177 : pnp 0d
01f0-01f7 : pnp 0c
0220-022f : pnp 16
02f8-02ff : pnp 15
0376-0377 : pnp 0d
0378-037a : pnp 10
0388-038b : pnp 16
03e0-03e1 : pnp 14
03f2-03f5 : pnp 0b
03f6-03f6 : pnp 0c
03f7-03f7 : pnp 0b
03f8-03ff : pnp 0e
0480-048f : pnp 0a
04d0-04d1 : pnp 0a
0534-0537 : pnp 16
0778-077a : pnp 10
0cf8-0cff : pnp 0a
1882-1885 : pnp 0a
1888-188d : pnp 0a

> more /proc/bus/pccard/irq
  0:  pnp 04
  1:  pnp 07
  2:  pnp 03
  3:  pnp 15
  4:  pnp 0e
  5:  pnp 16
  6:  pnp 0b
  7:  pnp 10
  8:  pnp 09
 12:  pnp 08
 13:  pnp 06
 14:  pnp 0c
 15:  pnp 0d

> more /proc/bus/pccard/memory
00000000-0009ffff : pnp 01
000d0000-000d0fff : card services
000d1000-000d8fff : ray_cs
000d9000-000dcfff : ray_cs
000dd000-000ddfff : ray_cs
000f0000-000fffff : pnp 01
00100000-0201ffff : pnp 01
fe000000-feffffff : pci 00:04.0
fff00000-ffffffff : pnp 01

Next-in-Thread Next Message

Select this message: BreezeCom/Raylink PCMCIA Does Not Configure on Toshiba Tecra

Messages Inline: 1 All Outline: 1 2 All

1. None Maybe a subtle kernel/module mismatch? by David Hinds, 1999, Dec 10
(_ Question Configures but Cannot Contact by John Turkovich, 1999, Dec 17
(_ None You'll probably need to talk to the ray_cs guy by David Hinds, 1999, Dec 17

Message Administration

This form allows you to delete, move, or copy one or more messages. You can move messages by copying and deleting the original. The action will be applied to the messages you select above and all replies to those selected messages.


If you want to copy or move messages, specify the HyperNews path of a destination forum or message that all messages will be copied or moved to. The destination must already exist, so maybe create it first.

Path of Destination (a Forum or Message): (e.g. "test")

Notify Subscribers at destination
NO


If you want to delete messages (the default), specify that here. If you want to move messages, you need to delete the original messages; placeholders will be left pointing to where they were moved.

Delete Messages
NO


Caution: After deleteing messages (the default), if you have not copied them (i.e. no destination above), then the selected messages are not be recoverable.

Members Subscribe No Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10
[ Edit This Forum ]