I am running 2.2.13 on an older laptop and I had to recompile pcmcia After
recompiling my kernel. I was getting similar errors to the ones you posted
but once I upgraded to potato and recompiled pcmcia it works now.
JJN
(not as technical as the other answers sorry)
I am running 2.2.13 on an older laptop and I had to recompile pcmcia After
recompiling my kernel. I was getting similar errors to the ones you posted
but once I upgraded to potato and recompiled pcmcia it works now.
JJN
(not as technical as the other answers sorry)
> By the way, how many Debian laptop users are on potato and keep up to date
> with the latest packages?
As of Monday, my lap top is as up to date on potato with kernel 2.2.13 and
lates pcmcia-source package which I think it's 3.1.6
And it's working fine
Chanop
--
,
> By the way, how many Debian laptop users are on potato and keep up to date
> with the latest packages?
As of Monday, my lap top is as up to date on potato with kernel 2.2.13 and
lates pcmcia-source package which I think it's 3.1.6
And it's working fine
Chanop
--
,
Hi Drew,
I am struggling to keep my potato installation up and running on my Sony
VAIO PCG-Z505F (japanese model). Works fine with a 2.3.24 kernel - except
that in half a year I NEVER yet got PCMCIA to work. It is not vital for
me, so I did not pour my best effort into it. I would like to use my
Hi Drew,
I am struggling to keep my potato installation up and running on my Sony
VAIO PCG-Z505F (japanese model). Works fine with a 2.3.24 kernel - except
that in half a year I NEVER yet got PCMCIA to work. It is not vital for
me, so I did not pour my best effort into it. I would like to use my
On Thu, Dec 16, 1999 at 09:31:24AM +0900, M. Miller wrote:
> Hello,
>
> I get those errors at dmesg/bootup whenever i compiled a new kernel but
> didn't compile pcmcia to go with it. You may want to go back into the
> pcmcia sources and type debian/rules build-binary
> that should make a .deb pack
On Thu, Dec 16, 1999 at 09:31:24AM +0900, M. Miller wrote:
> Hello,
>
> I get those errors at dmesg/bootup whenever i compiled a new kernel but
> didn't compile pcmcia to go with it. You may want to go back into the
> pcmcia sources and type debian/rules build-binary
> that should make a .deb pack
On Thu, Dec 16, 1999 at 01:36:10PM +1300, Andrew McMillan wrote:
> Drew Parsons wrote:
> >
> > I have a weird problem compiling the latest pcmcia modules (for pcmcia-cs
> > 3.1.6-1).
>
> I think this happens when the kernel version you have compiled doesn't
> _exactly_ match the pcmcia modules ve
On Thu, Dec 16, 1999 at 01:36:10PM +1300, Andrew McMillan wrote:
> Drew Parsons wrote:
> >
> > I have a weird problem compiling the latest pcmcia modules (for pcmcia-cs
> > 3.1.6-1).
>
> I think this happens when the kernel version you have compiled doesn't
> _exactly_ match the pcmcia modules ve
On Thu, Dec 16, 1999 at 10:26:17AM +0900, [EMAIL PROTECTED] wrote:
> dfparsons> I have a weird problem compiling the latest pcmcia modules
> dfparsons> (for pcmcia-cs 3.1.6-1).
>
> i also had problems compiling the latest modules for 3.1.6-1 -- my
> short-term work around was to say 'yes' to cardb
On Thu, Dec 16, 1999 at 10:26:17AM +0900, [EMAIL PROTECTED] wrote:
> dfparsons> I have a weird problem compiling the latest pcmcia modules
> dfparsons> (for pcmcia-cs 3.1.6-1).
>
> i also had problems compiling the latest modules for 3.1.6-1 -- my
> short-term work around was to say 'yes' to cardb
Hello,
I get those errors at dmesg/bootup whenever i compiled a new kernel but
didn't compile pcmcia to go with it. You may want to go back into the
pcmcia sources and type debian/rules build-binary
that should make a .deb package that is built against your kerneal source
tree..also since its a .d
Hello,
I get those errors at dmesg/bootup whenever i compiled a new kernel but
didn't compile pcmcia to go with it. You may want to go back into the
pcmcia sources and type debian/rules build-binary
that should make a .deb package that is built against your kerneal source
tree..also since its a .d
Drew Parsons wrote:
>
> I have a weird problem compiling the latest pcmcia modules (for pcmcia-cs
> 3.1.6-1).
I think this happens when the kernel version you have compiled doesn't
_exactly_ match the pcmcia modules version. The funny extension names
are there for uniqueness deliberately.
I get
Drew Parsons wrote:
>
> I have a weird problem compiling the latest pcmcia modules (for pcmcia-cs
> 3.1.6-1).
I think this happens when the kernel version you have compiled doesn't
_exactly_ match the pcmcia modules version. The funny extension names
are there for uniqueness deliberately.
I get
I have a weird problem compiling the latest pcmcia modules (for pcmcia-cs
3.1.6-1).
I compiled using make-kpkg modules_image, and the compilation seemed to
proceed correctly. But when I install and run the new version, it
complains that there are "unresolved symbols", as if some functions were
nev
I have a weird problem compiling the latest pcmcia modules (for pcmcia-cs
3.1.6-1).
I compiled using make-kpkg modules_image, and the compilation seemed to
proceed correctly. But when I install and run the new version, it
complains that there are "unresolved symbols", as if some functions were
nev
18 matches
Mail list logo
