| 1 |
On Wed, Mar 25, 2020 at 8:23 AM J. Roeleveld <joost@××××××××.org> wrote: |
| 2 |
> |
| 3 |
> On Tuesday, March 24, 2020 10:57:59 PM CET andrey.vul@×××××.com wrote: |
| 4 |
> > On Tue, Mar 24, 2020 at 2:45 AM J. Roeleveld <joost@××××××××.org> wrote: |
| 5 |
> > > On Tuesday, March 24, 2020 4:55:49 AM CET andrey.vul@×××××.com wrote: |
| 6 |
> > > > I've somehow built a kernel that won't accept any initramfs. To |
| 7 |
> > > > elaborate, it hangs in shell in dracut and panicks with a minimal |
| 8 |
> > > > initramfs as if it rejects the initramfs entirely and tries to boot an |
| 9 |
> > > > lvm volume, which of course, fails. |
| 10 |
> > > > |
| 11 |
> > > > Kernel config: |
| 12 |
> > > > http://sprunge.us/tqz3BM |
| 13 |
> > > > |
| 14 |
> > > > The minimal initramfs is described by the file listing |
| 15 |
> > > > http://sprunge.us/GQVbqc |
| 16 |
> > > > and init script http://sprunge.us/YHWY9Z , though this script is of |
| 17 |
> > > > limited use since even with `exec sh` in the first non-comment line, |
| 18 |
> > > > the kernel doesn't follow through. |
| 19 |
> > > > |
| 20 |
> > > > Thoughts? |
| 21 |
> > > |
| 22 |
> > > Please provide the info as attachments instead of temporary links. |
| 23 |
> |
| 24 |
> Few thoughts: |
| 25 |
> |
| 26 |
> 1) Are you certain your initramfs includes everything? My "config" file is a |
| 27 |
> lot longer. |
| 28 |
Yes, and it is the absolute bare minimum necessary. |
| 29 |
> |
| 30 |
> 2) How are you generating the initramfs? |
| 31 |
/usr/src/linux/usr/gen_init_cpio /usr/src/initramfs/files.list | xz -z |
| 32 |
> /boot/intramfs-....img |
| 33 |
> |
| 34 |
> 3) how are you adding it to the bootloader? |
| 35 |
Grub's default form. To elaborate, the usual method grub does when |
| 36 |
generating a linux entry in grub-mkconfig. |
| 37 |
> |
| 38 |
> 4) Have you tried embedding the initramfs into the kernel? |
| 39 |
Yes, and that made it work. Weird how it didn't work not embedded into |
| 40 |
the kernel. |
| 41 |
On further thought, it worked after a couple of debugging iterations. |
| 42 |
Could it have been the bugs in the script at fault? |
| 43 |
> |
| 44 |
> Also, can you provide the kernel messages leading to and including the panic? |
| 45 |
> (Either full text or a clear photo taken with a camera/phone/tablet) |
| 46 |
Well, the two panics were either trying to kill init or the familiar |
| 47 |
"VFS: Unable to mount root fs on unknown-block(0,0)". Kernel |
| 48 |
framebuffer load reset grub's high res console and the panic took over |
| 49 |
the screen so messages right before would've been impossible to |
| 50 |
extract without something like a serial console. |
Archives