[ltp] network/pcmcia problems

Robert Farney linux-thinkpad@www.bm-soft.com
Fri, 27 Aug 1999 19:34:04 -0500


Bruce,

      We have installed version 5.2 on our 12 IBM 770X laptops and everthing
works just fine.  From the 327mb Ram to the 10gb HD.  If you want to call me
at my office that would be fine.  I may be able to point out some things to
try.  I am not a linux expert, but we have done the job.  I would be happy
then to tell you what we did....  334-255-2448...... if no one answers keep
calling back.... I am often away from my desk.......


                                                    Bob
----- Original Message -----
From: Bruce Cowan <BRUCECO@Attachmate.com>
To: <linux-thinkpad@www.bm-soft.com>
Cc: <pete@lighthousecs.com>
Sent: Friday, August 27, 1999 1:59 PM
Subject: RE: [ltp] network/pcmcia problems


> Pete,
>
> I can't remember the details right now, but in the Linux PCMCIA package
doc
> there is a comment about memory conflicts and moving the memory window to
> a different place. My somewhat faulty memory says look at the config file
> and change the "c" in the high memory window to a "6" and everything will
> work. At least that was the change required to get things working on my
> TP770X.
>
> Bruce Cowan
>
> -----Original Message-----
> From: pete@lighthousecs.com [mailto:pete@lighthousecs.com]
>
> I am having a significant number of problems getting pcmcia networking up
on
> my TP770X. I have been trying different things for months it seems . . .
all
> to (as of this point in time) no avail.
>
> I have the IBM EtherJet card (32bit) and I noticed that the new pcmcia
> package (3.0.14) includes a driver for it.  I complied the package and now
> 'cardctl ident' can see the card. The funny thing is that I still see what
> appear to be errors in the /var/log/messages file:
>
> Aug 27 14:11:44 localhost cardmgr[377]: could not adjust resource: memory
> 0xc0000-0xfffff: Device or resource busy
> Aug 27 14:11:44 localhost cardmgr[377]: initializing socket 1
> Aug 27 14:11:44 localhost cardmgr[377]: unsupported card in socket 1
>
>  . . but then it goes on to identify the card. ???
>