Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I recently compiled kernel version 2.4.18. It seemed to compile right, I appended to lilo.conf, and the computer booted mostly fine to the login prompt. Except for the missing modules. Now the question is did the modules get compiled when I issued the command:
make modules && make modules_install
Do I have to go through and find all the modules I used before the new kernel and set them up to be loaded.
--Thanks in advance.
I'm surprised the kernel booted on the first compile
Your command compiles and installs the modules alright, but no one guarantees that you actually enabled all required modules that depend on each other. The "make xconfig" GUI attempts to disable an option when you did not enable a required other driver or some such, or at least give a hint (example: unless you enable SCSI support, you can't enable "USB mass storage support" in the USB section). But it's not comprehensive, and you may get missing modules. My users once had a problem that the ATA drivers were silently not enabled in a config file that someone had distributed, and so no one would get the kernel to boot.
It's also possible that you lack some alias settings in /etc/modules.conf.
and capture the error messages, if any. That will give you a hint what's wrong. If you get stuck, post the output and we'll see.
Well, it's hard to tell - why don't you post a list of the modules that give you an error at bootup. Anything to do with sound, network card, USB, parport, some char-major blurf?
There may be something when you type dmesg, or in /var/log/messages.
But there is a generic way to get the kernel configured as it was before. If you have configured another kernel previously, go to that /ur/src/linux-XXX directory and copy .config to /usr/src/linux (where your new kernel sources live). Then make any of make oldconfig, make config, or (as I do since I always want to inspect it) make xconfig, save, and
make dep clean bzImage modules modules_instal.l
That config file can also come from a kernel rpm from redhat if it's your initial installation, but since the redhat kernel must cover so much variety, it's usually too broad. I haven't done this in a long time - the config evolved from version to version.
Hope it helps. You shouldn't have any error messages at bootup. Looks bad.
I see your problem on the other thread - you need X for "make xconfig". You won't be able to make progress until you manage to configure the kernel properly - if you are in just text mode, make config gives you a somewhat less elegant text-based way of doing it. Is that the problem you're having with make xconfig?
So why don't you simply add all the stuff that your system wants from the kernel - devpts, the usb/uhci stuff, and you will be in business.
If you strictly make new modules [ of a subsystem that was already activated], you can just make modules modules_install.
depmod -a after that, and modprobe the new modules. Or reboot. You don't need to make the whole kernel new.
The caveat with "of a subsystem that was already activated" means that you can add, say, a new sound card driver this way, but not if sound support wasn't enabled in the first place already. In the same way you can add USB capabilities as long as USB was enabled in general. It's not a strict rule, but it usually works.
Here's mine -- that's the whole USB section -remember, I have stuff different from you, a Sharp Zaurus, an IBMCam, a Canon dig. camera, , a USB mouse, all things USB. But if you paste that in, you build some more stuff than you need but so what.
# USB support
# Miscellaneous USB options
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_LONG_TIMEOUT is not set
# USB Controllers
# CONFIG_USB_UHCI_ALT is not set
# CONFIG_USB_OHCI is not set
# USB Device Class drivers
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# USB Human Interface Devices (HID)
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_WACOM is not set
# USB Imaging devices
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
# USB Multimedia devices
# CONFIG_USB_OV511 is not set
# CONFIG_USB_PWC is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_DABUSB is not set
# USB Network adaptors
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER is not set
# CONFIG_USB_USBNET is not set
# USB port drivers
# USB Serial Converter support
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
The devpts, here's my line:
That should get you going. Remember that just editing the .config file is NOT enough. You must still make config ( or oldconfig or what).
OK, I built in USB support instead of a module. I believe I added devfs support, but I don't know. After doing a make xconfig (yeah! X works) and added a a bunch of options having to do with DEVFS. I looked at my .config file and couldn't find a line having to do with CONFIG_DEVPTS_FS. So I don't know.
Another question, When I tried to do a sndconfig, I got an error message saying I don't have modular sound support (soundcore.o) where do I activate that module when I'm xconfig'ing.
OK. the USB problem was resolved but I'm still getting these errors on boot up:
Jul 11 03:58:31 mybox keytable: Loading keymap: failed
Jul 11 03:58:33 mybox mount: mount: mount point /dev/pts does not exist
Jul 11 03:58:33 mybox mount: mount: mount point /dev/shm does not exist
Jul 11 03:58:33 mybox netfs: Mounting other filesystems: failed
Jul 11 03:58:14 mybox rc.sysinit: Loading default keymap failed
Jul 11 03:58:21 mybox mount: mount: mount point /dev/pts does not exist
Jul 11 03:58:21 mybox mount: mount: mount point /dev/shm does not exist
Jul 11 03:58:21 mybox rc.sysinit: Mounting local filesystems: failed
Before If i tried to boot the kernel it would fully boot, but now it won't and I had to go back to the older kernel. Just so you know I compiled the kernel using that kernel. Meaning while running the new 2.4.18 I did: make dep && make clean && make bzImage then I went back to 2.4.9-34 and did: make modules && make modules_install then I copied the new kernel to /boot and ran lilo then tried to boot the new kernel and it wouldn't boot at all this time.
The modules are kernel-version specific, so the ones made for the 2.4.9 aren't "seen" by 2.4.18. You MUST make modules modules_install in the 2.4.18 area. You'll see that 2.4.9 modules get installed in /lib/modules/2.4.9/ and 2.4.18 in /lib/modules/2.4.18. Don't try to get creative - unless you *really* know what you are doing and force it, a 2.4.9 module doesn't load in a 2.4.18 kernel. That's also the problem with the sound - you haven't actually made and installed the soundcore.o module before you do the above command.
Well I unfortunately had to REDO a "make config" (I need time to recover from the agony) Well this time the kernel actually compiled unlike before when I tried to manually configure the .config file. Good news is the /dev/pts and /dev/shm is solved. Now when it boots I still get the keymap errors and now a NEW error.
Here's the error I get after the message
"Running LinuxConf hooks"
INIT: Id "1" respawning too fast: disable for 5 minutes.
INIT: Id "2" respawning too fast: disable for 5 minutes.
INIT: Id "3" respawning too fast: disable for 5 minutes.
INIT: Id "4" respawning too fast: disable for 5 minutes.
INIT: Id "5" respawning too fast: disable for 5 minutes.
INIT: no more processes left in this runlevel
In addition to this error I have another new error. I kinda remember telling "make config" to make the swap space mounted as /dev/hdd instead of /dev/hda3. So now INIT can't find the swap space when it's supposed to be initialized.