Re: Erreur nvidia suite upgrade noyau 6.6.18

[Basile Starynkevitch]

On 2/10/24 15:10, ajh-valmer wrote:

On Friday 09 February 2024 18:47:09 ajh-valmer wrote:

On Tuesday 06 February 2024 12:50:21 Fabien Dubois wrote:

apt upgrade :
c'est le module Nvidia qui empêche l'installation du noyau 6.6.18.
Mon pilote Nvidia 470 est celui pêché sur le dépôt free de Debian.
Je n'ai jamais réussi à installer un pilote "nouveau".



Il existe pourtant un paquet (sur Debian/Sid)

i A xserver-xorg-video-nouveau  - X.Org X server -- Nouveau display 
driver



J'ai donc fait un test sur une sauvegarde sous Bookworm,
en purgeant nvidia.
Cette fois l'upgrade se fait bien avec le noyau 6.6.18.
J'ai tenté de réinstaller le pilote Nvidia 470, niet idem.
Par contre, j'ai le mode graphique mais qu'en mode 1024X768 max
(trop faible).
Je désire maintenant un howto pour installer le pilote "nouveau".
Cette commande ci-dessous m'affiche une erreur :
dpkg --configure -a|--pending
Je n'ai plus la commande nvidia-detect.

https://wiki.debian.org/fr/NvidiaGraphicsDrivers
https://forums.debian.net/viewtopic.php?t=16
https://debian-facile.org/doc:materiel:cartes-graphique:nvidia:accueil :

ne m'aident pas du tout.

Bonjour,
Dommage que personne sur la liste ne puisse m'aider pour installer
le pilote graphique "Nouveau" et qu'il soit fonctionnel.
Devrais-je être obligé d'acheter une nouvelle carte vidéo plus récente ?


Nvidia a mauvaise réputation dans le monde Linux (sur PC portable ou 
fixe). On peut googler "fuck nvidia".


Si vous achetez une nouvelle carte, considérez plutôt une carte AMD/ATI 
car AMD a payé des développeurs de pilotes libres pour Linux, et je 
crois que Nvidia (l'entreprise) est réticent à aider même le projet 
Nouveau (qui  travaille par rétro-ingénierie).


Et définissez d'abord votre besoin. En particulier avez vous besoin de 
faire du calcul hybride (OpenCL/OpenACC) sur la carte graphique, ou bien 
juste d'afficher correctement du texte et regarder des vidéos à une 
résolution pas trop élevée.


Il faut aussi savoir si vous avez un ou plusieurs écrans.

Personnellement, avec deux écrans, je mets plusieurs jours à les 
configurer correctement. Sur un ordinateur fixe avec deux cartes 
graphiques AMD.


root@rimski:/# lspci|grep VGA
0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
42:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Barts PRO [Radeon HD 6850]


J'utilise nvidia uniquement sur un ordinateur portable (sous Ubuntu).


Bonne chance en tout cas.


--
Basile Starynkevitch 
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
See/voir:   https://github.com/RefPerSys/RefPerSys

Re: shred bug? [was: Unidentified subject!]

[tomas]

On Sat, Feb 10, 2024 at 07:10:54PM -0500, Greg Wooledge wrote:
> On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote:
> > 2024-02-10 16:03:50 dpchrist@laalaa ~
> > $ shred -s 1K - | wc -c
> > shred: -: invalid file type
> > 0
> > 
> > 
> > It looks like a shred(1) needs a bug report.
> 
> I'm confused what you expected this command to do.  You wanted to
> "destroy" (by overwriting with random data) a pipe to wc?  What
> would that even look like?

What Thomas was trying to do is to get a cheap, fast random number
generator. Shred seems to have such.

> The basic premise of shred is that it determines the size of the file,
> then writes data over it, rewinds it, and repeats this a few times.
> A pipe to a process has no size, and can't be rewound.

That's right: stdout is a (potentially) infinite file, so only one
pass (-n 1, as Thomas put in the command line) really makes sense.
Unless you are into transfinite numbers, that is :-)

> Declaring a pipe to be an "invalid file type" for shredding sounds
> pretty reasonable to me.

This is one of those cases of the toolmaker knowing better than the
tool user. One of the things I like UNIX is that this attitude isn't
that widespread (it is slowly spreading, alas). I much prefer those
tool makers who say "surprise me".

Of course, helping people to not shoot themselves in the foot is
also a honourable endeavour. So "you are trying to shred a pipe.
Use option -f for that (see the manual page" would be fully OK
in my book.

I don't like opinionated software. It's messy enough as it is
when people have opinions :-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.

[tomas]

On Sun, Feb 11, 2024 at 12:48:52AM -0500, Jeffrey Walton wrote:
> On Sat, Feb 10, 2024 at 12:27 AM Maureen Thomas  wrote:
> >
> 
> Do you really _not_ know how to use email?
> 
> Or is this Phase II of the Sophie experiment?

Jeffrey, please. Having a bad day?

Cheer up
-- 
tomás


signature.asc
Description: PGP signature

Re: Debian bookwork 12.4 installation wifi card not being detected

[Exeonz]

I just tried using Trixie and it's the same issues. Seems that the 
installer isn't even recognizing wifi card at all  so no matter what 
drives I give it refuses to use them. *No Ethernet card was found on the 
system.* I think my only option is using wifi usb adapter that works, I 
already tried using usb wifi adapter that I had at hand but didn't work 
because it too uses proprietary driver.

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.

[Jeffrey Walton]

On Sat, Feb 10, 2024 at 12:27 AM Maureen Thomas  wrote:
>

Do you really _not_ know how to use email?

Or is this Phase II of the Sophie experiment?

Jeff

Re: hexchat being discontinued?

[Dan Ritter]

Default User wrote: 
> Well, it seems that hexchat is being discontinued. 
> IMHO, it is/was the only IRC client that was actually usable. 
> 
> Any recommendations for a GOOD alternative?

I like weechat. Some people like quassel.

Hexchat is packaged in bookworm, so there's no reason for you to
panic until it's removed.

-dsr-

Re: Debian weather bug

[Greg Marks]

> > I have a bug report but am not sure which package it should be filed
> > against.  The Weather Report application, version 1.24.1, is affected,
> > as is the weather reported by the Clock application, version 1.24.1, in
> > the MATE desktop environment.  Neither reports the correct weather, and
> > the log files contain the error "Failed to get METAR data."  I suspect
> > the issue is related to a URL change described in these two threads:
> > 
> >
> > https://www.reddit.com/r/flying/comments/179zm7o/for_those_of_you_who_made_metar_live/
> >https://www.reddit.com/r/flying/comments/179bmcj/metar_map_issues/
> > 
> > How should this be reported?
> > 
> 
> Update: the following are relevant lines from /var/log/syslog:
> 
>Oct 19 18:10:09 debian mateweather-app[3922]: Failed to get METAR data: 
> 404 Not Found.
>Oct 19 18:10:09 debian mateweather-app[3922]: Failed to get IWIN forecast 
> data: 404 Not Found
>Oct 19 18:10:09 debian mateweather-app[3922]: Source ID 50501 was not 
> found when attempting to remove it
>Oct 19 18:14:54 debian mateweather-app[3922]: Failed to get METAR data: 
> 404 Not Found.
>Oct 19 18:14:54 debian mateweather-app[3922]: Source ID 50562 was not 
> found when attempting to remove it
>Oct 19 18:23:55 debian clock-applet[3927]: Failed to get METAR data: 404 
> Not Found.
> 
> Note that two different applications are affected by this bug.

The latest upgrade of the packages libmateweather-common and
libmateweather1 (both to version 1.24.1-1+deb11u1) has fixed the
problem; the two weather applications are now functioning properly.

Best regards,
Greg Marks


signature.asc
Description: PGP signature

Re: Home UPS recommendations

[hw]

On Sat, 2024-02-10 at 18:40 +, Joe wrote:
> On Sat, 10 Feb 2024 16:45:29 +0100
> hw  wrote:
> 
> 
> > 
> > The cheap APC models seem to produce a lot more heat, and their
> > batteries don't seem to last as long.  They work and they're not
> > really a good deal.  I don't have test equipment for UPCs, but you can
> > feel how warm they get and see how cheaply they're built without
> > special equipment.
> > 
> 
> It's quite surprising how many complaints about swollen UPS batteries
> there are around the Net. Given the fairly light duties of the batteries
> almost all of the time, this is pretty well certain to be caused by
> overheating due to incompetent charging. Batteries, particularly
> lead-acid types, are not exactly new technology, and the correct
> charging of them is well understood.
> 

The batteries in the cheap ones were not swollen.  They're just no fun
to replace.

Perhaps they use cheaper components that are less efficient and thus
create more heat.  That doesn't necessarily affect the batteries.

hexchat being discontinued?

[Default User]

:(

Well, it seems that hexchat is being discontinued. 
IMHO, it is/was the only IRC client that was actually usable. 

Any recommendations for a GOOD alternative?

 

Re: Debian bookwork 12.4 installation wifi card not being detected

[Timothy M Butterworth]

On Sat, Feb 10, 2024 at 1:07 PM Exeonz  wrote:

> Hey thanks for your time in advance. I'm trying to install debian bookworm
> 12.4 on MacbookAir7,2 that doesn't have an ethernet port and the installer
> doesn't recognize it's wifi card and what drivers it needs for the card to
> work. From searching the web I found that it uses Broadcom BCM 4360
> wireless network adapter and requires broadcom-sda-dkms firmware drivers to
> function. The installer doesn't detect the wifi card and none of the
> drivers from the select list work and when I use 2nd bootable USB formatted
> as FAT32 with broadcom-sda-dkms firmware drivers saved to root and firmware
> folder it doesn't accept drivers and gives out error "ethernet card not
> found" I've looked through entire debian wiki and other wikis and forums
> like arch wiki and found no answers anywhere. I have successfully installed
> ubuntu on this macbook air and it works just fine with the wifi card. Could
> you please shed some light on how I can possibly install debian on this
> macbook air.
>
> Some other things that I've tried that didn't work.
> Every available driver from the install list.
> Older non-free debian version 11.8.0 because I thought it would have
> drivers but it didn't work either.
> Downloading all firmware from https://cdimage.debian.org/cdimage/firmware/
> onto USB formatted as FAT32 in root and firmware folder
> Using command like during installation for extra option to load drivers
> off USB. (this command doesn't seem to work on bookwork 12.4)
> https://wiki.debian.org/Firmware
>
>
>
> *Installation+Archive+USBStickpreseed/early_command="modprobe vfat ; sleep
> 2 ;mount /dev/disk/by-label/FIRMWARE /media ;cp -a /media/firmware /lib"*
> Using rtl8812au-5.2.20 firmware drivers
> Ripping out firmware drivers from ubuntu install that works fine with this
> wifi card and putting it on same USB
> *bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu10~22.04.1_amd64*
>
Try installing Trixie
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/. Debian 12
is starting to show its age. It uses the LTS kernel 6.1. You really have
two choices:

1. Install Debian Bullseye with a working USB WiFi adapter. Configure
Debian backports and upgrade the kernel and install the needed drivers.

2. Install Debian Testing (Trixie). Trixie has a much newer kernel and the
latest drivers. It also contains newer versions of the other software as
well. I ran Debian testing for Debian 12 for a little over a year until
Bullseye was released!




>
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm

[hw]

https://fostips.com/6-ways-create-bootable-debian-ubuntu-usb-installer/


On Sat, 2024-02-10 at 21:48 +, Maureen Thomas wrote:
>  So can I please get some help.  I have a portable CD/DVD and I made a USB 
> with a ISO on it.  The computer does not have a cd/dvd burner but I have a 
> portable one.  Can some one tell me if there are any special things I need to 
> do to put Debian 12 on this machine.  I really hate windows and need to get 
> it gone.  Your help is always appreciated by this old lady.  Thank you in 
> advance>
> On Friday, February 9, 2024 at 08:10:24 PM EST, Maureen Thomas 
>  wrote:  
>  
>  
> ,, 1  

Re: shred bug? [was: Unidentified subject!]

[David Christensen]

On 2/10/24 16:10, Greg Wooledge wrote:

On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote:

2024-02-10 16:03:50 dpchrist@laalaa ~
$ shred -s 1K - | wc -c
shred: -: invalid file type
0


It looks like a shred(1) needs a bug report.


I'm confused what you expected this command to do.  You wanted to
"destroy" (by overwriting with random data) a pipe to wc?  What
would that even look like?

The basic premise of shred is that it determines the size of the file,
then writes data over it, rewinds it, and repeats this a few times.
A pipe to a process has no size, and can't be rewound.

Declaring a pipe to be an "invalid file type" for shredding sounds
pretty reasonable to me.



The documentation is confusing:

On 2/10/24 16:05, David Christensen wrote:
> 2024-02-10 16:03:42 dpchrist@laalaa ~
> $ man shred | grep 'If FILE is -'
> If FILE is -, shred standard output.


David

Re: find and it uncommon syntax - grrrrrrrrr

[gene heskett]

On 2/10/24 16:07, Greg Wooledge wrote:

On Sat, Feb 10, 2024 at 02:58:24PM -0600, Nicholas Geovanis wrote:

On Sat, Feb 10, 2024, 2:46 PM gene heskett  wrote:


Greetings;

I have misplaced file someplace in /home/gene.
its name is bpim5*shelf.scad



Assuming that you are searching in the current working directory:
  find bpim*  -print | grep 'shelf.scad'


That's not correct.  The argument(s) that immediately follow find should
be the starting point(s) where it will begin its search.  Normally these
would be directories, especially the "." directory, which is actually
the default in GNU find (but not a default in POSIX find).

This command would only work if the file Gene's looking for happens to
be in his home directory, *or*, if the file he's looking for happens to
be underneath a *directory* whose name matches the bpim* glob.  This is
possible, but I wouldn't count on it.

Especially here. I resaved it, after a couple mods, in 
3dp-stf/genes-nas.  So searching thru all the children of "." should be 
the expected behavious. But finding that fraudulent pile of 2T disks was 
as bogus as a $3 bill, upsets my plans. The only usb-sata adapter I 
trust is StarTech, and its cable is 3x longer than I need. This bogus 
drive came sealed in a case that I had printed supports for that fit in 
2 shelf spaces, leaving room in the bottom of the care for a psu.  The 
sata package is bigger but would take 3 spaces for 6 of them, exiling 
the psu external to the cage.  So this job now printing is 4 more 
shelves, w/o the pi bolt pattern.  3dprinting is hard on memory, I've 
12G of 3dp.stf now.  Slicers and such are plain stupid, generating as 
much as 2 gigabytes for one complex part that takes 3 days to run. I've 
written 3 days jobs for a milling machine In 90 LOC because linuxcnc 
understands loops, none of the slicers or machines do, so the file you 
feed the printer is totally unrolled. And 10 to 30 times the size needed 
if the part file was converted from additive to subtractive.  It may get 
there, but probably after I miss roll call.


Thanks Greg.  Take care.

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: shred bug? [was: Unidentified subject!]

[Greg Wooledge]

On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote:
> 2024-02-10 16:03:50 dpchrist@laalaa ~
> $ shred -s 1K - | wc -c
> shred: -: invalid file type
> 0
> 
> 
> It looks like a shred(1) needs a bug report.

I'm confused what you expected this command to do.  You wanted to
"destroy" (by overwriting with random data) a pipe to wc?  What
would that even look like?

The basic premise of shred is that it determines the size of the file,
then writes data over it, rewinds it, and repeats this a few times.
A pipe to a process has no size, and can't be rewound.

Declaring a pipe to be an "invalid file type" for shredding sounds
pretty reasonable to me.

Re: shred bug? [was: Unidentified subject!]

[David Christensen]

On 2/10/24 04:40, to...@tuxteam.de wrote:

On Sat, Feb 10, 2024 at 11:38:21AM +0100, Thomas Schmitt wrote:

[...]


But shred(1) on Debian 11 refuses on "-" contrary to its documentation:
   shred: -: invalid file type
A non-existing file path causes "No such file or directory".


Hmm. This looks like a genuine bug: the man page mentions it.

Also, /dev/stdout as target runs into the very same problem.

Cheers



Testing:

2024-02-10 16:01:54 dpchrist@laalaa ~
$ cat /etc/debian_version ; uname -a
11.8
Linux laalaa 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) 
x86_64 GNU/Linux


2024-02-10 16:02:34 dpchrist@laalaa ~
$ bash --version | head -n 1
GNU bash, version 5.1.4(1)-release (x86_64-pc-linux-gnu)

2024-02-10 16:02:48 dpchrist@laalaa ~
$ shred --version | head -n 1
shred (GNU coreutils) 8.32

2024-02-10 16:03:42 dpchrist@laalaa ~
$ man shred | grep 'If FILE is -'
   If FILE is -, shred standard output.

2024-02-10 16:03:50 dpchrist@laalaa ~
$ shred -s 1K - | wc -c
shred: -: invalid file type
0


It looks like a shred(1) needs a bug report.


David

Re: testing new sdm drive continued

[David Christensen]

On 2/10/24 08:25, gene heskett wrote:

I managed to kill f3write, so f3probe could access it:
ene@coyote:/mnt/disktest$ sudo f3probe --destructive --time-ops /dev/sdm
F3 probe 8.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.

WARNING: Probing normally takes from a few seconds to 15 minutes, but
  it can take longer. Please be patient.

Bad news: The device `/dev/sdm' is a counterfeit of type limbo

You can "fix" this device using the following command:
f3fix --last-sec=124050943 /dev/sdm

Device geometry:
  *Usable* size: 59.15 GB (124050944 blocks)
     Announced size: 1.91 TB (409600 blocks)
     Module: 2.00 TB (2^41 Bytes)
     Approximate cache size: 1.00 MB (2048 blocks), need-reset=no
    Physical block size: 512.00 Byte (2^9 Bytes)

Probe time: 2.07s
  Operation: total time / count = avg time
   Read: 311.9ms / 4212 = 74us
  Write: 1.75s / 24740 = 70us
  Reset: 1us / 1 = 1us
gene@coyote:/mnt/disktest$
No faster than it is, its not worth the f3fix effort, I can buy 
reputable, much faster sd cards at 1/3rd the cost.



Okay -- here is the thread Thomas referenced.  It has not hit the 
archive servers yet.



The f3probe results are bad news, but not unexpected.  At least you have 
a definite answer that you can send to the seller and/or Amazon (?).



David

Re:[ Era (Sin título)] Compartir archivos con Samba

[Julián Daich]

El 10/2/24 a las 11:03, Camaleón escribió:



El tipo (rol) de servidor samba será «standalone server» si no has
cambiado nada más, que entiendo es lo correcto.



No cambié nada, pero vale la pena verificar si vale de algo¿ en dónde me 
fijo?



Las rutas con acentos no me terminan de convencer (Vídeos, Música),
crea mejor una de prueba sin caracteres extendidos, p. ej., en Ubuntu,
«/home/julian/prueba» o el directorio de «Documentos« si ya lo tienes
creado en «/home/julian/Documentos», y la añades en la configuración de
Samba (recuerda reiniciar el servidor samba cuando hags cambios).



Hice la prueba. Se comporta igual con directorios sin tilde.


En el cliente hago smb://nombre_del_equipo


Hum... a ver, prueba mejor a conectar desde el cliente con:

smb://julian@ip.servidor.samba.ubuntu/

Para que te liste los recursos/carpetas disponibles.


El mismo efecto usando el nombre del equipo o la IP. Por lo menos 
reconoce si son válidos. Probé darle rutas erróneas. Probé también con 
otro cliente con XFCE4 en Sid y fueron los mismos mensajes.


usuario@ no cambia mucho el comportamiento. Solo un campo menos en el 
menú de diálogo.


Probé también la ruta completa a la carpeta smb://equipo/carpeta. A 
veces da error de parámetros incorrectos y otras veces dice que la 
carpeta no existe.


Creo que el problema está en el servidor. Un Debian 12.

  

 Veo que esto de compartir archivos sigue siendo igual
de complicado como 20 años atrás.


Igual no... ¡peor! :-)

Ahora tienes que lidiar con la versión de NTLM entre cliente y servidor
cuando trabajas con equipos y sistemas operativos antiguos (Windows XP,
etc...). Un horror.



Usé NFS entre servidores de red, pero también me dio problemas cuando lo 
quise usar en casa.



Por exigencias de la red, tengo Samba en un servidor con Debian 12 y me
contecto desde mi equipo habitual (Debian 11) sin problemas


¿ podrías pasar tu configuración?


, pero con
dos linux en juego, prefiero conectarlos mediante SFTP, va como la seda
(eso sí, necesitas que SSH esté configurado y ejecutándose en el
servidor pero entiendo que lo estará).

sftp://julian@ip.servidor.ubuntu



Si KDE-Connect tendría la opción de explorar archivos entre computadoras 
todo sería más fácil- A mi solo me funciona de computadora a teléfono.


Saludos,

Julián

Te djo la wiki de Archlinux que siempre viene bien revisar las cosas a
configurar y/o tener en cuenta:

Samba
https://wiki.archlinux.org/title/samba

Saludos,



--
Julian Daich 

Re: Unidentified subject!

[David Christensen]

On 2/10/24 10:28, Thomas Schmitt wrote:

In the other thread about the /dev/sdm test:

Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32
but is taking a few bytes now and then.
[...]
$ ls -l
total 40627044
[...]
$ sudo f3probe --destructive --time-ops /dev/sdm
Bad news: The device `/dev/sdm' is a counterfeit of type limbo
Device geometry:
 *Usable* size: 59.15 GB (124050944 blocks)
Announced size: 1.91 TB (409600 blocks)
...
Probe time: 2.07s



Which other thread?  Please provide a URL to archived post.


So, the 2 TB USB SSD's are really scam 64 GB devices?


David

Re: Unidentified subject!

[David Christensen]

On 2/10/24 02:38, Thomas Schmitt wrote:

I have an own weak-random generator, but shred beats it by a factor of 10
when writing to /dev/null.



As a baseline, here is a 2011 Dell Latitude E6520 with Debian generating 
a non-repeatable 1 GiB stream of cryptographically secure pseudo-random 
numbers:


2024-02-10 14:10:27 dpchrist@laalaa ~
$ lscpu | grep 'Model name'
Model name: Intel(R) Core(TM) i7-2720QM CPU @ 
2.20GHz


2024-02-10 14:01:25 dpchrist@laalaa ~
$ cat /etc/debian_version ; uname -a
11.8
Linux laalaa 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) 
x86_64 GNU/Linux


2024-02-10 14:01:47 dpchrist@laalaa ~
$ bash --version | head -n 1
GNU bash, version 5.1.4(1)-release (x86_64-pc-linux-gnu)

2024-02-10 14:13:08 dpchrist@laalaa ~
$ time dd if=/dev/urandom bs=8K count=128K | wc -c
1073741824
131072+0 records in
131072+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 4.30652 s, 249 MB/s

real0m4.311s
user0m0.107s
sys 0m4.695s


If the OP has a known good storage device of equal or larger size than 
the UUT(s), I suggest using /dev/urandom and tee(1) to write the same 
CSPRN stream to all of the devices and using cmp(1) to validate.



I use Perl.  When I needed a CSPRNG, I searched and found:

https://metacpan.org/pod/Math::Random::ISAAC::XS


Using Perl and Math::Random::ISAAC::XS to generate a repeatable stream 
of cryptographically secure pseudo-random numbers:


2024-02-10 14:09:12 dpchrist@laalaa ~
$ perl -v | head -n 2 | grep .
This is perl 5, version 32, subversion 1 (v5.32.1) built for 
x86_64-linux-gnu-thread-multi


2024-02-10 14:09:53 dpchrist@laalaa ~
$ perl -MMath::Random::ISAAC::XS -e 'print 
$Math::Random::ISAAC::XS::VERSION, $/'

1.004

2024-02-10 14:10:32 dpchrist@laalaa ~
$ time perl -MMath::Random::ISAAC::XS -e 
'$i=Math::Random::ISAAC::XS->new(12345678); print pack 'L',$i->irand 
while 1' | dd bs=8K count=128K | wc -c

1073741824
131072+0 records in
131072+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 82.6523 s, 13.0 MB/s

real1m22.657s
user1m22.892s
sys 0m5.810s


The 'perl ... | dd ...' pipeline appears to be limited to a block size 
of 8,192 bytes.  I do not know if this is due to bash(1), perl(1), or 
dd(1) (?).



The repeatability of the ISAAC stream would substitute for the known 
good storage device, but the throughput is ~19x slower than 
/dev/urandom.  A drive capacity validation tool would want to feature 
concurrent threads and I/O on SMP machines.



David

Re: find and it uncommon syntax - grrrrrrrrr

[Andy Smith]

Hello,

On Sat, Feb 10, 2024 at 06:03:39PM -0500, gene heskett wrote:
> On 2/10/24 15:55, Greg Wooledge wrote:
> > find . -iname 'bpim5*shelf.scad'
> 
> Thank you Greg, it worked and 4 more copies are under construction now, but
> why is this not in the man page? Mind boggling.

Why can Gene not locate "iname" when it's right there in the "find"
man page? Mind boggling.

Why can Gene not type "how do I use GNU find to find a file by
name" into a web search engine and read any of the several links on
the first page of results? Mind boggling.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: find and it uncommon syntax - grrrrrrrrr

[Andy Smith]

Hello,

On Sat, Feb 10, 2024 at 03:46:09PM -0500, gene heskett wrote:
> I have misplaced file someplace in /home/gene.
> its name is bpim5*shelf.scad
> As usual it outputs 100,000 filenames, none of which is the one I am looking
> for. How in heck do you shut this thing up so it only spits out
> /the/path/to/the/file its looking for it it even found it?

Gene and his inability as usual to show us what he has tried and the
output he got - gr

> And where do I put that as an alias, in my .bashrc?

find is an extremely flexible command that can do a lot of different
queries so to get any sort of meaningful answer to this you'd have
to show us what exactly you tried.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: find and it uncommon syntax - grrrrrrrrr

[gene heskett]

On 2/10/24 15:55, Greg Wooledge wrote:

find . -iname 'bpim5*shelf.scad'


Thank you Greg, it worked and 4 more copies are under construction now, 
but why is this not in the man page? Mind boggling.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm

[Andrew M.A. Cater]

On Sat, Feb 10, 2024 at 09:48:52PM +, Maureen Thomas wrote:
>  So can I please get some help.  I have a portable CD/DVD and I made a USB 
> with a ISO on it.  The computer does not have a cd/dvd burner but I have a 
> portable one.  Can some one tell me if there are any special things I need to 
> do to put Debian 12 on this machine.  I really hate windows and need to get 
> it gone.  Your help is always appreciated by this old lady.  Thank you in 
> advance>
> On Friday, February 9, 2024 at 08:10:24 PM EST, Maureen Thomas 
>  wrote:  
>  
>  
> ,, 1  

Hi Maureen,

It will very much depend if your computer will boot from an exteral
CD/DVD which is USB connected. If it will - check in the BIOS / firmware,
then you should be fine.

If not, many machines will boot from a USB stick. You may find that yours
will do so, in which case the only thing you will need to do is to get the
image written appropriately to a USB drive.

We can help, potentially - there's enough expertise on the list to help
debug problems as they arise.

(Andy, just having done *lots* of Debian installs as part of the release
testing for the media team - but not one from an external CD/DVD drive -
from what I can see, the laptops I have do boot from external devices
connected via USB, though a CD/DVD might also be seen as a hard drive. Your
mileage may vary :) )

With every good wish, as ever,

Andy
(amaca...@debian.org)

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm

[Maureen Thomas]

 So can I please get some help.  I have a portable CD/DVD and I made a USB with 
a ISO on it.  The computer does not have a cd/dvd burner but I have a portable 
one.  Can some one tell me if there are any special things I need to do to put 
Debian 12 on this machine.  I really hate windows and need to get it gone.  
Your help is always appreciated by this old lady.  Thank you in advance>
On Friday, February 9, 2024 at 08:10:24 PM EST, Maureen Thomas 
 wrote:  
 
 
,, 1  

Re: Home UPS recommendations

[gene heskett]

On 2/10/24 13:40, Joe wrote:

On Sat, 10 Feb 2024 16:45:29 +0100
hw  wrote:




The cheap APC models seem to produce a lot more heat, and their
batteries don't seem to last as long.  They work and they're not
really a good deal.  I don't have test equipment for UPCs, but you can
feel how warm they get and see how cheaply they're built without
special equipment.



It's quite surprising how many complaints about swollen UPS batteries
there are around the Net. Given the fairly light duties of the batteries
almost all of the time, this is pretty well certain to be caused by
overheating due to incompetent charging. Batteries, particularly
lead-acid types, are not exactly new technology, and the correct
charging of them is well understood.

You have an excellent view of the problem.  One of the problems with PBa 
batteries is the each one of the gender has a mind of its own, and If 
you don't fiddle with the charging circuit, you will never find the 
optimum voltage to charge that battery to.  One of the things you never 
ever want to is look into a liquid acid battery and see it bubbling. 
That indicates and overcharge, the bubbling is the disassociated 
hydrogen and oxygen of the water component of the acid, which makes the 
water go away, leaving eve stronger acid..  Two instances I can regale 
you with.


1. shortly after I became the resident engineer at KXNE in NE Nebraska 
in '69, the two big truck batteries that started the 150 kw Cummins 
standby power failed, basically burned up from over charge. Replacing 
the batteries, they boiled like crazy.  So I turn down the curent from a 
charger with a higher resistor, because it was banging over 2 amps into 
the 2 of then to get the 24 the starter needed but that was holding 
those up to around 29 volts. The next day I raised the resistor about 4x 
as they were still boiling. Wash, rinse, repeat till the trickle charge 
was down to around .005 amps.  This was all it took for a trickle charge 
for a pair of 225ah large car batteries kept clean. 8 years later I'm 
bored out of my skull and had an offer to be the Chief at a station in 
NM, offering a 175% raise so I took it. Those batteries were then 8 
years old, and still were trying to turn that 335 Cummins wrong side out 
starting it. When the weekly 15 minute exercise came up you heard the 
bendix slam into the flywheel, followed milliseconds later by the first 
bark, and 1 measly second later the lights were back on


2. While in Nebraska, it can get pretty cold, like -35F once in a while. 
I had put an ambulance alternator in my daily driver, and made a 
switching regulator for the voltage regulator but in series with the 
voltage reference zener diode, I added 4 common si rectifier diodes to 
use their negative temp effects to turn it up or down according to the 
underhood temps.  15 seconds after a -25F start, it had the battery back 
up to about 16 volts, but 20 minutes and 20 miles later it was down to 
abound 12.7 volts, and on a 105F day down to around 12.3 volts.  That 
battery was then about 7 years old, still had its original water in it, 
spun the engine faster than it idled, when the missus threw a rod. The 
only thing I didn't get a chance to salvage was that alternator, the 
missus sold it to a junk yard the next day before I had a chance to pull 
it off.


Getting to know the battery and how to treat it could bankrupt all the 
replacement battery makers. The acid SG is important, reject any battery 
whose label says SG is 1.280. buy the one that says 1.260, It will be a 
fraction of a volt lower, but treated right will actually live years 
longer. Modern gel cell's are even more quickly destroyed by over charging.


Your trivia factoid for the day, from somebody who understands the 
chemistry.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: find and it uncommon syntax - grrrrrrrrr

[Greg Wooledge]

On Sat, Feb 10, 2024 at 02:58:24PM -0600, Nicholas Geovanis wrote:
> On Sat, Feb 10, 2024, 2:46 PM gene heskett  wrote:
> 
> > Greetings;
> >
> > I have misplaced file someplace in /home/gene.
> > its name is bpim5*shelf.scad
> >
> 
> Assuming that you are searching in the current working directory:
>  find bpim*  -print | grep 'shelf.scad'

That's not correct.  The argument(s) that immediately follow find should
be the starting point(s) where it will begin its search.  Normally these
would be directories, especially the "." directory, which is actually
the default in GNU find (but not a default in POSIX find).

This command would only work if the file Gene's looking for happens to
be in his home directory, *or*, if the file he's looking for happens to
be underneath a *directory* whose name matches the bpim* glob.  This is
possible, but I wouldn't count on it.

Re: find and it uncommon syntax - grrrrrrrrr

[Nicholas Geovanis]

On Sat, Feb 10, 2024, 2:46 PM gene heskett  wrote:

> Greetings;
>
> I have misplaced file someplace in /home/gene.
> its name is bpim5*shelf.scad
>

Assuming that you are searching in the current working directory:
 find bpim*  -print | grep 'shelf.scad'

As usual it outputs 100,000 filenames, none of which is the one I am
> looking for. How in heck do you shut this thing up so it only spits out
> /the/path/to/the/file its looking for it it even found it?
>
> And where do I put that as an alias, in my .bashrc?
>
> Cheers, Gene Heskett, CET.
> --
> "There are four boxes to be used in defense of liberty:
>   soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
>   - Louis D. Brandeis
>
>

Re: cherche exemple de code GtkMM4 (C++) pour ajouter des options à une application GtkMM-4 graphique (libre) add_main_option_entry

[Lamourec Alain]

Bonsoir

Sur cet exemple, j'ai plutôt Gio::Application::OPTION_TYPE_BOOL et 
Gio::Application::OPTION_TYPE_STRING : 
https://student.cs.uwaterloo.ca/~cs246/common/gtkmm/gtkmm-examples-3.0/09-commandLine/ex2/exampleapplication.cc


Voir également la documentation : 
https://gnome.pages.gitlab.gnome.org/glibmm/classGio_1_1Application.html




Basile Starynkevitch  writes:


Bonjour la liste,

GTK4 interface to RefPerSys inference engine. Contribute to 
RefPerSys/gtk4gui-refpersys development by creating an account 
on GitHub.


github.com

GitHub - RefPerSys/gtk4gui-refpersys: GTK4 interface to 
RefPerSys inference engine 

GTK4 interface to RefPerSys inference engine. Contribute to 
RefPerSys/gtk4gui-refpersys development by creating an account 
on GitHub.


 https://github.com/RefPerSys/gtk4gui-refpersys 

 est l'embryon d'un logiciel libre (sous licence MIT, je vais 
 peut-être plus tard la remplacer par la licence CeCILL ou 
 GPLv3+) d'interface graphique pour
le moteur d'inférences RefPerSys, lui-même en cours de 
développement en 

Reflexive & Persistent System (artificial intelligence) - GitHub 
- RefPerSys/RefPerSys: Reflexive & Persistent System (artificial 
intelligence)


github.com

GitHub - RefPerSys/RefPerSys: Reflexive & Persistent System 
(artificial intelligence) 

Reflexive & Persistent System (artificial intelligence) - GitHub 
- RefPerSys/RefPerSys: Reflexive & Persistent System (artificial 
intelligence)


 https://github.com/RefPerSys/RefPerSys 


 pour Linux et sous licence GPLv3+ (ou la CeCILL équivalente).

ce gtk4gui-refpersys contient le code suivant:

-

// file RefPerSys/gtk4gui-refpersys/mainrps_gtk.cc
//  SPDX-License-Identifier: MIT

/**
 * © Copyright 2023 - 2024 Basile STARYNKEVITCH and Abishek 
 CHAKRAVARTI

 *
 * A GTK4mm toolkit graphical interface (see fox-toolkit.org)
 * to the RefPerSys open source (GPLv3+ licensed) inference 
 engine

 *
 * see gnome.pages.gitlab.gnome.org/gtkmm-documentation/
 *
 * See refpersys.org and code on https://github.com/RefPerSys/
 *
 **/

#include "gtkrps.hh"

#include "gtkmm/version.h"

const char*gtkrps_progname;
const char gtkrps_git_id[] = GIT_ID;
const char gtkrps_shortgit_id[] = SHORTGIT_ID;
const char gtkrps_buildhost[]= GTKRPS_HOST;
const char gtkrps_arch[] = GTKRPS_ARCH;
const char gtkrps_opersys[] = GTKRPS_OPERSYS;
const char gtkrps_timestamp[] = __DATE__ "@" __TIME__;

extern "C" const char guirefpersys_ui[];
char gtkrps_myhostname[80];
void* gtkrps_dlhandle;
bool gtkrps_stderr_istty;

static void
gtkrps_show_version(void)
{
  printf("%s version information\n", gtkrps_progname);
  printf("\t full git %s\n", gtkrps_git_id);
  printf("\t short git %s\n", gtkrps_shortgit_id);
  printf("\t build host %s\n", gtkrps_buildhost);
  printf("\t arch: %s\n", gtkrps_arch);
  printf("\t OS: %s\n", gtkrps_opersys);
  printf("\t built: %s\n", gtkrps_timestamp);
  /// for some reason, don't work!
#if 0 && bad
  printf("\t GTKmm version: %d.%d.%d\n",
 gtkmm_major_version, gtkmm_minor_version, 
 gtkmm_micro_version);

#endif
} // end gtkrps_show_version

void
gtkrps_fatal_stop_at(const char*fil, int lin)
{
  fprintf(stderr, "%s FATAL STOP (%s:%d) pid %d shortgit %s\n",
  gtkrps_progname,
  fil, lin,
  (int)getpid(), gtkrps_shortgit_id);
  abort();

} // end gtkrps_fatal_stop_at

extern "C" const char gtkrpsui_guirefpersys[];

Glib::RefPtr gtkrps_app;
Gtk::Window*gtkrps_mainwin;

int
main(int argc, char**argv)
{
  assert(argc>0);
  gtkrps_progname = argv[0];
  gtkrps_dlhandle = dlopen(nullptr, RTLD_NOW| RTLD_GLOBAL);
  if (!gtkrps_dlhandle)
GTKRPS_FATALOUT("failed to dlopen main program: " << 
dlerror());

  gtkrps_stderr_istty = isatty(STDERR_FILENO);
  memset (gtkrps_myhostname, 0, sizeof(gtkrps_myhostname));
  gethostname(gtkrps_myhostname, sizeof(gtkrps_myhostname)-4);
  if (argc > 1 && !strcmp(argv[1], "--version"))
{
  gtkrps_show_version();
  exit (EXIT_SUCCESS);
};
  gtkrps_app = Gtk::Application::create 
  ("org.refpersys.gtk4gui");

#warning help needed here to parse program arguments
#if 0 && badcode 
///=
  gtkrps_app->add_main_option_entry(Gtk::OPTION_TYPE_BOOL, 
  "version",'V',
("Print version"), 
"");
  gtkrps_app->add_main_option_entry(Gtk::Application::OPTION_TYPE_STRING, 
  "fifo-prefix",'F',
("set the prefix of FIFO 
used for communication"),

"");
#endif
  Glib::ustring builder_str(gtkrpsui_guirefpersys);
  auto builder = Gtk::Builder::create_from_string(builder_str);
  gtkrps_app->signal_activate().connect([&] ()
  {
gtkrps_mainwin = 
builder->get_widget("app_window");

Re: Debian bookworm 12.4 installation wifi card not being detected

[Exeonz]

Results on ubuntu are

/03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries 
BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
    Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter 
[106b:0117]

    Kernel driver in use: wl
    Kernel modules: bcma, wl/


During debian install it's same result but without /kernel driver and 
kernel modules/

I use an iOS device and I don't think tethering feature is supported there.

Re: find and it uncommon syntax - grrrrrrrrr

[Greg Wooledge]

On Sat, Feb 10, 2024 at 03:46:09PM -0500, gene heskett wrote:
> I have misplaced file someplace in /home/gene.
> its name is bpim5*shelf.scad
> As usual it outputs 100,000 filenames, none of which is the one I am looking

cd
find . -iname 'bpim5*shelf.scad'

find and it uncommon syntax - grrrrrrrrr

[gene heskett]

Greetings;

I have misplaced file someplace in /home/gene.
its name is bpim5*shelf.scad
As usual it outputs 100,000 filenames, none of which is the one I am 
looking for. How in heck do you shut this thing up so it only spits out 
/the/path/to/the/file its looking for it it even found it?


And where do I put that as an alias, in my .bashrc?

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Unidentified subject!

[gene heskett]

On 2/10/24 13:30, Thomas Schmitt wrote:

Hi,

gene heskett wrote:

my fading eyesight couldn't see
the diffs between () and {} in a 6 point font.  I need a bigger, more
legible font in t-bird.


That's why i propose to copy+paste problematic command lines.

Your mouse can read it, your mail client can send it, and we have
youngsters here of merely 60 years who will be glad to tell our
most senior regular why the lines don't work.

With some luck this creates nostalgic tangents about how the used features
evolved since the early 1980s.

Or even the later 1970's when I made a cosmac super elf RCA 1802 board 
do anything I could dream up. Made the video hdwe, and the interface to 
control a broadcast vcr. S-100 bus adapter was the only thing I bought, 
and had to build that from a kit.  Built it for KRCR-TV in Redding CA, 
it was so useful to the production folks they used it many times a day 
from '79 to mid 90's when it burnt to the ground, That's eons in a tv 
station control room where stuff is often replaced before its fully 
written off tax wise in 5 years. Fun times back then. Now I'm searching 
amazon for a pi-clone hat with a 6 pack of sata-iii sockets on it, and 
coming up MT.  Sniff...


In the other thread about the /dev/sdm test:

Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32
but is taking a few bytes now and then.
[...]
$ ls -l
total 40627044
[...]
$ sudo f3probe --destructive --time-ops /dev/sdm
Bad news: The device `/dev/sdm' is a counterfeit of type limbo
Device geometry:
 *Usable* size: 59.15 GB (124050944 blocks)
Announced size: 1.91 TB (409600 blocks)


That's really barefaced.
How can the seller believe to get away with a problem which will show
already after a few dozen GB were written ?



Probe time: 2.07s


That's indeed a quick diagnosis. Congrats to the developers of f3probe.


Have a nice day :)

Thomas

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Erreur nvidia suite upgrade noyau 6.6.18

[ajh-valmer]

On Saturday 10 February 2024 19:41:01 Jean Bernon wrote:
> As-tu regardé du côté de xrandr ?
> https://doc.ubuntu-fr.org/xrandr#ajouter_une_resolution

Oui, merci du rappel, j'ai fait tout ça, et j'obtiens cette réponse :
Screen 0: minimum 320 x 200, ..., maximum 1024 x 768
Je ne peux donc pas augmenter la résolution avec ce pilote "Nouveau".
On dirait que c'est le pilote "Vesa" qui a pris la main, pas "Nouveau"...

> > Oui, j'ai fait exactement comme expliqué sur le lien sus-indiqué.
> > Ça semble marcher sauf que je me retrouve avec une résolution d'écran
> > trop faible de 1024x768, alors qu'avant avec le pilote nvidia,
> > j'avais 1280x1024.
> > J'ai vainement cherché, j'ai toujours cette faible résolution d'écran.
> > Voilà donc mon problème.
> > Les modules "nouveau" et "vesa" sont chargés.

Re: Erreur nvidia suite upgrade noyau 6.6.18

[Jean Bernon]

As-tu regardé du côté de xrandr ?
https://doc.ubuntu-fr.org/xrandr#ajouter_une_resolution

- Mail original - 

> Merci.
> Oui, j'ai fait exactement comme expliqué sur le lien sus-indiqué.
> Ça semble marcher sauf que je me retrouve avec une résolution d'écran
> trop faible de 1024x768, alors qu'avant avec le pilote nvidia,
> j'avais
> 1280x1024.
> J'ai vainement cherché, j'ai toujours cette faible résolution
> d'écran.
> Voilà donc mon problème.
> Les modules "nouveau" et "vesa" sont chargés.
> Bonne soirée.
> A. Valmer

Problema puerto usb-c

[JA CM]

Buenos días
Tengo una StremCam de Logitec con conector USB-C que hasta hace poco me
funcionaba correctamente pero que ha dejado de hacerlo de una manera
extraña.
El SO es un Debian 12 y el Kernel es 6.1.0-17-amd. Tiene arranque dual con
Windows 10 (con fast boot desactivado y en Windows la cámara va bien). La
placa base es una ASUS PRIME X299-A y sólo tiene un puerto USB-C
 Cuando arranco el sistema me detecta sin problemas el dispositivo:
* la salida lsusb y v4lw-ctl --list-devices es:
[image: lsusb.png][image: v412-list.png]
A pesar de esto, en los logs del núcleo (kern.log) me aparece varias veces
el mensaje siguiente:
usb 6-1 *current rate 16000 is different from the runtime rate 48000*.
Si ejecuto el programa de cámaras Cheese en los logs del nucleo me aparecen
multitud de veces los dos mensajes siguientes
2024-02-10T14:25:19.003426+01:00 debian kernel: [ 2749.691059] *xhci_hcd
:03:00.0: ERROR* Transfer event TRB DMA ptr not part of current TD
ep_index 2 comp_code 13
2024-02-10T14:25:19.003427+01:00 debian kernel: [ 2749.691061] xhci_hcd
:03:00.0: Looking for event-dma fffc5a20 trb-start
fffc5130 trb-end fffc5130 seg-start fffc5000
seg-end fffc5ff0
Si es guvcview quien arranca la cámara el kernel lanza lo siguiente
2024-02-10T14:25:41.313584+01:00 debian kernel: [ 2772.000990] *uvcvideo
6-1:1.1: Failed to query *(130) UVC probe control : -110 (exp. 26).
2024-02-10T14:25:46.433585+01:00 debian kernel: [ 2777.117761] *uvcvideo
6-1:1.1: Failed to set UVC probe control : -110 (exp. 26)*.
2024-02-10T14:25:53.980089+01:00 debian kernel: [ 2784.667935] *DMAR: DRHD*:
handling fault status reg 2
2024-02-10T14:25:53.980100+01:00 debian kernel: [ 2784.667944] DMAR: [DMA
Write NO_PASID] Request device [03:00.0] fault addr 0xffe2a000 [fault
reason 0x05] PTE Write access is not set
2024-02-10T14:25:53.980596+01:00 debian kernel: [ 2784.668452] *xhci_hcd
:03:00.0: WARN* Event TRB for slot 1 ep 0 with no TDs queued?
2024-02-10T14:25:53.981078+01:00 debian kernel: [ 2784.668949] DMAR: *DRHD:
handling fault status reg 102*
2024-02-10T14:25:53.981082+01:00 debian kernel: [ 2784.668953] *DMAR: [DMA
Read NO_PASID] *Request device [03:00.0] fault addr 0xffe2d000 [fault
reason 0x06] PTE Read access is not set
El caso es que después de esto, ya deja de aparecer la cámara al ejecutar
lsusb y v4lw-ctl con lo que dev/video0 tampoco existe y no hay cámara.
Además, en los log de núcleo tengo mensajes de intentos de reset del puerto
y de error como los siguientes sin llegar en ningún momento a reconocer la
cámara:
2024-02-10T14:26:08.321680+01:00 debian kernel: [ 2799.007414] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:26:13.569591+01:00 debian kernel: [ 2804.257167] usb 6-1: *device
descriptor read/8, error -110*
2024-02-10T14:26:13.677672+01:00 debian kernel: [ 2804.361604] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:26:29.185640+01:00 debian kernel: [ 2819.870020] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:26:29.497667+01:00 debian kernel: [ 2820.182922] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:26:34.561590+01:00 debian kernel: [ 2825.249296] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:26:34.669672+01:00 debian kernel: [ 2825.353701] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:26:50.177640+01:00 debian kernel: [ 2840.862151] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:26:50.489680+01:00 debian kernel: [ 2841.175072] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:26:55.553589+01:00 debian kernel: [ 2846.241524] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:26:55.661675+01:00 debian kernel: [ 2846.345808] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:27:11.169655+01:00 debian kernel: [ 2861.854227] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:27:11.485661+01:00 debian kernel: [ 2862.171067] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:27:16.549585+01:00 debian kernel: [ 2867.237473] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:27:16.657664+01:00 debian kernel: [ 2867.341915] usb 6-1:
reset SuperSpeed USB device number 2 using xhci_hcd
2024-02-10T14:27:32.161641+01:00 debian kernel: [ 2882.846322] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:27:32.293588+01:00 debian kernel: [ 2882.978077] usb 6-1: USB
disconnect, device number 2
2024-02-10T14:27:32.549559+01:00 debian kernel: [ 2883.234688] usb 6-1: new
SuperSpeed USB device number 3 using xhci_hcd
2024-02-10T14:27:37.793640+01:00 debian kernel: [ 2888.478316] usb 6-1:
device descriptor read/8, error -110
2024-02-10T14:27:37.901629+01:00 debian kernel: [ 2888.585993] usb 6-1: new
SuperSpeed USB device number 3 using xhci_hcd
2024-02-10T14:27:53.409639+01:00 debian kernel: [ 2904.094357] usb 6-1:
device 

Re: Unidentified subject!

[Thomas Schmitt]

Hi,

gene heskett wrote:
> my fading eyesight couldn't see
> the diffs between () and {} in a 6 point font.  I need a bigger, more
> legible font in t-bird.

That's why i propose to copy+paste problematic command lines.

Your mouse can read it, your mail client can send it, and we have
youngsters here of merely 60 years who will be glad to tell our
most senior regular why the lines don't work.

With some luck this creates nostalgic tangents about how the used features
evolved since the early 1980s.


In the other thread about the /dev/sdm test:
> Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32
> but is taking a few bytes now and then.
> [...]
> $ ls -l
> total 40627044
> [...]
> $ sudo f3probe --destructive --time-ops /dev/sdm
> Bad news: The device `/dev/sdm' is a counterfeit of type limbo
> Device geometry:
> *Usable* size: 59.15 GB (124050944 blocks)
>Announced size: 1.91 TB (409600 blocks)

That's really barefaced.
How can the seller believe to get away with a problem which will show
already after a few dozen GB were written ?


> Probe time: 2.07s

That's indeed a quick diagnosis. Congrats to the developers of f3probe.


Have a nice day :)

Thomas

Re: Erreur nvidia suite upgrade noyau 6.6.18

[ajh-valmer]

On Saturday 10 February 2024 18:13:06 Jean Bernon  wrote:
> Je découvre votre échange et vais sans doute être naïf. 
> Que se passe-t-il si tu suis la procédure classique de 
> passage de nvidia à nouveau, décrite par le crabeinfo 
(https://lecrabeinfo.net/installer-pilote-proprietaire-nvidia-sur-debian-linux.html#desinstaller-le-pilote-proprietaire-nvidia):
  
> - apt purge nvidia
> - systemctl restart gdm3.service (ou sddm ou lightdm)
> - apt install xserver-xorg-video-nouveau

Merci.
Oui, j'ai fait exactement comme expliqué sur le lien sus-indiqué.
Ça semble marcher sauf que je me retrouve avec une résolution d'écran 
trop faible de 1024x768, alors qu'avant avec le pilote nvidia, j'avais 
1280x1024.
J'ai vainement cherché, j'ai toujours cette faible résolution d'écran.
Voilà donc mon problème.
Les modules "nouveau" et "vesa" sont chargés.
Bonne soirée.
A. Valmer

Problems with `pactl load-module module-loopback'

[Rodolfo Medina]

Hi all.

Without pipewire I didn't manage to pair and connect my bluetooth
headset/microphone to my Debian 12 so I installed pipewire while pulseaudio was
already there.  So now both pulseaudio and pipewire are installed.  Now when I
do:

 $ pactl load-module module-loopback latency_msec=5

a terrible noise suddenly comes, and if I want to stop it with

 $ pactl exit

I get the error message `exit failure: connection refused'.  I searched around
but didn't find so far any solution.  Please help whoever can.

Thanks in advance,

Rodolfo

Can Linux update an old kernel [WAS Re: AW: AW: AW: su su- sudo dont work]

[Andrew M.A. Cater]

On Sat, Feb 10, 2024 at 01:21:55PM +, Schwibinger Michael wrote:
> Yes.
> 
> 
> I found out
> I do use an old kernel.
> 
> Can LINUX update a kernel?
> 

Hi Sophie,

Yes, of course. As root/sudo user, apt-get update ; apt-get dist-upgrade

But you still don't give anybody any actual *details*

All best, as ever,

Andy

> Regards
> Sophie
> 
> 
> 
> Von: chris 
> Gesendet: Mittwoch, 7. Februar 2024 19:35
> An: Schwibinger Michael 
> Betreff: Re: AW: AW: su su- sudo dont work
> 
> Very helpful ty
> 
> On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael 
> mailto:h...@hotmail.com>> wrote:
> Good afternoon.
> 
> The bug report
> 
> sudo ...
> You are not in the sudoers file.
> Regards
> Sophie
> 
> 
> 
> Von: Hans mailto:hans.ullr...@loop.de>>
> Gesendet: Freitag, 26. Januar 2024 18:44
> An: debian-user@lists.debian.org 
> mailto:debian-user@lists.debian.org>>
> Betreff: Re: AW: AW: su su- sudo dont work
> 
> 
> Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:
> 
> Yes, if you want to install soemthing for example by using the apt command, 
> best way is becoming root with the command "su -" and then install the 
> rquired package.
> 
> 
> Example:
> 
> su -  then enter the password of the user root
> 
> 
> If installing for example firefox, first read the repository:
> 
> 
> apt update
> 
> 
> then install the package
> 
> 
> apt install firefox-esr
> 
> 
> -
> 
> 
> Hint: If you want a graphical method and you have no X and Wndow-Manager 
> running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.
> 
> 
> You have to install aptitude first:
> 
> 
> apt install aptitude
> 
> 
> Then you can start the gui with the command "aptitude" as root.
> 
> 
> Hint 2: aptitude is controlled by keypresses without any enter-key.
> 
> For example, when started aptitude, just press the "u" key and it reads the 
> update, "U" (Shift + u)  marks all newer packages automatically to be 
> updated, then press "g" and you will shwo, what it will do. Press "g" again, 
> and it will do the update.
> 
> 
> Please note: If you want to upgrade the whole sytem, then using apt or 
> apt-get will be the better choice!
> 
> 
> But aptitude is very well for installing single packages or weekly upgrades, 
> where not much packages will be renewed.
> 
> 
> If you are not much experienced, and you have a window-manager running like 
> KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic is a 
> graphical tool for installing packages, it is a GUI for apt.
> 
> 
> Synaptic MUST run as root.
> 
> 
> Hope this helps.
> 
> 
> By the way: I believe, you are not very experienced in English language, so I 
> suggest to suscribe in the fine German forum,
> 
> which is 
> debian-user-ger...@lists.debioan.org.
> 
> 
> Here is the link:
> 
> https://lists.debian.org/debian-user-german/
> 
> 
> Good luck!
> 
> 
> Hans
> 
> 
> 
> > Sorry
> 
> > it was my mistake
> 
> >
> 
> > It is
> 
> >
> 
> > su -
> 
> > su
> 
> > or sudo.
> 
> >
> 
> > Sorry.
> 
> >
> 
> > Is su -
> 
> > the best for install?
> 
> >
> 
> > Regards
> 
> >
> 
> > Sophie
> 
> >
> 
> >
> 
> > 
> 
> >

Re: Unidentified subject!

[gene heskett]

On 2/10/24 05:39, Thomas Schmitt wrote:

Hi,

Gene Heskett wrote:

Is bash not actually bash these days? It is not doing for loops for me.


Come on Gene, be no sophie. Copy+paste your failing line here. :))

Alexander M. posted it a few days ago but my fading eyesight couldn't 
see the diffs between () and {} in a 6 point font.  I need a bigger, 
more legible font in t-bird. Or blow it up about 3x. Which doesn't 
stick, its gone with next msg.  G.


Thank Thomas.
[...]> Have a nice day :)


Thomas

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Things I don't touch with a 3.048m barge pole: USB storage(WasRe: Unidentified subject!)

[gene heskett]

On 2/10/24 00:54, David Christensen wrote:

On 2/9/24 04:53, gene heskett wrote:

Interesting report from gdisk however:
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
   MBR: MBR only
   BSD: not present
   APM: not present
   GPT: not present


***
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.

Command (? for help):
Command (? for help): p
Disk /dev/sdm: 409600 sectors, 1.9 TiB
Model: SSD 3.0
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 3230045D-589D-4601-8C4D-E9C4684B9657
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 409566
Partitions will be aligned on 64-sector boundaries
Total free space is 30 sectors (15.0 KiB)

Number  Start (sector)    End (sector)  Size   Code  Name
    1  64  409599   1.9 TiB 0700  Microsoft 
basic data


Command (? for help): q

What do we make of that?  Some sort of NTFS?



Do these commands produce any clues or error messages?

# fdisk -l /dev/sdm

# tail /var/log/messages

# dmesg | tail


They suggested an exfat format ootb, which matches most sd cards.
Thanks David, Take care.


David

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: testing new sdm drive

[gene heskett]

On 2/10/24 00:46, David Christensen wrote:

On 2/9/24 00:51, gene heskett wrote:

On 2/8/24 13:25, David Christensen wrote:

On 2/7/24 23:14, gene heskett wrote:

gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm
...
scsiModePageOffset: response length too short, resp_len=4 offset=4 
bd_len=0
scsiModePageOffset: response length too short, resp_len=4 offset=4 
bd_len=0

 >> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or 
more '-T permissive' options.

gene@coyote:/etc$

And then again, it worked, sorta
...
Please try again with the drive connected directly to a motherboard 
USB 3.0 port.



That is where it still is, on a blue usb3.0 port on a 3 yo ASUS mobo.



Does smartctl(8) fail when you connect the USB SSD to other USB ports?

Allready packed up for return, I found enough fraud with the f3 package 
to jail somebody.


David

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: testing new sdm drive

[gene heskett]

On 2/9/24 20:37, Alexander V. Makartsev wrote:

On 10.02.2024 03:34, gene heskett wrote:

On 2/8/24 07:22, Alexander V. Makartsev wrote:

This is how I would test it.
First create a new GPT partition table and a new 2TB partition:
 $ sudo gdisk /dev/sdX check

/!\  Make double sure you've selected the right device by using 
"lsblk" and "blkid" utilities.  /!\
/!\    It could change from 'sdm' to another 
name after reboot.      /!\


At gdisk prompt press "o" to create a new GPT table, next press "n" 
to create a new partition, accept default values by pressing "enter".
To verify setup press "p", to accept configuration and write it to 
device press "w". check


Next format partition to ext4 filesystem:
 $ sudo mkfs.ext4 -m 0 -e remount-ro /dev/sdX1 check

Next mount the filesystem:
 $ sudo mkdir /mnt/disktest check
 $ sudo mount /dev/sdX1 /mnt/disktest check

Next create reference 1GB file filled with dummy data:
 $ cd /mnt/disktest check
 $ sudo fallocate -l 1G ./reftestfile check
 $ sudo badblocks -w -s -t random ./reftestfile check

Now we can use script to create 1830 1GB files and check their checksum:
 $ for i in $(seq 1830); do sudo dd if="./reftestfile" 
of="./testfile${i}" status=none; md5sum -b "./testfile${i}" ;done


This procedure will take a very long time to complete. "md5sum" will 
output the checksum for each file and they should be equal to 
checksum of "reftestfile":

 $ md5sum -b ./reftestfile

Got a problem Alexander:
I had to put the script someplace else. So I put it in my private 
/home/gene/bin as disktest.txt with nano. couldn't find it.

But:
gene@coyote:/mnt/disktest$ sudo /home/gene/bin/disktest.txt
sudo: /home/gene/bin/disktest.txt: command not found
If you put that 'for' loop one-liner inside, I think you forgot to make 
"/home/gene/bin/disktest.txt" executable:

     $ chmod +x /home/gene/bin/disktest.txt


And:
gene@coyote:/mnt/disktest$ ls /home/gene/bin/disktest.txt
/home/gene/bin/disktest.txt
So I think I found the problem with my script, ancient eyeballs can't 
tell the diff between () and{} so I fixed that but it still won't run 
or be killed. I don't care how big you've made the t-bird font, by the 
time you've read 2 more msgs, its back to about 6 point text.  Grrr.


So I fired up a root session of htop, found about 8 copies of dd 
showing and started killing them but cannot kill the last 2 in the D 
state.


And cannot find .disktest.txt running in a root htop and the2 copy's 
of dd can't be killall'd.



It's not possible for me to know what went wrong.
Have you created "reftestfile" inside "/mnt/disktest" directory?
How many "testfile*" files, if any, were created on the filesystem 
mounted at "/mnt/disktest"?

Was there anything relevant in the syslog about "sdm" drive after the test?
If you'd followed my instructions step by step, you'd end up inside 
"/mnt/disktest" directory and for the last step all you had to do is 
copy and paste that one-liner 'for' loop into the command line.
It's a long line and it really meant to be copied and pasted not typed 
by hand, and also to give you the idea of the process, so you could 
adjust it if needed.
I've tested it again on my computer and it worked as expected, 
synchronously created "testfiles" inside current directory and 
calculated their hashes one by one.


Someone else advised me of the f3 package, designed to do exactly this, 
disclosed that the first one tested was actually an undersized and slow 
64G drive. Got them packed up and return authorization already for a 
mailing label,  Thank you very much for your assistance Alexander, 
interest much apprecaited.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Erreur nvidia suite upgrade noyau 6.6.18

[Jean Bernon]

Je découvre votre échange et vais sans doute être naïf. Que se passe-t-il si tu 
suis la procédure classique de passage de nvidia à nouveau, décrite par le 
crabeinfo 
(https://lecrabeinfo.net/installer-pilote-proprietaire-nvidia-sur-debian-linux.html#desinstaller-le-pilote-proprietaire-nvidia):

- apt purge nvidia
- systemctl restart gdm3.service (ou sddm ou lightdm)
- apt install xserver-xorg-video-nouveau


- Mail original - 

> De: "ajh-valmer" 
> À: debian-user-french@lists.debian.org
> Envoyé: Samedi 10 Février 2024 17:56:13
> Objet: Re: Erreur nvidia suite upgrade noyau 6.6.18

> On Saturday 10 February 2024 15:17:53 Fabien Dubois wrote:
> > Le 10/02/2024 à 15:10, ajh-valmer a écrit :
> > > Dommage que personne sur la liste ne puisse m'aider pour
> > > installer
> > > le pilote graphique "Nouveau" et qu'il soit fonctionnel.
> > > Devrais-je être obligé d'acheter une nouvelle carte vidéo plus
> > > récente ?
> > > Bonne journée,

> > Avec les liens déjà donnés tout s'installe sans souci. Bien faire
> > apt-get purge *nvidia* pour tout enlever du pilote propriétaire.
> > Après
> > s'il y a un pb particulier sur votre ordi...
> > Par contre avec nouveau c'est Wayland qui est utilisé, et il a
> > l'air pas
> > mal bugué. En ce moment des soucis de pointeurs de souris (mais pas
> > que...).
> > Et le pilote propriétaire qui devrait fonctionner avec wayland sous
> > sid,
> > gnome fait basculer automatiquement sous x11 au login.
> > Bref, désolé de ne pas aider plus. Fabien

> Hello,
> Tu n'étais pas visé en particulier, j'alertais l'ensemble de la ML,
> pensant qu'ils y avaient d'autres connaisseurs du pilote "Nouveau",
> mais semble t-il non.
> Bonne soirée.

Re: Erreur nvidia suite upgrade noyau 6.6.18

[ajh-valmer]

On Saturday 10 February 2024 15:17:53 Fabien Dubois wrote:
> Le 10/02/2024 à 15:10, ajh-valmer a écrit :
> > Dommage que personne sur la liste ne puisse m'aider pour installer
> > le pilote graphique "Nouveau" et qu'il soit fonctionnel.
> > Devrais-je être obligé d'acheter une nouvelle carte vidéo plus récente ?
> > Bonne journée,

> Avec les liens déjà donnés tout s'installe sans souci. Bien faire 
> apt-get purge *nvidia* pour tout enlever du pilote propriétaire. Après 
> s'il y a un pb particulier sur votre ordi...
> Par contre avec nouveau c'est Wayland qui est utilisé, et il a l'air pas 
> mal bugué. En ce moment des soucis de pointeurs de souris (mais pas que...).
> Et le pilote propriétaire qui devrait fonctionner avec wayland sous sid, 
> gnome fait basculer automatiquement sous x11 au login.
> Bref, désolé de ne pas aider plus. Fabien

Hello,
Tu n'étais pas visé en particulier, j'alertais l'ensemble de la ML,
pensant qu'ils y avaient d'autres connaisseurs du pilote "Nouveau",
mais semble t-il non.
Bonne soirée.

Re: testing new sdm drive continued

[gene heskett]

On 2/8/24 15:36, Linux-Fan wrote:

Alexander V. Makartsev writes:


[...]
I managed to kill f3write, so f3probe could access it:
ene@coyote:/mnt/disktest$ sudo f3probe --destructive --time-ops /dev/sdm
F3 probe 8.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.

WARNING: Probing normally takes from a few seconds to 15 minutes, but
 it can take longer. Please be patient.

Bad news: The device `/dev/sdm' is a counterfeit of type limbo

You can "fix" this device using the following command:
f3fix --last-sec=124050943 /dev/sdm

Device geometry:
 *Usable* size: 59.15 GB (124050944 blocks)
Announced size: 1.91 TB (409600 blocks)
Module: 2.00 TB (2^41 Bytes)
Approximate cache size: 1.00 MB (2048 blocks), need-reset=no
   Physical block size: 512.00 Byte (2^9 Bytes)

Probe time: 2.07s
 Operation: total time / count = avg time
  Read: 311.9ms / 4212 = 74us
 Write: 1.75s / 24740 = 70us
 Reset: 1us / 1 = 1us
gene@coyote:/mnt/disktest$
No faster than it is, its not worth the f3fix effort, I can buy 
reputable, much faster sd cards at 1/3rd the cost.




HTH
Linux-Fan

öö

[...]

c
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: testing new sdm drive

[gene heskett]

On 2/8/24 15:36, Linux-Fan wrote:

Alexander V. Makartsev writes:


On 08.02.2024 12:14, gene heskett wrote:

gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local 
build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, 
http://www.smartmontools.org>www.smartmontools.org


=== START OF INFORMATION SECTION ===
Vendor:
Product:  SSD 3.0


[...]

Looks like a scam. Probably a reprogrammed controller to falsely 
report 2TB of space to the system.


I support this view :)


This is how I would test it.
First create a new GPT partition table and a new 2TB partition:
    $ sudo gdisk /dev/sdX

/!\  Make double sure you've selected the right device by using 
"lsblk" and "blkid" utilities.  /!\
/!\    It could change from 'sdm' to another 
name after reboot.      /!\


At gdisk prompt press "o" to create a new GPT table, next press "n" to 
create a new partition, accept default values by pressing "enter".
To verify setup press "p", to accept configuration and write it to 
device press "w".


Next format partition to ext4 filesystem:
    $ sudo mkfs.ext4 -m 0 -e remount-ro /dev/sdX1

Next mount the filesystem:
    $ sudo mkdir /mnt/disktest
    $ sudo mount /dev/sdX1 /mnt/disktest

Next create reference 1GB file filled with dummy data:
    $ cd /mnt/disktest



From here on I'd suggest trying the tools from package `f3`.


After installing it, find the documentation under
/usr/share/doc/f3/README.rst.gz. Basic usage requires only two commands:

 f3write .

Which has now stopped after severa hours of quitelatharic speeds in the 
20m/second are, showing a litle over 1.5%.  The bash shell shows it has 
written:

ree space: 1.87 TB
Creating file 1.h2w ... OK!
Creating file 2.h2w ... OK!
Creating file 3.h2w ... OK!
Creating file 4.h2w ... OK!
Creating file 5.h2w ... OK!
Creating file 6.h2w ... OK!
Creating file 7.h2w ... OK!
Creating file 8.h2w ... OK!
Creating file 9.h2w ... OK!
Creating file 10.h2w ... OK!
Creating file 11.h2w ... OK!
Creating file 12.h2w ... OK!
Creating file 13.h2w ... OK!
Creating file 14.h2w ... OK!
Creating file 15.h2w ... OK!
Creating file 16.h2w ... OK!
Creating file 17.h2w ... OK!
Creating file 18.h2w ... OK!
Creating file 19.h2w ... OK!
Creating file 20.h2w ... OK!
Creating file 21.h2w ... OK!
Creating file 22.h2w ... OK!
Creating file 23.h2w ... OK!
Creating file 24.h2w ... OK!
Creating file 25.h2w ... OK!
Creating file 26.h2w ... OK!
Creating file 27.h2w ... OK!
Creating file 28.h2w ... OK!
Creating file 29.h2w ... OK!
Creating file 30.h2w ... OK!
Creating file 31.h2w ... OK!
Creating file 32.h2w ... OK!
Creating file 33.h2w ... OK!
Creating file 34.h2w ... OK!
Creating file 35.h2w ... OK!
Creating file 36.h2w ... OK!
Creating file 37.h2w ... OK!
Creating file 38.h2w ... OK!
Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32

but is taking a few bytes now and then. I 'd thing if f3write was having 
a problem, it would exist with a report. An ls -l in another shell took 
about two minutes to respond:

gene@coyote:/mnt/disktest$ ls -l
total 40627044
-rw--- 1 root root 1073741824 Feb 10 05:49 10.h2w
-rw--- 1 root root 1073741824 Feb 10 05:51 11.h2w
-rw--- 1 root root 1073741824 Feb 10 05:59 12.h2w
-rw--- 1 root root 1073741824 Feb 10 06:16 13.h2w
-rw--- 1 root root 1073741824 Feb 10 06:25 14.h2w
-rw--- 1 root root 1073741824 Feb 10 06:33 15.h2w
-rw--- 1 root root 1073741824 Feb 10 06:44 16.h2w
-rw--- 1 root root 1073741824 Feb 10 06:45 17.h2w
-rw--- 1 root root 1073741824 Feb 10 06:57 18.h2w
-rw--- 1 root root 1073741824 Feb 10 07:06 19.h2w
-rw--- 1 root root 1073741824 Feb 10 05:22 1.h2w
-rw--- 1 root root 1073741824 Feb 10 07:16 20.h2w
-rw--- 1 root root 1073741824 Feb 10 07:22 21.h2w
-rw--- 1 root root 1073741824 Feb 10 07:32 22.h2w
-rw--- 1 root root 1073741824 Feb 10 07:35 23.h2w
-rw--- 1 root root 1073741824 Feb 10 07:39 24.h2w
-rw--- 1 root root 1073741824 Feb 10 07:50 25.h2w
-rw--- 1 root root 1073741824 Feb 10 08:09 26.h2w
-rw--- 1 root root 1073741824 Feb 10 08:19 27.h2w
-rw--- 1 root root 1073741824 Feb 10 08:29 28.h2w
-rw--- 1 root root 1073741824 Feb 10 08:31 29.h2w
-rw--- 1 root root 1073741824 Feb 10 05:24 2.h2w
-rw--- 1 root root 1073741824 Feb 10 08:37 30.h2w
-rw--- 1 root root 1073741824 Feb 10 08:57 31.h2w
-rw--- 1 root root 1073741824 Feb 10 09:06 32.h2w
-rw--- 1 root root 1073741824 Feb 10 09:32 33.h2w
-rw--- 1 root root 1073741824 Feb 10 09:42 34.h2w
-rw--- 1 root root 1073741824 Feb 10 10:00 35.h2w
-rw--- 1 root root 1073741824 Feb 10 10:11 36.h2w
-rw--- 1 root root  799719936 Feb 10 10:21 37.h2w
-rw--- 1 root root 1073741824 Feb 10 05:26 3.h2w
-rw--- 1 root root 1073741824 Feb 10 05:29 4.h2w
-rw--- 1 root root 1073741824 Feb 10 05:31 5.h2w
-rw--- 1 root root 1073741824 Feb 10 05:33 6.h2w

cherche exemple de code GtkMM4 (C++) pour ajouter des options à une application GtkMM-4 graphique (libre) add_main_option_entry

[Basile Starynkevitch]

Bonjour la liste,

GTK4 interface to RefPerSys inference engine. Contribute to 
RefPerSys/gtk4gui-refpersys development by creating an account on GitHub.


github.com

GitHub - RefPerSys/gtk4gui-refpersys: GTK4 interface to RefPerSys 
inference engine <#>


GTK4 interface to RefPerSys inference engine. Contribute to 
RefPerSys/gtk4gui-refpersys development by creating an account on GitHub.


 https://github.com/RefPerSys/gtk4gui-refpersys 



 est l'embryon d'un logiciel libre (sous licence MIT, je vais peut-être 
plus tard la remplacer par la licence CeCILL ou GPLv3+) d'interface 
graphique pour le moteur d'inférences RefPerSys, lui-même en cours de 
développement en


Reflexive & Persistent System (artificial intelligence) - GitHub - 
RefPerSys/RefPerSys: Reflexive & Persistent System (artificial 
intelligence)


github.com

GitHub - RefPerSys/RefPerSys: Reflexive & Persistent System (artificial 
intelligence) <#>


Reflexive & Persistent System (artificial intelligence) - GitHub - 
RefPerSys/RefPerSys: Reflexive & Persistent System (artificial intelligence)


 https://github.com/RefPerSys/RefPerSys 



 pour Linux et sous licence GPLv3+ (ou la CeCILL équivalente).

ce gtk4gui-refpersys contient le code suivant:



// file RefPerSys/gtk4gui-refpersys/mainrps_gtk.cc
//  SPDX-License-Identifier: MIT

/**
 * © Copyright 2023 - 2024 Basile STARYNKEVITCH and Abishek CHAKRAVARTI
 *
 * A GTK4mm toolkit graphical interface (see fox-toolkit.org)
 * to the RefPerSys open source (GPLv3+ licensed) inference engine
 *
 * see gnome.pages.gitlab.gnome.org/gtkmm-documentation/
 *
 * See refpersys.org and code on https://github.com/RefPerSys/
 *
 **/

#include "gtkrps.hh"

#include "gtkmm/version.h"

const char*gtkrps_progname;
const char gtkrps_git_id[] = GIT_ID;
const char gtkrps_shortgit_id[] = SHORTGIT_ID;
const char gtkrps_buildhost[]= GTKRPS_HOST;
const char gtkrps_arch[] = GTKRPS_ARCH;
const char gtkrps_opersys[] = GTKRPS_OPERSYS;
const char gtkrps_timestamp[] = __DATE__ "@" __TIME__;

extern "C" const char guirefpersys_ui[];
char gtkrps_myhostname[80];
void* gtkrps_dlhandle;
bool gtkrps_stderr_istty;


static void
gtkrps_show_version(void)
{
  printf("%s version information\n", gtkrps_progname);
  printf("\t full git %s\n", gtkrps_git_id);
  printf("\t short git %s\n", gtkrps_shortgit_id);
  printf("\t build host %s\n", gtkrps_buildhost);
  printf("\t arch: %s\n", gtkrps_arch);
  printf("\t OS: %s\n", gtkrps_opersys);
  printf("\t built: %s\n", gtkrps_timestamp);
  /// for some reason, don't work!
#if 0 && bad
  printf("\t GTKmm version: %d.%d.%d\n",
 gtkmm_major_version, gtkmm_minor_version, gtkmm_micro_version);
#endif
} // end gtkrps_show_version


void
gtkrps_fatal_stop_at(const char*fil, int lin)
{
  fprintf(stderr, "%s FATAL STOP (%s:%d) pid %d shortgit %s\n",
  gtkrps_progname,
  fil, lin,
  (int)getpid(), gtkrps_shortgit_id);
  abort();

} // end gtkrps_fatal_stop_at

extern "C" const char gtkrpsui_guirefpersys[];

Glib::RefPtr gtkrps_app;
Gtk::Window*gtkrps_mainwin;

int
main(int argc, char**argv)
{
  assert(argc>0);
  gtkrps_progname = argv[0];
  gtkrps_dlhandle = dlopen(nullptr, RTLD_NOW| RTLD_GLOBAL);
  if (!gtkrps_dlhandle)
    GTKRPS_FATALOUT("failed to dlopen main program: " << dlerror());
  gtkrps_stderr_istty = isatty(STDERR_FILENO);
  memset (gtkrps_myhostname, 0, sizeof(gtkrps_myhostname));
  gethostname(gtkrps_myhostname, sizeof(gtkrps_myhostname)-4);
  if (argc > 1 && !strcmp(argv[1], "--version"))
    {
  gtkrps_show_version();
  exit (EXIT_SUCCESS);
    };
  gtkrps_app = Gtk::Application::create ("org.refpersys.gtk4gui");
#warning help needed here to parse program arguments
*#if 0 && badcode 
///=*
  gtkrps_app->add_main_option_entry(Gtk::OPTION_TYPE_BOOL, 
"version",    'V',
    ("Print 
version"),   "");
gtkrps_app->add_main_option_entry(Gtk::Application::OPTION_TYPE_STRING, 
"fifo-prefix",    'F',
    ("set the prefix of FIFO used for 
communication"),

    "");
#endif
  Glib::ustring builder_str(gtkrpsui_guirefpersys);
  auto builder = Gtk::Builder::create_from_string(builder_str);
  gtkrps_app->signal_activate().connect([&] ()
  {
    gtkrps_mainwin = builder->get_widget("app_window");
    gtkrps_app->add_window(*gtkrps_mainwin);
    gtkrps_mainwin->show();
  });
  return gtkrps_app->run(argc, argv);
} // end main

/
 **   for Emacs...
 ** Local Variables: ;;
 ** compile-command: "make guigtkrps" ;;
 ** End: ;;
 /




Voir ci dessus les lignes autour du *//*

Mais ça 

Re: Home UPS recommendations

[hw]

On Sat, 2024-02-10 at 08:57 -0500, Felix Miata wrote:
> hw composed on 2024-02-10 11:01 (UTC+0100):
> 
> > On Fri, 2024-02-09 at 22:28 -0500, Felix Miata wrote:
> 
> > > Those from the above URL are the same spec batteries used in many APC 
> > > models.
> 
> > Maybe, maybe not.  I couldn't get replacement batteries for the UPS
> > from HP not only because HP was so ridiculous as to tell me that I
> > could pay for a support ticket to get a price for the batteries, but
> > also because the replacement batteries I could get had smaller
> > contacts.
> 
> Contact size is part of an SLA battery's specs. Small contacts are
> terminal type "F1". I've never encountered a UPS that uses them. All
> I've encountered use terminal type "F2", which is 1/4" or about
> 6.35mm wide spade.

I don't remember how wide the contacts are the UPS from HP uses.
6.35mm is probably a common size, same as yellow connectors use.
There are connectors of the same type that are wider than that.

> > At least you have some cooling.  Basically nobody here has that,
> > though it's probably becoming more widespread because it gets warmer
> > all the time, and it's unbearable in the summer.  Electricity is
> > insanely expensive here and keeps getting more expensive all the time.
> 
> It's a big planet. Where is your "here"?

Germany

> > Hm, if the OEM batteries actually lasted 5 years and if what you say
> > is true, they must have been some awesome batteries.  That UPS takes
> > two batteries which are tightly packed, and they can get very warm.
> 
> OEM batteries must hold up through warranties, so are probably more
> locally sourced for high quality rather than low cost from
> China. Less expensive UPS models might be designed for a shorter
> expected lifetime, overcharging more as they get older and heat
> takes its toll. It's not something very many consumers are equipped
> to test.

The cheap APC models seem to produce a lot more heat, and their
batteries don't seem to last as long.  They work and they're not
really a good deal.  I don't have test equipment for UPCs, but you can
feel how warm they get and see how cheaply they're built without
special equipment.

AW: AW: AW: su su- sudo dont work

[Schwibinger Michael]

Yes.


I found out
I do use an old kernel.

Can LINUX update a kernel?

Regards
Sophie



Von: chris 
Gesendet: Mittwoch, 7. Februar 2024 19:35
An: Schwibinger Michael 
Betreff: Re: AW: AW: su su- sudo dont work

Very helpful ty

On Wed, Feb 7, 2024, 1:57 PM Schwibinger Michael 
mailto:h...@hotmail.com>> wrote:
Good afternoon.

The bug report

sudo ...
You are not in the sudoers file.
Regards
Sophie



Von: Hans mailto:hans.ullr...@loop.de>>
Gesendet: Freitag, 26. Januar 2024 18:44
An: debian-user@lists.debian.org 
mailto:debian-user@lists.debian.org>>
Betreff: Re: AW: AW: su su- sudo dont work


Am Freitag, 26. Januar 2024, 17:23:07 CET schrieben Sie:

Yes, if you want to install soemthing for example by using the apt command, 
best way is becoming root with the command "su -" and then install the rquired 
package.


Example:

su -  then enter the password of the user root


If installing for example firefox, first read the repository:


apt update


then install the package


apt install firefox-esr


-


Hint: If you want a graphical method and you have no X and Wndow-Manager 
running (like KDE, Gnome, XFCE whatever), I suggest using aptitude.


You have to install aptitude first:


apt install aptitude


Then you can start the gui with the command "aptitude" as root.


Hint 2: aptitude is controlled by keypresses without any enter-key.

For example, when started aptitude, just press the "u" key and it reads the 
update, "U" (Shift + u)  marks all newer packages automatically to be updated, 
then press "g" and you will shwo, what it will do. Press "g" again, and it will 
do the update.


Please note: If you want to upgrade the whole sytem, then using apt or apt-get 
will be the better choice!


But aptitude is very well for installing single packages or weekly upgrades, 
where not much packages will be renewed.


If you are not much experienced, and you have a window-manager running like 
KDE, Gnome, XFCE, LXDE or another one, then look at synaptic. Synaptic is a 
graphical tool for installing packages, it is a GUI for apt.


Synaptic MUST run as root.


Hope this helps.


By the way: I believe, you are not very experienced in English language, so I 
suggest to suscribe in the fine German forum,

which is 
debian-user-ger...@lists.debioan.org.


Here is the link:

https://lists.debian.org/debian-user-german/


Good luck!


Hans



> Sorry

> it was my mistake

>

> It is

>

> su -

> su

> or sudo.

>

> Sorry.

>

> Is su -

> the best for install?

>

> Regards

>

> Sophie

>

>

> 

>

Re: Unidentified subject!

[Stefan Monnier]

>> AFAIK the bogus 128TB drives do properly report such ridiculous sizes:
>> the reality only hits when you try to actually store that amount of
>> information on them.
>> [ I'm not sure how it works under the hood, but since SSDs store their
>>data "anywhere" in the flash, they can easily pretend to have any size
>>they want, and allocate the physical flash blocks only on-the-fly as
>>logical blocks are being written.
>>Also, some Flash controllers use compression, so if you store data
>>that compresses well, they can let you store a lot more than if you
>>store already compressed data.  ]
>> IOW, to really check, try to save 2TB of videos (or other already
>> compressed data), and then try and read it back.
>> 
> Sounds like a lawsuit to me. If I can get Alexanders script from a few days
> back to run.  Is bash not actually bash these days? It is not doing for
> loops for me.

As discussed in related threads, there's the `f3` package in Debian
designed specifically for that.
You can try `f3probe /dev/sdX` (or use `f3write` and `f3read` if you
prefer to test at the filesystem level rather than at the block level).


Stefan

Re: shred bug?

[tomas]

On Sat, Feb 10, 2024 at 02:58:06PM +0100, Thomas Schmitt wrote:
> Hi,
> 
> to...@tuxteam.de wrote:
> > Ah, it seems to be this one, from 2002:
> >  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155175
> 
> So it's not a bug but a feature. :(
> 
> I'm riddling over the code about the connection to an old graphics
> algorithm (Bresenham's Algorithm) and how shred produces a random pattern
> at all.

This [1] perhaps? It's not a good random generator (and not crypto,
by a long stretch) but it's pretty well equidistributed, ain't it?

Cheers

[1] https://en.wikipedia.org/wiki/Lehmer_random_number_generator
-- 
t


signature.asc
Description: PGP signature

Re: D12 Installer does not recognize rtl8xxxu wifi

[Felix Natter]

Charles Curley  writes:
> On Thu, 08 Feb 2024 19:24:35 +0100
> Felix Natter  wrote:
>
>> If I start a shell from the installer, I can see that the necessary
>> module rtl8xxxu is loaded (the same one that is loaded in live
>> option). So I guess it is a firmware issue. How can I get an
>> installer with non-free firmware (if that is the problem)?
>> I just found one page that says the (non-free?) FW is always included
>> in the images (starting from bookworm). Is that true?
>> Any other idea?

hello Charles,

thank you for your reply. 

> My understanding is that the non-free firmware is now included on
> Debian installation media.

yes, it is pretty clearly stated here:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

> I've been using "Debian GNU/Linux 12.2.0 "Bookworm" - Official amd64
> NETINST with firmware 20231007-10:28" and had no problems with non-free
> firmware on my several computers.
>
> So to diagnose this further, exactly what hardware? Please run lspci,
> and run lspci -v for the offending device.
>
> Also, you can run the netinst installer at least through the relevant
> installation phase. Then please capture the logs, probably under
> /var/log. Searching syslog on the word "firmware" should turn up some
> interesting messages.

As I wrote in the other reply, I was mainly concerned about Wifi not
working after installation (I wanted to understand it). I can install
from LAN.

Many Thanks for the reply,
Felix
-- 
Felix Natter

Re: D12 Installer does not recognize rtl8xxxu wifi

[Felix Natter]

hello Franco,

thanks for the answer.

Franco Martelli  writes:
> On 08/02/24 at 19:24, Felix Natter wrote:
>> Dear debian-users,
>> I put this on a stick and booted it:
>> debian-live-12.4.0-amd64-gnome.iso
>> When I boot the live option, the network is immediately loaded and I can
>> connect to a WIFI network. However, if I use the same stick
>> (or one with debian 12.4.0 netinst) with the installation option,
>> the LAN is recognized, but WLAN is not.
>
> Hope I'm wrong, but I've heard that D-I has trouble with USB devices other
> than keyboard and mouse. The rtl8xxxu module is usually for USB NIC, if
> it's the case I think you can rely only to LAN for the installation.

I was mainly concerned with Wifi not working after installation. I
bought a long LAN cable and can install via LAN. Now that I understand
the limitation (a search on google seems to confirm this), I am not
worried any more :)

Many Thanks and Best Regards,
Felix
-- 
Felix Natter

Re: Erreur nvidia suite upgrade noyau 6.6.18

[Fabien Dubois]

Le 10/02/2024 à 15:10, ajh-valmer a écrit :

Bonjour,
Dommage que personne sur la liste ne puisse m'aider pour installer
le pilote graphique "Nouveau" et qu'il soit fonctionnel.
Devrais-je être obligé d'acheter une nouvelle carte vidéo plus récente ?
Bonne journée,
ajh Valmer


Bonjour,

Avec les liens déjà donnés tout s'installe sans souci. Bien faire 
apt-get purge *nvidia* pour tout enlever du pilote propriétaire. Après 
s'il y a un pb particulier sur votre ordi...
Par contre avec nouveau c'est Wayland qui est utilisé, et il a l'air pas 
mal bugué. En ce moment des soucis de pointeurs de souris (mais pas que...).
Et le pilote propriétaire qui devrait fonctionner avec wayland sous sid, 
gnome fait basculer automatiquement sous x11 au login.

Bref, désolé de ne pas aider plus.
Fabien

Re: Debian bookworm 12.4 installation wifi card not being detected

[Marco Moock]

Am Sat, 10 Feb 2024 05:55:17 -0600
schrieb Exeonz :

> I'm trying to install debian bookworm 12.4 on MacbookAir7,2 that
> doesn't have an ethernet port and the installer doesn't recognize
> it's wifi card and what drivers it needs for the card to work. From
> searching the web I found that it uses Broadcom BCM 4360 wireless
> network adapter and requires broadcom-sda-dkms firmware drivers to
> function.

Please run 
lspci -nnk
and post the result of the network card here.
That includes the ID and that makes it possible to identify it and find
the right driver/firmware.

Do you have a smart phone with a USB cable?
You can connect that and use tethering to get internet connection.

Re: Erreur nvidia suite upgrade noyau 6.6.18

[ajh-valmer]

On Friday 09 February 2024 18:47:09 ajh-valmer wrote:
> On Tuesday 06 February 2024 12:50:21 Fabien Dubois wrote:
> > > apt upgrade :
> > > c'est le module Nvidia qui empêche l'installation du noyau 6.6.18.
> > > Mon pilote Nvidia 470 est celui pêché sur le dépôt free de Debian.
> > > Je n'ai jamais réussi à installer un pilote "nouveau".

> J'ai donc fait un test sur une sauvegarde sous Bookworm,
> en purgeant nvidia.
> Cette fois l'upgrade se fait bien avec le noyau 6.6.18.
> J'ai tenté de réinstaller le pilote Nvidia 470, niet idem.
> Par contre, j'ai le mode graphique mais qu'en mode 1024X768 max 
> (trop faible). 
> Je désire maintenant un howto pour installer le pilote "nouveau".
> Cette commande ci-dessous m'affiche une erreur :
> dpkg --configure -a|--pending 
> Je n'ai plus la commande nvidia-detect.
> > https://wiki.debian.org/fr/NvidiaGraphicsDrivers
> > https://forums.debian.net/viewtopic.php?t=16
> > https://debian-facile.org/doc:materiel:cartes-graphique:nvidia:accueil :
> ne m'aident pas du tout.

Bonjour,
Dommage que personne sur la liste ne puisse m'aider pour installer
le pilote graphique "Nouveau" et qu'il soit fonctionnel.
Devrais-je être obligé d'acheter une nouvelle carte vidéo plus récente ?
Bonne journée,
ajh Valmer

Re: shred bug?

[Thomas Schmitt]

Hi,

to...@tuxteam.de wrote:
> Ah, it seems to be this one, from 2002:
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155175

So it's not a bug but a feature. :(

I'm riddling over the code about the connection to an old graphics
algorithm (Bresenham's Algorithm) and how shred produces a random pattern
at all.


Have a nice day :)

Thomas

Re: Home UPS recommendations

[Felix Miata]

hw composed on 2024-02-10 11:01 (UTC+0100):

> On Fri, 2024-02-09 at 22:28 -0500, Felix Miata wrote:

>> Those from the above URL are the same spec batteries used in many APC models.

> Maybe, maybe not.  I couldn't get replacement batteries for the UPS
> from HP not only because HP was so ridiculous as to tell me that I
> could pay for a support ticket to get a price for the batteries, but
> also because the replacement batteries I could get had smaller
> contacts.

Contact size is part of an SLA battery's specs. Small contacts are terminal type
"F1". I've never encountered a UPS that uses them. All I've encountered use
terminal type "F2", which is 1/4" or about 6.35mm wide spade.

> At least you have some cooling.  Basically nobody here has that,
> though it's probably becoming more widespread because it gets warmer
> all the time, and it's unbearable in the summer.  Electricity is
> insanely expensive here and keeps getting more expensive all the time.

It's a big planet. Where is your "here"?

> Hm, if the OEM batteries actually lasted 5 years and if what you say
> is true, they must have been some awesome batteries.  That UPS takes
> two batteries which are tightly packed, and they can get very warm.

OEM batteries must hold up through warranties, so are probably more locally
sourced for high quality rather than low cost from China. Less expensive UPS
models might be designed for a shorter expected lifetime, overcharging more as
they get older and heat takes its toll. It's not something very many consumers 
are
equipped to test.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: shred bug?

[Gremlin]

On 2/10/24 08:32, Thomas Schmitt wrote:

Hi,

i wrote:

   shred: -: invalid file type


to...@tuxteam.de wrote:

Hmm. This looks like a genuine bug: the man page mentions it.


Even the help text in
   https://sources.debian.org/src/coreutils/9.4-3/src/shred.c/
says
   If FILE is -, shred standard output.

The name "-" is recognized in line 1257 and leads to a call of wipefd()
in line 958. The error messages there look different from above.
So i hop from line 973 to do_wipefd() and find the message in line 845.
fd is supposed to be 1 (= stdout). fstat(2) was successful but now this
condition snaps:

   if ((S_ISCHR (st.st_mode) && isatty (fd))
   || S_ISFIFO (st.st_mode)
   || S_ISSOCK (st.st_mode))

The problem seems to be in the S_ISFIFO part.
In a little test program fstat() reports about fd==1:
   st.st_mode= 010600 , S_ISFIFO(st.st_mode)= 1
(st_mode shown in octal as in man 2 fstat.)

It looks like the test expects a pipe(2) file descriptor to be
classified as S_ISCHR and !isatty().
Without redirection through a pipe, fd 1 has st.st_mode 20620, S_ISCHR,
and isatty()==1. The isatty() result is indeed a good reason, not to
flood stdout by a zillion random bytes.


Does anybody have an old GNU/Linux system where a file descriptor from
pipe(2) is classified as character device (S_IFCHR, S_ISCHR) ?



What about dash?

Re: shred bug?

[Thomas Schmitt]

Hi,

i wrote:
> >   shred: -: invalid file type

to...@tuxteam.de wrote:
> Hmm. This looks like a genuine bug: the man page mentions it.

Even the help text in
  https://sources.debian.org/src/coreutils/9.4-3/src/shred.c/
says
  If FILE is -, shred standard output.

The name "-" is recognized in line 1257 and leads to a call of wipefd()
in line 958. The error messages there look different from above.
So i hop from line 973 to do_wipefd() and find the message in line 845.
fd is supposed to be 1 (= stdout). fstat(2) was successful but now this
condition snaps:

  if ((S_ISCHR (st.st_mode) && isatty (fd))
  || S_ISFIFO (st.st_mode)
  || S_ISSOCK (st.st_mode))

The problem seems to be in the S_ISFIFO part.
In a little test program fstat() reports about fd==1:
  st.st_mode= 010600 , S_ISFIFO(st.st_mode)= 1
(st_mode shown in octal as in man 2 fstat.)

It looks like the test expects a pipe(2) file descriptor to be
classified as S_ISCHR and !isatty().
Without redirection through a pipe, fd 1 has st.st_mode 20620, S_ISCHR,
and isatty()==1. The isatty() result is indeed a good reason, not to
flood stdout by a zillion random bytes.


Does anybody have an old GNU/Linux system where a file descriptor from
pipe(2) is classified as character device (S_IFCHR, S_ISCHR) ?

Does anybody have an idea why shred would want to exclude fifos ?
(What ciould shred do with a non-tty character device that cannot be done
 with a fifo ?)


Have a nice day :)

Thomas

Re: shred bug? [was: Unidentified subject!]

[tomas]

On Sat, Feb 10, 2024 at 01:40:35PM +0100, to...@tuxteam.de wrote:
> On Sat, Feb 10, 2024 at 11:38:21AM +0100, Thomas Schmitt wrote:
> 
> [...]
> 
> > But shred(1) on Debian 11 refuses on "-" contrary to its documentation:
> >   shred: -: invalid file type
> > A non-existing file path causes "No such file or directory".
> 
> Hmm. This looks like a genuine bug: the man page mentions it.
> 
> Also, /dev/stdout as target runs into the very same problem.

Ah, it seems to be this one, from 2002:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155175

which is archived. The argument seems to be that shred on stdout
doesn't make any sense, because the shell would truncate the
file anyway when you did

  shred - > /this/file/to/be/shredded

... which, of course, undermines shred's purpose. It seems they
hadn't your sneaky use case in mind :-)

Cheers
-- 
t


signature.asc
Description: PGP signature

shred bug? [was: Unidentified subject!]

[tomas]

On Sat, Feb 10, 2024 at 11:38:21AM +0100, Thomas Schmitt wrote:

[...]

> But shred(1) on Debian 11 refuses on "-" contrary to its documentation:
>   shred: -: invalid file type
> A non-existing file path causes "No such file or directory".

Hmm. This looks like a genuine bug: the man page mentions it.

Also, /dev/stdout as target runs into the very same problem.

Cheers
-- 
t


signature.asc
Description: PGP signature

Debian bookworm 12.4 installation wifi card not being detected

[Exeonz]

Hey thanks for your time in advance. I'm trying to install debian bookworm
12.4 on MacbookAir7,2 that doesn't have an ethernet port and the installer
doesn't recognize it's wifi card and what drivers it needs for the card to
work. From searching the web I found that it uses Broadcom BCM 4360
wireless network adapter and requires broadcom-sda-dkms firmware drivers to
function. The installer doesn't detect the wifi card and none of the
drivers from the select list work and when I use 2nd bootable USB formatted
as FAT32 with broadcom-sda-dkms firmware drivers saved to root and firmware
folder it doesn't accept drivers and gives out error "ethernet card not
found" I've looked through entire debian wiki and other wikis and forums
like arch wiki and found no answers anywhere. I have successfully installed
ubuntu on this macbook air and it works just fine with the wifi card. Could
you please shed some light on how I can possibly install debian on this
macbook air.

Some other things that I've tried that didn't work.
Every available driver from the install list.
Older non-free debian version 11.8.0 because I thought it would have
drivers but it didn't work either.
Downloading all firmware from https://cdimage.debian.org/cdimage/firmware/ onto
USB formatted as FAT32 in root and firmware folder
Using command line during installation for extra options to load drivers
off USB. (this command doesn't seem to work on bookwork 12.4)
https://wiki.debian.org/Firmware



*Installation+Archive+USBStickpreseed/early_command="modprobe vfat ; sleep
2 ;mount /dev/disk/by-label/FIRMWARE /media ;cp -a /media/firmware /lib"*
Using rtl8812au-5.2.20 firmware drivers
Ripping out firmware drivers from ubuntu install that works fine with this
wifi card and putting it on same USB
*bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu10~22.04.1_amd64*

Debian bookwork 12.4 installation wifi card not being detected

[Exeonz]

Hey thanks for your time in advance. I'm trying to install debian bookworm
12.4 on MacbookAir7,2 that doesn't have an ethernet port and the installer
doesn't recognize it's wifi card and what drivers it needs for the card to
work. From searching the web I found that it uses Broadcom BCM 4360
wireless network adapter and requires broadcom-sda-dkms firmware drivers to
function. The installer doesn't detect the wifi card and none of the
drivers from the select list work and when I use 2nd bootable USB formatted
as FAT32 with broadcom-sda-dkms firmware drivers saved to root and firmware
folder it doesn't accept drivers and gives out error "ethernet card not
found" I've looked through entire debian wiki and other wikis and forums
like arch wiki and found no answers anywhere. I have successfully installed
ubuntu on this macbook air and it works just fine with the wifi card. Could
you please shed some light on how I can possibly install debian on this
macbook air.

Some other things that I've tried that didn't work.
Every available driver from the install list.
Older non-free debian version 11.8.0 because I thought it would have
drivers but it didn't work either.
Downloading all firmware from https://cdimage.debian.org/cdimage/firmware/
onto USB formatted as FAT32 in root and firmware folder
Using command like during installation for extra option to load drivers off
USB. (this command doesn't seem to work on bookwork 12.4)
https://wiki.debian.org/Firmware



*Installation+Archive+USBStickpreseed/early_command="modprobe vfat ; sleep
2 ;mount /dev/disk/by-label/FIRMWARE /media ;cp -a /media/firmware /lib"*
Using rtl8812au-5.2.20 firmware drivers
Ripping out firmware drivers from ubuntu install that works fine with this
wifi card and putting it on same USB
*bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu10~22.04.1_amd64*

Re: Unidentified subject!

[Thomas Schmitt]

Hi,

Gene Heskett wrote:
> Is bash not actually bash these days? It is not doing for loops for me.

Come on Gene, be no sophie. Copy+paste your failing line here. :))


IIRC the for-loop in question writes several copies of the same file.
( https://lists.debian.org/debian-user/2024/02/msg00318.html )
Others already pointed out that this invites for firmware scams like
deduplication or silent overwriting of older data.

I would vote for a filesystem killer like
  shred -n 1 -s 204768K -v - | tee /dev/sdm1 | sha256sum
  dd if=/dev/sdm1 bs=32K count=6399 skip=32 | sha256sum

But shred(1) on Debian 11 refuses on "-" contrary to its documentation:
  shred: -: invalid file type
A non-existing file path causes "No such file or directory".


The filesystem killer aspect could be removed by creating large data files
in the readily partitioned and formatted filesystems of the disk.
(Replace "/dev/sdm1" by "/where/mounted/random_test_file" and reduce the
 numbers 204768K and bs=32K count=6399 to what you expect to
 fit into the filesystem. Like 20K and bs=32K count=6250.
 Ask df for storage capacities.)

But there needs to be a fast pseudo-random byte stream (which shred would
provide if i could talk it into writing to stdout) which you can split
for the device and for sha256sum.
I have an own weak-random generator, but shred beats it by a factor of 10
when writing to /dev/null.


Have a nice day :)

Thomas

Re: Home UPS recommendations

[hw]

On Fri, 2024-02-09 at 22:28 -0500, Felix Miata wrote:
> hw composed on 2024-02-10 03:18 (UTC+0100):
> [...]
> > Well, having batteries shipped over from the US would probably cost
> > more than a new UPS.
> 
> They are made in China. Surely there are UK sellers.

It might be cheaper to ship them from China than from the UK.
Apparently there's some kind of agreement in place that makes shipping
stuff from China (or Hong Kong) cheap --- but I don't know if it
applies to UPS batteries.

> The URL was simply provided
> as a representative of specifications of a very common SLA battery for UPS 
> type.
> 
> > That rules out Liebert, Cyperpower and Triplite due to uncertain or no
> > availability.  That only leaves Eaton.
> 
> Those from the above URL are the same spec batteries used in many APC models.

Maybe, maybe not.  I couldn't get replacement batteries for the UPS
from HP not only because HP was so ridiculous as to tell me that I
could pay for a support ticket to get a price for the batteries, but
also because the replacement batteries I could get had smaller
contacts.  Since I didn't want to take the risk of burning down the
place because the smaller contacts might have melted under load, I
decided to get a new UPS.

It wasn't too bad because I had only payed 65 for the UPS, and the
batteries lasted about 3 years.  I hate having to trash a perfectly
good UPS just because the batteries aren't available, and shame on HP
for being so environmentally friendly as to make and sell one-way
UPSs.  That kind of thing should be illegal.

But it was a lesson about battery availability.

> > Does Eaton provide their own Linux software and/or do they accept
> > monitoring results from other software like nut (assuming that apcupsd
> > won't work for Eaton UPSs)?
> 
> Mine are all connected to a multitude of devices more to protect the
> hardware from a lousy power source. I don't try to use the
> software. When power fails, I shut things down when the outage lasts
> more than a few seconds.

Well, I need the UPSs monitored so the computer(s) can shutdown
properly.

> When you live on a power grid, extended outages are much less common
> than when on or near waterfront or political boundaries. Most of
> Florida's population has no out-of-state neighbors to share
> utilities with, making its grid more fragile. Being the lightning
> capital of the world doesn't help either.

Did they put the power lines into the ground water or something like
that?

> > > Here in FL, replacement battery life averages under 30 months, no
> > > matter the battery brand. OEM batteries have averaged more like 54.
> 
> > How is that?  Do you have frequent power outages that stress the
> > batteries so much?
> The nature of the beasts is that their use generates heat. These batteries 
> don't
> like heat. The cooler they can be kept, the longer they can last. My 
> thermostat
> temp setting in heating season is 78F, in cooling season 82F, and cooling 
> season
> is much longer than heating season. In climates where heating season is most 
> of
> the year and tstat is kept below 65F, I'm guessing likely they could last a 
> decade
> or more.

At least you have some cooling.  Basically nobody here has that,
though it's probably becoming more widespread because it gets warmer
all the time, and it's unbearable in the summer.  Electricity is
insanely expensive here and keeps getting more expensive all the time.

> Battery orientation within the unit probably makes a difference, and
> even more, separation, with worst orientation side-by-side with no
> air space between. It's not easy to learn about such specs prior to
> purchase. UPS makers seem to want to keep battery specs top secret,
> out of marketing materials, even from manuals.

Hm, if the OEM batteries actually lasted 5 years and if what you say
is true, they must have been some awesome batteries.  That UPS takes
two batteries which are tightly packed, and they can get very warm.

Re: Unidentified subject!

[gene heskett]

On 2/7/24 23:28, Stefan Monnier wrote:

Well the 2T memory everybody was curious about 3 weeks ago got here early.

 From dmesg after plugging one in:
[629240.916163] usb 1-2: new high-speed USB device number 39 using xhci_hcd
[629241.066221] usb 1-2: New USB device found, idVendor=048d,
idProduct=1234, bcdDevice= 2.00
[629241.066234] usb 1-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[629241.066239] usb 1-2: Product: Disk 3.0
[629241.066242] usb 1-2: Manufacturer: USB
[629241.066246] usb 1-2: SerialNumber: 2697241127107725123
[629241.069485] usb-storage 1-2:1.0: USB Mass Storage device detected
[629241.074187] scsi host37: usb-storage 1-2:1.0
[629242.100738] scsi 37:0:0:0: Direct-Access  SSD 3.02.00
PQ: 0 ANSI: 4
[629242.100959] sd 37:0:0:0: Attached scsi generic sg13 type 0
[629242.101190] sd 37:0:0:0: [sdm] 409600 512-byte logical blocks: (2.10
TB/1.91 TiB)
[629242.101289] sd 37:0:0:0: [sdm] Write Protect is off
[629242.101290] sd 37:0:0:0: [sdm] Mode Sense: 03 00 00 00
[629242.101409] sd 37:0:0:0: [sdm] No Caching mode page found
[629242.101410] sd 37:0:0:0: [sdm] Assuming drive cache: write through
[629242.103927]  sdm: sdm1
[629242.104047] sd 37:0:0:0: [sdm] Attached SCSI disk
gene@coyote:

Looks like a reasonable facsimile of a 2T disk to me.


AFAIK the bogus 128TB drives do properly report such ridiculous sizes:
the reality only hits when you try to actually store that amount of
information on them.

[ I'm not sure how it works under the hood, but since SSDs store their
   data "anywhere" in the flash, they can easily pretend to have any size
   they want, and allocate the physical flash blocks only on-the-fly as
   logical blocks are being written.
   Also, some Flash controllers use compression, so if you store data
   that compresses well, they can let you store a lot more than if you
   store already compressed data.  ]

IOW, to really check, try to save 2TB of videos (or other already
compressed data), and then try and read it back.

Sounds like a lawsuit to me. If I can get Alexanders script from a few 
days back to run.  Is bash not actually bash these days? It is not doing 
for loops for me.


Thanks for the heads up, Stefan.


 Stefan

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: Generic Linux / clib question

[tomas]

On Sat, Feb 10, 2024 at 08:45:32AM +0100, Thomas Schmitt wrote:
> Hi,
> 
> Greg Wooledge wrote:
> > > The readline library is released under the full GPL, not the LGPL.  If
> > > you dynamically link it with a program, then you can only release that
> > > program under terms compatible with the GPL.  This is an intentional
> > > choice.
> 
> to...@tuxteam.de wrote:
> > Practically it doesn't change much, but for some lawyer at Intel it might.
> 
> A substantial problem can be that libreadline became "GPLv3 or later" a
> few years ago and that GPLv3 is not compatible with GPLv2-only (i.e. not
> "or later"). The main reason is in the patent-fighting restrictions in
> GPLv3, which would be forbidden extra restrictions under GPLv2.

Yep, thanks for pointing that out. The "main" program would then have to
be GPLv3 compatible. There's no perfect world, sigh.

Cheers
-- 
t


signature.asc
Description: PGP signature