Deciphering variables

I had a problem with running the latest debian kernel. dpkg wasn't able to create the subdirectory with the modules (I think). So I am running rescue. It runs but kicks over to net cat. I am trying to follow the logic but I don't code so I am struggling.
How do I force the rescue system to stay on serial? I lose serial after it boots rescue.

Paul
PS Any idea why it dpkg wouldn't do the modules subdirectory?

Paul,

> How do I force the rescue system to stay on
> serial? I lose serial after it boots rescue.

This variable is what started your netconsole

preboot

So in rescue system, if for whatever reason you variables are set to start netconsole, then you should clear it while in rescue system, and reboot (but first make sure you know your serial console is working, i.e. by interrupting serial console during countdown).

List and copy the current content of preboot

fw_printenv preboot

To clear preboot

fw_setenv preboot

> PS Any idea why it dpkg wouldn't do the modules
> subdirectory?

Did you install the kernel while being root? I didn't experience any problem creating sub-directories for modules.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Bohdi,

Thanks. I just need to clear the preboot var.

I wish I would have logged the output of the dpkg operation. Maybe I can set it up again and capture it.
I recall it said something like, "say, your installer says to use this subdirectory but I don't see it so I am going to ignore that."

Anyhow, it looks like that is what it did. No modules installed.

Paul

I chrooted into the /boot directory and ran dpkg -i again. Here is are the messages I was presented with. Not to swift with the lingo but I am learning. In the meantime, Does anything jump out as a factor?

Paul

Done.
Unpacking linux-image-4.2.0-kirkwood-tld-1 (1.0) over (1.0) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-kirkwood-tld-1 /boot/vmlinuz-4.2.0-kirkwood-tld-1
Setting up linux-image-4.2.0-kirkwood-tld-1 (1.0) ...

 Hmm. There is a symbolic link /lib/modules/4.2.0-kirkwood-tld-1/build
 However, I can not read it: No such file or directory
 Therefore, I am deleting /lib/modules/4.2.0-kirkwood-tld-1/build


 Hmm. The package shipped with a symbolic link /lib/modules/4.2.0-kirkwood-tld-1/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/4.2.0-kirkwood-tld-1/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.2.0-kirkwood-tld-1 /boot/vmlinuz-4.2.0-kirkwood-tld-1
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.2.0-kirkwood-tld-1 /boot/vmlinuz-4.2.0-kirkwood-tld-1
update-initramfs: Generating /boot/initrd.img-4.2.0-kirkwood-tld-1
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 4.2.0-kirkwood-tld-1 /boot/vmlinuz-4.2.0-kirkwood-tld-1
root@macplug:/boot# 

z3bram3n Wrote:
-------------------------------------------------------
> I chrooted into the /boot directory and ran dpkg
> -i again. Here is are the messages I was presented
> with. Not to swift with the lingo but I am
> learning. In the meantime, Does anything jump out
> as a factor?
>
> Paul
>

> Done.
> Unpacking linux-image-4.2.0-kirkwood-tld-1 (1.0)
> over (1.0) ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing
> /etc/kernel/postrm.d/initramfs-tools
> 4.2.0-kirkwood-tld-1
> /boot/vmlinuz-4.2.0-kirkwood-tld-1
> Setting up linux-image-4.2.0-kirkwood-tld-1 (1.0)
> ...
> 
>  Hmm. There is a symbolic link
> /lib/modules/4.2.0-kirkwood-tld-1/build
>  However, I can not read it: No such file or
> directory
>  Therefore, I am deleting
> /lib/modules/4.2.0-kirkwood-tld-1/build
> 
> 
>  Hmm. The package shipped with a symbolic link
> /lib/modules/4.2.0-kirkwood-tld-1/source
>  However, I can not read the target: No such file
> or directory
>  Therefore, I am deleting
> /lib/modules/4.2.0-kirkwood-tld-1/source
> 
> Running depmod.
> Examining /etc/kernel/postinst.d.
> run-parts: executing
> /etc/kernel/postinst.d/apt-auto-removal
> 4.2.0-kirkwood-tld-1
> /boot/vmlinuz-4.2.0-kirkwood-tld-1
> run-parts: executing
> /etc/kernel/postinst.d/initramfs-tools
> 4.2.0-kirkwood-tld-1
> /boot/vmlinuz-4.2.0-kirkwood-tld-1
> update-initramfs: Generating
> /boot/initrd.img-4.2.0-kirkwood-tld-1
> run-parts: executing
> /etc/kernel/postinst.d/zz-flash-kernel
> 4.2.0-kirkwood-tld-1
> /boot/vmlinuz-4.2.0-kirkwood-tld-1
> root@macplug:/boot# 
> 
>

It is OK. These warnings are expected. Just artifacts of make-kpkg left in the deb file. dpkg -i saw the ./source and ./build directory symlinks (which are not relevant) and tried to find them.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Bohdi,
Using my serial adapter I noticed that the device reported trying to boot the prior kernel version 3 instead of the updated 4.2.0 version. Apparently, I made an error editing the cut and paste snippet when I ran the mkimage commands for 4.2.0.

I chrooted into the thumb drive and repeated the commands (with the correct edits) and I am back on track.

Thanks for all your help, once again.

Paul