Re: Re-visit: Thinkpad 760el D-Link dfe-690-txd problems
From: Jim (james_at_the-computer-shop.co.uk)
Date: 05/03/05
- Next message: Gary: "Re: Re-visit: Thinkpad 760el D-Link dfe-690-txd problems"
- Previous message: mjt: "Re: SuSE 9.3 Prof. does not recognize harddisk"
- In reply to: dhinds_at_sonic.net: "Re: Re-visit: Thinkpad 760el D-Link dfe-690-txd problems"
- Next in thread: Gary: "Re: Re-visit: Thinkpad 760el D-Link dfe-690-txd problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 03 May 2005 00:43:21 GMT
dhinds@sonic.net wrote:
> Gary <gws1@mtco.com> wrote:
>
>
>>The card gives me a low pitch beep on insertion and a high beep on eject.
>>The manfid is not correct, (0x1186, 0x1340) should be (0x149 ,0x0000) for
>>this card.
>
>
> The reported IDs are PCI IDs, not PCMCIA manfids. The reported IDs
> are correct. The PCMCIA manfids are different.
>
>
>>May 2 11:32:35 loki kernel: cs: could not allocate 4K memory for CardBus
>>socket 0
>
>
> This is your problem. I'm not sure why you're getting this error.
>
> Oh.
>
> Please put back the original, unmodified /etc/pcmcia/config and
> /etc/pcmcia/config.opts files. When you replaced the config file, you
> deleted the "source ./config.opts" line, hence, all your resource
> definitions are being completely ignored.
>
> -- Dave
from the Linux-PCMCIA-Config-HOWTO:
Symptoms:
* When a card is inserted, it is identified correctly but cannot be
configured (high/low beep pattern).
* One of the following messages will appear in the system log:
RequestIO: Resource in use
RequestIRQ: Resource in use
RequestWindow: Resource in use
GetNextTuple: No more items
could not allocate nn IO ports for CardBus socket n
could not allocate nnK memory for CardBus socket n
could not allocate interrupt for CardBus socket n
Interrupt starvation often indicates a problem with the interrupt probe
(see Interrupt scan failures). In some cases, the probe will seem to
work, but only report one or two available interrupts. Check your system
log to see if the scan results look sensible. Disabling the probe and
selecting interrupts manually should help.
If the interrupt probe is not working properly, the socket driver may
allocate an interrupt for monitoring card insertions, even when
interrupts are too scarce for this to be a good idea. You can switch the
controller to polled mode by setting PCIC_OPTS to ``poll_interval=100'.
Or, if you have a CardBus controller and an older version of the PCMCIA
drivers, try ``pci_csc=1'', which selects a PCI interrupt (if available)
for card status changes.
IO port starvation is fairly uncommon, but sometimes happens with cards
that require large, contiguous, aligned regions of IO port space, or
that only recognize a few specific IO port positions. The default IO
port ranges in /etc/pcmcia/config.opts are normally sufficient, but may
be extended. If this is the problem, try uncommenting the ``include port
0x1000-0x17ff'' line in config.opts. In rare cases, starvation may
indicate that the IO port probe failed (see IO port scan failures).
Memory starvation is also uncommon with the default memory window
settings in config.opts. CardBus cards may require larger memory regions
than typical 16-bit cards. Since CardBus memory windows can be mapped
anywhere in the host's PCI address space (rather than just in the
640K-1MB ``hole'' in PC systems), it is helpful to specify large memory
windows in high memory, such as 0xa0000000-0xa0ffffff.
HTH
-- Cheers, Jim -begin sig- Opinions expressed in this message may or may not be representative of the opinions of its author. You decide. Web: http://www.dotware.co.uk http://www.dotware-entertainment.co.uk Portable: P4m 2.0, 1GB, 40GB, MX440/15" XGA@1600x1200, Wi-Fi, GPRS, DVD/CDRW, XPSP2/Knoppix Powerbook G3/400, 392MB, 20GB, Rage 128/15"@1024x768, Wi-Fi, DVD, Mac OS X 10.4 "Tiger" Dev. Build Desktop: AMD64 3200+@2.63GHz, 512MB, 80GB, FX5700LE/32" WXGA@2048x768, DVD+-RW, XPSP1/Debian FileServer: Athlon XP 2400+, 256MB, 2.72TB, Blind, MuLinux More but I'm not tellin' ya, there's a pool forming at your feet. -end sig-
- Next message: Gary: "Re: Re-visit: Thinkpad 760el D-Link dfe-690-txd problems"
- Previous message: mjt: "Re: SuSE 9.3 Prof. does not recognize harddisk"
- In reply to: dhinds_at_sonic.net: "Re: Re-visit: Thinkpad 760el D-Link dfe-690-txd problems"
- Next in thread: Gary: "Re: Re-visit: Thinkpad 760el D-Link dfe-690-txd problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
