[6473] in RedHat Linux List
Re: Help with PCMCIA please
daemon@ATHENA.MIT.EDU (Edward C. Bailey)
Wed Nov 27 14:49:36 1996
Date: Wed, 27 Nov 1996 14:47:44 -0500
From: "Edward C. Bailey" <ed@pigdog.niehs.nih.gov>
To: Roef Ragas ~ NL <rragas@xs4all.nl>
Cc: redhat-list@redhat.com
Reply-to: bailey@niehs.nih.gov
Resent-From: redhat-list@redhat.com
">" Roef Ragas <rragas@xs4all.nl> writes:
> I am running RedHat 4.0 (Colgate) on a Thinkpad 365 ED, and the PCMCIA card
> I'm trying to use is a Psion Dacom V34 Gold Card Modem.
This shouldn't be a problem, unless you've rebuilt your kernel...
> According to the PCMCIA-HOWO, I did everything right, but still everything
> goes wrong. Here's my problem:
> (1) Compiled the Kernel: networking enabled, module version checking
> enabled, PCMCIA IDE device enabled.
Ah, you *did* rebuild your kernel...
> (2) After making the zImage, I did a make dep ; make clean, make modules,
> and make modules_install
Ok...
> (3) Running the new compiled Kernel, I get loads of trash scrolling over my
> screen:
> -unresolved symbols in modules ...
> -insmod: loading failed! the module symbols (version 2.0.18) don't match
> your kernel (2.0.18).
This is understandable...
> What did I do wrong?
> Are there any files in /etc/rc.d I have to adjust? If so, how?
> Is there a order in the things-to-do? I mean: first you compile a new
> kernel, make & install your modules, should that be enough?
It is enough, unless you need pcmcia support. Since you need pcmcia
support, you'll need to do a bit more work...
> I now downloaded modules-2.0.0 & pcmcia-cs-2.8.23, but that didn't do me any
> good either.
It's a little tricky, but here goes:
First, you need the PCMCIA Card Services software. I got mine
(pcmcia-cs-2.8.22) by installing the kernel-sources source RPM, which
leaves a compressed tar file in /usr/src/redhat/SOURCES. You can also ftp
the pcmcia-cs-xxxxx tar file from your favorite FTP site. Either approach
will work as well.
Here's what I did to get PCMCIA support working with my custom-built
kernel:
o I first untar'ed the Card Services sources into /usr/src.
o I then poked through the kernel-sources spec file
(/usr/src/redhat/SPECS/kernel-sources-xxx.spec), and did the
configuration steps by hand. This essentially amounted to creating
two symlinks in each directory in the pcmcia-cs build tree:
kernel-source: which points to the top of the kernel source tree
(/usr/src/linux-2.0.18, in my case).
install-dir: which points to a directory of your choosing where the
pcmcia-cs stuff will install itself. I created the
directory /usr/src/install-dir, and pointed the
symlinks there...
In retrospect, these steps might not be necessary, but I haven't had
the time or inclination to rip them out, and give make the full
path. There were a few patches that were part of the kernel-sources
SRPM, but I didn't bother with those...
o Then, whenever I needed to hack my kernel, I followed these steps:
1. Configure the kernel according to my latest whim :-)
2. Build the kernel (make dep ; make clean ; make zImage: hey, call
me old-fashioned :-)
3. Build the kernel modules (make modules)
4. cd into the pcmcia-cs directory, do a make config. Tell it to
use the kernel source tree to figure things out.
5. Do a make (or a make all -- It's been a month since I've done
this)
6. Do a make install. I think you might have to tell it where to
install. Point it at the install-dir symlink. The pcmcia stuff
will be installed in directory the install-dir symlink points
to.
7. cd to /lib/modules. Move your current module directory
(called 2.0.18 on my system) into something like "2.0.18-old".
This way you can recover if your build is messed up.
8. cd to /usr/src/linux. Do a make modules_install
9. save a copy of your current kernel (you *do* have a lilo entry
to boot from an old kernel, don't you?), and move the new one in
place. Run lilo.
10. Go into the pcmcia install directory. You'll find a number of
directories. Move files under lib/modules/2.0.18(or whatever) into
the proper place in /lib/modules/2.0.18(or whatever). I also move
the files in sbin, though I don't know if that's necessary or not.
11. Reboot. Enjoy your new kernel, and you happily beeping cardmgr,
all at the same time! :-)
It isn't the most elegant method, but it does work...
Hope this helps,
Ed
--
Ed Bailey, Information Systems and Networks
(contracted to: National Institute of Environmental Health Sciences)
2327 Englert Drive.
Suite 200
Durham, NC 27713
Internet: bailey@niehs.nih.gov
BITnet: BAILEY@NIEHS.BITNET
Voice: (919)361-9422, extension 239
FAX: (919)544-6642
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
