prompt stringlengths 1 63.6k | completion stringlengths 1 53.1k |
|---|---|
I am installing Debian on an unattended appliance,and am using the unattended-upgrades and apt-listchanges packages to ensure the system keeps up with security updates. It is a headless installation of Debian, with a minimal package footprint (for a Raspberry Pi). The unattended-upgrades service wants to be able to send e-mail updates, and I want to configure it to be able to send that mail to my external e-mail address (google). From this page it seems I need to enable an MTA, and I chose the default exim4 and followed the instructions on that page. I also updated /etc/email-addresses to specify my external e-mail address for root user. I tried using both sendmail and mail on the command line to generate test e-mails to my google email address like here But it doesn't seem to be working. I don't see any errors in journalctl but I'm not getting any e-mails, even in spam folders. What's the best way to validate and diagnose my e-mail configuration? | Thanks, @steve_v for mentioning "dma", which I wasn't aware of. For such configurations, I have always used nullmailer, which is also really easy to configure. |
https://wiki.debian.org/sudo Both sudo su and su, open the root/home/folder, have the same configuration: ls -l /usr/bin/synaptic-pkexec -rwxr-xr-x 1 root root 43 Nov 16 2020 /usr/bin/synaptic-pkexec. From terminal with sudo su opens the command synaptic, where from su terminal bash: synaptic: command not found. Similar results are for other apps from su terminal, but not from sudo su. Is it important to install sudo in Debian system, and how easily is to be removed after installing it? My advice, do not try to remove sudo if you don't have a good backup!!!! Solution Linux OS is a powerful system which gives to user to modify the system a lot! The package sudo is a very useful tool for administrators, experienced users and general users, but for general inexperience users can be dangerous. The reason that can be dangerous, is that the inexperience user can become easily root with the command sudo su. An easy way is to deactivate the sudo su by accessing the file: Code: Select all/etc/pam.d/su, and comment out, "auth sufficient pam_rootok.so" with the symbol (#). Code: Select all# This allows root to su without passwords (normal operation) #auth sufficient pam_rootok.so Save and close the file. Now if you try to access root account with the command sudo su, when you type the user password it asks another password and this is the root password, which if you provide then you access root account. This is the reason that user password is different from root password. If you want more security but less flexibility, then you remove completely sudo. Code: Select allsu And then: Code: Select allapt purge sudo It doesn't remove all the files of sudo, but the sudo command is removed. Now the system is more secure without sudo but less flexible, because if you want for example to access from terminal the fstab file from Xfce and the mousepad, then you must know the correct command, which is in that case: Code: Select allpkexec mousepad /etc/fstab Linux is a powerful OS, you decide how secure you want to have it! | panpan wrote: 2024-06-03 15:59 Is it important to install sudo in Debian system, and how easily is to be removed after installing it? Sudo is not needed, and maybe easy to remove. We need to comprehend that not every possible combination is synonymous with any other random combination. Be opinionated, make definitive choices, and accept that those choices limit other incompatible choices. I use Xfce with polkit for users and doas for scripts. Sudo is long removed. On the command line, su, su -, sudo, even doas is never required. Code: Select all$ synaptic-pkexec From a fresh install, "su -" should be able to get you to a complete solution - after which it also is no longer required. With the right choices, removal will not Break the system. |
Hello, I have installed the linux generic kernel with NVidia drivers in Debian 12. I want to install the real-time kernel. I know it's not compatible with NVidia, but since I would like to have a setup that allows me to start without the NVidia GPU when selecting the real-time kernel option at boot. This should not be crazy, since in the actual configuration, I'm offloading only specific apps to the GPU using NVidia Prime. The main issue, now, is that I cannot install the real-time kernel because the installation fails at configuration with the error: Code: Select allError! The /var/lib/dkms/nvidia-current/525.147.05/6.1.0-17-rt-amd64/x86_64/dkms.conf for module nvidia-current includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. So, two questions here: 1. how can I skip the DKMS configuration of a module for certain kernels? 2. how can I instruct the kernel not to load the NVidia driver from GRUB? | You could try setting this environment variable to override the RT detection before installing the new RT kernel. It should allow the Nvidia modules to build for the RT kernel. Code: Select allexport IGNORE_PREEMPT_RT_PRESENCE=1 I haven't used it lately but it worked for me several years ago. I eventually decided the RT kernel had no advantage for audio production so now use a Liquorix kernel which has default full preemption configured. It is also now possible to set full preemption in default kernels with the kernel option preempt=full. The only real requirement for RT kernels is for CNC machines and similar processes. |
I've been trying to track down an issue which ultimately causes avahi-daemon to spam my syslog with messages similar these: Code: Select all2023-12-19T19:22:15.143458+01:00 ... avahi-daemon[458]: Registering new address record for 2a02:####:####:####:2f89:f9d2:504f:595d on wlan0.*. 2023-12-19T19:22:16.181261+01:00 ... avahi-daemon[458]: Withdrawing address record for 2a02:####:####:####:2f89:f9d2:504f:595d on wlan0. 2023-12-19T19:22:18.011506+01:00 ... avahi-daemon[458]: Registering new address record for 2a02:####:####:####:2f89:f9d2:504f:595d on wlan0.*. 2023-12-19T19:22:19.240632+01:00 ... avahi-daemon[458]: Withdrawing address record for 2a02:####:####:####:2f89:f9d2:504f:595d on wlan0. Some research suggests that faulty IPv6 Router Advertisements may be the cause of this, but I don't think so. The RAs contain zero values for the prefix lifetimes, but that's fine. Code: Select all$ rdisc6 -1 wlan0 Soliciting ff02::2 (ff02::2) on wlan0... Hop limit : 64 ( 0x40) Stateful address conf. : Yes Stateful other conf. : Yes Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 1800 (0x00000708) seconds Reachable time : 3600000 (0x0036ee80) milliseconds Retransmit time : unspecified (0x00000000) Recursive DNS server : 2a02:####:####:####:f2af:85ff:fe11:70d DNS server lifetime : 300 (0x0000012c) seconds Prefix : 2a02:####:####:####::/64 On-link : Yes Autonomous address conf.: Yes Valid time : 0 (0x00000000) seconds Pref. time : 0 (0x00000000) seconds Route : ::/0 Route preference : medium Route lifetime : 1800 (0x00000708) seconds Source link-layer address: ##:##:##:##:##:## from fe80::f2af:85ff:fe11:70d Along the way I noticed that the lifetimes reported by ip address are sometimes a second or so higher than the values sent in the router advertisement. If the values are non-zero, that may or may not serve some purpose, but in the case of zero-valued lifetimes, that seems to cause the preferred_lft to become 1, which revives the deprecated address, only to immediately expire again. What could be the cause of this? I can reproduce this on 2 different machines, with Debian 12 and Raspberry Pi OS, but I wasn't able to reproduce it on Arch. The main problem here is I don't know where to look to diagnose this further. Any suggestions? See also my related question on stack overflow. | Hello, bplu4t2f wrote: 2024-06-05 17:18 This turned out to be a (rather embarrassing) bug in NetworkManager. https://gitlab.freedesktop.org/NetworkM ... ssues/1464 Thank you for updating the discussion. According to the reference you posted above, there seems to be a patch available: Fix: IPv6 addresses' lifetimes are one second longer than they should be. Fixes #1464 You may try applying this patch to the network-manager package and rebuild it to verify if it fixes the issue. -- EDIT Wed Jun 12 22:09:25 CEST 2024: marked as "solved". |
Hello All, I have 2 different pc's running Debian 12 with kernel i686 Linux 6.1.0-18-686 One is GNOME, The other is MATE. (DE) Both have updated and installed to kernel 6.1.0-21 But will not load the new kernel after reboot. kernel 6.1.0-21 does not show up in GRUB. It just keeps booting into kernel 6.1.0-18. How can I make it use the newer kernel? These are my options for installed kernel's: Code: Select allii linux-image-6.1.0-18-686 6.1.76-1 i386 Linux 6.1 for older PCs (signed) ii linux-image-6.1.0-21-686 6.1.90-1 i386 Linux 6.1 for older PCs (signed) ii linux-image-686 Thank-you for any help in advance. | Hello, hawghaven wrote: 2024-06-03 07:34 kernel 6.1.0-21 does not show up in GRUB. It just keeps booting into kernel 6.1.0-18. How can I make it use the newer kernel? These are my options for installed kernel's: ii linux-image-6.1.0-18-686 6.1.76-1 i386 Linux 6.1 for older PCs (signed) ii linux-image-6.1.0-21-686 6.1.90-1 i386 Linux 6.1 for older PCs (signed) ii linux-image-686 What are the listed items in the "Advanced Options" from the grub's main menu ? What is the content of /etc/default/grub after boot ? What is the output of the following command ? Code: Select allscript log.txt su -l -c "update-grub" su -l -c "update-initramfs -k all" Hope this helps. |
I've initiated 'Package Management System' and almost at the same time started 'Synaptic' which resulted in broken '# apt update && apt upgrade' process. I could observe it from the shell. Code: Select alluser@mypc:~$ sudo apt update && sudo apt upgrade Reading packages list… Done E: Could not get lock /var/lib/apt/lists/lock. It is held by process 1521 (packagekitd) N: Be noted that lock file deletion won't solve the problem and could brake your system. E: Unable to lock /var/lib/apt/lists/ After which I've done Code: Select alluser@mypc:~$ sudo fuser /var/lib/apt/lists/lock Cannot stat file /proc/2080/fd/21: Permission denied Cannot stat file /proc/2080/fd/22: Permission denied Cannot stat file /proc/2080/fd/185: Permission denied Cannot stat file /proc/2080/fd/219: Permission denied Cannot stat file /proc/2080/fd/220: Permission denied Cannot stat file /proc/2080/fd/221: Permission denied Cannot stat file /proc/2080/fd/245: Permission denied Cannot stat file /proc/2080/fd/246: Permission denied Cannot stat file /proc/2080/fd/247: Permission denied Cannot stat file /proc/2080/fd/251: Permission denied Cannot stat file /proc/2080/fd/252: Permission denied Cannot stat file /proc/2080/fd/253: Permission denied /var/lib/apt/lists/lock: 1521 So I killed the process 1521 Code: Select alluser@mypc:~$ sudo lsof -w /var/lib/apt/lists/lock COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME packageki 1521 root 14uW REG 254,0 0 2883969 /var/lib/apt/lists/lock user@mypc:~$ sudo kill -9 1521 That seems have damaged Debian update/upgrade ability. What should be done to repair Debian so it upgradable / updatable again? | nikobit wrote: 2024-06-04 11:25Code: Select allN: Be noted that lock file deletion won't solve the problem and could brake your system. Is this what was actually shown or did you type it? The word should be "break", "brake" means something completely different and doesn't make sense in this context. As written above, you can't run 2 package managers at the same time, the first one always locks out any others to avoid conflicts. |
Hi all, I'm facing an issue with a mount point defined in /etc/fstab during the boot sequence. I have the following line in my /etc/fstab file : Code: Select all//192.168.1.60/movies /mnt/synology cifs vers=3.0,credentials=/root/.synocred 0 0 During the boot sequence I have the following error : Code: Select all[ 2.754120] CIFS: Attempting to mount \\192.168.1.60\movies [ 2.754150] CIFS: VFS: Error connecting to socket. Aborting operation. [ 2.754172] CIFS: VFS: cifs_mount failed w/return code = -101 Once I'm connected after the boot sequence if I run command Code: Select allmount -a the CIFS shared is correctly mounted. It seems that system try to do mount before having network access. How can I get around this problem ? Debian version : 12.5 Running environment : VM running on top of proxmox Thanks in advance. | MyGoul wrote: 2024-05-03 16:32...It seems that system try to do mount before having network access. How can I get around this problem ? Add _netdev to your mount options in fstab. That will tell the system to wait for the network before attempting to mount the share. Hope this helps - |
I am trying to clamav scan files 1 day old, basically an incremental scan. my testing command: Code: Select allfind /home/fooname/icons/ -name "*.*" -ctime -1 -type f | clamscan -r --log=/home/fooname/Documents/clamscan/$(date +%FT%T).log This should create a list of all files in folder icons, 1 day old, pipe that list to clamscan for a recursive scan of the icons folder and write a log. When I run this in a terminal, the scan starts at the top of /. Can anyone show me what I am doing wrong? Edit: When I run this in a terminal, the scan starts at the top of /home/fooname Thanks | Does clamscan take filenames on stdin? |
I am setting up iptables on a Raspberry Pi with Bookworm (Debian 12) I've never done this before. I am doing this to teach High School Computer Science students and for myself. There are a lot of tutorials online and I have read and tried to apply some of the tutorials. I've read : https://wiki.debian.org/iptables and notice it does not reference netfilter-persistent I reference this post viewtopic.php?t=158592 I installed iptables and I get the following: # systemctl status iptables Unit iptables.service could not be found. Do I need to install : netfilter-persistent along with iptables? ipset-persistent - boot-time loader for netfilter rules, ipset plugin iptables-persistent - boot-time loader for netfilter rules, iptables plugin netfilter-persistent - boot-time loader for netfilter configuration Or what do I need to install to implement iptables? along with iptables. Please post an example of a solid tutorial that works. | cwc wrote: 2024-06-07 14:08 I've read : https://wiki.debian.org/iptables and notice it does not reference netfilter-persistent This is a page about iptables, so it refers to iptables-persistent. However, iptables has been supplanted by nftables. Unless you have a very specific reason to use and learn iptables, your time would be better spent learning nftables syntax. Whether it's iptables or nftables, all you need is to load the rules, iptables-persistent is not necessary. I personally just add a line in /etc/network/interfaces (man 5 interfaces) Code: Select allpre-up /path/to/my/rules where rules is a chmod +x nftables or iptables script. This is basically what the iptables page on the wiki shows, and I still use this method with nftables. There is a nftables.service that comes with nftables and is an alternative solution, but no package provides iptables.service. Code: Select all$> apt-file search "nftables.service" nftables: /lib/systemd/system/nftables.service $> apt-file search "iptables.service" $> |
Hello everyone, Yesterday I installed debian 12 on my old macbook pro (2009) During the installation I received the message "Missing files are: b43-open/ucode16_mimo.fw e b43/ucode16_mimo.fw" Anyway, I continue with the installation and after that, I couldn't see the wifi toggle so I connected the pc with ethernet and I follow this guide to install broadcom firmware: https://wiki.debian.org/wl After the installation of the drivers the wifi toggle appeared but the problem is that wifi can't find networks (where I live there are at least 10 wifi-networks) If it's useful the command iwconfig returns: Code: Select alllo no wireless extensions. enp3s0 no wireless extensions. wlp2s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=23 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Now I don't know what to do. Maybe I installed the wrong drivers? Can anyone help? I'm a very beginner, so be patient... Sorry for the english. Thank you in advance. | I have not had a Broadcom in many years, but my money would be on this: Code: Select all$ sudo apt install firmware-b43-installer or (if you made a root account during install): Code: Select all$ su - Enter root password Then finally: Code: Select all# apt install firmware-b43-installer And reboot. |
After a recent update all the other distros (including Windows) in my multiboot setup are now missing in the GRUB menu. Only Debian 12 is present in the GRUB menu. I think I made a mistake checking both selection boxes during the update. I selected /sda and /sda7 (where Debian 12 resides). Is there a way to safely recover the original GRUB menu? | I have found the fix... First, I found out I needed to edit the grub config file: Code: Select allsudo nano /etc/default/grub ...Inside the file, I enabled the line that says... Code: Select allGRUB_DISABLE_OS_PROBER=false ...That's it. And then I updated the grub: Code: Select allsudo update-grub Upon reboot of the machine, all the missing boot paritions are back. |
Hello everyone! I've been having a tricky situation with my vsftpd install since I followed a guide on installing an SSL certificate to have a friend connect to my file-share server. I used Openssl to create an ssl key with RSA encryption, made a public key off of that key, and then configured vsftpd to use both the private and public keys as well as enabling outright the use of SSL. The main problem I'm experiencing is the reverse of what most people talk about online: I cannot connect locally to the server using it's local IP address but I can connect to it via the external IP address. I'm also trying to use SFTP to connect properly as well. I have home internet, so getting a static line just isn't an option, and I'd hate to have to reconfigure my local clients every time. If I can get some assistance, that'd be greatly appreciated, just let me know what you'd need to see and I'll get it to ya. Thank you! | Hello everyone, Nevermind, big dummy on my part, I kept trying to use the public port instead of the private port, which just uses the default SSH port of 22 to connect to it. Sorry for creating a new thread, this can be locked now. Thank you! |
Hi installed debian bookworm (Debian 6.1.76-1) on a HP Elitebook x360 1040 G5. I cannot get my sound drivers working. I installed realtek drivers, did reboot, but still, the audio isnt working: sudo dmesg | grep snd: Code: Select all[ 5.047213] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 5.047219] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SST driver [ 5.265523] snd_soc_skl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 5.265527] snd_soc_skl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SST driver [ 5.265532] snd_soc_skl 0000:00:1f.3: enabling device (0000 -> 0002) [ 5.266162] snd_soc_skl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 5.471260] snd_soc_skl 0000:00:1f.3: firmware: failed to load 9d71-INTEL-KBL-2-tplg.bin (-2) [ 5.471487] snd_soc_skl 0000:00:1f.3: firmware: failed to load 9d71-INTEL-KBL-2-tplg.bin (-2) [ 5.471546] snd_soc_skl 0000:00:1f.3: Direct firmware load for 9d71-INTEL-KBL-2-tplg.bin failed with error -2 [ 5.471567] snd_soc_skl 0000:00:1f.3: tplg fw 9d71-INTEL-KBL-2-tplg.bin load failed with -2, trying alternative tplg name skl_hda_dsp_generic-tplg.bin [ 5.472000] snd_soc_skl 0000:00:1f.3: firmware: direct-loading firmware skl_hda_dsp_generic-tplg.bin [ 5.475040] snd_soc_skl 0000:00:1f.3: firmware: direct-loading firmware intel/dsp_fw_kbl.bin [ 5.986275] snd_soc_skl 0000:00:1f.3: skl_cldma_wait_interruptible: Wait timeout [ 5.988087] snd_soc_skl 0000:00:1f.3: Failed to set Run bit=2 enable=0 [ 5.988800] snd_soc_skl 0000:00:1f.3: Transfer firmware failed-5 [ 5.990768] snd_soc_skl 0000:00:1f.3: Failed to set Run bit=2 enable=0 [ 5.992618] snd_soc_skl 0000:00:1f.3: Load base fw failed : -5 [ 5.993596] snd_soc_skl 0000:00:1f.3: Failed to boot first fw: -5 [ 5.994436] snd_soc_skl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -5 aplay -l: Code: Select allaplay: device_list:274: no soundcards found... do you have any idea what i can do? | Help us to help you by posting hardware and system specs. Install inxi and post: Code: Select allinxi -ACSaz Also, maybe this will help - https://forum.openmandriva.org/t/fix-fo ... -work/4460 |
Hello all. First post time. Apologies in advance if this question seems a bit vague, but I'm not sure where to look to evidence of this issue. This is initially a request to see if anyone's seeing anything similar! Circumstances are: - We run workloads in AWS, historically on a weird mix of Amazon Linux, CentOS and Ubuntu. - I want to gradually migrate to using Debian, using official Debian AMIs, as we retire servers and introduce new services. - I have a few servers now running Debian 12 x86_64, I thought with no issues - but ... - A service I've just migrated from an Ubuntu 16.04 box, a Python app, is having occasional issues which it claims are due to DNS lookup failures, when trying to establish a new PostgreSQL connection to the endpoint of an AWS RDS database. - The app is Indico (see https://getindico.io/), so not one we write ourselves. It uses psycopg2 as the database client library. - The errors look like this: Code: Select all(psycopg2.OperationalError) could not translate host name "indico.cluster-example.eu-west-2.rds.amazonaws.com" to address: Name or service not known - By and large, the app is working fine, so it is clearly usually able to talk to the database, but we get a few tens of these errors every day in the app's log files. - We never saw this with the old Indico software on the Ubuntu server. - This prompted me to check our test Debian 12 box, also running a test version of this Indico service - and lo and behold, it has also had occurrences of this DNS error - but hardly any, since the test service isn't really used. - All our servers use the AWS VPC DNS resolver. - As far as I can tell, we've not seen any DNS failures of any kind on any of our other servers, many of which talk to databases, only these two new Debian 12 boxes. I have been discussing this over on the Indico forums, and the feeling is that it is not likely to be some new unknown issue in Indico or psycopg2 - I agree with this. So, currently, I have a DNS service (AWS's VPC DNS resolver) which I expect to be totally reliable, being used to look up a name (the AWS RDS endpoint) which I would expect to always return an answer, by an OS (Debian 12) and a DB client library (psycopg2) which I again would be amazed at if they had unknown new bugs in the area of DNS lookups. My Debian 12 servers have /etc/resolv.conf as a link to /run/systemd/resolve/resolv.conf, as expected, and it contains something like: Code: Select all# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 10.211.32.2 search . This looks normal. The boxes use DHCP, as per usual in AWS. Can anyone suggest anything I can do to attempt to diagnose this? Is there any more information I could provide or check, which might help? Many thanks if you read this far! Andy | Hello, According to your previous message, your Debian 12 installation uses systemd-resolved as DNS client (network name resolution to local applications). I don't know if it is the default configuration used by AWS Debian images, but, as far I know, this is not the default Debian 12 configuration. A quick search lead me to a previous thread in the forum: [Solved] Random name resolution failure with systemd-resolved (EC2 server) and to systemd issues: systemd issues #29069 - Intermittent DNS name resolution failure, likely IPv6-related Hope this helps. |
I'm posting this here becasue the solution is something someone else may find useful. My e-lab is in my basement and my dev workstation is in my main-floor office. The e-lab has a Debian server that hosts USB connected microcontroller dev boards. STmicro provides a TCP/USB bridge application called stlink-server. Unfortunately the thing is hardwired to only listen on the loopback address so anything connecting to it must be running on the local host. I remember there being a netcat swiff-army-knife type application that could bridge and forward ip traffic between different ip/port cominations, but it's been years and I don't remember the application name or the configuration. NOTE! this is user-space forwarding. I'm not interested in any of the iptables/netdev stuff that does forwarding from kernel space. Does anybody understand what I'm getting at and remember the name of the application I'm thinking of? | Code: Select allsocat TCP-LISTEN:1234,bind=10.10.1.5,fork,reuseaddr TCP:localhost:5555 |
On debian system (sid) I cannot access virsh commands without root access. In contrast when typing Code: Select allsudo virsh list --all I got the correct list of machines. I already added the user to the libvirt group, but nothing changes. | Code: Select all$ virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # list --all Id Name State ----------------------------------------- single line; Code: Select all:~$ virsh -c qemu:///system list --all |
This past Friday, little Miss Bookworm, had a tantrum and tossed all her timing toys out the pram. She was put into time-out for a while until I read enough to figure it out. Luckily this involved only reading and no rithmatic. It did afford me the opportunity to remove Mint from my drive and rely only on Debian, which frankly, after only a week, I am more comfortable with. I did add the directory var/log/ntpsec as recommended per the /etc/ntpsec/ntp.conf file, though I have not seen any logs in there. I have the ntp.conf place holder in /etc. If you have any suggestions, tips, or additional reading material, I am open to it. Thanks for look at this for me. ---- I decided to use the time.nist.gov time server, for no particular reason other than I know it will ( I hope ) always be there. Code: Select allntpq -p remote refid st t when poll reach delay offset jitter ======================================================================================================= 0.pool.time.nist.gov .DNS. 16 u - 68m 0 0.0000 0.0000 0.0000 I am not certain why I get the insufficient permissions on the file, other than I was not at root when the below command was issued. Code: Select allsystemctl status ntp ● ntpsec.service - Network Time Service Loaded: loaded (/lib/systemd/system/ntpsec.service; enabled; preset: enabled) Active: active (running) since Mon 2024-04-08 09:35:56 EDT; 1h 1min ago Docs: man:ntpd(8) Process: 1050 ExecStart=/usr/libexec/ntpsec/ntp-systemd-wrapper (code=exited, status=0/SUCCESS) Main PID: 1057 (ntpd) Tasks: 1 (limit: 18794) Memory: 12.4M CPU: 203ms CGroup: /system.slice/ntpsec.service └─1057 /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec Warning: some journal files were not opened due to insufficient permissions. The system is syncing, but no idea why NTP service is N/A. Code: Select alltimedatectl status Local time: Mon 2024-04-08 10:38:22 EDT Universal time: Mon 2024-04-08 14:38:22 UTC RTC time: Mon 2024-04-08 14:38:22 Time zone: US/Eastern (EDT, -0400) System clock synchronized: yes NTP service: n/a RTC in local TZ: no The below was from the root user. I believe the bottom two lines are from the nist main server not being known, the servers it points to are then resolved? I can edit ntp.conf and change to those particular servers, not certain I want to do that though. Code: Select allsystemctl status ntp ● ntpsec.service - Network Time Service Loaded: loaded (/lib/systemd/system/ntpsec.service; enabled; preset: enabled) Active: active (running) since Mon 2024-04-08 09:35:56 EDT; 1h 5min ago Docs: man:ntpd(8) Process: 1050 ExecStart=/usr/libexec/ntpsec/ntp-systemd-wrapper (code=exited, status=0/SUCCESS) Main PID: 1057 (ntpd) Tasks: 1 (limit: 18794) Memory: 12.4M CPU: 212ms CGroup: /system.slice/ntpsec.service └─1057 /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec Apr 08 09:35:57 lou ntpd[1057]: DNS: dns_check: processing 0.pool.time.nist.gov, 1, 20921 Apr 08 09:35:57 lou ntpd[1057]: DNS: dns_check: DNS error: -2, Name or service not known Apr 08 09:35:57 lou ntpd[1057]: DNS: dns_take_status: 0.pool.time.nist.gov=>error, 12 Apr 08 09:36:03 lou ntpd[1057]: IO: Listen normally on 4 enp0s31f6 206.248.211.38:123 Apr 08 09:36:03 lou ntpd[1057]: IO: Listen normally on 5 enp0s31f6 [fe80::aaa1:59ff:feac:557c%2]:123 Apr 08 09:36:03 lou ntpd[1057]: IO: new interface(s) found: waking up resolver Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_probe: 0.pool.time.nist.gov, cast_flags:1, flags:20921 Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_check: processing 0.pool.time.nist.gov, 1, 20921 Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_check: DNS error: -2, Name or service not known Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_take_status: 0.pool.time.nist.gov=>error, 12 | Hello, According to your logs: Augie77 wrote: 2024-04-08 15:12 Code: Select allApr 08 09:35:57 lou ntpd[1057]: DNS: dns_check: processing 0.pool.time.nist.gov, 1, 20921 Apr 08 09:35:57 lou ntpd[1057]: DNS: dns_check: DNS error: -2, Name or service not known Apr 08 09:35:57 lou ntpd[1057]: DNS: dns_take_status: 0.pool.time.nist.gov=>error, 12 [..] Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_probe: 0.pool.time.nist.gov, cast_flags:1, flags:20921 Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_check: processing 0.pool.time.nist.gov, 1, 20921 Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_check: DNS error: -2, Name or service not known Apr 08 09:36:03 lou ntpd[1057]: DNS: dns_take_status: 0.pool.time.nist.gov=>error, 12 The name 0.pool.time.nist.gov of the ntp server is unknown. For example: Code: Select all$ ntpdig 0.pool.time.nist.gov ntpdig: lookup of 0.pool.time.nist.gov failed, errno -2 = Name or service not known ntpdig: no eligible servers while: Code: Select all$ ntpdig time.nist.gov 2024-04-08 20:19:02.552135 (+0200) -0.015481 +/- 0.105696 time.nist.gov 132.163.96.4 s1 no-leap or: Code: Select all$ ntpdig 0.debian.pool.ntp.org 2024-04-08 20:20:35.409808 (+0200) +0.024334 +/- 0.063763 0.debian.pool.ntp.org 85.199.214.99 s1 no-leap |
Hi there, I would like to host a Debian mail server, where additionally an OpenVPN server instance is listening on UDP Port 53. The server itself should use DoH if possible, else DoT. I can not get it to work however. I tried using resolved, but without avail. My ideal solution would be to just be a DoH/DoT client and not bother setting up an own DNS server, so I would not interfere with Port 53. Can someone point me in the right direction? | You could make the OpenVPN server listen on your WAN IP (which is what you need), and your DNS resolver could listen on localhost. This way both OpenVPN and DNS resolver can "share" UDP port 53. Note however that if you want to host a mail server, it is (generally) recommended not to host a VPN server there, as some systems may (incorrectly) lower the reputation of the mail server because it also "offers" VPN. For VPN (OpenVPN, Wireguard) I'd recommend the cheapest VPS you can find. It will be enough, and you can keep it separated from other systems. |
running update-grub suddenly started failing to detect other LVs: ( all LVs used to get activated automatically on boot ) Code: Select alldeb10 ~ # update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.1.0-20-amd64 Found initrd image: /boot/initrd.img-6.1.0-20-amd64 Found linux image: /boot/vmlinuz-6.1.0-18-amd64 Found initrd image: /boot/initrd.img-6.1.0-18-amd64 Found linux image: /boot/vmlinuz-6.1.0-17-amd64 Found initrd image: /boot/initrd.img-6.1.0-17-amd64 Found linux image: /boot/vmlinuz-6.1.0-10-amd64 Found initrd image: /boot/initrd.img-6.1.0-10-amd64 Found linux image: /boot/vmlinuz-6.1.0-9-amd64 Found initrd image: /boot/initrd.img-6.1.0-9-amd64 Adding boot menu entry for UEFI Firmware Settings ... Found memdisk: /memdisk Imagepath /boot/images not found 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. lsblk: /dev/mapper/spvg1-root: not a block device lsblk: /dev/mapper/spvg1-var: not a block device lsblk: /dev/mapper/vg1-root: not a block device lsblk: /dev/mapper/vg1-varlog: not a block device Found Windows Boot Manager on /dev/nvme1n1p1@/EFI/Microsoft/Boot/bootmgfw.efi done deb10 ~ # uname -a Linux deb10 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux deb10 ~ # LVM: Code: Select alldeb10 ~ # vgs VG #PV #LV #SN Attr VSize VFree linvg 1 3 0 wz--n- 171.82g <16.20g spvg1 1 2 0 wz--n- <100.47g <51.47g vg1 1 2 0 wz--n- 666.63g 259.91g deb10 ~ # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert linlog linvg -wi-ao---- 4.00g linroot linvg -wi-ao---- 139.62g rootsrc linvg -wi-a----- 12.00g root spvg1 -wi------- 45.00g var spvg1 -wi------- 4.00g root vg1 -wi------- 403.00g varlog vg1 -wi------- 3.72g LSBLK: Code: Select alldeb10 ~ # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme1n1 259:0 0 1.8T 0 disk ├─nvme1n1p1 259:1 0 500M 0 part /boot/efi ├─nvme1n1p2 259:2 0 892.8G 0 part ├─nvme1n1p3 259:3 0 863M 0 part ├─nvme1n1p4 259:4 0 787G 0 part ├─nvme1n1p5 259:5 0 10G 0 part /boot └─nvme1n1p6 259:6 0 171.8G 0 part ├─linvg-linroot 254:2 0 139.6G 0 lvm / ├─linvg-linlog 254:5 0 4G 0 lvm /var/log └─linvg-rootsrc 254:6 0 12G 0 lvm nvme0n1 259:7 0 1.8T 0 disk ├─nvme0n1p1 259:8 0 10G 0 part ├─nvme0n1p2 259:9 0 666.6G 0 part ├─nvme0n1p3 259:10 0 512M 0 part ├─nvme0n1p4 259:11 0 100.5G 0 part ├─nvme0n1p5 259:12 0 299M 0 part └─nvme0n1p6 259:13 0 16M 0 part a workaround is a manual activation before running update-grub ( this was not required before ) Code: Select alldeb10 ~ # vgchange -ay 2 logical volume(s) in volume group "spvg1" now active 2 logical volume(s) in volume group "vg1" now active 3 logical volume(s) in volume group "linvg" now active troubleshooting done: i have downgraded the recently updated util-linux package back to: Code: Select allutil-linux-extra_2.38.1-5+b1_amd64.deb util-linux-locales_2.38.1-5_all.deb util-linux_2.38.1-5+b1_amd64.deb recreated all the initramfs ( should recreate just one ) no improvement after rebooting only the main/booted linvg LVs are active, update-grub fails there is no recent changes applied that I'm aware of that could influence the way update-grub "detects" the filesystems, or LVM scan/activation during boot. Other than util-linux, gcc, and and 6.1.0-20-amd64 kernel update applied recently... booting the older kernels results in the same problem ( but, i've recreated all initramfs's - by mistake - making the comparison between kernels and the boot process invalid ) i do not remember seeing update-grub/lsblk failing like this before before thanks all! | more troubleshooting: - analyzed lvm syslog from past ~4 weeks - lvm2-monitor and lvm2-lvmpolld starting as expected - no errors related to block storage/filesystems, etc... - nothing custom in /etc/lvm2 - nothing unusual found in /etc/default/grub, no customizations to /etc/initramfs-tools on this system - booting off a deb12 custom livecd activates all VGs/LVs as expected: automatically during boot - no unwanted ESC/special chars in the configs i have done some testing with multiple custom builds of 6.7 kernel for bcachefs ( but not within last 1 month ) then a few days ago i saw this ( Mr Torvalds about 6.9 kernel ): "Ok, so this rc3 looks a bit different than the usual ones, because there's a large series to bcachefs to do filesystem repair after corruption. Not normally something we'd see in an rc kernel, but hey, if you had a corrupted bcachefs filesystem you'd probably want this, and if you thought bcachefs was stable already, I have a bridge to sell you. Special deal only for you, real cheap. i am thinking now that lvm2 got somehow corrupted preventing it from proper activation during boot but then i would expect it to fail as well when 'vgchange -ay' is executed - plus i do not have any bcache fs that is expected to be mounted - there is one but inactive, for testing only still looking... |
So I installed the new kernel patch the other day and got a bucket full of errors about firmware drivers. I installed the non-free-linux firmware packages, but the firmware errors stayed. I rebooted and now my wifi was dead. So I timeshifted back and put that kernel patch and it's related packages on hold. Is this a widespread issue or just affecting me? Code: Select all>>>nala list --upgradable linux-compiler-gcc-12-x86 6.1.76-1 [Debian/bookworm main] ├── is installed and upgradable to 6.1.85-1 └── Compiler for Linux on x86 (meta-package) linux-image-amd64 6.1.76-1 [Debian/bookworm main] ├── is installed and upgradable to 6.1.85-1 └── Linux for 64-bit PCs (meta-package) linux-kbuild-6.1 6.1.76-1 [Debian/bookworm main] ├── is installed and upgradable to 6.1.85-1 └── Kbuild infrastructure for Linux 6.1 linux-libc-dev 6.1.76-1 [Debian/bookworm main] ├── is installed and upgradable to 6.1.85-1 └── Linux support headers for userspace development | Have you tried a newer kernel? I saw one post stating the driver for this device was added in kernel 6.2 . Try a kernel from backports. |
I'm reasonably certain that under bullseye (v11), I could sudo ifdown <tabComplete> / sudo ifup <tabComplete>. On bookworm (v12): sudo ifdown <tabComplete> does not "work" sudo -i ; ifdown <tabComplete> does "work" su -i ; ifdown <tabComplete> does "work" Does anyone know where I should log this bug? sudo or ifupdown? | Hello, Is the bash-completion package installed ? Code: Select allapt list bash-completion |
It's the most random thing.,, Let's say I shut down my system or it goes to sleep @ 9:45pm If I were to boot my system the following morning and log in, if I check the time, it will say 9:45pm. It both is and isn't persistent: It is persistent in that it happens every time I boot It's not persistent in that it resolves within about 3-10 seconds after I've logged in Some resulting issues: I use KDE and run a systemd service+timer that changes to a light/dark theme when the computer (re)boots and it is 'failing' on its first try due to the time being off. Syncthing has a systemd service as well... if I create/edit files on my tablet in the morning, and then it is set to auto-sync to my desktop when it boots, the metadata is applied retroactively and suggests the file was actually updated/edited the prior evening It's likely doing unforeseen damage to my journal logs and the occasional systemd service Curious if anyone has any theories/solutions? | Hello, What is your computer ? What is your Debian installed version ? m4c-attack wrote: 2024-04-14 01:39 Let's say I shut down my system or it goes to sleep @ 9:45pm [..] If I were to boot my system the following morning and log in, if I check the time, it will say 9:45pm. [..] It's not persistent in that it resolves within about 3-10 seconds after I've logged in Desktops and notebooks usually have an internal "hardware" real time clock (RTC) that is powered by an internal battery. This is your computer's reference real-time clock. It ticks even if the computer is off (as long as it is powered by its battery). The operating system (Debian) initialises the so-called "system clock" (software clock maintained by the kernel, see [1]) from the RTC at boot time. You can check system logs about RTC with the following command: Code: Select allsudo journalctl -b --grep rtc The operating system can then update the system time (within certain limits) from another networked computer using "network time servers". Perhaps, there something wrong with the RTC in your computer. -- [1] https://manpages.debian.org/bookworm/nvram-wakeup/rtc.8.en.html |
I've noticed on my system that some programs are not translating fully to norwegian. One of the most obvious programs suffering from this is timeshift. It happens sometimes in the terminal also, in the terminal I have a rudimentary fix for it in bashrc Code: Select all#Force english fallback export LANGUAGE="nb_NO:nb:no_NO:no:en" I also edited /etc/environment to force graphical programs to do the same. Code: Select allLANGUAGE="nb_NO:nb:no_NO:no:en" Forcing english is an acceptable fix for the time being, but it is somewhat bugging me that the system can't get the language right. Is this because the program has not been translated or because of some settings issue with locales. How much work would it take to make the translation if no one has done it? Like how big a list of words would need to be entered, I mean I could give it a shot since my native language is norwegian and english as a second language would make it pretty easy for me. But that is making the assumption that it is a translation problem and not a settings problem with debian. | Hello, sinterva wrote: 2024-04-22 15:38 After looking around a bit on github I found that the file included with timeshift did indeed have an only partial translation. [..] So I'm not sure if this is the right place to translate it or not, but if not I will just have to copy/paste my translations to where they need to be later You can see here to contribute: Debian » Developers-reference 13.6 documentation » 8. Internationalization and Translations¶ Hope this helps. |
A few days ago I was using the laptop without a battery and Wi-Fi was working fine. I don't know how I pushed or pulled the power cord and the laptop seemed to have lost power for a fraction of a second. In less than a second the power light was on again. However the screen turned black and wouldn't turn on again. I typed some keys and made some mouse clicks but it wouldn't recover. After about 5 minutes I think I remember issuing a controlled reboot with SysKey + REISUB which worked well because the laptop finally shut off. When the laptop started again everything was fine except for the Wi-Fi, which wouldn't work. The laptop runs Debian 12 on an encrypted filesystem. Code: Select alldj@Dell:~$ uname -a Linux Dell 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux dj@Dell:~$ dj@Dell:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm dj@Dell:~$ dj@Dell:~$ ip addr 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: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether e4:b9:7a:35:fa:0e brd ff:ff:ff:ff:ff:ff inet 192.168.18.33/24 brd 192.168.18.255 scope global dynamic noprefixroute enp0s31f6 valid_lft 2640sec preferred_lft 2640sec inet6 fe80::e6b9:7aff:fe35:fa0e/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 46:91:42:be:5c:dd brd ff:ff:ff:ff:ff:ff permaddr f0:d5:bf:e6:15:77 dj@Dell:~$ dj@Dell:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback dj@Dell:~$ dj@Dell:~$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 0a) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 0a) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0a) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31) 00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #2 (rev f1) 00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation CM238 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-LM (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1) 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) dj@Dell:~$ I tried reinstalling the drivers, reinserting the modules and reinstalling the kernel. Code: Select allroot@Dell:~# ip link set wlp2s0 up root@Dell:~# dmesg | grep 'intel\|wifi' [ 0.867454] intel_pstate: Intel P-state driver initializing [ 0.867939] intel_pstate: HWP enabled [ 1.360583] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002) [ 1.416942] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002) [ 13.126141] Btrfs loaded, crc32c=crc32c-intel, zoned=yes, fsverity=yes [ 13.206795] BTRFS info (device dm-0): using crc32c (crc32c-intel) checksum algorithm [ 14.113500] systemd[1]: Mounting snap-intellij\x2didea\x2dcommunity-475.mount - Mount unit for intellij-idea-community, revision 475... [ 14.114475] systemd[1]: Mounting snap-intellij\x2didea\x2dcommunity-478.mount - Mount unit for intellij-idea-community, revision 478... [ 14.426501] caller pmc_core_probe+0xb3/0x6a0 [intel_pmc_core] mapping multiple BARs [ 14.426518] intel-hid INT33D5:00: platform supports 5 button array [ 14.426529] intel_pmc_core INT33A1:00: initialized [ 15.288950] snd_hda_intel 0000:01:00.1: Disabling MSI [ 15.288958] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client [ 15.313633] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-8000C-36.ucode [ 15.314072] iwlwifi 0000:02:00.0: loaded firmware version 36.ca7b901d.0 8000C-36.ucode op_mode iwlmvm [ 15.445174] intel_rapl_common: Found RAPL domain package [ 15.445178] intel_rapl_common: Found RAPL domain dram [ 15.468191] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x201 [ 15.586489] iwlwifi 0000:02:00.0: base HW address: f0:d5:bf:e6:15:77, OTP minor version: 0x0 [ 15.667001] intel_rapl_common: Found RAPL domain package [ 15.667004] intel_rapl_common: Found RAPL domain core [ 15.667006] intel_rapl_common: Found RAPL domain dram [ 15.699465] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0 [ 16.279116] BTRFS info (device dm-1): using crc32c (crc32c-intel) checksum algorithm root@Dell:~# root@Dell:~# apt reinstall firmware-iwlwifi Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 9,336 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://ftp.cica.es/debian bookworm/non-free-firmware amd64 firmware-iwlwifi all 20230210-5 [9,336 kB] Fetched 9,336 kB in 0s (23.2 MB/s) (Reading database ... 352934 files and directories currently installed.) Preparing to unpack .../firmware-iwlwifi_20230210-5_all.deb ... Unpacking firmware-iwlwifi (20230210-5) over (20230210-5) ... Setting up firmware-iwlwifi (20230210-5) ... root@Dell:~# root@Dell:~# modprobe -rv iwlwifi modprobe: FATAL: Module iwlwifi is in use. root@Dell:~# lsmod | grep iwl iwlmvm 385024 0 mac80211 1175552 1 iwlmvm iwlwifi 360448 1 iwlmvm cfg80211 1142784 3 iwlmvm,iwlwifi,mac80211 rfkill 36864 7 iwlmvm,dell_laptop,dell_rbtn,cfg80211 root@Dell:~# modprobe -rv iwlmvm iwlwifi rmmod iwlmvm rmmod mac80211 rmmod iwlwifi root@Dell:~# modprobe -rv iwlmvm root@Dell:~# modprobe -rv iwlwifi root@Dell:~# modprobe iwlwifi root@Dell:~# root@Dell:~# apt reinstall linux-image-6.1.0-17-amd64 Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/68.7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 352934 files and directories currently installed.) Preparing to unpack .../linux-image-6.1.0-17-amd64_6.1.69-1_amd64.deb ... Unpacking linux-image-6.1.0-17-amd64 (6.1.69-1) over (6.1.69-1) ... Setting up linux-image-6.1.0-17-amd64 (6.1.69-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-17-amd64. dkms: autoinstall for kernel: 6.1.0-17-amd64. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.1.0-17-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-17-amd64 Found initrd image: /boot/initrd.img-6.1.0-17-amd64 Found linux image: /boot/vmlinuz-6.1.0-13-amd64 Found initrd image: /boot/initrd.img-6.1.0-13-amd64 Found linux image: /boot/vmlinuz-5.10.0-18-amd64 Found initrd image: /boot/initrd.img-5.10.0-18-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. done root@Dell:~# The laptop is a Dell Precision 7520 and it doesn't have any hardware wifi kill switch. I've rebooted the laptop and still not working. No idea what I am doing to be honest. Any help will be appreciated. | Have you checked with a live image to rule out any hardware problems? (don't use a live image with kernel 6.1.0-15, there is a known WIFI issue with this kernel version). |
Hello, i managed to use the Yubico Key to login and it worked well, but i have one issue which i want to solve. I want to display a message after typing the password to insert the key. I have tried to add in /etc/pam.d/login a line with pam_echo.so : Code: Select all@include common.auth auth required pam_u2f.so interactive [prompt=Insert Security KEY and press ENTER] As this works very well in the /etc/pam.d/sudo file it seems to be ignored in the /etc/pam.d/login. Thanks a lot for any help | Thanks for sharing the solution. |
Hi everyone, during boot i get a couple of lines with "blacklist: Problem blacklisting hash (-13)" . As far as i found out it this are are informational warnings, and the boot process continues without any errors. Also everything seems to be working as it should, but in my view these messages have a good reason as all warnings or errors in the Debian world. So hopefully someone knows a solution - i simply would sleep better if the system boots without any errors So, what do i have: hostnamectl Static hostname: P14s Icon name: computer-laptop Chassis: laptop Machine ID: 3e02be7346464877bfb44066d0f0ebf1 Boot ID: 1a0eb5281ec54e65b47bf8a5357eb0b8 Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-17-amd64 Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad P14s Gen 3 Firmware Version: R23ET70W (1.40 ) gnome-shell --version says: GNOME Shell 43.9 Thank you all in advance for any help | Here's another bug report which may make it a bit clearer - https://lore.kernel.org/lkml/1bb01e6c-3 ... enovo.com/ It's not an actual error message, only informational and is harmless so can be ignored. You could try a newer kernel from bookworm-backports as it mentions code to suppress it was introduced in kernel 6.3, but duplicate hashes in the firmware may take a little more time to be removed. I have never seen those messages on my systems. |
Just installed Debian 12.0.0. Upgrade from 11.2 didn't work, so installed clean from Bookworm DVD. sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target DOES NOT prevent screen from going to black even though sudo systemctl status sleep.target suspend.target hibernate.target hybrid-sleep.target DOES show that they are all masked. This worked perfectly on Debian 11.2 on this machine, and is still working fine on my other Debian 11.2 server. Creating /etc/systemd/sleep.conf.d/nosuspend.conf AS: [Sleep] AllowSuspend=no AllowHibernation=no AllowSuspendThenHibernate=no AllowHybridSleep=no ALSO HAS NO EFFECT, even after reboot. This is running on a Dell XPS 8930 with an i7-9700 CPU @ 3.00 GHz, 32 GB RAM, a 1 TB SSD, and two 4 TB HDD's. Any advice? | @mdavidjohnson : can you please update the thread ? |
This is a Debian 12.4 system installed to run mostly headless. Out of the box, it installed only networking.service. NetworkManager is not installed, and systemd-networkd is installed but disabled. My issue is that my pfSense firewall's DHCP server (a different system) provides both IPv6 and IPv4 name server entries, but resolv.conf on the problematic Debian box contains only the IPv6 address, and no search entry. I've grepped through everything I can find in /lib/systemd, especially for dhclient, for anything referring to resolv.conf but came up empty handed. The immediate question is how to make dhclient (or whatever is updating resolv.conv) configure the IPv4 DNS server and the "search" entry for the local domain in resolv.conf. I'd also really like to understand exactly where resolv.conf is being created/updated on network startup. Solution: ifup/dhclient by themselves do not work well with dual stack systems. In my case DHCP (v4) correctly set up resolv.conf, but then DHCP6 was overwriting it. The solution is to install the resolvconf package, which understands dual-stack and can combine the results from both DHCP clients into one resolv.conf. | jhg wrote: 2024-02-10 00:14 I've grepped through everything I can find in /lib/systemd, especially for dhclient, for anything referring to resolv.conf but came up empty handed. Code: Select all$ dpkg -S resolv.conf manpages: /usr/share/man/man5/resolv.conf.5.gz systemd: /lib/systemd/resolv.conf if you mean the resolv.conf man page it looks like it is in the extra package manpages.deb and not included with package systemd.deb |
When I used the graphical installer to install Debian 12, I chose full-disk encryption and the BTRFS filesystem instead of ext4 for the root partition. After finishing the installation, there's this line in /etc/fstab: Code: Select all/dev/mapper/cake--vg-root / btrfs defaults,subvol=@rootfs 0 0 If I now want to enable BTRFS compression using the lzo algorithm, is it just a simple matter of adding "compress=lzo" to the /etc/fstab mount options as shown below, and rebooting? Code: Select all/dev/mapper/cake--vg-root / btrfs defaults,compress=lzo,subvol=@rootfs 0 0 Is there anything else I need to do before I reboot? I am concerned about corrupting the existing data, or being unable to boot my computer. I have backups, but restoring backups is just time-consuming. | Hello, According to this post, it should be possible to compress existing previously-uncompressed data: From the FAQ: ...consider remounting with -o compress, and either rewrite particular files in-place, or run btrfs fi defragment to recompress everything. This may take a while. The command (to defragment file data on a BTRFS mounted filesystem) should be (where /path/to/fs is the mount point of the mounted file system): Code: Select allbtrfs filesystem defragment -r -clzo /path/to/fs According to the manual page [1]: [..] defragment [options] <file>|<dir> [<file>|<dir>...] Defragment file data on a mounted filesystem. Requires kernel 2.6.33 and newer. If -r is passed, files in dir will be defragmented recursively (not descending to subvolumes, mount points and directory symlinks). The start position and the number of bytes to defragment can be specified by start and length using -s and -l options below. Extents bigger than value given by -t will be skipped, otherwise this value is used as a target extent size, but is only advisory and may not be reached if the free space is too fragmented. Use 0 to take the kernel default, which is 256KiB but may change in the future. You can also turn on compression in defragment operations. WARNING: Defragmenting with Linux kernel versions < 3.9 or ≥ 3.14-rc2 as well as with Linux stable kernel versions ≥ 3.10.31, ≥ 3.12.12 or ≥ 3.13.4 will break up the reflinks of COW data (for example files copied with cp --reflink, snapshots or de-duplicated data). This may cause considerable increase of space usage depending on the broken up reflinks. I formatted a partition on an external disk using the btrfs file system (labelled "btrfs-part"), mounted it and copied the /usr directory (from root partition) in it: Code: Select all# mount | grep btrfs /dev/sdb1 on /media/aki/btrfs-part type btrfs (rw,nosuid,nodev,relatime,space_cache=v2,subvolid=5,subvol=/,uhelper=udisks2) # cp -r /usr /media/aki/btrfs-part/ I installed the btrfs-compsize package to get compression statistics about the partition: Code: Select all# apt install btrfs-compsize # compsize /media/aki/btrfs-part/ Processed 48333 files, 31205 regular extents (31205 refs), 16078 inline. Type Perc Disk Usage Uncompressed Referenced TOTAL 100% 5.4G 5.4G 5.4G none 100% 5.4G 5.4G 5.4G Then, unmounted the btrfs partition and remounted it with the compress option: Code: Select all# mount -o compress,remount /media/aki/btrfs-part # mount | grep btrfs /dev/sdb1 on /media/aki/btrfs-part type btrfs (rw,nosuid,nodev,relatime,compress=zlib:3,space_cache=v2,subvolid=5,subvol=/,uhelper=udisks2) Then, I defragmented it: Code: Select all# btrfs filesystem defragment -r -clzo /media/aki/btrfs-part # compsize /media/aki/btrfs-part/ Processed 48333 files, 59938 regular extents (59938 refs), 23951 inline. Type Perc Disk Usage Uncompressed Referenced TOTAL 50% 2.7G 5.4G 5.4G none 100% 13M 13M 13M lzo 49% 2.7G 5.4G 5.4G As you can see, it compressed to 50% the contents of the btrfs file system. I haven't tested it on a root file system. Just to be safe, you could defragment it after booting from a Debian Live ISO. Hope this helps. --- [1] btrfs-filesystem |
I think I have encountered a kernel bug and would like help in investigating and (if appropriate) reporting it, as I have no experience in this area. Since upgrading my Debian 12 workstation PCs to the linux-image-6.1.0-17-amd64 kernel package I am getting an error when I try to copy a file between two locations on mounted samba shares. The copy fails with the message Killed and the destination file is created as a zero bytes file. If I boot the workstations into the previous linux-image-6.1.0-16-amd64 kernel the problem does not occur. Here is a transcript of what happens (directories d1 and d2 are both located on a mounted SAMBA share): Code: Select all$ ls -l d1/ total 4 -rwxrwx--- 1 andrew andrew 6 Jan 7 22:23 file1.txt* $ ls -l d2/ total 0 $ cp d1/file1.txt d2 Killed $ ls -l d2/ total 0 -rwxrwx--- 1 andrew andrew 0 Jan 8 07:13 file1.txt* An attempt to repeat the copy hangs. ps shows the cp command process is still running, and it cannot be killed, even with kill -9. If I then try to shut down the shutdown hangs for some time with a message something like Job session-2.scope/stop running, and then later in the shutdown it hangs again for a while with messages like systemd-shudown[1]: Waiting for process: 2156 (cp) The shares are mounted via fstab with a line similar to that below: Code: Select all//SOL/copying /mnt/SOL/copying cifs credentials=/root/.smbcredentials,uid=andrew,gid=andrew,file_mode=0770,dir_mode=0770,x-systemd.automount,x-systemd.mount-timeout=240,x-systemd.idle-timeout=3600 0 0 I have reproduced this with a number of workstations running up-to-date Debian stable and two samba servers - one running a fully up-to-date Debian stable installation, the other a raspberry pi running Raspbian 10 which has not been updated for some time. I would like to: Determine if this is a real bug or a problem with my setup Find out if this is a known bug or something I should report Learn how to investigate further if required Get some help and advice or how to report this, if necessary | Hello, This bug report (about a CIFS regression) fits with your previous post: Debian Bug report logs - #1060005 cifs-utils: Copy file with cp, hangs with a kernel NULL pointer dereference. Perhaps this is the commit involved in the regression: cifs: Fix flushing, invalidation and file size with copy_file_range() Hope this helps. |
hi, i have an Linux XXXXXXX 6.6.11 #2 SMP PREEMPT_DYNAMIC Tue Jan 16 13:15:06 CET 2024 x86_64 GNU/Linux working perfectly on KDE plasma. i have toshiba network printers/copiers, i could print perfectly in color or b&w in both printers, but only in one sided config. I don't know why when i select double sided print option in system board/print preview, it print one sided papers instead. those printers/copiers work perfectly with windows driver in r/v options. What could i do to correct this pb ? printers: TOSHIBA e-studio5516AC, driverless,cups-filters 1.28.17 TOSHIBA e-studio3518A, driverless,cups-filters 1.28.17 | solved by downloading toshiba drivers from: https://www.toshibatec.eu/support/drive ... rchString=[Printer-Model] for me [Printer-Model] = e-STUDIO3015A choose TOSHIBA e-STUDIO CUPS v7.114 (101KB) expand the files on desktop ( ~/desktop/CUPS) or directly in folders 1 - select "2-sided_default" subfolder 2 - copy/extract files with root rights in correct paths for eatch model color and B&W ( usr/lib/cups/filters and usr/share/cups/model) 3 - in KDE printer management clic on configure->Driver->select personalized driver->Toshiba->TOSHIBA MonoMFP or ColorMFP thats all folks |
I installed osk-sdl on my tablet with Debian 11 amd64, how can I enable osk-sdl? It is an onscreen keyboard for LUKS. Here there is a wiki but is not for Debian https://github.com/ShapeShifter499/osk-sdl_arch. | I set in /etc/crypptab: Code: Select allsda3_crypt UUID=... crypt_disk luks,initramfs,keyscript=/usr/share/initramfs-tools/scripts/osk-sdl-keyscript,discard Or you can add in /etc/default/grub: Code: Select allGRUB_CMDLINE_LINUX_DEFAULT="quiet osk-sdl-root=/dev/sda3 osk-sdl-root-name=/dev/mapper/sda3_crypt" After you need to run `update-initramfs -u` for crypttab and `update-grub` for grub. No need to add modules in my case. With backports kernel on D11 and with osk-sdl_0.66-5mobian1_amd64.deb version it works. Debian version has a bug. I needed to install some packages from testing to install Mobian version. |
Hello, since 3 days ago I can't update my laptop because I get errors while configuring the package linux-image-6.0.1-18-amd64, here's what I get when I try to update my system: Code: Select allConfigurando linux-image-6.1.0-18-amd64 (6.1.76-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-18-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.1.0-18-amd64....................(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-18-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error al procesar el paquete linux-image-6.1.0-18-amd64 (--configure): el subproceso instalado paquete linux-image-6.1.0-18-amd64 script post-installation devolvió el código de salida de error 1 Configurando linux-headers-6.1.0-18-amd64 (6.1.76-1) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-18-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.1.0-18-amd64....................(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-18-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-18-amd64.postinst line 11. dpkg: error al procesar el paquete linux-headers-6.1.0-18-amd64 (--configure): el subproceso instalado paquete linux-headers-6.1.0-18-amd64 script post-installation devolvió el código de salida de error 1 dpkg: problemas de dependencias impiden la configuración de linux-image-amd64: linux-image-amd64 depende de linux-image-6.1.0-18-amd64 (= 6.1.76-1); sin embargo: El paquete `linux-image-6.1.0-18-amd64' no está configurado todavía. dpkg: error al procesar el paquete linux-image-amd64 (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de linux-headers-amd64: linux-headers-amd64 depende de linux-headers-6.1.0-18-amd64 (= 6.1.76-1); sin embargo: El paquete `linux-headers-6.1.0-18-amd64' no está configurado todavía. dpkg: error al procesar el paquete linux-headers-amd64 (--configure): problemas de dependencias - se deja sin configurar Se encontraron errores al procesar: linux-image-6.1.0-18-amd64 linux-headers-6.1.0-18-amd64 linux-image-amd64 linux-headers-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) I have searched this issue and I found some posts with a similar problem, but the solutions didn't work for me, I have removed the raspi-firmware like some posts suggests but it didn't solve my problem, another suggestion is that I will must wait for a update for the nvidia-driver package. Here's the posts: viewtopic.php?t=156305 viewtopic.php?t=155208 viewtopic.php?t=155192 viewtopic.php?t=154857 To add more information, here's the output for the command dkms status: Code: Select allnvidia-current/525.147.05, 6.1.0-17-amd64, x86_64: installed r8168/8.051.02, 6.1.0-17-amd64, x86_64: installed r8168/8.051.02, 6.1.0-18-amd64, x86_64: installed | Hello, This is caused by a issue in the nvidia proprietary kernel module showed up with latest Debian 6.1.0-18 kernel upgrade: https://forums.debian.net/viewtopic.php?t=158200 Debian Bug report logs - #1063675 - bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1 |
Hi folks, I am running three virtual machine in the same LAN (Network 192.168.88.0/24) These three virtual servers are running Debian 11 (I personally installed all updates available). Their goal is a glusterfs deployment: Two GlusterFS node as storage (their hostname are docker01 and docker02) One GlusterFS node as arbiter (its hostname is swarm01) GlusterFS installed is # gluster --version ==> glusterfs 11.1 I already edited /etc/hosts file to create DNS record with success. Code: Select allroot@docker01:~# tail -f /var/log/glusterfs/mnt.log [2024-02-13 22:16:23.623527 +0000] W [fuse-bridge.c:1403:fuse_attr_cbk] 0-glusterfs-fuse: 1020: LOOKUP() / => -1 (Transport endpoint is not connected) [2024-02-13 22:16:23.623571 +0000] W [fuse-bridge.c:1403:fuse_attr_cbk] 0-glusterfs-fuse: 1021: LOOKUP() / => -1 (Transport endpoint is not connected) [2024-02-13 22:16:23.792071 +0000] W [fuse-bridge.c:1403:fuse_attr_cbk] 0-glusterfs-fuse: 1022: LOOKUP() / => -1 (Transport endpoint is not connected) [2024-02-13 22:16:23.792118 +0000] W [fuse-bridge.c:1403:fuse_attr_cbk] 0-glusterfs-fuse: 1023: LOOKUP() / => -1 (Transport endpoint is not connected) [2024-02-13 22:16:23.908092 +0000] W [fuse-bridge.c:1403:fuse_attr_cbk] 0-glusterfs-fuse: 1024: LOOKUP() / => -1 (Transport endpoint is not connected) [2024-02-13 22:16:23.908136 +0000] W [fuse-bridge.c:1403:fuse_attr_cbk] 0-glusterfs-fuse: 1025: LOOKUP() / => -1 (Transport endpoint is not connected) [2024-02-13 22:16:26.241343 +0000] E [MSGID: 114058] [client-handshake.c:946:client_query_portmap_cbk] 0-storegfs-client-1: failed to get the port number for remote subvolume. Please run gluster volume status on server to see if brick process is running [] [2024-02-13 22:16:29.696653 +0000] W [fuse-bridge.c:1403:fuse_attr_cbk] 0-glusterfs-fuse: 1044: LOOKUP() / => -1 (Transport endpoint is not connected) [2024-02-13 22:16:45.654162 +0000] I [socket.c:835:__socket_shutdown] 0-storegfs-client-2: intentional socket shutdown(6) [2024-02-13 22:17:02.259513 +0000] I [socket.c:835:__socket_shutdown] 0-storegfs-client-0: intentional socket shutdown(6) q ^C root@docker01:~# gluster volume status Status of volume: storegfs Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick docker01:/mnt/disk1/br0 N/A N/A N N/A Brick docker02:/mnt/disk2/br0 N/A N/A N N/A Brick swarm01:/mnt/disk3/br0 N/A N/A N N/A Self-heal Daemon on localhost N/A N/A Y 906 Self-heal Daemon on swarm01 N/A N/A Y 940 Self-heal Daemon on docker02 N/A N/A Y 1765 Task Status of Volume storegfs ------------------------------------------------------------------------------ There are no active volume tasks These three virtual server can ping each other, iptables on these machines haven't any rule set. Gluster service is running, but I got error message concerning I collected this data from the first of three VM in my GlusterFS deployment. I create volume with the following command (I didn't got any error). Code: Select allcluster volume create storegfs replica 3 arbiter 1 docker01:/mnt/disk1/br0 docker02:/mnt/disk2/br0 swarm01:/mnt/disk3/br0 In the end I would use this GlusterFS deployment with Docker Swarm. I never tried Docker Swarm in this deployment due to it is not properly working GlusterFS now. Any suggestion for me? | I will share you more details. Below output of "cluster volume info" Code: Select allVolume Name: storegfs Type: Replicate Volume ID: b03c686a-46cd-458c-8209-d738d5d2e208 Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: docker01:/mnt/disk1/br0 Brick2: docker02:/mnt/disk2/br0 Brick3: swarm01:/mnt/disk3/br0 (arbiter) Options Reconfigured: performance.client-io-threads: off transport.address-family: inet storage.fips-mode-rchecksum: on cluster.granular-entry-heal: on cluster.self-heal-daemon: enable Thanks a lot in advance |
I have been trying to run stunnel as a service via systemd and the service does not start. Starting stunnel via the command sudo stunnel4 is successful and so the config file seems to be perfectly fine. Whenever I try to start the service via systemd through the command # systemctl start stunnel@telnet the service seems to start and immediately terminates journalctl seems to have these two entries Feb 23 01:40:46 newcore systemd[1]: Started stunnel@telnet.service - TLS tunnel for network daemons - per-config-file service. Feb 23 01:40:46 newcore systemd[1]: stunnel@telnet.service: Deactivated successfully. And the # systemctl status stunnel@telnet gives the following output stunnel@telnet.service - TLS tunnel for network daemons - per-config-file service Loaded: loaded (/lib/systemd/system/stunnel@.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:stunnel4(8) The systemd file for stunnel is as follows [Unit] Description=TLS tunnel for network daemons - per-config-file service Documentation=man:stunnel4(8) PartOf=stunnel.target [Service] ExecStart=/usr/bin/stunnel4 /etc/stunnel/%i.conf PrivateTmp=yes [Install] WantedBy=multi-user.target Can anyone suggest what is the issue here. This is not system specific as I have the same behavior in multiple Debian 12 systems Thanks | Hello, Thanks for reporting back the solution. |
Hello, I just tried to setup a local PC, using iwd (first time, just to learning purpose) as wireless connection manager (fix IP, Debian 12, adapter driver from https://github.com/cilynx/rtl88x2bu). Connection established successfully: Code: Select allroot@testpc1:~# iwctl adapter list Adapters -------------------------------------------------------------------------------- Name Powered Vendor Model -------------------------------------------------------------------------------- phy0 on TP-Link Archer T4U ver.3 root@testpc1:~# iwctl device list Devices -------------------------------------------------------------------------------- Name Address Powered Adapter Mode -------------------------------------------------------------------------------- wlx2887ba1fd809 28:87:ba:1f:d8:09 on phy0 station root@testpc1:~# iw dev wlx2887ba1fd809 info Interface wlx2887ba1fd809 ifindex 3 wdev 0x1 addr 28:87:ba:1f:d8:09 ssid TCRT-CLS5 type managed wiphy 0 channel 136 (5680 MHz), width: 20 MHz (no HT), center1: 5680 MHz txpower 26.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets 0 0 0 0 0 0 0 0 0 but with no HT/VHT capabilities utilized. It seems iwd knows VHT: Code: Select allroot@testpc1:~# systemctl status iwd ... Feb 24 07:34:29 testpc1 iwd[1442]: VHT Capabilities: Feb 24 07:34:29 testpc1 iwd[1442]: Short GI for 80Mhz Feb 24 07:34:29 testpc1 iwd[1442]: Max RX MCS: 0-9 for NSS: 2 Feb 24 07:34:29 testpc1 iwd[1442]: Max TX MCS: 0-9 for NSS: 2 Feb 24 07:34:29 testpc1 iwd[1442]: Ciphers: BIP-CMAC-256 BIP-GMAC-256 BIP-GMAC-128 CCMP-256 Feb 24 07:34:29 testpc1 iwd[1442]: GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128 Feb 24 07:34:29 testpc1 iwd[1442]: TKIP Feb 24 07:34:29 testpc1 iwd[1442]: Supported iftypes: ad-hoc station ap Feb 24 07:34:29 testpc1 iwd[1442]: Wiphy phy0 will only use the default interface Feb 24 07:38:23 testpc1 iwd[1442]: hardware_rekey not supported Adapter has capabilities (TL;DR) : Code: Select allroot@testpc1:~# iw phy Wiphy phy0 wiphy index: 0 max # scan SSIDs: 4 max scan IEs length: 2243 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports T-DLS. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CCMP-256 (00-0f-ac:10) * GCMP-128 (00-0f-ac:8) * GCMP-256 (00-0f-ac:9) * CMAC (00-0f-ac:6) * CMAC-256 (00-0f-ac:13) * GMAC-128 (00-0f-ac:11) * GMAC-256 (00-0f-ac:12) Available Antennas: TX 0x3 RX 0x3 Configured Antennas: TX 0x3 RX 0x3 Supported interface modes: * IBSS * managed * AP * AP/VLAN * monitor * mesh point Band 1: Capabilities: 0x196f RX LDPC HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 2 usec (0x04) HT Max RX data rate: 300 Mbps HT TX/RX MCS rate indexes supported: 0-15, 32 Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) * 2472 MHz [13] (20.0 dBm) * 2484 MHz [14] (disabled) Band 2: Capabilities: 0x196f RX LDPC HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 2 usec (0x04) HT Max RX data rate: 300 Mbps HT TX/RX MCS rate indexes supported: 0-15, 32 VHT Capabilities (0x03d071b2): Max MPDU length: 11454 Supported Channel Width: neither 160 nor 80+80 RX LDPC short GI (80 MHz) TX STBC SU Beamformee MU Beamformee +HTC-VHT VHT RX MCS set: 1 streams: MCS 0-9 2 streams: MCS 0-9 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 780 Mbps VHT TX MCS set: 1 streams: MCS 0-9 2 streams: MCS 0-9 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 780 Mbps VHT extended NSS: not supported Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 5180 MHz [36] (23.0 dBm) * 5200 MHz [40] (23.0 dBm) * 5220 MHz [44] (23.0 dBm) * 5240 MHz [48] (23.0 dBm) * 5260 MHz [52] (20.0 dBm) (radar detection) * 5280 MHz [56] (20.0 dBm) (radar detection) * 5300 MHz [60] (20.0 dBm) (radar detection) * 5320 MHz [64] (20.0 dBm) (radar detection) * 5500 MHz [100] (26.0 dBm) (radar detection) * 5520 MHz [104] (26.0 dBm) (radar detection) * 5540 MHz [108] (26.0 dBm) (radar detection) * 5560 MHz [112] (26.0 dBm) (radar detection) * 5580 MHz [116] (26.0 dBm) (radar detection) * 5600 MHz [120] (26.0 dBm) (radar detection) * 5620 MHz [124] (26.0 dBm) (radar detection) * 5640 MHz [128] (26.0 dBm) (radar detection) * 5660 MHz [132] (26.0 dBm) (radar detection) * 5680 MHz [136] (26.0 dBm) (radar detection) * 5700 MHz [140] (26.0 dBm) (radar detection) * 5720 MHz [144] (13.0 dBm) (radar detection) * 5745 MHz [149] (13.0 dBm) * 5765 MHz [153] (13.0 dBm) * 5785 MHz [157] (13.0 dBm) * 5805 MHz [161] (13.0 dBm) * 5825 MHz [165] (13.0 dBm) Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * new_mpath * set_mesh_config * set_bss * authenticate * associate * deauthenticate * disassociate * join_ibss * join_mesh * remain_on_channel * set_tx_bitrate_mask * frame * frame_wait_cancel * set_wiphy_netns * set_channel * tdls_mgmt * tdls_oper * probe_client * set_noack_map * register_beacons * start_p2p_device * set_mcast_rate * connect * disconnect * set_qos_map * set_multicast_to_unicast * set_sar_specs software interface modes (can always be added): * AP/VLAN * monitor interface combinations are not supported HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing Device supports TX status socket option. Device supports HT-IBSS. Device supports SAE with AUTHENTICATE command Device supports scan flush. Device supports per-vif TX power setting Driver supports full state transitions for AP/GO clients Driver supports a userspace MPM Device supports configuring vdev MAC-addr on create. Device supports randomizing MAC-addr in scans. max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0x40 0xb0 0xc0 0xd0 * managed: 0x40 0xb0 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-device: 0x40 0xd0 Supported extended features: * [ RRM ]: RRM * [ SET_SCAN_DWELL ]: scan dwell setting * [ FILS_STA ]: STA FILS (Fast Initial Link Setup) * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211 * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs * [ SCAN_RANDOM_SN ]: use random sequence numbers in scans * [ CAN_REPLACE_PTK0 ]: can safely replace PTK 0 when rekeying * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support * [ DEL_IBSS_STA ]: deletion of IBSS station support * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support It seems wpa_supplicant (with Connman) perform configuration (switch ch and freq), and uses HT capabilities (installed on same PC box): Code: Select allFeb 23 20:17:06 debian wpa_supplicant[1610]: wlx2887ba1fd809: CTRL-EVENT-DSCP-POLICY clear_all Feb 23 20:17:06 debian wpa_supplicant[1610]: wlx2887ba1fd809: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Feb 23 20:18:26 debian wpa_supplicant[1610]: wlx2887ba1fd809: Trying to associate with 58:90:43:5b:1a:47 (SSID='DLJK-CLS5' freq=5680 MHz) Feb 23 20:18:27 debian wpa_supplicant[1610]: wlx2887ba1fd809: CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5680 ht_enabled=1 ch_offset=-1 ch_width=40 MHz cf1=5670 cf2=0 Feb 23 20:18:27 debian wpa_supplicant[1610]: wlx2887ba1fd809: Associated with 58:90:43:5b:1a:47 Feb 23 20:18:27 debian wpa_supplicant[1610]: wlx2887ba1fd809: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Feb 23 20:18:27 debian wpa_supplicant[1610]: wlx2887ba1fd809: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE Feb 23 20:18:27 debian wpa_supplicant[1610]: wlx2887ba1fd809: WPA: Key negotiation completed with 58:90:43:5b:1a:47 [PTK=CCMP GTK=CCMP] Feb 23 20:18:27 debian wpa_supplicant[1610]: wlx2887ba1fd809: CTRL-EVENT-CONNECTED - Connection to 58:90:43:5b:1a:47 completed [id=0 id_str=] So, my question is: Is it possible to configure (switch) connection using iwd (iwctl or iw), and Howto? Sorry, I couldn't figure out it from iwd/iw docs. Or... forget iwd, and use old Connman+wpa_supplicant pair? Thanks for any help, Leslie | Hello, dlacx wrote: 2024-02-24 08:56 I just tried to setup a local PC, using iwd (first time, just to learning purpose) as wireless connection manager (fix IP, Debian 12, adapter driver from https://github.com/cilynx/rtl88x2bu). Connection established successfully: [..] It seems wpa_supplicant (with Connman) perform configuration (switch ch and freq), and uses HT capabilities [..] So, my question is: Is it possible to configure (switch) connection using iwd (iwctl or iw), and Howto? Sorry, I couldn't figure out it from iwd/iw docs. Or... forget iwd, and use old Connman+wpa_supplicant pair? There are the involved WiFi protocols: VHT corrisponds to IEEE 802.11ac-2013 (or or 802.11ac) [1] HT corrisponds to IEEE 802.11n-2009 (or 802.11n) [2] I've searched the iwd source code (Debian Bookworm version) for HT/VHT configurations, but haven't found any reference to user configurable parameters for HT/VHT. So my guess is that iwd automatically negotiates the best available connection based on the capabilities of your device and the access point (as it detects them). If you wish, you can probably try forcing the wireless adapter kernel module to use VHT (if a capable access point is available). The following command shows the available kernel module parameters for 88x2bu.ko out-of-the-tree kernel module: Code: Select all$ /sbin/modinfo ./88x2bu.ko | grep -i ht parm: rtw_vht_enable:int parm: rtw_vht_rx_mcs_map:VHT RX MCS map (uint) parm: rtw_ht_enable:int parm: rtw_vht_2g4:Allow VHT rate on 2.4G channel.(0 for deny and 1 for allow) (int) You are probably interested in the parameter rtw_vht_enable that, according to source code, can be used with these values (default = 1): Code: Select allos_dep/linux/os_intfs.c:int rtw_vht_enable = 1; /* 0:disable, 1:enable, 2:force auto enable */ Furthermore, as far as I know, the wpa_supplicant program negotiates the WiFi protocol through the underlying kernel module (rtl88x2bu in your case) used by the wireless adapter before negotiating the wpa connection. Therefore, wpa_supplicant.conf can be created and configured to force HT or VHT wifi protocols (details in /usr/share/doc/wpa_supplicant/) if it used. if Connman+wpa_supplicant pair already works, it is perhaps your first choice. Hope this helps. Please, let me know. -- [1] Wikipedia - VHT - IEEE 802.11ac-2013 (or or 802.11ac) [2] Wikipedia - HT - IEEE 802.11n-2009 (or 802.11n) |
Hello, I installed Fail2Ban.And its service was not running. The service ran successfully when I added the following lines to the beginning of the configuration file: Code: Select all[sshd] enabled = true Now I want to configure Fail2Ban for SSH service and my settings are as follows: Code: Select all[sshd] port = ssh logpath = %(sshd_log)s backend = %(sshd_backend)s maxretry = 2 findtime = 10 bantime = 4w When I restart the Fail2Ban service, I see the following error message: [1313]: ERROR Failed during configuration: While reading from '/etc/fail2ban/jail.local' [line 275]: section 'sshd' already exists How to solve it? Thank you. | Hello, I commented these two line: Code: Select all[sshd] enabled = true Then I changed the configuration as below: Code: Select all[sshd] enabled = true port = ssh logpath = %(sshd_log)s backend = %(sshd_backend)s maxretry = 2 findtime = 10 bantime = 4w After it, I got the error message Failed during configuration: Have not found any log file for sshd jail. How to solve it? |
Fresh install of Debian 12 on Lenovo W541 system specs: UEFI BIOS Version: GNET($WW (2.42) Embedded Controller Version: GMHT25WW (1.10) ME Firmware Version 9.1.20.1035 Machine Type Model 20EFCT01WW CPU Type: Intel Core i7-4810MQ @2.8GHZ when initiating a system shutdown, systemd stops/closes all the processes, blanks the screen, displays the following: Broadcast message from user@W541-debian (date time): The system will power off now! Code: Select all[ 48.134884] systemd-shutdown[1]: Waiting for process: 387 ((udev-worker)), 356 ((udev-worker)), 350(systemd-udevd), 585 [128.131373] systemd-shutdown[1]: sending SIGKILL to remaining processes... [128.138277] systemd-shutdown[1]: sending SIGKILL to PID 350 (systemd-udevd). [128.138591] systemd-shutdown[1]: sending SIGKILL to PID 356 ((udev-worker)). [128.138817] systemd-shutdown[1]: sending SIGKILL to PID 379 ((udev-worker)). [128.138977] systemd-shutdown[1]: sending SIGKILL to PID 387 ((udev-worker)). [128.139447] systemd-shutdown[1]: sending SIGKILL to PID 585 ((udev-worker)). [138.140382] systemd-shutdown[1]: waiting for process: 585 (modprobe). [218.141675] systemd-shutdown[1]: Unmounting file systems. [218.143578] (sd-remount) [4334]: remounting '/' read-only with options 'errors=remount-ro'. [218.156368] EXT4-fs (dm-0): re-mounted. Quota Mode: none. [218.163836]systemd-shutdown[1]: All filesystems unmounted. [218.163853] systemd-shutdown[1]:Deactivating swaps. [218.163903] systemd-shutdown[1]:All swaps deactivated. [218.163912] systemd-shutdown[1]:Detaching loop devices. [218.164390] systemd-shutdown[1]:All loop devices detached. [218.164404] systemd-shutdown[1]:Stopping MD devices. [218.164465] systemd-shutdown[1]:All MD devices stopped. [218.164476] systemd-shutdown[1]:Detaching DM devices. [218.164773] systemd-shutdown[1]:Detaching DM /dev/dm-1 (254:1). [218.220390] systemd-shutdown[1]:Not all DM devices detached, 1 left. [218.220490] systemd-shutdown[1]:Detaching DM devices. [218.220755] systemd-shutdown[1]:Not all DM devices detached, 1 left. [218.220800] systemd-shutdown[1]::Detaching DM devices. [218.220974] systemd-shutdown[1]:Not all DM devices detached, 1 left. [218.220989] systemd-shutdown[1]:Cannot finalize remaining DM devices, continuing. [218.283318] systemd-shutdown[1]:Failed to finalize DM devices, ignoring. [218.283517] systemd-shutdown[1]:Syncing filesystems and block devices. [218.283795] systemd-shutdown[1]:Powering off. At his point the system remains powered on until a long press on the power button. upon rebooting and checking the systemd journal with journalctl -r the following entries are listed at the point of shut down and reboot: .. .. app.slice: consumed 3min 2.254s CPU time. reached target shutdown.target -shutdown. Finished systemd-exit.service - Exit the Session. Reached target exit.target - Exit the Session. --- Boot 21d78##########...##### --- Queued start job for default target default.target. .. .. Any ideas will be greatly appreciated. | Please put large code blocks in code tags as I did for one of the sections. Re-open the message with 'edit' to see the example. |
Hello, The SSH part of Fail2ban is as follows: Code: Select all[sshd] enabled = true port = 22 logpath = /var/log/ssh-fail2ban.log backend = %(sshd_backend)s maxretry = 2 findtime = 10 bantime = 4w I connected to the host and entered the wrong SSH password a few times, but I was not blocked. Why? Thank you. MODERATOR EDIT (aki, Tue Feb 27 08:28:22 CET 2024): added "solved" tag. | @jasonnix: Are you in the other forum posting the same questions ? What part of the Fail2Ban configuration is wrong? |
I would like to enable numlock right after the kernel boots. Because I encrypted the disk during the installation and I need to ensure numlock is on when I enter the full-disk encryption password. I was able to enable numlock in BIOS, and it works, but then it automatically disables itself before entering the full-disk encryption password. I have also been able to set NumLock on by default on my LightDM display manager. If you know a procedure to enable numlock right after the kernel boots, please comment. Thanks in advance. Code: Select allOperating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.0-14-686-pae Architecture: x86 | newuser wrote: 2022-05-25 00:30 I need to ensure numlock is on when I enter the full-disk encryption password. Why ? Are you too lazy to press num lock or shift ? Head_on_a_Stick wrote: 2022-05-25 05:09 https://dev1galaxy.org/viewtopic.php?pid=33465#p33465 The passphrase is needed by the initramfs, so I am afraid that /etc/rc.local is too late for what the OP wants. |
Tried to transfer some video edits (4+ GB size) from my Linux Mint box to my Debian laptop using a NTFS formatted thumbdrive. Doesn't work ntfs3 not configured in Kernel. I haven't tried the exfat formated card in my 4k video camera yet. I so wanted to go back to debian. Is this a bug or a feature? | Hello, What is your Debian version ? Have you installed the ntfs-3g package ? This package allows to use the NTFS file system through from the user space through FUSE. The kernel module does not fully support current versions of NTFS file system. |
I updated to the latest Debian 12.4 and I have the issues described here: - no wifi connection - extremely slow reboot - system is not responsive - etc If I use an older image, then it is fine. For the moment, I "solve" it, by removing the 6.1.0-15 and using an older kernel. That one works properly (6.1.0.13). the /boot partition is the only one with ext4: Code: Select allsda 8:0 0 233.8G 0 disk ├─sda1 8:1 0 571M 0 part /boot/efi ├─sda2 8:2 0 954M 0 part /boot └─sda3 8:3 0 232.3G 0 part └─sda3_crypt 254:0 0 232.3G 0 crypt ├─vg-swap 254:1 0 8.4G 0 lvm [SWAP] └─vg-root 254:2 0 223.9G 0 lvm / For the moment, this is the only system where this issue manifests, the other are running properly. Questions: - should I wait for the next kernel package? In theory this latest version (6.1.0-15) should fix this. - how can I check /dev/sda2 for file system inconsistencies? When I run a fsck I get an error that the file system is mounted. I didn't dare to unmount it and to move the SSD in another machine is not an option, this is a Macbook. - what should I do to automatically install kernel headers for the respective version? - now, with the older kernel, the new kernel (6.1.0-15) is not displayed when I run 'apt update'. Why is that? | stevepusser wrote: 2023-12-12 20:59 Just rebuilt Liquorix 6.6-7, based on 6.6.6. The neighbour of the beast. |
Hi, I have as monitor a Panasonic TV which is capable of 1368x766 through VGA according to manual. However, my Debian 9.5 install doesn't detect that resolution and gives me an inferior one. I used the commands below to achieve the highest possible resolution: Code: Select allxrandr --newmode "1368x766_60.00" 85.64 1368 1440 1584 1800 766 767 770 793 -HSync +Vsync xrandr --addmode VGA-1 "1368x766_60.00" xrandr --output VGA-1 --mode 1368x766_60.00 To keep that resolution permanently, I thought I just add those 3 lines at the end of my ~/.profile file but I see after a reboot, I get again a lower resolution. Does anyone know what I'm doing wrong? | This video is on YouTube. He changes the resolution and then makes it permanent. https://www.youtube.com/watch?v=MScLD8dFNwk |
On Debian 11 I have installed the openvpn from repos. I have tried connecting it to an openVPN server I have setup on Debian 12 and also using an ovpn from Code: Select allhttps://www.vpnbook.com/freevpn Both work fine on Window10 using the openVPN client from Code: Select allhttps://swupdate.openvpn.org/community/releases/OpenVPN-2.6.6-I001-amd64.msi and if I check my IP with various what is my ip sites both vpn's respond with IP expected i.e. the vpn servers IP not my local broadband IP. But when I try with openVPN on debian 11 they show connecting okay but whats my IP for either shows my local broadband IP | k829king wrote: 2023-09-10 08:18 [..] But when I try with openVPN on debian 11 they show connecting okay but whats my IP for either shows my local broadband IP Check configuration and system logs. |
Debian Bullseye to Debian Bookworm 12 upgrade Intel AC7265 dual band wifi card , dmsmasq Network Manager created hotspot with the Intel Wifi card ------------------------------------------------------------------------------- After upgrading from Debian 11 to Debian 12 Bookworm , all Windows and Linux devices still see the hotspot but our three Android phones ,,various carriers, does not see the hotspot after upgrade. Looking in network manager command line i see nothing failing , only showing dnsmasq has handed out ip addreses to windows and linux devices on our home network. This setup has worked flawless for about two years previous to upgrade. Have never run into this before so dont really know how to run a diagnostics matrix on pinning down the actual problem TIA | @friendlysalmon88 Typically a particular mirror is not the best recommendation. Not everyone is closest to Washington. furthermore, it is sloppy form to include extraneous code in your code block. Clean it up. Take a breath. |
Hi, before I start trying to descend into the myriads of logs etc, is anyone else affected by an update to server component openvpn in Debian12. I recently ran an update which installed openvpn:amd64 2.6.3-1+deb12u2 I had a prompt to override the server.config which I said no to. since then clients connect but they no longer present the servers IP to whatsMyIp sites and DNS is failing I can only access websites by IP addresses, or possibly it is only a website on the server running on the same server. | Hello, Just a guess. Please, verify that your Debian Bookworm installation is up to date; see this other discussion: [Solved] Issues with kernel 6.1.0-15-amd64/stable 6.1.66-1 |
I have a keytronic keyboard with "windows" keys. I'd like to use those special keys to launch apps etc. However the left windows key does not give any events when testing it with "xev". So there is no point to trying to map it... There must be some configuration option in xorg to enable this key. Right win key and the "menu" key work just fine... I'm using Debian etch. Snippet from /etc/X11/xorg.conf: Code: Select allSection "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "fi" EndSection | NarriT4010 wrote: 2023-12-06 03:51 Oh nevermind it will lock and unlock when pressing fn+esc 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); for example: [Solved] How to get the left "windows" key to work? EDIT: Added the tag [Solved] on 13 Dec 2023. |
Hello, I setup an Debian server using version 11 I was able to install NGINX with PHP-FPM and run a website I am unable to have my website communicate to my SMTP sever. Example using an SMTP server for populating email settings in a Contact form. I can only have it communicate using PHPMailer. This causes an issue as GMAIL doesn't accept emails from PHPMailer by default Is there a Debian package or module that I can install to communicate to my SMTP server without using PHP? Z70DMS | @z70dms: Did you sort it out ? |
I've recently installed debian 12 on my HP laptop. The installer automatically transferred my WiFi network information to the installed OS after finishing, and since then I never touched anything related to wifi. Now that I'm out of home, I wanted to connect to another WiFi, but I wasnt able to. First, nmtui didnt show anythining related to wifi. I had to modify the file /etc/NewtorkManager/NetworkManager.conf and modify the managed parameter to true. After that, I stll wasnt anble to see wifi connections, but at least nmcli didnt show both the ethernet and wifi asunmanaged, and instead showed them as unavailable. After looking a bit, I discovered this: Code: Select allfpp@fpp-g42:~$ sudo systemctl status wpa_supplicant.service ● wpa_supplicant.service - WPA supplicant Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled; preset: enabled) Active: active (running) since Sun 2023-12-31 19:54:04 -03; 2min 19s ago Main PID: 583 (wpa_supplicant) Tasks: 1 (limit: 6678) Memory: 1.7M CPU: 82ms CGroup: /system.slice/wpa_supplicant.service └─583 /sbin/wpa_supplicant -u -s -O "DIR=/run/wpa_supplicant GROUP=netdev" dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: nl80211: kernel reports: Match already configured dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: nl80211: kernel reports: Match already configured dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: nl80211: kernel reports: Match already configured dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: nl80211: kernel reports: Match already configured dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: ctrl_iface exists and seems to be in use - cannot override it dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: Delete '/run/wpa_supplicant/wlo2' manually if it is not used anymore dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: Failed to initialize control interface 'DIR=/run/wpa_supplicant GROUP=netdev'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again. dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: wlo2: CTRL-EVENT-DSCP-POLICY clear_all dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: wlo2: CTRL-EVENT-DSCP-POLICY clear_all dic 31 19:54:54 fpp-g42 wpa_supplicant[583]: nl80211: deinit ifname=wlo2 disabled_11b_rates=0 fpp@fpp-g42:~$ sudo systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) Active: active (running) since Sun 2023-12-31 19:54:03 -03; 2min 30s ago Docs: man:NetworkManager(8) Main PID: 519 (NetworkManager) Tasks: 3 (limit: 6678) Memory: 16.4M CPU: 263ms CGroup: /system.slice/NetworkManager.service └─519 /usr/sbin/NetworkManager --no-daemon dic 31 19:54:14 fpp-g42 NetworkManager[519]: <error> [1704063254.4349] device (wlo2): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface. dic 31 19:54:24 fpp-g42 NetworkManager[519]: <warn> [1704063264.3624] device (wlo2): re-acquiring supplicant interface (#2). dic 31 19:54:24 fpp-g42 NetworkManager[519]: <error> [1704063264.4232] device (wlo2): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface. dic 31 19:54:34 fpp-g42 NetworkManager[519]: <warn> [1704063274.3631] device (wlo2): re-acquiring supplicant interface (#3). dic 31 19:54:34 fpp-g42 NetworkManager[519]: <error> [1704063274.4351] device (wlo2): Couldn't initialize supplicant interface: gDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface. dic 31 19:54:44 fpp-g42 NetworkManager[519]: <warn> [1704063284.3643] device (wlo2): re-acquiring supplicant interface (#4). dic 31 19:54:44 fpp-g42 NetworkManager[519]: <error> [1704063284.4390] device (wlo2): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface. dic 31 19:54:54 fpp-g42 NetworkManager[519]: <warn> [1704063294.3674] device (wlo2): re-acquiring supplicant interface (#5). dic 31 19:54:54 fpp-g42 NetworkManager[519]: <error> [1704063294.4311] device (wlo2): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface. dic 31 19:54:54 fpp-g42 NetworkManager[519]: <info> [1704063294.4312] device (wlo2): supplicant interface keeps failing, giving up I looked up a bit more and found that running this: Code: Select allfpp@fpp-g42:~$ sudo killall wpa_supplicant fpp@fpp-g42:~$ sudo systemctl restart NetworkManager fixes my issue, as long as I keep my laptop on. I've looked up a bit more, and in theory there must be a confict with two network managers, but the thing is that I havent installed nothing network-related, and i dont know how to identify wich are the managers that are in conflict | Hello, You probably need to comment the contents of the file named /etc/network/interfaces referred to your wireless network interface. |
Hello I just installed Debian Linux from a DVD disk without Internet so the network installation is not configured yet I want to use iPhone cellular data as a internnet connexion source to reach Internet. The phone is connected to the computer via an USB port lsusb Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone 5/5C/5S/6/SE/7/8/X/XR can someone help me how to configure the network connection ? thank you | carmima wrote: 2024-01-04 09:40 the answer is: I had to install libimobiledevice + usbmuxd.service It means the following Debian packages (in my Debian Bookworm with Gnome and Mate installed): Code: Select all$ apt list usbmuxd libimobiledevice6 Listing... Done libimobiledevice6/stable,now 1.3.0-6+b3 amd64 [installed,automatic] usbmuxd/stable,now 1.1.1-2 amd64 [installed,automatic] The usbmuxd package depends on libimobiledevice6: Code: Select all$ apt show usbmuxd Package: usbmuxd Version: 1.1.1-2 Priority: optional Section: utils Maintainer: gtkpod Maintainers <pkg-gtkpod-devel@alioth-lists.debian.net> Installed-Size: 120 kB Depends: libc6 (>= 2.17), libimobiledevice6 (>= 1.3.0), libplist3 (>= 2.2.0), libusb-1.0-0 (>= 2:1.0.22), adduser Homepage: https://github.com/libimobiledevice/usbmuxd Tag: hardware::embedded, hardware::usb, implemented-in::c, interface::daemon, role::program, use::synchronizing Download-Size: 41.6 kB APT-Manual-Installed: no APT-Sources: http://deb.debian.org/debian bookworm/main amd64 Packages Description: USB multiplexor daemon for iPhone and iPod Touch devices usbmuxd, the USB multiplexor daemon, is in charge of coordinating access to iPhone and iPod Touch services over USB. Synchronization and management applications for the iPhone and iPod Touch need this daemon to communicate with such devices concurrently. . This package includes udev rules to start the daemon when a supported device is plugged in, and stop it when all devices are removed. The libimobiledevice6 package have the following reverse dependencies (packages that depends on it and should install automatically it) : Code: Select allapt rdepends libimobiledevice6 libimobiledevice6 Reverse Depends: Dipende: libimobiledevice-dev (= 1.3.0-6+b3) Dipende: libimobiledevice6-dbgsym (= 1.3.0-6+b3) Dipende: usbmuxd (>= 1.3.0) Dipende: libkf5solid5 (>= 1.3.0) Dipende: python3-imobiledevice (>= 1.3.0) Dipende: libimobiledevice-utils (>= 1.3.0) Dipende: ipheth-utils (>= 0.9.7) Dipende: libgpod4 (>= 1.3.0) Dipende: libgpod-common (>= 1.3.0) Dipende: ifuse (>= 1.2.0) Dipende: gvfs-backends (>= 1.3.0) Dipende: idevicerestore (>= 1.3.0) Dipende: ideviceinstaller (>= 1.3.0) Among them, libkf5solid5 (installed by KDE) and (gvfs-backends) installed by Gnome (and alike). What is your Desktop Enviroment (Gnome, KDE, other ..) ? EDIT (Thu Jan 18 21:28:18 CET 2024): added "[Solved]" tag. |
Hallo to Everybody. Today, on my main pc, I did an upgrade from Debian 11 to Debian 12. If I load the OS with kernel 6.1.0-16-amd64, it appears the 'kernel panic' message, so from Grub I can load Debian 12 only choosing 5.18.0-0.deb11.3-amd64. When I run a full-upgrade, it happens (something is in italian): Code: Select allzambo@zambo-hplaptop15dw0xxx:~$ sudo apt full-upgrade Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto Calcolo dell'aggiornamento... Fatto I seguenti pacchetti sono stati mantenuti alla versione attuale: fcitx5-chinese-addons-data 0 aggiornati, 0 installati, 0 da rimuovere e 1 non aggiornati. 4 non completamente installati o rimossi. Dopo quest'operazione, verranno occupati 0 B di spazio su disco. Continuare? [S/n] s Configurazione di linux-image-6.1.0-16-amd64 (6.1.67-1)... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-16-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... 'make' -j8 KVER=6.1.0-16-amd64......(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-16-amd64 (x86_64) Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-16-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: errore nell'elaborare il pacchetto linux-image-6.1.0-16-amd64 (--configure): il sottoprocesso installato pacchetto linux-image-6.1.0-16-amd64 script post-installation ha restituito lo stato di errore 1 dpkg: problemi con le dipendenze impediscono la configurazione di linux-image-amd64: linux-image-amd64 dipende da linux-image-6.1.0-16-amd64 (= 6.1.67-1); tuttavia: Il pacchetto linux-image-6.1.0-16-amd64 non è ancora configurato. dpkg: errore nell'elaborare il pacchetto linux-image-amd64 (--configure): problemi con le dipendenze - lasciato non configurato Configurazione di linux-headers-6.1.0-16-amd64 (6.1.67-1)... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-16-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... 'make' -j8 KVER=6.1.0-16-amd64......(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-16-amd64 (x86_64) Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-16-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-16-amd64.postinst line 11. dpkg: errore nell'elaborare il pacchetto linux-headers-6.1.0-16-amd64 (--configure): il sottoprocesso installato pacchetto linux-headers-6.1.0-16-amd64 script post-installation ha restituito lo stato di errore 1 dpkg: problemi con le dipendenze impediscono la configurazione di linux-headers-amd64: linux-headers-amd64 dipende da linux-headers-6.1.0-16-amd64 (= 6.1.67-1); tuttavia: Il pacchetto linux-headers-6.1.0-16-amd64 non è ancora configurato. dpkg: errore nell'elaborare il pacchetto linux-headers-amd64 (--configure): problemi con le dipendenze - lasciato non configurato Si sono verificati degli errori nell'elaborazione: linux-image-6.1.0-16-amd64 linux-image-amd64 linux-headers-6.1.0-16-amd64 linux-headers-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) I suppose that the problem is during the compilation of the module regarding the wifi card (Realtek rtl8821ce), with Debian 11 I "used" the classical Tomas Pinho repository for this wifi card, that I'm using from Debian 10. "Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more information" here it is: Code: Select allDKMS make.log for rtl8821ce-v5.5.2_34066.20200325 for kernel 6.1.0-16-amd64 (x86_64) dom 31 dic 2023, 00:48:05, CET make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.1.0-16-amd64/build M=/var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build modules make[1]: ingresso nella directory «/usr/src/linux-headers-6.1.0-16-amd64» CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_mlme_ext.o /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_mlme.c: In function ‘rtw_drv_scan_by_self’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_mlme.c:3161:17: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 3161 | else | ^~~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_mlme.c:3164:25: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 3164 | goto exit; | ^~~~ CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ap.o /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rf.c: In function ‘dump_txpwr_lmt’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rf.c:765:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 765 | if (IS_HARDWARE_TYPE_JAGUAR_AND_JAGUAR2(adapter)) | ^~ In file included from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/drv_types.h:60, from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rf.c:17: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/rtw_debug.h:220:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 220 | do {\ | ^~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rf.c:767:17: note: in expansion of macro ‘RTW_PRINT_SEL’ 767 | RTW_PRINT_SEL(sel, "txpwr_lmt_5g_20_40_ref:0x%02x ", rfctl->txpwr_lmt_5g_20_40_ref); | ^~~~~~~~~~~~~ CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_tdls.o /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_sta_mgt.c: In function ‘rtw_mfree_stainfo’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_sta_mgt.c:379:25: warning: the comparison will always evaluate as ‘true’ for the address of ‘lock’ will never be NULL [-Waddress] 379 | if (&psta->lock != NULL) | ^~ In file included from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/drv_types.h:108, from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_sta_mgt.c:17: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/sta_info.h:263:17: note: ‘lock’ declared here 263 | _lock lock; | ^~~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ap.c: In function ‘rtw_ap_update_chbw_by_ifbmp’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ap.c:4392:42: warning: the comparison will always evaluate as ‘true’ for the address of ‘padapters’ will never be NULL [-Waddress] 4392 | if (!(ifbmp & BIT(i)) || !dvobj->padapters) | ^ In file included from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ap.c:17: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/drv_types.h:1041:19: note: ‘padapters’ declared here 1041 | _adapter *padapters[CONFIG_IFACE_NUMBER];/*IFACE_ID_MAX*/ | ^~~~~~~~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_ap.c:4412:42: warning: the comparison will always evaluate as ‘true’ for the address of ‘padapters’ will never be NULL [-Waddress] 4412 | if (!(ifbmp & BIT(i)) || !dvobj->padapters) | ^ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/drv_types.h:1041:19: note: ‘padapters’ declared here 1041 | _adapter *padapters[CONFIG_IFACE_NUMBER];/*IFACE_ID_MAX*/ | ^~~~~~~~~ CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/pci_intf.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/pci_ops_linux.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/mlme_linux.o /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/osdep_service.c: In function ‘rtw_change_ifname’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/osdep_service.c:2516:28: warning: passing argument 1 of ‘_rtw_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 2516 | _rtw_memcpy(pnetdev->dev_addr, adapter_mac_addr(padapter), ETH_ALEN); | ~~~~~~~^~~~~~~~~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/osdep_service.c:930:24: note: expected ‘void *’ but argument is of type ‘const unsigned char *’ 930 | void _rtw_memcpy(void *dst, const void *src, u32 sz) | ~~~~~~^~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/osdep_service.c: In function ‘rtw_random32’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/osdep_service.c:2640:16: error: implicit declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? [-Werror=implicit-function-declaration] 2640 | return prandom_u32(); | ^~~~~~~~~~~ | prandom_u32_max /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/efuse/rtw_efuse.c: In function ‘rtw_efuse_analyze’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/efuse/rtw_efuse.c:781:17: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 781 | if (i % 16 == 0) | ^~ In file included from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/drv_types.h:60, from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/efuse/rtw_efuse.c:17: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/rtw_debug.h:231:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 231 | do {\ | ^~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/core/efuse/rtw_efuse.c:783:25: note: in expansion of macro ‘_RTW_PRINT_SEL’ 783 | _RTW_PRINT_SEL(RTW_DBGDUMP, "%02X%s" | ^~~~~~~~~~~~~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.c: In function ‘rtw_net_set_mac_address’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.c:1244:28: warning: passing argument 1 of ‘_rtw_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 1244 | _rtw_memcpy(pnetdev->dev_addr, sa->sa_data, ETH_ALEN); /* set mac addr to net_device */ | ~~~~~~~^~~~~~~~~~ In file included from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/drv_types.h:27, from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.c:17: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/osdep_service.h:296:35: note: expected ‘void *’ but argument is of type ‘const unsigned char *’ 296 | extern void _rtw_memcpy(void *dec, const void *sour, u32 sz); | ~~~~~~^~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.c: In function ‘rtw_os_ndev_register’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.c:1683:9: error: too many arguments to function ‘netif_napi_add’ 1683 | netif_napi_add(ndev, &adapter->napi, rtw_recv_napi_poll, RTL_NAPI_WEIGHT); | ^~~~~~~~~~~~~~ In file included from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/osdep_service_linux.h:30, from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/osdep_service.h:50: /usr/src/linux-headers-6.1.0-16-common/include/linux/netdevice.h:2575:1: note: declared here 2575 | netif_napi_add(struct net_device *dev, struct napi_struct *napi, | ^~~~~~~~~~~~~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.c:1699:25: warning: passing argument 1 of ‘_rtw_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 1699 | _rtw_memcpy(ndev->dev_addr, adapter_mac_addr(adapter), ETH_ALEN); | ~~~~^~~~~~~~~~ /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/osdep_service.h:296:35: note: expected ‘void *’ but argument is of type ‘const unsigned char *’ 296 | extern void _rtw_memcpy(void *dec, const void *sour, u32 sz); | ~~~~~~^~~ make[2]: *** [/usr/src/linux-headers-6.1.0-16-common/scripts/Makefile.build:255: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/os_intfs.o] Errore 1 make[2]: *** Attesa per i processi non terminati.... cc1: some warnings being treated as errors make[2]: *** [/usr/src/linux-headers-6.1.0-16-common/scripts/Makefile.build:255: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/osdep_service.o] Errore 1 /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/ioctl_linux.c: In function ‘rtw_mp_efuse_set’: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/ioctl_linux.c:9789:46: warning: passing argument 1 of ‘_rtw_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] 9789 | _rtw_memcpy(padapter->pnetdev->dev_addr, get_hal_mac_addr(padapter), ETH_ALEN); /* set mac addr to net_device */ | ~~~~~~~~~~~~~~~~~^~~~~~~~~~ In file included from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/drv_types.h:27, from /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/os_dep/linux/ioctl_linux.c:17: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/include/osdep_service.h:296:35: note: expected ‘void *’ but argument is of type ‘const unsigned char *’ 296 | extern void _rtw_memcpy(void *dec, const void *sour, u32 sz); | ~~~~~~^~~ make[1]: *** [/usr/src/linux-headers-6.1.0-16-common/Makefile:2039: /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build] Errore 2 make[1]: uscita dalla directory «/usr/src/linux-headers-6.1.0-16-amd64» make: *** [Makefile:2244: modules] Errore 2 This time I see that dkms fails to compile the module, so now I can't use the 6.1.0-16-amd kernel: can you help me? A last thing (maybe not so good?): in order to avoid a conflict with the built-in module, I did also: Code: Select allsudo -i modprobe -r rtw88_8821ce modprobe 8821ce echo “blacklist rtw88_8821ce” >> /etc/modprobe.d/blacklist.conf exit Thanks in advance! | stilnovo wrote: 2023-12-31 00:08If I load the OS with kernel 6.1.0-16-amd64, it appears the 'kernel panic' message If you don't tell us what it said, we'll have no idea what to do about it. stilnovo wrote: 2023-12-31 00:08something is in italian Which I don't read, set 'LANG=C'. At a guess, I expect that's just the usual "leaving unconfigured" jazz from apt & dpkg, because your random out-of-tree module failed to build against the new kernel. stilnovo wrote: 2023-12-31 00:08I suppose that the problem is during the compilation of the module regarding the wifi card (Realtek rtl8821ce) You suppose correctly. Your module sources reference a function that doesn't exist in the kernel sources you are trying to compile it against: Code: Select allerror: implicit declaration of function ‘prandom_u32’ stilnovo wrote: 2023-12-31 00:08with Debian 11 I "used" the classical Tomas Pinho repository for this wifi card, that I'm using from Debian 10. Used how? What "repository"? Are we supposed to guess? I don't see any compatible apt repositories for this driver, so I presume you got it from github.com/tomaspinho/rtl8821ce? When? A quick look over there suggests kernel 6.1 compatibility was fixed over a year ago, if the last time you updated it was when you were running buster I'm not even slightly surprised it's failing to compile. In any case, this driver isn't shipped in a Debian release, so it's not a Debian problem. If the latest git version doesn't compile against kernel 6.1.x, appropriate bug reports should go direct to upstream. stilnovo wrote: 2023-12-31 00:08 in order to avoid a conflict with the built-in module, I did also: Code: Select allsudo -i modprobe -r rtw88_8821ce modprobe 8821ce echo “blacklist rtw88_8821ce” >> /etc/modprobe.d/blacklist.conf exit Unless you have some specific need to do otherwise, I suggest you use what's included in the Debian kernel modules. rtw88_8821ce is a newer driver intended to replace rtl8821ce... Or so Realtek would have us believe anyway. As usual, their drivers are a complete mess. mrmazda wrote: 2023-12-31 05:32inxi What is with the fixation on inxi these days? It's not going to provide the output of that kernel panic, nor will it fix horribly out of date third party module sources. The only relevant information inxi might provide is that the machine has a realtek 8821 based NIC, which could just as easily be deduced from lspci & co... Or that the OP is clearly trying to compile a driver for it. |
On my Lenovo laptop the Debian 11 works perfectly. Once it was upgraded to the 12 the networking stopped. What happens is it seems like every networking applications gets caught into an infinite loop. For example, using ping it just sits there. The upgrade on the desktop went perfectly. After doing some research, I found the resolv.conf file is now a symlink to a file that does not exist. This is the information from lshw before the upgrade. description: Ethernet interface product: Ethernet Connection (4) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@0000:00:1f.6 logical name: enp0s31f6 version: 21 serial: e8:6a:64:9b:fa:55 size: 100Mbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.10.0-18-amd64 duplex=full firmware=0.1-4 ip=192.168.1.45 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:145 memory:ec100000-ec11ffff | Sounds familiar. Same issue? viewtopic.php?p=786653#p786653 |
This is an update of my post at the end of a 'Solved' thread viewtopic.php?p=778125&hilit=cisco+anyconnect#p778125, with permission of the moderator. With Debian 11, I used the Cisco AnyConnect VPN with MFA available from my university without issues. This became impossible after the upgrade to Debian 12 (bookworm). When I type the command /opt/cisco/anyconnect/bin/vpnui, I get a dialogue box in which I enter the address of the VPN. I click on Connect, which starts the university's MFA. After I've entered my login credentials and the Duo Mobile code from my phone, I get a Cisco AnyConnect banner asking me to Accept. Clicking on that results in the messages: AnyConnect was not able to establish a connection to the specified secure gateway ... The certificate on the secure gateway is invalid. A VPN connection will not be established. Another user had a similar problem with VPN under bookworm, and found that the problem is that, under bookworm, clients do not identify themselves to the Cisco VPN servers with a useragent starting with AnyConnect. He circumvented the problem by using the openconnect command with the option --useragent 'AnyConnect'. His solution hasn't worked in my MFA environment; I get to an infinite loop of requests for my username and password. This user https://forums.freebsd.org/threads/open ... 2fa.87788/ found a way to run Cisco AnyConnect VPN with MFA on FreeBSD using openconnect-sso, but I haven't been able to adapt his approach to supply the changed useragent identification necesitated by Debian 12. I should add that the university's service desk has not been able to help so far. I'm guessing this is a problem without a solution, but maybe someone will surprise me! | Hello, drkayak99 wrote: 2023-12-16 19:44 [..] When I type the command /opt/cisco/anyconnect/bin/vpnui, I get a dialogue box in which I enter the address of the VPN. I click on Connect, which starts the university's MFA. After I've entered my login credentials and the Duo Mobile code from my phone, I get a Cisco AnyConnect banner asking me to Accept. Clicking on that results in the messages: AnyConnect was not able to establish a connection to the specified secure gateway ... The certificate on the secure gateway is invalid. A VPN connection will not be established. Debian packages usually does not install in the /opt path. This let me suppose that the program anyconnect is not from a Debian repository, but from a different source (Cisco, I suppose). If this is the case, are you using the same version of the anyconnect in both Debian 11 and Debian 12 ? drkayak99 wrote: 2023-12-16 19:44 [..] This user https://forums.freebsd.org/threads/open ... 2fa.87788/ found a way to run Cisco AnyConnect VPN with MFA on FreeBSD using openconnect-sso, but I haven't been able to adapt his approach to supply the changed useragent identification necesitated by Debian 12. Perhaps, you can see here: How to install openconnect-sso on Ubuntu 21.04 |
Good morning fellow debianautics! I'd be grateful for any help and hints regarding this issue of mine. Sorry in advance for any misunderstandings, as I am a noob regarding debian and system administration. After doing an upgrade from bullseye to bookworm (following the release notes with my best attention possible), it seems like the wifi link is not available anymore. (Not listed in "ip link", "nmtui" or "connman") Before, wifi connection worked just fine. System details Hardware Gigabit LAN (Realtek RTL8168/8111 Ethernet, 10/100/1000 Mbit/s) Intel Dual Band Wi-Fi 6 AX 200 & Bluetooth (M.2 2230) Software Code: Select all$ uname -a Linux somehost 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux $ cat /etc/debian_version 12.4 Steps I took for the upgrade: See the script recording in upgrade-bookworm.tgz (344.83 KiB) Downloaded 32 times What I have tried turning it off and on again connecting LAN via cable adding "non-free-firmware" for all applicable software repos in /etc/apt/sources.list (running the update process afterwards) Code: Select all$ rfkill list does not list wifi: So no blocking going on there. What else could I provide? Thanks for your patience! janina | Hello, janina wrote: 2024-01-07 20:20 it seems like the wifi link is not available anymore. (Not listed in "ip link", "nmtui" or "connman") Before, wifi connection worked just fine. [*] Intel Dual Band Wi-Fi 6 AX 200 & Bluetooth (M.2 2230) Therefore, it seems something about the Intel Dual Band Wi-Fi 6 AX 200 & Bluetooth (M.2 2230). I would un-install (purge) the connman package (if installed): it can interfere running together with the Network Manager. Then, I would try to configuring the network using the NetworkManager, if it is not configured in /etc/network/interface Then, I would report the details of wireless network card and IP network configuration with the following commands (as root user): Code: Select alllspci -vnn -d ::0280 ip address ip route journalctl -b -g network journalctl -b -g iwlwifi journalctl -b -g firmware |
Hello users, yesterday I have upgraded my debian system from version 12 to version 12.4 It was like a normal apt upgrade and installed a bunch of new packages, most notably a new kernel version. After restart KDE does not show any wifi icon. In linux terminal the wifi adapter has disappeared. No internet connection capability at all. I have searched for the hole day internet to try to pick up a solution. My guess is that we face a kernel issue. At the moment I have no solution but I a fix. Current fix At boot I choose to start the previous kernel, version 6.1.0-13. KDE is still useless, but from terminal, after configuring /etc/network/interfaces the wifi adpter did show up but no internet yet. I made a wpa_supplicant.conf file and then typed: sudo ip link set wlo1 down sudo ip link set wlo1 up sudo wpa_supplicant -B -iwlo1 -c/etc/wpa_supplicant/wpa_supplicant.conf sudo dhclient wlo1 and that worked. Current situation is rather akward. My current fix I think it confirms it is a kernel issue. Could it be a kernel wifi driver issue ? Am I the only one on earth to have a broken internet connection after version 12.4 upgrade? lspci shows I have wi-fi 6 AX201 (rev.20) adapter. I ask help to you debian power user to put me back happily managing wifi connections from KDE with current debian 12.4 kernel. | Hello, Take a look at this discussion for a similar issue and a similar Intel wireless network adapter: [Solved] After upgrade: No link for wifi Please, let me know. Hope this helps. |
Hi, so i followed this guide precisely to create a proxmox + debian + gnome GUI on an Asus v161 AIO. https://pve.proxmox.com/wiki/Install_Pr ... 2_Bookworm The intention is to display a home assistant dashboard using gnome gui running on top of proxmox-hosted home assistant VM The strange thing is that it's randomly losing connection after a few days, its not always the same time, sometimes 3 days, sometimes a week. Ping to other devices in the network doesn't work, but ping to home assistant VM works. Rebooting the machine solves the issue right away. My other machines on the same network (windows laptop and windows PC) don't do this. How do i troubleshoot this? 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Kernel driver in use: r8169 Kernel modules: r8169 127.0.0.1 localhost 192.168.100.91 aio.proxmox.com aio # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters SOlVED : Driver problem | that there area of the terminal you highlighted, middle click on it,open an editor, middle click in it... |
I am experiencing a strange networking issue with our EC2 server running Debian 12.2.. Servers running Debian 10 or Ubuntu 22 on the same VPC has no issue at all.. It started with random connection failures to AWS RDS database.. Further digging (and pinging) suggests that name resolution will fail every few seconds (but not DNS).. I even started a blank stock debian 12 image to reproduce this. I captured DNS traffic via tcpdump and there is *no* DNS lookup failure, so it appears the "resolution" just randomly fail - If I put the hostname-IP inside /etc/hosts, everything works fine. You can see this error after 6 successful ones and recovers after (it will fail again if I keep it going): ping: dev-aurora-1-cluster.cluster-ro-redacted.us-east-1.rds.amazonaws.com: Name or service not known Code: Select alladmin@ip-172-35-5-50:~$ function runx() { for ((n=0;n<$1;n++)); do ${*:2}; done; } admin@ip-172-35-5-50:~$ runx 100 ping -v -w 1 dev-aurora-1-cluster.cluster-ro-redacted.us-east-1.rds.amazonaws.com ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. --- ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. --- ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. --- ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. --- ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. --- ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ping: dev-aurora-1-cluster.cluster-ro-redacted.us-east-1.rds.amazonaws.com: Name or service not known ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. --- ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. --- ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms ping: sock4.fd: 3 (socktype: SOCK_RAW), sock6.fd: 4 (socktype: SOCK_RAW), hints.ai_family: AF_UNSPEC ai->ai_family: AF_INET, ai->ai_canonname: 'ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com' PING ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com (xxx.xx.4.57) 56(84) bytes of data. | Hello, mhkhung wrote: 2023-11-10 16:12 Turns out others have the same issue: https://github.com/flatcar/Flatcar/issues/374 and is supposedly a systemd issue. This workaround can be used: https://github.com/flatcar/Flatcar/issu ... -805836384 Thank your for sharing the solution to the reported issue. Your feedback could be still very useful for other Debian users and forum readers with the same issue. This is the issue report from systemd github (closed as fixed on Oct 2 2023): resolve: tolerate merging a zero-ttl RR and a nonzero-ttl RR if not mDNS #29307 You might consider opening an issue on the Debian Bug Tracking System (https://bugs.debian.org) with a reference to the upstream bug report. If I recall correctly, Debian Bookwork (12) do not install the package named "systemd-resolved" as default system resolver. Did you installed systemd-networkd manually ? I would suggest to change the subject of the first post to make it more informative to other Debian users and forum readers; for example: [Solved] Random name resolution failure with systemd-resolved (EC2 server) |
Since migrating a large forum that I administer to Discourse with Docker about 6 months ago I’ve been seeing infrequent crashes, with the cloud VM inaccessible via SSH and a kernel call trace on the virtual console. The crashes happen every 3 to 6 weeks approximately without any specific pattern. I was initially running Discourse on Clear Linux, but I started to suspect that maybe it was less stable due to all of its arcane performance optimizations, so I migrated my Discourse to Debian 12 Bookworm around the time of its initial release. Unfortunately today the Debian system had its first crash. Here’s the sequence of events: 1. Code: Select allJul 22 05:00:22 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000002 kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI kernel: CPU: 3 PID: 3235204 Comm: postmaster Not tainted 6.1.0-10-amd64 #1 Debian 6.1.37-1 kernel: Voluntary context switch within RCU read-side critical section! kernel: CPU: 3 PID: 3235204 Comm: postmaster Tainted: G D 6.1.0-10-amd64 #1 Debian 6.1.37-1 2. journalctl shows the last log entry at 06:40:50. But the OS and Discourse still kept running. The last entry was just standard chatter from the Dockerized mail agent I run on the same VM. 3. ~08:30 I checked that Discourse was up and running normally. 4. 08:46 in Discourse error log: Code: Select allUnexpected error in Message Bus : ActiveRecord::ConnectionNotEstablished : connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: could not fork new process for connection: Cannot allocate memory 5. 08:53 in Discourse error log: Code: Select allFailed to process hijacked response correctly : ActiveRecord::ConnectionNotEstablished : connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: could not fork new process for connection: Cannot allocate memory 6. 09:01 in Discourse error log: Code: Select allFailed to handle exception in exception app middleware : ActiveRecord::StatementInvalid : PG::ObjectNotInPrerequisiteState: ERROR: lost connection to parallel worker 7. Last post on Discourse was at 09:17. 8. 09:22 in Discourse error log: Code: Select all'Track Visit' is still running after 90 seconds on db default, this process may need to be restarted! 9. 09:22 in Discourse error log: Code: Select allRedis::TimeoutError (Connection timed out) 10. There were more similar Discourse logs until the time I noticed the site was down at around 11:20. When I couldn’t log in via SSH I took these screenshots from the virtual console viewer and hard-rebooted the VM: Here's the full output of the kernel oops that it self-labelled as a "BUG:" Code: Select allJul 22 05:00:22 myvm kernel: BUG: kernel NULL pointer dereference, address: 0000000000000002 Jul 22 05:00:22 myvm kernel: #PF: supervisor read access in kernel mode Jul 22 05:00:22 myvm kernel: #PF: error_code(0x0000) - not-present page Jul 22 05:00:22 myvm kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Jul 22 05:00:22 myvm kernel: CPU: 3 PID: 3235204 Comm: postmaster Not tainted 6.1.0-10-amd64 #1 Debian 6.1.37-1 Jul 22 05:00:22 myvm kernel: Hardware name: Hetzner vServer/Standard PC (Q35 + ICH9, 2009), BIOS 20171111 11/11/2017 Jul 22 05:00:22 myvm kernel: RIP: 0010:next_uptodate_page+0x45/0x1f0 Jul 22 05:00:22 myvm kernel: Code: 0f 84 2f 01 00 00 48 81 ff 06 04 00 00 0f 84 a3 00 00 00 48 81 ff 02 04 00 00 0f 84 26 01 00 00 40 f6 c7 01 0f 85 8c 00 00 00 <48> 8b 07 a8 01 0f 85 81 00 00 00 8b 47 34 85 c0 74 7a 8d 50 01 4c Jul 22 05:00:22 myvm kernel: RSP: 0000:ffffc1ae8274bcc0 EFLAGS: 00010246 Jul 22 05:00:22 myvm kernel: RAX: 0000000000000002 RBX: ffffc1ae8274bd18 RCX: 000000000000005e Jul 22 05:00:22 myvm kernel: RDX: ffffc1ae8274bd18 RSI: ffffa0210863d2b0 RDI: 0000000000000002 Jul 22 05:00:22 myvm kernel: RBP: ffffa0210863d2b0 R08: 000000000000005e R09: 000055fb22bbdfff Jul 22 05:00:22 myvm kernel: R10: 000000000000004f R11: 0000000000000000 R12: 000000000000005e Jul 22 05:00:22 myvm kernel: R13: ffffa02194ad6980 R14: ffffa0210863d2b0 R15: ffffa02118538f60 Jul 22 05:00:22 myvm kernel: FS: 00007f423625fa40(0000) GS:ffffa0226bf80000(0000) knlGS:0000000000000000 Jul 22 05:00:22 myvm kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 22 05:00:22 myvm kernel: CR2: 0000000000000002 CR3: 000000010d87e000 CR4: 0000000000350ee0 Jul 22 05:00:22 myvm kernel: Call Trace: Jul 22 05:00:22 myvm kernel: <TASK> Jul 22 05:00:22 myvm kernel: ? __die_body.cold+0x1a/0x1f Jul 22 05:00:22 myvm kernel: ? page_fault_oops+0xd2/0x2b0 Jul 22 05:00:22 myvm kernel: ? finish_task_switch.isra.0+0x9b/0x300 Jul 22 05:00:22 myvm kernel: ? exc_page_fault+0x70/0x170 Jul 22 05:00:22 myvm kernel: ? asm_exc_page_fault+0x22/0x30 Jul 22 05:00:22 myvm kernel: ? next_uptodate_page+0x45/0x1f0 Jul 22 05:00:22 myvm kernel: filemap_map_pages+0xb0/0x6e0 Jul 22 05:00:22 myvm kernel: xfs_filemap_map_pages+0x41/0x60 [xfs] Jul 22 05:00:22 myvm kernel: do_fault+0x1a7/0x410 Jul 22 05:00:22 myvm kernel: __handle_mm_fault+0x660/0xfa0 Jul 22 05:00:22 myvm kernel: handle_mm_fault+0xdb/0x2d0 Jul 22 05:00:22 myvm kernel: do_user_addr_fault+0x19c/0x570 Jul 22 05:00:22 myvm kernel: exc_page_fault+0x70/0x170 Jul 22 05:00:22 myvm kernel: asm_exc_page_fault+0x22/0x30 Jul 22 05:00:22 myvm kernel: RIP: 0033:0x7f42398b32a6 Jul 22 05:00:22 myvm kernel: Code: c7 5d 41 5c e9 3b 3d 00 00 5a 31 c0 5d 41 5c c3 0f 1f 40 00 89 f1 89 f8 48 83 e1 3f 48 83 e0 3f 83 f9 30 77 3f 83 f8 30 77 3a <66> 0f 12 0f 66 0f 12 16 66 0f 16 4f 08 66 0f 16 56 08 66 0f ef c0 Jul 22 05:00:22 myvm kernel: RSP: 002b:00007ffc8a9aae68 EFLAGS: 00010287 Jul 22 05:00:22 myvm kernel: RAX: 0000000000000001 RBX: 000055fb22b39750 RCX: 0000000000000010 Jul 22 05:00:22 myvm kernel: RDX: 0000000000000000 RSI: 00007f41b1534550 RDI: 000055fb22b59d01 Jul 22 05:00:22 myvm kernel: RBP: 0000000000000009 R08: 0000000000000000 R09: 000055fb22b39750 Jul 22 05:00:22 myvm kernel: R10: 00007f41b1534550 R11: 000000000000002c R12: 00007f42398c3180 Jul 22 05:00:22 myvm kernel: R13: 0000000000000000 R14: 0000000000000009 R15: 00007f42398c3180 Jul 22 05:00:22 myvm kernel: </TASK> Jul 22 05:00:22 myvm kernel: Modules linked in: ipt_REJECT nf_reject_ipv4 xt_multiport xt_nat xt_tcpudp veth xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc lz4 lz4_compress zram zsmalloc overlay binfmt_misc intel_rapl_msr intel_rapl_common ghash_clmulni_intel sha512_ssse3 sha512_generic iTCO_wdt intel_pmc_bxt iTCO_vendor_support virtio_rng aesni_intel crypto_simd watchdog cryptd pcspkr rng_core virtio_gpu virtio_console virtio_balloon virtio_dma_buf drm_shmem_helper drm_kms_helper button evdev joydev serio_raw sg fuse dm_mod drm loop efi_pstore configfs qemu_fw_cfg ip_tables x_tables autofs4 xfs libcrc32c crc32c_generic hid_generic usbhid hid sr_mod cdrom sd_mod t10_pi ahci crc64_rocksoft crc64 crc_t10dif libahci crct10dif_generic virtio_net net_failover virtio_scsi failover libata xhci_pci scsi_mod psmouse xhci_hcd crct10dif_pclmul crct10dif_common Jul 22 05:00:22 myvm kernel: crc32_pclmul crc32c_intel i2c_i801 i2c_smbus lpc_ich scsi_common usbcore virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev virtio usb_common virtio_ring Jul 22 05:00:22 myvm kernel: CR2: 0000000000000002 Jul 22 05:00:22 myvm kernel: ---[ end trace 0000000000000000 ]--- Jul 22 05:00:22 myvm kernel: RIP: 0010:next_uptodate_page+0x45/0x1f0 Jul 22 05:00:22 myvm kernel: Code: 0f 84 2f 01 00 00 48 81 ff 06 04 00 00 0f 84 a3 00 00 00 48 81 ff 02 04 00 00 0f 84 26 01 00 00 40 f6 c7 01 0f 85 8c 00 00 00 <48> 8b 07 a8 01 0f 85 81 00 00 00 8b 47 34 85 c0 74 7a 8d 50 01 4c Jul 22 05:00:22 myvm kernel: RSP: 0000:ffffc1ae8274bcc0 EFLAGS: 00010246 Jul 22 05:00:22 myvm kernel: RAX: 0000000000000002 RBX: ffffc1ae8274bd18 RCX: 000000000000005e Jul 22 05:00:22 myvm kernel: RDX: ffffc1ae8274bd18 RSI: ffffa0210863d2b0 RDI: 0000000000000002 Jul 22 05:00:22 myvm kernel: RBP: ffffa0210863d2b0 R08: 000000000000005e R09: 000055fb22bbdfff Jul 22 05:00:22 myvm kernel: R10: 000000000000004f R11: 0000000000000000 R12: 000000000000005e Jul 22 05:00:22 myvm kernel: R13: ffffa02194ad6980 R14: ffffa0210863d2b0 R15: ffffa02118538f60 Jul 22 05:00:22 myvm kernel: FS: 00007f423625fa40(0000) GS:ffffa0226bf80000(0000) knlGS:0000000000000000 Jul 22 05:00:22 myvm kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 22 05:00:22 myvm kernel: CR2: 0000000000000002 CR3: 000000010d87e000 CR4: 0000000000350ee0 Jul 22 05:00:22 myvm kernel: ------------[ cut here ]------------ Jul 22 05:00:22 myvm kernel: Voluntary context switch within RCU read-side critical section! Jul 22 05:00:22 myvm kernel: WARNING: CPU: 3 PID: 3235204 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x4ee/0x690 Jul 22 05:00:22 myvm kernel: Modules linked in: ipt_REJECT nf_reject_ipv4 xt_multiport xt_nat xt_tcpudp veth xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc lz4 lz4_compress zram zsmalloc overlay binfmt_misc intel_rapl_msr intel_rapl_common ghash_clmulni_intel sha512_ssse3 sha512_generic iTCO_wdt intel_pmc_bxt iTCO_vendor_support virtio_rng aesni_intel crypto_simd watchdog cryptd pcspkr rng_core virtio_gpu virtio_console virtio_balloon virtio_dma_buf drm_shmem_helper drm_kms_helper button evdev joydev serio_raw sg fuse dm_mod drm loop efi_pstore configfs qemu_fw_cfg ip_tables x_tables autofs4 xfs libcrc32c crc32c_generic hid_generic usbhid hid sr_mod cdrom sd_mod t10_pi ahci crc64_rocksoft crc64 crc_t10dif libahci crct10dif_generic virtio_net net_failover virtio_scsi failover libata xhci_pci scsi_mod psmouse xhci_hcd crct10dif_pclmul crct10dif_common Jul 22 05:00:22 myvm kernel: crc32_pclmul crc32c_intel i2c_i801 i2c_smbus lpc_ich scsi_common usbcore virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev virtio usb_common virtio_ring Jul 22 05:00:22 myvm kernel: CPU: 3 PID: 3235204 Comm: postmaster Tainted: G D 6.1.0-10-amd64 #1 Debian 6.1.37-1 Jul 22 05:00:22 myvm kernel: Hardware name: Hetzner vServer/Standard PC (Q35 + ICH9, 2009), BIOS 20171111 11/11/2017 Jul 22 05:00:22 myvm kernel: RIP: 0010:rcu_note_context_switch+0x4ee/0x690 Jul 22 05:00:22 myvm kernel: Code: 49 89 3f 49 83 bc 24 98 00 00 00 00 0f 85 66 fe ff ff e9 58 fe ff ff 48 c7 c7 68 53 70 94 c6 05 d7 0e ad 01 01 e8 d2 8e f6 ff <0f> 0b e9 70 fb ff ff a9 ff ff ff 7f 0f 84 2c fc ff ff 65 48 8b 3c Jul 22 05:00:22 myvm kernel: RSP: 0018:ffffc1ae8274bc60 EFLAGS: 00010086 Jul 22 05:00:22 myvm kernel: RAX: 0000000000000000 RBX: ffffa0226bfb1c00 RCX: 0000000000000000 Jul 22 05:00:22 myvm kernel: RDX: 0000000000000003 RSI: ffffffff9474105e RDI: 00000000ffffffff Jul 22 05:00:22 myvm kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffc1ae8274bad0 Jul 22 05:00:22 myvm kernel: R10: 0000000000000003 R11: ffffffff94ed43a8 R12: 0000000000030e40 Jul 22 05:00:22 myvm kernel: R13: ffffa02175d09980 R14: ffffc1ae8274bd50 R15: 0000000000000000 Jul 22 05:00:22 myvm kernel: FS: 0000000000000000(0000) GS:ffffa0226bf80000(0000) knlGS:0000000000000000 Jul 22 05:00:22 myvm kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 22 05:00:22 myvm kernel: CR2: 00007f41ef6dd70e CR3: 00000000059f6000 CR4: 0000000000350ee0 Jul 22 05:00:22 myvm kernel: Call Trace: Jul 22 05:00:22 myvm kernel: <TASK> Jul 22 05:00:22 myvm kernel: ? __warn+0x7d/0xc0 Jul 22 05:00:22 myvm kernel: ? rcu_note_context_switch+0x4ee/0x690 Jul 22 05:00:22 myvm kernel: ? report_bug+0xe6/0x170 Jul 22 05:00:22 myvm kernel: ? irq_work_queue+0xa/0x50 Jul 22 05:00:22 myvm kernel: ? handle_bug+0x41/0x70 Jul 22 05:00:22 myvm kernel: ? exc_invalid_op+0x13/0x60 Jul 22 05:00:22 myvm kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 22 05:00:22 myvm kernel: ? rcu_note_context_switch+0x4ee/0x690 Jul 22 05:00:22 myvm kernel: __schedule+0xac/0xa20 Jul 22 05:00:22 myvm kernel: schedule+0x5d/0xe0 Jul 22 05:00:22 myvm kernel: rwsem_down_write_slowpath+0x34e/0x730 Jul 22 05:00:22 myvm kernel: exit_mmap+0xf6/0x2f0 Jul 22 05:00:22 myvm kernel: __mmput+0x3e/0x130 Jul 22 05:00:22 myvm kernel: do_exit+0x2fc/0xb10 Jul 22 05:00:22 myvm kernel: make_task_dead+0x8d/0x90 Jul 22 05:00:22 myvm kernel: rewind_stack_and_make_dead+0x17/0x20 Jul 22 05:00:22 myvm kernel: RIP: 0033:0x7f42398b32a6 Jul 22 05:00:22 myvm kernel: Code: Unable to access opcode bytes at 0x7f42398b327c. Jul 22 05:00:22 myvm kernel: RSP: 002b:00007ffc8a9aae68 EFLAGS: 00010287 Jul 22 05:00:22 myvm kernel: RAX: 0000000000000001 RBX: 000055fb22b39750 RCX: 0000000000000010 Jul 22 05:00:22 myvm kernel: RDX: 0000000000000000 RSI: 00007f41b1534550 RDI: 000055fb22b59d01 Jul 22 05:00:22 myvm kernel: RBP: 0000000000000009 R08: 0000000000000000 R09: 000055fb22b39750 Jul 22 05:00:22 myvm kernel: R10: 00007f41b1534550 R11: 000000000000002c R12: 00007f42398c3180 Jul 22 05:00:22 myvm kernel: R13: 0000000000000000 R14: 0000000000000009 R15: 00007f42398c3180 Jul 22 05:00:22 myvm kernel: </TASK> Jul 22 05:00:22 myvm kernel: ---[ end trace 0000000000000000 ]--- I’ve been administering Linux servers for a long time, and this chain of events doesn’t make sense to me. The Discourse logs seem to be a fairly obvious indication of an out-of-memory event, and the virtual console confirms that a component of my Dockerized mail server on the same VM got axed by the OOM killer. But there is no record of that OOM action in journalctl, which apparently quit working well before the other systems started failing. The apparently first event at 05:00:22 mentions the postmaster process (from PostgreSQL in the Discourse app container) several times, but the DB didn’t go down completely until at least after 09:17 when there was a successful post on Discourse. Currently after running all day the system is showing normal memory usage, this is normally roughly where it sits at: Code: Select all#> free -m total used free shared buff/cache available Mem: 7751 4965 129 1832 4773 2785 Swap: 3875 2879 996 The only slightly uncommon thing about my configuration is that the swap space is actually via Zram instead of a swap file or swap partition. I’ve been using Zram for years and have never had a problem. Also I installed the VM from scratch with the Debian installer ISO in order to have an XFS root filesystem instead of the standard EXT4 that the cloud provider’s Debian images use. The host is Hetzner, and after my initial Clear Linux installation of Discourse I created a different VM for the migration to Debian, so presumably I’m on a different hypervisor node now. Since it's acting the same as the Clear Linux installation on a different node I don’t think it’s a hardware problem. So I wonder if this was just a simple out-of-memory condition, or have I found an edge case in the combination of kernel 6.1 + Zram + XFS + KVM/virtio ? I’d appreciate any insight you might have. | I leave it to those more experienced than me, but I would not rule out that these occasional events are caused by running user space programs. These programs overload the server's RAM for some reasons and, before/while triggering the kernel's out-of-memory killer, overload the kernel and cause kernel component malfunctions (such as the kernel's ability to fetch memory pages during memory page faults, as in the log of the above message). You may install and configure the crash program to collect more logs and kernel dumps (if any). You may install system monitoring programs (to collect data back after the issue has hit). Can you report the output of the inxi program (inxi -Fxxz) with your general software/hardware configuration ? May you share the URLs of discussions you are carrying on with other forums about this topic ? |
This one has had me perplexed for weeks. I run KDE and set up a script to trigger dark themes when the sun goes down. I know for a fact that the script runs successfully as I have to manually trigger it. Here is the script: Code: Select all#!/bin/bash # Theme Variables current_mode=$(/usr/bin/plasma-apply-colorscheme --list-schemes | /usr/bin/grep current) darkTheme=DraculaPurple konsoleID=$(/usr/bin/qdbus | /usr/bin/grep konsole | /usr/bin/cut -d- -f2) #The ID for the terminal app is randomly assigned, so I use this to grab its current ID. # Time Variables sunrise="$(/usr/bin/date -d "$(/usr/bin/curl wttr.in/Chicago?format="%S")" +%s)" sunset="$(/usr/bin/date -d "$(/usr/bin/curl wttr.in/Chicago?format="%s")" +%s)" current_time="$(/usr/bin/date +'%s')" #current_time="1695689400" #Scroll down for IF statement if [ "${current_time}" -ge "${sunset}" ] || [ "${current_time}" -lt "${sunrise}" ]; then case "$current_mode" in "$darkTheme") /usr/bin/qdbus org.kde.konsole-"$konsoleID" /Sessions/1 org.kde.konsole.Session.setProfile "NightOneDark";; *) /usr/bin/plasma-apply-colorscheme $darkTheme && /usr/bin/qdbus org.kde.konsole-"$konsoleID" /Sessions/1 org.kde.konsole.Session.setProfile "NightOneDark";; esac else /usr/bin/plasma-apply-colorscheme Summer && /usr/bin/qdbus org.kde.konsole-"$konsoleID" /Sessions/1 org.kde.konsole.Session.setProfile "Day" fi Here is my crontab entry. It's a little lengthy but it works. Basically it runs every 5 minutes, from 8-11am and from 4-7pm: Code: Select all*/5 16-19,08-11 * * * /home/M4cAttack/Scripts/NightMode_v0.8.sh >> /home/M4cAttack/Scripts/crontab.log 2>&1 Based on sudo service cron status, it is successfully triggering when expected, yet the script never seems to start (or if it starts never completes). Code: Select allOct 17 18:20:01 optiplex CRON[15897]: pam_unix(cron:session): session opened for user M4cAttack(uid=1000) by (uid=0) Oct 17 18:20:01 optiplex CRON[15900]: (M4cAttack) CMD (/home/M4cAttack/Scripts/NightMode_v0.8.sh >> /home/M4cAttack/Scripts/crontab.log 2>&1) Oct 17 18:20:01 optiplex CRON[15897]: pam_unix(cron:session): session closed for user M4cAttack Oct 17 18:25:01 optiplex CRON[16058]: pam_unix(cron:session): session opened for user M4cAttack(uid=1000) by (uid=0) Oct 17 18:25:01 optiplex CRON[16061]: (M4cAttack) CMD (/home/M4cAttack/Scripts/NightMode_v0.8.sh >> /home/M4cAttack/Scripts/crontab.log 2>&1) Oct 17 18:25:01 optiplex CRON[16058]: pam_unix(cron:session): session closed for user M4cAttack I thought it might've had something to do with the commands, so I gave them the full names (ie: grep -> /usr/bin/grep) but that didn't help. Also, I have it set up to log errors to /home/M4cAttack/Scripts/crontab.log but the log has never populated w/ data. | Hello, m4c-attack wrote: 2023-10-18 04:05 OK I haven't resolved the issue but I think I know what it is. Basically the default env variables aren't passed through to cron, I will dig around later this week for a solution and update the thread if i get lucky. Quite an interesting and recurring topic in the life of a Debian user. Yes, it depends on how the cron daemon sets up the "environment" of its jobs (the programs / scripts it starts). Cron jobs are linux processes. Each linux process has its own "environment". The "environment" is set up by the process that starts it, in this case cron. The cron manpage reports the following: ENVIRONMENT If configured in /etc/default/cron in Debian systems, the cron daemon localisation settings environment can be managed through the use of /etc/environment or through the use of /etc/default/locale with values from the latter overriding values from the former. These files are read and they will be used to setup the LANG, LC_ALL, and LC_CTYPE environment variables. These variables are then used to set the charset of mails, which defaults to 'C'. This does NOT affect the environment of tasks running under cron. For more information on how to modify the environment of tasks, consult crontab(5). The daemon will use, if present, the definition from /etc/timezone for the timezone. The environment can be redefined in user's crontab definitions but cron will only handle tasks in a single timezone. The crontab (5) manpage reports the following: [..] An active line in a crontab will be either an environment setting or a cron command. An en‐ vironment setting is of the form, name = value where the spaces around the equal-sign (=) are optional, and any subsequent non-leading spa‐ ces in value will be part of the value assigned to name. The value string may be placed in quotes (single or double, but matching) to preserve leading or trailing blanks. Several environment variables are set up automatically by the cron(8) daemon. SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd line of the crontab's owner. HOME and SHELL may be overridden by settings in the crontab; LOGNAME may not. (Another note: the LOGNAME variable is sometimes called USER on BSD systems... on these systems, USER will be set also.) In addition to LOGNAME, HOME, and SHELL, cron(8) will look at MAILTO if it has any reason to send mail as a result of running commands in ``this'' crontab. If MAILTO is defined (and non-empty), mail is sent to the user so named. If MAILTO is defined but empty (MAILTO=""), no mail will be sent. Otherwise mail is sent to the owner of the crontab. [..] Therefore, cron jobs are started by default with a very limited set of variables in their environments. You can test it running this example job: Code: Select all* * * * * env > $HOME/env.log The cron daemon will run it every minute storing the output of the env command in the file named $HOME/env.log (where $HOME is your home directory). The environment should contain the following variables (replace text in angle brackets with values in your installation): Code: Select allHOME=<YOUR_HOME_DIRECTORY> LOGNAME=<YOUR USER NAME> PATH=/usr/bin:/bin LANG=<YOUR LOCALE> SHELL=/bin/sh PWD=<JOB CURRENT WORKING DIRECTORY> Note that the cron daemon will populate the environment of its jobs using the variables in /etc/environment and /etc/default/locale (if any), too. Therefore, you can simulate the way the job is executed with the following command (with your user): Code: Select allenv -i HOME=$HOME LOGNAME=$LOGNAME PATH=/usr/bin:/bin LANG=$LANG SHELL=/bin/sh sh -c your_script.sh These errors appear running your example script as in the first post: Code: Select allqt.qpa.xcb: could not connect to display QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-aki' Could not connect to D-Bus server: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 That's why your script fails when run by cron. Hope this helps. -- Note: For those of you who may be interested, here are some references to the cron code involved: https://sources.debian.org/src/cron/3.0pl1-176/do_command.c/?hl=118#L118 https://sources.debian.org/src/cron/3.0pl1-176/do_command.c/?hl=118#L136 https://sources.debian.org/src/cron/3.0pl1-176/do_command.c/?hl=118#L335 https://sources.debian.org/src/cron/3.0pl1-176/do_command.c/?hl=118#L59 https://sources.debian.org/src/cron/3.0pl1-176/do_command.c/?hl=118#L364 |
Hi! I try to launch a script when I plug a USB drive. I've written and activated two units : dummy.path and dummy.service. Basically dummy.path launches dummy.service when a file on the disk is found. dummy.service has a oneshot type, RemainAfterExit=yes, and launches a script. It works fine the first time I plug the USB drive after a boot. But if I unplug the USB drive and plug it again the service unit is not triggered. Its status : active (exited). I have read a huge amount of doc, even the one of the freedesktop.org. I haven't found the way to activate the service when the USB drive is unplugged. I there a way to do what I try to do? (Sorry for my English. Hope I was clear) Sylvain | sylvain_48 wrote: 2023-11-10 19:23 I haven't found the way to activate the service when the USB drive is unplugged. In addition to the ambiguous unmount, I haven't found a complete foolproof solution either. |
I try to change options for auto-mounting USB flash keys, which should by done by udisks2.service. I have copied /etc/udisks2/mount_options.conf.example to mount_options.conf and uncomented and edited these lines: Code: Select alldefaults=errors=remount-ro,async,noatime,commit=1800 exfat_defaults=uid=$UID,gid=$GID,iocharset=utf8,errors=remount-ro,async,noatime,commit=1800 But after changes in the conf, I still get this line in /proc/mounts: Code: Select all/dev/sdb1 /media/maria/75F3-9167 exfat rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro 0 0 Why did not appear my options async,noatime,commit=1800 in the mounts file? (I have read, that async could be default option, so it does not appears, but has probably been applied. But commit cannot be the default option.) | Hello, ruwolf wrote: 2023-11-20 22:58 I try to change options for auto-mounting USB flash keys, which should by done by udisks2.service. I have copied /etc/udisks2/mount_options.conf.example to mount_options.conf and uncomented and edited these lines: Code: Select alldefaults=errors=remount-ro,async,noatime,commit=1800 exfat_defaults=uid=$UID,gid=$GID,iocharset=utf8,errors=remount-ro,async,noatime,commit=1800 [..] The name of the .conf file should be the "Drive:Id" property from that drive; according to udisks manual: DRIVE CONFIGURATION At start-up and when a drive is connected, udisksd(8) will apply configuration stored in the file /etc/udisks2/IDENTIFIER.conf where IDENTIFIER is the value of the Drive:Id property for the drive. If the file changes on disk its new contents will also be applied to the drive. For example, for the mounted /dev/sda block device the "Drive:Id" property should be obtainable with the following command: Code: Select alludisksctl info -b /dev/sda | grep "Id\:" In your example, you used another name for the .conf file. |
My laptop is running debian12. If I login to a Cinnamon desktop, I can play .mkv files on a Samba share. If I login to a Plasma(X11) desktop, I cannot play .mkv files on the same Samba share. Do I need some configuration change? | Hello, StevenFriedrich wrote: 2023-11-19 23:29 My laptop is running debian12. [..] If I login to a Plasma(X11) desktop, I cannot play .mkv files on the same Samba share. Do I need some configuration change? You may find some troubleshooting information here: The Smb4K Handbook |
Hello guys, Having some issues with Network-Manager which is not starting, although I strangely do still have networking. Here is the result for trying to start it Code: Select allsudo systemctl start NetworkManager Job for NetworkManager.service failed because the control process exited with error code. See "systemctl status NetworkManager.service" and "journalctl -xeu NetworkManager.service" for details. And here is the result of journalctl Code: Select alljournalctl -xeu NetworkManager.service nov 24 11:04:58 pc-quarto systemd[1]: Stopped NetworkManager.service - Network Manager. ░░ Subject: A stop job for unit NetworkManager.service has finished ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A stop job for unit NetworkManager.service has finished. ░░ ░░ The job identifier is 6531 and the job result is done. nov 24 11:04:58 pc-quarto systemd[1]: NetworkManager.service: Start request repeated too quickly. nov 24 11:04:58 pc-quarto systemd[1]: NetworkManager.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit NetworkManager.service has entered the 'failed' state with result 'exit-code'. nov 24 11:04:58 pc-quarto systemd[1]: Failed to start NetworkManager.service - Network Manager. ░░ Subject: A start job for unit NetworkManager.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit NetworkManager.service has finished with a failure. ░░ ░░ The job identifier is 6531 and the job result is failed. All I get is that this job is failing to start or finish, but not sure on what is it. Any ideas on how to solve it is greatly appreciated. | Hello, Maybe the suggested command: Code: Select allsystemctl status NetworkManager.service could give you more clues. |
I'm on Debian 12 Bookworm, and I am trying to compile and load the elants_i2c module for my currently-running kernel. This module is in-tree in the upstream kernel sources, but is not built and included in the default kernel package (linux-image-6.1.0-13-amd64). What I have done: Code: Select allsudo apt install linux-source cd && mkdir kernel && cd kernel tar xf /usr/src/linux-source-6.1.tar.xz cd linux-source-6.1/ make menuconfig # Mark drivers/input/touchscreen/elants_i2c as "M" make modules_prepare make M=drivers/input/touchscreen sudo insmod drivers/input/touchscreen/elants_i2c.ko That last insmod command gives me: Code: Select allinsmod: ERROR: could not insert module drivers/input/touchscreen/elants_i2c.ko: Invalid module format Looking back, "make M=drivers/input/touchscreen" gave the following output: Code: Select all$ make M=drivers/input/touchscreen CC [M] drivers/input/touchscreen/elants_i2c.o MODPOST drivers/input/touchscreen/Module.symvers WARNING: Module.symvers is missing. Modules may not have dependencies or modversions. You may get many unresolved symbol warnings. WARNING: modpost: "__fentry__" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "i2c_register_driver" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "i2c_transfer_buffer_flags" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "__x86_return_thunk" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "_dev_err" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "regulator_enable" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "__const_udelay" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "gpiod_set_value_cansleep" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "msleep" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: "regulator_disable" [drivers/input/touchscreen/elants_i2c.ko] undefined! WARNING: modpost: suppressed 46 unresolved symbol warnings because there were too many) LD [M] drivers/input/touchscreen/elants_i2c.ko BTF [M] drivers/input/touchscreen/elants_i2c.ko Skipping BTF generation for drivers/input/touchscreen/elants_i2c.ko due to unavailability of vmlinux I verified I'm running the same version of the kernel as the source: Code: Select allLast command had exit code: 130 at 12:01 nathan@fly:~/kernel/linux-source-6.1 $ uname -a Linux fly 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux Last command had exit code: 0 at 12:06 nathan@fly:~/kernel/linux-source-6.1 $ head Makefile # SPDX-License-Identifier: GPL-2.0 VERSION = 6 PATCHLEVEL = 1 SUBLEVEL = 55 EXTRAVERSION = NAME = Curry Ramen Any ideas what to try next? My ultimate goal is to be able to make a dkms package for this driver so when kernel updates come in, the module gets automatically recompiled and added. I want this driver because without it, my system resumes from suspend immediately without any input or keypresses. I don't want to run a custom-compiled kernel on this machine because I want regular upstream security updates from Debian stable, and compiling the entire kernel takes a very long time on this machine (around 5 hours for a "make localmodconfig" build with this module added) | You likely need to copy Module.symvers for the currently running kernel (i.e. /usr/src/linux-headers-$(uname -r)/Module.symvers) into your source tree before building. The kernel ring buffer (dmesg) usually has more detailed information on why a module couldn't be loaded, but there's also a pretty gigantic hint in that modpost output. Starting from the running config (i.e. cp /boot/config-$(uname -r) .config) before doing any make [foo] will probably save you some pain as well. |
Hello, I'm deploying Debian 12.2 on all office PCs in substitution of existing Mint 20.3 installations. PCs are Lenovo V520 and Lenovo V530. Everything works fine but, but randomly, not every day and not on all PCs, when the users turn on their PC as soon as they arrive at the office, the PC doesn't turn on; neither with power button nor triggering wakeonlan to it mac address Trying to replicate the issue booting the pc, quick user login, then shutting it down does not recreate the problem. It happens after the work day The PCs are installed via PXE + preseed config file + ansible playbook. Current kernel is 6.1.0, starting from tomorrow I'm gonna try kernel 6.4.0-12.2 from backports to see if this behavior persists How to debug a tuned of pc?! Any ideas? | Hello, laudanogi wrote: 2023-11-21 19:49 randomly, not every day and not on all PCs, when the users turn on their PC as soon as they arrive at the office, the PC doesn't turn on; neither with power button nor triggering wakeonlan to it mac address How do you boot the computer in question in the end? laudanogi wrote: 2023-11-21 19:49 How to debug a tuned of pc?! :) Any ideas? You can check system logs to verify if the computer was completely shutdown or it was not (for example, it was in a suspend or stand by mode). If it was completely shutdown, it's probably an hardware/firmware issue. |
I do not know, why my laptop cannot connect to WiFi. I have used it sometimes and it worked fine, but currently it behaves strange for me: It is power on: Code: Select all$ iwconfig wlp3s0 wlp3s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr=2347 B Fragment thr:off Power Management:on It is enabled: Code: Select all$ nmcli radio WIFI-HW WIFI WWAN-HW WWAN enabled enabled missing enabled But unavailable for unknown reason for me: Code: Select all$ nmcli device DEVICE TYPE STATE CONNECTION enp2s0 ethernet connected Wired connection 1 lo loopback connected (externally) lo wlp3s0 wifi unavailable -- Please, how to inspect the cause? | Does the laptop have a wifi enable disable key or combination that you might have hit by accident while say dusting the keyboard? Not that I've done that and spent an hour digging into wifi settings before noticing of course, but I've heard it does happen sometimes. |
Hi all. New to Debian after 20 year absence, having trouble getting wireless internet going. I have a TP-Link USB wireless adapter (realtek 8812au chip) which has been running successfully under Linux Mint. Doing sudo apt install firmware-realtek asks for the install CD, but as I burned the iso to a USB stick this isn't accepted. Is there a work around this? I tried burning a DVD image from the original iso using the same app, Balena Etcher, but it won't work for some reason. Perhaps an alternative to Etcher? I'm using a Mac. Thanks for any help. Barry | Firmware and drivers are different things. You need both. |
Hi, no trouble with my network for years then it suddenly stopped working, both the wireless and ethernet. I disconnected and reconnected, disabled and re-enabled networking, restarted NetworkManager. I switched off and rebooted. I have a Linux Mint in dual boot, rebooted from it and internet worked, but it was still "dead" when I rebooted Debian Buster. Description: When the system is booted I get the usual message "You are now connected to the Wireless network etc.". However, both Firefox and Chrome don't open any page; I always get a "no Internet" message. An attempt to sudo apt update gives a sequence of such messages as "Temporary failure resolving 'deb.debian.org'". I suspected a DNS problem and tried to ping IPs directly, but all I got for pinging, say, 8.8.8.8 was "ping: sendmsg: Operation not permitted". The only ping I successfully performed was to 127.0.0.1. Here is the output of ifconfig: Code: Select allenp8s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 48:0f:cf:dd:00:c6 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 42 bytes 3432 (3.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 42 bytes 3432 (3.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp9s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.43.112 netmask 255.255.255.0 broadcast 192.168.43.255 inet6 fe80::29ae:d303:a5ce:88fe prefixlen 64 scopeid 0x20<link> ether d8:5d:e2:1d:49:6f txqueuelen 1000 (Ethernet) RX packets 487 bytes 473544 (462.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 270 bytes 30088 (29.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 This is resolv.conf: Code: Select all# Generated by NetworkManager nameserver 192.168.43.1 Internet stopped working just after I stopped NordVpn from the console ("Nordvpn d"). I have a hunch that Nordvpn is the culprit, because it has to somehow interfere with the name service. It also happened a couple of times that I forgot to stop Nordvpn and left the PC alone doing some processing unrelated to internet, but when I got back after some hours the network wasn't working any more. This only happened with Nordvpn on and a reboot was enough to solve the problem. I tried to restart the nameservice but I am unable to find the right service; I keep being told that bind9 is not found. I think I'll keep meddling with services via systemctl, I just hope I'm not going to make things worse. Suggestions are welcome! | Well, the network is working now. The solution might be of some use to another nordvpn user that run into the same problem. First I got the list of my services: Code: Select allsystemctl list-units --type=service Even though I had stopped Nordvpn from the console, the daemon was still running: Code: Select allnordvpnd.service loaded active running NordVPN Daemon and so I stopped it: Code: Select allsudo systemctl stop nordvpnd I also restarted NetworkManager: Code: Select allsudo systemctl restart NetworkManager and I could access the Internet again, resolve names, ping, apt update etc. Then I restarted nordvpnd (fingers crossed); and the network still worked. I started nordvpn from the console ("nordvpn c") and the network was ok. I stopped Nordvpn from the console ("nordvpn d") and the network was down — same situation as described in my previous post. Everything got back to normal when I stopped the daemon: Code: Select allsudo systemctl stop nordvpn without even restarting NetworkManager. It's quite a bit annoying that I have to manually start and stop nordvpnd before and after running nordvpn, but that's it. Surely I could automate this in a simple batch, but if anyone has any hints on a more elegant way out, I'd be grateful. |
Hello, Please, give me a "rule of thumb" for SHMALL parameter (I mean which value in which scenario). OK, it is amount of shared memory (system wide, in pages). I've found so many different recommendations (50% of RAM, 90% of RAM, 2x RAM)...etc., or simply lets Kernel's default value? Thanks in advance, Leslie | Hello, dlacx wrote: 2023-11-14 20:41 Please, give me a "rule of thumb" for SHMALL parameter (I mean which value in which scenario). OK, it is amount of shared memory (system wide, in pages). I've found so many different recommendations (50% of RAM, 90% of RAM, 2x RAM)...etc., or simply lets Kernel's default value? According to [1]: Code: Select allshmall This parameter sets the total amount of shared memory pages that can be used system wide. Hence, shmall should always be at least ceil(shmmax/PAGE_SIZE). If you are not sure what the default PAGE_SIZE is on your Linux system, you can run the following command: Code: Select all# getconf PAGE_SIZE The Debian GNU/Linux kernel source code defining it is (e.g.) in https://sources.debian.org/src/linux/6.1.55-1/include/uapi/linux/shm.h/#L23: Code: Select all/* * SHMMNI, SHMMAX and SHMALL are default upper limits which can be * modified by sysctl. The SHMMAX and SHMALL values have been chosen to * be as large possible without facilitating scenarios where userspace * causes overflows when adjusting the limits via operations of the form * "retrieve current limit; add X; update limit". It is therefore not * advised to make SHMMAX and SHMALL any larger. These limits are * suitable for both 32 and 64-bit systems. */ #define SHMMIN 1 /* min shared seg size (bytes) */ #define SHMMNI 4096 /* max num of segs system wide */ #define SHMMAX (ULONG_MAX - (1UL << 24)) /* max shared seg size (bytes) */ #define SHMALL (ULONG_MAX - (1UL << 24)) /* max shm system wide (pages) */ #define SHMSEG SHMMNI /* max shared segs per process */ If you compute the SHMALL according to this definition, it should be (in HEX base): Code: Select all$ echo "obase=16; 2^64-1 - $((1<<24))" | bc FFFFFFFFFEFFFFFF The default value for Debian GNU/Linux kernel on my AMD64 / X86_64 architecture is (in pages), indeed: Code: Select all$ cat /proc/sys/kernel/shmall 18446744073692774399 $ echo "obase=16; $(cat /proc/sys/kernel/shmall)" | bc FFFFFFFFFEFFFFFF Therefore, the default value is all the virtual address space available decreased by 1<<24 memory pages: Code: Select all$ echo $((1 << 24)) 16777216 Why do you need to change the default value ? Have you special constraints ? If you need to customize it, its value probably depends on the limits you want to impose to running programs and shared memory used by them. Note: please, change the subject of the first post to make it understandable to interested viewers and forum users; for example: Linux kernel: what is the ”rule of thumb" for SHMALL parameter ? -- [1] The Linux Kernel - Documentation for /proc/sys/kernel/ |
In Debian 11, I had the following message in the logs( journalctl -u plocate-updatedb ) every day ... systemd[1]: plocate-updatedb.service: Consumed 24.073s CPU time. I lost this information when I upgraded to Debian 12. What does it mean - a different setup? - a problem with the termination of plocate-updatedb? - ? Thanks in advance for any help. | Perhaps some log level change? It's still there in bookworm Code: Select all$ journalctl -g plocate ...systemd[1]: plocate-updatedb.service: Consumed 1.032s CPU time. |
Hi All, On Debian 12, On the 24th, I have restarted the apache2 and ssh services and I attach the 2 extracts from my logs journalctl -u apache2 --since 2023-10-01 oct. 03 18:45:48 f2 systemd[1]: apache2.service: Consumed 29.990s CPU time. – Boot 6edbf711c24e4e06928315c28c280523 – oct. 22 09:09:34 f2 systemd[1]: apache2.service: Consumed 1min 56.245s CPU time. – Boot c71d9814cb68405791cf29688d7f9c5c – oct. 27 12:44:31 f2 systemd[1]: apache2.service: Consumed 37.508s CPU time. – Boot a3fece4054cd493d8f31b9b8c73c95af – oct. 29 18:59:41 f2 systemd[1]: apache2.service: Consumed 9.791s CPU time. journalctl -u ssh --since 2023-10-01 oct. 03 18:45:34 f2 systemd[1]: ssh.service: Consumed 1.025s CPU time. – Boot 6edbf711c24e4e06928315c28c280523 – oct. 17 07:53:21 f2 systemd[1]: ssh.service: Consumed 2.637s CPU time. oct. 22 09:09:24 f2 systemd[1]: ssh.service: Consumed 1.040s CPU time. – Boot f95e1300229140ea9f8f36359e043865 – nov. 24 16:12:27 f2 systemd[1]: ssh.service: Consumed 42min 38.087s CPU time. I don't understand why restarting ssh seems to have generated the last message but not apache2? Note that I then restarted ssh, which did not generate another log. PS: my initial problem is that plocate-updatedb never generates this message, whereas it used to do so systematically under Debian 11. Thank you in advance for any explanation. | Hello, pmgs wrote: 2023-11-27 17:48 On Debian 12, On the 24th, I have restarted the apache2 and ssh services and I attach the 2 extracts from my logs journalctl -u apache2 --since 2023-10-01 Code: Select alloct. 03 18:45:48 f2 systemd[1]: apache2.service: Consumed 29.990s CPU time. – Boot 6edbf711c24e4e06928315c28c280523 – oct. 22 09:09:34 f2 systemd[1]: apache2.service: Consumed 1min 56.245s CPU time. – Boot c71d9814cb68405791cf29688d7f9c5c – oct. 27 12:44:31 f2 systemd[1]: apache2.service: Consumed 37.508s CPU time. – Boot a3fece4054cd493d8f31b9b8c73c95af – oct. 29 18:59:41 f2 systemd[1]: apache2.service: Consumed 9.791s CPU time. journalctl -u ssh --since 2023-10-01 Code: Select alloct. 03 18:45:34 f2 systemd[1]: ssh.service: Consumed 1.025s CPU time. – Boot 6edbf711c24e4e06928315c28c280523 – oct. 17 07:53:21 f2 systemd[1]: ssh.service: Consumed 2.637s CPU time. oct. 22 09:09:24 f2 systemd[1]: ssh.service: Consumed 1.040s CPU time. – Boot f95e1300229140ea9f8f36359e043865 – nov. 24 16:12:27 f2 systemd[1]: ssh.service: Consumed 42min 38.087s CPU time. I don't understand why restarting ssh seems to have generated the last message but not apache2? Note that I then restarted ssh, which did not generate another log. Previous output is strange: the journalctl command is usually more verbose with the -u option. in my Debian Bookworm start/stop of ssh.service do not generate the "Consumed" log message If you look at boots ID, only the first one is the same across the two log exports. Therefore, it could be supposed that the notification of the ssh service termination did not make it to systemd (it terminated before processing it) or it was not issued at all (uncontrolled shutdown) or the ssh service was not started at all. pmgs wrote: 2023-11-27 17:48 PS: my initial problem is that plocate-updatedb never generates this message, whereas it used to do so systematically under Debian 11. That's a different topic, please open a new discussion about it. Hope this helps. --- note: please, use code tags to include commands and/or their logs in the body of a message. |
# lshw product: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz # uname -a Linux rich 5.10.0-25-amd64 #1 SMP Debian 5.10.191-1 (2023-08-16) x86_64 GNU/Linux # cat /etc/debian_version 11.7 if i type in terminal $ watch -n.1 "grep \"^[c]pu MHz\" /proc/cpuinfo" I see all threads run on 2900 MHz regardless of load (running tasks). apt install linux-cpupower # cpupower frequency-set --min 800 --max 4800 --related Setting cpu: 0 wrong, unknown or unhandled CPU? Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? What should I do to make cores work on lowest possible frequency when there are no tasks and to use all its power (frequency 4800 Mhz) on heavy load ? | Hello, C4H7Cl2O4P wrote: 2023-09-20 00:27 #Code: Select all lshw product: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz # uname -a Linux rich 5.10.0-25-amd64 #1 SMP Debian 5.10.191-1 (2023-08-16) x86_64 GNU/Linux # cat /etc/debian_version 11.7 if i type in terminal Code: Select all$ watch -n.1 "grep \"^[c]pu MHz\" /proc/cpuinfo" I see all threads run on 2900 MHz regardless of load (running tasks). Code: Select all# apt install linux-cpupower # cpupower frequency-set --min 800 --max 4800 --related Setting cpu: 0 wrong, unknown or unhandled CPU? Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? What should I do to make cores work on lowest possible frequency when there are no tasks and to use all its power (frequency 4800 Mhz) on heavy load ? Perhaps kernel 5.10.191-1 does not support the frequency governor of the Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz. What is the output of the following command ? Code: Select allcpupower frequency-info --- note: please use code tags to include commands or logs in messages. |
Each time I try to install phpMyAdmin locally on my laptop I run into the same problem. It fails: Code: Select allAll packages are up to date. root@fujitsu-lifebook-e781:/home/myuser# apt install phpmyadmin Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: dbconfig-common dbconfig-mysql default-mysql-client libconfig-inifiles-perl libdbd-mariadb-perl libdbi-perl libjs-codemirror libjs-jquery libjs-jquery-metadata libjs-jquery-mousewheel libjs-jquery-tablesorter libjs-jquery-timepicker libjs-jquery-ui libjs-sphinxdoc libjs-underscore libterm-readkey-perl libzip4 mariadb-client mariadb-client-core php-bz2 php-cli php-common php-composer-ca-bundle php-curl php-fig-http-message-util php-gd php-getallheaders php-google-recaptcha php-mariadb-mysql-kbs php-mbstring php-mcrypt php-mysql php-nikic-fast-route php-phpmyadmin-motranslator php-phpmyadmin-shapefile php-phpmyadmin-sql-parser php-psr-cache php-psr-container php-psr-http-factory php-psr-http-message php-psr-log php-slim-psr7 php-symfony-cache php-symfony-cache-contracts php-symfony-config php-symfony-dependency-injection php-symfony-deprecation-contracts php-symfony-expression-language php-symfony-filesystem php-symfony-polyfill-php80 php-symfony-service-contracts php-symfony-var-exporter php-tcpdf php-twig php-twig-i18n-extension php-webmozart-assert php-xml php-zip php8.2-bz2 php8.2-cli php8.2-common php8.2-curl php8.2-gd php8.2-mbstring php8.2-mcrypt php8.2-mysql php8.2-opcache php8.2-readline php8.2-xml php8.2-zip Suggested packages: default-mysql-server | virtual-mysql-server libmldbm-perl libnet-daemon-perl libsql-statement-perl libjs-requirejs libjs-jquery-ui-docs php-apcu php-dbase php-symfony-yaml php-symfony-finder php-symfony-proxy-manager-bridge php-imagick php-twig-doc php-pear php-recode php-gd2 php-pragmarx-google2fa-qrcode php-bacon-qr-code php-code-lts-u2f-php-server php-web-auth-webauthn-lib The following NEW packages will be installed: dbconfig-common dbconfig-mysql default-mysql-client libconfig-inifiles-perl libdbd-mariadb-perl libdbi-perl libjs-codemirror libjs-jquery libjs-jquery-metadata libjs-jquery-mousewheel libjs-jquery-tablesorter libjs-jquery-timepicker libjs-jquery-ui libjs-sphinxdoc libjs-underscore libterm-readkey-perl libzip4 mariadb-client mariadb-client-core php-bz2 php-cli php-common php-composer-ca-bundle php-curl php-fig-http-message-util php-gd php-getallheaders php-google-recaptcha php-mariadb-mysql-kbs php-mbstring php-mcrypt php-mysql php-nikic-fast-route php-phpmyadmin-motranslator php-phpmyadmin-shapefile php-phpmyadmin-sql-parser php-psr-cache php-psr-container php-psr-http-factory php-psr-http-message php-psr-log php-slim-psr7 php-symfony-cache php-symfony-cache-contracts php-symfony-config php-symfony-dependency-injection php-symfony-deprecation-contracts php-symfony-expression-language php-symfony-filesystem php-symfony-polyfill-php80 php-symfony-service-contracts php-symfony-var-exporter php-tcpdf php-twig php-twig-i18n-extension php-webmozart-assert php-xml php-zip php8.2-bz2 php8.2-cli php8.2-common php8.2-curl php8.2-gd php8.2-mbstring php8.2-mcrypt php8.2-mysql php8.2-opcache php8.2-readline php8.2-xml php8.2-zip phpmyadmin 0 upgraded, 71 newly installed, 0 to remove and 0 not upgraded. Need to get 24.3 MB of archives. After this operation, 175 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://deb.debian.org/debian bookworm/main amd64 php-common all 2:93 [13.1 kB] Get:2 http://deb.debian.org/debian bookworm/main amd64 php8.2-common amd64 8.2.7-1~deb12u1 [668 kB] Get:3 http://deb.debian.org/debian bookworm/main amd64 php8.2-opcache amd64 8.2.7-1~deb12u1 [344 kB] Get:4 http://deb.debian.org/debian bookworm/main amd64 php8.2-readline amd64 8.2.7-1~deb12u1 [12.4 kB] Get:5 http://deb.debian.org/debian bookworm/main amd64 php8.2-cli amd64 8.2.7-1~deb12u1 [1,732 kB] Get:6 http://deb.debian.org/debian bookworm/main amd64 php8.2-mcrypt amd64 3:1.0.5-4 [16.3 kB] Get:7 http://deb.debian.org/debian bookworm/main amd64 php-mcrypt amd64 3:1.0.5-4 [3,428 B] Get:8 http://deb.debian.org/debian bookworm/main amd64 dbconfig-common all 2.0.24 [592 kB] Get:9 http://deb.debian.org/debian bookworm/main amd64 libconfig-inifiles-perl all 3.000003-2 [45.9 kB] Get:10 http://deb.debian.org/debian bookworm/main amd64 mariadb-client-core amd64 1:10.11.3-1 [870 kB] Get:11 http://deb.debian.org/debian bookworm/main amd64 mariadb-client amd64 1:10.11.3-1 [2,930 kB] Get:12 http://deb.debian.org/debian bookworm/main amd64 default-mysql-client all 1.1.0 [2,852 B] Get:13 http://deb.debian.org/debian bookworm/main amd64 dbconfig-mysql all 2.0.24 [1,092 B] Get:14 http://deb.debian.org/debian bookworm/main amd64 libdbi-perl amd64 1.643-4 [773 kB] Get:15 http://deb.debian.org/debian bookworm/main amd64 libdbd-mariadb-perl amd64 1.22-1+b1 [93.8 kB] Get:16 http://deb.debian.org/debian bookworm/main amd64 libjs-codemirror all 5.65.0+~cs5.83.9-2 [774 kB] Get:17 http://deb.debian.org/debian bookworm/main amd64 libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [326 kB] Get:18 http://deb.debian.org/debian bookworm/main amd64 libjs-jquery-metadata all 12-4 [6,532 B] Get:19 http://deb.debian.org/debian bookworm/main amd64 libjs-jquery-mousewheel all 1:3.1.13-5 [7,792 B] Get:20 http://deb.debian.org/debian bookworm/main amd64 libjs-jquery-tablesorter all 1:2.31.3+dfsg1-3 [184 kB] Get:21 http://deb.debian.org/debian bookworm/main amd64 libjs-jquery-ui all 1.13.2+dfsg-1 [250 kB] Get:22 http://deb.debian.org/debian bookworm/main amd64 libjs-jquery-timepicker all 1.6.3-4 [48.4 kB] Get:23 http://deb.debian.org/debian bookworm/main amd64 libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [116 kB] Get:24 http://deb.debian.org/debian bookworm/main amd64 libjs-sphinxdoc all 5.3.0-4 [130 kB] Get:25 http://deb.debian.org/debian bookworm/main amd64 libterm-readkey-perl amd64 2.38-2+b1 [24.5 kB] Get:26 http://deb.debian.org/debian bookworm/main amd64 libzip4 amd64 1.7.3-1+b1 [55.5 kB] Get:27 http://deb.debian.org/debian bookworm/main amd64 php8.2-bz2 amd64 8.2.7-1~deb12u1 [10.6 kB] Get:28 http://deb.debian.org/debian bookworm/main amd64 php-bz2 all 2:8.2+93 [3,652 B] Get:29 http://deb.debian.org/debian bookworm/main amd64 php-cli all 2:8.2+93 [4,108 B] Get:30 http://deb.debian.org/debian bookworm/main amd64 php-composer-ca-bundle all 1.3.5-1 [11.5 kB] Get:31 http://deb.debian.org/debian bookworm/main amd64 php8.2-curl amd64 8.2.7-1~deb12u1 [35.7 kB] Get:32 http://deb.debian.org/debian bookworm/main amd64 php-curl all 2:8.2+93 [3,656 B] Get:33 http://deb.debian.org/debian bookworm/main amd64 php-fig-http-message-util all 1.1.5-2 [5,048 B] Get:34 http://deb.debian.org/debian bookworm/main amd64 php8.2-gd amd64 8.2.7-1~deb12u1 [28.6 kB] Get:35 http://deb.debian.org/debian bookworm/main amd64 php-gd all 2:8.2+93 [3,648 B] Get:36 http://deb.debian.org/debian bookworm/main amd64 php-getallheaders all 3.0.3-3 [3,032 B] Get:37 http://deb.debian.org/debian bookworm/main amd64 php-google-recaptcha all 1.2.4-5 [17.5 kB] Get:38 http://deb.debian.org/debian bookworm/main amd64 php-mariadb-mysql-kbs all 1.2.14-1 [61.1 kB] Get:39 http://deb.debian.org/debian bookworm/main amd64 php8.2-mbstring amd64 8.2.7-1~deb12u1 [444 kB] Get:40 http://deb.debian.org/debian bookworm/main amd64 php-mbstring all 2:8.2+93 [3,664 B] Get:41 http://deb.debian.org/debian bookworm/main amd64 php8.2-mysql amd64 8.2.7-1~deb12u1 [116 kB] Get:42 http://deb.debian.org/debian bookworm/main amd64 php-mysql all 2:8.2+93 [3,660 B] Get:43 http://deb.debian.org/debian bookworm/main amd64 php-nikic-fast-route all 1.3.0-4 [13.4 kB] Get:44 http://deb.debian.org/debian bookworm/main amd64 php-psr-cache all 1.0.1-3 [6,060 B] Get:45 http://deb.debian.org/debian bookworm/main amd64 php-psr-log all 1.1.4-2 [9,560 B] Get:46 http://deb.debian.org/debian bookworm/main amd64 php-symfony-cache-contracts all 2.5.2-1 [8,568 B] Get:47 http://deb.debian.org/debian bookworm/main amd64 php-symfony-deprecation-contracts all 2.5.2-1 [6,160 B] Get:48 http://deb.debian.org/debian bookworm/main amd64 php-psr-container all 1.1.2-1 [4,324 B] Get:49 http://deb.debian.org/debian bookworm/main amd64 php-symfony-service-contracts all 2.5.2-1 [10.1 kB] Get:50 http://deb.debian.org/debian bookworm/main amd64 php-symfony-var-exporter all 5.4.23+dfsg-1 [22.6 kB] Get:51 http://deb.debian.org/debian bookworm/main amd64 php-symfony-cache all 5.4.23+dfsg-1 [63.5 kB] Get:52 http://deb.debian.org/debian bookworm/main amd64 php-symfony-expression-language all 5.4.23+dfsg-1 [26.3 kB] Get:53 http://deb.debian.org/debian bookworm/main amd64 php-phpmyadmin-motranslator all 5.3.0-1 [15.7 kB] Get:54 http://deb.debian.org/debian bookworm/main amd64 php-phpmyadmin-shapefile all 3.0.1-2 [47.0 kB] Get:55 http://deb.debian.org/debian bookworm/main amd64 php-symfony-polyfill-php80 all 1.27.0-2 [11.8 kB] Get:56 http://deb.debian.org/debian bookworm/main amd64 php-phpmyadmin-sql-parser all 5.7.0-2 [88.4 kB] Get:57 http://deb.debian.org/debian bookworm/main amd64 php-psr-http-message all 1.0.1-3 [14.5 kB] Get:58 http://deb.debian.org/debian bookworm/main amd64 php-psr-http-factory all 1.0.1-3 [4,752 B] Get:59 http://deb.debian.org/debian bookworm/main amd64 php-slim-psr7 all 1.6.1-1 [18.0 kB] Get:60 http://deb.debian.org/debian bookworm/main amd64 php-symfony-filesystem all 5.4.23+dfsg-1 [27.8 kB] Get:61 http://deb.debian.org/debian bookworm/main amd64 php-symfony-config all 5.4.23+dfsg-1 [56.2 kB] Get:62 http://deb.debian.org/debian bookworm/main amd64 php-symfony-dependency-injection all 5.4.23+dfsg-1 [123 kB] Get:63 http://deb.debian.org/debian bookworm/main amd64 php-tcpdf all 6.6.2+dfsg1-1 [7,833 kB] Get:64 http://deb.debian.org/debian bookworm/main amd64 php-twig all 3.5.1-1 [86.6 kB] Get:65 http://deb.debian.org/debian bookworm/main amd64 php-twig-i18n-extension all 4.0.1-2 [9,848 B] Get:66 http://deb.debian.org/debian bookworm/main amd64 php-webmozart-assert all 1.11.0-1 [19.8 kB] Get:67 http://deb.debian.org/debian bookworm/main amd64 php8.2-xml amd64 8.2.7-1~deb12u1 [108 kB] Get:68 http://deb.debian.org/debian bookworm/main amd64 php-xml all 2:8.2+93 [3,672 B] Get:69 http://deb.debian.org/debian bookworm/main amd64 php8.2-zip amd64 8.2.7-1~deb12u1 [26.1 kB] Get:70 http://deb.debian.org/debian bookworm/main amd64 php-zip all 2:8.2+93 [3,656 B] Get:71 http://deb.debian.org/debian bookworm/main amd64 phpmyadmin all 4:5.2.1+dfsg-1 [4,825 kB] Fetched 24.3 MB in 4s (6,638 kB/s) Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package php-common. (Reading database ... 181575 files and directories currently installed.) Preparing to unpack .../php-common_2%3a93_all.deb ... Unpacking php-common (2:93) ... Selecting previously unselected package php8.2-common. Preparing to unpack .../php8.2-common_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-common (8.2.7-1~deb12u1) ... Selecting previously unselected package php8.2-opcache. Preparing to unpack .../php8.2-opcache_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-opcache (8.2.7-1~deb12u1) ... Selecting previously unselected package php8.2-readline. Preparing to unpack .../php8.2-readline_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-readline (8.2.7-1~deb12u1) ... Selecting previously unselected package php8.2-cli. Preparing to unpack .../php8.2-cli_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-cli (8.2.7-1~deb12u1) ... Setting up php-common (2:93) ... Created symlink /etc/systemd/system/timers.target.wants/phpsessionclean.timer → /lib/systemd/system/phpsessionclean.timer. Selecting previously unselected package php8.2-mcrypt. (Reading database ... 181686 files and directories currently installed.) Preparing to unpack .../00-php8.2-mcrypt_3%3a1.0.5-4_amd64.deb ... Unpacking php8.2-mcrypt (3:1.0.5-4) ... Selecting previously unselected package php-mcrypt. Preparing to unpack .../01-php-mcrypt_3%3a1.0.5-4_amd64.deb ... Unpacking php-mcrypt (3:1.0.5-4) ... Selecting previously unselected package dbconfig-common. Preparing to unpack .../02-dbconfig-common_2.0.24_all.deb ... Unpacking dbconfig-common (2.0.24) ... Selecting previously unselected package libconfig-inifiles-perl. Preparing to unpack .../03-libconfig-inifiles-perl_3.000003-2_all.deb ... Unpacking libconfig-inifiles-perl (3.000003-2) ... Selecting previously unselected package mariadb-client-core. Preparing to unpack .../04-mariadb-client-core_1%3a10.11.3-1_amd64.deb ... Unpacking mariadb-client-core (1:10.11.3-1) ... Selecting previously unselected package mariadb-client. Preparing to unpack .../05-mariadb-client_1%3a10.11.3-1_amd64.deb ... Unpacking mariadb-client (1:10.11.3-1) ... Selecting previously unselected package default-mysql-client. Preparing to unpack .../06-default-mysql-client_1.1.0_all.deb ... Unpacking default-mysql-client (1.1.0) ... Selecting previously unselected package dbconfig-mysql. Preparing to unpack .../07-dbconfig-mysql_2.0.24_all.deb ... Unpacking dbconfig-mysql (2.0.24) ... Selecting previously unselected package libdbi-perl:amd64. Preparing to unpack .../08-libdbi-perl_1.643-4_amd64.deb ... Unpacking libdbi-perl:amd64 (1.643-4) ... Selecting previously unselected package libdbd-mariadb-perl. Preparing to unpack .../09-libdbd-mariadb-perl_1.22-1+b1_amd64.deb ... Unpacking libdbd-mariadb-perl (1.22-1+b1) ... Selecting previously unselected package libjs-codemirror. Preparing to unpack .../10-libjs-codemirror_5.65.0+~cs5.83.9-2_all.deb ... Unpacking libjs-codemirror (5.65.0+~cs5.83.9-2) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../11-libjs-jquery_3.6.1+dfsg+~3.5.14-1_all.deb ... Unpacking libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Selecting previously unselected package libjs-jquery-metadata. Preparing to unpack .../12-libjs-jquery-metadata_12-4_all.deb ... Unpacking libjs-jquery-metadata (12-4) ... Selecting previously unselected package libjs-jquery-mousewheel. Preparing to unpack .../13-libjs-jquery-mousewheel_1%3a3.1.13-5_all.deb ... Unpacking libjs-jquery-mousewheel (1:3.1.13-5) ... Selecting previously unselected package libjs-jquery-tablesorter. Preparing to unpack .../14-libjs-jquery-tablesorter_1%3a2.31.3+dfsg1-3_all.deb ... Unpacking libjs-jquery-tablesorter (1:2.31.3+dfsg1-3) ... Selecting previously unselected package libjs-jquery-ui. Preparing to unpack .../15-libjs-jquery-ui_1.13.2+dfsg-1_all.deb ... Unpacking libjs-jquery-ui (1.13.2+dfsg-1) ... Selecting previously unselected package libjs-jquery-timepicker. Preparing to unpack .../16-libjs-jquery-timepicker_1.6.3-4_all.deb ... Unpacking libjs-jquery-timepicker (1.6.3-4) ... Selecting previously unselected package libjs-underscore. Preparing to unpack .../17-libjs-underscore_1.13.4~dfsg+~1.11.4-3_all.deb ... Unpacking libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Selecting previously unselected package libjs-sphinxdoc. Preparing to unpack .../18-libjs-sphinxdoc_5.3.0-4_all.deb ... Unpacking libjs-sphinxdoc (5.3.0-4) ... Selecting previously unselected package libterm-readkey-perl. Preparing to unpack .../19-libterm-readkey-perl_2.38-2+b1_amd64.deb ... Unpacking libterm-readkey-perl (2.38-2+b1) ... Selecting previously unselected package libzip4:amd64. Preparing to unpack .../20-libzip4_1.7.3-1+b1_amd64.deb ... Unpacking libzip4:amd64 (1.7.3-1+b1) ... Selecting previously unselected package php8.2-bz2. Preparing to unpack .../21-php8.2-bz2_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-bz2 (8.2.7-1~deb12u1) ... Selecting previously unselected package php-bz2. Preparing to unpack .../22-php-bz2_2%3a8.2+93_all.deb ... Unpacking php-bz2 (2:8.2+93) ... Selecting previously unselected package php-cli. Preparing to unpack .../23-php-cli_2%3a8.2+93_all.deb ... Unpacking php-cli (2:8.2+93) ... Selecting previously unselected package php-composer-ca-bundle. Preparing to unpack .../24-php-composer-ca-bundle_1.3.5-1_all.deb ... Unpacking php-composer-ca-bundle (1.3.5-1) ... Selecting previously unselected package php8.2-curl. Preparing to unpack .../25-php8.2-curl_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-curl (8.2.7-1~deb12u1) ... Selecting previously unselected package php-curl. Preparing to unpack .../26-php-curl_2%3a8.2+93_all.deb ... Unpacking php-curl (2:8.2+93) ... Selecting previously unselected package php-fig-http-message-util. Preparing to unpack .../27-php-fig-http-message-util_1.1.5-2_all.deb ... Unpacking php-fig-http-message-util (1.1.5-2) ... Selecting previously unselected package php8.2-gd. Preparing to unpack .../28-php8.2-gd_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-gd (8.2.7-1~deb12u1) ... Selecting previously unselected package php-gd. Preparing to unpack .../29-php-gd_2%3a8.2+93_all.deb ... Unpacking php-gd (2:8.2+93) ... Selecting previously unselected package php-getallheaders. Preparing to unpack .../30-php-getallheaders_3.0.3-3_all.deb ... Unpacking php-getallheaders (3.0.3-3) ... Selecting previously unselected package php-google-recaptcha. Preparing to unpack .../31-php-google-recaptcha_1.2.4-5_all.deb ... Unpacking php-google-recaptcha (1.2.4-5) ... Selecting previously unselected package php-mariadb-mysql-kbs. Preparing to unpack .../32-php-mariadb-mysql-kbs_1.2.14-1_all.deb ... Unpacking php-mariadb-mysql-kbs (1.2.14-1) ... Selecting previously unselected package php8.2-mbstring. Preparing to unpack .../33-php8.2-mbstring_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-mbstring (8.2.7-1~deb12u1) ... Selecting previously unselected package php-mbstring. Preparing to unpack .../34-php-mbstring_2%3a8.2+93_all.deb ... Unpacking php-mbstring (2:8.2+93) ... Selecting previously unselected package php8.2-mysql. Preparing to unpack .../35-php8.2-mysql_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-mysql (8.2.7-1~deb12u1) ... Selecting previously unselected package php-mysql. Preparing to unpack .../36-php-mysql_2%3a8.2+93_all.deb ... Unpacking php-mysql (2:8.2+93) ... Selecting previously unselected package php-nikic-fast-route. Preparing to unpack .../37-php-nikic-fast-route_1.3.0-4_all.deb ... Unpacking php-nikic-fast-route (1.3.0-4) ... Selecting previously unselected package php-psr-cache. Preparing to unpack .../38-php-psr-cache_1.0.1-3_all.deb ... Unpacking php-psr-cache (1.0.1-3) ... Selecting previously unselected package php-psr-log. Preparing to unpack .../39-php-psr-log_1.1.4-2_all.deb ... Unpacking php-psr-log (1.1.4-2) ... Selecting previously unselected package php-symfony-cache-contracts. Preparing to unpack .../40-php-symfony-cache-contracts_2.5.2-1_all.deb ... Unpacking php-symfony-cache-contracts (2.5.2-1) ... Selecting previously unselected package php-symfony-deprecation-contracts. Preparing to unpack .../41-php-symfony-deprecation-contracts_2.5.2-1_all.deb ... Unpacking php-symfony-deprecation-contracts (2.5.2-1) ... Selecting previously unselected package php-psr-container. Preparing to unpack .../42-php-psr-container_1.1.2-1_all.deb ... Unpacking php-psr-container (1.1.2-1) ... Selecting previously unselected package php-symfony-service-contracts. Preparing to unpack .../43-php-symfony-service-contracts_2.5.2-1_all.deb ... Unpacking php-symfony-service-contracts (2.5.2-1) ... Selecting previously unselected package php-symfony-var-exporter. Preparing to unpack .../44-php-symfony-var-exporter_5.4.23+dfsg-1_all.deb ... Unpacking php-symfony-var-exporter (5.4.23+dfsg-1) ... Selecting previously unselected package php-symfony-cache. Preparing to unpack .../45-php-symfony-cache_5.4.23+dfsg-1_all.deb ... Unpacking php-symfony-cache (5.4.23+dfsg-1) ... Selecting previously unselected package php-symfony-expression-language. Preparing to unpack .../46-php-symfony-expression-language_5.4.23+dfsg-1_all.deb ... Unpacking php-symfony-expression-language (5.4.23+dfsg-1) ... Selecting previously unselected package php-phpmyadmin-motranslator. Preparing to unpack .../47-php-phpmyadmin-motranslator_5.3.0-1_all.deb ... Unpacking php-phpmyadmin-motranslator (5.3.0-1) ... Selecting previously unselected package php-phpmyadmin-shapefile. Preparing to unpack .../48-php-phpmyadmin-shapefile_3.0.1-2_all.deb ... Unpacking php-phpmyadmin-shapefile (3.0.1-2) ... Selecting previously unselected package php-symfony-polyfill-php80. Preparing to unpack .../49-php-symfony-polyfill-php80_1.27.0-2_all.deb ... Unpacking php-symfony-polyfill-php80 (1.27.0-2) ... Selecting previously unselected package php-phpmyadmin-sql-parser. Preparing to unpack .../50-php-phpmyadmin-sql-parser_5.7.0-2_all.deb ... Unpacking php-phpmyadmin-sql-parser (5.7.0-2) ... Selecting previously unselected package php-psr-http-message. Preparing to unpack .../51-php-psr-http-message_1.0.1-3_all.deb ... Unpacking php-psr-http-message (1.0.1-3) ... Selecting previously unselected package php-psr-http-factory. Preparing to unpack .../52-php-psr-http-factory_1.0.1-3_all.deb ... Unpacking php-psr-http-factory (1.0.1-3) ... Selecting previously unselected package php-slim-psr7. Preparing to unpack .../53-php-slim-psr7_1.6.1-1_all.deb ... Unpacking php-slim-psr7 (1.6.1-1) ... Selecting previously unselected package php-symfony-filesystem. Preparing to unpack .../54-php-symfony-filesystem_5.4.23+dfsg-1_all.deb ... Unpacking php-symfony-filesystem (5.4.23+dfsg-1) ... Selecting previously unselected package php-symfony-config. Preparing to unpack .../55-php-symfony-config_5.4.23+dfsg-1_all.deb ... Unpacking php-symfony-config (5.4.23+dfsg-1) ... Selecting previously unselected package php-symfony-dependency-injection. Preparing to unpack .../56-php-symfony-dependency-injection_5.4.23+dfsg-1_all.deb ... Unpacking php-symfony-dependency-injection (5.4.23+dfsg-1) ... Selecting previously unselected package php-tcpdf. Preparing to unpack .../57-php-tcpdf_6.6.2+dfsg1-1_all.deb ... Unpacking php-tcpdf (6.6.2+dfsg1-1) ... Selecting previously unselected package php-twig. Preparing to unpack .../58-php-twig_3.5.1-1_all.deb ... Unpacking php-twig (3.5.1-1) ... Selecting previously unselected package php-twig-i18n-extension. Preparing to unpack .../59-php-twig-i18n-extension_4.0.1-2_all.deb ... Unpacking php-twig-i18n-extension (4.0.1-2) ... Selecting previously unselected package php-webmozart-assert. Preparing to unpack .../60-php-webmozart-assert_1.11.0-1_all.deb ... Unpacking php-webmozart-assert (1.11.0-1) ... Selecting previously unselected package php8.2-xml. Preparing to unpack .../61-php8.2-xml_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-xml (8.2.7-1~deb12u1) ... Selecting previously unselected package php-xml. Preparing to unpack .../62-php-xml_2%3a8.2+93_all.deb ... Unpacking php-xml (2:8.2+93) ... Selecting previously unselected package php8.2-zip. Preparing to unpack .../63-php8.2-zip_8.2.7-1~deb12u1_amd64.deb ... Unpacking php8.2-zip (8.2.7-1~deb12u1) ... Selecting previously unselected package php-zip. Preparing to unpack .../64-php-zip_2%3a8.2+93_all.deb ... Unpacking php-zip (2:8.2+93) ... Selecting previously unselected package phpmyadmin. Preparing to unpack .../65-phpmyadmin_4%3a5.2.1+dfsg-1_all.deb ... Unpacking phpmyadmin (4:5.2.1+dfsg-1) ... Setting up libconfig-inifiles-perl (3.000003-2) ... Setting up php8.2-common (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/calendar.ini with new version Creating config file /etc/php/8.2/mods-available/ctype.ini with new version Creating config file /etc/php/8.2/mods-available/exif.ini with new version Creating config file /etc/php/8.2/mods-available/fileinfo.ini with new version Creating config file /etc/php/8.2/mods-available/ffi.ini with new version Creating config file /etc/php/8.2/mods-available/ftp.ini with new version Creating config file /etc/php/8.2/mods-available/gettext.ini with new version Creating config file /etc/php/8.2/mods-available/iconv.ini with new version Creating config file /etc/php/8.2/mods-available/pdo.ini with new version Creating config file /etc/php/8.2/mods-available/phar.ini with new version Creating config file /etc/php/8.2/mods-available/posix.ini with new version Creating config file /etc/php/8.2/mods-available/shmop.ini with new version Creating config file /etc/php/8.2/mods-available/sockets.ini with new version Creating config file /etc/php/8.2/mods-available/sysvmsg.ini with new version Creating config file /etc/php/8.2/mods-available/sysvsem.ini with new version Creating config file /etc/php/8.2/mods-available/sysvshm.ini with new version Creating config file /etc/php/8.2/mods-available/tokenizer.ini with new version Setting up php8.2-mysql (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/mysqlnd.ini with new version Creating config file /etc/php/8.2/mods-available/mysqli.ini with new version Creating config file /etc/php/8.2/mods-available/pdo_mysql.ini with new version Setting up php8.2-bz2 (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/bz2.ini with new version Setting up php-tcpdf (6.6.2+dfsg1-1) ... Setting up php-bz2 (2:8.2+93) ... Setting up php-phpmyadmin-shapefile (3.0.1-2) ... Setting up php8.2-opcache (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/opcache.ini with new version Setting up libzip4:amd64 (1.7.3-1+b1) ... Setting up php8.2-readline (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/readline.ini with new version Setting up php8.2-mbstring (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/mbstring.ini with new version Setting up php-psr-container (1.1.2-1) ... Setting up libjs-jquery-mousewheel (1:3.1.13-5) ... Setting up php-getallheaders (3.0.3-3) ... Setting up dbconfig-common (2.0.24) ... Creating config file /etc/dbconfig-common/config with new version Setting up php-fig-http-message-util (1.1.5-2) ... Setting up php-mariadb-mysql-kbs (1.2.14-1) ... Setting up php-mbstring (2:8.2+93) ... Setting up mariadb-client-core (1:10.11.3-1) ... Setting up php-composer-ca-bundle (1.3.5-1) ... Setting up php8.2-curl (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/curl.ini with new version Setting up php8.2-xml (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/dom.ini with new version Creating config file /etc/php/8.2/mods-available/simplexml.ini with new version Creating config file /etc/php/8.2/mods-available/xml.ini with new version Creating config file /etc/php/8.2/mods-available/xmlreader.ini with new version Creating config file /etc/php/8.2/mods-available/xmlwriter.ini with new version Creating config file /etc/php/8.2/mods-available/xsl.ini with new version Setting up libjs-codemirror (5.65.0+~cs5.83.9-2) ... Setting up php-symfony-filesystem (5.4.23+dfsg-1) ... Setting up php-psr-cache (1.0.1-3) ... Setting up php-webmozart-assert (1.11.0-1) ... Setting up php-twig (3.5.1-1) ... Setting up php-psr-log (1.1.4-2) ... Setting up php-nikic-fast-route (1.3.0-4) ... Setting up php-symfony-polyfill-php80 (1.27.0-2) ... Setting up php8.2-gd (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/gd.ini with new version Setting up php-gd (2:8.2+93) ... Setting up php-google-recaptcha (1.2.4-5) ... Setting up php-symfony-var-exporter (5.4.23+dfsg-1) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up libterm-readkey-perl (2.38-2+b1) ... Setting up php8.2-cli (8.2.7-1~deb12u1) ... update-alternatives: using /usr/bin/php8.2 to provide /usr/bin/php (php) in auto mode update-alternatives: using /usr/bin/phar8.2 to provide /usr/bin/phar (phar) in auto mode update-alternatives: using /usr/bin/phar.phar8.2 to provide /usr/bin/phar.phar (phar.phar) in auto mode Creating config file /etc/php/8.2/cli/php.ini with new version Setting up php-psr-http-message (1.0.1-3) ... Setting up libdbi-perl:amd64 (1.643-4) ... Setting up libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Setting up php-symfony-deprecation-contracts (2.5.2-1) ... Setting up php-xml (2:8.2+93) ... Setting up php-curl (2:8.2+93) ... Setting up php-mysql (2:8.2+93) ... Setting up php-twig-i18n-extension (4.0.1-2) ... Setting up mariadb-client (1:10.11.3-1) ... Setting up php-symfony-cache-contracts (2.5.2-1) ... Setting up php8.2-zip (8.2.7-1~deb12u1) ... Creating config file /etc/php/8.2/mods-available/zip.ini with new version Setting up dbconfig-mysql (2.0.24) ... Setting up php-symfony-service-contracts (2.5.2-1) ... Setting up libdbd-mariadb-perl (1.22-1+b1) ... Setting up libjs-jquery-ui (1.13.2+dfsg-1) ... Setting up libjs-jquery-metadata (12-4) ... Setting up php-symfony-cache (5.4.23+dfsg-1) ... Setting up php-symfony-expression-language (5.4.23+dfsg-1) ... Setting up php-phpmyadmin-sql-parser (5.7.0-2) ... Setting up libjs-sphinxdoc (5.3.0-4) ... Setting up php-symfony-config (5.4.23+dfsg-1) ... Setting up php-cli (2:8.2+93) ... update-alternatives: using /usr/bin/php.default to provide /usr/bin/php (php) in auto mode update-alternatives: using /usr/bin/phar.default to provide /usr/bin/phar (phar) in auto mode update-alternatives: using /usr/bin/phar.phar.default to provide /usr/bin/phar.phar (phar.phar) in auto mode Setting up libjs-jquery-tablesorter (1:2.31.3+dfsg1-3) ... Setting up php-zip (2:8.2+93) ... Setting up libjs-jquery-timepicker (1.6.3-4) ... Setting up php8.2-mcrypt (3:1.0.5-4) ... Setting up php-psr-http-factory (1.0.1-3) ... Setting up default-mysql-client (1.1.0) ... Setting up php-symfony-dependency-injection (5.4.23+dfsg-1) ... Setting up php-slim-psr7 (1.6.1-1) ... Setting up php-phpmyadmin-motranslator (5.3.0-1) ... Setting up php-mcrypt (3:1.0.5-4) ... Setting up phpmyadmin (4:5.2.1+dfsg-1) ... dbconfig-common: writing config to /etc/dbconfig-common/phpmyadmin.conf Creating config file /etc/dbconfig-common/phpmyadmin.conf with new version Creating config file /etc/phpmyadmin/config-db.php with new version ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2). unable to connect to mysql server. error encountered creating user: ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2) dbconfig-common: phpmyadmin configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing package phpmyadmin (--configure): installed phpmyadmin package post-installation script subprocess returned error exit status 1 Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for libc-bin (2.36-9+deb12u1) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for php8.2-cli (8.2.7-1~deb12u1) ... Errors were encountered while processing: phpmyadmin E: Sub-process /usr/bin/dpkg returned an error code (1) Many years now I always finally find a cumbersome way in the end to get my localhost set-up as intended but I still don't understand what is expected of me. Isn't phpMyAdmin supposed to install all dependencies and guide me through the configuration of the database? It always seems like that isn't possible. All guides seem to recommend exactly what I am trying to do. What am I doing wrong? | do you installed mysql server? |
Hello! I have installed Debian 12 and MariaDB version 10.11.3 I am not good in text mode so I install webmin, I setup password for mysql root and everything worked just fine! After I decide that i need phpmyadmin from the beginning i have some issues to make this installation, but finally phpmyadmin installed and tested. So.. webmin is working! phpmyadmin is working! mysql -u user -p is working but when i try systemctl status mariadb i got the following Code: Select allroot@server:~# systemctl status mariadb ● mariadb.service - MariaDB 10.11.3 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled) Active: active (running) since Sat 2023-09-30 09:40:49 EEST; 1h 52min ago Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Process: 18492 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Process: 18494 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 18497 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && sy> Process: 18579 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 18581 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS) Main PID: 18568 (mariadbd) Status: "Taking your SQL requests now..." Tasks: 9 (limit: 14299) Memory: 226.1M CPU: 3.670s CGroup: /system.slice/mariadb.service └─18568 /usr/sbin/mariadbd Sep 30 09:40:49 server.1 systemd[1]: Starting mariadb.service - MariaDB 10.11.3 database server... Sep 30 09:40:49 server.1 systemd[1]: Started mariadb.service - MariaDB 10.11.3 database server. Sep 30 09:40:49 server.1 /etc/mysql/debian-start[18583]: Upgrading MySQL tables if necessary. Sep 30 09:40:49 server.1 debian-start[18595]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) Any idea how to solve this? | The specified username is not probably configured; see https://stackoverflow.com/questions/219 ... password-y |
Greetings, I have set up a Debian 12 minimal Server for my environtment and I have installed ntpsec using apt install ntp, which got me ntp ntpsec python3-ntp. then I modified the /etc/ntpsec/ntp.conf to point to my lans ntp server which serves another debian 11 with the original ntp just fine. i added the line server <myserver> iburst and the server seems to be recognized. however when i run the ntpd.service it does not update the systems time, even when i adjust it to a range well under 1000secs difference. when i shutdown the service and run an update manually with "ntpd -gq" then it gives me this really weird error: Code: Select allntpd -gq 2023-09-22T09:27:00 ntpd[956]: INIT: ntpd ntpsec-1.2.2: Starting 2023-09-22T09:27:00 ntpd[956]: INIT: Command line: ntpd -gq 2023-09-22T09:27:00 ntpd[956]: INIT: precision = 0.101 usec (-23) 2023-09-22T09:27:00 ntpd[956]: INIT: successfully locked into RAM 2023-09-22T09:27:00 ntpd[956]: CONFIG: readconfig: parsing file: /etc/ntpsec/ntp.conf 2023-09-22T09:27:00 ntpd[956]: CONFIG: restrict nopeer ignored 2023-09-22T09:27:00 ntpd[956]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature 2023-09-22T09:27:00 ntpd[956]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2023-12-28T00:00Z last=2017-01-01T00:00Z ofs=37 2023-09-22T09:27:00 ntpd[956]: INIT: Using SO_TIMESTAMPNS(ns) 2023-09-22T09:27:00 ntpd[956]: IO: Listen and drop on 0 v6wildcard [::]:123 2023-09-22T09:27:00 ntpd[956]: IO: Listen and drop on 1 v4wildcard 0.0.0.0:123 2023-09-22T09:27:00 ntpd[956]: IO: Listen normally on 2 lo 127.0.0.1:123 2023-09-22T09:27:00 ntpd[956]: IO: Listen normally on 3 ens160 10.10.200.27:123 2023-09-22T09:27:00 ntpd[956]: IO: Listen normally on 4 lo [::1]:123 2023-09-22T09:27:00 ntpd[956]: IO: Listen normally on 5 ens160 [fe80::250:56ff:fe82:e1ce%2]:123 2023-09-22T09:27:00 ntpd[956]: IO: Listening on routing socket on fd #22 for interface updates 2023-09-22T09:27:00 ntpd[956]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes 2023-09-22T09:27:00 ntpd[956]: INIT: OpenSSL 3.0.9 30 May 2023, 30000090 2023-09-22T09:27:00 ntpd[956]: NTSc: Using system default root certificates. 2023-09-22T09:27:00 ntpd[956]: statistics directory /var/log/ntpsec/ does not exist or is unwriteable, error No such file or directory 2023-09-22T09:27:01 ntpd[956]: DNS: dns_probe: time-sh.<myserver>.local, cast_flags:1, flags:20901 2023-09-22T09:27:01 ntpd[956]: DNS: dns_check: processing time-sh.<myserver>.local, 1, 20901 2023-09-22T09:27:01 ntpd[956]: DNS: Server taking: 10.10.10.244 2023-09-22T09:27:01 ntpd[956]: DNS: dns_take_status: time-sh.<myserver>.local=>good, 0 2023-09-22T09:27:11 ntpd[956]: SYNC: no servers found I don't get this as it clearly resolves my server and also manually querying the server returns a valid time. Ping also works flawlessly. Firewall shouldn't be the issue either: Code: Select alllsof -i -P -n COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ntpd 891 ntpsec 16u IPv6 12479 0t0 UDP *:123 ntpd 891 ntpsec 17u IPv4 12482 0t0 UDP *:123 ntpd 891 ntpsec 18u IPv4 12486 0t0 UDP 127.0.0.1:123 ntpd 891 ntpsec 19u IPv4 12488 0t0 UDP 10.10.200.27:123 ntpd 891 ntpsec 20u IPv6 12490 0t0 UDP [::1]:123 ntpd 891 ntpsec 21u IPv6 12492 0t0 UDP [fe80::250:56ff:fe82:e1ce]:123 Please advise me as I'm currently out of ideas what the issue might be. Thanks in advance. EDIT: just added the manual query response of my ntp server in case this is of interest: Code: Select allntpq -c rv time-sh.<myserver>.local associd=0 status=04f8 leap_none, sync_uhf_radio, 15 events, no_sys_peer, version="ntpd 4.2.8p15-mbg-03-o Fri Aug 27 10:26:49 UTC 2021 (2)", processor="i586", system="Linux/4.14.292", leap=00, stratum=1, precision=-18, rootdelay=0.0, rootdisp=0.155, refid=GPS, reftime=e8b7b7e5.096c8ade 2023-09-22T06:51:17.036Z, clock=e8b7b7e6.af0c6fc5 2023-09-22T06:51:18.683Z, peer=5676, tc=3, mintc=3, offset=0.001246, frequency=81.728, sys_jitter=0.003815, clk_jitter=0.004, clk_wander=0.0, tai=37, leapsec=201701010000, expire=202312280000, LANTIME="LANTIME/GPS170/M300/V7.06.009/SN030111200430" | @poweruser181: does the above answer from @michael_S solve your issue ? |
Hi all, I am trying to install Liquorix kernel but it fails after apt download: Code: Select allSetting up linux-image-6.5.6-1-liquorix-amd64 (6.5-7.1~bookworm) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.5.6-1-liquorix-amd64. Sign command: /lib/modules/6.5.6-1-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.6-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.5.6-1-liquorix-amd64........(bad exit status: 2) Error! Bad return status for module build on kernel: 6.5.6-1-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.5.6-1-liquorix-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.5.6-1-liquorix-amd64 (--configure): installed linux-image-6.5.6-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1 Setting up linux-headers-6.5.6-1-liquorix-amd64 (6.5-7.1~bookworm) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.5.6-1-liquorix-amd64. Sign command: /lib/modules/6.5.6-1-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.6-1-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.5.6-1-liquorix-amd64........(bad exit status: 2) Error! Bad return status for module build on kernel: 6.5.6-1-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.5.6-1-liquorix-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.5.6-1-liquorix-amd64.postinst line 11. dpkg: error processing package linux-headers-6.5.6-1-liquorix-amd64 (--configure): installed linux-headers-6.5.6-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-liquorix-amd64: linux-headers-liquorix-amd64 depends on linux-headers-6.5.6-1-liquorix-amd64 (= 6.5-7.1~bookworm); however: Package linux-headers-6.5.6-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-headers-liquorix-amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-liquorix-amd64: linux-image-liquorix-amd64 depends on linux-image-6.5.6-1-liquorix-amd64 (= 6.5-7.1~bookworm); however: Package linux-image-6.5.6-1-liquorix-amd64 is not configured yet. dpkg: error processing package linux-image-liquorix-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-6.5.6-1-liquorix-amd64 linux-headers-6.5.6-1-liquorix-amd64 linux-headers-liquorix-amd64 linux-image-liquorix-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Can anyone help in this regard? | Looks like Nvidia drivers have not been updated to work with 6.5 kernel yet. It happens regularly with kernel upgrades and you just have to wait for Nvidia to catch up. Use an older kernel until then. |
When I run the command everything seems fine but it gets stuck on 0% and show an error like this: Temporary error resolving <<deb.debian.org>> Please, I need help | Damianmg9 wrote: 2023-10-07 20:54 I reinstalled debian and this works now, the only thing I did different is that I used a wired connection instead of wireless Does the wired connection now works ? |
Hi All, I've been fighting with this all morning. I've created an isolated network following these admittedly old instructions (https://access.redhat.com/documentation ... pp_macvtap) The NICs on the guest VMs are using mactap without issue on my Debian 12 host--it doubles as my Desktop with KDE. When I enable a second NIC on any one of the guest machines and connect it to the isolated network with virt-manager I get a notice from KDE's network manager applet that mactapX has been activated (where X is whatever number the interface is). After that, the host machine loses its IPv4 connection to the WAN. IPv6 continues to work without issue. I've been able to confirm it's not a DNS issue as pinging to a known-good IP fails as well as to a hostname. I suspect that network manager isn't playing nice somehow but my google-foo is failing me about how to fix it. When I remove the isolated network interface from my VMs and restart them everything seems fine however I'm unable to communicate with them from my host and visa-versa. One of them runs my GVM/OpenVAS instance so at a minimum, I'd really like it to be able to scan the host. This is on a fresh install of Debian 12 stable. I originally had set this up under Debian 8 or 9 but for unrelated reasons decided on a fresh install for 12. Has anyone else run into this? Any advice? If you need more information please let me know. Here's the output of 'ip route list' before and after a VM with a connection to the isolated network is started: Before: Code: Select all0.0.0.0 dev macvtap3 scope link 0.0.0.0 dev macvtap2 scope link default via 192.168.0.1 dev enp4s0 <-- not the real IP but a valid IP on my LAN default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.5 metric 100 <-- not the real IP but a valid IP on my LAN 169.254.0.0/16 dev macvtap2 proto kernel scope link src 169.254.65.220 169.254.0.0/16 dev macvtap3 proto kernel scope link src 169.254.225.200 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.5 metric 100 <-- not the real IP but a valid IP on my LAN 192.168.0.1 dev enp4s0 scope link 192.168.254.0/24 dev virbr1 proto kernel scope link src 192.168.254.1 linkdown After: Code: Select all0.0.0.0 dev vnet6 scope link 0.0.0.0 dev macvtap9 scope link 0.0.0.0 dev macvtap3 scope link 0.0.0.0 dev macvtap2 scope link default dev vnet6 scope link default dev macvtap9 scope link default via 192.168.0.1 dev enp4s0 <-- not the real IP but a valid IP on my LAN default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.5 metric 100 <-- not the real IP but a valid IP on my LAN 169.254.0.0/16 dev macvtap2 proto kernel scope link src 169.254.65.220 169.254.0.0/16 dev macvtap3 proto kernel scope link src 169.254.225.200 169.254.0.0/16 dev macvtap9 proto kernel scope link src 169.254.175.213 169.254.0.0/16 dev vnet6 proto kernel scope link src 169.254.228.164 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.5 metric 100 <-- not the real IP but a valid IP on my LAN 192.168.0.1 dev enp4s0 scope link <-- not the real IP but a valid IP on my LAN 192.168.254.0/24 dev virbr1 proto kernel scope link src 192.168.254.1 | yu210148 wrote: 2023-10-09 18:42 When I enable a second NIC on any one of the guest machines This refers to vm's each with its nic a single macvtap, so host+vm1+vm2+etc, or are you saying vm1 has a macvtap and you're adding another in that same vm? yu210148 wrote: 2023-10-09 18:42 I suspect that network manager isn't playing nice somehow This would be my guess. I don't use one. |
Noob here . I was trying to enable secure boot but I came across this error. I'm at the step where I need to sign the Kernel with Sbsigntool. I'm following the Debian Wiki tutorial: https://wiki.debian.org/SecureBoot (which is very confusing) Code: Select alluser@debian:~$ sbsign --key "/var/lib/shim-signed/mok/MOK.priv" --cert "/var/lib/shim-signed/mok/MOK.pem" "/boot/vmlinuz-6.1.0-11-amd64" --output "/boot/vmlinuz-6.1.0-11-amd64.tmp" Can't load key from file '/var/lib/shim-signed/mok/MOK.priv' 40678B80A97F0000:error:8000000D:system library:BIO_new_file:Permission denied:../crypto/bio/bss_file.c:67:calling fopen(/var/lib/shim-signed/mok/MOK.priv, r) 40678B80A97F0000:error:10080002:BIO routines:BIO_new_file:system lib:../crypto/bio/bss_file.c:77: From what I've seen, this could even be a bug: Loading secureboot keys with LoadCredential does not work #1611 https://github.com/systemd/mkosi/issues/1611 execute: Chown credentials files and directories to service group #28759 https://github.com/systemd/systemd/pull/28759 I am trying to sign the Kernel and then sign the WIFI module. I already had problems with WIFI module (rtw_8723du) which had to be compiled in Kernel (?!) I got this error: Code: Select allsudo modinfo rtw_8723du modprobe: ERROR: could not insert 'rtw_8723du': Key was rejected by service I reported it here: Make sign-install - Debian 12 - linux-headers-6.1.0-11-amd64 #159 https://github.com/lwfinger/rtw88/issues/159 Then I tried to do the whole secure boot procedure again. Now I'm without WIFI, with Secure Boot enabled and a bug to resolve. I love Linux . I should try something like: Code: Select allsudo mokutil --reset Then restart my computer and ,in the BIOS MOK managerment screen, select reset MOK list. Reboot then retry from the step sign install ? Thanks --------------------------------------------------- Edit I've redone everything, but the system still exhibits strange behavior. I still can't sign the Kernel in Secure Boot or the wifi module. As for the kernel: Code: Select alluser@debian:/boot$ sudo sbverify --cert /var/lib/shim-signed/mok/mok.crt /boot/vmlinuz-6.1.0-11-amd64 Can't load certificate from file '/var/lib/shim-signed/mok/mok.crt' 40A7D7391F7F0000:error:80000002:system library:BIO_new_file:No such file or directory:../crypto/bio/bss_file.c:67:calling fopen(/var/lib/shim-signed/mok/mok.crt, r) 40A7D7391F7F0000:error:10000080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:75: Code: Select alluser@debian:~$ sudo modinfo /boot/vmlinuz-6.1.0-11-amd64 modinfo: ERROR: Module /boot/vmlinuz-6.1.0-11-amd64 not found. user@debian:~$ sudo ls /boot config-6.1.0-10-amd64 keyfile.gpg config-6.1.0-11-amd64 lost+found efi System.map-6.1.0-10-amd64 grub System.map-6.1.0-11-amd64 initrd.img-6.1.0-10-amd64 vmlinuz-6.1.0-10-amd64 initrd.img-6.1.0-11-amd64 vmlinuz-6.1.0-11-amd64 Estrange: Code: Select alluser@debian:~$ sudo ls /boot config-6.1.0-10-amd64 keyfile.gpg config-6.1.0-11-amd64 lost+found efi System.map-6.1.0-10-amd64 grub System.map-6.1.0-11-amd64 initrd.img-6.1.0-10-amd64 vmlinuz-6.1.0-10-amd64 initrd.img-6.1.0-11-amd64 vmlinuz-6.1.0-11-amd64 user@debian:~$ sudo sbverify --list /boot/vmlinuz-6.1.0-11-amd64 signature 1 image signature issuers: - /CN=Debian Secure Boot CA image signature certificates: - subject: /CN=Debian Secure Boot Signer 2022 - linux issuer: /CN=Debian Secure Boot CA signature 2 image signature issuers: - /CN=user image signature certificates: - subject: /CN=user issuer: /CN=user user@debian:~$ sudo sbverify --list /boot/vmlinuz-6.1.0-10-amd64 signature 1 image signature issuers: - /CN=Debian Secure Boot CA image signature certificates: - subject: /CN=Debian Secure Boot Signer 2022 - linux issuer: /CN=Debian Secure Boot CA As for wifi: Code: Select alluser@debian:~$ sudo modprobe rtw_8723du modprobe: ERROR: could not insert 'rtw_8723du': Key was rejected by service user@debian:~$ sudo modinfo rtw_8723du filename: /lib/modules/6.1.0-11-amd64/kernel/drivers/net/weless/realtek/rtw88/rtw_8723du.ko license: Dual BSD/GPL description: Realtek 802.11n wireless 8723du driver author: Hans Ulli Kroll <linux@ulli-kroll.de> alias: usb:v7392pD611d*dc*dsc*dp*icFFiscFFipFFin* alias: usb:v0BDApD723d*dc*dsc*dp*icFFiscFFipFFin* depends: rtw_usb,usbcore,rtw_8723d retpoline: Y name: rtw_8723du vermagic: 6.1.0-11-amd64 SMP preempt mod_unload modversion I had already reported here, but no solution: Make sign-install - Debian 12 - linux-headers-6.1.0-11-amd64 #159 https://github.com/lwfinger/rtw88/issues/159 | Hello, RZG01 wrote: 2023-08-12 15:12 ... Code: Select alluser@debian:~$ sbsign --key "/var/lib/shim-signed/mok/MOK.priv" --cert "/var/lib/shim-signed/mok/MOK.pem" "/boot/vmlinuz-6.1.0-11-amd64" --output "/boot/vmlinuz-6.1.0-11-amd64.tmp" Can't load key from file '/var/lib/shim-signed/mok/MOK.priv' 40678B80A97F0000:error:8000000D:system library:BIO_new_file:Permission denied:../crypto/bio/bss_file.c:67:calling fopen(/var/lib/shim-signed/mok/MOK.priv, r) 40678B80A97F0000:error:10080002:BIO routines:BIO_new_file:system lib:../crypto/bio/bss_file.c:77: .. Have your user the privileges to access /var/lib/shim-signed/mok/MOK.priv ? |
Dear all, I want to preserve for the posterity how I restored brightness control after upgrading from Debian 11 to 12, in case someone finds him/herself in a similar situation. I have a HP ProBook 4436s with a GPU integrated into the main CPU: "AMD A4-3300M APU with Radeon(tm) HD Graphics", now using the Kernel: Linux 6.1.0-13-amd64 (x86_64). With the upgrade to D12, the Xfce was upgraded to the v4.18, and I noticed with pleasure a "Display brightness" slider inside the power manager applet. Except that it did not do anything. Any method for changing the backlight brightness was doing nothing. Worst of all, after a suspend and resume, the brightness would be set at 100%. In the /sys/class/backlight/ folder there were two subfolders: acpi_video0 and acpi_video1, that I could affect with the commands such as Code: Select allecho 4 | sudo tee /sys/class/backlight/acpi_video1/brightness without any effect on the actual screen brightness. (for general reference on backlight management: https://wiki.archlinux.org/title/Backlight#xbacklight) The fix was: adding the kernel parameter acpi_backlight=native to the grub configuration file (/etc/default/grub) (ref: https://askubuntu.com/questions/19486/h ... -parameter) after which, the folders that appears in /sys/class/backlight/ became this one: radeon_bl0 And with that I regained control of the screen backlight with the Xfce power manager slider Cheers everyone | Trabuccodonosor wrote: 2023-10-13 11:42 Dear all, I want to preserve for the posterity how I restored brightness control after upgrading from Debian 11 to 12, in case someone finds him/herself in a similar situation. I have a HP ProBook 4436s with a GPU integrated into the main CPU: "AMD A4-3300M APU with Radeon(tm) HD Graphics", now using the Kernel: Linux 6.1.0-13-amd64 (x86_64). With the upgrade to D12, the Xfce was upgraded to the v4.18, and I noticed with pleasure a "Display brightness" slider inside the power manager applet. Except that it did not do anything. Any method for changing the backlight brightness was doing nothing. Worst of all, after a suspend and resume, the brightness would be set at 100%. In the /sys/class/backlight/ folder there were two subfolders: acpi_video0 and acpi_video1, that I could affect with the commands such as Code: Select allecho 4 | sudo tee /sys/class/backlight/acpi_video1/brightness without any effect on the actual screen brightness. (for general reference on backlight management: https://wiki.archlinux.org/title/Backlight#xbacklight) The fix was: adding the kernel parameter acpi_backlight=native to the grub configuration file (/etc/default/grub) (ref: https://askubuntu.com/questions/19486/h ... -parameter) after which, the folders that appears in /sys/class/backlight/ became this one: radeon_bl0 And with that I regained control of the screen backlight with the Xfce power manager slider :D Cheers everyone Happy you got sorted! Happy Debian ! |
system is debian 8/kde Installed cups and configured printers (all network printers) via web interface. Gui applications have no trouble printing. Installed lpr but it is not working. Here is the output of lpstat -t Code: Select allscheduler is running system default destination: HP_LaserJet_4100_Series device for HP_LaserJet_4100_Series: socket://192.168.1.237 device for HP_LaserJet_4200: socket://192.168.1.140 HP_LaserJet_4100_Series accepting requests since Wed 29 Jul 2015 03:04:36 PM CDT HP_LaserJet_4200 accepting requests since Tue 02 Jun 2015 06:37:27 PM CDT printer HP_LaserJet_4100_Series is idle. enabled since Wed 29 Jul 2015 03:04:36 PM CDT Waiting for printer to finish. printer HP_LaserJet_4200 is idle. enabled since Tue 02 Jun 2015 06:37:27 PM CDT Code: Select allls | lpr does not show any errors, but nothing prints. Here's the output of lpq: Code: Select allWarning: no daemon present Rank Owner Job Files Total Size 1st jonathan 0 (standard input) 738 bytes 2nd jonathan 1 (standard input) 447 bytes And if I read the log Code: Select alltail /var/log/lpr.log I get: Code: Select allJul 29 14:12:49 debian-jessie lpd[552]: /dev/lp0: No such file or directory Naturally I don't have a /dev/lp0 because these are all network printers. Not sure where to configure this. Searching around, somebody mentioned installing kdelibs3-cups, but I can't seem to find where to get it because apt-get install kdelibs3-cups didn't work (unable to locate package). | Well I solved my problem on my own, so for future reference I thought I'd let everyone know what I did. Rather than using lpr, I just used lp, as in: Code: Select allls | lp It works perfectly Not sure if this made a difference, but before I tried that, I removed lpr (apt-get remove lpr) and installed two other packages Code: Select allapt-get install rlpr xpp XPP offers command line printing but brings up a gui before you send the job on, and rlpr is meant to send print jobs to a remote network printer without running a local daemon. |
My web-host (Krystal) has migrated to a new server and changed its host name. I am having access problems with passwords not recognised, and have been advised to flush my DNS caches. This is not something I am used to. Rebooting the router did not work. My web searches led to the following candidate: Code: Select all ~$ resolvectl flush-caches Is this a good way to flush my DNS caches in Buster(Debian 10)? | geoffkaniuk wrote: 2023-10-20 12:18 [..] My conclusion is that rebooting the router plus changing all my relevant passwords may have been the solution. It might be that these changes take time to diffuse through the system? I consider the problem solved for now! I'm happy you got sorted. :-) 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) |
Hi guys, I have: Code: Select all# pvdisplay -v -m --- Physical volume --- PV Name /dev/sda5 VG Name SRVXXX-vg PV Size 29,52 GiB / not usable 2,00 MiB Allocatable yes (but full) PE Size 4,00 MiB Total PE 7557 Free PE 0 Allocated PE 7557 PV UUID yi52iG-4xHG-rdZV-T2bx-EZ48-itwd-XvG17c --- Physical Segments --- Physical extent 0 to 1501: Logical volume /dev/SRVXXX-LAMP01-vg/root Logical extents 0 to 1501 Physical extent 1502 to 2081: Logical volume /dev/SRVXXX-LAMP01-vg/var Logical extents 0 to 579 Physical extent 2082 to 2325: Logical volume /dev/SRVXXX-LAMP01-vg/swap_1 Logical extents 0 to 243 Physical extent 2326 to 2443: Logical volume /dev/SRVXXX-LAMP01-vg/tmp Logical extents 0 to 117 Physical extent 2444 to 7556: Logical volume /dev/SRVXXX-LAMP01-vg/home Logical extents 0 to 5112 In my past I extended the partition but this is the first time I need to decrease the home partition, I followed a lot of guides but now I have the doubt this is not allowed... GabrieleMax | Hello, I'm happy you got sorted. 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) Happy Debian ! |
Hello, I am facing an issue where my wifi randomly stops connecting to anything, but when I click the applet and the popup appears it starts working again. I couldn't find anything when searching for a solution, is this a known issue? Is there a long term solution? | There is too little info. At least post the output of Code: Select alllspci and tell us what desktop environment you use. Have you tried forgetting the connection and setting up the connection again? |
Hello, my WiFi keeps disconnecting, maybe twice or three times a day. I can't figure out what the problem is because my other devices stay connected without any problems. I've tried disconnecting and reconnecting and rebooting the router, but it still happens. Processor Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Memory 32817MB (5537MB used) Machine Type Desktop Operating System Debian GNU/Linux 12 (bookworm) Kernel Linux 6.1.0-13-amd64 (x86_64) Version #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) C Library GNU C Library / (Debian GLIBC 2.36-9+deb12u3) 2.36 | What is you WiFi network interface ? You can check with the command: Code: Select alllspci -vnn -d ::0280 |
Hi, I try to have bluetooth up and running, but I don't find what's wrong. Running Debian 11 with blueZ installed. What's wrong : Code: Select allroot@HS2-deb11:~# hcitool dev Devices: root@HS2-deb11:~# hcitool scan Device is not available: No such device My bluetooth hardware : intel integrated chipset - wifi with bluetooth network adapter 3165 Code: Select allroot@HS2-deb11:~# lspci -mmk 00:00.0 "Host bridge" "Intel Corporation" "Device 4e24" "Intel Corporation" "Device 7270" 00:02.0 "VGA compatible controller" "Intel Corporation" "Device 4e55" -r01 "Intel Corporation" "Device 2212" 00:04.0 "Signal processing controller" "Intel Corporation" "Device 4e03" "Intel Corporation" "Device 7270" 00:14.0 "USB controller" "Intel Corporation" "Device 4ded" -r01 -p30 "Intel Corporation" "Device 7270" 00:14.2 "RAM memory" "Intel Corporation" "Device 4def" -r01 "Intel Corporation" "Device 7270" 00:15.0 "Serial bus controller [0c80]" "Intel Corporation" "Device 4de8" -r01 "Intel Corporation" "Device 7270" 00:15.1 "Serial bus controller [0c80]" "Intel Corporation" "Device 4de9" -r01 "Intel Corporation" "Device 7270" 00:15.2 "Serial bus controller [0c80]" "Intel Corporation" "Device 4dea" -r01 "Intel Corporation" "Device 7270" 00:15.3 "Serial bus controller [0c80]" "Intel Corporation" "Device 4deb" -r01 "Intel Corporation" "Device 7270" 00:16.0 "Communication controller" "Intel Corporation" "Device 4de0" -r01 "Intel Corporation" "Device 7270" 00:17.0 "SATA controller" "Intel Corporation" "Device 4dd3" -r01 -p01 "Intel Corporation" "Device 7270" 00:19.0 "Serial bus controller [0c80]" "Intel Corporation" "Device 4dc5" -r01 "Intel Corporation" "Device 7270" 00:19.1 "Serial bus controller [0c80]" "Intel Corporation" "Device 4dc6" -r01 "Intel Corporation" "Device 7270" 00:1c.0 "PCI bridge" "Intel Corporation" "Device 4dbc" -r01 "" "" 00:1c.5 "PCI bridge" "Intel Corporation" "Device 4dbd" -r01 "" "" 00:1e.0 "Communication controller" "Intel Corporation" "Device 4da8" -r01 "Intel Corporation" "Device 7270" 00:1e.3 "Serial bus controller [0c80]" "Intel Corporation" "Device 4dab" -r01 "Intel Corporation" "Device 7270" 00:1f.0 "ISA bridge" "Intel Corporation" "Device 4d87" -r01 "Intel Corporation" "Device 7270" 00:1f.3 "Audio device" "Intel Corporation" "Device 4dc8" -r01 "Intel Corporation" "Device 7270" 00:1f.4 "SMBus" "Intel Corporation" "Device 4da3" -r01 "Intel Corporation" "Device 7270" 00:1f.5 "Serial bus controller [0c80]" "Intel Corporation" "Device 4da4" -r01 "Intel Corporation" "Device 7270" 01:00.0 "Network controller" "Intel Corporation" "Wireless 3165" -r81 "Intel Corporation" "Wireless 3165" 02:00.0 "Ethernet controller" "Realtek Semiconductor Co., Ltd." "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" -r15 "Realtek Semiconductor Co., Ltd." "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" My investigations Code: Select allroot@HS2-deb11:~# dmesg |grep -Ei 'blue|firm' [ 3.167181] platform regulatory.0: firmware: direct-loading firmware regulatory.db [ 3.167572] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [ 3.227523] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-7265D-29.ucode [ 3.227882] iwlwifi 0000:01:00.0: loaded firmware version 29.4063824552.0 7265D-29.ucode op_mode iwlmvm [ 3.404664] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor. [ 3.461654] Bluetooth: Core ver 2.22 [ 3.461691] Bluetooth: HCI device and connection manager initialized [ 3.461695] Bluetooth: HCI socket layer initialized [ 3.461697] Bluetooth: L2CAP socket layer initialized [ 3.461701] Bluetooth: SCO socket layer initialized [ 3.502035] Bluetooth: hci0: read Intel version: 370810011003110e32 [ 3.502037] Bluetooth: hci0: Intel device is already patched. patch num: 32 [ 3.684924] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168h-2.fw [ 3.844017] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 3.844020] Bluetooth: BNEP filters: protocol multicast [ 3.844024] Bluetooth: BNEP socket layer initialized [773077.373298] Bluetooth: HCI UART driver ver 2.3 [773077.373301] Bluetooth: HCI UART protocol H4 registered [773077.373302] Bluetooth: HCI UART protocol BCSP registered [773077.373328] Bluetooth: HCI UART protocol LL registered [773077.373329] Bluetooth: HCI UART protocol ATH3K registered [773077.373336] Bluetooth: HCI UART protocol Three-wire (H5) registered [773077.373377] Bluetooth: HCI UART protocol Intel registered [773077.373402] Bluetooth: HCI UART protocol Broadcom registered [773077.373410] Bluetooth: HCI UART protocol QCA registered [773077.373411] Bluetooth: HCI UART protocol AG6XX registered [773077.373417] Bluetooth: HCI UART protocol Marvell registered root@HS2-deb11:~# lsmod |grep hci hci_uart 159744 0 btqca 24576 1 hci_uart btrtl 28672 2 hci_uart,btusb btbcm 24576 2 hci_uart,btusb btintel 32768 2 hci_uart,btusb bluetooth 757760 30 btrtl,btqca,btintel,hci_uart,btbcm,bnep,btusb xhci_pci 24576 0 xhci_hcd 311296 1 xhci_pci usbcore 331776 6 xhci_hcd,snd_usb_audio,usbhid,snd_usbmidi_lib,btusb,xhci_pci ahci 40960 7 libahci 45056 1 ahci libata 299008 2 libahci,ahci usb_common 16384 2 xhci_hcd,usbcore root@HS2-deb11:~# bluetoothctl --version bluetoothctl: 5.55 root@HS2-deb11:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: DC:21:48:2A:A8:45 ACL MTU: 1021:5 SCO MTU: 96:6 DOWN RX bytes:2116636 acl:0 sco:0 events:74766 errors:0 TX bytes:84739 acl:0 sco:0 commands:16479 errors:0 Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT root@HS2-deb11:~# systemctl status hciuart.service Unit hciuart.service could not be found. I tried to have the hciuart service up and running, but did not find how. It's like the service is defined nowhere. Could someone give me a hand to have this bluetooth running? Thanks. | Hello, Thierry91 wrote: 2023-10-21 20:32 [..] But bluetoothctl is present and offers a lot of commands. One of these is "power" to set the power of the controller. And setting the power to "on" has solved the problem. So it means that at boot, the controller power is set to "off". Now I need to find out how to set it automatically to "on" at every boot. You can check your BIOS configuration to search for a option to activate bluetooth at boot time. Otherwise, many desktop environments have a function to launch scripts and commands when they start. Otherwise, you can create a oneshot systemd script to launch the command when the network target completes. Hope this helps. Let me know. |
I have 2 lab desktop systems running Debian 12. One is Gnome and the other is KDE. I cannot get the KDE based system to start Postfix via systemd. However I can start Postfix in the foreground from a console with "postfix start". Really stumped on this one. I have been running Postfix on Debian 10 and 11 for years on VPS's and baremetal for years. But the Gnome based system does not give me a problem. I did notice a note about postfix set-permissions being fixed in 12.1 but I am running 12.1. Code: Select all2023-08-10 13:34:43.7065 systemd[1]: Starting postfix@-.service - Postfix Mail Transport Agent (instance -)... 2023-08-10 13:34:43.7578 systemd[1]: postfix@-.service: Control process exited, code=exited, status=1/FAILURE 2023-08-10 13:34:43.7581 systemd[1]: postfix@-.service: Failed with result 'exit-code'. 2023-08-10 13:34:43.7585 systemd[1]: Failed to start postfix@-.service - Postfix Mail Transport Agent (instance -). How can I get syslog messages to be more verbose on this failure? | Hello, debian_toronto wrote: 2023-08-16 21:38 Re-installed Debian 12 from minimal net iso. Put all filesystems in one main nvme partition. Found that exim4 did not come pre-installed, so just installed postfix and created relay credentials in sasl dir for my AWS SES account. All worked fine. Thanks for reporting it. Please mark the discussion as solved adding the tag "[Solved]" at the beginning of the subject of the first post. |
Hi, I installed win11 and Debian11 in my new ASUS F515JA.. and the heat under debian is anormally highter when doing nothing while as for windows there is nearly some heat .. I upgraded BIOS to last version and installed intel microcode.. even update to last kernel 6.1 .. but still gets too hot just two minits after logging.. Ive read there is not a conlsuive solution cos it has to be with inner software propietary for manage fans or something like that.. Can you provide a solution?, thanks | i reinstalled and not happening anymore |
Hi. New to this board software so hope my formatting is proper? I had networking fine and working on Debian 10 but after a fresh installation of Bookworm, using the old interfaces config won't come up at all after reboot and using the brouted config below has both IPV4/6 working and brings the server up but on the guest machines, though V4 works, IPV6 is broken and can't access V6 networks.(I have set sysctl and resolv) I have a small /28 set of extra IP addresses and the IPV6/64 assigned. With my old operating system assigning a working IPV6 address to a VM was no problem and worked good but assigning an IPV6 address to a virtual machine is broken. This is the new, IPV6 not working for VM's current setup: GUEST /etc/network/interfaces: ------------------------------ auto enp7s0 iface enp7s0 inet static address 95.221.79.141 netmask 255.255.255.255 pointopoint 98.33.22.171 gateway 98.33.22.171 dns-nameservers 213.133.100.100 213.133.98.98 8.8.4.4 iface enp7s0 inet6 static address 2a01:49:2b4:150 netmask 64 gateway 2a01:49:2b4:2 dns-servers 2a01:4f8:0:1::add:1010 2a01:4f8:0:1::add:9999 2a01:4f8:0:1::add:9898 HOST /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback iface lo inet6 loopback auto eno1 iface eno1 inet static address 98.33.22.171 netmask 255.255.255.255 pointopoint 98.33.22.129 gateway 98.33.22.129 # up route add -net 98.33.22.128 netmask 255.255.255.192 gw 98.33.22.129 dev eno1 # iface eno1 inet6 static address 2a01:49:2b4:2 netmask 128 gateway fe80::1 dns-nameservers 2a01:4ff:ff00::add:1 2a01:4ff:ff00::add:2 # auto virpub iface virpub inet static address 98.33.22.171 netmask 255.255.255.255 bridge_ports none bridge_stp off bridge_fd 0 pre-up brctl addbr virpub up ip route add 95.221.79.128/32 dev virpub down ip route del 95.221.79.128/32 dev virpub up ip route add 95.221.79.129/32 dev virpub down ip route del 95.221.79.129/32 dev virpub iface virpub inet6 static address 2a01:49:2b4:2 netmask 64 My OLD HOST working interfaces that won't work for me at all on Bookworm: /etc/network/interfaces: ------------------------ source /etc/network/interfaces.d/* auto lo iface lo inet loopback iface lo inet6 loopback auto eno1 iface eno1 inet manual auto br0 iface br0 inet static address 98.33.22.171 netmask 255.255.255.255 network 98.33.22.128 broadcast 98.33.22.255 pointopoint 98.33.22.129 gateway 98.33.22.129 dns-nameservers 213.133.100.100 213.133.98.98 213.133.99.99 bridge_ports eno1 bridge_stp off auto br0 up ip route add 95.221.79.128/32 dev br0 down ip route del 95.221.79.128/32 dev br0 up ip route add 95.221.79.129/32 dev br0 down ip route del 95.221.79.129/32 dev br0 iface br0 inet6 static address 2a01:49:2b4:2 netmask 128 gateway fe80::1 dns-nameservers 2a01:4f8:0:1::add:1010 2a01:4f8:0:1::add:9999 2a01:4f8:0:1::add:9898 Can someone see/tell me what I'm doing wrong in either the new or old host interfaces? Thanks either way and Have a Great Day! CM | Use code tags for terminal text output. Please. |
Hi! I have been using linux for many years, but am new to Debian. I have a basic install (netinstall of Debian 12 with only system startup utitlities, plus lxde-core and xorg) on a HP Pavillion dv7-6c43cl laptop. I want to adjust the screen brightness. Most of the things I have read talk about the intel_backlight directory, but I only have the acpi_video0 directory and the brightness, actual brightness, and maxbrightness all show 0. lspci shows: VGA compatible controller:Intel Corp i915 I have tried the following: 1) added "acpi_backlight=video" or "acpi_backlight=vendor" to GRUB 2) installed xbacklight (when trying to use it, I receive a message that says "no outputs have backlight property" 3) installed brightnessctl (trying to use this affects the acpi_video0 device, but doesn't change the brightness). Does anyone have any suggestions? I have some linux knowledge, but am not an expert, so as much detail as possible of what to change and where to change it would be much appreciated. Thank you! | Please use code tags for terminal text. |
Hi, So I have Debian 12 + XFCE on an Asus v161 aio kiosk machine, installed PVE on top of it to run home assistant vm, The xfce is needed to run home assistant lovelace. And also since the aio has internal speaker I intend to use it for home assistant notifications using vlc audio telnet. The machine logged in as non root "aio" username running this from putty from other machine works without issue Code: Select all/usr/bin/vlc -I telnet --telnet-host 192.168.100.92:8123 --telnet-password=admin --telnet-port=4212 The unit systemd is as follows : Code: Select all[Unit] Description=VLC_Audio After=network-online.target [Service] ExecStart=/usr/bin/vlc -I telnet --telnet-host 192.168.100.92:8123 --telnet-password=admin --telnet-port=4212 User=aio Group=aio Type=notify Restart=always [Install] WantedBy=default.target But starting the service fails with the following error : Code: Select allaio@aio:~/.config/systemd/user$ systemctl --user enable vlc_audio.service Created symlink /home/aio/.config/systemd/user/default.target.wants/vlc_audio.service → /home/aio/.config/systemd/user/vlc_audio.service. aio@aio:~/.config/systemd/user$ systemctl --user start vlc_audio.service Job for vlc_audio.service failed because the control process exited with error code. See "systemctl --user status vlc_audio.service" and "journalctl --user -xeu vlc_audio.service" for details. aio@aio:~/.config/systemd/user$ systemctl --user status vlc_audio.service × vlc_audio.service - VLC_Audio Loaded: loaded (/home/aio/.config/systemd/user/vlc_audio.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2023-08-19 18:40:51 WIB; 12s ago Process: 11532 ExecStart=/usr/bin/vlc -I telnet --telnet-host 192.168.100.92:8123 --telnet-password=admi> Main PID: 11532 (code=exited, status=216/GROUP) CPU: 0 Aug 19 18:40:51 aio systemd[4767]: vlc_audio.service: Scheduled restart job, restart counter is at 5. Aug 19 18:40:51 aio systemd[4767]: Stopped vlc_audio.service - VLC_Audio. Aug 19 18:40:51 aio systemd[4767]: vlc_audio.service: Start request repeated too quickly. Aug 19 18:40:51 aio systemd[4767]: vlc_audio.service: Failed with result 'exit-code'. Aug 19 18:40:51 aio systemd[4767]: Failed to start vlc_audio.service - VLC_Audio. any thoughts? | Hello, cemara wrote: 2023-08-19 14:21 [...] Code: Select allaio@aio:~/.config/systemd/user$ systemctl --user status vlc_audio.service × vlc_audio.service - VLC_Audio Loaded: loaded (/home/aio/.config/systemd/user/vlc_audio.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2023-08-19 18:40:51 WIB; 12s ago Process: 11532 ExecStart=/usr/bin/vlc -I telnet --telnet-host 192.168.100.92:8123 --telnet-password=admi> Main PID: 11532 (code=exited, status=216/GROUP) CPU: 0 Aug 19 18:40:51 aio systemd[4767]: vlc_audio.service: Scheduled restart job, restart counter is at 5. Aug 19 18:40:51 aio systemd[4767]: Stopped vlc_audio.service - VLC_Audio. Aug 19 18:40:51 aio systemd[4767]: vlc_audio.service: Start request repeated too quickly. Aug 19 18:40:51 aio systemd[4767]: vlc_audio.service: Failed with result 'exit-code'. Aug 19 18:40:51 aio systemd[4767]: Failed to start vlc_audio.service - VLC_Audio. any thoughts? According to the man page of systemd.exec, the systemd exit code code=exited, status=216/GROUP means: Code: Select allTable 9. systemd-specific exit codes ┌──────────┬──────────────────────────────┬─────────────────────────────────────────────┐ │Exit Code │ Symbolic Name │ Description │ ├──────────┼──────────────────────────────┼─────────────────────────────────────────────┤ │216 │ EXIT_GROUP │ Failed to determine or change group │ │ │ │ credentials. See │ │ │ │ Group=/SupplementaryGroups= above. │ ├──────────┼──────────────────────────────┼─────────────────────────────────────────────┤ Therefore, it seems that there's a something wrong in setting the group that the service runs as. Does the group exist ? Is the user a member of it ? Hope this help. |
Today's updates (which include kernel package linux-image-6.1.0-11-amd64-6.1.38-3.amd64) break my system. Thankfully, a quick reboot with the previous kernel and running a restore from the most recent timeshift snapshot got me back online. After installing today's updates, on reboot, lightdm.service fails to start because the Nvidia kernel modules were not compiled for the new kernel. Does anyone know how I can quickly fix this so that I can install the updates successfully? | Which kernel did you upgrade from? If you hadn't previously run the upgrade from 6.1.0.9.x it may be the raspi-firmware bug - viewtopic.php?t=155245 Also please post more info about your system. You can do that by installing inxi and post Code: Select allinxi -CGSxxz |
Hello and thanks in advance! I'm using Debian 12 in a ThinkPad T14 Gen 2 AMD. The problem I'm facing is "random" disconnects from the Wifi although after a couple of seconds (maybe a minute) it get connected again. Any idea of what could be happening? Some info (let me know if I should provide more): Code: Select all ~$ uname -a Linux thinkpad-t14 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux With Realtek and `rtw89_8852ae` driver: Code: Select all ~$ lspci -knn | grep Net -A2 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852AE 802.11ax PCIe Wireless Network Adapter [10ec:8852] Subsystem: Lenovo RTL8852AE 802.11ax PCIe Wireless Network Adapter [17aa:4852] Kernel driver in use: rtw89_8852ae Kernel modules: rtw89_8852ae journalctl Code: Select all ~$ sudo journalctl |grep -i wlp3s0 -A10 Aug 23 08:58:31 thinkpad-t14 kernel: wlp3s0: deauthenticated from b8:d5:26:da:27:42 (Reason: 3=DEAUTH_LEAVING) Aug 23 08:58:31 thinkpad-t14 kernel: rtw89_8852ae 0000:03:00.0: timed out to flush queues Aug 23 08:58:31 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=b8:d5:26:da:27:42 reason=3 Aug 23 08:58:31 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 08:58:31 thinkpad-t14 NetworkManager[886]: <info> [1692773911.8763] device (wlp3s0): supplicant interface state: completed -> disconnected Aug 23 08:58:31 thinkpad-t14 NetworkManager[886]: <info> [1692773911.8763] device (p2p-dev-wlp3s0): supplicant management interface state: completed -> disconnected Aug 23 08:58:32 thinkpad-t14 NetworkManager[886]: <info> [1692773912.0090] device (wlp3s0): supplicant interface state: disconnected -> scanning Aug 23 08:58:32 thinkpad-t14 NetworkManager[886]: <info> [1692773912.0091] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning Aug 23 08:58:32 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Aug 23 08:58:32 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Aug 23 08:58:33 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Aug 23 08:58:33 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Aug 23 08:58:35 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN Aug 23 08:58:35 thinkpad-t14 wpa_supplicant[887]: wlp3s0: SME: Trying to authenticate with b8:d5:26:da:27:41 (SSID='TMNL-DA2741' freq=2462 MHz) Aug 23 08:58:35 thinkpad-t14 kernel: wlp3s0: authenticate with b8:d5:26:da:27:41 Aug 23 08:58:35 thinkpad-t14 NetworkManager[886]: <info> [1692773915.8870] device (wlp3s0): supplicant interface state: scanning -> authenticating Aug 23 08:58:35 thinkpad-t14 NetworkManager[886]: <info> [1692773915.8870] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> authenticating Aug 23 08:58:35 thinkpad-t14 kernel: wlp3s0: send auth to b8:d5:26:da:27:41 (try 1/3) Aug 23 08:58:35 thinkpad-t14 wpa_supplicant[887]: wlp3s0: Trying to associate with b8:d5:26:da:27:41 (SSID='TMNL-DA2741' freq=2462 MHz) Aug 23 08:58:35 thinkpad-t14 kernel: wlp3s0: authenticated Aug 23 08:58:35 thinkpad-t14 kernel: wlp3s0: associate with b8:d5:26:da:27:41 (try 1/3) Aug 23 08:58:35 thinkpad-t14 NetworkManager[886]: <info> [1692773915.8959] device (wlp3s0): supplicant interface state: authenticating -> associating Aug 23 08:58:35 thinkpad-t14 NetworkManager[886]: <info> [1692773915.8959] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating Aug 23 08:58:35 thinkpad-t14 kernel: wlp3s0: RX AssocResp from b8:d5:26:da:27:41 (capab=0x1c11 status=0 aid=1) Aug 23 08:58:35 thinkpad-t14 wpa_supplicant[887]: RRM: Ignoring radio measurement request: Not associated Aug 23 08:58:36 thinkpad-t14 wpa_supplicant[887]: wlp3s0: Associated with b8:d5:26:da:27:41 Aug 23 08:58:36 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Aug 23 08:58:36 thinkpad-t14 kernel: wlp3s0: associated Aug 23 08:58:36 thinkpad-t14 kernel: wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by b8:d5:26:da:27:41 Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.0249] device (wlp3s0): supplicant interface state: associating -> 4way_handshake Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.0249] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> 4way_handshake Aug 23 08:58:36 thinkpad-t14 wpa_supplicant[887]: wlp3s0: WPA: Key negotiation completed with b8:d5:26:da:27:41 [PTK=CCMP GTK=CCMP] Aug 23 08:58:36 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to b8:d5:26:da:27:41 completed [id=0 id_str=] Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.1038] device (wlp3s0): supplicant interface state: 4way_handshake -> completed Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.1042] device (wlp3s0): ip:dhcp4: restarting Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.1336] dhcp4 (wlp3s0): canceled DHCP transaction Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.1336] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds) Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.1336] dhcp4 (wlp3s0): state changed no lease Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.1337] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds) Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.1339] device (p2p-dev-wlp3s0): supplicant management interface state: 4way_handshake -> completed Aug 23 08:58:36 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-36 noise=9999 txrate=216000 Aug 23 08:58:36 thinkpad-t14 NetworkManager[886]: <info> [1692773916.3552] dhcp4 (wlp3s0): state changed new lease, address=192.168.1.125 Aug 23 08:58:36 thinkpad-t14 dbus-daemon[818]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=886 comm="/usr/sbin/NetworkManager --no-daemon") Aug 23 08:58:36 thinkpad-t14 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Aug 23 08:58:36 thinkpad-t14 dbus-daemon[818]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Aug 23 08:58:36 thinkpad-t14 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Aug 23 08:58:39 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 08:58:46 thinkpad-t14 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 23 08:58:50 thinkpad-t14 sudo[8227]: pdelboca : TTY=pts/1 ; PWD=/home/pdelboca ; USER=root ; COMMAND=/usr/bin/journalctl Aug 23 08:58:50 thinkpad-t14 sudo[8227]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Aug 23 08:58:53 thinkpad-t14 wpa_supplicant[887]: wlp3s0: WNM: Preferred List Available Aug 23 08:58:53 thinkpad-t14 wpa_supplicant[887]: wlp3s0: SME: Trying to authenticate with b8:d5:26:da:27:42 (SSID='TMNL-DA2741' freq=5520 MHz) Aug 23 08:58:54 thinkpad-t14 kernel: wlp3s0: disconnect from AP b8:d5:26:da:27:41 for new auth to b8:d5:26:da:27:42 Aug 23 08:58:54 thinkpad-t14 kernel: wlp3s0: authenticate with b8:d5:26:da:27:42 Aug 23 08:58:54 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.2959] device (wlp3s0): supplicant interface state: completed -> authenticating Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.2960] device (p2p-dev-wlp3s0): supplicant management interface state: completed -> authenticating Aug 23 08:58:54 thinkpad-t14 wpa_supplicant[887]: wlp3s0: Trying to associate with b8:d5:26:da:27:42 (SSID='TMNL-DA2741' freq=5520 MHz) Aug 23 08:58:54 thinkpad-t14 kernel: wlp3s0: send auth to b8:d5:26:da:27:42 (try 1/3) Aug 23 08:58:54 thinkpad-t14 kernel: wlp3s0: authenticated Aug 23 08:58:54 thinkpad-t14 kernel: wlp3s0: associate with b8:d5:26:da:27:42 (try 1/3) Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.3010] device (wlp3s0): supplicant interface state: authenticating -> associating Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.3010] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating Aug 23 08:58:54 thinkpad-t14 kernel: wlp3s0: RX ReassocResp from b8:d5:26:da:27:42 (capab=0x1931 status=0 aid=4) Aug 23 08:58:54 thinkpad-t14 wpa_supplicant[887]: wlp3s0: Associated with b8:d5:26:da:27:42 Aug 23 08:58:54 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Aug 23 08:58:54 thinkpad-t14 kernel: wlp3s0: associated Aug 23 08:58:54 thinkpad-t14 wpa_supplicant[887]: wlp3s0: WPA: Key negotiation completed with b8:d5:26:da:27:42 [PTK=CCMP GTK=CCMP] Aug 23 08:58:54 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to b8:d5:26:da:27:42 completed [id=0 id_str=] Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.4272] device (wlp3s0): supplicant interface state: associating -> completed Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.4273] device (wlp3s0): ip:dhcp4: restarting Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.4655] dhcp4 (wlp3s0): canceled DHCP transaction Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.4655] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds) Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.4655] dhcp4 (wlp3s0): state changed no lease Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.4656] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds) Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.4656] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> completed Aug 23 08:58:54 thinkpad-t14 wpa_supplicant[887]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-34 noise=9999 txrate=585000 Aug 23 08:58:54 thinkpad-t14 NetworkManager[886]: <info> [1692773934.7603] dhcp4 (wlp3s0): state changed new lease, address=192.168.1.125 Aug 23 08:58:54 thinkpad-t14 dbus-daemon[818]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=886 comm="/usr/sbin/NetworkManager --no-daemon") Aug 23 08:58:54 thinkpad-t14 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Aug 23 08:58:54 thinkpad-t14 dbus-daemon[818]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Aug 23 08:58:54 thinkpad-t14 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. dmesg: Code: Select all~$ sudo dmesg [ 2183.063883] rtw89_8852ae 0000:03:00.0: FW status = 0x33001100 [ 2183.063891] rtw89_8852ae 0000:03:00.0: FW BADADDR = 0x0 [ 2183.063895] rtw89_8852ae 0000:03:00.0: FW EPC/RA = 0x0 [ 2183.063898] rtw89_8852ae 0000:03:00.0: FW MISC = 0xb898f053 [ 2183.063901] rtw89_8852ae 0000:03:00.0: R_AX_HALT_C2H = 0x10 [ 2183.063904] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO = 0x43000050 [ 2183.063911] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe89 [ 2183.063928] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe8f [ 2183.063942] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 2183.063956] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fea5 [ 2183.063970] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe8d [ 2183.063983] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898febb [ 2183.063997] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff7b [ 2183.064012] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 2183.064025] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe8f [ 2183.064039] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fea7 [ 2183.064054] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff7f [ 2183.064067] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff7f [ 2183.064080] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 2183.064093] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 2183.064107] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff91 [ 2183.064118] rtw89_8852ae 0000:03:00.0: ---> err=0x10 [ 2183.064121] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO =0x43000050 [ 2183.064123] rtw89_8852ae 0000:03:00.0: R_AX_CMAC_ERR_ISR =0x00000000 [ 2183.064125] rtw89_8852ae 0000:03:00.0: R_AX_DMAC_ERR_ISR =0x00000000 [ 2183.064128] rtw89_8852ae 0000:03:00.0: R_AX_RPQ_RXBD_IDX =0x003d003d [ 2183.064130] rtw89_8852ae 0000:03:00.0: R_AX_DBG_ERR_FLAG=0x00000000 [ 2183.064132] rtw89_8852ae 0000:03:00.0: R_AX_LBC_WATCHDOG=0x00000081 [ 2183.064145] rtw89_8852ae 0000:03:00.0: quota lost! [ 2183.064150] rtw89_8852ae 0000:03:00.0: DLE group0 empty: 0xffffffff [ 2183.064154] rtw89_8852ae 0000:03:00.0: quota6 rsv/use: 0x137/0x316 [ 2183.064157] rtw89_8852ae 0000:03:00.0: [PLE][CMAC0_RX]min_pgnum=0x164 [ 2183.064157] rtw89_8852ae 0000:03:00.0: [PLE][CMAC0_RX]max_pgnum=0x44d [ 2183.064160] rtw89_8852ae 0000:03:00.0: R_AX_HOST_DISPATCHER_ALWAYS_IMR=0x0c000161 [ 2183.064166] rtw89_8852ae 0000:03:00.0: R_AX_HOST_DISPATCHER_ALWAYS_ISR=0x00000000 [ 2183.064168] rtw89_8852ae 0000:03:00.0: R_AX_CPU_DISPATCHER_ALWAYS_IMR=0x04000062 [ 2183.064170] rtw89_8852ae 0000:03:00.0: R_AX_CPU_DISPATCHER_ALWAYS_ISR=0x00000000 [ 2183.064173] rtw89_8852ae 0000:03:00.0: R_AX_OTHER_DISPATCHER_ALWAYS_IMR=0x00000000 [ 2183.064175] rtw89_8852ae 0000:03:00.0: R_AX_OTHER_DISPATCHER_ALWAYS_ISR=0x00000000 [ 2183.064175] rtw89_8852ae 0000:03:00.0: <--- [ 2183.064176] rtw89_8852ae 0000:03:00.0: SER catches error: 0x10 [ 2183.064304] rtw89_8852ae 0000:03:00.0: FW status = 0x33001100 [ 2183.064307] rtw89_8852ae 0000:03:00.0: FW BADADDR = 0x0 [ 2183.064310] rtw89_8852ae 0000:03:00.0: FW EPC/RA = 0x0 [ 2183.064313] rtw89_8852ae 0000:03:00.0: FW MISC = 0xb898f053 [ 2183.064315] rtw89_8852ae 0000:03:00.0: R_AX_HALT_C2H = 0x1001 [ 2183.064318] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO = 0x43000050 [ 2183.064324] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898feb5 [ 2183.064337] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff9f [ 2183.064350] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffa3 [ 2183.064364] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffa1 [ 2183.064377] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe87 [ 2183.064390] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe87 [ 2183.064403] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe7f [ 2183.064416] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe7d [ 2183.064430] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffb3 [ 2183.064443] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffad [ 2183.064456] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffa9 [ 2183.064469] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffa9 [ 2183.064482] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff8f [ 2183.064495] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff8d [ 2183.064509] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffa1 [ 2183.064521] rtw89_8852ae 0000:03:00.0: SER catches error: 0x1001 [ 2183.064853] rtw89_8852ae 0000:03:00.0: FW status = 0x33008100 [ 2183.064858] rtw89_8852ae 0000:03:00.0: FW BADADDR = 0x0 [ 2183.064860] rtw89_8852ae 0000:03:00.0: FW EPC/RA = 0x0 [ 2183.064863] rtw89_8852ae 0000:03:00.0: FW MISC = 0xb898e663 [ 2183.064866] rtw89_8852ae 0000:03:00.0: R_AX_HALT_C2H = 0x1002 [ 2183.064868] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO = 0x43000050 [ 2183.064874] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89b51bb [ 2183.064888] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c1be1 [ 2183.064902] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb893a5e5 [ 2183.064915] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c1c37 [ 2183.064928] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c1bfd [ 2183.064941] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c0e1f [ 2183.064954] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c0de9 [ 2183.064968] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c0db9 [ 2183.064981] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c0da1 [ 2183.064994] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89b42e1 [ 2183.065007] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89b519d [ 2183.065021] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89b519b [ 2183.065034] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89b42d7 [ 2183.065047] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89386a3 [ 2183.065060] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89394a3 [ 2183.065072] rtw89_8852ae 0000:03:00.0: SER catches error: 0x1002 [ 2183.163130] rtw89_8852ae 0000:03:00.0: c2h class 1 func 3 not support [ 3179.799774] rtw89_8852ae 0000:03:00.0: FW status = 0xbb001100 [ 3179.799786] rtw89_8852ae 0000:03:00.0: FW BADADDR = 0x0 [ 3179.799791] rtw89_8852ae 0000:03:00.0: FW EPC/RA = 0x0 [ 3179.799795] rtw89_8852ae 0000:03:00.0: FW MISC = 0xb898f053 [ 3179.799799] rtw89_8852ae 0000:03:00.0: R_AX_HALT_C2H = 0x10 [ 3179.799803] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO = 0x44000069 [ 3179.799811] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe7d [ 3179.799830] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff9f [ 3179.799846] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fea3 [ 3179.799861] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff9f [ 3179.799876] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898feb5 [ 3179.799891] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff99 [ 3179.799907] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff83 [ 3179.799922] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898feb1 [ 3179.799937] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff99 [ 3179.799952] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe7f [ 3179.799967] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe95 [ 3179.799982] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff7f [ 3179.799997] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 3179.800012] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 3179.800027] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 3179.800040] rtw89_8852ae 0000:03:00.0: ---> err=0x10 [ 3179.800043] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO =0x44000069 [ 3179.800047] rtw89_8852ae 0000:03:00.0: R_AX_CMAC_ERR_ISR =0x00000000 [ 3179.800051] rtw89_8852ae 0000:03:00.0: R_AX_DMAC_ERR_ISR =0x00000000 [ 3179.800054] rtw89_8852ae 0000:03:00.0: R_AX_RPQ_RXBD_IDX =0x00490049 [ 3179.800058] rtw89_8852ae 0000:03:00.0: R_AX_DBG_ERR_FLAG=0x00000000 [ 3179.800061] rtw89_8852ae 0000:03:00.0: R_AX_LBC_WATCHDOG=0x00000081 [ 3179.800064] rtw89_8852ae 0000:03:00.0: quota lost! [ 3179.800071] rtw89_8852ae 0000:03:00.0: DLE group0 empty: 0xffffffff [ 3179.800077] rtw89_8852ae 0000:03:00.0: quota6 rsv/use: 0x13c/0x311 [ 3179.800080] rtw89_8852ae 0000:03:00.0: [PLE][CMAC0_RX]min_pgnum=0x164 [ 3179.800082] rtw89_8852ae 0000:03:00.0: [PLE][CMAC0_RX]max_pgnum=0x44d [ 3179.800086] rtw89_8852ae 0000:03:00.0: R_AX_HOST_DISPATCHER_ALWAYS_IMR=0x0c000161 [ 3179.800166] rtw89_8852ae 0000:03:00.0: R_AX_HOST_DISPATCHER_ALWAYS_ISR=0x00000000 [ 3179.800170] rtw89_8852ae 0000:03:00.0: R_AX_CPU_DISPATCHER_ALWAYS_IMR=0x04000062 [ 3179.800173] rtw89_8852ae 0000:03:00.0: R_AX_CPU_DISPATCHER_ALWAYS_ISR=0x00000000 [ 3179.800176] rtw89_8852ae 0000:03:00.0: R_AX_OTHER_DISPATCHER_ALWAYS_IMR=0x00000000 [ 3179.800180] rtw89_8852ae 0000:03:00.0: R_AX_OTHER_DISPATCHER_ALWAYS_ISR=0x00000000 [ 3179.800182] rtw89_8852ae 0000:03:00.0: <--- [ 3179.800184] rtw89_8852ae 0000:03:00.0: SER catches error: 0x10 [ 3179.844949] rtw89_8852ae 0000:03:00.0: firmware failed to ack for entering ps mode [ 3179.848380] rtw89_8852ae 0000:03:00.0: FW status = 0xbb001100 [ 3179.848390] rtw89_8852ae 0000:03:00.0: FW BADADDR = 0x0 [ 3179.848395] rtw89_8852ae 0000:03:00.0: FW EPC/RA = 0x0 [ 3179.848399] rtw89_8852ae 0000:03:00.0: FW MISC = 0xb898f053 [ 3179.848403] rtw89_8852ae 0000:03:00.0: R_AX_HALT_C2H = 0x1001 [ 3179.848406] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO = 0x44000069 [ 3179.848414] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fea3 [ 3179.848514] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898febf [ 3179.848530] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff7d [ 3179.848545] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe91 [ 3179.848560] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fea7 [ 3179.848575] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff7d [ 3179.848590] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff95 [ 3179.848605] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffad [ 3179.848620] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff7d [ 3179.848635] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff91 [ 3179.848650] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ffa5 [ 3179.848665] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fe8d [ 3179.848680] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898fea1 [ 3179.848695] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898feb9 [ 3179.848710] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb898ff9f [ 3179.848722] rtw89_8852ae 0000:03:00.0: SER catches error: 0x1001 [ 3179.848993] rtw89_8852ae 0000:03:00.0: FW status = 0xbb008100 [ 3179.849001] rtw89_8852ae 0000:03:00.0: FW BADADDR = 0x0 [ 3179.849005] rtw89_8852ae 0000:03:00.0: FW EPC/RA = 0x0 [ 3179.849009] rtw89_8852ae 0000:03:00.0: FW MISC = 0xb898e663 [ 3179.849012] rtw89_8852ae 0000:03:00.0: R_AX_HALT_C2H = 0x1002 [ 3179.849015] rtw89_8852ae 0000:03:00.0: R_AX_SER_DBG_INFO = 0x44000069 [ 3179.849022] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89355ab [ 3179.849037] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89362cb [ 3179.849051] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb897cebf [ 3179.849064] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb893a683 [ 3179.849078] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb893a669 [ 3179.849091] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c42f8 [ 3179.849105] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb893a697 [ 3179.849118] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c1ec3 [ 3179.849131] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb897bdad [ 3179.849144] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb8937281 [ 3179.849158] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb893a619 [ 3179.849171] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89b51cb [ 3179.849184] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb897beaf [ 3179.849198] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89c0e57 [ 3179.849211] rtw89_8852ae 0000:03:00.0: [ERR]fw PC = 0xb89356bc [ 3179.849222] rtw89_8852ae 0000:03:00.0: SER catches error: 0x1002 [ 3179.849264] rtw89_8852ae 0000:03:00.0: c2h class 1 func 3 not support [ 3279.157311] wlp3s0: deauthenticated from b8:d5:26:da:27:42 (Reason: 3=DEAUTH_LEAVING) [ 3279.588342] rtw89_8852ae 0000:03:00.0: timed out to flush queues [ 3283.918329] wlp3s0: authenticate with b8:d5:26:da:27:41 [ 3284.036182] wlp3s0: send auth to b8:d5:26:da:27:41 (try 1/3) [ 3284.040413] wlp3s0: authenticated [ 3284.044127] wlp3s0: associate with b8:d5:26:da:27:41 (try 1/3) [ 3284.054826] wlp3s0: RX AssocResp from b8:d5:26:da:27:41 (capab=0x1c11 status=0 aid=1) [ 3284.168688] wlp3s0: associated [ 3284.168952] wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by b8:d5:26:da:27:41 [ 3302.196191] wlp3s0: disconnect from AP b8:d5:26:da:27:41 for new auth to b8:d5:26:da:27:42 [ 3302.321314] wlp3s0: authenticate with b8:d5:26:da:27:42 [ 3302.446017] wlp3s0: send auth to b8:d5:26:da:27:42 (try 1/3) [ 3302.447602] wlp3s0: authenticated [ 3302.448103] wlp3s0: associate with b8:d5:26:da:27:42 (try 1/3) [ 3302.451538] wlp3s0: RX ReassocResp from b8:d5:26:da:27:42 (capab=0x1931 status=0 aid=4) [ 3302.564561] wlp3s0: associated | "ps mode" may be power saving. You can make a config file to disable power saving for wifi. Do you use NetworkManager? Maybe check /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf I'm not absolutely sure about this as I don't use wifi on my main system. |
Sorry about this probably very easy question, but networking is not my specialty. OS: Debian 12 with KDE Plasma. I used the netinstall iso. Hardware: Lenovo ThinkPad X270. Code: Select all00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 Problem: WiFi works fine, but Ethernet does not work when I put the computer in the docking station. Here is the network interface: Code: Select allip link show enp0s31f6 2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 54:e1:ad:69:12:45 brd ff:ff:ff:ff:ff:ff /etc/network/interfaces looks like this: Code: Select all# The loopback network interface auto lo iface lo inet loopback This brings the interface up and working Code: Select all# dhclient enp0s31f6 How can I make Ethernet work automatically when I dock my laptop? I guess I could write a script to execute this command whenever the computer is docked, but there is probably an easier way to do this..? Edit: Ethernet works fine if I boot directly from the docking station. The problem is that the Ethernet connection is unresponsive (=no data) when WiFi has been used. WiFi works as normal. From the log: Code: Select allaug. 29 14:18:08 debian-mini NetworkManager[703]: <info> [1693311488.9832] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') aug. 29 14:18:08 debian-mini NetworkManager[703]: <info> [1693311488.9838] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') aug. 29 14:18:08 debian-mini NetworkManager[703]: <info> [1693311488.9849] manager: NetworkManager state is now CONNECTED_GLOBAL aug. 29 14:18:08 debian-mini NetworkManager[703]: <info> [1693311488.9882] device (enp0s31f6): Activation: successful, device activated. aug. 29 14:18:08 debian-mini nm-dispatcher[4853]: req:1 'dhcp4-change' [enp0s31f6], "/etc/NetworkManager/dispatcher.d/99tlp-rdw-nm": complete: failed with Script '/etc/NetworkManager/dispatcher.d/99tlp-rdw-nm' exited with status 2. aug. 29 14:18:08 debian-mini nm-dispatcher[4858]: /etc/NetworkManager/dispatcher.d/99tlp-rdw-nm: 14: .: cannot open /usr/share/tlp/tlp-func-base: No such file aug. 29 14:18:08 debian-mini NetworkManager[703]: <warn> [1693311488.9995] dispatcher: (47) /etc/NetworkManager/dispatcher.d/99tlp-rdw-nm failed (failed): Script '/etc/NetworkManager/dispatcher.d/99tlp-rdw-nm' exited with status 2. aug. 29 14:18:09 debian-mini plasmashell[1145]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x556921661510) QQmlContext(0x55691f37de50) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/G> aug. 29 14:18:09 debian-mini plasmashell[1145]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x556921661510) QQmlContext(0x55691f37de50) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/G> aug. 29 14:18:09 debian-mini nm-dispatcher[4905]: /etc/NetworkManager/dispatcher.d/99tlp-rdw-nm: 14: .: cannot open /usr/share/tlp/tlp-func-base: No such file aug. 29 14:18:09 debian-mini nm-dispatcher[4853]: req:3 'up' [enp0s31f6], "/etc/NetworkManager/dispatcher.d/99tlp-rdw-nm": complete: failed with Script '/etc/NetworkManager/dispatcher.d/99tlp-rdw-nm' exited with status 2. aug. 29 14:18:09 debian-mini NetworkManager[703]: <warn> [1693311489.0924] dispatcher: (49) /etc/NetworkManager/dispatcher.d/99tlp-rdw-nm failed (failed): Script '/etc/NetworkManager/dispatcher.d/99tlp-rdw-nm' exited with status 2. | dlu2021 wrote: 2023-08-29 14:58 If you are using network manager, you can try looking at the priority for the Ethernet connection on the general tab, the highest number wins. Ethernet has higher priority. It seems to connect fine, but there is just no throughput. Edit: I think I may have solved this. Having noticed that executing dhclient gave me a connection, this script will execute the command whenever an Ethernet connection is discovered. Code: Select all# nano /etc/NetworkManager/dispatcher.d/99-run-dhclient Paste the following code into the file: Code: Select all#!/bin/bash if [ "$2" = "up" ] && [ "$1" = "enp0s31f6" ]; then /sbin/dhclient enp0s31f6 fi Then make the script executable. Code: Select all# chmod +x /etc/NetworkManager/dispatcher.d/99-run-dhclient I will test this more tomorrow, so I am keeping the thread open for now. Edit2: That worked perfectly. Marking thread as solved. |
I have the latest Debian stable loaded on a system that DHCPs it's address. I need to define static DNS servers I added the following to /etc/network/interfaces FOR THE INTERFACE Code: Select alldns-nameservers 123.123.133.18 123.123.133.19 etc/resolv.conf shows dns servers from dhcp. I added the following to /etc/dhcp/dhclient.conf Code: Select allprepend domain-name-servers 123.123.133.18, 123.123.133.19; I even tried supercede domain-name-servers instead of prepend etc/resolv.conf shows dns servers from dhcp. All that is in /etc/dhcp/dhclient.conf is... Code: Select alloption rfc3442-classless-static-routes code 121 = array of unsigned integer 8; send host-name = gethostname(); request subnet-mask, broadcast-address, time-offset, routers, host-name, dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes, ntp-servers; supercede domain-name-servers 123.123.133.18, 123.123.133.19 supercede domain-name "sub.mydomain.net" supercede domain-search "sub.mydomain.net" etc/resolv.conf still shows dns servers from dhcp. The system reboots so fast that I just do a reboot after a change No matter what, /etc/resolv.conf always retains the dns servers from dhcp. I am stumped. | @bakerjw: Please: use code tags for commands and their output mark the thread as solved adding the tag [Solved] at the beginning of the subject of the first post Thanks. Edit on Sun Sep 3 00:06:45 CEST 2023: modified the subject of first post (added [Solved] tag), plus added code tags. |
Dear Friends at Debian, I have used the "net" install method for Debian 12 (Bookworm) on computers I donate to the needy -- with the Gnome default desktop. Some of the computers use Broadcom WiFi cards -- and I need very clear instructions on how to install the needed drivers. The instructions I have found online so far are not clear enough for me to feel comfortable because I don't want to guess what they mean and, potentially, mess things up. Bobby L. | https://wiki.debian.org/wl |
Hello everyon I decided to upgrade an old computer still on Buster to Bookworm by doing a fresh install. I used the netinst (https://www.debian.org/CD/netinst/) and only install system utils as I always like to start from a minimal system (I use only Xorg and i3). I was connected via Ethernet without issue during the whole installation process. After some minor UEFI issue, I managed to install Debian and boot into the system. However, I do not have internet although I used the exact same Ethernet connection than during installation. For instance, ping 8.8.8.8 directly results in: Code: Select allconnect: Network is unreachable I do not have WiFi on that computer. Any idea where the issue could come from? Is that because I didn't install any desktop environment and am therefore missing some critical package? ------------------------------------------------ EDIT ------------------------------------------------ The solution was: Get internet by running dhclient enp1s0 in root Install the system, including network-manager Comment, the line with enp1s0 in /etc/network/interfaces Reboot to check it worked | Show Code: Select allip a |
Hi. This is my hardware: Brand: Hewlett Packard x360 Envy Laptop (Alder Lake Architecture) CPU: 13th Gen Intel(R) Core(TM) i7-1355U Mem: 15GiB A little background: Everything was working fine before I performed a regular update (apt update, apt upgrade). Then, in my efforts to fix the issue, I updated from Buster to Bookworm and did a kernel update as well. Now I have a dilema: When I boot with kernel 6.1 my WiFi card is not recognized: Output of: lspci -nnv Code: Select all03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:c852] (rev 01) DeviceName: WLAN Subsystem: Hewlett-Packard Company Device [103c:88e5] Flags: fast devsel, IRQ 255, IOMMU group 17 I/O ports at 3000 [disabled] [size=256] Output of: inxi -Fxz Code: Select allNetwork: Device-1: Realtek vendor: Hewlett-Packard driver: N/A port: 3000 bus-ID: 03:00.0 Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 3-1.1:4 IF: enx00e04c680819 state: up speed: 1000 Mbps duplex: full mac: <filter> If I boot with kernel 6.4 the WiFi issue is gone, BUT the system hangs eventually. I must reboot, nothing else works. Output, while booting with Kernel 6.4, of inxi -Fxz Code: Select allNetwork: Device-1: Realtek vendor: Hewlett-Packard driver: rtw89_8852ce v: kernel port: 3000 bus-ID: 03:00.0 IF: wlo1 state: up mac: <filter> Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 3-1.1:4 IF: enx00e04c680819 state: up speed: 1000 Mbps duplex: full mac: <filter> I guess I can fix the WiFi issue and use Kernel 6.1 or fix the Hanging issue and use Kernel 6.4. More than anything I want to contribute with the detection of issues regarding Debian, which I love. Thanks. | Hello, Welcome to the forum. :-) Your logs from previous message show that your Realtek Semiconductor Co., Ltd. Device [10ec:c852] wireless network card: with kernel 6.1: is not driven by a kernel module (driver) with kernel 6.4: is is driven by the rtw89_8852ce kernel module For kernel 6.1, you may search for source code of the kernel module and compile it and "out of the tree module". For the system hang with kernel 6.4, you may acquire system logs after the system is hung to determine what is the involved operating system component. You may install ssh on your computer and try to access it remotely from another computer when it hangs. If it is not accessible during the hang, you can use the so called "REISUB" sequence to force flushing disk buffers, file system umounting and reboot. It could be useful to acquire the full output of the inxi command, for example: Code: Select allinxi -Fxxxz |
Hello, If you want Debian to connect with two different IP addresses. One private address and the other global, then it is better to have two network cards or one network card with two IP addresses? Thank you. | Two. |
So I have tried each of the following Code: Select allhttps://wiki.debian.org/OpenVPN https://www.howtoforge.com/how-to-install-and-configure-openvpn-server-on-debian-12/ https://www.server-world.info/en/note?os=Debian_12&p=openvpn&f=1 I appreciate that there are many ways to achieve the same result, but they seem quite different and in places hard to know whether definitely work for Debian 12. It appeared that the final tutorial was looking more promising, but on final step to Code: Select allsystemctl enable --now openvpn-server@server if fails and the log shows the below .... Code: Select allSep 03 13:13:55 VPNSERVER openvpn[1429513]: TUN/TAP device tun0 opened Sep 03 13:13:55 VPNSERVER openvpn[1429513]: net_iface_mtu_set: mtu 1500 for tun0 Sep 03 13:13:55 VPNSERVER openvpn[1429513]: net_iface_up: set tun0 up Sep 03 13:13:55 VPNSERVER openvpn[1429513]: net_addr_ptp_v4_add: 192.168.100.1 peer 192.168.100.2 dev tun0 Sep 03 13:13:55 VPNSERVER openvpn[1429513]: net_route_v4_add: 192.168.100.0/24 via 192.168.100.2 dev [NULL] table 0 metric -1 Sep 03 13:13:55 VPNSERVER openvpn[1429513]: Could not determine IPv4/IPv6 protocol. Using AF_INET Sep 03 13:13:55 VPNSERVER openvpn[1429513]: Socket Buffers: R=[212992->212992] S=[212992->212992] Sep 03 13:13:55 VPNSERVER openvpn[1429513]: UDPv4 link local (bound): [AF_INET][undef]:1194 Sep 03 13:13:55 VPNSERVER openvpn[1429513]: UDPv4 link remote: [AF_UNSPEC] Sep 03 13:13:55 VPNSERVER openvpn[1429513]: MULTI: multi_init called, r=256 v=256 Sep 03 13:13:55 VPNSERVER openvpn[1429513]: IFCONFIG POOL IPv4: base=192.168.100.4 size=62 Sep 03 13:13:55 VPNSERVER openvpn[1429513]: IFCONFIG POOL LIST Sep 03 13:13:55 VPNSERVER openvpn[1429513]: Initialization Sequence Completed Sep 03 13:13:55 VPNSERVER add-bridge.sh[1429523]: iptables: Bad rule (does a matching rule exist in that chain?). Sep 03 13:13:55 VPNSERVER systemd[1]: openvpn-server@server.service: Control process exited, code=exited, status=1/FAILURE What "matching rule" is it talking about? | You really should describe what kind of openvpn server setup you are looking for. Do you have 1 server and one client or something more complex? Do you have static public IP addresses? Is your client using random networks that might block UDP traffic to port 1194? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.