Re: vmlinuz-4.9.0-8-armmp-lpae pkg install fails due to /usr/bin/linux-update-symlinks
On 1/23/19 9:37 AM, Lennart Sorensen wrote:> On Tue, Jan 22, 2019 at
09:59:08PM -0500, Dennis Clarke wrote:
>> well darn !
>>
>> root@arm7:/boot# mount -v
>> /dev/mmcblk0p2 on / type ext4 (rw,relatime,data=ordered)
>> devtmpfs on /dev type devtmpfs<snip>>> /dev/mmcblk0p1 on /boot type
vfat
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
>> tmpfs on /run/user/0 type tmpfs
>> (rw,nosuid,nodev,relatime,size=206040k,mode=700)
>> root@arm7:/boot#
>>
>> What I need is a proper Debian install process on this tinker board ASUS
>> thing and then I can say goodbye to the linaro install that comes with
>> it.
>>
>> Thanks for catching that and .. gee .. is there a way to recover?
>
> I would think this could work:
>
> Move the files belonging to debian packages from /boot to another
> location,
root@arm7:~# cat /etc/debian_version
9.6
root@arm7:~# uname -a
Linux arm7 4.4.132+ #1 SMP Tue Oct 23 18:03:49 CST 2018 armv7l GNU/Linux
root@arm7:~#
root@arm7:~# pwd
/root
root@arm7:~#
root@arm7:~# cd /boot; tar -cf /root/files_from_old_slash_boot.tar .
root@arm7:/boot# ls -l /root/files_from_old_slash_boot.tar
-rw-r--r-- 1 root root 15104000 Jan 23 17:38
/root/files_from_old_slash_boot.tar
root@arm7:/boot# cd /root
> then unmount /boot and move the files into the /boot that
> is part of / then mount your boot partition as something else (like
> /vfatboot or something).
Weird .. there is a pre-existing 'hdmi' directory in there.
root@arm7:~# mount -v | grep 'boot'
/dev/mmcblk0p1 on /boot type vfat
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
root@arm7:~# umount /dev/mmcblk0p1
root@arm7:~# cd /
root@arm7:/# ls -lapb /boot
total 12
drwxr-xr-x 3 root root 4096 Dec 23 05:23 ./
drwxr-xr-x 23 root root 4096 Nov 3 2016 ../
drwxr-xr-x 2 root root 4096 Dec 23 05:23 hdmi/
root@arm7:/# find /boot -ls
524289 4 drwxr-xr-x 3 root root 4096 Dec 23 05:23
/boot
524290 4 drwxr-xr-x 2 root root 4096 Dec 23 05:23
/boot/hdmi
root@arm7:/#
root@arm7:/# cd /boot
root@arm7:/boot# tar -xvf /root/files_from_old_slash_boot.tar
./
./zImage
./rk3288-miniarm.dtb
./overlays/
./overlays/ads7846-tinker.dtbo
./overlays/camera-ov5647.dtbo
./overlays/ds1307.dtbo
./overlays/es90x8q2m-dac.dtbo
./overlays/googlevoicehat-soundcard.dtbo
./overlays/hifiberry-amp.dtbo
./overlays/hifiberry-dac.dtbo
./overlays/hifiberry-dacplus.dtbo
./overlays/hifiberry-digi-pro.dtbo
./overlays/hifiberry-digi.dtbo
./overlays/iqaudio-dac.dtbo
./overlays/iqaudio-dacplus.dtbo
./overlays/iqaudio-digi-wm8804-audio.dtbo
./overlays/justboom-dac.dtbo
./overlays/justboom-digi.dtbo
./overlays/lirc-rpi.dtbo
./overlays/lirc-toshiba.dtbo
./overlays/mcp2515-can0.dtbo
./overlays/pitft35-resistive-tinker.dtbo
./overlays/pps-gpio.dtbo
./overlays/w1-gpio.dtbo
./overlays/waveshare32b-tinker.dtbo
./overlays/waveshare35a-tinker.dtbo
./hw_intf.conf
./extlinux/
./extlinux/extlinux.conf
./extlinux/extlinux.conf_orig
./hdmi/
./hdmi/hdmi_modes.txt
./config-4.9.0-8-armmp-lpae
./vmlinuz-4.9.0-8-armmp-lpae
./System.map-4.9.0-8-armmp-lpae
root@arm7:/boot#
root@arm7:~# mkdir /vfatboot
root@arm7:~# mount /dev/mmcblk0p1 /vfatboot
root@arm7:~# mount -v | grep 'mmcblk0p'
/dev/mmcblk0p2 on / type ext4 (rw,relatime,data=ordered)
/dev/mmcblk0p1 on /vfatboot type vfat
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
root@arm7:~#
> On these types of machines usually you use
> the flash-kernel package, which copies to correct files from /boot to
> the vfat boot partition when a new kernel is installed and generates the
> needed uboot scripts or whatever a given system requires. That is once
> you add the machine identifier to the database for flash-kernel.
>
> There seems to be no reason to have a seperate /boot partition from the
> debian point of view if the system boots from a vfat partition so easier
> to just make /boot be a plain directory on the root partition in that
> case.
>
At this point I have a slightly borked /boot which is on the normal ext4fs
filesystem for '/' and I could re-run the script to create the temporary
symlinks and do the rename magic needed by the
linux-image-4.9.0-8-armmp-lpae
install process. Then copy everything back to /vfatboot and undo the above
merely to allow the unit to boot.
Really this is some sort of a slightly borked debian from "linaro" whereas
I really just want pure off the shelf debian buster/sid. That probably
explains how I landed in this mess.
Dennis
Reply to: