Re: Whom to send bugreport?
On 2022-10-20, Tixy wrote: > On Thu, 2022-10-20 at 09:15 +0200, Hans wrote: >> After upgrading to a newer version of the kernel and of course newer kernel- >> headers, the build is failing now with a crash. > > Usually 'crashing' is caused by bugs in the programs doing the > crashing, so which program is crashing when building the module, the > compiler? I wonder what the third-party module might be, or is that irrelevant? > Or do you mean compilation of the module fails, in which case there > will be error messages from compiler, or other tools, indicating what > the error is with the source code being compiled. In this case, some > kernel changes that your third-party module may need modifying to > support. > --
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Hi, Mario Marietto wrote: > But the technique below worked : So your initrd problems are solved now and you managed to modify a Debian Live ISO by help of Cubic ? Have a nice day :) Thomas
Disabling the automatic resizing
Good day... Am working on a github repository to give a walkthrough on the setup of a device hosting a linux interface, this will extend all the way through docker and a web-server, however have yet to figure out how to disable the automatic resizing on a Raspberry Pi using your pre-configured .img Have already written the scripts for the resize and docker components for Ubuntu and Raspbian, however the resizing of the root partition on the debian side... well I can't do it because the automatic resizing configures the "/" partition to consume all of the available space, the scripts that I have already written disable the resizing on the Raspbian and Ubuntu "init" sides as one can easily grow a "live" partition but the kernel does not like being made smaller. Any insight on how to disable the "grow part" on the debian side will be much appreciated! -- Thank you Kind Regards Johnny de Villiers
Re: Disabling the automatic resizing
On Tue, 25 Oct 2022 at 00:09, Johnny de Villiers wrote: > Am working on a github repository to give a walkthrough on the setup of > a device hosting a linux interface, this will extend all the way through > docker and a web-server, however have yet to figure out how to disable > the automatic resizing on a Raspberry Pi using your pre-configured .img > Have already written the scripts for the resize and docker components for > Ubuntu and Raspbian, however the resizing of the root partition on the > debian side... well I can't do it because the automatic resizing > configures the "/" partition to consume all of the available space, the > scripts that I have already written disable the resizing on the Raspbian > and Ubuntu "init" sides as one can easily grow a "live" partition but the > kernel does not like being made smaller. > Any insight on how to disable the "grow part" on the debian side will be > much appreciated! Hello I assume you are using one of the images found here[1]? If that is correct, note this additional information (from [2]): Partitioning: The image ships as a 1500MB media, which means you can use it in any device of that size or greater. The first 300MB will be set aside as a boot partition. The image will resize to use all of the available space on the first boot — If you want it not to span the SD’s full size, after flashing it to your SD card, you can use fdisk to create a limiting dummy partition at the limit you want to set. After the first boot, just delete (or use!) that partition; the auto-resizer will not be run again. The script that performs this operation is in the image: /scripts/local-bottom/rpi-resizerootfs When I did this a while ago, I spent some time wrestling with this script to persuade it to work. I found that this script has some additional requirements not stated above: 1) There must be no additional partitions except the dummy partition, or else the script will hang at boot. 2) The dummy partition must include the last sector of the drive. Because if parted (in the script) reports any 'Free Space' at all after the dummy partition, the resize script will decide to do nothing. 3) The reason that "the auto-resizer will not be run again" is (if my memory is correct) that it does not exist outside of the initrd, which subsequently gets rebuilt to not include it. So if you want to read the script, you have to look into the initrd before booting the image. If you try to look for this script after booting, you will never find it. [1] https://raspi.debian.net/tested-images/ [2] https://raspi.debian.net/defaults-and-settings/
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Almost,but not fully. Because I've realized that as soon as a new kernel
has been installed by the user,logos and images should be added
automatically inside the initrd.img* file. For this reason,I've created the
bash script below. It works,I've tested it. Now I should understand where
to place it and which stage of the linux booting is the better one to
invoke it. I would like to read your suggestions. Thanks.
#!/bin/bash
if [ "`id -u`" -ne 0 ]; then
echo "Switching from `id -un` to root"
exec sudo "$0"
exit 99
fi
# Lets check the kernel version
function kernels-check() {
CURRENT_KERNEL_VERSION_LIQUORIX=$(uname --kernel-release | cut
--delimiter="-" --fields=3)
if [ "$CURRENT_KERNEL_VERSION_LIQUORIX" = "liquorix" ]; then
CURRENT_KERNEL_VERSION_GZ='initrd.img-'$(uname --kernel-release |
cut --delimiter="-" --fields=1-3)'-amd64.gz'
CURRENT_KERNEL_VERSION_NO_GZ='initrd.img-'$(uname --kernel-release
| cut --delimiter="-" --fields=1-3)'-amd64'
else
CURRENT_KERNEL_VERSION_GZ='initrd.img-'$(uname --kernel-release |
cut --delimiter="-" --fields=1-2)'-amd64.gz'
CURRENT_KERNEL_VERSION_NO_GZ='initrd.img-'$(uname --kernel-release
| cut --delimiter="-" --fields=1-2)'-amd64'
fi
echo $CURRENT_KERNEL_VERSION_GZ
echo $CURRENT_KERNEL_VERSION_NO_GZ
cp $CURRENT_KERNEL_VERSION_GZ /boot/old
gunzip /boot/old/$CURRENT_KERNEL_VERSION_GZ
echo /usr/share/plymouth/themes/homeworld/debian.png | cpio -H newc
-o -A -F /boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
echo /usr/share/plymouth/themes/homeworld/logo.png | cpio -H newc
-o -A -F /boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
echo /usr/share/plymouth/debian-logo.png | cpio -H newc -o -A -F
/boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
gzip /boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
cp /boot/old/$CURRENT_KERNEL_VERSION_GZ /boot
}
kernels-check
Il giorno lun 24 ott 2022 alle ore 13:36 Thomas Schmitt
ha scritto:
> Hi,
>
> Mario Marietto wrote:
> > But the technique below worked :
>
> So your initrd problems are solved now and you managed to modify a Debian
> Live ISO by help of Cubic ?
>
>
> Have a nice day :)
>
> Thomas
>
>
--
Mario.
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
I've renamed the previous script as "check-kernels" and I've saved it on
/usr/sbin ; I've added this line inside the file /etc/sudoers :
ALL ALL = NOPASSWD: /usr/sbin/check-kernels
and I've created the file below that I have saved inside the folder
/etc/xdg/autostart :
check-nvidia-kernel.desktop
[Desktop Entry]
Version=1.0
Type=Application
Name=check_kernels
GenericName=Add logo and images inside the installed kernel
Comment=Add logo and images inside the installed kernel
Exec=/usr/sbin/check-kernels
Icon=applications-biology
Path=/usr/sbin
Terminal=false
StartupNotify=false
Dunno if it is correct.
Il giorno lun 24 ott 2022 alle ore 19:14 Mario Marietto <
marietto2...@gmail.com> ha scritto:
> Almost,but not fully. Because I've realized that as soon as a new kernel
> has been installed by the user,logos and images should be added
> automatically inside the initrd.img* file. For this reason,I've created the
> bash script below. It works,I've tested it. Now I should understand where
> to place it and which stage of the linux booting is the better one to
> invoke it. I would like to read your suggestions. Thanks.
>
> #!/bin/bash
>
> if [ "`id -u`" -ne 0 ]; then
> echo "Switching from `id -un` to root"
> exec sudo "$0"
> exit 99
> fi
>
> # Lets check the kernel version
>
> function kernels-check() {
> CURRENT_KERNEL_VERSION_LIQUORIX=$(uname --kernel-release | cut
> --delimiter="-" --fields=3)
> if [ "$CURRENT_KERNEL_VERSION_LIQUORIX" = "liquorix" ]; then
> CURRENT_KERNEL_VERSION_GZ='initrd.img-'$(uname --kernel-release |
> cut --delimiter="-" --fields=1-3)'-amd64.gz'
> CURRENT_KERNEL_VERSION_NO_GZ='initrd.img-'$(uname --kernel-release
> | cut --delimiter="-" --fields=1-3)'-amd64'
> else
> CURRENT_KERNEL_VERSION_GZ='initrd.img-'$(uname --kernel-release |
> cut --delimiter="-" --fields=1-2)'-amd64.gz'
> CURRENT_KERNEL_VERSION_NO_GZ='initrd.img-'$(uname --kernel-release
> | cut --delimiter="-" --fields=1-2)'-amd64'
> fi
> echo $CURRENT_KERNEL_VERSION_GZ
> echo $CURRENT_KERNEL_VERSION_NO_GZ
> cp $CURRENT_KERNEL_VERSION_GZ /boot/old
> gunzip /boot/old/$CURRENT_KERNEL_VERSION_GZ
> echo /usr/share/plymouth/themes/homeworld/debian.png | cpio -H
> newc -o -A -F /boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
> echo /usr/share/plymouth/themes/homeworld/logo.png | cpio -H newc
> -o -A -F /boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
> echo /usr/share/plymouth/debian-logo.png | cpio -H newc -o -A -F
> /boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
> gzip /boot/old/$CURRENT_KERNEL_VERSION_NO_GZ
> cp /boot/old/$CURRENT_KERNEL_VERSION_GZ /boot
>
> }
>
> kernels-check
>
> Il giorno lun 24 ott 2022 alle ore 13:36 Thomas Schmitt
> ha scritto:
>
>> Hi,
>>
>> Mario Marietto wrote:
>> > But the technique below worked :
>>
>> So your initrd problems are solved now and you managed to modify a Debian
>> Live ISO by help of Cubic ?
>>
>>
>> Have a nice day :)
>>
>> Thomas
>>
>>
>
> --
> Mario.
>
--
Mario.
Re: Disabling the automatic resizing
Hi Johnny I am sending you a copy of this message in CC in case you are not subscribed to the mailing list. However, can you please ensure that your reply goes to the mailing list, not just to me. Because this is a community discussion, not a private one. So I have copied your private reply below here so that the community does not miss part of the conversation. My reply is at the bottom of this message. On Tue, 25 Oct 2022 at 06:36, Johnny de Villiers wrote: > > Hi David > > Thank you for the fast reply... Attempted to do just that but instead of > fdisk was using gparted and the system did just what you said... IT HUNG > ITSELF;-P > > However when I found this to be the case I went ahead and reflashed, booted > and then after all was done attempted the resizing... however upon the next > reboot the partition was resized again!? Then while describing this to a > friend an idea popped up, the script was alway looking for the end of the > disk, right?! > > The script is looking for the end so why not swap the second and third > partitions places? Attempted it and... ... ... what would you know it worked! > Not ideal I know but. You say that the resize function does not exist outside > of "initrd", what are the chances that you guys would be able to add a > function/variable to prevent the resize? In raspbian this is achieved by > removing the init function on the cmdline.txt and in ubuntu by adding a > > growpart: > mode: disabled > > to the usrconfig that gets parsed to the cloud-init?! Or should I just have a > look into removing the " /scripts/local-bottom/rpi-resizerootfs " before > boot? > > Looking forward to hearing back from you! I am just a user of the image, not a developer. I just shared with you some experience that I had when using the image. If you want to have a conversation regarding changes to the image, you will need to contact the developer/team producing the image. I don't have any more information about this than I included in my previous message.
