Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[steve]

Le 30-08-2021, à 22:23:20 +0200, Christophe_VANHOUTTE a écrit :


  Optimus: Jamais entendu parler, peut-être parce que j’avais pas le
  besoin de configurer une carte graphique "récente"


Ce n'est pas vraiment le fait qu'elle soit récente qui pose problème
ici. D'ailleurs la GTX 10660 Ti ne l'est pas vraiment.


  Si je comprends bien Optimus NVIDIA (pas Optimus Prime dans les
  transfoemrs lol) permet de switcher entre les GPU ?


Pour être précis, il y a un GPU (ta NVIDIA) et un IGP (Integrated
Graphic Processor), la Radeon Vega 7.


  Mais il resterait des problèmes (source en 2020) et cela devrait
  s’améliorer dans le temps.

  Je viens de lire une documentation sur Optimus, il est dit “qu’il ne
  faut pas l’utiliser”


Mais encore… :)


  Pour reprendre , en installa,t XFCE, les paquets drivers NVIDIA libre
  seront installés comme ci-dessous , donc ?


Driver NVIDIA libre est un contre-sens. Le driver NVIDIA empaqueté dans
Debian est le driver propriétaire de NVIDIA. Le driver libre qui peut
faire tourner ta carte NVIDIA s'appelle « nouveau ». C'est celui-là qui
est installé par défaut. De plus, ça n'a strictement rien à voir avec
ton desktop, que ce soit Xfce, Kde, Gnome ou autre.

Le passage entre IGP et GPU se fait (normalement) automatiquement
dépendant des besoins. C'est transparent pour l'utilisateur. Par contre,
certains BIOS permettent de choisir quelle carte sera utilisée
prioritairement ou d'en désactiver une particulièrement. Sur mon Dell,
ce n'est malheureusement pas le cas. Dans ton cas, je ne sais pas.

Pour pouvoir utiliser cette techno Optimus, j'ai dû supprimer le driver
libre « nouveau » et installer la suite de paquets ci-dessous (en
particulier bumblebee). J'ai fait ça il y a environ un an, sous testing
à l'époque, donc c'est possible que ça a évolué depuis.

[snip]


dpkg -l | grep nvidia
ii  bumblebee-nvidia
3.2.1-27amd64NVIDIA Optimus support

  Merci pour cette info aussi.


Pas de quoi, et bon courage, tout ça est un peu galère (c'est fait pour
les machines Windows à la base).


--
Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 4.12


Pas encore mis à niveau vers Bullseye ? Si tu veux utiliser Optimus, je
ne peux que te conseiller de passer à Bullseye, il y a eu de vraies
améliorations entre les deux versions.

Re: Intel nuc 11 i5 kit 安裝debian後，首次開機就失敗，黑化面左上角遊標一直閃

[Keith Bainbridge]

On 31/8/21 05:09, Andrei POPESCU wrote:

Console font can be configured with

 dpkg-reconfigure console-setup



Thanks Andrei

Frankly, I was almost up to asking this myself.

--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
0447 667 468

Re: ifupdown lost at upgrade time to bullseye

[Jude DaShiell]

Is iwctl part of default bullseye installations?  Maybe networkd.service
can be used with systemd this I haven't tried since I'm using ethernet but
do have wi-fi capability.  I could try these avenues and see if they're
open.


On Mon, 30 Aug 2021, Dan Ritter wrote:

> Harald Dunkel wrote:
> > how comes ifupdown is dropped at upgrade time to bullseye, leaving the 
> > (headless) system without network connection while the upgrade is not 
> > completed yet, and breaking network on the next reboot?
>
> This has not yet happened to me in nine or ten upgrades to
> bullseye; all but two of them depended on
> /etc/network/interfaces and nothing weird happened regarding
> ifupdown.
>
> -dsr-
>
>

Full time is on the phone ☎️ I have been the most effective person I can get from this phone please please p

[Gabe Odabi]

Sent from my iPhone

Re: Get Terminal to Echo line in buffer on backspace

[songbird]

Greg Wooledge wrote:
...
> You simply aren't going to get that behavior.  So I'm telling you how
> you can work around the problem, or fix your *underlying problem*.

  i agree, if you have something sending information to a console
or terminal, you can just open up another terminal or tab and then
use that instead.

  the other approach would be to redirect the output of the programs
that are causing problems to a file or /dev/null


  songbird

Re: Permission Questions

[Rainer Dorsch]

Am Montag, 30. August 2021, 21:58:47 CEST schrieb Greg Wooledge:
> On Mon, Aug 30, 2021 at 09:01:33PM +0200, Rainer Dorsch wrote:
> > rd@h370:~/tmp.nobackup$ ls -l /tmp/123
> > -rw-rw-r-- 1 rd users 0 30. Aug 20:42 /tmp/123
> > 
> > User ka overwrites it with the content of another file (atomically):
> > 
> > ka@h370:~$ echo test > 123
> > ka@h370:~$ mv 123 /tmp/123
> > mv: cannot move '123' to '/tmp/123': Operation not permitted
> 
> In order to perform this move, ka would first need to unlink the
> existing /tmp/123 file.  ka cannot do that, because the /tmp directory
> is "sticky".  Only "rd" (or root) can do it.
> 
> > Maybe moving removes a node in /tmp,
> 
> Yes.  You can verify with strace if you're curious enough.
> 
> > so I am trying to append to the file as a
> > test:
> > 
> > -rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123
> > 
> > ka@h370:~$ id
> > uid=1401(ka) gid=1401(ka) Gruppen=1401(ka),20(dialout),21(fax),24(cdrom),
> > 30(dip),44(video),46(plugdev),100(users),1000(sispmctl)
> > ka@h370:~$ ls -l /tmp/123
> > -rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123
> > ka@h370:~$ echo test >> /tmp/123
> > -bash: /tmp/123: Permission denied
> 
> That one should have worked, due to the secondary group membership.
> 
> unicorn:~$ sudo touch /tmp/123; sudo chgrp video /tmp/123; sudo chmod 664
> /tmp/123 [sudo] password for greg:
> unicorn:~$ ls -l /tmp/123
> -rw-rw-r-- 1 root video 0 Aug 30 15:56 /tmp/123
> unicorn:~$ id
> uid=1000(greg) gid=1000(greg)
> groups=1000(greg),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video)
> ,46(plugdev),108(netdev) unicorn:~$ echo stuff >> /tmp/123
> unicorn:~$
> 
> It works for me.  Is your /tmp a non-Unix file system, or is it mounted
> with any unusual options?

Thanks for testing and your quick response.

Hmm...your example works for me as well

rd@h370:~/tmp.nobackup$ sudo touch /tmp/123; sudo chgrp video /tmp/123; sudo 
chmod 664 /tmp/123
[sudo] Passwort für rd: 
rd@h370:~/tmp.nobackup$ ls -l /tmp/123
-rw-rw-r-- 1 root video 0 30. Aug 22:52 /tmp/123
rd@h370:~/tmp.nobackup$ id
uid=2809(rd) gid=2809(rd) Gruppen=2809(rd),4(adm),20(dialout),21(fax),
24(cdrom),25(floppy),27(sudo),30(dip),44(video),46(plugdev),100(users),
114(lpadmin),118(scanner),126(docker),127(vboxusers),130(i2psvc),
131(wireshark),141(libvirt),1000(sispmctl)
rd@h370:~/tmp.nobackup$ echo stuff >> /tmp/123
rd@h370:~/tmp.nobackup$ 

As soon as I do a chown to a non-root user on /tmp/123 it does not work for me 
anymore.

Is root somehow treated differently as other users?

I am not aware of special mount options for /tmp, it should be a standard 
installation:

rd@h370:~/tmp.nobackup$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=16342996k,nr_inodes=4085749,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=3273064k,mode=755)
/dev/mapper/b370--vg-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
cgroup2 on /sys/fs/cgroup type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=13462)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sda2 on /boot type ext2 (rw,relatime)
/dev/sda1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-
ro)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
-hosts on /mnt/net type autofs 
(rw,relatime,fd=6,pgrp=1674,timeout=60,minproto=5,maxproto=5,indirect,pipe_ino=19859)
tmpfs on /run/user/113 type tmpfs 
(rw,nosuid,nodev,relatime,size=3273064k,nr_inodes=818266,mode=700,uid=113,gid=117)
tmpfs on /run/user/2809 type tmpfs 
(rw,nosuid,nodev,relatime,size=3273064k,nr_inodes=818266,mode=700,uid=2809,gid=2809)
-hosts on /mnt/net/fs/mnt/disk/data type autofs 

Re: How to avoid systemd/udev unpredictable NIC names

[Greg Wooledge]

On Tue, Aug 31, 2021 at 01:44:09AM +0200, Steve Keller wrote:
> One interface is on the mainboard (eth0), the other is a PCI card
> (eth1).  BTW, PCI really, not PCIe other something like that.  It's a
> really old machine.

OK.  I recommend making two "dot link" files, one for each card, in
order to assign the names you want them to have.

> Actually, I don't know this.  When I wrote unpredictable new naming
> scheme I meant systemd's enps scheme, since it's
> unpredictable for me as long as I don't learn these numbers for my
> mainboard and PCI card config.
> 
> Why is systemd-udevd unqualified for this jobs?

Because PCI slot numbers change.  They can change when you add a device,
or remove a device (even if they're not network interfaces), or upgrade
your motherboard firmware.

These names are not "predictable" because they're based on the PCI slot
number, which is not stable.

> Well, this is exactly what I dislike with systemd
> & co.  I've read lots of docs & man pages, still I don't know the
> exact process of how the interfaces are renamed after the kernel names
> the eth.  Does udevd run first, does systemd call udev, does
> systemd do the renaming itself or is it done by "net_setup_link udev
> builtin" as systemd.link(5) states?

I don't pretend to know every permutation.  On my system, which is a
desktop PC with a builtin NIC configured with a .link file, I get this:

[1.102914] libphy: r8169: probed
[1.103400] r8169 :02:00.0 eth0: RTL8168gu/8111gu, 18:60:24:77:5c:ec, 
XID 509, IRQ 127
[1.103761] r8169 :02:00.0 eth0: jumbo features [frames: 9194 bytes, tx 
checksumming: ko]
[1.104945] r8169 :02:00.0 lan0: renamed from eth0

In other words, the kernel probes NICs, and starts handing out names
to them based on the order in which the probing completes.  The first
one that successfully responds gets called eth0, the second one gets
called eth1, and so on.

Then, because I have a .link file, the matching interface is renamed to
the name I selected (lan0).  I chose this name specifically because it
is *not* one of the names the kernel will assign.

Nobody has ever explained to me how this all works, so I expect that
something will explode in the following scenario:

1) A .link file exists which maps one of the NICs to "eth0".
2) System is booted.
3) First interface is probed and named eth0.
4) Second interface is probed and named eth1.
5) The second interface matches the .link file, and is renamed to eth0.
6) Now there are two interfaces named "eth0", and things explode.

I don't know whether this is how it *actually* works, but I don't want
to find out the hard way.  So I chose names that make it impossible
for this to happen.

If there are no .link files, and assuming I'm not using net.ifnames=0,
the NICs will be renamed to the "predictable" names (eno0 or enp2s5 or
whatever) instead of the names that I selected.

If I use net.ifnames=0 then there won't be any renaming.  The NICs will
keep their probing-order-assigned named (eth0, eth1, and so on).

> NFS with systemd is a nightmare.

I haven't had an issue with it, personally.  Make sure your interfaces
are configured in /etc/network/interfaces with "auto" and not with
"allow-hotplug".  That solves 80% of the problems I hear about.

The only NFS issues I've had in recent years are related to NFS version
mismatches (NFSv3 vs. NFSv4 and so on).  Nothing caused by systemd.

Re: Intel nuc 11 i5 kit 安裝debian後，首次開機就失敗，黑化面左上角遊標一直閃

[Keith Bainbridge]

On 31/8/21 05:09, Andrei POPESCU wrote:

Console font can be configured with

 dpkg-reconfigure console-setup


Follow up from:Is there a way to make larger options available, please?

and chose VGA in screen 3  (rather than fixed) and got three lager 
options; and the result was immediate, including the output from the process



--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
0447 667 468

Re: Intel nuc 11 i5 kit 安裝debian後，首次開機就失敗，黑化面左上角遊標一直閃

[Keith Bainbridge]

On 31/8/21 05:09, Andrei POPESCU wrote:

Console font can be configured with

 dpkg-reconfigure console-setup



Exit and log in again

My result was very marginal improvement.  8x18 is the largest I was offered.

Is there a way to make larger options available, please?

--
All the best

Keith Bainbridge

keith.bainbridge.3...@gmail.com
0447 667 468

Re: How to avoid systemd/udev unpredictable NIC names

[Steve Keller]

Roberto C. Sánchez  writes:

> Since nobody else has mentioned this link, here is where I recommend you
> start: https://wiki.debian.org/NetworkInterfaceNames

Oh, that's what I meant by "wiki" in my posts.  Sorry, I should have
given the URL.  It's linked from the buster release-notes in section
5.1.6

Steve

Re: How to avoid systemd/udev unpredictable NIC names

[Steve Keller]

Greg Wooledge  writes:

> On Tue, Aug 31, 2021 at 12:27:57AM +0300, IL Ka wrote:
> > >
> > > This gives unpredictable results if the system has more than one
> > > ethernet interface, or more than one wireless interface.
> > >
> > > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
> > >
> >
> > Isn't that what the topic starter asked about?:)
>
> I sincerely hope that the OP will tell us how many ethernet interfaces
> their "server" has, so we can stop the hypothetical tennis match.

One interface is on the mainboard (eth0), the other is a PCI card
(eth1).  BTW, PCI really, not PCIe other something like that.  It's a
really old machine.

> I advocated creating the .link files in my original message.  I even
> gave examples.
>
> I do *not* advocate "letting systemd-udevd do its job", because it's
> absolutely unqualified for duty.  The names it chooses are *not*
> predictable.  The OP knew this.  I can tell by their wording.

Actually, I don't know this.  When I wrote unpredictable new naming
scheme I meant systemd's enps scheme, since it's
unpredictable for me as long as I don't learn these numbers for my
mainboard and PCI card config.

Why is systemd-udevd unqualified for this jobs?  As far as I
understand, systemd implements this new "predictavle" scheme by
calling udevd.  No?  Well, this is exactly what I dislike with systemd
& co.  I've read lots of docs & man pages, still I don't know the
exact process of how the interfaces are renamed after the kernel names
the eth.  Does udevd run first, does systemd call udev, does
systemd do the renaming itself or is it done by "net_setup_link udev
builtin" as systemd.link(5) states?  And is this udev builtin a part
of udev or part of systemd or part of systemd-udevd?  At least there
is no man page for net_setup_link. So the admin has to guess.

This is the same picture with other systemd, udev, avahi, ... stuff.
In newer clients, I don't understand DNS lookup anymore.  In
/etc/resolv.conf you cannot find the DNS server used.  A rndc reload
on the server is ignored for quite a long time.  I recently had that
problem and couldn't figure out how to make the client (Ubuntu 20.04)
get the DNS entry from the server as it was told by DHCP, instead of
its local cache.  Even restarting several systemd service on the
client didn't help.  Since the man pages are very incomplete I
could only poke in the dark, trial and error until it somehow
magically worked again.

NFS with systemd is a nightmare.

20 years ago until about 10 years ago I knew every single daemon on my
system and I knew exactly what each one did do.  Now there are dozens
of daemons, interacing in obscure ways, poorly documented, so I don't
know much of a current system anymore.  I consider this a major
security problem since any malicous new daemon would probably go
unrecognized quite a long time.

Steve

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

[Jim Popovitch]

On Mon, 2021-08-30 at 21:53 +0300, Andrei POPESCU wrote:
> On Ma, 10 aug 21, 13:32:09, Jim Popovitch wrote:
> > How can I determine what the "1 not upgraded" package might be?
> > 
> > 
> > ~$ apt-get update 
> > Hit:1 http://ftp.us.debian.org/debian bullseye InRelease
> > Hit:2 http://security.debian.org bullseye-security InRelease
> > Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease
> > Reading package lists... Done
> > 
> > ~$ apt-get upgrade 
> > Reading package lists... Done
> > Building dependency tree... Done
> > Calculating upgrade... Done
> > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> > 
> > 
> > ~$ apt-get dist-upgrade 
> > Reading package lists... Done
> > Building dependency tree... Done
> > Calculating upgrade... Done
> > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> 
> A bit late to the party...
> 
> If pinning is the issue, the definitive place to check that is always 
> the output of 'apt policy' (with no package)[1].
> 
> 
> If that doesn't provide any new information you could ask deity ;)
> 
> https://lists.debian.org/deity/
> 
> 
> [1] It's also a very good way to check your pinning actually works

There was nothing pinned, but the issue did go away sometime in the week
before Bullseye was released.  I'm convinced it was a mirror/cache
issue.

-Jim P.

Permission Questions

[Rainer Dorsch]

Hi,

I am looking for advice how to implement best this kind of usecase:

User rd creates a file on /tmp:

rd@h370:~/tmp.nobackup$ touch /tmp/123
rd@h370:~/tmp.nobackup$ chgrp users /tmp/123
rd@h370:~/tmp.nobackup$ chmod g+w /tmp/123
rd@h370:~/tmp.nobackup$ ls -l /tmp/123
-rw-rw-r-- 1 rd users 0 30. Aug 20:42 /tmp/123
rd@h370:~/tmp.nobackup$ 

User ka overwrites it with the content of another file (atomically):

ka@h370:~$ echo test > 123
ka@h370:~$ mv 123 /tmp/123
mv: cannot move '123' to '/tmp/123': Operation not permitted
ka@h370:~$ id
uid=1401(ka) gid=1401(ka) groups=1401(ka),20(dialout),21(fax),24(cdrom),
30(dip),44(video),46(plugdev),100(users),1000(sispmctl)
ka@h370:~$ 

Although ka has write permissions as group member, this does not work.

Maybe moving removes a node in /tmp, so I am trying to append to the file as a 
test:

rd@h370:~/tmp.nobackup$ touch /tmp/123 
rd@h370:~/tmp.nobackup$ chgrp users /tmp/123 
rd@h370:~/tmp.nobackup$ chmod g+w /tmp/123 
rd@h370:~/tmp.nobackup$ ls -l /tmp/123 
-rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123 
rd@h370:~/tmp.nobackup$ 

ka@h370:~$ id 
uid=1401(ka) gid=1401(ka) Gruppen=1401(ka),20(dialout),21(fax),24(cdrom),
30(dip),44(video),46(plugdev),100(users),1000(sispmctl) 
ka@h370:~$ ls -l /tmp/123 
-rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123 
ka@h370:~$ echo test >> /tmp/123 
-bash: /tmp/123: Permission denied 
ka@h370:~$ 

Even that does not work. Why not?

Is there something special with /tmp?

kan@h370:~$ ls -ld /tmp
drwxrwxrwt 26 root root 32768 Aug 30 20:51 /tmp
ka@h370:~$ 


Now attempting to do the same in a regular home directory:

rd@h370:~/tmp.nobackup$ touch 123
rd@h370:~/tmp.nobackup$ chgrp users 123
rd@h370:~/tmp.nobackup$ chmod g+w 123
rd@h370:~/tmp.nobackup$ 

ka@h370:~$ echo test >> /home/rd/tmp.nobackup/123
ka@h370:~$

Appending works!

But replacing the file with a mv command does not work in the /home directory:

rd@h370:~/tmp.nobackup$ touch 123   
rd@h370:~/tmp.nobackup$ ls -l 123 
-rw-rw-r-- 1 rd users 5 30. Aug 20:39 123 
rd@h370:~/tmp.nobackup$ 

ka@h370:~$ mv 123 /home/rd/tmp.nobackup/123 
mv: cannot move '123' to '/home/rd/tmp.nobackup/123': Permission denied 
ka@h370:~$ 

If I redirect the output and overwrite the file instead of using mv,  the 
system allows me to do that:

rd@h370:~/tmp.nobackup$ touch 123
rd@h370:~/tmp.nobackup$ chgrp users 123
rd@h370:~/tmp.nobackup$ chmod g+w 123
rd@h370:~/tmp.nobackup$ ls -l 123
-rw-rw-r-- 1 rd users 0 30. Aug 20:51 123
rd@h370:~/tmp.nobackup$ 

ka@h370:~$ echo test > 123
ka@h370:~$ cat 123 > /home/rd/tmp.nobackup/123 
ka@h370:~$ cat /home/rd/tmp.nobackup/123
test
ka@h370:~$ 

It is weird that mv is forbidden, but redirecting the output is allowed. The 
end result on the file system would be the same!

Downside of redirecting is that /home/rd/tmp.nobackup/123 is not updated 
atomically (assuming another process is reading it asynchronically).

So essentially what I want to achieve:
- Updating a file atomically
- Preferably in /tmp

Any advice or hint is welcome.

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

Re: How to avoid systemd/udev unpredictable NIC names

[Steve Keller]

Greg Wooledge  writes:

> On Mon, Aug 30, 2021 at 04:41:55PM -0400, Dan Ritter wrote:
> > Steve Keller wrote:
> > > I plan to upgrade a server from   Debian stretch to buster.  Having read
> > > the release notes I wonder what's the best way to avoid the new scheme
> > > of unpredictable network interface names.
> >
> > In /etc/default/grub, assuming that you are booting with grub,
> >
> > GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"
> >
> > The "quiet" is not necessary and is a different feature.
>
> This gives unpredictable results if the system has more than one
> ethernet interface, or more than one wireless interface.
>
> It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.

OK, several people suggested the kernel command-line option
net.ifnames=0.  Since I almost never change hardware configurations
this is probably OK even with my two NICs, one on the mainboard, the
second is a PCI card.  If the kernel should really change the
enumeration of the cards in some future, I will do something about
that.

In buster I still need to disable the
/etc/udev/rules.d/70-persistent-net.rule file since the kernel cmdline
option doesn't deactivate this.  AFAIK, the kernel cmdline option only
ends up in the environment of process 1, i.e. systemd.  Will systemd
communicate this to udev in a future Debian release or how is that
supposed to work.  The wiki says, the plan for buster was to not
support this .rules file.

My other option would be customized names using systemd.link files.
While I prefer eth I would then probably use en<0>, since the wiki
recommends not using eth.  I still don't understand, why eth in
a systemd.link file would be a problem, since in the udev .rules this
has worked for years.

Steve

Re: How to avoid systemd/udev unpredictable NIC names

[Roberto C . Sánchez]

On Mon, Aug 30, 2021 at 10:20:46PM +0200, Steve Keller wrote:
> I plan to upgrade a server from   Debian stretch to buster.  Having read
> the release notes I wonder what's the best way to avoid the new scheme
> of unpredictable network interface names.
> 
> I don't   care what PCI bus and what slot my NICs are attached to, I
> don't want to learn and don't want to have to remember this hardware
> configurationan and I don't want to type these cumbersome and error
> prone names.  I simply have eth0 for the internal network and eth1 for
> my external network to the DSL router.  That's easy and I want to keep
> it that way.
> 
> The Debian wiki   on this shows several ways involving kernel cmdline,
> udev, and systemd.  I've read it, I've also read some of the sparse
> and incomplete systemd documentation for almost an hour.  Still I
> don't know when and what software component (kernel, udev, systemd)
> decides the NIC names and whether and in which way these conflict each
> other. [1]
> 
> Also, after reading the   wiki it's still unclear to me, which of the
> several ways will survive the next upgrade to bullseye.
> 
> The safest way seems to   be what's called "Custom schemes" but this
> section explicitly states the names eth0, etc. shouldn't be used.
> 
> So I'm still confused what to do after the upgrade to buster to   keep
> my network names.
> 

Since nobody else has mentioned this link, here is where I recommend you
start: https://wiki.debian.org/NetworkInterfaceNames

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: TV hdmi overscan issues

[Felix Miata]

Henning Follmann composed on 2021-08-30 18:09 (UTC-0400):...
> xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
> to shift the x axis.
... 

On a 39" Proscan I needed this to eliminate overscan:
xrandr --output HDMI-1 --set underscan on --set "underscan vborder" 20 --set 
"underscan hborder" 35
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: How to avoid systemd/udev unpredictable NIC names

[Thomas Hochstein]

IL Ka schrieb:

> > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
> 
> Isn't that what the topic starter asked about?:)

I don't think so:
| I simply have eth0 for the internal network and eth1 for
| my external network to the DSL router.

That looks like two ethernet NICs.

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[didier gaumet]

Bon alors c'est vraiment pas un domaine que je maîtrise donc je raconte
potentiellement des bêtises, mais...

Ce n'est peut-être pas possible dans tous les cas (exemple: un
BIOS/UEFI capricieux, etc...) mais les retours sur internet semblent
indiquer que l'utilisation simultanée de deux cartes graphiques avec
Xorg (avec wayland, je ne sais pas, je n'ai pas cherché) est possible
depuis longtemps mais nécessite une configuration à l'ancienne:
création manuelle d'un xorg.conf avec toutes les options nécessaires  

il y a un exemple sur le wiki Archlinux avec une instance unique de
serveur Xorg contrôlant 4 écrans physiques via 2 cartes graphiques
https://wiki.archlinux.org/title/Multihead

TV hdmi overscan issues

[Henning Follmann]

Hello,
I recently upgraded a NUC (which is my kodi media server) to bullseye.
I always had an issue with the overscan of my TV monitor.
The overscan cannot be disabled on the monitor (it is an 16 year old
sharp). And I tried to compensate via xrandr --transform, which I never
was able to figure out. But you can set in kodi the display to compensate for
this. You still can do this, however kodi(bullseye) forgets these settings,
which means you have to configure this after every new start of kodi.
I think this might be a bug. But now I want o try again to solve the overscan
issue on system level (most likely again with xrandr)
Now this sytem runs with wayland and for any combination of the --transform
matrix I currently get an error:
X Error of failed request: BadValue (Integer parameter out of range for 
operation)

the initail try was just
xrandr --output XWAYLAND3 --mode 1280x720 --transform 1.05,0,-10,0,1,0,0,0,1
to shift the x axis.
Is this a wayland issue?


-H

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

Re: How to avoid systemd/udev unpredictable NIC names

[Greg Wooledge]

On Tue, Aug 31, 2021 at 12:27:57AM +0300, IL Ka wrote:
> >
> > This gives unpredictable results if the system has more than one
> > ethernet interface, or more than one wireless interface.
> >
> > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
> >
> 
> Isn't that what the topic starter asked about?:)

I sincerely hope that the OP will tell us how many ethernet interfaces
their "server" has, so we can stop the hypothetical tennis match.

> To make names predictable one can either leave everything as-is and let
> `systemd-udev` do its job, or create custom naming scheme using "link"
> files:
> 
> https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html
> https://systemd.io/PREDICTABLE_INTERFACE_NAMES/
> https://www.freedesktop.org/software/systemd/man/systemd.link.html

I advocated creating the .link files in my original message.  I even
gave examples.

I do *not* advocate "letting systemd-udevd do its job", because it's
absolutely unqualified for duty.  The names it chooses are *not*
predictable.  The OP knew this.  I can tell by their wording.

I do *not* advocate using "net.ifnames=0" *unless* the system is known
to have fewer than 2 ethernet interfaces *and* fewer than 2 wireless
interfaces.

Re: Permission Questions

[Greg Wooledge]

On Mon, Aug 30, 2021 at 09:29:14PM +, Andy Smith wrote:
> Hello,
> 
> On Mon, Aug 30, 2021 at 05:07:16PM -0400, Greg Wooledge wrote:
> > unicorn:~$ strace bash -c 'echo stuff >> /tmp/123'
> > [...]
> > openat(AT_FDCWD, "/tmp/123", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 EACCES 
> > (Permission denied)
> > 
> > As far as I can see, this is a kernel bug.  Unless I'm overlooking
> > something...?
> 
> I think it's the sysctl fs.protected_regular:
> 
> https://unix.stackexchange.com/a/503169

I think you're right.  The changed behavior doesn't happen in /srv (only
in /tmp), nor does it happen on a buster system.

According to 
and , the change
actually happened in... wait for it... systemd.

*sigh*

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[Christophe_VANHOUTTE]

Bonsoir,

Le 30/08/2021 à 22:58, Belaïd a écrit :
Optimus permet de switcher entre la carte peu puissante intégrée au 
processeur et la carte dédiée (NVIDIA ou AMD). Ça permet d'activer la 
carte dédiée quand tes applications demande plus de puissance 
graphique. Optimus permet donc également de réduire la consommation 
électrique de ton ordinateur et donc augmenter l'autonomie de ta 
batterie. Pourquoi utiliser la carte dédiée NVIDIA ou AMD - qui 
consomme beaucoup plus - sur des tâches ou la carte graphique intégrée 
au processeur - qui consomme beaucoup moins - suffit largement. Voilà 
la vocation première d'Optimus


Je comprends cela, il doit certainement y avoir un ''bonton'' pour 
activer ou désactiver la carte dédiée que l'on pourrait poser sur le 
menu ou bien cela est-il automatique à la detection de ce qui est lancé ?


Ou bien il faudrait redémarrer à chaque fois que l'onsouhaite changer de 
carte vidéo ?


Merci

Christophe




Le lun. 30 août 2021 à 22:23, Christophe_VANHOUTTE 
mailto:yodatempoa...@free.fr>> a écrit :


Bonsoir,
Le 30/08/2021 à 20:20, steve a écrit :

Salut,

Pour un peu plus de contexte, il faut s'intéresser à la technologie
Optimus utilisée dans ce genre de portable. Un bon début:

https://wiki.debian.org/NVIDIA%20Optimus


J'ai un Dell qui utilise cette même technologie et je dois avouer
que
c'est assez sport pour l'utiliser plus ou moins correctement.
Pour les
cartes Nvidia, j'utilise d'habitude le pilote propriétaire trouvé
sur
nvidia.com , mais j'ai été dans l'incapacité
de l'installer pour gérer
Optimus. La solution a été d'utiliser du 100% Debian. Sur ma
machine:


Je lis toutes ces informations avec grande curiosité, le fait
d’avoir un PC portable neuf avec du nouveau matos graphique

me permette de faire des recherches et de creuser, il faut être
curieux.

Optimus: Jamais entendu parler, peut-être parce que j’avais pas le
besoin de configurer une carte graphique "récente"

Si je comprends bien Optimus NVIDIA (pas Optimus Prime dans les 
transfoemrs lol) permet de switcher entre les GPU ?

Mais il resterait des problèmes (source en 2020) et cela devrait
s’améliorer dans le temps.

Je viens de lire une documentation sur Optimus, il est dit “qu’il
ne faut pas l’utiliser”

Pour reprendre , en installa,t XFCE, les paquets drivers NVIDIA
libre seront installés comme ci-dessous , donc ?


**


dpkg -l | grep nvidia
ii  bumblebee-nvidia 3.2.1-27    amd64   
NVIDIA Optimus support using the proprietary NVIDIA driver
ii  glx-alternative-nvidia 1.2.0  
amd64    allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64 460.91.03-1
amd64    NVIDIA binary EGL library
ii  libgl1-nvidia-glvnd-glx:amd64 460.91.03-1
amd64    NVIDIA binary OpenGL/GLX library (GLVND variant)
ii  libgles-nvidia1:amd64 460.91.03-1
amd64    NVIDIA binary OpenGL|ES 1.x library
ii  libgles-nvidia2:amd64 460.91.03-1
amd64    NVIDIA binary OpenGL|ES 2.x library
ii  libglx-nvidia0:amd64 460.91.03-1
amd64    NVIDIA binary GLX library
ii  libnvidia-cbl:amd64 460.91.03-1
amd64    NVIDIA binary Vulkan ray tracing (cbl) library
ii  libnvidia-cfg1:amd64 460.91.03-1
amd64    NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-compiler:amd64 460.91.03-1
amd64    NVIDIA runtime compiler library
ii  libnvidia-eglcore:amd64 460.91.03-1
amd64    NVIDIA binary EGL core libraries
ii  libnvidia-encode1:amd64 460.91.03-1
amd64    NVENC Video Encoding runtime library
ii  libnvidia-glcore:amd64 460.91.03-1
amd64    NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-glvkspirv:amd64 460.91.03-1
amd64    NVIDIA binary Vulkan Spir-V compiler library
ii  libnvidia-ml1:amd64 460.91.03-1
amd64    NVIDIA Management Library (NVML) runtime library
ii  libnvidia-ptxjitcompiler1:amd64
460.91.03-1 amd64    NVIDIA PTX JIT
Compiler library
ii  libnvidia-rtcore:amd64 460.91.03-1
amd64    NVIDIA binary Vulkan ray tracing (rtcore) library
ii  nvidia-alternative 460.91.03-1
amd64    allows the selection of NVIDIA as GLX provider
ii  nvidia-cuda-mps 460.91.03-1 amd64   
NVIDIA CUDA Multi Process Service (MPS)
ii  nvidia-driver 460.91.03-1 amd64   
NVIDIA metapackage
ii  nvidia-driver-bin 

Re: How to avoid systemd/udev unpredictable NIC names

[IL Ka]

>
> This gives unpredictable results if the system has more than one
> ethernet interface, or more than one wireless interface.
>
> It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
>

Isn't that what the topic starter asked about?:)

To make names predictable one can either leave everything as-is and let
`systemd-udev` do its job, or create custom naming scheme using "link"
files:

https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html
https://systemd.io/PREDICTABLE_INTERFACE_NAMES/
https://www.freedesktop.org/software/systemd/man/systemd.link.html

Re: Permission Questions

[Andy Smith]

Hello,

On Mon, Aug 30, 2021 at 05:07:16PM -0400, Greg Wooledge wrote:
> unicorn:~$ strace bash -c 'echo stuff >> /tmp/123'
> [...]
> openat(AT_FDCWD, "/tmp/123", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 EACCES 
> (Permission denied)
> 
> As far as I can see, this is a kernel bug.  Unless I'm overlooking
> something...?

I think it's the sysctl fs.protected_regular:

https://unix.stackexchange.com/a/503169

Cheers,
Andy

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

Re: How to avoid systemd/udev unpredictable NIC names

[Dan Ritter]

Dan Ritter wrote: 
> Steve Keller wrote: 
> > I plan to upgrade a server from Debian stretch to buster.  Having read
> > the release notes I wonder what's the best way to avoid the new scheme
> > of unpredictable network interface names.
> 
> In /etc/default/grub, assuming that you are booting with grub, 
> 
> GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"
> 
> The "quiet" is not necessary and is a different feature.

The success of this method on my 5-nic router may be related to
not using systemd.

Also, an update-grub will be necessary.

-dsr-

Re: How to avoid systemd/udev unpredictable NIC names

[IL Ka]

On Mon, Aug 30, 2021 at 11:36 PM Steve Keller  wrote:

> So I'm still confused what to do after the upgrade to buster to keep
> my network names.
>
>
>
in /etc/default/grub add
"net.ifnames=0"
to GRUB_CMDLINE_LINUX
and execute "update-grub"

This service:
https://www.freedesktop.org/software/systemd/man/systemd-udevd.service.html
is responsible for device creation and renaming

Here is a good overview:
https://opensource.com/article/20/2/linux-systemd-udevd



>
>
> [1] Unfortunately, much of the Linux community and many distributions
> try to get as far away from its Unix roots as possible, away from
> the good KISS principle,


I agree:) Old good times when devices were created by makedev without any
magic.

Try devuan: https://www.devuan.org/
It doesn't have systemd

Re: How to avoid systemd/udev unpredictable NIC names

[Greg Wooledge]

On Mon, Aug 30, 2021 at 04:41:55PM -0400, Dan Ritter wrote:
> Steve Keller wrote: 
> > I plan to upgrade a server from Debian stretch to buster.  Having read
> > the release notes I wonder what's the best way to avoid the new scheme
> > of unpredictable network interface names.
> 
> In /etc/default/grub, assuming that you are booting with grub, 
> 
> GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"
> 
> The "quiet" is not necessary and is a different feature.

This gives unpredictable results if the system has more than one
ethernet interface, or more than one wireless interface.

It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.

Re: Permission Questions

[Greg Wooledge]

On Mon, Aug 30, 2021 at 10:57:59PM +0200, Rainer Dorsch wrote:
> Hmm...your example works for me as well
> 
> rd@h370:~/tmp.nobackup$ sudo touch /tmp/123; sudo chgrp video /tmp/123; sudo 
> chmod 664 /tmp/123
> [sudo] Passwort für rd: 
> rd@h370:~/tmp.nobackup$ ls -l /tmp/123
> -rw-rw-r-- 1 root video 0 30. Aug 22:52 /tmp/123
> rd@h370:~/tmp.nobackup$ id
> uid=2809(rd) gid=2809(rd) Gruppen=2809(rd),4(adm),20(dialout),21(fax),
> 24(cdrom),25(floppy),27(sudo),30(dip),44(video),46(plugdev),100(users),
> 114(lpadmin),118(scanner),126(docker),127(vboxusers),130(i2psvc),
> 131(wireshark),141(libvirt),1000(sispmctl)
> rd@h370:~/tmp.nobackup$ echo stuff >> /tmp/123
> rd@h370:~/tmp.nobackup$ 
> 
> As soon as I do a chown to a non-root user on /tmp/123 it does not work for 
> me 
> anymore.
> 
> Is root somehow treated differently as other users?

unicorn:~$ ls -l /tmp/123
-rw-rw-r-- 1 daemon video 0 Aug 30 17:00 /tmp/123
unicorn:~$ echo stuff >> /tmp/123
bash: /tmp/123: Permission denied

That is interesting!

unicorn:~$ strace bash -c 'echo stuff >> /tmp/123'
[...]
openat(AT_FDCWD, "/tmp/123", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 EACCES 
(Permission denied)

As far as I can see, this is a kernel bug.  Unless I'm overlooking
something...?

For fun, I also tried it with the primary group:

unicorn:~$ id
uid=1000(greg) gid=1000(greg) 
groups=1000(greg),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev)
unicorn:~$ sudo chgrp 1000 /tmp/123
unicorn:~$ echo stuff >> /tmp/123
bash: /tmp/123: Permission denied
unicorn:~$ ls -l /tmp/123
-rw-rw-r-- 1 daemon greg 0 Aug 30 17:00 /tmp/123

So it's not just the secondary group that's causing it.

Re: How to avoid systemd/udev unpredictable NIC names

[Dan Ritter]

Steve Keller wrote: 
> I plan to upgrade a server from   Debian stretch to buster.  Having read
> the release notes I wonder what's the best way to avoid the new scheme
> of unpredictable network interface names.

In /etc/default/grub, assuming that you are booting with grub, 

GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"

The "quiet" is not necessary and is a different feature.


-dsr-

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[Belaïd]

Optimus permet de switcher entre la carte peu puissante intégrée au
processeur et la carte dédiée (NVIDIA ou AMD). Ça permet d'activer la carte
dédiée quand tes applications demande plus de puissance graphique. Optimus
permet donc également de réduire la consommation électrique de ton
ordinateur et donc augmenter l'autonomie de ta batterie. Pourquoi utiliser
la carte dédiée NVIDIA ou AMD - qui consomme beaucoup plus - sur des tâches
ou la carte graphique intégrée au processeur - qui consomme beaucoup moins
- suffit largement. Voilà la vocation première d'Optimus

Le lun. 30 août 2021 à 22:23, Christophe_VANHOUTTE 
a écrit :

> Bonsoir,
> Le 30/08/2021 à 20:20, steve a écrit :
>
> Salut,
>
> Pour un peu plus de contexte, il faut s'intéresser à la technologie
> Optimus utilisée dans ce genre de portable. Un bon début:
>
> https://wiki.debian.org/NVIDIA%20Optimus
>
> J'ai un Dell qui utilise cette même technologie et je dois avouer que
> c'est assez sport pour l'utiliser plus ou moins correctement. Pour les
> cartes Nvidia, j'utilise d'habitude le pilote propriétaire trouvé sur
> nvidia.com, mais j'ai été dans l'incapacité de l'installer pour gérer
> Optimus. La solution a été d'utiliser du 100% Debian. Sur ma machine:
>
> Je lis toutes ces informations avec grande curiosité, le fait d’avoir un
> PC portable neuf avec du nouveau matos graphique
>
> me permette de faire des recherches et de creuser, il faut être curieux.
>
> Optimus: Jamais entendu parler, peut-être parce que j’avais pas le besoin
> de configurer une carte graphique "récente"
>
> Si je comprends bien Optimus NVIDIA (pas Optimus Prime dans les
> transfoemrs lol) permet de switcher entre les GPU ?
>
> Mais il resterait des problèmes (source en 2020) et cela devrait
> s’améliorer dans le temps.
>
> Je viens de lire une documentation sur Optimus, il est dit “qu’il ne faut
> pas l’utiliser”
>
> Pour reprendre , en installa,t XFCE, les paquets drivers NVIDIA libre
> seront installés comme ci-dessous , donc ?
>
>
> dpkg -l | grep nvidia
> ii  bumblebee-nvidia
> 3.2.1-27amd64NVIDIA Optimus support using
> the proprietary NVIDIA driver
> ii  glx-alternative-nvidia
> 1.2.0   amd64allows the selection of NVIDIA
> as GLX provider
> ii  libegl-nvidia0:amd64
> 460.91.03-1 amd64NVIDIA binary EGL library
> ii  libgl1-nvidia-glvnd-glx:amd64
> 460.91.03-1 amd64NVIDIA binary OpenGL/GLX
> library (GLVND variant)
> ii  libgles-nvidia1:amd64
> 460.91.03-1 amd64NVIDIA binary OpenGL|ES 1.x
> library
> ii  libgles-nvidia2:amd64
> 460.91.03-1 amd64NVIDIA binary OpenGL|ES 2.x
> library
> ii  libglx-nvidia0:amd64
> 460.91.03-1 amd64NVIDIA binary GLX library
> ii  libnvidia-cbl:amd64
> 460.91.03-1 amd64NVIDIA binary Vulkan ray
> tracing (cbl) library
> ii  libnvidia-cfg1:amd64
> 460.91.03-1 amd64NVIDIA binary OpenGL/GLX
> configuration library
> ii  libnvidia-compiler:amd64
> 460.91.03-1 amd64NVIDIA runtime compiler
> library
> ii  libnvidia-eglcore:amd64
> 460.91.03-1 amd64NVIDIA binary EGL core
> libraries
> ii  libnvidia-encode1:amd64
> 460.91.03-1 amd64NVENC Video Encoding runtime
> library
> ii  libnvidia-glcore:amd64
> 460.91.03-1 amd64NVIDIA binary OpenGL/GLX core
> libraries
> ii  libnvidia-glvkspirv:amd64
> 460.91.03-1 amd64NVIDIA binary Vulkan Spir-V
> compiler library
> ii  libnvidia-ml1:amd64
> 460.91.03-1 amd64NVIDIA Management Library
> (NVML) runtime library
> ii  libnvidia-ptxjitcompiler1:amd64
> 460.91.03-1 amd64NVIDIA PTX JIT Compiler
> library
> ii  libnvidia-rtcore:amd64
> 460.91.03-1 amd64NVIDIA binary Vulkan ray
> tracing (rtcore) library
> ii  nvidia-alternative
> 460.91.03-1 amd64allows the selection of NVIDIA
> as GLX provider
> ii  nvidia-cuda-mps
> 460.91.03-1 amd64NVIDIA CUDA Multi Process
> Service (MPS)
> ii  nvidia-driver
> 460.91.03-1 amd64NVIDIA metapackage
> ii  nvidia-driver-bin
> 460.91.03-1 amd64NVIDIA driver support binaries
> ii  nvidia-driver-libs:amd64
> 460.91.03-1 amd64NVIDIA metapackage
> (OpenGL/GLX/EGL/GLES libraries)
> ii  nvidia-egl-common
> 460.91.03-1 amd64NVIDIA binary EGL driver -
> common files
> ii  nvidia-egl-icd:amd64
> 460.91.03-1 amd64NVIDIA EGL installable client
> driver (ICD)
> ii  nvidia-installer-cleanup
> 20151021+13 amd64cleanup after driver
> installation with the nvidia-installer
> ii  nvidia-kernel-common
> 

Re: How to avoid systemd/udev unpredictable NIC names

[Greg Wooledge]

On Mon, Aug 30, 2021 at 10:20:46PM +0200, Steve Keller wrote:
> I plan to upgrade a server from   Debian stretch to buster.  Having read
> the release notes I wonder what's the best way to avoid the new scheme
> of unpredictable network interface names.

You say "server", so I'm guessing it has more than one NIC.  That means
the old way (net.ifnames=0) is not viable.

Your best strategy is to create systemd.link(5) files, and give the NICs
the names you want them to have, based on their MAC addresses.

For example:

unicorn:~$ cat /etc/systemd/network/10-lan0.link 
[Match]
MACAddress=18:60:24:77:5c:ec

[Link]
Name=lan0
unicorn:~$ ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: lan0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
link/ether 18:60:24:77:5c:ec brd ff:ff:ff:ff:ff:ff

This is also viable on a single-NIC machine (like mine), but in that
case net.ifnames=0 would also suffice.

reportar bug: nemo de cinnamon

[Blackhold]

Hola,
Doncs rere la consulta que he "solventat" avui utilitzant un altre
entorn d'escriptori, m'agradaria poguer reportar el bug aquest que
m'he trobat.

Mentre investigava no he trobat cap error, ni els paquets de dades
semblaven erronis, simplement el comportament era que el llistat de
directoris era molt lent amb cinnamon. Utilitzar un altre entorn
d'escriptori ha sigut la forma de solventar el què inicialment volia,
solventar el problema, però canviar l'entorn d'escriptori sembla que
serà una mesura impopular entre els meus usuaris.

Em podrieu ajudar a reportar el bug? o si algú ho té per mà, podria
fer-ho per mi? recordo que ho vaig fer un cop però va ser tot un
cristo i al no fer-ho habitualment no vaig poguer aportar tota la
informació necessària per identificar-lo.

Reporto aquí en mode de correu electrònic a la llista per si alguna
ànima caritativa em pot donar un cop de mà amb aquest tema (també el
poguer-ho fer en català llengua per la qual m'expresso millor).

El problema és:
Amb una debian 11 acabada d'instal·lar amb entorn d'escriptori
cinnamon, al connectar la unitat de xarxa per webdav fa que el llistat
de directoris i obertura de fitxers sigui extremadament lent. Amb
debian 10 + cinnamon la navegació és correcta i totes les màquines amb
què ho he provat estàven a la mateixa xarxa (els debian 10 -4-
funcionava bé i amb els debian 11 -5- no).
Al servidor de nextcloud he provat de canviar nginx per apache i el
comportament era el mateix i la captura de paquets no mostrava cap
error.

El paquet afectat és nemo, el gestor de finestres que utilitza cinnamon.

De moment he solventat el problema utilitzant gnome com entorn
d'escriptori (he reinstal·lat la màquina).

Moltes gràcies

- Blackhold
http://blackhold.nusepas.com
@blackhold_
~> cal lluitar contra el fort per deixar de ser febles, i contra
nosaltres mateixos quan siguem forts (Xirinacs)
<°((( ><

How to avoid systemd/udev unpredictable NIC names

[Steve Keller]

I plan to upgrade a server from Debian stretch to buster.  Having read
the release notes I wonder what's the best way to avoid the new scheme
of unpredictable network interface names.

I don't care what PCI bus and what slot my NICs are attached to, I
don't want to learn and don't want to have to remember this hardware
configurationan and I don't want to type these cumbersome and error
prone names.  I simply have eth0 for the internal network and eth1 for
my external network to the DSL router.  That's easy and I want to keep
it that way.

The Debian wiki on this shows several ways involving kernel cmdline,
udev, and systemd.  I've read it, I've also read some of the sparse
and incomplete systemd documentation for almost an hour.  Still I
don't know when and what software component (kernel, udev, systemd)
decides the NIC names and whether and in which way these conflict each
other. [1]

Also, after reading the wiki it's still unclear to me, which of the
several ways will survive the next upgrade to bullseye.

The safest way seems to be what's called "Custom schemes" but this
section explicitly states the names eth0, etc. shouldn't be used.

So I'm still confused what to do after the upgrade to buster to keep
my network names.

Steve


[1] Unfortunately, much of the Linux community and many distributions
try to get as far away from its Unix roots as possible, away from
the good KISS principle, and instead repeat all the mistakes
Windows has made in making everything complex, automagic, obscure,
instable, and unpredictable.

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[Christophe_VANHOUTTE]

Bonsoir,
Le 30/08/2021 à 20:20, steve a écrit :

Salut,

Pour un peu plus de contexte, il faut s'intéresser à la technologie
Optimus utilisée dans ce genre de portable. Un bon début:

https://wiki.debian.org/NVIDIA%20Optimus

J'ai un Dell qui utilise cette même technologie et je dois avouer que
c'est assez sport pour l'utiliser plus ou moins correctement. Pour les
cartes Nvidia, j'utilise d'habitude le pilote propriétaire trouvé sur
nvidia.com, mais j'ai été dans l'incapacité de l'installer pour gérer
Optimus. La solution a été d'utiliser du 100% Debian. Sur ma machine:


Je lis toutes ces informations avec grande curiosité, le fait d’avoir un 
PC portable neuf avec du nouveau matos graphique


me permette de faire des recherches et de creuser, il faut être curieux.

Optimus: Jamais entendu parler, peut-être parce que j’avais pas le 
besoin de configurer une carte graphique "récente"


Si je comprends bien Optimus NVIDIA (pas Optimus Prime dans les 
transfoemrs lol) permet de switcher entre les GPU ?


Mais il resterait des problèmes (source en 2020) et cela devrait 
s’améliorer dans le temps.


Je viens de lire une documentation sur Optimus, il est dit “qu’il ne 
faut pas l’utiliser”


Pour reprendre , en installa,t XFCE, les paquets drivers NVIDIA libre 
seront installés comme ci-dessous , donc ?



**


dpkg -l | grep nvidia
ii  bumblebee-nvidia 3.2.1-27    amd64    
NVIDIA Optimus support using the proprietary NVIDIA driver
ii  glx-alternative-nvidia 1.2.0   
amd64    allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64 460.91.03-1 amd64    
NVIDIA binary EGL library
ii  libgl1-nvidia-glvnd-glx:amd64 460.91.03-1 
amd64    NVIDIA binary OpenGL/GLX library (GLVND variant)
ii  libgles-nvidia1:amd64 460.91.03-1 amd64    
NVIDIA binary OpenGL|ES 1.x library
ii  libgles-nvidia2:amd64 460.91.03-1 amd64    
NVIDIA binary OpenGL|ES 2.x library
ii  libglx-nvidia0:amd64 460.91.03-1 amd64    
NVIDIA binary GLX library
ii  libnvidia-cbl:amd64 460.91.03-1 amd64    
NVIDIA binary Vulkan ray tracing (cbl) library
ii  libnvidia-cfg1:amd64 460.91.03-1 amd64    
NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-compiler:amd64 460.91.03-1 
amd64    NVIDIA runtime compiler library
ii  libnvidia-eglcore:amd64 460.91.03-1 
amd64    NVIDIA binary EGL core libraries
ii  libnvidia-encode1:amd64 460.91.03-1 
amd64    NVENC Video Encoding runtime library
ii  libnvidia-glcore:amd64 460.91.03-1 
amd64    NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-glvkspirv:amd64 460.91.03-1 
amd64    NVIDIA binary Vulkan Spir-V compiler library
ii  libnvidia-ml1:amd64 460.91.03-1 amd64    
NVIDIA Management Library (NVML) runtime library
ii  libnvidia-ptxjitcompiler1:amd64 460.91.03-1 
amd64    NVIDIA PTX JIT Compiler library
ii  libnvidia-rtcore:amd64 460.91.03-1 
amd64    NVIDIA binary Vulkan ray tracing (rtcore) library
ii  nvidia-alternative 460.91.03-1 amd64    
allows the selection of NVIDIA as GLX provider
ii  nvidia-cuda-mps 460.91.03-1 amd64    
NVIDIA CUDA Multi Process Service (MPS)
ii  nvidia-driver 460.91.03-1 amd64    NVIDIA 
metapackage
ii  nvidia-driver-bin 460.91.03-1 amd64    
NVIDIA driver support binaries
ii  nvidia-driver-libs:amd64 460.91.03-1 
amd64    NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-egl-common 460.91.03-1 amd64    
NVIDIA binary EGL driver - common files
ii  nvidia-egl-icd:amd64 460.91.03-1 amd64    
NVIDIA EGL installable client driver (ICD)
ii  nvidia-installer-cleanup 20151021+13 
amd64    cleanup after driver installation with the nvidia-installer
ii  nvidia-kernel-common 20151021+13 amd64    
NVIDIA binary kernel module support files
ii  nvidia-kernel-dkms 460.91.03-1 amd64    
NVIDIA binary kernel module DKMS source
ii  nvidia-kernel-support 460.91.03-1 amd64    
NVIDIA binary kernel module support files
ii  nvidia-legacy-check 460.91.03-1 amd64    
check for NVIDIA GPUs requiring a legacy driver
ii  nvidia-libopencl1:amd64 460.91.03-1 
amd64    NVIDIA OpenCL ICD Loader library
ii  nvidia-modprobe 460.32.03-1 amd64    
utility to load NVIDIA kernel modules and create device nodes
ii  nvidia-opencl-common 460.91.03-1 amd64    
NVIDIA OpenCL driver - common files
ii  nvidia-opencl-icd:amd64 

Re: Permission Questions

[Greg Wooledge]

On Mon, Aug 30, 2021 at 09:01:33PM +0200, Rainer Dorsch wrote:
> rd@h370:~/tmp.nobackup$ ls -l /tmp/123
> -rw-rw-r-- 1 rd users 0 30. Aug 20:42 /tmp/123

> User ka overwrites it with the content of another file (atomically):
> 
> ka@h370:~$ echo test > 123
> ka@h370:~$ mv 123 /tmp/123
> mv: cannot move '123' to '/tmp/123': Operation not permitted

In order to perform this move, ka would first need to unlink the
existing /tmp/123 file.  ka cannot do that, because the /tmp directory
is "sticky".  Only "rd" (or root) can do it.

> Maybe moving removes a node in /tmp,

Yes.  You can verify with strace if you're curious enough.

> so I am trying to append to the file as a 
> test:
> 
> -rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123 

> ka@h370:~$ id 
> uid=1401(ka) gid=1401(ka) Gruppen=1401(ka),20(dialout),21(fax),24(cdrom),
> 30(dip),44(video),46(plugdev),100(users),1000(sispmctl) 
> ka@h370:~$ ls -l /tmp/123 
> -rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123 
> ka@h370:~$ echo test >> /tmp/123 
> -bash: /tmp/123: Permission denied 

That one should have worked, due to the secondary group membership.

unicorn:~$ sudo touch /tmp/123; sudo chgrp video /tmp/123; sudo chmod 664 
/tmp/123
[sudo] password for greg: 
unicorn:~$ ls -l /tmp/123
-rw-rw-r-- 1 root video 0 Aug 30 15:56 /tmp/123
unicorn:~$ id
uid=1000(greg) gid=1000(greg) 
groups=1000(greg),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev)
unicorn:~$ echo stuff >> /tmp/123
unicorn:~$ 

It works for me.  Is your /tmp a non-Unix file system, or is it mounted
with any unusual options?

Re: zoom client for bullseye

[Steven Rosenberg]

On Mon, 2021-08-30 at 08:15 +0800, Robbi Nespu wrote:
> Last time (that time bullseye still on testing release) I tried with 
> they official deb, I getting dependencies issues too.. trying with 
> "apt-get -f install" solve the installation but somehow when I using
> it, 
> it hang...and sometimes I can't close my camera properly.
> 
> Then I switched to snap version. It work fine until now so I just
> gonna 
> stick using snap version but honestly, I don't recommend you to use
> snap 
> package because of it disturbing for someone who really care about 
> bandwidth, permission to run and storage size. It will be the last 
> options for me.

I use the Flatpak for Zoom. It works fine, and since there's no .deb
repo, with the Flatpak I get updates. Since I very seldomly use Zoom,
it was always out of date when I did start it, so I'm happy to have the
Flatpak.

Re: ifupdown lost at upgrade time to bullseye

[Dan Ritter]

Harald Dunkel wrote: 
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the 
> (headless) system without network connection while the upgrade is not 
> completed yet, and breaking network on the next reboot?

This has not yet happened to me in nine or ten upgrades to
bullseye; all but two of them depended on
/etc/network/interfaces and nothing weird happened regarding
ifupdown.

-dsr-

Re: ifupdown lost at upgrade time to bullseye

[Brian]

On Mon 30 Aug 2021 at 21:37:50 +0200, Harald Dunkel wrote:

> Hi folks,
> how comes ifupdown is dropped at upgrade time to bullseye, leaving the
> (headless) system without network connection while the upgrade is not


That's a good question. Completely devoid of infirmation. But still a
good question :).

-- 
Brian.

Re: Permission Questions

[IL Ka]

>
>
> Is there something special with /tmp?
>

Do you have sticky bit on `/tmp`?

> For directories, when a directory's sticky bit is set, the filesystem
treats the files in such directories in a special way so only the file's
owner, the directory's owner, or root user can rename or delete the file.

https://en.wikipedia.org/wiki/Sticky_bit


>
> kan@h370:~$ ls -ld /tmp
> drwxrwxrwt 26 root root 32768 Aug 30 20:51 /tmp
> ka@h370:~$
>
>
AFAIK 't' means yes, you have it.

ifupdown lost at upgrade time to bullseye

[Harald Dunkel]

Hi folks,
how comes ifupdown is dropped at upgrade time to bullseye, leaving the 
(headless) system without network connection while the upgrade is not completed 
yet, and breaking network on the next reboot?
Regards
Harri

Re: Intel nuc 11 i5 kit 安裝debian後，首次開機就失敗，黑化面左上角遊標一直閃

[Andrei POPESCU]

On Du, 15 aug 21, 00:41:30, ellanios82 wrote:
> On 8/15/21 12:31 AM, Greg Wooledge wrote:
> > Press Ctrl-Alt-F2 to attempt to reach a text console.  If that's 
> > successful, then he can login there (as root) and attempt to install 
> > whatever's required to fix the problem
> 
> 
>  - that Text Console has letters too small for my poor eyesight :(
> 
>  - is there please, a complete command, as root. that will give large font??


Console font can be configured with

dpkg-reconfigure console-setup


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[Christophe_VANHOUTTE]

Bonsoir,
La réponse n'est pas parti, je repost
Le 30/08/2021 à 08:42, didier gaumet a écrit :


Avertissement: je n'ai jamais utilisé plusieurs moniteurs simultanément
et n'ai été confronté à des configurations multi-cartes graphiques que
pour eds besoins basiques.

Merci pour cette réponse, je vais répondre aux questions ci-dessous.


- utilisation simultanée de plusieurs cartes graphiques: la formulation
de ta question me fait me demander ce que tu veux vraiment faire.
  a) Si comme j'en ai vaguement l'impression, tu veux afficher la même
image ou deux portions complémentaires d'une même image sur deux
écrans, il doit probablement être possible de raccorder un écran en
HDMI->HDMI et un autre en USB-C->adaptateur displayport->HDMI et
Oui c’est bien cela un sur le HDMI voir 2 moniteurs si j’ai vraiment du 
HDMI 2.0 cela en mode étendu

Et un autre sur le USB-C->adaptateur Displayport
Idem en mode étendu , ce qui pourrait faire trois moniteurs minimul 
celui du PC portable et deux qutres un par connecteur, (mais je sais pas 
franchement si cela va fonctionner comme ça).

paramétrer ça dans les utilitaires de configuration d'XFCE. Tu n'as
besoin que d'une seule carte graphique en service dans ce cas.
  b) si tu veux utiliser deux cartes graphiques simultanément pour, par
exemple, afficher deux images totalement différentes (deux sessions
graphiques différentes pour Pierre et Paul, deux bureaux virtuels
différents pour Pierre...), est-ce possible ou pas, je dirais
probablement que oui mais en toute sincérité je n'en ai aucune idée et
encore moins sur le mode opératoire.
Bien cela serait bien d'utiliser les deux cartes graphiques, mais sur un 
PC portable j'ai jamais fait.

  c) si tu veux utiliser deux cartes graphiques pour profiter de la
puissance de calcul des GPU, je suppose que ça doit être possible mais
n'ai aucune idée non plus du mode opératoire
La machine est principalement utilisée pour la virtualisation Virtualbox 
vois peut-être VMWARE player.


- quels paquets installer?
  a) quand tu vas installer ton bureau XFCE, cela va entraîner
l'installation automatique du serveur graphique Xorg et de tous les
pilotes d'affichage Xorg *libres*, y compris ceux nécessaires à Nvidia
("nouveau") et AMD ("amdgpu"). Tu n'as besoin de rien d'autre pour un
fonctionnement standard de la carte graphique paramétrée comme active -
C'est une bonne nouvelle, en installant XFCE les pilotes graphiques sera 
automatiquement installé, c’est vraiment fort ça! (la résolution du 
moniteur aussi donc.).

j'imagine- dans ton UEFI. Après, tu auras peut-être besoin, suivant ce
que tu veux faire d'installer les pilotes graphiques propriétaires
Nvidia et/ou AMD et de paramétrer tout ça (tu peux regarder le wiki
Debian, sections Nvidia et Optimus, et le site AMD pour leurs pilotes
proprio)
https://wiki.debian.org/fr/FrontPage?action=show=PageD%27Accueil
https://www.amd.com/fr/support/kb/release-notes/rn-amdgpu-unified-linux-20-20

Je vais aller y faire un tour.
Avec le pilote propriétaire NVIDIA, que j’avais utilisé, (sur une tour) 
à chaque nouvelle modifications de mise à jour, il fallait réinstaller 
le driver.

Bon j’avais compris la chose, cela n’était pas long, mais embêtant.

  b) par contre, tu auras peut-être besoin de firmwares propriétaires et
installer Debian avec un support non-officiel contenant les firmwares
pourrait te faciliter la tâche
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/

Je comptais utiliser la version netinstall non-free, justement comme je 
le fais à chaque fois, pour mémoriser les paquets que je dois installer, 
j'ai aussi une autre machine à côté pour faire les manipulations.


Je devais attendre l'update 11.1, mais j'en peux plus du coup j'y vais 
sur cette version 11.


Merci pour ce retour très bien posé. Je vais avancer.

Christophe


--
Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 4.12
http://www.debian.org # http://fr.wikipedia.org/wiki/Obsolescence
https://soutien.laquadrature.net/
http://gnutux.free.fr # Il faut dire GNU/Linux :) # www.culte.org
--
GNU/Linux : May the Force be with you !

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

[Andrei POPESCU]

On Ma, 10 aug 21, 13:32:09, Jim Popovitch wrote:
> How can I determine what the "1 not upgraded" package might be?
> 
> 
> ~$ apt-get update 
> Hit:1 http://ftp.us.debian.org/debian bullseye InRelease
> Hit:2 http://security.debian.org bullseye-security InRelease
> Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease
> Reading package lists... Done
> 
> ~$ apt-get upgrade 
> Reading package lists... Done
> Building dependency tree... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> 
> 
> ~$ apt-get dist-upgrade 
> Reading package lists... Done
> Building dependency tree... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

A bit late to the party...

If pinning is the issue, the definitive place to check that is always 
the output of 'apt policy' (with no package)[1].


If that doesn't provide any new information you could ask deity ;)

https://lists.debian.org/deity/


[1] It's also a very good way to check your pinning actually works

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[Baptiste Chappe]

Bonjour,

Je confirme le KO avec deux cartes graphiques.
J’ai un XPS avec une 1650 mobile et un carte graphique externe 3070 via un
external GPU. Impossible d’utiliser la première carte en même temps que la
seconde.

Baptiste.

Le lun. 30 août 2021 à 19:55, Christophe_VANHOUTTE 
a écrit :

> Bonsoir,
> Le 30/08/2021 à 10:06, Belaïd a écrit :
>
> Bonjour,
>
> L'utilisation des deux cartes graphiques en même temps n'est pas possible.
> L'utilisation de l'une désactive l'autre. Généralement avec les pilotes
> "conventionnés", le passage de l'une à l'autre se fait de manière
> transparente selon le besoin en puissance graphique
>
> Mince alors, 
>
> Rien a faire donc ?
>
> Bien je ferai avec la carte NVIDIA Turing GeForce GTX 1660 Ti 6 Go GDDR6
>
> en reardant si je ne peux pas désactiver la carte intégrée.
>
> Je n'ai pas une utilisation nomade.
>
> Merci pour cette information importante, qui me fonds revoir mon
> paramètrage des moniteurs.
>
> Bien àvous 
>
> Christophe
>
>
>
>
> Le lun. 30 août 2021 à 00:29, Christophe_VANHOUTTE 
> a écrit :
>
>> Bonsoir,
>>
>> Je reviens sur Legion 5 17ARH05H (82GN004DFR) et l'installation de la
>> Debian 11 et gestion des deux cartes graphiques,
>>
>> J'utiliserai XFCE 4 (Il semble que XFCE 4 ne supporte pas encore
>> Wayland). (et peut-être MATE) ,
>>
>> A savoir:
>>
>> NVIDIA Turing GeForce GTX 1660 Ti 6 Go GDDR6 dédiés,
>> AMD Radeon Vega 7 intégrée au processeur et Optimus
>>
>> Sachant qu'il y aurait un USB-C 2.3 support DisplayPort) que je n'ai pas
>> encore testé, car Debian n'est pas encore installée.
>>
>> La connectique donnée est:
>>
>> Lecteur de carte mémoire4 en 1 (carte SD, MultiMediaCard, carte
>> SDHC, carte SDXC)
>> InterfacesUSB 3.2 Gen 1 (Always On)
>> 3 x USB 3.2 Gen 1
>> USB-C 3.2 Gen 1 (supports DisplayPort 1.2 Alt Mode)
>> HDMI 2.0
>> LAN
>> Prise combo casque/microphone
>>
>> Je me pose les questions suivantes:
>>
>> Peut-on utiliser les deux cartes graphique en mềme temps, sachant qu'il
>> y a un supports DisplayPort 1.2 ?
>>
>> Quel paquet graphique installé, avec accélération graphique ou pas sur
>> quelle carte vidéo ou les deux ?
>>
>> Voici donc pas mal de questions, je reste dans le flou complet, il faut
>> dire que j'ai pas l'habitude d'avoir du matériel très recent.
>>
>> Merci pour votre aide et éclirage.
>>
>>
>> Bien à vous.
>>
>> Christophe
>>
>> --
>> Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 4.12
>> http://www.debian.org  #http://fr.wikipedia.org/wiki/Obsolescence
>> https://soutien.laquadrature.net/
>> http://gnutux.free.fr  # Il faut dire GNU/Linux :) #www.culte.org
>> --
>> GNU/Linux : May the Force be with you !
>>
>>
> --
> Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 
> 4.12http://www.debian.org # 
> http://fr.wikipedia.org/wiki/Obsolescencehttps://soutien.laquadrature.net/http://gnutux.free.fr
>  # Il faut dire GNU/Linux :) # www.culte.org
>
> --
> GNU/Linux : May the Force be with you !
>
> --
Baptiste Chappe
06 61 28 71 10

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[steve]

Salut,

Pour un peu plus de contexte, il faut s'intéresser à la technologie
Optimus utilisée dans ce genre de portable. Un bon début:

https://wiki.debian.org/NVIDIA%20Optimus

J'ai un Dell qui utilise cette même technologie et je dois avouer que
c'est assez sport pour l'utiliser plus ou moins correctement. Pour les
cartes Nvidia, j'utilise d'habitude le pilote propriétaire trouvé sur
nvidia.com, mais j'ai été dans l'incapacité de l'installer pour gérer
Optimus. La solution a été d'utiliser du 100% Debian. Sur ma machine:

dpkg -l | grep nvidia
ii  bumblebee-nvidia  3.2.1-27  
  amd64NVIDIA Optimus support using the proprietary NVIDIA driver
ii  glx-alternative-nvidia1.2.0 
  amd64allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64  460.91.03-1   
  amd64NVIDIA binary EGL library
ii  libgl1-nvidia-glvnd-glx:amd64 460.91.03-1   
  amd64NVIDIA binary OpenGL/GLX library (GLVND variant)
ii  libgles-nvidia1:amd64 460.91.03-1   
  amd64NVIDIA binary OpenGL|ES 1.x library
ii  libgles-nvidia2:amd64 460.91.03-1   
  amd64NVIDIA binary OpenGL|ES 2.x library
ii  libglx-nvidia0:amd64  460.91.03-1   
  amd64NVIDIA binary GLX library
ii  libnvidia-cbl:amd64   460.91.03-1   
  amd64NVIDIA binary Vulkan ray tracing (cbl) library
ii  libnvidia-cfg1:amd64  460.91.03-1   
  amd64NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-compiler:amd64  460.91.03-1   
  amd64NVIDIA runtime compiler library
ii  libnvidia-eglcore:amd64   460.91.03-1   
  amd64NVIDIA binary EGL core libraries
ii  libnvidia-encode1:amd64   460.91.03-1   
  amd64NVENC Video Encoding runtime library
ii  libnvidia-glcore:amd64460.91.03-1   
  amd64NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-glvkspirv:amd64 460.91.03-1   
  amd64NVIDIA binary Vulkan Spir-V compiler library
ii  libnvidia-ml1:amd64   460.91.03-1   
  amd64NVIDIA Management Library (NVML) runtime library
ii  libnvidia-ptxjitcompiler1:amd64   460.91.03-1   
  amd64NVIDIA PTX JIT Compiler library
ii  libnvidia-rtcore:amd64460.91.03-1   
  amd64NVIDIA binary Vulkan ray tracing (rtcore) library
ii  nvidia-alternative460.91.03-1   
  amd64allows the selection of NVIDIA as GLX provider
ii  nvidia-cuda-mps   460.91.03-1   
  amd64NVIDIA CUDA Multi Process Service (MPS)
ii  nvidia-driver 460.91.03-1   
  amd64NVIDIA metapackage
ii  nvidia-driver-bin 460.91.03-1   
  amd64NVIDIA driver support binaries
ii  nvidia-driver-libs:amd64  460.91.03-1   
  amd64NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-egl-common 460.91.03-1   
  amd64NVIDIA binary EGL driver - common files
ii  nvidia-egl-icd:amd64  460.91.03-1   
  amd64NVIDIA EGL installable client driver (ICD)
ii  nvidia-installer-cleanup  20151021+13   
  amd64cleanup after driver installation with the nvidia-installer
ii  nvidia-kernel-common  20151021+13   
  amd64NVIDIA binary kernel module support files
ii  nvidia-kernel-dkms460.91.03-1   
  amd64NVIDIA binary kernel module DKMS source
ii  nvidia-kernel-support 460.91.03-1   
  amd64NVIDIA binary kernel module support files
ii  nvidia-legacy-check   460.91.03-1   
  amd64check for NVIDIA GPUs requiring a legacy driver
ii  nvidia-libopencl1:amd64   460.91.03-1   
  amd64NVIDIA OpenCL ICD Loader library
ii  nvidia-modprobe   460.32.03-1   
  amd64utility to load NVIDIA kernel modules and create device nodes
ii  nvidia-opencl-common  460.91.03-1   
  amd64NVIDIA OpenCL driver - common files
ii  nvidia-opencl-icd:amd64   

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[Christophe_VANHOUTTE]

Bonsoir,
Le 30/08/2021 à 10:06, Belaïd a écrit :

Bonjour,

L'utilisation des deux cartes graphiques en même temps n'est pas 
possible. L'utilisation de l'une désactive l'autre. Généralement avec 
les pilotes "conventionnés", le passage de l'une à l'autre se fait de 
manière transparente selon le besoin en puissance graphique


Mince alors, 

Rien a faire donc ?

Bien je ferai avec la carte NVIDIA Turing GeForce GTX 1660 Ti 6 Go GDDR6

en reardant si je ne peux pas désactiver la carte intégrée.

Je n'ai pas une utilisation nomade.

Merci pour cette information importante, qui me fonds revoir mon 
paramètrage des moniteurs.


Bien àvous 

Christophe





Le lun. 30 août 2021 à 00:29, Christophe_VANHOUTTE 
mailto:yodatempoa...@free.fr>> a écrit :


Bonsoir,

Je reviens sur Legion 5 17ARH05H (82GN004DFR) et l'installation de la
Debian 11 et gestion des deux cartes graphiques,

J'utiliserai XFCE 4 (Il semble que XFCE 4 ne supporte pas encore
Wayland). (et peut-être MATE) ,

A savoir:

NVIDIA Turing GeForce GTX 1660 Ti 6 Go GDDR6 dédiés,
AMD Radeon Vega 7 intégrée au processeur et Optimus

Sachant qu'il y aurait un USB-C 2.3 support DisplayPort) que je
n'ai pas
encore testé, car Debian n'est pas encore installée.

La connectique donnée est:

Lecteur de carte mémoire    4 en 1 (carte SD, MultiMediaCard, carte
SDHC, carte SDXC)
Interfaces    USB 3.2 Gen 1 (Always On)
3 x USB 3.2 Gen 1
USB-C 3.2 Gen 1 (supports DisplayPort 1.2 Alt Mode)
HDMI 2.0
LAN
Prise combo casque/microphone

Je me pose les questions suivantes:

Peut-on utiliser les deux cartes graphique en mềme temps, sachant
qu'il
y a un supports DisplayPort 1.2 ?

Quel paquet graphique installé, avec accélération graphique ou pas
sur
quelle carte vidéo ou les deux ?

Voici donc pas mal de questions, je reste dans le flou complet, il
faut
dire que j'ai pas l'habitude d'avoir du matériel très recent.

Merci pour votre aide et éclirage.


Bien à vous.

Christophe

--
Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 4.12
http://www.debian.org 
#http://fr.wikipedia.org/wiki/Obsolescence

https://soutien.laquadrature.net/ 
http://gnutux.free.fr  # Il faut dire
GNU/Linux :) #www.culte.org 
-- 
GNU/Linux : May the Force be with you !




--
Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 4.12
http://www.debian.org # http://fr.wikipedia.org/wiki/Obsolescence
https://soutien.laquadrature.net/
http://gnutux.free.fr # Il faut dire GNU/Linux :) # www.culte.org
--
GNU/Linux : May the Force be with you !

Re: zoom client for bullseye

[albcares]

I would suggest trying a different browser: Vivaldi.
It's a "fork" of chromium, with some interesting features.
I.e. it solved my troubles with teams in mint 17.3; maybe not a solution,
just a practical patch...

Il lun 30 ago 2021 02:33 Robbi Nespu  ha scritto:

> Last time (that time bullseye still on testing release) I tried with
> they official deb, I getting dependencies issues too.. trying with
> "apt-get -f install" solve the installation but somehow when I using it,
> it hang...and sometimes I can't close my camera properly.
>
> Then I switched to snap version. It work fine until now so I just gonna
> stick using snap version but honestly, I don't recommend you to use snap
> package because of it disturbing for someone who really care about
> bandwidth, permission to run and storage size. It will be the last
> options for me..
>
> Maybe you want to read my snap configuration adjustment[1]
>
> [1]
>
> https://robbinespu.gitlab.io/posts/control-your-snap-package/#how-to-control-and-configure-your-snap-stuff
>
> --
> Robbi Nespu 
> D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
> https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu
>
>

Re: Get Terminal to Echo line in buffer on backspace

[Greg Wooledge]

On Mon, Aug 30, 2021 at 05:05:49PM +0200, Nicolas George wrote:
> With Zsh, there is the "redisplay" zle command, it does exactly that:
> redraw the prompt and command without clearing the screen.
> 
> I do not know if readline, used by bash, has the same feature available.

Interesting.  I've never looked into this stuff before.

There is a "redraw-current-line" action in readline, but bash doesn't
bind any keys to it by default, neither in emacs nor vi mode.

But before I could even test that, I came across this section in the
man page:

   clear-screen (C-l)
  Clear the screen, then redraw the current line, leaving the cur‐
  rent  line  at the top of the screen.  With an argument, refresh
  the current line without clearing the screen.

That bit about "With an argument" is totally new information for me.
I'm a vi mode user, so I tried it as indicated: I typed some random
stuff, and then I pressed ESC 0 Ctrl-L.  It didn't work (it cleared the
whole screen).  So maybe an argument of 0 doesn't count... oh, right.
That's because 0 is a movement command ("jump to first column").  Next I
tried with a non-zero argument: ESC 1 Ctrl-L.  That worked.  It redrew
the current prompt and command line, without clearing the screen.

I also tested in emacs mode, but I'm not as proficient there.  Again,
ESC 1 Ctrl-L seems to work.  And so does Alt-1 Ctrl-L, in my terminal
(but Alt-1 may not work in all terminals, so be warned).

For extra fun: Alt-0 Ctrl-L also works in emacs mode.  Apparently emacs
can handle an argument of 0, because 0 isn't a movement command in
emacs the way it is in vi.

So, there's that.  And that will do what the OP wants, albeit not
"automatically" the way they seemed to want.  They actually have to
press the keys.

I'll let others play around with binding redraw-current-line to some
unused key combo.  I'm betting it does the same thing, once bound.

Re: Get Terminal to Echo line in buffer on backspace

[Nicolas George]

Greg Wooledge (12021-08-30):
> What you want to do is redraw the current command.  The easiest way to
> do this is to press Ctrl-L.  (Or if you're in vi mode, ESC Ctrl-L, and
> then you'll need to go back to command mode.)
> 
> This clears the whole screen, though.  So if there's information you
> need to preserve, take that into account.

With Zsh, there is the "redisplay" zle command, it does exactly that:
redraw the prompt and command without clearing the screen.

I do not know if readline, used by bash, has the same feature available.

As I said, without a line editor (dash for example), it is a feature of
the terminal, usually invoked with ^R.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Get Terminal to Echo line in buffer on backspace

[Nicolas George]

Thomas Anderson (12021-08-30):
> It's hard for me to describe, so here is an example of I am looking to
> emulate (this is from a mac).
> 
> https://cloud.little-beak.com/s/KxpjEHJ5RTEYZmS

Are you typing the ^R that appear on the screen?

What is the shell you are using? Does it have a line editor?

> On debian, I have tried many different terminal emulators, and all the
> visible options to get this type
> 
> of behavior, but have failed. =(

If you are using a shell with a line editor, the behavior comes from the
line editor, not from the terminal emulator. You really need to have a
clear idea of what you are doing.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Soft link confusion

[Gary L. Roach]

Thank you all for the help. Edwardo's mnemonic is a great help. So is 
the rest of the information. As to the BackupPC configuration change. 
While it is possible to redirect the backup in the config file, it is 
specifically not recommended. Not sure why.


Thanks again.

Gary R.

On 8/29/21 5:34 PM, David Christensen wrote:

On 8/29/21 4:59 PM, Gary L. Roach wrote:

Hi all,

I don't have occasion to use links very often and tend to get 
confused as to which direction the link is pointing. Specifically, I 
am trying to redirect backuppc files from the normal 
/var/lib/backuppc directory to another disk mounted at /media/Backup, 
a 1TB disk that is not being used. I wrote "ln -s /var/lib/backuppc  
/media/Backup". This produced "backuppc -> /var/lib/backuppc" on the 
1TB disk. The problem is that I now have duplicate files in both 
places. Specifically the cpool, log, pc, and pool directories appear 
on both drives. This is obviously not what I want. I need the pool 
files on the Backup disk and not on my system disk. What have I done 
wrong.


Sincerely appreciated any help.

Gary R



Rather than trying to symlink the backup repository directory out from 
underneath backuppc (which could lead to confusion and disaster in the 
future when you have forgotten about the symlink), can you change a 
backuppc configuration setting so that the backups are put where you 
want them?



David

Re: Canonical way to configure bonds for Bullseye

[Dan Ritter]

George Shuklin wrote: 
> Hello!
> 
> 
> We are building Debian bullsye images for our bare-metal servers, and there
> is a bit of ambiguity on 'canonical way to configure network bonds'.
> Wiki gives options with ifenslave and systemd-networkd, and there is an
> option to do it with post-up and ip route.
> ifenslave is broken due to #991930, but it can be easily patched.
> 
> 
> Which way is least surprise for a Debian user (for you)?
> 
> 1. bond-slaves in interfaces
> 
> Example:
> 
> auto bond0
> 
>   iface bond0
> 
>   inet static
> 
>   bond-slaves eth0 eth1

bond interfaces imply a nice static config, so the interfaces
file is definitely least surprising.

-dsr-

Re: Soft link confusion

[Tixy]

On Mon, 2021-08-30 at 10:18 -0300, Eduardo M KALINOWSKI wrote:
> On 29/08/2021 21:10, Greg Wooledge wrote:
> > The syntax is:  ln -s TARGET LINKNAME
> > 
> > I.e. you specify the existing thing first, and the name of the link that
> > you want to create last.
> 
> If you need a mnemonic, this is just like cp.
> 
> $ cp ORIGINAL NEW
> 
> creates NEW as a copy from ORIGINAL. Similarly,
> 
> $ ln -s ORIGINAL NEW
> 
> creates a link NEW pointing to ORIGINAL.
> 

Same order as for 'mount' command too.
I remember the argument order as WHAT WHERE

mount WHAT WHERE
cp WHAT WHERE
ln WHAT WHERE

-- 
Tixy

Re: Soft link confusion

[Eduardo M KALINOWSKI]

On 29/08/2021 21:10, Greg Wooledge wrote:

The syntax is:  ln -s TARGET LINKNAME

I.e. you specify the existing thing first, and the name of the link that
you want to create last.


If you need a mnemonic, this is just like cp.

$ cp ORIGINAL NEW

creates NEW as a copy from ORIGINAL. Similarly,

$ ln -s ORIGINAL NEW

creates a link NEW pointing to ORIGINAL.

--
"Be there.  Aloha."
-- Steve McGarret, _Hawaii Five-Oh_

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

Re: Get Terminal to Echo line in buffer on backspace

[Greg Wooledge]

> On 30/08/2021 14:41, Greg Wooledge wrote:
> > What you want to do is redraw the current command.  The easiest way to
> > do this is to press Ctrl-L.  (Or if you're in vi mode, ESC Ctrl-L, and
> > then you'll need to go back to command mode.)

(I mis-spoke slightly.  I meant "exit from command mode".  But this user
probably isn't in vi mode so it probably doesn't matter.)

On Mon, Aug 30, 2021 at 02:57:42PM +0200, Thomas Anderson wrote:
> It's hard for me to describe, so here is an example of I am looking to
> emulate (this is from a mac).
> 
> https://cloud.little-beak.com/s/KxpjEHJ5RTEYZmS
> 
> On debian, I have tried many different terminal emulators, and all the
> visible options to get this type
> 
> of behavior, but have failed. =(

What you're asking for sounds like "every time I backspace, I want
the shell to erase the current prompt and command and redraw them
from scratch, just in case there's some line noise on my terminal".
This is wasteful, and is not an available mode in bash.  I can't speak
for other shells.

You simply aren't going to get that behavior.  So I'm telling you how
you can work around the problem, or fix your *underlying problem*.

When "line noise" scribbles on your interactive shell prompt and makes
it too difficult to see what you're typing, you can either redraw the
screen (Ctrl-L), or power through, knowing what's there even if you
cannot see it, having faith in knowing what your fingers have done.
(For most of us, redrawing will be preferable.)

If the "line noise" is actually output from some job that *you* launched,
then you may wish to reconsider your work habits which are leading to
the undesired situation.  Run this background job in a different way,
which doesn't interfere with your ongoing work.

If you're getting *genuine* line noise (from an analog modem connection),
then you have my sympathy.  I haven't used an analog modem in many years.
But for modem use, there's a *really good reason* you don't redraw the
user's entire shell prompt & command on a frequent basis -- it's SLOW!
The amount of time it would take to redraw the prompt & command over a
slow (and noisy) analog modem line would be significant, and would annoy
you.  A lot.

Re: Get Terminal to Echo line in buffer on backspace

[Thomas Anderson]

It's hard for me to describe, so here is an example of I am looking to
emulate (this is from a mac).

https://cloud.little-beak.com/s/KxpjEHJ5RTEYZmS

On debian, I have tried many different terminal emulators, and all the
visible options to get this type

of behavior, but have failed. =(

On 30/08/2021 14:41, Greg Wooledge wrote:
> On Mon, Aug 30, 2021 at 12:26:32PM +0200, Thomas Anderson wrote:
>> My issue is: if I am typing to terminal, while receiving data, and I
>> backspace -- I just don't know how far I have backspaced, I have to guess.
> What you want to do is redraw the current command.  The easiest way to
> do this is to press Ctrl-L.  (Or if you're in vi mode, ESC Ctrl-L, and
> then you'll need to go back to command mode.)
>
> This clears the whole screen, though.  So if there's information you
> need to preserve, take that into account.
>
> Of course, another approach would be to stop doing whatever you're doing
> that causes you to "receive data" while you're typing in an interactive
> shell.  This might be a workflow issue of some kind.  Maybe you're
> running some sort of background job that spews noise.  Maybe you simply
> need to redirect that background job's output to a file.  Or maybe you
> want to run the noisy background job as a foreground job in a separate
> terminal (or a separate "tab", or a separate "virtual terminal" within
> screen or tmux, etc.).
>

Re: Get Terminal to Echo line in buffer on backspace

[Nicolas George]

Thomas Anderson (12021-08-30):
> I would really like to be able to use terminal in such a way that when I
> backspace, it will echo the line I am currently typing
> 
> 1. say if I am receiving data into the terminal window, and
> 
> 2. I have *not* pressed carriage return.
> 
> My issue is: if I am typing to terminal, while receiving data, and I
> backspace -- I just don't know how far I have backspaced, I have to guess.

If you are really talking about the terminal echo and line edition, then
the rprnt entry of the terminal line settings, as can be observed with
"stty -a", is what you are looking for. It is usually ^R.

I just checked:

$ { sleep 5; echo bar } & cat
[1] 263571
I type this before the 5 seconds.bar
[1]  + done   { sleep 5; echo bar; }
^R
I type this before the 5 seconds. And I can continue.

> I think years ago, someone helped me add a line to my user bash settings.

... but bash does not use the terminal line edition, it uses its own
line editor.

> If someone is familiar with how Mac's terminal emulator works, I would
> like it to be like that.

And I have no idea if Apple has done something non-standard here.
Knowing Apple, if they could break something standard, they did.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Get Terminal to Echo line in buffer on backspace

[Greg Wooledge]

On Mon, Aug 30, 2021 at 12:26:32PM +0200, Thomas Anderson wrote:
> My issue is: if I am typing to terminal, while receiving data, and I
> backspace -- I just don't know how far I have backspaced, I have to guess.

What you want to do is redraw the current command.  The easiest way to
do this is to press Ctrl-L.  (Or if you're in vi mode, ESC Ctrl-L, and
then you'll need to go back to command mode.)

This clears the whole screen, though.  So if there's information you
need to preserve, take that into account.

Of course, another approach would be to stop doing whatever you're doing
that causes you to "receive data" while you're typing in an interactive
shell.  This might be a workflow issue of some kind.  Maybe you're
running some sort of background job that spews noise.  Maybe you simply
need to redirect that background job's output to a file.  Or maybe you
want to run the noisy background job as a foreground job in a separate
terminal (or a separate "tab", or a separate "virtual terminal" within
screen or tmux, etc.).

Get Terminal to Echo line in buffer on backspace

[Thomas Anderson]

Hello Debian Users,


Maybe someone can help a brother out.


I would really like to be able to use terminal in such a way that when I
backspace, it will echo the line I am currently typing

1. say if I am receiving data into the terminal window, and

2. I have *not* pressed carriage return.

My issue is: if I am typing to terminal, while receiving data, and I
backspace -- I just don't know how far I have backspaced, I have to guess.

I think years ago, someone helped me add a line to my user bash settings.


If someone is familiar with how Mac's terminal emulator works, I would
like it to be like that.


Thanks to anyone that can help me out.

Neo

Re: Specifying dedicated partions during install - pros/cons?

[rhkramer]

On Sunday, August 29, 2021 10:30:53 AM Andy Smith wrote:
> In general it is best to have the simplest layout of filesystems
> possible that still matches your use case. Most of the time that
> will be a single partition for everything.

In general I agree.  I have had more complicated setups in the past, with more 
mount points.  The one thing I plan to continue to do is this:

I try to keep the system (and all its data) separate from what I consider my 
user data, that being files / stuff (like documents, noters, photos, videos, 
...) that I create or download from somewhere.

To do that, I fudge the system a little.

I let /home/ be created but I don't put the stuff I described above as my 
user data, I create a separate top level directory on a  separate partition, 
typically named /.

If I have to move all the data to another system, I can do things like move 
the entire hard disk (physically), or copy it, or ...

Re: Debian stable + backports + testing

[Andrew M.A. Cater]

On Sun, Aug 29, 2021 at 07:19:14AM -0700, Peter Ehlert wrote:
> 
> On 8/28/21 5:35 PM, Yoann LE BARS wrote:
> > Hello everybody out there!
> > 
> > On 2021/08/29 at 02:26 am, Roberto C. Sánchez wrote:
> > > That said, Dan's advice is quite solid: have your mixed environment in a
> > > VM, chroot, or other virtual environment.  When it gets into an unusable
> > > state (it very likely will at some point, especially as testing further
> > > diverges from stable), you can wipe it clean and start over.
> > So, here is the way I get it: use Debian stable + backports as the
> > system basis.
> Stability is really important for me.
> I am more conservative and I Don't use Backports*. Stable Only.
> 
> my experimenting is done on other machines or separate systems (multi-boot)
> 

Echoing this: if stability is important: use stable - currently Debian 11.
If everything works, fine.

Exceptionally: if your machine is too new for stable, then you might need
a backports kernel or similar.

If you want to do ANYTHING else: do it on a separate machine / in a VM.
That way - you have "vanilla" stable which is easily debugged.
You have stable+backports in a VM [unless you have the case where you
need backported kernel/firmware for basic booting] and you have anything 
else in a separate VM, maybe.

Don't make a FrankenDebian unless you absolutely must and you're sure
what you've done to get there and can undo changes.

All the very best, as ever,

Andy Cater

Re: debian 11 webdav lent

[Blackhold]

Hola,
Doncs de moment debian 11 + gnome sembla que funciona bé! he descobert
de passada gnome flashback que té aparença de gnome 2.0 (oh yeah!) i
s'assembla molt més a cinnamon i windows de tota la vida. És més lleig
però què hi farem tu!

Doncs de moment problema resolt! :) merci per al mètode de depuració
d'aneguet de goma!
https://es.wikipedia.org/wiki/M%C3%A9todo_de_depuraci%C3%B3n_del_patito_de_goma

[CLOSED]

- Blackhold
http://blackhold.nusepas.com
@blackhold_
~> cal lluitar contra el fort per deixar de ser febles, i contra
nosaltres mateixos quan siguem forts (Xirinacs)
<°((( ><

Missatge de Narcis Garcia  del dia dj., 26
d’ag. 2021 a les 20:43:
>
> El 26/8/21 a les 20:36, Blackhold ha escrit:
> > Missatge de Narcis Garcia  del dia dj., 26
> > d’ag. 2021 a les 18:21:
> >>
> >> Fins on jo sé, el client de NextCloud no munta cap unitat de xarxa sinó
> >> que sincronitza el contingut d'una carpeta local.
> >> Obrir la carpeta/directori i veure'n el contingut hauria d'anar igual de
> >> ràpid en una carpeta sincronitzada que qualsevol altra.
> >
> > Hola, no estic utilitzant el client de nextcloud, estic utilitzant el
> > sistema de finestres per muntar la unitat de xarxa dav. Al fer-ho així
> > hi tens accés i no es munta cap directori en local
> >
> >
>
> Aniria bé que especifiquessis què fas per a muntar la unitat de xarxa, i
> amb quin programari (incloent si has instal·lat alguna llibreria o
> extensió facilitadora). Tant a Debian 10 com a Debian 11.
>
> --
>
>
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this mail public archive. Public archive administrator
> should fix this against automated addresses collectors.
>

Canonical way to configure bonds for Bullseye

[George Shuklin]

Hello!


We are building Debian bullsye images for our bare-metal servers, and 
there is a bit of ambiguity on 'canonical way to configure network bonds'.
Wiki gives options with ifenslave and systemd-networkd, and there is an 
option to do it with post-up and ip route.

ifenslave is broken due to #991930, but it can be easily patched.


Which way is least surprise for a Debian user (for you)?

1. bond-slaves in interfaces

Example:

auto bond0

  iface bond0

  inet static

  bond-slaves eth0 eth1


2. systemd-networkd unit

.netdev in /etc/systemd/network.

3. Manual operations in interfaces:

post-up ip link add bond0 type bond
...

Which way is least surprise for you?

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[Belaïd]

Bonjour,

L'utilisation des deux cartes graphiques en même temps n'est pas possible.
L'utilisation de l'une désactive l'autre. Généralement avec les pilotes
"conventionnés", le passage de l'une à l'autre se fait de manière
transparente selon le besoin en puissance graphique

Le lun. 30 août 2021 à 00:29, Christophe_VANHOUTTE 
a écrit :

> Bonsoir,
>
> Je reviens sur Legion 5 17ARH05H (82GN004DFR) et l'installation de la
> Debian 11 et gestion des deux cartes graphiques,
>
> J'utiliserai XFCE 4 (Il semble que XFCE 4 ne supporte pas encore
> Wayland). (et peut-être MATE) ,
>
> A savoir:
>
> NVIDIA Turing GeForce GTX 1660 Ti 6 Go GDDR6 dédiés,
> AMD Radeon Vega 7 intégrée au processeur et Optimus
>
> Sachant qu'il y aurait un USB-C 2.3 support DisplayPort) que je n'ai pas
> encore testé, car Debian n'est pas encore installée.
>
> La connectique donnée est:
>
> Lecteur de carte mémoire4 en 1 (carte SD, MultiMediaCard, carte
> SDHC, carte SDXC)
> InterfacesUSB 3.2 Gen 1 (Always On)
> 3 x USB 3.2 Gen 1
> USB-C 3.2 Gen 1 (supports DisplayPort 1.2 Alt Mode)
> HDMI 2.0
> LAN
> Prise combo casque/microphone
>
> Je me pose les questions suivantes:
>
> Peut-on utiliser les deux cartes graphique en mềme temps, sachant qu'il
> y a un supports DisplayPort 1.2 ?
>
> Quel paquet graphique installé, avec accélération graphique ou pas sur
> quelle carte vidéo ou les deux ?
>
> Voici donc pas mal de questions, je reste dans le flou complet, il faut
> dire que j'ai pas l'habitude d'avoir du matériel très recent.
>
> Merci pour votre aide et éclirage.
>
>
> Bien à vous.
>
> Christophe
>
> --
> Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 4.12
> http://www.debian.org  #http://fr.wikipedia.org/wiki/Obsolescence
> https://soutien.laquadrature.net/
> http://gnutux.free.fr  # Il faut dire GNU/Linux :) #www.culte.org
> --
> GNU/Linux : May the Force be with you !
>
>

Re: Instalar firmware Ath9k en Nvidia Jetson Nano

[Camaleón]

El 2021-08-29 a las 22:53 -0700, Raúl Parada Medina escribió:

> El viernes, 23 de julio de 2021 a las 12:40:03 UTC+2, Camaleón escribió:
> > El 2021-07-23 a las 02:49 -0700, Raúl Parada Medina escribió: 
> > 
> > > El viernes, 23 de julio de 2021 a las 8:30:03 UTC+2, Camaleón escribió:
> > (...)
> > > > > No sé como debo hacer la instalación, se supone que al conectar el 
> > > > > módulo WiFi, se carga automáticamente el driver. Sin embargo, yo no 
> > > > > sé como activar la tarjeta o comprobar que realmente está cargado el 
> > > > > driver/firmware adecuado. 

(...)

> > > Ya he probado todas las configuraciones posibles típicas de configuración 
> > > de la tarjeta wifi. No existe ningún log. Y cuando ejecuto "sudo nmcli 
> > > dev wifi list", aparece vacío. Y con "sudo nmcli" aparece wlan0: 
> > > disconnected. ¿Cómo puedo hacer para que se muestren redes wifi? ¿O 
> > > comprobar que el problema no es de driver/firmware.
> > La configuración del wifi no es sencilla, y dependerá de qué 
> > herramientas uses, además de si es gráfica o por línea de órdenes: 
> > 
> > https://wiki.debian.org/WiFi/HowToUse 
> > 
> > Empieza con la orden más sencilla «ip link show». 
> > 
> > En los portátiles, normalmente tienes un interruptor físico para 
> > apagar/encender el adaptador de red inalámbrica, pero en el jetson no 
> > creo que tengas ese botón. Tendrás que asegurare de que el adaptador 
> > esté activado (existe una herramienta por software que se llama rfkill, 
> > si mal no recuerdo, que hace las funciones del conmutador físico). 
> > 
> > En fin, vete probando cosas y revsia siempre el registro (dmesg, 
> > /var/log/messages...) porque toda la actividad del adaptador 
> > inalámbrico y los mensajes de autentificación (WPA2) se registran ahí. 
> 
> Haciendo ip link show, me aparece la interficie wlan0 como mode DORMANT y 
> cuando hago nmcli, aparece como desconectado. ¿Cómo puedo activar la 
> interficie?

¿Dónde (en qué sección) te aparece el DORMANT?
El adpatador se habrá puesto en modo de reposo o de ahorro de energía, 
que no tiene por qué ser problemático salvo que no te funcione, claro 
:-)

Con la orden «ip link set [nombre_tarjeta_wifi] mode default» cambias el modo a 
«predeterminado», pero no sé si con eso será suficiente.

Saludos,

-- 
Camaleón 

Re: Debian 11 et Lenovo Legion 5 17ARH05H (82GN004DFR)

[didier gaumet]

Avertissement: je n'ai jamais utilisé plusieurs moniteurs simultanément
et n'ai été confronté à des configurations multi-cartes graphiques que
pour eds besoins basiques.

- utilisation simultanée de plusieurs cartes graphiques: la formulation
de ta question me fait me demander ce que tu veux vraiment faire.
 a) Si comme j'en ai vaguement l'impression, tu veux afficher la même
image ou deux portions complémentaires d'une même image sur deux
écrans, il doit probablement être possible de raccorder un écran en
HDMI->HDMI et un autre en USB-C->adaptateur displayport->HDMI et
paramétrer ça dans les utilitaires de configuration d'XFCE. Tu n'as
besoin que d'une seule carte graphique en service dans ce cas.
 b) si tu veux utiliser deux cartes graphiques simultanément pour, par
exemple, afficher deux images totalement différentes (deux sessions
graphiques différentes pour Pierre et Paul, deux bureaux virtuels
différents pour Pierre...), est-ce possible ou pas, je dirais
probablement que oui mais en toute sincérité je n'en ai aucune idée et
encore moins sur le mode opératoire.
 c) si tu veux utiliser deux cartes graphiques pour profiter de la
puissance de calcul des GPU, je suppose que ça doit être possible mais
n'ai aucune idée non plus du mode opératoire

- quels paquets installer? 
 a) quand tu vas installer ton bureau XFCE, cela va entraîner
l'installation automatique du serveur graphique Xorg et de tous les
pilotes d'affichage Xorg *libres*, y compris ceux nécessaires à Nvidia
("nouveau") et AMD ("amdgpu"). Tu n'as besoin de rien d'autre pour un
fonctionnement standard de la carte graphique paramétrée comme active -
j'imagine- dans ton UEFI. Après, tu auras peut-être besoin, suivant ce
que tu veux faire d'installer les pilotes graphiques propriétaires
Nvidia et/ou AMD et de paramétrer tout ça (tu peux regarder le wiki
Debian, sections Nvidia et Optimus, et le site AMD pour leurs pilotes
proprio)
https://wiki.debian.org/fr/FrontPage?action=show=PageD%27Accueil
https://www.amd.com/fr/support/kb/release-notes/rn-amdgpu-unified-linux-20-20
 b) par contre, tu auras peut-être besoin de firmwares propriétaires et
installer Debian avec un support non-officiel contenant les firmwares
pourrait te faciliter la tâche
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/

Re: Instalar firmware Ath9k en Nvidia Jetson Nano

[Raúl Parada Medina]

El viernes, 23 de julio de 2021 a las 12:40:03 UTC+2, Camaleón escribió:
> El 2021-07-23 a las 02:49 -0700, Raúl Parada Medina escribió: 
> 
> > El viernes, 23 de julio de 2021 a las 8:30:03 UTC+2, Camaleón escribió:
> (...)
> > > > No sé como debo hacer la instalación, se supone que al conectar el 
> > > > módulo WiFi, se carga automáticamente el driver. Sin embargo, yo no sé 
> > > > como activar la tarjeta o comprobar que realmente está cargado el 
> > > > driver/firmware adecuado. 
> > > Lo primero es saber qué módulo tienes cargado. Ejecuta «lsmod» y busca 
> > > el de la tarjeta inalámbrica. 
> > > 
> > > Si se trata de una tarjeta integrada (interna) debes tener el 
> > > controlador ath9k que viene directamente con el kernel. 
> > > 
> > > Si es así, sigue con los pasos habituales para configurar la tarjeta, y 
> > > a su vez, revisa los registros, son muy útiles para detectar problemas 
> > > con el wifi (como root, ejecuta «tail -f /var/log/messages»).
> > Ejecutando lsmod | grep ath9k tengo la salida: 
> > ath9k 
> > ath9k_common -> ath9k 
> > ath9k_hw -> ath9k, ath9k_common 
> > ath -> ath9k_hw, ath9k, ath9k_common 
> > mac80211 -> ath9k 
> > cfg80211-> mac80211, ath9k, ath, ath9k_common
> Parece correcto.
> > Ya he probado todas las configuraciones posibles típicas de configuración 
> > de la tarjeta wifi. No existe ningún log. Y cuando ejecuto "sudo nmcli dev 
> > wifi list", aparece vacío. Y con "sudo nmcli" aparece wlan0: disconnected. 
> > ¿Cómo puedo hacer para que se muestren redes wifi? ¿O comprobar que el 
> > problema no es de driver/firmware.
> La configuración del wifi no es sencilla, y dependerá de qué 
> herramientas uses, además de si es gráfica o por línea de órdenes: 
> 
> https://wiki.debian.org/WiFi/HowToUse 
> 
> Empieza con la orden más sencilla «ip link show». 
> 
> En los portátiles, normalmente tienes un interruptor físico para 
> apagar/encender el adaptador de red inalámbrica, pero en el jetson no 
> creo que tengas ese botón. Tendrás que asegurare de que el adaptador 
> esté activado (existe una herramienta por software que se llama rfkill, 
> si mal no recuerdo, que hace las funciones del conmutador físico). 
> 
> En fin, vete probando cosas y revsia siempre el registro (dmesg, 
> /var/log/messages...) porque toda la actividad del adaptador 
> inalámbrico y los mensajes de autentificación (WPA2) se registran ahí. 
> 
> Saludos, 
> 
> -- 
> Camaleón
Hola,

Haciendo ip link show, me aparece la interficie wlan0 como mode DORMANT y 
cuando hago nmcli, aparece como desconectado. ¿Cómo puedo activar la interficie?

Raúl

Re: Ayuda!! Cómo cambiar fondo de pantalla para lightdm con slick-greeter.

[Camaleón]

El 2021-08-30 a las 00:47 -0500, Joe Ronald Flórez Rada escribió:

> El El lun, 30 de ago. de 2021 a la(s) 12:42 a. m., Camaleón <
> noela...@gmail.com> escribió:
> 
> > El 2021-08-29 a las 19:48 -0500, Joe Ronald Flórez Rada escribió:
> >
> > > Hola. Alguien sabe cómo cambiar background para lightdm con
> > slick-greeter.
> > >
> > > No pasó nada. Yo intenté cambiar lightdm con slick-greeter y reinicié.
> > > Sigue lo mismo. No funciona nada.
> >
> > Si lo que buscas es la forma de cambiar la imagen del fondo de la
> > pantalla de inicio de sesión con slick-greeter instalado, revisa este
> > informe de fallo donde te indican varias pistas para que funcione:
> >
> > Slick Greeter don't use the /etc/lightdm/slick-greeter.conf
> > https://github.com/linuxmint/slick-greeter/issues/80

> Tampoco. Lo mismo no pasó. Pero es Linux Mint, es diferente. Debian, no
> funciona. Veo la ruta /usr/share/lughtdm.conf.d/59-slick-greeter.conf

¿Qué pasos has seguido para configurar la imagen de fondo?

Saludos,

-- 
Camaleón