prompt stringlengths 1 58.2k | completion stringlengths 1 53.1k |
|---|---|
Hi, I'm usually connected to an EDUROAM wifi network. Up to a few days ago, it was working just fine, and then it stopped working. I don't recall updating my system (Debian stable), so I don't think that something broke because of that. The only thing I tried these previous days was to install Weylus (from their GitHub repo), but I undid all the changes that it caused. I know this could be specific to a network more than Debian, but I thought I would give it a shot since the IT department at my University does not give support for Linux. Does anybody know what I can try to fix the problem? Thanks! | Hello, emek wrote: 2025-04-03 22:05 I'm usually connected to an EDUROAM wifi network. Up to a few days ago, it was working just fine, and then it stopped working. [..] Does anybody know what I can try to fix the problem? Perhaps it would help to give some details about: 1) What is "EDUROAM wifi network" ? 2) What version of Debian are you running ? 3) How do you configure the wireless network in Debian ? 4) How do you normally connect to the "EDUROAM wifi network" with Debian ? 5) How does the connection attempt to the "EDUROAM wifi network" currently fail ? 5) How do you authenticate yourself to the "EDUROAM wifi network" ? 6) What programs have you installed to connect to the "EDUROAM wifi network" ? 7) Can you connect Debian to other different wifi networks ? Which wireless network card is your computer equipped with ? Hope this helps. -- note: please modify the subject of the first post |
Hi there, I'm searching for a way to disable syslog messages written by dbus-daemon. I have read this : https://dbus.freedesktop.org/doc/dbus-daemon.1.html Then I tried to create a /etc/dbus-1/system-local.conf and use the "nosyslog" option but then dbus fails to start. Hence the question, how to use the "nosyslog" option to disable log messages from dbus-daemon. Thanks in advance. | Why not just filter the journalctl command by priority to not show all messages. journalctl -b -p 3 will just show error messages, -p 4 will show warnings. You can limit the size of the journal log in its config file if that's what you are concerned about. |
Hello Friends For Debian 12 as Server I am trying to define a static IP. About the official documentation I read the following links: 5.3. The modern network configuration without GUI SystemdNetworkd Thus in the /etc/systemd/network directory was created the static.network file with its respective settings. Now the reason of this post. In both links are covered about How to define DHCP and Static IPs but is indicated the following in the second link: Next enable systemd-networkd. You don't need to start the service yet because your old network is still running and there is currently no systemd-networkd defined. systemctl enable systemd-networkd If is executed the systemctl list-units | grep network command appears the following: Code: Select allnetworking.service load active exited Raise Network interfaces network.target load active active Network And for the systemctl list-unit-files | grep network command appears the following: Code: Select allnetworking.service enabled enabled systemd-network-generator.service disabled enabled systemd-networkd-wait-online.service disabled disabled systemd-networkd-wait-online@.service disabled enabled systemd-networkd.service disabled enabled systemd-networkd.socket disabled enabled network-online.target static - network-pre.target static - network.target static - Until here: The "network service manager" is networking.service systemd-networkd.service is disabled Even more, the networkctl list command in its output has as the first line the following: Code: Select allWARNING: systemd-networkd is not running, output will be incomplete. Therefore if to define DHCP and Static IPs is mandatory work with systemd-networkd Question Why from the beginning is disabled the systemd-networkd service? I want understand the reason about this approach Therefore from the previous question arises a parallel question as follows: What does networking.service have in special over systemd-networkd? Thank You | manueljordan wrote: 2025-03-25 23:23 I want understand the reason about this approach Code: Select all$ dpkg -S networking.service ifupdown: /lib/systemd/system/networking.service Well, I haven't transitioned yet but most systemd things slowly take over from prior methods. So everyone plays nicely together, kind of, for awhile until the transition is complete. Various network setups can be used, some step on each other and some mix. I'm not thinking of removing ifupdown any time soon, but following that time is when the systemd version needs turned on. I think this is still a hybrid of old and new. |
Hi Debianers, I'm trying to access my university's network using openvpn. I've got a certificate from my university which can be used to connect using openvpn. After connecting though I'm unable to browse the internet. I dug around a bit for a solution. I pinged google using both their domain name and IP address and found that I got a response only when I was using the IP address. This led me to believe that the DNS resolution is not working. I was able to understand that the remote server provides a DNS address and blocks my device to use original DNS provider. And usually openvpn rewrites /etc/resolv.conf to append the DNS of the VPN server. In my case, it is not happening. I checked /etc/resolv.conf before & after connection. I tried modifying my .ovpn file according to this post (https://serverfault.com/questions/77457 ... ot-working). This still couldn't fix the issue. I spun up a virtual machine for Ubuntu to see if it is something wrong with the .ovpn file, but there openvpn was working as intended. So please help! | You can use openvpn with networkmanager, that way you have only one program writing to /etc/resolv.conf |
Using MariaDB for the first time on Debian, I ran into a strange issue I did not observe on other OSes: the server did not accept root's and the users passwords from the CGI, so I was unable to access the SQL server. That only worked once after I entered this, as this seems to be a solution widely recommended in this case: Code: Select allMariaDB [(none)]> ALTER USER 'root'@'localhost' IDENTIFIED VIA mysql_native_password USING PASSWORD('ndrgnon23efrenUTGvbCtynFXŴDijUNvewINwBberfbiobni141ninIBesdvcNIfferONefr37vr4fBUewNIBN'); But, now I can no longer log into the MariaDB console, as it does not accept the password entered above, and neither the old password. How can I restore MariaDB access and configure it in a way that it works both from console and from CGI, as one is accustomed from other unixoids? | Hello, What is the MariaDB's username having trouble authenticating with the database server ? What are the commands that fail when you try to authenticate that username ? Can you provide the log of failed attempts (commands and message errors) ? |
I know what each of these command do, problem is that only last and lastlog work while lastb and faillog do not work. Command breakdown in regard which files are read when these commands are executed: - last (reads /var/log/wtmp) - lastb (reads /var/log/btmp) - lastlog (reads /var/log/lastlog) - faillog (reads /var/log/faillog) On my system (bookworm) btmp and faillog files are empty, 0 bytes, hence why the commands do not work. The other two files wtmp and lastlog are not empty so the commands for them work as expected. I've read the following stackexchange question: https://unix.stackexchange.com/question ... llog-count There under comments some people say it's a bug, and there is also a link stating that the bug has been fixed, however the question relates to Debian 10 but issue is present in bookworm, so slightly out of date. Question: Why don't lastb and faillog work and why are their files btmp and faillog empty? Question 2: What do I need to configure to make these 2 commands work? OR Is this still a bug in bookworm and/or testing branch? | Hello, Frostblade wrote: 2025-03-29 14:59 On my system (bookworm) btmp and faillog files are empty, 0 bytes, hence why the commands do not work. The faillog commands has been removed from the login binary package both in Debian Testing and Debian Unstable. The following bug report is about the notification in the NEWS.Debian file for faillog: Debian Bug report logs - #1074320 login: clean up now obsolete /var/log/faillog The last command has been removed from the util-linux binary package since current Debian Testing and Debian Unstable and implemented in the wtmpdb package: # apt show util-linux [..] util-linux (2.40.1-3) unstable; urgency=medium * Stop installing last(1), Suggest: wtmpdb instead -- Chris Hofstaedtler <zeha@debian.org> Wed, 29 May 2024 23:58:19 +0200 [..] This is the description for the wtmpdb package: Code: Select all# apt show wtmpdb Package: wtmpdb Version: 0.72.0-1 Priority: standard Section: admin Maintainer: Andrew Bower <andrew@bower.uk> Installed-Size: 75.8 kB Pre-Depends: init-system-helpers (>= 1.54~) Depends: libaudit1 (>= 1:2.2.1), libc6 (>= 2.38), libsystemd0 (>= 222), libwtmpdb0 (= 0.72.0-1) Recommends: libpam-wtmpdb Breaks: util-linux (<< 2.40.1-3) Replaces: util-linux (<< 2.40.1-3) Homepage: https://github.com/thkukuk/wtmpdb/ Download-Size: 19.3 kB APT-Sources: http://192.168.122.1:3142/debian testing/main amd64 Packages Description: utility to display login/logout/reboot information This package provides the program wtmpdb, which reads wtmp's database of user logins/logouts and system reboots. . It provides a year 2038-safe replacement for the traditional Unix "last" utility. The lastb command has been removed in Debian Testing and Debian Unstable from the login package. By the way, the lastb command works on my Debian Bookworm. Hope this helps. -- [1] https://github.com/util-linux/util-linux |
Hi all, I have just reinstalled Debian Bookworm to solve a wifi problem and now I have wifi and ethernet both working but I can't access the internet. It must have worked last night when the installation took place as it was a "netinst" image that I downloaded and put on my usb stick. I generally have a few local things showing on my screen so when wifi worked I thought all was well and hadn't noticed no internet until I started to install Home Assistant but got "could not resolve" errors. I think something in the install instructions broke the internet for me.. This is maybe where it is (direct from the install instructions): apt install \ apparmor \ bluez \ cifs-utils \ curl \ dbus \ iproute2 \ jq \ libglib2.0-bin \ lsb-release \ network-manager \ nfs-common \ systemd-journal-remote \ systemd-resolved \ systemd-timesyncd \ udisks2 \ wget -y Probably a network-manager setting that I don't get ? Maybe someone can help, I would be very grateful. Thanks, | usernamepasswordbs wrote: 2025-04-02 06:33 It's fixed !! Not sure how though. What did I do now...can't remember exactly, I know, sorry. I'm glad you sorted it out. Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message (after other tags, if any). Thanks. -- edit Sat Apr 12 09:43:04 CEST 2025: marked as solved. |
Searching around (both here and on other forums) I've come to realize this is a somewhat common issue. Alas, there doesn't seem to be a specific solution (or even narrowed done set of solutions). I'm using Debian 12 KDE on a Lenovo mini laptop. Attempting to change the monitor brightness either with the corresponding keys or using the brightness slider (or even from terminal) shows a numerical change (i.e. I see the applet indicating the brightness level changing), however this does not correspond to an actual change in monitor brightness, which seems to be at about 50%. /sys/class/backlight has one entry, acpi_video0. Any changes of brightness control (i.e. moving the slider or using the buttons) correspond to the numerical values changing (that is, e.g. acpi_video0/brightness changes, containing the new value). However, as I said, this doesn't reflect in actual brightness difference. For testing, I booted a live USB Fedore KDE. There, /sys/class/backlight contains a different entry, intel_backlight, and controls/slider work: The actual monitor brightness changes. I've already tried kernel boot parameters like acpi_backlight=native (as well as vendor, video, and none), to no avail. This is probably a simplistic way of putting it, but how do I use intel_backlight on Debian, since this seems to be working on Fedora? | Hello, Your computer is a LENOVO MIIX 300-10IBY 80NR marketed in 2015. It uses a special form-factor (it is a tablet with a separate keyboard). So, it is not a common laptop. JohnWasRight wrote: 2024-08-31 08:57 For testing, I booted a live USB Fedore KDE. There, /sys/class/backlight contains a different entry, intel_backlight, and controls/slider work: The actual monitor brightness changes. What is the Fedora kernel version and/or the Fedora version ? JohnWasRight wrote: 2024-09-01 04:22 The machine is several years old. Bought it in 2016 I think. Here's the output of inxi -Fa --za: Code: Select allGraphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Lenovo driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: DSI-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0f31 class-ID: 0300 Display: wayland server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9 compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :1 screens: 1 Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 339x212mm (13.35x8.35") s-diag: 400mm (15.74") Monitor-1: DSI-1 mapped: XWAYLAND0 res: 1280x800 hz: 60 dpi: 151 size: 216x135mm (8.5x5.31") modes: 800x1280 API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (BYT) direct-render: Yes The intel_backlight file in /sys/class/backlight is generated by the kernel: it may be useful to check the system journal after booting with the kernel parameter drm.debug=0x1ff (this should enable diagnostic messages in the DRM kernel code of the i915 kernel module, which should be responsible for handling display brightness) What is the output of the following commands ? Code: Select allcd /sys/class/backlight ls -la cd acpi_video0/ ls -la cat brightness cat max_brightness cat actual_brightness cat scale What is the current BIOS version ? What happens if you switch from Wayland to Xorg instead of Wayland as Desktop Manager ? Does the brightness is correctly handled ? Hope that helps. |
I've searched here and elsewhere online, and can't find a solution to my problem. I have a laptop that has not been used in several days. Today when I turned it on, it was unable to resolve any hostnames on the network. SSH, ping, everything I tried would not work using hostnames to any other machines on the network. All the other machines can resolve hostnames without issues, and this previously worked on the laptop. I can ssh to the laptop from other computers using its hostname. I can use ping, SSH, et al on the laptop by using the network IP address, just not with hostnames. I can't find any issues with any conf files, at least nothing I recognize, and comparing them to the same files on other computers, they seem mostly identical. I can't figure out why this happened to one machine, out of the blue. FWIW, all computers on the network are running Debian. | Hello, You can inspect the status of your debian installation with the following commands: Code: Select allip link ip address ip route cat /etc/hosts cat /etc/nsswitch.conf cat /etc/resolv.conf getent ahostsv4 getent ahostsv4 <canonical name> getent ahostsv4 www.google.com |
Hi there, I am trying to create a minimal debian system with just the stuff to work as a media center on an old laptop. I used live-build to create the .iso file. The configuration parameters are as following: Code: Select all--distribution stable \ --archive-areas "main non-free-firmware" \ --debootstrap-options "--variant=minbase" \ --debian-installer live \ I built the live system with the following packages in: Code: Select alllxde-core lxappearance ceni lxpolkit adwaita-icon-theme gnome-themes-extra gnome-themes-extra-data spice-vdagent xorg firefox-esr obconf lxappearance-obconf I copied the .iso to a usb sticks and when I boot it in live mode the wired connection can connect to other devices on the LAN, but can't reach the outside world. This is the /etc/network/interfaces file: Code: Select allauto lo iface lo inet loopback auto enp3s0 allow-hotplug enp3s0 iface enp3s0 inet dhcp Ceni shows enp3s0 in the logical interfaces list, but I suppose it should be in the hardware interfaces one EDIT 04/11 i realized that enp3s0 is not connected to the LAN more often than it is. If I try to ifdown/up it I get this answer Code: Select allNo working leases in persistent database - sleeping | Hello, learning wizard wrote: 2025-04-10 12:09 [..] If I try to ifdown/up it I get this answer Code: Select allNo working leases in persistent database - sleeping This error appears when the dhcp client cannot receive leases (IP addresses) from the dhcp server in your network. isc-dhcp/4.4.3-P1-6/client/dhclient.c You should be able to get more information from your system logs with the command: Code: Select allsudo journalctl -b -g dhcp Hope this helps. |
Once and for all DISABLE MAC RANDOMIZATION? The idea that a wired NIC should have a randomized MAC... Has to be one of the !!!!... So how do you explicitly disable ALL MAC RANDOMIZATION on wired NICs? I have spent over 2 hours trying 5 or 6 methods, include macchanger... NOTHING IS WORKING with Debian 12. Using NetworkManger but I realize the randomization maybe coming from systemd? Or somewhere else? Have clients that use PCLAAs and MAC auditing... so RANDOMIZED MACS IS A HORRIBLE IDEA! How do I DISABLE this horrible feature!??? | johndough wrote: 2025-04-04 09:50 Obviously it should be 'randomiSation' Obviously you are from a part of the world that is not the US of A. |
I'm running Linux version 6.1.0-26-amd64 Code: Select all$ uname -r 6.1.0-26-amd64 To get my VirtualBox host running, I need to run Code: Select all/sbin/vboxconfig. That command generates the following error: Code: Select allPlease install the Linux kernel "header" files matching the current kernel for adding new hardware support to the system. The distribution packages containing the headers are probably: linux-headers-amd64 linux-headers-6.1.0-26-amd64 The first package is in the Debian package repo, but the second one gives an error. Code: Select allNo such package (view) How can I get the header files for my current version of Debian linux? Thank you. | https://snapshot.debian.org/ |
I'm running my own mail server using postfix on debian 12. My installed postfix version is 3.7.11-0+deb12u1. In my main.cf, I have Code: Select allsmtpd_tls_security_level=encrypt This should, according to the manual, enforce TLS encryption for incoming connections, or else refuse it. However, I'm seeing unencrypted mail come in. If I run wireshark, I can see entire messages in plaintext. I have another postfix server on a different machine that I configured both with smtp_tls_security_level=encrypt and with smtp_tls_security_level just empty/commented out. With "encrypt," mail to my debian server is encrypted successfully. With it disabled, messages are sent in plaintext. Here's my main.cf: Code: Select all 1 smtpd_banner = $myhostname ESMTP 2 biff = no 3 append_dot_mydomain = no 4 readme_directory = no 5 queue_directory = /var/spool/postfix 6 command_directory = /usr/sbin 7 data_directory = /var/lib/postfix 8 meta_directory = /etc/postfix 9 sendmail_path = /usr/sbin/sendmail 10 newaliases_path = /usr/bin/newaliases 11 mailq_path = /usr/bin/mailq 12 setgid_group = postdrop 13 html_directory = no 14 manpage_directory = /usr/share/man 15 readme_directory = no 16 home_mailbox = Maildir/ 17 compatibility_level = 3.6 18 smtpd_tls_cert_file=/etc/certs/server.pem 19 smtpd_tls_key_file=/etc/certs/serverkey.pem 20 smtpd_sasl_type=dovecot 21 smtpd_sasl_path=private/auth 22 smtpd_sasl_auth_enable=yes 23 smtpd_tls_auth_only=yes 24 smtp_tls_security_level=encrypt 25 smtpd_tls_security_level=encrypt 26 tls_random_source=dev:/dev/urandom 27 smtpd_tls_loglevel=4 28 smtpd_sasl_security_options=noanonymous,noplaintext 29 smtpd_sasl_tls_security_options=noanonymous 30 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache 31 smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache 32 smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination 33 mail_owner = postfix 34 myhostname = myserver 35 mydomain = mydomain.com 36 mydestination = $mydomain, localhost 37 relay_domains=$mydomain 38 mynetworks_style=subnet 39 inet_interfaces = all 40 inet_protocols = all 41 smtpd_milters = local:/var/spool/postfix/opendkim/opendkim.sock 42 non_smtpd_milters = $smtpd_milters 43 milter_default_action = accept 44 unknown_local_recipient_reject_code=550 45 debug_peer_level=2 46 debugger_command = 47 PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin 48 ddd $daemon_directory/$process_name $process_id & sleep 5 Is this a bug in postfix or do I have something configured incorrectly? | https://www.postfix.org/TLS_README.html#server_tls wrote:According to RFC 2487 this MUST NOT be applied in case of a publicly-referenced Postfix SMTP server. This option is off by default and should only seldom be used. Maybe it doesn't enforce it for "public" traffic. Not sure how it would determine that programmatically, but your tests seem to confirm. Edit: sorry, misread your local test result. |
Greetings, and thank you for any time you spend on this problem beforehand. I recently got myself an Intel (H310M S2H 2.0) motherboard, which reportedly could connect to the internet only through WLAN. To test this I booted Linux Lite through USB, and I could indeed access the internet only through WLAN. I tried changing the ethernet cables, the ports which I plugged them into the router, using an ethernet card, switching the slots of the Wi-Fi and ethernet cards, toggling various options in the BIOS and updating it. The LAN port itself seems to function as well - the connection speed LED (orange) is active, and the activity LED (yellow) blinks, which is why I think that this may be a software-side problem. For now I have installed the GNOME desktop, the wired connection appears as active. Here are the outputs of some commands I tried before making this post with the wired connection active: ip a Code: Select all1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b4:2e:99:bb:af:d9 brd ff:ff:ff:ff:ff:ff inet 10.218.52.25/20 brd 10.218.63.255 scope global dynamic noprefixroute enp4s0 valid_lft 171931sec preferred_lft 171931sec inet6 fe80::b62e:99ff:febb:afd9/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 06:fb:d0:3d:af:45 brd ff:ff:ff:ff:ff:ff permaddr 58:11:22:20:db:fd ip route Code: Select alldefault via 10.218.48.1 dev enp4s0 proto dhcp src 10.218.52.25 metric 100 10.218.48.0/20 dev enp4s0 proto kernel scope link src 10.218.52.25 metric 100 ping 8.8.8.8 Code: Select allPING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 27 packets transmitted, 0 received, 100% packet loss, time 26538ms For more context, ethernet allegedly worked before, up until a certain point. The machine back then was running Windows I believe. I have time and am willing to do more troubleshooting, please, help me get ethernet working on that system | Hello, Apart from booting Linux Lite, what is the Debian version you are running ? What is the hardware do you use to connect to the internet ? It would be useful if you could provide more information about your hardware and software configuration using the following command (the inxi program must be installed): Code: Select allinxi -F -v 7 -z -s You can paste the logs into the body of a follow-up message between code tags (if they fit the size of a forum message). |
One of the most annoying things with Debian is the long wait after installing a package, even the smallest, simplest one. "Processing triggers for man-db" What happens there actually is that the whole manual pages database gets rebuilt, to produce a cache for formatted manual pages with a line width of 80 characters. Today's computers are so fast that they can format a manual page on-the-fly in the fraction of a second. So it is not only a waste of users' time to have them wait 15+ minutes every time they want to install a program, just to rebuild a cache that practically never gets used. Much worse, this shows a lack of respect for the user. So my question: What is the recommended method to non-interactively (e.g. not asking the user for confirmation) permanently deactivate this brain-damaged manual page cache rebuild? | Hello, According to previous posts, there's something wrong with your installation regarding the manual pages database. You can try to check what it is. When a package triggers the manual pages database update, the following code from the postinst script of the man-db package is executed: man-db/2.11.2-2/debian/postinst (line 36) Code: Select allif [ "$1" = triggered ]; then ensure_catdir # We don't print a status message here, as dpkg already said # "Processing triggers for man-db ...". run_mandb "" -pq exit 0 fi The triggered function in the postinst script of the mandb package is: run_mandb () Code: Select allrun_mandb () { if [ ! -e /var/lib/man-db/auto-update ]; then echo "Not building database; man-db/auto-update is not 'true'." >&2 return 0 fi # shellcheck disable=SC3043 local message="$1" shift [ "$message" ] && echo "$message" >&2 # start-stop-daemon isn't available when running from debootstrap. if command -v setpriv >/dev/null; then setpriv --reuid man --regid man --init-groups -- /usr/bin/mandb "$@" || true else # runuser isn't ideal here, because it starts a PAM session. # However, setpriv is only available on Linux. runuser -u man -- /usr/bin/mandb "$@" || true fi } So the command that is executed when the postinst or postrm script of an installing package triggers the mandb database update (after installing/removing man pages) is: Code: Select all/usr/bin/mandb -pq where the -p and -q options stand for: Code: Select all$ mandb -h Usage: mandb [OPTION...] [MANPATH] -c, --create create dbs from scratch, rather than updating -C, --config-file=FILE use this user configuration file -d, --debug emit debugging messages -f, --filename=FILENAME update just the entry for this filename -p, --no-purge don't purge obsolete entries from the dbs -q, --quiet work quietly, except for 'bogus' warning -s, --no-straycats don't look for or add stray cats to the dbs -t, --test check manual pages for correctness -u, --user-db produce user databases only -?, --help give this help list --usage give a short usage message -V, --version print program version You can check the behaviour of this command by using the --debug option and without the --quiet option: Code: Select alltime /usr/bin/mandb --debug -p You can also try to check which function(s) it is stuck in by tracing syscalls and their timings (the strace package must be installed):Code: Select allsudo strace -C -o mandb-statistics.log /usr/bin/mandb --debug -p The mandb-statistics.log will be generated, containing both the strace log and the statistics at the end of the file. You may want to consider compressing the mandb-statistics.log file and sharing it in a follow-up post. Hope this helps. -- notes: The /var/lib/man-db/auto-update file is created by debconf on behalf the man-db package: man-db/2.11.2-2/debian/postinst/?hl=76#L70 Code: Select all# debconf forms the interface used to suppress man-db updates during # automatic package builds (see https://bugs.debian.org/554914), but we # cache that value in the file system to avoid having to use debconf when # processing triggers. db_get man-db/auto-update if [ "$RET" = true ]; then touch /var/lib/man-db/auto-update else rm -f /var/lib/man-db/auto-update fi This is an excerpt from the documentation from the debconf-devel manual page : debconf-devel manual page Code: Select all#!/bin/sh set -e . /usr/share/debconf/confmodule db_get mypackage/reboot-now if [ "$RET" = true ]; then shutdown -r now fi |
Hi. I have been working at this for a bit. I am just not sure what I should try next. When in Chrome I try url: localhost/phpmyadmin All I get is: This page isn’t working localhost is currently unable to handle this request. HTTP ERROR 500 When I try the same url in Firefox is just get a blank screen. The /var/log/apache2/access.log shows the following entry each time I try to connect from chrome ::1 - - [20/Feb/2025:13:09:46 -0700] "GET /phpmyadmin/ HTTP/1.1" 500 185 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36" And when I try to connect from Firefox I see: 127.0.0.1 - - [20/Feb/2025:13:11:53 -0700] "GET /phpmyadmin/ HTTP/1.1" 500 185 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0" It seems Firefox is using ipv4 and Chrome is using ipv6... I suspect this is irrelevant. I did notice that when in Chrome I try to look at my user page ~/public_html/index.php by using the url in chrome localhost/~user/ it just shows the contents of index.php which is: <?PHP phpinfo(); ?> in this case. Oddly Firefox if I use the same url it actually process the php and sends the page. Anyway the actual issue is that phpmyadmin is not opening. I thought there might be some relevance here. Not sure. I do get the full php info page when I use localhost/~user/index.php in Chrome and Firefox gives me this page just using the url localhost/~user/. The default apache page is served when I use localhost only as a url. I opened up the www port (80) and I get the same from a remote computer on my network. /var/log/apache2/error.log shows: Thu Feb 20 13:11:53.403468 2025] [php:error] [pid 9421:tid 9421] [client 127.0.0.1:43450] PHP Fatal error: Uncaught Error: Failed opening required 'Composer/CaBundle/autoload.php' (include_path='.') in /usr/share/phpmyadmin/autoload.php:4 Stack trace: #0 /usr/share/phpmyadmin/index.php(36): require() #1 {main} thrown in /usr/share/phpmyadmin/autoload.php on line 4 for each attempt to open url localhost/phpmyadmin. file /usr/share/phpmyadmin/autoload.php does exist and it has permissions: -rw-r--r-- 1 root root 78082 Feb 8 2023 autoload.php Do I have to change it to www-data group/owner? I did not see that requirement anywhere? I assume phpmyadmin and its components runs as root? IDK When setting up phpmyadmin I uncommented all of the lines: $cfg['Servers'][$i]['pmadb'] = 'phpmyadmin'; $cfg['Servers'][$i]['bookmarktable'] = 'pma__bookmark'; $cfg['Servers'][$i]['relation'] = 'pma__relation'; $cfg['Servers'][$i]['table_info'] = 'pma__table_info'; $cfg['Servers'][$i]['table_coords'] = 'pma__table_coords'; $cfg['Servers'][$i]['pdf_pages'] = 'pma__pdf_pages'; $cfg['Servers'][$i]['column_info'] = 'pma__column_info'; $cfg['Servers'][$i]['history'] = 'pma__history'; $cfg['Servers'][$i]['table_uiprefs'] = 'pma__table_uiprefs'; $cfg['Servers'][$i]['tracking'] = 'pma__tracking'; $cfg['Servers'][$i]['userconfig'] = 'pma__userconfig'; $cfg['Servers'][$i]['recent'] = 'pma__recent'; $cfg['Servers'][$i]['favorite'] = 'pma__favorite'; $cfg['Servers'][$i]['users'] = 'pma__users'; $cfg['Servers'][$i]['usergroups'] = 'pma__usergroups'; $cfg['Servers'][$i]['navigationhiding'] = 'pma__navigationhiding'; $cfg['Servers'][$i]['savedsearches'] = 'pma__savedsearches'; $cfg['Servers'][$i]['central_columns'] = 'pma__central_columns'; $cfg['Servers'][$i]['designer_settings'] = 'pma__designer_settings'; $cfg['Servers'][$i]['export_templates'] = 'pma__export_templates'; in /usr/share/phpmyadmin/config.inc.php which I copied from config.sample.inc.php which is in the same directory. I also added the line $cfd['TempDir']= '/var/lib/phpmyadmin/tmp'; at the bottom of the file I notice that there is a config.inc.php in /var/www/html/phpmyadmin as well.?? Composer is installed on the machine. If I type composer at a prompt it shows the help screen. Is composer a requirement of the phpmyadmin package? Any direction would be greatly appreciated. Thanks, Mark | Hello mark-bboy wrote: 2025-02-26 08:20 [..] It is still giving the following in /var/log/apache2/error.log each time I try to connect from Chrome with /localhost/phpmyadmin: Code: Select allWed Feb 26 01:04:30.118687 2025] [php:error] [pid 12210:tid 12210] [client ::1:44582] PHP Fatal error: Uncaught Error: Failed opening required 'Composer/CaBundle/autoload.php' (include_path='.') in /usr/share/phpmyadmin/autoload.php:4 Stack trace: #0 /usr/share/phpmyadmin/index.php(36): require() #1 {main} thrown in /usr/share/phpmyadmin/autoload.php on line 4 According to the following command: Code: Select all$ apt-file search Composer/CaBundle/autoload.php php-composer-ca-bundle: /usr/share/php/Composer/CaBundle/autoload.php the missing file named "Composer/CaBundle/autoload.php" is in the package named "php-composer-ca-bundle". Is it installed ? You can use the following commands: Code: Select allsudo apt install php-composer-ca-bundle or Code: Select allsudo apt reinstall php-composer-ca-bundle mark-bboy wrote: 2025-02-26 08:20 As I indicated above I reran the installation script (that uses dbconfig-common and it still is not working. What's the name of this script ? Hope this helps. |
Hi there, Newer on Debian, I need some help please. I'm on Gnome and the bluetooth button is disable in my preference pannel. I think I've installed all needed modules, but it seems to be too difficult to me. I think that I use the wrong firmware, but I'm not sure. Here is the return of the command "sudo service bluetooth status" : Code: Select allbluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: inactive (dead) Thanks to you & regards | Hello and welcome! It is a good habit to search the forums before posting, here have recently been lot of discussion of bluetooth problems. Debian wiki is also a good place for Debian related problems. Check this https://wiki.debian.org/BluetoothUser If you still can't get bluetooth running, report back. |
Hi, I've installed Debian a few months ago (bookworm), instead of another classical distro I've been using for years, and for the first time I need to print a pdf. I tried to ping my printer, but received this error message : Code: Select allping: sendmsg: Operation not permitted I checked for iptables, and learned it was removed and replaced by nftables, which is inactive (and empty by default). I tried to ping with my user and then as root, and got the same error message : is it normal in a fresh install to have this message ? Thank for any hint to understand what's going on | Hello, debian_new_user wrote: 2025-03-07 16:21 [..] I tried to ping my printer, but received this error message : Code: Select allping: sendmsg: Operation not permitted [..] is it normal in a fresh install to have this message ? The ping command usually works on a fresh installation. So you may have messed up something in your installation. By the way, yours does not appear to be a fresh Debian installation: debian_new_user wrote: 2025-03-07 16:21 I've installed Debian a few months ago (bookworm) It would be useful if you could provide more information about your hardware and software configuration using the following command (the inxi program must be installed): Code: Select allinxi -F -v 7 -z -s You can paste the logs into the body of a follow-up message between code tags (if they fit the size of a forum message) |
Hello everyone. I'm trying to figure out AppArmor. To study its functionality, I wrote this program Code: Select all#include <iostream> #include <fstream> #include <string> int main() { const std::string filePath = "/home/username/Documents/Projects/AppArmorTest/hello.txt"; std::ofstream outFile(filePath); if (!outFile) { std::cerr << "Error: not able to write: " << filePath << std::endl; return 1; } outFile << "Hello world" << std::endl; outFile.close(); std::cout << "Successfull: " << filePath << std::endl; return 0; } Created an AppArmor profile in /etc/apparmor.d named create_file with the following contents Code: Select all/home/username/Documents/Projects/AppArmorTest/create_file { /usr/lib/x86_64-linux-gnu/libstdc++.so.6 r, /etc/** r, /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30 mr, } As you can see, the profile contains a strange permission "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30 mr," which allows modifying the system library. With the access mode set to "r", the program does not work, and "dmesg" contains the following violation log [ 4273.647810] audit: type=1400 audit(1742153237.059:54): apparmor="DENIED" operation="file_mmap" profile="/home/username/Documents/Projects/AppArmorTest/create_file" name="/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30" pid=5455 comm="create_file" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Why does this happen? Why does such a program need such permission? How can you configure apparmor profiles if even such a primitive program has to be allowed to change system libraries? What's the point then? | Hello, guma178 wrote: 2025-03-17 04:32 [..] As you can see, the profile contains a strange permission "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30 mr," which allows modifying the system library. With the access mode set to "r", the program does not work, and "dmesg" contains the following violation log [ 4273.647810] audit: type=1400 audit(1742153237.059:54): apparmor="DENIED" operation="file_mmap" profile="/home/username/Documents/Projects/AppArmorTest/create_file" name="/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30" pid=5455 comm="create_file" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Why does this happen? Why does such a program need such permission? How can you configure apparmor profiles if even such a primitive program has to be allowed to change system libraries? What's the point then? According to the apparmor.d manual page about access modes: [..] m - Allow executable mapping This mode allows a file to be mapped into memory using mmap(2)'s PROT_EXEC flag. This flag marks the pages executable; it is used on some architectures to provide non-executable data pages, which can complicate exploit attempts. AppArmor uses this mode to limit which files a well-behaved program (or all programs on architectures that enforce non-executable memory access controls) may use as libraries, to limit the effect of invalid -L flags given to ld(1) and LD_PRELOAD, LD_LIBRARY_PATH, given to ld.so(8). [..] I'm not an apparmor expert, but program's libraries needs to be mapped (loaded) into (user space) memory in order to be used/executed by linked programs. So the "m" flag is required with apparmor according to the documentation above. Hope this helps. |
Hi, A few weeks ago I had to do a complete reinstall of Debian Bookworm from a Debian Bookworm 12.5 Live ISO/DVD. Since then the laptop has not been able to access the web through the dongle (a Vodafone R219h) although the laptop can access the web through the local library access point. It seems that the laptop is using Network Manager to manage connections.I have read/worked through the Network Manager section of Debian Networking WiFi_HowToUse section of the Debian Wiki. The laptop still cannot access the web through the dongle. In my investigations I found that both 20-wired.network and dhcp.network were both missing from /etc/systemd/network. I have re-instated both files. This has made no difference. There is a .nmconnection file for the dongle in /etc/NetworkManager/system-connections/. In System Settings/Network/Connections I have tried changing the dongle (access) Mode from Infrastructure (the original setting) to Adhoc and then Access Point. Neither of these changes made any difference. Currently I have set Restrict to device to wlp7s0. Again this made no difference. Previous to re-installing Debian, the laptop had no problem whatever in accessing the web through the dongle at home. Could someone please point me in the direction of a fix for this problem ? Stuart EDIT: Whilst reading through the Network section of the Debian Wiki, I came across the "sudo nmcli d" command. With the dongle connected to a usb port, this gives the following output. Code: Select allstuart@localhost:~$ sudo nmcli d DEVICE TYPE STATE CONNECTION enx001e101f0000 ethernet connected Wired connection 2 wlp7s0 wifi connected VodafoneMobileWiFi-645C43 lo loopback connected (externally) lo p2p-dev-wlp7s0 wifi-p2p disconnected -- enp19s0 ethernet unavailable -- In an effort to get this problem fixed, I recently replaced wlp7s0 with enp19s0 in file /etc/systemd/network/20-wired.network. This made no difference so I put back wlp7s0. Also, use of the "ip a" command gives the following output Code: Select allstuart@localhost:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: enp19s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 78:84:3c:ff:8b:84 brd ff:ff:ff:ff:ff:ff 3: wlp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 64:27:37:96:82:fb brd ff:ff:ff:ff:ff:ff inet 10.190.96.149/25 metric 1024 brd 10.190.96.255 scope global dynamic wlp7s0 valid_lft 3072sec preferred_lft 3072sec inet 10.190.96.188/25 brd 10.190.96.255 scope global secondary dynamic noprefixroute wlp7s0 valid_lft 3084sec preferred_lft 3084sec inet6 fe80::efbc:cf7f:b0f5:ef8b/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: enx001e101f0000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff inet 192.168.0.130/24 brd 192.168.0.255 scope global dynamic noprefixroute enx001e101f0000 valid_lft 83089sec preferred_lft 83089sec inet6 fe80::b01a:499:2bc4:f290/64 scope link noprefixroute valid_lft forever preferred_lft forever stuart@localhost:~$ I have also replaced wlp7s0 with enx001e101f0000 in that same file. This also made no difference. | Hello, Stuarte wrote: 2025-01-11 15:14 [..] With the dongle connected to a usb port, this gives the following output. Code: Select allstuart@localhost:~$ sudo nmcli d DEVICE TYPE STATE CONNECTION enx001e101f0000 ethernet connected Wired connection 2 wlp7s0 wifi connected VodafoneMobileWiFi-645C43 lo loopback connected (externally) lo p2p-dev-wlp7s0 wifi-p2p disconnected -- enp19s0 ethernet unavailable -- You are trying to connect your computer's WiFi network device (what is it?) to the WiFi access point whose SSID is "VodafoneMobileWiFi-645C43", aren't you? It would be better to disconnect the cable from the Ethernet port before trying to connect the computer's WiFi network card to the Vodafone R219h WiFi access point (connected to the Internet via a mobile operator). Hope this helps. -- note: please rename the subject of the first post from "Cannot Access web through Vodafone R219h wifi dongle after re-install" to "Cannot Access web through Vodafone R219h wifi access point" |
I just recently installed Debian 12. PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian I have four PC in my local network. I have successfully tested out different networking tools. For example, commands to check that the SMBD, NMBD, WSDD2, netscan, and netdiscover all work. The tools that aren't working are dig and nslookup . When I execute nslookup <mycomputer> it returns the message in the thread's subject line. During the install, I did not setup a domain. Is this the reason why? I'm not a domain expert, so I'm looking for help. Content of /etc/resolv.conf cat resolv.conf # Generated by NetworkManager search <my provider name> nameserver 75.75.75.75 nameserver 75.75.76.76 nameserver 2001:558:feed::1 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 2001:558:feed::2 I have an install of Xubuntu, dig and nslookup work. I noted that systemd.resolved is installed and running. So, I installed it for my Debian computer, but it broke the network and I had to remove it. Now I'm back to a working network. | You need to point your DNS to a nameserver that has a record for <my computer> Alternatively, put it in your hosts file. |
Okay , so I am trying to set up a debian server on a computer that has been out of use and I am trying to get internet on it. Unfortunately , the last time I was not able to get the network to connect from a router ( or whatever it is called ) , this time I am trying something new. So what I am trying to see can I pass Internet from the WiFi connection on my laptop via the ethernet cable to the system I am trying to set up the server on? My operating system on my laptop is Debian Bookworm and I am trying to set up a debian server so there is that Any help would be appreciated. I asked ChatGPT and he recommended this On Linux, you can also share your Wi-Fi internet connection over Ethernet using **Internet Connection Sharing**. Here’s how you can do it: ### Steps for Linux (using `iptables` for routing): 1. **Connect to Wi-Fi**: Make sure your Linux machine is connected to the Wi-Fi network and has an active internet connection. 2. **Connect the Ethernet Cable**: Plug one end of the Ethernet cable into your Linux machine and the other into the system you want to share the connection with. 3. **Enable IP Forwarding**: - Open a terminal and enable IP forwarding to allow the system to route traffic between the Wi-Fi and Ethernet interfaces: ```bash sudo sysctl -w net.ipv4.ip_forward=1 ``` 4. **Configure `iptables` for NAT (Network Address Translation)**: - Set up `iptables` to NAT the traffic from the Ethernet interface through the Wi-Fi interface. Replace `eth0` with your Ethernet interface name (you can check it with `ifconfig` or `ip a`), and `wlan0` with your Wi-Fi interface name. ```bash sudo iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE ``` - Allow traffic forwarding from the Ethernet interface to the Wi-Fi interface: ```bash sudo iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT sudo iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT ``` 5. **Set Up a Static IP for the Ethernet Interface**: - You can set a static IP for the Ethernet interface or configure it to use DHCP, but for simplicity, we'll set it to a static IP (e.g., `192.168.137.1`). - Open the **Network Settings** and go to the **Ethernet** configuration. - Set a **static IP** like `192.168.137.1` with the subnet mask `255.255.255.0`. 6. **Configure the Second System**: - On the other machine, configure the Ethernet adapter to obtain an IP address automatically (DHCP) or manually set a static IP (e.g., `192.168.137.2`) with the gateway set to the Linux machine's Ethernet IP (`192.168.137.1`). 7. **Persist the Changes** (Optional): - To make the routing and NAT settings persistent after reboot, you can save the `iptables` rules. ```bash sudo iptables-save > /etc/iptables/rules.v4 ``` 8. **Restart the Network** (if needed): - If everything looks good, restart the networking service or reboot the system to ensure everything is set up properly. Now, the second system connected via Ethernet should have internet access through the Linux machine's Wi-Fi connection. ### Alternative: Use `NetworkManager` GUI If you’re using a Linux distribution with **NetworkManager**, you can share the connection without using the terminal: 1. Open **Network Settings**. 2. Select your **Wi-Fi connection**. 3. Go to the **IPv4 Settings** tab. 4. Set the **Method** to **Shared to other computers**. 5. Then, configure your **Ethernet** connection with either DHCP or a static IP. This method might be easier for those who prefer not to work directly with the command line. | I don't you can generally use bridging with wifi. Many APs only allow one MAC address for the client. You probably want to use NAT instead. |
I am confused. I do have 3 systems running Debain stable and two of them have been upgraded to the most recent kernel version 6.1.0-32-amd64 about a week ago. But one of them is still hanging on to 6.1.0-31-amd64 and the upgrade option isn't even found when I try to apply all upgrades. I guess that by default systems are probably configured to pull updates at different times in order to lessen the stress on repository servers but since it has been over a week now I wonder if something is wrong on my system. Is such a long update gap normal? The system with the still older version: Code: Select all$ uname -a Linux lenovo-t400s 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux $ apt list -i linux-image-amd64 linux-headers-amd64 -a Listing... Done linux-image-amd64/stable-backports 6.12.12-1~bpo12+1 amd64 linux-image-amd64/stable-security,now 6.1.128-1 amd64 [installed] linux-image-amd64/stable-updates 6.1.124-1 amd64 linux-image-amd64/stable 6.1.94-1 amd64 And one of the systems with the already newer version: Code: Select all$ uname -a Linux fujitsu-lifebook-e781 6.1.0-32-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.129-1 (2025-03-06) x86_64 GNU/Linux $ apt list -i linux-image-amd64 linux-headers-amd64 -a Listing... Done linux-image-amd64/stable-backports 6.12.12-1~bpo12+1 amd64 linux-image-amd64/stable,now 6.1.129-1 amd64 [installed] linux-image-amd64/stable-security 6.1.128-1 amd64 linux-image-amd64/stable-updates 6.1.124-1 amd64 | Maybe your apt lists are corrupted. Try the solution here - viewtopic.php?p=819236#p819236 |
Hello All, I wanted to ask the Debian community a question about networking.service for their opinion, I recently read a article on the internet about "How to speed up boot times in Linux". It said to DISABLE networking.service through systemctl. My question is: Are there any negative side affects to doing this? Does this "break" anything? Just curious ... Thanks. | @hawghaven: did you sort it out ? |
Question about the Debian clock. I have 2 boxes running linux. 1) Linux Mint 18 a Workstation 2) Debian 12 latest update. Home entertainment. Both have the hardware clock set to UTC. My time at hone is ADT = UTC-3 or -4 depending on the season I like to watch some Germany TV so I set the clock appelett to CET, UTC +1 When I look at a TV station over the internet, the box running Mint shows TV listings that are available at the time it would be Germany UTC+1. The Box running Debian shows listings that are available at the time where the box is ADT (UTC-3) Any reason for the difference in time. How can it be corrected. Thanks | Hello, Different configurations between the two computers ? What will the following commands do on both computers ? Code: Select alldate hwclock -v |
I am new to Debian but have experience with Unix/Linux for a couple of decades. For the past almost a decade other distributions automatic disk configurations seem to no longer install swap partition. I just installed Cinnamon version of Debian from Live USB onto a USB thumb drive, the automated system installed swap partition equal to my RAM size, which is a significant fraction of the 128 GB thumbdrive.... The 'other' distributions I have experienced now use a swap to ram scheme (zram or is it zswap?) and do not configure any swap file or partition at all. On my older hardware with 8GB Ram occasionally I would notice swapping, and close a couple of windows on the desktop to stop it. Also I would use S4 hibernate to disk sometimes. My newer hardware has 32GB and 64GB of ram and I never notice swapping any more... Since portable devices can be left on the bus seat or at the coffee shop, I maximize security of data inside by encrypting drives and enabling kernel lockdown mode. These disable S4 and newest hardware uses S0ix suspend modes nowadays. How big should I make my zram space so I can remove swap partition and use space for data storage?? Debian has the capability in package repository... On systems with a couple of TB system drives and little worry about full disks anymore , whats a few tens of GB among friends?? Although swap to ram is LOTS faster than swap to disk... | Usedtoberich wrote: 2025-02-20 20:48How big should I make my zram space so I can remove swap partition and use space for data storage?? Debian has the capability in package repository... systemd-zram-generator will give you up to 4gb of compressed swap in RAM. I quit using disk-based swap on my machines last summer and so far no hiccups, no glitches, no issues at all. How much swap you need depends on your hardware and how you use your machine, but most folks shouldn't need more swap than the 4gb provided. More info here - https://wiki.debian.org/ZRam |
[SOLVED] OVERVIEW: ----------------- I have a Startech PCIe ethernet card 1-port 2.5 GBASE-T Part#: ST2GPEX, installed on my ASUS Prime X670-P wifi mobo. It works fine at 1 Gbps with the Realtek r8169 driver loaded, and no other issues with this driver. I don't use wifi nor bluetooth; those controllers on the mobo are disabled in my BIOS (ver 3208). So, I'm strictly using a wired connection to my cable router, with new CAT 8 cables installed. I'm deplouing Debian 12.9, fully up to date, with LTS kernel 6.1.0-31-amd64, as of this writing. THE ISSUE: ----------------- I wanted to find out if I could run this card (RTK 8125) at it's potential 2.5 Gbps speed on my tiny LAN, and in order to do so, I require the Realtek r8125 driver instead of the r8169 driver. I've installed the latest r8125 driver source from: git clone https://github.com/awesometic/realtek-r8125-dkms.git and compiled the source, to get the object module r8125.ko, successfully. I believe the Rtek 8125 card hax the latest firmware installed. FIRMWARE & DRIVER LOADING: ----------------------------------------------- mikey@mikey:~$ apt list -i firmware-realtek Listing... Done firmware-realtek/stable,now 20230210-5 all [installed] mikey@mikey:~$ lspci -knn | grep -i -A 3 net 09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 04) Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:0123] Kernel driver in use: r8169 Kernel modules: r8169, r8125 QUESTION: ----------------- So after rebooting, I find that the r8169 driver continues to be the active one. How do I modify my configuation to enable the kernel to boot with the r8125 driver, instead of the r8169 driver? mikey@mikey:~$ nmcli device status DEVICE TYPE STATE CONNECTION enp9s0 ethernet connected Wired connection 1 lo loopback connected (externally) lo OR --- Is this an out-of-tree issue with kernel ver 6.1.0.31-amd64 potentially being tainted by the r8125 driver? And if so, which LTS kernel do I need to install, to be able to use the r8125 driver without any danger of tainting the kernel? OR--- Has the r8169 driver superceded the r8125 driver, so far as Debian 12 (Bookworm) long term support distribution, is concerned? I have spent the last 2 days reading dozens of articles about the Realtek r8125 driver and it's associated (earlier) foibles, and I find that the issue with getting it to work on a current version of Linux, is quite confusing. And IMO, the Startech Realtek 8125 support page for Linux is out of date, so I've been relying on the git repository for more up to date information and code downloads. I'm about to go nuts, but as far as I am concerned, some of this is the hardware vendor's issue, for generally poor Linux support (and not just with this component). Thank you. | Ok, I fixed it myself. After browsing (not mandatory) a copy of MAD Magazine from 1963 (which told me to consult the README.md file that came with the package); I reviewed the README instructions and ran the following from the terminal: (Configure an entry in the blacklist file to blacklist the r8169 driver)... sudo tee -a /etc/modprobe.d/blacklist-r8169.conf > /dev/null <<EOT ... blacklist r8169 EOT ... Next, apply the new blacklist to the kernel... sudo update-initramfs -u (the above takes a few moments, depending on your hardware's age; just watch the messages on the terminal as it executes) ... Next, Reboot your machine. ... Following reboot, open the terminal and run the following command to verify that the above worked, as expected... lsmod | grep -i r8125 mikey@mikey:~$ lsmod | grep -i r8125 r8125 274432 0 End Of Post --------------------------- ***--- +=+=+=+ ---*** --------------------------- |
Hi, I had recently switched to debian and installed debian 12 with kde plasma, I had not installed with the installer but rather the kde-plasma-desktop package, the install did not give any errors but when I tried to connect to the internet it just did not want to detect any nearby networks nor connect to them, it was detecting my adapter but still not using it, nmcli device show had shown that it is unmanaged or something, I installed rfkill by manually connecting and doing some tweaks with ChatGPT, because of the AI, I was finally able to connect to my nearby networks through the applet, but I had very slow internet. The network speed is about 100-200kbps with wifi and usb tethering, I am using the appropriate mtu that was identified in windows which was 1372, I set it on the device and in the settings of the connection itself. But still I had about the same speed, When I checked my system with speedtest-cli it showed a max speed of 1Mb/s download and the same for upload, which is ridiculous! My system used to have 5MB/s of internet speed but now it is only 100-200KB/s? Also when I checked with the ping command Code: Select allping -M do -s 1344 8.8.8.8 It just showed that there is substantial packet loss, before when I used to use xfce, it used to be 0% packet loss. Also I am using the best mirror in case you are wondering, I used nala to find the mirror and set the #1 mirror. inxi -Fxxxxz output- Code: Select allak@debian:~$ inxi -Fxxxxz System: Kernel: 6.1.0-30-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop Mobo: Gigabyte model: G31M-ES2L serial: <superuser required> BIOS: Award v: FI date: 08/09/2010 CPU: Info: quad core model: Intel Core2 Quad Q9550 bits: 64 type: MCP smt: <unsupported> arch: Penryn rev: A cache: L1: 256 KiB L2: 12 MiB Speed (MHz): avg: 2833 min/max: N/A cores: 1: 2833 2: 2833 3: 2833 4: 2833 bogomips: 22664 Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 Graphics: Device-1: NVIDIA GK107 [GeForce GT 740] driver: nvidia v: 470.256.02 arch: Kepler pcie: speed: 2.5 GT/s lanes: 16 ports: active: none off: HDMI-A-1 empty: DVI-I-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0fc8 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x261mm (19.02x10.28") s-diag: 549mm (21.61") Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: LG (GoldStar) FHD serial: <filter> res: 1920x1080 hz: 100 dpi: 102 size: 480x260mm (18.9x10.24") diag: 546mm (21.5") modes: max: 1920x1080 min: 640x480 API: OpenGL v: 4.6.0 NVIDIA 470.256.02 renderer: NVIDIA GeForce GT 740/PCIe/SSE2 direct-render: Yes Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Gigabyte GA-D525TUD driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:27d8 class-ID: 0403 Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e1b class-ID: 0403 API: ALSA v: k6.1.0-30-amd64 status: kernel-api Server-1: PulseAudio v: 16.1 status: active Network: Device-1: Qualcomm Atheros AR8131 Gigabit Ethernet vendor: Gigabyte GA-G31M-ES2L driver: atl1c v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: bf00 bus-ID: 03:00.0 chip-ID: 1969:1063 class-ID: 0200 IF: enp3s0 state: down mac: <filter> Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb bus-ID: 5-5:2 chip-ID: 148f:5370 class-ID: 0000 serial: <filter> IF: wlxc83a35c9505a state: up mac: <filter> Drives: Local Storage: total: 1.38 TiB used: 20.29 GiB (1.4%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: <unknown> type: HDD rpm: 7200 serial: <filter> rev: A7C0 scheme: MBR ID-2: /dev/sdb vendor: A-Data model: SU800 size: 476.94 GiB speed: <unknown> type: SSD serial: <filter> rev: 8B scheme: MBR Partition: ID-1: / size: 173.1 GiB used: 17.27 GiB (10.0%) fs: ext4 dev: /dev/sdb1 ID-2: /home size: 14.66 GiB used: 3.02 GiB (20.6%) fs: ext4 dev: /dev/sdb6 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb3 ID-2: swap-2 type: zram size: 1.91 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 55.0 C mobo: N/A gpu: nvidia temp: 40 C Fan Speeds (RPM): N/A gpu: nvidia fan: 30% Info: Processes: 164 Uptime: 22m wakeups: 0 Memory: 3.82 GiB used: 1.94 GiB (50.7%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Packages: pm: dpkg pkgs: 1743 Shell: Bash v: 5.2.15 running-in: konsole inxi: 3.3.26 ak@debian:~$ Please give serious suggestions, I just want this installation to be fine. Thanks, GK | Have you installed the firmware for that Ralink device? It's in the firmware-misc-nonfree package. |
I have a Debian server with two Ethernet ports. Relevant part of /etc/network/interfaces: Code: Select allallow-hotplug enp2s0 iface enp2s0 inet dhcp allow-hotplug enp3s0 iface enp3s0 inet static address 192.168.1.1/24 I have a service running (specifically, Home Assistant on port 8123) that I want to reverse proxy with nginx. My nginx config: Code: Select allserver { server_name <dns name>; listen 443 ssl; listen [::]:443 ssl; ssl_certificate <path to cert> ssl_certificate_key <path to key> location / { proxy_pass http://192.168.1.1:8123/; proxy_bind 192.168.1.1; proxy_set_header X-Forwarded-For $remote_addr; } } However, nginx makes connections from enp2s0's IP address, rather than 192.168.1.1. I tried to reproduce the problem in a VM with a similar network setup, but in the VM proxy_bind works correctly. Any ideas how I can debug why nginx is ignoring proxy_bind? | Right, made some progress! I have discovered this happens due to NAT being enabled. This section is present in my server's /etc/nftables.conf: Code: Select alltable ip nat { chain prerouting { type nat hook prerouting priority 0; } chain postrouting { type nat hook postrouting priority 100; masquerade } } and if I add that to my test VM, the VM then exhibits the problem. I still don't know how to fix this yet, but at least I know it's something to do with nftables. |
Dear community, I am experiencing problems enabling UEFI secure boot on my HP Elitebook when booting the PREEMPT RT kernel using linux-image-5.10.0-33-rt-amd64 Everything works fine when I use the stock linux-image-5.10.0-33-amd64 kernel. Booting the RT kernel also seems to work initially, I get a running system. Both systems report "secureboot: Secure boot enabled" when I grep dmesg output. However, running "efibootmgr" under the RT kernel reports "EFI variables are not supported on this system." Also, calling "modprobe efivarfs" fails with the RT kernel. For reference I have added dmesg of both kernels. In line 521 of the standard kernel, "Registered efivars operations" is reported. This is missing on line 523 in the RT dmesg output. What can I do Regards Richard | Hello, lerichi wrote: 2025-01-26 23:31 [..] running "efibootmgr" under the RT kernel reports "EFI variables are not supported on this system." Also, calling "modprobe efivarfs" fails with the RT kernel Can you report the log of the command and the error message using modprobe with the RT kernel ? What is the output of the following commands ? Code: Select allscript log.txt uname -a sudo modinfo efivarfs sudo modprobe efivarfs exit If you wish, you can report the log.txt file in one of the following ways: paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message attach the logs to a follow-up forum message as a compressed zip or gz file paste the logs into the body of a follow-up message between code tags (if they fit the size of a forum message) |
Hi all! I have been a linux user for some years although I'm very new to the networking aspects. This is the first time I will use OpenVPN and I have been struggling to make it work for a few days. I need to connect my home and work PCs (just two computers, each in a different location and with a different network) to use ssh in a way that I can access either computer. Then I could syncronize my files using the commands: sync, unison, etc. Both computers are using Debian 12. In case this info could be relevant, one computer has the default Debian kernel: 6.1.0-30-amd64, arch: x86_64. The other computer is using a newer kernel to achieve wifi compatibility: Kernel: 6.10.11+bpo-amd64 arch: x86_64. I would like to set both as server and client to access them from either location. I installed the default OpenVPN in Debian 12: OpenVPN 2.6.3 x86_64-pc-linux-gnu library versions: OpenSSL 3.0.15 3 Sep 2024, LZO 2.10 Originally developed by James Yonan Copyright (C) 2002-2023 OpenVPN Inc <sales@openvpn.net> First I followed the wiki debian page: https://wiki.debian.org/OpenVPN: In that page they first cover how to install and run openvpn in a raw unsecure connection just for testing. But the test didn't go well for me. Later they continue to configure openvpn which I also did, but still it seem not to work. Then I went through more complex guides on the net, configuring certificates, etc.... no luck. I think I should focus on that first step on the debian wiki page and find out why the raw test doesn't work. So here are the steps I followed from the debian wiki: Code: Select allsudo apt-get install openvpn sudo apt-get install network-manager-openvpn-gnome On the server's firewall, open up UDP 1194 (default port). I accomplished this using firewalld (which is the recommended program to reach the nftables in Debian). Code: Select allsudo apt install firewalld sudo systemctl start firewalld sudo systemctl enable firewalld sudo firewall-cmd --add-port=1194/udp I also check that the openvpn service was active and enable: Code: Select allsudo systemctl start openvpn.service Code: Select allsudo systemctl enable openvpn.service And I included OpenVPN in the firewall too: Code: Select allsudo firewall-cmd --add-service openvpn.service Here is the output of my firewalld configuration with the command: sudo firewall-cmd --list-all Code: Select allpublic (active) target: default icmp-block-inversion: no interfaces: wlp7s0 sources: services: dhcpv6-client openvpn ssh ports: 1194/udp protocols: forward: yes masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Since I want to use both computers as servers I did all those steps in both computers. From one computer (let's call it the server now) I run an openvpn instance: Code: Select allsudo openvpn --remote CLIENT_IP --dev tun1 --ifconfig 10.*.*.1 10.*.*.2 If I understood it well, I have to replace CLIENT_IP with the public IP of the other computer (let's call it the client). I opted to get the IP using the command: Code: Select allcurl https://api.ipify.org and copy/paste the IP, replacing the CLIENT_IP part in the command above. So here is the output of: sudo openvpn --remote xxx.xxx.xxx.xxx. --dev tun1 --ifconfig 10.*.*.1 10.*.*.2. Code: Select all2025-01-23 19:42:08 DEPRECATION: No tls-client or tls-server option in configuration detected. OpenVPN 2.7 will remove the functionality to run a VPN without TLS. See the examples section in the manual page for examples of a similar quick setup with peer-fingerprint. 2025-01-23 19:42:08 OpenVPN 2.6.3 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] 2025-01-23 19:42:08 library versions: OpenSSL 3.0.15 3 Sep 2024, LZO 2.10 2025-01-23 19:42:08 DCO version: N/A 2025-01-23 19:42:08 ******* WARNING *******: '--cipher none' was specified. This means NO encryption will be performed and tunnelled data WILL be transmitted in clear text over the network! PLEASE DO RECONSIDER THIS SETTING! 2025-01-23 19:42:08 ******* WARNING *******: '--auth none' was specified. This means no authentication will be performed on received packets, meaning you CANNOT trust that the data received by the remote side have NOT been manipulated. PLEASE DO RECONSIDER THIS SETTING! 2025-01-23 19:42:08 ******* WARNING *******: All encryption and authentication features disabled -- All data will be tunnelled as clear text and will not be protected against man-in-the-middle changes. PLEASE DO RECONSIDER THIS CONFIGURATION! 2025-01-23 19:42:08 TUN/TAP device tun1 opened 2025-01-23 19:42:08 net_iface_mtu_set: mtu 1500 for tun1 2025-01-23 19:42:08 net_iface_up: set tun1 up 2025-01-23 19:42:08 net_addr_ptp_v4_add: 10.*.*.1 peer 10.*.*.2 dev tun1 2025-01-23 19:42:08 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xxx:1194 2025-01-23 19:42:08 UDPv4 link local (bound): [AF_INET][undef]:1194 2025-01-23 19:42:08 UDPv4 link remote: [AF_INET]xxx.xxx.xxx.xxx:1194 So I got this good line saying: TUN/TAP device tun1 opened While openvpn is running, I execute from another terminal the command "ip a" and get this output: Code: Select alltun1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500 link/none inet 10.*.*.1 peer 10.*.*.2/32 scope global tun1 valid_lft forever preferred_lft forever I then continue with the debian wiki page, go to the client and run: Code: Select allsudo openvpn --remote SERVER_IP --dev tun1 --ifconfig 10.*.*.2 10.*.*.1 replacing now the SERVER_IP too with the public IP of the "server" computer. I get a very similar output as before, just exchanging the 10.*.*.1 and 10.*.*.2. I am also supposed to be able to ping the server: ping 10.*.*.1, but it doesn't work: PING 10.*.*.1 (10.*.*.1) 56(84) bytes of data. --- 10.*.*.1 ping statistics --- 11 packets transmitted, 0 received, 100% packet loss, time 10312ms So please, could anyone help me about how and where could I start searching for the issue in my openvpn or my computers? What commands could I run for debugging? Could it be something with my router instead? In that case, how can I configure my router to let openvpn connections? | Hello, anndreih wrote: 2025-01-23 20:08 [..] I need to connect my home and work PCs (just two computers, each in a different location and with a different network) to use ssh in a way that I can access either computer. Then I could syncronize my files using the commands: sync, unison, etc. Both computers are using Debian 12. [..] Just a guess: both computers are behind a modem/router (with an active NAT, Network address translation) and cannot reach each other, aren't they ? What are the IP address and default gateway of these two computers without trying to enable VPN? You can check this on each computer using the following commands: Code: Select allip address ip route |
Hello all, I recently reinstalled Debian 12, after switching from Gnome to KDE. Since the reinstall, I started having issues with the iwlwifi firmware. On boot, I would receive the "failed to load iwl-debug yoyo.bin" error. I fixed this by editing the modprobe iwlwifi.conf file. This fixed it for a bit before I started receiving the error "iwlwifi sorry - debug buffer is only 4096k while you requested 65536k." The weird thing is that sometimes it prevents the OS from fully booting while other times it goes straight through into the login screen, where I can log in and the wifi still works. I can also boot into recovery mode just fine, and the wifi works as expected. I haven't been able to find instances of this message anywhere else online, so I apologize if this is a repeat of old information. This is also my first post, so I hope I am doing everything the correct way! My hardware is as follows: Debian 12 KDE (wayland) 6.1.0-28 kernel Ryzen 5 2600x Nvidia Titan Xp 32gb ram Asrock b450m motherboard (no built-in wifi) Intel Ax200 pcie wifi card. Any information would be greatly appreciated. Thanks! | Hello, theinmine wrote: 2025-01-04 03:22 [..] On boot, I would receive the "failed to load iwl-debug yoyo.bin" error. I fixed this by editing the modprobe iwlwifi.conf file. This fixed it for a bit before I started receiving the error "iwlwifi sorry - debug buffer is only 4096k while you requested 65536k." The weird thing is that sometimes it prevents the OS from fully booting while other times it goes straight through into the login screen[..] What is the content of the "fixed" iwlwifi.conf file ? |
Hello, I have a debian 12 installed initially with DHCP and wifi. After sometime I changed to static IP the wifi config using the GUI in settings > wifi > select the SSID used > edit > IPv4 > from Automatic to Manual and set all configs.. everything works ok. Now I would like to configure the static IP with /etc/network/interfaces.. and that for what I see, the file wasn't changed by the GUI setting (the ip command shows me an 'wlo1' interface with the static IP but it doesn't appear in /etc/network/interfaces) my current /etc/network/interfaces has this: Code: Select all#/etc/network/interfaces source /etc/network/interfaces.d/* auto lo iface lo inet loopback The /etc/network/interfaces.d folder is empty. I noticed that debian is running a wpa_supplicant systemd service, but I can't see which wpa_supplicant.conf file is using (to set it on /etc/network/interfaces) and there is no /etc/wpa_supplicant/wpa_supplicant.conf file in my filesystem the systemd wpa_supplicant service file is: Code: Select all#/lib/systemd/system/wpa_supplicant.service [Unit] Description=WPA supplicant Before=network.target After=dbus.service Wants=network.target IgnoreOnIsolate=true [Service] Type=dbus BusName=fi.w1.wpa_supplicant1 ExecStart=/sbin/wpa_supplicant -u -s -O "DIR=/run/wpa_supplicant GROUP=netdev" ExecReload=/bin/kill -HUP $MAINPID Group=netdev RuntimeDirectory=wpa_supplicant RuntimeDirectoryMode=0750 [Install] WantedBy=multi-user.target Alias=dbus-fi.w1.wpa_supplicant1.service The only wpa_supplicant.conf I found in my filesystem is /etc/dbus-1/system.d/wpa_supplicant.conf and it doesn't have any SSID set.. don't know much about dbus :/ Code: Select all#/etc/dbus-1/system.d/wpa_supplicant.conf <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <policy user="root"> <allow own="fi.w1.wpa_supplicant1"/> <allow send_destination="fi.w1.wpa_supplicant1"/> <allow send_interface="fi.w1.wpa_supplicant1"/> <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/> </policy> <policy group="netdev"> <allow send_destination="fi.w1.wpa_supplicant1"/> <allow send_interface="fi.w1.wpa_supplicant1"/> <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/> </policy> <policy context="default"> <deny own="fi.w1.wpa_supplicant1"/> <deny send_destination="fi.w1.wpa_supplicant1"/> <deny receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/> </policy> </busconfig> I have tried adding this in /etc/network/interfaces Code: Select allauto wlo1 iface wlo1 inet static address x.x.x.x netmask x.x.x.x gateway x.x.x.x dns-nameservers x.x.x.x x.x.x.x wpa-ssid xxxxx wpa-psk xxxxx but it breaks the internet connection. Please help | Hopefully this isn't too off-topic but is there a reason you wouldn't set your static IP on your router instead of on the workstation? Personal preference but I'd rather have only one device on my network managing IP addressing - three machines and my printer are assigned static IPs using MAC reservations on my router. |
I installed Debian 12 32 bit on my laptop Hp Compac nw8042' which has intel Pro/Wireless 2200BG (Calexico2) network connection wireless card, properly yesterday, without getting an error. It looks excellent. The only problem my wireless broadcasting is not listed; although another wireless which I don`t know whose it is is listed. I am writing connecting via by ethernet cable. I added an wireless account using the information derived from a windows system but it didn`t run. I am new on linux. I want to learn linux and use it by debian. I need your help. | Hello, Is the firmware-ipw2x00 package installed ? You can verify with the command: Code: Select allapt list firmware-ipw2x00 Is the rfkill switch unlocked ? You can verify with the command: Code: Select allsudo apt install rfkill sudo rfkill Are there any errors and warning in the system journal ? You can verify with the command: Code: Select allsudo journalctl -b --no-pager -p err..warning What program is used to configure the network ? is the network manager running ? Code: Select allps ax | grep -i network If you wish, you can report logs in one of the following ways: paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message attach the logs to a follow-up forum message as a compressed zip or gz file paste the logs into the body of a follow-up message between code tags (if they fit the size of a forum message) Hope this helps. |
Hello, Im running into a WiFi problem when installing the latest backport-kernel for debian 12 bookorm. My WiFi works very well on debian 12 stable (bookworm, kernel 6.1) but as soon as I upgrade and boot into the kernel latest backpackages kernel (6.11.10), my WiFi becomes unavailable. When I boot into the kernel that was installed using backports (6.11.10), dmesg shows me these errors regarding iwlwifi: Code: Select all[ 6.050298] Intel(R) Wireless WiFi driver for Linux [ 6.050960] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002) [ 6.051097] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) [ 6.053740] usbcore: registered new interface driver uvcvideo [ 6.053663] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 6.057063] audit: type=1400 audit(1736236291.341:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=588 comm="apparmor_parser" [ 6.058913] audit: type=1400 audit(1736236291.341:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=586 comm="apparmor_parser" [ 6.058920] audit: type=1400 audit(1736236291.341:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=586 comm="apparmor_parser" [ 6.058923] audit: type=1400 audit(1736236291.341:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=586 comm="apparmor_parser" [ 6.058926] audit: type=1400 audit(1736236291.341:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=582 comm="apparmor_parser" [ 6.059260] audit: type=1400 audit(1736236291.341:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=583 comm="apparmor_parser" [ 6.059264] audit: type=1400 audit(1736236291.341:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=583 comm="apparmor_parser" [ 6.059560] audit: type=1400 audit(1736236291.341:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oosplash" pid=587 comm="apparmor_parser" [ 6.061461] audit: type=1400 audit(1736236291.345:12): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=592 comm="apparmor_parser" [ 6.063064] audit: type=1400 audit(1736236291.345:13): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=595 comm="apparmor_parser" [ 6.063586] intel_rapl_common: Found RAPL domain package [ 6.063589] intel_rapl_common: Found RAPL domain dram [ 6.078923] iwlwifi 0000:00:14.3: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x80000000 [ 6.078942] iwlwifi 0000:00:14.3: PCI dev 02f0/4070, rev=0x351, rfid=0x10a100 [ 6.078948] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz [ 6.080593] iwlwifi 0000:00:14.3: firmware: failed to load iwlwifi-QuZ-a0-hr-b0-77.ucode (-2) [ 6.080614] iwlwifi 0000:00:14.3: firmware: failed to load iwlwifi-QuZ-a0-hr-b0-77.ucode (-2) [ 6.080617] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-77.ucode failed with error -2 [ 6.080623] iwlwifi 0000:00:14.3: no suitable firmware found! [ 6.080652] iwlwifi 0000:00:14.3: iwlwifi-QuZ-a0-hr-b0-77 is required [ 6.080676] iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git I have already tried to uninstall my WiFi-Firmware using Code: Select all apt remove firmware-iwlwifi and afterwards Code: Select all apt install -t bookworm-backports firmware-iwlwifi I would like to understand why this issue occurs, because my WiFi was already working ootb on the stable kernel (6.1), and what I could do in order to fix this problem. Ive already encountered this issue on two separate machines running debian 12 bookworm. Output of lspci -vnn Code: Select all00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH-LP CNVi WiFi [8086:02f0] DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz [8086:4070] Flags: fast devsel, IRQ 16, IOMMU group 6 Memory at cc33c000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable- Count=16 Masked- Capabilities: [100] Latency Tolerance Reporting Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?> Kernel modules: iwlwifi Edit: I just found that kernel 6.1 tries to load wifi firmware iwlwifi-QuZ-a0-hr-b0-72.ucode while backport kernel 6.11.10 tries to load iwlwifi-QuZ-a0-hr-b0-77.ucode Maybe the debian repos are missing new microcode for this hardware? | debianuserman wrote: 2025-01-07 10:03Maybe the debian repos are missing new microcode for this hardware? I think that's possible. firmware-iwlwifi has no dependencies so it might be helpful to install Trixie's package, which is newer than the package in backports. You can find it here and this package has iwlwifi-QuZ-a0-hr-b0-77.ucode - https://packages.debian.org/trixie/all/ ... i/download And then - as rootCode: Select allcd /path/to/downloaded/firmware apt install ./firmware-iwlwifi_20241210-1_all.debHope this helps - |
I installed Debian 12.8 without a DE today on a Intel 10th gen PC. I ended up with the 6.1.29 kernel. I was working with it via ssh and every time I rebooted nothing happened. I hit the reset button to recover. I also tested shutdown, same issue. I finally re-hooked up a monitor to the PC and saw that a kernel panic happened. I've never seen this behavior. I remembered that on a very new N100 PC I had to install the bookworm backport kernel and firmware just to have wifi and bluetooth work. In this case I didn't need either of those two so I went with the standard stuff. So when I installed: Code: Select allsudo apt install -t bookworm-backports linux-image-amd64 sudo apt install -t bookworm-backports firmware-realtek reboot and shutdown work. Is this expected on an Intel 10th Gen PC with a Realtek NIC? Code: Select all$ inxi -Fxxx System: Host: mythtv Kernel: 6.11.10+bpo-amd64 arch: x86_64 bits: 64 compiler: N/A Console: pty pts/0 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> Mobo: ASUSTeK model: PRIME B460M-A v: Rev 1.xx serial: <superuser required> UEFI: American Megatrends v: 1620 date: 07/09/2021 CPU: Info: quad core model: Intel Core i3-10100 bits: 64 type: MT MCP smt: enabled arch: Comet Lake rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 800 min/max: 800/4300 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 57600 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel arch: Gen-9.5 ports: active: HDMI-A-2 empty: DP-1,HDMI-A-1,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:9bc8 class-ID: 0300 Device-2: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb vendor: Hauppauge works WinTV-quadHD driver: cx23885 v: 0.0.4 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 14f1:8880 class-ID: 0400 Device-3: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb vendor: Hauppauge works driver: cx23885 v: 0.0.4 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 14f1:8880 class-ID: 0400 Display: server: Xwayland v: 22.1.9 driver: gpu: i915 note: X driver n/a tty: 175x55 Monitor-1: HDMI-A-2 model: Sony TV 30 serial: 16843009 res: 3840x2160 dpi: 68 size: 1439x809mm (56.65x31.85") diag: 1651mm (65") modes: max: 3840x2160 min: 640x480 API: OpenGL Message: GL data unavailable in console. Try -G --display Audio: Device-1: Intel Comet Lake PCH-V cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a3f0 class-ID: 0403 Device-2: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb vendor: Hauppauge works WinTV-quadHD driver: cx23885 v: 0.0.4 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 14f1:8880 class-ID: 0400 Device-3: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb vendor: Hauppauge works driver: cx23885 v: 0.0.4 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 14f1:8880 class-ID: 0400 API: ALSA v: k6.11.10+bpo-amd64 status: kernel-api Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 7c:10:c9:41:d5:c1 Device-2: Intel 82572EI Gigabit Ethernet driver: e1000e v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 08:00.0 chip-ID: 8086:10b9 class-ID: 0200 IF: enp8s0 state: down mac: 00:1b:21:1e:54:05 Drives: Local Storage: total: 9.55 TiB used: 153.69 GiB (1.6%) ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G2B0C-00PXH0 size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: 21375D802051 rev: 233010WD temp: 30.9 C scheme: GPT ID-2: /dev/sda vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB speed: 6.0 Gb/s type: HDD rpm: 5980 serial: ZDHASSXD rev: SC60 ID-3: /dev/sdb vendor: Seagate model: ST4000VN008-2DR166 size: 3.64 TiB speed: 6.0 Gb/s type: HDD rpm: 5980 serial: ZDHASSZH rev: SC60 ID-4: /dev/sdc type: USB vendor: Toshiba model: HDWD120 size: 1.82 TiB type: HDD rpm: 7200 serial: 58NYHGNCS scheme: GPT Partition: ID-1: / size: 465.29 GiB used: 5.12 GiB (1.1%) fs: btrfs dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 475.1 MiB used: 5.8 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 465.29 GiB used: 5.12 GiB (1.1%) fs: btrfs dev: /dev/nvme0n1p2 ID-4: /var/log size: 465.29 GiB used: 5.12 GiB (1.1%) fs: btrfs dev: /dev/nvme0n1p2 ID-5: /var/tmp size: 465.29 GiB used: 5.12 GiB (1.1%) fs: btrfs dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: zram size: 3.87 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0 Sensors: System Temperatures: cpu: 29.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 213 Uptime: 3m wakeups: 0 Memory: 15.47 GiB used: 878 MiB (5.5%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Packages: pm: dpkg pkgs: 1566 Shell: Bash v: 5.2.15 running-in: pty pts/0 (SSH) inxi: 3.3.26 | Hello, jfabernathy wrote: 2025-01-11 21:34 I installed Debian 12.8 without a DE today on a Intel 10th gen PC. I ended up with the 6.1.29 kernel. I was working with it via ssh and every time I rebooted nothing happened. I hit the reset button to recover. I also tested shutdown, same issue. I finally re-hooked up a monitor to the PC and saw that a kernel panic happened. I've never seen this behavior. I remembered that on a very new N100 PC I had to install the bookworm backport kernel and firmware just to have wifi and bluetooth work. In this case I didn't need either of those two so I went with the standard stuff. So when I installed: Code: Select allsudo apt install -t bookworm-backports linux-image-amd64 sudo apt install -t bookworm-backports firmware-realtek reboot and shutdown work. Is this expected on an Intel 10th Gen PC with a Realtek NIC? Code: Select all$ inxi -Fxxx System: Host: mythtv Kernel: 6.11.10+bpo-amd64 arch: x86_64 bits: 64 compiler: N/A Console: pty pts/0 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> Mobo: ASUSTeK model: PRIME B460M-A v: Rev 1.xx serial: <superuser required> UEFI: American Megatrends v: 1620 date: 07/09/2021 The shutdown sequence sometimes fails to complete due to hardware (CPU and/or motherboard chipset and/or peripherals) or firmware incompatibilities (e.g. ACPI, peripherals firmware), especially with newer hardware. If I read correctly, your ASUSTeK PRIME B460M-A user manual [1] is dated "May 2020" and the Linux kernel 6.1.0 has been released: Code: Select all$ git log --tags --simplify-by-decoration --pretty="format:%ci %d" | grep 6\.1\.1 [..] 2022-12-21 17:48:12 +0100 (tag: v6.1.1) So newer kernels may fix the problem by adding support for newer hardware. It might be interesting to have a screen copy of the kernel dump back-trace for future reference. If you agree, please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message and adding the hardware involved, e.g.: Debian 12.8: kernel panic with reboot or shutdown with ASUSTeK PRIME B460M-A Thanks. Happy Debian ! :) -- [1] PRIME B460M-A - User Manual -- note: moved to "Hardware" sub-forum. |
The message in journal is this: Code: Select allfile system check on root device was skipped because of an unmet condition check What is the cause of this message and is it something to aware of? | We need to know the condition that was unmet. What is the full line? What is the output of the following? Code: Select all$ systemctl status systemd-fsck-root.service On my system I have this in journalctrl: Code: Select allJan 04 06:06:15 lenovo-debian-xfce systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root). And this from systemctl status systemd-fsck-root.service Code: Select all○ systemd-fsck-root.service - File System Check on Root Device Loaded: loaded (/lib/systemd/system/systemd-fsck-root.service; enabled-runtime; preset: enabled) Active: inactive (dead) Condition: start condition failed at Sat 2025-01-04 06:06:15 GMT; 1h 32min ago └─ ConditionPathExists=!/run/initramfs/fsck-root was not met Docs: man:systemd-fsck-root.service(8) This could be the e2scrub_reap.service trying to check a LVM that doesn't exist. https://ubuntuforums.org/showthread.php ... 925&page=2 Your condition may be different. Another reason for the message seems to be having the btrfs file system where fsck does not work, in which case the condition would be Code: Select allsystemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/). https://forum.manjaro.org/t/file-system ... ite/142688 So we need to know the unmet condition. |
I installed phpmyadmin for my local host on my Debin 12. Whenever I enter the phpmyadmin via by user name as `root` and its password I assigned' two lines in red are listed at the bottom the page mysqli::real_connect(): (HY000/1045): Access denied for user 'phpmyadmin'@'localhost' (using password: YES) The connection failed for the audit user defined in your configuration file. What should I do to fix this error? | Hello, fazli wrote: 2025-01-11 15:57 I installed phpmyadmin for my local host on my Debin 12. Whenever I enter the phpmyadmin via by user name as `root` and its password I assigned' two lines in red are listed at the bottom the page mysqli::real_connect(): (HY000/1045): Access denied for user 'phpmyadmin'@'localhost' (using password: YES) The connection failed for the audit user defined in your configuration file. What should I do to fix this error? A quick internet search led me here (first result): How to solve “Access denied for user 'phpmyadmin'@'localhost' (using password: YES)" Have you found it yet? |
Hello, on Debian 12, the "sudo apt upgrade" shows: Code: Select allThe following packages were automatically installed and are no longer required: linux-headers-6.1.0-28-amd64 linux-headers-6.1.0-28-common linux-image-6.1.0-28-amd64 yet during boot, my latest available kernel boot entry is older one: *27: 6.1.0-27-amd64 and the latest kernel which apt automatically installed is *29 yet it is not in a boot menu which appears during reboot. $ sudo apt reinstall linux-image-6.1.0-29-amd64 Code: Select allReading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.1.0-28-amd64 linux-headers-6.1.0-28-common linux-image-6.1.0-28-amd64 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 69.0 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://deb.debian.org/debian bookworm/main amd64 linux-image-6.1.0-29-amd64 amd64 6.1.123-1 [69.0 MB] Fetched 69.0 MB in 6s (10.8 MB/s) (Reading database ... 311759 files and directories currently installed.) Preparing to unpack .../linux-image-6.1.0-29-amd64_6.1.123-1_amd64.deb ... Unpacking linux-image-6.1.0-29-amd64 (6.1.123-1) over (6.1.123-1) ... Setting up linux-image-6.1.0-29-amd64 (6.1.123-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-29-amd64. dkms: autoinstall for kernel: 6.1.0-29-amd64. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.1.0-29-amd64 /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found background image: .background_cache.png Found linux image: /boot/vmlinuz-6.1.0-29-amd64 Found initrd image: /boot/initrd.img-6.1.0-29-amd64 Found linux image: /boot/vmlinuz-6.1.0-28-amd64 Found initrd image: /boot/initrd.img-6.1.0-28-amd64 Found linux image: /boot/vmlinuz-6.1.0-27-amd64 Found initrd image: /boot/initrd.img-6.1.0-27-amd64 Found linux image: /boot/vmlinuz-6.1.0-29-amd64 Found initrd image: /boot/initrd.img-6.1.0-29-amd64 Found linux image: /boot/vmlinuz-6.1.0-28-amd64 Found initrd image: /boot/initrd.img-6.1.0-28-amd64 Found linux image: /boot/vmlinuz-6.1.0-27-amd64 Found initrd image: /boot/initrd.img-6.1.0-27-amd64 Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done $ grep linux /boot/grub/grub.cfg Code: Select all### BEGIN /etc/grub.d/10_linux_proxy ### set linux_gfx_mode= export linux_gfx_mode ### END /etc/grub.d/10_linux_proxy ### menuentry "Debian GNU/Linux, with Linux 6.1.0-27-amd64" --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-27-amd64-advanced-stringhere' { echo 'Loading Linux 6.1.0-27-amd64 ...' linux /vmlinuz-6.1.0-27-amd64 root=/dev/mapper/abc--vg-root ro quiet ### BEGIN /etc/grub.d/41_linux_proxy ### menuentry "Debian GNU/Linux, with Linux 6.1.0-27-amd64 (recovery mode)" --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-27-amd64-recovery-stringhere' { echo 'Loading Linux 6.1.0-27-amd64 ...' linux /vmlinuz-6.1.0-27-amd64 root=/dev/mapper/abc--vg-root ro single quiet ### END /etc/grub.d/41_linux_proxy ### menuentry "Debian GNU/Linux, with Linux 5.10.0-20-amd64" --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-20-amd64-advanced-stringhere' { echo 'Loading Linux 5.10.0-20-amd64 ...' linux /vmlinuz-5.10.0-20-amd64 root=/dev/mapper/abc--vg-root ro quiet ### BEGIN /etc/grub.d/44_linux_xen ### ### END /etc/grub.d/44_linux_xen ### *29 is not there... $ grep / /etc/fstab Code: Select all/dev/mapper/abc--vg-root / ext4 noatime,errors=remount-ro,nofail 0 1 UUID=differentFromGrub.cfgOutput /boot ext2 defaults 0 2 UUID=xy-xy /boot/efi vfat umask=0022 How I could cause this? I only remember that in the past (~2 months ago?) I did: sudo apt reinstall linux-image-5.10.0-29-amd64 # one version older kernel than current Bullseye oldstable sudo update-initramfs -uk all ; sudo update-grub What to try please? | You can see what is going by grub-mkconfig command without arguments: sudo grub-mkconfig | less It does not write configuration to any disk file, it writes only to stdout. |
I'm running Debian 12.1 using Vagrant on HyperV and connecting to a network using a virtual switch. If I try to access resources on the public internet it works fine, but it fails to resolve resources on my local domain. The DHCP lease seems correct from `/var/lib/dhcp/dhclient.eth0.leases` Code: Select alldefault-duid "\000\001\000\001,\240\017\004\000\025]\012\016\307"; lease { interface "eth0"; fixed-address 172.23.230.141; option subnet-mask 255.255.240.0; option dhcp-lease-time 86400; option routers 172.23.224.1; option dhcp-message-type 5; option domain-name-servers 172.23.224.1; option dhcp-server-identifier 172.23.224.1; option dhcp-renewal-time 43200; option dhcp-rebinding-time 64800; option domain-name "mshome.net"; option netbios-node-type 4; renew 4 2025/01/09 23:34:54; rebind 4 2025/01/09 23:34:54; expire 4 2025/01/09 23:34:54; } lease { interface "eth0"; fixed-address 172.23.230.141; option subnet-mask 255.255.240.0; option dhcp-lease-time 86400; option routers 172.23.224.1; option dhcp-message-type 5; option domain-name-servers 172.23.224.1; option dhcp-server-identifier 172.23.224.1; option dhcp-renewal-time 43200; option dhcp-rebinding-time 64800; option domain-name "mshome.net"; option netbios-node-type 4; renew 5 2025/01/10 09:06:34; rebind 5 2025/01/10 17:34:57; expire 5 2025/01/10 23:34:57; } 172.23.224.1 is the address for the virtual switch and also the DHCP/DNS server If I manually specify a DNS server; then name resolution succeeds Code: Select allnslookup my.domain.local 172.23.224.1 But it fails if I don't. Resolvconf is running Code: Select all● resolvconf.service - Nameserver information manager Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; preset: enabled) Active: active (exited) since Fri 2025-01-10 00:47:55 UTC; 8min ago Docs: man:resolvconf(8) Process: 2569 ExecStart=/sbin/resolvconf --enable-updates (code=exited, status=0/SUCCESS) Main PID: 2569 (code=exited, status=0/SUCCESS) CPU: 1ms Jan 10 00:47:55 debian systemd[1]: Started resolvconf.service - Nameserver information manager. And the contents of `/etc/resolv.conf` is Code: Select all# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "resolvectl status" to see details about the actual nameservers. nameserver 4.2.2.1 nameserver 4.2.2.2 nameserver 208.67.220.220 search mshome.net I'm pretty sure that I've got an issue with how resolv is configured but don't know how to proceed from here Any help is appreciated. | Hello, What is exactly your Debian 12 version ? You can check with the following command: Code: Select allcat /etc/debian_version Chronocide0 wrote: 2025-01-10 01:02 I'm running Debian 12 using Vagrant on HyperV and connecting to a network using a virtual switch. If I try to access resources on the public internet it works fine, but it fails to resolve resources on my local domain. [..] 172.23.224.1 is the address for the virtual switch and also the DHCP/DNS server According to your quote above, I assume that 172.23.224.1 is the address of the DNS server/service for the local domain, and that the local domain is "mshome.net": can you please confirm this ? You need to assess the issue. You can check responses from the local DNS service and from local name resolver services with the following commands (replace <canonical name> with the canonical name of the hostname in the local domain computer that you want to resolve, for example, mycomputer.mshome.net where mycomputer is an existing host name): Code: Select allsudo apt install bind9-dnsutils cat /etc/hosts cat /etc/nsswitch.conf dig dig <canonical name> dig @172.23.224.1 <canonical name> getent ahostsv4 getent ahostsv4 <canonical name> dig @8.8.8.8 www.google.com getent ahostsv4 www.google.com Hope this helps. -- note: please update the subject of the first post from "Trouble configuring DNS" to "Trouble configuring DNS with Debian 12 for host names in local domain" |
I run Debian 12 KDE and I check for updates basically every day. A couple of days ago, I saw kernel 6.1.0.29 was available, so I installed it. All fine. Then this morning, I saw 6.1.0.30 was available, so I installed it too. Again, all seems to be fine. However, this rapid succession made me think there must've been some issue with 6.1.0.29. But then again, I'd expect Debian maintainers to have plenty of advance knowledge of such issues (this isn't Fedora ). I tried to find more info, bug trackers, change logs, but I became overwhelmed. I tried to search https://tracker.debian.org/pkg/linux but I seem to lack the experience to properly navigate it. Can anyone shed light on this particular issue, regarding this rapid update? Moreover, if you have any suggestions on how I can search debian.org for e.g. a particular kernel's changelog, or filter bugs by kernel, that would be appreciated. | https://bugs.debian.org/cgi-bin/bugrepo ... ug=1092772 |
Debian 12 Bookworm. I have been following https://kernel-team.pages.debian.net/ke ... n-official but I have run into a snag. When I run "apt-get source linux" W: Download is performed unsandboxed as root as file 'linux_6.1.76-1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) -rw-r--r-- 1 root root 290924 Jan 31 22:24 linux_6.1.76-1.dsc The only reason I am doing this is to use the ACS Override patch for VFIO passthrough. If there is an official Debian kernel I can install with it already patched that would be even better. Edit: Ok so apparently the issue is it doesn't like it when I do this as root. If I do it as a normal user there is no problem. | Hello, MrT wrote: 2024-04-08 08:28 Edit: Ok so apparently the issue is it doesn't like it when I do this as root. If I do it as a normal user there is no problem. I'm glad you sorted it out. :) Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message (after other tags, if any). It is also an opportunity to the make the subject more understandable to other forum users and readers, if necessary; i.e. : [Solved] Download is performed unsandboxed as root - pkgAcquire::Run (13: Permission denied) Happy Debian ! |
Hello there, I think, due to the updates today, QEMU/KVM network is not starting Result of sudo systemctl status libvirtd: Code: Select allerro:Falha ao iniciar a rede default erro:erro interno: Processo filho (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) inesperado status de saída 2: dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use Result of sudo systemctl status libvirtd Code: Select alljan 11 21:36:57 revolutions systemd[1]: Starting libvirtd.service - Virtualization daemon... jan 11 21:36:57 revolutions systemd[1]: Started libvirtd.service - Virtualization daemon. jan 11 21:37:26 revolutions dnsmasq[6241]: failed to create listening socket for 192.168.122.1: Address already in use jan 11 21:37:26 revolutions dnsmasq[6241]: FAILED to start up jan 11 21:37:26 revolutions libvirtd[2706]: libvirt version: 9.0.0, package: 9.0.0-4+deb12u2 (Debian) jan 11 21:37:26 revolutions libvirtd[2706]: hostname: revolutions jan 11 21:37:26 revolutions libvirtd[2706]: erro interno: Processo filho (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/l> dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use Topic created today here at the forum entitled "Updated Debian 12: 12.9 released", mention updates at QEMU e DNSMASQ Code: Select all qemu [54] | New upstream bugfix release [CVE-2024- | | | 7409]; mark internal codegen helper | | | symbols as hidden, fixing build failure | | dnsmasq [13] | Fix denial of service issues [CVE-2023- | | | 50387 CVE-2023-50868]; set default | | | maximum EDNS.0 UDP packet size to 1232 | | | [CVE-2023-28450] | | | | Anyone is facing the same issues post today's update? EDIT: Indeed was today's update, using Timeshift, i restored yesterday's image and everything went fine starting QEMU/KVM network. Anyone knows how to fix it? | Fontenele wrote: 2025-01-12 00:47 dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use Who's that? maybe something like Code: Select allss -p -o | grep 192.168 or Code: Select alljournalctl -b 0 -g 192.168 --no-pager Rebooted? |
Hello, I have upgraded to Debian 12.9 with kernel 6.1.0-29-amd64, but I am experiencing a problem. Every time I try to restart or power off the computer, I encounter a kernel panic. I did not have this issue before the upgrade. It seems to be related to the zram service, which I am also using. When I try to restart the zram service, I also get a kernel panic. I'm using a MAG B650 TOMAHAWK WIFI (MS-7D75) with 64 GB ram. Does anyone have any idea how to fix this? Edit: I have now successfully installed kernel 6.1.0-30 and the zram service works correctly now. Thanks all | Hello, Ophenix wrote: 2025-01-13 13:06 Hello, I have upgraded to Debian 12.9 with kernel 6.1.0-29-amd64, but I am experiencing a problem. Every time I try to restart or power off the computer, I encounter a kernel panic. I did not have this issue before the upgrade. It seems to be related to the zram service, which I am also using. When I try to restart the zram service, I also get a kernel panic. I'm using a MAG B650 TOMAHAWK WIFI (MS-7D75) with 64 GB ram. Does anyone have any idea how to fix this? It should be this: zram: Regression in at least linux-6.1.y tree * zram: Regression in at least linux-6.1.y tree @ 2025-01-07 20:48 Kenneth Van Alstyne 2025-01-08 3:54 ` Sergey Senozhatsky 0 siblings, 1 reply; 3+ messages in thread From: Kenneth Van Alstyne @ 2025-01-07 20:48 UTC (permalink / raw) To: stable; +Cc: regressions, senozhatsky, minchan, ngupta Greetings and apologies if this isn't the proper process for reporting an issue in a LTS kernel per https://www.kernel.org/doc/html/latest/ ... ssues.html. Happy to follow another process if more appropriate. Kernel 6.1.122 introduced a regression via commit ac3b5366b9b7c9d97b606532ceab43d2329a22f3 (backport of upstream commit 74363ec674cb172d8856de25776c8f3103f05e2f) in drivers/block/zram/zram_drv.c where attempting to set the size of /dev/zram0 after loading the zram kernel module results in a kernel NULL pointer dereference. That patch removed the following block from zram_reset_device(): Code: Select all - if (!init_done(zram)) { - up_write(&zram->init_lock); - return; - } However,without that, zram_reset_device subsequently calls zcomp_destroy on a device that has not been initialized, leading to the OOPS. Adding that block back does resolve the issue. In addition, the latest mainline kernel does not appear to exhibit these symptoms, but zram_drv.c seems to have been changed fairly substantially since kernel 6.1. Steps to reproduce: Code: Select allmodprobe zram zramctl /dev/zram0 --algorithm zstd --size 83886080k This is the patch to fix it: zram: check comp is non-NULL before calling comp_destroy Code: Select allauthor Dominique Martinet <dominique.martinet@atmark-techno.com> 2025-01-07 16:16:04 +0900 committer Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2025-01-09 13:30:07 +0100 commit 677294e4da96547b9ea2955661a4bbf1d13552a3 (patch) tree 83d4b070c6ce13a472f460bde84ddb9d7e8c018d parent 91b493f15d65266ebba806553c97a2ae5df581ce (diff) download linux-677294e4da96547b9ea2955661a4bbf1d13552a3.tar.gz zram: check comp is non-NULL before calling comp_destroy This is a pre-requisite for the backport of commit 74363ec674cb ("zram: fix uninitialized ZRAM not releasing backing device"), which has been implemented differently in commit 7ac07a26dea7 ("zram: preparation for multi-zcomp support") upstream. We only need to ensure that zcomp_destroy is not called with a NULL comp, so add this check as the other commit cannot be backported easily. Stable-dep-of: 74363ec674cb ("zram: fix uninitialized ZRAM not releasing backing device") Link: https://lore.kernel.org/Z3ytcILx4S1v_ueJ@codewreck.org Suggested-by: Kairui Song <kasong@tencent.com> Signed-off-by: Dominique Martinet <dominique.martinet@atmark-techno.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Diffstat -rw-r--r-- drivers/block/zram/zram_drv.c 3 1 files changed, 2 insertions, 1 deletions diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c index b83181357f36d1..b4133258e1bfde 100644 --- a/drivers/block/zram/zram_drv.c +++ b/drivers/block/zram/zram_drv.c @@ -1733,7 +1733,8 @@ static void zram_reset_device(struct zram *zram) zram_meta_free(zram, zram->disksize); zram->disksize = 0; memset(&zram->stats, 0, sizeof(zram->stats)); - zcomp_destroy(zram->comp); + if (zram->comp) + zcomp_destroy(zram->comp); zram->comp = NULL; reset_bdev(zram); A new kernel version with the fix is already in the debian bookworm-proposed-updates repository: linux (6.1.124-1) bookworm; urgency=medium * New upstream stable update: https://www.kernel.org/pub/linux/kernel ... og-6.1.124 [..] - zram: check comp is non-NULL before calling comp_destroy [ Salvatore Bonaccorso ] * Bump ABI to 30 -- Salvatore Bonaccorso <carnil@debian.org> Sun, 12 Jan 2025 20:58:02 +0100 Hope this helps. -- [1] zram: Regression in at least linux-6.1.y tree |
I'm not going into politics, but is there an easy way to block (most of) the IP ranges of an entire country - system wide on a headless server? | I used the firewall to block anything but the ports I needed open, and merely added a blocklist for the service itself. |
Hello all, Big time beginner here at administering my own home server. I do admit, I've been getting help from ChatGPT for a lot of the configurations and just recently it steered me way wrong and now I'm suffering the consequences. I was having issues getting OpenVPN and Wireguard to route traffic properly (whatsmyip.com was still displaying my routers public IP even while connected to either OpenVPN or Wireguard). That was my first problem. Whilst troubleshooting the issue, I was instructed to use the command iptables -F and immediately lost connection through ssh. I hopped back into the server and reestablished the ssh connection, but quickly realized that I no longer had access to the internet for updates or installations. Now ChatGPT is advising me to reinstall the iptables, only I do not have access to an internet connection. I've tried rewriting the iptables and routings. It was like everything was back to normal, yet still I have no connection to the internet. I can however ping my gateway ip, but anything else it's like I broke everyhing; honestly I'm 2 seconds from reinstalling debian on my machine... but before i do that, can anyone please tell me this is just a big noob moment and help me fix it? Sorry for any lack of important information, just ask and I'll supply it. Thanks | Hello, NotreTerre wrote: 2025-01-23 22:28 [..] I decided first to cut off the wg0 and tun0 devices I had set up with the installation of a VPN. Turns out that was the issue and I've regained internet access on my server. [..] I'm glad you sorted it out. Please mark the discussion as "solved" adding the tag "[Solved]" at the beginning of the subject of he first post. Happy Debian EDIT Thu Jan 30 07:48:57 CET 2025: added the "solved" tag. |
Hello everyone, First of all, thank you for accepting my account to join the community. I’m looking forward to all I can learn through it. I use Debian and code as a hobby. I am a beginner. My goals are to create my own home server in order to hold and share data for my personal and professional use. I would like to be able to evolve as I learn and be able to even host my own website but it all depends on the complexity and time invested. So thank you in advanced to all you who share your experiences and knowledge to help me progress in my endeavors! Today I have installed Debian 12 using an old computer that I had lying around. For now the processor and memory is all bare minimum, but I will be upgrading in the near future. More details will be shared in the future of my setup, for now I’d just like to resolve my SSH connection issues. After a fresh install following the careful instructions found on YouTube, I successfully setup and connected to my server via SSH with key. I was having no trouble until I installed UFW on my own in hopes to increase security. We I carefully configured to allow the custom port i had set up during the hardening process, but now I can no longer connect through SSH. I’ve checked all statuses, restarted, I even disabled my UFW in hopes of tracing back my steps to when things were working properly, but it seems irreversible. I’ve looked up many troubleshoots and have tried checking all I could find but to no avail. I know I must be missing something, perhaps something overly simple (besides typing in the wrong user or address, I’ve double checked a dozen times). I’m also probably forgetting to include important information that you all may need to help me solve my problem, sorry in advance. Please just let me know and I’ll include whatever information is missing. Anyone have some ideas to share? I’ve gone through every test I could find on the internet to get back up and running. Please share your thoughts! Thanks! | friendlysalmon88 wrote: 2025-01-09 02:40 /var/log/sshd As usual you need to brush up on reality and think a bit before posting. |
Hi everyone. I have been trying to run update on my installed deb 12 , but doesnt seem to work. also tried trough terminal with update - there i get an error . ╰─ sudo apt update ─╯ Bra:1 http://debian.lth.se/debian bookworm InRelease Bra:2 http://debian.lth.se/debian bookworm-updates InRelease Ign:3 https://deb.debian.org/debian bookworm-security InRelease Fel:4 https://deb.debian.org/debian bookworm-security Release 404 Not Found [IP: 2a04:4e42:14::644 443] Bra:5 https://dl.google.com/linux/chrome/deb stable InRelease Läser paketlistor… Färdig E: The repository 'https://deb.debian.org/debian bookworm-security Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. what to do.! can somebody give some advice to get it working properly. / lindis68 | Hej! Short version: It indicates that there is something wrong with your sources.list This is a sources.list that will work: Code: Select alldeb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware #deb-src http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware deb http://security.debian.org/debian-security bookworm-security main contrib non-free-firmware #deb-src http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free-firmware #deb-src http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware Then add your google chrome repository, save the file and type (as root or sudo) Code: Select allapt update |
Hi I am running Debian Bullseye with Xfce desktop Thunar file manager on legacy laptop. I am unable to see or browse any of my network shares in file manager. When I try to browse network I get message... Code: Select all"failed to browse the network", the specified location is not supported I can use terminal and ssh to connect to network device which is a NAS. I am able browse network using file manager from another laptop I tried google but didn't see anything to fix client pc, but lots of hits to configure target pc. any help would be appreciated. | What's the file manager? Gnome Files? I think most GUI file managers use gvfs. Is that installed? |
Hi there, I am trying a little network setup at home (just for learning for now): 1. Router (Internet connectivity): 192.168.31.1 2. Virtual Machine 'VM HomeServer' (Debian 12): - IP Address: 192.168.31.230 for ‘public network’ - IP Address: 192.168.1.4 for private network - This VM should act as router for the private network (in particular for ‘VM Sandbox’) 2.1 IP Address: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:41:2f:9d brd ff:ff:ff:ff:ff:ff inet 192.168.31.230/24 brd 192.168.31.255 scope global enp1s0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe41:2f9d/64 scope link valid_lft forever preferred_lft forever enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:26:30:9f brd ff:ff:ff:ff:ff:ff inet 192.168.1.4/24 brd 192.168.1.255 scope global enp7s0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe26:309f/64 scope link valid_lft forever preferred_lft forever 2.2 Netplan: network: version: 2 renderer: networkd ethernets: enp7s0: addresses: - 192.168.1.4/24 dhcp4: no routes: - to: 192.168.1.0/24 via: 192.168.1.4 table: 101 - to: default via: 192.168.31.1 table: 101 routing-policy: - from: 192.168.1.0/24 table: 101 enp1s0: addresses: - 192.168.31.230/24 dhcp4: no routes: - to: default via: 192.168.31.1 on-link: true - to: 192.168.31.0/24 via: 192.168.31.1 table: 102 routing-policy: - from: 192.168.31.0/24 table: 102 2.3 /etc/sysctl.conf net.ipv4.ip_forward=1 net.ipv4.conf.default.rp_filter=1 net.ipv4.conf.all.rp_filter=1 net.ipv4.ip_forward=1 2.4 UFW: inactive 2.5 VM network adapter is set as bridged on host. 3. Virtual Machine 'VM Sandbox' (Debian 12) - IP Address: 192.168.1.100 for private network - This VM should communicate via ‘VM HomeServer’ with any computer on the private network or internet 2.1 IP Address: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:9b:35:94 brd ff:ff:ff:ff:ff:ff inet 192.168.1.100/24 brd 192.168.1.255 scope global enp1s0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe9b:3594/64 scope link valid_lft forever preferred_lft forever 2.2 Netplan: network: ethernets: enp1s0: dhcp4: no dhcp6: no optional: false addresses: - 192.168.1.100/24 routes: - to: default via: 192.168.1.4 version: 2 renderer: networkd 3.3 UFW: inactive 3.4 VM network adapter is set as bridged on host. Results: I can ping from ‘VM HomeServer’ to ‘VM Sandbox’ succfessful. I can ping from ‘VM Sandbox’ to ‘VM HomeServer’ succfessful. I can ping any public IP (e.g. 8.8.8. from ‘VM HomeServer’. Issue: I can’t ping any public IP (e.,g. 8.8.8. from ‘VM Sandbox’ as it shows a 100% packet loss. I can’t dig any URL from ‘VM Sandbox’ as it shows the followign error message: communications error to 192.168.31.1#53: timed out. A ‘traceroute’ to a public IP (e.g. 8.8.8. shows the following result (i.e. never finishesand just continues with ‘*’): traceroute to 8.8.8.8 (8.8.8., 64 hops max 1 192.168.1.4 0.869ms 0.680ms 0.652ms 2 * * A ‘traceroute’ to a private IP in the router network (e.g. 192.168.31.200 – another PC in my network) shows the following result (i.e. never finishesand just continues with ‘*’): traceroute to 192.168.31.200 (192.168.31.200), 64 hops max 1 192.168.1.4 0.884ms 0.492ms 0.702ms 2 * Question: Any idea how I can enable ‘VM Sandbox’ to reach any PC in network ‘192.168.31.xxx’ and the internet via ‘VM HomeServer’ . Thank you for your help. C. | Great you got it working. Please edit the title in your first post to add prefix [Solved] so it may help others. Also please use code tags for commands, configs, and terminal text etc. Fixed it in your last post for you. Good to see someone else in Melbourne uses Debian! |
Hi I have a newish install from an iso of Debian 12.7.0 on a VM on Proxmox. All was working well on kernel 6.1.0-26-amd64 until I ran an unattended apt-get upgrade. Kernel 6.1.0-27-amd64 was installed but on rebooting I get a kernel panic and an "unable to mount root fs" error. If I tell grub to load 6.1.0-26 the system boots ok. I can see an initrd entry in /boot/grub/grub.cfg for kernel "6.1.0-26-amd64" but not for 6.1.0-27-amd64 If I run apt-get update I receive a "cpio: write error: No space left on device" message: Code: Select allroot@Control:~# apt-get update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://security.debian.org/debian-security bookworm-security InRelease Hit:4 http://phoscon.de/apt/deconz generic InRelease Reading package lists... Done root@HomeControl:~# apt-get upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.142+deb12u1) ... update-initramfs: deferring update (trigger activated) Setting up linux-image-6.1.0-27-amd64 (6.1.115-1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.1.0-27-amd64 cpio: write error: No space left on device E: mkinitramfs failure cpio 2 update-initramfs: failed for /boot/initrd.img-6.1.0-27-amd64 with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.1.0-27-amd64 (--configure): installed linux-image-6.1.0-27-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.1.0-27-amd64 (= 6.1.115-1); however: Package linux-image-6.1.0-27-amd64 is not configured yet. if I run update-initramfs -c -k 6.1.0-27-amd64 I see this output: Code: Select allupdate-initramfs: Generating /boot/initrd.img-6.1.0-27-amd64 cpio: write error: No space left on device E: mkinitramfs failure cpio 2 if I run df I seem to have plenty of disk space: Code: Select allFilesystem Size Used Avail Use% Mounted on udev 3.9G 0 3.9G 0% /dev tmpfs 795M 11M 785M 2% /run /dev/sda1 32G 7.0G 23G 24% / tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 200M 92K 200M 1% /var/log tmpfs 100M 0 100M 0% /var/mail tmpfs 200M 4.0K 200M 1% /var/tmp tmpfs 100M 0 100M 0% /var/spool tmpfs 795M 0 795M 0% /run/user/0 My /boot doesn't contain much: Code: Select alltotal 51M -rw-r--r-- 1 root root 254K Sep 30 20:08 config-6.1.0-26-amd64 -rw-r--r-- 1 root root 254K Nov 1 04:23 config-6.1.0-27-amd64 drwxr-xr-x 5 root root 4.0K Nov 21 18:28 grub -rw-r--r-- 1 root root 35M Nov 5 16:51 initrd.img-6.1.0-26-amd64 -rw-r--r-- 1 root root 83 Sep 30 20:08 System.map-6.1.0-26-amd64 -rw-r--r-- 1 root root 83 Nov 1 04:23 System.map-6.1.0-27-amd64 -rw-r--r-- 1 root root 7.9M Sep 30 20:08 vmlinuz-6.1.0-26-amd64 -rw-r--r-- 1 root root 7.9M Nov 1 04:23 vmlinuz-6.1.0-27-amd64 Running apt-get autoremove --purge doesn't help: Code: Select allReading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.142+deb12u1) ... update-initramfs: deferring update (trigger activated) Setting up linux-image-6.1.0-27-amd64 (6.1.115-1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.1.0-27-amd64 cpio: write error: No space left on device E: mkinitramfs failure cpio 2 update-initramfs: failed for /boot/initrd.img-6.1.0-27-amd64 with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.1.0-27-amd64 (--configure): installed linux-image-6.1.0-27-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.1.0-27-amd64 (= 6.1.115-1); however: Package linux-image-6.1.0-27-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.1.0-26-amd64 cpio: write error: No space left on device E: mkinitramfs failure cpio 2 update-initramfs: failed for /boot/initrd.img-6.1.0-26-amd64 with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.1.0-27-amd64 linux-image-amd64 initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) Now, I think I've had the issue before, but I can't find the post where I found the solution that worked for me! The fix was something like Debian was trying to store temp files in /boot, but there wasn't enough room, so I had to tell Debian to store the temporary files on the main filesystem. This may, or may not be the issue this time, but I'd appreciate your help. Thanks Bert | You can try increasing the size of the /tmp mount point (see https://unix.stackexchange.com/question ... e-manually) |
kworker/0:1+kacpi_notify eating all cpu 1st core 17 root 20 R 100.0 58:45.55 `- [kworker/0:1+kacpi_notify] I'm running 6.1.0-25-amd64. (Debian 12) Code: Select alldmesg | grep -i error [ 0.252655] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP6.WLAN], AE_NOT_FOUND (20220331/dswload2-162) [ 0.252659] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220) [ 0.253322] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20220331/dswload2-162) [ 0.253324] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220) [ 0.253332] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP5.RTL8], AE_NOT_FOUND (20220331/dswload2-162) [ 0.253334] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220) [ 0.253347] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP6._PRW], AE_ALREADY_EXISTS (20220331/dswload2-326) [ 0.253349] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220) [ 0.253354] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP6.DEV0], AE_NOT_FOUND (20220331/dswload2-162) [ 0.253356] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220) [ 2.025253] amdgpu 0000:05:00.0: Direct firmware load for amdgpu/gc_11_0_1_mes_2.bin failed with error -2 Code: Select alljournalctl -k | grep acpi Sep 18 07:54:47 omen kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) Sep 18 07:54:47 omen kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Sep 18 07:54:47 omen kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] Sep 18 07:54:47 omen kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR] Sep 18 07:54:47 omen kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration Sep 18 07:54:47 omen kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns Sep 18 07:54:48 omen kernel: acpi-tad ACPI000E:00: Missing _PRW Sep 18 07:54:53 omen kernel: ucsi_acpi USBC000:00: PPM init failed (-5) any help appreciated P.S.: can't find information about top displaying cpus values. but I guess 0/100 100 means user processes utilize 0, system processes (root user) 100% utilization, and last is total. (0/100 also have different colors on bar) | sequencer wrote: 2024-09-19 19:14 Installed kernel 6.10.9 from sid. You said you are on Debian 12. You should not install kernels from Sid! If you need a newer kernel, install it from bookworm-backports. |
Hi there, I am trying a little network setup at home (just for learning for now). DHVPv4 with KEA is working fine, but I am a bit confused with KEA-DHCPv6 (using ULA for internal DHCPv6 stateful testing purposes). 1. Virtual Machine 'VM HomeServer' (Debian 12): 1.1 IP Address: Code: Select allenp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:26:30:9f brd ff:ff:ff:ff:ff:ff inet6 fd00:0:0:1::3/64 scope global valid_lft forever preferred_lft forever - This VM should act as stateful DHCPv6 router for the private network (in particular for ‘VM Sandbox’). I am using KEA as DHCPv6 application. 1.2 KEA DHCPv6 configuration: Code: Select all{ "Dhcp6": { "interfaces-config": { "interfaces": [ "enp7s0" ] }, "lease-database": { "type": "memfile", "persist": true, "name": "/var/lib/kea/kea-leases6.csv" }, "valid-lifetime": 28800, "option-data": [ { "name": "dns-servers", "data": "2001:4860:4860::8888, 2001:4860:4860::8844" } ], "subnet6": [ { "subnet": "fd00:0000:0000:0001::/64", "pools": [ { "pool": "fd00:0000:0000:0001::a - fd00:0000:0000:0001::ffff" } ] } ], "loggers": [ { "name": "kea-dhcp6", "severity": "DEBUG", "output_options": [ { "output": "/var/log/kea/kea-dhcp6.log", "maxver": 10 } ] }, { "name": "kea-dhcp6.dhcpsrv", "severity": "DEBUG", "output_options": [ { "output": "/var/log/kea/dhcp6-dhcpsrv.log", "maxver": 10 } ] }, { "name": "kea-dhcp6.leases", "severity": "DEBUG", "output_options": [ { "output": "/var/log/kea/dhcp4-leases.log", "maxver": 10 } ] } ] } } 1.3 RADVD: Code: Select allinterface enp7s0 { MinRtrAdvInterval 3; MaxRtrAdvInterval 4; AdvSendAdvert on; AdvManagedFlag on; prefix fd00:0000:0000:0001::/64 { AdvValidLifetime 14300; AdvPreferredLifetime 14200; AdvAutonomous off; } ; }; 1.4 UFW: active 1.5 VM network adapter is set as bridged on host. 1.6 Status KEA DHCPv6 1.6.1 From ‘/var/log/kea/kea-dhcp6.log’ Code: Select all2024-11-24 09:28:11.052 INFO [kea-dhcp6.hosts/946.139846052082176] HOSTS_BACKENDS_REGISTERED the following host backend types are available: mysql postgresql 2024-11-24 09:28:11.054 INFO [kea-dhcp6.dhcp6/946.139846052082176] DHCP6_CONFIG_COMPLETE DHCPv6 server has completed configuration: added IPv6 subnets: 1; DDNS: disabled 2024-11-24 09:28:11.057 INFO [kea-dhcp6.dhcp6/946.139846052082176] DHCP6_USING_SERVERID server is using server-id 00:01:00:01:2e:66:39:5e:52:54:00:41:2f:9d and stores in the file /var/lib/kea/kea-dhcp6-serverid 2024-11-24 09:28:11.058 WARN [kea-dhcp6.dhcp6/946.139846052082176] DHCP6_MULTI_THREADING_INFO enabled: no, number of threads: 0, queue size: 0 2024-11-24 09:28:11.058 INFO [kea-dhcp6.dhcp6/946.139846052082176] DHCP6_STARTED Kea DHCPv6 server version 2.2.0 started 1.6.2 From ‘systemctl status kea-dhcp6-server’ Code: Select all kea-dhcp6-server.service - Kea IPv6 DHCP daemon Loaded: loaded (/lib/systemd/system/kea-dhcp6-server.service; enabled; preset: enabled) Active: active (running) since Sun 2024-11-24 09:28:10 AEDT; 35min ago Docs: man:kea-dhcp6(8) Main PID: 946 (kea-dhcp6) Tasks: 5 (limit: 9449) Memory: 11.6M CPU: 344ms CGroup: /system.slice/kea-dhcp6-server.service 1.7 Status RADVD 1.7.1 From ‘systemctl status radvd.service’: Code: Select allradvd.service - Router advertisement daemon for IPv6 Loaded: loaded (/lib/systemd/system/radvd.service; enabled; preset: enabled) Active: active (running) since Sun 2024-11-24 09:45:22 AEDT; 19min ago Docs: man:radvd(8) Process: 2069 ExecStartPre=/usr/sbin/radvd --logmethod stderr_clean --configtest (code=exited, status=0/SUCCESS) Process: 2070 ExecStart=/usr/sbin/radvd --logmethod stderr_clean (code=exited, status=0/SUCCESS) Main PID: 2071 (radvd) Tasks: 2 (limit: 9449) Memory: 464.0K CPU: 327ms CGroup: /system.slice/radvd.service 1.7.2 From ‘rdisc6 enp7s0’: Code: Select allSoliciting ff02::2 (ff02::2) on enp7s0... Hop limit : 64 ( 0x40) Stateful address conf. : Yes Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 12 (0x0000000c) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : fd00:0:0:1::/64 On-link : Yes Autonomous address conf.: No Valid time : 14300 (0x000037dc) seconds Pref. time : 14200 (0x00003778) seconds Source link-layer address: 52:54:00:26:30:9F from fe80::85f4:b665:fd85:3d1e Hop limit : 64 ( 0x40) Stateful address conf. : Yes Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 12 (0x0000000c) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : fd00:0:0:1::/64 On-link : Yes Autonomous address conf.: No Valid time : 14300 (0x000037dc) seconds Pref. time : 14200 (0x00003778) seconds Source link-layer address: 52:54:00:26:30:9F from fe80::85f4:b665:fd85:3d1e 2. Virtual Machine 'VM Sandbox' (Debian 12) 2.1 IP Address: Code: Select allenp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:9b:35:94 brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:fe9b:3594/64 scope link valid_lft forever preferred_lft forever 2.2 Netplan: Code: Select allnetwork: ethernets: enp1s0: dhcp4: yes dhcp6: yes optional: false version: 2 renderer: networkd 2.3 UFW: active 2.4 VM network adapter is set as bridged on host. 2.5 Status RADVD 2.5.1 From ‘rdisc6 enp1s0’: Code: Select allSoliciting ff02::2 (ff02::2) on enp1s0... Hop limit : 64 ( 0x40) Stateful address conf. : Yes Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 12 (0x0000000c) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : fd00:0:0:1::/64 On-link : Yes Autonomous address conf.: No Valid time : 14300 (0x000037dc) seconds Pref. time : 14200 (0x00003778) seconds Source link-layer address: 52:54:00:26:30:9F from fe80::85f4:b665:fd85:3d1e Hop limit : 64 ( 0x40) Stateful address conf. : Yes Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 12 (0x0000000c) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : fd00:0:0:1::/64 On-link : Yes Autonomous address conf.: No Valid time : 14300 (0x000037dc) seconds Pref. time : 14200 (0x00003778) seconds Source link-layer address: 52:54:00:26:30:9F from fe80::85f4:b665:fd85:3d1e 3. Additional observations: If I change the RADVD configuration on ‘VM HomeServer’ to switch off AdvAutonomous (autonomous address configuration), the client ‘VM Sandbox’ sets it IPv6 IP based on the defined prefix (but obviosuly autonomously, so the DHCPv6 server on ‘VM HomeServer’ does not have an entry in its lease database in ‘/var/lib/kea/kea-leases6.csv’). 4. Questions: What configuration do I miss to enable stateful DHCPv6? Thank you so much. Best, C. | @maggiv8 Please use code tags for terminal text, messages etc. |
I have problems installing some new packages. When comparing this system to a fully working system I discovered that my system does not appear to have updated to Bookworm 12.7. Here is debian_version Code: Select allcharles@Charles-MacBook:~$ cat /etc/debian_version 12.6 charles@Charles-MacBook:~$ Base-files is stuck at 12.6: Code: Select all charles@Charles-MacBook:~$ apt policy base-files base-files: Installed: 12.4+deb12u6 Candidate: 12.4+deb12u6 Version table: *** 12.4+deb12u6 500 500 http://ftp.uk.debian.org/debian bookworm/main amd64 Packages 100 /var/lib/dpkg/status charles@Charles-MacBook:~$ I have done an apt update, but this still shows base-files at 12.6 Here is my sources.list and I have no other sources.list entries Code: Select all#deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 NETINST with firmware 20230610-10:21]/ bookworm main non-free-firmware deb http://ftp.uk.debian.org/debian/ bookworm main contrib non-free non-free-firmware deb-src http://ftp.uk.debian.org/debian/ bookworm main contrib non-free deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware deb-src http://security.debian.org/debian-security bookworm-security main contrib non-free # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://ftp.uk.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware deb-src http://ftp.uk.debian.org/debian/ bookworm-updates main contrib non-free # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. Strangely apt policy shows some 12.7 entries: Code: Select allPackage files: 100 /var/lib/dpkg/status release a=now 500 http://ftp.uk.debian.org/debian bookworm-updates/non-free-firmware amd64 Packages release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=non-free-firmware,b=amd64 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm-updates/non-free i386 Packages release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=non-free,b=i386 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm-updates/non-free amd64 Packages release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=non-free,b=amd64 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm-updates/contrib amd64 Packages release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=contrib,b=amd64 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm-updates/main i386 Packages release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=main,b=i386 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm-updates/main amd64 Packages release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=main,b=amd64 origin ftp.uk.debian.org 500 http://security.debian.org/debian-security bookworm-security/non-free-firmware i386 Packages release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=non-free-firmware,b=i386 origin security.debian.org 500 http://security.debian.org/debian-security bookworm-security/non-free-firmware amd64 Packages release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=non-free-firmware,b=amd64 origin security.debian.org 500 http://security.debian.org/debian-security bookworm-security/contrib amd64 Packages release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=contrib,b=amd64 origin security.debian.org 500 http://security.debian.org/debian-security bookworm-security/main i386 Packages release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=main,b=i386 origin security.debian.org 500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=main,b=amd64 origin security.debian.org 500 http://ftp.uk.debian.org/debian bookworm/non-free-firmware i386 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=non-free-firmware,b=i386 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm/non-free-firmware amd64 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=non-free-firmware,b=amd64 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm/non-free i386 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=non-free,b=i386 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm/non-free amd64 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=non-free,b=amd64 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm/contrib i386 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=contrib,b=i386 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm/contrib amd64 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=contrib,b=amd64 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm/main i386 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=main,b=i386 origin ftp.uk.debian.org 500 http://ftp.uk.debian.org/debian bookworm/main amd64 Packages release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=main,b=amd64 origin ftp.uk.debian.org Pinned packages: I have compared this system with another system that is quite happily running 12.7 and cannot see any differences. I've done an apt clean and an apt autoclean, but I'm still in this situation. I have no idea how this could possibly have happened and need help! | Try Code: Select allapt full-upgrade |
Dropbox has apparently stopped offering a separate Debian download within the past year (a search for how to install dropbox shows a YouTube video tutorial uploaded 11 months ago that includes a Debian 12 specific download). I've understood from other search results that the Ubuntu version is supposed to work -- though whether I should be using the one for 22.04 or the one for 18.04-22.04 isn't very clear; I've tried both of those within the past half hour and both give an error box with a message like "Dropbox couldn't be started" even after downloading the daemon. A restart does the same, and if I click through to Compile from Source with a penguin icon ahead of it, that has a Debian specific package -- but it has the same problem. Do I need to do something special to get Dropbox to correctly install on my new Debian 12.8 KDE? Ideally, of course, it should include the Nautilus extensions so I can see the local Dropbox folder in Nautilus. | Well, never mind, then. What I needed to do was to get my home folder(s) straightened out. I installed with the wrong username, and renaming the user home folders (/home/username) doesn't fix that. Further, adding a new user with the same full name to use the disconnected user home folder wouldn't let me log in as that new user. Reinstalled with the correct username, and Dropbox installed without a hitch, all working now. Desktop shortcuts to the local Dropbox folder now work right, too. |
I have an old Gigabyte motherboard (can't find the model number without opening the computer case, but it supports an Fx8350 CPU, 4 DDR3 RAM slots, no built-in video, two PCIex16 slots and 2 PCIex1 plus one or two PCI). The back panel has two USB 3.0 ports and I think there are a couple connectors for front panel etc. ports that are USB 3. Other than a brief period just before I updated to Kubuntu 22.04 (found a fix that worked in Kubuntu 16.04 but would not work in the later version) I have been unable to access the USB 3 ports; they create a delay of about 17 seconds during boot due to i/o errors before the system times out attempting to activate them. My other ports (USB 2) have worked fine. Can anyone confirm whether Debian 12.8 natively supports those ports or can be patched to do so? This may be specific to this family of Gigabyte motherboards (same problem with previous MB which was a slightly different model in the same family), and I can get the model number, with some effort... | No need to to create a new thread for the same topic. Linux kernel supports well USB3, so does Debian, I searched the Gigabyte problem, in the previous thread, don't remember it just now. So it perhaps is not a OS problem at all. Gigabyte has a driver patch for windows https://www.gigabyte.com/Motherboard/GA-USB-30/support the same page advises Linux users to seek support from chipset vendor's websites. Run Code: Select allinxi -F as root, or with sudo, should tell the model and serial number of the mainboard. You might have to install inxi first: Code: Select allsudo apt install inxi Or as root, if you have not configure sudo. |
I dual boot between LMDE (Mint Debian) Faye and Debian 12 Bookworm. I set up a "login script" via crontab in both installations, on LMDE it works correctly, on Debian it is ignored. I read something about @reboot commands being ignored in Debian's crontab files. Is there a workaround for this? | If this is a user cron then you need to use the absolute path “/usr/sbin/reboot” or possibly call a script instead of placing the command inline. |
Hello, I'm using Debian version 11.11 with Mate Desktop Environment. On friday, november 22 I "apt update && apt upgrade" the system, and the kernel went from version 6.10.9 to 6.11.9, and now I don't have ethernet or wifi working (I'm looking at the network applet of the Mate bar). If I boot with the old kernel (6.10.9) I have ethernet and wifi working. If I boot with 6.11.9 or 6.11.10 gives me no network at all. My card Code: Select all>> lspci -vnn -d ::0200 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (16) I219-V [8086:1a1f] (rev 01) Subsystem: Lenovo Ethernet Connection (16) I219-V [17aa:22e8] Flags: bus master, fast devsel, latency 0, IRQ 125, IOMMU group 12 Memory at bc300000 (32-bit, non-prefetchable) [size=128K] Capabilities: <access denied> Kernel driver in use: e1000e Kernel modules: e1000e Thank you for you patience | To have stable and unstable sources on your working computer is brave and dangerous. You would need non-free-firmware in sources to get firmware for that 6.11 kernel. Your system currently is what is known as a FrankenDebian. Read this - https://wiki.debian.org/DontBreakDebian |
Does deleting the contents of the directory /var/lib/apt/lists help in any way? Or is there something else that we should look at? For example a file which is say 30 days old can be deleted but others should not? | Hello @DebianFox, DebianFox wrote: 2024-11-29 05:37 Does deleting the contents of the directory /var/lib/apt/lists help in any way? Or is there something else that we should look at? For example a file which is say 30 days old can be deleted but others should not? No, it does not. Files in /var/lib/apt/lists are required by the Advanced Package Tool (or apt); from the apt-get manual page [1]: [..] --list-cleanup This option is on by default; use --no-list-cleanup to turn it off. When it is on, apt-get will automatically manage the contents of /var/lib/apt/lists to ensure that obsolete files are erased. The only reason to turn it off is if you frequently change your sources list. Configuration Item: APT::Get::List-Cleanup. [..] /var/lib/apt/lists/ Storage area for state information for each package resource specified in sources.list(5) Configuration Item: Dir::State::Lists. /var/lib/apt/lists/partial/ Storage area for state information in transit. Configuration Item: Dir::State::Lists (partial will be implicitly appended) [..] Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message. Thanks. -- [1] apt-get |
Hello forum, I recently updated my debian bullseye to bookworm and became aware, that I'm not able to use my VPN connection anymore. I use the Cisco AnyConnect or OpenConnect protocol. Related installed packages are: network-manager-gnome/stable,now 1.30.0-2 amd64 [installed] network-manager-openconnect-gnome/stable,now 1.2.8-3 amd64 [installed] network-manager-openconnect/stable,now 1.2.8-3 amd64 [installed] network-manager/stable,now 1.42.4-1 amd64 [installed] openvpn/stable,now 2.6.3-1 amd64 [installed,automatic] vpnc-scripts/stable,stable,now 0.1~git20220510-1 all [installed,automatic] I became aware that /etc/NetworkManager/system-connections/... configuration contains all relevant information, but at least in the gui of the network manager I'm not able to configure an CA Certificate any more. The gui configuration says CA Certificate (None). When selecting the desired one, it returns to (None) after beeing saved. The syslog claims a successfully updated configuration though. The log output when trying to connect looks like this: Code: Select allPOST https://[SERVER]/[PATH] Attempting to connect to server [IP]:443 Connected to [IP]:443 SSL negotiation with [SERVER] Connected to HTTPS on [SERVER] with ciphersuite (TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA512)-(AES-256-GCM) Got HTTP response: HTTP/1.1 200 OK Content-Type: text/xml; charset=utf-8 Transfer-Encoding: chunked Cache-Control: no-store Pragma: no-cache Connection: Keep-Alive Date: Sun, 02 Jul 2023 17:15:20 GMT X-Frame-Options: SAMEORIGIN Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-XSS-Protection: 1 Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self' X-Aggregate-Auth: 1 HTTP body chunked (-2) XML POST enabled POST https://[SERVER]/ Got HTTP response: HTTP/1.1 404 Not Found Cache-Control: no-store Pragma: no-cache Connection: Close Date: Sun, 02 Jul 2023 17:15:54 GMT X-Frame-Options: SAMEORIGIN Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-XSS-Protection: 1 Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self' HTTP body http 1.0 (-1) TLS/DTLS socket closed uncleanly Unexpected 404 result from server This is what syslog says then. Code: Select all2023-07-02T19:16:46.895603+02:00 brutus NetworkManager[629]: <warn> [1688318206.8951] vpn[0x55b6bef2a9b0,e1464ad7-b57a-4bce-ae12-ca61008485d2,"UKEr"]: final secrets request failed to provide sufficient secrets When looking at my bullseye system, I have the following packages installed: network-manager-gnome/oldstable,now 1.20.0-3 amd64 [installed] network-manager-openconnect-gnome/oldstable,now 1.2.6-1 amd64 [installed] network-manager-openconnect/oldstable,now 1.2.6-1 amd64 [installed] network-manager/oldstable,now 1.30.6-1+deb11u1 amd64 [installed,automatic] openvpn/oldstable,now 2.5.1-3 amd64 [installed] vpnc-scripts/oldstable,oldstable,now 0.1~git20200930-1 all [installed,automatic] A connection attempt does not result in an error. Even the first lines of the connection log look completely different. This is the log output before the credentials are supplied an the login button is pushed. Code: Select allPOST https://[SERVER]/[PATH] Attempting to connect to server [IP]:443 Connected to [IP]:443 SSL negotiation with [SERVER] Connected to HTTPS on [SERVER] with ciphersuite (TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA512)-(AES-256-GCM) Got HTTP response: HTTP/1.0 302 Temporary moved Set-Cookie: tg=0VEdfTUlLX09UUA==; path=/; secure Content-Length: 0 Cache-Control: no-store Pragma: no-cache Connection: Close Date: Sun, 02 Jul 2023 17:56:38 GMT X-Frame-Options: SAMEORIGIN Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-XSS-Protection: 1 Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self' Location: /+webvpn+/index.html HTTP body length: (0) GET https://[SERVER]/[PATH] Attempting to connect to server [IP]:443 Connected to [IP]:443 SSL negotiation with [SERVER] Connected to HTTPS on [SERVER] with ciphersuite (TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA512)-(AES-256-GCM) Got HTTP response: HTTP/1.0 302 Temporary moved Set-Cookie: tg=0VEdfTUlLX09UUA==; path=/; secure Content-Length: 0 Cache-Control: no-store Pragma: no-cache Connection: Close Date: Sun, 02 Jul 2023 17:56:38 GMT X-Frame-Options: SAMEORIGIN Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-XSS-Protection: 1 Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self' Location: /+webvpn+/index.html HTTP body length: (0) GET https://[SERVER]/+webvpn+/index.html SSL negotiation with [SERVER] Connected to HTTPS on [SERVER] with ciphersuite (TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA512)-(AES-256-GCM) Got HTTP response: HTTP/1.1 200 OK Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-XSS-Protection: 1 Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self' X-Frame-Options: SAMEORIGIN Transfer-Encoding: chunked Content-Type: text/xml; charset=utf-8 Cache-Control: no-store Set-Cookie: webvpn=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure Set-Cookie: webvpn_as=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure Set-Cookie: webvpnc=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure Set-Cookie: webvpnlogin=1; secure X-Transcend-Version: 1 HTTP body chunked (-2) What could be the reason for not being able to connect after the update, or what could I do to fix the problem? To me it seems like the reason for the problems is associated with the strange behaviour while configuring the CA Certificate, but maybe my feeling is wrong. I thank you for any help. Please forgive any language inconsistencies, English is not my native language. Regards, Martin | Hello, There's a bug report for package "network-manager-openconnect" about it with the title "network-manager-openconnect fails but openconnect --no-xmlpost works": https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842195 The bug submitter proposed a patch (you could manually apply it as you see fit), but the package's maintainer replied with a "won't fix" because: The openconnect man page describes the --no-xmlpost as a fallback option. IOW you should not have to use this setting at all. If you need it to connect to your gateway, there may be some compatibility problem that needs to be fixed. Therefore, you should understand why openconnect does not connect any more in the first place (as before). What is the verbose output of openconnect (-v option multiple times, see [1]) when it fails connecting from the command line ? What is its exit code ? Are you connecting using IPv4 or IPv6 ? --- [1] https://manpages.debian.org/bookworm/openconnect/openconnect.8.en.html |
Hi, I’ve installed Debian 11 on my Asus N550JV and can’t get the wifi to work properly. The problem : I can connect using the NetworkManager Applet from the tray icon in XFCE, but the signal works properly only to 5 to 10 seconds, until it reduces to a point I can't even ping a website. Until now, I used Ubuntu derivatives or Arch on this computer, and wifi connection always worked without any tweaks. The laptop has an Atheros AR9485 Wireless Network Adapter, running the ath9k driver Code: Select allsudo lshw -class network *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Qualcomm Atheros ... capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=5.16.0-3-amd64 firmware=N/A ip=192.168.1.13 latency=0 link=yes multicast=yes wireless=IEEE 802.11 ... What I tried : 1) I installed debian using the default iso (debian-11.2.0-amd64-netinst.iso). As I ran into the problem during the installation (unable to download necessary packages), I admitted that even if I was able to connect, maybe I was needing something from the non-free repos. 2) I tried another install, this time the dirty way with the non-free XFCE live iso (debian-live-11.2.0-amd64-xfce+nonfree.iso). Still having the wifi bug, but I could at least finish the installation. Anyway, now I don’t think it could be a proprietary firmware issue, as the `ath9k` driver is included in the kernel https://cateee.net/lkddb/web-lkddb/ATH9K.html 3) I’ve seen a lot of forum posts about tweaking the params of `/etc/modprobe.d/ath9k.conf`, especially the `nohwcrypt=1` param. (full list of available params here https://github.com/reynhout/chrx/blob/m ... ath9k.conf) I tried a bit of everything, didn’t fix. 4) I’ve found this article, about replacing network-manager with `wicd` … http://pkill-9.com/2013/04/23/stabilizi ... ux-wheezy/ but `wicd` is not maintained anymore and has been kicked out of the debian repos. 5) I tried to compile a backported driver, as described here : https://ubuntuforums.org/showthread.php ... st12890183 The driver compiled successfully. But didn´t fix. 6) I wondered if my bug would be fixed in a recent kernel, so I decided to take a turn for the worse and upgraded to Sid. Code: Select allcat /proc/version Linux version 5.16.0-3-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 11.2.0-18) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 5.16.11-1 (2022-02-25) I am now running a shiny new 5.16 kernel. Didn’t fix either. 7) As I was running out of troubleshooting ideas, I installed other distributions aside to check if my hardware is faulty, or if they would include specific configuration or hint for a fix. - MX Linux : same bug - Manjaro : works - Linux Mint : works - Ubuntu : works - Fedora : works (currently : Triple Boot Debian Sid XFCE / Xubuntu 21.10 XFCE / Fedora 35 XFCE) It seems like only Debian and direct derivatives would be impacted by the problem on my machine. The `/etc/modprobe.d/` is stacked with config files on the other distributions (mostly blacklisting stuff), but nothing related with the ath9k driver. Most config files, like `/etc/resolv.conf` have exactly the same contents in each distribution, and I have a hard time trying to understand what is going on. Any tip would be highly appreciated ! | firmware=N/A Maybe needs firmware-atheros installed Some wifi chips have issues with power saving mode. Search for how to disable it. |
Hi, Newbie to Debian. I installed: Debian 12 with XFCE 4.18 from: debian-live-12.8.0-amd64-xfce.iso And updated using sudo apt update && sudo apt upgrade I have installed: network-manager-openvpn network-manager-openvpn-gnome openvpn-systemd-resolved openvpn Then I imported a .ovpn file with Network Manager GUI: Opened Network Manager by clicking on the WIFI bars icon VPN Conections > Configure VPN Clicked Add > Import a saved VPN configuration Then added my VPN Username and password So that all went very well Problem is when I try to activate this OpenVPN connection, then an Authentication required dialog box pops up and asks for a password. I presume this is the OpenVPN account password. The password is already prefilled. When I click Ok, this dialog box closes, the OpenVPN connection is not made and the same dialog box pops up a few seconds later again. This continues to loop. I have double checked I have the correct password. Not sure what I am doing wrong. Any help is much appreciated. | Hello! I use XFCE, but have not used network manager, or once tryied, but after that I always purged it. Most XFCE programs have configs in /home/.config Check if there is any OpenVPn dirs, might be you can give your credentials there. Many GUI programs are just frontends. I think the CLI really makes a difference in Linux, you may not feel the same |
Hi all, in debian 12 server, without GUI DE tty console is blocked after a idle period in black screen and even if I push any key it does nothing, I've just to reboot from the pc power button | Does your server have a monitor, or where did you seen that 'black tty' ? |
I have a fresh Debian 12 VPS that runs dnsmasq, stubby and wireguard so i can have my own VPN. However for some unknown reason i cannot resolve youtube & google services while connected to the wireguard tunnel from my phone or desktop. Other apps and domains work fine. If i try to go to youtube.com via firefox i get "Address not found". I've used the same configs for a few years now on another OS, so rather puzzling why it is not working on Debian. I've tried a different VPS provider to rule out that google is doing any sort of blocking against the current provider, i've also switched the dns resolver from cloudflare to google, to rule out that maybe it's an issue with cloudflare. Configs: dnsmasq.conf Code: Select allno-resolv proxy-dnssec server=::1#5300 [b]server=127.0.0.1#5300 stubby.yml Code: Select allresolution_type: GETDNS_RESOLUTION_STUB dns_transport_list: - GETDNS_TRANSPORT_TLS tls_authentication: GETDNS_AUTHENTICATION_REQUIRED tls_query_padding_blocksize: 128 edns_client_subnet_private : 1 round_robin_upstreams: 1 idle_timeout: 9000 listen_addresses: - 127.0.0.1@5300 - 0::1@5300 upstream_recursive_servers: ## Cloudflare 1.1.1.1 and 1.0.0.1 ## (NOTE: recommend reducing idle_timeout to 9000 if using Cloudflare) - address_data: 1.1.1.1 tls_auth_name: "cloudflare-dns.com" - address_data: 1.0.0.1 tls_auth_name: "cloudflare-dns.com" ## Google - address_data: 8.8.8.8 tls_auth_name: "dns.google" - address_data: 8.8.4.4 tls_auth_name: "dns.google" I get no errors shown using the drill command so idk what program is to blame in this situation. Code: Select alldrill youtube.com ;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 69 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;; youtube.com. IN A ;; ANSWER SECTION: youtube.com. 286 IN A 216.58.206.46 ;; AUTHORITY SECTION: ;; ADDITIONAL SECTION: ;; Query time: 37 msec ;; EDNS: version 0; flags: ; udp: 512 ;; SERVER: 127.0.0.1 ;; WHEN: Sat Aug 3 14:12:46 2024 ;; MSG SIZE rcvd: 67 ;; EDNS: version 0; flags: ; udp: 512 ;; SERVER: 127.0.0.1 ;; WHEN: Sat Aug 3 14:12:46 2024 ;; MSG SIZE rcvd: 67 UPDATE - so thanks to some awesome help from lunaphyte on #dns irc chan, it seems the phone is having issues with the domain www.youtube.com. Some commands used to troubleshoot: ping -c 10 www.youtube.com Code: Select all~ $ ping -c 10 www.youtube.com ping: unknown host www.youtube.com ~ $ ping -c 10 youtube.com PING youtube.com (142.250.186.110) 56(84) bytes of data. 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=1 ttl=115 time=52.2 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=2 ttl=115 time=110 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=3 ttl=115 time=108 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=4 ttl=115 time=62.0 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=5 ttl=115 time=111 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=6 ttl=115 time=50.1 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=7 ttl=115 time=107 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=8 ttl=115 time=57.0 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=9 ttl=115 time=110 ms 64 bytes from fra24s06-in-f14.1e100.net (142.250.186.110): icmp_seq=10 ttl=115 time=57.7 ms --- youtube.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9019ms rtt min/avg/max/mdev = 50.159/82.721/111.426/27.050 ms ~ $ curl -v 'http://youtube.com' Code: Select all~ $ curl -v 'http://www.youtube.com' * Host www.youtube.com:80 was resolved. * IPv6: 2a00:1450:4001:813::200e, 2a00:1450:4001:812::200e, 2a00:1450:4001:802::200e, 2a00:1450:4001:831::200e * IPv4: (none) * Trying [2a00:1450:4001:813::200e]:80... * connect to 2a00:1450:4001:813::200e port 80 from fe80::74d9:1b3b:c58c:c751 port 52488 failed: Connection timed out * Trying [2a00:1450:4001:812::200e]:80... ^ you can see here curl does not get any ipv4 addresses. curl -v 'https://youtube.com' Code: Select all~ $ curl -v 'https://youtube.com' * Host youtube.com:443 was resolved. * IPv6: 2a00:1450:4001:82f::200e * IPv4: 172.217.16.206 * Trying 172.217.16.206:443... * Connected to youtube.com (172.217.16.206) port 443 * ALPN: curl offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CAfile: /data/data/com.termux/files/usr/etc/tls/cert.pem * CApath: /data/data/com.termux/files/usr/etc/tls/certs * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):* TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / x25519 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=*.google.com * start date: Jul 30 12:32:53 2024 GMT * expire date: Oct 22 12:32:52 2024 GMT * subjectAltName: host "youtube.com" matched cert's "youtube.com" * issuer: C=US; O=Google Trust Services; CN=WR2 * SSL certificate verify ok. * Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://youtube.com/ * [HTTP/2] [1] [:method: GET] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: youtube.com] * [HTTP/2] [1] [:path: /] * [HTTP/2] [1] [user-agent: curl/8.8.0] * [HTTP/2] [1] [accept: */*] > GET / HTTP/2 > Host: youtube.com > User-Agent: curl/8.8.0 > Accept: */* > * Request completely sent off * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing < HTTP/2 301 < content-type: application/binary < x-content-type-options: nosniff < expires: Sat, 03 Aug 2024 14:54:43 GMT < date: Sat, 03 Aug 2024 14:54:43 GMT < cache-control: private, max-age=31536000 < location: https://www.youtube.com/ < x-frame-options: SAMEORIGIN < strict-transport-security: max-age=31536000; includeSubDomains; preload < origin-trial: AmhMBR6zCLzDDxpW+HfpP67BqwIknWnyMOXOQGfzYswFmJe+fgaI6XZgAzcxOrzNtP7hEDsOo1jdjFnVr2IdxQ4AAAB4eyJvcmlnaW4iOiJodHRwczovL3lvdXR1YmUuY29tOjQ0MyIsImZlYXR1cmUiOiJXZWJWaWV3WFJlcXVlc3RlZFdpdGhEZXByZWNhdGlvbiIsImV4cGlyeSI6MTc1ODA2NzE5OSwiaXNTdWJkb21haW4iOnRydWV9 < permissions-policy: ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-form-factors=*, ch-ua-platform=*, ch-ua-platform-version=* < cross-origin-opener-policy: same-origin-allow-popups; report-to="youtube_main" < report-to: {"group":"youtube_main","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/youtube_main"}]} < p3p: CP="This is not a P3P policy! See http://support.google.com/accounts/answer/151657?hl=de for more info." < server: ESF < content-length: 0 < x-xss-protection: 0 < set-cookie: YSC=ev22B8acU14; Domain=.youtube.com; Path=/; Secure; HttpOnly; SameSite=none < alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 < * Connection #0 to host youtube.com left intact ~ $ curl -v 'https://www.youtube.com/' Code: Select all~ $ curl -v 'https://www.youtube.com/' * Host www.youtube.com:443 was resolved. * IPv6: 2a00:1450:4001:801::200e, 2a00:1450:4001:829::200e, 2a00:1450:4001:809::200e, 2a00:1450:4001:81c::200e * IPv4: (none) * Trying [2a00:1450:4001:801::200e]:443... ^ here it just timed out. Here's the results of ping and curl on another VPS (non-debian) using the same configs: curl Code: Select all~ $ curl -vso /dev/null 'https://www.youtube.com' * Host www.youtube.com:443 was resolved. * IPv6: 2a00:1450:4001:80f::200e, 2a00:1450:4001:800::200e, 2a00:1450:4001:801::200e, 2a00:1450:4001:80e::200e * IPv4: 142.250.74.206, 172.217.16.142, 172.217.18.110, 142.250.184.206, 142.250.185.110, 142.250.186.110, 172.217.18.14, 172.217.16.206, 216.58.206.78, 142.250.185.78, 216.58.206.46, 142.250.186.174, 142.250.185.142, 172.217.23.110, 142.250.186.78, 142.250.186.142 * Trying 142.250.74.206:443... * Connected to www.youtube.com (142.250.74.206) port 443 * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [512 bytes data] * CAfile: /data/data/com.termux/files/usr/etc/tls/cert.pem * CApath: /data/data/com.termux/files/usr/etc/tls/certs{ [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [122 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):{ [15 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [6300 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [78 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / x25519 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=*.google.com * start date: Jul 30 12:32:53 2024 GMT * expire date: Oct 22 12:32:52 2024 GMT * subjectAltName: host "www.youtube.com" matched cert's "*.youtube.com" * issuer: C=US; O=Google Trust Services; CN=WR2 * SSL certificate verify ok. * Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption } [5 bytes data] * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://www.youtube.com/ * [HTTP/2] [1] [:method: GET] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: www.youtube.com] * [HTTP/2] [1] [:path: /] * [HTTP/2] [1] [user-agent: curl/8.8.0] * [HTTP/2] [1] [accept: */*] } [5 bytes data] > GET / HTTP/2 > Host: www.youtube.com > User-Agent: curl/8.8.0 > Accept: */* > * Request completely sent off { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [282 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [282 bytes data] * old SSL session ID is stale, removing { [5 bytes data] < HTTP/2 200 < content-type: text/html; charset=utf-8 < x-content-type-options: nosniff < cache-control: no-cache, no-store, max-age=0, must-revalidate < pragma: no-cache < expires: Mon, 01 Jan 1990 00:00:00 GMT < date: Sat, 03 Aug 2024 15:37:46 GMT < strict-transport-security: max-age=31536000 < x-frame-options: SAMEORIGIN < permissions-policy: ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-form-factors=*, ch-ua-platform=*, ch-ua-platform-version=* < origin-trial: AmhMBR6zCLzDDxpW+HfpP67BqwIknWnyMOXOQGfzYswFmJe+fgaI6XZgAzcxOrzNtP7hEDsOo1jdjFnVr2IdxQ4AAAB4eyJvcmlnaW4iOiJodHRwczovL3lvdXR1YmUuY29tOjQ0MyIsImZlYXR1cmUiOiJXZWJWaWV3WFJlcXVlc3RlZFdpdGhEZXByZWNhdGlvbiIsImV4cGlyeSI6MTc1ODA2NzE5OSwiaXNTdWJkb21haW4iOnRydWV9 < cross-origin-opener-policy: same-origin-allow-popups; report-to="youtube_main" < report-to: {"group":"youtube_main","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/youtube_main"}]} < p3p: CP="This is not a P3P policy! See http://support.google.com/accounts/answer/151657?hl=de for more info." < server: ESF < x-xss-protection: 0 < set-cookie: YSC=EHacVG1ib6A; Domain=.youtube.com; Path=/; Secure; HttpOnly; SameSite=none < set-cookie: __Secure-YEC=Cgt2THNtZ1pCaTJIWSjKnbm1BjIKCgJERRIEEgAgVw%3D%3D; Domain=.youtube.com; Expires=Tue, 02-Sep-2025 15:37:45 GMT; Path=/; Secure; HttpOnly; SameSite=lax < set-cookie: VISITOR_PRIVACY_METADATA=CgJERRIEEgAgVw%3D%3D; Domain=.youtube.com; Expires=Tue, 02-Sep-2025 15:37:46 GMT; Path=/; Secure; HttpOnly; SameSite=none { [5 bytes data] < set-cookie: VISITOR_INFO1_LIVE=; Domain=.youtube.com; Expires=Sun, 07-Nov-2021 15:37:46 GMT; Path=/; Secure; HttpOnly; SameSite=none < alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 < accept-ranges: none < vary: Accept-Encoding < { [5 bytes data] * Connection #0 to host www.youtube.com left intact ~ $ ping Code: Select all~ $ ping -c 10 www.youtube.com PING youtube-ui.l.google.com (142.250.186.46) 56(84) bytes of data. 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=1 ttl=114 time=47.6 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=2 ttl=114 time=54.9 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=3 ttl=114 time=48.2 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=4 ttl=114 time=50.8 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=5 ttl=114 time=109 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=6 ttl=114 time=52.4 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=7 ttl=114 time=58.7 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=8 ttl=114 time=57.5 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=9 ttl=114 time=57.6 ms 64 bytes from fra24s04-in-f14.1e100.net (142.250.186.46): icmp_seq=10 ttl=114 time=57.8 ms --- youtube-ui.l.google.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9012ms rtt min/avg/max/mdev = 47.656/59.550/109.496/17.093 ms ~ $ | Hello, cmm11 wrote: 2024-08-07 15:11 I must of forgot to set a long expire time (if there even was an option) should be fixed now. I'm glad you sorted it out. :) Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message. Happy Debian ! :) |
I'm having difficulties connecting my Debian computer to a WPA2 Enterprise Network with PEAP. I was able to connect to other networks with no problems. When I try running nmcli, I get the error message: Code: Select allPasswords or encryption keys are required to access the wireless network '<ssid>'. Warning: password for '802-1x.identity' not given in 'passwd-file' and nmcli cannot ask without '--ask' option. Error: Connection activation failed: Secrets were required, but not provided Hint: use 'journalctl -xe NM_CONNECTION=<conncetion_name> + NM_DEVICE=wlan0 + NM_DEVICE=wlan0' to get more details. The contents of the journalctl command below: Code: Select allAug 21 12:16:20 debian NetworkManager[1752]: <info> [1724267780.1478] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Aug 21 12:16:20 debian NetworkManager[1752]: <info> [1724267780.3195] device (wlan0): supplicant interface state: internal-starting -> disconnected Aug 21 12:16:20 debian NetworkManager[1752]: <info> [1724267780.3292] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7128] device (wlan0): Activation: starting connection 'AVH' (57fd4b13-8925-4735-984a-cd85cffcb8a8) Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7696] device (wlan0): supplicant interface state: disconnected -> associated Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7705] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7712] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7727] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7737] device (wlan0): Activation: (wifi) access point 'AVH' has security, but secrets are required. Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7740] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7765] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7774] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:16:23 debian NetworkManager[1752]: <info> [1724267783.7782] device (wlan0): Activation: (wifi) connection 'AVH' has security, and secrets exist. No new secrets needed. Aug 21 12:16:24 debian NetworkManager[1752]: <info> [1724267784.3664] device (wlan0): supplicant interface state: disconnected -> scanning Aug 21 12:16:25 debian NetworkManager[1752]: <info> [1724267785.5276] device (wlan0): supplicant interface state: scanning -> authenticating Aug 21 12:16:25 debian NetworkManager[1752]: <info> [1724267785.5281] device (wlan0): supplicant interface state: authenticating -> associating Aug 21 12:16:25 debian NetworkManager[1752]: <info> [1724267785.5285] device (wlan0): supplicant interface state: associating -> associated Aug 21 12:16:27 debian NetworkManager[1752]: <info> [1724267787.6493] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:16:27 debian NetworkManager[1752]: <info> [1724267787.7492] device (wlan0): supplicant interface state: disconnected -> scanning Aug 21 12:16:40 debian NetworkManager[1752]: <info> [1724267800.6646] device (wlan0): supplicant interface state: scanning -> authenticating Aug 21 12:16:40 debian NetworkManager[1752]: <info> [1724267800.6664] device (wlan0): supplicant interface state: authenticating -> associating Aug 21 12:16:40 debian NetworkManager[1752]: <info> [1724267800.6728] device (wlan0): supplicant interface state: associating -> associated Aug 21 12:16:43 debian NetworkManager[1752]: <info> [1724267803.1116] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:16:43 debian NetworkManager[1752]: <info> [1724267803.2124] device (wlan0): supplicant interface state: disconnected -> scanning Aug 21 12:16:48 debian NetworkManager[1752]: <warn> [1724267808.7310] device (wlan0): Activation: (wifi) association took too long Aug 21 12:16:48 debian NetworkManager[1752]: <info> [1724267808.7313] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:16:48 debian NetworkManager[1752]: <warn> [1724267808.7341] device (wlan0): Activation: (wifi) asking for new secrets Aug 21 12:16:48 debian NetworkManager[1752]: <warn> [1724267808.7358] device (wlan0): no secrets: No agents were available for this request. Aug 21 12:16:48 debian NetworkManager[1752]: <info> [1724267808.7360] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Aug 21 12:16:48 debian NetworkManager[1752]: <warn> [1724267808.7405] device (wlan0): Activation: failed for connection 'AVH' Aug 21 12:16:48 debian NetworkManager[1752]: <info> [1724267808.7420] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Aug 21 12:16:49 debian NetworkManager[1752]: <info> [1724267809.6806] device (wlan0): supplicant interface state: scanning -> disconnected Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7804] device (wlan0): Activation: starting connection 'AVH' (57fd4b13-8925-4735-984a-cd85cffcb8a8) Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7806] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7815] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7825] device (wlan0): Activation: (wifi) access point 'AVH' has security, but secrets are required. Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7826] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7892] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7897] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.7907] device (wlan0): Activation: (wifi) connection 'AVH' has security, and secrets exist. No new secrets needed. Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.8114] device (wlan0): supplicant interface state: disconnected -> authenticating Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.8136] device (wlan0): supplicant interface state: authenticating -> associating Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.8267] device (wlan0): supplicant interface state: associating -> associated Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.8313] device (wlan0): state change: config -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.8354] device (wlan0): disconnecting for new activation request. Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9308] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9329] device (wlan0): Activation: starting connection 'AVH' (57fd4b13-8925-4735-984a-cd85cffcb8a8) Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9337] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9343] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9352] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9368] device (wlan0): Activation: (wifi) access point 'AVH' has security, but secrets are required. Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9369] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9396] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9404] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:10 debian NetworkManager[1752]: <info> [1724268010.9410] device (wlan0): Activation: (wifi) connection 'AVH' has security, and secrets exist. No new secrets needed. Aug 21 12:20:11 debian NetworkManager[1752]: <info> [1724268011.9968] device (wlan0): supplicant interface state: disconnected -> authenticating Aug 21 12:20:11 debian NetworkManager[1752]: <info> [1724268011.9990] device (wlan0): supplicant interface state: authenticating -> associating Aug 21 12:20:12 debian NetworkManager[1752]: <info> [1724268012.0010] device (wlan0): supplicant interface state: associating -> associated Aug 21 12:20:14 debian NetworkManager[1752]: <info> [1724268014.4221] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:20:14 debian NetworkManager[1752]: <info> [1724268014.5236] device (wlan0): supplicant interface state: disconnected -> scanning Aug 21 12:20:35 debian NetworkManager[1752]: <warn> [1724268035.7310] device (wlan0): Activation: (wifi) association took too long Aug 21 12:20:35 debian NetworkManager[1752]: <info> [1724268035.7313] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:35 debian NetworkManager[1752]: <warn> [1724268035.7336] device (wlan0): Activation: (wifi) asking for new secrets Aug 21 12:20:35 debian NetworkManager[1752]: <warn> [1724268035.8007] device (wlan0): no secrets: No agents were available for this request. Aug 21 12:20:35 debian NetworkManager[1752]: <info> [1724268035.8009] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Aug 21 12:20:35 debian NetworkManager[1752]: <warn> [1724268035.8024] device (wlan0): Activation: failed for connection 'AVH' Aug 21 12:20:35 debian NetworkManager[1752]: <info> [1724268035.8079] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Aug 21 12:20:36 debian NetworkManager[1752]: <info> [1724268036.7679] device (wlan0): supplicant interface state: scanning -> disconnected Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5490] device (wlan0): Activation: starting connection 'AVH' (57fd4b13-8925-4735-984a-cd85cffcb8a8) Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5492] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5507] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5522] device (wlan0): Activation: (wifi) access point 'AVH' has security, but secrets are required. Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5523] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5559] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5566] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5577] device (wlan0): Activation: (wifi) connection 'AVH' has security, and secrets exist. No new secrets needed. Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5782] device (wlan0): supplicant interface state: disconnected -> scanning Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5938] device (wlan0): state change: config -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.5955] device (wlan0): disconnecting for new activation request. Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6491] device (wlan0): supplicant interface state: scanning -> disconnected Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6495] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6522] device (wlan0): Activation: starting connection 'AVH' (57fd4b13-8925-4735-984a-cd85cffcb8a8) Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6534] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6544] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6552] device (wlan0): Activation: (wifi) access point 'AVH' has security, but secrets are required. Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6552] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6575] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6581] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:34 debian NetworkManager[1752]: <info> [1724268154.6586] device (wlan0): Activation: (wifi) connection 'AVH' has security, and secrets exist. No new secrets needed. Aug 21 12:22:35 debian NetworkManager[1752]: <info> [1724268155.5984] device (wlan0): supplicant interface state: disconnected -> authenticating Aug 21 12:22:35 debian NetworkManager[1752]: <info> [1724268155.6554] device (wlan0): supplicant interface state: authenticating -> associating Aug 21 12:22:35 debian NetworkManager[1752]: <info> [1724268155.6558] device (wlan0): supplicant interface state: associating -> associated Aug 21 12:22:37 debian NetworkManager[1752]: <info> [1724268157.8274] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:22:37 debian NetworkManager[1752]: <info> [1724268157.9264] device (wlan0): supplicant interface state: disconnected -> scanning Aug 21 12:22:59 debian NetworkManager[1752]: <warn> [1724268179.7312] device (wlan0): Activation: (wifi) association took too long Aug 21 12:22:59 debian NetworkManager[1752]: <info> [1724268179.7315] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 21 12:22:59 debian NetworkManager[1752]: <warn> [1724268179.7338] device (wlan0): Activation: (wifi) asking for new secrets Aug 21 12:22:59 debian NetworkManager[1752]: <warn> [1724268179.7967] device (wlan0): no secrets: No agents were available for this request. Aug 21 12:22:59 debian NetworkManager[1752]: <info> [1724268179.7968] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Aug 21 12:22:59 debian NetworkManager[1752]: <warn> [1724268179.7981] device (wlan0): Activation: failed for connection 'AVH' Aug 21 12:22:59 debian NetworkManager[1752]: <info> [1724268179.7986] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Aug 21 12:23:00 debian NetworkManager[1752]: <info> [1724268180.7515] device (wlan0): supplicant interface state: scanning -> disconnected Aug 21 12:26:38 debian NetworkManager[1752]: <info> [1724268398.7191] device (wlan0): supplicant interface state: disconnected -> associated Aug 21 12:26:38 debian NetworkManager[1752]: <info> [1724268398.7214] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:26:38 debian NetworkManager[1752]: <info> [1724268398.8037] device (wlan0): supplicant interface state: disconnected -> inactive Aug 21 12:31:36 debian NetworkManager[1752]: <info> [1724268696.7119] device (wlan0): supplicant interface state: inactive -> associated Aug 21 12:31:36 debian NetworkManager[1752]: <info> [1724268696.7247] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:31:36 debian NetworkManager[1752]: <info> [1724268696.8136] device (wlan0): supplicant interface state: disconnected -> inactive Aug 21 12:36:11 debian NetworkManager[1752]: <info> [1724268971.6652] device (wlan0): supplicant interface state: inactive -> associated Aug 21 12:36:11 debian NetworkManager[1752]: <info> [1724268971.6656] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:36:11 debian NetworkManager[1752]: <info> [1724268971.7589] device (wlan0): supplicant interface state: disconnected -> inactive Aug 21 12:39:47 debian NetworkManager[1752]: <info> [1724269187.6093] device (wlan0): supplicant interface state: inactive -> associated Aug 21 12:39:47 debian NetworkManager[1752]: <info> [1724269187.6271] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:39:47 debian NetworkManager[1752]: <info> [1724269187.7083] device (wlan0): supplicant interface state: disconnected -> inactive Aug 21 12:43:47 debian NetworkManager[1752]: <info> [1724269427.8540] device (wlan0): supplicant interface state: inactive -> associated Aug 21 12:43:47 debian NetworkManager[1752]: <info> [1724269427.8641] device (wlan0): supplicant interface state: associated -> disconnected Aug 21 12:43:47 debian NetworkManager[1752]: <info> [1724269427.9502] device (wlan0): supplicant interface state: disconnected -> inactive My connection.nmconnection file: Code: Select all[connection] id=AVH uuid=7e8f9581-3832-4a08-a813-12be14bfb684 type=wifi permissions=user:ky:; [wifi] mode=infrastructure ssid=redacted [wifi-security] key-mgmt=wpa-eap [802-1x] eap=peap; identity=redacted password=redacted phase2-auth=mschapv2 [ipv4] method=auto [ipv6] addr-gen-mode=stable-privacy method=auto [proxy] I have tried providing my password in a separate passwd-file, and by using the --ask flag to no avail. Trying to connect with wpa_supplicant produces the errors: Code: Select allCould not set interface p2p-dev-wlan0' UP deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0 p2p-dev-wlan0: Failed to initialize driver interface p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all P2P: Failed to enable P2P Device Interface All the outputs were copied by hand except for the journal logs to a computer which can connect to the internet, so there may be some typos. Thank you, Ky | Hello, May you can see here: 5.2.1. Configuring 802.1X Security for Wi-Fi with nmcli I cannot test it, but this is an example from link above, but I suspect that some options are not strictly mandatory and they depend on the parameters required by the configuration of the WPA2-PEAP you are connecting to: Code: Select allnmcli c add type wifi ifname wlo61s0 con-name 'My Wifi Network' \ 802-11-wireless.ssid 'My Wifi' \ 802-11-wireless-security.key-mgmt wpa-eap \ 802-1x.eap peap \ 802-1x.identity identity@example.com \ 802-1x.ca-cert /etc/pki/my-wifi/ca.crt \ 802-1x.client-cert /etc/pki/my-wifi/client.crt \ 802-1x.private-key /etc/pki/my-wifi/client.key \ 802-1x.private-key-password s3cr3t Hope this helps. |
I have a new installation of Debian 11 on a HP 17 laptop, that I am unable to connect to my home wireless network, LSPCI shows my wifi controller as: Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter . I installed the software from an image that included non-free sources. The Software package manager says that I already have Binary firmware for Realtek wired/wifi/BT adapters installed. ip link show returns the following: Code: Select all1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether e4:e7:49:93:00:99 brd ff:ff:ff:ff:ff:ff altname enp2s0 I used to have Linux Lite on this laptop, and was eventually able to get the wifi working, so I know that it is possible with this laptop. Any assistance that the board can provide would be useful. | If you search the forum, you will find many references to this device. The solution used to be to manually install the driver, because it wasn't in the kernel. However, the driver may be in the newest kernel from backports now, so try that first: viewtopic.php?p=749748#p749748 https://backports.debian.org/Instructions/ |
What are the main differences between the following? And when should environment variables be put in each of them? 1) /etc/environment 2) $HOME/.bashrc 3) $HOME/.profile Also if a Desktop environment (KDE or GNOME ) or Window Manager (IceWM, XFCe, etc) is used and an application is started using a shortcut then which of these files is parsed and then the variables used? | All of those files are parsed. As @Bloom mentioned /etc/environment is a systemwide config. ~/.profile is sourced once when you first log on to the machine, ~/.bashrc is sourced any time bash is called - like when you run a script or open a terminal window. Hope this helps- |
laptop: HP Pavilion G-series os: Debian 12 XFCE The shutdown process is not able to stop some processes: Code: Select all... job networking.service/stop running ... job networkmanager.service/stop running ... job wpa_supplicant.service/stop running... job networking.service/stop running After a while I get the following: Code: Select all[576.7-3785] systemd-shutdown[1] waiting for proces: 653 (Networkmanager), 654 (wpa_supplicant), 1723 (ifdown) So it hangs and does not shutdown. I have to remove the battery to stop What can be wrong and how can I solve this? | 6.1.0.16 is in bookworm-updates now. It fixes the issues mentioned in the link undesign posted. |
Edit: Here is the solution I was able to find. Firstly I would like to blame intel's screen refresh optimization. While I wouldn't call what I was seeing flickering, the screen was failing to refresh so this makes since. The fix was to add "i915.enable_psr=0" to the grub cmd line default. Here is the source https://wiki.archlinux.org/title/Intel_ ... flickering I don't know if this would work in debian or it's derivatives as I have switched to Arch. Here is a video of the issue https://vimeo.com/1009526794 and here is a link to my reddit post my hardware is a dell inspiron 16 plus 7630 with an intel core i13700H and 32gb of ram Firstly the Issue I've been having has spanned multiple different distros including: Nobara 40 GNOME, UBUNTU 24.04, Nyarch Linux 24.04, Kali 2024.1, zorin 17.1, mint 22, and Debian 12.7. Although Ubuntu, Debian and Mint work with safe graphics mode (nomodeset), however even with that set Nobara was still laggy. what i want to know is Option A) A solution to get my laptop not struggle to run Linux. Option B) If the solution is to just run safe graphics then is there any issues with always using nomodeset? I have discovered that for some reason my GPU is misidentified by Linux and Debian. What I mean is that as you can see below from the first and third command my driver is using a "Raptor Lake-P" driver where my CPU and from my understanding GPU are H chips. (Update) 9/16/24: I have purged xserver-xorg-video-intel as recommended by https://wiki.debian.org/GraphicsCard this resulted in little to no improvement. 9/16/24: I added Code: Select alldeb http://deb.debian.org/debian bookworm-backports main to /etc/apt/sources.list and updated apt packages. Then I installed with Code: Select allsudo apt install -t bookworm-backports linux-image-amd64 This resulted in a very slight improvement to the refresh rate of the screen. 9/16/24: as per a suggestion from a reddit user I tested my CPU and GPU usage without nomodeset. The results were that the CPU was only hit with about 15-20% on 2 cores while running system monitor and "intel_gpu_top" in a terminal. What I found much more interesting was that "intel_gpu_top" reported ~96% usage but the breakdown of the different engines showed 0% usage. "lspci -nn | egrep -i "3d|display|vga"" returns Code: Select allVGA compatible controller [0300]: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) "uname -r" returns Code: Select all6.1.0-25-amd64 "glxinfo -B" returns Code: Select allname of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Graphics (RPL-P) (0xa7a0) Version: 22.3.6 Accelerated: yes Video memory: 31778MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (RPL-P) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.6 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 | Use code tags for terminal text etc. please. Include the command you used to get the output as well. Fixed it for you this time. Your reddit link didn't work and "uname -r" is absent. |
at the moment my wlan is not working on my Server. The Error is the following Code: Select all[ 26.065107] wlan0: 80 MHz not supported, disabling VHT The WLAN-Card AX210 is recognized without problems see here: Code: Select alliwlwifi 0000:02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz I tried a lot of things but nothing works. my wlan is configured in /etc/network/interfaces as wlan0 Code: Select allauto eth0 iface eth0 inet dhcp metric 1 auto wlan0 iface wlan0 inet static metric 2 wpa-ssid wlan** wpa-psk ************ address ***.***.***.*** netmask ***.***.***.*** gateway ***.***.***.*** I think i need to activate VHT for more Bandwith but didn't find anything to enable that. Because the error is: 80MHz not supported. Any Ideas? | Hello @ayguddedachach, I see your marked your topic as [Solved]. How did you solve the problem? This might be useful for other users in the same case. Thanks. |
In my work environment I very frequently have the need to flush DNS cache, for which my go-to tool has been "resolvectl flush-caches" (and "systemd-resolve --flush-caches"before that). I recently upgraded to Debian 12 Bookworm and just today needed to flush the DNS cache, but to my surprise the new Debian OS seems to include neither resolvectl nor systemd-resolved. I have spent literally hours trying to verify this but have only found numerous examples of using those commands rather than an explanation as to why they're not included. Also surprising is that, if this omission is intentional, there seems to be no alternative other than rebooting. I was hoping the community here could give me some guidance. | ranomark wrote: 2023-06-29 14:08 Thank you @bw123 for the links to the release notes. The first link explained everything very clearly, and installing systemd-resolved manually was the solution. @ranomark : please mark the thread as "Solved" adding the tag "[Solved]" to the subject of the first post, e.g.: [Software] [Solved] Debian 12 Missing Resolvectl --- Moderator edit (aki) Mon Jul 10 07:32:56 CEST 2023: added [Solved] tag to the subject of the first post |
Hello there, is there a way to completely disable IPv6? So far the only working method I found is adding ipv6.disable=1 to GRUB; however this workaround doesn't block it completely, it only prevents to be used. The point is I don't run an ISP, I don't need IPv6, I don't want to see IPv6 utterly complicated stuff when I use Debian. It should be asked during the installation (and after a dist-upgrade) if you want enable IPv6, otherwise Debian is becoming and acting like Canonical does with Ubuntu. | Hello, Danielsan wrote: 2023-10-17 13:30 [..] adding ipv6.disable=1 to GRUB [..] however this workaround doesn't block it completely, it only prevents to be used. [..] So what do you want to achieve that disabling IPv6 from grub will not allow ? The ipv6 kernel module is compiled as a built-in part of the Debian kernel and this cannot be modified at install time (even if the debian developers wanted to): Code: Select all# grep CONFIG_IPV6= /boot/config-$(uname -r) CONFIG_IPV6=y If you wish, you can rebuild your own custom kernel disabling the compilation of IPV6 module. Are you willing to do this for the sake of block it completely ? |
I have searched this forum for a solution but I am still unsure how to fix this. My debian installation have not been started for a month or two, now that I started it I can't upgrade it. When I run apt update I get this: Code: Select allroot@MainDesktop:~# apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 https://download.docker.com/linux/debian bookworm InRelease 245 packages can be upgraded. Run 'apt list --upgradable' to see them. Then when I try to upgrade using apt upgrade I get this: Code: Select allSummary: Upgrading: 237, Installing: 13, Removing: 0, Not Upgrading: 8 Download size: 354 MB / 526 MB Space needed: 189 MB / 212 GB available Continue? [Y/n] Err:1 http://deb.debian.org/debian trixie/main amd64 dpkg amd64 1.22.9 404 Not Found [IP: 151.101.38.132 80] My sources.list looks like this: Code: Select allroot@MainDesktop:~# cat /etc/apt/sources.list # deb cdrom:[Debian GNU/Linux testing _Trixie_ - Official Snapshot amd64 NETINST with firmware 20240527-15:11]/ trixie contrib main non-free-firmware deb http://deb.debian.org/debian/ trixie main non-free-firmware contrib non-free #deb https://deb.debian.org/debian/ trixie-security main non-free-firmware contrib non-free #deb-src https://deb.debian.org/debian/ trixie-security main non-free-firmware contrib non-free # trixie-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://deb.debian.org/debian/ trixie-updates main non-free-firmware contrib non-free # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. Please help getting my system on track again. | Hello, What is the Debian release you are targeting? Bookworm or Trixie ? |
In Buster it was possible to run -cloud kernel and have functioning wireguard via apt install wireguard wireguard-tools. In Bookworkm, -cloud does not have necessary modules and an attempt to install the Wireguard while running it will result in the RT kernel installed and set as the default boot option... Which is rarely desirable on a server. What's up? | Hello, /usr/ wrote: 2024-09-19 14:00 In Bookworkm, -cloud does not have necessary modules and an attempt to install the Wireguard It seems it is not the case: Code: Select all$ wget http://ftp.us.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.1.0-25-cloud-amd64_6.1.106-3_amd64.deb $ dpkg-deb -x linux-image-6.1.0-25-cloud-amd64_6.1.106-3_amd64.deb . $ grep -i wireguard boot/config-6.1.0-25-cloud-amd64 CONFIG_WIREGUARD=m # CONFIG_WIREGUARD_DEBUG is not set /usr/ wrote: 2024-09-19 14:00 while running it will result in the RT kernel installed and set as the default boot option... Which is rarely desirable on a server. You don’t need to install wireguard package (it is a meta package). You need the package named wireguard-tools. |
os debian 12 testing kde Wayland Pipewire I installed an usb bluetooth adapter and had troubles conning devices. When I added a new device I got the error "br-connection-profile-unavailable". I added a phone, pc and headpohne. They all gave the same error. After I long search (google) I found the solution: - install libspa-0.2-bluetooth - reboot And then bluetooth worked. I checked another pc with and there was libspa-0.2-bluetooth installed allready. I don't know why libspa-0.2-bluetooth was missing on my pc. | Curious. KDE in Bookworm has Pulseaudio as default, not Pipewire. libspa-0.2-bluetooth is the bluetooth module for Pipewire however. Good you got it working. |
[I first posted essentially this question in the RPi Troubleshooting forum, but no takers. I have now tried exactly the same thing in a fresh install of stock Debian 12 on a separate machine. Same behaviour, so this doesn't seem to be RPi-specific. I'm hoping that one of the Debian network gurus will be able to set me straight. For context, I have not made any changes to the network configuration beyond plugging in a wifi dongle and using the Gnome widget to connect to my home wifi. The wlan interface name below is the one that was chosen automagically.] I have a script that I want to be executed when the wireless lan interface is taken down. I have tried both the following: a) place a script in /etc/network/if-down.d; b) place a script in /etc/NetworkManager/dispatcher.d. As far as I can tell, a) has no effect (the script is never run). For b) the script is run sometimes, but not when the wlan interface is taken down. For debugging purposes I have this: Code: Select all> cat /etc/NetworkManager/dispatcher.d/00-log-iface-events.sh #!/usr/bin/env bash interface=$1 event=$2 echo "===========" >> /tmp/Hello-there.txt echo "$interface received $event" >> /tmp/Hello-there.txt Having checked that wlx7cdd905b9c3d is up, I do Code: Select allsudo ip link set wlx7cdd905b9c3d down Nothing is written to the tmp file at all. I then do Code: Select allsudo ip link set wlx7cdd905b9c3d up The following is written: Code: Select all=========== wlx7cdd905b9c3d received dhcp4-change =========== wlx7cdd905b9c3d received dhcp6-change Note that only the dhcp events are logged, no "up" event. One additional data point: if I reboot with that script in place in /etc/NetworkManager/dispatcher.d, an "up" event is logged in the tmp file, so it seems that things do behave the way I was expecting when the wlan is first brought up. Any ideas? | Hello, What is the content of the file named /etc/network/interfaces ? You can use the following command: Code: Select allcat /etc/network/interfaces Just a guess. Try the following command: Code: Select allsudo ifdown wlan0 Then check the output of tmp file generated by the script in /etc/network/if-down.d |
I've never seen this behaviour before, so I took careful note of files and timestamps. (famous last words) In the past, I've had updates which changed config files which I had edited . These always stopped and offered to "go with the new maintainers version", keep mine, of diff them etc. In this case it appears to have just edited MY version of the file and so stopped exim4 from working. Here My log : On 08Sep2024 (log says @19:35:45) , I did a an apt-get update (actually synaptic) , followed by a reboot. When the system came up exim4 was no longer listening on most interfaces. It was only listening on localhost. A bit of investigation showed the file /etc/exim4/update-exim4.conf.conf had been modified during the update and rebuilt as /var/lib/exim4/config.autogenerated . FYI. I keep a git repo of my system file edits, so I can see my last edit I use a script to regnerate /var/lib/exim4/config.autogenerated and these keep logs of changes. (obvously this script was not use in this "unapproved" update) Code: Select allroot@zbox:~/XBOX-Configs/xbox.config/etc/exim4# make diff diff -X ../../.gitignore README /etc/exim4/README diff -X ../../.gitignore systemfilter.txt /etc/exim4/systemfilter.txt diff -X ../../.gitignore update-exim4.conf.conf /etc/exim4/update-exim4.conf.conf 51a52 > dc_local_interfaces='127.0.0.1 ; ::1' make: [Makefile:33: diff] Error 1 (ignored) diff -X ../../.gitignore GPV-commit-changes.sh /etc/exim4/GPV-commit-changes.sh diff -X ../../.gitignore passwd.client /etc/exim4/passwd.client diff -X ../../.gitignore -r conf.d /etc/exim4/conf.d diff -X ../../.gitignore -r exim.crt /etc/exim4/exim.crt diff -X ../../.gitignore -r exim.key /etc/exim4/exim.key diff -X ../../.gitignore -r BLESS-KEYS /etc/exim4/BLESS-KEYS diff -X ../../.gitignore -r GEN-KEYS /etc/exim4/GEN-KEYS diff -X ../../.gitignore -r get-dns-records /etc/exim4/get-dns-records diff -X ../../.gitignore -r README /etc/exim4/README diff -X ../../.gitignore -r keys /etc/exim4/keys Only in keys: dkim_ed25519.private Only in keys: dkim_ed25519.public Only in keys: dkim_rsa.private Only in keys: dkim_rsa.public Only in keys: README make: [Makefile:43: diff] Error 1 (ignored) You can see the line > dc_local_interfaces='127.0.0.1 ; ::1' was added to Code: Select allroot@zbox:~/XBOX-Configs/xbox.config/etc/exim4# ls -l update-exim4.conf.conf /etc/exim4/update-exim4.conf.conf -rw-r--r-- 1 root root 2840 Sep 8 19:40 /etc/exim4/update-exim4.conf.conf -rw-r--r-- 1 root root 2802 May 18 19:28 update-exim4.conf.conf root@zbox:~/XBOX-Configs/xbox.config/etc/exim4# ls -l /etc/exim4/*update-exim4* -rw-r--r-- 1 root root 2840 Sep 8 19:40 /etc/exim4/update-exim4.conf.conf -rw-r--r-- 1 root root 2497 Apr 3 18:27 /etc/exim4/update-exim4.conf.conf~ /var/lib/exim4: total used in directory 108 available 5.3 GiB drwxr-xr-x 2 root root 4096 Sep 8 20:23 . -rw-r--r-- 1 root Debian-exim 29388 Sep 8 20:23 config.autogenerated drwxr-xr-x 72 root root 4096 Sep 8 19:47 .. -rw-r--r-- 1 root root 29300 Apr 12 15:50 config.autogenerated.2024-04-12_15:50:01 -rw-r--r-- 1 root root 29469 Apr 12 15:39 config.autogenerated.2024-04-12_15:39:30 -rw-r--r-- 1 root root 4 Apr 2 16:45 berkeleydbvers.txt root@zbox:/etc/exim4# diff /var/lib/exim4/config.autogenerated.2024-04-12_15:50:01 /var/lib/exim4/config.autogenerated.broken-by-apt-upgrade 51a52,54 > .ifndef MAIN_LOCAL_INTERFACES > MAIN_LOCAL_INTERFACES=<; 127.0.0.1 ; ::1 > .endif 56c59 < MAIN_PACKAGE_VERSION=4.96-15+deb12u4 --- > MAIN_PACKAGE_VERSION=4.96-15+deb12u5 59c62 < MAIN_LOCAL_DOMAINS=@:localhost:ybox.home:home:wellesleydrive:xbox.home --- > MAIN_LOCAL_DOMAINS=@:localhost:ybox.home:home:wellesleydrive:xbox.home:zbox.home Note there are no "dist upgrade" files of other indication of "you have edited a file, choose original/maintainers/diff" ... Code: Select allroot@zbox:~/XBOX-Configs/xbox.config/etc/exim4# date Sun 8 Sep 22:29:27 BST 2024 root@zbox:~/XBOX-Configs/xbox.config/etc/exim4# uptime 22:29:30 up 2:06, 1 user, load average: 0.59, 0.58, 0.61 root@zbox:~/XBOX-Configs/xbox.config/etc/exim4# cat /var/log/apt/history.log Start-Date: 2024-09-08 19:35:45 Commandline: /usr/sbin/synaptic Requested-By: graeme (1501) Install: libparams-validate-perl:amd64 (1.31-1, automatic), linux-headers-6.1.0-25-common:amd64 (6.1.106-3, automatic), libgetopt-long-descriptive-perl:amd64 (0.111-1, automatic), linux-headers-6.1.0-25-amd64:amd64 (6.1.106-3, automatic), linux-image-6.1.0-25-amd64:amd64 (6.1.106-3, automatic) Upgrade: emacs:amd64 (1:28.2+1-15, 1:28.2+1-15+deb12u3), libcups2:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), libcurl4:amd64 (7.88.1-10+deb12u5, 7.88.1-10+deb12u7), initramfs-tools-core:amd64 (0.142, 0.142+deb12u1), libc6-i386:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), calamares-settings-debian:amd64 (12.0.9-1, 12.0.9-1+deb12u1), udev:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libvpx7:amd64 (1.12.0-1+deb12u2, 1.12.0-1+deb12u3), libkf5kiontlm5:amd64 (5.103.0-1, 5.103.0-1+deb12u1), krb5-locales:amd64 (1.20.1-2+deb12u1, 1.20.1-2+deb12u2), python3.11:amd64 (3.11.2-6, 3.11.2-6+deb12u3), libltdl7:amd64 (2.4.7-5, 2.4.7-7~deb12u1), exim4:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), bind9-host:amd64 (1:9.18.24-1, 1:9.18.28-1~deb12u2), libgssapi-krb5-2:amd64 (1.20.1-2+deb12u1, 1.20.1-2+deb12u2), libcurl3-gnutls:amd64 (7.88.1-10+deb12u5, 7.88.1-10+deb12u7), openssh-client:amd64 (1:9.2p1-2+deb12u2, 1:9.2p1-2+deb12u3), libgdk-pixbuf2.0-bin:amd64 (2.42.10+dfsg-1+b1, 2.42.10+dfsg-1+deb12u1), bubblewrap:amd64 (0.8.0-2, 0.8.0-2+deb12u1), libnss-myhostname:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), wpasupplicant:amd64 (2:2.10-12, 2:2.10-12+deb12u2), libglib2.0-bin:amd64 (2.74.6-2+deb12u2, 2.74.6-2+deb12u3), firefox-esr-l10n-sv-se:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-es-ar:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-es-cl:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-es-es:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-es-mx:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), cups-common:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), kio:amd64 (5.103.0-1, 5.103.0-1+deb12u1), gstreamer1.0-gl:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), libpam-systemd:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libqt5core5a:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), libkf5kiowidgets5:amd64 (5.103.0-1, 5.103.0-1+deb12u1), qt5-gtk-platformtheme:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), libarchive13:amd64 (3.6.2-1, 3.6.2-1+deb12u1), usb.ids:amd64 (2024.01.20-0+deb12u1, 2024.07.04-0+deb12u1), libaom3:amd64 (3.6.0-1, 3.6.0-1+deb12u1), firefox-esr-l10n-pa-in:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libgtk2.0-bin:amd64 (2.24.33-2, 2.24.33-2+deb12u1), dovecot-imapd:amd64 (1:2.3.19.1+dfsg1-2.1, 1:2.3.19.1+dfsg1-2.1+deb12u1), libtool-bin:amd64 (2.4.7-5, 2.4.7-7~deb12u1), firefox-esr-l10n-en-gb:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), temurin-8-jdk:amd64 (8.0.412.0.0+8, 8.0.422.0.0+5), gir1.2-gdkpixbuf-2.0:amd64 (2.42.10+dfsg-1+b1, 2.42.10+dfsg-1+deb12u1), bluetooth:amd64 (5.66-1+deb12u1, 5.66-1+deb12u2), libgs10-common:amd64 (10.0.0~dfsg-11+deb12u4, 10.0.0~dfsg-11+deb12u5), bluez-obexd:amd64 (5.66-1+deb12u1, 5.66-1+deb12u2), cups-client:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), cups-ppdc:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), libpathplan4:amd64 (2.42.2-7+b3, 2.42.2-7+deb12u1), cups-daemon:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), liblua5.4-0:amd64 (5.4.4-3, 5.4.4-3+deb12u1), firefox-esr-l10n-ast:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libjavascriptcoregtk-4.1-0:amd64 (2.44.2-1~deb12u1, 2.44.3-1~deb12u1), linux-compiler-gcc-12-x86:amd64 (6.1.90-1, 6.1.106-3), libgs10:amd64 (10.0.0~dfsg-11+deb12u4, 10.0.0~dfsg-11+deb12u5), software-properties-common:amd64 (0.99.30-4, 0.99.30-4.1~deb12u1), graphviz:amd64 (2.42.2-7+b3, 2.42.2-7+deb12u1), libsystemd0:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libqt5network5:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), libfreetype6:amd64 (2.12.1+dfsg-5, 2.12.1+dfsg-5+deb12u3), gir1.2-javascriptcoregtk-4.0:amd64 (2.44.2-1~deb12u1, 2.44.3-1~deb12u1), libcjson1:amd64 (1.7.15-1, 1.7.15-1+deb12u1), emacs-gtk:amd64 (1:28.2+1-15, 1:28.2+1-15+deb12u3), firefox-esr-l10n-nb-no:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libgvpr2:amd64 (2.42.2-7+b3, 2.42.2-7+deb12u1), libnss-systemd:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libgvc6:amd64 (2.42.2-7+b3, 2.42.2-7+deb12u1), libgstreamer-gl1.0-0:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), gir1.2-webkit2-4.0:amd64 (2.44.2-1~deb12u1, 2.44.3-1~deb12u1), linux-headers-amd64:amd64 (6.1.90-1, 6.1.106-3), openssh-server:amd64 (1:9.2p1-2+deb12u2, 1:9.2p1-2+deb12u3), exim4-config:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), libpython3.11-minimal:amd64 (3.11.2-6, 3.11.2-6+deb12u3), libgdk-pixbuf-2.0-0:amd64 (2.42.10+dfsg-1+b1, 2.42.10+dfsg-1+deb12u1), libqt5dbus5:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), libgail18:amd64 (2.24.33-2, 2.24.33-2+deb12u1), libkrb5support0:amd64 (1.20.1-2+deb12u1, 1.20.1-2+deb12u2), python3-software-properties:amd64 (0.99.30-4, 0.99.30-4.1~deb12u1), gir1.2-gtk-3.0:amd64 (3.24.38-2~deb12u1, 3.24.38-2~deb12u2), libglib2.0-data:amd64 (2.74.6-2+deb12u2, 2.74.6-2+deb12u3), libgtk2.0-common:amd64 (2.24.33-2, 2.24.33-2+deb12u1), gstreamer1.0-alsa:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), gir1.2-gst-plugins-base-1.0:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), firefox-esr-l10n-hi-in:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), systemd:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libudev1:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libqt5widgets5:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), libpostproc56:amd64 (7:5.1.4-0+deb12u1, 7:5.1.6-0+deb12u1), linux-kbuild-6.1:amd64 (6.1.90-1, 6.1.106-3), exim4-base:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), cups-ipp-utils:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), libcgraph6:amd64 (2.42.2-7+b3, 2.42.2-7+deb12u1), dovecot-core:amd64 (1:2.3.19.1+dfsg1-2.1, 1:2.3.19.1+dfsg1-2.1+deb12u1), libmagickcore-6.q16-6-extra:amd64 (8:6.9.11.60+dfsg-1.6+deb12u1, 8:6.9.11.60+dfsg-1.6+deb12u2), libqt5gui5:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), libltdl-dev:amd64 (2.4.7-5, 2.4.7-7~deb12u1), libgtk2.0-0:amd64 (2.24.33-2, 2.24.33-2+deb12u1), libc6:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), locales:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), libcdt5:amd64 (2.42.2-7+b3, 2.42.2-7+deb12u1), ghostscript:amd64 (10.0.0~dfsg-11+deb12u4, 10.0.0~dfsg-11+deb12u5), libssl3:amd64 (3.0.11-1~deb12u2, 3.0.14-1~deb12u2), libndp0:amd64 (1.8-1, 1.8-1+deb12u1), gstreamer1.0-x:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), firefox-esr-l10n-nn-no:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libkrb5-3:amd64 (1.20.1-2+deb12u1, 1.20.1-2+deb12u2), libqt5printsupport5:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), libpython3.11:amd64 (3.11.2-6, 3.11.2-6+deb12u3), linux-image-amd64:amd64 (6.1.90-1, 6.1.106-3), libavcodec59:amd64 (7:5.1.4-0+deb12u1, 7:5.1.6-0+deb12u1), libqt5xml5:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), bash:amd64 (5.2.15-2+b2, 5.2.15-2+b7), libmagickwand-6.q16-6:amd64 (8:6.9.11.60+dfsg-1.6+deb12u1, 8:6.9.11.60+dfsg-1.6+deb12u2), firefox-esr-l10n-gu-in:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), shim-helpers-amd64-signed:amd64 (1+15.7+1, 1+15.8+1~deb12u1), gstreamer1.0-plugins-base:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), bind9-dnsutils:amd64 (1:9.18.24-1, 1:9.18.28-1~deb12u2), base-files:amd64 (12.4+deb12u5, 12.4+deb12u7), libk5crypto3:amd64 (1.20.1-2+deb12u1, 1.20.1-2+deb12u2), libpython3.11-stdlib:amd64 (3.11.2-6, 3.11.2-6+deb12u3), software-properties-gtk:amd64 (0.99.30-4, 0.99.30-4.1~deb12u1), libavutil57:amd64 (7:5.1.4-0+deb12u1, 7:5.1.6-0+deb12u1), firefox-esr-l10n-ar:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-be:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-bg:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-bn:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-bs:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-ca:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-cs:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-cy:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-da:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-de:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-el:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-eo:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-et:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-eu:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-fa:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-fi:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-fr:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-gl:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-he:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-hr:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-hu:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-id:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-is:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-it:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-ja:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-kk:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-km:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-kn:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-ko:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-lt:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-lv:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-mk:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-mr:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-nl:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-pl:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-ro:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-ru:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-si:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-sk:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-sl:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-sq:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-sr:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-ta:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libqt5sql5:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), firefox-esr-l10n-te:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-th:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-tr:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-uk:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-vi:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libswscale6:amd64 (7:5.1.4-0+deb12u1, 7:5.1.6-0+deb12u1), libjavascriptcoregtk-4.0-18:amd64 (2.44.2-1~deb12u1, 2.44.3-1~deb12u1), libcupsimage2:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), libwebkit2gtk-4.1-0:amd64 (2.44.2-1~deb12u1, 2.44.3-1~deb12u1), distro-info-data:amd64 (0.58+deb12u1, 0.58+deb12u2), libtool:amd64 (2.4.7-5, 2.4.7-7~deb12u1), firefox-esr-l10n-pt-br:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-pt-pt:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libmagickcore-6.q16-6:amd64 (8:6.9.11.60+dfsg-1.6+deb12u1, 8:6.9.11.60+dfsg-1.6+deb12u2), libseccomp2:amd64 (2.5.4-1+b3, 2.5.4-1+deb12u1), libbluetooth3:amd64 (5.66-1+deb12u1, 5.66-1+deb12u2), libc-dev-bin:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), libglib2.0-0:amd64 (2.74.6-2+deb12u2, 2.74.6-2+deb12u3), openssh-sftp-server:amd64 (1:9.2p1-2+deb12u2, 1:9.2p1-2+deb12u3), nano:amd64 (7.2-1, 7.2-1+deb12u1), emacs-el:amd64 (1:28.2+1-15, 1:28.2+1-15+deb12u3), libc-l10n:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), libgtk-3-0:amd64 (3.24.38-2~deb12u1, 3.24.38-2~deb12u2), bind9-libs:amd64 (1:9.18.24-1, 1:9.18.28-1~deb12u2), python3.11-minimal:amd64 (3.11.2-6, 3.11.2-6+deb12u3), gtk2-engines-pixbuf:amd64 (2.24.33-2, 2.24.33-2+deb12u1), liblab-gamut1:amd64 (2.42.2-7+b3, 2.42.2-7+deb12u1), cups-core-drivers:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), libmail-dkim-perl:amd64 (1.20230212-1, 1.20230212-2~deb12u1), libc-bin:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), libsystemd-shared:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libc-devtools:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), libswresample4:amd64 (7:5.1.4-0+deb12u1, 7:5.1.6-0+deb12u1), imagemagick-6-common:amd64 (8:6.9.11.60+dfsg-1.6+deb12u1, 8:6.9.11.60+dfsg-1.6+deb12u2), gtk-update-icon-cache:amd64 (3.24.38-2~deb12u1, 3.24.38-2~deb12u2), firefox-esr-l10n-zh-cn:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), firefox-esr-l10n-zh-tw:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), initramfs-tools:amd64 (0.142, 0.142+deb12u1), libgtk-3-common:amd64 (3.24.38-2~deb12u1, 3.24.38-2~deb12u2), libc6-dev:amd64 (2.36-9+deb12u7, 2.36-9+deb12u8), libkf5kiocore5:amd64 (5.103.0-1, 5.103.0-1+deb12u1), libqt5sql5-sqlite:amd64 (5.15.8+dfsg-11, 5.15.8+dfsg-11+deb12u2), systemd-sysv:amd64 (252.22-1~deb12u1, 252.30-1~deb12u2), libgtk-3-bin:amd64 (3.24.38-2~deb12u1, 3.24.38-2~deb12u2), python3-idna:amd64 (3.3-1, 3.3-1+deb12u1), libwebkit2gtk-4.0-37:amd64 (2.44.2-1~deb12u1, 2.44.3-1~deb12u1), bluez:amd64 (5.66-1+deb12u1, 5.66-1+deb12u2), eximon4:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), libgnutls30:amd64 (3.7.9-2+deb12u2, 3.7.9-2+deb12u3), libavformat59:amd64 (7:5.1.4-0+deb12u1, 7:5.1.6-0+deb12u1), cups:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), curl:amd64 (7.88.1-10+deb12u5, 7.88.1-10+deb12u7), libkf5kiogui5:amd64 (5.103.0-1, 5.103.0-1+deb12u1), firefox-esr-l10n-ne-np:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), amd64-microcode:amd64 (3.20230808.1.1~deb12u1, 3.20240820.1~deb12u1), libgs-common:amd64 (10.0.0~dfsg-11+deb12u4, 10.0.0~dfsg-11+deb12u5), hostapd:amd64 (2:2.10-12, 2:2.10-12+deb12u2), libgstreamer-plugins-base1.0-0:amd64 (1.22.0-3+deb12u1, 1.22.0-3+deb12u2), firefox-esr:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), exim4-daemon-heavy:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), cups-server-common:amd64 (2.4.2-3+deb12u5, 2.4.2-3+deb12u7), emacs-common:amd64 (1:28.2+1-15, 1:28.2+1-15+deb12u3), shim-signed:amd64 (1.39+15.7-1, 1.44~1+deb12u1+15.8-1~deb12u1), firefox-esr-l10n-ga-ie:amd64 (115.11.0esr-1~deb12u1, 115.15.0esr-1~deb12u1), libcurl3-nss:amd64 (7.88.1-10+deb12u5, 7.88.1-10+deb12u7), libpq5:amd64 (15.6-0+deb12u1, 15.8-0+deb12u1), libgnutls-dane0:amd64 (3.7.9-2+deb12u2, 3.7.9-2+deb12u3), openjdk-17-jre-headless:amd64 (17.0.11+9-1~deb12u1, 17.0.12+7-2~deb12u1), shim-signed-common:amd64 (1.39+15.7-1, 1.44~1+deb12u1+15.8-1~deb12u1), dns-root-data:amd64 (2023010101, 2024041801~deb12u1), intel-microcode:amd64 (3.20231114.1~deb12u1, 3.20240813.1~deb12u1), libkworkspace5-5:amd64 (4:5.27.5-2+deb12u1, 4:5.27.5-2+deb12u2), emacs-bin-common:amd64 (1:28.2+1-15, 1:28.2+1-15+deb12u3), libgail-common:amd64 (2.24.33-2, 2.24.33-2+deb12u1), shim-unsigned:amd64 (15.7-1, 15.8-1~deb12u1), openssl:amd64 (3.0.11-1~deb12u2, 3.0.14-1~deb12u2), linux-libc-dev:amd64 (6.1.90-1, 6.1.106-3), libavfilter8:amd64 (7:5.1.4-0+deb12u1, 7:5.1.6-0+deb12u1), libgdk-pixbuf2.0-common:amd64 (2.42.10+dfsg-1, 2.42.10+dfsg-1+deb12u1) End-Date: 2024-09-08 19:49:03 Start-Date: 2024-09-08 20:01:17 Commandline: apt-get autoremove Requested-By: graeme (1501) Remove: linux-headers-6.1.0-21-amd64:amd64 (6.1.90-1), linux-headers-6.1.0-21-common:amd64 (6.1.90-1), linux-image-6.1.0-21-amd64:amd64 (6.1.90-1) End-Date: 2024-09-08 20:01:30 root@zbox:~/XBOX-Configs/xbox.config/etc/exim4# who -r run-level 5 2024-09-08 20:23 So things happened around (just before?) reboot. These are all listed in the Upgrade: exim4:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), exim4-config:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), exim4-base:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), eximon4:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), exim4-daemon-heavy:amd64 (4.96-15+deb12u4, 4.96-15+deb12u5), So it looks as if the update just out of the blue, modified my file and regenerated it. Code: Select allroot@zbox:/etc/exim4# uname -a Linux zbox 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux root@zbox:/etc/exim4# cat /etc/*release* PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@zbox:/etc/exim4# Just to be clear, it added the following lines: Code: Select all dc_local_interfaces='127.0.0.1 ; ::1' including the blank lines | Hello @mike.deb and @graemev2, Is there a bug report open in the Debian Bug Tracking System? If not, did one of you open one? |
Hello, during Debian 11 (with IIRC latest 5.x kernel) to Debian 12 apt update/upgrade/dist-upgrade, I have noticed: Setting up udev (252.30-1~deb12u2) ... configuration error - unknown item 'NONEXISTENT' (notify administrator) configuration error - unknown item 'PREVENT_NO_AUTH' (notify administrator) ... Setting up openssh-client (1:9.2p1-2+deb12u3) ... configuration error - unknown item 'NONEXISTENT' (notify administrator) configuration error - unknown item 'PREVENT_NO_AUTH' (notify administrator) if this is my failure, please how to fix it? Or if it is a Debian failure, was this already reported and which data I need to supply, please? | Hello, postcd wrote: 2024-10-05 08:45 during Debian 11 (with IIRC latest 5.x kernel) to Debian 12 apt update/upgrade/dist-upgrade, I have noticed: Setting up udev (252.30-1~deb12u2) ... configuration error - unknown item 'NONEXISTENT' (notify administrator) configuration error - unknown item 'PREVENT_NO_AUTH' (notify administrator) ... Setting up openssh-client (1:9.2p1-2+deb12u3) ... configuration error - unknown item 'NONEXISTENT' (notify administrator) configuration error - unknown item 'PREVENT_NO_AUTH' (notify administrator) if this is my failure, please how to fix it? The error messages: Code: Select allconfiguration error - unknown item 'NONEXISTENT' (notify administrator) configuration error - unknown item 'PREVENT_NO_AUTH' (notify administrator) are generated by the pwck program [1] from the passwd package [2]: Code: Select all# strings /usr/sbin/pwck | grep admin configuration error - unknown item '%s' (notify administrator) at the following position in the source code: sources / shadow / 1:4.16.0-4 / lib / getdef.c at line 434 The program checks if known configuration items are defined in a configuration file (perhaps /etc/login.defs, I assume) comparing them to a list of known configuration items (hard coded in the program itself). The error messages are probably caused by an not updated pwck program (after a Debian release upgrade) which is unaware of some configuration items or by some unknown configuration items in the configuration files. As reference, the allowed configuration items in /etc/login.defs can be found here [3]. You can replicate the error with: Code: Select all# pwck --read-only Check what is the pwck version with: Code: Select all# apt list passwd Hope this helps. Please let me know. -- [1] pwck manual page [2] passwd [3] login.defs.5 manual page |
Dear Team Thanks for reading my problem. I have googled the problem and tried to find out solutions at various platforms. But, no concrete answer I could find that would resolve the issue and remove my confusion. I am trying to install a fotware using spack on my Linux Debian cluster, which gave me error : Code: Select all ModuleNotFoundError: No module named '_ctypes' Internet fix suggested installing libffi-dev While trying to do so I am encounetring following issue: Code: Select allReading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libffi-dev 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 157 kB of archives. After this operation, 314 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libffi-dev Install these packages without verification? [y/N] y Err http://deb.debian.org/debian/ jessie/main libffi-dev amd64 3.1-2+deb8u1 404 Not Found [IP: 146.75.74.132 80] Err http://security.debian.org/debian-security/ jessie/updates/main libffi-dev amd64 3.1-2+deb8u1 404 Not Found [IP: 151.101.2.132 80] E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/libf/libffi/libffi-dev_3.1-2+deb8u1_amd64.deb 404 Not Found [IP: 151.101.2.132 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? I am not sure how can I overcome the above problem? My Linux cluster distribution is : Debian 8 (Jessie). Please advise. Thanks. | There is no security support for Jessie. That repo no longer exists. You really should upgrade your Debian, especially if connected to the internet. |
I’ve disabled Hyper Threading via Kernel by setting nosmt=force. After the system boots, running cat /sys/devices/system/cpu/smt/active returned 0 confirming that smt is disabled. Running lscpu showed Off-line CPU(s) list of off-line cores. Thread(s) per core shows 1. So all signs point that Hyper Threading is disabled. However, when I look at the System Monitor, it still shows all of the cores (including SMT’s). When I run sysbench CPU Test, I see all cores being utilized at 100% (including SMT’s). What am I doing wrong? How can I disable Hyper Threading permanently on Debian 12? I’m running with Coreboot and firmware does not have an option to disable HT on that level. | SubZero wrote: 2024-06-26 09:19 firmware does not have an option to disable HT That's unfortunate. I am a fan of disabling HT and have done so on Xeons for years. Those types have bios settings so I have never used 'software' control. I have tested w/ and w/o in the early days to come to that conclusion - from that I'd suggest you devise a timed test to give an indication whether the 'threaded' section is being used. Many methods may lie under software control, and lie either way? Handbrake is something that will benefit from threading assuming you exceed the base core count required. I would do a rescale of a 1080i source to 540 since that will add 4+ threads to the job. A straight compression using h265 of 1080 will top out at 10-12 threads, the rescale takes that up to 14-16. If these numbers are within the real core count then the test is invalid, if they exceed available cores then a short 10 minute video should reveal an advantage if HT is being used - no difference if not. If 10 exceeds your real core count, then you could skip the rescale. |
E4tHam wrote: 2024-06-27 23:54 Hello. I am a first time Debian-user, moving from Windows+WSL. I installed Debian through debian-live-12.5.0-amd64-gnome.iso, but my WiFi doesn't work with my Intel AX211. Gnome Settings just says "No Wi-Fi Adapter Found. Make sure you have a Wi-Fi adapter plugged and turned on" WiFi Card: Code: Select alllspci -vnn -d ::02xx 00:14.3 Network controller [0280]: Intel Corporation Meteor Lake PCH CNVi WiFi [8086:7e40] (rev 20) DeviceName: WLAN Subsystem: Intel Corporation Wi-Fi 6E AX211 160MHz [8086:0094] Flags: fast devsel, IRQ 18, IOMMU group 12 Memory at 50202d4000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel modules: iwlwifi I used mainline to install the latest kernel: Code: Select alluname -r 6.9.3-060903-generic Well, that's a Really Bad™ thing for starters. That's a Ubuntu kernel which is most certainly not supported for Debian. I modified my sources to match DebianTesting: Also a bad thing. Change your sources back to bookworm if you haven't updated the system yet. Otherwise you're stuck with Testing which is no place for a new user. And I have firmware-iwlwifi_20230625-2 installed. Yes you need that. A quick search shows that wifi device works in most of the Linux distros tested. https://linux-hardware.org/?id=pci:8086-7e40-8086-0094 It certainly looks fine in lspci. I don't know why GNOME would screw it up but I don't use GNOME. Post this command: Code: Select allip a Also check if it is blocked. Run as root or sudo: Code: Select allrfkill | Solved here, 2 days ago:- https://forums.debian.net/viewtopic.php ... 20#p802120 It's always good to search the forum before posting questions. |
os: debian 12 kde plasma When I execute the command "lsblk" I see a disk that does not exist: Code: Select allpeer@debian:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 119.2G 0 disk ├─sda1 8:1 0 102.2G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 17G 0 part [SWAP] sdb 8:16 0 931.5G 0 disk ├─sdb1 8:17 0 683.7G 0 part /media/data └─sdb2 8:18 0 247.8G 0 part /mnt/kvm sdc 8:32 0 149.1G 0 disk ├─sdc1 8:33 0 100M 0 part └─sdc2 8:34 0 149G 0 part sdd 8:48 0 931.5G 0 disk └─sdd1 8:49 0 931.5G 0 part /media/backup sde 8:64 1 0B 0 disk sr0 11:0 1 1024M 0 rom It is disk 'sde' with size=0 This happens with "lsblk¨, not with "sudo fdisk -l"or "sudo blkid" What can be wrong?? | Nothing wrong, man 8 lsblk wrote:DESCRIPTION lsblk lists information about all available or the specified block devices. The lsblk command reads the sysfs filesystem and udev db to gather information. On my system Code: Select all$> ls /dev/s[dr]* /dev/sda /dev/sda2 /dev/sdb1 /dev/sdb3 /dev/sdc /dev/sdc2 /dev/sdd /dev/sdf /dev/sdh /dev/sdh2 /dev/sda1 /dev/sdb /dev/sdb2 /dev/sdb4 /dev/sdc1 /dev/sdc3 /dev/sde /dev/sdg /dev/sdh1 /dev/sr0 Code: Select all$> lsblk -o NAME,MAJ:MIN,RM,SIZE,TYPE,FSROOTS,HOTPLUG,ROTA,MODEL,VENDOR,STATE NAME MAJ:MIN RM SIZE TYPE FSROOTS HOTPLUG ROTA MODEL VENDOR STATE sda 8:0 0 71,5G disk 0 0 INTEL SSDSC2CW120A3 ATA running ├─sda1 8:1 0 96M part / 0 0 └─sda2 8:2 0 71,4G part / 0 0 sdb 8:16 0 931,5G disk 0 1 WDC WD1003FZEX-00K3CA0 ATA running ├─sdb1 8:17 0 7,5G part 0 1 ├─sdb2 8:18 0 18,8G part / 0 1 ├─sdb3 8:19 0 281,3G part / 0 1 └─sdb4 8:20 0 623,9G part / 0 1 sdc 8:32 1 1,8T disk 1 1 WDC WD2003FZEX-00SRLA0 ATA running ├─sdc1 8:33 1 7,5G part 0 1 ├─sdc2 8:34 1 900G part / 0 1 └─sdc3 8:35 1 955,5G part / 0 1 sdd 8:48 1 0B disk 1 1 STORAGE DEVICE Generic running sde 8:64 1 0B disk 1 1 STORAGE DEVICE Generic running sdf 8:80 1 0B disk 1 1 STORAGE DEVICE Generic running sdg 8:96 1 0B disk 1 1 STORAGE DEVICE Generic running sdh 8:112 1 3,7G disk 1 1 USB Flash Disk General running ├─sdh1 8:113 1 627M part 1 1 └─sdh2 8:114 1 9,3M part 1 1 sr0 11:0 1 1024M rom 1 1 TSSTcorp CDDVDW SH-222BB TSSTcorp running Flash cards reader or something like this. man 8 lsblk wrote: OPTIONS -A, --noempty Don’t print empty devices. Code: Select all$> lsblk -o NAME,MAJ:MIN,RM,SIZE,TYPE,FSROOTS,HOTPLUG,ROTA,MODEL,VENDOR,STATE -A NAME MAJ:MIN RM SIZE TYPE FSROOTS HOTPLUG ROTA MODEL VENDOR STATE sda 8:0 0 71,5G disk 0 0 INTEL SSDSC2CW120A3 ATA running ├─sda1 8:1 0 96M part / 0 0 └─sda2 8:2 0 71,4G part / 0 0 sdb 8:16 0 931,5G disk 0 1 WDC WD1003FZEX-00K3CA0 ATA running ├─sdb1 8:17 0 7,5G part 0 1 ├─sdb2 8:18 0 18,8G part / 0 1 ├─sdb3 8:19 0 281,3G part / 0 1 └─sdb4 8:20 0 623,9G part / 0 1 sdc 8:32 1 1,8T disk 1 1 WDC WD2003FZEX-00SRLA0 ATA running ├─sdc1 8:33 1 7,5G part 0 1 ├─sdc2 8:34 1 900G part / 0 1 └─sdc3 8:35 1 955,5G part / 0 1 sdh 8:112 1 3,7G disk 1 1 USB Flash Disk General running ├─sdh1 8:113 1 627M part 1 1 └─sdh2 8:114 1 9,3M part 1 1 sr0 11:0 1 1024M rom 1 1 TSSTcorp CDDVDW SH-222BB TSSTcorp running |
How do I migrate `/` and `/home` from one device to a *prior* device? ## Background I'm tweeking a recent installs partition setup. I no longer want the swap partition I started with. Here is my partially updated disk configuration: Code: Select all$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 285M 0 part /boot/efi ├─sda2 8:2 0 16.1G 0 part └─sda3 8:3 0 449.4G 0 part /home / Note: `sda2` used to be the swap partition. ## So far I've formatted `sda2` as `btrfs`. This is the same filesystem as `sda3` where `/` and `/home` are. I've rsync'd everything I think I need from `sda3` over to `sda2`. Code: Select allrsync -avPAHXx / --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} ## Next steps? I believe I need to make changes to `grub` and `/etc/fstab` next. I haven't found anything solid in my web searches that I feel confident won't break my setup. Here is `/etc/fstab`, Code: Select all... # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda3 during installation UUID=b7bdceb4-660a-4951-94cd-df9412b74f93 / btrfs rw,noatime,space_cache=v2,compress=zstd,ssd,discard=async,subvol=@ 0 0 UUID=b7bdceb4-660a-4951-94cd-df9412b74f93 /home btrfs rw,noatime,space_cache=v2,compress=zstd,ssd,discard=async,subvol=@home 0 0 # /boot/efi was on /dev/sda1 during installation UUID=C0E2-7937 /boot/efi vfat umask=0077 0 1 # swap was on /dev/sda2 during installation # UUID=d23ef0d1-b4bd-4d7a-bb4a-f3bc0f41f5d2 none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 Note: I haven't updated `fstab` yet, beyond commenting out the original `swap` line. Note: the original install has the separate `/boot` partition. ## The goal(s) - Boot from the replicated device `sda2` - then I can delete the old `/` and `/home` on `sda3` - then I can merge `sda2` and `sda3` Thanks for any help! | The plan is workable here is the line I use in my backup script. Code: Select allrsync -ahPHAXx --delete --exclude={/boot/efi/*,/dev/*,/proc/*,/sys/*,/tmp/*,/run/*,/mnt/*,/media/*,/swapfile,/lost+found} / /tmp/root/ You will see I exclude the /boot/efi/* files as I have seperate line that does that partition. It is in here that you need to change the UUID in the grub.cfg file in the debian directory that is under the EFI directory. This is where grub first sets the partition it will boot from and makes it available. So the next step can load the /boot/grub/grub.cfg to give you the grub menu if enabled or to boot the first entry in the list. This file needs to be edited with the partition UUID you want to use to boot from the are many in there a good sed line will do them all at the same time. Code: Select all# My spare NVME install. cp /boot/grub/grub.cfg bin/boot_sp_nvme_grub.cfg sed -i "s/766dcfc3-a1e4-495f-86e2-570205723fef/a4410a13-b1ea-4007-b22f-6eb9e0a2ead4/g" /root/bin/boot_sp_nvme_grub.cfg The above line is from my fix_grub.sh script I run everytime the kernel is updated so my backup/cloning script get the correct kernel to boot from when /root/bin/boot_sp_nvme_grub.cfg gets copied to the destination drive /tmp/root/boot/grub/grub.cfg as that partition is mounted on /tmp/root/ when doing the procedure. And of course you already know the /etc/fstab needs to have proper UUIDs in it to know what you want mounted now. Oh and now I think my fix_swap.sh script that creates a swapfile. Code: Select allroot@9600k:~# cat bin/fix_swap.sh #!/bin/bash # A script to fix the swapfile missed when using new partition without one already there for a backup/clone/restore. # make the /swapfile file fallocate -l 2G /swapfile # correct the permissions chmod 600 /swapfile # format as swap space mkswap /swapfile # load the /swapfile swapon /swapfile In the /etc/fstab. Code: Select allroot@9600k:~# grep -i swap /etc/fstab # use swapfile instead of partition /swapfile none swap sw 0 0 You can create the swapfile anytime you wish after booting to "new" install. |
Hi, is there a way to selectively upgrade a package with apt, or to exclude specific packages from upgrade? Specifically, LibreOffice likes to reinstall 100s of megabytes of language extensions with each upgrade. Perhaps I just need to disable unwanted languages in LO, but I've tried this before and it's broken stuff.. Cheers, bitrat | What I have done to avoid updates on a package, is: Code: Select all apt-mark hold package_name apt update and then check if the system still needs updates for the package. If you want to upgrade a single package, I use: Code: Select all apt install package_name and if you use Code: Select all apt --only-upgrade install package_name it will avoid other stuff but the package_name. Cheers. |
Hi there. When starting the PC, the message "failed to start exim. service" appears. What happens is that the Internet does not work on my PC. I have verified that the exim4 exim-dev exim-daemon-heavy packages are not installed. Is it possible that I need to change the host advertising option or install a new certificate? Thank you. All the best. Hola buenas. Al iniciar el pc, aparece el mensaje "failed to start exim. service". Lo que sucede es que el Internet no me va en el PC. Los paquetes exim4 exim-dev exim-daemon-heavy he comprobado que no están instalados. Es posible que tenga que cambiar la opción de anunciar el hosts ó instalar un nuevo certificado? Gracias. Un saludo. | Hello, Debianday wrote: 2024-06-27 08:27 When starting the PC, the message "failed to start exim. service" appears. What happens is that the Internet does not work on my PC. I assume that your main problem is that you cannot configure the network connection to access the internet: Is it right ? If yes, what did you do to configure the network connection? Can you please give a log of your installation ? You can use the following commands: Code: Select allscript log.txt sudo apt install inxi inxi -Faz ip address sudo journalctl -b -g firmware exit This will create the log.txt file. You can report logs in one of the following ways: paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message attaching the logs to a follow-up forum message as a compressed zip or gz file paste logs into the body of a follow-up message between code tags (if they fit the size of a forum message) |
Hi, Is there a way to block a specific SSID in Debian so that a non admin. user will not be able to connect to it? Thanks. | Don't tell them the password. |
I upgraded my system from Debian 11 to Debian 12 a week or so ago. Printing stopped, with `lp` reporting `lp: Unauthorized` for any job sent to a printer. The following site, "Why do lp and lpr return unauthorized?"[1], indicates that a CUPS configuration has to be set to avoid the problem. Specifically, "AuthInfoRequired negotiate" is required. This lets an older printer work as expected. However, a modern, driverless printer still does not, since it is not possible to add that line to the printers.conf file. When CUPS is stopped, the entry for driverless printer disappears. It seems that line has to be present for the specific printer, just to make things difficult. I would like to retire the older printer and switch to the more modern printer. So, this problem is an issue that I would like resolved as soon as possible. Any help appreciated! 1. https://serverfault.com/questions/36920 ... authorized | Edit /etc/cups/cupsd.conf to allow local printing without authentication? |
Hello, kookamunga wrote: 2024-07-10 23:08 I have a Raspberry Pi 4 /8 GB running Debian Bookworm. In past months, the wireless connection worked fine. Now, after sitting unpowered for a few weeks, the Pi boots up but no wireless connection is made. [..] I believe the wireless hardware on the Pi is working. No IP address is being assigned to the Pi though, which is set for dynamic IP assignment from my router. The router doesn't show the Pi in its connection list, and I can't ping the router or anything else from the Pi. [..] I've also read about a supplicant file and an interfaces file. How should those be configured? You can see here: Debian Wiki - Network Configuration kookamunga wrote: 2024-07-10 23:08 Are you using the RPi's built-in wireless device or an external device? I re-ran "sudo raspi-config" and reset the network SSID and password -- and also made sure my country code was set to US, then rebooted. No change. If you have the raspi-config program installed, your operating system is not Debian but Raspbian. Can you confirm this? | Before trying to configure anything else, since you reported that the wireless connection worked before, you should have already installed a network configuration program: How were you used to connecting to the wireless network? What is your current network configuration ? What is your running kernel ? Are there any missing firmware ? You can verify with the following commands: Code: Select alluname -a lspci -vnn lsusb ip link ip address ip route sudo journalctl -b --no-pager -g firmwar What are running processes ? Is there a connection manager running ? You can verify with the following commands: Code: Select allps ax |
Might be a dumb question to ask but is a firewall necessary if a device is behind a CGNAT network? This is assuming the device only uses the CGNAT network and no other network. A similar question regarding VPN as well. VPN has several uses but If VPN is only needed to prevent people from seeing a device's ip address is it needed if one is behind a CGNAT network? I understand the ISP that runs the CGNAT network will be able to see everything. | DebianMan wrote: 2024-07-06 23:17 Might be a dumb question to ask but is a firewall necessary if a device is behind a CGNAT network? This is assuming the device only uses the CGNAT network and no other network. A carrier-grade NAT (CG-NAT) [1] should not allow access to an internal port from outside the NAT unless a connection to that port has already been established from inside. This ensures that the services of your Debian installation are not directly exposed to the public Internet. The need for a firewall is therefore less relevant. DebianMan wrote: 2024-07-06 23:17 A similar question regarding VPN as well. VPN has several uses but If VPN is only needed to prevent people from seeing a device's ip address is it needed if one is behind a CGNAT network? I understand the ISP that runs the CGNAT network will be able to see everything. The purpose of a VPN (Virtual Private Network) is to provide a secure (encrypted) communication channel between two networks. It's not intended to hide your originating IP address, that's just a side effect. Therefore, the server offering VPN services will always know what your originating address is. The CG-NAT is not relevant in this respect. Hope this helps. -- [1] https://en.wikipedia.org/wiki/Carrier-grade_NAT |
I just got a travel router (GL.iNET 750S), a very nifty little thing. When I start it, it starts emitting the WiFi. In order to get the router to connect to internet (e.g. hotel's wifi), I need to connect to the router and enter details in 192.168.8.1. However, the wirless network of the router doesn't show up when I list available networks to connect to. I found out I must first do below, and _then_ I see the network in my network manager menu. Code: Select allnmcli dev wifi Any idea why this is, or how to do it such that it sees the network immediately? I'm guessing it's not listing the wifi since it's a network that doesn't have internet (yet)? | cthulhu wrote: 2024-07-06 06:22 I just got a travel router (GL.iNET 750S), a very nifty little thing. [..] I found out I must first do below, and _then_ I see the network in my network manager menu. Code: Select allnmcli dev wifi Any idea why this is, or how to do it such that it sees the network immediately? I'm guessing it's not listing the wifi since it's a network that doesn't have internet (yet)? According to the manual page [1], the command nmcli device wifi: [..] wifi [list [--rescan | auto | no | yes] [ifname ifname] [bssid BSSID]] List available Wi-Fi access points. The ifname and bssid options can be used to list APs for a particular interface or with a specific BSSID, respectively. By default, nmcli ensures that the access point list is no older than 30 seconds and triggers a network scan if necessary. The --rescan can be used to either force or disable the scan regardless of how fresh the access point list is. [..] As you can see, the command triggers a network scan. That's why the wireless network name generated by the router is recognised by Debian's network manager as soon as you run the command. -- [1] NMCLI(1) - General Commands Manual |
Debian Bullseye on PI4B I created some source routing policies for my 2 vlans to fix the asymmetric routing issues I was having. It works fine . My question is why does 'ip rule show' display the following Code: Select all0: from all lookup local 32734: from all iif eth0.3 lookup vlan3 32735: from all iif eth0.1 lookup vlan1 32738: from all iif eth0.3 lookup vlan3 32739: from all iif eth0.1 lookup vlan1 32740: from 10.10.20.3 lookup vlan3 32741: from 10.10.10.3 lookup vlan1 32742: from all iif eth0.3 lookup vlan3 32743: from all iif eth0.1 lookup vlan1 32744: from 10.10.20.3 lookup vlan3 32745: from 10.10.10.3 lookup vlan1 32746: from all iif eth0.3 lookup vlan3 32747: from all iif eth0.1 lookup vlan1 32748: from 10.10.20.3 lookup vlan3 32749: from 10.10.10.3 lookup vlan1 32750: from all iif eth0.3 lookup vlan3 32751: from all iif eth0.1 lookup vlan1 32752: from 10.10.20.3 lookup vlan3 32753: from 10.10.10.3 lookup vlan1 32754: from all iif eth0.3 lookup vlan3 32755: from all iif eth0.1 lookup vlan1 32756: from 10.10.20.3 lookup vlan3 32757: from 10.10.10.3 lookup vlan1 32758: from all iif eth0.3 lookup vlan3 32759: from all iif eth0.1 lookup vlan1 32760: from 10.10.20.3 lookup vlan3 32761: from 10.10.10.3 lookup vlan1 32762: from all iif eth0.3 lookup vlan3 32763: from all iif eth0.1 lookup vlan1 32764: from 10.10.20.3 lookup vlan3 32765: from 10.10.10.3 lookup vlan1 32766: from all lookup main 32767: from all lookup default There are a lot of duplicate entries . | evinrude wrote: 2024-07-11 18:46 I created some source routing policies for my 2 vlans to fix the asymmetric routing issues I was having. [..] My question is why does 'ip rule show' display the following How did you set up those source routing policies ? Can you share the commands used ? |
Hello, mani wrote: 2024-07-01 14:13 SAR daily report files uses "OpenPGP Secret Key Version 6" as file type on Debian12.5, [..] Can someone clarify why Debian12 uses file-type as "OpenPGP Secret Key Version 6" ? is this can be the reason for occupying more disk space ? Refer the below output from Debian12.5, Code: Select allroot@10.0.0.1/var/log/sysstat#file * sa27: OpenPGP Secret Key Version 6 sa28: OpenPGP Secret Key Version 6 sa29: OpenPGP Secret Key Version 6 sa30: OpenPGP Secret Key Version 6 sar27: ASCII text sar28: ASCII text sar29: ASCII text sar30: ASCII text Here is the sample output from Debian11.7, sa27: data sa28: data sa29: data sa30: data sar27: ASCII text sar28: ASCII text sar29: ASCII text sar30: ASCII text It is highly probable that the file command identifies the binary files in /var/log/sysstat as "OpenPGP Secret Key Version 6" type, while they are not. According to the manual [1] of the file command: [..] The magic tests are used to check for files with data in particular fixed formats. [..] The information identifying these files is read from /etc/magic and the compiled magic file /usr/share/misc/magic.mgc, or the files in the directory /usr/share/misc/magic if the compiled file does not exist. In addition, if $HOME/.magic.mgc or $HOME/.magic exists, it will be used in preference to the system magic files. If a file does not match any of the entries in the magic file, it is examined to see if it seems to be a text file. [..] Any file that cannot be identified as having been written in any of the character sets listed above is simply said to be “data”. The magic test file named /etc/magic follows the format shown in [2]. The magic file can be compiled in a binary form, using the file command itself; According to the manual [1] of the file command: [..] NAME file — determine file type SYNOPSIS [..] file -C [-m magicfiles] [..] DESCRIPTION [..] -C, --compile Write a magic.mgc output file that contains a pre-parsed version of the magic file or directory. [..] The patterns used by default are in the source package of the file command and distributed as binary file in the file binary pacakge, i.e: sources/ file / 1:5.45-3 / magic / Magdir This is the file pattern that detect a pgp key: sources / file / 1:5.45-3 / magic / Magdir / pgp-binary-keys Hope this helps. --- [1] FILE(1) - General Commands Manual [2] MAGIC(1) - General Commands Manual -- note: lease, use code tags to include commands and/or their logs in the body of a message. I did it for you in the previous message | Hello @mani, Have you sorted it out? As a confirmation, you can analyse the first 255 bytes of one of the log SAR files recognized by the "file" command as a different type ? I.e. you can use the following command (the file name is from your example in the first post): Code: Select allhexdump -C -n 255 root@10.0.0.1/var/log/sysstat/sar27 Please let me know --- EDIT Tue Jul 30 12:11:42 CEST 2024: marked the discussion as solved. |
Hi, Per the title my laptop boots slowly. The message, Code: Select allBegin: Waiting for suspend/resume device ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. ... ... runs down the page for a while then the rest of the boot process resumes. Immediately before the message above is this line, Code: Select allBTRFS: device fsid ##### devid 1 trandid 1111 /dev/sda3 scanned by btrfs (217) I'm not sure where to start with this. The eventually machine boots. It's a quality of life type thing I'm posting about. Thanks, | eljfe wrote: 2024-07-18 02:55 Hi, Per the title my laptop boots slowly. The message, Code: Select allBegin: Waiting for suspend/resume device ... Begin: Running /scripts/local-block ... done. You may want to give the following thread a read. As I was suspecting with the warning above it is the resume slowing it down the page is discussing. https://askubuntu.com/questions/1034359 ... l-premount Found with this search. https://www.google.com/search?q=Begin%3 ... ne.&udm=14 |
Hi Debian community! And particularly, the lost few souls that are using Debian 12 & have the ALC4080 codec on their mobo that might encounter the same issue as I did. I had the problem where only the sound output on the back of my MSI PRO Z790-A WIFI worked ( L-out ). The front headphone jack output and both the front & back microphone input didn't work. After trying to revert back to PulseAudio from PipeWire, I understood that the problem isn't with the sound server. I was then able to narrow down the problem to ALSA not recognizing my Realtek ALC4080 chip/codec outputs & inputs correctly by following comments on some Github issue. The solution was to install the latest version of ALSA ucm ( 1.2.9 instead of 1.2.8 that we get with Debian by default on the date of writing this topic ) configuration from here. After following the guide, inside of my Gnome sound settings, my audio inputs and outputs had the '- USB Audio' appended to their names in the dropdowns which seemed right as the 4080 codec uses a USB interface between it and the CPU as far as I understand. Keep in mind that microphone volume could still potentially be very low, so I recommend setting it to 150% in pavucontrol. Maybe amplifying it inside of `EasyEffects` might work as well, but I didn't try that yet. Hopefully this is going to be helpful to someone out there. Enjoy! | Thank you! Debian Bookworm here with a MAG Z790 TOMAHAWK WIFI motherboard. I noticed S/PDIF Output was missing. Based on your post, I grabbed alsa-ucm-conf (1.2.9-1) from sid and installed it with dpkg. No fuss, just working sound outputs. EDIT: sid has since moved on to 1.2.13 and the libasound2t64 dependency is not compatible with bookworm. Fortunately, 1.2.9 can still be found in snapshots: https://snapshot.debian.org/package/als ... nf_1.2.9-1 (see alsa-ucm-conf_1.2.9-1_all.deb at the bottom) |
Ever since I moved to 6.1.0-21 I have been having problem shutting down. I had NO problems with earlier kernels. The system slowly over about ten minutes closes everything and announces it is ready for power down and then says: Tainted: P OE 6.1.0-21-amd64 Here is a snap of the screen. Is there a problem with this kernel? | https://docs.kernel.org/admin-guide/tai ... rnels.html The messages show the shutdown was blocked before the Tainted message so that is likely irrelevant. sd-sync appears to be the misbehaving process. Possibly a storage device is not syncing - https://github.com/systemd/systemd/issues/30025 |
Hi I have a Debian Bookworm image for the PineTab2 with plasma-mobile installed. The problem with this device at the moment is that the bes2600 wifi driver is buggy, and hangs unloading the module (I think that's the problem with it). The consequence is that it take about six minutes to shutdown/reboot the tablet whilst it waits for networkmanager and wpasupplicant to timeout. On shutdown you get a call trace from the bes2600 driver. then: Stopped wpa_supplicant.service - WPA supplicant then: device enter sleep then: Job NetworkManager.service/stop running (1min 37s / 3min 3s) after 3min 3 the timer increases to 4min 33s then: system-shutdown: waiting for process (NetworkManager) then: sending SIGKILL to remaining processes sending SIGKILL to PID 2263 (NetworkManager) which adds several minutes more I can't do anything about the bes2600 driver, but, I am wondering if some of these timeouts are configurable and how I could reduce them. I have also noticed that if I use the pull down menu thing in plasma-mobile (the one that has the shutdown button, airplane mode, etc etc) if I tap on the "WiFi" button to disable WiFi then there is a much shorter delay (two or three seconds) to disable WiFi and then I can shutdown or reboot instantly. What does that button actually do? and can I do the same thing in a shutdown script? thanks | Hello, dieselnutjob wrote: 2024-03-01 15:49 running "nmcli radio wifi off" prior to shutdown works how would I (and is it a good idea to) add that to a shutdown script ? It could be a good idea if you can do nothing about the bes2600 wireless kernel module, as you reported before. You can look here for instructions on how to get systemd to run a customised script when shutting down: SYSTEMD-HALT.SERVICE(8): [..] Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in /lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables finished. [..] As an alternative, you can create your own custom system service to run your custom script on shutdown. You can see this here: How to run a script with systemd right before shutdown? Hope this helps. Let me know :) |
Hi guys, I'm trying to use an old Dell 1320c printer which worked with linux some years ago... The printer had no Dell driver, so one had to use one from Fuji-Xerox to get this working back in the days. My problem is the driver I used before is a 32bit driver available here. I'm not at all experienced in manipulating drivers - is it possible to make the above .deb file use a 64bit system after some changes? Is there any information about switching a .deb file from 32 to 64 bit? My actual system is a 64bit debian bookworm. I first tried to search the web but found no information about that by myself - but after a few days I gave up... maybe I used the wrong search terms. Any help appreciated! thanks, Dan | Hello, damn. wrote: 2024-05-16 14:39 [..] My problem is the driver I used before is a 32bit driver available here. I'm not at all experienced in manipulating drivers - is it possible to make the above .deb file use a 64bit system after some changes? Is there any information about switching a .deb file from 32 to 64 bit? My actual system is a 64bit debian bookworm. [..] You cannot recompile because the debian file you referfenced above does not contains source code, but only binary files. These are the executable contained in the deb file named fuji-xerox-docuprint-c525-a-ap_1.0-2_i386.deb : Code: Select all$ wget https://fastcat.org/debrepo/pool/main/f/fuji-xerox-docuprint-c525-a-ap/fuji-xerox-docuprint-c525-a-ap_1.0-2_i386.deb $ mkdir fuji-xerox-docuprint-c525 $ cd fuji-xerox-docuprint-c525 $ dpkg-deb -x ../fuji-xerox-docuprint-c525-a-ap_1.0-2_i386.deb ./ $ ls -la usr/lib/cups/filter/ -la total 464 drwxr-xr-x 2 aki aki 4096 May 16 17:56 . drwxr-xr-x 3 aki aki 4096 Mar 5 2013 .. -rwxr-xr-x 1 aki aki 221005 Jun 1 2005 FXM_ALC -rwxr-xr-x 1 aki aki 52357 Jun 1 2005 FXM_CC -rwxr-xr-x 1 aki aki 58488 Jun 1 2005 FXM_HBPL -rwxr-xr-x 1 aki aki 15813 Jun 1 2005 FXM_MF -rwxr-xr-x 1 aki aki 17065 Jun 1 2005 FXM_PF -rwxr-xr-x 1 aki aki 19500 Jun 1 2005 FXM_PM2FXR -rwxr-xr-x 1 aki aki 22648 Jun 1 2005 FXM_PR -rwxr-xr-x 1 aki aki 753 Jun 1 2005 FXM_PS2PM -rwxr-xr-x 1 aki aki 43702 Jun 1 2005 FXM_SBP These are 32 bit executables; i.e.: Code: Select all$ cd usr/lib/cups/filter/ $ file ./FXM_ALC ./FXM_ALC: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.2.5, with debug_info, not stripped The linked 32 bit libraries are: Code: Select all$ for f in *; do ldd $f; done | cut -d ' ' -f 1 | sort| uniq /lib/ld-linux.so.2 libc.so.6 libcups.so.2 linux-gate.so.1 These libraries are contained in these package (note: linux-gate.so.1 [1] is not a library): Code: Select alllibcups2 (for i386) libc6 (for i386) Therefore, you can activate the multiarch support for i386 on amd64 in Debian; see: Multiarch HOWTO After you have activated the multiarch support for i386 on amd64, then you can install libcups2 for i386 architecture (libc6:i386 should be already installed): Code: Select all# apt install libcups2:i386 # apt list libcups2 Listing... Done libcups2/stable,now 2.4.2-3+deb12u5 amd64 [installed,automatic] libcups2/stable,now 2.4.2-3+deb12u5 i386 [installed] # apt list libc6 Listing... Done libc6/stable-security,now 2.36-9+deb12u7 amd64 [installed] libc6/stable-security,now 2.36-9+deb12u7 i386 [installed,automatic] Then, you can download and install the 32 bit package: Code: Select all# wget https://fastcat.org/debrepo/pool/main/f/fuji-xerox-docuprint-c525-a-ap/fuji-xerox-docuprint-c525-a-ap_1.0-2_i386.deb # dpkg -i fuji-xerox-docuprint-c525-a-ap_1.0-2_i386.deb Hope this helps. -- [1] What are ld-linux.so.2 and linux-gate.so.1? |
Hello! On Debian 12 Bookworm systems, the following error appears in the systemd journal when I attempt to start Apache with the 'qos' module enabled (aka mod_qos), and Apache fails to start: Code: Select allapachectl[14577]: apache2: Syntax error on line 143 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/qos.load: Cannot load /usr/lib/apache2/modules/mod_qos.so into server: /usr/lib/apache2/modules/mod_qos.so: undefined symbol: pcre_free apachectl[14574]: Action 'start' failed. apachectl[14574]: The Apache error log may have more information. systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE The systems in question were installed with the 'netinst' Bookworm image, and mod_qos was installed on them with the 'libapache2-mod-qos' package from the 'bookworm/main' repository. I have checked the Apache error log, as suggested in the message above, but there is no information on this event there. I have also read the mod_qos documentation, which says that "PCRE" is required for mod_qos to operate, but it is not specific about exactly what PCRE libraries are needed. It does appear that a PCRE dependency is missing, though I can't work out quite what that is. The package depends on the following, and those packages all appear to be installed: Code: Select all'(>= 1.2.7), libaprutil1 (>= 1.2.7+dfsg), libc6 (>= 2.33), libpcre3, libpng16-16 (>= 1.6.2-1), libssl3 (>= 3.0.0), zlib1g (>= 1:1.1.4), apache2-api-20120211, apache2-bin (>= 2.4.16)' I have also tried installing other PCRE packages that were not already installed on the system, to no avail. A package maintainer is listed in the information about 'libapache2-mod-qos', but I thought it would be a good idea to check with the community to see if I might be missing something somewhat obvious in my configuration before enquiring with him, or compiling the software myself (which is fairly simple for mod_qos). With that, might you have any thoughts on what could be causing this issue? Again, I think it fairly likely that the problem is a missing dependency, but if so, what is that? Thank you for reading my message, and for any insight you may be able to provide! Michela | Hello, A bug report is opened in the Debian Bug Tracking System on this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039898 Other similar reports are found in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-qos/+bug/1956056 The ubuntu report is closed with the solution: "invalid, because involved packages were installed from PPAs" Sorry to bother you asking about that, but have you installed packages that are not from Debian repositories ? You can check with: Code: Select allapt list '?narrow(?installed, ?not(?origin(Debian)))' What are the installed packages related to pcr3 source code [1] ? you can check with the command: Code: Select allapt list "libpcre*" apt list pcregrep --- [1] https://tracker.debian.org/pkg/pcre3 |
I've tried several days of manual 'apt update' along with 'apt upgrade' with no results. Code: Select all$ apt list --upgradable Reading package list… Ready curl/oldstable-proposed-updates 7.74.0-1.3+deb11u12 amd64 [upgradable from: 7.74.0-1.3+deb11u11] libcurl3-gnutls/oldstable-proposed-updates 7.74.0-1.3+deb11u12 amd64 [upgradable from: 7.74.0-1.3+deb11u11] libcurl4/oldstable-proposed-updates 7.74.0-1.3+deb11u12 amd64 [upgradable from: 7.74.0-1.3+deb11u11] These three packages remain in the list no matter how I try to 'apt update' and 'apt upgrade' them. Other packages keep updating|upgrading procedure on a regular basis. Is there a reason for such system behaiviour and should I start to worry? How to force their upgrade? -- Moderator EDIT (Aki) Thu May 2 08:06:59 CEST 2024 : subject modified from "Debian 11 Bullseye doesn't uprade packages" to "Debian 11 Bullseye doesn't upgrade packages". | Hello, What is the output of the following command ? Code: Select allapt policy curl |
os on /dev/sda: Debian 12 kde, bios system, grub installed on sda os on /dev/sdb: Pureos 10 kde encrypted, bios system, grub installed on sdb I want to add Pureos to the grub menu of Debian on /dev/sda. In /etc/default/grub I have the os-probler line: Code: Select all# If your computer has multiple operating systems installed, then you # probably want to run os-prober. However, if your computer is a host # for guest OSes installed via LVM or raw disk devices, running # os-prober can cause damage to those guest OSes as it mounts # filesystems to look for things. GRUB_DISABLE_OS_PROBER=false When I run the command sudo update-grub I get: Code: Select allGenerating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-6.7.12-amd64 Found initrd image: /boot/initrd.img-6.7.12-amd64 Found linux image: /boot/vmlinuz-6.6.15-amd64 Found initrd image: /boot/initrd.img-6.6.15-amd64 Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Adding boot menu entry for UEFI Firmware Settings ... done os-prober is executed but Pureos is not added to the grub menu. Am I doing something wrong? | What is the output (as root or sudo) of Code: Select all# os-prober from the command line interface? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.