Fix for bug in r8168-dkms with kernel 6.4.0.2-amd64
I am posting this to the list in the hope that it will help someone who has encountered the same issue I did. I am running the testing stream and a few days back, during a regular update, I encountered a kernel panic. The error appeared to be in the r8168-dkms package. I searched around for a few days and found the solution at this link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050287 Specifically it was this bit that fixed the issue: Package: r8168-dkms Version: 8.051.02-3 Severity: important Dear Maintainer, I confirm that the bug is present. "PascalHambourg" on our forum found a workaround by directly editing the file /usr/src/r8168-8.051.02/r8168_n.c Replace #if LINUX_VERSION_CODE >= KERNEL_VERSION(6,5,0) By #if LINUX_VERSION_CODE >= KERNEL_VERSION(6,4,10) And the compilation of the module happens without error. Best regards, Lol. -- I am not subscribed to the list. Sam Varghese
Re: Emacsclient bug in sid
On 2023-08-31, Charles Curley wrote: > You need an emacs process running in order to use emacsclient. It need > not be a daemon. -a="" will launch a daemon process if there isn't a > process already running, daemon or otherwise. emacs is enough if you put start-server in init file. Else it don't listen for emacsclient. With it emacs acts as display + daemon.
Re: I uninstalled OpenMediaVault (because totally overkill for me) and replaced it with borgbackup and rsync
Jason writes: > Hi > > I was a user of OpenMediaVault for several years. I even donated money to the > developer. > > But very provocatively OpenMediaVault is bloatware, way too big. The only > thing > I need is a reliable backup. > > I had pure Debian (minimal installation, very few packages) installed with > borgbackup and rsync. > > I am now very satisfied, much more streamlined than OpenMediaVault. > > Am I wrong, are my statements completely off? > > Or how does your backup look like? > > cheers > Jason > > Another OMV user for several years and have been happy about it. It's a NAS system based on Debian (latest version based on Buster), on top of which it provides its NAS management layer and you can control what to install or not. There is no ads, no telemetry, and it manages my ZFS raidz1 cluster without any issue for several years, and the system itself takes less than 5GB space, so I'm not sure why you'd call it bloatware. -- Manphiz
Re: Sleep: out of control
On Fri, Sep 1, 2023 at 01:15 The Wanderer wrote: > On 2023-08-31 at 13:03, zithro wrote: ... Tom, does your version of that file not include a comment with that same > information? Yes, and they are uncommented and set to 'no'. So far all seems to be working. Now I need to study and understand those sleep options. I also realize I didn't report some other details. I have three hosts (Debian PC, Window PC, and Debian laptop) connected to a single monitor, keyboard, and mouse via a KVM switch. The other day, when I finally emailed for advice, I had noticed the following: When switching the KVM between the Win and Deb hosts, I could see the mouse was not getting power (no sensor light) nor was the keyboard or monitor screen. So that is probably why I could not wake up the Debian PC by stirring the mouse or hitting a key. My conclusion: I need to find out which sleep modes turn off power to the external input devices. -Tom
How to install the kernel 5.4.14 (source and headers) packages on Debian buster.
Hello to everyone. I've just installed Debian Buster on my ARM Chromebook,using this image : https://github.com/hexdump0815/imagebuilder/releases?page=12 He says that the image is based on the kernel 5.4 and it is. Infact the default running kernel is 5.4.14. But for the project that I'm working on,I also need to install the linux source and the headers packages for the same kernel (5.4.14),but unfortunately,between the packages I only see versions 4.19 and 5.10. Is there a method to install the sources and headers packages also for the kernel 5.4.14 ? The point is that for the project that I'm working on (using qemu 5.1 + enabling kvm + kernel 5.4 + libvirt on my ARM chromebook) I need the kvm.h header,that's provided by the linux-headers (5.4.14) package. I can't use a version of qemu greater than 5.1 and a version of the kernel greater than 5.4. That's the reason why I'm asking this question. Thanks very much. -- Mario.
Problem with libreoffice and localisation - LO hangs
Dear list, I discovered a strange problem with libreofffice. When I install libreoffice (apt install libreoffice) everything works fine. But as soon as I have installed the localisation file (apt install libreoffice- l10n-de) Libreofffice hangs at start for several minutes. I purged all LO-installations and reinstalled, to verify this issue I also discovered, that the installation of libreoffice-l10n-de will deinstall several libs. IMHO I believe, there is some incompabilty with the libs and it would be nice, if someoene might confirm this behavior. Strange thing on my own computer with the same configuration everything works fine, even with the localisation. Thanks for reading this and any help. Best regards Hans
Re: Sleep: out of control
On Fri, Sep 1, 2023 at 06:08 Tom Browder wrote: My conclusion: I need to find out which sleep modes turn off power to the > external input devices. > I forgot to mention that my problem child is all SSD, no moving parts (from SilentPC). -Tom
Re: I uninstalled OpenMediaVault (because totally overkill for me) and replaced it with borgbackup and rsyncq
Jason writes: > Or how does your backup look like? Just rsync. -- John Hasler j...@sugarbit.com Elmwood, WI USA
Re: Problem with libreoffice and localisation - LO hangs
On Fri, 01 Sep 2023 13:51:35 +0200
Hans wrote:
Hello Hans,
>I also discovered, that the installation of libreoffice-l10n-de will
>deinstall several lib
With little in the way of information from you, we can only guess, but
the first thing to check is that the localisation package is the same
version as the rest of LO.
Further; Stable, Testing or Sid?
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
It's got nothing to do with the need to impress
Titanic (My Over) Reaction - 999
pgpksg5xD90PU.pgp
Description: OpenPGP digital signature
Re: Problem with libreoffice and localisation - LO hangs
Hi Brad, thanks for the fast response. Yes, you are correct, my information was not much. The computer is one of my customers, so I have no access to it at the moment. However, it is running debian/stable, amd64. This issue appeared suddenly from one day to another and he swore, he had nothing done except shutting down and starting. But of course I can not be sure. It might be, that I installed the localisation from 7.5 on LO-7.4, as both are in the repo. At the moment, I can not recheck it. My goal was first to explore, if someone else ran into the same issue. In the web I found several similar issues, the most reason was the change of some databases. When I first explored the issue (his message was: Does not start and hang), it shows the issue in anaother way:. Libreoffice started, then the splash screen appeared and the progress bar was a fifth of the whole bar. Here it hangs for about 10 minutes and then a popup appeared, asking me to create a database. However, I did not start Libreoffice Base, I just wanbted to open an ODS File with CALC! As I could not find a solution and wanted to help thje customer quickly, I first removed all ~/.config/libreoffice/ with no success. Then deinstalled everything of libreoffice and reinstalled. After installing the localisation I ran into the issue again. Tried all several times to confirm it is AFTER installing localisation package. At the moment the customer is running the English version and waits for me to fix it. Thats the actual status, hope, it helps. Best regards Hans > With little in the way of information from you, we can only guess, but > the first thing to check is that the localisation package is the same > version as the rest of LO. > > Further; Stable, Testing or Sid?
Re: Problem with libreoffice and localisation - LO hangs
Am Fri, Sep 01, 2023 at 02:57:29PM +0200 schrieb Hans: Hello Hans, [...] > It might be, that I installed the localisation from 7.5 on LO-7.4, as both > are > in the repo. At the moment, I can not recheck it. Just as reference: I run Bookworm and I have installed the metapackage. I have no issues running libreoffice. dpkg -l lists almost everything as ii liblibreoffice-java 4:7.4.7-1 all LibreOffice UNO runtime environment -- Java library ii libreoffice 4:7.4.7-1 amd64office productivity suite (metapackage) ii libreoffice-base 4:7.4.7-1 amd64office productivity suite -- database ii libreoffice-help-de 4:7.4.7-1 all office productivity suite -- German help ii libreoffice-l10n-de 4:7.4.7-1 all office productivity suite -- German language package ... Just two parts look different ii libreoffice-nlpsolver 4:0.9+LibO7.4.7-1all "Solver for Nonlinear Programming" extension for LibreOffice ii libreoffice-wiki-publisher 4:1.2.0+LibO7.4.7-1 all LibreOffice extension for working with MediaWiki articles I hope it helps at least a little bit. Viele Grüße, Christoph -- Ist die Katze gesund schmeckt sie dem Hund. signature.asc Description: PGP signature
Re: Problem with libreoffice and localisation - LO hangs
On Fri, 01 Sep 2023 14:57:29 +0200
Hans wrote:
Hello Hans,
>thanks for the fast response. Yes, you are correct, my information was
>not much.
No probs.
>This issue appeared suddenly from one day to another and he swore, he
>had nothing done except shutting down and starting.
When someone swears they "only $AnyThing" it's almost axiomatic they
did something - whatever it might be..
>It might be, that I installed the localisation from 7.5 on LO-7.4, as
>both are in the repo. At the moment, I can not recheck it.
OTOH, if you/they installed LO from (say) stable, and the
localisation from backports, that may explain the issue.
Can't check here, as I'm on Testing (which doesn't exhibit the fault
you're encountering).
>Libreoffice started, then the splash screen appeared and the progress
>bar was a fifth of the whole bar. Here it hangs for about 10 minutes
Sounds almost as if LO had shut down improperly and is trying to
rebuild/create the database. However, the crash dialog usually comes
up pretty quickly, IME.
The only way beyond this point is to get hold of the machine, I think.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Did you do it for fame, did you do it in a fit?
Identity - X-Ray Spex
pgpQczacGwNeu.pgp
Description: OpenPGP digital signature
Monthly FAQ for Debian-user mailing list (Unmodified August 2023)
Debian-user is a mailing list provided for support for Debian users, and to facilitate discussion on relevant topics. Some guidelines which may help explain how the list works: * The language on this mailing list is English. There may be other mailing lists that are language-specific, for example, debian-user-french * It is common for users to be redirected here from other lists, for example, from debian-project. It is also common for people to be posting here when English is not their primary language. Please be considerate. * The list is a Debian communication forum. As such, it is subject to both the Debian mailing list Code of Conduct and the main Debian Code of Conduct https://www.debian.org/MailingLists/#codeofconduct https://www.debian.org/code_of_conduct * This is a fairly busy mailing list and you may have to wait for an answer - please be patient. Please post answers back to the list so others can benefit; private conversations don't benefit people who may be following along on the list or reading the archives later. * Help and advice on this list is provided by volunteers in their own time. It is common for there to be different opinions or answers provided. * Please try to stay on topic. Arguments for the sake of it are not welcome here. Partisan political / religious / cultural arguments do not belong here either. Debian's community is world wide; do not assume others will agree with your views or need to read them on a Debian list. * There is an FAQ on the Debian wiki derived from some questions asked on this list at https://wiki.debian.org/FAQsFromDebianUser * One question that comes up on almost all Debian lists from time to time is of the form: "I have done something wrong / included personal details in an email. Could you please delete my name / details / remove the mail" Practically, this is impossible: the mailing lists are archived, potentially cached by Google and so on. Unfortunately, there is nothing much we can do to ensure that all copies anywhere on the Internet are deleted. Asking to do this may only serve to draw further attention - the so-called "Streisand effect" See: https://en.wikipedia.org/wiki/Streisand_effect Problems? = Complaints about inappropriate behaviour should be referred to the Debian Community Team . Inappropriate behaviour on the list may lead to warnings; repeated bad behaviour may lead to temporary or permanent bans for offenders.
Re: How to install the kernel 5.4.14 (source and headers) packages on Debian buster.
On Fri, Sep 01, 2023 at 01:16:31PM +0200, Mario Marietto wrote: > Hello to everyone. > > I've just installed Debian Buster on my ARM Chromebook,using this image : > > https://github.com/hexdump0815/imagebuilder/releases?page=12 > > He says that the image is based on the kernel 5.4 and it is. Infact the > default running kernel is 5.4.14. But for the project that I'm working on,I > also need to install the linux source and the headers packages for the same > kernel (5.4.14),but unfortunately,between the packages I only see versions > 4.19 and 5.10. Is there a method to install the sources and headers > packages also for the kernel 5.4.14 ? > You're out of luck - Debian doesn't offer 5.4 but does offer 5.10 - and what you've got is not from Debian. You might be able to install debootstrap and current kernel sources and build your own. I'd suggest starting from Debian 12 to build a current image. In the interim, you need to ask the person who provided that image where the source and headers are. > The point is that for the project that I'm working on (using qemu 5.1 + > enabling kvm + kernel 5.4 + libvirt on my ARM chromebook) I need the kvm.h > header,that's provided by the linux-headers (5.4.14) package. I can't use a > version of qemu greater than 5.1 and a version of the kernel greater than > 5.4. That's the reason why I'm asking this question. > Go and ask, maybe - we can't really help. PS: Thanks very much for clear formatting of this message which is much easier to read than some of your prior messages. > Thanks very much. > > -- > Mario. With every good wish, as ever, Andy Cater
Re: I uninstalled OpenMediaVault (because totally overkill for me) and replaced it with borgbackup and rsyncq
On Fri, 2023-09-01 at 07:25 -0500, John Hasler wrote: > Jason writes: > > Or how does your backup look like? > > Just rsync. Sorry, I just couldn't resist chiming in here. I have never used OpenMediaVault. I HAVE used a number of other backup methodologies, including Borgbackup, for which I had high hopes, but was highly disappointed. In the end, I currently have settled upon using rsnapshot to back up my single-machine, single-user setup to external external usb hard drive A, which is then copied to external usb hard drive B, using rsync. If you can do rsync, you can do rsnapshot. It's easy, especially when it comes to restoring, verifying, and impromptu access to data, to use random stuff, or even to just "check on" your data occasionally, to reassure yourself that it is still there. Yes, it does require considerable space (no data de-duplication), and the rsync of the backup drives does take considerable time. But to me, it is worth it, to avoid the methodological equivalent of "vendor lock- in". INB4: No, I don't do online backups. If people or organizations with nose problems want my data they are going to have to make at least a little effort to get it. And yes, I do know the 1-2-3 backup philosophy, which does seem like a good idea for many (most?) users. Also, I really like Clonezilla for occasional brute-force, scorched- earth backups, such as when preparing for a complete reinstall or release upgrade, or when switching to a new computer. (Note: everything above applies to backing up my data: (/home/[user] only). For backing up the actual system: (/ except for /home/[user]), I use (and like) Timeshift. It has saved my donkey more than once!) Well, that's what works for me. Feel free to disregard this. It may not work for you. And, "if it breaks, you get to keep both pieces"!
bookworm and network connections
I just upgraded my main server to bookworm, having successfully, over the course of the past couple of months, methodically upgraded my other machines with only minor issues. Unfortunately, the upgrade of the server, the most important of my machines, has not been smooth at all, even though no important errors appeared during the upgrade process. So right now the thing I want to fix is networking (which of course worked fine in the last few releases of debian, until now). The machine has two ethernet ports, which used to be eth0 and eth1 in the old days, but are now magically called "Wired connection enp11s0(eth0)" and "Wired connection enp12s0(eth1)". When I booted the machine after the upgrade, no networking was working at all, on either interface, even though: zserver# nmcli networking connectivity full zserver# which was definitely a lie, as nothing was successfully going in or out of the machine. Looking in more detail: [Z:~] nmcli enp12s0: connected to Wired connection enp11s0(eth0) "Intel I210" ethernet (igb), D8:50:E6:C2:76:03, hw, mtu 1500 ip4 default inet4 209.97.232.18/24 route4 209.97.232.0/24 metric 100 route4 default via 209.97.232.1 metric 100 inet6 fe80::e0c1:20a:c535:873c/64 route6 fe80::/64 metric 1024 lo: connected (externally) to lo "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 inet4 127.0.0.1/8 inet6 ::1/128 enp11s0: disconnected "Intel I210" 1 connection available ethernet (igb), D8:50:E6:C2:76:02, hw, mtu 1500 enp13s0: unavailable "Intel I210" ethernet (igb), D8:50:E6:C2:76:04, hw, mtu 1500 enp14s0: unavailable "Intel I210" ethernet (igb), D8:50:E6:C2:76:05, hw, mtu 1500 DNS configuration: servers: 127.0.0.1 209.97.224.2 209.97.224.3 interface: enp12s0 Somehow, it had got into a state where enp12s0 was connected to enp11s0 (whatever that means), with the result that nothing worked. So, after a bit of messing around with an increasing sense of desperation, I discovered that: [Z:~] sudo nmcli connection down "Wired connection enp11s0(eth0)" Connection 'Wired connection enp11s0(eth0)' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) [Z:~] sudo nmcli connection up "Wired connection enp11s0(eth0)" Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4) resulted in: [Z:~] nmcli enp11s0: connected to Wired connection enp11s0(eth0) "Intel I210" ethernet (igb), D8:50:E6:C2:76:02, hw, mtu 1500 ip4 default inet4 209.97.232.18/24 route4 209.97.232.0/24 metric 101 route4 default via 209.97.232.1 metric 101 inet6 fe80::1ae1:dfcf:be36:f72f/64 route6 fe80::/64 metric 1024 enp12s0: connected to Wired connection enp12s0(eth1) "Intel I210" ethernet (igb), D8:50:E6:C2:76:03, hw, mtu 1500 inet4 192.168.0.1/24 route4 192.168.0.0/24 metric 100 inet6 fe80::d30e:86f6:ca86:8986/64 route6 fe80::/64 metric 1024 lo: connected (externally) to lo "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 inet4 127.0.0.1/8 inet6 ::1/128 enp13s0: unavailable "Intel I210" ethernet (igb), D8:50:E6:C2:76:04, hw, mtu 1500 enp14s0: unavailable "Intel I210" ethernet (igb), D8:50:E6:C2:76:05, hw, mtu 1500 DNS configuration: servers: 127.0.0.1 209.97.224.2 209.97.224.3 interface: enp11s0 and indeed, everything was now working. Which was good, because I was running out of ideas, and had no way to reach the Internet to look for more help. Well, great, sort-of, except that every time I reboot I have to manually issue the two above nmcli commands to take down and bring back up enp11s. I tried putting them in my rc.local file, but that had no effect (for reasons that I don't understand; I was sure that that would paper over the problem). So how do I fix this so that the networking is configured to work correctly during the boot sequence, as it has always done before? (I suppose it has to be said explicitly: I did not change any configuration files ... indeed, these days I don't even know where the files are that control the network devices.) All the other machines that I have upgraded to bookworm have only a single ethernet port, which may be why I have not seen this issue after any other upgrade. Doc -- Web: http://enginehousebooks.com/drevans
Re: bookworm and network connections
On Fri, 1 Sep 2023 14:02:31 -0600
"D. R. Evans" wrote:
Hello D.,
>So how do I fix this so that the networking is configured to work
>correctly during the boot sequence, as it has always done before?
I had changing ethernet port issues and found that creating
/etc/systemd/network/99-default.link
with the stanza
--8X-
[Match]
MACAddress=AA:BB:CC:DD:EE:FF
# Substitute the real MAC address
[Link]
Name=ethN
# Replace N with something unique (e.g. 0)
--8X---
works well. I see no reason that creating two stanzas with (I hope) the
obvious changes, one for each i/f, should fail.
Now somebody's bound to come along and say
"No, there's a better way."
:-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Every single one of us
Devil Inside - INXS
pgpWQA_JWIojc.pgp
Description: OpenPGP digital signature
Re: bookworm and network connections
On 1 Sep 2023 14:02 -0600, from doc.ev...@gmail.com (D. R. Evans): > Well, great, sort-of, except that every time I reboot I have to manually > issue the two above nmcli commands to take down and bring back up enp11s. > > I tried putting them in my rc.local file, but that had no effect (for > reasons that I don't understand; I was sure that that would paper over the > problem). Well, as you note, it's not a fix. Still, if a workaround gets you closer to where you want to be... I don't think /etc/rc.local is executed by default on modern Debian systems. Have you checked to make sure that rc-local.service is enabled and actually gets started during boot? Is there anything relevant in the logs for that? Is /etc/rc.local set as executable? -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: bookworm and network connections
On Fri, Sep 01, 2023 at 08:32:40PM +, Michael Kjörling wrote: > I don't think /etc/rc.local is executed by default on modern Debian > systems. Have you checked to make sure that rc-local.service is > enabled and actually gets started during boot? Is there anything > relevant in the logs for that? Is /etc/rc.local set as executable? The rc-local.service is enabled by default. It will execute /etc/rc.local if it exists and is executable. The Debian installer used to create a stub /etc/rc.local file which had a correct shell script shebang, and the necessary permissions. This is longer created during installation, so the user would need to create it themselves, if they want to have it. They'd also have to know enough to put a correct shebang on it, and to do chmod +x. That's not a huge barrier to entry, but it's just enough to confuse some people. Double-checking "systemctl status rc-local.service" certainly wouldn't hurt, just to make sure everything's working as desired.
Re: bookworm and network connections
On 2023-09-01 at 16:50, Greg Wooledge wrote: > On Fri, Sep 01, 2023 at 08:32:40PM +, Michael Kjörling wrote: > >> I don't think /etc/rc.local is executed by default on modern Debian >> systems. Have you checked to make sure that rc-local.service is >> enabled and actually gets started during boot? Is there anything >> relevant in the logs for that? Is /etc/rc.local set as executable? > > The rc-local.service is enabled by default. It will execute /etc/rc.local > if it exists and is executable. > > The Debian installer used to create a stub /etc/rc.local file which had > a correct shell script shebang, and the necessary permissions. This is > longer created during installation, so the user would need to create > it themselves, if they want to have it. They'd also have to know enough > to put a correct shebang on it, and to do chmod +x. That's not a huge > barrier to entry, but it's just enough to confuse some people. It's actually still available, although I expect you're right that in a default configuration it won't be installed during Debian installation: $ dlocate /etc/rc.local initscripts: /etc/rc.local $ apt-cache policy initscripts initscripts: Installed: 3.07-1 Candidate: 3.07-1 Version table: *** 3.07-1 900 900 http://ftp.us.debian.org/debian testing/main amd64 Packages 900 http://ftp.us.debian.org/debian testing/main i386 Packages 100 /var/lib/dpkg/status $ cat /etc/rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. if test -d /etc/boot.d ; then run-parts /etc/boot.d fi This is in an environment that's running sysvinit, not systemd; 'sysvinit-core' currently depends on the 'initscripts' package. I'm not in a position to tell whether there would be issues trying to install 'initscripts' in a systemd environment, but I just offhand wouldn't particularly expect there to be. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: bookworm and network connections
On 2023-09-01, D. R. Evans wrote: > The machine has two ethernet ports, which used to be eth0 and eth1 in the old > days, but are now magically called "Wired connection enp11s0(eth0)" and "Wired > connection enp12s0(eth1)". If you want old names put in /etc/default/grub GRUB_CMDLINE_LINUX="net.ifnames=0" (add other parameters if you have some) and do update-grub > zserver# nmcli networking connectivity > full network manager is good for changing networks. For a server the network must not change normally. So you could put configuration in /etc/network/interfaces.d/ with something like : auto enp11s0 iface enp11s0 inet static mtu 1500 metric 101 address 209.97.232.18/24 netmask 255.255.255.0 gateway 209.97.232.1 auto enp12s0 iface enp12s0 inet static mtu 1500 metric 100 address 192.168.0.1/24 netmask 255.255.0.0 auto lo iface lo inet loopback I you want IPv6 add : iface enp11s0 inet6 auto iface enp12s0 inet6 auto Once it works you can then remove network manager
Re: I uninstalled OpenMediaVault (because totally overkill for me) and replaced it with borgbackup and rsyncq
Default User writes: On Fri, 2023-09-01 at 07:25 -0500, John Hasler wrote: > Jason writes: > > Or how does your backup look like? See https://lists.debian.org/debian-user/2019/11/msg00073.html and https://lists.debian.org/debian-user/2019/11/msg00420.html > Just rsync. Sorry, I just couldn't resist chiming in here. I have never used OpenMediaVault. I HAVE used a number of other backup methodologies, including Borgbackup, for which I had high hopes, but was highly disappointed. Would you care to share in what regards BorgBackup failed you? I am currently using `bupstash` (not in Debian unfortunatly) and `jmbb` (which I wrote for myself in 2013) in parallel and am considering switching to `bupstash` which provides just about all features that I need. Here are my notes on these programs: * https://masysma.net/37/backup_tests_borg_bupstash_kopia.xhtml * https://masysma.net/32/jmbb.xhtml And also the Bupstash home page: * https://bupstash.io/ IMHO borg is about the best backup program that you can get from the Debian repositories (if you need any of the modern features that is). The only issue I really had with it is that it was too slow for my use cases. In the end, I currently have settled upon using rsnapshot to back up my single-machine, single-user setup to external external usb hard drive A, which is then copied to external usb hard drive B, using rsync. If you can do rsync, you can do rsnapshot. It's easy, especially when it comes to restoring, verifying, and impromptu access to data, to use random stuff, or even to just "check on" your data occasionally, to reassure yourself that it is still there. Yes, it does require considerable space (no data de-duplication), and the rsync of the backup drives does take considerable time. But to me, it is worth it, to avoid the methodological equivalent of "vendor lock- in". Yes, the “vendor lock-in” is really a thing especially when it comes to restoring a backup but the fancy backup software just does not compile for the platform or is not available for other reasons or you are stuck on a Windows laptop without Admin permissions (wost case scenario?). I mitigated this with `jmbb` by providing for a way to restore individual files also using third-party utilities and I intend to mitigate this for `bupstash` by writing my own restore program (work-in progress: https://masysma.net/32/maxbupst.xhtml) INB4: No, I don't do online backups. If people or organizations with nose problems want my data they are going to have to make at least a little effort to get it. And yes, I do know the 1-2-3 backup philosophy, which does seem like a good idea for many (most?) users. The problem I have with offline backups that it is an inconvenience to carry around copies and that this means they are always more out of date than I want them to be. Hence I rely on encryption to store backups on untrusted storages. [...] Short but comprehensive resource on the subject (includes some advertising / I am not affiliated / maybe this has outlived the product it advertises for?): http://www.taobackup.com/index.html YMMV Linux-Fan öö pgptt2qvn0tQe.pgp Description: PGP signature
Re: How to install the kernel 5.4.14 (source and headers) packages on Debian buster.
Hello. I've got a crazy idea : I see that Ubuntu has a 5.4 kernel source and header package. Is there a method or tool to convert these packages to debian packages so that I can use them on Debian ? That's because I prefer Debian over Ubuntu. Thanks. On Fri, Sep 1, 2023 at 10:25 PM Andrew M.A. Cater wrote: > On Fri, Sep 01, 2023 at 01:16:31PM +0200, Mario Marietto wrote: > > Hello to everyone. > > > > I've just installed Debian Buster on my ARM Chromebook,using this image : > > > > https://github.com/hexdump0815/imagebuilder/releases?page=12 > > > > He says that the image is based on the kernel 5.4 and it is. Infact the > > default running kernel is 5.4.14. But for the project that I'm working > on,I > > also need to install the linux source and the headers packages for the > same > > kernel (5.4.14),but unfortunately,between the packages I only see > versions > > 4.19 and 5.10. Is there a method to install the sources and headers > > packages also for the kernel 5.4.14 ? > > > > You're out of luck - Debian doesn't offer 5.4 but does offer 5.10 - and > what you've got is not from Debian. > > You might be able to install debootstrap and current kernel sources > and build your own. I'd suggest starting from Debian 12 to build a > current image. > > In the interim, you need to ask the person who provided that image > where the source and headers are. > > > The point is that for the project that I'm working on (using qemu 5.1 + > > enabling kvm + kernel 5.4 + libvirt on my ARM chromebook) I need the > kvm.h > > header,that's provided by the linux-headers (5.4.14) package. I can't > use a > > version of qemu greater than 5.1 and a version of the kernel greater than > > 5.4. That's the reason why I'm asking this question. > > > > Go and ask, maybe - we can't really help. > > PS: Thanks very much for clear formatting of this message which is much > easier to read than some of your prior messages. > > > Thanks very much. > > > > -- > > Mario. > > With every good wish, as ever, > > Andy Cater > > -- Mario.
Re: bookworm and network connections
Thank you for your thoughts... As people are addressing the rc.local issue (I now realise that I shouldn't have mentioned it :-) )... I just checked, and: 1. rc.local is being executed; 2. it is executing the nmcli commands; 3. the commands are successful. But it remains true that when the boot is fully complete, the networking is still hosed in the way that I described. So, apparently, putting commands in rc.local doesn't provide the workaround that I expected. I think that we should concentrate on the underlying networking issue so that it comes up properly rather than being derailed by trying to fix the networking after the fact. [[ I speculate wildly that systemd or something doesn't complete configuring the network until after rc.local has finished processing (I know that rc.local executes late in the boot process, but I don't think that that means that everything else has *finished* executing when rc.local runs). I may easily be wrong, but really I don't think I care. ]] I just want to get the networking to come up properly :-) I don't understand modern systemd-controlled networking initiation well enough to know where to look for something that the upgrade might have clobbered, nor how I might go about fixing it. Doc -- Web: http://enginehousebooks.com/drevans
Re: I uninstalled OpenMediaVault (because totally overkill for me) and replaced it with borgbackup and rsyncq
Michel Verdier writes: On 2023-09-01, Default User wrote: > Yes, it does require considerable space (no data de-duplication), and > the rsync of the backup drives does take considerable time. But to me, > it is worth it, to avoid the methodological equivalent of "vendor lock- > in". You must have a bad configuration : rsnaphot de-duplicate using hard links so you never have duplicated files. Keeping 52 weekly and 7 daily and 24 hourly I need only 130% of original space. And it takes minimal time as it transfers only changes and can use ssh compression. It highly depends on the type of data that is being backed up. For my regular user files, I think a file-based deduplication works OK. But for my VM images, hardlinks would only save space for those VMs which did not run between the current and the preceding backup. Btw.: I am personally not using any hard-link based approach, mostly due to the missing encryption and integrity protection of data and metadata. HTH Linux-Fan öö pgp_XdT1JGgxv.pgp Description: PGP signature
Re: bookworm and network connections
On Fri, Sep 01, 2023 at 03:18:47PM -0600, D. R. Evans wrote: > [[ I speculate wildly that systemd or something doesn't complete configuring > the network until after rc.local has finished processing (I know that > rc.local executes late in the boot process, but I don't think that that > means that everything else has *finished* executing when rc.local runs). I > may easily be wrong, but really I don't think I care. ]] On Debian, there's an override file: unicorn:~$ cat /usr/lib/systemd/system/rc-local.service.d/debian.conf [Unit] # not specified by LSB, but has been behaving that way in Debian under SysV # init and upstart After=network-online.target # Often contains status messages which users expect to see on the console # during boot [Service] StandardOutput=journal+console StandardError=journal+console The "After=network-online.target" line is supposed to ensure that rc-local.service doesn't run until the network configuration has been completed. However, the definition of "completed" here can be murky. In particular, when using /etc/network/interfaces, only interfaces that are marked as "auto" need to be up, to satisfy this criterion. An interface that's only "allow-hotplug" isn't required to be up. Also, since the issue here involves network configuration, it would seem counterintuitive to expect it to be done in a service that runs *after* the network is supposed to be up.
Re: How to install the kernel 5.4.14 (source and headers) packages on Debian buster.
On Fri, Sep 01, 2023 at 11:15:38PM +0200, Mario Marietto wrote: > I've got a crazy idea : I see that Ubuntu has a 5.4 kernel source and > header package. Is there a method or tool to convert these packages to > debian packages so that I can use them on Debian ? That's because I prefer > Debian over Ubuntu. Thanks. Kernel packages tend to be very self-contained. It's likely that an Ubuntu kernel package would work on Debian without any changes. Try It And See. Make sure you have another kernel installed that you know can boot, and that you have the ability to boot into it, should the Ubuntu kernel fail.
Re: How to install the kernel 5.4.14 (source and headers) packages on Debian buster.
On Fri, Sep 01, 2023 at 11:15:38PM +0200, Mario Marietto wrote: > Hello. > > I've got a crazy idea : I see that Ubuntu has a 5.4 kernel source and > header package. Is there a method or tool to convert these packages to > debian packages so that I can use them on Debian ? That's because I prefer > Debian over Ubuntu. Thanks. > > It looks as if the image you installed was using the Ubuntu kernel and header - maybe look to see if there's a pure Debian image somewhere. I've never owned a Chromebook of any kind and can't remember what the solution allowing you to run a Debian VM under ChromeOS is. > On Fri, Sep 1, 2023 at 10:25 PM Andrew M.A. Cater > wrote: > > > On Fri, Sep 01, 2023 at 01:16:31PM +0200, Mario Marietto wrote: > > > Hello to everyone. > > > > > > I've just installed Debian Buster on my ARM Chromebook,using this image : > > > > > > https://github.com/hexdump0815/imagebuilder/releases?page=12 > > > > > > He says that the image is based on the kernel 5.4 and it is. Infact the > > > default running kernel is 5.4.14. But for the project that I'm working > > on,I > > > also need to install the linux source and the headers packages for the > > same > > > kernel (5.4.14),but unfortunately,between the packages I only see > > versions > > > 4.19 and 5.10. Is there a method to install the sources and headers > > > packages also for the kernel 5.4.14 ? > > > > > > > You're out of luck - Debian doesn't offer 5.4 but does offer 5.10 - and > > what you've got is not from Debian. > > > > You might be able to install debootstrap and current kernel sources > > and build your own. I'd suggest starting from Debian 12 to build a > > current image. > > > > In the interim, you need to ask the person who provided that image > > where the source and headers are. > > > > > The point is that for the project that I'm working on (using qemu 5.1 + > > > enabling kvm + kernel 5.4 + libvirt on my ARM chromebook) I need the > > kvm.h > > > header,that's provided by the linux-headers (5.4.14) package. I can't > > use a > > > version of qemu greater than 5.1 and a version of the kernel greater than > > > 5.4. That's the reason why I'm asking this question. > > > > > > > Go and ask, maybe - we can't really help. > > > > PS: Thanks very much for clear formatting of this message which is much > > easier to read than some of your prior messages. > > > > > Thanks very much. > > > > > > -- > > > Mario. > > > > With every good wish, as ever, > > > > Andy Cater > > > > > > -- > Mario. as above :) Andy
Re: bookworm and network connections
Greg Wooledge wrote on 9/1/23 15:38: In particular, when using /etc/network/interfaces, only interfaces that are marked as "auto" need to be up, to satisfy this criterion. An I don't think that debian has used used /etc/network/interfaces for a while, at least not by default. Certainly there's nothing useful there on the machine that I just upgraded and whose networking is failing to configure itself correctly. Network Manager -- I think -- uses some completely different mechanism for managing networking (although I have no idea what that mechanism is.) Doc -- Web: http://enginehousebooks.com/drevans
Re: bookworm and network connections
Hello, On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote: > I don't think that debian has used used /etc/network/interfaces for a while, > at least not by default. All of my Debian servers (and desktops) have an /etc/network/interfaces file and ifupdown installed. It depends upon choices made in the installer as to whether ifupdown is installed at all. > Network Manager -- I think -- uses some completely different mechanism for > managing networking (although I have no idea what that mechanism is.) Yes, it is ifupdown which uses that file. NetworkManager is configured another way. Uusally NetworkManager will ignore interfaces which are mentioned in /etc/network/interfaces, so if you have ifupdown installed and put stuff in /etc/network/interfaces, it should be ifupdown (and only that) that configures them. As others have mentioned, NetworkManager is not usually considered a good choice for servers with a static networking environment. You need to decide whether you are going to persevere with configuring NetworkManager, or switch to something else (generally ifupdown or systemd-networkd). I don't know enough about NetworkManager to advise you how to get out of the situation you are in. I only use it on laptops and generally don't touch it, there. Your situation appears to have been triggered by the renaming of your network interfaces (which was warned about in the release notes). You should decide whether to revert that (it's already been posted how to do that, also see the wiki link below), or go with it. Both of these are worth reading: https://wiki.debian.org/NetworkConfiguration https://wiki.debian.org/NetworkInterfaceNames Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: bookworm and network connections
On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote: > Greg Wooledge wrote on 9/1/23 15:38: > > > In particular, when using /etc/network/interfaces, only interfaces that > > are marked as "auto" need to be up, to satisfy this criterion. An > > I don't think that debian has used used /etc/network/interfaces for a while, > at least not by default. Certainly there's nothing useful there on the > machine that I just upgraded and whose networking is failing to configure > itself correctly. > > Network Manager -- I think -- uses some completely different mechanism for > managing networking (although I have no idea what that mechanism is.) Debian *absolutely* uses /etc/network/interfaces. By default, in a Standard installation. But as you noted, it's optional. Debian *also* allows the use of Network Manager, systemd-networkd, and probably several other systems for configuring one's network(s). I haven't installed Debian 12 yet (upgraded to it, but haven't installed it), but I did a Debian 11 install yesterday. And I can assure you, that system uses /etc/network/interfaces just like every other Debian system I've ever run. I used a Standard install, then booted it to confirm that all the necessary firmware was present, and then installed KDE (among other things). I don't know whether N-M is installed on that system -- I didn't check -- but it doesn't matter, because the machine's sole ethernet interface is configured in /e/n/i and therefore N-M would skip it. Returning to the previous topic, I have no idea how After=network-online.target interacts with N-M. I have experience with network-online.target vs. /e/n/i and its absurd "allow-hotplug" default setting, but I don't use N-M so I don't know how that works.
Re: bookworm and network connections
Andy Smith wrote on 9/1/23 16:32: Your situation appears to have been triggered by the renaming of your network interfaces (which was warned about in the release These weird names like "Wired connection enp11s0(eth0)" were names that the debian installer came up with several OS versions ago (stretch, perhaps?). Anyway, they haven't changed since bullseye, when everything worked (i.e., early this morning, before I ran the upgrade :-( ). Both of these are worth reading: https://wiki.debian.org/NetworkConfiguration https://wiki.debian.org/NetworkInterfaceNames I'll take a look at those. Doc -- Web: http://enginehousebooks.com/drevans
Re: bookworm and network connections
Michel Verdier wrote on 9/1/23 15:06: If you want old names put in /etc/default/grub GRUB_CMDLINE_LINUX="net.ifnames=0" Nice to know, but I'll stay with the new names, I think. network manager is good for changing networks. For a server the network must not change normally. So you could put configuration in /etc/network/interfaces.d/ with something like : auto enp11s0 iface enp11s0 inet static mtu 1500 metric 101 address 209.97.232.18/24 netmask 255.255.255.0 gateway 209.97.232.1 auto enp12s0 iface enp12s0 inet static mtu 1500 metric 100 address 192.168.0.1/24 netmask 255.255.0.0 When I'm feeling less tired and prone to making a mistake, I'll do this. The old method seems so much simpler, so I'd be happy to go back to it. It seems that enough people are using it that it doesn't seem likely that it'll go away anytime soon. When I installed debian on this computer -- quite a few years ago -- I'm pretty sure it just went off and installed all the Network Manager stuff without asking. And, to be honest, it's worked fine for the last several years. I can't imagine why its so messed up now. I (obviously) didn't change anything related to Network Manager myself; the upgrade is entirely responsible for its now-non-functioning state. I you want IPv6 add : iface enp11s0 inet6 auto iface enp12s0 inet6 auto I would love IPv6, but my ISP doesn't support it, and has no plans to do so, so for now I'm stuck in IPv4 land. Once it works you can then remove network manager That sounds like something to celebrate. I'll try to get time to work on all this over the weekend, and let everyone know how it turns out. Thanks to everyone for their suggestions. Doc -- Web: http://enginehousebooks.com/drevans
Re: bookworm and network connections
On Fri 01 Sep 2023 at 17:38:48 (-0400), Greg Wooledge wrote: > On Fri, Sep 01, 2023 at 03:18:47PM -0600, D. R. Evans wrote: > > [[ I speculate wildly that systemd or something doesn't complete configuring > > the network until after rc.local has finished processing (I know that > > rc.local executes late in the boot process, but I don't think that that > > means that everything else has *finished* executing when rc.local runs). I > > may easily be wrong, but really I don't think I care. ]] > > On Debian, there's an override file: > > unicorn:~$ cat /usr/lib/systemd/system/rc-local.service.d/debian.conf > [Unit] > # not specified by LSB, but has been behaving that way in Debian under SysV > # init and upstart > After=network-online.target > > # Often contains status messages which users expect to see on the console > # during boot > [Service] > StandardOutput=journal+console > StandardError=journal+console > > > The "After=network-online.target" line is supposed to ensure that > rc-local.service doesn't run until the network configuration has been > completed. However, the definition of "completed" here can be murky. > In particular, when using /etc/network/interfaces, only interfaces that > are marked as "auto" need to be up, to satisfy this criterion. An > interface that's only "allow-hotplug" isn't required to be up. > > Also, since the issue here involves network configuration, it would > seem counterintuitive to expect it to be done in a service that runs > *after* the network is supposed to be up. I don't see that the OP is doing anything complicated that requires rc.local to run at all. They just need to distinguish between the two interfaces, and then configure them in a conventional manner. A .link file and the ifupdown package should be able to cope with that. (I haven't used the buster-onwards interface matching/renaming facility myself, which could replace using the .link file.) On Fri 01 Sep 2023 at 18:33:51 (-0400), Greg Wooledge wrote: > On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote: > > Greg Wooledge wrote on 9/1/23 15:38: > > > > > In particular, when using /etc/network/interfaces, only interfaces that > > > are marked as "auto" need to be up, to satisfy this criterion. An > > > > I don't think that debian has used used /etc/network/interfaces for a while, > > at least not by default. Certainly there's nothing useful there on the > > machine that I just upgraded and whose networking is failing to configure > > itself correctly. > > > > Network Manager -- I think -- uses some completely different mechanism for > > managing networking (although I have no idea what that mechanism is.) > > Debian *absolutely* uses /etc/network/interfaces. By default, in a > Standard installation. But as you noted, it's optional. Debian *also* > allows the use of Network Manager, systemd-networkd, and probably several > other systems for configuring one's network(s). > > I haven't installed Debian 12 yet (upgraded to it, but haven't installed > it), but I did a Debian 11 install yesterday. And I can assure you, > that system uses /etc/network/interfaces just like every other Debian > system I've ever run. I used a Standard install, then booted it to > confirm that all the necessary firmware was present, and then installed > KDE (among other things). I don't know whether N-M is installed on > that system -- I didn't check -- but it doesn't matter, because the > machine's sole ethernet interface is configured in /e/n/i and therefore > N-M would skip it. Installing bookworm (standard packages, no DE) installed and configured ifupdown as per usual here. > Returning to the previous topic, I have no idea how > After=network-online.target interacts with N-M. I have experience with > network-online.target vs. /e/n/i and its absurd "allow-hotplug" default > setting, but I don't use N-M so I don't know how that works. I know you have a low opinion of allow-hotplug, but I can't see that auto/allow-auto is necessarily better for the naive user that doesn't install a DE for whatever reason. AIUI auto gives you a one-shot attempt to start the network at boot time, and if that fails for any reason (eg USB not yet plugged in/ not detected/hardblocked on/etc), you get a long timeout before the login prompt, and may have to reboot to get it to attempt again. OTOH allow-hotplug gets you to a login prompt as normal, without the network being up, and then rectifying the problem makes ifupdown/udev automatically have another go. Cheers, David.
Re: bookworm and network connections
On Fri, Sep 01, 2023 at 08:40:43PM -0500, David Wright wrote: > I know you have a low opinion of allow-hotplug, but I can't see that > auto/allow-auto is necessarily better for the naive user that doesn't > install a DE for whatever reason. > > AIUI auto gives you a one-shot attempt to start the network at boot > time, and if that fails for any reason (eg USB not yet plugged in/ > not detected/hardblocked on/etc), you get a long timeout before the > login prompt, and may have to reboot to get it to attempt again. > > OTOH allow-hotplug gets you to a login prompt as normal, without the > network being up, and then rectifying the problem makes ifupdown/udev > automatically have another go. It depends on the hardware, and how the system is going to be used. A built-in ethernet interface SHOULD NOT be configured as "allow-hotplug". It should be "auto". I'd argue that the same applies to a PCI card or other non-built-in but internal device. If you have to take the machine apart to remove the device, it's "auto". allow-hotplug is intended for things like USB ethernet interfaces, as you mention. They're literally hot-pluggable, and may not be present when the system is booted. If you're dealing with one of those, then by all means, use allow-hotplug for it. That's what it's for. My gripe is that the installer has (traditionally?) used allow-hotplug for ALL ethernet interfaces, including the built-in interfaces on a server. This causes massive problems with the ordering of service initializations at boot. It took me a *long* time and a lot of digging to figure out why things were breaking, so I try to pass that knowledge along for others.
Re: Sleep: out of control
On 01/09/2023 18:08, Tom Browder wrote: When switching the KVM between the Win and Deb hosts, I could see the mouse was not getting power (no sensor light) nor was the keyboard or monitor screen. So that is probably why I could not wake up the Debian PC by stirring the mouse or hitting a key. My conclusion: I need to find out which sleep modes turn off power to the external input devices. It might depend on USB hubs on motherboards (wiring and whether particular chips retain power and support switching off power on particular ports) and on wake on USB implementation and settings in firmware. An example: an external keyboard is connected through a USB hub built-in into a monitor. The laptop may be waked up by pressing any key on the external keyboard. However if monitor is powered off (using its power button or the switch on a AC power line filter) then wake on USB does not work any more after the monitor switched on again. Once I tried if I can power off laptop USB ports to avoid battery drain in sleep state by an external USB hub. I was unable to do it for a particular laptop. The uhubctl project has some list of supported hardware.
Re: How to install the kernel 5.4.14 (source and headers) packages on Debian buster.
On 02/09/2023 04:15, Mario Marietto wrote: I've got a crazy idea : I see that Ubuntu has a 5.4 kernel source and header package. Is there a method or tool to convert these packages to debian packages so that I can use them on Debian ? Kernel image from one project and headers+sources from another one may be a call to trouble due to different config and set of patches. I suspect that kernel image+modules packages from Ubuntu would not work for you. Having config for your current kernel in /boot you may try to rebuild the whole suite from sources (if you can get applied patches).
Re: bookworm and network connections
David Wright wrote on 9/1/23 19:40: I don't see that the OP is doing anything complicated that requires rc.local to run at all. They just need to distinguish between the two Correct. I was simply trying to workaround the problem by putting commands into rc.local that are known to work when I type them manually. I wish I had never mentioned rc.local. It seems to have taken over the thread, whereas it's not the problem that I'm trying to fix at all :-( Regarding the whole "Network Manager versus old-style" thing, I would gladly have done it all old style, except that when I first installed debian on the system, it went the Network Manager route. And because that all worked until today's upgrade (which was, I think, the third upgrade upgrade of debian stable on the machine; so it worked correctly for a lustrum or so), I didn't pay much attention to it apart from being mildly annoyed that it looked a lot more complicated than old-style network management. The real problem remains, per the original post, that Network Manager isn't configuring the interfaces properly and seems to be sort-of setting one interface to be the same as the other, with the result that neither of them work. I'm going to try switching to old-style when I feel confident that I have enough high-quality time to make the switch, and I expect that to work. It would be nice to really fix the Network Manager misconfiguration; but it seems that the expertise here is all with old-style. Which is fine. I'm happy to go back to old-style. I probably need to file some sort of bug report against the upgrade, but I'd like to get a better feel for how the misconfiguration is happening before I do that. Doc -- Web: http://enginehousebooks.com/drevans
