"Jeffrey Knight" <[EMAIL PROTECTED]> writes: | Hello all: Hi.
First, if you're going to reply to a message to create a new message on the list please also remove the "References:" header from your new message. Doing it the way you did doesn't play nice with threading news readers. To me your post looked like a reply in the rather long "hello?" thread instead of a brand new subject. | Please forgive the fact this question has probably been asked here | about 100 times: | My tecra laptop is currently running 2.0.x and i'm upgrading to 2.2.x I | finally managed to build a kernel that'll boot (why is it so hard with | debian? i can build bzImages for my tecra with SuSE all day!) ... What caused you so much trouble? It's probably just a process you have to get used to. I can't remember the last time I built a kernel that wouldn't boot. | Where do I have to option to compile in pcmcia? pcmcia is a separate package that you'll need to download and compile. Just install the pcmcia-source package. It'll create the file /usr/src/pcmcia-cs.tar.gz. Unpack it in the /usr/src directory via "tar xzf pcmcia-cs.tar.gz". If you're using the kernel-package package, as you should be, and you built your kernel with it then you simply change to the kernel source directory and do: make-kpkg modules and you'll get a pcmcia-modules-*.deb file in /usr/src that you can install via dpkg -i. | I tried to just copy /lib/modules/2.0/pcmcia to /lib/modules/2.2, but the | bootup process didn't think that that was very funny. You can generally do this if you didn't compile with MODVERSION within the same kernel level, eg., 2.2.14 modules will often work fine with a 2.2.15 kernel, but I think 2.0.x modules in a 2.2.x kernel is pushing it. I generally recompile pcmcia every time I do a kernel upgrade though, just to be on the safe side. Good luck, Gary
