DebianThis forum is for the discussion of Debian Linux.
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.
──────────────────┤ Configuring linux-image-188.8.131.52-grsec-bastion ├───────────────────┐
│ You are installing a kernel with an initrd image │
│ You are attempting to install an initrd kernel image (version │
│ 184.108.40.206-grsec-bastion) on a machine currently running kernel version 2.4.27-2-386. │
│ I have been unable to find a suitable tool for generating initrd images (I looked at │
│ the list "mkinitramfs-kpkg mkinitrd.yaird") This will break the installation, unless │
│ such tools are also being installed right now in the same run. (This means, one from │
│ the following list yaird (>= 0.0.11-8) | initramfs-tools (>= 0.53) | │
│ linux-initramfs-tool,) │
Building Dependency Tree... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
initramfs-tools: Depends: klibc-utils (>= 1.1.16-1) but it is not going to be installed
Depends: busybox (>= 1:1.01-3) but it is not going to be installed or
busybox-cvs-static (>= 20040623-1) but it is not going to be installed
Depends: module-init-tools but it is not going to be installed
Depends: udev (>= 0.076-5) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
depmod: *** Unresolved symbols in /lib/modules/220.127.116.11-grsec-bastion/kernel/net/irda/ircomm/ircomm-tty.ko
depmod: *** Unresolved symbols in /lib/modules/18.104.22.168-grsec-bastion/kernel/net/irda/irnet/irnet.ko
depmod: *** Unresolved symbols in /lib/modules/22.214.171.124-grsec-bastion/kernel/net/sctp/sctp.ko
Finding valid ramdisk creators.
Failed to find suitable ramdisk generation tool for kernel version
126.96.36.199-grsec-bastion on running kernel 2.4.27-2-386 in mkinitramfs-kpkg mkinitrd.yaird
dpkg: error processing linux-image-188.8.131.52-grsec-bastion (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
i followd your instructions, and installed libmikmod2, and now xmms will start up and play songs....but still no sound. none of the installed mixers will let me adjust the master volume setting, it's not muted...just isnt available.
Not sure, if my contribution is still desired, but I had similar problem with SuSE 10.0 OSS on the ThinkPad 600x. The reason was ACPI - I had an IRQ-conflict.
I have a similar problem. I have 2.4.27-2-386 and I boot with that. I installed 2.6.16-2-686 too using aptitude but I can't boot with that. The boot process stops with message "waiting for root file system"
What is wrong?
What if the sources (for example for do a step in the tar of vmware-player) arent there????
Linux hecatombe 2.6.15-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686 GNU/Linux
My best solution because I don't know how to handle the dependencies in command line was to start synaptic search the kernel-image.x.x.x-x-x that I have installed, right click and see the recommended packages and it have downloaded kernel-source.x.x.x without the extra -x-x ... By the way... what mean that extra -1-k7?????
By the way, if I have the kernel-source installed, I need anyway the kernel-headers????
Distribution: Ubuntu 6.06 LTS, PC / Debian Etch 184.108.40.206 PPC
I think I will follow these instructions and see what happens for me on PPC.
The last time I tried compiling a new kernel (linux-2.6.17.tar.bz2 from kernel.org) I was getting a bunch of errors in drivers such as for the Intel E1000 Gigabit controller and vmlinux.coff package build errors.
Couldn't hurt to try.
(Errors still there. The former is in e1000_xmit_frame() : /net/drivers/e1000/e1000_main.c, and the latter fails on a cp operation.
I'm confused now.)
(EDIT 2: Okay, so I got past those, and made vmlinux.coff appear with the 'touch' command - strange that I didn't remember it seeing as I used it all the time for work on PC. I set HAVE_COFF_IMAGE to NO in debian/rules but apparently that last made the kernel build process use it anyway. I installed the kernel_image .deb and then did a depmod.
unknown symbol in kernel: vgacon_remap_base
Looked around a while, saw that this symbol belongs to CONFIG_VGA_CONSOLE, which is already built in to the kernel. So it shouldn't do much damage to proceed, right? Wrong.
Yaboot halted at "loading ramdisk" and I had to get a live CD to fix it up. This entailed removing all of the new kernel.
What did I do wrong?)
(EDIT 3: Now net/ixgb/ixgb_main is halting with the same errors as e1000. I think this would soon be better off in its own thread.)
Last edited by RavenOfOdin; 07-30-2006 at 04:26 PM.
When I install the kernel modules using make module install, will I blow away the 2.4 modules? If so, is there a way to have modules for both kernels installed?
I'm in the middle of upgrading our kernel at work from 2.4 to 2.6. We're using Debian sarge. I'm compiling the kernel from source. I disabled my os when I made this upgrade at home on my slackware box, and I'm trying to avoid the same trouble here, as its a production server :P
When I upgraded my kernel at home, my first attempt failed, but I was unable to rollback because (apparently) the 2.4 modules had been blown away (I'm not entirely sure this is what happened, but my os was fried at that point so I had to start over)
I would think that you could install both types of kernels on the same system, but I don't know why trying to upgrade broke your old kernel. If you are worried, I would suggest trying to upgrade to the 2.6 kernel using a generic one available in the Debian repositories. Those kernels usually upgrade smoothly. Once you have a 2.6 kernel installed, you can then custom compile your own.
Of course you can have two or more kernels and boot in kernel of your choise but you need to do it right.About above message " waiting root partition to boot" I had that problem too until I realized that I forgot to copy config file from /boot/ to
/usr/src/linux-source-x.x.x/.config before make menuconfig command.
Its easy to make new kernel under Etch.After you download and unpack wanted kernel source and cd in that directory you need to copy /boot/config file to /path/to/source/.config , do make menuconfig and then
make-kpkg --append-to-version=.yourrevision --initrd kernel_image which will make kernel_image in parent directory.Then after cd .. do
dpkg -i linux-image-version and isntall it and then
grub install /dev/sda or your device
and system will do everything initrd , sysconfig ,edit your grub file just everything .So you need to reboot and chose kernel you want and thats it !
make-kpkg will make new modules directory /lib/modules/newkernel/ so it will not be mixed up with existing /lib/modules/oldkernel/
You need to have gcc kernel-package kernel-source-2.6.x.x libc6-dev
tk8.3 libncurses5-dev fakeroot to do this.