Recent 2.3.* kernels have lots of problems

Forum: PCMCIA on Toshiba laptops
Re: Question: problem with satellite 2540cds ToPIC97 (Stef Epardaud)
Date: 2000, Feb 28
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The PCMCIA drivers in the latest 2.3.* kernels seem to not work for many people, including me. A lot of this code is new and went in over my objections. -- Dave

[ Next-in-Thread ] [ Next Message ]

Messages Inline: [ 0 ] [ 1 ]

when do you think it will be fixed?

Re: Recent 2.3.* kernels have lots of problems (David Hinds)
Date: 2000, Feb 28
From: Stef Epardaud <stef@exes-de-vie>

thanx for your fast answer, i can now relax and stop banging my head on the wall trying to fix this :) one thing i don't understand is how things that worked perfectly were broken, and why. but then it must be because things were maybe not working for all of us, right? anyways, do you have any idea when it will be fixed ? too bad my experience with drivers is non existent, i would have gladly helped :(

Question: When did the Kernels change? Can I revert?

Re: Recent 2.3.* kernels have lots of problems (David Hinds)
Date: 2000, Mar 02
From: Joseph Fannin II trevorcor

Just curious if anyone could tell me when the 2.3 kernels changed; I would like to use the latest kernel that isn't broken. I can't fix this by using Dave Hinds' package, can I? I've tried something like this before, and apparently I have to use the in-kernel drivers rather than the pcmcia-cs package.
pcmcia_core loads fine, but the i82365 bridge module claims that 'device or resource is busy.' The fact that I remember what the bridge is called means I've spent too much time trying to fix this.
Well, at least it isn't pgcs that's screwing things up. Thanks in advance for any help.

Something new to try

Re: Question: When did the Kernels change? Can I revert? (Joseph Fannin II)
Date: 2000, Mar 02
From: David Hinds <dhinds@pcmcia.sourceforge.org>

If you want to try, you can grab the latest PCMCIA beta from sourceforge.org in /pcmcia/NEW, and build a 2.3.* kernel with all PCMCIA stuff turned off... and I think you can then compile all PCMCIA modules from the standalone package. I haven't had a chance to test it yet (beyond verifying that the compile is clean). -- Dave

More: tried it, does not work for me at least

Re: Something new to try (David Hinds)
Date: 2000, Mar 03
From: Stef Epardaud <stef@exes-de-vie>

hi, i tried the latest pcmcia package, and i get: ACPI: "TOSHIB" found at ... ACPI: SCI (IRQ13) allocation failed

ACPI != PCMCIA

Re: More: tried it, does not work for me at least (Stef Epardaud)
Date: 2000, Mar 03
From: David Hinds <dhinds@pcmcia.sourceforge.org>

> ACPI: "TOSHIB" found at ... > ACPI: SCI (IRQ13) allocation failed These messages have absolutely nothing to do with PCMCIA. Do you get any system log messages that mention PCMCIA? -- Dave

More: well that was all i got :(

Re: ACPI != PCMCIA (David Hinds)
Date: 2000, Mar 04
From: Stef Epardaud <stef@exes-de-vie>

ah, ok, sorry :) in fact that aws the closest to what i got usually, i did not get any message mentionning pcmcia at all. but this may be because i compiled the modules appart from the kernel and messed up something as i've never done that before, i'll look more to see. what modules have to be in the kernel to detect pcmcia cards?

Recent 2.3.* kernels have lots of problems

[ Add Message ] to: "Recent 2.3.* kernels have lots of problems"

[ Members ] [ Subscribe ] [ Admin Mode ]
[ Show Frames ] [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]