Re: Archiving on optical media
Hi,
> My conclusion: invest in more recent hardware.
> https://en.wikipedia.org/wiki/Blu-ray_Disc_recordable#Pricing
Those prices are slightly optimistic. But not too much.
> Tips to select a drive welcome.
Beware of "Combo" drives. Make sure the product description mentions
_write_ speed for BD-RE and BD-R, not only read speed for BD-ROM.
("Combo" drives are usually a bit cheaper than real BD burners.)
Buy from a seller who takes defective or wrongly chosen hardware back
without offering much resistance.
The quality of new drives varies much more individually than by the
brand or manufacturer. (Even 80 EUR are not enough to pay for a
convincing quality management in the factory.)
If my ASUS BW-16D1HT would die, i would by a new one of the same model.
It is the only one which writes more than 128 sessions to a single BD-R.
Another good drive which i have and is still at sale is LG BH16NS40.
I would not buy a new Pioneer BDR-S09 in the next years because mine
creates cracks on contemporary Verbatim BD-RE media after reading
them a dozen times. The cracks start at the inner hole and eventually
reach the recording area which then causes read failure.
I did not observe this damage with RITEK BD-RE, which are sold by about
any brand except Verbatim, or with older Verbatim BD-RE media.
(I'd blame the problem on the 10x read speed of the drive, its hard
grip on the medium, and the little engraved letters at the inner rim
of the modern Verbatim BD-RE. Forcing the drive to read more slowly
protects the victim media. It does not react on speed setting commands
but only slows down when i let the reader program wait between read
operations.)
I have no experience with slim BD drives which are sold in USB enclosures.
My USB attached drives are full-height "internal" drives which i put
into USB boxes which cost nearly as much as the drives.
("Man goennt sich ja sonst nichts." = I hardly grant myself anything else.)
Have a nice day :)
Thomas
Afficher la phrase de passe pour LVM-encrypt au boot
Salut, J'utilise lvm-encrypt sur mon laptop, mais il commence à présenter des faiblesses sur certaines touches, et je loupe régulièrement ma passphrase sans savoir pourquoi. Par ailleurs, il n'affiche pas si Caps Lock est locké ou non, donc un peu galère. Est-ce qu'il est possible de faire en sorte que le mot de passe que je tape soit affiché (plutôt que de mettre des étoiles) ? Parce qu'en pratique, je ne taperai pas ce mot de passe si quelqu'un regarde par dessus mon épaule (c'est pas trop mon contexte) ? Ou a minima de switcher pour voir ce que j'ai tapé ? Merci.
Archiving on optical media; was Re: Archiving content of a directory on a DVD-R.
From: "Thomas Schmitt" Date: Sun, 27 Feb 2022 09:15:04 +0100 > Ouch. That's a "Combo" drive which can write only CD-R and CD-RW. > With DVD media it can only do reading. ... > That would be the job of an older project of mine: > http://scdbackup.sourceforge.net/main_eng.html > http://scdbackup.sourceforge.net/scdbackup-0.9.2.tar.gz > > Installation and configuration are some work: > http://scdbackup.sourceforge.net/examples.html#configure ... > (Back in 1999 a 650 MB CD-R was a respectable backup medium, competing > with 500 MB QIC tapes and 1.2 GB DDS tapes. > Nowadays i use them only for small backups and for software delivery. > My bread-and-butter backup media are now "25 GB" BD-RE media. They are > not much more expensive than DVD+RW. Only the prices of burner drives > are significantly higher for BD than for DVD.) My conclusion: invest in more recent hardware. https://en.wikipedia.org/wiki/Blu-ray_Disc_recordable#Pricing Backing data in a 4 or 16 GB SD card is a modest requirement. PC Galore might have a drive in stock. http://www.pcgalore.com/ Tips to select a drive welcome. Thanks, ... P. -- mobile: +1 778 951 5147 VoIP: +1 604 670 0140 48.7693 N 123.3053 W
Re: Ho to properly rebuild single module?
On Sun, Feb 27, 2022 at 3:14 PM Grzesiek wrote: > Hi there, > > I need to apply the following > > https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u > and rebuild ib_qib. To rebuild I wrote the following script > . > But the module I get is almost 20 times bigger than the original one. > In the most general terms: Make sure that symbol tables for debugging purposes are excluded from the build. Make sure you are not linking statically but instead dynamically. > What is the proper way to build? > > Regards Greg > >
Re: Ho to properly rebuild single module?
On 2/27/22 23:13, Grzesiek wrote: > Hi there, > > I need to apply the following > https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u > > and rebuild ib_qib. To rebuild I wrote the following script > ($1 is the kernel version, i.e. 5.16.0-3) > > #!/bin/sh > #use in /usr/src > set -e -x > tar xJf linux-source-`echo $1| cut -f -2 -d.`.tar.xz > cp linux-headers-$1-amd64/.config linux-source-`echo $1| cut -f -2 -d.`/ > cp linux-headers-$1-amd64/Module.symvers linux-source-`echo $1| cut -f > -2 -d.`/ > cd linux-source-`echo $1| cut -f -2 -d.` > patch -p1 < ../ib_qib.patch > make menuconfig > # press exit and save > make kernelversion > make scripts > make prepare > make modules_prepare > make M=drivers/infiniband/hw/qib ib_qib.ko > > But the module I get is almost 20 times bigger than the original one. > > What is the proper way to build? > Hi Greg, I don't know how to build a single module but I use this Debian's howto to build Debian packages for Linux kernel. https://wiki.debian.org/BuildADebianKernelPackage HTH Kind regards Georgi
XFCE: ALT-F1 shows the wrong menu on Debian 11
Hi, Upon upgrading to Debian 11, the ALT+F1 key, which is assigned as a shortcut to xfce4-popup-applicationsmenu, according to XFCE's settings, no longer shows the applications menu and instead the app menu button on my panel appears pressed without the menu unfolded. A second key press shows the CTRL-ESC (xfdesktop --menu) menu, not the app menu. What's going on? I'm suffering from the same in both machines I have with Debian 11.
Re: Ho to properly rebuild single module?
On 2/27/22 22:21, Sven Hartge wrote: Grzesiek wrote: I need to apply the following https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u and rebuild ib_qib. The easiest way to ensure consistency would be to just rebuild the kernel package(s) as a whole: https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html#s4.2.3 Well, it takes ages. building a single module is like minute or two.
Re: Ho to properly rebuild single module?
Grzesiek wrote: > I need to apply the following > https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u > and rebuild ib_qib. The easiest way to ensure consistency would be to just rebuild the kernel package(s) as a whole: https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html#s4.2.3 S° -- Sigmentation fault. Core dumped.
Ho to properly rebuild single module?
Hi there, I need to apply the following https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u and rebuild ib_qib. To rebuild I wrote the following script ($1 is the kernel version, i.e. 5.16.0-3) #!/bin/sh #use in /usr/src set -e -x tar xJf linux-source-`echo $1| cut -f -2 -d.`.tar.xz cp linux-headers-$1-amd64/.config linux-source-`echo $1| cut -f -2 -d.`/ cp linux-headers-$1-amd64/Module.symvers linux-source-`echo $1| cut -f -2 -d.`/ cd linux-source-`echo $1| cut -f -2 -d.` patch -p1 < ../ib_qib.patch make menuconfig # press exit and save make kernelversion make scripts make prepare make modules_prepare make M=drivers/infiniband/hw/qib ib_qib.ko But the module I get is almost 20 times bigger than the original one. What is the proper way to build? Regards Greg
RE: strange boot messages
Thanks Kushal (and thanks Cindy Sue). Glad I’m not the only one seeing these! An observation to anyone who might be able to do something about this in the future... it would be less stressful or scary if these messages were said in such a way that they didn’t look like failures. Is ConditionFirstBoot something set when Debian boots for the first time after an install? It seems like this shouldn’t even be a message since it’s going to be printed into the log forever going forward! First boot, sure, say it’s true and do whatever but after that, imho, no need to print anything unless perhaps some verbose flag is set. Anyway, this stuff may not even be Debian specific, just my observations from a user (a sysadmin user). Hope this gets tidied up at some point. I’m happy and relieved you knew what these were and will now summarily ignore them in the future! Michael Grant From: Kushal Kumaran Sent: 27 February 2022 19:01 To: debian-user@lists.debian.org Cc: Michael Grant Subject: Re: strange boot messages cc-ing as requested On Sun, Feb 27 2022 at 09:01:31 AM, Michael Grant wrote: > I'm running Debian 11.2 stable on a Linode (a popular VPS). After a recent > update, I think from > around 25th of January, I'm starting to see some strange messages in > my logs: > > systemd[1]: First Boot Complete was skipped because of a failed > condition check (ConditionFirstBoot=yes). > > systemd[1]: getty on tty2-tty6 if dbus and logind are not available > was skipped because of a failed condition check > (ConditionPathExists=!/usr/bin/dbus-daemon). > > systemd[1]: Platform Persistent Storage Archival was skipped because > of a failed condition check > (ConditionDirectoryNotEmpty=/sys/fs/pstore). > > systemd[1]: Set Up Additional Binary Formats was skipped because all trigger > condition checks failed. > > systemd[1]: Store a System Token in an EFI Variable was skipped > because of a failed condition check > (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). > > systemd-udevd[277]: Network interface NamePolicy= disabled on kernel command > line, ignoring. > > systemd[1]: fast remote file copy program daemon was skipped because > of a failed condition check (ConditionPathExists=/etc/rsyncd.conf). > > > Are these just informational or are these problems I need to fix? I > did some searching but couldn't find much. > > Please CC me, I'm not currently on the list. > > Michael Grant These are normal. Several bits of bootup are conditional based on the ambient environment (whether it is a first boot, whether you have specific hardware features such as pstore or efi available, or whether you have particular binary packages are installed, etc.). My system has the same messages in slightly different format. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in First Boot Complete being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped. Feb 23 22:26:29 copper systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Feb 23 22:26:29 copper systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Feb 23 22:26:29 copper systemd[1]: Condition check resulted in File System Check on Root Device being skipped. I guess either a version or a configuration difference results in your system logging the actual condition. -- regards, kushal
Re: strange boot messages
cc-ing as requested On Sun, Feb 27 2022 at 09:01:31 AM, Michael Grant wrote: > I'm running Debian 11.2 stable on a Linode (a popular VPS). After a recent > update, I think from > around 25th of January, I'm starting to see some strange messages in > my logs: > > systemd[1]: First Boot Complete was skipped because of a failed > condition check (ConditionFirstBoot=yes). > > systemd[1]: getty on tty2-tty6 if dbus and logind are not available > was skipped because of a failed condition check > (ConditionPathExists=!/usr/bin/dbus-daemon). > > systemd[1]: Platform Persistent Storage Archival was skipped because > of a failed condition check > (ConditionDirectoryNotEmpty=/sys/fs/pstore). > > systemd[1]: Set Up Additional Binary Formats was skipped because all trigger > condition checks failed. > > systemd[1]: Store a System Token in an EFI Variable was skipped > because of a failed condition check > (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). > > systemd-udevd[277]: Network interface NamePolicy= disabled on kernel command > line, ignoring. > > systemd[1]: fast remote file copy program daemon was skipped because > of a failed condition check (ConditionPathExists=/etc/rsyncd.conf). > > > Are these just informational or are these problems I need to fix? I > did some searching but couldn't find much. > > Please CC me, I'm not currently on the list. > > Michael Grant These are normal. Several bits of bootup are conditional based on the ambient environment (whether it is a first boot, whether you have specific hardware features such as pstore or efi available, or whether you have particular binary packages are installed, etc.). My system has the same messages in slightly different format. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in First Boot Complete being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Feb 23 22:26:28 copper systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped. Feb 23 22:26:29 copper systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Feb 23 22:26:29 copper systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Feb 23 22:26:29 copper systemd[1]: Condition check resulted in File System Check on Root Device being skipped. I guess either a version or a configuration difference results in your system logging the actual condition. -- regards, kushal
Re: strange boot messages
On 2/27/22, Michael Grant wrote: > I'm running Debian 11.2 stable on a Linode (a popular VPS). After a recent > update, I think from > around 25th of January, I'm starting to see some strange messages in > my logs: > > systemd[1]: First Boot Complete was skipped because of a failed condition > check (ConditionFirstBoot=yes). > > systemd[1]: getty on tty2-tty6 if dbus and logind are not available was > skipped because of a failed condition check > (ConditionPathExists=!/usr/bin/dbus-daemon). > > systemd[1]: Platform Persistent Storage Archival was skipped because of a > failed condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). > > systemd[1]: Set Up Additional Binary Formats was skipped because all trigger > condition checks failed. > > systemd[1]: Store a System Token in an EFI Variable was skipped because of a > failed condition check > (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). > > systemd-udevd[277]: Network interface NamePolicy= disabled on kernel command > line, ignoring. > > systemd[1]: fast remote file copy program daemon was skipped because of a > failed condition check (ConditionPathExists=/etc/rsyncd.conf). > > > Are these just informational or are these problems I need to fix? I > did some searching but couldn't find much. > > Please CC me, I'm not currently on the list. I can't answer that, but I can share in this curiosity from within Bookworm. Goes back to 2022.02.20 for one partition and 2022.02.14 for the other Bookworm partition. The /var/log/sys* variants date back further than that which is notable since yours starting appearing even earlier. Our date difference could somehow be about the releases that we're each using. The date differences for mine stand out since both partitions are updated basically daily per each with minimal difference in the packages affected each day, mostly just libreoffice as the difference. Grepping dmesg for "skipped" found these: systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathExists=!/run/initramfs/fsck-root). systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed. Grepping /var/log/sys* for "skipped" shows that I likely received most, if not all, of the other ones you shared here. System is running, but it makes one wonder what might run even smoother if those weren't appearing. I'm not seeing a glaring "E" or "error" so there's that comfort. That word "failed" is interesting, but maybe it just means we have defaults set that are intended to speed up booting or something? Or not. Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
strange boot messages
I'm running Debian 11.2 stable on a Linode (a popular VPS). After a recent update, I think from around 25th of January, I'm starting to see some strange messages in my logs: systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes). systemd[1]: getty on tty2-tty6 if dbus and logind are not available was skipped because of a failed condition check (ConditionPathExists=!/usr/bin/dbus-daemon). systemd[1]: Platform Persistent Storage Archival was skipped because of a failed condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). systemd[1]: Set Up Additional Binary Formats was skipped because all trigger condition checks failed. systemd[1]: Store a System Token in an EFI Variable was skipped because of a failed condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). systemd-udevd[277]: Network interface NamePolicy= disabled on kernel command line, ignoring. systemd[1]: fast remote file copy program daemon was skipped because of a failed condition check (ConditionPathExists=/etc/rsyncd.conf). Are these just informational or are these problems I need to fix? I did some searching but couldn't find much. Please CC me, I'm not currently on the list. Michael Grant signature.asc Description: PGP signature
Re: problème PATH
Le 27/02/2022 à 09:10, Marc Chantreux a écrit : pi@rpiBullseye64:~ $ echo $GOTPATH * ce qui ne répond pas à ma question: je te laisse chercher ;) * ce qui me laisse à penser que tu n'as pas lu la doc ? est ce que export GOTHPATH=/usr/local/go go règle le problème par hasard (il se pourrait qu'une typo se soit glissé dans la dernière ligne)? Marc, Désolé pour l'erreur du $GOPATH Finalement j'ai tout réinstallé en suivant les indications trouvées sur https://go.dev/doc/install (enfin presque pour que ça marche) donc : pi@rpiBullseye64:~ $ go version go version go1.17 linux/arm64 merci pour ton aide et j'espère avancer avec çà.
Re: Which nvidia driver? xset +dpms issues. Is my video card dead/broken?
On 27.02.2022 04:57, R. Ramesh wrote: p nvidia-driver - NVIDIA metapackage p nvidia-driver-bin - NVIDIA driver support binaries p nvidia-driver-libs - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) p nvidia-driver-libs:i386 - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) p nvidia-vdpau-driver:i386 - Video Decode and Presentation API for Unix - NVIDIA driver Do I have a better driver that I should try? Is my video card gone bad? Your graphics adapter is modern enough so you should install "nvidia-driver" package. Additional essential packages are: "nvidia-driver-bin", "nvidia-driver-libs", "nvidia-kernel-support", "nvidia-kernel-dkms", and others. If all of them already installed, try to re-install "nvidia-kernel-dkms" package. It will rebuild DKMS module using kernel sources to match kernel in use. It is a good idea to do this, after every update of kernel image, to make sure a new kernel and DKMS module will be 100% compatible. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Créer TensoFlow LIte avec CMake
Bonjour, en parallèle de mon problème avec "go" (fil "problème PATH"). voilà pourquoi j'ai envisagé de changer de statégie pour installer tflite sur un rasberry pi. J'ai suivi la méthode donnée en titre sur " https://www.tensorflow.org/lite/guide/build_cmake; mais arrivé au bout ?que faire? soit j'ai loupé quelque chose pour que l'installation se fasse au fur et mesure dans l'arborescence /usr/.. soit il manque la fin : la commande pour installer le résultat duu répertoire tflite_build dans cette l'arborescence /usr/ .. et je n'en ai aucune idée. A lire les pages de tensorflow on comprend qu'elles sont faites pour des spécialistes et non pour des néophytes comme je le suis.
Re: Archiving content of a directory on a DVD-R.
Hi, pe...@easthope.ca wrote: > Drive type : vendor 'SONY' product 'CD-RW CRX320E' revision 'NYK2' Ouch. That's a "Combo" drive which can write only CD-R and CD-RW. With DVD media it can only do reading. So there is no use buying writable DVDs for it. > To squeeze the data, add -zisofs. This can help if the data are compressible by a factor 3. But that would be quite boring data. > xorriso -for_backup -dev /dev/sr0 \ > -update_r . / \ > -zisofs \ > -commit \ Command -zisofs sets parameters for the compression. It needs an argument or else it would eat the command -commit and complain that it is not a suitable parameter for -zisofs. To cause the files to be compressed you have to equip them by zisofs filters. For best and slowest compression choose zlib level 9: xorriso -for_backup -dev /dev/sr0 \ -update_r . / \ -zisofs level=9 \ -find / -type f -pending_data -exec set_filter --zisofs -- \ -commit \ ... -- > Likely xorriso provides a way to spread an archive over multiple CDs. > Documentation or example? That would be the job of an older project of mine: http://scdbackup.sourceforge.net/main_eng.html http://scdbackup.sourceforge.net/scdbackup-0.9.2.tar.gz Installation and configuration are some work: http://scdbackup.sourceforge.net/examples.html#configure (That's a reason why it is not in Debian. Another reason is that scdbackup gets installed by particular users, which is good for isolating their backup data but not suitable for the sysadmin-driven model of a Linux distro.) For building the software you need the C compiler and its companions from Debian package "build-essential". Compilation happens automatically during the run of ./CONFIGURE_CD or ./CONFIGURE_DVD. After the installation you may simply run scdbackup_home See http://scdbackup.sourceforge.net/examples.html#scdbackup_home The more general command scdbackup takes pathspecs as known from mkisofs and exclusions of paths: scdbackup /home /home2=/usr/home -not /home/guest This example backups /home and /usr/home . It gives on CD the name /home2 to the directory tree that is /usr/home on hard disk. Subdir /home/guest will not get into the backup. (Back in 1999 a 650 MB CD-R was a respectable backup medium, competing with 500 MB QIC tapes and 1.2 GB DDS tapes. Nowadays i use them only for small backups and for software delivery. My bread-and-butter backup media are now "25 GB" BD-RE media. They are not much more expensive than DVD+RW. Only the prices of burner drives are significantly higher for BD than for DVD.) Have a nice day :) Thomas
Re: problème PATH
> pi@rpiBullseye64:~ $ echo $GOTPATH > * ce qui ne répond pas à ma question: je te laisse chercher ;) * ce qui me laisse à penser que tu n'as pas lu la doc ? est ce que export GOTHPATH=/usr/local/go go règle le problème par hasard (il se pourrait qu'une typo se soit glissé dans la dernière ligne)? -- Marc Chantreux Direction du numérique de l'Université de Strasbourg Pôle de Calcul et Services Avancés à la Recherche (CESAR) http://annuaire.unistra.fr/p/20200
