Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Debian will modify the lilo.conf for you If it gives you any directions on adding a line to it, make sure you write it down. If you dont have an initrd line it will ask you to then add one. If it does, it is importatnt you do or you won't be able to bring the box back up.
initrd is the kernel which is loaded into a ramdisk (ie memory) and then the system boots from this ramdisk. I think I gave the line above. Check your /boot and check the initrd.img it is likely to be initrd.img-2.4.27-1-686 so the line to add to lilo would be;
initrd=/boot/initrd.img-2.4.27-1-686
then from the command line do lilo to write it ro the mbr
The install will configure the old kernel as well to Linux.old so you will still be able to boot the old kernel
hmm... this is a bit disturbing, but i ran modconf and there isn't any PCMCIA package... looked under /kernel/drivers/net, but i think that isn't the place to look, 'cos the drivers there don't seem to be for PCMCIA Ethernet cards...
I just checked a 2.4.25 kernel on my system (I use 2.6.3) and the pcmcia modules are separate in /lib/modules/kernel_version_#. If you know which module you need then check this directory as you can use insmod to install the module. Also check your /var/log/syslog or messages and see what the kernel has done with the ethernet.
There isn't any PCMCIA under /lib/modules/2.4.27-1-686 either.
There are 2 directories (under them, are similar to what i see in modconf):
kernel
init
And there are 8 files:
modules.dep
modules.generic_string
modules.ieee1394map
modules.isapnpmap
modules.parportmap
modules.pcimap
modules.pnpbiosmap
modules.usbmap
There is a pcmcia sub-directory under /lib/modules/2.2.20-idepci (previous kernel), and there is a xirc2ps_cs.o which i think is the driver for my card (i use a Xircom card), but i can't insmod that one (different compiler ver).
You have a couple of options now. You can up and download a 2.6.x kernel-image and install that through dpkg-install or go backward. I have a 2.4.24 kernel with the pcmcia modules.
well i guess before i go to 2.4.24 or 2.6.x, i first have to go all the way back to 2.2.20? 'cos without the PCMCIA support and hence the Ethernet connection, i can't do anything right?
now how do I go back to my previous kernel?
btw, 2.6.x is an unstable release right? is it really *unstable*?
Problem solved. I had a look at the package details for the kernel-image-2.4.27 here and you need to install the pcmcia modules as a package and this should rectify the situation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.