From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264813AbUEEV7I (ORCPT ); Wed, 5 May 2004 17:59:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264814AbUEEV7I (ORCPT ); Wed, 5 May 2004 17:59:08 -0400 Received: from dns1.vanja.com ([207.44.194.94]:56962 "EHLO dns1.vanja.com") by vger.kernel.org with ESMTP id S264813AbUEEV7A (ORCPT ); Wed, 5 May 2004 17:59:00 -0400 Date: Wed, 5 May 2004 23:58:41 +0200 From: Vanja Hrustic To: linux-kernel@vger.kernel.org Subject: "PCI: Unable to reserve mem region" problem Message-Id: <20040505235841.3b89e1d3.vanja@pobox.com> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I have PCI-PCMCIA adapter (Ricoh RL5C475 based) in a desktop machine. Initially, I had problems making it work, but managed to get help on comp.os.linux.portable. Now, most of the cards work okay. However, I still have one wireless PCMCIA card (Prism GT based) which doesn't work, and was advised to post the problem here. I have noticed that quite few other people (on prism54 mailing list, for example) have similar/same problems, and noone could find a solution. Dave (from comp.os.linux.portable) said: "This part is a tricky one. It is a bug in the kernel's PCI resource allocation code. It tries to allocate CardBus memory resources from whatever memory ranges happened to be allocated for the bridge device by the BIOS at power-up time; but in this case, those memory windows are too small. There isn't a simple fix for this and I don't have a good suggestion for what to do about it; you can report it on the linux-kernel mailing list." cardmgr starts okay, and when I insert the card, I get: Apr 23 16:16:52 amber cardmgr[7537]: watching 1 socket Apr 23 18:16:52 amber kernel: cs: IO port probe 0xc000-0xcfff: clean. Apr 23 18:16:58 amber kernel: cs: cb_alloc(bus 2): vendor 0x1260, device 0x3890 Apr 23 18:16:58 amber kernel: PCI: Failed to allocate resource 0(e2006000-e2004fff) for 02:00.0 Apr 23 18:16:58 amber kernel: PCI: Enabling device 02:00.0 (0000 -> 0002) Apr 23 16:16:58 amber cardmgr[7538]: socket 0: CardBus hotplug device Apr 23 18:16:58 amber /etc/hotplug/pci.agent: Setup prism54 for PCI slot 02:00.0 Apr 23 18:16:58 amber kernel: Loaded prism54 driver, version 1.1 Apr 23 18:16:58 amber kernel: PCI: Unable to reserve mem region #1:fffff000@e2006000 for device 02:00.0 Apr 23 18:16:58 amber kernel: PCI: Unable to reserve mem region #1:fffff000@e2006000 for device 02:00.0 Apr 23 18:16:58 amber kernel: prism54: pci_request_regions failure (rc=-16) Apr 23 18:16:58 amber insmod: /lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o: init_module: No such device Apr 23 18:16:58 amber insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Apr 23 18:16:58 amber insmod: /lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o: insmod /lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o failed Apr 23 18:16:58 amber insmod: /lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o: insmod prism54 failed Apr 23 18:16:58 amber /etc/hotplug/pci.agent: ... can't load module prism54 Apr 23 18:16:58 amber /etc/hotplug/pci.agent: missing kernel or user mode driver prism54 lspci -vvv shows: ... 01:08.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 80) Subsystem: CARRY Computer ENG. CO Ltd: Unknown device 0101 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- 16bInt- PostWrite+ 16-bit legacy interface ports at 0001 02:00.0 Network controller: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01) Subsystem: Unknown device 17cf:0014 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-