Re: Need Support on Debian10 Linux Kernel Upgrade

[Balasubramanian Ravuthan]

Hi Dan,

Thanks for your reply. We need few more information.


  1.  Debian 10 Buster is not released with Linux Kernel 5.10 ; That means We 
cant upgrade Kernel 5.10 with Debian 10? - Please confirm.
  2.
  3.  In order to upgrade Linux Kernel to 5.10 means we have to install Debian 
11 BullsEye. Please  Confirm.
  4.
  5.  What will be the impact for upgrading Debian 10 with Kernel 4.19 to 
Debian 11 with Kernel 5.10.

Thanks in advance,

Regards,
Bala

From: Dan Ritter 
Sent: Thursday, December 16, 2021 9:05 PM
To: Balasubramanian Ravuthan 
Cc: debian-user@lists.debian.org 
Subject: Re: Need Support on Debian10 Linux Kernel Upgrade

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Balasubramanian Ravuthan wrote:
>
>  We are looking support from you on the Linux Kernel upgrade on  Debian 10.
>
> We are currently using Debian10 Buster Linux Kernel 4.19 version and trying 
> to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact 
> on this upgrading.
>
> In other words, what are the things will get affected if we do kernel upgrade.

Buster was not released with a 5.10 kernel. A 5.10 kernel came
with Bullseye, Debian 11. Are you getting this from backports?

In general, Linus is pretty flexible about what kernels are
being used. The difference will be that the 5 series presumably
has fixed some old bugs, introduced some new bugs, and some
things will be faster or slower. Overall, more hardware is
supported, but if everything was working well with 4.19, then
there's no immediate reason to suspect it won't work with 5.10.

For more details, you're going to have to ask a more specific
question.

-dsr-
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: IPv4 specific issue with USB tethering between my Debian laptop and my phone

[Tim Woodall]

On Fri, 17 Dec 2021, Vincent Lefevre wrote:


Dan Ritter wrote:

ip link set USBNET0 mtu 1450, or something like that. I don't
know NetworkManager's syntax for that; random googling suggests
that they at least had a historical problem with not being able
to set MTU on anything other than a pure ethernet or wifi link,
but perhaps they've solved that?


"ip link" works on its side. I can see with wireshark that something
like "ip link set usb0 mtu 1300" is honored, but this doesn't solve
the problem (I've tried various values from 1000 to 1450).

Note that I could also see with wireshark that the iptables rules
with --clamp-mss-to-pmtu did not change the packet lengths.



Does this happen on any connection or just some?

You said you could reproduce using ssh? Does that mean you can run
wireshark on both ends and see which packet is getting lost?

Did you try setting both mtu on the interface to something smallish plus
--clamp-mss-to-pmtu?


I'm pretty sure all ipv4 over mobile (which I think is what you are
testing) depends on NAT. So my other guess of a dodgy NAT device isn't
impossible. IIRC your ping tests suggested that ipv4 is being tunnelled
in ipv6

Re: 8 -> 9 update changing things

[Charles Curley]

On Thu, 16 Dec 2021 19:49:36 -0500
"Roy J. Tellason, Sr."  wrote:

> > You don't do regular backups?
> > 
> > I recommend them.  
> 
> Configuring Amanda is on my list,  here.

Good. Perhaps more to think about than you want. ...
https://charlescurley.com/blog/posts/2019/Nov/02/backups-on-linux/

-- 
Does anybody read signatures any more?

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

Re: changed file while editing

[David Christensen]

On 12/16/21 10:04 AM, mick crane wrote:

On 2021-12-11 18:58, David Christensen wrote:


When a computer gets to the point that it is doing weird things that I
cannot understand, troubleshoot, or fix, I download the OS installer
of choice, burn it to USB, make sure my configuration files are
checked in to CVS, backup my data, remove the system disk, insert a
blank system disk, do a fresh install, take an image of the system
disk, boot, check out the old configuration files to a side directory,
edit the new configuration files (rebooting and testing as I proceed),
and restore data.  This is the only way I know to get a "clean", and
hopefully reliable, OS image.


lovely.

I've used vi for the last 3 days and it's happened once instead of 
multiple times.



Assuming the bug is in Debian, it's not Nano and it's not Vi.  But Nano 
somehow increases the bug frequency.  And, the intermittent nature leads 
me to believe it is a race condition.  So, it's likely to be down deep 
(e.g. IRQ device driver).



I'd love it to be user error, well to know what the use error is, but 
I've been using basic editing with vi/vim for years and this never 
happened before.
Is it at all possible that running Perl executable file somehow shares 
the same memory as same file opened in vi and they get jumbled?



I seriously doubt it.


I don't understand why the error is random words from elsewhere in the 
file get randomly inserted as opposed to garbage.



My guess is that the bug is somewhere in the keyboard and mouse input 
stacks.




I'm inclined to get another PC and see if it still does it.



Whatever you can do to isolate the problem, go for it.


Are using a KVM switch?  I have an IOGEAR GCS78KIT.  It has a power 
adapter, but can obtain power from any connected computer that provides 
power.  Several of my computers do, so the KVM switch is power cycled 
only infrequently (when I take the time to disconnect everything, wait 2 
minutes, then reconnect everything).  Over long periods (months? 
years?), it can start producing weird UI bugs.  I need to bypass it, 
connect my keyboard, monitor, and mouse directly to a computer with an 
OS/ applications disk under test, use it for an hour or more, see if the 
problems exhibit, try another disk and/or machine, etc.



Another potential problem is my PS/2 to USB adapters -- IOGEAR GUC100KM 
(older) and GUC10KM (newer).  I have not seen the random UI weirdness 
with these, but the newer model tends to lose the connection when the 
computer powers down (e.g. keyboard and mouse do not work on next boot; 
I must disconnect the adapter from everything and hot-plug everything to 
the booted computer).



David

Re: 8 -> 9 update changing things

[Roy J. Tellason, Sr.]

On Thursday 16 December 2021 06:00:19 pm Dan Ritter wrote:
> Roy J. Tellason, Sr. wrote: 
> > On Thursday 16 December 2021 02:49:17 pm Andrew M.A. Cater wrote:
> > > 
> > > I would seriously suggest upgrading from 9 to at least 10. You might sort 
> > > out some of the issues but, more
> > > importantly, will be moving up to a better supported system
> > 
> 
> > I'll get there.  But upgrading involves me copying a whole pile of
> > stuff over to my server, including some really large files that are
> > involved in Virtualbox and the one snapshot I have, and then figuring
> > out a whole mess of detailed stuff that I need to do to make the
> > upgrade happen.  Last time it was something like 3 or 4 days before I
> > was back to anything remotely resembling normal, and I'm not looking
> > forward to the next time (or two).
> 
> You don't do regular backups?
> 
> I recommend them.

Configuring Amanda is on my list,  here.
 
> I can also vouch for a couple of facts:
> 
> - every version of Debian stable has been easier to upgrade to than the last.
> 
> - you do about half the amount of work by upgrading from 9 to 10 and then 
> immediately to 11, and then figuring out what
>   needs to change, as you would if you tried to figure out changes for each 
> upgrade.

Yeah,  but I'm really getting to know a lot about the details of this setup in 
the process.  :-)

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: realtek bluetooth puzzle

[deloptes]

Jude DaShiell wrote:

> I have firmware-realtek installed for wireless devices and that's all
> debian offers.

but sometime if it is a new device on the market you may need either to wait
for the firmware to go to the package or you can download from vendor or
you can extract from the windows package

Anyway - by price of BT USB dongles around 12,- it is perhaps worth to
return and find a supported one

Before doing this perhaps try on another linux if available

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

Re: realtek bluetooth puzzle

[deloptes]

Jude DaShiell wrote:

> hcitool and rfkill list showed nothing, according to them the device isn't
> there yet.  I might be able to get this going with usb_modeswitch but need
> a product identifier and another item to do that.

based on the product name, find what is the chip inside and ask google

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

Re: IPv4 specific issue with USB tethering between my Debian laptop and my phone

[Vincent Lefevre]

Dan Ritter wrote:
> ip link set USBNET0 mtu 1450, or something like that. I don't
> know NetworkManager's syntax for that; random googling suggests
> that they at least had a historical problem with not being able
> to set MTU on anything other than a pure ethernet or wifi link,
> but perhaps they've solved that?

"ip link" works on its side. I can see with wireshark that something
like "ip link set usb0 mtu 1300" is honored, but this doesn't solve
the problem (I've tried various values from 1000 to 1450).

Note that I could also see with wireshark that the iptables rules
with --clamp-mss-to-pmtu did not change the packet lengths.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: realtek bluetooth puzzle

[Jude DaShiell]

I have firmware-realtek installed for wireless devices and that's all
debian offers.


On Fri, 17 Dec 2021, deloptes wrote:

> Thomas Schmitt wrote:
>
> > I find its home page somehow confusing
> > https://www.draisberghof.de/usb_modeswitch/
> > But the web says that it is supposed to work automagically for known
> > devices.
>
> may be OP is needing the firmware and this mode is a fallout mode. It is
> strange if it would need usb_modeswitch.
> Also it is strange that it does not try anything else first.
>
>

Re: realtek bluetooth puzzle

[Jude DaShiell]

hcitool and rfkill list showed nothing, according to them the device isn't
there yet.  I might be able to get this going with usb_modeswitch but need
a product identifier and another item to do that.


On Fri, 17 Dec 2021, deloptes wrote:

> Jude DaShiell wrote:
>
> > Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth
> > service being skipped.
> > Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service
> > 'org.bluez': timed out (service_start_timeout=25000ms)
> > Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22
> > Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager
> > initialized
> > Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized
> > Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized
> > Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized
>
> it says it can not start bluetooth, but HCI device and connection manager
> initialized, so what does hcitool said?
> and why is pulseaudio involved - perhaps you need
> pulseaudio-module-bluetooth and reboot to be sure it all setup properly
>
> also what said rfkill?
>
>

Re: realtek bluetooth puzzle

[deloptes]

Jude DaShiell wrote:

> Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth
> service being skipped.
> Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service
> 'org.bluez': timed out (service_start_timeout=25000ms)
> Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22
> Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager
> initialized
> Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized
> Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized
> Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized

it says it can not start bluetooth, but HCI device and connection manager
initialized, so what does hcitool said?
and why is pulseaudio involved - perhaps you need
pulseaudio-module-bluetooth and reboot to be sure it all setup properly

also what said rfkill?

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

Re: realtek bluetooth puzzle

[deloptes]

Thomas Schmitt wrote:

> I find its home page somehow confusing
> https://www.draisberghof.de/usb_modeswitch/
> But the web says that it is supposed to work automagically for known
> devices.

may be OP is needing the firmware and this mode is a fallout mode. It is
strange if it would need usb_modeswitch.
Also it is strange that it does not try anything else first.

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

Re: 8 -> 9 update changing things

[Dan Ritter]

Roy J. Tellason, Sr. wrote: 
> On Thursday 16 December 2021 02:49:17 pm Andrew M.A. Cater wrote:
> > 
> > I would seriously suggest upgrading from 9 to at least 10. You might sort 
> > out some of the issues but, more
> > importantly, will be moving up to a better supported system
> 

> I'll get there.  But upgrading involves me copying a whole pile of
> stuff over to my server, including some really large files that are
> involved in Virtualbox and the one snapshot I have, and then figuring
> out a whole mess of detailed stuff that I need to do to make the
> upgrade happen.  Last time it was something like 3 or 4 days before I
> was back to anything remotely resembling normal, and I'm not looking
> forward to the next time (or two).

You don't do regular backups?

I recommend them.

I can also vouch for a couple of facts:

- every version of Debian stable has been easier to upgrade to
  than the last.

- you do about half the amount of work by upgrading from 9 to
  10 and then immediately to 11, and then figuring out what
  needs to change, as you would if you tried to figure out
  changes for each upgrade.

-dsr-

Re: realtek bluetooth puzzle

[Jude DaShiell]

firmware-realtek has been installed a while ago.  I'm probably going to
have to run usb-modeswitch against the device.


On Thu, 16 Dec 2021, Jude DaShiell wrote:

>
>
> On Thu, 16 Dec 2021, deloptes wrote:
>
> > Jude DaShiell wrote:
> >
> > > No Linux firmware came on the disk only windows files.  To that extent I
> > > checked.  On debian does a way exist to check devices for missing
> > > firmware?
> > >
> >
> > in the log file journalctl or /var/log/syslog, after plugging in the usb (I
> > am not sure if it is usb stick, because you mentioned card, but anywa)
> > When bluetooth initializes you should see if it is looking for firmware and
> > in your case not loading it.
> >
> > It could be that you have to install linux firmware packages free or not
> > free (depends on the chip you have on the device)
> >
> > You could also check output of command rfkill list and see if hci0 device
> > exists and is blocked
> >
> > The other thing use hcitool command (hcitool dev) and see if it shows hci
> > device - I have seen some cases that hciattach needs to be run to enable
> > the device.
> Does any of this make sense?  This is journalctl output:
> 16:56:28 taf bluetoothd[1157]: Starting SDP server
> Dec 16 16:56:28 taf bluetoothd[1157]: Bluetooth management interface 1.18
> initialized
> Dec 16 16:56:40 taf bluetoothd[1157]: Terminating
> Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0
> matched rules; type="error", sender=":1.9" (uid=1000 pid=817
> comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
> interface="(unset)" member="(unset)" error
> name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0"
> destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ")
> Dec 16 16:56:40 taf bluetoothd[1157]: Stopping SDP server
> Dec 16 16:56:40 taf bluetoothd[1157]: Exit
> Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0
> matched rules; type="error", sender=":1.9" (uid=1000 pid=817
> comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
> interface="(unset)" member="(unset)" error
> name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0"
> destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ")
> Dec 16 17:07:06 taf NetworkManager[1764]:   [1639692426.3763]
> Loaded device plugin: NMBluezManager
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so)
> Dec 16 17:09:50 taf NetworkManager[476]:   [1639692590.3550] Loaded
> device plugin: NMBluezManager
> (/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so)
> Dec 16 17:10:08 taf dbus-daemon[475]: [system] Activating via systemd:
> service name='org.bluez' unit='dbus-org.bluez.service' requested by
> ':1.15' (uid=1000 pid=868 comm="/usr/bin/pulseaudio --daemonize=no
> --log-target=jo")
> Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth
> service being skipped.
> Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service
> 'org.bluez': timed out (service_start_timeout=25000ms)
> Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22
> Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager
> initialized
> Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized
> Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized
> Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized
>
> > >
>
>

Re: IPv4 specific issue with USB tethering between my Debian laptop and my phone

[Vincent Lefevre]

On 2021-12-15 17:01:54 +, Tim Woodall wrote:
> On Wed, 15 Dec 2021, Vincent Lefevre wrote:
> > I've tried
> > 
> >  iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS 
> > --clamp-mss-to-pmtu
> > 
> > and
> > 
> >  iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1024
> > 
> I think you possibly want -A OUTPUT rules too.

This doesn't change anything.

> And also ip6tables rules.

There are no issues with IPv6.

> If you're going via a firewall then you (usually) only need -A FORWARD
> But if you're trying to configure it on your laptop itself you probably
> need -A OUTPUT (and possibly -A INPUT).

I can't use -A INPUT:

# iptables -A INPUT -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
iptables v1.8.7 (nf_tables):  RULE_APPEND failed (Invalid argument): rule in 
chain INPUT

And similar error with "-I INPUT":

iptables v1.8.7 (nf_tables):  RULE_INSERT failed (Invalid argument): rule in 
chain INPUT

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: realtek bluetooth puzzle

[Jude DaShiell]

On Thu, 16 Dec 2021, deloptes wrote:

> Jude DaShiell wrote:
>
> > No Linux firmware came on the disk only windows files.  To that extent I
> > checked.  On debian does a way exist to check devices for missing
> > firmware?
> >
>
> in the log file journalctl or /var/log/syslog, after plugging in the usb (I
> am not sure if it is usb stick, because you mentioned card, but anywa)
> When bluetooth initializes you should see if it is looking for firmware and
> in your case not loading it.
>
> It could be that you have to install linux firmware packages free or not
> free (depends on the chip you have on the device)
>
> You could also check output of command rfkill list and see if hci0 device
> exists and is blocked
>
> The other thing use hcitool command (hcitool dev) and see if it shows hci
> device - I have seen some cases that hciattach needs to be run to enable
> the device.
Does any of this make sense?  This is journalctl output:
16:56:28 taf bluetoothd[1157]: Starting SDP server
Dec 16 16:56:28 taf bluetoothd[1157]: Bluetooth management interface 1.18
initialized
Dec 16 16:56:40 taf bluetoothd[1157]: Terminating
Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.9" (uid=1000 pid=817
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0"
destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ")
Dec 16 16:56:40 taf bluetoothd[1157]: Stopping SDP server
Dec 16 16:56:40 taf bluetoothd[1157]: Exit
Dec 16 16:56:40 taf dbus-daemon[453]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.9" (uid=1000 pid=817
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
interface="(unset)" member="(unset)" error
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0"
destination=":1.17" (uid=0 pid=1157 comm="bluetoothd ")
Dec 16 17:07:06 taf NetworkManager[1764]:   [1639692426.3763]
Loaded device plugin: NMBluezManager
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so)
Dec 16 17:09:50 taf NetworkManager[476]:   [1639692590.3550] Loaded
device plugin: NMBluezManager
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.0/libnm-device-plugin-bluetooth.so)
Dec 16 17:10:08 taf dbus-daemon[475]: [system] Activating via systemd:
service name='org.bluez' unit='dbus-org.bluez.service' requested by
':1.15' (uid=1000 pid=868 comm="/usr/bin/pulseaudio --daemonize=no
--log-target=jo")
Dec 16 17:10:08 taf systemd[1]: Condition check resulted in Bluetooth
service being skipped.
Dec 16 17:10:33 taf dbus-daemon[475]: [system] Failed to activate service
'org.bluez': timed out (service_start_timeout=25000ms)
Dec 16 17:20:36 taf kernel: Bluetooth: Core ver 2.22
Dec 16 17:20:36 taf kernel: Bluetooth: HCI device and connection manager
initialized
Dec 16 17:20:36 taf kernel: Bluetooth: HCI socket layer initialized
Dec 16 17:20:36 taf kernel: Bluetooth: L2CAP socket layer initialized
Dec 16 17:20:36 taf kernel: Bluetooth: SCO socket layer initialized

> >

Re: realtek bluetooth puzzle

[Thomas Schmitt]

Hi,

Jude DaShiell wrote:
> [10200.545324] usb 3-1: Product: DISK
> [10200.545329] usb 3-1: Manufacturer: Realtek
> [10200.545637] usb-storage 3-1:1.0: USB Mass Storage device detected
> [10200.546006] scsi host6: usb-storage 3-1:1.0
> [10201.560487] scsi 6:0:0:0: CD-ROMRealtek  Driver Storage 1.00 
> PQ: 0 ANSI: 0 CCS
> [10201.566607] sr 6:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy
> [10201.588298] sr 6:0:0:0: Attached scsi CD-ROM sr1

Looks like the device is emulating a CD-ROM which offers driver files
to MS-Windows for automatic installation. The web says that this happens
when the device does not get the right answers from the operating system
which indicate that the drivers are already installed.

An Archlinux thread proposes to use a program named usb_modeswitch to get
the device out of this mode
  https://bbs.archlinux.org/viewtopic.php?id=228195
Debian has it in a package
  https://tracker.debian.org/pkg/usb-modeswitch

I find its home page somehow confusing
  https://www.draisberghof.de/usb_modeswitch/
But the web says that it is supposed to work automagically for known
devices.


Have a nice day :)

Thomas

Re: changed file while editing

[mick crane]

On 2021-12-16 20:35, Greg Wooledge wrote:

Be specific and detailed about what you do.  Be clear in how you 
describe

things.  Otherwise, we can't help you.


I try my best
--
Key ID4BFEBB31

Re: Fwd: Returned mail: see transcript for details

[gene heskett]

On Thursday, December 16, 2021 4:04:16 PM EST Greg Wooledge wrote:
> On Thu, Dec 16, 2021 at 03:10:17PM -0500, gene heskett wrote:
> >- The following addresses had permanent fatal errors -
> > 
> > 
> > 
> >- Transcript of session follows -
> > 
> > ... Deferred: Connection refused by lists.apple.com.
> > Message could not be delivered for 5 days
> > Message will be deleted from queue
> 
> This is definitely an error on the CUPS/Apple end, not your end.
> (Assuming of course that c...@cups.org was the correct address in the
> first place.  I know nothing about this particular list.)
> 
> .
Well, as a way to check my subscription status, I  had it send me my forgotten 
passwd, which it did just fine. And correct.

Right hand, meet left hand, its obvious you are strangers.

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

Re: 8 -> 9 update changing things

[Roy J. Tellason, Sr.]

On Thursday 16 December 2021 02:49:17 pm Andrew M.A. Cater wrote:
> On Thu, Dec 16, 2021 at 02:35:43PM -0500, Roy J. Tellason, Sr. wrote:
> > I'd posted about my update a while back,  and while some folks were 
> > encouraging me to go all the way to 11 since it's the current version,  
> > my thinking has been to see how things are working,  what's changed,  
> > what broke,  etc. and deal with all of that before I continue on in the 
> > update process.
> > 
> > Some of the things I'm dealing with are:
> > 
> > 1. An annoying blue dot showed up in my taskbar.  
> > Right-clicking on this gave me an option to "quit",  which I would do,  
> > and then within a few seconds it would come right back again!  I finally 
> > tracked this down to being "KDEaccessible",  which I've done nothing to 
> > invoke and don't know why the upgrade put that in there.  I solved the 
> > problem by using synaptic to uninstall the package,  since I have no use 
> > for it.
> > 
> 
> This one is solved for the moment, then.

Yeah,  but why the heck did this get turned on in the first place?  Or even 
installed?
 
> > 2. My virtual (older) Slackware virtualbox install is seeing a few issues.
> > One of them is that there is apparently a screensaver kicking in after 
> > some extended period of time.  I can't find any place where this is 
> > enabled,  to turn it off.  I wasn't using one before and don't want one 
> > now.  Suggestions?
> 
> XFCE desktop: if this is blanking the screen, try checking for power settings.
> If it's an _actual_ screensaver with patterns - check to see what screen
> saving/locking programs come by default.

Under Slackware it's a very old version of KDE,  which I much prefer to the 
newer stuff.  When I select screen saver from the k menu,  it acts like it's 
loading for a bit and then stops,  with nothing loaded.  When I open the 
control center I can select screen saver in there,  under appearance and 
themes,  and blank screen is one of the choices besides all of the graphic 
ones,  but "start automatically" is NOT checked.  Under power control the only 
option seems to be "laptop battery" and selecting a number of different tabs 
tells me that there seems to be "a partial ACPI installation",  but nothing 
seems to be activated in there either.  I can't see anything else in there that 
seems applicable,  even after poking all through the k-menu.

The other thing that's changed is that this is a different (and newer) version 
of Virtualbox,  which in fact has been recently upgraded even further.  I've 
poked around in all of the options for that,  too,  and don't see anything 
applicable to this.  And regarding ACPI,  I have used the ACPI shutdown and it 
does work.  Nothing else in there about that.

> > 3. Also under the Slackware virtualbox sound has quit working.  
> > When I boot it,  I get a message that says "Host audio backend (PulseAudio) 
> > initialization has failed. Selecting the NULL audio backend with the 
> > consequence that no sound is audible."  I'm not sure what changed here 
> > either.  On the host (Debian) side,  audio works fine for,  ferinstance,  
> > playing a youtube video.  But for some things I want to be able to play 
> > audio under Slackware as well.  I found an item in the Xfce applications 
> > menu under Multimedia that says "Pulseaudio Volume Control" and when I 
> > hit that I get a smallish popup window with no apparent content other 
> > than "Establishing connection to PulseAudio, please wait..." and then 
> > nothing happens for a good long while now.  Suggestions?
> > 
> 
> How old id the virtualbox version - is there an option for audio passthrough 
> or similar?

The version is pretty recent,  and in fact has been recently updated.  Clicking 
on the about option under help, I see "Version 6.1.3-r148432 (Qt5.7.1).  But 
both this and the above issue were happening before and after the virtualbox 
upgrade,  and only since the Debian upgrade,  which got me to a different 
version of Virtualbox than what I'd been running before.  As far as Virtualbox 
audio settings,  under Devices there are two options under Audio,  one for in 
and one for out,  and when selecting them there's a minor change in the icon 
displayed,  but other than that it's not clear to me what these are supposed to 
do.  I suppose digging into the help might be enlightening.  Except that it's 
not finding the file that it wants to open to display help.  :-(  Their online 
help pointed me at settings,  where I see that audio out and in are enabled but 
it also says "invalid settings detected" on that page,  and I've not a clue yet 
where I might find those...
 
> > 4. There is *something* kicking off around midnight local time that 
> > produces a whole lot of disk activity for a few minutes,  slowing down 
> > whatever else I might be doing at the time.  I've looked at various things 
> > like cron, at,  etc. to see if I can find something in there but no luck
> >  so far.  Suggestions?
> 

re: realtek bluetooth puzzle

[Jude DaShiell]

Havbing removed the device I ran dmesg| wc -l.
Inserting the device I ran dmesg| wc -l again and got a difference of 11
lines.
So dmesg >dmesg.log and tail -11 dmesg.log got me this information.
[10200.545324] usb 3-1: Product: DISK
[10200.545329] usb 3-1: Manufacturer: Realtek
[10200.545637] usb-storage 3-1:1.0: USB Mass Storage device detected
[10200.546006] scsi host6: usb-storage 3-1:1.0
[10201.560487] scsi 6:0:0:0: CD-ROMRealtek  Driver Storage
1.00 PQ: 0 ANSI: 0 CCS
[10201.566607] sr 6:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy
[10201.588298] sr 6:0:0:0: Attached scsi CD-ROM sr1
[10201.721911] usb 3-1: reset high-speed USB device number 6 using
ehci-pci
[10232.215266] usb 3-1: reset high-speed USB device number 6 using
ehci-pci
[10262.935626] usb 3-1: reset high-speed USB device number 6 using
ehci-pci
[10293.655994] usb 3-1: reset high-speed USB device number 6 using
ehci-pci

Re: realtek bluetooth puzzle

[deloptes]

Jude DaShiell wrote:

> No Linux firmware came on the disk only windows files.  To that extent I
> checked.  On debian does a way exist to check devices for missing
> firmware?
> 

in the log file journalctl or /var/log/syslog, after plugging in the usb (I
am not sure if it is usb stick, because you mentioned card, but anywa)
When bluetooth initializes you should see if it is looking for firmware and
in your case not loading it.

It could be that you have to install linux firmware packages free or not
free (depends on the chip you have on the device)

You could also check output of command rfkill list and see if hci0 device
exists and is blocked

The other thing use hcitool command (hcitool dev) and see if it shows hci
device - I have seen some cases that hciattach needs to be run to enable
the device.

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

Re: realtek bluetooth puzzle

[Christian Britz]

On 2021-12-16 21:45 UTC+0100, Jude DaShiell wrote:
> No Linux firmware came on the disk only windows files.  To that extent I
> checked.  On debian does a way exist to check devices for missing
> firmware?
> 
> 
> On Thu, 16 Dec 2021, deloptes wrote:
> 
>> Jude DaShiell wrote:
>>
>>> So in reality this may actually not be a card
>>> The disk that came with this claimed it was an realtek-0179 device if
>>> memory serves.
>>
>> did you check firmware if required - do you have it installed?
>>
>>
> 

You might have to install some non-free firmware from Debian repository.
If it is not yet enabled, edit file /etc/apt/sources.list and edit the
lines to look similar like "deb http://deb.debian.org/debian/ bullseye
main non-free contrib"
Then run "apt update". Then install the needed firmware package.

Of course the difficulty is to find out which package you need. A search
for realtek-0179 brings no usefull results on Google. It is strange that
neither lsusb nor lspci bring up usefull information. If it is an USB
device, unplug and plug it in again and watch the output of dmesg for
messages. If it tells you firmware file "ExampleFileName" is missing
then issue command "apt-file search ExampleFileName". It should tell
you, which package to install.

Regards,
Christian

Re: Fwd: Returned mail: see transcript for details

[Greg Wooledge]

On Thu, Dec 16, 2021 at 03:10:17PM -0500, gene heskett wrote:
> 
>- The following addresses had permanent fatal errors -
> 
> 
>- Transcript of session follows -
> ... Deferred: Connection refused by lists.apple.com.
> Message could not be delivered for 5 days
> Message will be deleted from queue

This is definitely an error on the CUPS/Apple end, not your end.
(Assuming of course that c...@cups.org was the correct address in the
first place.  I know nothing about this particular list.)

Re: realtek bluetooth puzzle

[Jude DaShiell]

No Linux firmware came on the disk only windows files.  To that extent I
checked.  On debian does a way exist to check devices for missing
firmware?


On Thu, 16 Dec 2021, deloptes wrote:

> Jude DaShiell wrote:
>
> > So in reality this may actually not be a card
> > The disk that came with this claimed it was an realtek-0179 device if
> > memory serves.
>
> did you check firmware if required - do you have it installed?
>
>

Re: changed file while editing

[Greg Wooledge]

On Thu, Dec 16, 2021 at 06:04:05PM +, mick crane wrote:
> Is it at all possible that running Perl executable file somehow shares the
> same memory as same file opened in vi and they get jumbled?

No.  Each process has its own private memory space.

Even if you WROTE to the file (via perl or any other program), the
editing buffer you've already got opened in vi would not change, until
you explicitly tell vi to re-read the file from disk.

So when you add the notion of perl somehow ACCIDENTALLY writing to a
random file, it's just doubly nonsense.

Your problem description so far has been very hard to understand.  It's
not clear to me WHAT you are seeing, or why you've reached the conclusions
that you've reached.

I would start by trying to identify the LAYER where the error is
occurring.  This could be the X (or Wayland?) display system.  Or the
terminal emulator which uses the display system.  Or the editor which
uses the terminal emulator.  (Hint: it's probably not the editor.)

The first thing I'd do, when I see the problem happen again, would be
to ask the editor to redraw the contents of the terminal.  In vi, this
is done by pressing Ctrl-L while in command mode.  You should see a
very brief flash as the terminal's contents are wiped, and then recreated.

Editors have this command because they run on terminals, and terminals
were traditionally connected via RS-232 serial lines, either hard-wired
inside a building, or with a modem involved.  When a modem is involved,
there is a phenomenon called "line noise" which frequently causes extra
characters to be printed on the terminal wherever the cursor happens to
be.  You can ignore these for a while, but if they start to accumulate,
or if you're especially bothered by them, you just request a screen redraw.

If redrawing the screen within the editor fixes the problem, then the
problem was most likely extra characters that had been written onto the
terminal.  At that point, you can try to discover what wrote them, but
it might not be easy to do so.  Anything with appropriate privileges can
open one of your terminals and write to it.  This would include any program
you're running, but also things like the kernel broadcasting an emergency
message to every terminal.  (I doubt the latter is the case for you, as
you seem to be saying this is a frequent occurrence, and that you don't
recognize the unexpected content.  Maybe.  It's hard to understand what
you're saying.)

If redrawing the screen doesn't do anything, then I'd try to figure out
the nature of the unexpected content.  Is it whole characters?  Like,
could you -- in theory -- run commands from a different terminal which
would move the cursor and write characters on the mangled terminal, and
get the results that you see?

Or is it misplaced pixels, rather than whole characters?  Do you see pieces
of window manager borders, parts of characters, and stuff like that?

If you're seeing pixel-level stuff, that points toward an issue at the X
or Wayland level, possibly bogus drivers or firmware.  Or even bad hardware.

If it's misplaced whole characters, which are not fixed by redrawing the
screen within the editor, then that sounds like a bug in your terminal
emulator.

Another simple test to perform would be to MOVE the window around.  Does
this change the unexpected content, or does it move around with the window?

Be specific and detailed about what you do.  Be clear in how you describe
things.  Otherwise, we can't help you.

Re: all of a sudden I have no sound

[deloptes]

Jude DaShiell wrote:

> debian-accessibility is interested in replacing pulseaudio with pipewire
> and I can understand why!  Not saying pipewire has these essential
> features but pulseaudio has been a p.i.t.a. since I've had it on any
> hardware I've used.  Whenever possible I avoid installing pulseaudio or
> remove it from a system that installs it automatically for sanity
> purposes.

as of approx version 11 of pulseaudio, there are virtually no issues, so you
may revisit your decision now.

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

Re: realtek bluetooth puzzle

[deloptes]

Jude DaShiell wrote:

> So in reality this may actually not be a card
> The disk that came with this claimed it was an realtek-0179 device if
> memory serves.

did you check firmware if required - do you have it installed?

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

Re: realtek bluetooth puzzle

[Jude DaShiell]

On Thu, 16 Dec 2021, Christian Britz wrote:

>
>
> On 2021-12-16 20:01 UTC+0100, Dan Ritter wrote:
> > Jude DaShiell wrote:
> >> bnep   20480  0
> >> bluetooth 483328  1 bnep
> >> ecdh_generic   16384  1 bluetooth
> >> ecc40960  1 ecdh_generic
> >>
> >> That's relevant output from lsmod.
> >> If I run inxi -E
> >> that returns no bluetooth data available.
> >> This is supposed to be linux-compatible.
> >> Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after
> >> starting bluetooth adapters gets me nowhere.
> >> Has anyone got one of these cards from WalMart going and can give me some
> >> ideas for getting this up and working or find out if it can't work so I
> >> can trash it and buy a different card from WalMart?
> >
> > Anything interesting in lsusb?
> >
> > -dsr-
> >
>
> Or in the syslog?
> (If it is really a "card", Jude should issue lspci.)
>
I ran lspci and no mention of bluetooth happened.  dmesg.log output
returned:
[  402.931062] Bluetooth: Core ver 2.22
[  402.931086] NET: Registered PF_BLUETOOTH protocol family
[  402.931088] Bluetooth: HCI device and connection manager initialized
[  402.931092] Bluetooth: HCI socket layer initialized
[  402.931094] Bluetooth: L2CAP socket layer initialized
[  402.931098] Bluetooth: SCO socket layer initialized
[  402.942727] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  402.942733] Bluetooth: BNEP filters: protocol multicast
[  402.942741] Bluetooth: BNEP socket layer initialized


So in reality this may actually not be a card
The disk that came with this claimed it was an realtek-0179 device if
memory serves.
The Linux instructions were in an .mp4 file that was inaudible on my
system.
>

Fwd: Returned mail: see transcript for details

[gene heskett]

See attached, the final reject of my attempt to post to the cups list, which I 
am subscribed to.

Where did I mess it up?

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 
--- Begin Message ---
The original message was received at Sat, 11 Dec 2021 11:24:12 -0800
from ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]

   - The following addresses had permanent fatal errors -


   - Transcript of session follows -
... Deferred: Connection refused by lists.apple.com.
Message could not be delivered for 5 days
Message will be deleted from queue
Reporting-MTA: dns; ma1-aaemail-dr-lapp02.apple.com
Arrival-Date: Sat, 11 Dec 2021 11:24:12 -0800

Final-Recipient: RFC822; cups@cups.org
Action: failed
Status: 4.4.7
Remote-MTA: DNS; lists.apple.com
Last-Attempt-Date: Thu, 16 Dec 2021 11:40:48 -0800
--- Begin Message ---
Having my main drive take a long walk off a short pier last week while running
stretch, I am now on bullseye, but the driverless is also featureless so I went
to brothers site and installed their drivers. From this machine it works 
although
I only did the test page which is not duplex. Had to reconfigure cups a couple
times to get it shared to the rest of the machines on my home network.


Then, intending to do some reconfiguring of one of my cnc drivers, I fired up my
net and logged into it, then finally managed to get a printout of the file I'm
going to work on. Normally 19 pages in landscape, duplex format. From the 

bottom tray as I usually have 50 cents a sheet photo paper in the top tray.


On a stretch install, a 3 minute job. But from a buster machine over a cat6 

pipe, it was a 40 minute, non duplex job I had to put copy paper in the top
tray to do, and its not only single sided, it started with the last page.


On stretch, that would have been a 3 minute job, page 1 face down on the
output tray, duplex all the way.


How do I fix this comedy of errors? 



Thank you.
Gene--- End Message ---
--- End Message ---

Re: Instalar Debian con UEFI

[Leonardo Marín]

El jue, 16 dic 2021 a las 16:17, Jerigondor ()
escribió:

>
> El 16/12/2021 a las 19:28, Leonardo Marín escribió:
>
>
>
> El jue, 16 dic 2021 a las 14:15, Jerigondor ()
> escribió:
>
>>
>> Cuando se me queda la pantalla en negro solo me aparece el cursor arriba
>> a la izquierda. Pero fijo, no parpadea. Y no me permite pasar a otra
>> consola. Está como congelado. Ni Control+Alt+Suprimir ni nada.
>>
> Es lo que normalmente sucede cuando tienes una grafica nvidia y el sistema
> intenta iniciar el video con el driver libre nouveau,
> de entrada tienes una pantalla totalmente negra o un ( _ ) arriba a la
> izquierda como comentas,
>
> por eso te comentaba en el correo anterior que luego de iniciar y estando
> en esa pantalla negra debes intentar con Ctrl+Alt+F2 esto te debería de
> abrir otra terminal donde te pedirá te loguees,
> si eso pasa entonces si tienes un problema con el driver de video y no
> está relacionado con uefi,
>
> Es que ahí radica el problema, que no puedo hacer absolutamente nada. Ni
> Control+Alt+F2, ni nada. Y no puedo entrar como Root, ni como usuario. Así
> no puedo modificar nada.
>
 Entiendo, te diría prueba como ha comentado Javier en modo recovery a ver
si de esa manera funciona,

solo por decir algo más y por si sirve de ayuda,
antes de actualizar (comprar) el desktop y la notebook ya había leído de
esto en varios sitios, lei un monton de cosas pero casi todo iba por los
mismos temas, uefi, secure boot, gpt y mbr, dual boot, y los posibles
problemas que daban al tener windows con linux en el mismo disco, y se me
quedó porque yo de toda la vida nada que ver con uefi,
por lo que instale en discos separados desde el inicio, en el desktop el
disco nvme está con debian y un ssd aparte con windows 10, la notebook
tiene windows 10 en el nvme y en el 2do disco coloqué un ssd con debian,
eso hasta hace poco que compré un nvme de 1tb y le instalé debian y windows
se fue al ssd,

en ambos casos todo está en uefi, en el desktop está activado el secure
boot y activado o desactivado en mi caso da lo mismo,
no selecciono el disco con el menú del grub lo hago con F11 en el desktop y
F9 en la notebook, no sé porque razón anteriormente al moverme entre las
opciones del grub este se congelaba y debía de reiniciar forzosamente, de
esta manera no pasa, y bueno ya prefiero usarlo así antes de pasar la
molestia de que se congele el grub,

entonces aparte de la molestia de hace meses del grub ni un problema
iniciando uno u otro,
saludos.

> en caso de que el problema sea el driver de nouveau esta es la
> configuracion que tengo para evitar que se inicie:
> asumiendo que pudiste iniciar sesion como root desde la consola;
>
> # nano /etc/default/grub
>
> editas la linea como la mostrada abajo para dejarlo de esta manera guardas
> y sales
> GRUB_CMDLINE_LINUX_DEFAULT="quiet nouveau.modeset=0 nvidia-drm.modeset=1"
>
> # nano /etc/modprobe.d/blacklist.conf
>
> agregas las siguientes líneas guardas y sales
> blacklist nouveau
> blacklist lbm-nouveau
> options nouveau modeset=0
> alias nouveau off
> alias lbm-nouveau off
>
> # nano /etc/modprobe.d/nouveau-kms.conf
>
> agregas las siguientes líneas guardas y sales
> options nouveau modeset=0
> options nvidia-drm modeset=1
>
> corres estos 2 comandos para que se reflejen los cambios
> # update-initramfs -u
> # update-grub2
>
> reinicias y de entrada no deberías de tener una pantalla negra sino
> directamente en la línea de comandos (aunque en mi notebook eso no pasa
> solo se queda la pantalla con la info que se muestra de inicio y parece
> colgada),
> si instalas el driver vesa y no tienes nada configurado debería de iniciar
> con el video.
> # apt install xserver-xorg-video-vesa
>
> eso si tienes xor, con wayland no se como sea no lo he usado todavía,
> si logras iniciar con vesa ya luego puedes elegir si instalas el driver de
> nvidia directamente o lo instalas de los repositorios de debian.
>
>
>> Si elijo Recovery mode, me aparece algo mas de informacion. La que
>> aparece en la imagen.
>>
>> https://ibb.co/KsfcC64
>>
>> Pero se bloquea despues de un segundo de arranque, como se puede ver en
>> la imagen. La ultima linea hace referencia a noveau, los drivers libres
>> de Nvidia. Quizas tenga algo que ver con la grafica.
>>
>>
>> Algo mas de informacion:
>>
>> No he conseguido arrancar con un live USB de Ubuntu. Probaré con otras
>> imagenes...
>>
>> Durante la instalacion, me avisa de que no se ha podido cargar firmware
>> no libre. Concretamente rtw88/rtw8822c_fw.bin rtw88/rtw8822c_wow_fw.bin.
>> Pero creo que es firmware de la wifi. He intentado instalar con una
>> imagen de Debian con el firmware non-free, pero sigue apareciendome el
>> mensaje.
>>
>>
>> Saludos.
>>
>>
>> --
>> Este correo electrónico ha sido comprobado en busca de virus por AVG.
>> http://www.avg.com
>>
>>
>
> --
> L.J.Marín
> Usando: Debian Testing
>
>
>
> 
>  Libre
> de virus. 

Re: realtek bluetooth puzzle

[Jude DaShiell]

On Thu, 16 Dec 2021, Dan Ritter wrote:

> Jude DaShiell wrote:
> > bnep   20480  0
> > bluetooth 483328  1 bnep
> > ecdh_generic   16384  1 bluetooth
> > ecc40960  1 ecdh_generic
> >
> > That's relevant output from lsmod.
> > If I run inxi -E
> > that returns no bluetooth data available.
> > This is supposed to be linux-compatible.
> > Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after
> > starting bluetooth adapters gets me nowhere.
> > Has anyone got one of these cards from WalMart going and can give me some
> > ideas for getting this up and working or find out if it can't work so I
> > can trash it and buy a different card from WalMart?
>
> Anything interesting in lsusb?
>
> -dsr-
>
file: lsbusb.orig

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass9 Hub
  bDeviceSubClass 0
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize064
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0002 2.0 root hub
  bcdDevice5.14
  iManufacturer   3 Linux 5.14.14 ehci_hcd
  iProduct2 EHCI Host Controller
  iSerial 1 :00:16.2
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0019
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0004  1x 4 bytes
bInterval  12
Hub Descriptor:
  bLength   9
  bDescriptorType  41
  nNbrPorts 4
  wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
  bPwrOn2PwrGood   10 * 2 milli seconds
  bHubContrCurrent  0 milli Ampere
  DeviceRemovable0x00
  PortPwrCtrlMask0xff
 Hub Port Status:
   Port 1: .0100 power
   Port 2: .0100 power
   Port 3: .0100 power
   Port 4: .0100 power
Device Status: 0x0001
  Self Powered

Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass9 Hub
  bDeviceSubClass 0
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize064
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0001 1.1 root hub
  bcdDevice5.14
  iManufacturer   3 Linux 5.14.14 ohci_hcd
  iProduct2 OHCI PCI host controller
  iSerial 1 :00:16.0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0019
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0002  1x 2 bytes
bInterval 255
Hub Descriptor:
  bLength   9
  bDescriptorType  41
  nNbrPorts 4
  wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
  bPwrOn2PwrGood2 * 2 milli seconds
  bHubContrCurrent  0 milli Ampere
  DeviceRemovable0x00
  PortPwrCtrlMask0xff
 Hub Port Status:
   Port 1: .0100 power
   Port 2: .0100 power
   Port 3: .0100 power
   Port 4: .0100 power
Device Status:

Re: 8 -> 9 update changing things

[Andrew M.A. Cater]

On Thu, Dec 16, 2021 at 02:35:43PM -0500, Roy J. Tellason, Sr. wrote:
> I'd posted about my update a while back,  and while some folks were 
> encouraging me to go all the way to 11 since it's the current version,  
> my thinking has been to see how things are working,  what's changed,  
> what broke,  etc. and deal with all of that before I continue on in the 
> update process.
> 
> Some of the things I'm dealing with are:
> 
> 1. An annoying blue dot showed up in my taskbar.  
> Right-clicking on this gave me an option to "quit",  which I would do,  
> and then within a few seconds it would come right back again!  I finally 
> tracked this down to being "KDEaccessible",  which I've done nothing to 
> invoke and don't know why the upgrade put that in there.  I solved the 
> problem by using synaptic to uninstall the package,  since I have no use 
> for it.
> 

This one is solved for the moment, then.

> 2. My virtual (older) Slackware virtualbox install is seeing a few issues.
> One of them is that there is apparently a screensaver kicking in after 
> some extended period of time.  I can't find any place where this is 
> enabled,  to turn it off.  I wasn't using one before and don't want one 
> now.  Suggestions?
> 

XFCE desktop: if this is blanking the screen, try checking for power settings.
If it's an _actual_ screensaver with patterns - check to see what screen
saving/locking programs come by default.

> 3. Also under the Slackware virtualbox sound has quit working.  
> When I boot it,  I get a message that says "Host audio backend (PulseAudio) 
> initialization has failed. Selecting the NULL audio backend with the 
> consequence that no sound is audible."  I'm not sure what changed here 
> either.  On the host (Debian) side,  audio works fine for,  ferinstance,  
> playing a youtube video.  But for some things I want to be able to play 
> audio under Slackware as well.  I found an item in the Xfce applications 
> menu under Multimedia that says "Pulseaudio Volume Control" and when I 
> hit that I get a smallish popup window with no apparent content other 
> than "Establishing connection to PulseAudio, please wait..." and then 
> nothing happens for a good long while now.  Suggestions?
> 

How old id the virtualbox version - is there an option for audio passthrough
or similar?

> 4. There is *something* kicking off around midnight local time that 
> produces a whole lot of disk activity for a few minutes,  slowing down 
> whatever else I might be doing at the time.  I've looked at various things 
> like cron, at,  etc. to see if I can find something in there but no luck
>  so far.  Suggestions?
> 

Run top / ps -elf | less to see what processes are running and check 
what seems to be eating memory or disk?

> There's probably more,  but I would like to get these things ironed out 
> before I go chasing any more stuff,  and before I continue on the upgrade
>  path...
> 

Hi Roy,

I would seriously suggest upgrading from 9 to at least 10. You might sort 
out some of the issues but, more importantly, will be moving up to a
better supported system

With every good wish, as ever,

Andy Cater

> 
> -- 
> Member of the toughest, meanest, deadliest, most unrelenting -- and
> ablest -- form of life in this section of space,  a critter that can
> be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
> -
> Information is more dangerous than cannon to a society ruled by lies. --James 
> M Dakin
> 

jupyter-notebook and bullseye

[D. R. Evans]

I don't use jupyter-notebook often, so I only just discovered that I am 
encountering a problem with it following my upgrade from buster to bullseye a 
couple of months ago. It worked fine on buster, and I have changed nothing 
related to jupyter since the upgrade.


When jupyter-notebook starts the browser, I see a big red "kernel error" 
button, and when I press it, the following pops up:




Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/tornado/web.py", line 1704, in _execute
 result = await result
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 769, in run
 yielded = self.gen.throw(*exc_info)  # type: ignore
   File 
"/usr/lib/python3/dist-packages/notebook/services/sessions/handlers.py", line 
69, in post

 model = yield maybe_future(
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 762, in run
 value = future.result()
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 769, in run
 yielded = self.gen.throw(*exc_info)  # type: ignore
   File 
"/usr/lib/python3/dist-packages/notebook/services/sessions/sessionmanager.py", 
line 88, in create_session
 kernel_id = yield self.start_kernel_for_session(session_id, path, name, 
type, kernel_name)

   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 762, in run
 value = future.result()
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 769, in run
 yielded = self.gen.throw(*exc_info)  # type: ignore
   File 
"/usr/lib/python3/dist-packages/notebook/services/sessions/sessionmanager.py", 
line 100, in start_kernel_for_session

 kernel_id = yield maybe_future(
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 762, in run
 value = future.result()
   File 
"/usr/lib/python3/dist-packages/notebook/services/kernels/kernelmanager.py", 
line 176, in start_kernel
 kernel_id = await maybe_future(self.pinned_superclass.start_kernel(self, 
**kwargs))
   File 
"/usr/lib/python3/dist-packages/jupyter_client/multikernelmanager.py", line 
185, in start_kernel

 km.start_kernel(**kwargs)
   File "/usr/lib/python3/dist-packages/jupyter_client/manager.py", line 313, 
in start_kernel

 self.kernel = self._launch_kernel(kernel_cmd, **kw)
   File "/usr/lib/python3/dist-packages/jupyter_client/manager.py", line 222, 
in _launch_kernel

 return launch_kernel(kernel_cmd, **kw)
   File "/usr/lib/python3/dist-packages/jupyter_client/launcher.py", line 
134, in launch_kernel

 proc = Popen(cmd, **kwargs)
   File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
 self._execute_child(args, executable, preexec_fn, close_fds,
   File "/usr/lib/python3.9/subprocess.py", line 1823, in _execute_child
 raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/python'

-

It is certainly true that that file does not exist, but something is obviously 
telling jupyter to look for it. So something about the jupyter configuration 
seems to have been hosed by the upgrade.


The command "jupyter kernelspec list" produces:



[ZB:~] jupyter kernelspec list
-bash: /home/n7dr/.local/bin/jupyter: /usr/bin/python: bad interpreter: No 
such file or directory

[ZB:~]



In buster I had perhaps half a dozen kernels available (and they all worked).

Can someone suggest how I might get back to the fully-working set of kernels 
that I had in buster?


  Doc

--
Web:  http://enginehousebooks.com/drevans

Re: realtek bluetooth puzzle

[Christian Britz]

On 2021-12-16 20:01 UTC+0100, Dan Ritter wrote:
> Jude DaShiell wrote: 
>> bnep   20480  0
>> bluetooth 483328  1 bnep
>> ecdh_generic   16384  1 bluetooth
>> ecc40960  1 ecdh_generic
>>
>> That's relevant output from lsmod.
>> If I run inxi -E
>> that returns no bluetooth data available.
>> This is supposed to be linux-compatible.
>> Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after
>> starting bluetooth adapters gets me nowhere.
>> Has anyone got one of these cards from WalMart going and can give me some
>> ideas for getting this up and working or find out if it can't work so I
>> can trash it and buy a different card from WalMart?
> 
> Anything interesting in lsusb?
> 
> -dsr-
> 

Or in the syslog?
(If it is really a "card", Jude should issue lspci.)

8 -> 9 update changing things

[Roy J. Tellason, Sr.]

I'd posted about my update a while back,  and while some folks were encouraging 
me to go all the way to 11 since it's the current version,  my thinking has 
been to see how things are working,  what's changed,  what broke,  etc. and 
deal with all of that before I continue on in the update process.

Some of the things I'm dealing with are:

1. An annoying blue dot showed up in my taskbar.  Right-clicking on this gave 
me an option to "quit",  which I would do,  and then within a few seconds it 
would come right back again!  I finally tracked this down to being 
"KDEaccessible",  which I've done nothing to invoke and don't know why the 
upgrade put that in there.  I solved the problem by using synaptic to uninstall 
the package,  since I have no use for it.

2. My virtual (older) Slackware virtualbox install is seeing a few issues.  One 
of them is that there is apparently a screensaver kicking in after some 
extended period of time.  I can't find any place where this is enabled,  to 
turn it off.  I wasn't using one before and don't want one now.  Suggestions?

3. Also under the Slackware virtualbox sound has quit working.  When I boot it, 
 I get a message that says "Host audio backend (PulseAudio) initialization has 
failed. Selecting the NULL audio backend with the consequence that no sound is 
audible."  I'm not sure what changed here either.  On the host (Debian) side,  
audio works fine for,  ferinstance,  playing a youtube video.  But for some 
things I want to be able to play audio under Slackware as well.  I found an 
item in the Xfce applications menu under Multimedia that says "Pulseaudio 
Volume Control" and when I hit that I get a smallish popup window with no 
apparent content other than "Establishing connection to PulseAudio, please 
wait..." and then nothing happens for a good long while now.  Suggestions?

4. There is *something* kicking off around midnight local time that produces a 
whole lot of disk activity for a few minutes,  slowing down whatever else I 
might be doing at the time.  I've looked at various things like cron, at,  etc. 
to see if I can find something in there but no luck so far.  Suggestions?

There's probably more,  but I would like to get these things ironed out before 
I go chasing any more stuff,  and before I continue on the upgrade path...


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: realtek bluetooth puzzle

[Dan Ritter]

Jude DaShiell wrote: 
> bnep   20480  0
> bluetooth 483328  1 bnep
> ecdh_generic   16384  1 bluetooth
> ecc40960  1 ecdh_generic
> 
> That's relevant output from lsmod.
> If I run inxi -E
> that returns no bluetooth data available.
> This is supposed to be linux-compatible.
> Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after
> starting bluetooth adapters gets me nowhere.
> Has anyone got one of these cards from WalMart going and can give me some
> ideas for getting this up and working or find out if it can't work so I
> can trash it and buy a different card from WalMart?

Anything interesting in lsusb?

-dsr-

Re: Instalar Debian con UEFI

[Jerigondor]

El 16/12/2021 a las 19:28, Leonardo Marín escribió:



El jue, 16 dic 2021 a las 14:15, Jerigondor () 
escribió:



Cuando se me queda la pantalla en negro solo me aparece el cursor
arriba
a la izquierda. Pero fijo, no parpadea. Y no me permite pasar a otra
consola. Está como congelado. Ni Control+Alt+Suprimir ni nada.

Es lo que normalmente sucede cuando tienes una grafica nvidia y el 
sistema intenta iniciar el video con el driver libre nouveau,
de entrada tienes una pantalla totalmente negra o un ( _ ) arriba a la 
izquierda como comentas,


por eso te comentaba en el correo anterior que luego de iniciar y 
estando en esa pantalla negra debes intentar con Ctrl+Alt+F2 esto te 
debería de abrir otra terminal donde te pedirá te loguees,
si eso pasa entonces si tienes un problema con el driver de video y no 
está relacionado con uefi,


Es que ahí radica el problema, que no puedo hacer absolutamente nada. Ni 
Control+Alt+F2, ni nada. Y no puedo entrar como Root, ni como usuario. 
Así no puedo modificar nada.



en caso de que el problema sea el driver de nouveau esta es la 
configuracion que tengo para evitar que se inicie:

asumiendo que pudiste iniciar sesion como root desde la consola;

# nano /etc/default/grub

editas la linea como la mostrada abajo para dejarlo de esta manera 
guardas y sales

GRUB_CMDLINE_LINUX_DEFAULT="quiet nouveau.modeset=0 nvidia-drm.modeset=1"

# nano /etc/modprobe.d/blacklist.conf

agregas las siguientes líneas guardas y sales
blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

# nano /etc/modprobe.d/nouveau-kms.conf

agregas las siguientes líneas guardas y sales
options nouveau modeset=0
options nvidia-drm modeset=1

corres estos 2 comandos para que se reflejen los cambios
# update-initramfs -u
# update-grub2

reinicias y de entrada no deberías de tener una pantalla negra sino 
directamente en la línea de comandos (aunque en mi notebook eso no 
pasa solo se queda la pantalla con la info que se muestra de inicio y 
parece colgada),
si instalas el driver vesa y no tienes nada configurado debería de 
iniciar con el video.

# apt install xserver-xorg-video-vesa

eso si tienes xor, con wayland no se como sea no lo he usado todavía,
si logras iniciar con vesa ya luego puedes elegir si instalas el 
driver de nvidia directamente o lo instalas de los repositorios de debian.



Si elijo Recovery mode, me aparece algo mas de informacion. La que
aparece en la imagen.

https://ibb.co/KsfcC64

Pero se bloquea despues de un segundo de arranque, como se puede
ver en
la imagen. La ultima linea hace referencia a noveau, los drivers
libres
de Nvidia. Quizas tenga algo que ver con la grafica.


Algo mas de informacion:

No he conseguido arrancar con un live USB de Ubuntu. Probaré con
otras
imagenes...

Durante la instalacion, me avisa de que no se ha podido cargar
firmware
no libre. Concretamente rtw88/rtw8822c_fw.bin
rtw88/rtw8822c_wow_fw.bin.
Pero creo que es firmware de la wifi. He intentado instalar con una
imagen de Debian con el firmware non-free, pero sigue
apareciendome el
mensaje.


Saludos.


-- 
Este correo electrónico ha sido comprobado en busca de virus por AVG.

http://www.avg.com



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

realtek bluetooth puzzle

[Jude DaShiell]

bnep   20480  0
bluetooth 483328  1 bnep
ecdh_generic   16384  1 bluetooth
ecc40960  1 ecdh_generic

That's relevant output from lsmod.
If I run inxi -E
that returns no bluetooth data available.
This is supposed to be linux-compatible.
Unfortunately using bluetoothd and bluetoothctl or blueman in G.U.I. after
starting bluetooth adapters gets me nowhere.
Has anyone got one of these cards from WalMart going and can give me some
ideas for getting this up and working or find out if it can't work so I
can trash it and buy a different card from WalMart?

Re: changed file while editing

[mick crane]

On 2021-12-16 18:04, mick crane wrote:

On 2021-12-11 18:58, David Christensen wrote:


When a computer gets to the point that it is doing weird things that I
cannot understand, troubleshoot, or fix, I download the OS installer
of choice, burn it to USB, make sure my configuration files are
checked in to CVS, backup my data, remove the system disk, insert a
blank system disk, do a fresh install, take an image of the system
disk, boot, check out the old configuration files to a side directory,
edit the new configuration files (rebooting and testing as I proceed),
and restore data.  This is the only way I know to get a "clean", and
hopefully reliable, OS image.


lovely.

I've used vi for the last 3 days and it's happened once instead of
multiple times.
I'd love it to be user error, well to know what the use error is, but
I've been using basic editing with vi/vim for years and this never
happened before.
Is it at all possible that running Perl executable file somehow shares
the same memory as same file opened in vi and they get jumbled?
I don't understand why the error is random words from elsewhere in the
file get randomly inserted as opposed to garbage.
I'm inclined to get another PC and see if it still does it.


actually it happened twice
I have used find and replace
:%s/old/new/g
but error there doesn't explain it
line nowhere near editing changed from
"}" to "f}" which makes no sense.
mick
--
Key ID4BFEBB31

Re: Instalar Debian con UEFI

[Leonardo Marín]

El jue, 16 dic 2021 a las 14:15, Jerigondor ()
escribió:

>
> Cuando se me queda la pantalla en negro solo me aparece el cursor arriba
> a la izquierda. Pero fijo, no parpadea. Y no me permite pasar a otra
> consola. Está como congelado. Ni Control+Alt+Suprimir ni nada.
>
Es lo que normalmente sucede cuando tienes una grafica nvidia y el sistema
intenta iniciar el video con el driver libre nouveau,
de entrada tienes una pantalla totalmente negra o un ( _ ) arriba a la
izquierda como comentas,

por eso te comentaba en el correo anterior que luego de iniciar y estando
en esa pantalla negra debes intentar con Ctrl+Alt+F2 esto te debería de
abrir otra terminal donde te pedirá te loguees,
si eso pasa entonces si tienes un problema con el driver de video y no está
relacionado con uefi,

en caso de que el problema sea el driver de nouveau esta es la
configuracion que tengo para evitar que se inicie:
asumiendo que pudiste iniciar sesion como root desde la consola;

# nano /etc/default/grub

editas la linea como la mostrada abajo para dejarlo de esta manera guardas
y sales
GRUB_CMDLINE_LINUX_DEFAULT="quiet nouveau.modeset=0 nvidia-drm.modeset=1"

# nano /etc/modprobe.d/blacklist.conf

agregas las siguientes líneas guardas y sales
blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

# nano /etc/modprobe.d/nouveau-kms.conf

agregas las siguientes líneas guardas y sales
options nouveau modeset=0
options nvidia-drm modeset=1

corres estos 2 comandos para que se reflejen los cambios
# update-initramfs -u
# update-grub2

reinicias y de entrada no deberías de tener una pantalla negra sino
directamente en la línea de comandos (aunque en mi notebook eso no pasa
solo se queda la pantalla con la info que se muestra de inicio y parece
colgada),
si instalas el driver vesa y no tienes nada configurado debería de iniciar
con el video.
# apt install xserver-xorg-video-vesa

eso si tienes xor, con wayland no se como sea no lo he usado todavía,
si logras iniciar con vesa ya luego puedes elegir si instalas el driver de
nvidia directamente o lo instalas de los repositorios de debian.


> Si elijo Recovery mode, me aparece algo mas de informacion. La que
> aparece en la imagen.
>
> https://ibb.co/KsfcC64
>
> Pero se bloquea despues de un segundo de arranque, como se puede ver en
> la imagen. La ultima linea hace referencia a noveau, los drivers libres
> de Nvidia. Quizas tenga algo que ver con la grafica.
>
>
> Algo mas de informacion:
>
> No he conseguido arrancar con un live USB de Ubuntu. Probaré con otras
> imagenes...
>
> Durante la instalacion, me avisa de que no se ha podido cargar firmware
> no libre. Concretamente rtw88/rtw8822c_fw.bin rtw88/rtw8822c_wow_fw.bin.
> Pero creo que es firmware de la wifi. He intentado instalar con una
> imagen de Debian con el firmware non-free, pero sigue apareciendome el
> mensaje.
>
>
> Saludos.
>
>
> --
> Este correo electrónico ha sido comprobado en busca de virus por AVG.
> http://www.avg.com
>
>

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

Re: Btrfs best practices

[Jorge P . de Morais Neto]

Hi.

Em [2021-12-16 qui 14:55:23-0300], Eduardo M KALINOWSKI escreveu:

> On 16/12/2021 14:13, Jorge P. de Morais Neto wrote:
>> I'll put system and /home on the SSD but all XDG user dirs² on the
>> HDD [snip]
>
> I don't have that manpage installed, but if you're refering to
> ~/.config, ~/.local, etc, these are exactly the kinds of things that
> should be on the SSD - it'll help with application startup times as
> files in those directories are read when applications start.

No, I was referring to:

DESKTOP
DOWNLOAD
TEMPLATES
PUBLICSHARE
DOCUMENTS
MUSIC
PICTURES
VIDEOS

> As for the other questions, I cannot help specifically, but as a
> general advice, don't overthink it and don't bother trying to optimize
> everything up to the smallest details.  Unless you have some very
> specific use, default settings are good enough, you should'nt notice
> any different in day to day use.

Thank you for the advice!  I will think about it.  I must not return to
the days when I riced Gentoo for hours every week trying to gain a tiny
bit of extra performance.  There must be moderation.

Regards

-- 
- Many people hate injustice but few check the facts; this causes more
  injustice.  Ask me about 
- Please adopt free/libre formats like PDF, Org, LaTeX, ODF, Opus, WebM and 7z.
- Libre apps for AOSP (Replicant, LineageOS, etc.) and Android: F-Droid
- https://www.gnu.org/philosophy/free-sw.html "What is free software?"

Re: Btrfs best practices

[Jorge P . de Morais Neto]

Hi.  I must add the information that I use zswap:

GRUB_CMDLINE_LINUX_DEFAULT="quiet zswap.enabled=1 zswap.zpool=z3fold 
zswap.compressor=lzo-rle"

Em [2021-12-16 qui 14:13:05-0300], Jorge P. de Morais Neto escreveu:

> Hi!  I own a Dell Inspiron 5570 laptop with 1 TB SATA HDD, a new 250 GB
> NVMe SSD¹ and 16 GiB RAM.  I seek reliability, durability, performance
> and power efficiency.
>
> I do weekly duplicity backups to external 1.5 TB USB3 HDD.  I'll start
> also daily rsyncing some of the SSD data to the SATA HDD.
>
> The SSD will have 50 GB extra over provisioning and a 200 GB partition,
> besides the special UEFI partition.  The SATA HDD will start with 16 GiB
> swap partition then a big partition.  I'll put system and /home on the
> SSD but all XDG user dirs² on the HDD, and tmpfs on /tmp.  All three
> drives will have Btrfs with space_cache=v2, noatime, zstd compression
> and reasonable free breathing space.
>
> I use Gnome and:
> - GNU Emacs
> - notmuch and offlineimap (I may switch to mbsync)
> - GNU IceCat, Mozilla Firefox and ungoogled-chromium
> - Gajim and GNU Jami
> - Gnome Boxes or Virtual Machine Manager running a VM with 2 GiB RAM and
>   one .qcow2 disk image currently weighting 24 GB.
> - mpv
> - Nextcloud (always running but rarely syncing changes)
>
> I use Debian stable with only official repositories, including
> bullseye-backports.  I manually installed GNU Guix package manager and
> have 163 packages on main Guix profile.
>
> * Doubts
> ** Backported kernel
> Should I use a backported kernel as Btrfs [wiki][] recommends?  I worry
> that bullseye-backports comes from Debian testing with poor security.
>
> [wiki]: 
> https://btrfs.wiki.kernel.org/index.php/Getting_started#Before_you_start
>
> ** Strong compression during install
> For lifetime and space saving, I intend to install Debian to the SSD
> with compress-force=zstd:12, but then adopt compress-force=zstd.  Thus
> the installation will be slow---I'll do something else while the
> installer works---but the installed system will be efficient, right?
>
> ** HDD Compression
> Both HDD have a lot of already-compressed data: videos, audio, photos
> and compressed archives and disk images; compress-force would force
> Btrfs to recompress it all, only to discard the recompressed data and
> store the original.  Therefore compress=zstd:4 would be better, right?
>
> ** Fragmentation
> Is fragmentation a concern?  Is the [Gotchas][] article accurate?
>
> [Gotchas]: https://btrfs.wiki.kernel.org/index.php/Gotchas#Fragmentation
>
> ** Subvolumes
> What about
> https://fedoraproject.org/wiki/Changes/BtrfsByDefault#Additional_subvolumes ?
>
> ** Swappiness
> Most performance-critical data will be on the SSD, so there will be much
> less need for RAM caches; therefore I should decrease swappiness
> (especially if I put swap on the SSD), right?  By how much?
>
> * Footnotes
> ¹ A 250 GB WD Blue SN550 rated for 150 TBW.
> ² See the xdg-user-dir manpage.
>
> Kindest regards,
>   Jorge
>
> -- 
> - Many people hate injustice but few check the facts; this causes more
>   injustice.  Ask me about 
> - I am Brazilian.  I hope my English is correct and I welcome feedback.
> - https://www.defectivebydesign.org
> - https://www.gnu.org

-- 
- Many people hate injustice but few check the facts; this causes more
  injustice.  Ask me about 
- I am Brazilian.  I hope my English is correct and I welcome feedback.
- Free Software Supporter: https://www.fsf.org/free-software-supporter
- If an email of mine arrives at your spam box, please notify me.

Re: changed file while editing

[mick crane]

On 2021-12-11 18:58, David Christensen wrote:


When a computer gets to the point that it is doing weird things that I
cannot understand, troubleshoot, or fix, I download the OS installer
of choice, burn it to USB, make sure my configuration files are
checked in to CVS, backup my data, remove the system disk, insert a
blank system disk, do a fresh install, take an image of the system
disk, boot, check out the old configuration files to a side directory,
edit the new configuration files (rebooting and testing as I proceed),
and restore data.  This is the only way I know to get a "clean", and
hopefully reliable, OS image.


lovely.

I've used vi for the last 3 days and it's happened once instead of 
multiple times.
I'd love it to be user error, well to know what the use error is, but 
I've been using basic editing with vi/vim for years and this never 
happened before.
Is it at all possible that running Perl executable file somehow shares 
the same memory as same file opened in vi and they get jumbled?
I don't understand why the error is random words from elsewhere in the 
file get randomly inserted as opposed to garbage.

I'm inclined to get another PC and see if it still does it.

mick
--
Key ID4BFEBB31

Re: Btrfs best practices

[Eduardo M KALINOWSKI]

On 16/12/2021 14:13, Jorge P. de Morais Neto wrote:

I'll put system and /home on the
SSD but all XDG user dirs² on the HDD [snip]


I don't have that manpage installed, but if you're refering to 
~/.config, ~/.local, etc, these are exactly the kinds of things that 
should be on the SSD - it'll help with application startup times as 
files in those directories are read when applications start.


Put large files (photos, music, video, etc) on the HD. For everything 
else, prefer the SSD.


As for the other questions, I cannot help specifically, but as a general 
advice, don't overthink it and don't bother trying to optimize 
everything up to the smallest details. Unless you have some very 
specific use, default settings are good enough, you should'nt notice any 
different in day to day use.


--
The best way to get rid of worries is to let them die of neglect.

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

Re: Instalar Debian con UEFI

[Jerigondor]

El 15/12/2021 a las 0:14, JavierDebian escribió:



El 14/12/21 a las 17:03, jerigondor escribió:

Buenas.

Pues me acabo de comprar un nuevo PC y no consigo instalar Debian. 
Bueno, en realidad si que lo instalo, pero no consigo que arranque. 
despues del GRUB se queda en una pantalla en negro.


Es un HP con un i5 de 11º generación. Por lo que he visto, este 
procesador no tiene la opción de modo legacy, que he visto en varios 
tutoriales aunque según creo Debian desde hace tiempo es compatible 
con UEFI y Secure Boot (que esta desactivado por si acaso).


La idea es tener Dual Boot. Por lo que he instalado Windows 11.

Después de la instalación de Windows, que arranca perfectamente, 
procedo a instalar Debian. Todo perfecto hasta la hora de arrancar 
Debian que sucede lo que comentaba. Si en el menú de GRUB elijo la 
opción de Windows, este arranca sin problema. Pero con Debian no hay 
manera.


He de reconocer que mis conocimientos no son demasiados. Y UEFI me ha 
pillado desprevenido. Estoy leyendo articulos y tutoriales, pero me 
sobrepasa, por lo que quizas me esté haciendo una idea equivocada del 
funcionamiento.


Cuando instalo Windows, se crea una partición EFI, que según tengo 
entendido es necesaria para el inicio del S.O. Por si acaso Debian no 
escribiese su entrada en esta particion, he borrado todo el disco 
duro y he instalado solo Debian. En este caso se crea una particion 
EFI junto a la de "/" y la de "home" (me gusta tenerlas separadas) 
algo mas grande que la que se crea durante la instalacion de Windows 
(500MB frente a los 100MB). Por lo que supongo que Debian hace 
correctamente lo que quiera que haga con la particion EFI.


He de aclarar que en todo momento solo ha habido una particion EFI.

Pero como he dicho, quizás no entienda como funciona la cosa, y solo 
esté diciendo tonterias.


A ver si alguien me puede decir que estoy haciendo mal.

El PC es un HP con Intel Core™ i5 de 11ma Generación un SSD de 500 Gb 
(donde estarian los S.O.) y un  HDD de un TB. 16GB de ram y NVIDIA 
GeForce GTX 1660 SUPER.



Saludos.





Como dice Lenoardo, eso me huele más a problema de la controladora 
gráfica que a Debian.
Arranca el sistema y cuando llegues al menú de Sistemas Operativos, 
selecciona "Recovery mode".

Ingresa a la antigua, sólo consola como "root".
Si eso funciona, tu problema es el controlador NVIDIA, no UEFI.
Desde allí, a la antigua, trata de arreglar el problema, identificando 
tu placa de video y configurándola como se debe, todo desde consola.


JAP

Cuando se me queda la pantalla en negro solo me aparece el cursor arriba 
a la izquierda. Pero fijo, no parpadea. Y no me permite pasar a otra 
consola. Está como congelado. Ni Control+Alt+Suprimir ni nada.


Si elijo Recovery mode, me aparece algo mas de informacion. La que 
aparece en la imagen.


https://ibb.co/KsfcC64

Pero se bloquea despues de un segundo de arranque, como se puede ver en 
la imagen. La ultima linea hace referencia a noveau, los drivers libres 
de Nvidia. Quizas tenga algo que ver con la grafica.



Algo mas de informacion:

No he conseguido arrancar con un live USB de Ubuntu. Probaré con otras 
imagenes...


Durante la instalacion, me avisa de que no se ha podido cargar firmware 
no libre. Concretamente rtw88/rtw8822c_fw.bin rtw88/rtw8822c_wow_fw.bin. 
Pero creo que es firmware de la wifi. He intentado instalar con una 
imagen de Debian con el firmware non-free, pero sigue apareciendome el 
mensaje.



Saludos.


--
Este correo electrónico ha sido comprobado en busca de virus por AVG.
http://www.avg.com

Btrfs best practices

[Jorge P. de Morais Neto]

Hi!  I own a Dell Inspiron 5570 laptop with 1 TB SATA HDD, a new 250 GB
NVMe SSD¹ and 16 GiB RAM.  I seek reliability, durability, performance
and power efficiency.

I do weekly duplicity backups to external 1.5 TB USB3 HDD.  I'll start
also daily rsyncing some of the SSD data to the SATA HDD.

The SSD will have 50 GB extra over provisioning and a 200 GB partition,
besides the special UEFI partition.  The SATA HDD will start with 16 GiB
swap partition then a big partition.  I'll put system and /home on the
SSD but all XDG user dirs² on the HDD, and tmpfs on /tmp.  All three
drives will have Btrfs with space_cache=v2, noatime, zstd compression
and reasonable free breathing space.

I use Gnome and:
- GNU Emacs
- notmuch and offlineimap (I may switch to mbsync)
- GNU IceCat, Mozilla Firefox and ungoogled-chromium
- Gajim and GNU Jami
- Gnome Boxes or Virtual Machine Manager running a VM with 2 GiB RAM and
  one .qcow2 disk image currently weighting 24 GB.
- mpv
- Nextcloud (always running but rarely syncing changes)

I use Debian stable with only official repositories, including
bullseye-backports.  I manually installed GNU Guix package manager and
have 163 packages on main Guix profile.

* Doubts
** Backported kernel
Should I use a backported kernel as Btrfs [wiki][] recommends?  I worry
that bullseye-backports comes from Debian testing with poor security.

[wiki]: https://btrfs.wiki.kernel.org/index.php/Getting_started#Before_you_start

** Strong compression during install
For lifetime and space saving, I intend to install Debian to the SSD
with compress-force=zstd:12, but then adopt compress-force=zstd.  Thus
the installation will be slow---I'll do something else while the
installer works---but the installed system will be efficient, right?

** HDD Compression
Both HDD have a lot of already-compressed data: videos, audio, photos
and compressed archives and disk images; compress-force would force
Btrfs to recompress it all, only to discard the recompressed data and
store the original.  Therefore compress=zstd:4 would be better, right?

** Fragmentation
Is fragmentation a concern?  Is the [Gotchas][] article accurate?

[Gotchas]: https://btrfs.wiki.kernel.org/index.php/Gotchas#Fragmentation

** Subvolumes
What about
https://fedoraproject.org/wiki/Changes/BtrfsByDefault#Additional_subvolumes ?

** Swappiness
Most performance-critical data will be on the SSD, so there will be much
less need for RAM caches; therefore I should decrease swappiness
(especially if I put swap on the SSD), right?  By how much?

* Footnotes
¹ A 250 GB WD Blue SN550 rated for 150 TBW.
² See the xdg-user-dir manpage.

Kindest regards,
  Jorge

-- 
- Many people hate injustice but few check the facts; this causes more
  injustice.  Ask me about 
- I am Brazilian.  I hope my English is correct and I welcome feedback.
- https://www.defectivebydesign.org
- https://www.gnu.org

Re: Need Support on Debian10 Kernel Upgrade

[Cindy Sue Causey]

On 12/16/21, David Wright  wrote:
> On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
>> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
>> > Hi Team,
>> >
>> >   We are looking support from you on the Linux Kernel upgrade on  Debian
>> > 10. Please help on this.
>>
>> This is a user's list, not a support channel.
>>
>> If you have concrete questions, you can pose them here. Chances are good
>> that some experienced users can help you. Note that this is all
>> voluntary work.
>>
>> There are companies out there offering commercial Debian support. I'm
>> sure a web search will turn up a couple of good candidates.
>
> Anyone think it ironic that a multinational IT company with a
> market capitalisation of $50 billion as of September 2021 comes
> here for help on upgrading the kernel on an old Debian system?


Sounds like something I'd say (and actually have in the past). I
didn't go to the length you did regarding research, but I did notice
it had a style similar to something else in the last week or so
something that... just didn't "sit quite right" from start to finish.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: printing in Debian 11; was bullseye fusses.

[peter]

From: Gene Heskett 
Date: Sat, 11 Dec 2021 18:11:28 -0800
> ... does it [debian-printing] exist?

Gene, in case you didn't catch this earlier, posting again with 
reference corrected. 

The current problem might be solved.  If another surfaces in the 
future, debian-printing might be more efficient than debian-user. 

https://lists.debian.org/debian-printing/

Regards,   ... P.

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

Re: all of a sudden I have no sound

[Jude DaShiell]

debian-accessibility is interested in replacing pulseaudio with pipewire
and I can understand why!  Not saying pipewire has these essential
features but pulseaudio has been a p.i.t.a. since I've had it on any
hardware I've used.  Whenever possible I avoid installing pulseaudio or
remove it from a system that installs it automatically for sanity
purposes.



On Thu, 16 Dec 2021, David Wright wrote:

> On Thu 16 Dec 2021 at 09:13:11 (-0500), Dan Ritter wrote:
> > Jude DaShiell wrote:
> > > it would be nice if pulseaudio say in pavucontrol would get a find my
> > > speakers button which would try what it thinks is a speaker andput a
> > > message on the screen asking if the user heard some music.  If the answer
> > > is no, move onto the next speaker.
> >
> > It would be nice if, for example, it remembered the way that you
> > wanted a system to be rather than recalculating it every time a
> > device changes state. If I turn off the home theater receiver
> > connected to my media server via HDMI, PulseAudio decides that
> > it can't be used, so it helpfully switches over to another audio
> > output device. When I turn the receiver back on, PulseAudio does
> > not switch back to it automatically.
> >
> > The present case is probably similar: PA decided something was
> > unplugged, switched to a different sink, and did not bring it
> > back when it was "replugged".
>
> It's not just nice to have these features, but essential, and
> that's one reason why I don't install pulseaudio. Using amixer
> in ALSA, I can type one line and have the audio set how I want
> it, with the correct levels set and unmuted, just as aumix did
> under OSS for many years.
>
> And, of course, it's not that /I/ have to type that line. If
> I now type in:
> $ touch .cron/2021-12-19-05-55-rk-250
> then the system will automatically record the Sunday morning
> programme from the radio, using appropriate recording levels
> set by the script in bin/rk.sh.
>
> I could never get beyond having to poke around in pulseaudio
> every time I used it. What I wanted was something that would
> enable me to power up the PC at bedtime Saturday, and have it
> just work without the necessity of logging in etc.
>
> Cheers,
> David.
>
>

Re: Desktop "locking".

[Cindy Sue Causey]

On 12/16/21, pe...@easthope.ca  wrote:
>
> Thanks Andre.  I wonder whether we all refer to the same green button.
> http://easthope.ca/UnlockYourDesktop.jpg
> It wasn't among the first hundred or so images reported by Google.

I've never seen that before. Just means I haven't used the program
that's involved.

> I removed light-locker and green button continues to appear.  =8~(

There must be a way to track down what's invoking that button's image.
That would lead to a parent directory. In the last couple of weeks,
I've either tripped over a package that could do so or else have seen
it shared here at Debian-User for some query. I can't remember what it
was, though. It was something that was not apt-file.

Oh, PS I plugged the image into Google's image search. I had high
hopes that would find something, but it said nope, nothing matches. It
did identify the image as a dot and said:

"When used as a diacritic mark, the term dot is usually reserved for
the interpunct, or to the glyphs "combining dot above" and "combining
dot below" which may be combined with some letters of the extended
Latin alphabets in use in Central European languages and Vietnamese.
Wikipedia"

Cindy :))
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: Need Support on Debian10 Linux Kernel Upgrade

[Dan Ritter]

Balasubramanian Ravuthan wrote: 
> 
>  We are looking support from you on the Linux Kernel upgrade on  Debian 10.
> 
> We are currently using Debian10 Buster Linux Kernel 4.19 version and trying 
> to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact 
> on this upgrading.
> 
> In other words, what are the things will get affected if we do kernel upgrade.

Buster was not released with a 5.10 kernel. A 5.10 kernel came
with Bullseye, Debian 11. Are you getting this from backports?

In general, Linus is pretty flexible about what kernels are
being used. The difference will be that the 5 series presumably
has fixed some old bugs, introduced some new bugs, and some
things will be faster or slower. Overall, more hardware is
supported, but if everything was working well with 4.19, then
there's no immediate reason to suspect it won't work with 5.10.

For more details, you're going to have to ask a more specific
question.

-dsr-

Re: all of a sudden I have no sound

[David Wright]

On Thu 16 Dec 2021 at 09:13:11 (-0500), Dan Ritter wrote:
> Jude DaShiell wrote: 
> > it would be nice if pulseaudio say in pavucontrol would get a find my
> > speakers button which would try what it thinks is a speaker andput a
> > message on the screen asking if the user heard some music.  If the answer
> > is no, move onto the next speaker.
> 
> It would be nice if, for example, it remembered the way that you
> wanted a system to be rather than recalculating it every time a
> device changes state. If I turn off the home theater receiver
> connected to my media server via HDMI, PulseAudio decides that
> it can't be used, so it helpfully switches over to another audio
> output device. When I turn the receiver back on, PulseAudio does
> not switch back to it automatically. 
> 
> The present case is probably similar: PA decided something was
> unplugged, switched to a different sink, and did not bring it
> back when it was "replugged".

It's not just nice to have these features, but essential, and
that's one reason why I don't install pulseaudio. Using amixer
in ALSA, I can type one line and have the audio set how I want
it, with the correct levels set and unmuted, just as aumix did
under OSS for many years.

And, of course, it's not that /I/ have to type that line. If
I now type in:
$ touch .cron/2021-12-19-05-55-rk-250
then the system will automatically record the Sunday morning
programme from the radio, using appropriate recording levels
set by the script in bin/rk.sh.

I could never get beyond having to poke around in pulseaudio
every time I used it. What I wanted was something that would
enable me to power up the PC at bedtime Saturday, and have it
just work without the necessity of logging in etc.

Cheers,
David.

Re: Need Support on Debian10 Kernel Upgrade

[David Wright]

On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> > Hi Team,
> > 
> >   We are looking support from you on the Linux Kernel upgrade on  Debian 
> > 10. Please help on this.
> 
> This is a user's list, not a support channel.
> 
> If you have concrete questions, you can pose them here. Chances are good
> that some experienced users can help you. Note that this is all
> voluntary work.
> 
> There are companies out there offering commercial Debian support. I'm
> sure a web search will turn up a couple of good candidates.

Anyone think it ironic that a multinational IT company with a
market capitalisation of $50 billion as of September 2021 comes
here for help on upgrading the kernel on an old Debian system?

Cheers,
David.

Re: Desktop "locking".

[peter]

From: Andrei POPESCU 
Date: Tue, 14 Dec 2021 10:17:31 +0100
> On Lu, 13 dec 21, 23:56:14, Kenneth Parker wrote:
> > 
> > light-locker is the package.  It is a small subset of xscreensaver, if I
> > recall correctly.
> 
> It's a component of XFCE (though LXDE is using it too) and completely 
> unrelated to xscreensaver.
> 
> Gnome is very likely using it's own thing (as per the description, 
> light-locker relies on lightdm while Gnome is using gdm3).

Thanks Andre.  I wonder whether we all refer to the same green button.  
http://easthope.ca/UnlockYourDesktop.jpg
It wasn't among the first hundred or so images reported by Google.

I removed light-locker and green button continues to appear.  =8~(

peter@joule:/home/peter$ dpkg -l | grep locker
peter@joule:/home/peter$

I don't need a desktop environment particularly.  Definitely don't 
need screen  locking.  A screen saver is a good idea.

With Wayland/Weston working I think of removing as much of gnome as 
possible.

In case anyone has helpful tips about the transition from X11, 
https://wiki.debian.org/wayland can be severely improved.

Thx,... P.




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

Re: Logiciel pas pour couper de la vidéo

[Klaus Becker]

Am 16/12/2021 um 12:10 schrieb benoit:

Bonjour à tou·te·s

Je recherche un logiciel pour couper et rabouter des vidéos.
En paquet Debian, facile à utiliser et si possible en ligne de commande.

Merci d'avance

--
Benoit



pas en ligne de commande, mais assez simple : avidemux

Klaus

Re: Need Support on Debian10 Linux Kernel Upgrade

[Christian Britz]

On 2021-12-16 16:04 UTC+0100, Balasubramanian Ravuthan wrote:
>  We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
> 
> We are currently using Debian10 Buster Linux Kernel 4.19 version and
> trying to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there
> any impact on this upgrading.
> 
> In other words, what are the things will get affected if we do kernel
> upgrade.

Kernel 5.10 for buster is available as a backport (backports.debian.org).
There should be no negative impact, but I would suggest to upgrade
a test system first. There should be some Linux expert available at HCL,
otherwise I would suggest to pay a Debian consultant.

Please give an indication that you actually read the replies on this
mailing list, otherwise I will stop trying to help you.

Regards,
Christian

Need Support on Debian10 Linux Kernel Upgrade

[Balasubramanian Ravuthan]

Hi Debian Team,

 We are looking support from you on the Linux Kernel upgrade on  Debian 10.

We are currently using Debian10 Buster Linux Kernel 4.19 version and trying to 
upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact on 
this upgrading.

In other words, what are the things will get affected if we do kernel upgrade.

Please help on this.

Regards,
Bala
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: Need Support on Debian10 Kernel Upgrade

[tomas]

On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> Hi Team,
> 
>   We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
> Please help on this.

This is a user's list, not a support channel.

If you have concrete questions, you can pose them here. Chances are good
that some experienced users can help you. Note that this is all
voluntary work.

There are companies out there offering commercial Debian support. I'm
sure a web search will turn up a couple of good candidates.

Cheers
-- 
tomás


signature.asc
Description: PGP signature

Dysfonctionnements microphone externe Debian 11

[Jean Bernon]

Bonjour, 


J'utilise une webcam / microphone Logitech Webcam Pro 9000 relié par USB à un 
système Debian 11 stable. Quelquefois, après une période d'inactivité, le 
microphone ne marche plus ou il marche en produisant un son nasillard 
inaudible. Dans ce cas je débranche et rebranche le câble USB une ou plusieurs 
fois (3 fois le plus souvent) avant de retrouver un fonctionnement normal qui 
dure au moins toute la session active. C'est agaçant, mais viable. J'aimerais 
bien comprendre d'où ça vient et corriger si possible. Quelqu'un a-t-il déjà 
rencontré ce problème ? 
Merci 
Jean 

Re: Écran noir après mise à jour Debian 11

[Polyna-Maude Racicot-Summerside]

Salut

On 2021-12-15 5:42 p.m., Haricophile wrote:
> Le Tue, 14 Dec 2021 19:09:01 +0100,
> "ajh-valmer"  a écrit :
> 
>> Bonsoir,
>>
>> Je vois que je ne suis pas le seul après migration Buster vers
>> Bullseye...
>>
>> Si ce n'est pas déjà fait et excuses,
>> Démarrer en mode "recovery" (mode console sans Xorg) pour réparer.
>> En démarrage mode graphique, souvent ça bloque à la fin,
>> il faut taper CTRL-D (redémarrage) ou le mode de passe root pour être
>> loggué.
>>
ok
et ?
est-ce que tu as déjà regardé les journaux (logs) pour voir quel service
chargeait mal ou s'il y avait des messages d'erreurs ?

c'est passablement douteux ce que tu racontes ici.
qu'il faut se connecter en utilisant le mots de passe root, est-ce que
tu parles d'un échec et l'utilisation du mots de passe root pour
utiliser le système en mode simple utilisateur, suite à un échec par
exemple au montage ? c'est certain que si tu redémarres ton PC sans bien
démonter les systèmes de fichiers alors ça pourra arriver.

par exemple, tu trouves que le chargement est trop long (ce que tu
appelles problème d'écran noir), tu fais un redémarrage à froid (cold
boot, tu éteins le PC) puis par la suite au redémarrage ça l'aura des
possibles problèmes à remonter le système de fichier.

l'écran noir peut simplement venir du fait que le pilote qui gère la
carte graphique dans X est mal configuré.

as-tu essayé de changer de terminal virtuel lors du démarrage ?
(ALT+F3/F1, etc) ? ALT+F1 risque de te montrer la console principale.

Si tu veux un peu d'aide il faudra en dire plus de précision car là ça
ressemble passablement à "mon PC marche mal", ce qui n'est que de peu
d'utilité (et de possibilité de t'aider).

Quel périphérique avec pilote propriétaire ?
Quel est ta configuration ?
As-tu essayé d'utiliser un média "live" de BullsEye pour voir si ton
système serait pas supporter sans pilote externe ?

>> Bonne soirée.
> 
> Il y a un maximum de chance d'avoir des problèmes de ce genre avec des
> pilotes propriétaires installés. D'ailleurs j'ai déjà vu dans ma vie ce
> genre de gags sous Windows aussi : Moins on dépend des pilotes matériels
> spécifiques (et parfois buggués), mieux les changements de version,
> restaurations de sauvegardes, changement de matériel etc ont de chance
> de bien se passer.
> spéculation (utile ?)

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: Need Support on Debian10 Kernel Upgrade

[Dan Ritter]

Balasubramanian Ravuthan wrote: 
> Hi Debian Team,
> 
>   We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
> Please help on this.
> 

sudo apt update && sudo apt upgrade

Consider a dist-upgrade to Debian 11.

-dsr-

Re: all of a sudden I have no sound

[Dan Ritter]

Jude DaShiell wrote: 
> it would be nice if pulseaudio say in pavucontrol would get a find my
> speakers button which would try what it thinks is a speaker andput a
> message on the screen asking if the user heard some music.  If the answer
> is no, move onto the next speaker.

It would be nice if, for example, it remembered the way that you
wanted a system to be rather than recalculating it every time a
device changes state. If I turn off the home theater receiver
connected to my media server via HDMI, PulseAudio decides that
it can't be used, so it helpfully switches over to another audio
output device. When I turn the receiver back on, PulseAudio does
not switch back to it automatically. 

The present case is probably similar: PA decided something was
unplugged, switched to a different sink, and did not bring it
back when it was "replugged".

-dsr-

Re: Need Support on Debian10 Kernel Upgrade

[Christian Britz]

On 2021-12-16 13:28 UTC+0100, Balasubramanian Ravuthan wrote:
> Hi Team,
> 
>   We are looking support from you on the Linux Kernel upgrade on  Debian
> 10. Please help on this.

There is no "Team" who will support you, we are all users who support
each other. Paid support is available elsewhere.

What is you specific issue? What do you want to do?

Regards,
Christian

Need Support on Debian10 Kernel Upgrade

[Balasubramanian Ravuthan]

Hi Team,

  We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
Please help on this.

Regards,
Bala
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: all of a sudden I have no sound

[Jude DaShiell]

it would be nice if pulseaudio say in pavucontrol would get a find my
speakers button which would try what it thinks is a speaker andput a
message on the screen asking if the user heard some music.  If the answer
is no, move onto the next speaker.


On Thu, 16 Dec 2021, Dan Ritter wrote:

> Maureen L Thomas wrote:
> > I was on the computer and stopped to eat dinner and the puter went into
> > black screen as it always does if left unattended.  It would not wake up so
> > I changed the batteries in my keyboard and it still would not wake up.  So I
> > turned it off with the switch and then back on.  Once it was on it worked
> > fine until I tried to play a you tube and found I had no sound at all.  I
> > checked the sound icon on the top right of the screen and it was set where I
> > always have it.  I went to the sound thing to check that I have sound and as
> > I tested both speakers I heard nothing.  The computer seemed to think that
> > was fine with a smiley face.
>
> Are the speakers internal or external? If external, are they
> powered up and turned on with an appropriate volume?
>
> Does it work with headphones plugged in?
>
> Run pavucontrol and click on the Configuration tab. It is not
> rare for this subsystem to decide to select the wrong audio
> output device after a reboot.
>
> Tell us what options it offers you in the Configuration tab.
>
>
> > I am on a Lenova all in one computer with Debian 9.  I have not needed any
> > upgrades lately so that is not the problem as my system is kept up to date
> > with all software.
>
> I agree that this is not the problem, but you should know that
> the reason you are not getting upgrades on Debian 9 is because
> Debian 11 is the current stable version.
>
> -dsr-
>
>

Need Support on Debian10 Kernel Upgrade

[Balasubramanian Ravuthan]

Hi Debian Team,

  We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
Please help on this.

Regards,
Bala
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: all of a sudden I have no sound

[Dan Ritter]

Maureen L Thomas wrote: 
> I was on the computer and stopped to eat dinner and the puter went into
> black screen as it always does if left unattended.  It would not wake up so
> I changed the batteries in my keyboard and it still would not wake up.  So I
> turned it off with the switch and then back on.  Once it was on it worked
> fine until I tried to play a you tube and found I had no sound at all.  I
> checked the sound icon on the top right of the screen and it was set where I
> always have it.  I went to the sound thing to check that I have sound and as
> I tested both speakers I heard nothing.  The computer seemed to think that
> was fine with a smiley face.

Are the speakers internal or external? If external, are they
powered up and turned on with an appropriate volume?

Does it work with headphones plugged in?

Run pavucontrol and click on the Configuration tab. It is not
rare for this subsystem to decide to select the wrong audio
output device after a reboot.

Tell us what options it offers you in the Configuration tab.


> I am on a Lenova all in one computer with Debian 9.  I have not needed any
> upgrades lately so that is not the problem as my system is kept up to date
> with all software.

I agree that this is not the problem, but you should know that
the reason you are not getting upgrades on Debian 9 is because
Debian 11 is the current stable version. 

-dsr-

Re: [HS]lxde perte capacité clic (dont le droit) sur barre de menu + clic sur fenêtre et dans les applis

[Alain Vaugham]

Le Thu, 16 Dec 2021 11:39:19 +0100,
Greg  a écrit :

> fréquemment (parfois 2 fois par semaine), je perd la possibilité de
> * cliquer sur la barre d'application
> * de cliquer direct sur une fenetre 

Bonjour,

Depuis peu je constate une anomalie similaire avec Xfce sur Debian
10.11. Les mises à jour sont quotidiennes.

* Firefox :
  impossible de fermer la fenêtre avec la souris. Je peux la
  fermer avec le claver par CTRL W.
* Claws Mail :
  Pareil. La souris permet son déplacement sur tout l'écran mais ne
  permet plus le clic à l'intérieur de la fenêtre. Comme pour Firefox,
  le clavier reste actif.

Pour ces deux-là, les clics restent actifs en dehors de leur fenêtre.
Par exemple je peux changer de bureau avec la souris mais quand je
reviens dans la fenêtre de Claws Mail, je ne peux toujours pas la
fermer ni cliquer sur un email pour, par exemple, l'ouvrir.
Je ferme donc la fenêtre avec le clavier et relance Claws Mail.

C'est très récent. Je l'ai constaté trois ou quatre fois. Je n'ai pas
investigué ni conservé davantage de notes.


-- 
Alain Vaugham
Clef GPG : 0xDB77E054673ECFD2

Re: Logiciel pas pour couper de la vidéo

[Cyrille]

très simple pitivi
plus complet en restant simle shotcut
++

Re: Logiciel pas pour couper de la vidéo

[l0f4r0]

Bonjour,

16 déc. 2021, 12:10 de benoit...@protonmail.ch:

> Je recherche un logiciel pour couper et rabouter des vidéos.
> En paquet Debian, facile à utiliser et si possible en ligne de commande.
>

=> ffmpeg

l0f4r0

Re: [HS]lxde perte capacité clic [...] complément

[Greg]

Truc rigolo

Mon menu lxpanel est en haut par defaut (convenance personnelle)

si je le met en bas cela fonctionne  mais j'ai mieux !

en fait ma souris est fonctionnelle pour les clic que sur les ~ 3/4 bas
de l'écran !!

Re : Logiciel pas pour couper de la vidéo

[nicolas . patrois]

Le 16/12/2021 12:10:46, benoit a écrit :

> Je recherche un logiciel pour couper et rabouter des vidéos.
> En paquet Debian, facile à utiliser et si possible en ligne de
> commande.

mplayer ?

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? 
Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Logiciel pas pour couper de la vidéo

[benoit]

Bonjour à tou·te·s

Je recherche un logiciel pour couper et rabouter des vidéos.
En paquet Debian, facile à utiliser et si possible en ligne de commande.

Merci d'avance

--
Benoit

Sent with ProtonMail Secure Email.

[HS]lxde perte capacité clic (dont le droit) sur barre de menu + clic sur fenêtre et dans les applis

[Greg]

Bonjour, 

Je suppose fortement que cela ne soit pas spécifique debian , mais
n'ayant pas d'autres os (que debian) sous la main, je me permet cette
question avec tag HS

Avec lxde/debian en mode Virtualbox

fréquemment (parfois 2 fois par semaine), je perd la possibilité de
* cliquer sur la barre d'application
* de cliquer direct sur une fenetre 

Quand je fais du 'alt tab' pour naviguer sur les fenêtres je peux
travailler sur la fenêtre active (saisir du texte) 
 * firefox impossible de cliquer sur menu du navigateur, menu de sites
   web, mais je peux cliquer sur les onglets ... (de quoi rendre
   dingue) 
 * mousepad : je peux cliquer sur la croix de fermeture fenêtre , mais
   impossible de cliquer sur "ne pas enregistrer / annuler /
   enregistrer"

le plus drôle c'est que je suis dans une vm  (virtualbox) multi-écran,
tout ce qui se trouve sur le 2eme écran fonctionne bien ! 
par contre impossible de déplacer les fenêtres vers le 2eme écran 


j'ai tenté des restart du lxpanel, sans changement 

Note : 
* pour avoir le menu des applications, ctrl-echap fonctionne 
* j'ai une autre vm debian, même config (configurée initialement via
  ansible) qui ne présente pas ce problème

Re: all of a sudden I have no sound

[deloptes]

Maureen L Thomas wrote:

> Any help would be greatly appreciated.

you were already answered before

on Debian 9 it might be you need some debugging after the shutdown via the
power switch. it could be anything from hardware to software  - the
archlinux article is good

I would start with alsamixer first

you must do the work yourself

BR

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

Re: reject dhclient offer from wrong subnet

[Reco]

Hi.

On Wed, Dec 15, 2021 at 04:37:19PM +0100, Tuxo wrote:
> Can I configure dhclient on my router to discard lease offers from a certain 
> subnet? I could also try to match the lease time, the 192.168.100/24 lease 
> time
> is only several seconds (!!) short, the real one will be 4 hours or more and 
> come with a valid WAN subnet mask.

Try adding "reject 192.168.100/24;" into your router's dhclient.conf.

Also, dhclient.conf(5).

Reco