From: Andrea Venturi <a.venturi@nextra.it>
To: linux-kernel@vger.kernel.org
Subject: Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x (also latitude)
Date: Wed, 28 Feb 2001 18:09:05 +0100 [thread overview]
Message-ID: <3A9D30B1.FC629CE1@nextra.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
hi,
sorry to bother you all...
i would like to follow up this thread because, i have too this strange
effect that with kernel 2.4.2 i'm no more able to use the pcmcia
interface (and with 2.2.17 it was ok!).
i tried to make some troubleshooting to the best of my knowledge but i
lost myself when, last email, Jeff Lessem ended saying that, just using
lilo (and not grub) the problem went away.. but is he still speaking of
the pcmcia problem?
i am using:
- a dell latitude cpx h450 (bios a07)
- 256 MB of ram
- lilo (without any mem append option)
- with 2.2.17 pcmcia is working well
- with 2.4.2 and external pcmcia-cs 3.1.24 no (i have never been able to
load the i82365.o module)
you can find in attach my dmesg and the output of "lspci -vvxxx -s03:00"
that are my pci entries of the pcmcia adapter (hope not to be a mistake
posting a couple of small bin attach) and the relevant message is:
Intel PCIC probe: PCI: Enabling device 00:03.0 (0000 -> 0002)
PCI: Found IRQ 11 for device 00:03.0
PCI: The same IRQ used for device 00:03.1
PCI: The same IRQ used for device 00:07.2
Bridge register mapping failed: check cb_mem_base setting not found.
....
i tried to add the cb_mem_base parameter loading pcmcia_core but in the
pci_fixup.c source is commented out when you use a >= 2.3.24 kernel, so
this line fails:
insmod pcmcia_core cb_mem_base=0x10000000
could someone kindly shed some light!?
sorry, i'm not subscribed to lkml so, please, cc. to me, otherwise, i
will check the answers on the ml archive.
thank you in advance
andrea venturi
> In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write:
> >
> >Careful, you're overwriting ACPI data now (and using it as normal RAM).
>
> Hmm, I guess that would be bad.
>
> >Can you try one of a) LILO b) a fixed version of grub c) this patch ?
>
> I tried LILO and the problem did indeed go away when using that. I
> guess I'll stick with LILO until Linux or grub (whichever is broken)
> is fixed. There is just something appealing about a proper boot
> console on a PC...
--
andrea venturi - Nextra spa
a.venturi@nextra.it - +390516139246
--
"If a man speaks in the forest and there is no woman to hear him,
is he still wrong?"
[-- Attachment #2: ti1225.txt.bz2 --]
[-- Type: application/octet-stream, Size: 833 bytes --]
[-- Attachment #3: dmesg.txt.bz2 --]
[-- Type: application/octet-stream, Size: 3133 bytes --]
reply other threads:[~2001-02-28 17:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A9D30B1.FC629CE1@nextra.it \
--to=a.venturi@nextra.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox