Re: actualizar kernel para problema con wifi

[Camaleón]

El 2022-02-25 a las 00:04 -0300, Daniel escribió:

> Hola. Consulta bastante de novato, disculpas por eso (uso consola pero me
> suelo manejar mas en GUI).
> 
> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
> Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora instalación
> básica, sólo agregado Synaptic y poco más.
> 
> Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6 MT7921).

(...)

Revisa esta página donde te explican bien las opciones y alternativas 
que tienes, que no son pocas:

How to install driver for Wi-Fi Mediatek MT7921 and Mediatek MT7961 in 
Linux
https://miloserdov.org/?p=6899

> El equipo conecta perfecto cableado a Rj45.
> 
> La pregunta es: ¿es factible y aconsejable actualizar el kernel (solamente)
> a una versión posterior para solucionar el problema como encontré
> recomendado por allí?

Yo no lo haría porque del kernel dependen varios módulos y 
controladores que te pueden dejar de funcionar o dar problemas al 
mezclar entre distintas versiones.

Antes preferiría instalar Debian testing como ya te han comentado, con 
el reisgo inherente que conlleva.

Si el equipo es para uso personal, testing es una buena opción, yo 
llevo varios años ya con esa versión en mi equipo de pruebas y no he 
tenido ningún problema. Eso sí, me cuido bien antes de actualizar a lo 
loco, y espero unos días para ver que no haya bugs.

> y en ese caso: ¿un procedimiento adecuado seguro sería agregar el
> repositorio "testing" y actualizar el kernel al disponible en Synaptic?

Si fuera otro paquete el que necesitaras actualizar, te diría que sí, 
pero el kernel es mucha cosa como para ir jugando :-)

Saludos,

-- 
Camaleón 

Re: actualizar kernel para problema con wifi

[Alfonso Camacho]

Saludos:

No creo vayas a solucionar tú problema actualizando el kernel. Para mi es un 
clásico que después de que caiga en mis manos un portátil diferente tenga que 
instalar un firmware propietario para el dispositivo wifi sea reconocido y 
poder trabajar con él. En tu caso (MediaTek) parece que requiere instalar 
'firmware-misc-nonfree' y después reiniciar:

# apt update
# apt install firmware-misc-nonfree

https://blog.abysm.org/2020/03/mediatek-802-11ac-usb-wi-fi-linux-driver-installation/


- Mensaje original -
> De: "Daniel" 
> Para: "debian-user-spanish" 
> Enviados: Viernes, 25 de Febrero 2022 7:04:26
> Asunto: Re: actualizar kernel para problema con wifi

> Muchas gracias por las recomendaciones!!
> 
> El uso del equipo es familiar y de trabajo no experimental digamos.
> 
> Mi idea era (tal vez una locura) agregar el repositorio Testing,
> actualizar el kernel, solamente e inmediatamente quitar dicho repositorio.
> 
> Evaluaré el consejo, sí, de conseguir una wifi usb "hasta que aclare"
> como decimos aquí en el sur porque no veo otra solución (el error, ya lo
> se, ya me retaron por otro lado, es comprar sin investigar suficiente
> antes...)
> 
> La salida de lspci es:
> 
> 00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host
> Bridge/DRAM Registers (rev 01)
> 00:02.0 VGA compatible controller: Intel Corporation TigerLake GT2 [Iris
> Xe Graphics] (rev 01)
> 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
> 00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe
> Controller (rev 01)
> 00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI
> Express Root Port #1 (rev 01)
> 00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4
> USB Controller (rev 01)
> 00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4
> NHI #0 (rev 01)
> 00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1
> xHCI Host Controller (rev 20)
> 00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
> 00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP
> Serial IO I2C Controller #0 (rev 20)
> 00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP
> Serial IO I2C Controller #1 (rev 20)
> 00:16.0 Communication controller: Intel Corporation Tiger Lake-LP
> Management Engine Interface (rev 20)
> 00:1d.0 PCI bridge: Intel Corporation Tiger Lake-LP PCI Express Root
> Port #9 (rev 20)
> 00:1d.1 PCI bridge: Intel Corporation Device a0b1 (rev 20)
> 00:1d.3 PCI bridge: Intel Corporation Device a0b3 (rev 20)
> 00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
> 00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP
> Smart Sound Technology Audio Controller (rev 20)
> 00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
> 00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP
> SPI Controller (rev 20)
> 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (13)
> I219-V (rev 20)
> 04:00.0 Non-Volatile memory controller: Toshiba Corporation XG6 NVMe SSD
> Controller
> 09:00.0 Network controller: MEDIATEK Corp. Device 7961
> 0a:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller
> (rev 01)
> 

-- 
Alfonso 

Re: W10 sur kvm/qemu

[Michel Memeteau]

Tu peux t'inspirer de https://snapcraft.io/clouds

Le 24/02/2022 à 14:00, BERTRAND Joël a écrit :

Bonjour à tous,

Je fatigue...

J'essaie maintenant d'installer W10 sur une VM avec un disque virtio.
J'ai essayé plusieurs iso des pilotes et je me retrouve toujorus avec un
pilote virtio non installable... J'ai essayé :

virtio-win-0.1.172.iso  virtio-win-0.1.208.iso  virtio-win-0.1.215.iso

Une installation à la main en ligne de commande échoue aussi avec une
erreur cryptique.

Comment faire ?

Bien cordialement,

JKB




--
--
Michel Memeteau

Ekimia ( https://ekimia.fr )

Directeur

tel:0624808051

Address :
620 avenue de la roche fourcade
13400 Aubagne
France

Re: packages kept back on Debian stable

[Geoff]

L Dimov wrote:

As you and I both install the generic kernel linux-image-amd64, we
would expect to have to use  apt-get dist-upgrade  whenever there's
a new kernel version (because a version number is included in the
package name, so it's a "new" package).




apt upgrade will install new packages but not rip anything out.

Regards,
Geoff

Re: actualizar kernel para problema con wifi

[Daniel]

Muchas gracias por las recomendaciones!!

El uso del equipo es familiar y de trabajo no experimental digamos.

Mi idea era (tal vez una locura) agregar el repositorio Testing, 
actualizar el kernel, solamente e inmediatamente quitar dicho repositorio.


Evaluaré el consejo, sí, de conseguir una wifi usb "hasta que aclare" 
como decimos aquí en el sur porque no veo otra solución (el error, ya lo 
se, ya me retaron por otro lado, es comprar sin investigar suficiente 
antes...)


La salida de lspci es:

00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host 
Bridge/DRAM Registers (rev 01)
00:02.0 VGA compatible controller: Intel Corporation TigerLake GT2 [Iris 
Xe Graphics] (rev 01)

00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe 
Controller (rev 01)
00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI 
Express Root Port #1 (rev 01)
00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 
USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 
NHI #0 (rev 01)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 
xHCI Host Controller (rev 20)

00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP 
Serial IO I2C Controller #0 (rev 20)
00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP 
Serial IO I2C Controller #1 (rev 20)
00:16.0 Communication controller: Intel Corporation Tiger Lake-LP 
Management Engine Interface (rev 20)
00:1d.0 PCI bridge: Intel Corporation Tiger Lake-LP PCI Express Root 
Port #9 (rev 20)

00:1d.1 PCI bridge: Intel Corporation Device a0b1 (rev 20)
00:1d.3 PCI bridge: Intel Corporation Device a0b3 (rev 20)
00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP 
Smart Sound Technology Audio Controller (rev 20)

00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP 
SPI Controller (rev 20)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (13) 
I219-V (rev 20)
04:00.0 Non-Volatile memory controller: Toshiba Corporation XG6 NVMe SSD 
Controller

09:00.0 Network controller: MEDIATEK Corp. Device 7961
0a:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller 
(rev 01)


El 25/2/22 a las 01:18, Yoel Villarreal escribió:
No recomendaria agregar testing a tu sources.list, esas mezclas de 
dependencias suelen ser explosivas.


Que te dice el comando `lspci` ??

En 24 de febrero de 2022 10:05:02 p. m. Daniel 
 escribió:



Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
me suelo manejar mas en GUI).

Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
instalación básica, sólo agregado Synaptic y poco más.

Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6 
MT7921).


Tengo instalado el paquete de Firmware non-free. Busqué en web por
varios lados y por lo que encuentro aparentemente el problema está en la
versión del kernel que todavía no contiene controlador para este hard.

En configuración de redes aparece (pero inútil) la opción de agregar
coexión Wifi (me pide SSID y etc.) Entiendo que no puede manejar el
dispositivo y/o lo reconoce parcialmente.

En información de dispositivos USD indica:
Wireless_Device:  Fabricante: MediaTec Inc.
Clase   239 (Mescellaneous Device)
Subclase  2 (?)
Protocolo 0
Versión USB 2.10
ID del fabricante  0x489 (Foxconn/Hon Hai)
ID del producto    0xe0cd
Revisión  0
Velocidad    480 Mbits/s
Canales   0
Tamaño máximo de paquete  64

El equipo conecta perfecto cableado a Rj45.

La pregunta es: ¿es factible y aconsejable actualizar el kernel
(solamente) a una versión posterior para solucionar el problema como
encontré recomendado por allí?

y en ese caso: ¿un procedimiento adecuado seguro sería agregar el
repositorio "testing" y actualizar el kernel al disponible en Synaptic?

Bueno, desde ya gracias y disculpen la molestia.

Daniel


Enviado con Aqua Mail para Android 


https://www.mobisystems.com/aqua-mail

Re: actualizar kernel para problema con wifi

[Leonardo Marín]

El vie, 25 feb 2022 a las 0:04, Daniel ()
escribió:

> Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
> me suelo manejar mas en GUI).
>
> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
> Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
> instalación básica, sólo agregado Synaptic y poco más.
>
> Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6 MT7921).
>
> Tengo instalado el paquete de Firmware non-free. Busqué en web por
> varios lados y por lo que encuentro aparentemente el problema está en la
> versión del kernel que todavía no contiene controlador para este hard.
>
> En configuración de redes aparece (pero inútil) la opción de agregar
> coexión Wifi (me pide SSID y etc.) Entiendo que no puede manejar el
> dispositivo y/o lo reconoce parcialmente.
>
> En información de dispositivos USD indica:
> Wireless_Device:  Fabricante: MediaTec Inc.
> Clase   239 (Mescellaneous Device)
> Subclase  2 (?)
> Protocolo 0
> Versión USB 2.10
> ID del fabricante  0x489 (Foxconn/Hon Hai)
> ID del producto0xe0cd
> Revisión  0
> Velocidad480 Mbits/s
> Canales   0
> Tamaño máximo de paquete  64
>
> El equipo conecta perfecto cableado a Rj45.
>
> La pregunta es: ¿es factible y aconsejable actualizar el kernel
> (solamente) a una versión posterior para solucionar el problema como
> encontré recomendado por allí?


> y en ese caso: ¿un procedimiento adecuado seguro sería agregar el
> repositorio "testing" y actualizar el kernel al disponible en Synaptic?
>
depende para que estés utilizando el equipo, si es para trabajo y lo
necesitas siempre operativo veo más fácil comprar un adaptador usb que
funcione con linux hasta que el tema se solucione en futuras
actualizaciones y seguir con la versión estable,

si no es el caso y quieres probar si te recomiendo cambiar a testing,
la versión del kernel es la 5.16 y la de kde 5.23.5,

el firmware es otro tema, en mi caso tambien tuve problemas con el wifi,
una actualización y funcionaba bien y a la siguiente no, dejaba de
funcionar el BT, o funcionaba el BT pero no el wifi, una locura,
me aburri y desinstalé todo el firmware y lo cloné directo al disco con git,
si, terminas con un montón de firmware que no necesitas y hay que estarlo
"actualizando" de vez en cuando, pero no he tenido problemas desde entonces
y el firmware siempre está ahí,

saludos.


>
> Bueno, desde ya gracias y disculpen la molestia.
>
> Daniel
>
>
>
>

-- 
L.J.Marín
Usando: Debian Testing

Re: actualizar kernel para problema con wifi

[Yoel Villarreal]

No recomendaria agregar testing a tu sources.list, esas mezclas de 
dependencias suelen ser explosivas.


Que te dice el comando `lspci` ??

En 24 de febrero de 2022 10:05:02 p. m. Daniel 
 escribió:



Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
me suelo manejar mas en GUI).

Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
instalación básica, sólo agregado Synaptic y poco más.

Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6 MT7921).

Tengo instalado el paquete de Firmware non-free. Busqué en web por
varios lados y por lo que encuentro aparentemente el problema está en la
versión del kernel que todavía no contiene controlador para este hard.

En configuración de redes aparece (pero inútil) la opción de agregar
coexión Wifi (me pide SSID y etc.) Entiendo que no puede manejar el
dispositivo y/o lo reconoce parcialmente.

En información de dispositivos USD indica:
Wireless_Device:  Fabricante: MediaTec Inc.
Clase   239 (Mescellaneous Device)
Subclase  2 (?)
Protocolo 0
Versión USB 2.10
ID del fabricante  0x489 (Foxconn/Hon Hai)
ID del producto0xe0cd
Revisión  0
Velocidad480 Mbits/s
Canales   0
Tamaño máximo de paquete  64

El equipo conecta perfecto cableado a Rj45.

La pregunta es: ¿es factible y aconsejable actualizar el kernel
(solamente) a una versión posterior para solucionar el problema como
encontré recomendado por allí?

y en ese caso: ¿un procedimiento adecuado seguro sería agregar el
repositorio "testing" y actualizar el kernel al disponible en Synaptic?

Bueno, desde ya gracias y disculpen la molestia.

Daniel



Enviado con Aqua Mail para Android
https://www.mobisystems.com/aqua-mail

actualizar kernel para problema con wifi

[Daniel]

Hola. Consulta bastante de novato, disculpas por eso (uso consola pero 
me suelo manejar mas en GUI).


Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado 
Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora 
instalación básica, sólo agregado Synaptic y poco más.


Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6 MT7921).

Tengo instalado el paquete de Firmware non-free. Busqué en web por 
varios lados y por lo que encuentro aparentemente el problema está en la 
versión del kernel que todavía no contiene controlador para este hard.


En configuración de redes aparece (pero inútil) la opción de agregar 
coexión Wifi (me pide SSID y etc.) Entiendo que no puede manejar el 
dispositivo y/o lo reconoce parcialmente.


En información de dispositivos USD indica:
Wireless_Device:  Fabricante: MediaTec Inc.
Clase   239 (Mescellaneous Device)
Subclase  2 (?)
Protocolo 0
Versión USB 2.10
ID del fabricante  0x489 (Foxconn/Hon Hai)
ID del producto    0xe0cd
Revisión  0
Velocidad    480 Mbits/s
Canales   0
Tamaño máximo de paquete  64

El equipo conecta perfecto cableado a Rj45.

La pregunta es: ¿es factible y aconsejable actualizar el kernel 
(solamente) a una versión posterior para solucionar el problema como 
encontré recomendado por allí?


y en ese caso: ¿un procedimiento adecuado seguro sería agregar el 
repositorio "testing" y actualizar el kernel al disponible en Synaptic?


Bueno, desde ya gracias y disculpen la molestia.

Daniel

Re: Tarjeta de sonido USB

[Leonardo Marín]

El jue, 24 feb 2022 a las 8:54, Josu Lazkano ()
escribió:

> Gracias a los dos.
>
> Pero sigue sin funcionar, he reiniciado el servidor, pero da el mismo
> error.
>
> Lo de instalar más módulos, no sabría que más instalar, en el enlace
> ejecuta "armbian-config", pero no es mi caso.
>
> Parece que el problema es que no lo detecta como dispositivo por defecto,
> ya que el "alsamixer" a secas no le gusta, pero con el parámetro del
> dispositivo si que funciona: "alsamixer -c 1".
>
no está claro que DE estás utilizando, y qué controlador de sonido usas,

probaste con instalar pulseaudio?, si solo tienes alsa quizás le esté
costando hacer el trabajo,

creo que vi en el 1er correo que el chip del usb de sonido es cmedia,
revisa que modelo es y comprueba si está soportado en el kernel, que lo
probable es que si,
saludos.


>
> Seguiré investigando un poco más.
>
> Un saludo.
>
> --
> Josu Lazkano
>


-- 
L.J.Marín
Usando: Debian Testing

Re: Ouvrir un PDF signé avec Docusign. Associer un fichier à une application spécifique

[Haricophile]

Le Wed, 23 Feb 2022 10:17:00 +0100,
Olivier  a écrit :

> J'ai pensé à créer une extension de fichier comme docusignpdf, à
> renommer mon fichier avec cette extension et à associer cette
> extension à Firefox

Je ne sais pas s'il y a une manière de faire satisfaisante avec
XDG, mais il doit y avoir moyen de faire un script. 

Il n'y a pas de nombre magique et je ne crois pas qu'il y ait un moyen
fiable d'identifier un PDF signé, sinon en parsant le document. 

J'utiliserais pdfgrep ou autre chose. Il doit bien y avoir un
"AOP_DIGITAL_CERTIFICATE" ou quelque chose comme ça qui traîne pas
loin du début du document pour identifier si le document est signé ou
pas, voir quelle signature est utilisée. Après tu fais le traitement que
tu veux, tu associe le PDF a ton script placé dans /usr/local/bin ou
/opt et roulez jeunesse.

Mais ça demande un petit bout de code en bash ou python par exemple.
Je n'ai pas cherché si quelqu'un avait déjà inventé la roue ;)

-- 
Jérôme

Re: Tarjeta de sonido USB

[Richard]

en el enlace que enviaste en las preguntas al vendedor alguien le 
pregunta si sirve para linux y el vendedor contesta que no, ya se muchos 
vendedores no tienen idea pero bueno es un dato a tomar en cuenta, 
quizas un desafio hacerlo funcionar correctamente en linux, saludos


El 24/02/2022 a las 08:58 a. m., Camaleón escribió:

El 2022-02-24 a las 12:53 +0100, Josu Lazkano escribió:


Gracias a los dos.

Pero sigue sin funcionar, he reiniciado el servidor, pero da el mismo error.

Lo de instalar más módulos, no sabría que más instalar, en el enlace
ejecuta "armbian-config", pero no es mi caso.

Esa orden no es para Debian :-)

Lo que te sugiere el artículo es que revises, si en tu caso y debido al
chipset de la tarjeta, no necesites cargar módulos de sonido
adicionales a los que el sistema carga de manera predeterminada.


Parece que el problema es que no lo detecta como dispositivo por defecto,
ya que el "alsamixer" a secas no le gusta, pero con el parámetro del
dispositivo si que funciona: "alsamixer -c 1".

Seguiré investigando un poco más.

Ya nos dirás si al final has logrado hacerla funcionar.

Saludos,

Re : Ouvrir un PDF signé avec Docusign. Associer un fichier à une application spécifique

[k6dedijon]

Bonjour Olivier,
Peut-être que PDFCrack peut permettre de l'ouvrir avec okular.
Bon courage
Cassis



- Mail d'origine -
De: Olivier 
À: ML Debian User French 
Envoyé: Wed, 23 Feb 2022 10:17:00 +0100 (CET)
Objet: Ouvrir un PDF signé avec Docusign. Associer un fichier à une application 
spécifique

Bonjour,

J'ai dernièrement reçu un fichier PDF correspondant à un devis signé
avec Docusign.

Sur Debian Buster, l'application Visonneur de Document m'affiche "PDF
document is damaged".
Par contre, je peut ouvrir ledit fichier avec Firefox.

J'ai pensé à créer une extension de fichier comme docusignpdf, à
renommer mon fichier avec cette extension et à associer cette
extension à Firefox

Existe-t-il un moyen plus approprié pour associer une application
particulière (ici Firefox) à un fichier particulier ?

Slts

Re: W10 sur kvm/qemu

[BERTRAND Joël]

didier gaumet a écrit :
> 
> - Je ne me souviens pas avoir eu de problèmes avec les versions de
> pilotes RedHat et il me semble avoir toujours utilisé ce dont je
> disposais à ce moment-là généralement la dernière version mais pas
> forcément vu que je ne vérifie pas le site RedHat)
> 
> - je ne me souviens plus trop mais en fait les fichiers .inf de Windows
> sont plutôt des fichiers d'informations sur les pilotes mais les
> pilotes eux-mêmes sont plutôt des .sys ou quelque chose du genre, non?
> (peux pas vérifier pour le moment, j'ai plus de machine virtuelle win)

Je suis en train de me demander si mon problème ne provient pas du fait
que l'image disque est sur un disque réseau exporté par NFS. Je ne vois
pas ce qui change par rapport à toute la doc que je trouve sur internet.

JKB

Re: My printer doesn't work for bullseye's cups

[Brian]

On Thu 24 Feb 2022 at 14:39:55 -0500, gene heskett wrote:

> On Thursday, February 24, 2022 1:08:26 PM EST Brian wrote:
> > On Wed 23 Feb 2022 at 18:44:37 -0500, gene heskett wrote:
> > 
> > [...[
> > 
> > > With all the crash and burn sessions I've had with bullseye, I'd have
> > > to go get the drivers anew from Brother if cups-everywhere can't do
> > > it.
> > It is possible it may yet come to that.
> > 
> > > Is that what I have to do for this printer? FWIW No Brother printers
> > > show up at all in the ppd selection menu.
> > > 
> > > Might be related:
> > > sane-find-scanner, run as root, finds the scanner in this MFC at:
> > > 
> > > found USB scanner (vendor=0x04f9 [Brother], product=0x02f5
> > > [MFC-J6920DW]) at libusb:003:005
> > > 
> > > but xsane can't find it. So both the printer and the scanner are on
> > > the injured list.
> > 
> > Let's put scanning on one side for the time being.
> > 
> > 1. Read the Release Notes for Debian 11.
> > 
> > 2. Disconnect fro USB. It complicates matters.
> > 
> I would much rather the installer was taught to iterrogate whats beyond 
> an fdti serial adaptor, they are used to drive far more than braille 
> interfaces, or make the installer as the user if they WANT the speech 
> dispatcher and brltty. I don't, and the only way I've found to control 
> all that BS is to edit their configs to send their screaming fits aboiut 
> not finding brltty, to /dev/null.  Blaming the user for not disconnecting 
> a usb tree that looks like a weeping willow is at best poor form.
> 
> Then refusing to advise that user howe to legally uniinstall that crap 
> just frosts the cake.  Fix the damned installer.
> 
> As for my printer, I'll install the Brother drivers, they've Just Worked 
> for over a decade now.
>  
> > 3. Give
> >avahi-browse -rt _ipp._tcp
> >avahi-browse -rt _uscan._tcp
> >driverless
> 
> And what will that do, except further screw things up.
> 
> Avahi is another of those unwanted "helpers". I've had to disable or 
> uninstal it since wheezy because it insists on overwriteing the route to 
> the network with bogus 169.xx.yy.zz numbers.
> 
> > 4. avahi-browse is in the avahi-utils package.
> 
> And have it wreck this installs host file based network? I think not.
> 
> I originally asked how to get rid of brltty. And was ignored. No one has 
> suggested a course of action except yet anothr install AFTER gutting the 
> system of usb which would include the keyboard and mouse.
> 
> Stop ignoring the users complaints and fix the installer, at the very 
> least by asking the user if he wants it, and don't install it if he says 
> no. I have no problem with aiding the blind, but make even him confirm he 
> wants it before its made a permanent part of the install.
> 
> Currently, if its enabled at install, and removed 30 minutes later, the 
> system stops forever about 10 seconds into a reboot because it can't find 
> it, but thats without any sign of a log saying why it won't reboot.  I 
> did 4 installs proving that boot stall was that once I managed at get 4 
> out of 2+2.  You may take it that yes, I'm unhappy. This was far more 
> annoying than it was years ago when I installed stretch. I had forgotten 
> about that, but that didn't lead to 15 or 20 reinstalls like this did 
> either.
> 
> No Cheers, Gene Heskett.
> -- 
> "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
> Genes Web page 

Years ago I resolved never to get involved with your printing syste. I
broke that resolution today because I thought you really needed help.
One lives and learns.

Your response has been the worst I have ever met from any user. It does
not addresss a single requested point for information. The questions
have been completely ignored. Basically, you haven't a clue what you are
doing regarding printing, so you construct a narrative to pull the wool
over users' eyes. This is your standard technique.

The response is also ill-informed, technically deficient, ignorent of
what is invlved on bullseye and dismissive. In short, it displays an
uderstanding of our printing system that is pathetic.

On the bright side: Your self-serving response makes you eligible for the
Piss Artist of the Year award.

-- 
Brian.

Re: My printer doesn't work for bullseye's cups

[Andrew M.A. Cater]

On Thu, Feb 24, 2022 at 02:39:55PM -0500, gene heskett wrote:
> On Thursday, February 24, 2022 1:08:26 PM EST Brian wrote:
> > On Wed 23 Feb 2022 at 18:44:37 -0500, gene heskett wrote:
> > 
> > [...[
> > 
> > > With all the crash and burn sessions I've had with bullseye, I'd have
> > > to go get the drivers anew from Brother if cups-everywhere can't do
> > > it.
> > It is possible it may yet come to that.
> > 
> > > Is that what I have to do for this printer? FWIW No Brother printers
> > > show up at all in the ppd selection menu.
> > > 
> > > Might be related:
> > > sane-find-scanner, run as root, finds the scanner in this MFC at:
> > > 
> > > found USB scanner (vendor=0x04f9 [Brother], product=0x02f5
> > > [MFC-J6920DW]) at libusb:003:005
> > > 
> > > but xsane can't find it. So both the printer and the scanner are on
> > > the injured list.
> > 
> > Let's put scanning on one side for the time being.
> > 
> > 1. Read the Release Notes for Debian 11.
> > 
> > 2. Disconnect fro USB. It complicates matters.
> > 

Hi Gene,

> I would much rather the installer was taught to iterrogate whats beyond 
> an fdti serial adaptor, they are used to drive far more than braille 
> interfaces, or make the installer as the user if they WANT the speech 
> dispatcher and brltty. I don't, and the only way I've found to control 
> all that BS is to edit their configs to send their screaming fits aboiut 
> not finding brltty, to /dev/null.  Blaming the user for not disconnecting 
> a usb tree that looks like a weeping willow is at best poor form.

You're not a visually impaired user absolutely reliant on speech output / 
a Braille display. That step is there for them: there's a beep - if you hit
s on that, you get speech (mostly) for the remainder of the install.

If you have a brltty as a serial device, the installer does a check for serial
and tries to activate something that will make it work.

If you do neither, the installer goes right over that and there's no effect
for anyone else. It costs you relatively little to do a clean install
- which will go nowhere near brltty - by disconnecting serial devices briefly.
You're capable and you can make use of your sight.

Blaming everybody else - even those who are trying to help you - isn't helping
endear folks to your approach.

If not, I've told you how to remove brltty neatly by removing the packages and
their reverse dependencies.
> 
> Then refusing to advise that user howe to legally uniinstall that crap 
> just frosts the cake.  Fix the damned installer.
> 

The installer is fine: I've used it many, many times - including deliberately
testing speech output / high contrast installs to check they worked.

> As for my printer, I'll install the Brother drivers, they've Just Worked 
> for over a decade now.
>  
> > 3. Give
> >avahi-browse -rt _ipp._tcp
> >avahi-browse -rt _uscan._tcp
> >driverless
> 
> And what will that do, except further screw things up.
> 

Folks are trying to be polite and helpful. You may find that you no longer
need the Brother drivers: driverless printing works for many more printers 
now.

Similarly - if you have two interfaces plugged into the same printer,
it's sometimes harder to debug: if you want a network printer, set it up
as such without needing USB, perhaps?

> Avahi is another of those unwanted "helpers". I've had to disable or 
> uninstal it since wheezy because it insists on overwriteing the route to 
> the network with bogus 169.xx.yy.zz numbers.
> 
> > 4. avahi-browse is in the avahi-utils package.
> 
> And have it wreck this installs host file based network? I think not.
> 

Host file based networks have already been done to death on another thread
of yours, I think.

> I originally asked how to get rid of brltty. And was ignored. No one has 
> suggested a course of action except yet anothr install AFTER gutting the 
> system of usb which would include the keyboard and mouse.
> 

See above: you weren't ignored.

USB serial _doesn't_ include the keyboard and mouse if you're using a USB 
wireless dongle: if it did, I would also hae had the same issues you have.

> Stop ignoring the users complaints and fix the installer, at the very 
> least by asking the user if he wants it, and don't install it if he says 
> no. I have no problem with aiding the blind, but make even him confirm he 
> wants it before its made a permanent part of the install.
> 
> Currently, if its enabled at install, and removed 30 minutes later, the 
> system stops forever about 10 seconds into a reboot because it can't find 
> it, but thats without any sign of a log saying why it won't reboot.  I 
> did 4 installs proving that boot stall was that once I managed at get 4 
> out of 2+2.  You may take it that yes, I'm unhappy. This was far more 
> annoying than it was years ago when I installed stretch. I had forgotten 
> about that, but that didn't lead to 15 or 20 reinstalls like this did 
> either.
> 

Please help us to help you by detailing problems and 

Re: packages kept back on Debian stable

[David Wright]

On Thu 24 Feb 2022 at 18:32:47 (+), L Dimov wrote:
> On Thursday, February 24, 2022, 01:12:48 PM EST, David Wright 
>  wrote:  
> >  On Thu 24 Feb 2022 at 17:50:28 (+), L Dimov wrote:
> > > On Thursday, February 24, 2022, 12:39:27 PM EST, Greg Wooledge 
> > >  wrote:  
> > > >  On Thu, Feb 24, 2022 at 05:32:45PM +, L Dimov wrote:
> > > > > Is it normal that for a while now, maybe 2 or so weeks, these 17 
> > > > > packages are continuing to be kept back? I am on Debian 11 Bullseye 
> > > > > stable with only main repositories.
> > > > > 
> > > > > The following packages have been kept back:
> > > > >   gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 
> > > > > libjavascriptcoregtk-4.0-18 libreoffice libreoffice-base 
> > > > > libreoffice-base-core
> > > > >   libreoffice-base-drivers libreoffice-calc libreoffice-common 
> > > > > libreoffice-core libreoffice-draw libreoffice-impress libreoffice-math
> > > > >   libreoffice-writer libwebkit2gtk-4.0-37 linux-image-amd64 
> > > > > python3-uno
> > > > > 0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
> > > > > 
> > > > What command are you typing to get this result?  If you're using
> > > > "apt-get upgrade", try "apt-get dist-upgrade" instead, or if you prefer,
> > > > "apt-get --with-new-pkgs upgrade".
> > > I do indeed use apt-get update and apt-get upgrade, and I am aware that 
> > > there are ways I can force them to upgrade, but should I?
> > 
> > apt-get is a good tool to use, but only if you learn how
> > to use it effectively. You're not going to "force" anything.
> > You merely have to allow libopengl0 to be installed so that
> > libjavascriptcoregtk-4.0-18 and libwebkit2gtk-4.0-37 can be
> > upgraded.
> 
> In that case, should I be running the dist-upgrade every time I encounter 
> such the issue of packages being kept back? 
> Here is the output from apt-get dist-upgrade by the way:
> 
> The following NEW packages will be installed:  libabsl20200923 libopengl0 
> linux-image-5.10.0-11-amd64
> The following packages will be upgraded:
>   gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libjavascriptcoregtk-4.0-18 
> libreoffice libreoffice-base libreoffice-base-core
>   libreoffice-base-drivers libreoffice-calc libreoffice-common 
> libreoffice-core libreoffice-draw libreoffice-impress libreoffice-math
>   libreoffice-writer libwebkit2gtk-4.0-37 linux-image-amd64 python3-uno
> 17 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/163 MB of archives.
> After this operation, 312 MB of additional disk space will be used.
> Do you want to continue? [Y/n] 

As you and I both install the generic kernel linux-image-amd64, we
would expect to have to use   apt-get dist-upgrade   whenever there's
a new kernel version (because a version number is included in the
package name, so it's a "new" package).

The other two are more unusual; so for example I have only needed
dist-upgrade once in two years on this buster system, last June.

I've just installed libopengl0 on my bullseye, but didn't require
libabsl20200923, perhaps (at first glance) because I don't have
those gir1.2* packages shown above.

But yes, always check with dist-upgrade whenever packages are held
back, and inspect the output.

And BTW, the more frequently you upgrade your system, the lower the
probability that you will hit three of these occurrences at the same
time. (The kernel upgrade was available before the end of January.)

Cheers,
David.

Re: My printer doesn't work for bullseye's cups

[tomas]

On Thu, Feb 24, 2022 at 02:39:55PM -0500, gene heskett wrote:

[...]

> I would much rather the installer was taught to iterrogate whats beyond 

[rest of rant deleted]

Gene,

this is no paid-for service (and even if it were, this kind of
ranting at people is still unwarranted for). The software is
made by volunteers, at no cost to you. The help is given by
volunteers, again, at no cost to you.

I understand that dealing with software can be frustrating at
times. But your way to rant at people isn't justified by that,
IMHO.

Go let steam off the way you prefer before posting here. This
would even make your posts easier to understand (what the hell
is a rant about BRLTTY doing here? I thought you have a problem
with CUPS?).

Be considerate. Help others help you.

As far as I'm concerned, I feel less and less motivated to
help you (in the concrete case I couldn't anyway, since
CUPS is not my home turf).

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: My printer doesn't work for bullseye's cups

[gene heskett]

On Thursday, February 24, 2022 1:08:26 PM EST Brian wrote:
> On Wed 23 Feb 2022 at 18:44:37 -0500, gene heskett wrote:
> 
> [...[
> 
> > With all the crash and burn sessions I've had with bullseye, I'd have
> > to go get the drivers anew from Brother if cups-everywhere can't do
> > it.
> It is possible it may yet come to that.
> 
> > Is that what I have to do for this printer? FWIW No Brother printers
> > show up at all in the ppd selection menu.
> > 
> > Might be related:
> > sane-find-scanner, run as root, finds the scanner in this MFC at:
> > 
> > found USB scanner (vendor=0x04f9 [Brother], product=0x02f5
> > [MFC-J6920DW]) at libusb:003:005
> > 
> > but xsane can't find it. So both the printer and the scanner are on
> > the injured list.
> 
> Let's put scanning on one side for the time being.
> 
> 1. Read the Release Notes for Debian 11.
> 
> 2. Disconnect fro USB. It complicates matters.
> 
I would much rather the installer was taught to iterrogate whats beyond 
an fdti serial adaptor, they are used to drive far more than braille 
interfaces, or make the installer as the user if they WANT the speech 
dispatcher and brltty. I don't, and the only way I've found to control 
all that BS is to edit their configs to send their screaming fits aboiut 
not finding brltty, to /dev/null.  Blaming the user for not disconnecting 
a usb tree that looks like a weeping willow is at best poor form.

Then refusing to advise that user howe to legally uniinstall that crap 
just frosts the cake.  Fix the damned installer.

As for my printer, I'll install the Brother drivers, they've Just Worked 
for over a decade now.
 
> 3. Give
>avahi-browse -rt _ipp._tcp
>avahi-browse -rt _uscan._tcp
>driverless

And what will that do, except further screw things up.

Avahi is another of those unwanted "helpers". I've had to disable or 
uninstal it since wheezy because it insists on overwriteing the route to 
the network with bogus 169.xx.yy.zz numbers.

> 4. avahi-browse is in the avahi-utils package.

And have it wreck this installs host file based network? I think not.

I originally asked how to get rid of brltty. And was ignored. No one has 
suggested a course of action except yet anothr install AFTER gutting the 
system of usb which would include the keyboard and mouse.

Stop ignoring the users complaints and fix the installer, at the very 
least by asking the user if he wants it, and don't install it if he says 
no. I have no problem with aiding the blind, but make even him confirm he 
wants it before its made a permanent part of the install.

Currently, if its enabled at install, and removed 30 minutes later, the 
system stops forever about 10 seconds into a reboot because it can't find 
it, but thats without any sign of a log saying why it won't reboot.  I 
did 4 installs proving that boot stall was that once I managed at get 4 
out of 2+2.  You may take it that yes, I'm unhappy. This was far more 
annoying than it was years ago when I installed stretch. I had forgotten 
about that, but that didn't lead to 15 or 20 reinstalls like this did 
either.

No Cheers, Gene Heskett.
-- 
"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
Genes Web page 

Re: packages kept back on Debian stable

[Christian Britz]

On 2022-02-24 19:32 UTC+0100, L Dimov wrote:
> The following NEW packages will be installed:
>   libabsl20200923 libopengl0 linux-image-5.10.0-11-amd64
These are legitimate Debian packages which are also installed on my
Bullseye system. Apparently, some dependencies have changed.

-- 
http://www.cb-fraggle.de

Re: packages kept back on Debian stable

[David Wright]

On Thu 24 Feb 2022 at 17:50:28 (+), L Dimov wrote:
> On Thursday, February 24, 2022, 12:39:27 PM EST, Greg Wooledge 
>  wrote:  
> >  On Thu, Feb 24, 2022 at 05:32:45PM +, L Dimov wrote:
> > > Is it normal that for a while now, maybe 2 or so weeks, these 17 packages 
> > > are continuing to be kept back? I am on Debian 11 Bullseye stable with 
> > > only main repositories.
> > > 
> > > The following packages have been kept back:
> > >   gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 
> > > libjavascriptcoregtk-4.0-18 libreoffice libreoffice-base 
> > > libreoffice-base-core
> > >   libreoffice-base-drivers libreoffice-calc libreoffice-common 
> > > libreoffice-core libreoffice-draw libreoffice-impress libreoffice-math
> > >   libreoffice-writer libwebkit2gtk-4.0-37 linux-image-amd64 python3-uno
> > > 0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
> > > 
> > What command are you typing to get this result?  If you're using
> > "apt-get upgrade", try "apt-get dist-upgrade" instead, or if you prefer,
> > "apt-get --with-new-pkgs upgrade".
> I do indeed use apt-get update and apt-get upgrade, and I am aware that there 
> are ways I can force them to upgrade, but should I?

apt-get is a good tool to use, but only if you learn how
to use it effectively. You're not going to "force" anything.
You merely have to allow libopengl0 to be installed so that
libjavascriptcoregtk-4.0-18 and libwebkit2gtk-4.0-37 can be
upgraded.

Cheers,
David.

Re: packages kept back on Debian stable

[Christian Britz]

On 2022-02-24 18:50 UTC+0100, L Dimov wrote:

> I do indeed use apt-get update and apt-get upgrade, and I am aware that
> there are ways I can force them to upgrade, but should I?

At least it will help you to analyze the situation, you still can cancel
the operation.
IMO this is not a normal situation on the stable distribution. Maybe
packages from outside Debian are affected?

-- 
http://www.cb-fraggle.de

Re: My printer doesn't work for bullseye's cups

[Brian]

On Thu 24 Feb 2022 at 09:26:40 -0300, Eduardo M KALINOWSKI wrote:

> On 24/02/2022 06:35, Klaus Singvogel wrote:
> > linuxprinting.org showed me, that your printer Brother MFC-J6920DW is
> > listed as paperweight only, regarding Open Source drivres.
> 
> It seems to support AirPrint (https://support.apple.com/en-us/HT201311), so
> driverless printing (actually a universal driver) should work.
> 
> This wiki page has some instructions:
> https://wiki.debian.org/CUPSDriverlessPrinting . It's a bit confusing,
> though.

Please pinpoint the source(s) of confusion.

-- 
Brian.

Re: My printer doesn't work for bullseye's cups

[Brian]

On Wed 23 Feb 2022 at 18:44:37 -0500, gene heskett wrote:

[...[

> With all the crash and burn sessions I've had with bullseye, I'd have to 
> go get the drivers anew from Brother if cups-everywhere can't do it.

It is possible it may yet come to that.

> Is that what I have to do for this printer? FWIW No Brother printers show 
> up at all in the ppd selection menu.
> 
> Might be related:
> sane-find-scanner, run as root, finds the scanner in this MFC at:
>  
> found USB scanner (vendor=0x04f9 [Brother], product=0x02f5 [MFC-J6920DW]) 
> at libusb:003:005
> 
> but xsane can't find it. So both the printer and the scanner are on the 
> injured list.

Let's put scanning on one side for the time being.

1. Read the Release Notes for Debian 11.

2. Disconnect fro USB. It complicates matters.

3. Give
   avahi-browse -rt _ipp._tcp
   avahi-browse -rt _uscan._tcp
   driverless

4. avahi-browse is in the avahi-utils package.

-- 
Brian.

Re: packages kept back on Debian stable

[Greg Wooledge]

On Thu, Feb 24, 2022 at 05:32:45PM +, L Dimov wrote:
> Is it normal that for a while now, maybe 2 or so weeks, these 17 packages are 
> continuing to be kept back? I am on Debian 11 Bullseye stable with only main 
> repositories.
> 
> The following packages have been kept back:
>   gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libjavascriptcoregtk-4.0-18 
> libreoffice libreoffice-base libreoffice-base-core
>   libreoffice-base-drivers libreoffice-calc libreoffice-common 
> libreoffice-core libreoffice-draw libreoffice-impress libreoffice-math
>   libreoffice-writer libwebkit2gtk-4.0-37 linux-image-amd64 python3-uno
> 0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
> 
> Thanks!Luben

What command are you typing to get this result?  If you're using
"apt-get upgrade", try "apt-get dist-upgrade" instead, or if you prefer,
"apt-get --with-new-pkgs upgrade".

Re: W10 sur kvm/qemu

[didier gaumet]

- Je ne me souviens pas avoir eu de problèmes avec les versions de
pilotes RedHat et il me semble avoir toujours utilisé ce dont je
disposais à ce moment-là généralement la dernière version mais pas
forcément vu que je ne vérifie pas le site RedHat)

- je ne me souviens plus trop mais en fait les fichiers .inf de Windows
sont plutôt des fichiers d'informations sur les pilotes mais les
pilotes eux-mêmes sont plutôt des .sys ou quelque chose du genre, non?
(peux pas vérifier pour le moment, j'ai plus de machine virtuelle win)

Re: W10 sur kvm/qemu

[BERTRAND Joël]

Patrick ZAJDA a écrit :
> Hello,
> 
> 
> J'ai une VM windows 10 installée en suivant ce tuto :
> https://dennisnotes.com/note/20180614-ubuntu-18.04-qemu-setup/
> 
> J'avais pris la dernière version.
> 
> 
> Vu que ça fait un moment, je ne me souviens pas suffisamment pour t'en
> dire plus que "j'ai utilisé ce tuto" ;)
> 
> Il explique pour installer le pilote dès l'installation de Windows.

C'est très exactement ce que je fais... sans succès.

Re: W10 sur kvm/qemu

[BERTRAND Joël]

didier gaumet a écrit :
> 
> Tu essaies d'installer le pilote virtio pour le disque dur après
> l'installation de windows ou pendant?

J'essaie de l'installer durant l'installation de Windows.

> Parce qu'en fait, je le fais pendant l'installation: l'invité est
> déclaré dans virt(manager avec 2 lecteurs cd-roms: le 1er chargé avec
> le CD d'install et le 2ème chargé avec le CD de drivers RedHat. Durant
> l'install, Windows couine qu'il ne peut s'installer nulle part puisque
> dans virt-manager j'ai déclaré un pilote virtio pour le disque dur et
> que Windows ne dispose pas du pilote, il ne voit donc aucun disque dur.

C'est exactement ça.

> Quand il couine il propose de charger un pilote: là on va chercher ce
> pilote sur le 2ème CD dans le répertoire viostor\w10\amd64, à la suite
> de quoi, Win trouve le disque et on peut installer dessus.

Il trouve bien le pilote (Red Hat VirtIO SCSI controller dans
E:\amd64\w10\viostor.inf), mais il refuse de l'installer :

"aucun nouveau pilote de périphérique n'a été détecté..."

Si je l'installe à la main depuis la ligne de commande, j'ai une autre
erreur :

E:\amd64\w10\>drvload viostor.inf
DrvLoad : chargement de viostor.inf impossible (erreur 0x80070103)

> Sinon, je pense qu'on peut installer Win10 en mode SATA (déclaré comme
> tel dans virt-manager), puis une fois dans Win10, appeler l'exécutable
> à la racine du disques des pilotes RedHat pour installer tous les
> pilotes, arrêter (pas redémarrer) Win10, declarer le disque dur en
> virtio dans virt-manager et démarre Win10

Quelle version des pilotes utilises-tu ?

JKB

Re: W10 sur kvm/qemu

[didier gaumet]

Tu essaies d'installer le pilote virtio pour le disque dur après
l'installation de windows ou pendant?

Parce qu'en fait, je le fais pendant l'installation: l'invité est
déclaré dans virt(manager avec 2 lecteurs cd-roms: le 1er chargé avec
le CD d'install et le 2ème chargé avec le CD de drivers RedHat. Durant
l'install, Windows couine qu'il ne peut s'installer nulle part puisque
dans virt-manager j'ai déclaré un pilote virtio pour le disque dur et
que Windows ne dispose pas du pilote, il ne voit donc aucun disque dur.
Quand il couine il propose de charger un pilote: là on va chercher ce
pilote sur le 2ème CD dans le répertoire viostor\w10\amd64, à la suite
de quoi, Win trouve le disque et on peut installer dessus.

Sinon, je pense qu'on peut installer Win10 en mode SATA (déclaré comme
tel dans virt-manager), puis une fois dans Win10, appeler l'exécutable
à la racine du disques des pilotes RedHat pour installer tous les
pilotes, arrêter (pas redémarrer) Win10, declarer le disque dur en
virtio dans virt-manager et démarre Win10

Re: W10 sur kvm/qemu

[Patrick ZAJDA]

Hello,


J'ai une VM windows 10 installée en suivant ce tuto : 
https://dennisnotes.com/note/20180614-ubuntu-18.04-qemu-setup/


J'avais pris la dernière version.


Vu que ça fait un moment, je ne me souviens pas suffisamment pour t'en 
dire plus que "j'ai utilisé ce tuto" ;)


Il explique pour installer le pilote dès l'installation de Windows.


Patrick


Le 24/02/2022 à 14:00, BERTRAND Joël a écrit :

Bonjour à tous,

Je fatigue...

J'essaie maintenant d'installer W10 sur une VM avec un disque virtio.
J'ai essayé plusieurs iso des pilotes et je me retrouve toujorus avec un
pilote virtio non installable... J'ai essayé :

virtio-win-0.1.172.iso  virtio-win-0.1.208.iso  virtio-win-0.1.215.iso

Une installation à la main en ligne de commande échoue aussi avec une
erreur cryptique.

Comment faire ?

Bien cordialement,

JKB


--
Patrick ZAJDA

W10 sur kvm/qemu

[BERTRAND Joël]

Bonjour à tous,

Je fatigue...

J'essaie maintenant d'installer W10 sur une VM avec un disque virtio.
J'ai essayé plusieurs iso des pilotes et je me retrouve toujorus avec un
pilote virtio non installable... J'ai essayé :

virtio-win-0.1.172.iso  virtio-win-0.1.208.iso  virtio-win-0.1.215.iso

Une installation à la main en ligne de commande échoue aussi avec une
erreur cryptique.

Comment faire ?

Bien cordialement,

JKB

Re: My printer doesn't work for bullseye's cups

[Eduardo M KALINOWSKI]

On 24/02/2022 06:35, Klaus Singvogel wrote:

linuxprinting.org showed me, that your printer Brother MFC-J6920DW is
listed as paperweight only, regarding Open Source drivres.


It seems to support AirPrint (https://support.apple.com/en-us/HT201311), 
so driverless printing (actually a universal driver) should work.


This wiki page has some instructions: 
https://wiki.debian.org/CUPSDriverlessPrinting . It's a bit confusing, 
though.



--
A free society is one where it is safe to be unpopular.
-- Adlai Stevenson

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: Tarjeta de sonido USB

[Camaleón]

El 2022-02-24 a las 12:53 +0100, Josu Lazkano escribió:

> Gracias a los dos.
> 
> Pero sigue sin funcionar, he reiniciado el servidor, pero da el mismo error.
> 
> Lo de instalar más módulos, no sabría que más instalar, en el enlace
> ejecuta "armbian-config", pero no es mi caso.

Esa orden no es para Debian :-)

Lo que te sugiere el artículo es que revises, si en tu caso y debido al 
chipset de la tarjeta, no necesites cargar módulos de sonido 
adicionales a los que el sistema carga de manera predeterminada. 

> Parece que el problema es que no lo detecta como dispositivo por defecto,
> ya que el "alsamixer" a secas no le gusta, pero con el parámetro del
> dispositivo si que funciona: "alsamixer -c 1".
> 
> Seguiré investigando un poco más.

Ya nos dirás si al final has logrado hacerla funcionar.

Saludos,

-- 
Camaleón 

Re: Tarjeta de sonido USB

[Josu Lazkano]

Gracias a los dos.

Pero sigue sin funcionar, he reiniciado el servidor, pero da el mismo error.

Lo de instalar más módulos, no sabría que más instalar, en el enlace
ejecuta "armbian-config", pero no es mi caso.

Parece que el problema es que no lo detecta como dispositivo por defecto,
ya que el "alsamixer" a secas no le gusta, pero con el parámetro del
dispositivo si que funciona: "alsamixer -c 1".

Seguiré investigando un poco más.

Un saludo.

-- 
Josu Lazkano

Re: My printer doesn't work for bullseye's cups

[Klaus Singvogel]

Hi Gene,

linuxprinting.org showed me, that your printer Brother MFC-J6920DW is
listed as paperweight only, regarding Open Source drivres.

But a quick search with Google showed me this promising site with Linux
drivers:


https://support.brother.com/g/b/downloadtop.aspx?c=us=en=mfcj6920dw_us_eu_as

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Re: Windows 11 sur qemu/kvm

[BERTRAND Joël]

BERTRAND Joël a écrit :
> didier gaumet a écrit :
>> J'ai peut-être une piste pour toi :-)
>>
>> le fichier /usr/share/doc/ovmf/README.Debian détaille les différences
>> et cas d'usage de ces firmwares
> 
>   Pourtant, j'ai lu le fichier en question et ce n'est pas clair du tout.
> 
>> et pour du Secure Boot, lorsque OVMF_CODE_4M.secboot.fd est utilisé, 
>> par défaut cela ne fait que rendre *possible* le Secure Boot, sans
>> l'activer. Pour cela il faut importer manuellement des clés dans
>> l'UEFI.
>> Pour du Secure Boot *activé* par défaut sans action particulière, c'est
>> OVMF_CODE_4M.ms.fd qui doit être utilisé.
> 
>   De toute façon, même avec OVMF_CODE_4M.ms.fd, ça ne fonctionne pas...
> Je vais me rabattre sur Windows 10.

Bon bon bon... Je viens de suivre pas à pas plusieurs vidéos, rien à
faire. L'émulation TPM fonctionne parfaitement (si j'en crois les
fichiers logs), je laisse tomber W11 et vais tenter l'installation d'un
W10 (qui plante un peu plus loin, mais au moins, ce n'est qu'un problème
de pilotes).

JKB

Re: jigdo can't complete debian-10.9.0-amd64-STICK16GB-1.iso: 63 files not found

[Thomas Schmitt]

Hi,

i wrote:
> > snapshot.debian.org/archive/debian/20210328T103801Z/dists/buster/main/instal
ler-amd64/20190702+deb10u9/images/netboot/debian-installer/amd64/grub/x86_64
-efi/hfsplus.mod
> > But this one works for me with wget.

Danilo Schembri wrote:
> On the server that directory doesn't exist

Indeed. The entry "2021-03-28 10:32:28" is missing in
  https://snapshot.debian.org/archive/debian/?year=2021=3
I did not look at that list yesterday, because i could access
20210328T103801Z directly.


> On the server that directory doesn't exist (try
> snapshot.debian.org/archive/debian/20210328T103801Z ), but there is
> "some magic" that brings you "somewhere" (latest build? the nearest?)
> when you ask for a subdirectory that could (?) exist. And I like it!
> :-)

That explains why it worked for me yesterday.
In my role as bystander i express my deep distrust towards such automats
which cover up discrepancies between .jigdo files and snapshot.debian.org.

(The behavior of URLs like https://snapshot.debian.org/archive/debian
is confusing on its own. The browser gets redirected to the main page.
wget throws a 404 error.)


Whatever
  
http://us.cdimage.debian.org/cdimage/snapshot/Debian/dists/buster/main/installer-amd64/20190702+deb10u9/
and
  
http://us.cdimage.debian.org/cdimage/snapshot/Debian/dists/buster/main/installer-amd64/20190702+deb10u9/images/netboot/debian-installer/amd64/grub/x86_64-efi/hfsplus.mod
are still reachable.

So my proposal still stands. Try jigdo-lite with "Debian mirror"

  http://us.cdimage.debian.org/cdimage/snapshot/Debian/

-

> under Windows,

This might or might not explain why the fallback mechanism does not work.
It will be interesting to see whether my proposal avoids the need for
falling back and whether jigdo-lite can work with the downloaded files.


> BUT (tada!) when the download finishes, jigdo doesn't understand files
> are there ("No such file or directory" it says) and throws away
> everything.

If it complains about the MD5 checksum of the downloaded files, then
this would be due to the fact that the downloaded file is not the
expected version.
But when i do

  wget 
https://snapshot.debian.org/archive/debian/20210328T103801Z/dists/buster/main/installer-amd64/20190702+deb10u9/images/netboot/debian-installer/amd64/grub/x86_64-efi/hfsplus.mod

i get a file of which md5sum says 08ec2778c184818dc20af491bb291112,
which seems correct.

(The expectation of the .jigdo file is encoded as ("URL safe") base64 in
this line
   
COwneMGEgY3CCvSRuykREg=Debian:dists/buster/main/installer-amd64/20190702+deb10u9/images/netboot/debian-installer/amd64/grub/x86_64-efi/hfsplus.mod
The checksum can be decoded by
  echo 'COwneMGEgY3CCvSRuykREg' | sed -e 's/-/+/g' -e 's/_/\//g' | \
  base64 -d | od -t x1 | sed -e 's/^...//' -e 's/ //g'
which yields
  08ec2778c184818dc20af491bb291112
)


> I guess the other questions in your e-mail are no more relevant, but,
> please, tell me if I'm wrong.

Well, the proposal to try as "Debian mirror"
  http://us.cdimage.debian.org/cdimage/snapshot/Debian/
is still worth a try.

If it does not work at all with MS-Windows and you have problems to
get jigdo-lite for the reachable Linuxes, then consider to try
  https://wiki.debian.org/JigdoOnLive
which describes how to download Jigdo ISOs by a Debian Live system.


Have a nice day :)

Thomas