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
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
> 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
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
On Sat, Feb 24, 2001 at 10:25:42AM -0700, Jeff Lessem wrote:
> In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write:
> >Jeff, are you using the e820 memory map at all ? In particular, are you
> >using grub or some other buggy bootloader that insists on specifying a
> >mem= option on the
In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write:
>Jeff, are you using the e820 memory map at all ? In particular, are you
>using grub or some other buggy bootloader that insists on specifying a
>mem= option on the kernel command line ? There should be a kernel command
>line message
On Sat, Feb 24, 2001 at 05:36:47AM -0800, Linus Torvalds wrote:
> On Sat, 24 Feb 2001, Jeff Lessem wrote:
> >
> > >Also, how much memory does this machine have? That "13ff" does worry
> > >me a bit..
> >
> > The comptuer has 320MB. At this point I am ready to conclude that the
> > computer
In your message of: Fri, 23 Feb 2001 09:48:04 PST, you write:
>The much more likely cause is the "magic registers" for the Texas
>Instruments PCI1225, namely
>
> works broken
>
> 81: b0 90
> a8: 11 10
>
>Although it worries me
In your message of: Fri, 23 Feb 2001 09:48:04 PST, you write:
The much more likely cause is the "magic registers" for the Texas
Instruments PCI1225, namely
works broken
81: b0 90
a8: 11 10
Although it worries me a bit
On Sat, Feb 24, 2001 at 05:36:47AM -0800, Linus Torvalds wrote:
On Sat, 24 Feb 2001, Jeff Lessem wrote:
Also, how much memory does this machine have? That "13ff" does worry
me a bit..
The comptuer has 320MB. At this point I am ready to conclude that the
computer is broken in
In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write:
Jeff, are you using the e820 memory map at all ? In particular, are you
using grub or some other buggy bootloader that insists on specifying a
mem= option on the kernel command line ? There should be a kernel command
line message
On Sat, Feb 24, 2001 at 10:25:42AM -0700, Jeff Lessem wrote:
In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write:
Jeff, are you using the e820 memory map at all ? In particular, are you
using grub or some other buggy bootloader that insists on specifying a
mem= option on the kernel
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
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
On Thu, 22 Feb 2001, Jeff Lessem wrote:
>
> In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write:
> >Hmm.. You shouldn't be loading any i82365 module at all. You should load
> >the "yenta_socket" module.
>
> I had gone back to my old ways of useing the external PCMCIA stuff.
> Here
On 22 Feb 2001 23:01:14 -0800, Barry K. Nathan wrote:
> Tom Sightler wrote:
> > What's strange is that I have the exact same type of machine and I don't see
> > this problem, could you forward me your kernel config as well? I'll compare
> > that, and your info from your previous message to mine
On Thu, 22 Feb 2001, Jeff Lessem wrote:
In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write:
Hmm.. You shouldn't be loading any i82365 module at all. You should load
the "yenta_socket" module.
I had gone back to my old ways of useing the external PCMCIA stuff.
Here are the
On 22 Feb 2001 23:01:14 -0800, Barry K. Nathan wrote:
Tom Sightler wrote:
What's strange is that I have the exact same type of machine and I don't see
this problem, could you forward me your kernel config as well? I'll compare
that, and your info from your previous message to mine and see
In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write:
>Hmm.. You shouldn't be loading any i82365 module at all. You should load
>the "yenta_socket" module.
I had gone back to my old ways of useing the external PCMCIA stuff.
Here are the relevant lspci --vvxx listings using the yenta
> I took your advice and used the kernel drivers from 2.4.2. I built
> the Cardbus and i82365 drivers into the kernel. This shows the exact
> same behavior, after a power-on reboot I get:
You don't need the i82365 driver, only the Cardbus (yenta) driver. I don't
think this would cause your
On Thu, 22 Feb 2001, Jeff Lessem wrote:
>
> No problem, the listings are below. Both listings were done on a
> freshly booted system. The only difference in system states was that
> the i82365 modules had loaded.
Hmm.. You shouldn't be loading any i82365 module at all. You should load
the
In your message of: Thu, 22 Feb 2001 19:40:03 PST, you write:
>Can you do a full "lspci -vvxxx" (as root) both on a working and a
>non-working setup, and send the two files to the kernel list and cc to
>me?
No problem, the listings are below. Both listings were done on a
freshly booted system.
In your message of: Thu, 22 Feb 2001 15:19:15 EST, you write:
>I'm a little confused by what you mean when you say PCMCIA modules, are you
>referring to the actual PCMCIA socket drivers themselves? If so, perhaps
Yes, the i82365 module does not load.
>this is why you have problems and I don't.
In your message of: Thu, 22 Feb 2001 15:19:15 EST, you write:
I'm a little confused by what you mean when you say PCMCIA modules, are you
referring to the actual PCMCIA socket drivers themselves? If so, perhaps
Yes, the i82365 module does not load.
this is why you have problems and I don't.
In your message of: Thu, 22 Feb 2001 19:40:03 PST, you write:
Can you do a full "lspci -vvxxx" (as root) both on a working and a
non-working setup, and send the two files to the kernel list and cc to
me?
No problem, the listings are below. Both listings were done on a
freshly booted system.
On Thu, 22 Feb 2001, Jeff Lessem wrote:
No problem, the listings are below. Both listings were done on a
freshly booted system. The only difference in system states was that
the i82365 modules had loaded.
Hmm.. You shouldn't be loading any i82365 module at all. You should load
the
I took your advice and used the kernel drivers from 2.4.2. I built
the Cardbus and i82365 drivers into the kernel. This shows the exact
same behavior, after a power-on reboot I get:
You don't need the i82365 driver, only the Cardbus (yenta) driver. I don't
think this would cause your
In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write:
Hmm.. You shouldn't be loading any i82365 module at all. You should load
the "yenta_socket" module.
I had gone back to my old ways of useing the external PCMCIA stuff.
Here are the relevant lspci --vvxx listings using the yenta
I have a Dell Inspiron 5000e which shows some odd behavior related to
the PCI and PCMCIA systems. I believe this problem is related to the
kernel more than the PCMCIA modules, because the "fix" involves
booting the system to 2.2 and then into 2.4. Though I am now using
different PCMCIA versions
I have a Dell Inspiron 5000e which shows some odd behavior related to
the PCI and PCMCIA systems. I believe this problem is related to the
kernel more than the PCMCIA modules, because the "fix" involves
booting the system to 2.2 and then into 2.4. Though I am now using
different PCMCIA versions
30 matches
Mail list logo
