prompt stringlengths 1 63.6k | completion stringlengths 1 53.1k |
|---|---|
Hello, relatively new to the linux thing. I'm running kvm with vmm. I've got my windows vm running off a macvtap on my second nic. It works great, until I shut the vm off (this was also an issue with a couple redhat based vm's, and I don't believe it to be guest OS related). Once I go to to power the vm back on, I get an error about the address being in use already. Code: Select allError starting domain: Cannot set interface flags on 'macvtap7': Address already in use Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup self._backend.create() File "/usr/lib/python3/dist-packages/libvirt.py", line 1353, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: Cannot set interface flags on 'macvtap7': Address already in use I can either delete the macvtap interface directly with Code: Select all sudo ip link delete macvtap# Or I can edit the xml to have a different mac address. Both of these options work to let the vm boot. While annoying, this works. I really feel like this shouldn't be a thing. It looks like it's tying the mac address to the macvtap interface (makes sense) and not releasing it when the vm shutdowns. As such, is there a way to automate this in some form? I am seeing this in my log Code: Select allSep 15 00:09:27 AlansPC audit[1165438]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165438 comm="apparmor_parser" Sep 15 00:09:27 AlansPC kernel: audit: type=1400 audit(1663218567.565:103): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165438 comm="apparmor_parser" Sep 15 00:09:27 AlansPC audit[1165441]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165441 comm="apparmor_parser" Sep 15 00:09:27 AlansPC kernel: audit: type=1400 audit(1663218567.701:104): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165441 comm="apparmor_parser" Sep 15 00:09:27 AlansPC audit[1165473]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165473 comm="apparmor_parser" Sep 15 00:09:27 AlansPC kernel: audit: type=1400 audit(1663218567.829:105): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165473 comm="apparmor_parser" Sep 15 00:09:27 AlansPC audit[1165477]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165477 comm="apparmor_parser" Sep 15 00:09:27 AlansPC kernel: audit: type=1400 audit(1663218567.949:106): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165477 comm="apparmor_parser" Sep 15 00:09:27 AlansPC NetworkManager[1048]: <info> [1663218567.9685] manager: (macvtap8): new Macvlan device (/org/freedesktop/NetworkManager/Devices/15) Sep 15 00:09:27 AlansPC systemd-udevd[1165482]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 15 00:09:27 AlansPC systemd-udevd[1165482]: Using default interface naming scheme 'v247'. Sep 15 00:09:28 AlansPC audit[1165494]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165494 comm="apparmor_parser" Sep 15 00:09:28 AlansPC kernel: audit: type=1400 audit(1663218568.105:107): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165494 comm="apparmor_parser" Sep 15 00:09:28 AlansPC systemd-machined[1057]: New machine qemu-10-win10. Sep 15 00:09:28 AlansPC systemd[1]: Started Virtual Machine qemu-10-win10. Sep 15 00:09:28 AlansPC audit[1279]: AVC apparmor="DENIED" operation="capable" profile="libvirtd" pid=1279 comm="rpc-worker" capability=39 capname="bpf" Sep 15 00:09:28 AlansPC audit[1279]: AVC apparmor="DENIED" operation="capable" profile="libvirtd" pid=1279 comm="rpc-worker" capability=38 capname="perfmon" Sep 15 00:09:28 AlansPC kernel: audit: type=1400 audit(1663218568.157:108): apparmor="DENIED" operation="capable" profile="libvirtd" pid=1279 comm="rpc-worker" capability=39 capname="bpf" Sep 15 00:09:28 AlansPC kernel: audit: type=1400 audit(1663218568.157:109): apparmor="DENIED" operation="capable" profile="libvirtd" pid=1279 comm="rpc-worker" capability=38 capname="perfmon" Sep 15 00:09:28 AlansPC libvirtd[1279]: Cannot set interface flags on 'macvtap8': Address already in use Sep 15 00:09:28 AlansPC systemd[1]: machine-qemu\x2d10\x2dwin10.scope: Succeeded. Sep 15 00:09:28 AlansPC systemd-machined[1057]: Machine qemu-10-win10 terminated. Sep 15 00:09:28 AlansPC audit[1165550]: AVC apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165550 comm="apparmor_parser" Sep 15 00:09:28 AlansPC kernel: audit: type=1400 audit(1663218568.833:110): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1165550 comm="apparmor_parser" Sep 15 00:09:28 AlansPC libvirtd[1279]: error destroying network device macvtap8: Operation not supported Sep 15 00:10:15 AlansPC kernel: pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:08:00.0 Sep 15 00:10:15 AlansPC kernel: amdgpu 0000:08:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Sep 15 00:10:15 AlansPC kernel: amdgpu 0000:08:00.0: device [1002:67df] error status/mask=00000040/00002000 Sep 15 00:10:15 AlansPC kernel: amdgpu 0000:08:00.0: [ 6] BadTLP when I try to start the vm without wiping out the taps or changing mac address. I get this on a successful shutdown of the system Code: Select allSep 15 00:15:27 AlansPC libvirtd[1279]: internal error: End of file from qemu monitor Sep 15 00:15:27 AlansPC systemd[1]: machine-qemu\x2d11\x2dwin10.scope: Succeeded. Sep 15 00:15:27 AlansPC systemd[1]: machine-qemu\x2d11\x2dwin10.scope: Consumed 35.966s CPU time. Sep 15 00:15:27 AlansPC systemd-machined[1057]: Machine qemu-11-win10 terminated. Sep 15 00:15:27 AlansPC audit[1175951]: AVC apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1175951 comm="apparmor_parser" Sep 15 00:15:27 AlansPC kernel: audit: type=1400 audit(1663218927.720:117): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-03543fa6-0983-495a-8f20-ffb74ee157fa" pid=1175951 comm="apparmor_parser" Sep 15 00:15:27 AlansPC libvirtd[1279]: error destroying network device macvtap9: Operation not supported where do I find out what the operation it is trying to do that isn't supported.. I get that destroying network device macvtap9.. but where do I see the command it's attempting to run. This is definitely my problem spot, just lost on where to go next. Thanks, Alan | I can't quite follow. Specify vm or host and not 'system' What version host? VMM does keep track of all vm xml's, so can't use same definitions on more than one vm. What address are you recycling? I *think* you have the same MAC defined in more than one xml. You should not have a macvtap9 without macvtap1-8 being actively and currently defined. In the vm OS the ip is set, they need to be different. This does not prevent the vm from booting, just no network once booted. |
Hi, I have been running Debian 11 on a repurposed Qnap NAS box for a few months now. Earlier this week I ran apt update and apt dist-upgrade. I haven't had any issues doing this before, but during the upgrade there was a text prompt to select my grub partition. I never needed to touch grub when I set this up, so it was a bit of a surprise. I selected /dev/sda3 which has a /boot/grub folder and went on with the upgrade. Since then, the boot process stops with a GRUB display (no prompt). I was able to boot the system using Super Grub, but I have not been able to restore the boot configuration. Most of the responses are for dual boot systems, which this is not (with the caveat that the original Qnap drive still exists). I've tried running grub-install on both /dev/sda (error: will not proceed with blocklists) and /dev/sda3. Just for fun I also tried running grub-install /dev/sdf (the old Qnap boot partition) -- no error reported, but no success either (initially I tried to use that as the boot partition but couldn't get it to work). I ran bootinfoscript and it seems to suggest that I am missing a core.img, and maybe two different versions of grub? Here is the initial part of RESULT.txt (/dev/sde is the Super Grub USB stick): Code: Select all Boot Info Script 0.78 [09 October 2019] ============================= Boot Info Summary: =============================== => Grub2 (v1.99-2.00) is installed in the MBR of /dev/sda and looks at sector 93531816 of the same hard drive for core.img, but core.img can not be found at this location. => No boot loader is installed in the MBR of /dev/sdb. => Grub2 (v2.00) is installed in the MBR of /dev/sde and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks for (,msdos1)/boot/grub. It also embeds following components: modules --------------------------------------------------------------------------- fshelp fat part_msdos biosdisk --------------------------------------------------------------------------- => Grub2 (v2.00) is installed in the MBR of /dev/sdf and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks for /boot/grub. It also embeds following components: modules --------------------------------------------------------------------------- fshelp ext2 part_msdos biosdisk search_fs_uuid --------------------------------------------------------------------------- config script --------------------------------------------------------------------------- search.fs_uuid 6c777e28-647e-4957-b1dc-7422ed289183 root hd0,msdos1 set prefix=($root)'/boot/grub' --------------------------------------------------------------------------- sda1: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Boot files: sda2: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Operating System: Boot files: sda3: __________________________________________________________________________ File system: ext4 Boot sector type: Grub2 (v1.99-2.00) Boot sector info: Grub2 (v2.00) is installed in the boot sector of sda3 and looks at sector 72242424 of the same hard drive for core.img. core.img is at this location and looks for (,gpt3)/boot/grub. It also embeds following components: modules ------------------------------------------------------- fshelp ext2 part_gpt biosdisk ------------------------------------------------------- Operating System: Debian GNU/Linux 11 (bullseye) Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/i386-pc/core.img sda4: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Mounting failed: mount: /tmp/BootInfo-EZrIvWi3/sda4: wrong fs type, bad option, bad superblock on /dev/sda4, missing codepage or helper program, or other error. At this point I seem to be going in circles. Any advice would be welcome. | maltycat wrote: 2022-09-17 01:16 during the upgrade there was a text prompt to select my grub partition You are the second one who I see report this issue. The boot location(s) should have been registered in debconf during the installation and reused during grub* package updates. Code: Select alldebconf-show grub-pc AFAIK this prompt appears only during initial grub-pc installation or when the boot device recorded in debconf is not found. maltycat wrote: 2022-09-17 01:16 I selected /dev/sda3 which has a /boot/grub folder Wrong choice. You should have selected the whole drive /dev/sda to install GRUB boot image in the MBR. Now the old boot image in the MBR points to a non existent core image file which has been replaced with the new core image. maltycat wrote: 2022-09-17 01:16 I've tried running grub-install on both /dev/sda (error: will not proceed with blocklists) It seems that /dev/sda has a GPT partition table but no "BIOS boot" (biosgrub) partition. So you need to force the installation using blocklists with --force. But blocklists are not reliable an may break anytime so you should create a BIOS boot partition and reinstall GRUB. The required size is less than 1 MB, so there should be a free space on the disk, usually between the partition table and the first partition. When you are in the running system, run Code: Select alldpkg-reconfigure grub-pc and select /dev/sda when prompted to register the proper boot location in debconf. |
Even though I've been using Debian for over 20 years, I made a really newbie mistake. After a software upgrade with aptitude I noticed that I had a few obsolete packages. Some were old kernels, but for some reason my r8186 drivers came up which are for the Realtek wireless chips. I figured there must be some sort of replacement, so I purged the obsolete software. Well, surprise, surprise, no more wireless connectivity. I'm using AMD64 testing, and after looking through the repository I can not find any new or old drivers. I know Realtek has always had a problem with "free" software, but I wouldn't expect aptitude to break a working system. Although, it has happened before. Any suggestions on how to get these working again? Thanks. | Drivers are generally built as kernel modules, they don't come in packages. Exactly which package removal do you think caused this? You can look in /var/log/apt/history if you don't remember and just reinstall it. I suspect you may have removed the firmware package firmware-realtek rather than driver. |
I know this has probably been answered already, I installed Bullseye lxde live last week. Installed firmware for realtek rtk-8732be. Wifi worked until today. Laptop is a lenovo G50. Code: Select alldmesg | grep wlan [ 18.608996] rtl8723be 0000:01:00.0 wlp1s0: renamed from wlan0 Code: Select alliwconfig lo no wireless extensions. enp2s0 no wireless extensions. wlp1s0 IEEE 802.11 ESSID:"George.Guest" Mode:Managed Frequency:2.412 GHz Access Point: EA:CC:18:E0:FD:1B Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr=2347 B Fragment thr:off Encryption key:off Power Management:on Link Quality=58/70 Signal level=-52 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:7 Missed beacon:0 | Can you ping your gateway? |
I have an HP PowerBook 440 G4 with Debian Bullseye & BSPWM installed. My locker is lightdm with slick-greeter without a screensaver. My xset q says: Code: Select allDPMS (Energy Star): Standby: 600 Suspend: 600 Off: 600 DPMS is Enabled Monitor is On I installed xfce4-power-manager in order to put my laptop in suspend mode after a certain period of time, but it only turned off my monitor, so I uninstalled since I get this by default without the power manager. So, I want to suspend my laptop after a certain amount of inactivity, as I can get with a power manager in a desktop environment, i.e. after X minutes on battery and after X minutes on AC. How can I achieve this? | Did you use the right tab in xfce4-power-manager? There are settings for mains/battery on my laptop, but I'm on my desktop at the moment. As far as I remember, the laptop also suspends after a certain time. I will check the next time I turn it on. Works for me on the desktop. I have never touched xset; a cursory glance suggests xfce4-power-manager should override xset settings: https://wiki.archlinux.org/title/Displa ... _Signaling |
* Realtek RTL8821AE firmware, version 29 (rtlwifi/rtl8821aefw_29.bin). Please see the snapshot attached. Also, you can see those files installed in my system: /lib/modules/5.10.0-18-amd64/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae /lib/modules/5.10.0-18-amd64/kernel/drivers/net/wireless/realtek/rtlwifi/rtl_pci.ko /lib/modules/5.10.0-18-amd64/kernel/drivers/net/wireless/realtek/rtlwifi/rtl_usb.ko /lib/modules/5.10.0-18-amd64/kernel/drivers/net/wireless/realtek/rtlwifi/rtlwifi.ko However, wifi is no where to be found: loc@debian:~$ /sbin/iwconfig lo no wireless extensions. enp2s0 no wireless extensions. loc@debian:~$ | LTL wrote: 2022-10-12 03:08How can I report this problem was solved? Edit the title of your first post to add [SOLVED]. |
My situation is pretty straight-forward but networking is clearly not my specialty: I have two routers - one has an address of 192.168.0.1, the other router (connected to the first router on address 192.168.0.3) has an address of 192.168.10.1. I have a home server running Bullseye on 192.168.0.2. I have a networked printer connected to 192.168.10.100. I want the server to be able to use the printer and I don't know how to go about doing that; the server can't even ping the printer. I tried forwarding port 9100 on the primary router. The secondary router has no port forwarding features, if that even matters. I have the firewall disabled on both routers to keep things simple. For what it's worth, devices on secondary router seem to have no problem talking to anything on the primary router, just not the other way around. | configure 192.168.0.1 to route packets to network 192.168.10.0/24 via 192.168.0.3 |
I have a USB WiFi Adapter and I want to connect to it using systemd-networkd. I created the WPA supplicant conf for it at /etc/wpa_supplicant/ as: Code: Select allnetwork={ ssid="TheSSID" psk=TheHash } And then the network file for systemd-networkd at /etc/systemd/network as: Code: Select all[Match] Name=wlx00e1b010c2f7 [Network] Address=192.168.2.180/24 Gateway=192.168.2.1 DNS=127.0.0.53 DNS=127.0.2.2 But the WiFi never connects: Code: Select allsudo systemctl restart systemd-networkd Code: Select all❯ networkctl | grep wlx00e1b010c2f7 3 wlx00e1b010c2f7 wlan no-carrier configuring ❯ ip link | grep wlx00e1b010c2f7 3: wlx00e1b010c2f7: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 If I connect using wpa_supplicant it just works! Code: Select all❯ sudo wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant-wlx.conf -i wlx00e1b010c2f7 Successfully initialized wpa_supplicant wlx00e1b010c2f7: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN wlx00e1b010c2f7: SME: Trying to authenticate with TheSSID (SSID='TheHatch' freq=2452 MHz) wlx00e1b010c2f7: Trying to associate with TheSSID (SSID='TheHatch' freq=2452 MHz) wlx00e1b010c2f7: Associated with TheSSID wlx00e1b010c2f7: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 wlx00e1b010c2f7: WPA: Key negotiation completed with TheSSID [PTK=CCMP GTK=CCMP] wlx00e1b010c2f7: CTRL-EVENT-CONNECTED - Connection to TheSSID completed [id=0 id_str=] How come WiFi doesn't work when trying to connect with systemd-networkd? How can I make it work? | Turns out the name of the configuration file for wpa_supplicant is pretty important. Code: Select all❯ ip link | grep wlx00e1b010c2f7 3: wlx00e1b010c2f7: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 Erroneously it was: "/etc/wpa_supplicant/wpa_supplicant-wlx.conf". But it should be: "/etc/wpa_supplicant/wpa_supplicant-wlx00e1b010c2f7.conf". And then enable the wpa_supplicant service as such: Code: Select allsudo systemctl enable --now wpa_supplicant@wlx00e1b010c2f7 And now it's working: Code: Select all❯ networkctl | grep wlx00e1b010c2f7 3 wlx00e1b010c2f7 wlan routable configured ❯ ip link | grep wlx00e1b010c2f7 3: wlx00e1b010c2f7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 |
Bullseye stable 2022-10-19 I lost the ability to cause a button mouse click. That happened immediately after going to settings and further to a screen for touchpad and moving a slide from on to off. (Amazing what you cannot do thereafter). I ask for suggestions for correcting so I can get back to paid work. I purpose to login as root, navigate to some configuration file where that setting is and change it. If that is a good way to proceed, then what file might that be in? Further, I have only myself as a desktop login window. Thanks to "sudo" I have never had to login as root through the GUI since installation was complete over half a year ago. This is a fast system (Dell M6500) and the reboot scroll is too fast to be useful (at least until I can login as root). I do not know if that touchpad setting is unique or if specific to the login user. I expect to attempt all I do without the necessity of clicking a "left mouse button". When this is resolved I will briefly explain why I ever went into that setting and shot myself in the foot. | Is this Gnome? Obtain a console with Code: Select allCtrl + Alt + FN# 2-6 should work, but I used 3, so I'll give an example with that: Code: Select allCtrl + Alt + F3 or if you have a function button on a laptop: Code: Select allCtrl + Alt + FN + F3 https://wiki.debian.org/Console Log in with your user name and password (not root). Enter this command at the user prompt. Code: Select all$ dconf read /org/gnome/desktop/peripherals/touchpad/send-events With the touchpad slider to on it says 'enabled'. Hopefully yours will say something different, then you can do Code: Select all$ dconf write /org/gnome/desktop/peripherals/touchpad/send-events "'enabled'" Note double quote around single quote. |
OK.. been working on some scripts to get info into files I can read as a non-admin (mainly to display in my conky output). I have a couple crontab entries that are working perfectly.. I also have one that isn't working at all. @reboot sleep 30 /mnt/raid/scripts/testups.sh & This script runs a while loop (just keeping the thing running without having to relaunch it all the time). It checks upsc's output for a specific field. If that field is abesent, it restarts nut-driver.service. Otherwise it goes to sleep and queries in 10 seconds. It works perfectly when I run it as root from terminal. I see no evidence of it running, backgrounded or after a reboo. The man 5 for crontab does indicate @reboot is supposed to work. Any suggestions or links? I've been googling this for about the last 2 hours. I do see in journalctl that it's running it, or trying to at least Code: Select allOct 23 05:15:09 alanspc anacron[1058]: Anacron 2.3 started on 2022-10-23 Oct 23 05:15:09 alanspc anacron[1058]: Normal exit (0 jobs run) Oct 23 05:15:09 alanspc cron[1064]: (CRON) INFO (pidfile fd = 3) Oct 23 05:15:09 alanspc cron[1064]: (CRON) INFO (Running @reboot jobs) Oct 23 05:15:09 alanspc CRON[1066]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Oct 23 05:15:09 alanspc CRON[1071]: (root) CMD (sleep 30 /mnt/raid/scripts/testups.sh &) Oct 23 05:15:09 alanspc CRON[1066]: pam_unix(cron:session): session closed for user root Oct 23 05:15:09 alanspc systemd[1]: anacron.service: Succeeded. Oct 23 05:17:01 alanspc CRON[6399]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Oct 23 05:17:01 alanspc CRON[6400]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) I dont see anything when I run jobs or a ps -e|grep -ki "testups.sh" Thanks | meh, screw the cronjob.. I just wrote a systemd service and have it wanted by multi-user. still don't know why the cron didn't work, but thats the nice thing about linux... more than 2 ways to get things done. |
I have a old IBM laptop which I have just installed Debian Bullseye on (netinstall) and the Wifi is refusing to connect. The wifi worked perfectly with the previous distro on my home wifi network so I am happy that the wifi on the laptop works.Ethernet is working perfectly The laptop wifi is a Intel Corporation PRO/Wireless 2200BG I downloaded the non-free firmware package, "firmware-ipw2x00" and instaled it Code: Select allsudo iwconfig lo no wireless extensions. enp2s1 no wireless extensions. wlp2s2 IEEE 802.11 ESSID:off/any Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I can see my wifi networks ( I have 2 the third is a test I setup) Code: Select allsudo iwlist wlp2s2 scan | grep ESSID ESSID:"web@32" ESSID:"watertest" ESSID:"Telly" But everytime I try to connect it will try and then just responds by asking me to re-enter the passphrase. The wifi is turned on, every now and again the laptop wifi light will flash. I have tried using both the Network Manager and from CLI to make the connection (although I prefer Network manager). Any suggestions please. Tim | I can confirm that the firmware for the wifi is being loaded without an issue Code: Select alldmesg | grep 'wifi\|ipw2200\|firmware' [ 5.130231] radeon 0000:01:00.0: firmware: failed to load radeon/R100_cp.bin (-2) [ 5.130245] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 5.130253] radeon 0000:01:00.0: Direct firmware load for radeon/R100_cp.bin failed with error -2 [ 5.130416] [drm:r100_cp_init [radeon]] *ERROR* Failed to load firmware! [ 5.903428] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 18.957780] platform regulatory.0: firmware: direct-loading firmware regulatory.db [ 18.988814] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [ 19.431489] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [ 19.431497] ipw2200: Copyright(c) 2003-2006 Intel Corporation [ 19.431878] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [ 19.490794] ipw2200 0000:02:02.0: firmware: direct-loading firmware ipw2200-bss.fw [ 19.651510] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels) [ 20.669329] ipw2200 0000:02:02.0 wlp2s2: renamed from eth0 |
os: debian 12 kde Here is the output of lsblk: Code: Select all~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 683.7G 0 part /media/data └─sda2 8:2 0 247.8G 0 part /mnt/kvm sdb 8:16 0 119.2G 0 disk ├─sdb1 8:17 0 102.2G 0 part / ├─sdb2 8:18 0 1K 0 part └─sdb5 8:21 0 17G 0 part [SWAP] sdc 8:32 0 931.5G 0 disk └─sdc1 8:33 0 931.5G 0 part /media/backup sdd 8:48 1 0B 0 disk sr0 11:0 1 1024M 0 rom The disks 'sda', 'sdb','sdc' and the cdrom 'sr0' are present. The disk ´sdd´ is not present. According to the colums it is removable and the size is 0. In the past I had created (and removed) a virtual usb disk on my synology nas and I think this could be a leftover of this virtual usb disk. How can I solve this??? | Hello, Have you searched the system logs ? You can do it with the following command (root password is required): Code: Select allsu -l -c "journactl -b --grep "STORAGE_DEVICE" |
(this is in the context of adding layers to the official Debian Docker image) I've been needing to install the "intel-media-va-driver-non-free" package, that's never been an issue on bullseye after adding the non-free repo with Code: Select allapt-add-repository -y non-free On bookworm however this results in "no installation candidates". As far as I understand packages.debian.org shows it still existing on bookworm, and still in the non-free repo (https://packages.debian.org/bookworm/in ... r-non-free) so I don't know what I'm doing wrong. I've noticed that there had been changes with the new "non-free-firmware" source so tried adding that, and contrib too, but still no dice. | What is the output of the following command ? Code: Select all$ apt-cache policy intel-media-va-driver-non-free This is mine: Code: Select all$ apt-cache policy intel-media-va-driver-non-free intel-media-va-driver-non-free: Installed: (none) Candidate: 23.1.1+ds1-1 Version table: 23.1.1+ds1-1 500 500 http://localhost:3142/debian bookworm/non-free amd64 Packages |
I liked my experience with Debian on my desktop, so I decided to install it on my brand new Dell Inspiron 16 laptop. During the installation process, my home network was detected, but it was impossible to connect to it. After several attempts, I decided to just hotspot from another computer, and figured I would solve the issue later. Now Debian is installed, along with KDE Plasma. Still can't connect to anything but hotspots. It is possible to connect to hotspots created using different phones and computers, but I can't connect directly to my home network. I tried changing the channel that my wireless interface uses to some random lower channels, but no luck. I also tried booting into another kernel via GRUB (oddly enough, I have two: 6.1.0.10 an d 6.1.0.11-amd64). I also tried changing the frequency to the frequency that is displayed for my home network when I click on the Wi-Fi applet in the KDE system tray. Still no luck. I'm not sure what is causing the issue, and I also have very little knowledge of networking, unfortunately. Any suggestions would be appreciated. Of course, reinstalling Debian didn't seem like a viable option to me, because the installer wouldn't even connect to the network in the first place. However, if any of you see reinstalling as an option for whatever reason, I don't mind going through the process, given that I have a brand new installation. Do note that all the other devices in my home, including Windows and Linux computers and several different phones, all connect flawlessly to the home internet. I also have a Debian 11 (Bullseye) installation on my desktop that connects fine as well. Here's my exact laptop model: https://www.dell.com/en-ca/shop/laptops/amd/spd/inspiron-16-5635-laptop/caeichbts5635fyxf#BVQAContainer I'm running Debian 12 (Bookwork) on my Dell Inspiron 16 laptop, which is the problematic machine. Thank you in advance, and God bless. | GPWR wrote: 2023-08-27 22:36 but I can't connect directly to my home network. Does that router utilize mac white listing or limited connection counts? I use both and frequently forget. |
The same issue was also before the upgrade to 11.4 with the new installation of 11.3. I have to close and open Thunderbird after the resume of suspend to recover the high usage of the CPU. Code: Select allCPU: Info: Dual Core model: Intel Celeron N2840 bits: 64 type: MCP arch: Silvermont rev: 8 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8666 Speed: 600 MHz min/max: 500/2582 MHz Core speeds (MHz): 1: 600 2: 790 Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0f31 class ID: 0300 Device-2: Realtek Lenovo EasyCamera type: USB driver: uvcvideo bus ID: 1-4.1:4 chip ID: 0bda:579a class ID: 0e02 serial: <filter> Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) v: 4.2 Mesa 20.3.5 compat-v: 3.0 direct render: Yes | Hello, Do you suspend to ram or to disk ? Have you checked system memory usage before and after suspension with thunderbird running (including swap memory)? How much ram is installed in your computer ? |
Every time after resume from suspend, it took 20 seconds to start the Ethernet connection where Wi-Fi was in less than 3 seconds. The solution with the help of, https://dannyda.com/2021/04/01/how-to-f ... nterfaces/ was to change the eth0 with the real name of the connection at, Code: Select all/etc/network/interfaces.d/setup in my case, it is after running the code, Code: Select allip a Then, Code: Select allauto enp3s0 iface enp3s0 inet dhcp Save, close the file and reboot the system. | Or just delete that bogus file which should not exist in the first place and let the network manager manage the interface. |
Hi, I have a Zotac ZBOX CI547 nano with an intel core i5-7200U and an intel HD Graphics 620 card on which I installed Debian 11 and the linux-firmware package (fresh install, kernel 5.10.0-9). It is connected to a monitor supporting 1920*1080 via HDMI. On boot, the grub resolution is fine, then while booting, on 90% of the case, the screen resolution is set at 1280*800 and once on Gnome I cannot change to a higher resolution, even with xrandr: Code: Select allzbox@black-box:~$ xrandr --verbose Screen 0: minimum 16 x 16, current 1280 x 800, maximum 32767 x 32767 XWAYLAND0 connected primary 1280x800+0+0 (0x22) normal (normal left inverted right x axis y axis) 510mm x 280mm Identifier: 0x21 Timestamp: 26284 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 0.0 Clones: CRTC: 0 CRTCs: 0 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: non-desktop: 0 supported: 0, 1 1280x800 (0x22) 83.500MHz -HSync +VSync *current +preferred h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 49.70KHz v: height 800 start 803 end 809 total 831 clock 59.81Hz Code: Select allzbox@black-box:~$ cvt -v 1920 1080 # 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz Modeline "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync zbox@black-box:~$ xrandr --newmode "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync zbox@black-box:~$ xrandr --addmode XWAYLAND0 1920x1080_60.00 zbox@black-box:~$ xrandr --output XWAYLAND0 --mode 1920x1080_60.00 xrandr: Configure crtc 0 failed Here is the full dmesg when the computer boot with the right resolution (approximately 10% off the time): http://pastebin.fr/97303 And here the dmesg when the resolution is wrong: http://pastebin.fr/97302 Here are the relevant errors I could find when the resolution is wrong by comparing the two files (line 860 of the file): Code: Select all[ 3.918717] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful And here is the full dmesg with the drm.debug=0x1e log_buf_les=10M boot options when the resolution is wrong: http://pastebin.fr/97304 Here are the relevant lines regarding the error: Code: Select all[ 3.883899] i915 0000:00:02.0: [drm:intel_dp_start_link_train [i915]] Same voltage tried 5 times [ 3.883953] i915 0000:00:02.0: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:95:DP-1] Link Training failed at link rate = 162000, lane count = 1 [ 3.883955] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful The second problem I have is that after suspend or hibernate, the display does not come back but the system is fine (I can log on the machine by ssh). The monitors says it does not receive any signal, and when I check with xrandr the display is labelled as disconnected. I catch the following dmesg typing blindly on TTY mode. Here is the full dmesg after suspend and wake, when the boot resolution is right: http://pastebin.fr/97306 And here is the full dmesg after suspend and wake, when the boot resolution is wrong: http://pastebin.fr/97305 And here is the dmesg with the drm.debug=0x1e log_buf_les=10M boot options when the resolution is wrong: http://pastebin.fr/97307 What I could see is this error appearing after suspend when the resolution is right: Code: Select all[ 151.138095] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training And this when the resolution is wrong: Code: Select all[ 854.422386] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training [ 854.422390] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful I tried to install Debian 10 to check is the problem existed before and I have exactly the same problems, intermittent wrong resolution and no display after suspend. I guess the two problems are related and something goes wrong with the intel firmware. | I don't like to do it this way but I installed Ubuntu 21.10 just to see of the problems exist on another distro. The screen resolution is set correctly at each boot, but the suspend problem persists. |
Dear All, First of all: I know next to nothing about dri3, but when I try running an application (the x86_64 release of a file sync application at https://github.com/FilenCloudDienste/fi ... p/releases), I get an error message Code: Select all[4291:0804/104713.546997:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported. I run debian stable on a desktop and I have nothing fancy installed (all stuff from the standard repos) + nvidia drivers (for cuda and friends) because I need them to use my gpu to crunch numbers. I am not at all an expert about dri3 and so far I have never needed to be one. This is my card Code: Select all $ lspci | grep -i --color 'vga\|3d\|2d' 05:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) and based on what I saw here viewtopic.php?f=5&t=137330&p=672221&hilit=dri3#p672221 Code: Select all $ xdpyinfo | grep -i "DRI" DRI2 dri3 is definitely not enabled, but I installed the relevant packages, I believe Code: Select all$ sudo apt list --installed | grep dri3 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libxcb-dri3-0/stable,now 1.14-3 amd64 [installed,automatic] libxcb-dri3-dev/stable,now 1.14-3 amd64 [installed] Any idea about how to enable dri3? Any suggestion is appreciated. | If you're using the proprietary drivers then they are responsible for the stuff that's handled by DRI3 under Mesa. That "DRI2" in the xdpyinfo output is just what the driver reports when queried through the DRI protocol but the protocol itself is not used. So if you want DRI3 try nouveau. |
I had Debian 11 installed on my PC, everything worked fine (that time I installed both xfce and lxqt). I did a reinstall and everything was going great, until later the next day internet would not connect, not through Ethernet or WiFi. With the help of a friend and his computer I found out how to edit /etc/network/interfaces and I set up the Ethernet connection, however I did not set the WiFi. I set it up today and it works, however I'm still getting some kind of error every time I run Code: Select allsystemctl status networking this is what I get Code: Select all● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2022-08-06 04:16:16 CDT; 28min ago Docs: man:interfaces(5) Main PID: 36050 (code=exited, status=1/FAILURE) CPU: 592ms Aug 06 04:15:59 denebian ifup[36073]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 10 Aug 06 04:16:09 denebian dhclient[36073]: No DHCPOFFERS received. Aug 06 04:16:09 denebian ifup[36073]: No DHCPOFFERS received. Aug 06 04:16:09 denebian ifup[36073]: No working leases in persistent database - sleeping. Aug 06 04:16:09 denebian dhclient[36073]: No working leases in persistent database - sleeping. Aug 06 04:16:16 denebian ifup[37107]: Could not get a link-local address Aug 06 04:16:16 denebian ifup[36050]: ifup: failed to bring up enp2s0 Aug 06 04:16:16 denebian systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Aug 06 04:16:16 denebian systemd[1]: networking.service: Failed with result 'exit-code'. Aug 06 04:16:16 denebian systemd[1]: Failed to start Raise network interfaces. Thanks in advance to anyone willing to help, much appreciated. If more information is needed I will gladly provide it. | DidGrasstouching wrote: 2022-08-07 03:12 2: enp2s0: <NO-CARRIER The ethernet interface is not connected. No wonder why the DHCP client cannot get an IP address. |
Hi all, I am managing an Debian 9 host (I could not upgrade it in this moment). I have to install some additional software package, but I get HTTP 404 error. In this moment I have to repair some package using "apt --fix-broken install" however I can't handle this task. I tried to update /etc/apt/source.list and I tried to run apt-get update command. I get these error message: Code: Select allW: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ftp.it.debian.org/debian sid InRelease: The following signatures have not been verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 Here my source.list file Code: Select all# # deb cdrom:[Debian GNU/Linux 9.8.0 _Stretch_ - Official i386 NETINST 20190216-12:51]/ stretch main #deb cdrom:[Debian GNU/Linux 9.8.0 _Stretch_ - Official i386 NETINST 20190216-12:51]/ stretch main #deb http://ftp.it.debian.org/debian/ stretch main #deb-src http://ftp.it.debian.org/debian/ stretch main #deb http://security.debian.org/debian-security stretch/updates main #deb-src http://security.debian.org/debian-security stretch/updates main # stretch-updates, previously known as 'volatile' #deb http://ftp.it.debian.org/debian/ stretch-updates main #deb-src http://ftp.it.debian.org/debian/ stretch-updates main #deb http://security.debian.org/debian-security stretch/updates main #DEB deb http://deb.debian.org/debian stretch main deb-src http://deb.debian.org/debian stretch main deb http://deb.debian.org/debian stretch-updates main deb-src http://deb.debian.org/debian stretch-updates main deb http://security.debian.org/debian-security/ stretch/updates main deb-src http://security.debian.org/debian-security/ stretch/updates main In this moment "APT" ignore "deb.debian.org" new added repository. How can I solve this trouble? Thanks a lot | viewtopic.php?p=647679 |
How can I add "startx -- -nocursor" to nodm? In /etc/default/nodm: Code: Select all# nodm configuration # Set NODM_ENABLED to something different than 'false' to enable nodm NODM_ENABLED=true # User to autologin for NODM_USER=<user> # First vt to try when looking for free VTs NODM_FIRST_VT=7 # X session NODM_XSESSION=/etc/X11/Xsession # Options for nodm itself #NODM_OPTIONS= # Options for the X server. # # Format: [/usr/bin/<Xserver>] [:<disp>] <Xserver-options> #xserver-command = X -nocursor # The Xserver executable and the display name can be omitted, but should # be placed in front, if nodm's defaults shall be overridden. NODM_X_OPTIONS='-nolisten tcp' # If an X session will run for less than this time in seconds, nodm will wait an # increasing bit of time before restarting the session. NODM_MIN_SESSION_TIME=6 # Timeout (in seconds) to wait for X to be ready to accept connections. If X is # not ready before this timeout, it is killed and restarted. NODM_X_TIMEOUT=300 Seeing the man page of Xsession.options and Xsession doesn't seem possible there. | I would add it to the NODM_X_OPTIONS array within the same quotation marks as '-nolisten tcp' and separated with a space. But that's just a wild guess. EDIT: for clarity: Code: Select allNODM_X_OPTIONS='-nolisten tcp -nocursor' |
I have a fresh, fully updated Bullseye installation. There are 2 Ethernet NICs, each with manually configured ipv4 settings on different ip networks, and only one gateway assigned. All works fine unless... when the system reboots or is awakened from a power save state, sometimes Network Manager swaps the configurations, assigning Network-A to NIC-B and Network-B to NIC-A. Since these are on different networks, the machine can no longer communicate with any device on either network - I have to login to the physical console in order to correct the problem. Is there a way to lock in the Network Manager configuration so this doesn't happen? Or do I need to just dump NM and configure everything through /etc/network/interfaces instead? | bithead wrote: 2022-09-10 00:10dump NM and configure everything through /etc/network/interfaces Call me old-school if you will, but that would be my approach right out of the gate. I mean, why fight with opaque abstractions and bloated GUI trash when some lightweight shell scripts do the job just fine? Frankly NetworkManager has caused me more pain than it's worth, even on machines (i.e. laptops) where it's halfway appropriate. |
Hello, My Linux box has two NICs: Code: Select allenp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::a00:27ff:febc:c5a7 prefixlen 64 scopeid 0x20<link> ether 08:00:27:bc:c5:a7 txqueuelen 1000 (Ethernet) RX packets 615 bytes 154476 (150.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 384 bytes 125712 (122.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp0s9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::a00:27ff:fee5:267c prefixlen 64 scopeid 0x20<link> ether 08:00:27:e5:26:7c txqueuelen 1000 (Ethernet) RX packets 613 bytes 153792 (150.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 386 bytes 126396 (123.4 KiB) 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 44309 bytes 265369512 (253.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 44309 bytes 265369512 (253.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 And its hardware is as follows: Code: Select all# lspci ... 00:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) 00:09.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) ... Is 00:08.0 related to enp0s8 and 00:09.0 related to enp0s9? Thank you. | hack3rcon wrote: 2023-09-12 12:23 Is 00:08.0 related to enp0s8 and 00:09.0 related to enp0s9? Yes. https://wiki.debian.org/NetworkInterfaceNames |
Hello, I have some questions about network settings: 1- How can I rename a NIC name? 2- What is the difference between interfaces and interfaces.d? 3- If I open the interfaces file and put the new NIC settings in it or create a new file under the interfaces.d directory and then put the new NIC settings in it, then which one is better? Thank you. | Here ya go Mr.Bot 1. Equivalent was the wrong term, they are complimentary. The paragraphed continued to more or less explain the intentional difference. You could simply read most any /etc/*d or *.conf file provided and find the answers. No google or endless are we there yet forum questions... 2. Create *.link files in /etc/systemd/network/ and reference /lib/systemd/network to see default config files that will appear in a enumeration check. See 'man systemd-networkd' Code: Select all# udevadm test=builtin net_setup_link /sys/class/net/* Find what * is by a quick list Code: Select all$ ls /sys/class/net/ |
Hello, I want to use the TinyProxy to launch an HTTP proxy and share the Internet with the clients. My TinyProxy server has two NICs: Code: Select allenp0s3: 10.0.2.15 enp0s8: 192.168.1.1 The enp0s3 is a NIC that has Internet access. My clients connected to the enp0s8 NIC. In the TinyProxy configuration file, there are two statements: Code: Select allAllow IP Listen IP Should Allow be the public IP address and Listen be the local IP address? Thank you. | https://tinyproxy.github.io wrote:Listen By default, Tinyproxy listens for connections on all available interfaces (i.e. it listens on the wildcard address `0.0.0.0`). With this configuration parameter, Tinyproxy can be told to listen only on one specific address. Allow Deny The `Allow` and `Deny` options provide a means to customize which clients are allowed to access Tinyproxy. `Allow` and `Deny` lines can be specified multiple times to build the access control list for Tinyproxy. The order in the config file is important. If there are no `Allow` or `Deny` lines, then all clients are allowed. Otherwise, the default action is to deny access. The argument to `Allow` or `Deny` can be a single IP address of a client host, like `127.0.0.1`, an IP address range, like `192.168.0.1/24` or a string that will be matched against the end of the client host name, i.e, this can be a full host name like `host.example.com` or a domain name like `.example.com` or even a top level domain name like `.com`. Note that by adding a rule using a host or domain name, a costly name lookup has to be done for every new connection, which could slow down the service considerably. |
Hi, Maybe it's not the right section, if so, I beg it to be moved, since it's not a debian issue, but despite searching, I haven't been able to find a way to fix it and since I've been using debian, I consider this forum as a database knowledge that I have not seen in another forum. Previously I had a tp link archer c7 router, usb disk connected and configured in fstab to auto mount at startup, the command line I had was this: Code: Select all//192.168.1.5/Router /mnt/external cifs auto,users,vers=2.0,username=myusername,password=mypassword,dir_mode=0777,file_mode=0777 0 0 I have changed my router, currently I have put a tp link archer X50, apparently, samba is different in this router and that previous line does not work for me, it does not mount the disk. I have searched, the best I have seen has been: Code: Select all//192.168.1.5/G /mnt/external cifs auto,users,vers=1.0,username=myusername,password=mypassword,uid=1000,gid=1000,nofail 0 0 But... sometimes it works for me and sometimes it doesn't, I don't know if it's due to a failure in the router (I also have others that I'm dealing with technical support) or it's the line entered in fstab that is not entirely adequate. I don't know if vers=1.0 is the right one, I can put another one or... that, I don't know if the failure is due to the command or the router. Thanks in advance. | Hello, What is the equipment/computer in which the USB disk is plugged in ? Is it the router or a computer connected to the router ? On which equipment/computer is the /etc/fstab with the reported line? |
when I run updates i get the bellow Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. when I run apt list --upgradable, i get this linux-headers-amd64/bullseye-backports 6.1.27-1~bpo11+1 amd64 [upgradable from: 6.1.20-2~bpo11+1] why isnt this been updated/upgraded? | biojo wrote: 2023-09-02 15:19 [..] when I run apt list --upgradable, i get this linux-headers-amd64/bullseye-backports 6.1.27-1~bpo11+1 amd64 [upgradable from: 6.1.20-2~bpo11+1] why isnt this been updated/upgraded? As @dlu2021 already pointed out, backports repository is low-priority by default (see [1]). For example, in a Debian Bookworm with both bookworm-backports and bookworm repositories configured: Code: Select all# apt policy linux-headers-amd64 linux-headers-amd64: Installed: 6.1.38-4 Candidate: 6.1.38-4 Version table: 6.4.4-3~bpo12+1 100 100 http://deb.debian.org/debian bookworm-backports/main amd64 Packages *** 6.1.38-4 500 500 http://localhost:3142/debian-security bookworm-security/main amd64 Packages 100 /var/lib/dpkg/status 6.1.38-1 500 500 http://localhost:3142/debian bookworm/main amd64 Packages As you can see, the package from bookworm-backports has a lower priority (100) than the one (already installed, ***) from debian-security or bookworm repositories. If you want to force the installation of packages from debian-backports, you have to do it manually. A way is to explicitly instruct apt to do it with the -t option; for example: Code: Select all# apt policy -t bookworm-backports linux-headers-amd64 linux-headers-amd64: Installed: 6.1.38-4 Candidate: 6.4.4-3~bpo12+1 Version table: 6.4.4-3~bpo12+1 990 990 http://deb.debian.org/debian bookworm-backports/main amd64 Packages *** 6.1.38-4 500 500 http://localhost:3142/debian-security bookworm-security/main amd64 Packages 100 /var/lib/dpkg/status 6.1.38-1 500 500 http://localhost:3142/debian bookworm/main amd64 Packages Now, you can see that that the package from bookworm-backports has a higher priority (990) than the one from bookworm-security or bookworm repositories (500). If the package does not exists in bookworm repositories but only in bookworm-backports, it can be installed manually (since it does not compete with bookworm packages); for example: Code: Select all# apt -s install linux-headers-6.4.0-0.deb12.2-amd64 It would be better not to replace linux-headers-amd64 from stable with the one from backports, otherwise you'll need to upgrade manually linux-headers for stable in the future. Please update the subject of the first message from "Updates not working, broken headers?" to "Cannot install linux kernel headers from bookworm-backports" Hope this helps. --- [1] Debian Wiki - Backports |
I have a file server running debian 10 using iptables. Contected is 4 windows 10 desktops with microsoft access database front ends. The tables are stored on a map drive on windows 10 which points to a shared folder where the tables are stored on the file server. All works how it should and no problems. I have built a new testing server with debian 11 bullseye using nftables. It is the excact same setup but the only difference is nftables. I first tried it using iptables but it didnt work. Had the same problem that follows. The 4 desktops connect ok to the map drive and can read tables ok. If one desktop makes a change to a text field the changes show up on all other machines. If another machine makes a change to the same field same record it shows the change on the two other machines but the first machine that made the orginal change the new edit doesnt show. I can reload the records from the start and all changes are shown correctly. I know from past experience that this alone means the database is not working correctly. Every field is unbound to the database and only when you make a change to the field it writes back to tables and the change is made in the tables correctly. I had this problem when I tried to update to bulleyes when first released. I re-installed buster debian 10 as it works there with no problems. I now have more time to investigate and to find out why this happens. Any help or just to point me in the right direction would be very appreciated | like to add further details to the above post I have now created a table that logs any updates on any field in each record. this is timestamped and the user who made the change and logs old data. When I make a change all logs are correct and the database table shows correct data. This now makes me think its a cache problem. I cant understand why it works with iptables and buster but not with nftables and bullseye. Has anyone any views on this. I just seem to be going round and round in circles. |
Hi I am trying to get my head around NFtables priorities so that a a dynamically created chain can override a rule set in another chain. But I am not able to get an example code to work. The code that I have is as below and I expect since the INPUT chain has a lower priority it should allow icmp from 172.17.12.165, but if i run this code i get an ICMP destination port unavailable which is part of the second chain which I do not expect the packet to traverse. Can someone explain what is wrong in this #!/usr/bin/nft -f flush ruleset table ip firewall { chain INPUT { type filter hook input priority 0; policy drop; iifname lo accept ip saddr 172.17.13.100 icmp type echo-request accept; ct state vmap {established:accept, related:accept, invalid:drop} ip saddr 171.17.13.100 tcp dport ssh accept; } chain PASSALL { type filter hook input priority 10; policy accept; ip saddr 172.17.13.100 icmp type echo-request reject; } } | A typo? You specified ip saddr 171.17.13.100 instead of ip saddr 172.17.13.100 in the INPUT chain. Does this work? Code: Select all#!/usr/sbin/nft -f flush ruleset table ip firewall { chain INPUT { type filter hook input priority 0; policy drop; iifname lo accept ip saddr 172.17.13.100 icmp type echo-request accept; ct state vmap {established: accept, related: accept, invalid: drop} ip saddr 172.17.13.100 tcp dport ssh accept; } chain PASSALL { type filter hook input priority 10; policy accept; ip saddr 172.17.13.100 icmp type echo-request reject; } } |
[solved] Hello fellow debianists. I wanted to switch from sudo to doas but I encountered a strange problem. I red the doas man page, doas debwiki page and also the doas.conf page so I think I require help from the community Here's a reconstitution of my actions: Code: Select all➜sudo apt update Tous les paquets sont à jour. #Everything is working gud ! ➜doas apt update doas: Operation not permitted ➜username@.hostname mousepad /etc/doas.conf (content of /etc/doas.conf ) permit USERNAME as root ➜doas -C /etc/doas.conf #No output which means no problem I guess ➜groups username username cdrom floppy sudo audio dip video plugdev netdev lpadmin scanner ➜ls -l $(which doas) -rwsr-xr-x 1 root root 43184 27 juil. 2022 /usr/bin/doas Maybe I commit an error because before "apt install doas" I "apt purge sudo" I don't know what else to give in order for you to help me! Also it's my first time on this forum so hello everybody I hope I will find a warmer community than the distros I used to contribute for and use Sorry for any english errors it isnt my native langage and i'm currently enjoying a 39 degrees fever | Hello, Welcome to the forum. Can you report the full content of /etc/doas.conf ? |
Last week I switched from Kubuntu to Debian, which was generally pretty straight-forward. But there is a locale problem I don't understand. On my system, I have both en_US and de_DE locales generated, but then set the en_US locale as active. For root, everything is fine: Code: Select allcassiopeia:~# locale LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= But as user, I get this result: Code: Select allcassiopeia ~ > locale LANG=de_DE.UTF-8 LANGUAGE=en_US.UTF-8 LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= I've checked my local and global shell config files, but there is nothing about locales. Neither does Konsole (where I've tested this) have a locale setting. Also, this: Code: Select allcassiopeia:~# cat /etc/default/locale # File generated by update-locale LANG=en_US.UTF-8 LANGUAGE="en_US.UTF-8" So why the difference? It seems that there is a setting I don't know about. | Please edit the title of your first post to add [SOLVED]. And welcome! |
I've been running Debian 11 stable on a Lenovo Thinkpad X220 since March and have had nearly no issues with it. Recently though, my laptop hasn't been able to start up after suspending (e.g. running "systemctl suspend"). After suspension, pressing the power button caused the system to appear to boot and light up but then stop, start to boot again, stop, and repeat. After completely shutting my laptop down and booting it up a couple of times, i noticed that GRUB output a message along the lines of (because I can't 100% remember it): "Failed to create variable: out of resources" before displaying the "Welcome to Grub!" text. Then, I ran "efibootmgr" as root while booted into Debian and this was the output: Code: Select allBootCurrent: 000A Timeout: 0 seconds BootOrder: 0091,001B,000C,0007,0006,0008,0009,000A,000B,000D,000E,000F,0010,0011,0012,0013,0019 Boot0000 Setup Boot0001 Boot Menu Boot0002 Diagnostic Splash Screen Boot0003 Startup Interrupt Menu Boot0004 ME Configuration Menu Boot0005 Rescue and Recovery Boot0006* USB CD Boot0007* USB FDD Boot0008* ATAPI CD0 Boot0009* ATA HDD2 Boot000A* ATA HDD0 Boot000B* ATA HDD1 Boot000C* USB HDD Boot000D* PCI LAN Boot000E* ATAPI CD1 Boot000F* ATAPI CD2 Boot0010 Other CD Boot0011* ATA HDD3 Boot0012* ATA HDD4 Boot0013 Other HDD Boot0014* IDER BOOT CDROM Boot0015* IDER BOOT Floppy Boot0016* ATA HDD Boot0017* ATAPI CD: Boot0018* PCI LAN Boot0019* ubuntu Boot001A* ubuntu Boot001B* debian Boot001C* debian Boot001D* ubuntu Boot001E* debian Boot001F* ubuntu Boot0020* debian Boot0021* ubuntu Boot0022* debian Boot0023* debian Boot0024* debian Boot0025* debian Boot0026* debian Boot0027* debian Boot0028* debian Boot0029* debian Boot002A* debian Boot002B* debian Boot002C* debian Boot002D* debian Boot002E* debian Boot002F* debian Boot0030* debian Boot0031* debian Boot0032* debian Boot0033* debian Boot0034* debian Boot0035* debian Boot0036* debian Boot0037* debian Boot0038* debian Boot0039* debian Boot003A* debian Boot003B* debian Boot003C* debian Boot003D* debian Boot003E* debian Boot003F* debian Boot0040* debian Boot0041* debian Boot0042* debian Boot0043* debian Boot0044* debian Boot0045* debian Boot0046* debian Boot0047* debian Boot0048* debian Boot0049* debian Boot004A* debian Boot004B* debian Boot004C* debian Boot004D* debian Boot004E* debian Boot004F* debian Boot0050* debian Boot0051* debian Boot0052* debian Boot0053* debian Boot0054* debian Boot0055* debian Boot0056* debian Boot0057* debian Boot0058* debian Boot0059* debian Boot005A* debian Boot005B* debian Boot005C* debian Boot005D* debian Boot005E* debian Boot005F* debian Boot0060* debian Boot0061* debian Boot0062* debian Boot0063* debian Boot0064* debian Boot0065* debian Boot0066* debian Boot0067* debian Boot0068* debian Boot0069* debian Boot006A* debian Boot006B* debian Boot006C* debian Boot006D* debian Boot006E* debian Boot006F* debian Boot0070* debian Boot0071* debian Boot0072* debian Boot0073* debian Boot0074* debian Boot0075* debian Boot0076* debian Boot0077* debian Boot0078* debian Boot0079* debian Boot007A* debian Boot007B* debian Boot007C* debian Boot007D* debian Boot007E* debian note: there are ubuntu boot entries here because I was running Linux Mint before I installed Debian I assumed that all of these debian boot entries were taking up space I needed on my system so I deleted them one by one with "efibootmgr -b 00xx -B". When I restarted my laptop, there were no error messages and I was able to boot into Debian, suspend, and wake from suspend just fine! But then I ran efibootmgr again and the long list of debian boot entries was back. Since then I've tried: - Deleting all debian entries except one, then running "grub-update" - Deleting all debian entries, then reinstalling grub on the EFI partition, and changing the boot order in my BIOS before booting back in Each time I boot back into the system, the debian boot entries are there. If I restart my laptop without removing the entries, no GRUB error messages pop up, but I still can't wake from suspend. In this current state, when I attempt waking, my computer doesn't light up and stop, it lights up and just shows a black screen. Is there any way I can stop these boot entries from being added back? | Looks like the UEFI firmware is flawed and boots from the removable media path instead of the registered boot entries. Also it creates multiple boot entries with the same name instead of replacing them. Workaround : Code: Select allgrub-install --force-extra-removable rm /boot/efi/EFI/Boot/fbx64.efi The first command makes sure the removable media path (/boot/efi/EFI/Boot) contains Debian's GRUB and not some older GRUB instance. The second command deletes the "fall back" executable from this location, which scans the EFI partitions for BOOT.CSV files at boot time and adds EFI boot entries for each of them. You will have to do it again after each grub* or shim* package upgrade. There may be a better workaround but I don't know it. |
I'm running Debian bullseye on AMD Ryzen 5 3600. I have been running the standard bullseye kernel, but recently upgraded my kernel from bullseye-backports (current version linux-image-5.16.0-0.bpo.4-amd64). The main reason for this was to get the new ntfs3 driver, but so far I haven't been able to get that to work, and haven't found any obviously relevant info online. Whether I set ntfs3 as the type of an NTFS partition in fstab, or just run "mount -t ntfs3" manually, I get "mount: unknown filesystem type 'ntfs3'". The kernel appears to be working fine in all other respects. Any idea how I should progress this? Are there other bits and pieces I need to pull from bullseye-backports, in addition to the kernel itself? | Maybe the wiki might give a clue to the correct mount type. Oh yes, here it is - https://wiki.debian.org/NTFS First hit from a Startpage search for "debian ntfs-3g driver". Please Read.. What we expect you have already Done. |
Any idea what couses the problem? This solution didn't work. viewtopic.php?t=148185 Code: Select all apt update Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. # update-initramfs -uk all update-initramfs: Generating /boot/initrd.img-5.10.0-15-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly. W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_08.bin for module i915 W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.10.0-13-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly. W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_08.bin for module i915 W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_02.bin for module i915 System: Kernel: 5.10.0-15-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 Distro: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: LENOVO product: 80G0 v: Lenovo G50-30 serial: <filter> Chassis: type: 10 v: Lenovo G50-30 serial: <filter> Mobo: LENOVO model: Lancer 5A6 v: SDK0F82993WIN serial: <filter> UEFI: LENOVO v: A7CN40WW date: 07/18/2014 Battery: ID-1: BAT0 charge: 24.4 Wh condition: 24.4/28.5 Wh (85%) volts: 16.2/14.4 model: Lenovo type: Unknown serial: <filter> status: Full CPU: Info: Dual Core model: Intel Celeron N2840 bits: 64 type: MCP arch: Silvermont rev: 8 L1 cache: 56 KiB L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8666 Speed: 753 MHz min/max: 500/2582 MHz volts: 1.0 V ext-clock: 83 MHz Core speeds (MHz): 1: 753 2: 914 Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0f31 class ID: 0300 Device-2: Realtek Lenovo EasyCamera type: USB driver: uvcvideo bus ID: 1-4.1:4 chip ID: 0bda:579a class ID: 0e02 serial: <filter> Display: server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) v: 4.2 Mesa 20.3.5 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:0f04 class ID: 0403 Sound Server: ALSA v: k5.10.0-15-amd64 Network: Device-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Lenovo driver: ath9k v: kernel port: 2000 bus ID: 02:00.0 chip ID: 168c:0036 class ID: 0280 IF: wlp2s0 state: down mac: <filter> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: kernel port: 1000 bus ID: 03:00.0 chip ID: 10ec:8168 class ID: 0200 IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> Device-3: Qualcomm Atheros AR3012 Bluetooth 4.0 type: USB driver: usb-network bus ID: 1-4.3:6 chip ID: 0cf3:3004 class ID: e001 Bluetooth: Device-1: Qualcomm Atheros AR3012 Bluetooth 4.0 type: USB driver: N/A bus ID: 1-4.3:6 chip ID: 0cf3:3004 class ID: e001 Drives: Local Storage: total: 476.94 GiB used: 231.44 GiB (48.5%) ID-1: /dev/sda vendor: Patriot model: P210 512GB size: 476.94 GiB speed: 1.5 Gb/s rotation: SSD serial: <filter> rev: ae20 temp: 44 C scheme: GPT Partition: ID-1: / size: 28.67 GiB used: 10.33 GiB (36.0%) fs: ext4 dev: /dev/sda6 ID-2: /boot/efi size: 558.9 MiB used: 11.5 MiB (2.1%) fs: vfat dev: /dev/sda1 Swap: ID-1: swap-1 type: zram size: 512 MiB used: 0 KiB (0.0%) priority: -2 dev: /dev/zram0 Sensors: System Temperatures: cpu: 48.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: Packages: apt: 2101 Active apt repos in: /etc/apt/sources.list 1: deb http://deb.debian.org/debian/ bullseye main 2: deb-src http://deb.debian.org/debian/ bullseye main 3: deb http://deb.debian.org/debian/ bullseye-updates main 4: deb-src http://deb.debian.org/debian/ bullseye-updates main 5: deb http://security.debian.org/debian-security/ bullseye-security main 6: deb-src http://security.debian.org/debian-security/ bullseye-security main Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main Info: Processes: 197 Uptime: 28m wakeups: 1 Memory: 3.72 GiB used: 1.32 GiB (35.5%) Init: systemd v: 247 runlevel: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: Bash (sudo) v: 5.1.4 running in: xfce4-terminal inxi: 3.3.01 | The issues are solved as follows, I enabled non-free repositories and then the commands. Code: Select allapt install Firmware-Realtek apt install firmware-misc-nonfree dpkg-reconfigure keyboard-configuration |
Hello. I'm trying to set up a Raspberry Pi with Debian as a wifi router. I have installed and configured hostapd, dnsmasq and iptables. Currently my devices can connect to the RPi acting as AP (hostapd), they get IP's and names from dnsmasq, and thanks to a NAT rule in iptables, they can access the internet (through the RPi's ethernet, connected to my ISP provided wifi router). But they can not connect to one another. So my computer has IP 10.0.0.10 and my Android phone is 10.0.0.16. Both can google, or whatever, but if I start Primitiv FTPd (an android sftp server) on my phone, my computer can't connect to it; it times out. (If I connect both to the wifi router provided by my IPS, it works). At the begining I couldn't ping the phone either. Then I checked the routes and found this: Code: Select allroot@ysbryd:~# ip route default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.10 metric 600 10.0.0.0/8 dev wlo1 proto kernel scope link src 10.0.0.10 metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 Deleting the rule for 10.0.0.0/8 fixed ping from my computer to my phone, but that's a local change, and my phone isn't getting its routes changed like that. Perhaps that's why the connection to sftp still didn't work?. So I tried adding a route from dnsmasq, so that 10.0.0.0/8 would go via 10.0.0.1 (the RPi, router, gateway, dhcp, etc). I added this line to /etc/dnsmasq.conf: Code: Select alldhcp-option=121,10.0.0.0/8,10.0.0.1 Now the routes in my computer look like this: Code: Select allroot@ysbryd:~# ip route default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.10 metric 600 10.0.0.0/8 dev wlo1 proto kernel scope link src 10.0.0.10 metric 600 10.0.0.0/8 via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.10 metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 So the rule was added, but the broken rule is still there, and it still doesn't work. Am I on the right path here? Or is this an iptables problem? How can I fix this? Thanks in advance for your help: Wences PS: This is what my iptables looks like right now (I know it could be much tighter, once it all works I'll harden it): Code: Select allroot@peimafon:~# iptables-save # Generated by iptables-save v1.8.9 (nf_tables) on Thu Nov 2 01:39:13 2023 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A FORWARD -s 10.0.0.0/8 -j ACCEPT COMMIT # Completed on Thu Nov 2 01:39:13 2023 # Generated by iptables-save v1.8.9 (nf_tables) on Thu Nov 2 01:39:13 2023 *nat :PREROUTING ACCEPT [268155:30817688] :INPUT ACCEPT [41340:2687374] :OUTPUT ACCEPT [17335:1139669] :POSTROUTING ACCEPT [17332:1139161] -A POSTROUTING -s 10.0.0.0/8 -j MASQUERADE COMMIT # Completed on Thu Nov 2 01:39:13 2023 | Hello, Raspberry Pi with Debian as a wifi router. I have installed and configured hostapd, dnsmasq and iptables [..] my computer has IP 10.0.0.10 and my Android phone is 10.0.0.16 [..] if I start [..] an android sftp server on my phone, my computer can't connect to it; it times out. [..] I checked the routes and found this: Code: Select allroot@ysbryd:~# ip route default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.10 metric 600 10.0.0.0/8 dev wlo1 proto kernel scope link src 10.0.0.10 metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 Deleting the rule for 10.0.0.0/8 fixed ping from my computer to my phone I suppose you hostapd router IP is 10.0.0.1. I suppose the route table is from your computer with IP 10.0.0.10. Have you checked the ap_isolate parameter in hostapd configuration ? Is the iptable listed in the previous post from your computer or hostapd access point ? |
Hi guys, I've got 2 repos set up with reprepro. The two repos' reprepro configuration is the same, apart of course from the basedirs and upstream URLs used. They use the same GPG key for signing the local repo. repo A is working fine, it's a mirror of posgtresql packages. And I can run apt update from a client and install packages. No issues. repo B is not working, it's a mirror of Xpra debian packages. When I run apt-update on a client I get: Code: Select allroot@amgt01:~# apt update Hit:1 http://arepo01.example.org/debian bullseye InRelease Hit:2 http://arepo01.example.org/debian-security bullseye-security InRelease ... Hit:5 http://arepo01.example.org/postgres bullseye-pgdg InRelease Ign:6 http://arepo01.example.org/xpra bullseye InRelease Err:7 http://arepo01.example.org/xpra bullseye Release 404 Not Found [IP: 172.16.202.206 80] Reading package lists... Done E: The repository 'http://arepo01.example.org/xpra bullseye Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root@amgt01:~# So, as I see it, it complains about the Release file not being found. This is the folder structure of repo B, which is NOT WORKING: Code: Select allmirror@arepo01:/srv/mirror/xpra$ tree -L 3 . ├── conf │ ├── distributions │ ├── options │ └── updates ├── db │ ├── checksums.db │ ├── contents.cache.db │ ├── packages.db │ ├── references.db │ ├── release.caches.db │ └── version ├── dists │ └── bullseye │ ├── InRelease │ ├── main │ ├── Release │ └── Release.gpg ├── lists │ ├── bullseye_bullseye_InRelease │ ├── bullseye_bullseye_main_amd64_Packages │ └── _bullseye_lastseen ├── logs │ └── logfile └── pool └── main └── x 10 directories, 16 files And this is the folder structure for repo A that is working fine: Code: Select allmirror@arepo01:/srv/mirror/postgres$ tree -L 3 . ├── conf │ ├── distributions │ ├── options │ └── updates ├── db │ ├── checksums.db │ ├── contents.cache.db │ ├── packages.db │ ├── references.db │ ├── release.caches.db │ └── version ├── dists │ └── bullseye-pgdg │ ├── InRelease │ ├── main │ └── Release ├── lists │ ├── bullseye-pgdg_bullseye-pgdg_InRelease │ ├── bullseye-pgdg_bullseye-pgdg_main_amd64_Packages │ └── _bullseye-pgdg_lastseen ├── logs │ └── logfile └── pool └── main ... 33 directories, 15 files And I can see that there are some differences in what Release files exist and where they are. So my question is: How do I get reprepro to create a working repo/mirror of xpra.org? Thanks in advance, /tony P.S. Here are the reprepro config files, just so you can see that they are done the same way: Postgres: Code: Select allmirror@arepo01:/srv/mirror/postgres/conf$ ls -1 distributions options updates mirror@arepo01:/srv/mirror/postgres/conf$ mirror@arepo01:/srv/mirror/postgres/conf$ cat distributions Origin: arepo01.example.org Label: PostgreSQL apt repository Codename: bullseye-pgdg Architectures: amd64 source SignWith: mirror@example.org Components: main Description: PostgreSQL package repo Update: - bullseye-pgdg Log: logfile mirror@arepo01:/srv/mirror/postgres/conf$ mirror@arepo01:/srv/mirror/postgres/conf$ cat options verbose basedir /srv/mirror/postgres ask-passphrase mirror@arepo01:/srv/mirror/postgres/conf$ mirror@arepo01:/srv/mirror/postgres/conf$ cat updates Name: bullseye-pgdg Method: http://apt.postgresql.org/pub/repos/apt Architectures: amd64 VerifyRelease: 7FCC7D46ACCC4CF8 Components: main mirror@arepo01:/srv/mirror/postgres/conf$ And the same files used to mirror Xpra: Code: Select allmirror@arepo01:/srv/mirror/xpra/conf$ cat distributions Origin: arepo01.example.org Label: Xpra apt repository Codename: bullseye Architectures: amd64 SignWith: mirror@example.org Components: main Description: Xpra package repo Update: - bullseye Log: logfile mirror@arepo01:/srv/mirror/xpra/conf$ mirror@arepo01:/srv/mirror/xpra/conf$ cat options verbose basedir /srv/mirror/xpra ask-passphrase mirror@arepo01:/srv/mirror/xpra/conf$ mirror@arepo01:/srv/mirror/xpra/conf$ cat updates Name: bullseye Method: https://xpra.org Architectures: amd64 VerifyRelease: 73254CAD17978FAF Components: main mirror@arepo01:/srv/mirror/xpra/conf$ edit: Improved subject description | Right.. I think I'll just go dig a deep hole for me somewhere and get in it. The dumb sysadmin(me) forgot to create a symlink so that apache could actually share the new /srv/mirror/xpra folder.. Jeez... Forget everything after "Good morning". /tony |
I am posting this for the benefit of anyone still having similar issues. Any comments, feedback, suggestions are welcome. Since the recent kernel update (6.1.0-13-amd64), my system was having intermittent issues: Suspend/resume, resumed with a non-responsive black screen. Suspend/resume, the audio volume was muted. "Shutdown" from the menu (poweroff), did not completely shutdown. After reading several posts here regarding similar issues, I discovered that the kernel was causing my problems, due to some modules being ommitted. Why? I don't know, I just know it caused me problems. The best solution I found was to activate "bookworm-backports" repository, and install a higher series kernel. After installing the suggested kernel 6.4.0-0.deb12.2-amd64, the Suspend/resume worked, and the poweroff worked, but the audio volume still resumed muted. I used this kernel for a while, but it gave me another major issue: The Ethernet connection (Realtek driver r8169) would cease working after some time. So after rebooting into the old kernel, I removed the 6.4, and installed the next one up, 6.5.0-0.deb12.1-amd64. All problems were solved, except for the audio volume still resuming muted. I tried various things, but what fixed it was installing Pipewire for audio. All solved. Here is how it's done: ADDING BACKPORTS ON SOURCE LIST Code: Select allsudo echo >> deb http://deb.debian.org/debian bookworm-backports main >> /etc/apt/sources.list.d/backports.list sudo apt update INSTALLING KERNEL Code: Select allsudo apt install -t bookworm-backports linux-headers-6.5.0-0.deb12.1-amd64 linux-image-6.5.0-0.deb12.1-amd64 *Note: I prefer to use Synaptic INSTALLING FIRMWARE Code: Select allsudo apt install -t bookworm-backports firmware-linux *Note: I used this but it didn't improve anything, so not needed. UPDATE GRUB Code: Select allsudo update-grub REBOOT Code: Select allsudo reboot SOUND UNMUTE FIX After suspend/resume the sound would be muted. I solved this by installing Pipewire, following the instructions here: https://wiki.debian.org/PipeWire Final Note It would be nice to be notified of any major changes, especially to the kernel. If anyone knows where there is such a resource, please comment here. | This includes all changes in Debian bookworm-backports kernels, which is rather a slog to read: https://metadata.ftp-master.debian.org/ ... _changelog The package I search for at packages.debian.org is linux-source-X.X, which for your goal is linux-source-6.5. Debian just added 6.6.4 in Experimental, but I'm going to hold off of it for MX until it gets into Sid. We already have working 6.6 Liquorix kernels in our AHS repo section, and mostly updated the most used -dkms drivers for 6.6. |
Hello, I started reading about Bluetooth audio (I get choppy audio over Bluetooth when web pages are loading, for example) and I saw a post about using wireplumber instead of pipewire. However it appears that on my system both are running at the same time: systemctl --user list-units | grep wire pipewire-pulse.service => loaded active running PipeWire PulseAudio pipewire.service => loaded active running PipeWire Multimedia Service wireplumber.service => loaded active running Multimedia Service Session Manager pipewire-pulse.socket => loaded active running PipeWire PulseAudio pipewire.socket => loaded active running PipeWire Multimedia System Socket I'm running Debian Bookworm with this kernel: Linux Debian 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux And this CPU: 12th Gen Intel(R) Core(TM) i7-1255U Can I switch to wireplumber completely or is there another way to improve audio quality over Bluetooth? Thank you! | wireplumber is the chosen session manager for pipewire, they go together. |
Help, I have borked my ZFS system for my secondary drives by somehow no longer getting the ZFS module to load at boot nor thru modprobe. I boot from NVME ext4 but I have a large spinning drive that is managed under ZFS that is not appearing. So this if not a boot from root zfs problem. But I cannot find the ZFS drive because it is no longer recognised. I have tried a full uninstall of ZFS and DKMS but a reinstall started up a recompile of the modules but bombed out withe the "DPKG error(1)" message." I trust the ZFS drive is in good health. If I were to physically move it to another machine and import the pools, but I don't have another machine. This presents a challenge. Is there any real reason for me to be running a 6.5 kernel for Debian 12? I know it is the default but would 5.15 work fine? OS: Debian GNU/Linux 12 (bookworm) x86_64 Kernel: 6.5.0-0.deb12.4-amd64 | debian_toronto wrote: 2023-12-08 19:42 I have tried a full uninstall of ZFS and DKMS but a reinstall started up a recompile of the modules but bombed out withe the "DPKG error(1)" message." Can you report the full log about failure in compiling kernel modules? debian_toronto wrote: 2023-12-08 19:42 Is there any real reason for me to be running a 6.5 kernel for Debian 12? I know it is the default but would 5.15 work fine? OS: Debian GNU/Linux 12 (bookworm) x86_64 Kernel: 6.5.0-0.deb12.4-amd64 This is not the default kernel released with Debian Bookwork (12.2); the current kernel version released with Debian Bookworm is: Code: Select all$ uname -a Linux debian 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux The kernel versions currently distributed with different debian releases are: Code: Select all$ rmadison linux-image-amd64 linux-image-amd64 | 4.19+105+deb10u16 | oldoldstable | amd64 linux-image-amd64 | 5.10.127-2~bpo10+1 | buster-backports | amd64 linux-image-amd64 | 5.10.197-1 | oldstable | amd64 linux-image-amd64 | 6.1.55-1~bpo11+1 | bullseye-backports | amd64 linux-image-amd64 | 6.1.55-1 | stable | amd64 linux-image-amd64 | 6.1.64-1 | proposed-updates | amd64 linux-image-amd64 | 6.5.10-1~bpo12+1 | buildd-stable-backports | amd64 linux-image-amd64 | 6.5.10-1~bpo12+1 | stable-backports | amd64 linux-image-amd64 | 6.5.13-1 | testing | amd64 linux-image-amd64 | 6.5.13-1 | unstable | amd64 linux-image-amd64 | 6.6.4-1~exp1 | experimental | amd64 I found this report in the Debian Bug Tracking System: Debian Bug report logs - #1043124 zfs-dkms: module fails to build for Linux 6.5 […] It was fixed in version zfs-linux/2.1.13-1. What is the zfs-linux version you are using ? You can check with: Code: Select allapt list zfs-dkms |
Debian 12, xen-hypervisor 4.17, xen-utils 4.17 A bit of a strange one, as I have 2 DomUs and when I start 1 it gets added to the bridge, but the other does not! When I start gitlab.cfg it gets added to the bridge: Code: Select all root@legend:/etc/xen# xl create gitlab.cfg Parsing config from gitlab.cfg root@legend:/etc/xen# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.46922c3130cd no eno1 vif6.0 But when I start debproxy.cfg, it does not: Code: Select all root@legend:/etc/xen# xl create debproxy.cfg Parsing config from debproxy.cfg root@legend:/etc/xen# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.46922c3130cd no eno1 vif6.0 But it can be manually added: Code: Select all root@legend:/etc/xen# brctl addif xenbr0 vif7.0 root@legend:/etc/xen# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.46922c3130cd no eno1 vif6.0 vif7.0 The two configurations are almost identical. gitlab.cfg: Code: Select all bootloader = '/usr/lib/xen-4.17/bin/pygrub' vcpus = '2' memory = '8192' root = '/dev/xvda2 ro' disk = [ 'phy:/dev/vg2/gitlab-disk,xvda2,w', 'phy:/dev/vg2/gitlab-swap,xvda1,w', ] name = 'gitlab' vif = [ 'ip=192.168.88.240 ,mac=00:16:3E:44:BC:75,bridge=xenbr0' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' debproxy.cfg: Code: Select all bootloader = '/usr/lib/xen-4.17/bin/pygrub' vcpus = '1' memory = '1024' root = '/dev/xvda2 ro' disk = [ 'phy:/dev/vg2/debproxy-disk,xvda2,w', 'phy:/dev/vg2/debproxy-swap,xvda1,w', ] name = 'debproxy' vif = [ 'ip=192.168.88.242 ,mac=00:16:3E:D2:E0:32,bridge=xenbr0' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' Any ideas to diagnose and fix? | Some more info from systlog. This time debproxy if coming up as vif8 and failing, gitlab is coming up as vif9 as is succesfully added to the bridge. Seem like NetworkManager is trying to get involved in vif8 and perhaps this is what causes it do be removed from the bridge? From syslog for vif8: Code: Select all2023-12-10T11:41:55.561908+00:00 legend NetworkManager[1190]: <info> [1702208515.5584] manager: (vif8.0): new Ethernet device (/org/freedesktop/NetworkManager/Device s/11) 2023-12-10T11:41:55.586758+00:00 legend NetworkManager[1190]: <info> [1702208515.5858] device (vif8.0): state change: unmanaged -> unavailable (reason 'managed', sys -iface-state: 'external') 2023-12-10T11:41:55.589589+00:00 legend root: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/8/0 2023-12-10T11:41:55.592812+00:00 legend dbus-daemon[1058]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm -dispatcher.service' requested by ':1.11' (uid=0 pid=1190 comm="/usr/sbin/NetworkManager --no-daemon") 2023-12-10T11:41:55.593535+00:00 legend dbus-daemon[1058]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org .freedesktop.nm-dispatcher.service not found. 2023-12-10T11:41:55.645396+00:00 legend root: /etc/xen/scripts/vif-bridge: xenbr0 MTU is 1500 2023-12-10T11:41:55.652579+00:00 legend root: /etc/xen/scripts/vif-bridge: setting vif8.0 MTU to 1500 2023-12-10T11:41:55.664370+00:00 legend root: /etc/xen/scripts/vif-bridge: Writing /local/domain/8/device/vif/0/mtu 1500 to xenstore. 2023-12-10T11:41:55.677493+00:00 legend root: /etc/xen/scripts/vif-bridge: adding vif8.0 to bridge xenbr0 2023-12-10T11:41:55.686250+00:00 legend kernel: [156845.549224] xenbr0: port 2(vif8.0) entered blocking state 2023-12-10T11:41:55.686271+00:00 legend kernel: [156845.549232] xenbr0: port 2(vif8.0) entered disabled state 2023-12-10T11:41:55.686273+00:00 legend kernel: [156845.549487] device vif8.0 entered promiscuous mode 2023-12-10T11:41:55.703397+00:00 legend root: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif8.0, bridge xenbr0. 2023-12-10T11:41:55.714924+00:00 legend root: /etc/xen/scripts/vif-bridge: Writing backend/vif/8/0/hotplug-status connected to xenstore. 2023-12-10T11:41:55.730225+00:00 legend kernel: [156845.591799] xen-blkback: backend/vbd/8/51713: using 1 queues, protocol 1 (x86_64-abi) persistent grants 2023-12-10T11:41:55.738173+00:00 legend kernel: [156845.598770] xen-blkback: backend/vbd/8/51714: using 1 queues, protocol 1 (x86_64-abi) persistent grants 2023-12-10T11:41:55.753356+00:00 legend NetworkManager[1190]: <info> [1702208515.7526] device (vif8.0): carrier: link connected 2023-12-10T11:41:55.753517+00:00 legend NetworkManager[1190]: <info> [1702208515.7529] device (vif8.0): state change: unavailable -> disconnected (reason 'carrier-ch anged', sys-iface-state: 'managed') 2023-12-10T11:41:55.754139+00:00 legend kernel: [156845.615241] vif vif-8-0 vif8.0: Guest Rx ready 2023-12-10T11:41:55.754150+00:00 legend kernel: [156845.615262] IPv6: ADDRCONF(NETDEV_CHANGE): vif8.0: link becomes ready 2023-12-10T11:41:55.754153+00:00 legend kernel: [156845.615298] xenbr0: port 2(vif8.0) entered blocking state 2023-12-10T11:41:55.754153+00:00 legend kernel: [156845.615301] xenbr0: port 2(vif8.0) entered forwarding state 2023-12-10T11:41:55.756567+00:00 legend NetworkManager[1190]: <info> [1702208515.7540] policy: auto-activating connection 'Wired connection 1' (48eeee9c-0188-4be5-86 f3-502ebbe826f2) 2023-12-10T11:41:55.756696+00:00 legend NetworkManager[1190]: <info> [1702208515.7553] device (vif8.0): Activation: starting connection 'Wired connection 1' (48eeee9 c-0188-4be5-86f3-502ebbe826f2) 2023-12-10T11:41:55.756787+00:00 legend NetworkManager[1190]: <info> [1702208515.7554] device (vif8.0): state change: disconnected -> prepare (reason 'none', sys-ifa ce-state: 'managed') 2023-12-10T11:41:55.758180+00:00 legend kernel: [156845.620022] device vif8.0 left promiscuous mode 2023-12-10T11:41:55.758189+00:00 legend kernel: [156845.620049] xenbr0: port 2(vif8.0) entered disabled state 2023-12-10T11:41:55.763472+00:00 legend NetworkManager[1190]: <info> [1702208515.7624] device (xenbr0): detached bridge port vif8.0 2023-12-10T11:41:55.763615+00:00 legend NetworkManager[1190]: <info> [1702208515.7626] device (vif8.0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') 2023-12-10T11:41:55.763714+00:00 legend NetworkManager[1190]: <info> [1702208515.7629] device (vif8.0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') 2023-12-10T11:41:55.764208+00:00 legend NetworkManager[1190]: <info> [1702208515.7640] dhcp4 (vif8.0): activation: beginning transaction (timeout in 45 seconds) 2023-12-10T11:41:55.765837+00:00 legend named[1452]: listening on IPv6 interface vif8.0, fe80::fcff:ffff:feff:ffff%11#53 2023-12-10T11:41:55.767981+00:00 legend avahi-daemon[1055]: Joining mDNS multicast group on interface vif8.0.IPv6 with address fe80::fcff:ffff:feff:ffff. 2023-12-10T11:41:55.768173+00:00 legend avahi-daemon[1055]: New relevant interface vif8.0.IPv6 for mDNS. 2023-12-10T11:41:55.768314+00:00 legend avahi-daemon[1055]: Registering new address record for fe80::fcff:ffff:feff:ffff on vif8.0.*. From syslog for vif9: Code: Select all 2023-12-10T11:42:34.459452+00:00 legend NetworkManager[1190]: <info> [1702208554.4586] manager: (vif9.0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/12) 2023-12-10T11:42:34.489636+00:00 legend root: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/9/0 2023-12-10T11:42:34.516409+00:00 legend NetworkManager[1190]: <info> [1702208554.5156] device (vif9.0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') 2023-12-10T11:42:34.552888+00:00 legend root: /etc/xen/scripts/vif-bridge: xenbr0 MTU is 1500 2023-12-10T11:42:34.558497+00:00 legend root: /etc/xen/scripts/vif-bridge: setting vif9.0 MTU to 1500 2023-12-10T11:42:34.568381+00:00 legend root: /etc/xen/scripts/vif-bridge: Writing /local/domain/9/device/vif/0/mtu 1500 to xenstore. 2023-12-10T11:42:34.582237+00:00 legend root: /etc/xen/scripts/vif-bridge: adding vif9.0 to bridge xenbr0 2023-12-10T11:42:34.594175+00:00 legend kernel: [156884.456020] xenbr0: port 2(vif9.0) entered blocking state 2023-12-10T11:42:34.594196+00:00 legend kernel: [156884.456031] xenbr0: port 2(vif9.0) entered disabled state 2023-12-10T11:42:34.594198+00:00 legend kernel: [156884.456168] device vif9.0 entered promiscuous mode 2023-12-10T11:42:34.606323+00:00 legend root: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif9.0, bridge xenbr0. 2023-12-10T11:42:34.615281+00:00 legend root: /etc/xen/scripts/vif-bridge: Writing backend/vif/9/0/hotplug-status connected to xenstore. 2023-12-10T11:42:34.630382+00:00 legend kernel: [156884.494099] xen-blkback: backend/vbd/9/51713: using 2 queues, protocol 1 (x86_64-abi) persistent grants 2023-12-10T11:42:34.638244+00:00 legend kernel: [156884.501313] xen-blkback: backend/vbd/9/51714: using 2 queues, protocol 1 (x86_64-abi) persistent grants 2023-12-10T11:42:34.664524+00:00 legend NetworkManager[1190]: <info> [1702208554.6641] device (vif9.0): carrier: link connected 2023-12-10T11:42:34.664680+00:00 legend NetworkManager[1190]: <info> [1702208554.6643] device (vif9.0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') 2023-12-10T11:42:34.666548+00:00 legend kernel: [156884.529069] vif vif-9-0 vif9.0: Guest Rx ready 2023-12-10T11:42:34.666560+00:00 legend kernel: [156884.529093] IPv6: ADDRCONF(NETDEV_CHANGE): vif9.0: link becomes ready 2023-12-10T11:42:34.666563+00:00 legend kernel: [156884.529133] xenbr0: port 2(vif9.0) entered blocking state 2023-12-10T11:42:34.666563+00:00 legend kernel: [156884.529136] xenbr0: port 2(vif9.0) entered forwarding state |
Hi guys, I installed Fail2Ban on my Debian Bookworm from repository by aptitude install fail2ban, it's my first experience and maybe I should do something to configure it like what I do for Samba and other services; here below you can find the result of systemctl status fail2ban.service Code: Select all× fail2ban.service - Fail2Ban Service Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2023-11-09 12:55:03 CET; 2min 10s ago Duration: 49ms Docs: man:fail2ban(1) Process: 1682 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION) Main PID: 1682 (code=exited, status=255/EXCEPTION) CPU: 47ms nov 09 12:55:03 SRV01 systemd[1]: Started fail2ban.service - Fail2Ban Service. nov 09 12:55:03 SRV01 fail2ban-server[1682]: 2023-11-09 12:55:03,709 fail2ban [1682]: ERROR Failed during configuration: File contains no section headers. nov 09 12:55:03 SRV01 fail2ban-server[1682]: file: '/etc/fail2ban/jail.local', line: 21 nov 09 12:55:03 SRV01 fail2ban-server[1682]: ' bantime = 1h ' nov 09 12:55:03 SRV01 fail2ban-server[1682]: 2023-11-09 12:55:03,711 fail2ban [1682]: ERROR Async configuration of server failed nov 09 12:55:03 SRV01 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION nov 09 12:55:03 SRV01 systemd[1]: fail2ban.service: Failed with result 'exit-code'. I opened /etc/fail2ban/jail.local and at line 21 there's bantime = 1h and also if I enable\disable it I have the same error. If i do fail2ban-client start I have: Code: Select all2023-11-09 13:16:34,198 fail2ban.configreader [2104]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto' 2023-11-09 13:16:34,203 fail2ban [2104]: ERROR Failed during configuration: Have not found any log file for sshd jail Regards. GabrieleMax | Hello, fail2ban usually works "out the box" after installation in Debian Bookworm. After that, it can be customized, of course. Therefore, I suspect you messed up something in the program's configuration files (as error messages report) after installing it. Please check the configuration files of the program. Let me know. |
Hi all, I am trying to convert a working networking scheme from NetworkManager to /etc/network/interfaces.d/setup file. The host has Debian bookworm. I have two ethernet connections to my PC (enp5s0 and enp6s0) that I bond (bond0) using LACP. I need a bridge (bridge0) on top of that to interface with the VMs that I have. This works well with the NetworkManager setup; however, the next challenge is assigning some VMs to a separate VLAN, something I don't know how to do using NetworkManager. I set this up in a proxmox host earlier with the following /etc/network/interfaces file: Code: Select allauto eno1 iface eno1 inet manual auto br0 iface br0 inet manual bridge-ports eno1 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-500 auto br0.1 iface br0.1 inet static address 192.168.1.10/24 gateway 192.168.1.1 However, in this host I am using a bond, so I modified the file as follows, partly by using Debian wiki, and partly by trying to replicate the working NetworkManager settings (e.g. stp on, instead of off): Code: Select allauto lo iface lo inet loopback # onboard network interfaces auto enp5s0 iface enp5s0 inet manual auto enp6s0 iface enp6s0 inet manual # bond interface auto bond0 iface bond0 inet manual bond-slaves enp5s0 enp6s0 bond-mode 802.3ad bond-miimon 1 bond-downdelay 0 bond-updelay 0 bond-lacp-rate 1 # up ifconfig bond0 0.0.0.0 up # bridge interface auto bridge0 iface bridge0 inet manual bridge-ports bond0 bridge_stp on # bridge_fd 0 bridge_maxwait 0 bridge-vlan-aware yes bridge-vids 2-500 auto bridge0.1 iface bridge0.1 inet static address 192.168.1.130/24 # netmask 255.255.255.0 # broadcast 192.168.1.255 gateway 192.168.1.1 # network 192.168.1.0 vlan-raw-device bridge0 The objective here is the host machine having an IP number on VLAN1 (192.168.1.130), and be able to bridge the connection to VMs, some of which will be in e a different VLAN (20 in my case. i.e. 192.168.20.*). Unfortunately, the host machine does not get a working network connection with these settings, although it reports having the right IP. I cannot ping any host outside of LAN, I didn't try the hosts in the LAN. I would appreciate any pointers about this and would be happy to provide more information as needed. | Hello, hakayova wrote: 2023-12-14 06:10 After days of work on this, I am giving up. Unfortunately, I couldn't find a way to create an access port to KVM/QEMU VMs on Debian for a specific VLAN (20 in my example). This is so easy on Proxmox. According to my tests, I have the VLANs available on the hypervisor and it can get an IP on both VLANs in question (1 or 20). However, the NIC on VM does not have a setting to be tagged by a certain VLAN ID and serve as an access port. Defining a subinterface on the VM (e.g. eth0.20) does not work either. I am not sure where the packets get filtered but DHCP requests from the VM are not answered, although the server is on and responds to requests from other hosts. Thank you for reading my failure story. Can you share the full configuration of the network of the hypervisor ? For example, you can use the following commands in the host: Code: Select allip addr ip route Can you share the full configuration of your VM (the KVM/QEMU configuration file or the command line used to start it with configuration parameters) ? Can you report the configuration used in Proxmox ? |
First off all my specs: - OS: Debian 12.4 - Kernel version: 6.1.0-17 - Laptop: HP ENVY x360 Convertible 15-ee0xxx - CPU: AMD Ryzen 5 4500U - GPU: inbuilt So basically my Wi-Fi is not working. Like NetworkManager (aka nmapplet) is not even displaying the Wi-Fi settings. I have found out if I stop wpa_supplicant and then restart NetworkManager using systemctl then the wifi works again. But only until I reboot again and everything is broken again. Even if I disable wpa_supplicant. All the same. To see the details of what I have tried already see this reddit thread: https://www.reddit.com/r/linuxquestions ... licant_is/ Please let me know if I should provide any more information. Here are some outputs: Code: Select allnmcli device status: DEVICE TYPE STATE CONNECTION wlo1 wifi unavailable -- systemctl status wpa_supplicant.service: ● wpa_supplicant.service - WPA supplicant Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; enabled; preset: enabled) Active: active (running) since Mon 2024-01-08 14:29:44 CET; 1h 53min ago Main PID: 3342 (wpa_supplicant) Tasks: 1 (limit: 18360) Memory: 1.8M CPU: 10.866s CGroup: /system.slice/wpa_supplicant.service └─3342 /sbin/wpa_supplicant -u -s -O "DIR=/run/wpa_supplicant GROUP=netdev" | Hello, What's in the file named /etc/network/interfaces ? |
The following is for a systemd service that runs (successfully) right before I can log in and runs my script. Code: Select all[Unit] Description=Some description. Before=multi-user.target [Service] ExecStart/usr/local/sbin/my_script.sh Type=oneshot RemainAfterExit=no [Install] WantedBy=multi-user.target But, the problem is, ideally, I'd like for my script to run right before the shutdown process, rather than right before I can log in (mostly because I prefer adding to my shutdown time rather than my bootup time). So, I unsuccessfully tried a systemd service like the following.: Code: Select all[Unit] Description=Some description. Before=poweroff.target [Service] ExecStart/usr/local/sbin/my_script.sh Type=oneshot RemainAfterExit=no [Install] WantedBy=poweroff.target I also tried shutdown.target and final.target, but those were unsuccessful too. Could someone please tell me why this isn't working and/or how I can get it to work? Any input would be greatly appreciated! P.S. I do systemctll disable my_service.service and then systemctl enable my_service.service, and I rebooted at least twice (and also shut down and started up again at least twice), and it's still not working. I use journalctl -u my_service.service and observe the debugging output (via echo statements) of my_script.sh in the displayed log (at the end of it, where the latest output is) to see whether it's successful or not. | Hello, A quick internet search led me to these two links. I suppose they may give you some insight: manpage: systemd-halt.service Run a Linux systemd service during shutdown Hope this helps. Please, let me know. |
Hi folks I have been swearing over my Debian12 Xfce install for a few month now and it start to become really annoying. I get zombie processes on polkitd (pkla-check-auth) and this make the computer freeze eventually. But it only happen on 95% of the times after the computer wakes up.. so not 100% of the times. . . so i always need to restart the polkit service to get rid of the zombies. I really getting tired of remember to always check after restart if i have a zombie or not.. if i forget i end up in a semi freeze eventually even if it takes a whole day before it finally freeze up.. most often on next shutdown. as a last workaround I'm thinking of making a script that auto runs after restart to restart polkit or install another distro if the problem becomes to big of a problem, The logs do not say much.. perhaps you can see if i have missed something. Have you any ideas of what it can be, and how to fix it.. i just cant figure it out on my own as i dont have the time to spend more weeks on a problem when i need to use the computer for work. I'm grateful for any inputs. Here is my logs and i can not find what makes the polkit go zombie in auth.log at time 2024-01-07T16:43:28.7 //Marie auth.log Code: Select all2024-01-07T03:06:43.659492+01:00 a73s systemd-logind[695]: Power key pressed short. 2024-01-07T03:06:43.689036+01:00 a73s dbus-daemon[681]: [system] Rejected send message, 4 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=1207 comm="xfce4-power-manager --restart --sm-client-id 22d52") interface="org.freedesktop.NetworkManager" member="Sleep" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=743 comm="/usr/sbin/NetworkManager --no-daemon") 2024-01-07T03:06:44.254789+01:00 a73s systemd-logind[695]: The system will hibernate now! 2024-01-07T03:06:44.342027+01:00 a73s pkexec: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000) 2024-01-07T03:06:44.354547+01:00 a73s pkexec[470943]: user: Executing command [USER=root] [TTY=unknown] [CWD=/home/user] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness 0] 2024-01-07T03:06:44.357113+01:00 a73s dbus-daemon[681]: [system] Rejected send message, 4 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=1207 comm="xfce4-power-manager --restart --sm-client-id 22d52") interface="org.freedesktop.NetworkManager" member="Sleep" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=743 comm="/usr/sbin/NetworkManager --no-daemon") 2024-01-07T16:43:28.777214+01:00 a73s polkitd[444907]: Terminating runaway script after 15 seconds 2024-01-07T16:43:28.785404+01:00 a73s polkitd[444907]: Error evaluating admin rules: Error: Error spawning helper: Timed out after 10 seconds (g-io-error-quark, 24) 2024-01-07T16:43:29.379087+01:00 a73s systemd-logind[695]: Operation 'sleep' finished. Note ((Me restarting the polkitd service)) 2024-01-07T16:43:53.904971+01:00 a73s sudo: user : TTY=pts/2 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/systemctl restart polkit.service 2024-01-07T16:43:53.906852+01:00 a73s sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) 2024-01-07T16:43:54.008379+01:00 a73s polkitd[471547]: Loading rules from directory /etc/polkit-1/rules.d 2024-01-07T16:43:54.008633+01:00 a73s polkitd[471547]: Loading rules from directory /usr/share/polkit-1/rules.d 2024-01-07T16:43:54.012850+01:00 a73s polkitd[471547]: Finished loading, compiling and executing 9 rules 2024-01-07T16:43:54.016974+01:00 a73s polkitd[471547]: Acquired the name org.freedesktop.PolicyKit1 on the system bus 2024-01-07T16:43:54.021937+01:00 a73s sudo: pam_unix(sudo:session): session closed for user root 2024-01-07T16:43:54.617176+01:00 a73s polkitd[471547]: Registered Authentication Agent for unix-session:1 (system bus name :1.45 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8) and the Kern.log Code: Select all2024-01-07T03:06:44.537110+01:00 a73s kernel: [622923.614490] PM: hibernation: hibernation entry 2024-01-07T03:06:44.897241+01:00 a73s kernel: [622923.975722] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s 2024-01-07T03:06:44.897262+01:00 a73s kernel: [622923.975767] (NULL device *): firmware: direct-loading firmware regulatory.db 2024-01-07T16:43:28.436623+01:00 a73s kernel: [622923.994159] Filesystems sync: 0.018 seconds 2024-01-07T16:43:28.455236+01:00 a73s kernel: [622923.994305] Freezing user space processes 2024-01-07T16:43:28.458398+01:00 a73s kernel: [622924.000968] Freezing user space processes completed (elapsed 0.006 seconds) 2024-01-07T16:43:28.458412+01:00 a73s kernel: [622924.000981] OOM killer disabled. 2024-01-07T16:43:28.458415+01:00 a73s kernel: [622924.001151] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff] 2024-01-07T16:43:28.458416+01:00 a73s kernel: [622924.001156] PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000fffff] 2024-01-07T16:43:28.462814+01:00 a73s kernel: [622924.001160] PM: hibernation: Marking nosave pages: [mem 0x20000000-0x201fffff] 2024-01-07T16:43:28.462831+01:00 a73s kernel: [622924.001171] PM: hibernation: Marking nosave pages: [mem 0x40000000-0x401fffff] 2024-01-07T16:43:28.462834+01:00 a73s kernel: [622924.001182] PM: hibernation: Marking nosave pages: [mem 0xaad20000-0xaad8dfff] 2024-01-07T16:43:28.462835+01:00 a73s kernel: [622924.001186] PM: hibernation: Marking nosave pages: [mem 0xaad95000-0xaad95fff] 2024-01-07T16:43:28.462837+01:00 a73s kernel: [622924.001187] PM: hibernation: Marking nosave pages: [mem 0xaad97000-0xaadb7fff] 2024-01-07T16:43:28.462838+01:00 a73s kernel: [622924.001189] PM: hibernation: Marking nosave pages: [mem 0xaadc6000-0xaade7fff] 2024-01-07T16:43:28.462840+01:00 a73s kernel: [622924.001192] PM: hibernation: Marking nosave pages: [mem 0xaaf25000-0xaafe7fff] 2024-01-07T16:43:28.462841+01:00 a73s kernel: [622924.001197] PM: hibernation: Marking nosave pages: [mem 0xaaffd000-0xffffffff] 2024-01-07T16:43:28.462843+01:00 a73s kernel: [622924.003103] PM: hibernation: Basic memory bitmaps created 2024-01-07T16:43:28.462844+01:00 a73s kernel: [622924.003242] PM: hibernation: Preallocating image memory 2024-01-07T16:43:28.462846+01:00 a73s kernel: [622937.740713] PM: hibernation: Allocated 1195653 pages for snapshot 2024-01-07T16:43:28.466733+01:00 a73s kernel: [622937.740720] PM: hibernation: Allocated 4782612 kbytes in 13.73 seconds (348.33 MB/s) 2024-01-07T16:43:28.466751+01:00 a73s kernel: [622937.740724] Freezing remaining freezable tasks 2024-01-07T16:43:28.466753+01:00 a73s kernel: [622937.742764] Freezing remaining freezable tasks completed (elapsed 0.002 seconds) 2024-01-07T16:43:28.466754+01:00 a73s kernel: [622937.742972] printk: Suspending console(s) (use no_console_suspend to debug) 2024-01-07T16:43:28.466755+01:00 a73s kernel: [622937.756200] ata2.00: Entering standby power mode 2024-01-07T16:43:28.466757+01:00 a73s kernel: [622937.764198] ata1.00: Entering standby power mode 2024-01-07T16:43:28.466758+01:00 a73s kernel: [622938.373559] ACPI: EC: interrupt blocked 2024-01-07T16:43:28.466759+01:00 a73s kernel: [622938.374486] ACPI: PM: Preparing to enter system sleep state S4 2024-01-07T16:43:28.466761+01:00 a73s kernel: [622938.376285] ACPI: EC: event blocked 2024-01-07T16:43:28.466762+01:00 a73s kernel: [622938.376287] ACPI: EC: EC stopped 2024-01-07T16:43:28.466763+01:00 a73s kernel: [622938.376288] ACPI: PM: Saving platform NVS memory 2024-01-07T16:43:28.466764+01:00 a73s kernel: [622938.376854] Disabling non-boot CPUs ... 2024-01-07T16:43:28.466765+01:00 a73s kernel: [622938.378561] smpboot: CPU 1 is now offline 2024-01-07T16:43:28.466767+01:00 a73s kernel: [622938.380539] smpboot: CPU 2 is now offline 2024-01-07T16:43:28.466768+01:00 a73s kernel: [622938.382634] smpboot: CPU 3 is now offline 2024-01-07T16:43:28.466775+01:00 a73s kernel: [622938.383016] PM: hibernation: Creating image: 2024-01-07T16:43:28.466777+01:00 a73s kernel: [622938.644943] PM: hibernation: Need to copy 1193853 pages 2024-01-07T16:43:28.466779+01:00 a73s kernel: [622938.644948] PM: hibernation: Normal pages needed: 1193853 + 1024, available pages: 1927613 2024-01-07T16:43:28.466780+01:00 a73s kernel: [622938.384445] ACPI: PM: Restoring platform NVS memory 2024-01-07T16:43:28.466781+01:00 a73s kernel: [622938.384733] ACPI: EC: EC started 2024-01-07T16:43:28.466782+01:00 a73s kernel: [622938.385133] Enabling non-boot CPUs ... 2024-01-07T16:43:28.466783+01:00 a73s kernel: [622938.385236] x86: Booting SMP configuration: 2024-01-07T16:43:28.466784+01:00 a73s kernel: [622938.385239] smpboot: Booting Node 0 Processor 1 APIC 0x2 2024-01-07T16:43:28.466785+01:00 a73s kernel: [622938.388765] CPU1 is up 2024-01-07T16:43:28.474366+01:00 a73s kernel: [622938.388842] smpboot: Booting Node 0 Processor 2 APIC 0x1 2024-01-07T16:43:28.477390+01:00 a73s kernel: [622938.392818] CPU2 is up 2024-01-07T16:43:28.477408+01:00 a73s kernel: [622938.392898] smpboot: Booting Node 0 Processor 3 APIC 0x3 2024-01-07T16:43:28.477410+01:00 a73s kernel: [622938.396648] CPU3 is up 2024-01-07T16:43:28.477411+01:00 a73s kernel: [622938.403738] ACPI: PM: Waking up from system sleep state S4 2024-01-07T16:43:28.477412+01:00 a73s kernel: [622938.867345] ACPI: EC: interrupt unblocked 2024-01-07T16:43:28.477413+01:00 a73s kernel: [622938.868073] nvidia 0000:01:00.0: Enabling HDA controller 2024-01-07T16:43:28.477418+01:00 a73s kernel: [622939.397867] usb usb1: root hub lost power or was reset 2024-01-07T16:43:28.477420+01:00 a73s kernel: [622939.397909] ACPI: EC: event unblocked 2024-01-07T16:43:28.477421+01:00 a73s kernel: [622939.398070] usb usb2: root hub lost power or was reset 2024-01-07T16:43:28.477422+01:00 a73s kernel: [622939.398602] ath: phy0: ASPM enabled: 0x42 2024-01-07T16:43:28.477424+01:00 a73s kernel: [622939.694271] usb 2-1: reset high-speed USB device number 2 using ehci-pci 2024-01-07T16:43:28.477425+01:00 a73s kernel: [622939.694286] usb 1-1: reset high-speed USB device number 2 using ehci-pci 2024-01-07T16:43:28.477426+01:00 a73s kernel: [622939.745837] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 2024-01-07T16:43:28.477432+01:00 a73s kernel: [622939.745856] ata2.00: Entering active power mode 2024-01-07T16:43:28.477433+01:00 a73s kernel: [622939.745884] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) 2024-01-07T16:43:28.477435+01:00 a73s kernel: [622939.745914] ata1.00: Entering active power mode 2024-01-07T16:43:28.477436+01:00 a73s kernel: [622939.745944] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 2024-01-07T16:43:28.477437+01:00 a73s kernel: [622939.746946] ata2.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.477438+01:00 a73s kernel: [622939.747102] ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477439+01:00 a73s kernel: [622939.748807] ata3.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477440+01:00 a73s kernel: [622939.754246] ata3.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477442+01:00 a73s kernel: [622939.756245] ata3.00: configured for UDMA/100 2024-01-07T16:43:28.477443+01:00 a73s kernel: [622939.769548] ata2.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.477444+01:00 a73s kernel: [622939.769638] ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477445+01:00 a73s kernel: [622939.790934] ata2.00: configured for UDMA/133 2024-01-07T16:43:28.477450+01:00 a73s kernel: [622940.166127] usb 1-1.2: reset high-speed USB device number 4 using ehci-pci 2024-01-07T16:43:28.477452+01:00 a73s kernel: [622940.354220] usb 1-1.1: reset full-speed USB device number 52 using ehci-pci 2024-01-07T16:43:28.477453+01:00 a73s kernel: [622940.462503] usb 1-1.1: device firmware changed 2024-01-07T16:43:28.477454+01:00 a73s kernel: [622940.463869] PM: hibernation: Basic memory bitmaps freed 2024-01-07T16:43:28.477455+01:00 a73s kernel: [622940.464350] OOM killer enabled. 2024-01-07T16:43:28.477456+01:00 a73s kernel: [622940.464354] Restarting tasks ... 2024-01-07T16:43:28.477457+01:00 a73s kernel: [622940.468862] usb 1-1.1: USB disconnect, device number 52 2024-01-07T16:43:28.477462+01:00 a73s kernel: [622940.478632] done. 2024-01-07T16:43:28.477464+01:00 a73s kernel: [622940.478943] video LNXVIDEO:00: Restoring backlight state 2024-01-07T16:43:28.477465+01:00 a73s kernel: [622940.479279] video LNXVIDEO:01: Restoring backlight state 2024-01-07T16:43:28.477466+01:00 a73s kernel: [622940.498131] PM: hibernation: hibernation exit 2024-01-07T16:43:28.477481+01:00 a73s kernel: [622940.558044] usb 1-1.1: new full-speed USB device number 53 using ehci-pci 2024-01-07T16:43:28.593470+01:00 a73s kernel: [622940.672098] usb 1-1.1: New USB device found, idVendor=13d3, idProduct=3362, bcdDevice= 0.01 2024-01-07T16:43:28.593493+01:00 a73s kernel: [622940.672109] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2024-01-07T16:43:28.593496+01:00 a73s kernel: [622940.672113] usb 1-1.1: Product: Bluetooth USB Host Controller 2024-01-07T16:43:28.593498+01:00 a73s kernel: [622940.672117] usb 1-1.1: Manufacturer: Atheros Communications 2024-01-07T16:43:28.593499+01:00 a73s kernel: [622940.672120] usb 1-1.1: SerialNumber: Alaska Day 2006 2024-01-07T16:43:28.617548+01:00 a73s kernel: [622940.695883] usb 1-1.1: firmware: direct-loading firmware ar3k/AthrBT_0x01020200.dfu 2024-01-07T16:43:28.661068+01:00 a73s kernel: [622940.739940] usb 1-1.1: firmware: direct-loading firmware ar3k/ramps_0x01020200_40.dfu 2024-01-07T16:43:28.849302+01:00 a73s kernel: [622940.926725] ata1.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.849325+01:00 a73s kernel: [622940.927089] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.849327+01:00 a73s kernel: [622940.929583] ata1.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.849329+01:00 a73s kernel: [622940.929722] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.853172+01:00 a73s kernel: [622940.930867] ata1.00: configured for UDMA/133 2024-01-07T16:43:28.919808+01:00 a73s kernel: [622940.997086] usb 1-1.1: USB disconnect, device number 53 2024-01-07T16:43:29.142424+01:00 a73s kernel: [622941.218510] usb 1-1.1: new full-speed USB device number 54 using ehci-pci 2024-01-07T16:43:29.654754+01:00 a73s kernel: [622941.734641] atl1c 0000:04:00.0: atl1c: enp4s0 NIC Link is Up<1000 Mbps Full Duplex> 2024-01-07T16:43:34.269053+01:00 a73s kernel: [622946.348165] usb 1-1.1: New USB device found, idVendor=13d3, idProduct=3362, bcdDevice= 0.02 2024-01-07T16:43:34.269074+01:00 a73s kernel: [622946.348174] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2024-01-07T16:43:34.269076+01:00 a73s kernel: [622946.348177] usb 1-1.1: Product: Bluetooth USB Host Controller 2024-01-07T16:43:34.269079+01:00 a73s kernel: [622946.348179] usb 1-1.1: Manufacturer: Atheros Communications 2024-01-07T16:43:34.269080+01:00 a73s kernel: [622946.348190] usb 1-1.1: SerialNumber: Alaska Day 2006 2024-01-07T16:43:34.365421+01:00 a73s kernel: [622946.445194] Bluetooth: MGMT ver 1.22 2024-01-07T16:44:55.185072+01:00 a73s kernel: [623027.264015] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2024-01-07T16:44:55.209044+01:00 a73s kernel: [623027.288594] psmouse serio4: Touchpad at isa0060/serio4/input0 - driver resynced. 2024-01-07T16:50:44.392685+01:00 a73s kernel: [623376.469981] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2024-01-07T16:50:44.405110+01:00 a73s kernel: [623376.481332] psmouse serio4: Touchpad at isa0060/serio4/input0 - driver resynced. and the syslog Code: Select all2024-01-07T03:06:44.263753+01:00 a73s NetworkManager[743]: <info> [1704593204.2629] manager: sleep: sleep requested (sleeping: no enabled: yes) 2024-01-07T03:06:44.268070+01:00 a73s NetworkManager[743]: <info> [1704593204.2668] device (wlp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') 2024-01-07T03:06:44.269818+01:00 a73s ModemManager[444920]: <info> [sleep-monitor-systemd] system is about to suspend 2024-01-07T03:06:44.270162+01:00 a73s NetworkManager[743]: <info> [1704593204.2684] device (wlp3s0): set-hw-addr: reset MAC address to 00:08:CA:84:CD:0B (unmanage) 2024-01-07T03:06:44.271347+01:00 a73s NetworkManager[743]: <info> [1704593204.2703] manager: NetworkManager state is now ASLEEP 2024-01-07T03:06:44.271614+01:00 a73s NetworkManager[743]: <info> [1704593204.2705] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') 2024-01-07T03:06:44.273637+01:00 a73s dbus-daemon[681]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=743 comm="/usr/sbin/NetworkManager --no-daemon") 2024-01-07T03:06:44.310457+01:00 a73s systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... 2024-01-07T03:06:44.335284+01:00 a73s dbus-daemon[681]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 2024-01-07T03:06:44.335611+01:00 a73s systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. 2024-01-07T03:06:44.337380+01:00 a73s NetworkManager[743]: <info> [1704593204.3372] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') 2024-01-07T03:06:44.365175+01:00 a73s NetworkManager[743]: <info> [1704593204.3650] dhcp4 (enp4s0): canceled DHCP transaction 2024-01-07T03:06:44.371664+01:00 a73s NetworkManager[743]: <info> [1704593204.3651] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds) 2024-01-07T03:06:44.371829+01:00 a73s NetworkManager[743]: <info> [1704593204.3651] dhcp4 (enp4s0): state changed no lease 2024-01-07T03:06:44.391439+01:00 a73s avahi-daemon[676]: Withdrawing address record for 192.168.0.160 on enp4s0. 2024-01-07T03:06:44.391806+01:00 a73s avahi-daemon[676]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.160. 2024-01-07T03:06:44.391911+01:00 a73s avahi-daemon[676]: Interface enp4s0.IPv4 no longer relevant for mDNS. 2024-01-07T03:06:44.456537+01:00 a73s nm-openvpn[444621]: SIGTERM received, sending exit notification to peer 2024-01-07T03:06:44.457274+01:00 a73s NetworkManager[743]: <info> [1704593204.4543] device (enp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') 2024-01-07T03:06:44.494059+01:00 a73s systemd[1]: Reached target sleep.target - Sleep. 2024-01-07T03:06:44.510007+01:00 a73s systemd[1]: Starting systemd-hibernate.service - Hibernate... 2024-01-07T03:06:44.535918+01:00 a73s systemd-sleep[470960]: Entering sleep state 'hibernate'... 2024-01-07T03:06:44.537110+01:00 a73s kernel: [622923.614490] PM: hibernation: hibernation entry 2024-01-07T03:06:44.897241+01:00 a73s kernel: [622923.975722] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s 2024-01-07T03:06:44.897262+01:00 a73s kernel: [622923.975767] (NULL device *): firmware: direct-loading firmware regulatory.db 2024-01-07T16:43:28.436623+01:00 a73s kernel: [622923.994159] Filesystems sync: 0.018 seconds 2024-01-07T16:43:28.455236+01:00 a73s kernel: [622923.994305] Freezing user space processes 2024-01-07T16:43:28.458398+01:00 a73s kernel: [622924.000968] Freezing user space processes completed (elapsed 0.006 seconds) 2024-01-07T16:43:28.458412+01:00 a73s kernel: [622924.000981] OOM killer disabled. 2024-01-07T16:43:28.458415+01:00 a73s kernel: [622924.001151] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff] 2024-01-07T16:43:28.458416+01:00 a73s kernel: [622924.001156] PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000fffff] 2024-01-07T16:43:28.462814+01:00 a73s kernel: [622924.001160] PM: hibernation: Marking nosave pages: [mem 0x20000000-0x201fffff] 2024-01-07T16:43:28.462831+01:00 a73s kernel: [622924.001171] PM: hibernation: Marking nosave pages: [mem 0x40000000-0x401fffff] 2024-01-07T16:43:28.462834+01:00 a73s kernel: [622924.001182] PM: hibernation: Marking nosave pages: [mem 0xaad20000-0xaad8dfff] 2024-01-07T16:43:28.462835+01:00 a73s kernel: [622924.001186] PM: hibernation: Marking nosave pages: [mem 0xaad95000-0xaad95fff] 2024-01-07T16:43:28.462837+01:00 a73s kernel: [622924.001187] PM: hibernation: Marking nosave pages: [mem 0xaad97000-0xaadb7fff] 2024-01-07T16:43:28.462838+01:00 a73s kernel: [622924.001189] PM: hibernation: Marking nosave pages: [mem 0xaadc6000-0xaade7fff] 2024-01-07T16:43:28.462840+01:00 a73s kernel: [622924.001192] PM: hibernation: Marking nosave pages: [mem 0xaaf25000-0xaafe7fff] 2024-01-07T16:43:28.462841+01:00 a73s kernel: [622924.001197] PM: hibernation: Marking nosave pages: [mem 0xaaffd000-0xffffffff] 2024-01-07T16:43:28.462843+01:00 a73s kernel: [622924.003103] PM: hibernation: Basic memory bitmaps created 2024-01-07T16:43:28.462844+01:00 a73s kernel: [622924.003242] PM: hibernation: Preallocating image memory 2024-01-07T16:43:28.462846+01:00 a73s kernel: [622937.740713] PM: hibernation: Allocated 1195653 pages for snapshot 2024-01-07T16:43:28.466733+01:00 a73s kernel: [622937.740720] PM: hibernation: Allocated 4782612 kbytes in 13.73 seconds (348.33 MB/s) 2024-01-07T16:43:28.466751+01:00 a73s kernel: [622937.740724] Freezing remaining freezable tasks 2024-01-07T16:43:28.466753+01:00 a73s kernel: [622937.742764] Freezing remaining freezable tasks completed (elapsed 0.002 seconds) 2024-01-07T16:43:28.466754+01:00 a73s kernel: [622937.742972] printk: Suspending console(s) (use no_console_suspend to debug) 2024-01-07T16:43:28.466755+01:00 a73s kernel: [622937.756200] ata2.00: Entering standby power mode 2024-01-07T16:43:28.466757+01:00 a73s kernel: [622937.764198] ata1.00: Entering standby power mode 2024-01-07T16:43:28.466758+01:00 a73s kernel: [622938.373559] ACPI: EC: interrupt blocked 2024-01-07T16:43:28.466759+01:00 a73s kernel: [622938.374486] ACPI: PM: Preparing to enter system sleep state S4 2024-01-07T16:43:28.466761+01:00 a73s kernel: [622938.376285] ACPI: EC: event blocked 2024-01-07T16:43:28.466762+01:00 a73s kernel: [622938.376287] ACPI: EC: EC stopped 2024-01-07T16:43:28.466763+01:00 a73s kernel: [622938.376288] ACPI: PM: Saving platform NVS memory 2024-01-07T16:43:28.466764+01:00 a73s kernel: [622938.376854] Disabling non-boot CPUs ... 2024-01-07T16:43:28.466765+01:00 a73s kernel: [622938.378561] smpboot: CPU 1 is now offline 2024-01-07T16:43:28.466767+01:00 a73s kernel: [622938.380539] smpboot: CPU 2 is now offline 2024-01-07T16:43:28.466768+01:00 a73s kernel: [622938.382634] smpboot: CPU 3 is now offline 2024-01-07T16:43:28.466775+01:00 a73s kernel: [622938.383016] PM: hibernation: Creating image: 2024-01-07T16:43:28.466777+01:00 a73s kernel: [622938.644943] PM: hibernation: Need to copy 1193853 pages 2024-01-07T16:43:28.466779+01:00 a73s kernel: [622938.644948] PM: hibernation: Normal pages needed: 1193853 + 1024, available pages: 1927613 2024-01-07T16:43:28.466780+01:00 a73s kernel: [622938.384445] ACPI: PM: Restoring platform NVS memory 2024-01-07T16:43:28.466781+01:00 a73s kernel: [622938.384733] ACPI: EC: EC started 2024-01-07T16:43:28.466782+01:00 a73s kernel: [622938.385133] Enabling non-boot CPUs ... 2024-01-07T16:43:28.466783+01:00 a73s kernel: [622938.385236] x86: Booting SMP configuration: 2024-01-07T16:43:28.466784+01:00 a73s kernel: [622938.385239] smpboot: Booting Node 0 Processor 1 APIC 0x2 2024-01-07T16:43:28.466785+01:00 a73s kernel: [622938.388765] CPU1 is up 2024-01-07T16:43:28.474366+01:00 a73s kernel: [622938.388842] smpboot: Booting Node 0 Processor 2 APIC 0x1 2024-01-07T16:43:28.477390+01:00 a73s kernel: [622938.392818] CPU2 is up 2024-01-07T16:43:28.477408+01:00 a73s kernel: [622938.392898] smpboot: Booting Node 0 Processor 3 APIC 0x3 2024-01-07T16:43:28.477410+01:00 a73s kernel: [622938.396648] CPU3 is up 2024-01-07T16:43:28.477411+01:00 a73s kernel: [622938.403738] ACPI: PM: Waking up from system sleep state S4 2024-01-07T16:43:28.477412+01:00 a73s kernel: [622938.867345] ACPI: EC: interrupt unblocked 2024-01-07T16:43:28.477413+01:00 a73s kernel: [622938.868073] nvidia 0000:01:00.0: Enabling HDA controller 2024-01-07T16:43:28.477418+01:00 a73s kernel: [622939.397867] usb usb1: root hub lost power or was reset 2024-01-07T16:43:28.477420+01:00 a73s kernel: [622939.397909] ACPI: EC: event unblocked 2024-01-07T16:43:28.477421+01:00 a73s kernel: [622939.398070] usb usb2: root hub lost power or was reset 2024-01-07T16:43:28.477422+01:00 a73s kernel: [622939.398602] ath: phy0: ASPM enabled: 0x42 2024-01-07T16:43:28.477424+01:00 a73s kernel: [622939.694271] usb 2-1: reset high-speed USB device number 2 using ehci-pci 2024-01-07T16:43:28.477425+01:00 a73s kernel: [622939.694286] usb 1-1: reset high-speed USB device number 2 using ehci-pci 2024-01-07T16:43:28.477426+01:00 a73s kernel: [622939.745837] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 2024-01-07T16:43:28.477432+01:00 a73s kernel: [622939.745856] ata2.00: Entering active power mode 2024-01-07T16:43:28.477433+01:00 a73s kernel: [622939.745884] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) 2024-01-07T16:43:28.477435+01:00 a73s kernel: [622939.745914] ata1.00: Entering active power mode 2024-01-07T16:43:28.477436+01:00 a73s kernel: [622939.745944] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 2024-01-07T16:43:28.477437+01:00 a73s kernel: [622939.746946] ata2.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.477438+01:00 a73s kernel: [622939.747102] ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477439+01:00 a73s kernel: [622939.748807] ata3.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477440+01:00 a73s kernel: [622939.754246] ata3.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477442+01:00 a73s kernel: [622939.756245] ata3.00: configured for UDMA/100 2024-01-07T16:43:28.477443+01:00 a73s kernel: [622939.769548] ata2.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.477444+01:00 a73s kernel: [622939.769638] ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.477445+01:00 a73s kernel: [622939.790934] ata2.00: configured for UDMA/133 2024-01-07T16:43:28.477450+01:00 a73s kernel: [622940.166127] usb 1-1.2: reset high-speed USB device number 4 using ehci-pci 2024-01-07T16:43:28.477452+01:00 a73s kernel: [622940.354220] usb 1-1.1: reset full-speed USB device number 52 using ehci-pci 2024-01-07T16:43:28.477453+01:00 a73s kernel: [622940.462503] usb 1-1.1: device firmware changed 2024-01-07T16:43:28.477454+01:00 a73s kernel: [622940.463869] PM: hibernation: Basic memory bitmaps freed 2024-01-07T16:43:28.477455+01:00 a73s kernel: [622940.464350] OOM killer enabled. 2024-01-07T16:43:28.477456+01:00 a73s kernel: [622940.464354] Restarting tasks ... 2024-01-07T16:43:28.477457+01:00 a73s kernel: [622940.468862] usb 1-1.1: USB disconnect, device number 52 2024-01-07T16:43:28.477462+01:00 a73s kernel: [622940.478632] done. 2024-01-07T16:43:28.477464+01:00 a73s kernel: [622940.478943] video LNXVIDEO:00: Restoring backlight state 2024-01-07T16:43:28.477465+01:00 a73s kernel: [622940.479279] video LNXVIDEO:01: Restoring backlight state 2024-01-07T16:43:28.477466+01:00 a73s kernel: [622940.498131] PM: hibernation: hibernation exit 2024-01-07T16:43:28.477481+01:00 a73s kernel: [622940.558044] usb 1-1.1: new full-speed USB device number 53 using ehci-pci 2024-01-07T16:43:28.593470+01:00 a73s kernel: [622940.672098] usb 1-1.1: New USB device found, idVendor=13d3, idProduct=3362, bcdDevice= 0.01 2024-01-07T16:43:28.593493+01:00 a73s kernel: [622940.672109] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2024-01-07T16:43:28.593496+01:00 a73s kernel: [622940.672113] usb 1-1.1: Product: Bluetooth USB Host Controller 2024-01-07T16:43:28.593498+01:00 a73s kernel: [622940.672117] usb 1-1.1: Manufacturer: Atheros Communications 2024-01-07T16:43:28.593499+01:00 a73s kernel: [622940.672120] usb 1-1.1: SerialNumber: Alaska Day 2006 2024-01-07T16:43:28.617548+01:00 a73s kernel: [622940.695883] usb 1-1.1: firmware: direct-loading firmware ar3k/AthrBT_0x01020200.dfu 2024-01-07T16:43:28.661068+01:00 a73s kernel: [622940.739940] usb 1-1.1: firmware: direct-loading firmware ar3k/ramps_0x01020200_40.dfu 2024-01-07T16:43:28.750937+01:00 a73s systemd-sleep[470960]: System returned from sleep state. 2024-01-07T16:43:28.764612+01:00 a73s rtkit-daemon[952]: The canary thread is apparently starving. Taking action. 2024-01-07T16:43:28.768487+01:00 a73s NetworkManager[743]: <info> [1704642208.6304] device (tun0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') 2024-01-07T16:43:28.768830+01:00 a73s rtkit-daemon[952]: Demoting known real-time threads. 2024-01-07T16:43:28.769117+01:00 a73s rtkit-daemon[952]: Demoted 0 threads. 2024-01-07T16:43:28.783172+01:00 a73s systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. 2024-01-07T16:43:28.787386+01:00 a73s dbus-daemon[681]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=743 comm="/usr/sbin/NetworkManager --no-daemon") 2024-01-07T16:43:28.846490+01:00 a73s systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... 2024-01-07T16:43:28.849302+01:00 a73s kernel: [622940.926725] ata1.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.849325+01:00 a73s kernel: [622940.927089] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.849327+01:00 a73s kernel: [622940.929583] ata1.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out 2024-01-07T16:43:28.849329+01:00 a73s kernel: [622940.929722] ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out 2024-01-07T16:43:28.853172+01:00 a73s kernel: [622940.930867] ata1.00: configured for UDMA/133 2024-01-07T16:43:28.858627+01:00 a73s systemd-sleep[471108]: /dev/sda: 2024-01-07T16:43:28.859009+01:00 a73s systemd-sleep[471108]: setting Advanced Power Management level to 0xfe (254) 2024-01-07T16:43:28.859071+01:00 a73s systemd-sleep[471108]: APM_level#011= 254 2024-01-07T16:43:28.859409+01:00 a73s systemd[1]: Started anacron.service - Run anacron jobs. 2024-01-07T16:43:28.871642+01:00 a73s systemd[1]: Starting apt-daily.service - Daily apt download activities... 2024-01-07T16:43:28.879574+01:00 a73s anacron[471114]: Anacron 2.3 started on 2024-01-07 2024-01-07T16:43:28.880182+01:00 a73s systemd[1]: Starting e2scrub_all.service - Online ext4 Metadata Check for All Filesystems... 2024-01-07T16:43:28.882351+01:00 a73s anacron[471114]: Will run job `cron.daily' in 5 min. 2024-01-07T16:43:28.897136+01:00 a73s systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... 2024-01-07T16:43:28.898561+01:00 a73s anacron[471114]: Jobs will be executed sequentially 2024-01-07T16:43:28.901808+01:00 a73s systemd[1]: Starting plocate-updatedb.service - Update the plocate database... 2024-01-07T16:43:28.910665+01:00 a73s systemd[1]: Starting sysstat-collect.service - system activity accounting tool... 2024-01-07T16:43:28.919808+01:00 a73s kernel: [622940.997086] usb 1-1.1: USB disconnect, device number 53 2024-01-07T16:43:28.929556+01:00 a73s systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... 2024-01-07T16:43:28.930293+01:00 a73s systemd[1]: Starting man-db.service - Daily man-db regeneration... 2024-01-07T16:43:28.959426+01:00 a73s systemd[1]: sysstat-collect.service: Deactivated successfully. 2024-01-07T16:43:28.959602+01:00 a73s systemd[1]: Finished sysstat-collect.service - system activity accounting tool. 2024-01-07T16:43:28.983667+01:00 a73s systemd[1]: e2scrub_all.service: Deactivated successfully. 2024-01-07T16:43:28.983943+01:00 a73s systemd[1]: Finished e2scrub_all.service - Online ext4 Metadata Check for All Filesystems. 2024-01-07T16:43:29.045262+01:00 a73s systemd-sleep[471148]: /dev/sdb: 2024-01-07T16:43:29.045425+01:00 a73s systemd-sleep[471148]: setting Advanced Power Management level to 0xfe (254) 2024-01-07T16:43:29.045489+01:00 a73s systemd-sleep[471148]: APM_level#011= 254 2024-01-07T16:43:29.088924+01:00 a73s dbus-daemon[681]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 2024-01-07T16:43:29.091513+01:00 a73s systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. 2024-01-07T16:43:29.104663+01:00 a73s systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status. 2024-01-07T16:43:29.142424+01:00 a73s kernel: [622941.218510] usb 1-1.1: new full-speed USB device number 54 using ehci-pci 2024-01-07T16:43:29.157770+01:00 a73s systemd[1]: Stopped target bluetooth.target - Bluetooth Support. 2024-01-07T16:43:29.176448+01:00 a73s systemd[923]: Stopped target bluetooth.target - Bluetooth. 2024-01-07T16:43:29.205922+01:00 a73s fwupd[467117]: 15:43:29.172 FuPluginIntelMe failed to get public key using /fpf/OemCred: generic failure [0x9e] 2024-01-07T16:43:29.375922+01:00 a73s systemd[1]: systemd-hibernate.service: Deactivated successfully. 2024-01-07T16:43:29.376109+01:00 a73s systemd[1]: Finished systemd-hibernate.service - Hibernate. 2024-01-07T16:43:29.376213+01:00 a73s systemd[1]: systemd-hibernate.service: Consumed 13.221s CPU time. 2024-01-07T16:43:29.376712+01:00 a73s systemd[1]: Reached target hibernate.target - System Hibernation. 2024-01-07T16:43:29.377024+01:00 a73s systemd[1]: Stopped target sleep.target - Sleep. 2024-01-07T16:43:29.377438+01:00 a73s systemd[1]: Stopped target hibernate.target - System Hibernation. 2024-01-07T16:43:29.381628+01:00 a73s NetworkManager[743]: <info> [1704642209.3815] manager: sleep: wake requested (sleeping: yes enabled: yes) 2024-01-07T16:43:29.382275+01:00 a73s NetworkManager[743]: <info> [1704642209.3816] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') 2024-01-07T16:43:29.383503+01:00 a73s ModemManager[444920]: <info> [sleep-monitor-systemd] system is resuming 2024-01-07T16:43:29.415533+01:00 a73s NetworkManager[743]: <info> [1704642209.4118] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') 2024-01-07T16:43:29.415727+01:00 a73s NetworkManager[743]: <info> [1704642209.4135] device (wlp3s0): set-hw-addr: set MAC address to 06:09:61:F7:3C:78 (scanning) 2024-01-07T16:43:29.415860+01:00 a73s NetworkManager[743]: <info> [1704642209.4143] manager: NetworkManager state is now DISCONNECTED 2024-01-07T16:43:29.654421+01:00 a73s NetworkManager[743]: <info> [1704642209.6541] device (enp4s0): carrier: link connected 2024-01-07T16:43:29.654754+01:00 a73s kernel: [622941.734641] atl1c 0000:04:00.0: atl1c: enp4s0 NIC Link is Up<1000 Mbps Full Duplex> 2024-01-07T16:43:29.655773+01:00 a73s NetworkManager[743]: <info> [1704642209.6545] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') 2024-01-07T16:43:29.656339+01:00 a73s NetworkManager[743]: <info> [1704642209.6554] policy: auto-activating connection 'Wired connection 1' (4010882a-d40c-48e7-8042-7ba7be24bccd) 2024-01-07T16:43:29.656479+01:00 a73s NetworkManager[743]: <info> [1704642209.6563] device (enp4s0): Activation: starting connection 'Wired connection 1' (4010882a-d40c-48e7-8042-7ba7be24bccd) 2024-01-07T16:43:29.656614+01:00 a73s NetworkManager[743]: <info> [1704642209.6564] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') 2024-01-07T16:43:29.656933+01:00 a73s NetworkManager[743]: <info> [1704642209.6568] manager: NetworkManager state is now CONNECTING 2024-01-07T16:43:29.657199+01:00 a73s NetworkManager[743]: <info> [1704642209.6571] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') 2024-01-07T16:43:29.658064+01:00 a73s NetworkManager[743]: <info> [1704642209.6579] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') 2024-01-07T16:43:29.658481+01:00 a73s NetworkManager[743]: <info> [1704642209.6584] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds) 2024-01-07T16:43:30.057211+01:00 a73s fwupdmgr[471124]: Uppdaterar lvfs 2024-01-07T16:43:30.112613+01:00 a73s fwupdmgr[471124]: Hämtar… [ - ]Hämtar… [ - ] 2024-01-07T16:43:30.121163+01:00 a73s systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE 2024-01-07T16:43:30.121375+01:00 a73s systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. 2024-01-07T16:43:30.121527+01:00 a73s systemd[1]: Failed to start fwupd-refresh.service - Refresh fwupd metadata and update motd. 2024-01-07T16:43:31.673449+01:00 a73s NetworkManager[743]: <info> [1704642211.6728] dhcp4 (enp4s0): state changed new lease, address=192.168.0.160 2024-01-07T16:43:31.673987+01:00 a73s NetworkManager[743]: <info> [1704642211.6735] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS 2024-01-07T16:43:31.697749+01:00 a73s avahi-daemon[676]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.160. 2024-01-07T16:43:31.697935+01:00 a73s avahi-daemon[676]: New relevant interface enp4s0.IPv4 for mDNS. 2024-01-07T16:43:31.698031+01:00 a73s avahi-daemon[676]: Registering new address record for 192.168.0.160 on enp4s0.IPv4. 2024-01-07T16:43:31.712298+01:00 a73s NetworkManager[743]: <info> [1704642211.7121] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') 2024-01-07T16:43:31.721324+01:00 a73s NetworkManager[743]: <info> [1704642211.7211] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') 2024-01-07T16:43:31.722878+01:00 a73s NetworkManager[743]: <info> [1704642211.7221] vpn[0x55d0b0bb01f0,c083f866-9e8b-4457-bcbe-389d0240dd93,"Bahnhof-VPN"]: starting openvpn 2024-01-07T16:43:31.925759+01:00 a73s nm-openvpn[471295]: OpenVPN 2.6.3 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] 2024-01-07T16:43:32.373687+01:00 a73s nm-openvpn[471295]: library versions: OpenSSL 3.0.11 19 Sep 2023, LZO 2.10 2024-01-07T16:43:32.374378+01:00 a73s nm-openvpn[471295]: DCO version: N/A 2024-01-07T16:43:32.374839+01:00 a73s ModemManager[444920]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0': not supported by any plugin 2024-01-07T16:43:32.374976+01:00 a73s ModemManager[444920]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:04:00.0': not supported by any plugin 2024-01-07T16:43:32.375083+01:00 a73s nm-openvpn[471295]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2024-01-07T16:43:32.375301+01:00 a73s nm-openvpn[471295]: TCP/UDP: Preserving recently used remote address: [AF_INET]85.24.253.48:1198 2024-01-07T16:43:32.376043+01:00 a73s nm-openvpn[471295]: UDPv4 link local: (not bound) 2024-01-07T16:43:32.376170+01:00 a73s nm-openvpn[471295]: UDPv4 link remote: [AF_INET]85.24.253.48:1198 2024-01-07T16:43:32.376276+01:00 a73s nm-openvpn[471295]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay 2024-01-07T16:43:32.376349+01:00 a73s nm-openvpn[471295]: [integrityvpn] Peer Connection Initiated with [AF_INET]85.24.253.48:1198 2024-01-07T16:43:33.390210+01:00 a73s nm-openvpn[471295]: AUTH: Received control message: AUTH_FAILED 2024-01-07T16:43:33.390419+01:00 a73s nm-openvpn[471295]: SIGUSR1[soft,auth-failure] received, process restarting 2024-01-07T16:43:34.111129+01:00 a73s systemd[1]: systemd-rfkill.service: Deactivated successfully. 2024-01-07T16:43:34.269053+01:00 a73s kernel: [622946.348165] usb 1-1.1: New USB device found, idVendor=13d3, idProduct=3362, bcdDevice= 0.02 2024-01-07T16:43:34.269074+01:00 a73s kernel: [622946.348174] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2024-01-07T16:43:34.269076+01:00 a73s kernel: [622946.348177] usb 1-1.1: Product: Bluetooth USB Host Controller 2024-01-07T16:43:34.269079+01:00 a73s kernel: [622946.348179] usb 1-1.1: Manufacturer: Atheros Communications 2024-01-07T16:43:34.269080+01:00 a73s kernel: [622946.348190] usb 1-1.1: SerialNumber: Alaska Day 2006 2024-01-07T16:43:34.293846+01:00 a73s systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... 2024-01-07T16:43:34.295597+01:00 a73s systemd[1]: man-db.service: Deactivated successfully. 2024-01-07T16:43:34.296259+01:00 a73s systemd[1]: Finished man-db.service - Daily man-db regeneration. 2024-01-07T16:43:34.331107+01:00 a73s systemd[1]: Reached target bluetooth.target - Bluetooth Support. 2024-01-07T16:43:34.337078+01:00 a73s systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status. 2024-01-07T16:43:34.340251+01:00 a73s systemd[923]: Reached target bluetooth.target - Bluetooth. 2024-01-07T16:43:34.365421+01:00 a73s kernel: [622946.445194] Bluetooth: MGMT ver 1.22 2024-01-07T16:43:34.368039+01:00 a73s bluetoothd[678]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. 2024-01-07T16:43:34.368273+01:00 a73s bluetoothd[678]: sap-server: Operation not permitted (1) 2024-01-07T16:43:38.670556+01:00 a73s nm-openvpn[471295]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2024-01-07T16:43:38.671057+01:00 a73s nm-openvpn[471295]: TCP/UDP: Preserving recently used remote address: [AF_INET]85.24.253.48:1198 2024-01-07T16:43:38.671195+01:00 a73s nm-openvpn[471295]: UDPv4 link local: (not bound) 2024-01-07T16:43:38.671306+01:00 a73s nm-openvpn[471295]: UDPv4 link remote: [AF_INET]85.24.253.48:1198 2024-01-07T16:43:38.737634+01:00 a73s nm-openvpn[471295]: [integrityvpn] Peer Connection Initiated with [AF_INET]85.24.253.48:1198 2024-01-07T16:43:39.342980+01:00 a73s systemd[1]: systemd-rfkill.service: Deactivated successfully. 2024-01-07T16:43:39.856719+01:00 a73s nm-openvpn[471295]: AUTH: Received control message: AUTH_FAILED 2024-01-07T16:43:39.857069+01:00 a73s nm-openvpn[471295]: SIGUSR1[soft,auth-failure] received, process restarting 2024-01-07T16:43:40.438347+01:00 a73s systemd[1]: plocate-updatedb.service: Deactivated successfully. 2024-01-07T16:43:40.438575+01:00 a73s systemd[1]: Finished plocate-updatedb.service - Update the plocate database. 2024-01-07T16:43:40.438832+01:00 a73s systemd[1]: plocate-updatedb.service: Consumed 3.238s CPU time. 2024-01-07T16:43:41.732406+01:00 a73s systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. 2024-01-07T16:43:43.360034+01:00 a73s nm-openvpn[471295]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2024-01-07T16:43:43.360259+01:00 a73s nm-openvpn[471295]: TCP/UDP: Preserving recently used remote address: [AF_INET]85.24.253.48:1198 2024-01-07T16:43:43.360369+01:00 a73s nm-openvpn[471295]: UDPv4 link local: (not bound) 2024-01-07T16:43:43.360461+01:00 a73s nm-openvpn[471295]: UDPv4 link remote: [AF_INET]85.24.253.48:1198 2024-01-07T16:43:43.409394+01:00 a73s nm-openvpn[471295]: [integrityvpn] Peer Connection Initiated with [AF_INET]85.24.253.48:1198 2024-01-07T16:43:43.417276+01:00 a73s nm-openvpn[471295]: Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:7: block-outside-dns (2.6.3) 2024-01-07T16:43:43.417626+01:00 a73s nm-openvpn[471295]: sitnl_send: rtnl: generic error (-95): Operation not supported 2024-01-07T16:43:43.423724+01:00 a73s NetworkManager[743]: <info> [1704642223.4224] manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/30) 2024-01-07T16:43:43.429412+01:00 a73s nm-openvpn[471295]: TUN/TAP device tun0 opened 2024-01-07T16:43:43.429787+01:00 a73s nm-openvpn[471295]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 471287 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_88 --tun -- tun0 1500 0 10.251.26.9 255.255.255.0 init 2024-01-07T16:43:43.459609+01:00 a73s nm-openvpn[471295]: UID set to nm-openvpn 2024-01-07T16:43:43.459816+01:00 a73s nm-openvpn[471295]: GID set to nm-openvpn 2024-01-07T16:43:43.459929+01:00 a73s nm-openvpn[471295]: Capabilities retained: CAP_NET_ADMIN 2024-01-07T16:43:43.460565+01:00 a73s nm-openvpn[471295]: Initialization Sequence Completed 2024-01-07T16:43:43.492711+01:00 a73s NetworkManager[743]: <info> [1704642223.4925] device (tun0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') 2024-01-07T16:43:43.494429+01:00 a73s dbus-daemon[681]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=743 comm="/usr/sbin/NetworkManager --no-daemon") 2024-01-07T16:43:43.498548+01:00 a73s NetworkManager[743]: <info> [1704642223.4984] device (tun0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') 2024-01-07T16:43:43.501189+01:00 a73s NetworkManager[743]: <info> [1704642223.5008] device (tun0): Activation: starting connection 'tun0' (5690ce0c-111b-4fb8-9621-b306d697aeed) 2024-01-07T16:43:43.501375+01:00 a73s NetworkManager[743]: <info> [1704642223.5011] device (tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') 2024-01-07T16:43:43.501905+01:00 a73s NetworkManager[743]: <info> [1704642223.5016] device (tun0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') 2024-01-07T16:43:43.503537+01:00 a73s NetworkManager[743]: <info> [1704642223.5028] device (tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') 2024-01-07T16:43:43.506669+01:00 a73s NetworkManager[743]: <info> [1704642223.5063] device (tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') 2024-01-07T16:43:43.530791+01:00 a73s systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... 2024-01-07T16:43:43.544810+01:00 a73s dbus-daemon[681]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 2024-01-07T16:43:43.545237+01:00 a73s systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. 2024-01-07T16:43:43.547801+01:00 a73s NetworkManager[743]: <info> [1704642223.5475] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') 2024-01-07T16:43:43.551510+01:00 a73s NetworkManager[743]: <info> [1704642223.5494] manager: NetworkManager state is now CONNECTED_SITE 2024-01-07T16:43:43.551713+01:00 a73s NetworkManager[743]: <info> [1704642223.5500] manager: NetworkManager state is now CONNECTED_LOCAL 2024-01-07T16:43:43.551836+01:00 a73s NetworkManager[743]: <info> [1704642223.5502] manager: NetworkManager state is now CONNECTED_SITE 2024-01-07T16:43:43.551958+01:00 a73s NetworkManager[743]: <info> [1704642223.5503] policy: set 'Bahnhof-VPN' (tun0) as default for IPv4 routing and DNS 2024-01-07T16:43:43.573466+01:00 a73s NetworkManager[743]: <info> [1704642223.5733] device (enp4s0): Activation: successful, device activated. 2024-01-07T16:43:43.574856+01:00 a73s NetworkManager[743]: <info> [1704642223.5741] manager: NetworkManager state is now CONNECTED_GLOBAL 2024-01-07T16:43:43.578962+01:00 a73s NetworkManager[743]: <info> [1704642223.5787] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') 2024-01-07T16:43:43.579630+01:00 a73s NetworkManager[743]: <info> [1704642223.5795] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') 2024-01-07T16:43:43.580549+01:00 a73s NetworkManager[743]: <info> [1704642223.5804] device (tun0): Activation: successful, device activated. 2024-01-07T16:43:44.369464+01:00 a73s systemd[1]: apt-daily.service: Deactivated successfully. 2024-01-07T16:43:44.369801+01:00 a73s systemd[1]: Finished apt-daily.service - Daily apt download activities. 2024-01-07T16:43:44.397757+01:00 a73s systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities... 2024-01-07T16:43:45.099454+01:00 a73s systemd[1]: apt-daily-upgrade.service: Deactivated successfully. 2024-01-07T16:43:45.099615+01:00 a73s systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities. 2024-01-07T16:43:48.419057+01:00 a73s smartd[690]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 162 to 250 2024-01-07T16:43:49.173364+01:00 a73s smartd[690]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 74 2024-01-07T16:43:49.173838+01:00 a73s smartd[690]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 66 to 74 2024-01-07T16:43:53.763001+01:00 a73s systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. 2024-01-07T16:43:53.916800+01:00 a73s ModemManager[444920]: <info> caught signal, shutting down... 2024-01-07T16:43:53.916992+01:00 a73s systemd[1]: Stopping ModemManager.service - Modem Manager... 2024-01-07T16:43:53.948125+01:00 a73s NetworkManager[743]: <info> [1704642233.9474] modem-manager: ModemManager no longer available 2024-01-07T16:43:53.948429+01:00 a73s ModemManager[444920]: <info> ModemManager is shut down 2024-01-07T16:43:53.957366+01:00 a73s systemd[1]: ModemManager.service: Deactivated successfully. 2024-01-07T16:43:53.957745+01:00 a73s systemd[1]: Stopped ModemManager.service - Modem Manager. 2024-01-07T16:43:53.959033+01:00 a73s systemd[1]: Stopping polkit.service - Authorization Manager... 2024-01-07T16:43:53.973681+01:00 a73s systemd[1]: polkit.service: Deactivated successfully. 2024-01-07T16:43:53.973957+01:00 a73s systemd[1]: Stopped polkit.service - Authorization Manager. 2024-01-07T16:43:53.994235+01:00 a73s systemd[1]: Starting polkit.service - Authorization Manager... 2024-01-07T16:43:54.001479+01:00 a73s polkitd[471547]: Started polkitd version 122 2024-01-07T16:43:54.016790+01:00 a73s systemd[1]: Started polkit.service - Authorization Manager. 2024-01-07T16:43:54.018237+01:00 a73s systemd[1]: Starting ModemManager.service - Modem Manager... 2024-01-07T16:43:54.066620+01:00 a73s ModemManager[471561]: <info> ModemManager (version 1.20.4) starting in system bus... 2024-01-07T16:43:54.634798+01:00 a73s systemd[1]: Started ModemManager.service - Modem Manager. 2024-01-07T16:43:54.680562+01:00 a73s NetworkManager[743]: <info> [1704642234.6804] modem-manager: ModemManager now available . Edit I forgot to mention the hardware Code: Select allSystem: Kernel: 6.1.0-16-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Xfce v: 4.18.1 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Laptop System: ASUSTeK product: K73SD v: 1.0 serial: <filter> Mobo: ASUSTeK model: K73SD v: 1.0 serial: <filter> BIOS: American Megatrends v: K73SD.206 date: 06/20/2012 Memory: RAM: total: 11.59 GiB used: 8.75 GiB (75.5%) Array-1: capacity: 32 GiB slots: 4 EC: None max-module-size: 8 GiB note: est. Device-1: ChannelA-DIMM0 type: DDR3 size: 4 GiB speed: 1333 MT/s Device-2: ChannelA-DIMM1 type: no module installed Device-3: ChannelB-DIMM0 type: DDR3 size: 8 GiB speed: 1333 MT/s Device-4: ChannelB-DIMM1 type: no module installed CPU: Info: dual core model: Intel Core i3-2350M bits: 64 type: MT MCP arch: Sandy Bridge rev: 7 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 1022 high: 1351 min/max: 800/2300 cores: 1: 859 2: 1351 3: 893 4: 986 bogomips: 18357 Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel arch: Gen-6 bus-ID: 00:02.0 Device-2: NVIDIA GF119M [GeForce 610M] vendor: ASUSTeK driver: nvidia v: 390.157 arch: Fermi bus-ID: 01:00.0 Device-3: IMC Networks UVC VGA Webcam type: USB driver: uvcvideo bus-ID: 1-1.2:4 Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa failed: nvidia dri: crocus gpu: i915 resolution: 1600x900~60Hz API: OpenGL v: N/A renderer: N/A direct-render: N/A Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK 6 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 API: ALSA v: k6.1.0-16-amd64 status: kernel-api Server-1: PulseAudio v: 16.1 status: active (root, process) Network: Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: AzureWave driver: ath9k v: kernel bus-ID: 03:00.0 IF: wlp3s0 state: down mac: <filter> Device-2: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: ASUSTeK driver: atl1c v: kernel port: a000 bus-ID: 04:00.0 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A Bluetooth: Device-1: IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter type: USB driver: btusb v: 0.8 bus-ID: 1-1.1:54 Report: hciconfig ID: hci0 rfk-id: 28 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 Drives: Local Storage: total: 835.54 GiB used: 217.3 GiB (26.0%) ID-1: /dev/sda vendor: Hitachi model: HTS547564A9E384 size: 596.17 GiB ID-2: /dev/sdb vendor: Micron model: MTFDDAK256MAY-1AH1ZABHA size: 238.47 GiB ID-3: /dev/sdc type: USB model: CCR-70 size: 913 MiB Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-RAM UJ8B0AW rev: 1.00 dev-links: cdrom Partition: ID-1: / size: 136.74 GiB used: 24.17 GiB (17.7%) fs: ext4 dev: /dev/sdb1 label: N/A uuid: 635811a1-38ca-45d2-9483-180a2432e062 Swap: ID-1: swap-1 type: partition size: 22.47 GiB used: 8.3 GiB (36.9%) dev: /dev/sdb3 label: N/A uuid: 7e093a79-d7c1-4587-8f6a-b713ef6e36e1 Sensors: System Temperatures: cpu: 55.0 C mobo: N/A Fan Speeds (RPM): cpu: 2200 Info: Processes: 310 Uptime: 14d 5h 9m Init: systemd target: graphical (5) Compilers: gcc: 12.2.0 Packages: 2850 Shell: Sudo v: 1.9.13p3 inxi: 3.3.26 | something is initializing an authority chain that is not being answered. Marie SWE wrote: 2024-01-07 17:21 2024-01-07T16:43:54.012850+01:00 a73s polkitd[471547]: Finished loading, compiling and executing 9 rules Post a cat of these rules. It may be useful to check these rules in a terminal, with execution in a terminal, or checking with pkcheck. Marie SWE wrote: 2024-01-07 17:21 2024-01-07T03:06:44.354547+01:00 a73s pkexec[470943]: user: Executing command [USER=root] [TTY=unknown] [CWD=/home/user] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness 0] 2024-01-07T03:06:44.357113+01:00 a73s dbus-daemon[681]: [system] Rejected send message, 4 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=1207 comm="xfce4-power-manager --restart --sm-client-id 22d52") interface="org.freedesktop.NetworkManager" member="Sleep" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=743 comm="/usr/sbin/NetworkManager --no-daemon") 2024-01-07T16:43:28.777214+01:00 a73s polkitd[444907]: Terminating runaway script after 15 seconds 2024-01-07T16:43:28.785404+01:00 a73s polkitd[444907]: Error evaluating admin rules: Error: Error spawning helper: Timed out after 10 seconds (g-io-error-quark, 24) Well that quote came out garbled, as not a NetworkManager on a sleeping laptop user, I might not be of much help. |
Hi I just installed Debian 12.1 Xfce with the full ISO I'm known for hating the installing and tweaking part on computers, since the last 3years.. no matter the operating systems Win/Mac or Linux, and sadly Computers are needed in the year 2023, so i can not throw them out the window and solve everything that way. So my solution is, aim for the OS with longest life, as then i don't have to do it to often. I have three laptops and one desktops that is total EOL now year 2023 (1xWin7ESU) 3xWin8.1 and they was dualboot LMDE3 Linux was EOL first and then now Windows this year. Then i also have two Desktops that running Debian10+11 so they are okay for a few years more.. So now i need to install Debian12 on three laptops and one desktop. My plan is to install, tweak, remove and add software on one... and then create scripts out of that one to run on the others to ease my pain. So hopefully I only have to swear and use ugly words one time the next years to come. So with that introduction said.. I have two small things.. I start with what my first victim is.. It is an old laptop i use for research and as it is 17.6" i have a hard time depart from this one. Brand Asus 17.6" CPU i3-2350M Ram12GB.(planing to put in 16GB) Graphics: Primary Intel 2 gen integrated i915 driver.... Secondary Nvidia GF119M(Geforce 610) nouveau driver. Disks: Primary Disk SSD Micron 256GB Three partitions: / swap(32GB) and Timeshift-backup.... Secondary Disk: 1TB HDD Three partitions: OEM-Recovery, Secondary-OS (win7ESU) and Data.. and one DVD-RW This one had LMDE3 on a HDD but i put in an SSD now for Debian to speed up the computer a bit. I started with installing Debian11 but i realize 12 is soon out, so i never finish that install as summer was coming and i don't need the laptop until September again. I have not done any deep research do to lack of time. so the 1st solution might be easy or not. . 1st Phenomenon Hibernation fails some times.. It works 80% of the time. and when it don't work.. symptoms, it first disconnect from Lan and then the screen goes black as it should.. 1 or 2second later the screens comes on again and the Lan connects again.... I can try put it to hibernation 10times in a row and same result.. then if put it to sleep when hibernation fails... then goes to sleep without problem and stays a sleep... Then when i wake it up again and put it directly back down to Hibernation again and then hibernation works again. So those times Hibernation don't work i just put it to sleep for 10seconds (or a day, it do not matter).. then Hibernation works again. I did not have that problem with LMDE3 (that builds on Debian9.) Thought i have.. I did change from HDD to SSD.. Can it be a fstab entry that is needed for Fstab, do to the SSD.. i dont know.. just a wild guess I'm waiting for it to happen again, as i did not check the logs the last time it happen, as i was busy with other things and when i came back it had totally slipped my mind. so please do not ask for logs yet.. please. i will post log entries as soon it happens gain . 2nd Grub entry.. this one is probably easy for you that might have been around on bookworm testing for a year or so... I didn't find any answers after 6hours searching. I have this line in my Grub GRUB_CMDLINE_LINUX="initrd=/install/gtk/initrd.gz" I have search this forum and no one seems to have that line... of those that has posted their grub of Debian12 in here. Debian10 non-free and Debian 11 none-free, do not have this line. I just tested to install them on a older test-laptop to check it wasn't a new feature. I also installed Debian 12.1 Xfce, Mate and Cinnamon on that test-laptop.. all this three editions has that Grub line. and the ISO's is verified hash. as far i have seen searching online with Google, Bing and Duckduckgo is the input: initrd=/install/gtk/initrd.gz seems to be in NetISO installs and other install media.. But this is grub on an installed system. not an installer. So i wonder.. what is [c]GRUB_CMDLINE_LINUX="initrd=/install/gtk/initrd.gz"[/c] and what is it good for? Time to get some sleep Take care everyone. | Marie SWE wrote: 2023-08-06 22:48So Debian repo does not seem to have Nvidia drivers. so where do i get them... Backports?? nope not there https://wiki.debian.org/NvidiaGraphicsDrivers |
Just installed the xfce on debian 11. I am interested in editing the menu items, is there any clear cut instructions how this can be done? thanks | MenuLibre is a great tool for that. |
I have 2 computers running Debian Bullseye that I wanted to share some files across. I've installed samba and nautilus-share on both. If I put a file in the Public/ folder, I can access it from the other computer. So everything is working. Except, if I share an arbitrary folder in my /home/user/ directory (e.g. Documents/), I cannot "see" it on the other computer. I receive no errors and an emblem appears on the folder icon to show it's shared. So how do I access that folders contents from the other computer? Neither the shared folder nor its contents show any where. Only the Public/ folder is shared. | I've made some headway on this, albeit partially. Code: Select allsmbpasswd -a username service smbd restart Did this on both computers. I can access shared folders by using Nautilus > Other Locations > Network > DEBIAN But it's only working in one direction. Could I be missing a package that needs to be installed? |
Hello Guys, Quick question: Debian Bulleyes clean install. Openbox and i3 wms' installed. No login manager - using startx. First I installed Openbox and in the /etc/X11/xinit/xinitrc I placed 'exec openbox-session' and this works fine. Then I installed i3 and replaced 'exec openbox-session' with 'exec i3'. Then I hit startx but I have been logged into openbox instead i3. I erase all exec commands from xinitrc and still I got openbox running. I know I can hit startx i3 - then I will get i3 running but I would like to know how to disable default openbox-session. I spent several hours but no success. I did not create any local .xinitrc or so. Where is catch ? Thanks in advance. | Use this to change from Openbox to i3: Code: Select all# update-alternatives --config x-session-manager If you want to use an xinitrc file then copy it to ~/.xinitrc but note that not all desktop features will work correctly without further scripting. It is recommended to use ~/.xsession instead in Debian. Reference: https://wiki.debian.org/Xsession |
Good day, all. I have been around Linux off and on for many years but would still consider myself a newbie. I have been poking around and have not been able to find anything that works for this. I have a Debian core loaded on a VM that resides on 2 different networks. Network 1 is the primary network (ens192) and is on a firewalled segment of our corporate network that is routed to corporate assets. Network 2 is a network that is connected to multiple test networks that we use for testing purposes using public IP ranges. i.e. 10.0.x.x, 172.16.x.x, 192.168.x.x etc... There is routing between all of these subnets. This Debian installation serves as an SMTP gateway to our secure corporate SMTP servers and works well from devices attached to the Network 1 and Network 2 subnets. For test subnets, I am needing to add route tables to the Debian machine. Network 2 is on a 192.168.0.0/20 supernet and the Debian address is 192.168.0.6. Normally, I cannot ping 192.168.16.32 as ICMP response packets the sent out the network 1 - the default. If I enter ip route add 192.168.16.0/24 via 192.168.0.1 I can then ping a device at 192.168.16.32 Great. But it is static and I need it to be persistent. I am editing /etc/network/interfaces as shown here. I blocked the corporate IP address with ###. # 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 # The primary network interface auto ens192 iface ens192 inet static address ###.###.133.31/24 gateway ###.###.133.1 dns-nameservers ###.###.133.18 ###.###.133.19 # The secondary network interface auto ens224 iface ens224 inet static address 192.168.0.6/20 gateway 192.168.0.1 #This has not worked to add a persistent route. up ip route add 192.168.16.0/24 via 192.168.0.1 I am not sure of what I am missing. Should the route be deleted from ens192? | I think you want this: https://www.cyberciti.biz/faq/ip-route- ... explained/ (/etc/network/interfaces snippet at the end) |
Hey everyone, I have a primitive shell script that displays some text and accepts user input. I would like to make this script available over telnet, at least within my LAN. Ideally, I want the user to be able to 'telnet 192.168.xx.xx' and be able to play the game. What is the best way to achieve this? (I am aware of the security risks associated with telnet, this is simply an experiment within my LAN). | Best is if you use ssh instead of telnet, so you can just: $ ssh 192.168.xx.xx -t /path/to/your/script The -t is needed to make sure ssh allocates a pseudo-terminal, so that interactive programs work as expected. If you want to use telnet, or ssh but without having to give the path for the script, you could create a user (e.g. "game") at the server whose .profile (or .bashrc) runs the script. This way telnet game@192.168.xx.xx or ssh game@192.168.xx.xx will directly run the script. |
Today I made changes to the nftables.conf as recommend by @Head_on_a_Stick Code: Select allcp /usr/share/doc/nftables/examples/workstation.nft /etc/nftables.conf. I made the changes on three different drives, two in my desktop and one in my Intel NUC. After making the changes and checking the ruleset (nft list ruleset) I see huge differences between the different drives. Here is what I see on my desktop drive SDA (it's quite long) Code: Select alltable inet filter { chain input { type filter hook input priority filter; policy accept; iif "lo" accept ct state established,related accept ip6 nexthdr ipv6-icmp icmpv6 type { nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert } accept counter packets 67 bytes 9081 drop } } table ip filter { chain ufw-logging-deny { ct state invalid limit rate 3/minute burst 10 packets counter packets 0 bytes 0 return limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW BLOCK] " } chain ufw-logging-allow { limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW ALLOW] " } chain ufw-skip-to-policy-input { counter packets 0 bytes 0 drop } chain ufw-skip-to-policy-output { counter packets 0 bytes 0 accept } chain ufw-skip-to-policy-forward { counter packets 0 bytes 0 drop } chain ufw-before-input { iifname "lo" counter packets 0 bytes 0 accept ct state related,established counter packets 0 bytes 0 accept ct state invalid counter packets 0 bytes 0 jump ufw-logging-deny ct state invalid counter packets 0 bytes 0 drop meta l4proto icmp icmp type destination-unreachable counter packets 0 bytes 0 accept meta l4proto icmp icmp type time-exceeded counter packets 0 bytes 0 accept meta l4proto icmp icmp type parameter-problem counter packets 0 bytes 0 accept meta l4proto icmp icmp type echo-request counter packets 0 bytes 0 accept meta l4proto udp udp sport 67 udp dport 68 counter packets 0 bytes 0 accept counter packets 0 bytes 0 jump ufw-not-local meta l4proto udp ip daddr 224.0.0.251 udp dport 5353 counter packets 0 bytes 0 accept meta l4proto udp ip daddr 239.255.255.250 udp dport 1900 counter packets 0 bytes 0 accept counter packets 0 bytes 0 jump ufw-user-input } chain ufw-before-output { oifname "lo" counter packets 0 bytes 0 accept ct state related,established counter packets 0 bytes 0 accept counter packets 0 bytes 0 jump ufw-user-output } chain ufw-before-forward { ct state related,established counter packets 0 bytes 0 accept meta l4proto icmp icmp type destination-unreachable counter packets 0 bytes 0 accept meta l4proto icmp icmp type time-exceeded counter packets 0 bytes 0 accept meta l4proto icmp icmp type parameter-problem counter packets 0 bytes 0 accept meta l4proto icmp icmp type echo-request counter packets 0 bytes 0 accept counter packets 0 bytes 0 jump ufw-user-forward } chain ufw-not-local { fib daddr type local counter packets 0 bytes 0 return fib daddr type multicast counter packets 0 bytes 0 return fib daddr type broadcast counter packets 0 bytes 0 return limit rate 3/minute burst 10 packets counter packets 0 bytes 0 jump ufw-logging-deny counter packets 0 bytes 0 drop } chain ufw-after-input { meta l4proto udp udp dport 137 counter packets 0 bytes 0 jump ufw-skip-to-policy-input meta l4proto udp udp dport 138 counter packets 0 bytes 0 jump ufw-skip-to-policy-input meta l4proto tcp tcp dport 139 counter packets 0 bytes 0 jump ufw-skip-to-policy-input meta l4proto tcp tcp dport 445 counter packets 0 bytes 0 jump ufw-skip-to-policy-input meta l4proto udp udp dport 67 counter packets 0 bytes 0 jump ufw-skip-to-policy-input meta l4proto udp udp dport 68 counter packets 0 bytes 0 jump ufw-skip-to-policy-input fib daddr type broadcast counter packets 0 bytes 0 jump ufw-skip-to-policy-input } chain ufw-after-output { } chain ufw-after-forward { } chain ufw-user-input { } chain ufw-user-output { } chain ufw-user-forward { } chain ufw-user-logging-input { } chain ufw-user-logging-output { } chain ufw-user-logging-forward { } chain ufw-user-limit { limit rate 3/minute counter packets 0 bytes 0 log prefix "[UFW LIMIT BLOCK] " counter packets 0 bytes 0 reject } chain ufw-user-limit-accept { counter packets 0 bytes 0 accept } chain ufw-before-logging-input { } chain ufw-before-logging-output { } chain ufw-before-logging-forward { } chain ufw-after-logging-input { limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW BLOCK] " } chain ufw-after-logging-output { } chain ufw-after-logging-forward { limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW BLOCK] " } } table ip6 filter { chain INPUT { type filter hook input priority filter; policy drop; counter packets 44 bytes 4835 jump ufw6-before-logging-input counter packets 44 bytes 4835 jump ufw6-before-input counter packets 0 bytes 0 jump ufw6-after-input counter packets 0 bytes 0 jump ufw6-after-logging-input counter packets 0 bytes 0 jump ufw6-reject-input counter packets 0 bytes 0 jump ufw6-track-input } chain FORWARD { type filter hook forward priority filter; policy drop; counter packets 0 bytes 0 jump ufw6-before-logging-forward counter packets 0 bytes 0 jump ufw6-before-forward counter packets 0 bytes 0 jump ufw6-after-forward counter packets 0 bytes 0 jump ufw6-after-logging-forward counter packets 0 bytes 0 jump ufw6-reject-forward counter packets 0 bytes 0 jump ufw6-track-forward } chain OUTPUT { type filter hook output priority filter; policy accept; counter packets 42 bytes 4274 jump ufw6-before-logging-output counter packets 42 bytes 4274 jump ufw6-before-output counter packets 28 bytes 3122 jump ufw6-after-output counter packets 28 bytes 3122 jump ufw6-after-logging-output counter packets 28 bytes 3122 jump ufw6-reject-output counter packets 28 bytes 3122 jump ufw6-track-output } chain ufw6-before-logging-input { } chain ufw6-before-logging-output { } chain ufw6-before-logging-forward { } chain ufw6-before-input { iifname "lo" counter packets 2 bytes 152 accept rt type 0 counter packets 0 bytes 0 drop ct state related,established counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type echo-reply counter packets 0 bytes 0 accept ct state invalid counter packets 0 bytes 0 jump ufw6-logging-deny ct state invalid counter packets 0 bytes 0 drop meta l4proto ipv6-icmp icmpv6 type destination-unreachable counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type packet-too-big counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type time-exceeded counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type parameter-problem counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type echo-request counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type nd-router-solicit ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type nd-router-advert ip6 hoplimit 255 counter packets 3 bytes 216 accept meta l4proto ipv6-icmp icmpv6 type nd-neighbor-solicit ip6 hoplimit 255 counter packets 2 bytes 144 accept meta l4proto ipv6-icmp icmpv6 type nd-neighbor-advert ip6 hoplimit 255 counter packets 1 bytes 64 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type ip6 hoplimit 1 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type ip6 hoplimit 1 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type ip6 hoplimit 1 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type counter packets 0 bytes 0 accept meta l4proto udp ip6 saddr fe80::/10 ip6 daddr fe80::/10 udp sport 547 udp dport 546 counter packets 6 bytes 672 accept meta l4proto udp ip6 daddr ff02::fb udp dport 5353 counter packets 30 bytes 3587 accept meta l4proto udp ip6 daddr ff02::f udp dport 1900 counter packets 0 bytes 0 accept counter packets 0 bytes 0 jump ufw6-user-input } chain ufw6-before-output { oifname "lo" counter packets 2 bytes 152 accept rt type 0 counter packets 0 bytes 0 drop ct state related,established counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type destination-unreachable counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type packet-too-big counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type time-exceeded counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type parameter-problem counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type echo-request counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type echo-reply counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type nd-router-solicit ip6 hoplimit 255 counter packets 1 bytes 48 accept meta l4proto ipv6-icmp icmpv6 type nd-neighbor-advert ip6 hoplimit 255 counter packets 2 bytes 136 accept meta l4proto ipv6-icmp icmpv6 type nd-neighbor-solicit ip6 hoplimit 255 counter packets 2 bytes 144 accept meta l4proto ipv6-icmp icmpv6 type nd-router-advert ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type counter packets 7 bytes 672 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type ip6 hoplimit 255 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type ip6 hoplimit 1 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type ip6 hoplimit 1 counter packets 0 bytes 0 accept meta l4proto ipv6-icmp ip6 saddr fe80::/10 icmpv6 type ip6 hoplimit 1 counter packets 0 bytes 0 accept counter packets 28 bytes 3122 jump ufw6-user-output } chain ufw6-before-forward { rt type 0 counter packets 0 bytes 0 drop ct state related,established counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type destination-unreachable counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type packet-too-big counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type time-exceeded counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type parameter-problem counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type echo-request counter packets 0 bytes 0 accept meta l4proto ipv6-icmp icmpv6 type echo-reply counter packets 0 bytes 0 accept counter packets 0 bytes 0 jump ufw6-user-forward } chain ufw6-after-input { meta l4proto udp udp dport 137 counter packets 0 bytes 0 jump ufw6-skip-to-policy-input meta l4proto udp udp dport 138 counter packets 0 bytes 0 jump ufw6-skip-to-policy-input meta l4proto tcp tcp dport 139 counter packets 0 bytes 0 jump ufw6-skip-to-policy-input meta l4proto tcp tcp dport 445 counter packets 0 bytes 0 jump ufw6-skip-to-policy-input meta l4proto udp udp dport 546 counter packets 0 bytes 0 jump ufw6-skip-to-policy-input meta l4proto udp udp dport 547 counter packets 0 bytes 0 jump ufw6-skip-to-policy-input } chain ufw6-after-output { } chain ufw6-after-forward { } chain ufw6-after-logging-input { limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW BLOCK] " } chain ufw6-after-logging-output { } chain ufw6-after-logging-forward { limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW BLOCK] " } chain ufw6-reject-input { } chain ufw6-reject-output { } chain ufw6-reject-forward { } chain ufw6-track-input { } chain ufw6-track-output { meta l4proto tcp ct state new counter packets 0 bytes 0 accept meta l4proto udp ct state new counter packets 26 bytes 2930 accept } chain ufw6-track-forward { } chain ufw6-logging-deny { ct state invalid limit rate 3/minute burst 10 packets counter packets 0 bytes 0 return limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW BLOCK] " } chain ufw6-logging-allow { limit rate 3/minute burst 10 packets counter packets 0 bytes 0 log prefix "[UFW ALLOW] " } chain ufw6-skip-to-policy-input { counter packets 0 bytes 0 drop } chain ufw6-skip-to-policy-output { counter packets 0 bytes 0 accept } chain ufw6-skip-to-policy-forward { counter packets 0 bytes 0 drop } chain ufw6-user-input { } chain ufw6-user-output { } chain ufw6-user-forward { } chain ufw6-user-logging-input { } chain ufw6-user-logging-output { } chain ufw6-user-logging-forward { } chain ufw6-user-limit { limit rate 3/minute counter packets 0 bytes 0 log prefix "[UFW LIMIT BLOCK] " counter packets 0 bytes 0 reject } chain ufw6-user-limit-accept { counter packets 0 bytes 0 accept } } And here is what I see on my desktop SDB and on the NUC Code: Select alltable inet filter { chain input { type filter hook input priority filter; policy accept; iif "lo" accept ct state established,related accept ip6 nexthdr ipv6-icmp icmpv6 type { nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert } accept counter packets 24 bytes 3224 drop } } Can anybody tell me why SDB and the NUC are so much different than SDA and if there is an issue what I need to do to remedy the issue. To my untrained eye it looks like MAYBE iptables is enabled on SDA. Is that the issue? | I found the problem. iptables were indeed enabled. Apparently at some time I installed the ufw package and it uses iptables. Dummy! Anyway, I stopped and disabled ufw. The ruleset is now the same on all three drives. Is there any reason to NOT uninstall the ufw package? EDIT: I went ahead and uninstalled the ufw package. Everything is working as expected. Thanks again to @Head_on_a_Stick for his response in my other post viewtopic.php?f=20&t=152141 |
Hello everyone. I have a strange problem that I am unsure where to start with. I have a fairly new Bookworm install, and everything was working fine. I am not new to Debian, having switched in 2005, and I've dealt with a lot, but networking issues have always been my weakness. Anyway, I went to print a document, and had no printers anymore. I went to localhost:631, and nothing was listed as a network printer. Blank. I have an HP Laserjet 1109w, and an Epson ET 2850. All have worked in the past, and now neither is visible. My android phone can connect and print without a problem to either one. Another thing that may or may not be related, but equally strange is that I can no longer access my openmediavault server at user@openmediavalut.local, but can access it with user@192.168.0.88. Swapping the quad address for the openmediavault.local restored the rsync funtionality. (I ssh into the server for backups). Let me know whatever other information is needed, and thanks in advance! Gary | How did you set up the printers? Both printers are driverless enabled - they use Airprint - and a print queue would have been set up in Bookworm automatically, no driver required. This is a fairly recent change. Please check the following page. Apologies if you are doing this already. It may be that you are fighting against the system if you are still using old approaches to setting up the printers. https://wiki.debian.org/CUPSAirPrint It could have been a router issue with Bonjour, maybe? https://discussions.apple.com/thread/78 ... ortBy=best |
hi, i had a big problem with kernel 6.1.17, it didn't find my ALC897 intel chipset audio card. To correct that i needed to compile a 6.6.11 to retrieve my sound card with pulse audio in kde. But the correct pulseaudio config seems to be loaded manualy only after an /sbin/alsactl init. not at start and not before this command. is anybody know why ? thanks in advance. /sbin/alsactl init Code: Select allFound hardware: "HDA-Intel" "Realtek ALC897" "HDA:10ec0897,103c8717,00100402 HDA:8086280b,80860101,00100000" "0x103c" "0x8717" Hardware is initialized using a generic method Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100300" "0x103c" "0xaab0" Hardware is initialized using a generic method An other curious thing remain on kde pulseaudio visual window config, it show me an "Oland/Hainan/Cape Verde/Pitcairn SDMI Audio [radeon HD 7000 series]" truned off, and cannot be turned on. is that normal? | Hello, Can you report the output of the following command (the inxi command must be installed) ? Code: Select allinxi -AS What is your audio output: Realtek ALC897 or ATI R6xx HDMI ? |
Hi, I installed Debian Buster in sda7 several years ago but thought it is high time to install Bookworm in a free partition sda2. I downloaded the 64 netinst iso, copied it to a USB stick ("cp debian_image /dev/sdb"), re-booted the PC from USB. The installation program started, the wireless card was recognized and the network connection successfully negotiated. After a while, the installation stopped with a message that I don't exactly remember: I think it said more or less that some data transfer failed. I was given the option to retry, which I did some three or four times. Then I stopped the installation from the main installation menu and switched off the PC. When I restarted, the Grub menu was the same as usual. I selected Debian Buster and got the usual firmware bug warning: (I only see the word "Image" in my preview; if I can't link to the image I'll copy the messages) This is not the problem; I tried to fix it several times in the past, never succeeded, but the booting normally goes on. Then I got this: I have tried several times, but pressing CTRL-C doesn't seem to speed up the process. After some 30 secs I get: and after one more minute and 30 seconds the booting goes on, as fast as usual, to a normally working system. This is the dmesg (I cut some 1000 characters at about 37 secs to keep within the allowed characters for this message): Code: Select all[ 0.000000] Linux version 4.19.0-26-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.304-1 (2024-01-09) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-26-amd64 root=UUID=5eaf65d7-bf69-4634-b4b8-2b4c7f153bd0 ro quiet [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable [ 0.000000] BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000070000-0x0000000000087fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000088000-0x00000000000bffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000009c64efff] usable [ 0.000000] BIOS-e820: [mem 0x000000009c64f000-0x000000009c87efff] type 20 [ 0.000000] BIOS-e820: [mem 0x000000009c87f000-0x000000009ceaefff] reserved [ 0.000000] BIOS-e820: [mem 0x000000009ceaf000-0x000000009cfaefff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000009cfaf000-0x000000009cffefff] ACPI data [ 0.000000] BIOS-e820: [mem 0x000000009cfff000-0x000000009cffffff] usable [ 0.000000] BIOS-e820: [mem 0x000000009d000000-0x000000009f9fffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fe101000-0x00000000fe112fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000feb00000-0x00000000feb0ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000025f5fffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] efi: EFI v2.31 by INSYDE Corp. [ 0.000000] efi: ACPI=0x9cffe000 ACPI 2.0=0x9cffe014 SMBIOS=0x9ceaef98 [ 0.000000] secureboot: Secure boot disabled [ 0.000000] SMBIOS 2.7 present. [ 0.000000] DMI: Hewlett-Packard HP 250 G3 Notebook PC/2211, BIOS F.36 12/18/2014 [ 0.000000] tsc: Fast TSC calibration using PIT [ 0.000000] tsc: Detected 2394.334 MHz processor [ 0.000174] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000175] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000182] last_pfn = 0x25f600 max_arch_pfn = 0x400000000 [ 0.000186] MTRR default type: uncachable [ 0.000186] MTRR fixed ranges enabled: [ 0.000187] 00000-9FFFF write-back [ 0.000188] A0000-BFFFF uncachable [ 0.000189] C0000-E7FFF write-protect [ 0.000190] E8000-EFFFF write-combining [ 0.000190] F0000-FFFFF write-protect [ 0.000191] MTRR variable ranges enabled: [ 0.000192] 0 base 0000000000 mask 7F80000000 write-back [ 0.000193] 1 base 0080000000 mask 7FE0000000 write-back [ 0.000194] 2 base 009D000000 mask 7FFF000000 uncachable [ 0.000195] 3 base 009E000000 mask 7FFE000000 uncachable [ 0.000195] 4 base 00FFA00000 mask 7FFFE00000 write-protect [ 0.000196] 5 base 00FFC00000 mask 7FFFC00000 write-protect [ 0.000197] 6 base 00FF800000 mask 7FFFE00000 uncachable [ 0.000198] 7 base 0100000000 mask 7F00000000 write-back [ 0.000198] 8 base 0200000000 mask 7F80000000 write-back [ 0.000199] 9 base 025F600000 mask 7FFFE00000 uncachable [ 0.001013] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.001133] last_pfn = 0x9d000 max_arch_pfn = 0x400000000 [ 0.016420] Using GB pages for direct mapping [ 0.016805] RAMDISK: [mem 0x336d9000-0x35b63fff] [ 0.016807] ACPI: Early table checksum verification disabled [ 0.016810] ACPI: RSDP 0x000000009CFFE014 000024 (v02 HPQOEM) [ 0.016814] ACPI: XSDT 0x000000009CFFE210 0000AC (v01 HPQOEM SLIC-MPC 00000001 HP 01000013) [ 0.016819] ACPI: FACP 0x000000009CFF8000 00010C (v05 HPQOEM SLIC-MPC 00000001 HP 00040000) [ 0.016823] ACPI: DSDT 0x000000009CFE1000 01376C (v02 HPQOEM SLIC-MPC 00000000 HP 00040000) [ 0.016826] ACPI: FACS 0x000000009CFA9000 000040 [ 0.016828] ACPI: UEFI 0x000000009CFFD000 000236 (v01 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016830] ACPI: FPDT 0x000000009CFFB000 000044 (v01 HPQOEM SLIC-MPC 00000001 HP 00040000) [ 0.016833] ACPI: ASF! 0x000000009CFF9000 0000A5 (v32 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016835] ACPI: HPET 0x000000009CFF7000 000038 (v01 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016837] ACPI: APIC 0x000000009CFF6000 00008C (v03 HPQOEM SLIC-MPC 00000001 HP 00040000) [ 0.016840] ACPI: MCFG 0x000000009CFF5000 00003C (v01 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016842] ACPI: SSDT 0x000000009CFE0000 0006FE (v01 HPQOEM INSYDE 00001000 HP 00040000) [ 0.016844] ACPI: BOOT 0x000000009CFDE000 000028 (v01 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016847] ACPI: ASPT 0x000000009CFDC000 000034 (v07 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016849] ACPI: DBGP 0x000000009CFDB000 000034 (v01 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016851] ACPI: LPIT 0x000000009CFD7000 00005C (v01 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016854] ACPI: SSDT 0x000000009CFD6000 000539 (v01 HPQOEM INSYDE 00003000 HP 00040000) [ 0.016856] ACPI: SSDT 0x000000009CFD5000 000AD8 (v01 HPQOEM INSYDE 00003000 HP 00040000) [ 0.016858] ACPI: SSDT 0x000000009CFD4000 0001C7 (v01 HPQOEM INSYDE 00003000 HP 00040000) [ 0.016861] ACPI: SSDT 0x000000009CFCE000 005A14 (v01 HPQOEM INSYDE 00003000 HP 00040000) [ 0.016863] ACPI: BGRT 0x000000009CFCD000 000038 (v01 HPQOEM INSYDE 00000001 HP 00040000) [ 0.016865] ACPI: Reserving FACP table memory at [mem 0x9cff8000-0x9cff810b] [ 0.016866] ACPI: Reserving DSDT table memory at [mem 0x9cfe1000-0x9cff476b] [ 0.016867] ACPI: Reserving FACS table memory at [mem 0x9cfa9000-0x9cfa903f] [ 0.016868] ACPI: Reserving UEFI table memory at [mem 0x9cffd000-0x9cffd235] [ 0.016869] ACPI: Reserving FPDT table memory at [mem 0x9cffb000-0x9cffb043] [ 0.016870] ACPI: Reserving ASF! table memory at [mem 0x9cff9000-0x9cff90a4] [ 0.016870] ACPI: Reserving HPET table memory at [mem 0x9cff7000-0x9cff7037] [ 0.016871] ACPI: Reserving APIC table memory at [mem 0x9cff6000-0x9cff608b] [ 0.016872] ACPI: Reserving MCFG table memory at [mem 0x9cff5000-0x9cff503b] [ 0.016873] ACPI: Reserving SSDT table memory at [mem 0x9cfe0000-0x9cfe06fd] [ 0.016874] ACPI: Reserving BOOT table memory at [mem 0x9cfde000-0x9cfde027] [ 0.016874] ACPI: Reserving ASPT table memory at [mem 0x9cfdc000-0x9cfdc033] [ 0.016875] ACPI: Reserving DBGP table memory at [mem 0x9cfdb000-0x9cfdb033] [ 0.016876] ACPI: Reserving LPIT table memory at [mem 0x9cfd7000-0x9cfd705b] [ 0.016877] ACPI: Reserving SSDT table memory at [mem 0x9cfd6000-0x9cfd6538] [ 0.016878] ACPI: Reserving SSDT table memory at [mem 0x9cfd5000-0x9cfd5ad7] [ 0.016878] ACPI: Reserving SSDT table memory at [mem 0x9cfd4000-0x9cfd41c6] [ 0.016879] ACPI: Reserving SSDT table memory at [mem 0x9cfce000-0x9cfd3a13] [ 0.016880] ACPI: Reserving BGRT table memory at [mem 0x9cfcd000-0x9cfcd037] [ 0.016889] ACPI: Local APIC address 0xfee00000 [ 0.016969] No NUMA configuration found [ 0.016970] Faking a node at [mem 0x0000000000000000-0x000000025f5fffff] [ 0.016974] NODE_DATA(0) allocated [mem 0x25f5fb000-0x25f5fffff] [ 0.016999] Zone ranges: [ 0.017000] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.017001] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] [ 0.017002] Normal [mem 0x0000000100000000-0x000000025f5fffff] [ 0.017002] Device empty [ 0.017003] Movable zone start for each node [ 0.017004] Early memory node ranges [ 0.017005] node 0: [mem 0x0000000000001000-0x000000000006efff] [ 0.017005] node 0: [mem 0x0000000000070000-0x0000000000087fff] [ 0.017006] node 0: [mem 0x0000000000100000-0x000000009c64efff] [ 0.017006] node 0: [mem 0x000000009cfff000-0x000000009cffffff] [ 0.017007] node 0: [mem 0x0000000100000000-0x000000025f5fffff] [ 0.017299] Zeroed struct page in unavailable ranges: 17450 pages [ 0.017300] Initmem setup node 0 [mem 0x0000000000001000-0x000000025f5fffff] [ 0.017302] On node 0 totalpages: 2079702 [ 0.017303] DMA zone: 64 pages used for memmap [ 0.017303] DMA zone: 22 pages reserved [ 0.017304] DMA zone: 3974 pages, LIFO batch:0 [ 0.017398] DMA32 zone: 9946 pages used for memmap [ 0.017399] DMA32 zone: 636496 pages, LIFO batch:63 [ 0.033833] Normal zone: 22488 pages used for memmap [ 0.033835] Normal zone: 1439232 pages, LIFO batch:63 [ 0.066448] Reserving Intel graphics memory at [mem 0x9da00000-0x9f9fffff] [ 0.066595] ACPI: PM-Timer IO Port: 0x1808 [ 0.066597] ACPI: Local APIC address 0xfee00000 [ 0.066612] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-39 [ 0.066614] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.066616] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.066617] ACPI: IRQ0 used by override. [ 0.066617] ACPI: IRQ9 used by override. [ 0.066619] Using ACPI (MADT) for SMP configuration information [ 0.066620] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.066630] e820: update [mem 0x8a5ca000-0x8a5d4fff] usable ==> reserved [ 0.066639] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x20 (or later) [ 0.066642] smpboot: Allowing 8 CPUs, 4 hotplug CPUs [ 0.066664] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.066665] PM: Registered nosave memory: [mem 0x0006f000-0x0006ffff] [ 0.066667] PM: Registered nosave memory: [mem 0x00088000-0x000bffff] [ 0.066668] PM: Registered nosave memory: [mem 0x000c0000-0x000fffff] [ 0.066669] PM: Registered nosave memory: [mem 0x8a5ca000-0x8a5d4fff] [ 0.066671] PM: Registered nosave memory: [mem 0x9c64f000-0x9c87efff] [ 0.066671] PM: Registered nosave memory: [mem 0x9c87f000-0x9ceaefff] [ 0.066672] PM: Registered nosave memory: [mem 0x9ceaf000-0x9cfaefff] [ 0.066672] PM: Registered nosave memory: [mem 0x9cfaf000-0x9cffefff] [ 0.066674] PM: Registered nosave memory: [mem 0x9d000000-0x9f9fffff] [ 0.066675] PM: Registered nosave memory: [mem 0x9fa00000-0xdfffffff] [ 0.066675] PM: Registered nosave memory: [mem 0xe0000000-0xefffffff] [ 0.066676] PM: Registered nosave memory: [mem 0xf0000000-0xfe100fff] [ 0.066676] PM: Registered nosave memory: [mem 0xfe101000-0xfe112fff] [ 0.066677] PM: Registered nosave memory: [mem 0xfe113000-0xfeafffff] [ 0.066677] PM: Registered nosave memory: [mem 0xfeb00000-0xfeb0ffff] [ 0.066678] PM: Registered nosave memory: [mem 0xfeb10000-0xfebfffff] [ 0.066678] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff] [ 0.066679] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff] [ 0.066679] PM: Registered nosave memory: [mem 0xfed00000-0xfee00fff] [ 0.066680] PM: Registered nosave memory: [mem 0xfee01000-0xff9fffff] [ 0.066680] PM: Registered nosave memory: [mem 0xffa00000-0xffffffff] [ 0.066682] [mem 0x9fa00000-0xdfffffff] available for PCI devices [ 0.066683] Booting paravirtualized kernel on bare hardware [ 0.066686] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns [ 0.174736] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1 [ 0.175057] percpu: Embedded 50 pages/cpu s165272 r8192 d31336 u262144 [ 0.175065] pcpu-alloc: s165272 r8192 d31336 u262144 alloc=1*2097152 [ 0.175066] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 [ 0.175088] Built 1 zonelists, mobility grouping on. Total pages: 2047182 [ 0.175089] Policy zone: Normal [ 0.175090] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-26-amd64 root=UUID=5eaf65d7-bf69-4634-b4b8-2b4c7f153bd0 ro quiet [ 0.180294] Calgary: detecting Calgary via BIOS EBDA area [ 0.180295] Calgary: Unable to locate Rio Grande table in EBDA - bailing! [ 0.207118] Memory: 8002128K/8318808K available (10252K kernel code, 1236K rwdata, 3192K rodata, 1624K init, 2212K bss, 316680K reserved, 0K cma-reserved) [ 0.207323] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.207328] Kernel/User page tables isolation: enabled [ 0.214780] ftrace: allocating 32081 entries in 126 pages [ 0.228362] ftrace: allocated 126 pages with 6 groups [ 0.228466] rcu: Hierarchical RCU implementation. [ 0.228468] rcu: RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8. [ 0.228469] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8 [ 0.231432] NR_IRQS: 33024, nr_irqs: 760, preallocated irqs: 16 [ 0.231627] random: crng init done [ 0.231648] Console: colour dummy device 80x25 [ 0.231657] console [tty0] enabled [ 0.231675] ACPI: Core revision 20180810 [ 0.231906] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns [ 0.231914] hpet clockevent registered [ 0.231918] APIC: Switch to symmetric I/O mode setup [ 0.232510] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.251919] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x22834f0cb51, max_idle_ns: 440795251795 ns [ 0.251932] Calibrating delay loop (skipped), value calculated using timer frequency.. 4788.66 BogoMIPS (lpj=9577336) [ 0.251950] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.251950] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [ 0.251964] CPU0: Thermal monitoring enabled (TM1) [ 0.251974] process: using mwait in idle threads [ 0.251977] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024 [ 0.251977] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4 [ 0.251979] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 0.251980] Spectre V2 : Mitigation: Retpolines [ 0.251981] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 0.251981] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT [ 0.251982] Speculative Store Bypass: Vulnerable [ 0.252007] MDS: Vulnerable: Clear CPU buffers attempted, no microcode [ 0.252007] MMIO Stale Data: Unknown: No mitigations [ 0.252008] SRBDS: Vulnerable: No microcode [ 0.252014] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.252015] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.252015] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.252016] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [ 0.252017] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [ 0.255622] Freeing SMP alternatives memory: 24K [ 0.257344] pid_max: default: 32768 minimum: 301 [ 0.260820] Security Framework initialized [ 0.260821] Yama: disabled by default; enable with sysctl kernel.yama.* [ 0.260840] AppArmor: AppArmor initialized [ 0.261609] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) [ 0.262009] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.262032] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes) [ 0.262044] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes) [ 0.376223] smpboot: CPU0: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz (family: 0x6, model: 0x45, stepping: 0x1) [ 0.376319] Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver. [ 0.376372] ... version: 3 [ 0.376372] ... bit width: 48 [ 0.376373] ... generic registers: 4 [ 0.376373] ... value mask: 0000ffffffffffff [ 0.376374] ... max period: 00007fffffffffff [ 0.376374] ... fixed-purpose events: 3 [ 0.376375] ... event mask: 000000070000000f [ 0.376414] rcu: Hierarchical SRCU implementation. [ 0.377300] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. [ 0.377361] smp: Bringing up secondary CPUs ... [ 0.377424] x86: Booting SMP configuration: [ 0.377426] .... node #0, CPUs: #1 [ 0.377786] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [ 0.377786] #2 #3 [ 0.377786] smp: Brought up 1 node, 4 CPUs [ 0.377786] smpboot: Max logical packages: 2 [ 0.377786] smpboot: Total of 4 processors activated (19154.67 BogoMIPS) [ 0.380188] devtmpfs: initialized [ 0.380188] x86/mm: Memory block size: 128MB [ 0.380665] PM: Registering ACPI NVS region [mem 0x9ceaf000-0x9cfaefff] (1048576 bytes) [ 0.380665] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.380665] futex hash table entries: 2048 (order: 5, 131072 bytes) [ 0.380665] pinctrl core: initialized pinctrl subsystem [ 0.380665] NET: Registered protocol family 16 [ 0.380665] audit: initializing netlink subsys (disabled) [ 0.380665] audit: type=2000 audit(1705824011.148:1): state=initialized audit_enabled=0 res=1 [ 0.380665] cpuidle: using governor ladder [ 0.380665] cpuidle: using governor menu [ 0.380665] Simple Boot Flag at 0x44 set to 0x1 [ 0.380665] ACPI: bus type PCI registered [ 0.380665] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.380665] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) [ 0.380665] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 [ 0.380665] PCI: Using configuration type 1 for base access [ 0.380665] core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on [ 0.384533] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.384533] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.384533] ACPI: Added _OSI(Module Device) [ 0.384533] ACPI: Added _OSI(Processor Device) [ 0.384533] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.384533] ACPI: Added _OSI(Processor Aggregator Device) [ 0.384533] ACPI: Added _OSI(Linux-Dell-Video) [ 0.384533] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 0.398987] ACPI: 6 ACPI AML tables successfully acquired and loaded [ 0.400942] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 0.401832] ACPI: Dynamic OEM Table Load: [ 0.401838] ACPI: SSDT 0xFFFF9B2C959E3C00 0003D3 (v01 PmRef Cpu0Cst 00003001 INTL 20120913) [ 0.402246] ACPI: Dynamic OEM Table Load: [ 0.402251] ACPI: SSDT 0xFFFF9B2C959DC800 0005AA (v01 PmRef ApIst 00003000 INTL 20120913) [ 0.402684] ACPI: Dynamic OEM Table Load: [ 0.402688] ACPI: SSDT 0xFFFF9B2C95A55E00 000119 (v01 PmRef ApCst 00003000 INTL 20120913) [ 0.403539] ACPI: EC: EC started [ 0.403539] ACPI: EC: interrupt blocked [ 0.567964] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as first EC [ 0.567966] ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0xa, EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.567968] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions [ 0.567968] ACPI: Interpreter enabled [ 0.568016] ACPI: (supports S0 S3 S4 S5) [ 0.568017] ACPI: Using IOAPIC for interrupt routing [ 0.568049] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.568403] ACPI: Enabled 8 GPEs in block 00 to 7F [ 0.608332] ACPI: Power Resource [FN00] (off) [ 0.608399] ACPI: Power Resource [FN01] (off) [ 0.608455] ACPI: Power Resource [FN02] (off) [ 0.608511] ACPI: Power Resource [FN03] (off) [ 0.608566] ACPI: Power Resource [FN04] (off) [ 0.609114] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 0.609118] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.609228] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [ 0.609637] PCI host bridge to bus 0000:00 [ 0.609639] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.609641] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.609642] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.609643] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window] [ 0.609644] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window] [ 0.609645] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window] [ 0.609645] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window] [ 0.609646] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window] [ 0.609647] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window] [ 0.609648] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] [ 0.609649] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] [ 0.609650] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window] [ 0.609651] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window] [ 0.609652] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window] [ 0.609653] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window] [ 0.609654] pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff window] [ 0.609655] pci_bus 0000:00: root bus resource [mem 0x9fa00000-0xfeafffff window] [ 0.609656] pci_bus 0000:00: root bus resource [bus 00-fe] [ 0.609665] pci 0000:00:00.0: [8086:0a04] type 00 class 0x060000 [ 0.609817] pci 0000:00:02.0: [8086:0a16] type 00 class 0x030000 [ 0.609829] pci 0000:00:02.0: reg 0x10: [mem 0xb2000000-0xb23fffff 64bit] [ 0.609834] pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref] [ 0.609838] pci 0000:00:02.0: reg 0x20: [io 0x5000-0x503f] [ 0.609850] pci 0000:00:02.0: BAR 2: assigned to efifb [ 0.609979] pci 0000:00:03.0: [8086:0a0c] type 00 class 0x040300 [ 0.609989] pci 0000:00:03.0: reg 0x10: [mem 0xb2710000-0xb2713fff 64bit] [ 0.610148] pci 0000:00:14.0: [8086:9c31] type 00 class 0x0c0330 [ 0.610166] pci 0000:00:14.0: reg 0x10: [mem 0xb2700000-0xb270ffff 64bit] [ 0.610219] pci 0000:00:14.0: PME# supported from D3hot D3cold [ 0.610347] pci 0000:00:16.0: [8086:9c3a] type 00 class 0x078000 [ 0.610368] pci 0000:00:16.0: reg 0x10: [mem 0xb2718000-0xb271801f 64bit] [ 0.610431] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold [ 0.610563] pci 0000:00:1b.0: [8086:9c20] type 00 class 0x040300 [ 0.610591] pci 0000:00:1b.0: reg 0x10: [mem 0xb2714000-0xb2717fff 64bit] [ 0.610655] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold [ 0.610786] pci 0000:00:1c.0: [8086:9c10] type 01 class 0x060400 [ 0.610858] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 0.611028] pci 0000:00:1c.1: [8086:9c12] type 01 class 0x060400 [ 0.611102] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold [ 0.611269] pci 0000:00:1c.2: [8086:9c14] type 01 class 0x060400 [ 0.611344] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold [ 0.611509] pci 0000:00:1c.5: [8086:9c1a] type 01 class 0x060400 [ 0.611582] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold [ 0.611753] pci 0000:00:1d.0: [8086:9c26] type 00 class 0x0c0320 [ 0.611773] pci 0000:00:1d.0: reg 0x10: [mem 0xb271c000-0xb271c3ff] [ 0.611852] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold [ 0.611991] pci 0000:00:1f.0: [8086:9c43] type 00 class 0x060100 [ 0.612223] pci 0000:00:1f.2: [8086:9c03] type 00 class 0x010601 [ 0.612237] pci 0000:00:1f.2: reg 0x10: [io 0x5088-0x508f] [ 0.612243] pci 0000:00:1f.2: reg 0x14: [io 0x5094-0x5097] [ 0.612249] pci 0000:00:1f.2: reg 0x18: [io 0x5080-0x5087] [ 0.612255] pci 0000:00:1f.2: reg 0x1c: [io 0x5090-0x5093] [ 0.612260] pci 0000:00:1f.2: reg 0x20: [io 0x5060-0x507f] [ 0.612267] pci 0000:00:1f.2: reg 0x24: [mem 0xb271b000-0xb271b7ff] [ 0.612297] pci 0000:00:1f.2: PME# supported from D3hot [ 0.612419] pci 0000:00:1f.3: [8086:9c22] type 00 class 0x0c0500 [ 0.612434] pci 0000:00:1f.3: reg 0x10: [mem 0xb2719000-0xb27190ff 64bit] [ 0.612452] pci 0000:00:1f.3: reg 0x20: [io 0x5040-0x505f] [ 0.612621] pci 0000:00:1c.0: PCI bridge to [bus 01] [ 0.612712] pci 0000:02:00.0: [10ec:5229] type 00 class 0xff0000 [ 0.612752] pci 0000:02:00.0: reg 0x10: [mem 0xb1000000-0xb1000fff] [ 0.612909] pci 0000:02:00.0: supports D1 D2 [ 0.612910] pci 0000:02:00.0: PME# supported from D1 D2 D3hot [ 0.613121] pci 0000:00:1c.1: PCI bridge to [bus 02-07] [ 0.613123] pci 0000:00:1c.1: bridge window [io 0x4000-0x4fff] [ 0.613126] pci 0000:00:1c.1: bridge window [mem 0xb1000000-0xb1ffffff] [ 0.613130] pci 0000:00:1c.1: bridge window [mem 0xb0000000-0xb0ffffff 64bit pref] [ 0.613195] pci 0000:08:00.0: [10ec:8136] type 00 class 0x020000 [ 0.613227] pci 0000:08:00.0: reg 0x10: [io 0x3000-0x30ff] [ 0.613258] pci 0000:08:00.0: reg 0x18: [mem 0xb2600000-0xb2600fff 64bit] [ 0.613278] pci 0000:08:00.0: reg 0x20: [mem 0xb2400000-0xb2403fff 64bit pref] [ 0.613384] pci 0000:08:00.0: supports D1 D2 [ 0.613385] pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold [ 0.613516] pci 0000:00:1c.2: PCI bridge to [bus 08] [ 0.613518] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff] [ 0.613521] pci 0000:00:1c.2: bridge window [mem 0xb2600000-0xb26fffff] [ 0.613525] pci 0000:00:1c.2: bridge window [mem 0xb2400000-0xb24fffff 64bit pref] [ 0.613579] pci 0000:09:00.0: [1814:3290] type 00 class 0x028000 [ 0.613615] pci 0000:09:00.0: reg 0x10: [mem 0xb2510000-0xb251ffff] [ 0.613743] pci 0000:09:00.0: PME# supported from D0 D3hot [ 0.613829] pci 0000:09:00.1: [1814:3298] type 00 class 0x0d1100 [ 0.613855] pci 0000:09:00.1: reg 0x10: [mem 0xb2500000-0xb250ffff] [ 0.613982] pci 0000:09:00.1: supports D1 [ 0.613983] pci 0000:09:00.1: PME# supported from D0 D1 D3hot [ 0.614091] pci 0000:00:1c.5: PCI bridge to [bus 09] [ 0.614096] pci 0000:00:1c.5: bridge window [mem 0xb2500000-0xb25fffff] [ 0.696478] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.696528] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.696576] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.696622] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.696669] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.696716] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.696763] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.696813] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 0.697349] ACPI: EC: interrupt unblocked [ 0.697359] ACPI: EC: event unblocked [ 0.697365] ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0xa, EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.697367] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions and events [ 0.697427] pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.697427] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.697427] pci 0000:00:02.0: vgaarb: bridge control possible [ 0.697427] vgaarb: loaded [ 0.697427] pps_core: LinuxPPS API ver. 1 registered [ 0.697427] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.697427] PTP clock support registered [ 0.697427] EDAC MC: Ver: 3.0.0 [ 0.697427] Registered efivars operations [ 0.697427] PCI: Using ACPI for IRQ routing [ 0.703404] PCI: pci_cache_line_size set to 64 bytes [ 0.703482] e820: reserve RAM buffer [mem 0x0006f000-0x0006ffff] [ 0.703483] e820: reserve RAM buffer [mem 0x00088000-0x0008ffff] [ 0.703484] e820: reserve RAM buffer [mem 0x8a5ca000-0x8bffffff] [ 0.703485] e820: reserve RAM buffer [mem 0x9c64f000-0x9fffffff] [ 0.703486] e820: reserve RAM buffer [mem 0x9d000000-0x9fffffff] [ 0.703487] e820: reserve RAM buffer [mem 0x25f600000-0x25fffffff] [ 0.703586] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [ 0.703586] hpet0: 8 comparators, 64-bit 14.318180 MHz counter [ 0.703923] clocksource: Switched to clocksource tsc-early [ 0.712982] VFS: Disk quotas dquot_6.6.0 [ 0.712999] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.713104] AppArmor: AppArmor Filesystem Enabled [ 0.713121] pnp: PnP ACPI init [ 0.713289] system 00:00: [io 0x0680-0x069f] has been reserved [ 0.713291] system 00:00: [io 0xffff] has been reserved [ 0.713292] system 00:00: [io 0xffff] has been reserved [ 0.713293] system 00:00: [io 0xffff] has been reserved [ 0.713294] system 00:00: [io 0x1800-0x18fe] has been reserved [ 0.713295] system 00:00: [io 0x164e-0x164f] has been reserved [ 0.713300] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.713337] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active) [ 0.713379] system 00:02: [io 0x1854-0x1857] has been reserved [ 0.713382] system 00:02: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [ 0.713403] pnp 00:03: Plug and Play ACPI device, IDs HPQ8001 PNP0303 (active) [ 0.713422] pnp 00:04: Plug and Play ACPI device, IDs SYN1eae PNP0f13 (active) [ 0.796625] system 00:05: [mem 0xfed1c000-0xfed1ffff] has been reserved [ 0.796629] system 00:05: [mem 0xfed10000-0xfed17fff] has been reserved [ 0.796631] system 00:05: [mem 0xfed18000-0xfed18fff] has been reserved [ 0.796632] system 00:05: [mem 0xfed19000-0xfed19fff] has been reserved [ 0.796634] system 00:05: [mem 0xe0000000-0xefffffff] has been reserved [ 0.796636] system 00:05: [mem 0xfed20000-0xfed3ffff] has been reserved [ 0.796637] system 00:05: [mem 0xfed90000-0xfed93fff] has been reserved [ 0.796639] system 00:05: [mem 0xff000000-0xff000fff] has been reserved [ 0.796641] system 00:05: [mem 0xff010000-0xffffffff] could not be reserved [ 0.796643] system 00:05: [mem 0xfee00000-0xfeefffff] could not be reserved [ 0.796644] system 00:05: [mem 0x9fa20000-0x9fa20fff] has been reserved [ 0.796646] system 00:05: [mem 0x9fa10000-0x9fa1ffff] has been reserved [ 0.796650] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.796949] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.797442] pnp: PnP ACPI: found 7 devices [ 0.803189] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns [ 0.803196] pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 01] add_size 1000 [ 0.803199] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000 add_align 100000 [ 0.803200] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 01] add_size 200000 add_align 100000 [ 0.803211] pci 0000:00:1c.0: BAR 14: assigned [mem 0x9fb00000-0x9fcfffff] [ 0.803221] pci 0000:00:1c.0: BAR 15: assigned [mem 0x9fd00000-0x9fefffff 64bit pref] [ 0.803223] pci 0000:00:1c.0: BAR 13: assigned [io 0x2000-0x2fff] [ 0.803225] pci 0000:00:1c.0: PCI bridge to [bus 01] [ 0.803227] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff] [ 0.803231] pci 0000:00:1c.0: bridge window [mem 0x9fb00000-0x9fcfffff] [ 0.803234] pci 0000:00:1c.0: bridge window [mem 0x9fd00000-0x9fefffff 64bit pref] [ 0.803239] pci 0000:00:1c.1: PCI bridge to [bus 02-07] [ 0.803240] pci 0000:00:1c.1: bridge window [io 0x4000-0x4fff] [ 0.803244] pci 0000:00:1c.1: bridge window [mem 0xb1000000-0xb1ffffff] [ 0.803247] pci 0000:00:1c.1: bridge window [mem 0xb0000000-0xb0ffffff 64bit pref] [ 0.803251] pci 0000:00:1c.2: PCI bridge to [bus 08] [ 0.803253] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff] [ 0.803256] pci 0000:00:1c.2: bridge window [mem 0xb2600000-0xb26fffff] [ 0.803259] pci 0000:00:1c.2: bridge window [mem 0xb2400000-0xb24fffff 64bit pref] [ 0.803264] pci 0000:00:1c.5: PCI bridge to [bus 09] [ 0.803267] pci 0000:00:1c.5: bridge window [mem 0xb2500000-0xb25fffff] [ 0.803274] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] [ 0.803275] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] [ 0.803276] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] [ 0.803277] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window] [ 0.803278] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window] [ 0.803279] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window] [ 0.803280] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window] [ 0.803281] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window] [ 0.803282] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window] [ 0.803283] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window] [ 0.803284] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window] [ 0.803285] pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff window] [ 0.803286] pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff window] [ 0.803287] pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff window] [ 0.803288] pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff window] [ 0.803289] pci_bus 0000:00: resource 19 [mem 0x000f0000-0x000fffff window] [ 0.803290] pci_bus 0000:00: resource 20 [mem 0x9fa00000-0xfeafffff window] [ 0.803292] pci_bus 0000:01: resource 0 [io 0x2000-0x2fff] [ 0.803293] pci_bus 0000:01: resource 1 [mem 0x9fb00000-0x9fcfffff] [ 0.803294] pci_bus 0000:01: resource 2 [mem 0x9fd00000-0x9fefffff 64bit pref] [ 0.803295] pci_bus 0000:02: resource 0 [io 0x4000-0x4fff] [ 0.803296] pci_bus 0000:02: resource 1 [mem 0xb1000000-0xb1ffffff] [ 0.803297] pci_bus 0000:02: resource 2 [mem 0xb0000000-0xb0ffffff 64bit pref] [ 0.803298] pci_bus 0000:08: resource 0 [io 0x3000-0x3fff] [ 0.803299] pci_bus 0000:08: resource 1 [mem 0xb2600000-0xb26fffff] [ 0.803300] pci_bus 0000:08: resource 2 [mem 0xb2400000-0xb24fffff 64bit pref] [ 0.803301] pci_bus 0000:09: resource 1 [mem 0xb2500000-0xb25fffff] [ 0.803401] NET: Registered protocol family 2 [ 0.803528] IP idents hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.804725] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes) [ 0.804751] TCP established hash table entries: 65536 (order: 7, 524288 bytes) [ 0.804847] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.804986] TCP: Hash tables configured (established 65536 bind 65536) [ 0.805016] UDP hash table entries: 4096 (order: 5, 131072 bytes) [ 0.805042] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes) [ 0.805094] NET: Registered protocol family 1 [ 0.805099] NET: Registered protocol family 44 [ 0.805110] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] [ 0.828572] pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x6d0 took 21599 usecs [ 0.828618] PCI: CLS 64 bytes, default 64 [ 0.828664] Unpacking initramfs... [ 1.442930] Freeing initrd memory: 37420K [ 1.442944] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.442945] software IO TLB: mapped [mem 0x9818b000-0x9c18b000] (64MB) [ 1.443608] Initialise system trusted keyrings [ 1.443617] Key type blacklist registered [ 1.443658] workingset: timestamp_bits=40 max_order=21 bucket_order=0 [ 1.444853] zbud: loaded [ 1.611368] Key type asymmetric registered [ 1.611369] Asymmetric key parser 'x509' registered [ 1.611377] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [ 1.611396] io scheduler noop registered [ 1.611397] io scheduler deadline registered [ 1.611422] io scheduler cfq registered (default) [ 1.611423] io scheduler mq-deadline registered [ 1.612453] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 1.612466] efifb: probing for efifb [ 1.612478] efifb: framebuffer at 0xa0000000, using 4160k, total 4160k [ 1.612479] efifb: mode is 1366x768x32, linelength=5504, pages=1 [ 1.612480] efifb: scrolling: redraw [ 1.612481] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 1.614737] Console: switching to colour frame buffer device 170x48 [ 1.616783] fb0: EFI VGA frame buffer device [ 1.616791] intel_idle: MWAIT substates: 0x11142120 [ 1.616792] intel_idle: v0.4.1 model 0x45 [ 1.616972] intel_idle: lapic_timer_reliable_states 0xffffffff [ 1.617278] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.617669] Linux agpgart interface v0.103 [ 1.617720] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de> [ 1.617720] AMD IOMMUv2 functionality not available on this system [ 1.617978] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 [ 1.637125] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.637128] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.637234] mousedev: PS/2 mouse device common for all mice [ 1.637476] rtc_cmos 00:01: RTC can wake from S4 [ 1.637625] rtc_cmos 00:01: registered as rtc0 [ 1.637638] rtc_cmos 00:01: alarms up to one month, 242 bytes nvram, hpet irqs [ 1.637648] intel_pstate: Intel P-state driver initializing [ 1.637860] ledtrig-cpu: registered to indicate activity on CPUs [ 1.638914] NET: Registered protocol family 10 [ 1.653172] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [ 1.653676] Segment Routing with IPv6 [ 1.653700] mip6: Mobile IPv6 [ 1.653702] NET: Registered protocol family 17 [ 1.653738] mpls_gso: MPLS GSO support [ 1.653950] mce: Using 7 MCE banks [ 1.653986] microcode: sig=0x40651, pf=0x40, revision=0x1c [ 1.654054] microcode: Microcode Update Driver: v2.2. [ 1.654074] sched_clock: Marking stable (1653746893, 301805)->(1664093622, -10044924) [ 1.654260] registered taskstats version 1 [ 1.654260] Loading compiled-in X.509 certificates [ 1.691829] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [ 1.691845] Loaded X.509 cert 'Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f' [ 1.693020] zswap: loaded using pool lzo/zbud [ 1.693129] AppArmor: AppArmor sha1 policy hashing enabled [ 1.693418] rtc_cmos 00:01: setting system clock to 2024-01-21 08:00:12 UTC (1705824012) [ 1.895352] Freeing unused kernel image memory: 1624K [ 1.923989] Write protecting the kernel read-only data: 16384k [ 1.925458] Freeing unused kernel image memory: 2028K [ 1.925724] Freeing unused kernel image memory: 904K [ 1.936934] x86/mm: Checked W+X mappings: passed, no W+X pages found. [ 1.936936] x86/mm: Checking user space page tables [ 1.945361] x86/mm: Checked W+X mappings: passed, no W+X pages found. [ 1.945362] Run /init as init process [ 2.001117] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2 [ 2.001136] ACPI: Lid Switch [LID0] [ 2.001196] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 2.001207] ACPI: Power Button [PWRB] [ 2.001267] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 2.001278] ACPI: Power Button [PWRF] [ 2.008704] hidraw: raw HID events driver (C) Jiri Kosina [ 2.015398] wmi_bus wmi_bus-PNP0C14:00: WQBJ data block query control method not found [ 2.050917] ACPI: bus type USB registered [ 2.050943] usbcore: registered new interface driver usbfs [ 2.050955] usbcore: registered new interface driver hub [ 2.050970] usbcore: registered new device driver usb [ 2.052262] i801_smbus 0000:00:1f.3: SPD Write Disable is set [ 2.052291] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt [ 2.054657] r8169 0000:08:00.0: can't disable ASPM; OS doesn't have ASPM control [ 2.059730] SCSI subsystem initialized [ 2.061846] cryptd: max_cpu_qlen set to 1000 [ 2.070403] thermal LNXTHERM:00: registered as thermal_zone0 [ 2.070406] ACPI: Thermal Zone [TZ00] (44 C) [ 2.070792] thermal LNXTHERM:01: registered as thermal_zone1 [ 2.070793] ACPI: Thermal Zone [TZ01] (44 C) [ 2.070887] thermal LNXTHERM:02: registered as thermal_zone2 [ 2.070889] ACPI: Thermal Zone [TZ02] (28 C) [ 2.083979] libata version 3.00 loaded. [ 2.085865] AVX2 version of gcm_enc/dec engaged. [ 2.085866] AES CTR mode by8 optimization enabled [ 2.087246] r8169 0000:08:00.0 eth0: RTL8106e, 48:0f:cf:dd:00:c6, XID 44900000, IRQ 41 [ 2.092368] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 2.092376] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 [ 2.092442] ahci 0000:00:1f.2: version 3.0 [ 2.093425] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x000000000004b810 [ 2.093429] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported [ 2.093605] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.093607] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.093609] usb usb1: Product: xHCI Host Controller [ 2.093610] usb usb1: Manufacturer: Linux 4.19.0-26-amd64 xhci-hcd [ 2.093612] usb usb1: SerialNumber: 0000:00:14.0 [ 2.093964] hub 1-0:1.0: USB hub found [ 2.093979] hub 1-0:1.0: 9 ports detected [ 2.094597] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.095618] ehci-pci: EHCI PCI platform driver [ 2.096797] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 2.096802] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 [ 2.096807] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed [ 2.096854] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 [ 2.096856] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.096858] usb usb2: Product: xHCI Host Controller [ 2.096859] usb usb2: Manufacturer: Linux 4.19.0-26-amd64 xhci-hcd [ 2.096861] usb usb2: SerialNumber: 0000:00:14.0 [ 2.096925] ehci-pci 0000:00:1d.0: EHCI Host Controller [ 2.096999] hub 2-0:1.0: USB hub found [ 2.097009] hub 2-0:1.0: 4 ports detected [ 2.097546] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 3 [ 2.097558] ehci-pci 0000:00:1d.0: debug port 2 [ 2.101479] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported [ 2.101498] ehci-pci 0000:00:1d.0: irq 23, io mem 0xb271c000 [ 2.103009] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 3 ports 6 Gbps 0x3 impl SATA mode [ 2.103013] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst [ 2.105321] r8169 0000:08:00.0 enp8s0: renamed from eth0 [ 2.107292] scsi host0: ahci [ 2.107453] scsi host1: ahci [ 2.107691] scsi host2: ahci [ 2.107750] ata1: SATA max UDMA/133 abar m2048@0xb271b000 port 0xb271b100 irq 42 [ 2.107752] ata2: SATA max UDMA/133 abar m2048@0xb271b000 port 0xb271b180 irq 42 [ 2.107752] ata3: DUMMY [ 2.115940] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00 [ 2.116013] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 2.116015] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.116017] usb usb3: Product: EHCI Host Controller [ 2.116019] usb usb3: Manufacturer: Linux 4.19.0-26-amd64 ehci_hcd [ 2.116020] usb usb3: SerialNumber: 0000:00:1d.0 [ 2.116166] hub 3-0:1.0: USB hub found [ 2.116174] hub 3-0:1.0: 2 ports detected [ 2.175747] checking generic (a0000000 410000) vs hw (a0000000 10000000) [ 2.175748] fb: switching to inteldrmfb from EFI VGA [ 2.175767] Console: switching to colour dummy device 80x25 [ 2.175872] [drm] Replacing VGA console driver [ 2.176587] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.176588] [drm] Driver supports precise vblank timestamp query. [ 2.176958] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 2.268181] [drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0 [ 2.269485] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 2.270393] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 [ 2.274498] fbcon: inteldrmfb (fb0) is primary device [ 2.352010] usb 1-1: new low-speed USB device number 2 using xhci_hcd [ 2.380025] usb 3-1: new high-speed USB device number 2 using ehci-pci [ 2.423243] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 2.423266] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.425503] ata1.00: supports DRM functions and may not be fully accessible [ 2.425653] ata1.00: ATA-10: CT500MX500SSD1, M3CR023, max UDMA/133 [ 2.425656] ata1.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 32), AA [ 2.427126] ata1.00: supports DRM functions and may not be fully accessible [ 2.427361] ata2.00: ATAPI: hp DVDRW SU208GB, HH00, max UDMA/100 [ 2.428195] ata1.00: configured for UDMA/133 [ 2.430188] ata2.00: configured for UDMA/100 [ 2.438336] ahci 0000:00:1f.2: port does not support device sleep [ 2.438769] scsi 0:0:0:0: Direct-Access ATA CT500MX500SSD1 023 PQ: 0 ANSI: 5 [ 2.453178] scsi 1:0:0:0: CD-ROM hp DVDRW SU208GB HH00 PQ: 0 ANSI: 5 [ 2.468041] tsc: Refined TSC clocksource calibration: 2394.456 MHz [ 2.468059] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2283c236f90, max_idle_ns: 440795217409 ns [ 2.468112] clocksource: Switched to clocksource tsc [ 2.503913] usb 1-1: New USB device found, idVendor=046d, idProduct=c05a, bcdDevice=63.00 [ 2.503918] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.503920] usb 1-1: Product: USB Optical Mouse [ 2.503941] usb 1-1: Manufacturer: Logitech [ 2.517332] usbcore: registered new interface driver usbhid [ 2.517333] usbhid: USB HID core driver [ 2.536368] usb 3-1: New USB device found, idVendor=8087, idProduct=8000, bcdDevice= 0.04 [ 2.536371] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.536902] hub 3-1:1.0: USB hub found [ 2.537110] hub 3-1:1.0: 8 ports detected [ 2.824048] usb 3-1.5: new high-speed USB device number 3 using ehci-pci [ 2.982808] usb 3-1.5: New USB device found, idVendor=0c45, idProduct=6517, bcdDevice= 0.09 [ 2.982812] usb 3-1.5: New USB device strings: Mfr=2, Product=1, SerialNumber=3 [ 2.982815] usb 3-1.5: Product: HP Webcam [ 2.982817] usb 3-1.5: Manufacturer: DESEL01BI7Q9JZ [ 2.982819] usb 3-1.5: SerialNumber: HP Webcam [ 3.094459] psmouse serio1: synaptics: queried max coordinates: x [..5696], y [..4884] [ 3.137991] psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1044..] [ 3.222061] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, id: 0x1c0b1, caps: 0xf00133/0x240000/0xa2400/0x0, board id: 2665, fw id: 1458825 [ 3.278127] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 3.414775] Console: switching to colour frame buffer device 170x48 [ 3.440386] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 3.466468] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C05A.0001/input/input7 [ 3.466550] hid-generic 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-1/input0 [ 3.471066] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 3.471069] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 3.471076] sd 0:0:0:0: [sda] Write Protect is off [ 3.471078] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 3.471086] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.473982] sda: sda1 sda2 sda3 sda4 sda6 sda7 [ 3.474551] sd 0:0:0:0: [sda] supports TCG Opal [ 3.474553] sd 0:0:0:0: [sda] Attached SCSI disk [ 3.516279] sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray [ 3.516282] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 3.516610] sr 1:0:0:0: Attached scsi CD-ROM sr0 [ 36.052073] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null) [ 36.290218] systemd[1]: Inserted module 'autofs4' [ 36.368520] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [...] [ 37.423514] intel_rapl: RAPL package 0 domain package locked by BIOS [ 37.475481] audit: type=1400 audit(1705824048.274:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=666 comm="apparmor_parser" [ 37.477318] audit: type=1400 audit(1705824048.278:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=664 comm="apparmor_parser" [ 37.478019] audit: type=1400 audit(1705824048.278:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=667 comm="apparmor_parser" [ 37.480624] audit: type=1400 audit(1705824048.282:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=665 comm="apparmor_parser" [ 37.482022] audit: type=1400 audit(1705824048.282:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=676 comm="apparmor_parser" [ 37.482026] audit: type=1400 audit(1705824048.282:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=676 comm="apparmor_parser" [ 37.484433] audit: type=1400 audit(1705824048.286:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session" pid=673 comm="apparmor_parser" [ 37.484437] audit: type=1400 audit(1705824048.286:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session//chromium" pid=673 comm="apparmor_parser" [ 37.485297] audit: type=1400 audit(1705824048.286:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=675 comm="apparmor_parser" [ 37.485301] audit: type=1400 audit(1705824048.286:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=675 comm="apparmor_parser" [ 37.490803] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input17 [ 37.490875] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input18 [ 37.635898] input: HP WMI hotkeys as /devices/virtual/input/input10 [ 126.846022] vboxdrv: loading out-of-tree module taints kernel. [ 126.846303] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 126.856428] vboxdrv: Found 4 processor cores [ 126.880113] vboxdrv: TSC mode is Invariant, tentative frequency 2394454504 Hz [ 126.880114] vboxdrv: Successfully loaded version 6.0.24 (interface 0x00290008) [ 127.047031] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready [ 127.049820] r8169 0000:08:00.0: firmware: direct-loading firmware rtl_nic/rtl8106e-1.fw [ 127.051322] Generic PHY r8169-800:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE) [ 127.091797] VBoxNetFlt: Successfully started. [ 127.098008] VBoxNetAdp: Successfully started. [ 127.312116] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready [ 127.317547] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready [ 127.317589] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 127.317726] rt2800pci 0000:09:00.0: firmware: direct-loading firmware rt3290.bin [ 127.317732] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 127.402817] broken atomic modeset userspace detected, disabling atomic [ 127.449737] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready [ 127.582228] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready [ 127.670551] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready [ 128.902291] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready [ 130.021090] wlp9s0f0: authenticate with cc:ce:1e:e7:0d:49 [ 130.023445] wlp9s0f0: send auth to cc:ce:1e:e7:0d:49 (try 1/3) [ 130.028585] wlp9s0f0: authenticated [ 130.031976] wlp9s0f0: associate with cc:ce:1e:e7:0d:49 (try 1/3) [ 130.043559] wlp9s0f0: RX AssocResp from cc:ce:1e:e7:0d:49 (capab=0x1431 status=0 aid=1) [ 130.043622] wlp9s0f0: associated [ 130.096620] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0f0: link becomes ready [ 130.222513] wlp9s0f0: Limiting TX power to 20 (20 - 0) dBm as advertised by cc:ce:1e:e7:0d:49 The two big delays are just before 36 and 126. It takes some 30 secs to mount sda7 (where Buster is) and 90 seconds for some operation related to Virtualbox; that delay wasn't there before the broken installation to sda2. The UUID bb5b8660etc. mentioned in the third photo linked above ("A start job is running for /dev/disk/by-uuid/bb5b...") might perhaps refer to a virtual machine? None of my partitions has that UUID. I updated grub and reinstalled it, but the problem persists. I installed a Mint to the free partition sda2 and it boots without delay (some 16 seconds, 6 of which for suppressed callbacks in kauditd_printk_skb), but my old Debian Buster still takes more than 2 minutes. Perhaps I should try to reinstall Bookworm to sda2? I am using this PC for working and would really like to fix the booting delay. Many thanks for any suggestions you can provide. | ForeverNewbie wrote: 2024-01-21 09:53 I've solved a part of the problem. The second delay of 90 secs was because Bookworm installation changed the UUID of the swap file, so that the /etc/fstab of my Buster in sda7 was looking for the wrong UUID. I have fixed that and only have the first 30 secs delay now. Good to know. Please report your current disk partitioning scheme and the /etc/fstab content; you can use the commands: Code: Select alllsblk -f cat /etc/fstab ForeverNewbie wrote: 2024-01-21 09:53 But the first delay, which appears to have to do with mounting sda7 is clearly not dependent on the fstab in sda7 — at any rate, the UUID of sda7 in fstab is correct. Boot Debian after replacing the "quiet" kernel option with "debug": this will make your logs more verbose. After booting, check the contents of /var/log/syslog mainly in the time lapse between 3 and 37 seconds from the start of the boot, but the full log could be useful to inspect. You can report logs in one the following ways: paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message attaching the logs to a follow-up forum message as a compressed zip or gz file paste logs into the body of a follow-up message between code tags (if they fit the size of a forum message) Hope this helps. |
Hello everyone, Lately had to search for some binary for bluetooth rtw8852b_fw-1.bin, it is not present in stable branch Code: Select allapt-filie search rtw8852b_fw-1.bin But found it in testing firmware-realtek. Was wondering what would be best way to add testing/sid branch so I could query from there as well using apt-file. My idea was adding them to sources and just setting them priority of -1 in apt preferences. Does anyone know if there is easier way? Cheers | Hello @steve_v, That's really interesting. In my Debian Bookworm, I added the following line to instruct apt-file to include packages from Debian Trixie (current testing) in the search: Code: Select alldeb [target=Contents-deb] http://deb.debian.org/debian trixie main non-free contrib non-free-firmware If I do the search proposed by the OP in the first post, the result is: Code: Select all$ apt-file search rtw8852b_fw-1.bin firmware-realtek: /usr/lib/firmware/rtw89/rtw8852b_fw-1.bin From the previous output, I cannot tell which suite the package in the result is from: is it from Bookworm or Trixie? I can filter using the --filter-suites option, but I would do it every time for each configured suite (if more than one): Code: Select all$ apt-file --filter-suites=bookworm search rtw8852b_fw-1.bin $ apt-file --filter-suites=trixie search rtw8852b_fw-1.bin firmware-realtek: /usr/lib/firmware/rtw89/rtw8852b_fw-1.bin Furthermore, when the same file is in a package that exists both in Bookworm and Trixie, the apt-file command does not report both, but reports only one of them and it do not show from which suite; for example: Code: Select all$ apt-file --filter-suites=trixie search /usr/bin/apt-file apt-file: /usr/bin/apt-file $ apt-file --filter-suites=bookworm search /usr/bin/apt-file apt-file: /usr/bin/apt-file $ apt-file search /usr/bin/apt-file apt-file: /usr/bin/apt-file Is there a way to make apt-file: 1) display the suite in the output line 2) display all the matching suites Something like (just an example): Code: Select all$ apt-file search /usr/bin/apt-file bookworm apt-file: /usr/bin/apt-file trixie apt-file: /usr/bin/apt-file Thanks. |
System Specs OS: Debian GNU/Linux 12 (bookworm) x86_64 (stable) Kernel: 6.1.0-17-amd64 Shell: bash 5.2.15 DE: GNOME 43.9 WM: Mutter Windowing System: Wayland systemd version: systemd 252 (252.19-1~deb12u1) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified ____________________________________________ Issue I don't know exactly when this issue started happening, but I only realised it today when booting my system and I saw a quick [FAILED] message popped up when systemd starts the various services and daemons. Unfortunately, I can't quite catch it with my eyes (the screen scrolls by too quickly), but I got to investigating and it is most likely the zram swap service. Firstly, I checked the service status: Code: Select all$ sudo systemctl status zramswap.service Output Then I ran Code: Select all$ sudo dmesg Output Both outputs list the same error: /usr/sbin/zramswap: line 53: echo: write error: Device or resource busy zram: Can't change algorithm for initialized device. Then I checked the output of zramctl: Code: Select all$ sudo zramctl [sudo] password for ory: NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 4G 4K 80B 12K 12 [SWAP] I verified the algorithm by running: Code: Select all$ cat /sys/block/zram0/comp_algorithm lzo [lzo-rle] lz4 lz4hc zstd The algorithm and disksize values are wrong, they are supposed to be 'zstd' and '8G' as I had originally configured them when I installed the system several months ago. I had previously verified the status of zramctl and always got the correct values. Well, up until today. I verified the zram configuration (correct) with Code: Select all$ cat /etc/default/zramswap Output So I'm not sure how to go from here. Any advice on how I could fix this issue? For the record, I don't remember any system updates related to systemd or zram in the last days, and the system has been stable running without any hiccups. ____________________________________________ Workaround One workaround I found though is modifying zram-generator.conf and rebooting the system: Code: Select all$ sudo nano /etc/systemd/zram-generator.conf zram-generator.conf I added all the lines below Code: Select all[zram0] Upon reboot, the systemd errors still persist in the logs (dmesg and journalctl), but zramctl is configured as intended: Code: Select all$ sudo zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 zstd 7.8G 4K 64B 4K 12 [SWAP] Code: Select all$ cat /sys/block/zram0/comp_algorithm lzo lzo-rle lz4 lz4hc [zstd] | Hello, Can you check in /var/log/apt/history.log when you upgraded the kernel to the 6.1.0-17-amd64 version ? You can check with command: Code: Select allsudo zgrep -B 3 6.1.0-17-amd64 /var/log/apt/history.* Can you verify when the error appeared for the first time in the systemd journal ? You can check with the following command: Code: Select allsudo journalctl -g "zram: Can't change algorithm for initialized device" |
Dear team We have a linux debian cluster (HPC). When I am adding users on the head node, it is getting accomplished successfully. The user is displayed on /etc/passwd However, when I am logging onto the individual nodes, the user name is not being displayed on /etc/passwd despite the fact that I ran sync-nodes during user addition. In the directory, /var/log/sync-nodes/ the individual node.log is showing following error: @ERROR: max connections (50) reached -- try again later rsync error: error starting client-server protocol (code 5) at main.c(1534) [Receiver=3.0.9] @ERROR: max connections (50) reached -- try again later rsync error: error starting client-server protocol (code 5) at main.c(1534) [Receiver=3.0.9] kernel.shmmax = 1610612736 vm.nr_hugepages = 64 exit status = 0 Could you please shed some light? Thanks. | Hello, Code: Select allrsync error: error starting client-server protocol (code 5) at main.c(1534) [Receiver=3.0.9] @ERROR: max connections (50) reached -- try again later To correct the error above, you probably need to adjust the "max connections" [1] parameter in the rsyncd.conf configuration file (of the node running rsync in daemon node). How many nodes are there in the HPC ? --- [1] rsyncd.conf (5) - configuration file for rsync in daemon mode |
I have three systems on bookworm, all with the same rkhunter configuration. Two of them are sending daily email reports from the daily cron job, the third one is not. I would like the third system to send emails as well. The following files have exactly the same content on all systems: /etc/cron.daily/rkhunter (as distributed by debian) /etc/rkhunter.conf (slightly modified, mostly some local exceptions) | What does this command produce Code: Select all$> LANG="C" apt policy courier-mta dma esmtp-run exim4-daemon-heavy exim4-daemon-light msmtp-mta nullmailer opensmtpd postfix sendmail-bin ssmtp 2>/dev/null |\ mawk '/^[^[:blank:]]/{PK=$1} /^ Installed: [^(]/{print PK,$2}' on each of your systems? |
Hi folks, Here is my iptables: Code: Select allChain PREROUTING (policy ACCEPT) target prot opt source destination REDIRECT tcp -- anywhere anywhere tcp dpt:submission redir ports 23001 REDIRECT tcp -- anywhere anywhere tcp dpt:31284 redir ports 23002 REDIRECT tcp -- anywhere anywhere tcp dpt:2223 redir ports 23003 REDIRECT tcp -- anywhere anywhere tcp dpt:35742 redir ports 23004 REDIRECT tcp -- anywhere anywhere tcp dpt:imaps redir ports 23005 REDIRECT tcp -- anywhere anywhere tcp dpt:https redir ports 23006 REDIRECT tcp -- anywhere anywhere tcp dpt:2224 redir ports 23007 REDIRECT tcp -- anywhere anywhere tcp dpt:2225 redir ports 23008 REDIRECT tcp -- anywhere anywhere tcp dpt:imap2 redir ports 23009 REDIRECT tcp -- anywhere anywhere tcp dpt:smtp redir ports 23010 REDIRECT tcp -- anywhere anywhere tcp dpt:submissions redir ports 23011 REDIRECT tcp -- anywhere anywhere tcp dpt:http redir ports 23012 REDIRECT tcp -- anywhere anywhere tcp dpt:2222 redir ports 23013 Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination REDIRECT tcp -- anywhere anywhere tcp dpt:submission redir ports 23001 REDIRECT tcp -- anywhere anywhere tcp dpt:31284 redir ports 23002 REDIRECT tcp -- anywhere anywhere tcp dpt:2223 redir ports 23003 REDIRECT tcp -- anywhere anywhere tcp dpt:35742 redir ports 23004 REDIRECT tcp -- anywhere anywhere tcp dpt:imaps redir ports 23005 REDIRECT tcp -- anywhere anywhere tcp dpt:https redir ports 23006 REDIRECT tcp -- anywhere anywhere tcp dpt:2224 redir ports 23007 REDIRECT tcp -- anywhere anywhere tcp dpt:2225 redir ports 23008 REDIRECT tcp -- anywhere anywhere tcp dpt:imap2 redir ports 23009 REDIRECT tcp -- anywhere anywhere tcp dpt:smtp redir ports 23010 REDIRECT tcp -- anywhere anywhere tcp dpt:submissions redir ports 23011 REDIRECT tcp -- anywhere anywhere tcp dpt:http redir ports 23012 REDIRECT tcp -- anywhere anywhere tcp dpt:2222 redir ports 23013 Chain POSTROUTING (policy ACCEPT) target prot opt source destination My server is accessible locally on ports 80 and 23012. But not from outside. Any ideas? Code: Select all$ curl 127.0.0.1:80 <html> <head><title>401 Authorization Required</title></head> <body> <center><h1>401 Authorization Required</h1></center> <hr><center>nginx/1.24.0</center> </body> </html> $ curl 127.0.0.1:23012 <html> <head><title>401 Authorization Required</title></head> <body> <center><h1>401 Authorization Required</h1></center> <hr><center>nginx/1.24.0</center> </body> </html> Same set of rules works on another instance with amazon linux. Any idea is highly appreciated. Thanks in advance. | Debian and also other "modern" Linux distros use nftables. |
There are some rumblings about this when doing a web search, but nothing substantive jumps out. I need to switch to linux-image-rt/oldstable and it seems nvidia-current-dkms is incompatible. Any elegant path forward? I'd hate to have to jump to manual driver build from the nvidia vendor website. | Nvidia has never built on RT kernels afaik. There's a check in the build script which blocks it. You can override it with: Code: Select allexport IGNORE_PREEMPT_RT_PRESENCE=1 before installing a kernel or nvidia driver. I'm interested to hear why you want to install an RT kernel. They may be useful in an industrial engineering setting but can be a problem for general purpose use. I tried several for audio production a while back but got better results with a Liquorix kernel which is default configured for low latency. Even stock kernels since 5.19 have been capable of full pre-emption by adding the kernel boot option preempt=full. |
Hi, I've used systemd-cryptenroll to add a slot to my LUKS encrypted root partition to allow unlocking with a FIDO2 key. I followed up by modifying /etc/crypttab and update-initramfs. However, when the initramfs was generated, as well as upon boot I the following error was displayed: Code: Select allcryptsetup: WARNING: nvme0n1p3_crypt: ignoring unknown option 'fido2-device' Upon boot, I was prompted for my LUKS passphrase instead of being able to unlok with the fido2 key. I also tried adding libfido2.so.1.10.0 to the initramfs image, but it didn't solve it. Any ideas? | Okay, so switching to dracut instead of initramfs-tools seems to be a good start. It now attempts to unlock the luks partition with systemd-cryptsetup (instead of the old cryptsetup). However, it still doesn't recognize the fido support. It looks like it fails to dlopen the libfido2 shared library, despite the fact that I explicitly added it to the initramfs. |
I have 2 computers running Stretch and am trying to get an offline backup of one, transferring using rsync over ssh across the internet. When transferring a large file, the speed will suddenly drop for no reason that I can figure out. When running at its best, I get just under 3MB/sec - a 16GB file will take less than 2 hours at this rate. During the same file transfer, the speed will drop to < 130K/sec, resulting in multiple days required to complete the transfer. Top shows no indication as to why the change occurred. During the best transfer rate, the source CPU hovers at around 5% and the destination at about 20%. Memory usage is also healthy on both ends. When the speed slows, both computers drop to about 1% CPU utilization. My test file is a 16+ GB tar.gz file, so I am not using compression during the transfer: Code: Select allrsync -avh -e ssh --progress source dest Sometimes if I restart the transfer, it will repeat the above. Other times it will start out at the slow speed. I am looking for any reasons why the speed might change so drastically, and more importantly, for anyway to prevent it. I realize "over the internet" is not optimal and there are many factors in between the endpoints that might affect this, but it would seem that the fluctuations would be up *and* down, yet I've never seen the speed increase once it has dropped. Traceroute between the 2 endpoints shows < 20ms hop counts all the way through, while the transfer is moving along, and when it is crawling. I'm stuck. Ideas welcome!! | Sometimes it's just the hardware. Please edit the title of your first post to mark [SOLVED]. |
I have built a Bullseye postfix server to replace one currently running Stretch. The Stretch server is running Squirrelmail which is no longer available with Bullseye, so I am setting up Roundcube instead. The Stretch server uses system users from /etc/passwd for the postfix accounts - there is no separate database of users, and I am continuing that on the Bullseye system. When users access Squirrelmail, they do so using the url 'hostname.example.org/webmail' - in other words there is a 'webmail' alias configured, which I've also built into the Roundcube setup. I am able to login via Roundcube and access my imap email ported from the Stretch system, however Roundcube thinks my email address includes the webmail server's host name, not just the domain. For example, roundcube thinks my email address is bithead@webmail.examplel.org when it should be bithead@example.org. I am not sure how to fix the email addresses as seen by Roundcube - any pointers would be appreciated! | Have a look here: https://github.com/roundcube/roundcubem ... figuration The config file is also fairly well documented. Are you logging in with a full address or just a username? |
Hi I have a problem with my wifi card after install Debian 11. It worked for a moment but after a time never come back to work and looking the system logs I found this: mar 03 17:11:11 taurus95 sudo[50553]: andres : TTY=pts/4 ; PWD=/home/andres ; USER=root ; COMMAND=/usr/bin/journalctl -xe mar 03 17:11:11 taurus95 sudo[50553]: pam_unix(sudo:session): session opened for user root(uid=0) by andres(uid=1000) mar 03 17:11:12 taurus95 NetworkManager[50220]: <error> [1646338272.4666] device (wlo1): Couldn't initialize supplicant interface: Failed to D-Bus activate wpa_supplicant service mar 03 17:11:12 taurus95 NetworkManager[50220]: <info> [1646338272.4667] manager: startup complete I try to see the status of wpa_supplicant service and this is the output: ● wpa_supplicant.service Loaded: masked (Reason: Unit wpa_supplicant.service is masked.) Active: inactive (dead) I don't know if this is normal. I try to found something usefully in google but nothing. Wifi info: Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) iwlwifi installed I think that the problem is the wpa_supplicant service running masked? Someone can help me please? | Check if /lib/systemd/system/wpa_supplicant.service has a symbolic link to /dev/null. If it does, remove the link, and run "systemctl daemon-reload". Then the service should be able to be enabled. |
I have Debian 11 64 bit on my machine and have been using Windows apps on wine. My wine version are as per below command Code: Select alldpkg -l | grep wine ii wine-stable 7.0.0.0~bullseye-1 amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-stable-amd64 7.0.0.0~bullseye-1 amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-stable-i386:i386 7.0.0.0~bullseye-1 i386 WINE Is Not An Emulator - runs MS Windows programs ii winehq-stable 7.0.0.0~bullseye-1 amd64 WINE Is Not An Emulator - runs MS Windows programs ii winetricks 0.0+20210206-2 all simple tool to work around common problems in Wine For the last few days I am unable to launch any windows apps and when I type winefile or winecfg on terminal I get "Bus error" message. Please assist | https://forum.winehq.org/viewtopic.php?f=8&t=36345 I think that winehq is definitely the best site for discussing this problem But besides that, winecfg is not used to launch the apllications, and the env variable WINEDEBUG=all can help in diagnosing the problems with the wine command. |
I have Debian 11 64 bit on my machine.Lately when I run the command Code: Select allapt update && apt upgrade I get message Code: Select allError: Timeout was reached Please assist. | What does your sources list say? |
Hi everyone, I'm having a problem with my internet connection and I'm hoping someone here might be able to help me solve it. I'm using my neighbourg wifi network (which he knows & agrees). It was working very well until a few days ago. Since then I have various different errors and, most of the time, I'm unable to reach any page. Sometimes I do but it's very, very, slow. Sometimes my pc has trouble connecting to the wifi. The thing is, I'm able to use the same wifi network on a different machine on Debian as well, an old laptop, and the network works fine there. On the new pc (the one I'm having the problem on) I have a dual boot Debian Bullseye/Windows and on windows, the wifi works fine as well. The signal is good. So on Debian Bullseye, the most common mistake I get is : Code: Select allping debian-facile.org PING nc-ass-vip.sdv.fr (212.95.74.75) 56(84) bytes of data. ^CFrom 192.168.0.21 icmp_seq=63 Destination Host Unreachable From 192.168.0.21 icmp_seq=64 Destination Host Unreachable From 192.168.0.21 icmp_seq=65 Destination Host Unreachable From 192.168.0.21 icmp_seq=66 Destination Host Unreachable --- nc-ass-vip.sdv.fr ping statistics --- 66 packets transmitted, 0 received, +4 errors, 100% packet loss, time 66572ms pipe 4 It doesn't even reach the website I'm asking but goes directly to nc-ass-vip.sdv.fr which is the internet provider (numericable) error webpage... Which is probably related to this : Code: Select allcat /etc/resolv.conf # Generated by NetworkManager search numericable.fr nameserver 89.2.0.1 nameserver 89.2.0.2 Also encoutered this : Code: Select allfévr. 22 17:08:29 asus wpa_supplicant[754]: bgscan simple: Failed to enable sig> févr. 22 17:08:29 asus wpa_supplicant[754]: bgscan simple: Failed to enable signal strength monitoring Also this : Code: Select allsystemctl systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-02-22 18:17:40 CET; 13min ago Docs: man:NetworkManager(8) Main PID: 747 (NetworkManager) Tasks: 3 (limit: 18902) Memory: 14.4M CPU: 417ms CGroup: /system.slice/NetworkManager.service └─747 /usr/sbin/NetworkManager --no-daemon févr. 22 18:17:52 asus NetworkManager[747]: <info> [1645550272.0251] manager: startup complete févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.3120] device (wlan0): supplicant interface state: completed -> authenticating févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.3121] device (wlan0): DHCPv4 lease renewal requested févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.3343] dhcp4 (wlan0): canceled DHCP transaction févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.3344] dhcp4 (wlan0): state changed bound -> done févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.3347] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds) févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.3380] device (wlan0): supplicant interface state: authenticating -> associating févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.3566] device (wlan0): supplicant interface state: associating -> 4way_handshake févr. 22 18:18:22 asus NetworkManager[747]: <info> [1645550302.4799] device (wlan0): supplicant interface state: 4way_handshake -> completed févr. 22 18:18:25 asus NetworkManager[747]: <info> [1645550305.3493] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.21 The network problems have come simultaneously with troubles booting Debian. One time on two, the screen just freezes before I even get to the page where I should be able to enter my username & pwd. This might show up in this but I don't understand this enough to tell : Code: Select alljournalctl -b -r -p err -- Journal begins at Sun 2021-12-05 15:48:49 CET, ends at Sat 2022-02-26 19:38:> févr. 26 19:02:17 asus pipewire[1511]: Failed to receive portal pid: org.freede> févr. 26 19:02:17 asus pulseaudio[1109]: Error opening PCM device front:0: Aucu> févr. 26 19:02:17 asus pulseaudio[1109]: Error opening PCM device front:0: Aucu> févr. 26 19:02:17 asus lightdm[1485]: gkr-pam: unable to locate daemon control > févr. 26 18:58:47 asus wpa_supplicant[761]: bgscan simple: Failed to enable sig> févr. 26 18:58:43 asus pipewire[1108]: Failed to receive portal pid: org.freede> févr. 26 18:58:41 asus systemd[1]: Failed to start Raise network interfaces. févr. 26 18:58:41 asus dhclient[1005]: exiting. févr. 26 18:58:41 asus dhclient[1005]: févr. 26 18:58:41 asus dhclient[1005]: process and the information we find help> févr. 26 18:58:41 asus dhclient[1005]: before submitting a bug. These pages ex> févr. 26 18:58:41 asus dhclient[1005]: bugs on either our web page at www.isc.o> févr. 26 18:58:41 asus dhclient[1005]: than a configuration issue please read t> févr. 26 18:58:41 asus dhclient[1005]: If you think you have received this mess> févr. 26 18:58:41 asus dhclient[1005]: févr. 26 18:58:41 asus dhclient[1005]: Failed to get interface index: No such d> févr. 26 18:58:41 asus bluetoothd[835]: sap-server: Operation not permitted (1) févr. 26 18:58:41 asus bluetoothd[835]: profiles/sap/server.c:sap_server_regist> févr. 26 18:58:39 asus kernel: ucsi_acpi USBC000:00: PPM init failed (-110) févr. 26 18:58:39 asus kernel: mt7921e 0000:03:00.0: Firmware init done févr. 26 18:58:38 asus systemd[1]: Failed to start NVIDIA Persistence Daemon. févr. 26 18:58:38 asus nvidia-persistenced[775]: Failed to query NVIDIA devices> lines 1-23...skipping... -- Journal begins at Sun 2021-12-05 15:48:49 CET, ends at Sat 2022-02-26 19:38:48 CET. -- févr. 26 19:02:17 asus pipewire[1511]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name févr. 26 19:02:17 asus pulseaudio[1109]: Error opening PCM device front:0: Aucun fichier ou dossier de ce type févr. 26 19:02:17 asus pulseaudio[1109]: Error opening PCM device front:0: Aucun fichier ou dossier de ce type févr. 26 19:02:17 asus lightdm[1485]: gkr-pam: unable to locate daemon control file févr. 26 18:58:47 asus wpa_supplicant[761]: bgscan simple: Failed to enable signal strength monitoring févr. 26 18:58:43 asus pipewire[1108]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name févr. 26 18:58:41 asus systemd[1]: Failed to start Raise network interfaces. févr. 26 18:58:41 asus dhclient[1005]: exiting. févr. 26 18:58:41 asus dhclient[1005]: févr. 26 18:58:41 asus dhclient[1005]: process and the information we find helpful for debugging. févr. 26 18:58:41 asus dhclient[1005]: before submitting a bug. These pages explain the proper févr. 26 18:58:41 asus dhclient[1005]: bugs on either our web page at www.isc.org or in the README file févr. 26 18:58:41 asus dhclient[1005]: than a configuration issue please read the section on submitting févr. 26 18:58:41 asus dhclient[1005]: If you think you have received this message due to a bug rather févr. 26 18:58:41 asus dhclient[1005]: févr. 26 18:58:41 asus dhclient[1005]: Failed to get interface index: No such device févr. 26 18:58:41 asus bluetoothd[835]: sap-server: Operation not permitted (1) févr. 26 18:58:41 asus bluetoothd[835]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. févr. 26 18:58:39 asus kernel: ucsi_acpi USBC000:00: PPM init failed (-110) févr. 26 18:58:39 asus kernel: mt7921e 0000:03:00.0: Firmware init done févr. 26 18:58:38 asus systemd[1]: Failed to start NVIDIA Persistence Daemon. févr. 26 18:58:38 asus nvidia-persistenced[775]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 119 has read and write permissions for those files. févr. 26 18:58:38 asus kernel: mt7921e 0000:03:00.0: ASIC revision: 79610010 févr. 26 18:58:38 asus systemd-udevd[561]: Error running install command 'modprobe -i nvidia-current ' for module nvidia: retcode 1 févr. 26 18:58:37 asus systemd-udevd[527]: /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14 Invalid key 'SYSFS' févr. 26 18:58:37 asus systemd-udevd[527]: /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9 Invalid key 'SYSFS' févr. 26 18:58:37 asus systemd-modules-load[506]: Failed to insert module 'nvidia_drm': Invalid argument févr. 26 18:58:37 asus systemd-modules-load[506]: Error running install command 'modprobe nvidia-modeset ; modprobe -i nvidia-current-drm ' for module nvidia_drm: retcode 1 févr. 26 18:58:37 asus systemd[1]: Failed to start Load Kernel Modules. févr. 26 18:58:37 asus kernel: DMAR: [DMA Read NO_PASID] Request device [02:00.0] fault addr 0xffffb000 [fault reason 0x06] PTE Read access is not set févr. 26 18:58:37 asus kernel: DMAR: DRHD: handling fault status reg 3 févr. 26 18:58:37 asus kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PCI0.LPCB.H_EC.TFN1 (20210930/dspkginit-438) févr. 26 18:58:37 asus kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PCI0.LPCB.H_EC.TFN1 (20210930/dspkginit-438) févr. 26 18:58:37 asus kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PCI0.LPCB.H_EC.TFN1 (20210930/dspkginit-438) févr. 26 18:58:37 asus kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PCI0.LPCB.H_EC.TFN1 (20210930/dspkginit-438) févr. 26 18:58:37 asus kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PCI0.LPCB.H_EC.TFN1 (20210930/dspkginit-438) févr. 26 18:58:37 asus kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PCI0.LPCB.H_EC.TFN1 (20210930/dspkginit-438) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) févr. 26 18:58:37 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS10._PLD], AE_ALREADY_EXISTS (20210930/dswload2-326) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) févr. 26 18:58:37 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS10._UPC], AE_ALREADY_EXISTS (20210930/dswload2-326) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) févr. 26 18:58:37 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS09._PLD], AE_ALREADY_EXISTS (20210930/dswload2-326) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) févr. 26 18:58:37 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS09._UPC], AE_ALREADY_EXISTS (20210930/dswload2-326) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) févr. 26 18:58:37 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS08._PLD], AE_ALREADY_EXISTS (20210930/dswload2-326) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) févr. 26 18:58:37 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS08._UPC], AE_ALREADY_EXISTS (20210930/dswload2-326) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) févr. 26 18:58:37 asus kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS07._PLD], AE_ALREADY_EXISTS (20210930/dswload2-326) févr. 26 18:58:37 asus kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210930/psobject-220) lines 1-53 I've tried many different things, with no sucess so far. Maybe I can already tell you that : - firmware-misc-nonfree is installed. This is the hardware I have related to networking : Code: Select all03:00.0 Network controller: MEDIATEK Corp. Device 7961 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Here is what /etc/network/interfaces looks like : Code: Select all# 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 iwconfig gives me this Code: Select alllo no wireless extension enp4s0 no wireless extension wlan0 IEEE 802.11 ESSID:"SFR-86e8" Mode: Managed Frequency: 5.18 GHz Access Point : 24:7F:20:98:86:EF Bit rate=585 Mb/s Tx-Power= 3dbm Retry short limit: 7 RTS thr: off Fragment thr: off Encryption key: off Power Management: on Link Quality= 52/70 Signal level= 58dBm Rx invalid nwid:0 Rx invalid crypt: 0 Rx invalid frag:0 Tx excessiv retries: 6 Invalid misc: 0 Missed beacon: 0 Anyone has any ideas on how to solve the network & booting problems (I have a feeling they might be related) ? Thanks | It is reported that the driver for this card is included in kernels 5.12+ and the firmware is in firmware-misc-nonfree. Install the current kernel linux-image-5.15.0-0.bpo.2-amd64 from backports. |
Hi everyone, I recently opened a thread about my wifi connection being unstable/really slow/not working. For various reasons, I have decided to try to connect to the wifi through a wifi USB adapter instead. I bought ASUS USB-N13 | Wireless-N300 adapter after checking it's compatible with Linux. I encountered errors during the driver's installation. Here's a copy of the steps I followed to try to install the linux driver for this USB wireless adapter : Code: Select allroot@asus:/home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01# chmod +x install.sh root@asus:/home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01# sh install.sh ################################################## Realtek Wi-Fi driver Auto installation script Novembor, 21 2011 v1.1.0 ################################################## Decompress the driver source tar ball: rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01.tar.gz rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/ rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/core/ rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/core/mesh/ rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/core/mesh/rtw_mesh_pathtbl.c [... I'm suppressing lines here because it seems to me they're just about the decompression going ok and it's 20 pages long] rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/os_dep/osdep_service.c rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01 Authentication requested [root] for make clean: install.sh: 38: [: unexpected operator #make -C /lib/modules/5.10.0-10-amd64/build M=/home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01 clean cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd core ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~ rm -fr .tmp_versions Authentication requested [root] for make driver: install.sh: 48: [: unexpected operator make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.10.0-10-amd64/build M=/home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01 modules make[1] : on entre dans le répertoire « /usr/src/linux-headers-5.10.0-10-amd64 » CC [M] /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/core/rtw_cmd.o In file included from /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/include/drv_types.h:75, from /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/core/rtw_cmd.c:17: /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/include/rtw_security.h:252:8: error: redefinition of ‘struct sha256_state’ 252 | struct sha256_state { | ^~~~~~~~~~~~ In file included from /usr/src/linux-headers-5.10.0-10-common/include/linux/filter.h:24, from /usr/src/linux-headers-5.10.0-10-common/include/net/sock.h:59, from /usr/src/linux-headers-5.10.0-10-common/include/linux/tcp.h:19, from /usr/src/linux-headers-5.10.0-10-common/include/linux/ipv6.h:87, from /usr/src/linux-headers-5.10.0-10-common/include/net/addrconf.h:50, from /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/include/osdep_service_linux.h:49, from /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/include/osdep_service.h:53, from /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/include/drv_types.h:27, from /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/core/rtw_cmd.c:17: /usr/src/linux-headers-5.10.0-10-common/include/crypto/sha.h:84:8: note: originally defined here 84 | struct sha256_state { | ^~~~~~~~~~~~ make[3]: *** [/usr/src/linux-headers-5.10.0-10-common/scripts/Makefile.build:285 : /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01/core/rtw_cmd.o] Erreur 1 make[2]: *** [/usr/src/linux-headers-5.10.0-10-common/Makefile:1846 : /home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01/driver/rtl8192FU_rtl8725AU_WiFi_linux_v5.8.6_33905.20190604_COEX20190509-0d01] Erreur 2 make[1]: *** [/usr/src/linux-headers-5.10.0-10-common/Makefile:185 : __sub-make] Erreur 2 make[1] : on quitte le répertoire « /usr/src/linux-headers-5.10.0-10-amd64 » make: *** [Makefile:2327 : modules] Erreur 2 ################################################## Compile make driver error: 2 Please check error Mesg ################################################## root@asus:/home/gekko/Documents/ASUS_USB-N13_C1_20191031/Linux/RTL8192FU_RTL8725AU_linux_v5.8.6_33905.20190604_COEX20190509-0d01# I did Code: Select alllsusb which shows the kernel sees the usb wireless adapter : Code: Select alllsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 005: ID 0b05:18f1 ASUSTek Computer, Inc. 802.11n WLAN Adapter Bus 001 Device 004: ID 8564:1000 Transcend Information, Inc. JetFlash Bus 001 Device 003: ID 13d3:3563 IMC Networks Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Heres the result of Code: Select allip a : Code: Select allip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 04:42:1a:a0:e5:a1 brd ff:ff:ff:ff:ff:ff Is someone able to help me ? Thank you | First the "teach how to fish" bit: First get the device ID from the lsusb command and search - "Debian 0b05:18f1". Peruse results for one that is solved. Now because I am feeling generous, the "feed the fish" bit: Go to https://github.com/kelebek333/rtl8192fu-dkms and follow the "How to install". Do not follow the PPA method! This is from a search result at https://forums.linuxmint.com/viewtopic.php?t=362842 but that thread contains several failed attempts as well. You will likely also need to install firmware-realtek from the non-free section of Debian repo. Drivers supplied by vendors are often never updated from when the device is released so regularly fail to work with more recent kernels. In this case I see that driver installation script is 11 years old! |
I have successfully installed Debian on my Acer laptop. Everything is working fine, except Bluetooth. I think that Intel Wi-Fi 6 AX200 is responsible for Wi-Fi and Bluetooth. I cannot connect to my phone ( Honor 20 lite ), it cannot be found by my laptop. The output of the "sudo journalctl -b -r -p err" is: Code: Select all-- Journal begins at Tue 2021-12-07 16:39:07 CET, ends at Fri 2022-03-25 19:17:01 CET. -- мар 25 18:37:31 laptop kernel: Bluetooth: hci0: link tx timeout мар 25 14:36:28 laptop bluetoothd[689]: sap-server: Operation not permitted (1) мар 25 14:36:28 laptop bluetoothd[689]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. мар 24 19:02:37 laptop bluetoothd[689]: sap-server: Operation not permitted (1) мар 24 19:02:37 laptop bluetoothd[689]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. мар 23 19:25:34 laptop pipewire[1124]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name мар 23 19:25:27 laptop pipewire[761]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name мар 23 19:25:26 laptop bluetoothd[689]: sap-server: Operation not permitted (1) мар 23 19:25:26 laptop bluetoothd[689]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. мар 23 19:25:25 laptop kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware мар 23 19:25:25 laptop kernel: iwlwifi 0000:08:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) мар 23 19:25:25 laptop kernel: integrity: Problem loading X.509 certificate -65 мар 23 19:25:25 laptop kernel: integrity: Problem loading X.509 certificate -65 On this forum I have found that the message about the firmware is harmless. About other messages I cannot find relevant information about Debian. Can somebody help me. If you need some other information about my configuration please feel free to ask. | In addition from previous information I have found this link https://bugs.debian.org/cgi-bin/bugrepo ... =803265#45 The sap server is not a problem in this case. Maybe the problem is pipewire. |
Hi, I have an issue with the network manager telling me there is no internet. When I hover over its icon on the taskbar it shows "No connection" but I'm online. Screenshot from 2022-03-25 04-49-13.png (4.15 KiB) Viewed 1551 times Another bug I discovered is that when I turn off a VPN, I can't get back online and have to restart. Plus, the Maps app doesn't work, says it's offline and I suspect it's because of the buggy network manager. I tried to reinstall the network manager to fix that but that didn't work Code: Select allliam@debian:~$ screenfetch _,met$$$$$gg. liam@debian ,g$$$$$$$$$$$$$$$P. OS: Debian 11 bullseye ,g$$P"" """Y$$.". Kernel: x86_64 Linux 5.10.0-12-amd64 ,$$P' `$$$. Uptime: 37m ',$$P ,ggs. `$$b: Packages: 2175 `d$$' ,$P"' . $$$ Shell: bash 5.1.4 $$P d$' , $$P Resolution: 1800x1012 $$: $$. - ,d$$' DE: Cinnamon 4.8.6 $$\; Y$b._ _,d$P' WM: Muffin Y$$. `.`"Y$$$$P"' WM Theme: Menta (GreenLaguna) `$$b "-.__ GTK Theme: Adapta-Nokto [GTK2/3] `Y$$ Icon Theme: ePapirus `Y$$. Font: Sans 9 `$$b. Disk: 67G / 346G (20%) `Y$$b. CPU: Intel Atom x5-Z8350 @ 4x 1.92GHz `"Y$b._ GPU: Mesa DRI Intel(R) HD Graphics (CHV) `"""" RAM: 2842MiB / 3860MiB | Try adding to /etc/NetworkManager/NetworkManager.conf: Code: Select allmanaged=true And then restart Network Manager. |
SOLVED: Turns out it was because I was using BTRFS in my drive, using ext4 it works just fine. I have dual boot debian and windows 11, just for gaming, on a laptop. My laptop is usually closed and I use an external monitor, and I used to change from debian to windows using Code: Select allsudo grub-reboot 2 && sudo reboot, and then back to debian from windows simply restarting, but now it always uses windows by default, the third option. ¿How can I make it pick the first option always? I've tried edited /etc/default/grub, and then run Code: Select allupdate-grub, but it appears to do nothing and still go to the third option. My /etc/default/grub file is this: # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT="0" GRUB_TIMEOUT="2" GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`" GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="" # If your computer has multiple operating systems installed, then you # probably want to run os-prober. However, if your computer is a host # for guest OSes installed via LVM or raw disk devices, running # os-prober can cause damage to those guest OSes as it mounts # filesystems to look for things. GRUB_DISABLE_OS_PROBER="false" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal #GRUB_TERMINAL="console" # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE="640x480" # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID="true" # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" GRUB_SAVEDEFAULT="false" export GRUB_COLOR_NORMAL="black/black" export GRUB_COLOR_HIGHLIGHT="magenta/black" | Did you try to disable "fast boot", either from BIOS or Windows? |
I setup a new non root partition with Luks and clevis with unlocking configured to a Tang server. I can successfully decrypt the volume from the Tang server via clevis luks unlock -d /dev/sdX . So the encryption and Tang server is working fine. I have installed clevis-systemd and also enabled clevis-luks-askpass.path. But the system never asks for a password at boot and hence does not trigger clevis-luks. I verified that the /etc/crypttab is correct as below bdrive UUID="d0adb4eb-8179-419d-825a-8e1260ba3917" none _netdev For some reason systemd does not seem to fall into to the ask password prompt. I had faced this issue sometime ago and I think I had to enable / install an additional systemd service. (which I accidently stumbled upon during a google search). But now I am unable to figure this out. Can someone help on this please. | Maybe this one: Code: Select allPackage: clevis-initramfs Source: clevis Version: 19-2 Installed-Size: 33 kB Maintainer: Christoph Biedl <debian.axhn@manchmal.in-ulm.de> Architecture: amd64 Depends ▼ clevis-luks (=19-2), initramfs-tools Description-en: Clevis initramfs integration Clevis is a plugable framework for automated decryption. This package provides integration for initramfs-tools to automatically unlock LUKS encrypted block devices in early boot. Homepage: https://github.com/latchset/clevis Section: net Priority: optional Filename: pool/main/c/clevis/clevis-initramfs_19-2_amd64.deb Size: 7.3 kB ? |
Starting today, when I try to start Steam for Linux, it gives me the following dialog: Is this safe to enable? | On my xubuntu-22.04 /proc/sys/kernel/unprivileged_userns_clone=1, /proc/sys/user/max_user_namespaces=63222. I don't know how much requires Steam, but I think you can increase this value. |
Installed Debian 12, newest release. I had experience with Debian before and knew I needed to install nfs-common in order to mount my networkshares. Unfortunatley nfs-common no longer available thru Synaptic? So I downloaded the package from the Debian server but it does not install due to other missing packages that are not available. Installation of the other packages also a problem because of dependencies. Is there another nfs package that I can install or another solution? I preferably do not want to use samba or cifs. | Hello, audiolover wrote: 2023-12-04 16:23 that is it, version 4 of nfs was not activated on mij nas. problem solved, thank you very much! 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] Cannot mount NFS share Happy Debian ! :) |
Hi all, According to the German CERT-Bund Reports, DNS Open-resolvers can be abused for DDoS reflection attacks against third parties. They describe a simple test to discover if a server has this issue. One can execute the following command (replacing the IP with the server IP which we want to test) Code: Select all$ dig cert-bund.de @192.168.45.67 An open resolver allowing recursive queries will return a response with status NOERROR, whereas an open resolver not allowing recursive queries will return a response with status REFUSED. One of my servers, which uses Debian 12.5, has a DNS open resolver. However, I don't know how to avoid the open resolver. Some instructions say I should modify the BIND configuration. However, it seems BIND is not installed on the server: Code: Select all$ aptitude show bind9 Package: bind9 Version: 1:9.18.24-1 State: not installed ... How can I disallow recursive queries? How can I disallow the open resolver? I think I don't need it. | Hello, 818erm9x1 wrote: 2024-03-19 06:24 Thank you again! Your last answer was very useful. With netstat, I noticed that the DNS server was dnsmasq. Then, I added `no-resolv` to the configuration as described on https://serverfault.com/a/847856. This also solves the issue. 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); i.e. : [Solved] How to disallow DNS servers responding to recursive queries? Happy Debian ! |
I've dist-upgraded from Buster to Bullseye and setting up cups-pdf. I've changed to output directory from the default, however, I am not able to change the output file name to my preferred format of having the job_number preceding the file name. Even with the default line commented out, it will name the output file with a with a tailing "-job_#" (Label 2). What I'm wanting to switch to is option 1, preceding "job_#-". So I'm assuming that there's another config file that needs to be updated as well, but I haven't found it. Any ideas? the relevant part of /etc/cups/cups-pdf.conf Code: Select all### Key: Label (config, ppd, lpoptions) ## label all jobs with a unique job-id in order to avoid overwriting old ## files in case new ones with identical names are created; always true for ## untitled documents ## 0: label untitled documents only ## 1: label all documents with a preceeding "job_#-" ## 2: label all documents with a tailing "-job_#" ### Default: 0 Label 1 | Bu opening LocalHost in Firefox and changing the default options for Label outputfiles to "Prefix all documents with job-id", the output filename changed to the format I was wanting. From the CLI and cd'ing into /etc/cups, I looked at the time stamps of files and directories to see what changed, /etc/cups/ppd/PDF.ppd is modified to reflect the changes. Why doesn't editing the label options in /etc/cups/cups-pdf.conf have the desired effect for the output filenames? |
Hello, i have an EFI server with a small /boot partition (~230MB - ext2), which is always nearly full, and a /boot/efi partition (~512MB - vfat) which is nearly empty. After the /boot partition was full today, after running an upgrade, i asked myself if it wouldn't be a good idea to install the kernel and initrd images into /boot/efi instead of /boot. But even after searching the internet and reading several manpages (kernel-install, installkernel, ...) i don't know for how to achive this. Even looking at the preinst and postinst scripts of the linux-image-amd64 package doesn't help me to fix this. I thought i was asked where to install the kernel images while installing debian to another system a while ago, so i'm pretty sure that it is possible, but i need help to know how. So if anybody knows, please let me know. Kind regards, Timo | teissler wrote: 2022-01-23 16:04 i asked myself if it wouldn't be a good idea to install the kernel and initrd images into /boot/efi instead of /boot. IMO mounting the EFI partition on /boot is not a good idea. 1) GRUB expects the EFI partition to be mounted on /boot/efi, not /boot. Other boot loaders (systemd-boot) may have different expectations. 2) IIUC, the Debian package management expects /boot to be in a POSIX filesystem (need to create hard links...), which FAT used for the EFI partition is not. You could set MODULES=dep in /etc/initramfs-tools/initramfs.conf to reduce the size of the initramfs. Caveat: the generated initramfs may not boot on a different hardware. Or you could reduce the EFI partition and extend the /boot partition, or swap the two partitions. teissler wrote: 2022-01-23 16:04 I thought i was asked where to install the kernel images while installing debian to another system a while ago, I do not remember ever seeing this. Wasn't it rather where to install the boot loader ? |
It appears that the current 5.10 kernel has issues with NTFS file system: - some errors are displayed in the logs (see below) - the speed is about half compared with the same external HDD operating under Windows. Less than an issue, but this shows that there is room for improvements. - higher CPU usage (about 15 - 20%) compared to Windows. Most likely is related with the point above. First snippet: kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 37 7c f0 00 00 00 10 00 00 kernel: blk_update_request: I/O error, dev sdd, sector 1949793520 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 38 ca 00 00 00 00 f0 00 00 kernel: blk_update_request: I/O error, dev sdd, sector 1949878784 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0 kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 3d c2 00 00 00 00 f0 00 00 kernel: blk_update_request: I/O error, dev sdd, sector 1950204416 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0 kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=32s kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 45 39 00 00 00 00 f0 00 00 kernel: blk_update_request: I/O error, dev sdd, sector 1950693632 op 0x0:(READ) flags 0x84700 phys_seg 18 prio class 0 kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 49 eb 00 00 00 00 f0 00 00 kernel: blk_update_request: I/O error, dev sdd, sector 1951001344 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0 In this case the disk activity simply "froze" for 30 seconds, then resumes and the cycle repeats. Second snippet: kernel: blk_update_request: I/O error, dev sdc, sector 1672718464 op 0x0:(READ) flags 0x80700 phys_seg 9 prio class 0 kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b3 c0 80 00 01 00 00 kernel: blk_update_request: I/O error, dev sdc, sector 1672724608 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 41 80 00 01 00 00 kernel: blk_update_request: I/O error, dev sdc, sector 1672757632 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 4f 80 00 01 00 00 kernel: blk_update_request: I/O error, dev sdc, sector 1672761216 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 0 kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 b2 80 00 01 00 00 kernel: blk_update_request: I/O error, dev sdc, sector 1672786560 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 0 kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 e6 80 00 01 00 00 kernel: blk_update_request: I/O error, dev sdc, sector 1672799872 op 0x0:(READ) flags 0x80700 phys_seg 28 prio class 0 kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b5 20 80 00 01 00 00 kernel: blk_update_request: I/O error, dev sdc, sector 1672814720 op 0x0:(READ) flags 0x80700 phys_seg 9 prio class 0 kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b5 75 80 00 01 00 00 kernel: blk_update_request: I/O error, dev sdc, sector 1672836480 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 Here there is a movie playing and the play stops or video/sound loose sync. Using USB 2 or USB 3 ports doesn't change anything. The problem is that there is no issue with the hard drive, I did a (surface) check on Windows and everything was ok. Under Windows everything works as expected, no error is displayed in the logs. None of the drives show symptoms of a dying drive like vibrations, chirping sounds while operating. If I remember correctly, I read that in kernel 5.12 there is a new NTFS driver. Any observations, suggestions, tips will be highly appreciated. | This seems to be a USB or drive issue. FWIW, the old limited NTFS driver (ntfs) is disabled in Debian kernels and NTFS is handled in userspace with ntfs-3g. The new NTFS driver (ntfs3) was introduced in kernel 5.15, not 5.12. |
Hello everyone! My name is Jo, this is my first time here and I'm very new to Linux. I'll try my best. Please help me out a bit. There's no sound. My computer which is freshly installed Debian 11 from (debian-11.2.0-amd64-netinst.iso) just keep showing "Dummy Output" for the sound. In fact, this dummy output is very glitchy too. 9 out of 10 restarts the Sound Output Device will be "Dummy Output", then somehow 1 out of 10 times it will be okay. By 'okay', I mean the Output Device will be "HDMI" (and there is a sound output normally through my monitor's built-in speaker) for like 15 seconds, then if I try to adjust by pressing volume up or volume down on my keyboard a little, the Output Device will turn into "LINE OUT" then finally "Dummy Output". And I'm back to no sound again. I tried researching a bit about the abstract layers of sound in Linux and still have completely no idea what in the world am I facing at. Please help. Any advice or comments are highly appreciated. Thank you. Things I've tried and found no change (Sorry I'm so noob that I don't know what in the world I'm doing at all) - I tried following a thread somewhere that said "sudo alsa force-reload" but the terminal says: sudo: alsa: command not found - Confirmed that my monitor/HDMI cable is not the problem - Before installing Debian 11, I previously used Linux Mint (Kernel: 5.4.0-96-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal ) and I also encountered the same issue too. - tried reinstalling Debian twice - appending these two lines to /etc/modprobe.d/alsa-base.conf.dpkg-new #options snd-usb-audio index=-2 options snd_hda_intel model=auto index=-0 I posted some info from my machine that I think is relevant at this link: https://pastebin.com/SmYKSveU | Your system has a Comet Lake processor so is quite recent. You probably need firmware. I think your audio needs firmware-sof-signed and alsa-ucm-conf. https://wiki.archlinux.org/title/Advanc ... A_firmware Looking at your dmesg shows other missing firmware - firmware-linux-nonfree, firmware-realtek, and intel-microcode should cover it. |
Hello. I have created a VM using only qemu but I'm not sure the resulting .img file can be used with virtio or if I have to create this .img file already with vritio. Or is it possible to create the VM in any way and then, use it with virtio at the start command, using some parameter? The issue is that I created this VM and when I try to compile a program with the usual ./configure && sudo make && make install, it takes ages to do so. Mainly the sudo make command. I created this VM with: Code: Select allqemu-img create -f qcow2 bullseyebtc.img 25G qemu-system-x86_64 -machine accel=kvm:tcg -m 4096 -hda debian-11.1.0-amd64.img -boot d -cdrom ../LinuxIMGsPool/debian-11.1.0-amd64-netinst.iso and I start it with: Code: Select allqemu-system-x86_64 -m 8192 -hda bullseyebtc.img Do I need to create the VM from start wit virtio or is it something I can use with the command that starts the VM? | I think I got it. This is the command I'musing now to start my VM: Code: Select allqemu-system-x86_64 -cpu host -enable-kvm -smp 4 -m 8192 -drive file=bullseye.img,if=virtio Solved |
Ever since upgrading to kernel 5.10.0-10 (it's been a while), I have been getting status messages during boot where I used to only get [ OK ] messages. I won't post the whole log because of the length, but heres an excerpt. Code: Select allBegin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.36.1 [/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1 /dev/sda1: clean, 773924/19013632 files, 44088507/76054528 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Debian GNU/Linux 11 (bullseye)! [ OK ] Created slice system-getty.slice. [ OK ] Created slice system-modprobe.slice. [ OK ] Created slice User and Session Slice. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Set up automount Arbitrary Executable File Formats File System Automount Point. [ OK ] Reached target Remote File Systems. [ OK ] Reached target Slices. [ OK ] Listening on Syslog Socket. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. Mounting Huge Pages File System... Mounting POSIX Message Queue File System... Mounting Kernel Debug File System... Mounting Kernel Trace File System... Starting Set the console keyboard layout... Starting Create list of static device nodes for the current kernel... Starting Load Kernel Module configfs... Starting Load Kernel Module drm... Starting Load Kernel Module fuse... Starting Journal Service... Starting Load Kernel Modules... Starting Remount Root and Kernel File Systems... Starting Coldplug All udev Devices... [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Kernel Debug File System. [ OK ] Mounted Kernel Trace File System. [ OK ] Finished Create list of static device nodes for the current kernel. [ OK ] Finished Load Kernel Module configfs. Mounting Kernel Configuration File System... [ OK ] Mounted Kernel Configuration File System. [ OK ] Started Journal Service. [ OK ] Finished Load Kernel Module fuse. Mounting FUSE Control File System... [ OK ] Mounted FUSE Control File System. [ OK ] Finished Remount Root and Kernel File Systems. Starting Flush Journal to Persistent Storage... Starting Load/Save Random Seed... Starting Create System Users... [ OK ] Finished Load Kernel Module drm. [ OK ] Finished Coldplug All udev Devices. Starting Helper to synchronize boot up for ifupdown... [ OK ] Finished Set the console keyboard layout. [ OK ] Finished Helper to synchronize boot up for ifupdown. [ OK ] Finished Load/Save Random Seed. [ OK ] Finished Create System Users. Starting Create Static Device Nodes in /dev... [ OK ] Finished Create Static Device Nodes in /dev. [ OK ] Reached target Local File Systems (Pre). Starting Rule-based Manager for Device Events and Files... [ OK ] Finished Load Kernel Modules. Starting Apply Kernel Variables... [ OK ] Finished Apply Kernel Variables. [* ] (1 of 5) A start job is running for Flush Journal to Persistent Storage[** ] (1 of 5) A start job is running for Flush Journal to Persistent Storage[ OK ] Started Rule-based Manager for Device Events and Files. Starting Show Plymouth Boot Screen... [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Forward Password Requests to Plymouth Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Reached target Paths. [ OK ] Found device Samsung SSD 970 EVO 500GB NVME_SSD. Mounting /media/sdebian/NVME-SSD... [ OK ] Mounted /media/sdebian/NVME-SSD. [ OK ] Found device WDC_WD5000AACS-00G8B1 Media. Mounting /media/sdebian/Media... [ OK ] Mounted /media/sdebian/Media. [ OK ] Reached target Local File Systems. Starting Load AppArmor profiles... Starting Enable support for additional executable binary formats... Starting Set console font and keymap... Starting Tell Plymouth To Write Out Runtime Data... [ OK ] Finished Tell Plymouth To Write Out Runtime Data. [ OK ] Finished Set console font and keymap. Mounting Arbitrary Executable File Formats File System... [ OK ] Mounted Arbitrary Executable File Formats File System. [ OK ] Found device ST3320310CS 5. Activating swap /dev/disk/by-uuid/ecf22972-da89-40fe-a90b-4af7eff79b75... [ OK ] Activated swap /dev/disk/by-uuid/ecf22972-da89-40fe-a90b-4af7eff79b75. [ OK ] Reached target Swap. [ OK ] Finished Enable support for additional executable binary formats. [*** ] (1 of 2) A start job is running for Flush Journal to Persistent Storage[ *** ] (2 of 2) A start job is running for Load AppArmor profiles (17s / no li[ *** ] (2 of 2) A start job is running for Load AppArmor profiles (17s / no li[ ***] (2 of 2) A start job is running for Load AppArmor profiles (18s / no li[ OK ] Finished Load AppArmor profiles. I'm not sure how many of the messages that don't start with [ OK ] are new, but I know the "Debian GNU/Linux 11 (bullseye)" is new. The last time I saw that, I was booting into recovery mode. I couldn't swear to it, but bootup also feels like it's taking longer. | If you have the older and the newer kernels that you can boot with, you could boot each up and run: systemd-analyze blame, for each and compare the timings |
Hi, I'm having problems with "apt source". After having enabled deb-src in my sources.list and run "apt update", apt fails to download any source packages : Code: Select all$ apt source hello Reading package lists... Done E: Unable to find a source package for hello An intensive internet search hasn't provided any clue (just "check your sources.list for deb-src and don't forget to update apt"). What am I missing here ? Code: Select all// apt.conf Acquire::Languages { "environment"; "fr_FR"; "fr"; "en"; }; APT::Default-Release "/^bullseye(|-security|-updates)$/"; APT::Cache-Limit "90000000"; Code: Select all// preferences Package: * Pin: origin "" Pin-Priority: 990 Package: * Pin: origin "deb.nodesource.com" Pin-Priority: 990 Package: npm Pin: release o=Debian Pin-Priority: -1 Package: nodejs* Pin: release o=Debian Pin-Priority: -1 Package: libnode-dev Pin: release o=Debian Pin-Priority: -1 Package: libnode64 Pin: release o=Debian Pin-Priority: -1 Package: node-* Pin: release o=Debian Pin-Priority: -1 Package: * Pin: release o=Debian,n=bullseye-security Pin-Priority: 990 Package: * Pin: release a=bullseye Pin-Priority: 989 Package: * Pin: release o=Debian,n=testing-security Pin-Priority: 99 Package: * Pin: release a=testing Pin-Priority: 80 Code: Select all// sources.list deb http://debian.proxad.net/debian/ bullseye main contrib non-free deb-src http://debian.proxad.net/debian/ bullseye main contrib non-free deb http://deb.debian.org/debian bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free deb http://deb.torproject.org/torproject.org bullseye main deb-src http://deb.torproject.org/torproject.org bullseye main deb http://deb.debian.org/debian bullseye-backports main contrib non-free deb-src http://deb.debian.org/debian bullseye-backports main contrib non-free | Good you worked it out. I never used sources and I assume a majority of other users haven't either so didn't know how. It is preferable to post the contents of text config files here in CODE tags rather than hiding in a tarball. A lot more people would have looked at them if you did. Remove deb-multimedia from your sources. Leaving that repo open has caused many issues. |
Hello, Sorry, I speak a little English. My /etc/apache2/sites-available/example.com.conf file: Code: Select all<VirtualHost *:80> ServerName example.com ServerAlias www.example.com DocumentRoot /var/www/example.com/public_html/ AddDefaultCharset UTF-8 AddCharset ISO-8859-2 .iso8859-2 .latin2 .cen AddType application/x-httpd-php .php ErrorLog /var/www/example.com/error_log CustomLog /var/www/example.com/access_log combined HostnameLookups Off UseCanonicalName Off ServerSignature Off IndexIgnore * ErrorDocument 500 "Error 500" ErrorDocument 403 "Error 403" <Directory "/var/www/example.com/public_html/"> Options FollowSymLinks MultiViews AllowOverride All Require all granted </Directory> </VirtualHost> It works with: Code: Select allcd /etc/apache2/sites-available a2ensite example.com.conf My /etc/hosts file: Code: Select allHID.DEN.IP.ADD example.com It works, but only http:// protocol. I would like use https:// protocol. Maybe Let's Encrypt SSL or another free and easy way. Please help me. Thanks! | Either a self-signed certificate, which is fine for testing purposes, or a Letsencrypt certificate, which is obviously necessary "for production." To get Letsencrypt just do: Code: Select all# apt install certbot To check for errors you can simulate getting a LE certificate by adding --dry-run like this: Code: Select all# certbot certonly --webroot --webroot-path /var/www/example.com -d example.com --dry-run And remove --dry-run when you want to get the certificate: Code: Select all# certbot certonly --webroot --webroot-path /var/www/public_html/example.com -d example.com |
Hi, poweroff, blkdiscard, openvpn and lot of others command aren't available anymore from root terminal (unless I type /usr/sbin/xxxx instead of xxxx). /etc/profile and /etc/login.defs are exact same as normal (compared to a not dist-upgraded Debian 9 on which root PATH is correct). Code: Select all# /etc/profile: system-wide .profile file for the Bourne shell (sh(1)) # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...). if [ "`id -u`" -eq 0 ]; then PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" else PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games" fi export PATH [...] Code: Select all[...] # *REQUIRED* The default PATH settings, for superuser and normal users. # # (they are minimal, add the rest in the shell startup files) ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games[...] But when I do any change inside of it (user or root path) nothing changes (even after a reboot - for root and non root users, this has absolutely no effect). I guess there is tons of useless copies of the same settings that aren't used anymore but I failed to find the good one. /etc/environnement is empty but it is, again, same as normal (on Debian 9 it's empty too and PATH works fine for users and root). Files inside /root/ directory are the exact same as normal. Do you have any idea of where the change has been made/forgotten by apt dist-upgrade ? EDIT : from Ctrl+Alt+F1 terminal (leaving Xorg to the non graphic command line mode) the path are correct and /etc/profiles values are used. Into graphical mode, user and root terminal (and user terminal using su root) PATH values aren't updated by the content of /etc/profiles or /etc/login.defs and root always has standard user path. | Try Code: Select allsu - The `su` command now comes from the util-linux package, hence the new behaviour. There is a note to this effect somewhere on the wiki but I can't find it right now. EDIT: here it is: https://wiki.debian.org/NewInBuster ^ In the "Changes" section. |
1. I am using Debian 11 Bullseye. 2. I am using 3g mobile USB cable modem(ethernet - not wireless). My system uses connman for networking as default. Connman cause some trouble and I want to disable it and use an alternative program to connect internet. My questions : 1. Which programs are the best alternatives for connman? 2. Can I install it using synaptic package manager? 3. After installation, simply disabling connman service and enabling new program's service solves my problem(i.e connect to internet)? | If that modem device gives a dhcp server on it's eth port you connected to, then you don't need any program. Set /etc/network/interfaces.d/eth.conf. Remove connman. |
I am using Debian 11 Bullseye. Sometimes strangely, connmand fails and starts using more than 90% of my CPU. Although I restart its service by using : sudo service connman restart it does not work anymore until I unplug and replug the USB modem cable? How can I restore connmand service when it fails? | Check output of Code: Select all# journalctl -u connman for errors. |
Hello, I have a problem on one of my server when I try to update or install new package using apt. Off course, I already check my resolv.conf configuration and I can ping deb.debian.org and other domains without any problem. Curl is also working. Do you have any idea of a solution to fix that ? When I use "apt update", I have this error : Code: Select allIgn :1 https://deb.debian.org/debian bookworm InRelease Ign :2 https://security.debian.org/debian-security bookworm-security InRelease Ign :3 https://deb.debian.org/debian bookworm-updates InRelease Ign :2 https://security.debian.org/debian-security bookworm-security InRelease Ign :1 https://deb.debian.org/debian bookworm InRelease Ign :3 https://deb.debian.org/debian bookworm-updates InRelease Ign :2 https://security.debian.org/debian-security bookworm-security InRelease Ign :1 https://deb.debian.org/debian bookworm InRelease Ign :3 https://deb.debian.org/debian bookworm-updates InRelease Err :2 https://security.debian.org/debian-security bookworm-security InRelease Temporary "security.debian.org" resolution error " Err :1 https://deb.debian.org/debian bookworm InRelease Temporary « deb.debian.org resolution error » Err :3 https://deb.debian.org/debian bookworm-updates InRelease Temporary "deb.debian.org" resolution error Reading package lists... Done Build dependency tree... Done Read status information... Done All packages are up to date. W: Unable to retrieve https://deb.debian.org/debian/dists/bookworm/InRelease Temporary error resolving "deb.debian.org". W: Unable to recover https://deb.debian.org/debian/dists/bookworm-updates/InRelease Temporary "deb.debian.org" resolution error. W: Unable to recover https://security.debian.org/debian-security/dists/bookworm-security/InRelease Temporary "security.debian.org" resolution error W: Download of some index files failed, they were ignored, or old ones were used instead. My sources.list configuration : Code: Select alldeb https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware deb https://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware deb https://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware Thanks you very much ! | I had this happen to me on one of three Sid machines last week when I was running routine updates. I'm running Google's DNS at the router; I rebooted the broken machine and the router and everything came back up. |
pc1: Debian 12 Bookworm KDE X pc2: Debian 12 Bookworm KDE Wayland The output of the command evtest (owner root) is different on both pc's pc1: Code: Select allevtest No device specified, trying to scan all of /dev/input/event* Not running as root, no devices may be available. Available devices: /dev/input/event0: AT Translated Set 2 keyboard /dev/input/event1: Power Button /dev/input/event10: HUION 256C PEN STYLUS /dev/input/event11: RFID Reader RFID Reader /dev/input/event12: RFID Reader RFID Reader Keyboard /dev/input/event14: HDA ATI HDMI HDMI/DP,pcm=3 /dev/input/event15: HDA ATI HDMI HDMI/DP,pcm=7 /dev/input/event16: HDA ATI HDMI HDMI/DP,pcm=8 /dev/input/event17: HDA ATI HDMI HDMI/DP,pcm=9 /dev/input/event18: HDA ATI HDMI HDMI/DP,pcm=10 /dev/input/event19: HDA ATI HDMI HDMI/DP,pcm=11 /dev/input/event2: Power Button /dev/input/event20: HDA Digital PCBeep /dev/input/event21: HDA Intel PCH Front Mic /dev/input/event22: HDA Intel PCH Rear Mic /dev/input/event23: HDA Intel PCH Line /dev/input/event24: HDA Intel PCH Line Out /dev/input/event25: HDA Intel PCH Front Headphone /dev/input/event26: Huion Tablet /dev/input/event27: Huion Tablet /dev/input/event29: Huion keyboard /dev/input/event3: YICHIP Wireless Device /dev/input/event30: Huion mouse /dev/input/event4: YICHIP Wireless Device Mouse /dev/input/event5: YICHIP Wireless Device System Control /dev/input/event6: PC Speaker /dev/input/event7: YICHIP Wireless Device Consumer Control /dev/input/event8: HUION Huion Tablet_H640P Keyboard /dev/input/event9: Logitech USB Trackball Select the device event number [0-30]: pc2: Code: Select allevtest No device specified, trying to scan all of /dev/input/event* Not running as root, no devices may be available. Available devices: Select the device event number [0-30]: On pc1 the devices are shown and I can execute the command without root On pc2 the devices are not shown and I cannot execute the command without root groupinf0: pc1: Code: Select allgroups peer disk cdrom floppy sudo audio dip video plugdev input kvm netdev bluetooth lpadmin scanner libvirt libvirt-qemu pc2: Code: Select allgroups peer cdrom floppy sudo audio dip video plugdev users netdev bluetooth lpadmin scanner After this I added the group 'input' on pc2 and now the command evtest works also without on pc2. My question: When I look at the properties of the file evtest I see that the owner is 'root' and the group is 'root'. But members of the group 'input' also can execute the command without sudo. I discovered this by trial and error. How can I find which groups are able to execute the command (evtest) without sudo???? | Hello, peer wrote: 2024-04-23 07:36 When I look at the properties of the file evtest I see that the owner is 'root' and the group is 'root'. I assume you mean the executable /usr/bin/evtest The permissions of this file should be rwxr-xr-x (755) which means executable by anyone. peer wrote: 2024-04-23 07:36 But members of the group 'input' also can execute the command without sudo. I discovered this by trial and error. How can I find which groups are able to execute the command (evtest) without sudo???? According to evtest's manual man 1 evtest wrote:The output of evtest shows the information presented by the kernel namely in /dev/input/ and man 1 evtest wrote:evtest needs to be able to read from the device; in most cases this means it must be run as root. However, files in /dev/input/ belong to root/input with permissions 660, e.g. Code: Select all$> ls -l /dev/input/event1 crw-rw---- 1 root input 13, 65 Apr 23 12:11 /dev/input/event1 and are therefore readable (and writable) by user root or group input. If your user is in the input group, evtest is “able to read from the device”. Code: Select all$> find /dev/ -group "input" will show you all these files. May also be relevant: man 1 evtest wrote:If evtest does not show any events even though the device is being used, the device may be grabbed by a process (EVIOCGRAB). This is usually the case when debugging a synaptics device from within X. VT switching to a TTY or shutting down the X server terminates this grab and synaptics devices can be debugged. The following command shows the processes with an open file descriptor on the device: fuser -v /dev/input/eventX |
I installed SLI-only Debian 12, and installed NTP on it in this way: https://timetoolsltd.com/ntp/how-to-ins ... -on-linux/ I added my Windows domain controller IP address in the ntp.conf file and commended out the Debian pools, because this server isn't supposed to have internet access. When I ran ntpq -p, I got: remote refid st t when poll reach delay offset jitter ======================================================================================= +xxx.xxx.xxx.xxx 61.239.100.17 2 u 7 64 377 1.1269 -14398695 0.6500 Note the '+' symbol and the offset. I added 'tos maxdist 16' to no avail. I created this Debian server to replace and old CentOS server that was working. It used Chrony though. Both servers are on the same subnet, while the DS is on another. What is missing? | Hello, Duud wrote: 2024-04-07 02:56 The time zone on all servers and client computers starting from the PDC downwards is UTC + 4:00. They all match, zone-wise and time-wise. Perhaps another time synchronization service (different from ntpd) is running on Debian ? What are the full contents of the ntpd configuration file (/etc/ntp.conf) ? What is the output of the following commands (root password is required), replacing "your-win-time-server" with the IP address of your Windows PDC: Code: Select allscript log.txt timedatectl status timedatectl show-timesync su -l -c "systemctl status systemd-timesyncd.service" systemctl status systemd-timesyncd.service su -l -c "apt install ntpdate" su -l -c "ntpdate -v -q your-win-time-server" su -l -c "ntpdate -v -q 61.239.100.17" exit |
I have about fifty devices, of which there are five severs and six workstations. NTP seems to be running fine on all but one server. I am lost as why it is having problems. In the graphic here, Note all the times on three are pretty much right where they are supposed to be as I jumped from one to the next to issue the command. However note the red box. That one is way off! All sit on this network and of the four, that odd one and two others are VMs on the same host! All are running Debian 12. All ar set to the same Timezone. All but the NTP server and set to "NTP service: active" All four have the same RTC time: Tue 2024-04-23 18:55 But the odd one has Universal time matching it's RTC time while the others have Universal time eight hours back. Also not local time on the odd one is ahead eight hours. RTC in local TZ: no is the same for all four. Any guidance will be appreciated. | I don't work with a lot of VMs but this is very interesting. The misbehaving instance on the same machine is set to take its time from its own NTP agent? Do you have restrict default kod nomodify notrap in each of the ntp.conf files? |
my Debian server is running Debian 10 - Buster. recently updated to Debian 4.19.0-25-amd64 - Debian 4.19.289-1 sometimes I loose DNS when that happens, I can not ping any outside website. my solution is, to reboot my server that always sobes the problem but there must me an easier way to get DNS back, I hope any suggesntions ?? | @fred44nl please use code tags for terminal text output. |
Code: Select allsudo systemctl status nvidia-persistenced.service ● nvidia-persistenced.service - NVIDIA Persistence Daemon Loaded: loaded (/lib/systemd/system/nvidia-persistenced.service; enabled; > Active: failed (Result: exit-code) since Sun 2021-11-14 20:20:37 GMT; 31mi> Process: 527 ExecStart=/usr/bin/nvidia-persistenced --user nvpd (code=exite> Process: 539 ExecStopPost=/bin/rm -rf /var/run/nvidia-persistenced (code=ex> CPU: 10ms Nov 14 20:20:36 debian systemd[1]: Starting NVIDIA Persistence Daemon... Nov 14 20:20:37 debian nvidia-persistenced[538]: Started (538) Nov 14 20:20:37 debian nvidia-persistenced[538]: Failed to open libnvidia-cfg.s> Nov 14 20:20:37 debian nvidia-persistenced[527]: nvidia-persistenced failed to > Nov 14 20:20:37 debian nvidia-persistenced[538]: Shutdown (538) Nov 14 20:20:37 debian systemd[1]: nvidia-persistenced.service: Control process> Nov 14 20:20:37 debian systemd[1]: nvidia-persistenced.service: Failed with res> Nov 14 20:20:37 debian systemd[1]: Failed to start NVIDIA Persistence Daemon. lines 1-15/15 (END)...skipping... ● nvidia-persistenced.service - NVIDIA Persistence Daemon Loaded: loaded (/lib/systemd/system/nvidia-persistenced.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-11-14 20:20:37 GMT; 31min ago Process: 527 ExecStart=/usr/bin/nvidia-persistenced --user nvpd (code=exited, status=1/FAILURE) Process: 539 ExecStopPost=/bin/rm -rf /var/run/nvidia-persistenced (code=exited, status=0/SUCCESS) CPU: 10ms Nov 14 20:20:36 debian systemd[1]: Starting NVIDIA Persistence Daemon... Nov 14 20:20:37 debian nvidia-persistenced[538]: Started (538) Nov 14 20:20:37 debian nvidia-persistenced[538]: Failed to open libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object: No such file or directory Nov 14 20:20:37 debian nvidia-persistenced[527]: nvidia-persistenced failed to initialize. Check syslog for more details. Nov 14 20:20:37 debian nvidia-persistenced[538]: Shutdown (538) Nov 14 20:20:37 debian systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE Nov 14 20:20:37 debian systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Nov 14 20:20:37 debian systemd[1]: Failed to start NVIDIA Persistence Daemon. Any ideas? | Please use CODE tags for terminal text output. I have edited your post accordingly. I don't know how to fix your issue but recall there have been other similar posts. Maybe a search will find them. Some details about your system including graphics cards and what changes were made before this started would be essential for any help. |
When I run mkinitramfs with the following settings: /etc/initramfs-tools/initramfs.conf: Code: Select all# # initramfs.conf # Configuration file for mkinitramfs(8). See initramfs.conf(5). # # Note that configuration options from this file can be overridden # by config files in the /etc/initramfs-tools/conf.d directory. # # MODULES: [ most | netboot | dep | list ] # # most - Add most filesystem and all harddrive drivers. # # dep - Try and guess which modules to load. # # netboot - Add the base modules, network modules, but skip block devices. # # list - Only include modules from the 'additional modules' list # MODULES=most # # BUSYBOX: [ y | n | auto ] # # Use busybox shell and utilities. If set to n, klibc utilities will be used. # If set to auto (or unset), busybox will be used if installed and klibc will # be used otherwise. # BUSYBOX=y # # KEYMAP: [ y | n ] # # Load a keymap during the initramfs stage. # KEYMAP=n # # COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ] # COMPRESS=lz4 # # DEVICE: ... # # Specify a specific network interface, like eth0 # Overridden by optional ip= or BOOTIF= bootarg # #DEVICE=wlan0 # # NFSROOT: [ auto | HOST:MOUNT ] # NFSROOT=auto # # RUNSIZE: ... # # The size of the /run tmpfs mount point, like 256M or 10% # Overridden by optional initramfs.runsize= bootarg # RUNSIZE=10% # # FSTYPE: ... # # The filesystem type(s) to support, or "auto" to use the current root # filesystem type # FSTYPE=ext4 ... the USB Debian system boots fine when plugged into either USB slot. Note the MODULES=most setting. However, booting with the MODULES setting like so doesn't work: Code: Select all... MODULES=dep ... It gives the error: ...gave up waiting for root file system device... And if I then exit from that shell, it's a kernel panic. To make my initrd, I used the command: Code: Select all# mkinitramfs -o /boot/initrd.img-5.10.0-10-amd64 # update-grub Other configs: /etc/fstab: Code: Select allLABEL=main / ext4 defaults 0 1 #UUID=a2704de2-447f-44d2-92f5-69068d709796 / ext4 errors=remount-ro 0 1 UUID=7f6026e8-b383-4628-9a97-3c676056c144 /home/user/share ext4 errors=remount-ro 0 2 UUID=adc32db6-eb6b-4e53-8f8c-da9f984ef57b none swap sw 0 0 tmpfs /var/log tmpfs rw,nosuid,noatime,nodev,size=1G,mode=1777 0 0 tmpfs /var/cache tmpfs rw,nosuid,noatime,nodev,size=1G,mode=1777 0 0 tmpfs /var/tmp tmpfs rw,nosuid,noatime,nodev,size=1G,mode=1777 0 0 tmpfs /home/user/.cache tmpfs rw,nosuid,noatime,nodev,size=1G,mode=1777 0 0 #none / tmpfs defaults 00 #/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 Code: Select all$ lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 ext4 1.0 main a2704de2-447f-44d2-92f5-69068d709796 5.4G 26% / ├─sda2 ext4 1.0 backup b758e4e1-aaf0-4027-9efc-503d48ebe39b ├─sda3 ext4 1.0 7f6026e8-b383-4628-9a97-3c676056c144 5.2G 28% /home/user/share └─sda4 swap 1 adc32db6-eb6b-4e53-8f8c-da9f984ef57b [SWAP] sr0 /etc/default/grub: Code: Select all# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries GRUB_DISABLE_RECOVERY=false GRUB_ENABLE_LINUX_LABEL=true # Uncomment to get a beep at grub start GRUB_INIT_TUNE="480 440 1" /boot/grub/grub.cfg (file is just the default made by update-grub): Code: Select all... menuentry 'Debian GNU/Linux' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1'GRUB_ENABLE_LINUX_LABEL=true search --no-floppy --label --set=root echo 'Loading Linux 5.10.0-10-amd64 ...' linux /boot/vmlinuz-5.10.0-10-amd64 root=LABEL=main ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-5.10.0-10-amd64 } ... So my issue is getting this to work on both USB slots with the MODULES=dep setting, as it does when set to MODULES=most. Maybe I'm missing modules? Any ideas? | Do you build the initramfs with MODULES=dep when the system is booted from USB (with MODULEs=most) ? If yes, In the system : Check the active modules with lsmod. Check the modules in the initramfs with lsinitramfs. It should have at least sd_mod, usb-storage, ehci-pci (if USB 2), xhci-pci (if USB 3) (note that module/driver names may contain "_" instead of "-"). In the initramfs shell : Check the active modules with lsmod. Check /dev/sd* devices. Check metadata with blkid. |
Hello, I have a strange pb: when i have no ethernet (unplugged cable for example), and i start Debian, after 1 minute (more or less) Network Manager show me a new active ethernet connexion, and so pretend to be connected: enp3s0: external connexion?... Different UUID between enp3s0 and profil-enp3s0 (the profile i created) ?... In fact, there is no internet connexion with this ethernet interface, and the parameters of this "false" connexion are very strange: (its always the same parameters each time i reproduce the pb. Even if i delete this connexion, it reappairs on the next boot) This false connexion doesn't conflict with wifi. So i can have a real wifi connection with this false connexion. And if, for example, i plug the ethernet cable and i connect with the ethernet profile i have defined, then it's ok, i have my real ethernet connection. If i have a working ethernet, and i start Debian, it's ok: Network Manager connect with the profile i have defined. I try the "no-auto-default=*" in NetworkManager.conf: it doesn't work. Is this a Network Manager pb, or is this a pb due to something else? These are the active services: Code: Select allsystemctl --type=service Code: Select all UNIT LOAD ACTIVE SUB DESCRIPTION alsa-restore.service loaded active exited Save/Restore Sound Card State apparmor.service loaded active exited Load AppArmor profiles avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack colord.service loaded active running Manage, Install and Generate Color Profiles console-setup.service loaded active exited Set console font and keymap cron.service loaded active running Regular background program processing daemon cups-browsed.service loaded active running Make remote CUPS printers available locally cups.service loaded active running CUPS Scheduler dbus.service loaded active running D-Bus System Message Bus getty@tty1.service loaded active running Getty on tty1 ifup@enp3s0.service loaded active exited ifup for enp3s0 keyboard-setup.service loaded active exited Set the console keyboard layout kmod-static-nodes.service loaded active exited Create list of static device nodes for the current kernel lightdm.service loaded active running Light Display Manager ModemManager.service loaded active running Modem Manager NetworkManager-wait-online.service loaded active exited Network Manager Wait Online NetworkManager.service loaded active running Network Manager nmbd.service loaded active running Samba NMB Daemon plymouth-quit-wait.service loaded active exited Hold until boot process finishes up plymouth-read-write.service loaded active exited Tell Plymouth To Write Out Runtime Data plymouth-start.service loaded active exited Show Plymouth Boot Screen polkit.service loaded active running Authorization Manager rsyslog.service loaded active running System Logging Service rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service smbd.service loaded active running Samba SMB Daemon systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:acpi_video0 systemd-backlight@backlight:radeon_bl0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:radeon_bl0 systemd-fsck@dev-disk-by\x2duuid-17a8eacb\x2d8947\x2d4460\x2d97bf\x2df07592da508a.service loaded active exited File System Check on /dev/disk/by-uuid/17a8eacb-8947-4460-97bf-> systemd-fsck@dev-disk-by\x2duuid-a685edfe\x2db09a\x2d4ac0\x2db07d\x2d39856d840f28.service loaded active exited File System Check on /dev/disk/by-uuid/a685edfe-b09a-4ac0-b07d-> systemd-fsck@dev-disk-by\x2duuid-ff2bceeb\x2d7cb4\x2d44e8\x2d8743\x2d7b7c619be0ae.service loaded active exited File System Check on /dev/disk/by-uuid/ff2bceeb-7cb4-44e8-8743-> systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage systemd-journald.service loaded active running Journal Service systemd-logind.service loaded active running User Login Management systemd-modules-load.service loaded active exited Load Kernel Modules systemd-random-seed.service loaded active exited Load/Save Random Seed systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems systemd-sysctl.service loaded active exited Apply Kernel Variables systemd-sysusers.service loaded active exited Create System Users systemd-timesyncd.service loaded active running Network Time Synchronization systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories systemd-udev-trigger.service loaded active exited Coldplug All udev Devices systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown systemd-user-sessions.service loaded active exited Permit User Sessions udisks2.service loaded active running Disk Manager user-runtime-dir@1000.service loaded active exited User Runtime Directory /run/user/1000 user@1000.service loaded active running User Manager for UID 1000 winbind.service loaded active running Samba Winbind Daemon wpa_supplicant.service loaded active running WPA supplicant LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 50 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. lines 1-57/57 (END) Code: Select allutilisateur@debian-ordi:~$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 00:23:8b:6b:7d:71 brd ff:ff:ff:ff:ff:ff 3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether 2a:32:68:53:08:b0 brd ff:ff:ff:ff:ff:ff permaddr 00:22:fa:3b:22:2e utilisateur@debian-ordi:~$ I have Debian 11 LXDE, upgraded. I uninstalled connman & connman-tray, and i installed network-manager-gnome. Do you have an idea? | something here might help... https://html.duckduckgo.com/html/?q=lin ... er+169.254. Why is it a problem if everything works correctly? |
Hello, I have looked at the debian wiki and it explains how to install VNC, but it seems that the xvnc4viewer package is not in the repositories for version 11. How could I install it without having security problems? Is there any other alternative to vnc? Thanks in advance! Regards | Try this: https://packages.debian.org/bullseye/remmina and this: https://packages.debian.org/bullseye/x11vnc TC |
Computer A is a debian 10 x86 notebook, having a wifi vpn connection to the internet. Computer B is another gnulinux computer connected to computer A by a crossover lan cable. https://www.linuxquestions.org/question ... er-743795/ I do not know if this work. I have not tested it in case it messes up computer A. I want computer B to get internet access through computer B's vpn internet connection. Best solution is a solution which is as simple as possible, less intrusive as possible and preferable a non persistent solution. Such that networking settings are reversed when computer A is turned off or easily reversed utilizing commands or editing files. Suggestions? There is no program having a graphical user interface which can do the task? Thank you. | hthi wrote: 2022-01-05 07:14 https://www.linuxquestions.org/question ... er-743795/ I do not know if this work. Probably. That thread is ancient, but very little has changed. Try it and find out? There are zillions of howtos and plenty of documentation on the 'net on this subject (though much of it is somewhat out of date), they all boil down to the same basic steps: Enable ip forwarding in the kernel and/or turn it on via sysctl. Add a masquerade rule to your firewall of choice (IIRC nftables is the default in Debian now). Set up something to handle DHCP and DNS, e.g. dnsmasq. hthi wrote: 2022-01-05 07:14I have not tested it in case it messes up computer A. So back it up before you mess with it? If this machines configuration is important to you, you must have backups already, right? hthi wrote: 2022-01-05 07:14There is no program having a graphical user interface which can do the task? Networkmanager probably can, but I don't use it, so I make no promises. It does have a GUI though. This targets Fedora, but it it should be much the same regardless of distro. At least it's not 10+ year old info, so it should have the correct command names. |
Hello: I have been reading up on how to keep Debian secure and have updated dozens of packages on a couple of servers running Debian Buster. I had no problems until yesterday when I tried to update apache2 in response to a security update issued by the Debian security team. However, I have not been able to get my servers to "see" the update. When I run apt upgrade and apt list --upgradable, the system returns nothing. I thought the problem might be in sources.list. The file looked ok to me, since it explicitly refers to Buster and so I don't have to change stable to oldstable, but I added contrib and non-free to all lines and also added a line to explicitly point to security updates. My system still doesn't see the update. Here are the contents of my sources.list file: deb http://deb.debian.org/debian/ buster main contrib non-free deb-src http://deb.debian.org/debian/ buster main contrib non-free deb http://security.debian.org/debian-security buster/updates main contrib non-free deb-src http://security.debian.org/debian-security buster/updates main contrib non-free # Added this line on 1/4/22 to see if it helps to find security updates deb http://security.debian.org/debian-security buster-security main contrib non-free # buster-updates, previously known as 'volatile' deb http://deb.debian.org/debian/ buster-updates main contrib non-free deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free The security update says the bugs identified are fixed in version 2.4.38-3+deb10u7. I verified I am running 2.4.38-3+deb10u6. Does anyone know what I'm doing wrong? Thank you. | The debian-security part is Bullseye - in Buster was just debian. I know because I edited my sources.list this morning to update Buster to Bullseye on a computer. Try: Code: Select alldeb http://deb.debian.org/debian buster/security main contrib non-free |
My Wi-Fi adapter, brcm4360, has been causing connectivity problems when using NetworkManager to access the internet. The connection frequently drops, and I find it impossible to reconnect without rebooting my computer. To overcome this inconvenience, I decided to disable NetworkManager and opted to connect to Wi-Fi using WPA Supplicant, following instructions from: https://www.linuxbabe.com/debian/connec ... supplicant As a result of this change, I have successfully configured the system to automatically connect to the Wi-Fi network during boot time. However, despite being authenticated and connected to the wireless network, I am unable to access the internet. It seems that I am facing difficulty in obtaining an IP address automatically. I have created and enabled the following dhclient service unit file at "/etc/systemd/system/dhclient.service": [Unit] Description=DHCP Client Before=network.target After=wpa_supplicant.service [Service] Type=forking ExecStart=/usr/sbin/dhclient wlp5s0 -v ExecStop=/usr/sbin/dhclient wlp5s0 -r Restart=always [Install] WantedBy=multi-user.target While I can manually connect to the internet by executing "sudo dhclient wlp5s0" from the command line, my objective is to ensure automatic connectivity at boot time. Any advice and expertise in helping me obtain an IP address automatically during the system's startup process? Thank you. | There's a neat section on wpa_supplicant configuration here: https://wiki.debian.org/WiFi/HowToUse. It's simple working with the /etc/network/interfaces file, and works here flawlessly. For auto IP, have dhcp in the iface line, nothing more necessary (apart from having the dhcp software installed). |
From what I read in this forum and others: up to and including Debian 10, journald was writing to /run/log/. Then with Debian 11 (starting in 2019, or 2020 for the stable branch) there were announcements and discussions about journald’s default being set to persistent storage henceforth. (Not “auto”, but outright persistent. See What's new in Debian 11.) I didn’t really find anything on to this topic beyond the year 2020 or in relation to Debian 12. I suppose the change to a persistent log must have stuck for those who somehow upgraded their Debian 11 to Debian 12. But what if one does a fresh install of Debian 12? That’s what I did. (I had nothing to upgrade because I had never used Debian before February 2024. I was on Linux Mint before; it's based on Ubuntu, but behind by a few years.) And what I found in Debian 12 is that the log is not persistent. The Storage= parameter is followed by auto but the line is commented out! Was persistence really the default only in Debian 11? Anyway... I need persistence, at least for a while. So I un-commented the Storage line in /etc/systemd/journald.conf, changed its option from auto to persistent and restarted systemd-journald.service. (Also systemd-journald at first, because that’s the instruction I had found initially.) But the log still gets created in /run/log/. Even rebooting doesn’t cause the new option to take effect. What am I missing? | From man journald.conf Storage= ... "auto" behaves like "persistent" if the /var/log/journal directory exists, and "volatile" otherwise (the existence of the directory controls the storage mode)... Default is "auto". Read the man for more info. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.