Re: Following Pipewire developments

[Yoann LE BARS]

Hello everybody out there!

	One last question before deciding to use Fedora, what about use this 
repository:


https://pipewire-debian.github.io/pipewire-debian/

	Well, it seems a bit making some kind of a Frankendebian, but it seems 
to be less susceptible to broke anything else in the system.


What do you think about it?

Best regards.

--
Yoann LE BARS
https://le-bars.net/yoann/
Diaspora* : yleb...@framasphere.org

Re: Probelmas con la Wikipedia off-line

[Camaleón]

El 2021-11-09 a las 21:18 -0500, Wilfredo Beyra escribió:

> Hola a todos:
> Estoy teniendo problemas para ejecutar la appimage de kiwix. Seguí la
> siguiente rutina:
> mkdir -p AppImages
> Luego copie en esta carpeta la appimage que ya había descargado
> previamente.
> A ontinuación lo siguiente
> cd ~/AppImages
> chmod +x kiwix-desktop_x86_64_2.0.5.appimage
> Y aquí viene el problema: se supone que a este punto solo debería bastar
> con hacer doble clic sobre la appimage y listo pero no es así. Por otro
> lado si la trato de ejecutar por consola
> ./kiwix-desktop_x86_64_2.0.5.appimage
> Me sale un mensaje que dice violación de segmento. Quedo a la espera de su
> sabiduría. Gracias,

Prueba con una versión anterior del archivo appimage.

En el Github del proyecto tienen localizados algunos errores de este 
tipo:

Kiwix Desktop 2.0.4 always quits with segfault on Ubuntu 18.04 #423 
https://github.com/kiwix/kiwix-desktop/issues/423

O recurre al paquete de toda la vida que ya tiene las dependencias a 
las bibliotecas satisfechas... o al menos te avisará de lo que necesita 
:-)

https://packages.debian.org/search?keywords=kiwix

Saludos,

-- 
Camaleón 

Probelmas con la Wikipedia off-line

[Wilfredo Beyra]

Hola a todos:
Estoy teniendo problemas para ejecutar la appimage de kiwix. Seguí la
siguiente rutina:
mkdir -p AppImages
Luego copie en esta carpeta la appimage que ya había descargado
previamente.
A ontinuación lo siguiente
cd ~/AppImages
chmod +x kiwix-desktop_x86_64_2.0.5.appimage
Y aquí viene el problema: se supone que a este punto solo debería bastar
con hacer doble clic sobre la appimage y listo pero no es así. Por otro
lado si la trato de ejecutar por consola
./kiwix-desktop_x86_64_2.0.5.appimage
Me sale un mensaje que dice violación de segmento. Quedo a la espera de su
sabiduría. Gracias,
Wilfredo

Re: Recs for new Linux laptop? (to replace Zareason)

[Charles Curley]

On Tue, 9 Nov 2021 16:06:39 +
"Andrew M.A. Cater"  wrote:

> Does it have to be new out of the box new? There are many of us
> working happily with second hand Lenovo Thinkpads - and a year old
> machine from a bankrupt business is relatively easy to source.

Refurbished Lenovos are also available. Many years ago I bought two
refurbished T61, and both still run well enough with Bullseye.

Check the thinkwiki for information on available models and how they
work with Linux.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Recs for new Linux laptop? (to replace Zareason)

[Dan Ritter]

Bob McGowan wrote: 
> On 11/9/21 7:17 AM, Tom Browder wrote:
> Just two comments of things to look out for:
> 
> 1.  If possible avoid Optimus based (dual graphics card) laptops.  It seems
> there is a lot of variability in how different companies implement this,
> which may impact how well a Linux distribution works with the laptop.

I've had a bunch of success with Ryzen laptops with built-in AMD
graphics.

-dsr-

Re: ALSA device names.

[deloptes]

pe...@easthope.ca wrote:

> surround21:CARD=Set,DEV=0
> and
> surround40:CARD=Set,DEV=0
> aren't atomic names.  Is the syntax and semantics explained in
> documentation?
> 
> No surround22, surround23 ... surround39 evident here. How does ALSA
> derive or find the names and numbers?

you hopefully know that sourround21 stands there for 2+1 and 40 stands for 4
outputs
Also it is explained in documents like for example on the alsa-project web
site
https://alsa-project.org/wiki/DeviceNames

I sometimes wonder if some peoples google is broken. For me it worked quite
well. I type in "ALSA device name"

another excellent reading is
https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture

-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Re: Recs for new Linux laptop? (to replace Zareason)

[Bob McGowan]

On 11/9/21 7:17 AM, Tom Browder wrote:
My Zareason laptop (13-in screen, very lightweight and thin) is 
running Debian 10 natively and wonderfully (with Win10 as a dual boot 
option), but the company has gone out of business and I want to start 
preparing a standby replacement.


I would appreciate any recommendations for that. I have looked at both 
Emperor Linux and System 76 over the years. They always seem a bit 
pricey, but I'm willing to bite the bullet now if I have to--I'm 
getting too old to waste time on problem installations now.


Thanks,

-Tom


Just two comments of things to look out for:

1.  If possible avoid Optimus based (dual graphics card) laptops.  It 
seems there is a lot of variability in how different companies implement 
this, which may impact how well a Linux distribution works with the laptop.


2.  I've had problems with recent laptops from Dell that have Windows 
installed and use an Intel disk controller in RAID mode (even though 
there is only one disk).  These machines will boot the installer just 
fine but the installer fails to detect the disk or controller making 
installation impossible.  This is likely to change over time but short 
term could be an issue.


Cheers,

Bob

Re: Problème pour accèder au disque D en dual boot avec Windows 10

[didier gaumet]

Pour ne pas te laisser dans la nature, j'ai parcouru le README d'1 des
3 plugins: les fichiers zip contiennent les sources et les plugins
binaires (extension *.so*). Ceux-ci sont à copier dans /usr/lib64/ntfs-
3g/ dans le cas d'un OS linux 64 bits

Re: Problème pour accèder au disque D en dual boot avec Windows 10

[didier gaumet]

Le mardi 09 novembre 2021 à 14:51 +0100, lists.deb...@netc.eu a écrit :
>  
> Bonjour,
>  
> Hier soir j'ai essayé de faire les modifications que nous avons
> discuté :
>  
> Dans un 1er temps j'ai essayé de désactiver le fastboot, mais
> l'option n'était pas présente dans Windows. J'ai donc du réactiver
> l'hibernation (avec powercfg dans Powershell), et j'ai pu voir
> l'option dans Windows.
> J'ai donc désactivé fastboot, et ensuite j'ai désactivé à nouveau
> l’hibernation. Malheureusement il n'y a pas eu de changements dans le
> côté Debian (toujours les mêmes messages 'unsupported reparse
> point').
>  
> Par contre j'ai une autre question :
>  
> En profitant de ce nouveau dual boot sur mon PC, je me suis décidé de
> faire un upgrade et changer ma SSD, en remplaçant mon SSD de 128GO
> pour une nouvelle de 512GO (et ajouter de la mémoire RAM au passage).
> L'idée c'est d'avoir 2 partitions de ~256GO, une pour chaque système
> d'exploitation.
>  
> Je me pose donc la question si dans ce cas de figure, sauriez-vous
> dire si je pourrais profiter de cette MAJ pour résoudre mon problème
> d'accès ? C'est à dire, j'avais pensé à cloner mon ancienne SSD, mais
> si vous pensez qu'en faisant une nouvelle installation (d'un ou des 2
> systèmes) je pourrais optimiser mon PC, je pourrais profiter de
> l'opportunité... Qu'en pensez-vous ?
>  
> Avez-vous des conseils à me donner ?
>  
> Merci encore une fois de votre aide,
>  
> Cordialement,
> Marc

WARNING: I will present you a monstrous BILL for having gone through
the GATES of the WINDOWS hell ;-)

Je rigole mais ça été un peu dur d'avoir une vue d'ensemble de ton
problème...

D'abord: Non, la résolution de ton problème de lecture NTFS à partir de
Linux ne sera pas facilitée par une réinstallation: ce sont deux points
bien séparés et le 2ème n'a pas d'incidence évidente sur le 1er. 

Ensuite, les messages d'erreur que tu rencontres sont a priori dus à de
nouvelles (par rapport aux versions précédentes) fonctionnalités de
Windows 10.
En résumé rapide les messages d'erreur "Reparse files" ont à voir avec
plusieurs concepts, principalement de (dé)compression de fichiers
systèmes Windows et de réagrégation de fichiers dédupliqués. C'est
aussi plus ou moins en lien (hahaha, facile) avec les liens symboliques
sous Linux qui traduisent différentes notions de liens et jonctions
sous Windows.
https://github.com/tuxera/ntfs-3g/wiki/Junctions-Points,-Symbolic-Links-and-Reparse-Points
https://wiki.archlinux.org/title/NTFS-3G#Compressed_files

En gros, dans Debian 11 Bullseye, NTFS est géré quoiqu'il arrive par
ntfs-3g (même lorsque le système de fichier est monté avec le type
ntfs). Et la version ntfs-3g de Debian 11 est la dernière version
stable à être parue avant Debian 11, la 2017.3 

Il devrait te suffire de télécharger 3 plugins compatibles avec la
version 2017.3.
Tu n'as probablement besoin que du plugin de déduplication mais les 2
autres pourraient t'être utiles au cas où (page perso d'un des auteurs
de ntfs-3g, c'est pas un site douteux):
https://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g-old.html#download
Je n'ai pas creusé (je te laisse le faire ;-)) où et comment les
installer

Une autre solution indiquée par le Wiki d'Archlinux (lien plus haut)
serait de désactiver la compression dans Windows 10 (ça devrait
probablement résoudre les pb autant pour les fichiers systèmes
compressés que pour les fichiers ordinaires dédupliqués):
C:\WINDOWS\system32> compact.exe /CompactOS:never

ça fait  (non c'est pas des prompt shell ;-))

Allez, bon courage :-)
(mais dis-nous quand même si tu y es arrivé)

Re: Renommer les interfaces réseau

[ajh-valmer]

On Tuesday 09 November 2021 11:45:23 you wrote:
> Le 09/11/2021 à 11:16, ajh-valmer a écrit :

> https://leforuminfo.com/renommer-interface-reseau

> Le nommage est géré par udev, donc il faut allez voir dans 
> la doc de udev : /usr/share/doc/udev/
> Tu peux lire le fichier "/usr/share/doc/udev/README.Debian.gz" et en 
> particulier le paragraphe "Custom net interface naming".

Super, merci pour ces 2 infos.

Re: Recs for new Linux laptop? (to replace Zareason)

[Celejar]

On Tue, 9 Nov 2021 17:47:16 +
"Andrew M.A. Cater"  wrote:

> On Tue, Nov 09, 2021 at 06:20:38PM +0100, Christian Britz wrote:
> > My cheap Lenovo Ideapad S145 was not supported by the stable kernel in
> > Debian Buster (especially SSD and WiFi) when I bought it in April 2020,
> > but very soon got supported better and better by the testing
> > distribution. When Bullseye got released, it was fully supported.
> > 
> 
> Results may vary: cheap Lenovo may be a very different experience to 
> Thinkpad. There is a quality difference which depends on original price,
> I think.

To clarify: the difference is not necessarily between price points but
between the various series, i.e., between the highly regarded ones such
as the T, X, and W ThinkPad lines, and the lesser ones such as the
IdeaPad and ThinkPad E lines. The L series ThinkPad is apparently
in-between.

See, e.g.: 
https://www.reddit.com/r/thinkpad/comments/5662i5/how_much_worse_is_the_lseries/

> All the very best, as ever,
> 
> Andy Cater
> 
> 
> > I would assume that Lenovo machines generally are supported well by
> > Testing in a short time frame and can grow into a stable system. ;-)
> > 
> > Christian
> > 
> > Am 09.11.21 um 16:17 schrieb Tom Browder:
> > > My Zareason laptop (13-in screen, very lightweight and thin) is running
> > > Debian 10 natively and wonderfully (with Win10 as a dual boot option),
> > > but the company has gone out of business and I want to start preparing a
> > > standby replacement.
> > > 
> > > I would appreciate any recommendations for that. I have looked at both
> > > Emperor Linux and System 76 over the years. They always seem a bit
> > > pricey, but I'm willing to bite the bullet now if I have to--I'm getting
> > > too old to waste time on problem installations now.
> > > 
> > > Thanks,
> > > 
> > > -Tom
> > 
> 


Celejar

Re: Package: nvidia-legacy-390xx-driver

[Alexander V. Makartsev]

On 09.11.2021 18:23, lina wrote:

It seems the drivers are there, my problems are:

1. I can't use gaussian view
2. The Sweet Home 3D Error: Sweet Home 3D will exit now because of a 
fatal error in the 3D rendering system of your computer. Please update 
the DirectX/OpenGL drivers of your computer graphic card.
I've installed SweetHome3D on my system with Nvidia VGA to see if this 
program would work for me.
When I tried to start it using "./SweetHome3D" I got the same message 
about "DirectX/OpenGL drivers", which is false.
But when I start SweetHome3D using "./SweetHome3D-Java3D-1_5_2" it runs 
and works without problems, AFAICS.




Thanks again, lina

# glxinfo -B
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 2048 MB
    Total available memory: 2048 MB
    Currently available dedicated video memory: 1718 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 460.91.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

It looks like Nvidia driver is installed and working correctly.

--
With kindest regards, Alexander.

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

Re: Following Pipewire developments

[Henning Follmann]

On Mon, Nov 08, 2021 at 11:15:00PM +0100, Yoann LE BARS wrote:
> 
> Hello, everybody out there!
> 
> On 2021/11/08 at 2:39 pm, Henning Follmann wrote:
> > The easiest way to get a current version of pipewire is
> > to install fedora core.
> 
>   Yes, this is something I have considered. I have already tried and use
> Fedora, but I prefer Debian in general.
> 

So do I. But when it comes to kernel development and
more current tools I sometimes use fc.


-H


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Recs for new Linux laptop? (to replace Zareason)

[Andrew M.A. Cater]

On Tue, Nov 09, 2021 at 06:20:38PM +0100, Christian Britz wrote:
> My cheap Lenovo Ideapad S145 was not supported by the stable kernel in
> Debian Buster (especially SSD and WiFi) when I bought it in April 2020,
> but very soon got supported better and better by the testing
> distribution. When Bullseye got released, it was fully supported.
> 

Results may vary: cheap Lenovo may be a very different experience to 
Thinkpad. There is a quality difference which depends on original price,
I think.

All the very best, as ever,

Andy Cater


> I would assume that Lenovo machines generally are supported well by
> Testing in a short time frame and can grow into a stable system. ;-)
> 
> Christian
> 
> Am 09.11.21 um 16:17 schrieb Tom Browder:
> > My Zareason laptop (13-in screen, very lightweight and thin) is running
> > Debian 10 natively and wonderfully (with Win10 as a dual boot option),
> > but the company has gone out of business and I want to start preparing a
> > standby replacement.
> > 
> > I would appreciate any recommendations for that. I have looked at both
> > Emperor Linux and System 76 over the years. They always seem a bit
> > pricey, but I'm willing to bite the bullet now if I have to--I'm getting
> > too old to waste time on problem installations now.
> > 
> > Thanks,
> > 
> > -Tom
> 

Re: Recs for new Linux laptop? (to replace Zareason)

[Christian Britz]

My cheap Lenovo Ideapad S145 was not supported by the stable kernel in
Debian Buster (especially SSD and WiFi) when I bought it in April 2020,
but very soon got supported better and better by the testing
distribution. When Bullseye got released, it was fully supported.

I would assume that Lenovo machines generally are supported well by
Testing in a short time frame and can grow into a stable system. ;-)

Christian

Am 09.11.21 um 16:17 schrieb Tom Browder:
> My Zareason laptop (13-in screen, very lightweight and thin) is running
> Debian 10 natively and wonderfully (with Win10 as a dual boot option),
> but the company has gone out of business and I want to start preparing a
> standby replacement.
> 
> I would appreciate any recommendations for that. I have looked at both
> Emperor Linux and System 76 over the years. They always seem a bit
> pricey, but I'm willing to bite the bullet now if I have to--I'm getting
> too old to waste time on problem installations now.
> 
> Thanks,
> 
> -Tom

Re: Package: nvidia-legacy-390xx-driver

[Andrew M.A. Cater]

On Tue, Nov 09, 2021 at 11:34:46AM -0500, Greg Wooledge wrote:
> On Tue, Nov 09, 2021 at 04:15:49PM +, Andrew M.A. Cater wrote:
> > On Tue, Nov 09, 2021 at 02:51:33PM +0100, lina wrote:
> > > Can I have a system with both X-session and the nvidia-driver
> > > as gaussian view requires
> > > 
> > > Gaussview must be run in an X-windows session. Details for controlling the
> > > application are provided in the materials found in the Resources section.
> > > 
> > 
> > If you are running Bullseye [Debian 11] and GNOME, I think it defaults
> > to using Waylan - if you are at the login prompt, you can choose which
> > session is loaded by clicking on the cogwheel.
> 
> Wayland, with a "d".  This is also true for Debian 10 (buster).
> 

Yes: I realised - as ever, you only see the typo once it's gone :)

Purging nouveau is always hard, but I understand that the installation 
scripts for the proprietary driver do a pretty good job. I think you may
only have to install nvidia-driver and the other necessary packages will be
pulled in.

All the very best, as ever,

Andy Cater

Re: Package: nvidia-legacy-390xx-driver

[Greg Wooledge]

On Tue, Nov 09, 2021 at 04:15:49PM +, Andrew M.A. Cater wrote:
> On Tue, Nov 09, 2021 at 02:51:33PM +0100, lina wrote:
> > Can I have a system with both X-session and the nvidia-driver
> > as gaussian view requires
> > 
> > Gaussview must be run in an X-windows session. Details for controlling the
> > application are provided in the materials found in the Resources section.
> > 
> 
> If you are running Bullseye [Debian 11] and GNOME, I think it defaults
> to using Waylan - if you are at the login prompt, you can choose which
> session is loaded by clicking on the cogwheel.

Wayland, with a "d".  This is also true for Debian 10 (buster).

Re: Package: nvidia-legacy-390xx-driver

[Andrew M.A. Cater]

On Tue, Nov 09, 2021 at 02:51:33PM +0100, lina wrote:
> Can I have a system with both X-session and the nvidia-driver
> as gaussian view requires
> 
> Gaussview must be run in an X-windows session. Details for controlling the
> application are provided in the materials found in the Resources section.
> 

If you are running Bullseye [Debian 11] and GNOME, I think it defaults
to using Waylan - if you are at the login prompt, you can choose which
session is loaded by clicking on the cogwheel.

Hope this helps, all best as ever,

Andy Cater

> Thanks,
> 
> On Tue, Nov 9, 2021 at 2:23 PM lina  wrote:
> 
> > It seems the drivers are there, my problems are:
> >
> > 1. I can't use gaussian view
> > 2. The Sweet Home 3D Error: Sweet Home 3D will exit now because of a fatal
> > error in the 3D rendering system of your computer. Please update the
> > DirectX/OpenGL drivers of your computer graphic card.
> >
> > Thanks again, lina
> >
> > # glxinfo -B
> > name of display: :0.0
> > display: :0  screen: 0
> > direct rendering: Yes
> > Memory info (GL_NVX_gpu_memory_info):
> > Dedicated video memory: 2048 MB
> > Total available memory: 2048 MB
> > Currently available dedicated video memory: 1718 MB
> > OpenGL vendor string: NVIDIA Corporation
> > OpenGL renderer string: GeForce GT 730/PCIe/SSE2
> > OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
> > OpenGL core profile shading language version string: 4.60 NVIDIA
> > OpenGL core profile context flags: (none)
> > OpenGL core profile profile mask: core profile
> >
> > OpenGL version string: 4.6.0 NVIDIA 460.91.03
> > OpenGL shading language version string: 4.60 NVIDIA
> > OpenGL context flags: (none)
> > OpenGL profile mask: (none)
> >
> > OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
> > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
> >
> >
> >
> > On Tue, Nov 9, 2021 at 12:05 PM Alexander V. Makartsev 
> > wrote:
> >
> >> On 09.11.2021 15:26, lina wrote:
> >>
> >> Hi all,
> >>
> >> I am still struggling with the graphic card issue.
> >>
> >> What issue exactly?
> >>
> >> # nvidia-detect
> >> Detected NVIDIA GPUs:
> >> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B
> >> [GeForce GT 730] [10de:1287] (rev a1)
> >>
> >> Checking card:  NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)
> >> Your card is supported by all driver versions.
> >> Your card is also supported by the Tesla 460 drivers series.
> >> Your card is also supported by the Tesla 450 drivers series.
> >> Your card is also supported by the Tesla 418 drivers series.
> >> It is recommended to install the
> >> nvidia-driver
> >> package.
> >>
> >> Geforce GT 730 is still supported by Nvidia, so you should use recent
> >> driver, not a legacy one.
> >> $ sudo apt install nvidia-driver nvidia-driver-bin nvidia-driver-libs
> >> nvidia-kernel-dkms nvidia-kernel-support mesa-utils
> >>
> >> Check the installation with:
> >> $ glxinfo -B
> >>
> >> Shall I install the nvidia-legacy-390xx-driver
> >>
> >> https://packages.debian.org/sid/nvidia-legacy-390xx-driver
> >>
> >>
> >> There is no point in doing that, because 390.xx driver series are
> >> inferior to the most recent driver available.
> >>
> >>
> >> --
> >> With kindest regards, Alexander.
> >>
> >> ⢀⣴⠾⠻⢶⣦⠀
> >> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> >> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> >> ⠈⠳⣄
> >>
> >>

Re: Recs for new Linux laptop? (to replace Zareason)

[Andrew M.A. Cater]

On Tue, Nov 09, 2021 at 09:17:53AM -0600, Tom Browder wrote:
> My Zareason laptop (13-in screen, very lightweight and thin) is running
> Debian 10 natively and wonderfully (with Win10 as a dual boot option), but
> the company has gone out of business and I want to start preparing a
> standby replacement.
> 
> I would appreciate any recommendations for that. I have looked at both
> Emperor Linux and System 76 over the years. They always seem a bit pricey,
> but I'm willing to bite the bullet now if I have to--I'm getting too old to
> waste time on problem installations now.
> 
> Thanks,
> 
> -Tom

Hi Tom,

Does it have to be new out of the box new? There are many of us working
happily with second hand Lenovo Thinkpads - and a year old machine from
a bankrupt business is relatively easy to source.

The latest/greatest may have it's own problems: you may also find 
that Dell or Lenovo are selling Linux-qualified laptops new now.

All the very best, as ever,

Andy Cater

Re: Install debian on USB-stick

[Michael Castellon]

Hi,
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.1.0-live+nonfree/amd64/iso-hybrid/debian-live-11.1.0-amd64-standard+nonfree.iso
# cp debian-live-11.1.0-amd64-standard+nonfree.iso /dev/sdb
# sync

for other live
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.1.0-live+nonfree/amd64/iso-hybrid/

for minimal usbstick
https://ftp.sh.cvut.cz/slax/Slax-9.x/slax-64bit-9.11.0.iso

Regards.

On Tue, Nov 9, 2021 at 9:48 AM Sim Sim  wrote:

> Hi.
>
> Is possible to install debian-11.1.0-i386-netinst.iso on 16Gb
> USB2.0-stick? A minimal environment, of course. And productivity do not
> need, just curiosity.
>
> Thanks.
>

Re: Install debian on USB-stick

[Dan Ritter]

Sim Sim wrote: 
> Is possible to install debian-11.1.0-i386-netinst.iso on 16Gb USB2.0-stick?
> A minimal environment, of course. And productivity do not need, just
> curiosity.

You can:

- write that ISO to the stick and use it as an installer

OR 

- boot that ISO and select a stick like that as the target disk

but not both at once.

16GB is enough room for a fair number of things; I have a
desktop PC here with lots of installed software where everytning
which is not /home fits in 16GB.

It will be fairly slow. A USB3 stick, if available, should be
faster, and a USB3-connected SSD quite usable in the short term.

-dsr-

Re: mobilt 4g bredband

[Jonathan Sélea]

Det borde absolut fungera.
Vad säger dmesg när du kopplar in den? Vad är det för chipset på 
modemet?



--
Jonathan Sélea

Website: https://jonathanselea.se
PGP Key: 0x8B35B3C894B964DD
Fingerprint: 4AF2 10DE 996B 673C 0FD8  AFA0 8B35 B3C8 94B9 64DD



On 2021-11-05 15:26, mattias jonsson wrote:

funkar sånt i buster?
kopplar in mitt kombinerade router+modem i en usbport
verkar som det dyker upp ett interface
men det är inaktiverat
obs! ingen pinkod på simkortet
det funkar fint i win och mac os

ALSA device names.

[peter]

Ref. https://lists.debian.org/debian-user/2021/09/msg01112.html
Subject: Re: Persistent names for audio devices.
From: David Wright 
Date: Wed, 29 Sep 2021 22:35:11 -0500
Message-id: <20210930033511.gc22...@axis.corp>
References:  
<_Vy48xSpy3r0uj8kBgbIiS_l-GGEeoinqJc5I64K4YfKpqSs7HJIz4-v6PvMpeJ609TFiLSqSiG2VbElSR5NzLAiMqSkwAjFCHI1gK1NNlc=@protonmail.com>
  <[] 20210928233134.ga22...@axis.corp> <[] 
E1mVfDB-cu-IE@joule.invalid>

> I think this thread has been around for a couple of years now.
> I assume the penny dropped that names like Live and ICH5 are
> the persistent items you were looking for.

Yah, 2019-10-20 a guinea wore a hole through my pocket and fell 
down a sewer grate.  =8~|  https://en.wikipedia.org/wiki/Guinea_(coin)

Ref. https://lists.debian.org/debian-user/2019/10/msg00743.html
Subject: Re: Unidentified subject!
From: Reco 
Date: Sun, 20 Oct 2019 18:23:08 +0300
Message-id: 
References:  


> Use "aplay -L" to get strings that are specific for your hardware.
> The way I see it, there's no need for these "predictable audio devices
> names", they are here already.

OK, although
surround21:CARD=Set,DEV=0
and 
surround40:CARD=Set,DEV=0
aren't atomic names.  Is the syntax and semantics explained in 
documentation?

No surround22, surround23 ... surround39 evident here. How does ALSA 
derive or find the names and numbers?

What is meant by CARD=Set?

DEV=0 turns up frequently.  What's the point?  DEV=1?

Incidentally, the AUDIODEV variable is a distraction.  Rather than 
mess with it, specify the device directly.
sox noise.WAV -t alsa plughw:CARD=ICH5,DEV=0 gain 1

Regards & thanks for the multiple earlier replies,
... P.

-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W

Recs for new Linux laptop? (to replace Zareason)

[Tom Browder]

My Zareason laptop (13-in screen, very lightweight and thin) is running
Debian 10 natively and wonderfully (with Win10 as a dual boot option), but
the company has gone out of business and I want to start preparing a
standby replacement.

I would appreciate any recommendations for that. I have looked at both
Emperor Linux and System 76 over the years. They always seem a bit pricey,
but I'm willing to bite the bullet now if I have to--I'm getting too old to
waste time on problem installations now.

Thanks,

-Tom

Re: No DNS in Fedora Podman image on Debian 11

[Francois Gouget]

On Sun, 7 Nov 2021, Ulf Volmer wrote:
[...]
> podman run --rm --security-opt=seccomp=unconfined -it fedora:latest
> 
> solves the issue for me.

That does work. Thanks!

Today I also found that this is actually a known issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995777

It indicates that this is going to hit all Linux containers using 
glibc >= 2.33. Fedora 35 is just the first casualty.

The upstream bug that's referenced there also provides a fix and that 
has been integrated in the Podman that's in Debian Testing.
(I checked that there is no issue on Debian Testing)

However I don't know how to convert the 'correct' fix into something 
usable with the Debian 11 Podman; and the Debian Testing Podman (3.4) is 
not easily installable on Debian 11 (needs a newer libc). So until a fix 
makes its way into Debian 11 your workaround will be quite useful.
So thanks again.



-- 
Francois Gouget   http://fgouget.free.fr/
  Hell is empty and all the devils are here.
   -- Wm. Shakespeare, "The Tempest"

Install debian on USB-stick

[Sim Sim]

Hi.

Is possible to install debian-11.1.0-i386-netinst.iso on 16Gb USB2.0-stick?
A minimal environment, of course. And productivity do not need, just
curiosity.

Thanks.

Re: Package: nvidia-legacy-390xx-driver

[lina]

Can I have a system with both X-session and the nvidia-driver
as gaussian view requires

Gaussview must be run in an X-windows session. Details for controlling the
application are provided in the materials found in the Resources section.

Thanks,

On Tue, Nov 9, 2021 at 2:23 PM lina  wrote:

> It seems the drivers are there, my problems are:
>
> 1. I can't use gaussian view
> 2. The Sweet Home 3D Error: Sweet Home 3D will exit now because of a fatal
> error in the 3D rendering system of your computer. Please update the
> DirectX/OpenGL drivers of your computer graphic card.
>
> Thanks again, lina
>
> # glxinfo -B
> name of display: :0.0
> display: :0  screen: 0
> direct rendering: Yes
> Memory info (GL_NVX_gpu_memory_info):
> Dedicated video memory: 2048 MB
> Total available memory: 2048 MB
> Currently available dedicated video memory: 1718 MB
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: GeForce GT 730/PCIe/SSE2
> OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
> OpenGL core profile shading language version string: 4.60 NVIDIA
> OpenGL core profile context flags: (none)
> OpenGL core profile profile mask: core profile
>
> OpenGL version string: 4.6.0 NVIDIA 460.91.03
> OpenGL shading language version string: 4.60 NVIDIA
> OpenGL context flags: (none)
> OpenGL profile mask: (none)
>
> OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
>
>
>
> On Tue, Nov 9, 2021 at 12:05 PM Alexander V. Makartsev 
> wrote:
>
>> On 09.11.2021 15:26, lina wrote:
>>
>> Hi all,
>>
>> I am still struggling with the graphic card issue.
>>
>> What issue exactly?
>>
>> # nvidia-detect
>> Detected NVIDIA GPUs:
>> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B
>> [GeForce GT 730] [10de:1287] (rev a1)
>>
>> Checking card:  NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)
>> Your card is supported by all driver versions.
>> Your card is also supported by the Tesla 460 drivers series.
>> Your card is also supported by the Tesla 450 drivers series.
>> Your card is also supported by the Tesla 418 drivers series.
>> It is recommended to install the
>> nvidia-driver
>> package.
>>
>> Geforce GT 730 is still supported by Nvidia, so you should use recent
>> driver, not a legacy one.
>> $ sudo apt install nvidia-driver nvidia-driver-bin nvidia-driver-libs
>> nvidia-kernel-dkms nvidia-kernel-support mesa-utils
>>
>> Check the installation with:
>> $ glxinfo -B
>>
>> Shall I install the nvidia-legacy-390xx-driver
>>
>> https://packages.debian.org/sid/nvidia-legacy-390xx-driver
>>
>>
>> There is no point in doing that, because 390.xx driver series are
>> inferior to the most recent driver available.
>>
>>
>> --
>> With kindest regards, Alexander.
>>
>> ⢀⣴⠾⠻⢶⣦⠀
>> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
>> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
>> ⠈⠳⣄
>>
>>

Re: Problème pour accèder au disque D en dual boot avec Windows 10

[lists . debian]

Bonjour, Hier soir j'ai essayé de faire les modifications que nous avons 
discuté : Dans un 1er temps j'ai essayé de désactiver le fastboot, mais 
l'option n'était pas présente dans Windows. J'ai donc du réactiver 
l'hibernation (avec powercfg dans Powershell), et j'ai pu voir l'option dans 
Windows. J'ai donc désactivé fastboot, et ensuite j'ai désactivé à nouveau 
l’hibernation. Malheureusement il n'y a pas eu de changements dans le côté 
Debian (toujours les mêmes messages 'unsupported reparse point'). Par contre 
j'ai une autre question : En profitant de ce nouveau dual boot sur mon PC, je 
me suis décidé de faire un upgrade et changer ma SSD, en remplaçant mon SSD de 
128GO pour une nouvelle de 512GO (et ajouter de la mémoire RAM au passage). 
L'idée c'est d'avoir 2 partitions de ~256GO, une pour chaque système 
d'exploitation. Je me pose donc la question si dans ce cas de figure, 
sauriez-vous dire si je pourrais profiter de cette MAJ pour résoudre mon 
problème d'accès ? C'est à dire, j'avais pensé à cloner mon ancienne SSD, mais 
si vous pensez qu'en faisant une nouvelle installation (d'un ou des 2 systèmes) 
je pourrais optimiser mon PC, je pourrais profiter de l'opportunité... Qu'en 
pensez-vous ? Avez-vous des conseils à me donner ? Merci encore une fois de 
votre aide, Cordialement, Marc Le 2021-11-08 12:02, didier gaumet 
 a écrit : > > > > Le lundi 08 novembre 2021 à 11:06 
+0100, lists.deb...@netc.eu a écrit : > > > > Merci Didier, > > > > Petite 
précision, tu parles de fastboot ou hibernation ? > > > Je pose la question car 
j'ai déjà fait la manip dans powershell, mais > > je pense que avec la commande 
"powercfg -hibernate off", mais je > > pense qu'il est pareil. > > > > Tu as 
raison, je suis allé un peu vite sans bien me rappeler. > Si je comprends bien, 
il y a 3 modes démarrage dans les Windows récents > (à froid, réveil 
d'hibernation, Fast Startup) > 
https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/distinguishing-fast-startup-from-wake-from-hibernation
 > > Tu as déjà déactivé le 2ème mode (powercfg), il reste le 3ème > > Comment 
le Fast Startup (lien en anglais) avec les outils graphiques > d'administration 
Microsoft: > 
https://winaero.com/how-to-disable-or-enable-fast-startup-in-windows-8-1/ > ou 
avec le powershell en modifiant une clé de régistre > 
https://mspscripts.com/disable-windows-10-fast-boot-via-powershell/ > > ou en 
vérifiant peut-être que tu peux le faire avec powercfg (je n'ai > pas épulché 
toutes les options, y en a certaines qui pourraient être > adaptées) > 
https://docs.microsoft.com/fr-fr/windows-hardware/design/device-experiences/powercfg-command-line-options
 > > > Sinon je n'ai pas la main maintenant, mais si je me souviens bien, > > 
dans la BIOS il y a aussi une option Fastboot (je pense activé). Tu > > penses 
que cela pourrait avoir une incidence ? > > Autre question : pourquoi le 
dossier des images n'est pas affecté ? > > Que le dossier documents ? > [...] > 
> je suppose que tes difficultés à lire/accéder certaines données plutôt > que 
d'autres pourraient résulter d'un état insistant du système de > fichiers sous 
depuis Linux (possiblement que quand il démarre, en, > arrière plan, Windows 
remet en ordre certaines choses) > > >

Re: Package: nvidia-legacy-390xx-driver

[lina]

It seems the drivers are there, my problems are:

1. I can't use gaussian view
2. The Sweet Home 3D Error: Sweet Home 3D will exit now because of a fatal
error in the 3D rendering system of your computer. Please update the
DirectX/OpenGL drivers of your computer graphic card.

Thanks again, lina

# glxinfo -B
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 2048 MB
Total available memory: 2048 MB
Currently available dedicated video memory: 1718 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 460.91.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20



On Tue, Nov 9, 2021 at 12:05 PM Alexander V. Makartsev 
wrote:

> On 09.11.2021 15:26, lina wrote:
>
> Hi all,
>
> I am still struggling with the graphic card issue.
>
> What issue exactly?
>
> # nvidia-detect
> Detected NVIDIA GPUs:
> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B
> [GeForce GT 730] [10de:1287] (rev a1)
>
> Checking card:  NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)
> Your card is supported by all driver versions.
> Your card is also supported by the Tesla 460 drivers series.
> Your card is also supported by the Tesla 450 drivers series.
> Your card is also supported by the Tesla 418 drivers series.
> It is recommended to install the
> nvidia-driver
> package.
>
> Geforce GT 730 is still supported by Nvidia, so you should use recent
> driver, not a legacy one.
> $ sudo apt install nvidia-driver nvidia-driver-bin nvidia-driver-libs
> nvidia-kernel-dkms nvidia-kernel-support mesa-utils
>
> Check the installation with:
> $ glxinfo -B
>
> Shall I install the nvidia-legacy-390xx-driver
>
> https://packages.debian.org/sid/nvidia-legacy-390xx-driver
>
>
> There is no point in doing that, because 390.xx driver series are inferior
> to the most recent driver available.
>
>
> --
> With kindest regards, Alexander.
>
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> ⠈⠳⣄
>
>

Re: [OT, deeply] Guix

[Curt]

On 2021-11-08, Nicholas Geovanis  wrote:
>>
>> I thought plain text meant "a pure sequence of character codes" without
>> any formatting information attached to it (e.g. HTML) or something. As
>>
>
> Here's the thing. We already have many ways to install debian and any other

Here's yet another thing: your delightfully confident diatribe has
little or nothing to do with my post.  

Re: Debian version

[Linux-Fan]

Koler, Nethanel writes:


Hi
I am Nati, I am trying to find a variable that is configured in the linux- 
headers that can tell me on which Debian I am


Any reason for not using /etc/os-release instead?
IIRC this one is available on RHEL _and_ Debian systems.


For example in RedHat
After downloading the linux-headers
I can go to cd /usr/src/kernels//include/generated/uapi/linux
There there is a file called version.h
Where they define this variables

#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
#define RHEL_MAJOR 8
#define RHEL_MINOR 4

When I tried the same with Debian I got to a dead end
Can you please help me find something similar in the linux-headers for  
Debian?


I tried

$ grep -RF Debian /usr/src

and got a few hits, among those are

| .../include/generated/autoconf.h:#define CONFIG_CC_VERSION_TEXT "gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110"
| .../include/generated/compile.h:#define LINUX_COMPILER "gcc-10 (Debian 10.2.1-6) 
10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2"
| .../include/generated/compile.h:#define UTS_VERSION "#1 SMP Debian 5.10.46-5 
(2021-09-23)"
| .../include/generated/package.h:#define LINUX_PACKAGE_ID " Debian 5.10.46-5"

If your goal is to evaluate them programatically during compile-time of a C  
project, this might not be ideal though, because all of the values I found  
seem to be strings.


HTH
Linux-Fan

öö


pgpliwZzHZIW3.pgp
Description: PGP signature

Re: Debian version

[Greg Wooledge]

On Tue, Nov 09, 2021 at 09:22:25AM +, Koler, Nethanel wrote:
> I am Nati, I am trying to find a variable that is configured in the 
> linux-headers that can tell me on which Debian I am 

This sounds like an X-Y problem.  What's your real objective?

There is NOT a one-to-one correspondence between a Linux kernel version
and a Debian release version.  Debian allows you the freedom to use
any kernel you want -- one of Debian's kernels, or one that you built
yourself, or one that you copied over from an Ubuntu system, or whatever.

Even if you use a Debian kernel, it might not have come from the Debian
version that you're currently running.  You might still be using a 4.x
kernel on bullseye, for instance, due to incompatibility with one of
your devices.  Or you might be using a backported kernel from a future
release because of hardware needs.

> For example in RedHat 
> After downloading the linux-headers
> I can go to cd /usr/src/kernels//include/generated/uapi/linux
> There there is a file called version.h
> Where they define this variables  
> 
> #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
> #define RHEL_MAJOR 8
> #define RHEL_MINOR 4

That sounds like a really bad idea to me.

At *best* this would only tell you what version of Red Hat Enterprise
Linux the developer thought the kernel was being built on.  At worst,
it's a complete fabrication.  In *all* cases, this number is baked into
the kernel, at compile time, and does not reflect anything about the
actual system that the kernel is booting.

Correct me if I'm wrong, but I think RHEL does not support upgrades.  If
you're running RHEL 7 and you want to upgrade to RHEL 8, you have to
reinstall.

Therefore, it's *sort of* conceivable that the version number which is
baked into the kernel might mean something, but only if the administrator
of the box has actually followed RHEL's advice and never upgraded it,
outside of official RHEL support channels.

That doesn't work for Debian, at all.

Debian's greatest strength is its ability to be upgraded.  A great deal
of development time is put into achieving this goal.  A Debian system is
expected to be installed one time, and upgraded many times, until it's
finally retired.

At any point in that lifespan, you might have a kernel which has an older
release's version number baked into it, on a newer release of Debian.  The
version number inside the kernel would therefore be inaccurate.

Re: Package: nvidia-legacy-390xx-driver

[Alexander V. Makartsev]

On 09.11.2021 15:26, lina wrote:

Hi all,

I am still struggling with the graphic card issue.


What issue exactly?


# nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B 
[GeForce GT 730] [10de:1287] (rev a1)


Checking card:  NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)
Your card is supported by all driver versions.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
Your card is also supported by the Tesla 418 drivers series.
It is recommended to install the
    nvidia-driver
package.

Geforce GT 730 is still supported by Nvidia, so you should use recent 
driver, not a legacy one.
    $ sudo apt install nvidia-driver nvidia-driver-bin 
nvidia-driver-libs nvidia-kernel-dkms nvidia-kernel-support mesa-utils


Check the installation with:
    $ glxinfo -B


Shall I install the nvidia-legacy-390xx-driver

https://packages.debian.org/sid/nvidia-legacy-390xx-driver 




There is no point in doing that, because 390.xx driver series are 
inferior to the most recent driver available.



--
With kindest regards, Alexander.

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

Re: Renommer les interfaces réseau

[Frédéric MASSOT]

Le 09/11/2021 à 11:16, ajh-valmer a écrit :

Bonjour à tous,

Mes interfaces réseau :
enp0s25 (carte ethernet n°1)
enp4s0 (carte ethernet n°2)
wlp0s29u1u2 (clé USB Wifi)

Est-il possible de les renommer comme ceci ? :
eth0
eth1
wlan0
c'est à dire en terme plus parlant,
et si oui, comment ?



Le nommage est géré par udev, donc il faut allez voir dans la doc de 
udev : /usr/share/doc/udev/


Tu peux lire le fichier "/usr/share/doc/udev/README.Debian.gz" et en 
particulier le paragraphe "Custom net interface naming".




--
==
|  FRÉDÉRIC MASSOT   |
| http://www.juliana-multimedia.com  |
|   mailto:frede...@juliana-multimedia.com   |
| +33.(0)2.97.54.77.94  +33.(0)6.67.19.95.69 |
===Debian=GNU/Linux===

Re: Renommer les interfaces réseau

[B. GRANDHOMME]

Bonjour,

Ce site doit correspondre à ta demande

https://leforuminfo.com/renommer-interface-reseau

Cordialement

Le 2021-11-09T11:16:27.000+01:00, ajh-valmer  a
écrit :

> Bonjour à tous,
> 
> Mes interfaces réseau :
> 
> enp0s25 (carte ethernet n°1)
> 
> enp4s0 (carte ethernet n°2)
> 
> wlp0s29u1u2 (clé USB Wifi)
> 
> Est-il possible de les renommer comme ceci ? :
> 
> eth0
> 
> eth1
> 
> wlan0
> 
> c'est à dire en terme plus parlant,
> 
> et si oui, comment ?
> 
> Merci d'avance, bonne journée.
> 
> A. Valmer

B. GRANDHOMME

06.87.83.57.65

Re: Renommer les interfaces réseau

[Bernard Schoenacker]

- Mail original -
> De: "ajh-valmer" 
> À: debian-user-french@lists.debian.org
> Envoyé: Mardi 9 Novembre 2021 11:16:27
> Objet: Renommer les interfaces réseau
> 
> Bonjour à tous,
> 
> Mes interfaces réseau :
> enp0s25 (carte ethernet n°1)
> enp4s0 (carte ethernet n°2)
> wlp0s29u1u2 (clé USB Wifi)
> 
> Est-il possible de les renommer comme ceci ? :
> eth0
> eth1
> wlan0
> c'est à dire en terme plus parlant,
> et si oui, comment ?
> 
> Merci d'avance, bonne journée.
> 
> A. Valmer
> 

Bonjour,

le sujet à déjà été abordé et il est disponible dans les 
archives de la liste ...

Cordialement

Bernard

Package: nvidia-legacy-390xx-driver

[lina]

Hi all,

I am still struggling with the graphic card issue.

# nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B
[GeForce GT 730] [10de:1287] (rev a1)

Checking card:  NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)
Your card is supported by all driver versions.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
Your card is also supported by the Tesla 418 drivers series.
It is recommended to install the
nvidia-driver
package.
# dpkg --get-selections | grep nvidia
glx-alternative-nvidia install
libegl-nvidia0:amd64 install
libgl1-nvidia-glvnd-glx:amd64 install
libgles-nvidia1:amd64 install
libgles-nvidia2:amd64 install
libglx-nvidia0:amd64 install
libnvidia-cbl:amd64 install
libnvidia-cfg1:amd64 install
libnvidia-eglcore:amd64 install
libnvidia-encode1:amd64 install
libnvidia-glcore:amd64 install
libnvidia-glvkspirv:amd64 install
libnvidia-ml1:amd64 install
libnvidia-ptxjitcompiler1:amd64 install
libnvidia-rtcore:amd64 install
nvidia-alternative install
nvidia-detect install
nvidia-driver install
nvidia-driver-bin install
nvidia-driver-libs:amd64 install
nvidia-egl-common install
nvidia-egl-icd:amd64 install
nvidia-installer-cleanup install
nvidia-kernel-common install
nvidia-kernel-dkms install
nvidia-kernel-support install
nvidia-legacy-check install
nvidia-modprobe install
nvidia-persistenced install
nvidia-settings install
nvidia-smi install
nvidia-support install
nvidia-vdpau-driver:amd64 install
nvidia-vulkan-common install
nvidia-vulkan-icd:amd64 install
xserver-xorg-video-nvidia install


Shall I install the nvidia-legacy-390xx-driver

https://packages.debian.org/sid/nvidia-legacy-390xx-driver

Renommer les interfaces réseau

[ajh-valmer]

Bonjour à tous,

Mes interfaces réseau :
enp0s25 (carte ethernet n°1)
enp4s0 (carte ethernet n°2)
wlp0s29u1u2 (clé USB Wifi)

Est-il possible de les renommer comme ceci ? :
eth0
eth1
wlan0
c'est à dire en terme plus parlant,
et si oui, comment ?

Merci d'avance, bonne journée.

A. Valmer

Re: Imprimante scanner

[Michel]

Le 08/11/2021 à 21:50, didier gaumet a écrit :

>>
>> Note: à chaque question j'ai juste tapé "Enter" et donc c'est
>> l'option
>> avec '*' qui était choisie.
> 
> C'est là que je pense tu devrais recommencer en répondant yes à "Would
> you like to install another print queue for this device": le but c'est
> de réinstaller ton combo par hp-setup mais en tant que root plutôt
> qu'utilisateur lambda (je crois bien que par le passé avec une HP
> OfficeJet ça m'avait permis d'arriver à scanner alors qu'en installant
> via les outils hplip en simple utilisateur je n'y arrivais pas) 
> 
Je l'avais fait auparavant sans meilleurs résultats. J'avais ensuite
recommencé, en virant d'abord les imprimantes connues puis en repartant
de zéro.

Bon, ce n'est pas la fin du monde, encore merci de l’intérêt porté mes
interrogations.

> NOTE: c'est intéressant, en regardant les messages de scanimage, j'ai
> un peu l'impression (trompeuse?) que HP a conçu à l'identique la M28a
> (USB) et M28w (USB+wifi): la M28a doit manquer d'une petite carte
> d'extension wifi mais semble reconnue comme un combo réseau à travers
> son port USB (ipp-usb), donc si ça se trouve ton modèle M28a
> fonctionnerait en désinsallant totalement hplip et en installant cusp-
> daemon, cups-common et sane-airscan... (pure hypothèse sabs l'ombre
> d'une preuve)
> 

Je vais en rester là, ça deviendrait à prendre un marteau pilon pour
écraser une mouche ;)

Le plus râlant, c'est qu'avant cette mise à jour, tout fonctionnait sans
problème.