Re: [Sid] Nouveau: only one monitor after 6.6.15 to 6.7.9 upgrade

[Sven Joachim]

On 2024-04-03 21:39 +0200, Greg wrote:

> I have two HP Z30i connected to Nvidia GeForce GTX 670. After last
> upgrade I'm able to use only one monitor.
>
> When running linux-image-6.7.9:
>
> # dmesg | grep nouveau | cut -b 16-
> nouveau :01:00.0: vgaarb: deactivate vga console
> nouveau :01:00.0: NVIDIA GK104 (0e4090a2)
> nouveau :01:00.0: bios: version 80.04.19.00.0f
> nouveau :01:00.0: fb: 2048 MiB GDDR5
> nouveau :01:00.0: DRM: VRAM: 2048 MiB
> nouveau :01:00.0: DRM: GART: 1048576 MiB
> nouveau :01:00.0: DRM: TMDS table version 2.0
> nouveau :01:00.0: DRM: MM: using COPY for buffer copies
> snd_hda_intel :01:00.1: bound :01:00.0 (ops
> nv50_audio_component_bind_ops [nouveau])
> [drm] Initialized nouveau 1.4.0 20120801 for :01:00.0 on minor 0
> fbcon: nouveaudrmfb (fb0) is primary device
> nouveau :01:00.0: vgaarb: VGA decodes changed:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
> # xrandr
> Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 16384 x 16384
> DVI-I-1 connected 2560x1600+0+0 (normal left inverted right x axis y
> axis) 641mm x 400mm
>2560x1600 59.97*+
>1920x1200 59.95
>1920x1080 60.00
>1600x1200 60.00
>1680x1050 59.88
>1280x1024 60.02
>1440x900  59.90
>1280x800  59.91
>1280x720  60.00
>1024x768  60.00
>800x600   60.32
>640x480   59.94
>720x400   70.08
> DVI-D-1 disconnected (normal left inverted right x axis y axis)
> HDMI-1 disconnected (normal left inverted right x axis y axis)
> DP-1 disconnected (normal left inverted right x axis y axis)
>
> When running linux-image-6.6.15:
>
> # dmesg | grep nouveau | cut -b 16-
> nouveau :01:00.0: vgaarb: deactivate vga console
> nouveau :01:00.0: NVIDIA GK104 (0e4090a2)
> nouveau :01:00.0: bios: version 80.04.19.00.0f
> nouveau :01:00.0: fb: 2048 MiB GDDR5
> nouveau :01:00.0: DRM: VRAM: 2048 MiB
> nouveau :01:00.0: DRM: GART: 1048576 MiB
> nouveau :01:00.0: DRM: TMDS table version 2.0
> nouveau :01:00.0: DRM: DCB version 4.0
> nouveau :01:00.0: DRM: DCB outp 00: 01000f02 00020030
> nouveau :01:00.0: DRM: DCB outp 01: 02000f00 
> nouveau :01:00.0: DRM: DCB outp 02: 08011f82 00020030
> nouveau :01:00.0: DRM: DCB outp 03: 02022f62 00020010
> nouveau :01:00.0: DRM: DCB outp 04: 04833fb6 0f420010
> nouveau :01:00.0: DRM: DCB outp 05: 04033f72 00020010
> nouveau :01:00.0: DRM: DCB conn 00: 1030
> nouveau :01:00.0: DRM: DCB conn 01: 00020131
> nouveau :01:00.0: DRM: DCB conn 02: 00010261
> nouveau :01:00.0: DRM: DCB conn 03: 2346
> nouveau :01:00.0: DRM: MM: using COPY for buffer copies
> snd_hda_intel :01:00.1: bound :01:00.0 (ops
> nv50_audio_component_bind_ops [nouveau])
> [drm] Initialized nouveau 1.4.0 20120801 for :01:00.0 on minor 0
> nouveau :01:00.0: vgaarb: VGA decodes changed:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> fbcon: nouveaudrmfb (fb0) is primary device
> nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
> # xrandr
> Screen 0: minimum 320 x 200, current 5120 x 1600, maximum 16384 x 16384
> DVI-I-1 connected 2560x1600+2560+0 (normal left inverted right x axis
> y axis) 641mm x 400mm
>2560x1600 59.97*+
>1920x1200 59.95
>1920x1080 60.00
>1600x1200 60.00
>1680x1050 59.88
>1280x1024 60.02
>1440x900  59.90
>1280x800  59.91
>1280x720  60.00
>1024x768  60.00
>800x600   60.32
>640x480   59.94
>720x400   70.08
> DVI-D-1 connected 2560x1600+0+0 (normal left inverted right x axis y
> axis) 641mm x 400mm
>2560x1600 59.97*+
>1920x1200 59.95
>1920x1080 60.00
>1600x1200 60.00
>1680x1050 59.88
>1280x1024 60.02
>1440x900  59.90
>1280x800  59.91
>1280x720  60.00
>1024x768  60.00
>800x600   60.32
>640x480   59.94
>720x400   70.08
> HDMI-1 disconnected (normal left inverted right x axis y axis)
> DP-1 disconnected (normal left inverted right x axis y axis)
>
> Any suggestions?

File a bug against the kernel: reboot to the 6.7 kernel if it is not
currently running, install the reportbug package if it is not installed
already, then run

$ reportbug linux-image-$(uname -r)

Good luck,
Sven

Re: sid

[Richard Hector]

On 28/11/23 04:52, Michael Thompson wrote:

[lots of stuff]

Quick question - are you subscribed to the list? I notice you've replied 
a couple of times to your own emails, but not to any of the people 
who've offered suggestions. It's probably a good idea to subscribe, or 
at least check the archives:


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

Secondly, you say:

"I sent a big email a couple of days ago, which covered how you might 
work around that, but so far, it has not been fixed.

By my reckoning, it's been 6 days now."

Filing a bug may well be useful, but it should be done through the 
proper channels, not via a post on debian-user.


https://www.debian.org/Bugs/Reporting

Cheers,
Richard

Re: sid

[John Hasler]

Removing the Gnome desktop will not break anything.  There are several
"desktops" in Debian: Gnome is merely the default that you get when you
indicate that you want one but don't say which.  There is in fact no
requirement for a "desktop" at all.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: sid

[Michael Thompson]

Dear Debian,
Thanks for your patience.
I just went back to square one, deleted the netinstall ISO, deleted the 3
VMs I had, made a new one. I downloaded a fresh netinstall, made a new
VirtBox, and installed. One thing I did different, I checked the Mate
desktop box, but I didn't un-check the gnome box. I chose to use the
lightdm, but other than that, I have both gnome and Mate.
>From that point on, I did the edit to sources.list, dist upgrade, and that
worked without any evident problem.
Next, I started firefox and went to VBox, downloaded the latest version of
the Guest Additions. (Which is 458 as I write this.)
Did this ~
Install Virtualbox Guest Additions on Debian
Log into Debian (Guest OS) as root and update your software.
apt-get update && apt-get upgrade
Install required packages for building kernel modules.
apt-get install build-essential module-assistant
Prepare your system for building kernel module
m-a prepare
=
~ and reboot.

===
mike@debian
---
OS: Debian GNU/Linux trixie/sid x86_64
Host: VirtualBox 1.2
 Kernel: 6.5.0-4-amd64
 Uptime: 1 min
 Packages: 1823 (dpkg)
Shell: bash 5.2.21
 Resolution: 1920x951
DE: MATE 1.26.1
 WM: Metacity (Marco)
 Theme: Menta [GTK2/3]
 Icons: menta [GTK2/3]
 Terminal: mate-terminal
 Terminal Font: Monospace 15
 CPU: Intel i7-6700 (4) @ 3.408GHz
 GPU: 00:02.0 VMware SVGA II Adapter
 Memory: 693MiB / 7938MiB

After a week of struggle, we appear to be back exactly where Debian sid
should be, with the possible exception of the gnome desktop. Whether that
has any bearing on the matter or not, I don't know, but it did strike me
during the install, that perhaps I should leave it in, because gnome3 is
the default desktop, so the Debs would be developing for compatibility with
that first ~ Remove it, and that might break things 

I remain gratefully yours,

Mike

On Tue, Nov 28, 2023 at 1:52 AM Michael Thompson 
wrote:

> Dear Debian,
>
> Minor update, it works!!!
>
> I know I did one thing differently, which possibly influenced things, I
> don't know what you guys and the team did.
>
> First, check that the 2 remaining lines in sources.list ended with
> non-free-firmware, as in ~
> deb http://deb.debian.org/debian sid main contrib non-free-firmware
> deb-src http://deb.debian.org/debian sid main contrib non-free-firmware
>
>
> ~ when I ran the dist-upgrade command, I got a couple of places where it
> said something like 'Errors were encountered by dpkg in dealing with ~
>
> linux-image-6.5.0-4-amd64 ~and~ linux-image-amd64
>
> ~ so, before rebooting, I went
> sudo apt install  linux-image-6.5.0-4-amd64  linux-image-amd64
> ~ predictably, it said something along the lines of "Those are already the
> newest version. What's your problem?"
>
> I also ran sudo apt autoremove, which reclaimed a surprising amount of
> disk space... well over 200MB.
> Then I rebooted and now it works. Yipee!!
>
> I know something changed, because the previous dist-upgrade went chasing
> 1100 files. This attempt went after 1098. Two less files. Ergo, something
> changed ~ in addition to the non-free-*firmware*.
> Thank you Debian, congratulations on your excellent work.
>
> I remain yours gratefully,
>
> Mike
>
> On Mon, Nov 27, 2023 at 7:24 PM Michael Thompson 
> wrote:
>
>> Dear Debian,
>>
>> I just tried it again, and got the same result.
>> If you download the standard vanilla Debian netinstall ISO, create a
>> VBox, and install, it works fine. I just confirmed this by downloading a
>> fresh one. I know it's a new one because it includes the non-free-firmware
>> part in the sources.list, which is new. A netinstall ISO from last week
>> didn't mention firmware.
>>
>> 1st login, make user a member of sudo.
>> useradd mike sudo
>> Login as mike,
>> sudo pluma
>> as root, open & edit the /etc/apt/sources.list. Delete everything and add
>> 2 lines ~
>> deb http://deb.debian.org/debian sid main contrib non-free-firmware
>> deb-src http://deb.debian.org/debian sid main contrib non-free-firmware
>> Save and close.
>> Now, as root or as mike,
>> sudo apt update ; sudo apt dist upgrade
>> Standard method of upgrading from vanilla to sid.
>> Problem is, it breaks your networking.
>> It loses your nic and any reference to it, any settings, any ip address
>> ...
>> You cannot add something else because there is no network.
>> You cannot update or install anything. I sent a big email a couple of
>> days ago, which covered how you might work around that, but so far, it has
>> not been fixed.
>> By my reckoning, it's been 6 days now.
>> If my understanding is correct, then nobody anywhere can install a
>> vanilla Debian and upgrade to sid while this problem remains.
>> Yes, I am aware there are other install ISOs, there's about 80 of them.
>> I did find one that is a daily build of Trixie, and that has no problems,
>> although I didn't try to upgrade it to sid. I'm rather pleased to have a
>> working Trixie and I don't want to break it.
>> One (very long & tedious) 

Re: sid

[Michael Thompson]

Dear Debian,

Minor update, it works!!!

I know I did one thing differently, which possibly influenced things, I
don't know what you guys and the team did.

First, check that the 2 remaining lines in sources.list ended with
non-free-firmware, as in ~
deb http://deb.debian.org/debian sid main contrib non-free-firmware
deb-src http://deb.debian.org/debian sid main contrib non-free-firmware


~ when I ran the dist-upgrade command, I got a couple of places where it
said something like 'Errors were encountered by dpkg in dealing with ~

linux-image-6.5.0-4-amd64 ~and~ linux-image-amd64

~ so, before rebooting, I went
sudo apt install  linux-image-6.5.0-4-amd64  linux-image-amd64
~ predictably, it said something along the lines of "Those are already the
newest version. What's your problem?"

I also ran sudo apt autoremove, which reclaimed a surprising amount of disk
space... well over 200MB.
Then I rebooted and now it works. Yipee!!

I know something changed, because the previous dist-upgrade went chasing
1100 files. This attempt went after 1098. Two less files. Ergo, something
changed ~ in addition to the non-free-*firmware*.
Thank you Debian, congratulations on your excellent work.

I remain yours gratefully,

Mike

On Mon, Nov 27, 2023 at 7:24 PM Michael Thompson 
wrote:

> Dear Debian,
>
> I just tried it again, and got the same result.
> If you download the standard vanilla Debian netinstall ISO, create a VBox,
> and install, it works fine. I just confirmed this by downloading a fresh
> one. I know it's a new one because it includes the non-free-firmware part
> in the sources.list, which is new. A netinstall ISO from last week didn't
> mention firmware.
>
> 1st login, make user a member of sudo.
> useradd mike sudo
> Login as mike,
> sudo pluma
> as root, open & edit the /etc/apt/sources.list. Delete everything and add
> 2 lines ~
> deb http://deb.debian.org/debian sid main contrib non-free-firmware
> deb-src http://deb.debian.org/debian sid main contrib non-free-firmware
> Save and close.
> Now, as root or as mike,
> sudo apt update ; sudo apt dist upgrade
> Standard method of upgrading from vanilla to sid.
> Problem is, it breaks your networking.
> It loses your nic and any reference to it, any settings, any ip address ...
> You cannot add something else because there is no network.
> You cannot update or install anything. I sent a big email a couple of days
> ago, which covered how you might work around that, but so far, it has not
> been fixed.
> By my reckoning, it's been 6 days now.
> If my understanding is correct, then nobody anywhere can install a
> vanilla Debian and upgrade to sid while this problem remains.
> Yes, I am aware there are other install ISOs, there's about 80 of them.
> I did find one that is a daily build of Trixie, and that has no problems,
> although I didn't try to upgrade it to sid. I'm rather pleased to have a
> working Trixie and I don't want to break it.
> One (very long & tedious) way around this, I mentioned in my previous
> email. It does work, but you might as well create a new Linux from Scratch.
> It's a lot of messing about to achieve something that should be quite
> straightforward.
> There are something over a hundred sites and pages up, that give
> simple logical instructions about how you install Debian and upgrade to
> sid. Every one of those pages is currently wrong.
>
> Yours respectfully,
>
> Mike
>

Re: sid

[songbird]

Arno Lehmann, ITS wrote:
...
> Then, you have problems with Sid. Now, Sid is the unstable development 
> version of the distro. On the web page describing the different 
> releases, https://www.debian.org/releases/ the authors stated very 
> clearly that Sid might not work and even mentions disfunctional updates 
> as an example. They also state that users of Sid should subscribe to 
> debian-devel-announce. My conclusion is that problems with Sid should be 
> discussed with the developers community.

...

  on top of your comments also realise that sid and testing 
are going through usr-merge changes for some time and it will
continue and things may be in an in-between-state in places
between not working and working.

  i would also follow debian-devel, installer and tool-chain
lists if you are going to get into sid and testing to see 
what has been being talked about.


  songbird

Re: sid

[Arno Lehmann, ITS]

Hi Michael,

your problem report is a bit difficult to comment upon.

First, this is a debian users mailing list. I think nobody here will 
feel that they "are" Debian.


Then, you have problems with Sid. Now, Sid is the unstable development 
version of the distro. On the web page describing the different 
releases, https://www.debian.org/releases/ the authors stated very 
clearly that Sid might not work and even mentions disfunctional updates 
as an example. They also state that users of Sid should subscribe to 
debian-devel-announce. My conclusion is that problems with Sid should be 
discussed with the developers community.



And, considering that you tackled a development release, I think it 
would be useful if you provided details about the problem -- not just 
the result as in "network doesn't work anymore" but rather some 
observation of *why* -- which may be software packages that are 
essential for networking were uninstalled  during the upgrade, or 
provide binaries that do not work. Without such information it will be 
hard to work on fixes.



Also, you write

There are something over a hundred sites and pages up, that give 
simple logical instructions about how you install Debian and upgrade 
to sid. Every one of those pages is currently wrong.


but this is not something the audience of this mailing can take 
responsibility for.



If you address the right audience with your observations, the problem 
you found may be fixed. Here, it's unlikely you can get better results 
than pointers into other directions or just questions of "why Sid?".



Best,


Arno

Re: SID Xorg Erreur Segmentation

[Orion]

Bonjour,

J'ai finalement installé les driver nvidia, un simple :
apt-get install nvidia-driver a résolu le problème, le driver s'installe
très simplement.

Je suppose que mon problème est dans nouveau ou mesa, peut être
libglamoregl.so.
moralité ; si vous faites des bêtises avec Sid pensez à avoir une partition
avec une testing ou un ubuntu au cas ou! et zless et zmore c'est bien!
Merci de m'avoir proposé des solutions!

On Sun, Jan 8, 2023 at 8:51 PM Basile Starynkevitch <
bas...@starynkevitch.net> wrote:

>
> On 08/01/2023 19:49, Orion wrote:
>
> merci pour vos réponses!
> je pense que didier gaumet qui a la meilleure piste, ça peut venir de
> mesa,
> j'ai cherché sur apt-list-bug mais c'est pas concluant,
> apparemment apt ne garde pas mes réponses suite à ses mises en garde.
> lspci
> 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host
> Bridge/DRAM Registers (rev 07)
> 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe
> Controller (x16) (rev 07)
> 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD
> Graphics 630]
> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family
> USB 3.0 xHCI Controller
> 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME
> HECI #1
> 00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller
> [AHCI mode]
> 00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
> #17 (rev f0)
> 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
> #1 (rev f0)
> 00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
> #4 (rev f0)
> 00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
> #9 (rev f0)
> 00:1d.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
> #13 (rev f0)
> 00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
> 00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset
> Family Power Management Controller
> 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
> 00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus
> Controller
> 01:00.0 VGA compatible controller: *NVIDIA Corporation TU106 [GeForce RTX
> 2070 Rev. A]* (rev a1)
> 01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio
> Controller (rev a1)
> 01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller
> (rev a1)
> 01:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C UCSI
> Controller (rev a1)
> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
>
>
>
> Donc une carte  NVIDIA récente: je suggère alors soit d'utiliser Nouveau
> (pour les libristes convaincus) via
>
> aptitude install libdrm-nouveau2 nouveau-firmware
> xserver-xorg-video-nouveau
>
> soit d'accepter le compromis de télécharger puis d'installer un pilote
> NVIDIA propriétaire: https://www.nvidia.com/fr-fr/drivers/unix/ donc en
> janvier 2023
> https://www.nvidia.fr/content/DriverDownloads/confirmation.php?url=/XFree86/Linux-x86_64/525.78.01/NVIDIA-Linux-x86_64-525.78.01.run=fr=TITAN
>
> et il faudra bien sûr rebooter, et préalablement avoir installer le code
> source du noyau (nécessaire à Nvidia, si j'ai bonne mémoire) ou au moins
> les paquets linux-headers
>
> --
> Basile Starynkevitch   
> 
> (only mine opinions / les opinions sont miennes uniquement)
> 92340 Bourg-la-Reine, France
> web page: starynkevitch.net/Basile/
>
>

Re: SID Xorg Erreur Segmentation

[Basile Starynkevitch]

On 08/01/2023 19:49, Orion wrote:

merci pour vos réponses!
je pense que didier gaumet qui a la meilleure piste, ça peut venir de 
mesa,

j'ai cherché sur apt-list-bug mais c'est pas concluant,
apparemment apt ne garde pas mes réponses suite à ses mises en garde.
lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host 
Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe 
Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 
[UHD Graphics 630]
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset 
Family USB 3.0 xHCI Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH 
CSME HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA 
controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #17 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #1 (rev f0)
00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #4 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root 
Port #13 (rev f0)

00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset 
Family Power Management Controller

00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus 
Controller
01:00.0 VGA compatible controller: *NVIDIA Corporation TU106 [GeForce 
RTX 2070 Rev. A]* (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host 
Controller (rev a1)
01:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C 
UCSI Controller (rev a1)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)




Donc une carte  NVIDIA récente: je suggère alors soit d'utiliser Nouveau 
(pour les libristes convaincus) via


aptitude install libdrm-nouveau2 nouveau-firmware xserver-xorg-video-nouveau

soit d'accepter le compromis de télécharger puis d'installer un pilote 
NVIDIA propriétaire: https://www.nvidia.com/fr-fr/drivers/unix/ donc en 
janvier 2023 
https://www.nvidia.fr/content/DriverDownloads/confirmation.php?url=/XFree86/Linux-x86_64/525.78.01/NVIDIA-Linux-x86_64-525.78.01.run=fr=TITAN 



et il faudra bien sûr rebooter, et préalablement avoir installer le code 
source du noyau (nécessaire à Nvidia, si j'ai bonne mémoire) ou au moins 
les paquets linux-headers


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

Re: SID Xorg Erreur Segmentation

[Klaus Becker]

Am 08/01/2023 um 19:49 schrieb Orion:

merci pour vos réponses!




J'ai un peu de mal à m'en souvenir, mais il me semble avoir eu le même 
problème sous unstable il y a qq semaines, et la solution était de

revenir à une version antérieure de xorg.

Mais le problème a peut-être était résolu depuis, au moins sous 
unstable. Il me semble qu'il y avait un report de bug, ça doit se 
trouver facilement.


J'ai

~$ apt-cache policy xserver-xorg
xserver-xorg:
  Installé: 1:7.7+23
  Candidat: 1:7.7+23
  Versionstabelle:
 *** 1:7.7+23 500
500 http://ftp.halifax.rwth-aachen.de/debian unstable/main 
amd64 Packages

100 /var/lib/dpkg/status

bye
Klaus

Re: SID Xorg Erreur Segmentation

[Orion]

merci pour vos réponses!
je pense que didier gaumet qui a la meilleure piste, ça peut venir de mesa,
j'ai cherché sur apt-list-bug mais c'est pas concluant,
apparemment apt ne garde pas mes réponses suite à ses mises en garde.
mon xorg log :

X.Org X Server 1.21.1.6
X Protocol Version 11, Revision 0
[79.378] Current Operating System: Linux debian 6.0.0-6-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.0.12-1 (2022-12-09) x86_64
[79.378] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6-amd64
root=UUID=1083d7f2-5605-4c39-b74e-987011602c8e ro single
[79.380] xorg-server 2:21.1.6-1 (https://www.debian.org/support)
[79.381] Current version of pixman: 0.42.2
[79.384] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[79.384] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[79.389] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan  8
16:25:51 2023
[79.390] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[79.390] (==) No Layout section.  Using the first Screen section.
[79.390] (==) No screen section available. Using defaults.
[79.390] (**) |-->Screen "Default Screen Section" (0)
[79.390] (**) |   |-->Monitor ""
[79.390] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[79.390] (==) Automatically adding devices
[79.390] (==) Automatically enabling devices
[79.390] (==) Automatically adding GPU devices
[79.390] (==) Automatically binding GPU devices
[79.390] (==) Max clients allowed: 256, resource mask: 0x1f
[79.390] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[79.390] Entry deleted from font path.
[79.390] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[79.390] (==) ModulePath set to "/usr/lib/xorg/modules"
[79.390] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[79.390] (II) Loader magic: 0x556d58f82f00
[79.390] (II) Module ABI versions:
[79.390] X.Org ANSI C Emulation: 0.4
[79.390] X.Org Video Driver: 25.2
[79.390] X.Org XInput driver : 24.4
[79.390] X.Org Server Extension : 10.0
[79.390] (EE) dbus-core: error connecting to system bus:
org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket
/run/dbus/system_bus_socket: No such file or directory)
[79.390] (--) using VT number 2

[79.390] (II) systemd-logind: logind integration requires -keeptty and
-keeptty was not provided, disabling logind integration
[79.391] (II) xfree86: Adding drm device (/dev/dri/card0)
[79.391] (II) Platform probe for
/sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0
[79.392] (II) xfree86: Adding drm device (/dev/dri/card1)
[79.392] (II) Platform probe for
/sys/devices/pci:00/:00:02.0/drm/card1
[79.399] (--) PCI:*(0@0:2:0) 8086:3e92:1043:8694 rev 0, Mem @
0xf500/16777216, 0xd000/268435456, I/O @ 0xf000/64, BIOS @
0x/131072
[79.399] (--) PCI: (1@0:0:0) 10de:1f07:1043:866d rev 161, Mem @
0xf600/16777216, 0xe000/268435456, 0xf000/33554432, I/O @
0xe000/128, BIOS @ 0x/524288
[79.399] (II) LoadModule: "glx"
[79.399] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[79.400] (II) Module glx: vendor="X.Org Foundation"
[79.400] compiled for 1.21.1.6, module version = 1.0.0
[79.400] ABI class: X.Org Server Extension, version 10.0
[79.466] (==) Matched modesetting as autoconfigured driver 0
[79.466] (==) Matched fbdev as autoconfigured driver 1
[79.466] (==) Matched vesa as autoconfigured driver 2
[79.466] (==) Assigned the driver to the xf86ConfigLayout
[79.466] (II) LoadModule: "modesetting"
[79.466] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[79.466] (II) Module modesetting: vendor="X.Org Foundation"
[79.466]* compiled for 1.21.1.6, module version = 1.21.1*
[79.466] Module class: X.Org Video Driver
[79.466] *ABI class: X.Org Video Driver, version 25.2*
[79.466] (II) LoadModule: "fbdev"
[79.467] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[79.467] (II) Module fbdev: vendor="X.Org Foundation"
[79.467] compiled for 1.21.1.3, module version = 0.5.0
[79.467] Module class: X.Org Video Driver
[79.467] ABI class: X.Org Video Driver, version 25.2
[79.467] (II) LoadModule: "vesa"
[79.467] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[79.467] (II) Module vesa: vendor="X.Org Foundation"
[79.467] *compiled for 1.21.1.3, module version = 2.5.0*
[

Re: SID Xorg Erreur Segmentation

[didier gaumet]

Le 08/01/2023 à 11:47, Orion a écrit :

Bonjour,

Suite à une mise à jour autour du 31/12, Xorg ne démarre plus, je me 
souviens d'un message d'alerte d'apt list bug lors de la maj parlant 
d'un risque de segmentation error mais je me pensais sous Wayland et non 
concerné.


Quelqu'un a t il peut être vu le message et a un lien vers une solution?

Merci


- Solution? Je ne suis as sûr, à part attendre que le bug soit corrigé 
dans Sid ou réinstaller une version antérieure à condition de ne pas 
avoir purgé (tu peux aussi trouver des versions particulières des 
exécutables sur https://snapshot.debian.org/ )


- le dépistage peut probablement s'effectuer en cherchant (mots clé xorg 
et xserver) les paquets xorg installés sur ton système et en cherchant 
pour chacun d'eux les bugs sur le site https://www.debian.org/Bugs/ . Tu 
devrais pouvoir obtenir en local le même résultat par la commande 
apt-listbugs list paquet_à_vérifier.

Re: SID Xorg Erreur Segmentation

[Basile Starynkevitch]

On 08/01/2023 11:47, Orion wrote:

Bonjour,

Suite à une mise à jour autour du 31/12, Xorg ne démarre plus, je me 
souviens d'un message d'alerte d'apt list bug lors de la maj parlant 
d'un risque de segmentation error mais je me pensais sous Wayland et 
non concerné.


Quelqu'un a t il peut être vu le message et a un lien vers une solution?



Sans aucune garantie que ça marche (car Xorg comme Wayland dépend du 
matériel, c'est différent avec un contrôleur graphique NVIDIA et avec 
une carte graphique AMD) je vous invite à faire (sous root, en console - 
il faut peut être booter en mode rescue) les commandes suivantes et à en 
poster sur debian-user-french les effets.



mise à jour des paquets et installation de xfce4

aptitude update

aptitude upgrade

aptitude install xfce4-session

redemarrage

reboot

interrogation du matériel

lspci

lscpu

tentative de redemarrage du serveur Xorg

startx /usr/bin/xfce4-session

regarder avec less /var/log/Xorg.0.log les messages d'erreurs puis

grep -ni5 error /var/log/Xorg.0.log


Pour ma part, je vous souhaite une bonne année 2023 et cherche des 
partenaires intéressés par /RefPerSys/ en http://refpersys.org/



Bonne fin de weekend

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

Re: sid - no sound on speakers

[Jude DaShiell]

An audio screen reader user would have noticed this problem as soon as it
happened.  If others are on sid, and haven't got to the same upgrade
level, running speaker-test after each upgrade may narrow down the likely
culprits.



Jude  "There are four boxes to be used in
defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Sun, 13 Nov 2022, Tixy wrote:

> On Sat, 2022-11-12 at 19:01 +1000, David wrote:
> > What are you running?
> > Stable, Testing, Unstable?
>
> The subject line if prefixed with 'sid'. So Unstable I presume.
>
>

Re: sid - no sound on speakers

[Tixy]

On Sat, 2022-11-12 at 19:01 +1000, David wrote:
> What are you running?
> Stable, Testing, Unstable?

The subject line if prefixed with 'sid'. So Unstable I presume.

-- 
Tixy

Re: sid - no sound on speakers

[Amn]

Are you promoting violence?

On 2022-11-12 11:30 a.m., Jude DaShiell wrote:



Jude 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Sun, 13 Nov 2022, David wrote:



On Sat, Nov 12, 2022 at 13:42, Kamil Jo?ca  wrote:


David mailto:curmudg...@telaman.net.au>> writes:


On Sat, Nov 12, 2022 at 09:31, Kamil Jo?ca mailto:kjo...@o2.pl>> wrote:

  Recently I found strange thing: I have no sound on speakers. There is
no problem with usb headphone, or headphone via jack but speakers are
silent. As I almost exclusively use usb headphones I have no idea when this
problem started. In theory is possible that
  speakers are broken but the same thing on completely different
laptpop. I tried to play with: --8<---cut
here---start->8--- options snd-intel-dspcfg
dsp_driver= --8<---cut
here---end--->8---
  but without success. Any hints? During my searching I found

 but I am not sure if
this is related.

  What are you running?
  Stable, Testing, Unstable?

sid on both laptops

devices
on one laptop:
--8<---cut here---start->8---
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High
Definition Audio Controller (rev 01)
--8<---cut here---end--->8---

on second laptop:
--8<---cut here---start->8---
:00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP
Smart Sound Technology Audio Controller (rev 20)
--8<---cut here---end--->8---

I have exactly the opposite problem on an Acer laptop on SID.
No sound through headphones, but I do through speakers.
This since the last install.
The USB headphones can't even be found.
Cheers!

If memory serves, debian has an update-usb utility that can be used to
update information on usb devices.  I think it is a standard install so
everyone got it that installed debian.

Re: sid - no sound on speakers

[Jude DaShiell]

Jude 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Sun, 13 Nov 2022, David wrote:

>
>
> On Sat, Nov 12, 2022 at 13:42, Kamil Jo?ca  wrote:
> >
> >
> > David mailto:curmudg...@telaman.net.au>> writes:
> >
> >> On Sat, Nov 12, 2022 at 09:31, Kamil Jo?ca  >> > wrote:
> >>
> >>  Recently I found strange thing: I have no sound on speakers. There is
> >> no problem with usb headphone, or headphone via jack but speakers are
> >> silent. As I almost exclusively use usb headphones I have no idea when this
> >> problem started. In theory is possible that
> >>  speakers are broken but the same thing on completely different
> >> laptpop. I tried to play with: --8<---cut
> >> here---start->8--- options snd-intel-dspcfg
> >> dsp_driver= --8<---cut
> >> here---end--->8---
> >>  but without success. Any hints? During my searching I found
> >> 
> >>  but I am not sure if
> >> this is related.
> >>
> >>  What are you running?
> >>  Stable, Testing, Unstable?
> >
> > sid on both laptops
> >
> > devices
> > on one laptop:
> > --8<---cut here---start->8---
> > 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High
> > Definition Audio Controller (rev 01)
> > --8<---cut here---end--->8---
> >
> > on second laptop:
> > --8<---cut here---start->8---
> > :00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP
> > Smart Sound Technology Audio Controller (rev 20)
> > --8<---cut here---end--->8---
>
> I have exactly the opposite problem on an Acer laptop on SID.
> No sound through headphones, but I do through speakers.
> This since the last install.
> The USB headphones can't even be found.
> Cheers!
If memory serves, debian has an update-usb utility that can be used to
update information on usb devices.  I think it is a standard install so
everyone got it that installed debian.
>

Re: sid - no sound on speakers

[David]

On Sat, Nov 12, 2022 at 13:42, Kamil Jońca  wrote:



David mailto:curmudg...@telaman.net.au>> 
writes:


 On Sat, Nov 12, 2022 at 09:31, Kamil Jońca > wrote:


 Recently I found strange thing: I have no sound on speakers. 
There is no problem with usb headphone, or headphone via jack but 
speakers are silent. As I almost exclusively use usb headphones I 
have no idea when this problem started. In theory is possible that
 speakers are broken but the same thing on completely different 
laptpop. I tried to play with: --8<---cut 
here---start->8--- options snd-intel-dspcfg 
dsp_driver= --8<---cut 
here---end--->8---
 but without success. Any hints? During my searching I found 
 
 but I am not 
sure if this is related.


 What are you running?
 Stable, Testing, Unstable?


sid on both laptops

devices
on one laptop:
--8<---cut here---start->8---
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake 
PCH-P High Definition Audio Controller (rev 01)

--8<---cut here---end--->8---

on second laptop:
--8<---cut here---start->8---
:00:1f.3 Multimedia audio controller: Intel Corporation Tiger 
Lake-LP Smart Sound Technology Audio Controller (rev 20)

--8<---cut here---end--->8---


I have exactly the opposite problem on an Acer laptop on SID.
No sound through headphones, but I do through speakers.
This since the last install.
The USB headphones can't even be found.
Cheers!

Re: sid - no sound on speakers

[Kamil Jońca]

David  writes:

> On Sat, Nov 12, 2022 at 09:31, Kamil Jońca  wrote:
>
> Recently I found strange thing: I have no sound on speakers. There is no 
> problem with usb headphone, or headphone via jack but speakers are silent. As 
> I almost exclusively use usb headphones I have no idea when this problem 
> started. In theory is possible that
> speakers are broken but the same thing on completely different laptpop. I 
> tried to play with: --8<---cut 
> here---start->8--- options snd-intel-dspcfg 
> dsp_driver= --8<---cut here---end--->8---
> but without success. Any hints? During my searching I found 
> https://bbsarchlinux.org/viewtopic.php?id=275061 
> https://bugzilla.kernel.org/show_bug.cgi?id=216139 but I am not sure if this 
> is related.
>
> What are you running?
> Stable, Testing, Unstable?

sid on both laptops

devices
on one laptop:
--8<---cut here---start->8---
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High 
Definition Audio Controller (rev 01)
--8<---cut here---end--->8---

on second laptop:
--8<---cut here---start->8---
:00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart 
Sound Technology Audio Controller (rev 20)
--8<---cut here---end--->8---


KJ

-- 
http://wolnelektury.pl/wesprzyj/teraz/

Re: sid - no sound on speakers

[David]

On Sat, Nov 12, 2022 at 09:31, Kamil Jońca  wrote:


Recently I found strange thing: I have no sound on speakers. There is 
no

problem with usb headphone, or headphone via jack but speakers are
silent.
As I almost exclusively use usb headphones I have no idea when this
problem started.
In theory is possible that speakers are broken but the same thing on
completely different laptpop.
I tried to play with:

--8<---cut here---start->8---
options snd-intel-dspcfg dsp_driver=
--8<---cut here---end--->8---

but without success.
Any hints?
During my searching I found


but I am not sure if this is related.


What are you running?
Stable, Testing, Unstable?
Cheers!

Re: Sid installation fails - No kernel modules found

[Piscium]

On Sat, 16 Jul 2022 at 23:41, Brian  wrote:

> But you did not download and try the one I suggested? Therefore, you
> are working blindfolded. It is dated 2022-0 7-05. The archive modules
> may match the d-i kernel.

I successfully installed Sid using the Bullseye mini.iso that I
downloaded from the UK mirror. It has the same timestamp  as the file
you suggested from the Netherlands mirror.

I filed a bug report, hopefully someone will fix it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015172

Thanks for your help.

Re: Sid installation fails - No kernel modules found

[Brian]

On Sat 16 Jul 2022 at 20:56:51 +0100, Piscium wrote:

> On Sat, 16 Jul 2022 at 19:49, Brian  wrote:
> >
> > On Sat 16 Jul 2022 at 18:27:29 +0100, Piscium wrote:
> 
> > > [1] https://wiki.debian.org/DebianUnstable
> > > [2] deb.debian.org
> >
> > Is the mini.iso at
> >
> >   
> > http://ftp.nl.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/
> >
> > any use?
> 
> I downloaded the mini.iso in [3] as suggested in [1] (link above),

But you did not download and try the one I suggested? Therefore, you
are working blindfolded. It is dated 2022-0 7-05. The archive modules
may match the d-i kernel.

> which is supposed to be the one to install Sid. The one you ask about
> seems to be not for Sid. There is another method of installation which

You are misunderstanding; all mini.isos will install sid.

> is to start with the Testing iso and then upgrade to Sid. I have done
> that in the past successfully. Today is the first time I am trying
> this other method, the Sid mini.iso.
> 
> [3] 
> http://ftp.uk.debian.org/debian/dists/unstable/main/installer-amd64/current/images/netboot/mini.iso

[3] is dated 31-Jul-2021.

-- 
Brian.

Re: Sid installation fails - No kernel modules found

[Piscium]

On Sat, 16 Jul 2022 at 21:02, Piscium  wrote:

> I chose "Execute Shell", got a window with instructions that mentions
> /target, was dropped into BusyBox, and strangely enough there is no
> /target in the RAM disk. The other usual folders at the root are there
> (/bin, /dev, and so on).

On BusyBox I ran 'uname -a' and it told me I am running the debian-sid
kernel 5.10.0-8, built on 2021-07-28. This might be the reason for the
error message I got, "No kernel modules found". It is a very old
kernel. So perhaps the mini.iso was not built in a long while and got
out of date, or else the mirror is out of date. The mirror site says
the upload date is 31-Jul-2021 04:20. I looked at the German mirror
and it is the same date.

Any ideas? Anyway, this is not a big problem because there are two
other methods of installing sid, from the Stable iso and from the
Testing iso.

Re: Sid installation fails - No kernel modules found

[Piscium]

On Sat, 16 Jul 2022 at 19:26, Charles Curley
 wrote:

> Look in the installation logs for suspicious messages. During
> installation, they are at /target/var/log/installer/. After you reboot
> into the newly installed system, they are at /var/log/installer/.

I chose "Execute Shell", got a window with instructions that mentions
/target, was dropped into BusyBox, and strangely enough there is no
/target in the RAM disk. The other usual folders at the root are there
(/bin, /dev, and so on).

Any ideas?

Re: Sid installation fails - No kernel modules found

[Piscium]

On Sat, 16 Jul 2022 at 19:49, Brian  wrote:
>
> On Sat 16 Jul 2022 at 18:27:29 +0100, Piscium wrote:

> > [1] https://wiki.debian.org/DebianUnstable
> > [2] deb.debian.org
>
> Is the mini.iso at
>
>   
> http://ftp.nl.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/
>
> any use?

I downloaded the mini.iso in [3] as suggested in [1] (link above),
which is supposed to be the one to install Sid. The one you ask about
seems to be not for Sid. There is another method of installation which
is to start with the Testing iso and then upgrade to Sid. I have done
that in the past successfully. Today is the first time I am trying
this other method, the Sid mini.iso.

[3] 
http://ftp.uk.debian.org/debian/dists/unstable/main/installer-amd64/current/images/netboot/mini.iso

Re: Sid installation fails - No kernel modules found

[Brian]

On Sat 16 Jul 2022 at 18:27:29 +0100, Piscium wrote:

> Hiya,
> 
> I tried to install Sid (on a VirtualBox VM) following the instructions
> in [1], section "Use the Unstable "mini.iso" image.". I downloaded the
> specified ISO, did the sha256 check, proceeded with all the various
> options without any error, network configuration also succeeded, then
> at the step "Download installer components" I got the error "No kernel
> modules found". The mirror is the default and recommended [2].
> 
> Any ideas? Could it be that the specified ISO got somehow out of sync
> with what is available in the default mirror?
> 
> [1] https://wiki.debian.org/DebianUnstable
> [2] deb.debian.org

Is the mini.iso at

  
http://ftp.nl.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/

any use?

-- 
Brian.
> 

Re: Sid installation fails - No kernel modules found

[Charles Curley]

On Sat, 16 Jul 2022 18:27:29 +0100
Piscium  wrote:

> … network configuration also succeeded, then
> at the step "Download installer components" I got the error "No kernel
> modules found". The mirror is the default and recommended [2].
> 
> Any ideas? Could it be that the specified ISO got somehow out of sync
> with what is available in the default mirror?

Look in the installation logs for suspicious messages. During
installation, they are at /target/var/log/installer/. After you reboot
into the newly installed system, they are at /var/log/installer/.

-- 
Does anybody read signatures any more?

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

Re: [Sid] InfiniBand (please apply the following pach)

[Grzesiek]

On 2/20/22 01:14, Grzesiek wrote:

On 2/16/22 00:11, Grzesiek wrote:

Hi there,

I plan to use NFS over RDMA. I decided to buy two QLE7340 InfniBand 
controllers and DAC cable (no switch, two nodes only). Is QLE7340 
supported by Sid? Is required software included in Debian repositories?


It seems that the required software is present in Sid unfortunately 
there is a problem with kernels 5.15 and 5.16. When trying to load 
ib_qib you get:


[    4.481908] ib_qib :02:00.0: qib0: Reserving QPNs from 0x656b78 
to 0x656b78 for non-verbs use
[    4.482005] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.1/:02:00.0/infiniband/qib0/ports/1/

linkcontrol'
[    4.482008] CPU: 4 PID: 471 Comm: systemd-udevd Not tainted 
5.16.0-1-amd64 #1  Debian 5.16.7-2
[    4.482011] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Extreme4, BIOS P2.60 03/06/2018

[    4.482013] Call Trace:
[    4.482014]  
[    4.482016]  dump_stack_lvl+0x48/0x5e
[    4.482021]  sysfs_warn_dup.cold+0x17/0x24
[    4.482024]  internal_create_group+0x365/0x380
[    4.482027]  internal_create_groups.part.0+0x3d/0xa0
[    4.482029]  setup_port+0x370/0x680 [ib_core]
[    4.482044]  ? kobject_add+0x7e/0xb0
[    4.482048]  ib_setup_port_attrs+0x98/0x240 [ib_core]
[    4.482058]  ib_register_device+0x57f/0x660 [ib_core]
[    4.482067]  ? vmalloc_node+0x47/0x50
[    4.482071]  rvt_register_device+0x10c/0x270 [rdmavt]
[    4.482076]  qib_register_ib_device+0x608/0x7d0 [ib_qib]
[    4.482089]  qib_init_one+0x17f/0x470 [ib_qib]
[    4.482099]  local_pci_probe+0x45/0x80
[    4.482102]  ? pci_match_device+0xd7/0x130
[    4.482104]  pci_device_probe+0xd2/0x1c0
[    4.482106]  really_probe+0x1f5/0x3f0
[    4.482109]  __driver_probe_device+0xfe/0x180
[    4.482111]  driver_probe_device+0x1e/0x90
[    4.482113]  __driver_attach+0xc0/0x1c0
[    4.482115]  ? __device_attach_driver+0xe0/0xe0
[    4.482117]  ? __device_attach_driver+0xe0/0xe0
[    4.482119]  bus_for_each_dev+0x78/0xc0
[    4.482122]  bus_add_driver+0x149/0x1e0
[    4.482124]  driver_register+0x8f/0xe0
[    4.482126]  ? qib_init_qibfs+0x11/0x11 [ib_qib]
[    4.482135]  qib_ib_init+0x3e/0xf62 [ib_qib]
[    4.482144]  do_one_initcall+0x44/0x200
[    4.482147]  ? kmem_cache_alloc_trace+0x175/0x3d0
[    4.482150]  do_init_module+0x5c/0x280
[    4.482153]  __do_sys_finit_module+0xae/0x110
[    4.482156]  do_syscall_64+0x3b/0xc0
[    4.482159]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[    4.482162] RIP: 0033:0x7fe1bbc36f79
[    4.482164] Code: 48 8d 3d 9a a8 0d 00 0f 05 eb a5 66 0f 1f 44 00 00 
48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8
4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c7 5e 0d 00 
f7 d8 64 89 01 48
[    4.482167] RSP: 002b:7fff9e28e408 EFLAGS: 0246 ORIG_RAX: 
0139
[    4.482170] RAX: ffda RBX: 556a935aedb0 RCX: 
7fe1bbc36f79
[    4.482171] RDX:  RSI: 7fe1bbde6eed RDI: 
000f
[    4.482173] RBP: 0002 R08:  R09: 
556a93570540
[    4.482174] R10: 000f R11: 0246 R12: 
7fe1bbde6eed
[    4.482175] R13:  R14: 556a935af730 R15: 
556a935aedb0

[    4.482178]  
[    4.482195] infiniband qib0: Couldn't register device with driver model
[    4.482209] ib_qib :02:00.0: qib0: Failed to register driver with 
ib core.

[    4.482229] ib_qib :02:00.0: qib0: cannot register verbs: 17!
[    4.482762] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 49
[    4.482818] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 50
[    4.482841] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 51
[    4.482911] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 53
[    4.483485] ib_qib: probe of :02:00.0 failed with error -17

After installing linux-image-5.10.0-10-amd64 from Bullseye ib_qib loads 
without problem. Please fix.


The problem seems to be related to newer kernels.

btw: Is the openibd needed to acquire direct connect between two 
adapters? If so, how to install it on Sid?


This patch seems to fix the problem. Please apply.

https://lore.kernel.org/linux-rdma/1645106372-23004-1-git-send-email-mike.marcinis...@cornelisnetworks.com/T/#u

Re: [Sid] InfiniBand (please fix)

[Grzesiek]

On 2/16/22 00:11, Grzesiek wrote:

Hi there,

I plan to use NFS over RDMA. I decided to buy two QLE7340 InfniBand 
controllers and DAC cable (no switch, two nodes only). Is QLE7340 
supported by Sid? Is required software included in Debian repositories?


It seems that the required software is present in Sid unfortunately 
there is a problem with kernels 5.15 and 5.16. When trying to load 
ib_qib you get:


[4.481908] ib_qib :02:00.0: qib0: Reserving QPNs from 0x656b78 
to 0x656b78 for non-verbs use
[4.482005] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:01.1/:02:00.0/infiniband/qib0/ports/1/

linkcontrol'
[4.482008] CPU: 4 PID: 471 Comm: systemd-udevd Not tainted 
5.16.0-1-amd64 #1  Debian 5.16.7-2
[4.482011] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Extreme4, BIOS P2.60 03/06/2018

[4.482013] Call Trace:
[4.482014]  
[4.482016]  dump_stack_lvl+0x48/0x5e
[4.482021]  sysfs_warn_dup.cold+0x17/0x24
[4.482024]  internal_create_group+0x365/0x380
[4.482027]  internal_create_groups.part.0+0x3d/0xa0
[4.482029]  setup_port+0x370/0x680 [ib_core]
[4.482044]  ? kobject_add+0x7e/0xb0
[4.482048]  ib_setup_port_attrs+0x98/0x240 [ib_core]
[4.482058]  ib_register_device+0x57f/0x660 [ib_core]
[4.482067]  ? vmalloc_node+0x47/0x50
[4.482071]  rvt_register_device+0x10c/0x270 [rdmavt]
[4.482076]  qib_register_ib_device+0x608/0x7d0 [ib_qib]
[4.482089]  qib_init_one+0x17f/0x470 [ib_qib]
[4.482099]  local_pci_probe+0x45/0x80
[4.482102]  ? pci_match_device+0xd7/0x130
[4.482104]  pci_device_probe+0xd2/0x1c0
[4.482106]  really_probe+0x1f5/0x3f0
[4.482109]  __driver_probe_device+0xfe/0x180
[4.482111]  driver_probe_device+0x1e/0x90
[4.482113]  __driver_attach+0xc0/0x1c0
[4.482115]  ? __device_attach_driver+0xe0/0xe0
[4.482117]  ? __device_attach_driver+0xe0/0xe0
[4.482119]  bus_for_each_dev+0x78/0xc0
[4.482122]  bus_add_driver+0x149/0x1e0
[4.482124]  driver_register+0x8f/0xe0
[4.482126]  ? qib_init_qibfs+0x11/0x11 [ib_qib]
[4.482135]  qib_ib_init+0x3e/0xf62 [ib_qib]
[4.482144]  do_one_initcall+0x44/0x200
[4.482147]  ? kmem_cache_alloc_trace+0x175/0x3d0
[4.482150]  do_init_module+0x5c/0x280
[4.482153]  __do_sys_finit_module+0xae/0x110
[4.482156]  do_syscall_64+0x3b/0xc0
[4.482159]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[4.482162] RIP: 0033:0x7fe1bbc36f79
[4.482164] Code: 48 8d 3d 9a a8 0d 00 0f 05 eb a5 66 0f 1f 44 00 00 
48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8
4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c7 5e 0d 00 
f7 d8 64 89 01 48
[4.482167] RSP: 002b:7fff9e28e408 EFLAGS: 0246 ORIG_RAX: 
0139
[4.482170] RAX: ffda RBX: 556a935aedb0 RCX: 
7fe1bbc36f79
[4.482171] RDX:  RSI: 7fe1bbde6eed RDI: 
000f
[4.482173] RBP: 0002 R08:  R09: 
556a93570540
[4.482174] R10: 000f R11: 0246 R12: 
7fe1bbde6eed
[4.482175] R13:  R14: 556a935af730 R15: 
556a935aedb0

[4.482178]  
[4.482195] infiniband qib0: Couldn't register device with driver model
[4.482209] ib_qib :02:00.0: qib0: Failed to register driver with 
ib core.

[4.482229] ib_qib :02:00.0: qib0: cannot register verbs: 17!
[4.482762] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 49
[4.482818] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 50
[4.482841] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 51
[4.482911] ib_qib :02:00.0: Disabling notifier on HCA 0 irq 53
[4.483485] ib_qib: probe of :02:00.0 failed with error -17

After installing linux-image-5.10.0-10-amd64 from Bullseye ib_qib loads 
without problem. Please fix.


The problem seems to be related to newer kernels.

btw: Is the openibd needed to acquire direct connect between two 
adapters? If so, how to install it on Sid?


Thanks in advance for any help

Greg

Re: Sid : reboot looses boot partition and goes directly to bios

[David Wright]

On Tue 15 Feb 2022 at 10:37:52 (+0100), Sébastien Kalt wrote:
> 
> I'm experiencing something weird on my ASUS PN50 : I have a dual boot,
> windows and Sid.
> 
> CPU: 8-core AMD Ryzen 7 4700U with Radeon Graphics (-MCP-)
> speed/min/max: 2514/1400/2000 MHz Kernel: 5.15.0-3-amd64 x86_64 Up: 3h 1m
> Mem: 9300.6/15483.7 MiB (60.1%) Storage: 238.47 GiB (66.6% used) Procs: 386
> Shell: Bash inxi: 3.3.12
> 
> Some time ago (say one month), I noticed that if I reboot my Sid (with KDE
> menu or reboot from a console) the computer goes to the BIOS, loosing the
> partition start order.
> 
> If I choose my Debian partition first, everything returns to normal,
> booting to grub, letting me choosing between Debian and Windows.
> 
> If I stop the computer (shutdown -h now or with KDE menu) it boots
> normally to grub when powered on.
> 
> I don't really know when it starts, I rarely reboot my system, last time
> might be last november.
> 
> I don't really know where to look to find what might goes wrong during
> reboot.
> 
> Does anyone experienced this problem ?
> 
> Any clue as where to look to find what is dysfunctionning ?

It sounds as if you've accidentally set your system to boot with
an unsatisfactory default, but are using a one-shot scheme to
override it.

With BIOS systems, you can set up Grub to boot by default any
particular menu entry (rather than 0, the first). Your default
is written to /boot/grub/grubenv.

However, if before you close down you run grub-reboot, a
single-shot override value is written to grubenv, meaning that
when the system powers up, Grub will read grubenv and
automatically boot with the override, but will also clear
the override setting from grubenv.

EFI systems have a similar scheme that obviously runs before
Grub is given control. (The grubenv scheme can still operate
afterwards as well.)

$ efibootmgr 
BootCurrent: 
Timeout: 2 seconds
BootOrder: ,0006,0001,0002,0003,0004,0005
Boot* debian
Boot0001* Diskette Drive
Boot0002* ST500LX025-123456
Boot0003* USB Storage Device
Boot0004* CD/DVD/CD-RW Drive
Boot0005  Onboard NIC
Boot0006* UEFI: ST500LX025-123456
$ 

This gives the default order when, for example, you force closedown
and then boot up (ie preempting any configuration being set up).
Ctrl-Alt-Del usually does the same sort of thing. I imagine that
you have a bad default choice here, accidentally set up a while back.

When you close down in the manner you have hinted at,¹
I again imagine that something in the bowels of your KDE
is using the   efibootmgr --bootnext   facility to set up
a more pleasing choice, but /for one-time only/.

man 8 efibootmgr   has copious examples to help you.

¹ You wrote "If I choose my Debian partition first" but
  you don't say how you made that choice. We are also
  left to guess whether it's affecting what's reported in
  the previous paragraph ("if I reboot my Sid …")
  or the next one ("If I stop the computer …").

Cheers,
David.

Re: Sid : reboot looses boot partition and goes directly to bios

[Christian Britz]

Is this by any chance an UEFI system?

I think I remember from dual boot times, that Windows 10 played from
time to time with the EFI bootloaders and I experienced the same
symptoms like you. I think running grub-install inside Debian fixed it
for me.

The final solution for me was to get rid of the Windows partition and
use a VM and sometimes WINE. The only thing I am missing from the VM
(tried both qemu/kvm/libvirt and VirtualBox) is 3D and video
acceleration, but this is no big deal for me.

Regards,
Christian



On 2022-02-15 10:37 UTC+0100, Sébastien Kalt wrote:
> Hi,
> 
> I'm experiencing something weird on my ASUS PN50 : I have a dual boot,
> windows and Sid.
> 
> CPU: 8-core AMD Ryzen 7 4700U with Radeon Graphics (-MCP-)
> speed/min/max: 2514/1400/2000 MHz Kernel: 5.15.0-3-amd64 x86_64 Up: 3h 1m
> Mem: 9300.6/15483.7 MiB (60.1%) Storage: 238.47 GiB (66.6% used) Procs: 386
> Shell: Bash inxi: 3.3.12
> 
> Some time ago (say one month), I noticed that if I reboot my Sid (with
> KDE menu or reboot from a console) the computer goes to the BIOS,
> loosing the partition start order.
> 
> If I choose my Debian partition first, everything returns to normal,
> booting to grub, letting me choosing between Debian and Windows.
> 
> If I stop the computer (shutdown -h now or with KDE menu) it boots
> normally to grub when powered on.
> 
> I don't really know when it starts, I rarely reboot my system, last time
> might be last november.
> 
> I don't really know where to look to find what might goes wrong during
> reboot.
> 
> Does anyone experienced this problem ?
> 
> Any clue as where to look to find what is dysfunctionning ?
> 
> Regards,
> 
> Sébastien
> 

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

Re: Sid : reboot looses boot partition and goes directly to bios

[songbird]

Sébastien Kalt wrote:
...
> If I stop the computer (shutdown -h now or with KDE menu) it boots
> normally to grub when powered on.
>
> I don't really know when it starts, I rarely reboot my system, last time
> might be last november.
>
> I don't really know where to look to find what might goes wrong during
> reboot.
>
> Does anyone experienced this problem ?
>
> Any clue as where to look to find what is dysfunctionning ?

  for me there is a difference between how i shut down as to
what gets saved and how the desktop will come up next time i
boot.

  so my guess is that it will be the setting you have in the
desktop someplace (i'm not familiar with KDE any longer).

  if i shutdown from the command line MATE will not save the
layout of my windows (and that is fine with me), but i also
know that if i want my layout saved then i have to use the
MATE desktop menu shutdown or reboot commands to do it and 
then it will save everything.  i also have a backup copy of
the layout in case something happens to reset things (i've 
had that happen at times) so i can restore it.


  songbird

Re: SID: update-grub ---Warning: os-prober will not be executed to detect other bootable partitions.

[David Wright]

On Thu 09 Dec 2021 at 08:28:37 (-0800), Peter Ehlert wrote:
> the full error message at the end of update-grub:
> 
> Warning: os-prober will not be executed to detect other bootable partitions.
> Systems on them will not be added to the GRUB boot configuration.
> Check GRUB_DISABLE_OS_PROBER documentation entry.
> 
> Question: why would this desirable?
> it's totally new to me.

AIUI a potential security risk. I don't know whether there are
plans to mitigate whatever the risk is.

I imagine there may be someone crafting a paragraph for the
next Release Notes.

> Back story:
> I just upgraded a Bullseye install to Sid.
> this is a multi-boot machine, my daily driver is Bullseye.
> after reboot my GRUB had only one entry
> 
> I was able to get it back (thanks to Google)
> edit /etc/default/grub
> add GRUB_DISABLE_OS_PROBER=false
> 
> saved then ran grub-install /dev/sd(foo) && update-grub

Cheers,
David.

Re: [Sid] Firefox problem

[Grzesiek]

On 11/7/21 06:29, Michael Castellon wrote:
wget --no-check-certificate -O firefox.tar 
"https://download.mozilla.org/?product=firefox-latest=linux64 
"


On Fri, Nov 5, 2021 at 5:54 PM Grzesiek > wrote:


On 10/19/21 16:21, Grzesiek wrote:
 > On 10/18/21 5:35 PM, Celejar wrote:
 >> On Sun, 17 Oct 2021 10:55:45 +0200
 >> Grzesiek mailto:p...@sojka.co>> wrote:
 >>
 >>> Hi there,
 >>>
 >>> On some of machines I use, after opening of Firefox I get empty
browser
 >>> window (with menus, decorations etc) but nothing else is
displayed. Its
 >>> impossible to open menu, type address, etc. The only thing you
can do is
 >>> to close the window. After changing display configuration
(rotate to
 >>> portrait, adding external monitor..) it starts to work as
expected. You
 >>> do not even need to reopen. Moreover, it looks that Firefox was
running
 >>> ok all the time but nothing was displayed.
 >>> After recent updates on some machines I get the same problem using
 >>> firefox-esr.
 >>> The only error mesg I get is:
 >>> ###!!! [Parent][RunMessage] Error: Channel closing: too late to
 >>> send/recv, messages will be lost
 >>
 >> I don't know what that message means, but I frequently get a similar
 >> message from Firefox, despite the fact that the program is (mostly)
 >> functional.
 >>
 >> ###!!! [Child][RunMessage] Error: Channel closing: too late to
 >> send/recv, messages will be lost
 >
 > So the message is not related to the problem
 >

After some more tests I discovered that the problem occurs on all my
machines using integrated GPU and intel_drv.so driver (i5-2520M,
i5-2450M, i7-2600, i5-8250U). The workaround is to switch to
modesetting_drv.so or rotate to portrait. After that Firefox starts to
work as expected.

On builds based on discrete GPU (in my case Nvidia GTX) Firefox
works ok.


Upgrading Firefox to 94.0.1 solved the problem

Re: [Sid] Firefox problem

[Michael Castellon]

wget --no-check-certificate -O firefox.tar "
https://download.mozilla.org/?product=firefox-latest=linux64;

On Fri, Nov 5, 2021 at 5:54 PM Grzesiek  wrote:

> On 10/19/21 16:21, Grzesiek wrote:
> > On 10/18/21 5:35 PM, Celejar wrote:
> >> On Sun, 17 Oct 2021 10:55:45 +0200
> >> Grzesiek  wrote:
> >>
> >>> Hi there,
> >>>
> >>> On some of machines I use, after opening of Firefox I get empty browser
> >>> window (with menus, decorations etc) but nothing else is displayed. Its
> >>> impossible to open menu, type address, etc. The only thing you can do
> is
> >>> to close the window. After changing display configuration (rotate to
> >>> portrait, adding external monitor..) it starts to work as expected. You
> >>> do not even need to reopen. Moreover, it looks that Firefox was running
> >>> ok all the time but nothing was displayed.
> >>> After recent updates on some machines I get the same problem using
> >>> firefox-esr.
> >>> The only error mesg I get is:
> >>> ###!!! [Parent][RunMessage] Error: Channel closing: too late to
> >>> send/recv, messages will be lost
> >>
> >> I don't know what that message means, but I frequently get a similar
> >> message from Firefox, despite the fact that the program is (mostly)
> >> functional.
> >>
> >> ###!!! [Child][RunMessage] Error: Channel closing: too late to
> >> send/recv, messages will be lost
> >
> > So the message is not related to the problem
> >
>
> After some more tests I discovered that the problem occurs on all my
> machines using integrated GPU and intel_drv.so driver (i5-2520M,
> i5-2450M, i7-2600, i5-8250U). The workaround is to switch to
> modesetting_drv.so or rotate to portrait. After that Firefox starts to
> work as expected.
>
> On builds based on discrete GPU (in my case Nvidia GTX) Firefox works ok.
>
> Any ideas?
>
> Could you confirm?
>
> Regards
> Greg
>
>

Re: [Sid] Firefox problem

[Grzesiek]

On 10/19/21 16:21, Grzesiek wrote:

On 10/18/21 5:35 PM, Celejar wrote:

On Sun, 17 Oct 2021 10:55:45 +0200
Grzesiek  wrote:


Hi there,

On some of machines I use, after opening of Firefox I get empty browser
window (with menus, decorations etc) but nothing else is displayed. Its
impossible to open menu, type address, etc. The only thing you can do is
to close the window. After changing display configuration (rotate to
portrait, adding external monitor..) it starts to work as expected. You
do not even need to reopen. Moreover, it looks that Firefox was running
ok all the time but nothing was displayed.
After recent updates on some machines I get the same problem using
firefox-esr.
The only error mesg I get is:
###!!! [Parent][RunMessage] Error: Channel closing: too late to
send/recv, messages will be lost


I don't know what that message means, but I frequently get a similar
message from Firefox, despite the fact that the program is (mostly)
functional.

###!!! [Child][RunMessage] Error: Channel closing: too late to 
send/recv, messages will be lost


So the message is not related to the problem



After some more tests I discovered that the problem occurs on all my 
machines using integrated GPU and intel_drv.so driver (i5-2520M, 
i5-2450M, i7-2600, i5-8250U). The workaround is to switch to 
modesetting_drv.so or rotate to portrait. After that Firefox starts to 
work as expected.


On builds based on discrete GPU (in my case Nvidia GTX) Firefox works ok.

Any ideas?

Could you confirm?

Regards
Greg

Re: [Sid] Firefox problem

[Richard Hector]

On 17/10/21 9:55 pm, Grzesiek wrote:

Hi there,

On some of machines I use, after opening of Firefox I get empty browser 
window (with menus, decorations etc) but nothing else is displayed. Its 
impossible to open menu, type address, etc. The only thing you can do is 
to close the window. After changing display configuration (rotate to 
portrait, adding external monitor..) it starts to work as expected. You 
do not even need to reopen. Moreover, it looks that Firefox was running 
ok all the time but nothing was displayed.
After recent updates on some machines I get the same problem using 
firefox-esr.

The only error mesg I get is:
###!!! [Parent][RunMessage] Error: Channel closing: too late to 
send/recv, messages will be lost


Are you seeing that message in the shell that you started it from? If 
not, and if you're not running it in a shell, try that to see if there 
are more messages?


Cheers,
Richard

Re: [Sid] Firefox problem

[Grzesiek]

On 10/18/21 5:35 PM, Celejar wrote:

On Sun, 17 Oct 2021 10:55:45 +0200
Grzesiek  wrote:


Hi there,

On some of machines I use, after opening of Firefox I get empty browser
window (with menus, decorations etc) but nothing else is displayed. Its
impossible to open menu, type address, etc. The only thing you can do is
to close the window. After changing display configuration (rotate to
portrait, adding external monitor..) it starts to work as expected. You
do not even need to reopen. Moreover, it looks that Firefox was running
ok all the time but nothing was displayed.
After recent updates on some machines I get the same problem using
firefox-esr.
The only error mesg I get is:
###!!! [Parent][RunMessage] Error: Channel closing: too late to
send/recv, messages will be lost


I don't know what that message means, but I frequently get a similar
message from Firefox, despite the fact that the program is (mostly)
functional.

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, 
messages will be lost


So the message is not related to the problem

Re: [Sid] Firefox problem

[Grzesiek]

On 10/17/21 8:40 PM, harrywea...@tutanota.com wrote:



17 Oct 2021, 18:55 by p...@sojka.co:


Hi there,

On some of machines I use, after opening of Firefox I get empty browser window 
(with menus, decorations etc) but nothing else is displayed. Its impossible to 
open menu, type address, etc. The only thing you can do is to close the window. 
After changing display configuration (rotate to portrait, adding external 
monitor..) it starts to work as expected. You do not even need to reopen. 
Moreover, it looks that Firefox was running ok all the time but nothing was 
displayed.
After recent updates on some machines I get the same problem using firefox-esr.
The only error mesg I get is:
###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, 
messages will be lost


I'm running 91.2.0 esr on SID and I'm not seeing any of this.
I find it performs better on some sites than others, so use Falkon as well, but 
general performance is good without these symptoms.


Well, I have 7 machines running Sid and on 4 of it Firefox is running 
ok. Thus I'm perfectly aware that on some configuration there are no 
(significant) issues with Firefox.


Regards
Greg

Re: [Sid] Firefox problem

[Celejar]

On Sun, 17 Oct 2021 10:55:45 +0200
Grzesiek  wrote:

> Hi there,
> 
> On some of machines I use, after opening of Firefox I get empty browser 
> window (with menus, decorations etc) but nothing else is displayed. Its 
> impossible to open menu, type address, etc. The only thing you can do is 
> to close the window. After changing display configuration (rotate to 
> portrait, adding external monitor..) it starts to work as expected. You 
> do not even need to reopen. Moreover, it looks that Firefox was running 
> ok all the time but nothing was displayed.
> After recent updates on some machines I get the same problem using 
> firefox-esr.
> The only error mesg I get is:
> ###!!! [Parent][RunMessage] Error: Channel closing: too late to 
> send/recv, messages will be lost

I don't know what that message means, but I frequently get a similar
message from Firefox, despite the fact that the program is (mostly)
functional.

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, 
messages will be lost

Celejar

Re: [Sid] Firefox problem

[harryweaver]

17 Oct 2021, 18:55 by p...@sojka.co:

> Hi there,
>
> On some of machines I use, after opening of Firefox I get empty browser 
> window (with menus, decorations etc) but nothing else is displayed. Its 
> impossible to open menu, type address, etc. The only thing you can do is to 
> close the window. After changing display configuration (rotate to portrait, 
> adding external monitor..) it starts to work as expected. You do not even 
> need to reopen. Moreover, it looks that Firefox was running ok all the time 
> but nothing was displayed.
> After recent updates on some machines I get the same problem using 
> firefox-esr.
> The only error mesg I get is:
> ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, 
> messages will be lost
>
I'm running 91.2.0 esr on SID and I'm not seeing any of this.
I find it performs better on some sites than others, so use Falkon as well, but 
general performance is good without these symptoms.
HTHCheers!

Harry.

Re: Sid: Korean input

[황병희]

> #+BEGIN_SRC: emacs lisp
> (set-fontset-font "fontset-default"
> 'hangul "Noto Sans Mono CJK KR")
> (set-input-method "korean-hangul")
> (global-set-key (kbd "") 'toggle-input-method)
> #+END_SRC
>
> I am now input Korean with above 3 lines only under GNU Emacs.

The screenshot:
http://forum.ubuntu-kr.org/download/file.php?id=15593=e9de28599b6644a2b1d827f5c9ec0bff

Sincerely, Byung-Hee from South Korea

Re: Sid: Korean input

[황병희]

황병희  writes:

> Hellow!
>
> Grzesiek  writes:
>
>> Hi there,
>>
>> I was asked to install Korean input on XFCE4 environment. I have never
>> done this before and I do not speak Korean.
>>
>> First question is if it is possible to get Korean input using standard
>> US keyboard?
>>
>> I tried to follow this manual:
>> https://linuxreviews.org/HOWTO_get_Korean_input_on_Debian
>> Unfortunately, no luck. I added the following to .bashrc:
>> export GTK_IM_MODULE=ibus
>> export QT_IM_MODULE=ibus
>> export XMODIFIERS=@im=ibus
>> but ibus-setup still asks to add these variables. ibus-daemon is not
>> started automatically. So:
>>
>> Is there any more detailed how-to? It would be perfect to have
>> switchable English and Korean input.
>>
>> How to test? Remember I do not speak Korean and I have never used
>> Korean input.
>>
>
> Sorry man Greg. There is no general way. Because there are many linux
> distro and many input method program for Korean.
>
> To me, i am using Nabi under Ubuntu 18.04 LTS currently.
>
> Though, you would be wait for 30 days. Maybe i am willing to install
> Debian 11 *Bullseye* into my new hardware (AMD Ryzen notebook).


Ah for a while i am stick aroud chromebook. So now i did install debian
11 bullseye into chromebook via linux support for chrome os. That is
easy but Korean input is not easy. And i did setup Korean input
environment by ~/.emacs.

#+BEGIN_SRC: emacs lisp
(set-fontset-font "fontset-default"
  'hangul "Noto Sans Mono CJK KR")
(set-input-method "korean-hangul")
(global-set-key (kbd "") 'toggle-input-method)
#+END_SRC

I am now input Korean with above 3 lines only under GNU Emacs.


This is my distro information on Chrome OS:
soyeomul@penguin:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
soyeomul@penguin:~$

And debian 11 runs Wayland.

Thanks (감사합니다) ^^^

Sincerely, Byung-Hee from South Korea

Re: Sid: Korean input

[황병희]

didier gaumet  writes:

> Hello,
>
> Disclaimer: I have never done this for korean but I have done it for
> chinese (I am only able to type "sun" in chinese in order to verify it
> is functional)
>
> I would not bother with under-the-hood manipulations: install the task-
> korean and task-korean-desktop packages. this will take care of needed
> fonts, input methods and all. 
>
> This will not convert the user environment to korean but instead bring
> him the possibility to display and type korean inside his english
> environment.
>
> Then your user will be able by himself to click on an applet or a menu
> option (both are present, I think) to set up how he wants to input
> korean.
>
> Feel free to disagree but I would advise you against installing Sid
> rather than Bullseye for a user who is asking you to setup his korean
> environment, though: if he is not able to do this, how could he
> administer his computer? 

Thanks for good guidence! Also i need above your guide, thanks again!

Sincerely, Byung-Hee from South Korea

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

Re: Sid: Korean input

[didier gaumet]

Hello,

Disclaimer: I have never done this for korean but I have done it for
chinese (I am only able to type "sun" in chinese in order to verify it
is functional)

I would not bother with under-the-hood manipulations: install the task-
korean and task-korean-desktop packages. this will take care of needed
fonts, input methods and all. 

This will not convert the user environment to korean but instead bring
him the possibility to display and type korean inside his english
environment.

Then your user will be able by himself to click on an applet or a menu
option (both are present, I think) to set up how he wants to input
korean.

Feel free to disagree but I would advise you against installing Sid
rather than Bullseye for a user who is asking you to setup his korean
environment, though: if he is not able to do this, how could he
administer his computer? 

Re: Sid: Korean input

[황병희]

Hellow!

Grzesiek  writes:

> Hi there,
>
> I was asked to install Korean input on XFCE4 environment. I have never
> done this before and I do not speak Korean.
>
> First question is if it is possible to get Korean input using standard
> US keyboard?
>
> I tried to follow this manual:
> https://linuxreviews.org/HOWTO_get_Korean_input_on_Debian
> Unfortunately, no luck. I added the following to .bashrc:
> export GTK_IM_MODULE=ibus
> export QT_IM_MODULE=ibus
> export XMODIFIERS=@im=ibus
> but ibus-setup still asks to add these variables. ibus-daemon is not
> started automatically. So:
>
> Is there any more detailed how-to? It would be perfect to have
> switchable English and Korean input.
>
> How to test? Remember I do not speak Korean and I have never used
> Korean input.
>

Sorry man Greg. There is no general way. Because there are many linux
distro and many input method program for Korean.

To me, i am using Nabi under Ubuntu 18.04 LTS currently.

Though, you would be wait for 30 days. Maybe i am willing to install
Debian 11 *Bullseye* into my new hardware (AMD Ryzen notebook).

Sincerely, Byung-Hee from South Korea

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//

Re: [sid] efibootmgr not working on linux 5.10.x [solved]

[Steve McIntyre]

p...@sojka.co wrote:
>On 5/6/21 1:10 PM, Steve McIntyre wrote:
>> 
>> This line:
>> 
>> efivarfs   16384  0
>> 
>> suggests the cause of the problem for you. efibootmgr (and other tools
>> using libefivar) will look into both:
>> 
>>   * /sys/firmware/efi/vars (the old, deprecated interface that was
>> removed in 5.10)
>>   * /sys/firmware/efi/efivars (the new interface, provided by efivarfs)
>> 
>> As you have efivarfs loaded but with use-count of 0, that suggests
>> that you don't have the efivarfs pseudo-filesystem mounted. This
>> should normally be automatically mounted on system boot, along with
>> the other pseudo-filesystems like /sys and /proc.
>
>Thanks! Manually mounting solved the problem. Which service is 
>responsible for mounting /sys/firmware/efi/efivars?

AFAIK it's normally mounted automatically by systemd on EFI systems,
no service needed. It's considered a core part of the system these
days.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Re: [sid] efibootmgr not working on linux 5.10.x [solved]

[Grzesiek]

On 5/6/21 1:10 PM, Steve McIntyre wrote:

Hi!

p...@sojka.co wrote:

On 4/10/21 7:52 PM, Sven Joachim wrote:

On 2021-04-08 22:30 +0200, Grzesiek wrote:


The problem seems to be related to 5.10.x kernels & LGA1155 based systems.

1. On laptop based on i5-8250u efibootmgr works fine (all kernel versions)

2. On systems based on LGA1155 socket (i5-2500k, i7-3770):
- kernels 5.10.x: efibootmgr does not work,
directory /sys/firmware/efi/efivars is empty
- kernel 5.8.0-2: efibootmgr woks as expected

On 5.8.0-2 i get:

# lsmod | grep efi
efivarfs   16384  0
efi_pstore 16384  0
efivars20480  1 efi_pstore

There is no efivars.ko in 5.10.x. Maybe that is the problem?


The efivars module has indeed been removed from Debian's 5.10 kernels,
as it had been deprecated in favor of efivarfs for a while.

Which versions of efibootmgr and libefivar1 do you have installed?


The problem persists since several months. Now I have:

# apt-list | grep efi
efibootmgr/unstable,now 17-1 amd64 [installed]
libefiboot1/unstable,now 37-6 amd64 [installed,automatic]
libefivar1/unstable,now 37-6 amd64 [installed,automatic]


This line:

efivarfs   16384  0

suggests the cause of the problem for you. efibootmgr (and other tools
using libefivar) will look into both:

  * /sys/firmware/efi/vars (the old, deprecated interface that was
removed in 5.10)
  * /sys/firmware/efi/efivars (the new interface, provided by efivarfs)

As you have efivarfs loaded but with use-count of 0, that suggests
that you don't have the efivarfs pseudo-filesystem mounted. This
should normally be automatically mounted on system boot, along with
the other pseudo-filesystems like /sys and /proc.


Thanks! Manually mounting solved the problem. Which service is 
responsible for mounting /sys/firmware/efi/efivars?

Re: [sid] efibootmgr not working on linux 5.10.x & LGA1155

[Steve McIntyre]

Hi!

p...@sojka.co wrote:
>On 4/10/21 7:52 PM, Sven Joachim wrote:
>> On 2021-04-08 22:30 +0200, Grzesiek wrote:
>>>
>>> The problem seems to be related to 5.10.x kernels & LGA1155 based systems.
>>>
>>> 1. On laptop based on i5-8250u efibootmgr works fine (all kernel versions)
>>>
>>> 2. On systems based on LGA1155 socket (i5-2500k, i7-3770):
>>> - kernels 5.10.x: efibootmgr does not work,
>>> directory /sys/firmware/efi/efivars is empty
>>> - kernel 5.8.0-2: efibootmgr woks as expected
>>>
>>> On 5.8.0-2 i get:
>>>
>>> # lsmod | grep efi
>>> efivarfs   16384  0
>>> efi_pstore 16384  0
>>> efivars20480  1 efi_pstore
>>>
>>> There is no efivars.ko in 5.10.x. Maybe that is the problem?
>> 
>> The efivars module has indeed been removed from Debian's 5.10 kernels,
>> as it had been deprecated in favor of efivarfs for a while.
>> 
>> Which versions of efibootmgr and libefivar1 do you have installed?
>
>The problem persists since several months. Now I have:
>
># apt-list | grep efi
>efibootmgr/unstable,now 17-1 amd64 [installed]
>libefiboot1/unstable,now 37-6 amd64 [installed,automatic]
>libefivar1/unstable,now 37-6 amd64 [installed,automatic]

This line:

efivarfs   16384  0

suggests the cause of the problem for you. efibootmgr (and other tools
using libefivar) will look into both:

 * /sys/firmware/efi/vars (the old, deprecated interface that was
   removed in 5.10)
 * /sys/firmware/efi/efivars (the new interface, provided by efivarfs)

As you have efivarfs loaded but with use-count of 0, that suggests
that you don't have the efivarfs pseudo-filesystem mounted. This
should normally be automatically mounted on system boot, along with
the other pseudo-filesystems like /sys and /proc.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Re: [sid] efibootmgr not working on linux 5.10.x & LGA1155

[Grzesiek]

On 4/10/21 7:52 PM, Sven Joachim wrote:

On 2021-04-08 22:30 +0200, Grzesiek wrote:


On 3/18/21 9:55 PM, Sven Joachim wrote:

On 2021-03-18 21:03 +0100, Grzesiek Sójka wrote:


I noticed recently that efibootmgr stoped working. On all my Sid
machines I get the following:

# efibootmgr
EFI variables are not supported on this system.

But if I run Buster (the same hardware) then everything is ok. So this
is definitely software problem. I also noticed that the
/sys/firmware/efi/efivars
directory is empty.

Not here, and efibootmgr works for me.


Kernel problem? Missing modules?

Perhaps the efivarfs module is not loaded.  I don not have to load
it
manually, though.


The problem seems to be related to 5.10.x kernels & LGA1155 based systems.

1. On laptop based on i5-8250u efibootmgr works fine (all kernel versions)

2. On systems based on LGA1155 socket (i5-2500k, i7-3770):
- kernels 5.10.x: efibootmgr does not work,
directory /sys/firmware/efi/efivars is empty
- kernel 5.8.0-2: efibootmgr woks as expected

On 5.8.0-2 i get:

# lsmod | grep efi
efivarfs   16384  0
efi_pstore 16384  0
efivars20480  1 efi_pstore

There is no efivars.ko in 5.10.x. Maybe that is the problem?


The efivars module has indeed been removed from Debian's 5.10 kernels,
as it had been deprecated in favor of efivarfs for a while.

Which versions of efibootmgr and libefivar1 do you have installed?


The problem persists since several months. Now I have:

# apt-list | grep efi
efibootmgr/unstable,now 17-1 amd64 [installed]
libefiboot1/unstable,now 37-6 amd64 [installed,automatic]
libefivar1/unstable,now 37-6 amd64 [installed,automatic]

Re: [sid] efibootmgr not working on linux 5.10.x & LGA1155

[Sven Joachim]

On 2021-04-08 22:30 +0200, Grzesiek wrote:

> On 3/18/21 9:55 PM, Sven Joachim wrote:
>> On 2021-03-18 21:03 +0100, Grzesiek Sójka wrote:
>> 
>>> I noticed recently that efibootmgr stoped working. On all my Sid
>>> machines I get the following:
>>>
>>> # efibootmgr
>>> EFI variables are not supported on this system.
>>>
>>> But if I run Buster (the same hardware) then everything is ok. So this
>>> is definitely software problem. I also noticed that the
>>> /sys/firmware/efi/efivars
>>> directory is empty.
>> Not here, and efibootmgr works for me.
>> 
>>> Kernel problem? Missing modules?
>> Perhaps the efivarfs module is not loaded.  I don not have to load
>> it
>> manually, though.
>
> The problem seems to be related to 5.10.x kernels & LGA1155 based systems.
>
> 1. On laptop based on i5-8250u efibootmgr works fine (all kernel versions)
>
> 2. On systems based on LGA1155 socket (i5-2500k, i7-3770):
> - kernels 5.10.x: efibootmgr does not work,
> directory /sys/firmware/efi/efivars is empty
> - kernel 5.8.0-2: efibootmgr woks as expected
>
> On 5.8.0-2 i get:
>
> # lsmod | grep efi
> efivarfs   16384  0
> efi_pstore 16384  0
> efivars20480  1 efi_pstore
>
> There is no efivars.ko in 5.10.x. Maybe that is the problem?

The efivars module has indeed been removed from Debian's 5.10 kernels,
as it had been deprecated in favor of efivarfs for a while.

Which versions of efibootmgr and libefivar1 do you have installed?

Cheers,
   Sven

Re: [sid] efibootmgr not working on linux 5.10.x & LGA1155

[Grzesiek]

On 3/18/21 9:55 PM, Sven Joachim wrote:

On 2021-03-18 21:03 +0100, Grzesiek Sójka wrote:


I noticed recently that efibootmgr stoped working. On all my Sid
machines I get the following:

# efibootmgr
EFI variables are not supported on this system.

But if I run Buster (the same hardware) then everything is ok. So this
is definitely software problem. I also noticed that the
/sys/firmware/efi/efivars
directory is empty.


Not here, and efibootmgr works for me.


Kernel problem? Missing modules?


Perhaps the efivarfs module is not loaded.  I don not have to load it
manually, though.


The problem seems to be related to 5.10.x kernels & LGA1155 based systems.

1. On laptop based on i5-8250u efibootmgr works fine (all kernel versions)

2. On systems based on LGA1155 socket (i5-2500k, i7-3770):
- kernels 5.10.x: efibootmgr does not work,
directory /sys/firmware/efi/efivars is empty
- kernel 5.8.0-2: efibootmgr woks as expected

On 5.8.0-2 i get:

# lsmod | grep efi
efivarfs   16384  0
efi_pstore 16384  0
efivars20480  1 efi_pstore

There is no efivars.ko in 5.10.x. Maybe that is the problem?

--
Regards
Greg

Re: [sid] efibootmgr not working

[Sven Joachim]

On 2021-03-18 21:03 +0100, Grzesiek Sójka wrote:

> I noticed recently that efibootmgr stoped working. On all my Sid
> machines I get the following:
>
> # efibootmgr
> EFI variables are not supported on this system.
>
> But if I run Buster (the same hardware) then everything is ok. So this
> is definitely software problem. I also noticed that the
> /sys/firmware/efi/efivars
> directory is empty.

Not here, and efibootmgr works for me.

> Kernel problem? Missing modules?

Perhaps the efivarfs module is not loaded.  I don not have to load it
manually, though.

Cheers,
   Sven

Re: Sid, upgrade kernel casse mon Wifi

[Étienne Mollier]

Bonsoir Jérôme,

jerome moliere, on 2021-02-10 18:30:33 +0100:
> Bonjour
> d'apres le support System76 la these de la panne materielle semble la plus
> probable.

Ce ne serait pas surprenant.

> Je vais donc commander une carte et tester 
> Vous avez des references a conseiller en la matiere, compatibles si
> possible Linux libre ?

Il y a eu une grosse discussion sur debian-devel le mois dernier
après que quelqu'un a signalé que le disque d'installation
réseau sans firmware non libres mis en avant en page d'accueil
de debian.org était un choix malheureux[1].  Attention, il y a
beaucoup de lecture en Anglais, si vous vous intéressez au fil
de discussion complet.

[1] https://lists.debian.org/debian-devel/2021/01/msg00151.html

Je n'ai pas retrouvé le message en question, mais il me semble
qu'une des difficultés pour avoir des micrologiciels libres dans
le domaine des puces de communication sans fil est la
réglementation, qui interdit les fabricant de fournir du
matériel qui serait capable d'opérer en dehors des bandes
autorisées.

Il y avait également un ou plusieurs message concernant quelques
références pour des puces wifi libres, mais elle ne semblaient
ni être les plus performantes, ni être les plus simples à se
procurer.

> chipsets ath9k ou ath10k . D'autres ?
> Quelles references eventuellement ...

Dans la gamme Qualcomm Atheros, les chipsets supportés
comprennent ceux listés dans la description du paquet
firmware-atheros.  Ils ne sont malheureusement pas Libres, mais
ils sont disponibles via le dépôt non-free.  La liste est assez
longue, mais peut être obtenue avec la commande :

$ apt show firmware-atheros

Il y a également des puces Broadcom, Marvell, Intel (mais
j'imaginge que vous n'avez pas envie de retenter l'expérience
iwlwifi que avez eu), etc.  Pour une liste, probablement non
exhaustive, des paquets de micrologiciels supportés par non-free
pour fournir du wifi, vous pouvez voir le résultat de la
commande suivante, qui sur Sid avec non-free me donne :

$ apt-cache search ^firmware- | grep -Ei 'wireless|wifi'
firmware-ath9k-htc - firmware for AR7010 and AR9271 USB wireless 
adapters
firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards
firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 
wireless cards
firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 
and 2915
firmware-iwlwifi - Binary firmware for Intel Wireless cards
firmware-libertas - Binary firmware for Marvell wireless cards
firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters
firmware-ti-connectivity - Binary firmware for TI Connectivity wifi and 
BT/FM/GPS adapters
firmware-zd1211 - binary firmware for the zd1211rw wireless driver
firmware-ralink - Binary firmware for Ralink wireless cards (dummmy 
package)

> Merci a vous

Bonne soirée,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Re: Sid, upgrade kernel casse mon Wifi

[jerome moliere]

Bonjour
d'apres le support System76 la these de la panne materielle semble la plus
probable.
Je vais donc commander une carte et tester 
Vous avez des references a conseiller en la matiere, compatibles si
possible Linux libre ?
chipsets ath9k ou ath10k . D'autres ?
Quelles references eventuellement ...
Merci a vous

Le lun. 8 févr. 2021 à 18:12, jerome moliere  a
écrit :

> Bonjour a tous,
> je suis victime d'un souci sournois sur 1 laptop System76 lemur pro dote
> de composants Intel 11eme generation.
> Suite a l'upgrade du kernel en 5.10-2 (et 3 depuis) je n'ai plus de wifi:
> - lspci voit toujours la carte lspci -nnk
> lspci -nnk|grep -i network   ─╯
> 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP
> CNVi WiFi [8086:02f0]
>
> par contre  elle est invisible par ip/iwconfig etc
> ip a ─╯
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
> default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
>valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
> 2: enx0050b6ebc397:  mtu 1500
> qdisc pfifo_fast state UP group default qlen 1000
> link/ether 00:50:b6:eb:c3:97 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.34/24 brd 192.168.1.255 scope global enx0050b6ebc397
>valid_lft forever preferred_lft forever
> inet6 2a01:cb19:65b:4100:2b1a:5245:8c46:60f3/64 scope global temporary
> dynamic
>valid_lft 1773sec preferred_lft 573sec
> inet6 2a01:cb19:65b:4100:250:b6ff:feeb:c397/64 scope global dynamic
> mngtmpaddr
>valid_lft 1773sec preferred_lft 573sec
> inet6 fe80::250:b6ff:feeb:c397/64 scope link
>valid_lft forever preferred_lft forever
> 3: docker0:  mtu 1500 qdisc noqueue
> state DOWN group default
> link/ether 02:42:a0:41:aa:9a brd ff:ff:ff:ff:ff:ff
> inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
>valid_lft forever preferred_lft forever
>
>
> Dans les logs du kernel on voit qu'il y a un souci de chargement du
> firmware:
> sudo dmesg|grep -i iwlwifi
>
>
>─╯
> [4.769596] iwlwifi :00:14.3: minimum version required: (efault)198
> [4.769643] iwlwifi :00:14.3: maximum version supported: (efault)143
> [4.769684] iwlwifi :00:14.3: check git://
> git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> [4.769744] iwlwifi :00:14.3: Couldn't request the fw
> [4.783252] iwlwifi: probe of :00:14.3 failed with error -2
>
>
> Effectivement avec une version mini (198) > a la version maxi (143) cela
> va etre dur de charger quoi que ce soit je pense
> J'ai tente de copier les fichiers .ucode chopes sur le site de Intel dans
> /lib/firmware mais sans succes
>
>
> Que puis je faire ?
> Depuis ma carte wifi est invisible sur toutes les distros avec des kernels
> differents j'ai tente plusieurs livecd mais elle est tjs aux abonnes
> absents...
>
> Vos conseils eclaires sont les bienvenus.
> Cordialement
>

Re: Sid, upgrade kernel casse mon Wifi

[jerome moliere]

Bonjour a tous,
merci Etienne de cete reponse...
Alors OUI le souci n'est pas specifique a une distro il se produit pour
toutes les distros testees (environ 7 ou 8 avec des versions de kernel et
de packages linux-firmware differentes)
J'ai voulu teste GhostBSD mais la machine est recente et il ne boote pas
...-(
La carte Wifi est vue par le systeme avec lspci -nnk et le module essaie de
se charger Et juste avant l'update (jusqu'a Dimanche soir ou Lundi)
elle fonctionnait tres biem
Cela me parait etre du soft pur et dur 
Pour les numeros de version a noter que Garuda (Arch based)  n'indique pas
les memes mais ils sont errones et incoherents de la meme facon

Merci encore du coup de main... Je dois dire que je n'ai jamais ete
confronte a un souci aussi severe 
Encore merci

Le mar. 9 févr. 2021 à 21:26, Étienne Mollier 
a écrit :

> Bonsoir Jérôme,
>
> jerome moliere, on 2021-02-08 18:12:11 +0100:
> > Dans les logs du kernel on voit qu'il y a un souci de chargement du
> > firmware:
> > sudo dmesg|grep -i iwlwifi
>
> Les numéros de version ci-après :
>
> > [4.769596] iwlwifi :00:14.3: minimum version required:
> (efault)198
>  
> > [4.769643] iwlwifi :00:14.3: maximum version supported:
> (efault)143
>   
> sont précédés de la mention "(efault)".  Pour une raison ou pour
> une autre, le pilote tente d'accèder à une address invalide[1]
> pour indiquer les numéros de version de micrologiciel supportés
> par le pilote, d'où le résultat confus.
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/core-api/printk-formats.rst#n68
>
> > [4.769684] iwlwifi :00:14.3: check git://
> > git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> > [4.769744] iwlwifi :00:14.3: Couldn't request the fw
> > [4.783252] iwlwifi: probe of :00:14.3 failed with error -2
> [...]
> > Que puis je faire ?
> > Depuis ma carte wifi est invisible sur toutes les distros avec des
> kernels
> > differents j'ai tente plusieurs livecd mais elle est tjs aux abonnes
> > absents...
>
> Si le problème est indépendant des distributions, apparaissant
> ailleurs que dans Debian et ses distributions dérivées, alors ça
> vaudrait peut-être le coup d'ouvrir un rapport de bogue sur
> le bugzilla en amont[2].
>
> Éventuellement, ça pourrait valoir le coup de tester avec un
> système d'exploitation et un noyau entièrement différent (BSD,
> MS Windows), si c'est possible bien entendu, juste pour
> s'assurer que ce n'est pas la carte wifi qui a rendu l'âme.
>
> [2] https://bugzilla.kernel.org/
>
> Bonne soirée,
> --
> Étienne Mollier 
> Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
> Sent from /dev/pts/2, please excuse my verbosity.
>

Re: Sid, upgrade kernel casse mon Wifi

[Étienne Mollier]

Bonsoir Jérôme,

jerome moliere, on 2021-02-08 18:12:11 +0100:
> Dans les logs du kernel on voit qu'il y a un souci de chargement du
> firmware:
> sudo dmesg|grep -i iwlwifi

Les numéros de version ci-après :

> [4.769596] iwlwifi :00:14.3: minimum version required: (efault)198
 
> [4.769643] iwlwifi :00:14.3: maximum version supported: (efault)143
  
sont précédés de la mention "(efault)".  Pour une raison ou pour
une autre, le pilote tente d'accèder à une address invalide[1]
pour indiquer les numéros de version de micrologiciel supportés
par le pilote, d'où le résultat confus.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/core-api/printk-formats.rst#n68

> [4.769684] iwlwifi :00:14.3: check git://
> git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> [4.769744] iwlwifi :00:14.3: Couldn't request the fw
> [4.783252] iwlwifi: probe of :00:14.3 failed with error -2
[...]
> Que puis je faire ?
> Depuis ma carte wifi est invisible sur toutes les distros avec des kernels
> differents j'ai tente plusieurs livecd mais elle est tjs aux abonnes
> absents...

Si le problème est indépendant des distributions, apparaissant
ailleurs que dans Debian et ses distributions dérivées, alors ça
vaudrait peut-être le coup d'ouvrir un rapport de bogue sur
le bugzilla en amont[2].

Éventuellement, ça pourrait valoir le coup de tester avec un
système d'exploitation et un noyau entièrement différent (BSD,
MS Windows), si c'est possible bien entendu, juste pour
s'assurer que ce n'est pas la carte wifi qui a rendu l'âme.

[2] https://bugzilla.kernel.org/

Bonne soirée,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

RE: Sid random crash with no clue in log files

[Leandro neto]

 
Hi guys sorry form any inconvenience I would like to report what i am thinking a severe security vulnerability that affects all Debian based distros. it was on python 3 files  i am sending a link to every malign list that i am subscribed. IAM NOT A PROFESSIONAL. FELL FREE TO REMOTE ACCESS MY MACHINES ANYTIME. if i am wrong my apology. but i think on my little knowledge certain has something in there. There is a lot of files on the link. I am trying to upload the raw files. but every distro brakes. it shows 140.7 tbTB!!! yes 104000 gbt that fits on a flash drive of 32gb is is very difficult to me to use interment. am being hunting down. so this is my last try. contact only by phone number. because the monitored and listen everything mine.  is like a movie but is true.+552122366155 +552121796156 sorry but i don't know to tell this to anyone. because they don't believe.
link with the photos this is the link for linux distros  https://photos.app.goo.gl/oHRP5Z8JEoT9Q4GN9

link for the other systems osx windows andorid... 

https://photos.app.goo.gl/BsBCuYtVtE4VwGUC9
 
this is the link of the windows apple etc...

best regards leandro leme neto



De: to...@tuxteam.de
Enviada: 2020/10/28 14:00:50
Para: debian-user@lists.debian.org
Assunto:  Re: Sid random crash with no clue in log files

On Wed, Oct 28, 2020 at 04:09:33PM +0100, Sébastien Kalt wrote:
> Hello,
>
> I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while
> copying large files through network, sometimes when watching a youtube
> video, sometimes juste using LibreOffice, or going nothing ...
>
> I can't manage to have a pattern for thoses craches. Today it craches 4
> times, the last week it didn't crash.
>
> I encoded a video with 100 % CPU charge during one hour and it didn't crash.
>
> When I look at the log files, I see nothing : syslog, messages, daemon.log,
> kern.log, Xorg.0.log.old, dmesg
>
> When it crashes, the system seems to be not responding, I can move the
> mouse, but it doesn't click, and then the screen becomes blank. I need to
> shut down the mini PC pushing the power button for a long time.
>
> When I restart it, I don't see anything during the reboot (well, it's quite
> fast, so I might miss something).
>
> Do you have any suggestions to find what might be causing this ?

If the mouse still moves, I'd look first into software. Try to log
into your machine either with a Linux console (CTRL-ALT+F1 or some
other function key) or via ssh, as linux fan suggests.

Try to locate some central gui program which might be misbehaving
and kill it (gnome-panel or some such).

If it were a hardware problem, the machine would most probably
freeze completely or at least show non-repeatable symptoms.

Cheers
- t

Re: Sid random crash with no clue in log files

[tomas]

On Wed, Oct 28, 2020 at 04:09:33PM +0100, Sébastien Kalt wrote:
> Hello,
> 
> I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while
> copying large files through network, sometimes when watching a youtube
> video, sometimes juste using LibreOffice, or going nothing ...
> 
> I can't manage to have a pattern for thoses craches. Today it craches 4
> times, the last week it didn't crash.
> 
> I encoded a video with 100 % CPU charge during one hour and it didn't crash.
> 
> When I look at the log files, I see nothing : syslog, messages, daemon.log,
> kern.log, Xorg.0.log.old, dmesg
> 
> When it crashes, the system seems to be not responding, I can move the
> mouse, but it doesn't click, and then the screen becomes blank. I need to
> shut down the mini PC pushing the power button for a long time.
> 
> When I restart it, I don't see anything during the reboot (well, it's quite
> fast, so I might miss something).
> 
> Do you have any suggestions to find what might be causing this ?

If the mouse still moves, I'd look first into software. Try to log
into your machine either with a Linux console (CTRL-ALT+F1 or some
other function key) or via ssh, as linux fan suggests.

Try to locate some central gui program which might be misbehaving
and kill it (gnome-panel or some such).

If it were a hardware problem, the machine would most probably
freeze completely or at least show non-repeatable symptoms.

Cheers
 - t


signature.asc
Description: Digital signature

Re: Sid random crash with no clue in log files

[Charles Curley]

On Wed, 28 Oct 2020 16:09:33 +0100
Sébastien Kalt  wrote:

> I'm having random crashes on my ASUS PN50 mini PC : sometimes it's
> while copying large files through network, sometimes when watching a
> youtube video, sometimes juste using LibreOffice, or going nothing ...

> Do you have any suggestions to find what might be causing this ?

I suspect something, likely RAM, isn't properly seated. I would: remove
and re-seat any socketed ICs, and any daughter boards. Replug all
cables.

Install and run memtest86 for several hours.

If you have played with hardware settings in the BIOS, set them back to
factory values.

-- 
Does anybody read signatures any more?

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

Re: Sid random crash with no clue in log files

[Linux-Fan]

Sébastien Kalt writes:


Hello,

I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while  


[...]

When it crashes, the system seems to be not responding, I can move the mouse,  
but it doesn't click, and then the screen becomes blank. I need to shut down  
the mini PC pushing the power button for a long time.


[...]

Hello,

common things to test in case of random crashes are hardware-related issues  
like cooling (CPU temperatures?), power supply and RAM (memtest86+).


Another thing to debug is: While the system is in the described crash state,  
you can still move the mouse -- this means some software on the system  
remains running despite not being accessible through GUI. An interesting  
step could be to attempt a login through SSH (install openssh-server if not  
already there to enable SSH access). From that SSH login you might be able  
to call a tool like `htop` to check the state of the system and stop any  
rouge processes etc.


I used to have similar types of crashes (the screen never went black, but  
the mouse cursor would move with any further inputs like klicks and key  
presses ignored) on a system with VirtualBox and the NVidia proprietary GPU  
driver (must have been Debian 7 or 8 IIRC). If either VirtualBox or NVidia  
graphics driver were uninstalled, it would never crash that way... In any  
case, logging in through SSH, I could see that the Xorg process was at 100%  
CPU. Killing it caused the screen to go black. Attempting to re-start would  
fail in some way, but afterwards a login from the local system would again  
be possible and the hard reset could be avoided...


HTH
Linux-Fan

öö


pgpIWNhCGmk3b.pgp
Description: PGP signature

Re: SID/GNOME/son/périphérique de sortie HDMI /Display port

[Orion]

Bonjour,

en comparant la  sortie pactl info d'une fedora Fedora 32:
f
edora:
Profils :
input:analog-stereo: Entrée Stéréo analogique (sinks: 0, sources: 1,
priority: 65, available: oui)
output:analog-stereo: Sortie Stéréo analogique (sinks: 1, sources: 0,
priority: 6500, available: oui)
output:analog-stereo+input:analog-stereo: Duplex stéréo analogique (sinks:
1, sources: 1, priority: 6565, available: oui)
output:iec958-stereo: Sortie Stéréo numérique (IEC958) (sinks: 1, sources:
0, priority: 5500, available: oui)
output:iec958-stereo+input:analog-stereo: Sortie Stéréo numérique (IEC958)
+ Entrée Stéréo analogique (sinks: 1, sources: 1, priority: 5565,
available: oui)

debian :
Profils :
input:analog-stereo: Entrée Stéréo analogique (sinks: 0, sources: 1,
priority: 65, available: oui)
output:iec958-stereo: Sortie Stéréo numérique (IEC958) (sinks: 1, sources:
0, priority: 5500, available: oui)
output:iec958-stereo+input:analog-stereo: Sortie Stéréo numérique (IEC958)
+ Entrée Stéréo analogique (sinks: 1, sources: 1, priority: 5565,
available: oui)

j''ai pas les profils
output:analog-stereo: Sortie Stéréo analogique (sinks: 1, sources: 0,
priority: 6500, available: oui)
output:analog-stereo+input:analog-stereo: Duplex stéréo analogique (sinks:
1, sources: 1, priority: 6565, available: oui)
sous debian, je peux les rajouter?

On Sat, Sep 12, 2020 at 8:18 PM François LE GAD 
wrote:

> Le 12/09/2020 à 19:08, Orion a écrit :
> > Nom du serveur : pulseaudio
>
> Puseaudio permet de choisir le périphérique de sortie.
>
> Dans le greffon pulseaudio: Général > Lancer le mixeur audio >
> Périphérique de sortie > port
>
> Bon, c'est pour XFCE, qui a son propre greffon. Pour gnome, la manip est
> peut-être différente.
>
> --
> François
>
>

Re: SID/GNOME/son/périphérique de sortie HDMI /Display port

[François LE GAD]

Le 12/09/2020 à 19:08, Orion a écrit :

Nom du serveur : pulseaudio


Puseaudio permet de choisir le périphérique de sortie.

Dans le greffon pulseaudio: Général > Lancer le mixeur audio > 
Périphérique de sortie > port


Bon, c'est pour XFCE, qui a son propre greffon. Pour gnome, la manip est 
peut-être différente.


--
François

Re: [Sid] ahci: disk order

[Grzesiek Sójka]

On 2020-07-24 21:08, Reco wrote:

Hi.

On Fri, Jul 24, 2020 at 10:03:01PM +0300, Andrei POPESCU wrote:

On Vi, 24 iul 20, 21:58:26, Andrei POPESCU wrote:

On Vi, 24 iul 20, 19:39:21, Grzesiek Sójka wrote:

Hi there,

I noticed that SATA disks appear in random order. More precisely, I have two
disks, HDD and SSD. Sometimes HDD=/dev/sda, SSD=/dev/sdb and sometimes
HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order?


Not that I know of.


I would
like the disk connected to port 1 to be sda, disk connected to port 2 to be
sdb and so on (like it was in the past)


It might be possible with some special udev rules,


Correction: probably not, since those names are assigned by the kernel.


A correction over the correction ;) :

- it's possible, it's called RENAME= in udev rules.
- it's unneeded in about every case, given that wonderful /dev/disk
   directory.
- and if it is needed for some reason, one's always better to use SYMLINK
   over the RENAME.


Thanks for the info

Re: [Sid] ahci: disk order

[Kamil Jońca]

Stefan Monnier  writes:

>> HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order? I would
>
> The usual recommendation is to change the way you work such that you
> don't depend on those names.

+1
>
> Personally, I use LVM so all my "partitions" (called "logical volumes")
> have a name that I chose.  I started using LVM for other reasons (the
> flexibility it offers in terms of manipulation of "partitions"), but the
> naming turned out to be an invaluable side benefit.

Same history in my case. For my new installations I don't even try "not to
use" lvm.

KJ


-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

Re: [Sid] ahci: disk order

[Stefan Monnier]

> HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order? I would

The usual recommendation is to change the way you work such that you
don't depend on those names.

Personally, I use LVM so all my "partitions" (called "logical volumes")
have a name that I chose.  I started using LVM for other reasons (the
flexibility it offers in terms of manipulation of "partitions"), but the
naming turned out to be an invaluable side benefit.


Stefan

Re: [Sid] ahci: disk order

[Reco]

Hi.

On Fri, Jul 24, 2020 at 10:03:01PM +0300, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 21:58:26, Andrei POPESCU wrote:
> > On Vi, 24 iul 20, 19:39:21, Grzesiek Sójka wrote:
> > > Hi there,
> > > 
> > > I noticed that SATA disks appear in random order. More precisely, I have 
> > > two
> > > disks, HDD and SSD. Sometimes HDD=/dev/sda, SSD=/dev/sdb and sometimes
> > > HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order?
> > 
> > Not that I know of.
> > 
> > > I would
> > > like the disk connected to port 1 to be sda, disk connected to port 2 to 
> > > be
> > > sdb and so on (like it was in the past)
> > 
> > It might be possible with some special udev rules,
> 
> Correction: probably not, since those names are assigned by the kernel.

A correction over the correction ;) :

- it's possible, it's called RENAME= in udev rules.
- it's unneeded in about every case, given that wonderful /dev/disk
  directory.
- and if it is needed for some reason, one's always better to use SYMLINK
  over the RENAME.

Reco

Re: [Sid] ahci: disk order

[Andrei POPESCU]

On Vi, 24 iul 20, 21:58:26, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 19:39:21, Grzesiek Sójka wrote:
> > Hi there,
> > 
> > I noticed that SATA disks appear in random order. More precisely, I have two
> > disks, HDD and SSD. Sometimes HDD=/dev/sda, SSD=/dev/sdb and sometimes
> > HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order?
> 
> Not that I know of.
> 
> > I would
> > like the disk connected to port 1 to be sda, disk connected to port 2 to be
> > sdb and so on (like it was in the past)
> 
> It might be possible with some special udev rules,

Correction: probably not, since those names are assigned by the kernel.

> or you could use LABELs or UUIDs instead, like the rest of the world 
> ;)
> 
> What specific problem is this creating for you?

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


signature.asc
Description: PGP signature

Re: [Sid] ahci: disk order

[Andrei POPESCU]

On Vi, 24 iul 20, 19:39:21, Grzesiek Sójka wrote:
> Hi there,
> 
> I noticed that SATA disks appear in random order. More precisely, I have two
> disks, HDD and SSD. Sometimes HDD=/dev/sda, SSD=/dev/sdb and sometimes
> HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk order?

Not that I know of.

> I would
> like the disk connected to port 1 to be sda, disk connected to port 2 to be
> sdb and so on (like it was in the past)

It might be possible with some special udev rules, or you could use 
LABELs or UUIDs instead, like the rest of the world ;)

What specific problem is this creating for you?

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


signature.asc
Description: PGP signature

Re: [Sid] ahci: disk order

[Cindy Sue Causey]

On 7/24/20, Grzesiek Sójka  wrote:
> Hi there,
>
> I noticed that SATA disks appear in random order. More precisely, I have
> two disks, HDD and SSD. Sometimes HDD=/dev/sda, SSD=/dev/sdb and
> sometimes HDD=/dev/sdb, SSD=/dev/sda. Is there any way to fix the disk
> order? I would like the disk connected to port 1 to be sda, disk
> connected to port 2 to be sdb and so on (like it was in the past)
>
> Thanks in advance for any help.


DISCLAIMER: I acknowledge this is the kind of information request
redirect that gets dissed, but still... :)

Are you working on a project that could implement "label" instead? I
LOVE THEM... ever since I finally understood them.

Over time, I've gone from /dev/sdx to "UUID=" to... LABEL. For /dev &
UUID, I ALWAYS had to do what I'm imagining you doing on some level. I
ALWAYS had to rely on something like "blkid" to get things pointed in
the right direction.

These days, I still do turn to blkid for reassurance once in a while,
mostly just to confirm if something is or is NOT actually functionally
plugged in. Otherwise, I've got labels that are "rational" *to my
brain* such that I can whip them out in e.g. terminal commands without
having to stop and look at anything first...

Gparted is where I set mine up, by the way. EVERY ONE needs to be
different for this to work successfully. There appears to be one
possible exception to that, but just.. *GACK* on that (GRUB v. GPT)
topic.

You pick memorable names that are uniquely identifiable so that
there's no chance of a system-wide clash. Mine are named based on the
function of the partition and that partition's hand chosen physical
hard drive ID, e.g. "nikon-hd1".

Those labels work in /etc/fstab, "sudo mount", and other fun places..
that I can't remember offhand just now

Just thinking out loud..

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Re: [Sid] hp active stylus support

[Tomaž Šolc]

On 25. 05. 20 22:11, Grzesiek Sójka wrote:

Hi there,

I'm considering buying Hp Elite X2 1013 tablet PC. I'm wondering if the 
Hp active stylus attached to the device is supported by Debian Sid. Any 
experiences?


Not a first hand experience, but I did some searching because I'm 
curious about tablet PC support. Here are some links in case you haven't 
them yet.


This post says that touchscreen and pen are supported in Linux and 
mentions kernel 4.19. Debian Sid currently ships with a newer one, so 
unless there's been a regression, it should work.


https://www.reddit.com/r/linux/comments/9sxymj/linux_driver_compatibility_with_modern_2in1/

Apparently touchscreen is based on Wacom hardware and I have very good 
experience with their Linux drivers for Cintiqs.


This issue says that there's a problem with the key mapping for the 
button on the HP pen:


https://github.com/linuxwacom/input-wacom/issues/49

Best regards
Tomaž

Re: Sid: /sbin/ifenslave missing??

[Sven Hartge]

Sven Hartge  wrote:

> Temporary solution: downgrade to 2.9 again, hold the package and monitor
> the bug report I linked.

Sorry, the correct bug is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959236

Unfortunately it has only "normal" severity, "grave" would be better
here, since it not only breaks the function of the package, it breaks
the whole system.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Sid: /sbin/ifenslave missing??

[Sven Hartge]

Grzesiek Sójka  wrote:
> On 5/17/20 12:34 PM, Sven Hartge wrote:

>> Mind doing a "ifup -v bond0" to really see what is called how and where
>> it fails in what way?

> after "ifup -v bond0" I get a larg number of following messages 
> (probably 1000?):

> + [ -n  ]
> + return 0
> + setup_master
> + add_master
> + [ -f /sys/class/net/bond0/bonding/slaves ]
> + return
> + early_setup_master
> + sysfs fail_over_mac
> + [ -n  ]
> + return 0
> + setup_master
> + add_master
> + [ -f /sys/class/net/bond0/bonding/slaves ]
> + return
> + early_setup_master
> + sysfs fail_over_mac
> /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth 
> (1000) reached
> run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 2
> ifup: failed to bring up bond0

Interesting. Yes, this seems like a genuine bug in the package but not
caused by the removal of the ifenslave shell script but by some bug in
the ifup-(pre)scripts provided by the package.

Temporary solution: downgrade to 2.9 again, hold the package and monitor
the bug report I linked.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Sid: /sbin/ifenslave missing??

[Grzesiek Sójka]

On 5/17/20 12:34 PM, Sven Hartge wrote:

Mind doing a "ifup -v bond0" to really see what is called how and where
it fails in what way?


after "ifup -v bond0" I get a larg number of following messages 
(probably 1000?):


+ [ -n  ]
+ return 0
+ setup_master
+ add_master
+ [ -f /sys/class/net/bond0/bonding/slaves ]
+ return
+ early_setup_master
+ sysfs fail_over_mac
+ [ -n  ]
+ return 0
+ setup_master
+ add_master
+ [ -f /sys/class/net/bond0/bonding/slaves ]
+ return
+ early_setup_master
+ sysfs fail_over_mac
/etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth 
(1000) reached

run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 2
ifup: failed to bring up bond0

BTW: # apt-list | grep ifup
ifupdown/unstable,now 0.8.35+b1 amd64 [installed]

Re: Sid: /sbin/ifenslave missing??

[Sven Hartge]

Grzesiek Sójka  wrote:
> On 5/17/20 12:13 PM, Sven Hartge wrote:

>> How does your /etc/network/interfaces look like? Usally all the work is
>> done via if-pre-up.d and if-up.d scripts provided by the ifenslave
>> package.

> # cat /etc/network/interfaces
> source-directory /etc/network/interfaces.d
> auto bond0

> iface bond0 inet static
>   address 192.168.0.130
>   netmask 255.255.255.252
>   gateway 192.168.0.129
>   slaves eth0 eth1
>   mtu 9000

> So I need to "adjust" network configuration to bond using iproute2 instead?

No, that should work, my configurations look similar (but they are all
on Buster and thus on 2.9, so I have not seen this bug myself).

Mind doing a "ifup -v bond0" to really see what is called how and where
it fails in what way?

Grüße,
Sven.


-- 
Sigmentation fault. Core dumped.

Re: Sid: /sbin/ifenslave missing??

[Grzesiek Sójka]

On 5/17/20 12:13 PM, Sven Hartge wrote:

How does your /etc/network/interfaces look like? Usally all the work is
done via if-pre-up.d and if-up.d scripts provided by the ifenslave
package.


# cat /etc/network/interfaces
source-directory /etc/network/interfaces.d
auto bond0

iface bond0 inet static
  address 192.168.0.130
  netmask 255.255.255.252
  gateway 192.168.0.129
  slaves eth0 eth1
  mtu 9000

So I need to "adjust" network configuration to bond using iproute2 instead?

Re: Sid: /sbin/ifenslave missing??

[Sven Joachim]

On 2020-05-17 11:27 +0200, Grzesiek Sójka wrote:

> After upgrading ifenslave from 2.9 to 2.10 i found that there if no
> /sbin/ifenslave binary. To restore network connectivity I had to 
> manually downgrade to 2.9. Is it on purpose? If so, then how to
> properly configure link aggregation?

I don't use ifenslave, but this change has been done on purpose:

,
| ifenslave (2.10) unstable; urgency=medium
| [...]
|   * Remove the ifenslave binary, use iproute2 instead.
| [...]
|  -- Guus Sliepen   Sun, 26 Apr 2020 21:09:15 +0200
`

Refer to ip(8) and the manpages it references, if you can comprehend
them.

Cheers,
   Sven

Re: Sid: /sbin/ifenslave missing??

[Sven Hartge]

Grzesiek Sójka  wrote:

> After upgrading ifenslave from 2.9 to 2.10 i found that there if no
> /sbin/ifenslave binary. To restore network connectivity I had to
> manually downgrade to 2.9. Is it on purpose? If so, then how to
> properly configure link aggregation?

It seems you hit
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959075

But NEWS.Debian says:

,
| ifenslave (2.10) UNRELEASED; urgency=medium
|
|   This version of the ifenslave package no longer provides /sbin/ifenslave. 
The
|   /sbin/ip command from the iproute2 package supports creating bonding masters
|   and enslaving other interfaces to it.
|
|  -- Guus Sliepen   Tue, 08 May 2018 22:47:07 +0200
`

How does your /etc/network/interfaces look like? Usally all the work is
done via if-pre-up.d and if-up.d scripts provided by the ifenslave
package.

S!

-- 
Sigmentation fault. Core dumped.

Re: [sid] xorg keymap modifying

[Siard]

Grzesiek Sójka wrote:
> I do have sid running on  tablet pc. I decided to use one of the 
> physical keys as F11. Its keycode is 125 (the one with windows icon). To 
> do it on console i put the following in /etc/rc.local:
> 
> echo "keycode 125 = F11" | loadkeys
> 
> And it works as expected. Unfortunately, I did not find a way to do it 
> on xorg.

xmodmap is used for that.

$ xmodmap -e "keycode 125 = F11"

Re: Sid broke my wireless

[Miguel A. Vallejo]

Hi!

Kernels 5.2.x are a disaster for wifi. Several wifi modules doesn't
work well or doesn't work at all. I'm experiencing myself too much
frequent disconnects with USB wifi cards (Mediatek and Realtek). Then
add USB 3.0 problems (Wrong bounce buffer write length warnings) and
the result is a barely usable system.

Downgrade to 4.19 kernels is not possible for me because with them I
have 100% cpu usage from ksoftirqd kernel process.

I'm really waiting for a new kernel upgrade in Sid.

Re: Sid: APC Smart-UPS 1500 & nut

[Grzesiek Sójka]

On 2/11/19 1:56 PM, Alexander V. Makartsev wrote:

On 11.02.2019 16:20, Grzesiek Sójka wrote:

Hi there,

Ups is connected via usb:

Bus 003 Device 002: ID 051d:0002 American Power Conversion 
Uninterruptible Power Supply


Recently I noticed that nut stopped to recognize it (probably after 
some update):


# /lib/nut/usbhid-ups -a APC
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
# cat /etc/nut/ups.conf
[APC]
driver = usbhid-ups
port = auto

I did try to fix the problem by adding vendor or product options or 
changing the driver but no luck.


Any suggestions? Is the driver correct?

I don't know about nut, but I had similar problems with APC SU1500 
models in the past.
They had some kind of firmware bug, or hardware problem with USB 
interface and sporadically loose connectivity to host. Also there was no 

[...]

I have PLD-linux in chroot ad I did run the following:

# /lib/nut/usbhid-ups -u root -a APC
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Using subdriver: APC HID 0.96

As you can see, result is positive. No reboot, the same kernel. So, this 
is 100% software problem related to Debian. A bug maybe??


Any suggestions? Workaround?? Different driver??

Re: Sid: APC Smart-UPS 1500 & nut

[Alexander V. Makartsev]

On 11.02.2019 16:20, Grzesiek Sójka wrote:
> Hi there,
>
> Ups is connected via usb:
>
> Bus 003 Device 002: ID 051d:0002 American Power Conversion
> Uninterruptible Power Supply
>
> Recently I noticed that nut stopped to recognize it (probably after
> some update):
>
> # /lib/nut/usbhid-ups -a APC
> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> USB communication driver 0.33
> No matching HID UPS found
> # cat /etc/nut/ups.conf
> [APC]
> driver = usbhid-ups
> port = auto
>
> I did try to fix the problem by adding vendor or product options or
> changing the driver but no luck.
>
> Any suggestions? Is the driver correct?
>
I don't know about nut, but I had similar problems with APC SU1500
models in the past.
They had some kind of firmware bug, or hardware problem with USB
interface and sporadically loose connectivity to host. Also there was no
way to recover UPS from this state other than performing "cold reset"
procedure. [1] After that USB connectivity was restored and continued to
function until this bug is triggered again, which could happen in a span
from few hours to weeks.
In the end I've resolved this nightmare by creating custom 9pin
COM-to-COM cables [2] [3] and stopped to use USB ports. Additionally, in
some cases I had to reprogram UPS firmware via terminal, [4] to get it
working again and be discovered by management software. This also could
be useful to perform basic connectivity diagnostics.

There are some bookmarks I saved about this problem that could be useful:
[1] https://www.schneider-electric.com/en/faqs/FA156611/
[2] http://news-posts.aplawrence.com/472.html
[3] http://pinoutguide.com/UPS/apc_smart_cable_pinout.shtml
[4] http://www.joeteck.com/apc.htm

-- 
With kindest regards, Alexander.

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

Re: Sid les dernières mises à jours veulent supprimer Xsane et digikam

[Florent BAYLE]

On vendredi 23 novembre 2018 18 h 14 min 30 s CET, MERLIN Philippe wrote:

Bonjour,
Mon installation est une Debian Sid AMD64 depuis plusieurs 
jours les dernières 
mises à jours veulent supprimer des logiciels importants comme 
xsane , digikam 
et hplip , ce qui me fait refuser ces dernières. Es ce que vous 
savez ce qui 
cause ce problème et si possible dans combien de temps cela va 
être corrigé ?


Bonjour,

Il y a eu pas mal d'activité autour de libsane/libsane1.

Si tu as toujours le problème, tu peux essayer la commande suivante :

apt-get install libsane libsane1-

qui permet d'installer libsane, tout en désinstallant libsane1, ce qui 
devrait te permettre de mettre à jour libsane-common au passage.


--
Florent

Re: Sid les dernières mises à jours veulent supprimer Xsane et digikam

[Haricophile]

Le Fri, 23 Nov 2018 18:14:30 +0100,
MERLIN Philippe  a écrit :

> Bonjour,
> Mon installation est une Debian Sid AMD64 depuis plusieurs jours les
> dernières mises à jours veulent supprimer des logiciels importants comme
> xsane , digikam et hplip , ce qui me fait refuser ces dernières. Es ce que
> vous savez ce qui cause ce problème et si possible dans combien de temps cela
> va être corrigé ? Philippe Merlin

Si on se pose ce genre de question sous SID il vaudrait peut-être mieux penser
à utiliser autre chose.

- Dans les versions de développement, que ce soit SID ou Testing il faut
toujours faire les mises a jour de manière "sure" (safe-upgrade avec aptitude)
et vérifier les problème de dépendances paquet par paquet avant de faire une
mise a jour de manière forcée (full-upgrade avec aptitude). Si SID est beaucoup
plus dynamique que Testing il faut quand même de temps en temps avoir de la
patience.

- De même il faut consulter les listes de bugs.

- Pour compléter, ne pas trop faire confiance aux meta-paquets dans SID. Il
 peut y avoir a supprimer l'attribut "installé automatiquement" sur certains
 paquets (unmarkauto avec aptitude).

Bref, si on n'est pas a l'aise avec la gestion des paquets et de leur
dépendance, avoir SID en version de production n'est pas franchement
recommandé. Ça ne l'est d'ailleurs jamais dans la doc de Debian ;)

Re: Sid les dernières mises à jours veulent supprimer Xsane et digikam

[Dominique Dumont]

Bonjour

On Friday, 23 November 2018 18:14:30 CET MERLIN Philippe wrote:
> Mon installation est une Debian Sid AMD64 depuis plusieurs jours les
> dernières mises à jours veulent supprimer des logiciels importants comme
> xsane , digikam et hplip , ce qui me fait refuser ces dernières. Es ce que
> vous savez ce qui cause ce problème 

C'est souvent dû:
- à une mise à jour de KDE qui est pas compatible avec la précédente version
- au temps qu'il faut pour construire tous les paquets KDE dans les serveurs 
de Debian

Quand les premières librairies compilées deviennent disponibles, apt cherche à 
déinstaller tous les paquets qui dépendent d'elle et ne sont pas compatibles. 

Ce mécanisme est appelé "transition". Les différentes transitions en court 
sont suivies ici: https://release.debian.org/transitions/

> et si possible dans combien de temps
> cela va être corrigé ? 

Faut attendre quelques jours que les serveurs Debian aient fini leur boulot.

HTH

Re: Sid les dernières mises à jours veulent supprimer Xsane et digikam

[fremoin]

Bonjour,

Le 23/11/2018 à 21:14, MERLIN Philippe a écrit :

Bonjour,
Mon installation est une Debian Sid AMD64 depuis plusieurs jours


Semaines, pour moi...


les dernières
mises à jours veulent supprimer des logiciels importants comme xsane , digikam


et toute une flopée de kde


et hplip , ce qui me fait refuser ces dernières.


pour xsane et hplip, j'ai passé l'épreuve mais ne sais plus trop 
comment... Je suppose en enlevant le paquet bloquant pour le remettre 
ensuite (ce qui en dit long sur ma compréhension de la chose).

En revanche...  les mises à jour du jour ont l'air de moins casser qu'avant.


Es ce que vous savez ce qui
cause ce problème et si possible dans combien de temps cela va être corrigé ?
Philippe Merlin


Donc, je n'aide pas vraiment, mais on se sent moins seul :)
Bonne journée,
Frédédic

Re: Sid: NFS after upgrade

[Elimar Riesebieter]

* Grzesiek Sójka  [2018-10-28 11:27 +]:

> Hi there,
> 
> I just upgraded Sid and now I get the following during boot:
> 
> [] Configuring network interfaces.../etc/init.d/rpcbind: 42:
> /etc/init.d/rpcbind: stat: not found
> /run/rpcbind not owned by root failed!
> Starting NFS common utilities: statd

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

Elimar
-- 
  Numeric stability is probably not all that
  important when you're guessing;-)

Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind

[Sven Joachim]

On 2018-10-28 16:58 +, Grzesiek Sójka wrote:

> On 10/28/18 2:10 PM, Sven Joachim wrote:
>> Wouldn't it be better to fix the init system that sets such a bad
>> default PATH?  Whatever init system that may be - sysv-rc's
>> /etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this
>> should not happen with sysvinit + sysv-rc. 
>
> Please, keep in mind that /etc/init.d/rpcbind may also be invoked by
> /etc/network/if-up.d/mountnfs (after bringing up interfaces):
>
> # grep PATH /etc/network/if-up.d/mountnfs
> PATH=/sbin:/bin

I see.  This could be fixed in ifupdown by not setting PATH in its init
scripts or by setting PATH in the rpcbind init script.

Overall PATH handling in init scripts is a total mess and needs to be
cleaned up.  These days /usr is supposed to be mounted by the initramfs
if it's on a different filesystem than /, so init scripts can rely on it
being present.

Please file a bug - most maintainers use systemd these days where those
problems do not exist, so they won't notice them.

Cheers,
   Sven

Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind

[Grzesiek Sójka]

On 10/28/18 2:10 PM, Sven Joachim wrote:

Wouldn't it be better to fix the init system that sets such a bad
default PATH?  Whatever init system that may be - sysv-rc's
/etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this
should not happen with sysvinit + sysv-rc. 


Please, keep in mind that /etc/init.d/rpcbind may also be invoked by 
/etc/network/if-up.d/mountnfs (after bringing up interfaces):


# grep PATH /etc/network/if-up.d/mountnfs
PATH=/sbin:/bin


What init system do you use?


# apt --installed list | grep sys | cut -f 1 -d ' '
busybox-syslogd/unstable,now
init-system-helpers/unstable,now
libboost-filesystem1.62.0/unstable,now
libboost-system1.62.0/unstable,now
libsystemd0/unstable,now
sysv-rc/unstable,now
sysvinit-core/unstable,now
sysvinit-utils/unstable,now

--
Pozdrawiam
Grzesiek

Wysłane z kompa wolnego od wirusów Billa Gatesa.

Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind

[Sven Joachim]

On 2018-10-28 14:47 +, Grzesiek Sójka wrote:

> On 10/28/18 11:27 AM, Grzesiek Sójka wrote:
>> Hi there,
>>
>> I just upgraded Sid and now I get the following during boot:
>>
>> [] Configuring network interfaces.../etc/init.d/rpcbind: 42:
>> /etc/init.d/rpcbind: stat: not found
>> /run/rpcbind not owned by root failed!
>> Starting NFS common utilities: statd
>> Not starting: portmapper is not running ... (warning).
>> mount.nfs: rpc.statd is not running but is required for remote locking.
>> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
>> mount.nfs: rpc.statd is not running but is required for remote locking.
>> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
>> done.
>> [ ok ] Starting RPC port mapper daemon: rpcbind.
>> [ ok ] Starting NFS common utilities: statd.
>
> The problem is caused by wrong setting of the PATH variable during the
> execution of the /etc/init.d/rpcbind script. The new version uses stat
> binary which is located in /usr/bin but the PATH is set to
> PATH='/sbin:/bin'.

This leaves the question why PATH is set that way.

> As a workaround I added PATH="$PATH:/usr/bin" to
> /etc/init.d/rpcbind. It works fine now.
>
> Please fix init scripts.

Wouldn't it be better to fix the init system that sets such a bad
default PATH?  Whatever init system that may be - sysv-rc's
/etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this
should not happen with sysvinit + sysv-rc.  What init system do you use?

Cheers,
   Sven

Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind

[Grzesiek Sójka]

On 10/28/18 11:27 AM, Grzesiek Sójka wrote:

Hi there,

I just upgraded Sid and now I get the following during boot:

[] Configuring network interfaces.../etc/init.d/rpcbind: 42: 
/etc/init.d/rpcbind: stat: not found

/run/rpcbind not owned by root failed!
Starting NFS common utilities: statd
Not starting: portmapper is not running ... (warning).
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
done.
[ ok ] Starting RPC port mapper daemon: rpcbind.
[ ok ] Starting NFS common utilities: statd.


The problem is caused by wrong setting of the PATH variable during the 
execution of the /etc/init.d/rpcbind script. The new version uses stat 
binary which is located in /usr/bin but the PATH is set to 
PATH='/sbin:/bin'. As a workaround I added PATH="$PATH:/usr/bin" to 
/etc/init.d/rpcbind. It works fine now.


Please fix init scripts.

--
Pozdrawiam
Grzesiek

Wysłane z kompa wolnego od wirusów Billa Gatesa.

Re: sid upgrade problem

[Default User]

On Sat, Sep 1, 2018 at 6:13 PM Ben Caradoc-Davies  wrote:

> On 02/09/2018 08:33, Default User wrote:
> > Setting up libsane1:amd64 (1.0.27-1) ...
> > Setting up sane-utils (1.0.27-1) ...
> > Installing new version of config file /etc/user/saned ...
> > Installing new version of config file /etc/init.d/saned ...
> > update-inetd: warning: cannot add service, /etc/inetd.conf does not exist
>
> It looks to me that your upgrade went fine. sane-utils depends on
> update-inetd for some reason, perhaps in case you are using inetd to
> share a local scanner via your network? Like you, I do not use inetd, do
> not have inetutils-inetd installed, and do not have /etc/inetd.conf . I
> saw the same message and took it as a harmless warning.
>
> Kind regards,
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
>

Hi, Ben.
Thanks for the reply. No, I am not using inetd to
share a local scanner via network. So, since I am not conversant with
inetd, I will just have to use my system for a while, to see if there is
something there that just doesn't seem to work, and if so, just take it
from there.

Re: sid upgrade problem

[Ben Caradoc-Davies]

On 02/09/2018 08:33, Default User wrote:

Setting up libsane1:amd64 (1.0.27-1) ...
Setting up sane-utils (1.0.27-1) ...
Installing new version of config file /etc/user/saned ...
Installing new version of config file /etc/init.d/saned ...
update-inetd: warning: cannot add service, /etc/inetd.conf does not exist


It looks to me that your upgrade went fine. sane-utils depends on 
update-inetd for some reason, perhaps in case you are using inetd to 
share a local scanner via your network? Like you, I do not use inetd, do 
not have inetutils-inetd installed, and do not have /etc/inetd.conf . I 
saw the same message and took it as a harmless warning.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: sid upgrade problem

[Default User]

On Sat, Sep 1, 2018 at 12:38 AM Ben Caradoc-Davies  wrote:

> On 01/09/2018 15:14, Default User wrote:
> > On Fri, Aug 31, 2018, 21:00 Ben Caradoc-Davies  wrote:
> >> On 30/08/2018 07:18, Ben Caradoc-Davies wrote:
> >>> On 30/08/2018 03:46, Default User wrote:
>  The following packages have unmet dependencies:
> libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
> libsane : Depends: libsane-common (= 1.0.25-4.1) but
>  1.0.27-1~experimental6 is to be installed
> >> [...]
>  I always choose "Y".  I keep waiting for the situation to resolve
> >> itself,
>  but it never does.
>  Insight?
> >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905913
> >> sane-backends 1.0.27-1 (the source package) was just uploaded and should
> >> soon be available on sid:
> >>
> https://tracker.debian.org/news/984005/accepted-sane-backends-1027-1-source-into-unstable/
> >> This upload (supposedly) fixes #905913 and so should resolve the upgrade
> >> problem.
> >
> > Hi, Ben.
> > Thanks for the heads-up.
> > I'll be watching.
>
> I just updated to 1.0.27-1 and my scanner still works (Brother
> MFC-L2740DW over WiFi network). Note that libsane is removed and
> replaced with libsane1. Package manager insistence on removing libsane
> is by design.
>
> Kind regards,
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
>
Hi.

Okay, I updated (sid).  Here is how it was done, and how it went. Please
consider the following (and please pardon the verbosity; I am used to
distributions where people will give you a hard time for not providing
"enough" information):

user@domain:~$ sudo aptitude -Pvv update
[sudo] password for user:
Get: 1 http://ftp.us.debian.org/debian unstable InRelease [233 kB]
Get: 2 http://ftp.us.debian.org/debian unstable/main Sources.diff/Index
[27.9 kB]
Get: 3 http://ftp.us.debian.org/debian unstable/main amd64
Packages.diff/Index [27.9 kB]
Get: 4 http://ftp.us.debian.org/debian unstable/main
Translation-en.diff/Index [27.9 kB]
Get: 5 http://ftp.us.debian.org/debian unstable/main Sources
2018-09-01-0208.01.pdiff [8,803 B]
Get: 6 http://ftp.us.debian.org/debian unstable/main Sources
2018-09-01-0808.21.pdiff [5,256 B]
Get: 7 http://ftp.us.debian.org/debian unstable/main Sources
2018-09-01-1408.47.pdiff [8,201 B]
Get: 8 http://ftp.us.debian.org/debian unstable/main amd64 Packages
2018-09-01-0208.01.pdiff [12.8 kB]
Get: 9 http://ftp.us.debian.org/debian unstable/main Sources
2018-09-01-1408.47.pdiff [8,201 B]
Get: 10 http://ftp.us.debian.org/debian unstable/main amd64 Packages
2018-09-01-0808.21.pdiff [4,293 B]
Get: 11 http://ftp.us.debian.org/debian unstable/main amd64 Packages
2018-09-01-1408.47.pdiff [11.0 kB]
Get: 12 http://ftp.us.debian.org/debian unstable/main Translation-en
2018-09-01-0208.01.pdiff [1,013 B]
Get: 13 http://ftp.us.debian.org/debian unstable/main amd64 Packages
2018-09-01-1408.47.pdiff [11.0 kB]
Get: 14 http://ftp.us.debian.org/debian unstable/main Translation-en
2018-09-01-1408.47.pdiff [693 B]
Get: 15 http://ftp.us.debian.org/debian unstable/main Translation-en
2018-09-01-1408.47.pdiff [693 B]
Fetched 368 kB in 3s (116 kB/s)


Current status: 0 (+0) broken, 10 (+8) upgradable, 58957 (-34) new.
There are 3 newly obsolete packages: linux-image-4.16.0-2-amd64,
linux-image-4.17.0-1-amd64, linux-image-4.17.0-2-amd64

user@domain:~$ sudo aptitude -Pvv safe-upgrade
Resolving dependencies...
The following packages will be upgraded:
  aspell-en libidn2-0 libnghttp2-14 libpython2.7 libpython2.7-minimal
libpython2.7-stdlib python2.7
  python2.7-minimal
The following packages will NOT be UPGRADED:
  libsane-common{a} sane-utils{a}
8 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 5,452 kB of archives. After unpacking 136 kB will be used.
Do you want to continue? [Y/n/?] n
Abort.

user@domain:~$ sudo aptitude -Pvv full-upgrade
The following NEW packages will be installed:
  libsane1{ab}
The following packages will be upgraded:
  aspell-en libidn2-0 libnghttp2-14 libpython2.7 libpython2.7-minimal
libpython2.7-stdlib
  libsane-common python2.7 python2.7-minimal sane-utils
10 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,480 kB of archives. After unpacking 8,568 kB will be used.
The following packages have unmet dependencies:
 libsane1 : Conflicts: libsane (< 1.0.27-1~) but 1.0.25-4.1 is installed
 libsane : Depends: libsane-common (= 1.0.25-4.1) but 1.0.27-1 is to be
installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) libsane-common [1.0.25-4.1 (now, unstable)]
2) libsane1 [Not Installed]
3) sane-utils [1.0.25-4.1 (now)]

Accept this solution? [Y/n/q/?] Y
The following packages will be upgraded:
  aspell-en libidn2-0 libnghttp2-14 libpython2.7 libpython2.7-minimal
libpython2.7-stdlib python2.7
  python2.7-minimal
The following packages will 

Re: sid upgrade problem

[Ben Caradoc-Davies]

On 01/09/2018 15:14, Default User wrote:

On Fri, Aug 31, 2018, 21:00 Ben Caradoc-Davies  wrote:

On 30/08/2018 07:18, Ben Caradoc-Davies wrote:

On 30/08/2018 03:46, Default User wrote:

The following packages have unmet dependencies:
   libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
   libsane : Depends: libsane-common (= 1.0.25-4.1) but
1.0.27-1~experimental6 is to be installed

[...]

I always choose "Y".  I keep waiting for the situation to resolve

itself,

but it never does.
Insight?

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

sane-backends 1.0.27-1 (the source package) was just uploaded and should
soon be available on sid:
https://tracker.debian.org/news/984005/accepted-sane-backends-1027-1-source-into-unstable/
This upload (supposedly) fixes #905913 and so should resolve the upgrade
problem.


Hi, Ben.
Thanks for the heads-up.
I'll be watching.


I just updated to 1.0.27-1 and my scanner still works (Brother 
MFC-L2740DW over WiFi network). Note that libsane is removed and 
replaced with libsane1. Package manager insistence on removing libsane 
is by design.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: sid upgrade problem

[Default User]

On Fri, Aug 31, 2018, 21:00 Ben Caradoc-Davies  wrote:

> On 30/08/2018 07:18, Ben Caradoc-Davies wrote:
> > On 30/08/2018 03:46, Default User wrote:
> >> The following packages have unmet dependencies:
> >>   libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
> >>   libsane : Depends: libsane-common (= 1.0.25-4.1) but
> >> 1.0.27-1~experimental6 is to be installed
> [...]
> >> I always choose "Y".  I keep waiting for the situation to resolve
> itself,
> >> but it never does.
> >> Insight?
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905913
>
> sane-backends 1.0.27-1 (the source package) was just uploaded and should
> soon be available on sid:
>
> https://tracker.debian.org/news/984005/accepted-sane-backends-1027-1-source-into-unstable/
>
> This upload (supposedly) fixes #905913 and so should resolve the upgrade
> problem.
>
> Kind regards,
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>



Hi, Ben.
Thanks for the heads-up.
I'll be watching.

Re: sid upgrade problem

[Ben Caradoc-Davies]

On 30/08/2018 07:18, Ben Caradoc-Davies wrote:

On 30/08/2018 03:46, Default User wrote:

The following packages have unmet dependencies:
  libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
  libsane : Depends: libsane-common (= 1.0.25-4.1) but
1.0.27-1~experimental6 is to be installed

[...]

I always choose "Y".  I keep waiting for the situation to resolve itself,
but it never does.
Insight?

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


sane-backends 1.0.27-1 (the source package) was just uploaded and should 
soon be available on sid:

https://tracker.debian.org/news/984005/accepted-sane-backends-1027-1-source-into-unstable/

This upload (supposedly) fixes #905913 and so should resolve the upgrade 
problem.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: sid upgrade problem

[Default User]

On Wed, Aug 29, 2018, 15:19 Ben Caradoc-Davies  wrote:

> On 30/08/2018 03:46, Default User wrote:
> > Running sid (Debian Unstable).
> > For several weeks, one particular update seems to be stalled. All other
> > updates work as normal:
> > user@domain:~$ sudo aptitude -Pvv full-upgrade
> > [sudo] password for default:
> > The following NEW packages will be installed:
> >libsane1{ab}
> > The following packages will be upgraded:
> >libsane-common sane-utils
> > 2 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 3,028 kB of archives. After unpacking 8,432 kB will be used.
> > The following packages have unmet dependencies:
> >   libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
> >   libsane : Depends: libsane-common (= 1.0.25-4.1) but
> > 1.0.27-1~experimental6 is to be installed
> > The following actions will resolve these dependencies:
> >   Keep the following packages at their current version:
> > 1) libsane-common [1.0.25-4.1 (now, unstable)]
> > 2) libsane1 [Not Installed]
> > 3) sane-utils [1.0.25-4.1 (now)]
> > Accept this solution? [Y/n/q/?]
> > I always choose "Y".  I keep waiting for the situation to resolve itself,
> > but it never does.
> > Insight?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905913
>
> Kind regards,
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
>
>
>

Hi, Ben!

Thanks for the pointer to bug information regarding this situation.

Now we just wait.

: )

Re: sid upgrade problem

[Ben Caradoc-Davies]

On 30/08/2018 03:46, Default User wrote:

Running sid (Debian Unstable).
For several weeks, one particular update seems to be stalled. All other
updates work as normal:
user@domain:~$ sudo aptitude -Pvv full-upgrade
[sudo] password for default:
The following NEW packages will be installed:
   libsane1{ab}
The following packages will be upgraded:
   libsane-common sane-utils
2 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,028 kB of archives. After unpacking 8,432 kB will be used.
The following packages have unmet dependencies:
  libsane1 : Breaks: libsane (< 1.0.27-1) but 1.0.25-4.1 is installed
  libsane : Depends: libsane-common (= 1.0.25-4.1) but
1.0.27-1~experimental6 is to be installed
The following actions will resolve these dependencies:
  Keep the following packages at their current version:
1) libsane-common [1.0.25-4.1 (now, unstable)]
2) libsane1 [Not Installed]
3) sane-utils [1.0.25-4.1 (now)]
Accept this solution? [Y/n/q/?]
I always choose "Y".  I keep waiting for the situation to resolve itself,
but it never does.
Insight?


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

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Sid: please fix dependences of nfs-common

[Marco d'Itri]

On Aug 20, Michael Stone  wrote:

> This should probably actually be in the rpcbind package rather than
> nfs-common. Once upon a time, when rpcbind was still portmap, it was
> actually part of netbase so a dependency was unnecessary. But rpcinfo is
And after my slimming cure nowadays netbase is just four small 
configuration files: it has important priority, but it should be 
upgraded to required since a lot of software does not depends on it but 
will break without it.

-- 
ciao,
Marco


signature.asc
Description: PGP signature