Hi KatolaZ, It's gzip compressed:
emi@devuan:~$ file /boot/initrd.img-4.7.0-0.bpo.1-686 /boot/initrd.img-4.7.0-0.bpo.1-686: gzip compressed data, last modified: Fri Dec 16 09:32:51 2016, from Unix It unpacks ok: emi@devuan:~$ mkdir -p /tmp/initrd emi@devuan:~$ cd /tmp/initrd emi@devuan:/tmp/initrd$ zcat /boot/initrd.img-4.7* | cpio -idmv 2>/dev/null emi@devuan:/tmp/initrd$ file init init: POSIX shell script, ASCII text executable emi@devuan:/tmp/initrd$ file sbin/init sbin/init: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=6948872c0e5c6e1933b25bc2ae3eb8b4f9bdac19, stripped emi@devuan:/tmp/initrd$ head init #!/bin/sh echo "Loading, please wait..." # Default PATH differs between shells, and is not automatically exported # by klibc dash. Make it consistent. export PATH=/sbin:/usr/sbin:/bin:/usr/bin [ -d /dev ] || mkdir -m 0755 /dev [ -d /root ] || mkdir -m 0700 /root That's the "Loading, please wait..." I never see. I tried the 4.6 kernel with the 4.7 initrd and it almost boot (at the end init cannot access the root fs device). But the 4.6 kernel extracts the 4.7 initrd and loads de init process. This leads me to think it's a kernel issue. Tried booting the 4.7 to /bin/sh. Same results. It seems it cannot extract the initrd? Cheers, Emiliano. On Fri, Dec 16, 2016 at 9:07 AM, KatolaZ <[email protected]> wrote: > On Fri, Dec 16, 2016 at 08:21:11AM -0300, Emiliano Marini wrote: > > I've got rid of that error installing the kernel headers. But nothing has > > changed. > > > > apt-get install linux-headers-4.7.0-0.bpo.1-all > > apt-get install --reinstall linux-image-4.7.0-0.bpo.1-686 > > > > This definitely looks to me as something (i.e., either /sbin/init or a > kernel module) being missing/misplaced in the initrd. Is the initrd > actually uncompressed successfully? If it is (and now I am just > wondering), is it possible that the "init" you have in there is > corrupted or missing, or instead waiting for some magic to happen? > Have you tried to pass "init=/bin/sh" to the kernel? What happens? > > Which is the format of the initrd file that is created for you by > initramfs-tools? Maybe (but this would be quite weird) that > initramfs-tools has used xz compression, and for > who-knows-which-reason the kernel does not have xz builtin, and the > kernel fails to uncompress the initrd file? > > My2Cents > > KatolaZ > > -- > [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] > [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] > [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] > [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] > [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] > _______________________________________________ > Dng mailing list > [email protected] > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >
_______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
