|
Hi Folks,
I got a strange effect. Setup is RedHat 6.2, Tosiba Portege 7200CT. Other PCMCIA devices work well (CD ROM, Xircom Network etc). I'm trying to get a Fritz Card PCMCIA ISDN Adapter (also known as AVM A1 PCMCIA) to work with my kernel. If you read the docs in the kernel and on www.isdn4linux.de, this card is fully supported. If I read the docs in pcmcia_cs, this card is not mentioned. The card is a passive ISDN card so it doesnt fit into the section "Modem cards which have their own UART". So there are differentiating statements. The german Suse distribution comes with the device listed in /etc/pcmcia/config. I copied that into my RedHat config file and adopted the modules accordingly. All modules load properly so that part works for shure. Anyway, the situation I have now is if you insert the card you get a high beep followed by a low beep. The correct ISDN drivers are ready to be installed and get loaded properly at the insertion. However I get this message in syslog:
Aug 19 01:58:04 florida kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x37f 0x4d0-0x4d7 Aug 19 01:58:04 florida kernel: cs: IO port probe 0x0a00-0x0aff: clean. Aug 19 01:58:08 florida cardmgr[690]: initializing socket 0 Aug 19 01:58:08 florida kernel: cs: memory probe 0x0d0000-0x0dffff: clean. Aug 19 01:58:08 florida cardmgr[690]: socket 0: AVM ISDN-Controller A1 Aug 19 01:58:08 florida cardmgr[690]: product info: "AVM", "ISDN A" Aug 19 01:58:08 florida cardmgr[690]: function: 6 (network)u Aug 19 01:58:09 florida cardmgr[690]: get dev info on socket 0 failed: Resource temporarily unavailable It seems to be that this last line is the killer. What I see off /proc is that the card has an IRQ but the io ports dont get assigned somehow. Under Windows the card gets either 0x1000 or 0x1400 (or maybe it was 0x100 and 0x140). Both areas are valid in the config. I tried various IRQ's with no difference. The BIOS of the Toshiba is set to CardBus 16. That works best and I dont have any problem with any other card. I tried the latest kernel 2.4.0test4 with the lates PCMCIA_CS tools downloaded today and I get the same results whatsoever. Anyone having any clue how to track this problem down to the source? Andreas Fink
|
Messages