Software > Operating Systems and Porting

[NEWS] Debian 11 is out

<< < (7/9) > >>

xilinder:
I do not make .deb packages. I also do not use make -jx, or make modules.

Pretty much I do make menuconfig, make, make modules_install, make install.

In menuconfig I change things to what I want, like 4k PAGESIZE, and for my system with 2x8 cores, I use 64 processors.

If I want I use mc (midnight commander) as root or sudo to look at /boot and perhaps remove,move, or add kernels and
other stuff and then use update-grub as necessary.
Using the update-grub command may require you to login as su - (the  - is important) and then do /usr/sbin/update-grub.

MauryG5:
Hi Xlinder, I also do like you and I use that procedure that they say is the universal one, only that way the system does not recognize you the fully installed kernel and when you have to remove it to put a new one, you have to remove file by file in the boot folder and when you run the grep command to find out how many kernels you have installed, the one you made is not there since you have not installed .deb packages. and you can't even do the classic purge command to remove that kernel because it tells you that kernel isn't installed on your system. So the system eventually does not recognize as installed, a kernel with that procedure even if it regularly makes you use it obvious. I would like to understand if it is possible to make the system recognize a kernel installed with this universal procedure as you do ...

Borley:
I have been burned by running make as root user in the past, so I always avoid running make with sudo when possible. My understanding of the process so far:
[*]apt install dpkg-dev flex bison rsync libssl-dev (if not already installed)
[*]mkdir build-directory && cd build-directory
[*]apt source linux-image-X.XX.X-XX-powerpc64le
[*]make oldconfig (to copy kernel config from existing entries)
[*]Edit .config and:
   CONFIG_LOCALVERSION=""  (<-- append custom kernel name in "")
[*]Make whichever changes you need to the kernel/modules
[*]make bindeb-pkg
Then finally:
[*]sudo dpkg -i linux-image-X.XX.X_X.XX.X-1_ppc64el.deb
[/list]

xilinder:
I have been using Midnight Commander for so long, not only on Linux, that it has become my goto default tool for kernel building, system snooping, etc.. I build my kernels as user, and install as root as necessary.
Many times I will remove them from /boot by moving to a folder in /home along with the modules....just in case.
Different strokes for different folks.

Now that my Radeon 7750 is working with 64k pagesize there is less urgency.

MauryG5:
Borley, I tried your procedure, practically the same as the one done with the command: make -j 32 KDEB_PKGVERSION = 1.-maury.ppc64le deb-pkg and the error that gives me at the end is always the same on the Kernels with long support of the 5.15.X series If I try to compile the recent ones then it works but unfortunately the recent kernels as we know do not work on Power, like 5.17.X and therefore I cannot use this procedure yet. The error here is this too: make [2]: *** [debian / rules: 7: build-arch] Error 2
dpkg-buildpackage: Error: debian / rules binary subprocess returned exit status 2
make [1]: *** [scripts / Makefile.package: 83: bindeb-pkg] Error 2
make: *** [Makefile: 1576: bindeb-pkg] Error 2

I don't understand why these 5.15 Kernels make this error, 5.15.2 does it, 5.15.30 does it and also the current 5.15.33. Only if you use the universal procedure like the one I've always used and which uses Xlinder, then it doesn't give you compiler errors but I don't know how to make the system recognize it in that case. I'm waiting for them to fix the new Kernel bug so I can use that ...

Navigation

[0] Message Index

[#] Next page

[*] Previous page