• Unidentified subject!

    From =?utf-8?B?5paw5bm557ea44GV44GP44KJ?@21:1/5 to All on Mon Oct 7 12:40:01 2024
    I'm using the latest stable version of Debian 12 on a lenovo D330 Celeron N4020 model, but the auto-rotate is inverted, it won't boot up from lock, it starts up with a black screen, and sleep is the same.
    I'm pretty sure the same thing happens when the screen is off.
    Other than that, I have no complaints, so please improve them.
    If you have any additional information, I would be happy to provide it further.

    Translated with DeepL.com (free version)
    iPhoneから送信

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Schmitt@21:1/5 to BALDO on Sun Mar 23 11:40:01 2025
    Hi,

    BALDO wrote:
    We work with BD images, but is it
    possible to merge these images and put them on an external m.2?

    Aha. Once in a year this question pops up.
    Three years ago i invested some shell programming effort and tested it
    with amd64 ISOs. See:

    https://wiki.debian.org/MergeDebianIsos


    Actually the script
    https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos
    is hanging between the libisoburn package and the debian-cd package.
    I personally think that it should get under the control of debian-cd,
    because it mainly cares for Debian-specific entrails of the ISOs. But
    the maintainer of debian-cd is reluctant to take it, because it
    consists of 1136 lines of shell code.
    So probably it will in future become a "binary" package of libisoburn.


    Debian does not have a general ISO with the entire OS,

    To my knowledge Debian is the only distro which offers all its
    packages in sets of ISO images. Kudos.


    I can only issue guesses about the following question:

    If we create
    the first bootable disk on the external memory with Balena Etcher, then manually add the packages in the pool folder can it work?

    I understand Balena Etcher is a plain image copier, with the same
    result as dd or cp (but hopefully protecting people from spoiling the
    system disk).

    So you would put the ISO onto the storage device so that it can boot.
    The pool folder would be put in a writable filesystem on a partition
    of the same storage device.
    After copying the ISO, you would have to add a partition to the ISO's
    peculiar partition table. You would have to make sure that no GPT
    backup table is at the end of the storage device, remaining from a
    previous device content. Then you need a partition editor which ignores
    the invalid GPT header block of the ISO. (It exists because of an old
    bug of virtual EFI implementation OVMF which refused to boot without
    this header block.)
    The new partition needs to be added to the MBR ("DOS") partition table.

    Possibly it would be easier if you let program Rufus unpack the ISO
    content into a bootable FAT filesystem on the storage device and copy
    the pool tree into that filesystem.

    However, filling the pool is topic of several tools
    https://wiki.debian.org/DebianRepository/Setup


    I myself would not want to do either. So i used my xorriso-fu for the merge_debian_isos script.


    Have a nice day :)

    Thomas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew M.A. Cater@21:1/5 to BALDO on Sun Mar 23 14:40:02 2025
    On Sun, Mar 23, 2025 at 10:19:18AM +0100, BALDO wrote:
    Hi everyone, I have a question for you. We work with BD images, but is it possible to merge these images and put them on an external m.2?

    I think you've been given an answer. I would always suggest using a USB
    because this is more straightforward to use.

    Optical media isn't "completely" gone but each of the Debian bootable images can be written directly to a USB stick. The images are iso-hybrid so will
    boot directly off the medium.

    In order to make the BD / DLBD disks, you need to use a mirror and jigdo
    or similar. As somebody testing images when point releases are made, I
    would suggest against using larger images than the DLBD - there is the likelihood of bit errors to ruin your image when writing many GB.

    The bootable DLBD and a mirror mean that you can always install an up to date Debian. In some sense, the images are out of date one day after they are released, so you need a mirror to keep things current..

    If we create the first bootable disk on the external memory with Balena Etcher, then manually add the packages in the pool folder can it work?
    Today using optical media such as CDs and DVDs is obsolete, and Debian does not have a general ISO with the entire OS, even if it were 125GB, it would not be a problem for us. In fact, it would make our life easier. How can we solve this problem? Could the procedure described above work? We need a way to merge all the BDs and put them on an external pendrive/hdd. Thanks guys for your support/advice.

    Please don't post in HTML to this list if you can avoid it. Thanks.
    Similarly, the main language here is English but I can at least wish you well.

    Ciao a tutti voi, spero che possiamo aiutarvi con questo. Auguri!!

    Andrew Cater
    ([email protected])

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Schmitt@21:1/5 to Andrew M.A. Cater on Sun Mar 23 15:50:02 2025
    Hi,

    Andrew M.A. Cater wrote:
    As somebody testing images when point releases are made, I
    would suggest against using larger images than the DLBD - there is the likelihood of bit errors to ruin your image when writing many GB

    There is a file md5sum.txt in the ISOs to check the transport integrity
    of the packages and some other files.

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011343#180
    gives my re-narration of the checksum run of internal Debian tool
    https://packages.debian.org/unstable/cdrom-checker
    :

    (cd /mnt/iso
    cat md5sum.txt | while read line
    do
    if echo -n "$line" | md5sum -c 1>/dev/null 2>&1
    then
    dummy=dummy
    else
    echo "BAD: $line"
    fi
    done ) 2>&1 | wc

    I dimly remember that cdrom-checker is part of a check offered by the
    installer in the ISO.
    This run with mounted debian-12.7.0-amd64-netinst.iso reports a match:
    gunzip < /mnt/iso/install.amd/initrd.gz | fgrep 'cdrom-checker'

    But that's much more your realm than mine.


    Damage after the end of the directory tree area of a Debian ISO hits
    only the content of particular data files. A single byte can spoil not
    more than one data file (and its hardlink siblings, like with the
    three vmlinuz files in the netinst ISO).
    With debian-11.2.0-amd64-DVD-2.iso the size of the directory tree
    is 6 MB. Multiplied by 21 DVD ISOs for 12.10.0 = ~ 126 MB.


    Have a nice day :)

    Thomas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Christensen@21:1/5 to BALDO on Sun Mar 23 18:30:01 2025
    On 3/23/25 02:19, BALDO wrote:
    Hi everyone, I have a question for you. We work with BD images, but is it possible to merge these images and put them on an external m.2? If we create the
    first bootable disk on the external memory with Balena Etcher, then manually add
    the packages in the pool folder can it work? Today using optical media such as
    CDs and DVDs is obsolete, and Debian does not have a general ISO with the entire
    OS, even if it were 125GB, it would not be a problem for us. In fact, it would
    make our life easier. How can we solve this problem? Could the procedure described above work? We need a way to merge all the BDs and put them on an external pendrive/hdd. Thanks guys for your support/advice.


    Perhaps Ventoy?

    https://www.ventoy.net/en/index.html?ref=itsfoss.com


    David

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)