PHARscape

lunixusar · Joined: 28 Aug 2008 Posts: 1

With the 2.1d driver (the only one that seemed to compile without modifications (pci_register_driver, etc) and warnings) I got:

kernel: Initializing Nozomi driver 2.1d (build date: Aug 27 2008 18:10:54)
kernel: nozomi 0000:04:00.0: Card type is: 2048
kernel: PCI: Enabling device 0000:04:00.0 (0000 -> 0002)
kernel: ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 18
kernel: nozomi 0000:04:00.0: Unable to map card MMIO
kernel: ACPI: PCI interrupt for device 0000:04:00.0 disabled

With the 2.21alpha driver (and other more recent) I got:

kernel: Initializing Nozomi driver 2.21alpha (build date: Aug 27 2008 17:13:44)
kernel: Unloading Nozomi drivernozomi 0000:04:00.0: Init, cards_found: 1
kernel: nozomi 0000:04:00.0: Card type is: 2048
kernel: ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 18
kernel: nozomi 0000:04:00.0: No I/O-Address for card detected
kernel: ACPI: PCI interrupt for device 0000:04:00.0 disabled

# pccardctl status
Socket 0:
3.3V 32-bit PC Card

# lspci -v

04:00.0 Network controller: Option N.V. Qualcomm MSM6275 UMTS chip
Flags: medium devsel, IRQ 18
Memory at 124000000 (32-bit, non-prefetchable) [size=2K]
Kernel modules: nozomi

I guess that ^ looks bad..shouldn't there be some "I/O ports at" lines?

# cat /etc/redhat-release
Fedora release 8 (Werewolf)

# uname -r
2.6.23.15-137.fc8

# rpm -qa|grep -ir pcmcia
pcmciautils-014-11.fc8

This seems to be the same problem in both cases. The error message is just different different.

This is where it seems to be failing:

In 2.1d

dc->base_addr = ioremap(start, dc->card_type);
if (!dc->base_addr) {
dev_err(&pdev->dev, "Unable to map card MMIO\n");
ret = -ENODEV;
goto err_rel_regs;
}

In nozomi_2.21alpha_060917

dc->base_addr = (void *)ioremap((int)dc->base_addr, dc->card_type);
if (!dc->base_addr) {
dev_err(&pdev->dev, "No I/O-Address for card detected\n");
ret = -ENODEV;
goto err_disable_device;
}

Anyone have any idea what this could be or possible workarounds...Maybe I can hardcode something? Any other info I can provide to help diagnose this?

Paul · Posted: Wed Sep 24, 2008 9:51 am Post subject:

Hi,

Which device is it and who supplied it? (model number or serial number first 2 letters).

Also - is the slot fully to specification (power)?

Cheers,
Paul