Re: making debs for u-boot kernels
On Friday 26 July 2019 17:35:01 Reco wrote:
> Hi.
>
> On Thu, Jul 25, 2019 at 12:49:32PM -0400, Gene Heskett wrote:
> > I am furious (fat lot of good that does me) with the lack of tools,
> > and information on how to use them to build an installable
> > kernel.deb for a rpi-3b. I know it can be done, I have witnessed
> > apt do it several times, on at least two of the arm platforms, once
> > on an arm64 running stretch and several times on armhf for releases
> > from jessie to buster.
>
> Raspberry Pi does not use u-boot. Raspbian does not use u-boot. Their
> proprietary bootloader can be forced to run u-boot, but its not worth
> it - by using u-boot you're limiting yourself to armhf, and Raspberry
> Pi3 is an aarch64 board.
>
> > I want to take a linux-rt tar.xz direct from kernel.org, and its
> > patches to bring it up to realtime, build it and install it all on
> > the pi-3b, to which I have added a 120GB SSD for workspace, and a
> > 10GB swap so it can now build linuxcnc.
>
> Consider installing a proper Debian first the way it's outlined at
> [1]. Booting a custom kernel will be as easy as adding an another
> entry to grub.cfg.
>
> Reco
>
> [1]
> https://pete.akeo.ie/2019/07/installing-debian-arm64-on-raspberry-pi.h
>tml
Now, after doing the boot rescue stuff, I let it use the default, which
made the whole thing into a fat16 lba. I don't think thats correct. So
I'll go back to fdisk, which now seems to be working, and use
size=+314.6MB for last sector of part #1
Then because I have a 10GB swap on one of the SSD's, I made the rest of
that 64GB u-sd into linux extended. That as close to ext4 as fdisk
gets.
But now it makes no attempt at booting. Back in this machine,
mounting /dev/sdf1 as vfat, an ls -l returns:
root@coyote:Sheldon-frankenheskett$ ls -l /media/sdf1
total 5200
-rwxr-xr-x 1 root root 25354 Jul 25 16:46 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 25617 Jul 25 16:46 bcm2710-rpi-3-b-plus.dtb
drwxr-xr-x 3 root root 8192 Jul 27 09:53 boot
-rwxr-xr-x 1 root root 2048 Jul 6 00:00 boot.catalog
-rwxr-xr-x 1 root root 52296 Jul 25 16:47 bootcode.bin
-rwxr-xr-x 1 root root 925 Jul 25 16:42 config.txt
drwxr-xr-x 2 root root 8192 Jul 27 09:53 css
drwxr-xr-x 3 root root 8192 Jul 27 09:53 dists
drwxr-xr-x 3 root root 8192 Jul 27 09:53 doc
drwxr-xr-x 4 root root 8192 Jul 27 09:53 EFI
drwxr-xr-x 2 root root 8192 Jul 25 16:42 firmware
-rwxr-xr-x 1 root root 6724 Jul 25 16:47 fixup.dat
drwxr-xr-x 2 root root 8192 Jul 27 09:53 install.a64
-rwxr-xr-x 1 root root 79209 Jul 6 00:00 md5sum.txt
drwxr-xr-x 2 root root 8192 Jul 27 09:53 pics
drwxr-xr-x 3 root root 8192 Jul 27 09:53 pool
-rwxr-xr-x 1 root root 8161 Jul 6 00:00 README.html
-rwxr-xr-x 1 root root 2617 Jul 25 16:42 Readme.md
-rwxr-xr-x 1 root root 291 Mar 4 2017 README.mirrors.html
-rwxr-xr-x 1 root root 86 Mar 4 2017 README.mirrors.txt
-rwxr-xr-x 1 root root 4897 Jul 6 00:00 README.txt
-rwxr-xr-x 1 root root 2097152 Jul 25 12:52 RPI_EFI.fd
-rwxr-xr-x 1 root root 2878180 Jul 25 16:47 start.elf
With all this messing around, I don't imagine anything on the rest of the
u-sd survives.
on to fdisk /dev/sdf:
Welcome to fdisk (util-linux 2.29.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): a
Partition number (1,2, default 2): 1
The bootable flag on partition 1 is enabled now.
Command (m for help): p
Disk /dev/sdf: 58 GiB, 62277025792 bytes, 121634816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbc9947f0
Device Boot Start End Sectors Size Id Type
/dev/sdf1 * 2048 647167 645120 315M e W95 FAT16 (LBA)
/dev/sdf2 647168 121634815 120987648 57.7G 85 Linux extended
and an ls on the mounted /dev/sdf1 is now empty, so I assume I start over
with the copies.
But one question, can it install w/o a swap, or is it smart enough to
find the 10GB of swap on an ssd plugged into a usb port?
Probably better I steal a couple gigs from sdf2 for a swap. But that
command "getsz" is deprecated, so best I use a +56G for lastsector of
part #2
So now it looks like this:
Device Boot Start End Sectors Size Id Type
/dev/sdf1 * 2048 647167 645120 315M e W95 FAT16 (LBA)
/dev/sdf2 647168 4841471 4194304 2G 82 Linux swap / Solaris
/dev/sdf3 4841472 121634815 116793344 55.7G 85 Linux extended
And that worked. But now I wonder why I bothered. Nearly all the tools to
configure and build stuff are on the missing list and both apt and
synaptic can't find them. like furinstance, where the heck is blkid?
I've no way to id a disk and add it to /etc/fstab except by a volatile
name like /dev/sda1 etc. And security? Rampant overkill, the first
thing I removed was apparmor.
As a user I can't even look at dmesg to see what the hell it called the
usb drive I just plugged in. Thats best described as the stuff, warm and
odorous, found on the ground behind the bovine specie males.
where is dpkg-buildpackage and its family of prep tools for building
installable debs from a kernel.org tarball?
None of that stuff can be found by apt or synaptic.
I bought this stuff for ME to use for whatever I can make it wiggle bits
and do a job for me. But I'm feeling like I tilting with M$, telling me
what I can and cannot do with it.
So where are those tools?
Thanks for any productive answers, maybe the default sources.lists are
hiding them?
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: