Next-in-Thread Next Message

Question it now works 

Forum: PCMCIA driver development
Re: Sad system hang upon pcmcia subsystem start (Tonko de Rooy)
Re: None Re: Sad: system hang upon pcmcia subsystem start (David Hinds)
Date: 2000, Jun 04
From: Tonko de Rooy tderooy


For some strange reason it now works. I recompiled the 2.2.16pre6 kernel and pcmcia 3.1.15 and it all loads and works again perfectly.

here is what gets printed now to syslog:

Linux PCMCIA Card Services 3.1.15
  kernel build: 2.2.16pre6 #1 Wed May 31 11:33:44 BST 2000
  options:  [pci] [cardbus] [apm] [pnp]
PCI routing table version 1.0 at 0xf9f80
PnP: PNP BIOS installation structure at 0xc00fe700
PnP: PNP BIOS version 1.0, entry at f0000:e724, dseg at f0000
Intel PCIC probe: 
  TI 1251A rev 00 PCI-to-CardBus at slot 00:02, mem 0x50103000
    host opts [0]: [ring] [isa irq] [pci irq 11] [lat 168/176] [bus 2/4]
    host opts [1]: [ring] [isa irq] [pci irq 11] [lat 168/176] [bus 5/7]
    ISA irqs (scanned) = 3,4,9,10 PCI status changes
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff
cs: memory probe 0x60000000-0x60ffffff: clean.

The only thing left is that I get a error when running depmod on epic_cb. Here is what depmod -ae tells me:

depmod: *** Unresolved symbols in /lib/modules/2.2.16pre6/pcmcia/epic_cb.o
depmod:         epic100_probe
But this is a longer standing problem. I always have this problem when I compile my own kernel and modules. And as I have no idea what epic_cb is, I probably don't need it and don't need to worry to much about the error.

Next-in-Thread Next Message

Select this message: it now works

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

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

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 1.10
[ Edit This Forum ]