On Sat, 20 Mar 2004, PHPTOm wrote: [Snip Tale of Woe upgrading 2.2-2.4] > > Is upgrading the kernel in this fashion just a bad idea? > It does sometime get more difficult than it needs to be. On Debian I try to use the official bug tracking and reporting system at www.debian.org when I run into problems like this, but sometimes drastic measures are called for. You might need to upgrade quite a few packages to catch things up with your new libc version but dselect+apt should resolve those out with minimal fuss. Just do Upgrade,Select- just hit enter to get out of select once you have the list up, it will resolve the dependencies, offering you choices when there are multiple ways to go. Then Install. Everything should go smoothly from there. <drastic_measures> First off, if you can, work from your functional 2.2.20 kernel while getting the 2.4 kernel working. It will save a lot of heartburn. Second, try creating local packages using the kernel and pcmcia support source packages with make-kpkg. I use this to work around a buggy motherboard bios at home that I should really just fix. Local packages with make-kpkg will allow you have a fully customized kernel optimized for your system, with just the stuff you want. More importantly for your system, the dependency versions are _what_you_have_installed_! rather than What the package maintainer was running. Last of all, use grub. grub-install once, and update-grub when you add a new kernel to the system. Keep a grub floppy handy. A bag of grubs to snack on. Um, well, maybe that last would be going too far, but grub kicks lilo's gerentological hienie 3 times around the block. Yeah, it is a steep learning curve, welcome to computer hot-rodding. </drastic_measures> -- Daniel Taylor random at argle.org Forget diamonds, Copyright is forever. _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list