Eckhard Hoeffner wrote: >* Gerhard <[EMAIL PROTECTED]> [03 05 02 16:17]: > >>Hallo, >> >>Ich habe Probleme einen eigenen Kernel für ein ext3 woody zu übersetzen. >> > >Wenn Du einen eigenen Kernel baust, brauchst du eigentlich kein >initrd. Also ich habe hier ext3 mit 2.4.18 ohne Probleme am laufen. > >Das initrd wird ja nur dafür hergenommen, sozusagen zwischendurch >die Treiber zur Verfügung zu stellen, die notwendig sind, um das >System anzuschmeißen, also etwa SCSI-Festplatten. Wenn Du deien >Hardware kennst, brauchst du kein initrd und auch kein mkinitrd > >>Unter http://qref.sourceforge.net/quick/ch-kernel.en.html >><http://freemailng1101.web.de/jump.htm?goto=http://qref.sourceforge.net/quick/ch-kernel.en.html> > >>ist die Rede von mkinitrd -o, um ein initrd image in /boot zu schreiben. >> >>Wo finde ich das Packet? >> >>Ich habe es über rpmfind gefunden und mit alien -d -i installiert, war >>das falsch? >> >>Vorher ergab apt-cache search nur für mkinitrd-cd ein Ergebnis, was mich >>dazu verleitete es als Ersatz zu verwenden, was mir die gibraltar-livecd >>von der harddisk starten wollte und hängen blieb. >> >>Jetzt versuche ich erst mal ein apt-get install kernel-image-2.4.18-bf2.4 . >> >>Hat hier jemand Erfahrungen mit ext3 und mkinitrd auf debian? >> >>Nach der installation des rpm von RedHat: >>apt-cache search mkinitrd >>mkinitrd - Creates an initial ramdisk image for preloading modules. >> >>Ich habe schon folgende Beiträge zu meinem Installationsproblem gepostet: >> >>-probleme mit installation eines ext3 woody: habe gibraltar-bootcd auf >>meine festplatte in boot kopiert. >> >>-Kann Kernel nicht installieren. >> >>Vielleicht kann mir ja jemand auf die Sprünge helfen. >> > Hallo Eckhard,
Danke für die Antwort, endlich mal eine Info die mich (hoffentlich :-) )vom Holzweg abbringt. Ich habe jetzt mal wie von Eduart Boch empfohlen ein neues Kernel-image installiert. Ging nicht ganz problemlos. Ich hab den Terminal output mal angehangen. Nach dieser mail reboot. Mal schauen, was mich erwartet... :-) Vielen Dank an allen, und entschuldigt die verqueren postings - html, über 72 zeilen 3fach posts etc. .. :( , mein pop3 account ist noch nicht freigeschaltet, ich lese alles über webmail :( ). ciao gerhard
debian:~# apt-get install kernel-image-2.4.18-bf2.4 Reading Package Lists... Done Building Dependency Tree... Done The following NEW packages will be installed: kernel-image-2.4.18-bf2.4 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 1 packages not fully installed or removed. Need to get 0B/6401kB of archives. After unpacking 16.4MB will be used. Media Change: Please insert the disc labeled 'Debian GNU/Linux 3.0 _Woody_ - fsn.hu's i386 Binary-1 (20020411)' in the drive '/cdrom/' and press enter Selecting previously deselected package kernel-image-2.4.18-bf2.4. (Reading database ... 148954 files and directories currently installed.) Unpacking kernel-image-2.4.18-bf2.4 (from .../kernel-image-2.4.18-bf2.4_2.4.18-4_i386.deb) ... You are attempting to install a kernel image (version 2.4.18-bf2.4) However, the directory /lib/modules/2.4.18-bf2.4 still exists. If this directory belongs to a previous kernel-image-2.4.18-bf2.4 package, and if you have deselected some modules, or installed standalone modules packages, this could be bad. However, if this directory exists because you are also installing some stand alone modules right now, and they got unpacked before I did, then this is pretty benign. Unfortunately, I can't tell the difference. If /lib/modules/2.4.18-bf2.4 belongs to a old install of kenel-image-2.4.18-bf2.4, this is your last chance to abort the installation of this kernel image (nothing has been changed yet). If this directory is because of stand alone modules being installed right now, or if it does belong to an older kernel-image-2.4.18-bf2.4 package but you know what you are doing, and if you feel that this image should be installed despite this anomaly, Please answer n to the question. Otherwise, I suggest you move /lib/modules/2.4.18-bf2.4 out of the way, perhaps to /lib/modules/2.4.18-bf2.4.old or something, and then try re-installing this image. Do you want to stop now? [Y/n]n Setting up kernel-image-2.4.18-686 (rev.01) ... usage: mkinitrd [--version] [-v] [-f] [--ifneeded] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15) Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-686 (--configure): subprocess post-installation script returned error exit status 29 Setting up kernel-image-2.4.18-bf2.4 (2.4.18-4) ... You are attempting to install a kernel version that is the same as the version you are currently running (version 2.4.18-bf2.4). The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.4.18-bf2.4/modules.dep needs to be re-built. It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed. I am creating a new modules.dep file, but that may not be correct. It shall be regenerated correctly at next reboot. I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. Reboot as soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately after). I can not stress that too much. You need to reboot soon. Please Hit return to continue. I notice that you have System.map symbolic links in /. These were installed by older kernel image packages. However, all the programs that look at the information in the map files (including top, ps, and klogd) also will look at /boot/System.map-<version>, we just need to ensure that that file is present, and no longer require the symbolic link. Actually, having the symbolic link in / is technically detrimental (apart from cluttering up /); many programs, though looking in /boot, still allow /System.map to override. If you use LILO to choose between multiple kernels, then the /System.map symbolic link only applies to one such kernel, for all other choices the symbols loaded will be wrong. Not having the symbolic links at all prevents this. I can delete these symbolic links for you, if you wish. Would you like to delete the obsolete links now? [Yes] A new kernel image has been installed, and usually that means that some action has to be taken to make sure that the new kernel image is used next time the machine boots. Usually, this entails running a ``bootloader'' like SILO, loadlin, LILO, ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy. (Some boot loader, like grub, for example, do not need to be run on each new image install, so please ignore this if you are using such a boot loader). A new kernel image has been installed. at /boot/vmlinuz-2.4.18-bf2.4 (Size: 1219kB) Symbolic links, unless otherwise specified, can be found in / LILO sets up your system to boot Linux directly from your hard disk, without the need for booting from a boot floppy. WARNING If you are keeping another operating system or another version of Linux on a separate disk partition, you should not have LILO install a boot block now. Wait until you read the LILO documentation. That is because installing a boot block now might make the other system un-bootable. If you only want to run this version of Linux, go ahead and install the boot block here. If it does not work, you can still boot this system from a boot floppy. Would you like to create a boot floppy now? [No] yes Please note that the system size is 1248637 This is greater than the size that the kernel loader supports on i386 machines. What this means is that you need to use lilo to boot this kernel on i386 machines; the floppy is not going to be sufficient by itself on an i386 box. Of course, things may have changed since July 2000, when this diagnostic was written. Your Mileage may indeed vary. Please consider yourselves warned. Please hit return to continue. This process needs a formatted floppy. Please note that an unformatted floppy will cause this process to fail, and may well need a reboot to fix, and unfortunately, the system is not bootable yet. The first thing to determine is which floppy drive you wish to use. For most people, the default, which is the the default floppy drive, referred to as /dev/fd0, or A: would work. Some people may want the second floppy drive which is drive 1, or /dev/fd1, or B:. (Theoretically there could be 8 floppy drives on a machine) If in doubt, accept the default [0], which should work in most cases. Which floppy drive [0-7] do you want to use? [0] Ok, using drive at /dev/fd0. If there is no formatted floppy available, I could attempt to format it for you. Do you wish me to format the floppy? [No] yes Insert a floppy diskette into your boot drive (/dev/fd0) and press <Return> when ready: Measuring drive 0's raw capacity In order to avoid this time consuming measurement in the future, add the following line to /etc/driveprm: drive0: deviation=-1760 CAUTION: The line is drive and controller specific, so it should be removed before installing a new drive 0 or floppy controller. Verifying cylinder 79, head 1 mformat -s18 -t80 -h2 -S2 -M512 a: 2438+1 records in 2438+1 records out You already have a LILO configuration in /etc/lilo.conf Install a boot block using the existing /etc/lilo.conf? [Yes] no Wipe out your old LILO configuration and make a new one? [No] yes Rotated `/etc/lilo.conf' at Fri May 3 17:20:24 CEST 2002. Do you wish to set up Linux to boot from the hard disk? [Yes] You must do three things to make the Linux system boot from the hard disk. Install a partition boot record, install a master boot record, and set the partition active. You will be asked to perform each of these tasks. You may skip any or all of them, and perform them manually later on Hmm... I can't determine which partition to put the partition boot record on. I'm defaulting to the /dev/hdb5 which is where the root file system lives. Install a partition boot block on partition /dev/hdb5? [Yes] no A master boot record is required to run the partition boot record. However, you do not seem to have /boot/mbr.b, provided by the Debian package mbr. I hope that your master boot record or boot manager does boot the active partition. If not, you have to acquire the package mbr and install it. Please hit return to proceed. The master boot record will boot the active partition. If you want your system to boot another operating system, such as DOS or Windows, by default, answer "no" to the following question. You may still use your boot manager or the master boot record to boot Linux. If you want the system to boot Linux. by default, answer "yes". Make /dev/hdb5 the active partition? [Yes] 5: not a valid partition number (1-4) There was an error trying to activate /dev/hdb5. Please run "/sbin/activate /dev/hdb 5" by hand. Please hit return to proceed. Errors were encountered while processing: kernel-image-2.4.18-686 E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~# apt-get install kernel-image-2.4.18-bf2.4 Reading Package Lists... Done Building Dependency Tree... Done Sorry, kernel-image-2.4.18-bf2.4 is already the newest version. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 packages not fully installed or removed. Need to get 0B of archives. After unpacking 0B will be used. Setting up kernel-image-2.4.18-686 (rev.01) ... usage: mkinitrd [--version] [-v] [-f] [--ifneeded] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15) Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-686 (--configure): subprocess post-installation script returned error exit status 29 Errors were encountered while processing: kernel-image-2.4.18-686 E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~# apt-get install kernel-image-2.4.18-bf2.4remove Reading Package Lists... Done Building Dependency Tree... Done E: Couldn't find package kernel-image-2.4.18-bf2.4remove debian:~# apt-get upgrade kernel-image-2.4.18-bf2.4 Reading Package Lists... Done Building Dependency Tree... Done 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 packages not fully installed or removed. Need to get 0B of archives. After unpacking 0B will be used. Do you want to continue? [Y/n] Setting up kernel-image-2.4.18-686 (rev.01) ... usage: mkinitrd [--version] [-v] [-f] [--ifneeded] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15) Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-686 (--configure): subprocess post-installation script returned error exit status 29 Errors were encountered while processing: kernel-image-2.4.18-686 E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~# debian:~# apt-get install kernel-image-2.4.18-bf2.4 Reading Package Lists... Done Building Dependency Tree... Done Sorry, kernel-image-2.4.18-bf2.4 is already the newest version. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 packages not fully installed or removed. Need to get 0B of archives. After unpacking 0B will be used. Setting up kernel-image-2.4.18-686 (rev.01) ... usage: mkinitrd [--version] [-v] [-f] [--ifneeded] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15) Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-686 (--configure): subprocess post-installation script returned error exit status 29 Errors were encountered while processing: kernel-image-2.4.18-686 E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~# apt-get install kernel-image-2.4.18-bf2.4remove Reading Package Lists... Done Building Dependency Tree... Done E: Couldn't find package kernel-image-2.4.18-bf2.4remove debian:~# apt-get upgrade kernel-image-2.4.18-bf2.4 Reading Package Lists... Done Building Dependency Tree... Done 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 packages not fully installed or removed. Need to get 0B of archives. After unpacking 0B will be used. Do you want to continue? [Y/n] Setting up kernel-image-2.4.18-686 (rev.01) ... usage: mkinitrd [--version] [-v] [-f] [--ifneeded] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15) Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-686 (--configure): subprocess post-installation script returned error exit status 29 Errors were encountered while processing: kernel-image-2.4.18-686 E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~# apt-get remove kernel-image-2.4.18-bf2.4 Reading Package Lists... Done Building Dependency Tree... Done The following packages will be REMOVED: kernel-image-2.4.18-bf2.4 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 packages not fully installed or removed. Need to get 0B of archives. After unpacking 16.4MB will be freed. Do you want to continue? [Y/n] (Reading database ... 149588 files and directories currently installed.) Removing kernel-image-2.4.18-bf2.4 ... You are running a kernel (version 2.4.18-bf2.4) and attempting to remove the same version. This is a potentially disastrous action. Not only will /boot/vmlinuz-2.4.18-bf2.4 be removed, making it impossible to boot it, (you will have to take action to change your boot loader to boot a new kernel), it will also remove all modules under the directory /lib/modules/2.4.18-bf2.4. Just having a copy of the kernel image is not enough, you will have to replace the modules too. I repeat, this is very dangerous. If at all in doubt, answer no. If you know exactly what you are doing, and are prepared to hose your system, then answer Yes. Remove the running kernel image (not recommended) [No]? yes Ok, proceeding with removing running kernel image. Setting up kernel-image-2.4.18-686 (rev.01) ... usage: mkinitrd [--version] [-v] [-f] [--ifneeded] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15) Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-686 (--configure): subprocess post-installation script returned error exit status 29 Errors were encountered while processing: kernel-image-2.4.18-686 E: Sub-process /usr/bin/dpkg returned an error code (1) debian:~# apt-get remove kernel-image-2.4.18-686 Reading Package Lists... Done Building Dependency Tree... Done The following packages will be REMOVED: kernel-image-2.4.18-686 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 packages not fully installed or removed. Need to get 0B of archives. After unpacking 14.5MB will be freed. Do you want to continue? [Y/n] (Reading database ... 148954 files and directories currently installed.) Removing kernel-image-2.4.18-686 ... debian:~# apt-get install kernel-image-2.4.18-bf2.4 Reading Package Lists... Done Building Dependency Tree... Done The following NEW packages will be installed: kernel-image-2.4.18-bf2.4 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/6401kB of archives. After unpacking 16.4MB will be used. Media Change: Please insert the disc labeled 'Debian GNU/Linux 3.0 _Woody_ - fsn.hu's i386 Binary-1 (20020411)' in the drive '/cdrom/' and press enter Selecting previously deselected package kernel-image-2.4.18-bf2.4. (Reading database ... 148334 files and directories currently installed.) Unpacking kernel-image-2.4.18-bf2.4 (from .../kernel-image-2.4.18-bf2.4_2.4.18-4_i386.deb) ... Setting up kernel-image-2.4.18-bf2.4 (2.4.18-4) ... You are attempting to install a kernel version that is the same as the version you are currently running (version 2.4.18-bf2.4). The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.4.18-bf2.4/modules.dep needs to be re-built. It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed. I am creating a new modules.dep file, but that may not be correct. It shall be regenerated correctly at next reboot. I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. Reboot as soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately after). I can not stress that too much. You need to reboot soon. Please Hit return to continue. A new kernel image has been installed, and usually that means that some action has to be taken to make sure that the new kernel image is used next time the machine boots. Usually, this entails running a ``bootloader'' like SILO, loadlin, LILO, ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy. (Some boot loader, like grub, for example, do not need to be run on each new image install, so please ignore this if you are using such a boot loader). A new kernel image has been installed. at /boot/vmlinuz-2.4.18-bf2.4 (Size: 1219kB) Symbolic links, unless otherwise specified, can be found in / LILO sets up your system to boot Linux directly from your hard disk, without the need for booting from a boot floppy. WARNING If you are keeping another operating system or another version of Linux on a separate disk partition, you should not have LILO install a boot block now. Wait until you read the LILO documentation. That is because installing a boot block now might make the other system un-bootable. If you only want to run this version of Linux, go ahead and install the boot block here. If it does not work, you can still boot this system from a boot floppy. Would you like to create a boot floppy now? [No] yes Please note that the system size is 1248637 This is greater than the size that the kernel loader supports on i386 machines. What this means is that you need to use lilo to boot this kernel on i386 machines; the floppy is not going to be sufficient by itself on an i386 box. Of course, things may have changed since July 2000, when this diagnostic was written. Your Mileage may indeed vary. Please consider yourselves warned. Please hit return to continue. This process needs a formatted floppy. Please note that an unformatted floppy will cause this process to fail, and may well need a reboot to fix, and unfortunately, the system is not bootable yet. The first thing to determine is which floppy drive you wish to use. For most people, the default, which is the the default floppy drive, referred to as /dev/fd0, or A: would work. Some people may want the second floppy drive which is drive 1, or /dev/fd1, or B:. (Theoretically there could be 8 floppy drives on a machine) If in doubt, accept the default [0], which should work in most cases. Which floppy drive [0-7] do you want to use? [0] Ok, using drive at /dev/fd0. If there is no formatted floppy available, I could attempt to format it for you. Do you wish me to format the floppy? [No] Insert a (formatted) floppy diskette into your boot drive (/dev/fd0) and press <Return> when ready: 2438+1 records in 2438+1 records out You already have a LILO configuration in /etc/lilo.conf Install a boot block using the existing /etc/lilo.conf? [Yes] Testing lilo.conf ... Testing successful. Installing the partition boot sector... Installation successful. debian:~# lilo Warning: LBA32 addressing assumed Warning: COMPACT may conflict with LBA32 on some systems Added Linux * debian:~# cat /etc/lilo.conf boot=/dev/hda3 root=/dev/hdb5 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label = Linux read-only debian:~# debian:~# cat /etc/lilo.conf boot=/dev/hda3 root=/dev/hdb5 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label = Linux read-only other=/dev/hda1 label=windows table=/dev/hda other=/dev/fd0 label=floppy unsafedebian:~# lilo Warning: LBA32 addressing assumed Warning: COMPACT may conflict with LBA32 on some systems Added Linux * Added windows Added floppy debian:~#reboot