kernel: prism54: pci_request_regions failure (rc=-16)

Jörg Esser <[email protected]>
Newsgroups gmane.linux.drivers.prism54.user
Message-ID <[email protected]>
Hi list,

I have a EPIA -MII Motherboard with a Netgear WG511 running kernel 
2.4.26 and the prism cvs driver.

When the kernel boots I get the following error:
May  3 21:29:16 vdrclient kernel: cs: cb_alloc(bus 2): vendor 0x1260, 
device 0x3890
May  3 21:29:16 vdrclient kernel: PCI: Failed to allocate resource 
0(e6404000-e6404fff) for 02:00.0
May  3 21:29:16 vdrclient kernel: PCI: Enabling device 02:00.0 (0000 -> 
0002)

When I remove the card and reinsert it I get the following output:
May  3 21:30:49 vdrclient kernel: cs: cb_free(bus 2)
May  3 21:30:53 vdrclient kernel: cs: cb_alloc(bus 2): vendor 0x1260, 
device 0x3890
May  3 21:30:53 vdrclient kernel: PCI: Failed to allocate resource 
0(e6404000-e6404fff) for 02:00.0
May  3 21:30:53 vdrclient kernel: PCI: Enabling device 02:00.0 (0000 -> 
0002)
May  3 21:30:53 vdrclient cardmgr[308]: socket 0: CardBus hotplug device
May  3 21:30:53 vdrclient kernel: Loaded prism54 driver, version 1.1
May  3 21:30:53 vdrclient kernel: prism54: PCI device memory region not 
configured; fix your BIOS or CardBus bridge/drivers
May  3 21:30:54 vdrclient insmod: 
/lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o: 
init_module: No such device
May  3 21:30:54 vdrclient insmod: Hint: insmod errors can be caused by 
incorrect module parameters, including invalid IO or IRQ parameters
May  3 21:30:54 vdrclient insmod: 
/lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o: 
insmod prism54 failed
May  3 21:30:54 vdrclient pci.agent[451]: ... can't load module prism54
May  3 21:30:54 vdrclient pci.agent[451]: missing kernel or user mode 
driver prism54

When I try it the second time I get this:
May  3 21:31:33 vdrclient kernel: cs: cb_free(bus 2)
May  3 21:31:36 vdrclient kernel: cs: cb_alloc(bus 2): vendor 0x1260, 
device 0x3890
May  3 21:31:36 vdrclient kernel: PCI: Failed to allocate resource 
0(e6406000-e6404fff) for 02:00.0
May  3 21:31:36 vdrclient kernel: PCI: Enabling device 02:00.0 (0000 -> 
0002)
May  3 21:31:36 vdrclient cardmgr[308]: socket 0: CardBus hotplug device
May  3 21:31:37 vdrclient kernel: Loaded prism54 driver, version 1.1
May  3 21:31:37 vdrclient kernel: PCI: Unable to reserve mem region 
#1:fffff000@e6406000 for device 02:00.0
May  3 21:31:37 vdrclient kernel: PCI: Unable to reserve mem region 
#1:fffff000@e6406000 for device 02:00.0
May  3 21:31:37 vdrclient kernel: prism54: pci_request_regions failure 
(rc=-16)
May  3 21:31:37 vdrclient insmod: 
/lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o: 
init_module: No such device
May  3 21:31:37 vdrclient insmod: Hint: insmod errors can be caused by 
incorrect module parameters, including invalid IO or IRQ parameters
May  3 21:31:37 vdrclient insmod: 
/lib/modules/2.4.26/kernel/drivers/net/wireless/prism54/prism54.o: 
insmod prism54 failed
May  3 21:31:37 vdrclient pci.agent[483]: ... can't load module prism54
May  3 21:31:37 vdrclient pci.agent[483]: missing kernel or user mode 
driver prism54

The lspci output:

lspci -vvv -s 02:00.0
02:00.0 Network controller: Harris Semiconductor: Unknown device 3890 
(rev 01)
        Subsystem: Netgear: Unknown device 4800
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 12
        Region 0: [virtual] Memory at e6406000 (32-bit, non-prefetchable)
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME+



So now my question is what means:

PCI device memory region not configured; fix your BIOS or CardBus 
bridge/drivers


And how can I solve this ?



Thx,


Joerg Esser
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.