prompt stringlengths 1 63.6k | completion stringlengths 1 53.1k |
|---|---|
Hi, my bluetooth stopped working and after I restarted my computer I was told that I had no bluetooth drivers. After I got my bluetooth working my headphones would only be able to work in HSP/HSP, no A2DP. I have no idea what I am doing, thanks for any suggestions. Also, I use pulseaudio with the bluetooth module installed. | Wild Tom wrote: 2023-09-10 00:25 Had the idea that I might be missing a package, found and installed the "a2ps" package, and restarted bluetooth and pulseaudio, and it now works. Thanks for all the help that you all gave me. That seems like a strange dependency, seemingly unrelated to bluetooth or audio. How did you determine it might help? GNU a2ps - 'Anything to PostScript' converter and pretty-printer Anyway, great you got it working. Please edit your first post and add prefix [Solved] to the title so it may help others. |
Hello, I want to assign a static IP address to the network card named enps08. To do this, I put the following settings in the /etc/network/interfaces file: Code: Select allauto enp0s8 iface enp0s8 inet static address 192.168.1.2 netmask 255.255.255.0 Then, I restarted the networking service, but the IP address card was not set on the network card. Then, I did the following command and I got an error: Code: Select all# /sbin/ifup enps08 ifup: unknown interface enps08 I removed those line and created a file named enps08 under the /etc/network/interfaces.d/ directory and I put the following settings in it: Code: Select allauto enp0s8 iface enp0s8 inet static address 192.168.1.2 netmask 255.255.255.0 Then, I restarted the networking service, but again the IP address card was not set on the network card!!! When I put the above lines in the /etc/network/interfaces file and created the enps08 file with above lines under the /etc/network/interfaces.d/ directory (that is, both together), then the problem was solved. Why both together? Thank you. | hack3rcon wrote: 2023-09-11 12:58 lindi wrote: 2023-09-09 09:32 You misspelled enp0s8? [..] why I must write the configuration in both places? You won't have to: a single configuration file is needed. Take a look at man page for “interfaces”: Code: Select allINTERFACES(5) File formats INTERFACES(5) NAME /etc/network/interfaces - network interface configuration for ifup and ifdown [..] INCLUDING OTHER FILES [..] By default, on a freshly installed Debian system, the interfaces file includes a line to source files in the /etc/network/interfaces.d directory. Please, mark the thread as solved. |
Hello, I used https://www.howtoforge.com/how-to-insta ... debian-10/ tutorial to configure OpenVPN server on Linux. My OpenVPN configuration file is as the following: Code: Select all# cat /etc/openvpn/server.conf port 1194 proto udp dev tun ca ca.crt cert server.crt key server.key dh dh.pem server 10.8.0.0 255.255.255.0 push "redirect-gateway def1 bypass-dhcp" push "dhcp-option DNS 208.67.222.222" push "dhcp-option DNS 208.67.220.220" keepalive 10 120 tls-auth ta.key 0 cipher AES-256-CBC user nobody group nogroup persist-key persist-tun status /var/log/openvpn/openvpn-status.log log /var/log/openvpn/openvpn.log log-append /var/log/openvpn/openvpn.log verb 3 explicit-exit-notify 1 Then, I started the OpenVPN service: Code: Select all# systemctl start openvpn@server And it worked: Code: Select all# systemctl status openvpn@server ● openvpn@server.service - OpenVPN connection to server Loaded: loaded (/lib/systemd/system/openvpn@.service; disabled; preset: enabled) Active: active (running) since Sun 2023-07-16 07:42:24 EDT; 1min 17s ago Docs: man:openvpn(8) https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage https://community.openvpn.net/openvpn/wiki/HOWTO Main PID: 2362 (openvpn) Status: "Initialization Sequence Completed" Tasks: 1 (limit: 10) Memory: 1.4M CPU: 30ms CGroup: /system.slice/system-openvpn.slice/openvpn@server.service └─2362 /usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10 --cd /etc/openvpn --config /etc/openvpn/server> Jul 16 07:42:24 debian systemd[1]: Starting openvpn@server.service - OpenVPN connection to server... Jul 16 07:42:24 debian systemd[1]: Started openvpn@server.service - OpenVPN connection to server. It created a NIC on my server: Code: Select all# ifconfig enp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.20 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::a00:27ff:fe74:6397 prefixlen 64 scopeid 0x20<link> ether 08:00:27:74:63:97 txqueuelen 1000 (Ethernet) RX packets 597 bytes 63680 (62.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 594 bytes 47394 (46.2 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 5640 bytes 17516906 (16.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5640 bytes 17516906 (16.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.8.0.1 netmask 255.255.255.255 destination 10.8.0.2 inet6 fe80::4f45:bad7:c6a2:8e50 prefixlen 64 scopeid 0x20<link> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7 bytes 336 (336.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I have a series of questions: 1- Is Diffie-Hellman algorithm enough? 2- In the tutorial, the author used "nopass" with easyrsa tool, is this option recommended? Is this so that the client doesn't have to enter a password to connect to the server? 3- How about the following IP addresses? What alternatives can I use? Code: Select allpush "redirect-gateway def1 bypass-dhcp" push "dhcp-option DNS 208.67.222.222" push "dhcp-option DNS 208.67.220.220" 4- I have a Windows OS client and I want to connect it to my OpenVPN server. In the tutorial, the client configuration is as follow: Code: Select allclient dev tun proto udp remote 192.168.1.20 1194 # Linux Server IP resolv-retry infinite nobind persist-key persist-tun ca ca.crt cert client.crt key client.key remote-cert-tls server tls-auth ta.key 1 cipher AES-256-CBC verb 3 I created a .ovpn file with the above lines and copied it to the "C:\Program Files\OpenVPN\config" directory. How about the client keys that are on my Server? In which folder should I copy them? Thank you. | Merged with previous topic "A question about the OpenVPN" and "Some questions about the OpenVPN server", with "A question about the OpenVPN". @hack3rcon Please don't open multiple topics on the same subject. |
Hello, I have a Linux box that connected to the internet directly. I connect to it via ssh, but I want to put another Linux box between it and internet and when I connect to this new box, then it forward me to the main Linux box. On the other hand, I want to hide the main Linux. What should I do? Thank you. | Merged "How to forward requests to another Linux server?" with "How to share the internet connection from Linux to clients?" @hack3rcon: Please don't open multiple topics on the same subject. |
Hi, everyone, tldr: Is there any "non-obvious" reason unprivileged users on server environments should belong to any of the following groups? * cdrom * floppy * audio * dip * video * plugdev * netdev Upon checking the official Debian documentation (https://wiki.debian.org/SystemGroups), it appears that I can remove unprivileged users from the above-listed groups. In fact, it appears doing so is a good idea in a production environment -- unless, of course, unprivileged users require access to the resources associated with one or more of these groups (they need to access USB or CD/DVD media, edit network connections, etc.). I have also done a bit of searching elsewhere online, and could not find the confirmation I am looking for (I presume at least one or two others somewhere have asked this before, and I just can't find the conversations about it). I say "non-obvious" because, having read the documentation, I can see no reason to put users of the systems I am responsible for in these groups in question by default. Might there be other reasons not listed in the documentation to leave all users in such groups? Is there a recommendation made somewhere about this in the Debian documentation? Background: I am a RHEL clone defector, since Red Hat changed their code policies, and so my company is very likely replacing the fleet of servers we're responsible for to Debian over time. I am used to seeing the user's own group (the one that has the same name as the user's user name) as the only group users are assigned to by default. Thank you for your knowledge and advice! Michela | Yes, there can be only 1 group for the user if desired. |
Hello, after today's "apt update/upgrade" on Debian 11 (Bullseye), i could see: dkms: running auto installation service for kernel 5.10.0-23-amd64:Error! The /var/lib/dkms/wireguard/1.0.20210219/5.10.0-23-amd64/x86_64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. I am in lower kernel 5.10.0-20-amd64 (accidentally booted into it since for some reason newer one 5.10.0-23-amd64 is not a primary boot entry) $ grep GRUB_DEFAULT /etc/default/grub GRUB_DEFAULT="0" $ sudo update-grub Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-5.10.0-23-amd64 Found initrd image: /boot/initrd.img-5.10.0-23-amd64 Found linux image: /boot/vmlinuz-5.10.0-20-amd64 Found initrd image: /boot/initrd.img-5.10.0-20-amd64 Found linux image: /boot/vmlinuz-5.10.0-23-amd64 Found initrd image: /boot/initrd.img-5.10.0-23-amd64 Found linux image: /boot/vmlinuz-5.10.0-20-amd64 Found initrd image: /boot/initrd.img-5.10.0-20-amd64 Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Adding boot menu entry for UEFI Firmware Settings ... done $ apt list *wireg* golang-golang.zx2c4-wireguard-dev/bullseye-backports,bullseye-backports 0.0.20220117-2~bpo11+1 all wireguard-dkms/oldstable,oldstable,now 1.0.20210219-1 all [installed] wireguard-go/bullseye-backports 0.0.20220117-2~bpo11+1 amd64 wireguard-go/bullseye-backports 0.0.20220117-2~bpo11+1 i386 wireguard-tools/oldstable,now 1.0.20210223-1 amd64 [installed] wireguard-tools/oldstable 1.0.20210223-1 i386 wireguard/oldstable,oldstable,now 1.0.20210223-1 all [installed] I would appreciate your feedback on how to understand this/prevent/improve. | Hello, According to the source code of package named "wireguard-linux-compat" (version 1.0.20210219-1) for Debian Bullseye (old stable, 11) (see [1]), the wireguard kernel module should be compiled by dkms [2] for kernels from 3.10 to 5.5 (for upstream) and from 3.10 to 5.4 (for Debian): Code: Select allPACKAGE_NAME="wireguard" PACKAGE_VERSION="1.0.20210219" AUTOINSTALL=yes BUILT_MODULE_NAME="wireguard" DEST_MODULE_LOCATION="/kernel/net" if ls /lib/modules/5.5*/source/include/uapi/linux/wireguard.h >/dev/null 2>&1 ; then # debian backported wireguard into the 5.5 release: BUILD_EXCLUSIVE_KERNEL="^((5\.[0-4]($|[.-]))|(4\.)|(3\.1[0-9]))" else # upstream requires kernel 3.10 - 5.5, inclusive: BUILD_EXCLUSIVE_KERNEL="^((5\.[0-5]($|[.-]))|(4\.)|(3\.1[0-9]))" fi Since Debian Bullseye is shipped with kernel 5.10.x, this module should not be compiled by dkms for Debian Bullseye. --- [1] https://sources.debian.org/src/wireguard-linux-compat/1.0.20210219-1/src/dkms.conf/ [2] https://it.wikipedia.org/wiki/Dynamic_Kernel_Module_Support |
Hello people, I've installed Debian 12 oh my Asus laptop and I had no issues at all with my Wi-Fi. Now, booting into Kde (or Gnome) I didn't have a Wi-Fi card available. If I use lspci I got: 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) I don't know how to enable my card on my system. I read a lot of posts but I'm a newbie. Any help on how to load the "driver" for my card? I don't have dual-boot and in BIOS the Fast-Boot option is disabled. Thanks in advance. | IoSonoPiero wrote: 2023-07-21 21:33 How I can manage the network via Network Manager? Edit /etc/NetworkManager/NetworkManager.conf changeCode: Select allmanaged=false toCode: Select allmanaged=true |
I do not have a UUID on my system similar to the ones the system seems to think it needs to initialize that start with x2duuid . journalctl -b -p 3 Code: Select allJun 14 16:25:25 god kernel: nvme nvme0: [i]failed to set APST feature[/i] (2) Jun 14 16:25:25 god kernel: Jun 14 16:26:55 god systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-34bc93dd\x2d4ccc\x2d44a3\x2da052\x2dda942d6816e3.device - /dev/disk/by> Jun 14 16:26:55 god systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-ff6c3a6b\x2d7223\x2d4781\x2d8037\x2d89ada4978b2e.device - /dev/disk/by> Jun 14 16:26:55 god systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-3faed653\x2d9fd5\x2d46cb\x2d9539\x2d76d0510b3b16.device - /dev/disk/by> Jun 14 16:26:55 god smartd[946]: Device: /dev/nvme0, number of Error Log entries increased from 27 to 28 To deal with the "failed to set APST feature" thing I modified my /etc/default/grub to include some verbiage that some folks used successfully, but after I did a "update-grub" and rebooted it didn't help. GRUB_CMDLINE_LINUX_DEFAULT="quiet nvme_core.default_ps_max_latency_us=0" Mostly the upgrades have been going smoothly, but I have been running into a couple of rough patches. | Joined: 2006-12-19 00:00 |
Hey everyone, Been playing around with Debian's Live Build, and just wondering in general why the Debian Live ISO by default always seems to set the time to UTC. it is not possible to set the timezone in the chroot stage, because booting the ISO reverts it back. This person Erwin said that is must be done at boot time - https://lists.debian.org/debian-live/20 ... 00010.html - Do they mean the cmdline? There are also boot time hooks possible - https://live-team.pages.debian.net/live ... n.html#515 But it was never really explained in detail how to do this. It would be unusual to set the timezone with the cmdline just for a VM, especially if the HW clock should be used on real hardware, assuming NTP is not used either. But I can't seem to figure out how to make a "boot-time hook" yet. In general, what is the best way to set the time zone automatically when booting up? I know there is NTP and the HW clock for setting the time (UTC or local time), and time zones are usually handled by `timedatectl` or the tzdata/tzselect things. I shouldn't rely on NTP if there isn't a network connection for the Live environment for setting the time at least, and HW clock can sometimes be inaccurate. I really don't like having to change the TZ every time I boot up a Live ISO to the correct one, there has just got to be a better and most ideal way to do this sort of thing. I've been questioning if presetting the time zone is really the best thing to do. But regardless, does anyone have an idea how to set a boot time configuration on a Linux Live ISO for the time zone? | I set the timezone, locale & keyboard via the bootloader options: https://git.sr.ht/~head_on_a_stick/dead ... config#L10 See live-config(7) for a full list of options. They must be preceded by the "boot=live" parameter. |
Today I updated the system and I got the following error message: Code: Select all$ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up linux-image-6.1.0-10-amd64 (6.1.37-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-10-amd64. dkms: autoinstall for kernel: 6.1.0-10-amd64. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64 raspi-firmware: missing /boot/firmware, did you forget to mount it? run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1 run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure): installed linux-image-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); however: Package linux-image-6.1.0-10-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-6.1.0-10-amd64 linux-image-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) | viewtopic.php?t=155192 |
Ive done 2 fresh installs because of this issue. I can turn on laptop log in and that's it . I have zero upper privileges in terminal. I can't update or install absolutely nothing I can do. My Host name is my middle name. Domain name is my last name Full name of new user is my first and last name. i have the same password for everything. Can someone please help me sort out this puzzle? I'm lost. I have Linux Mint on my desk top and never have issues. Thanks for listening | Problem is unclear. Did you set up your user for sudo during installation? What happens when you do Code: Select allsudo <somecommand> eg. Code: Select allsudo apt update sudo requires your user password. Check if your user is in the sudo group. As user, do: Code: Select allgroups If you didn't set up sudo, you need to use root account. Get root with: Code: Select allsu - root needs root password. There are simple steps in the installer asking you if you want to set up sudo, and to set a password for it. If you don't set up sudo, the installer asks if you want to set up a root password. Simple! Let us know how you go with the above if you still need guidance. |
On a system that was upgraded from Debian 11, the console is blocked after a while when idle (except for smplayer running in full screen). I use LXDE, but now the screensaver option has disappeared from Preferences. It is still available from the terminal (xscreensaver-settings). Here, everything is deactivated, like it was in Debian 11. I also deactivated any form of power management in Gnome (gnome-settings). This apparently didn't changed anything. I stopped and deactivated the following services: power-profiles-daemon.service and upower.service. Now the console is blocked only when idleing. If I watch a movie on YT (not in full screen), then the console is not activated. After a few minutes when CPU is not used (maybe that's the trigger), the console is blocked and I am asked for the password. I have these processes: Code: Select allps ax | grep saver 6529 pts/0 S 0:40 xscreensaver --splash 6531 pts/0 S 0:00 xscreensaver-systemd and their parent is systemd. If I terminate them (SIGTERM), they are not respawn. What should I check now? | @undesign: please consider to record and share a video recording of the issue |
First of all sorry for the beginner question, but nevertheless I try to give my best I have a fresh install of Debian 1.4 on my pretty old Mac Mini (2011) which has an Broadcom Inc. Ethernet controller. Code: Select all lspci | grep -i eth 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM57766 Gigabit Ethernet PCIe (rev 01) While checking the logs I found the following entries, which appear once or twice daily: Code: Select allJun 23 15:05:40 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is down Jun 23 17:57:28 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is down Jun 27 21:33:57 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is down Jun 28 16:21:33 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is down It seems that the link is down only for a few seconds: Code: Select all Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is down Aug 15 09:21:28 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is up at 1000 Mbps, full duplex Aug 15 09:21:28 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Flow control is off for TX and off for RX Aug 15 09:21:28 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: EEE is enabled Here some statistics of the interface: Code: Select all ip -s -s link ls enp1s0f0 2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 10:dd:b1:d4:dc:74 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 46581769402 110040530 4 359203 119057 4440503 RX errors: length crc frame fifo overrun 4 0 0 0 0 TX: bytes packets errors dropped carrier collsns 105773354180 120107638 133 0 0 0 TX errors: aborted fifo window heartbeat transns 0 0 0 0 67 Here some interface configuration details: Code: Select all/usr/sbin/ethtool -k enp1s0f0 Features for enp1s0f0: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: on tx-checksum-ip-generic: off [fixed] tx-checksum-ipv6: on tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: on tx-tcp-mangleid-segmentation: off tx-tcp6-segmentation: on generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off [fixed] rx-vlan-offload: on [fixed] tx-vlan-offload: on [fixed] ntuple-filters: off [fixed] receive-hashing: off [fixed] highdma: on rx-vlan-filter: off [fixed] vlan-challenged: off [fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: off [fixed] tx-gre-csum-segmentation: off [fixed] tx-ipxip4-segmentation: off [fixed] tx-ipxip6-segmentation: off [fixed] tx-udp_tnl-segmentation: off [fixed] tx-udp_tnl-csum-segmentation: off [fixed] tx-gso-partial: off [fixed] tx-tunnel-remcsum-segmentation: off [fixed] tx-sctp-segmentation: off [fixed] tx-esp-segmentation: off [fixed] tx-udp-segmentation: off [fixed] tx-gso-list: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: off loopback: off [fixed] rx-fcs: off [fixed] rx-all: off [fixed] tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed] l2-fwd-offload: off [fixed] hw-tc-offload: off [fixed] esp-hw-offload: off [fixed] esp-tx-csum-hw-offload: off [fixed] rx-udp_tunnel-port-offload: off [fixed] tls-hw-tx-offload: off [fixed] tls-hw-rx-offload: off [fixed] rx-gro-hw: off [fixed] tls-hw-record: off [fixed] rx-gro-list: off macsec-hw-offload: off [fixed] Her the full output of kernel: tg3 Code: Select all Aug 15 09:21:21 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: transmit timed out, resetting Aug 15 09:21:21 MacMini kernel: clocksource: timekeeping watchdog on CPU3: hpet wd-wd read-back delay of 1059073ns Aug 15 09:21:21 MacMini kernel: clocksource: wd-tsc-wd read-back delay of 1059841ns, clock-skew test skipped! Aug 15 09:21:22 MacMini kernel: clocksource: timekeeping watchdog on CPU4: hpet wd-wd read-back delay of 1058095ns Aug 15 09:21:22 MacMini kernel: clocksource: wd-tsc-wd read-back delay of 1057885ns, clock-skew test skipped! Aug 15 09:21:22 MacMini kernel: clocksource: timekeeping watchdog on CPU5: hpet wd-wd read-back delay of 1057885ns Aug 15 09:21:22 MacMini kernel: clocksource: wd-tsc-wd read-back delay of 1058095ns, clock-skew test skipped! Aug 15 09:21:23 MacMini kernel: clocksource: timekeeping watchdog on CPU6: hpet wd-wd read-back delay of 1057955ns Aug 15 09:21:23 MacMini kernel: clocksource: wd-tsc-wd read-back delay of 1058095ns, clock-skew test skipped! Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000000: 0x168614e4, 0x00100406, 0x02000001, 0x00800040 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000010: 0xa040000c, 0x00000000, 0xa041000c, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000020: 0x00000000, 0x00000000, 0x00000000, 0x168614e4 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000030: 0x00000000, 0x00000048, 0x00000000, 0x0000010b Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000040: 0x00000000, 0x73000000, 0xc8035001, 0x16002008 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000050: 0x00005803, 0x00000000, 0x0086a005, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000060: 0x00000000, 0x00000000, 0xf0010298, 0x761b000f Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000070: 0x00001090, 0xf6766977, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000080: 0x168614e4, 0x800000f8, 0x00000000, 0x0000016a Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000090: 0x00000000, 0x00000027, 0x00000000, 0x0000004b Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000000a0: 0x8005ac11, 0x00000002, 0x00000122, 0x00020010 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000000b0: 0x05908d80, 0x00105400, 0x00475c11, 0x10110142 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000000d0: 0x0000081f, 0x00000000, 0x00000000, 0x00010001 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000000f0: 0x00000000, 0x00000000, 0x00000000, 0x57766001 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000100: 0x13c10001, 0x00000000, 0x00000000, 0x00062030 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000110: 0x00002000, 0x00002000, 0x000000a0, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000130: 0x00000000, 0x00000000, 0x00000000, 0x15010003 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000140: 0xb1d4dc74, 0x000010dd, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000150: 0x16010004, 0x00000000, 0x00078116, 0x00000001 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000160: 0x1b010002, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000170: 0x00000000, 0x800000ff, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000001b0: 0x00010018, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000200: 0x00000000, 0x73000000, 0x00000000, 0xfe000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000210: 0x00000000, 0x58000000, 0x00000000, 0x76000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000220: 0x00000000, 0xc2000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000260: 0x00000000, 0x00000000, 0x00000000, 0x0000004b Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000280: 0x00000000, 0x0000016a, 0x00000000, 0x00000059 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000290: 0x00000000, 0x000003ff, 0x00000000, 0x000001c1 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000300: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000310: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000320: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000330: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000340: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000350: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000360: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000370: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000380: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000390: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000003a0: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000003b0: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000003c0: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000003d0: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000003e0: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000003f0: 0x00000000, 0x00000027, 0x00000000, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000400: 0x00e04808, 0x02400000, 0x00001000, 0x00000c80 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000410: 0x000010dd, 0xb1d4dc74, 0x000010dd, 0xb1d4dc74 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000420: 0x000010dd, 0xb1d4dc74, 0x000010dd, 0xb1d4dc74 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000430: 0x00000000, 0x00000000, 0x000000cf, 0x000005f2 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000440: 0x00000000, 0x00000000, 0x00000000, 0x04384400 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000450: 0x00000001, 0x00008000, 0x00000000, 0x00000102 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000460: 0x00000018, 0x00002620, 0x01ff0002, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000470: 0xa1002080, 0x000000a6, 0x00000000, 0x50001000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000480: 0x42000000, 0x7fffffff, 0x06000004, 0x7fffffff Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000500: 0x00000008, 0x00000001, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000590: 0x00900110, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000600: 0xffffffff, 0x00f80011, 0x00000000, 0x00001f0c Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000610: 0xffffffff, 0x00000000, 0x07c00044, 0x07cb8800 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000620: 0x00000040, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000630: 0x01230123, 0x01230123, 0x01230123, 0x01230123 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000640: 0x01230123, 0x01230123, 0x01230123, 0x01230123 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000650: 0x01230123, 0x01230123, 0x01230123, 0x01230123 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000660: 0x01230123, 0x01230123, 0x01230123, 0x01230123 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000670: 0xa4ca0076, 0x23140171, 0xd2f4da44, 0x5bd7ae45 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000680: 0x83d14c77, 0x36eb60f4, 0x7e9a44b3, 0x2bcf5e35 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000690: 0x7e7e2370, 0xfdc86bac, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000800: 0x00000000, 0xffffffff, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000810: 0x00000000, 0xffffffff, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000820: 0x00000000, 0x00000000, 0xffffffff, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000830: 0x00000000, 0xffffffff, 0xffffffff, 0xffffffff Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000840: 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000850: 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000860: 0xffffffff, 0xffffffff, 0xffffffff, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000880: 0x000002a0, 0x000332b6, 0x00000000, 0x00000001 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000890: 0x00000000, 0x00000001, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000008f0: 0x007c0001, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000c00: 0x0000000a, 0x00000000, 0x00000003, 0x00000001 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000c10: 0x00000000, 0x00000000, 0x00000000, 0x025a0000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000c80: 0x00030227, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000ce0: 0xffa2f0fe, 0x00000000, 0x0000025a, 0x00041028 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00000cf0: 0x00000000, 0x50000027, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001000: 0x00000002, 0x00000000, 0xa0007d82, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001010: 0x00270271, 0x00007d82, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001400: 0x00000006, 0x00000000, 0x00000000, 0x00000001 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001440: 0x00000027, 0x00000027, 0x00000027, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001450: 0x00000027, 0x00000027, 0x00000027, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001460: 0x00000027, 0x00000027, 0x00000027, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001470: 0x00000027, 0x00000027, 0x00000027, 0x00000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001800: 0x00000016, 0x00000000, 0x00000027, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001840: 0x00000000, 0x00000000, 0x00000200, 0x00000010 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001850: 0x0000001f, 0x00000000, 0x00004260, 0x00270027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001860: 0x01000000, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00001c00: 0x00000002, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002000: 0x00000002, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002010: 0x00000181, 0x00000001, 0x007bffff, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002100: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002110: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002120: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002130: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002140: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002150: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002160: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002170: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002180: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002190: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000021a0: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000021b0: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000021c0: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000021d0: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000021e0: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000021f0: 0x000df0fd, 0x000d68c0, 0x0000002e, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002200: 0x0001cc75, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002400: 0x00000012, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002440: 0x00000000, 0x00000000, 0x00000002, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002450: 0x00000000, 0xffff0000, 0x02001800, 0x00006000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002470: 0x00000000, 0x0000018e, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000024c0: 0x0201a101, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002800: 0x00000006, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002c00: 0x00000006, 0x00000000, 0x00000000, 0x000001fd Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002c10: 0x00000000, 0x00000000, 0x00000019, 0x0000000c Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00002c20: 0x00020002, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003000: 0x00000006, 0x00000000, 0x00000000, 0x000001fd Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003600: 0x00137400, 0x00130000, 0x00110000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003610: 0x00170000, 0x00130000, 0x00150000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003620: 0x00000000, 0x00000000, 0x00000000, 0x00022080 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003630: 0x00000000, 0x80008000, 0x00001080, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003640: 0x0000000a, 0x32f00003, 0x00000020, 0x00000019 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003650: 0x00000171, 0x00000bff, 0x57766001, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003660: 0x00000000, 0x00000000, 0x010400a7, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003670: 0x0000002a, 0xfeffff63, 0x0000000a, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003690: 0x80157766, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000036a0: 0x00000000, 0x00000000, 0x00000000, 0x00000044 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000036b0: 0x001003c8, 0x07ff07ff, 0x07ff07ff, 0x0100000d Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000036c0: 0xffffffff, 0x05997aa8, 0x0a1aa2c6, 0x00000256 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000036d0: 0x0000019d, 0x00000000, 0x00000000, 0x000012fc Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000036e0: 0x00000b19, 0x20800799, 0x00500799, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003c00: 0x00000302, 0x00000000, 0x00000000, 0x00000048 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003c10: 0x00000000, 0x00000035, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003c20: 0x00000000, 0x00000005, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003c30: 0x00000000, 0x00000000, 0x00000000, 0xffffa000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003c40: 0x00000000, 0x00000b00, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003c50: 0x00000000, 0x00000184, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003c80: 0x0000016a, 0x00000059, 0x00000000, 0x000001c1 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003cc0: 0x00000027, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003cd0: 0x00000000, 0x0000000f, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003d00: 0x00000000, 0xffff9000, 0x00000000, 0xffff8000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003d10: 0x00000000, 0xffff7000, 0x00000000, 0xffff6000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003d80: 0x00000014, 0x00000000, 0x00000005, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003d90: 0x00000005, 0x00000000, 0x00000014, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003da0: 0x00000005, 0x00000000, 0x00000005, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003db0: 0x00000014, 0x00000000, 0x00000005, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003dc0: 0x00000005, 0x00000000, 0x00000014, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00003dd0: 0x00000005, 0x00000000, 0x00000005, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004000: 0x00000002, 0x00000000, 0x000d6250, 0x000c820f Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004010: 0x00482070, 0x002c0012, 0x00800440, 0x01004e22 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004020: 0x00000000, 0x00000010, 0x00000010, 0x00000050 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004030: 0x00000000, 0x01084c20, 0x002e4010, 0x00000002 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004040: 0x00400000, 0x0aec2000, 0x00000010, 0x0047d062 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004400: 0x00000006, 0x00000000, 0x00010000, 0x0000a000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004410: 0x00000000, 0x0000002a, 0x000000a0, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004420: 0x0000003d, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004440: 0x00000000, 0x00000000, 0x00000000, 0x07d20884 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004450: 0x023a0223, 0x00e500c2, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004700: 0x00030002, 0x00100000, 0x00100010, 0x155b0000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004710: 0xffff4240, 0x000ca924, 0x00100012, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004720: 0x00000000, 0x00000000, 0xf02c0000, 0xffff4270 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004770: 0x000c0404, 0x00000042, 0x00000018, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004800: 0x188303fe, 0x00000000, 0x00000000, 0x00000100 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004810: 0x00000000, 0x00000009, 0x03509580, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004820: 0x00000067, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004860: 0x00000067, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004870: 0x00000000, 0x003e1820, 0x003e1820, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004890: 0x28090404, 0x00305400, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000048a0: 0x000f0010, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004900: 0x18030006, 0x00000003, 0x30000000, 0x00000120 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004910: 0x00000040, 0x00000003, 0x0000d59c, 0x00000018 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004920: 0x00000083, 0x023e8000, 0xffa31601, 0x0f000030 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004930: 0xffa0ea01, 0x0f000030, 0xffa2f0f9, 0x0f000260 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004940: 0xfdade801, 0x0f000078, 0xb9b9b1b1, 0x4545bfbf Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004950: 0xf0330000, 0xffa31630, 0xaf000000, 0x837d0082 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004960: 0x00000000, 0xffa0ea30, 0xaf000000, 0x40000027 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004970: 0x00028203, 0x00205400, 0x0000001c, 0x000000ff Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004980: 0x00000083, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004990: 0x00000000, 0x00000000, 0xffa2f358, 0xef000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000049a0: 0x00f000ff, 0x00000083, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000049b0: 0xffd60401, 0xff860801, 0xffdb5601, 0xfb7b80f9 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000049c0: 0xffa31602, 0xffa0ea02, 0xffa2f0fe, 0xfdade802 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000049d0: 0xffd60402, 0xff860802, 0xffdb5602, 0xfb7b80fe Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000049f0: 0xf0330000, 0xfdade878, 0xaf000000, 0x0000ffff Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004c00: 0x200003fe, 0x00000020, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004c10: 0x00000015, 0x00000000, 0x00000006, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004c20: 0x00000000, 0x00000000, 0x00000000, 0x00000006 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004c30: 0x00000000, 0x005a8000, 0x0000003d, 0x0000003d Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004c40: 0x00000000, 0xfffbffe0, 0x00010020, 0x00140020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004c50: 0x3ff16169, 0x184ffdc0, 0x9c100059, 0xaa047373 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00004c60: 0x00000020, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005000: 0x00009800, 0x80000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005010: 0x00000000, 0x00000000, 0x00000000, 0x08000dcc Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005020: 0x00831821, 0x00000000, 0x00000000, 0x40000020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005030: 0x00000000, 0x0000001d, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005040: 0x00000000, 0x00000000, 0x08000dde, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005080: 0x00009800, 0x80000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005090: 0x00000000, 0x00000000, 0x00000000, 0x08000dcc Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000050a0: 0x00000000, 0x00000000, 0x00000000, 0x40000020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000050b0: 0x00000000, 0x0000001d, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000050c0: 0x00000000, 0x00000000, 0x08000dde, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005100: 0x00009800, 0x80000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005110: 0x00000000, 0x00000000, 0x00000000, 0x08000dcc Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005120: 0x00831821, 0x00000000, 0x00000000, 0x40000020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005130: 0x00000000, 0x0000001d, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005140: 0x00000000, 0x00000000, 0x08000dde, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005180: 0x00009800, 0x80000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005190: 0x00000000, 0x00000000, 0x00000000, 0x08000dd8 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000051a0: 0x00831821, 0x00000000, 0x00000000, 0x40000020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000051b0: 0x00000000, 0x0000001d, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000051c0: 0x00000000, 0x00000000, 0x08000dde, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005200: 0x00000000, 0x00000000, 0x00000000, 0x531ede98 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005210: 0x531ede9a, 0x531ede9d, 0x000003e8, 0x000003e8 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005220: 0x000003e8, 0x08000900, 0x08000900, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005230: 0x531ede70, 0x531ede70, 0x531edeb5, 0x000003e8 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005240: 0x000003e8, 0x531edebd, 0x531edec0, 0x000003e8 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005250: 0x0800ff68, 0x00000000, 0x000003e8, 0x000003e8 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005260: 0x000003e8, 0x0800ff68, 0x0800ff68, 0xc0000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005270: 0xc0000000, 0x08000900, 0x00000000, 0x000003e8 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005280: 0x00009800, 0x80000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005290: 0x00000000, 0x00000000, 0x00000000, 0x08000dcc Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000052a0: 0x1460fffb, 0x00000000, 0x00000000, 0x40000020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000052b0: 0x00000000, 0x0000001d, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000052c0: 0x00000000, 0x00000000, 0x08000dde, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005300: 0x00009800, 0x80008000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005310: 0x00000000, 0x00000000, 0x00000000, 0x08000dcc Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005320: 0x00831821, 0x00000000, 0x00000000, 0x40000020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005330: 0x00000000, 0x0000001d, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005340: 0x00000000, 0x00000000, 0x08000dde, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005380: 0x00009800, 0x80000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005390: 0x00000000, 0x00000000, 0x00000000, 0x08000dd8 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000053a0: 0x00831821, 0x00000000, 0x00000000, 0x40000020 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000053b0: 0x00000000, 0x0000001d, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000053c0: 0x00000000, 0x00000000, 0x08000dde, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005800: 0x00000000, 0x73000000, 0x00000000, 0xfe000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005810: 0x00000000, 0x58000000, 0x00000000, 0x76000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005820: 0x00000000, 0xc2000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005860: 0x00000000, 0x00000000, 0x00000000, 0x0000004b Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005880: 0x00000000, 0x0000016a, 0x00000000, 0x00000059 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005890: 0x00000000, 0x000003ff, 0x00000000, 0x000001c1 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005900: 0x00000000, 0x00000027, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005980: 0x00000027, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00005a00: 0x000f601f, 0x00000000, 0x00010000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006000: 0x20000082, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006400: 0x00000000, 0x00000000, 0x00010091, 0xc0000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006410: 0x05000016, 0x05000016, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006430: 0x00000000, 0x14e41686, 0x168614e4, 0x01020000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006440: 0x0000304f, 0x000002e4, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000064c0: 0x00000005, 0x00000002, 0x00000122, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000064d0: 0x00000040, 0x00008d80, 0x00000000, 0x00d75e11 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000064e0: 0x00000031, 0x0000001f, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000064f0: 0x00000002, 0x00000030, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006500: 0x03e10003, 0xb1d4dc74, 0x000010dd, 0x00000003 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006510: 0x00078116, 0x0005810b, 0x00046105, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006550: 0x00000001, 0x02800000, 0x0000000f, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006560: 0x0000000f, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006800: 0x04130034, 0x20081082, 0x01009618, 0x53272bee Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006810: 0x01122010, 0xffffffff, 0x00000000, 0x00000040 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006880: 0x77fff020, 0x00000040, 0x80011686, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006890: 0x00800000, 0x88008000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000068a0: 0x00000000, 0x00010001, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x000068b0: 0x00040000, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006900: 0xe8711938, 0x00000000, 0x00000000, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00006920: 0x00000000, 0x00000000, 0x00000001, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00007000: 0x08000188, 0x00000000, 0x00000000, 0x000000c4 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00007010: 0xd1c00001, 0x02408200, 0x000500db, 0x03000a00 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00007020: 0x00000000, 0x00000000, 0x00000406, 0x10004000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00007030: 0x00010000, 0x000000c8, 0x000c0030, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0x00007500: 0x00000000, 0x00000000, 0x00000080, 0x00000000 Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0: Host status block [00000001:00000073:(0000:0184:0000):(0000:000f)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 0: NAPI info [00000073:00000073:(0027:000f:01ff):0000:(004b:0000:0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 1: Host status block [00000001:000000fe:(0000:0000:0000):(016a:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 1: NAPI info [000000fe:000000fe:(0000:0000:01ff):016a:(016a:016a:0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 2: Host status block [00000001:00000058:(0059:0000:0000):(0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 2: NAPI info [00000058:00000058:(0000:0000:01ff):0059:(0059:0059:0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 3: Host status block [00000001:00000076:(0000:0000:0000):(0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 3: NAPI info [00000076:00000076:(0000:0000:01ff):03ff:(01ff:01ff:0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 4: Host status block [00000001:000000c2:(0000:0000:01c1):(0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: 4: NAPI info [000000c2:000000c2:(0000:0000:01ff):01c1:(01c1:01c1:0000:0000)] Aug 15 09:21:24 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is down Aug 15 09:21:28 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is up at 1000 Mbps, full duplex Aug 15 09:21:28 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Flow control is off for TX and off for RX Aug 15 09:21:28 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: EEE is enabled Unfortunately I have no idea on how I could trace this problem down, I'm even not sure if it's a hard, network driver or kernel issue. I tried googling some of them and found the following: Re: Kernel 3.4.57: "tg3 0000:01:00.0: eth0: transmit timed out, resetting" https://lkml.iu.edu/hypermail/linux/ker ... 00204.html, So I turned scatter-gather off, but it does solve the problem Many thanks in advance for any input or guidance, which is very much appreciated! Deekee | Please use CODE tags when posting terminal text output. |
During a fresh install of Debian 12 [bookworm] i386 32 bit i was notified I needed mentioned firmware. Using k3b do I burn it as a image or Data. Thank guys! | Just install them with Synaptic, no need to download them unless you don't have internet. fwcutter is to extract firmware from a manually downloaded file, whereas firmware-b43-installer will download firmware from the net and install it. There is also firmware-b43legacy-installer . You need to work out the exact chipset of your device before you can know what to use. More info here - https://wiki.debian.org/bcm43xx |
I disabled IPv6 at multiple levels: - kernel: ipv6.disable=1 - NetworkManager.conf: ipv6.method=disabled in [main] section - GUI (yes, the system was restarted after I saw that restarting NetworkManager service has no effect) Yet, in system logs I see a message like this every 2 seconds: Code: Select allAug 03 20:58:39 studio256 NetworkManager[121910]: <warn> [1691089119.3423] platform-linux: do-add-ip6-address[3: fe80::1435:9171:c37b:cdca]: failure 95 (Operation not supported) This behavior is true for both the Ethernet and wifi interfaces. How can I configure NetworkManager not to write these messages / disable IPv6? | Have you tried to use the nmtui command in the terminal to disable IPv6: |
It seems like this should be easy to resolve because wifi is almost working. I recently installed Debian 11 Bullseye in a HP T620 thin client. The installer asked for iwlwifi-7260-17.ucode, which I found, put on a USB stick and inserted. As I recall the installer didn't exactly acknowledge it, but didn't complain. Ethernet works, no problem. According to lspci -k, the wifi controller is an Intel Corporation Wireless 7260 (rev c3). Kernel driver = iwlwifi, module = iwlwifi. The relevant output from ip a is Code: Select all3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 7c:5c:f8:fc:a5:f3 brd ff:ff:ff:ff:ff:ff inet 192.168.4.59/22 brd 192.168.7.255 scope global dynamic noprefixroute wlp1s0 valid_lft 13851sec preferred_lft 13851sec inet6 fd55:7959:7e7:1:8c2f:851f:b03b:32c4/64 scope global dynamic noprefixroute valid_lft 2591873sec preferred_lft 604673sec inet6 fe80::1492:113d:a09c:3ed6/64 scope link noprefixroute valid_lft forever preferred_lft forever ip route gives this output: Code: Select alldefault via 192.168.4.1 dev enp2s0 onlink linkdown default via 192.168.4.1 dev wlp1s0 proto dhcp metric 600 192.168.4.0/24 dev enp2s0 proto kernel scope link src 192.168.4.58 linkdown 192.168.4.0/22 dev wlp1s0 proto kernel scope link src 192.168.4.59 metric 600 Note, enp2s0 showing linkdown is OK because the ethernet is unplugged. Output from systemctl status wpa_supplicant: Code: Select all● wpa_supplicant.service - WPA supplicant Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-08-04 19:22:40 CDT; 12min ago Main PID: 683 (wpa_supplicant) Tasks: 1 (limit: 8788) Memory: 5.0M CPU: 108ms CGroup: /system.slice/wpa_supplicant.service └─683 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant So wifi seems to be partly working. But I can't ping the T620's IP from other hosts on the LAN, and from the T620 I can't ping anything. From another host, I probe the network with nmap, and the T620's IP doesn't appear. Still, the Network Manager icon in the panel shows full bars, and Connection Information all looks OK, I think. Some info from there that might be significant: Broadcast Address = 192.168.4.255, Subnet Mask = 255.255.252.0, Default Route = 192.168.4.1 (this is the router), Primary DNS = 216.165.129.158, Secondary DNS = 216.170.153.146. Looking at Network Manager's edit dialog for Network Connections, the checkbox for "All users may connect" was open so I checked it; in the Wi-Fi tab, the SSID is correct, Mode = Client, Channel = default, BSSID = (blank), Rate = 0, Transmission power = 0, Device = wlp1s0, Cloned MAC address = (blank), MTU = automatic. In the Wi-Fi Security tab, Security = WPA & WPA2 Personal. In the Proxy tab, Method = None, other fields are blank. In the IPv4 Settings tab, Method = Automatic (DHCP) and other fields are blank. In the IPv6 Settings tab, Method = Automatic, most fields are blank, IPv6 privacy extensions = Default, IPv6 address generation mode = Stable privacy. Rate = 0 and transmission power = 0 look suspicious, don't they? /etc/network/interfaces is this: Code: Select allsource /etc/network/interfaces.d/* auto lo iface lo inet loopback auto enp2s0 iface enp2s0 inet static address 192.168.4.58 netmask 255.255.255.0 gateway 192.168.4.1 There's nothing in /etc/network/interfaces.d/. There wasn't a stanza in /etc/network/interfaces for wlp1s0, so I added the following and restarted networking with systemctl (which took no time at all) - but it didn't help so then I removed the stanza. Code: Select alliface wlp1s0 inet dhcp wpa-essid %myRealSSID% wpa-psk %myRealPassword There was no /etc/wpa_supplicant/wpa_supplicant.conf, so following a recipe at https://linuxconfig.org/how-to-connect- ... -10-buster I created one with sudo wpa_passphrase %myRealSSID% %myRealPassword% > /etc/wpa_supplicant/wpa_supplicant.conf and edited it per the recipe. The resulting wpa_supplicant.conf was Code: Select allctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel network={ ssid="%myRealSSID%" psk=%a long hexadecimal number% proto=RSN key_mgmt=WPA-PSK group=CCMP pairwise=CCMP } Then I issued systemctl restart wpa_supplicant, which took maybe 10 seconds. But wifi still can't communicate over the LAN. Any ideas or suggestions are appreciated. Thanks. | Hi, The "Communication" section of the "HP t620 Flexible Thin Client Product Specifications" [1] reports the following possible hardware: 10/100/1000 Gigabit Ethernet (RJ-45) (actual speeds may vary) Broadcom 802.11 a/b/g/n Wi-Fi with dual internal antennas (optional) Broadcom 802.11ac with dual internal antennas (optional) HP 100 Mbps Mini PCIe SC Fiber NIC (factory-installed option) There's apparently no Intel Wifi adapter. Perhaps I have found the wrong HP model ? Anyway, can you report system log messages about the Wifi kernel module ? You can do it with the command: Code: Select allsu -l -c "journalctl -b --no-pager --grep iwl" Can you report system log messages about the NetworkManager? You can do it with the command: Code: Select allsu -l -c "journalctl -b --no-pager --grep networkmanager" --- [1] https://support.hp.com/hk-en/document/c04017240#AbT4 |
Hey guys! I'm pretty new to Linux stuff, so please be patient with me when it comes to technical details. I have tinkered with a few other distroes in the past on this same laptop, as I'm on now, and everything worked fine, till a few months back, when I installed Endeavour OS if I remember correctly and then my wifi just became slow, tried to fix it back then but gave up on it and just started using my desktop as my daily driver. Now I freshly installed Debian 12 on the same laptop and, well my wifi still sucks, checked the network driver and updated it (tho it was the latest version) updated and upgraded all the packages and all, router can't be the problem because all of my other devices are working properly except this one(and switched to a new router in the period I wasn't using this laptop), and I just can't find an answer. Read a few other topics similar to mine but I can't figure out what they did at the end to solve their problem. I am getting 2-3000ms when I ping google.com and using anything through the network is just a pain in the ass at this point. Thanks for your answer! | There could be several issues, like poor signal strength, interference, slow DNS resolution and WiFi power saving features. You could also try disabling IPv6. Check your log to see if you can find anything there. Code: Select all# journalctl -b |
Hello all, I am trying to install the "openvpn" package on Debian Bookworm. The reason I'm doing this is because it's a dependency of ProtonVPN. The installation fails as follows: Why is this happening? Code: Select allmiracledinner@miracledinner-b550aoruselitev2:~$ sudo apt update Hit:1 http://security.debian.org/debian-security bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://deb.debian.org/debian bookworm-backports InRelease Hit:5 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. miracledinner@miracledinner-b550aoruselitev2:~$ sudo apt install openvpn Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: easy-rsa libpkcs11-helper1 opensc opensc-pkcs11 Suggested packages: resolvconf openvpn-dco-dkms openvpn-systemd-resolved The following NEW packages will be installed: easy-rsa libpkcs11-helper1 opensc opensc-pkcs11 openvpn 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. Need to get 651 kB/2,042 kB of archives. After this operation, 6,825 kB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://deb.debian.org/debian bookworm/main amd64 openvpn amd64 2.6.3-1 404 Not Found [IP: 199.232.58.132 80] E: Failed to fetch http://deb.debian.org/debian/pool/main/o/openvpn/openvpn_2.6.3-1_amd64.deb 404 Not Found [IP: 199.232.58.132 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? miracledinner@miracledinner-b550aoruselitev2:~$ sudo apt install --fix-missing openvpn Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: easy-rsa libpkcs11-helper1 opensc opensc-pkcs11 Suggested packages: resolvconf openvpn-dco-dkms openvpn-systemd-resolved The following NEW packages will be installed: easy-rsa libpkcs11-helper1 opensc opensc-pkcs11 openvpn 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. Need to get 651 kB/2,042 kB of archives. After this operation, 6,825 kB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://deb.debian.org/debian bookworm/main amd64 openvpn amd64 2.6.3-1 404 Not Found [IP: 199.232.58.132 80] Selecting previously unselected package easy-rsa. (Reading database ... 324904 files and directories currently installed.) Preparing to unpack .../easy-rsa_3.1.0-1_all.deb ... Unpacking easy-rsa (3.1.0-1) ... Selecting previously unselected package libpkcs11-helper1:amd64. Preparing to unpack .../libpkcs11-helper1_1.29.0-1_amd64.deb ... Unpacking libpkcs11-helper1:amd64 (1.29.0-1) ... Selecting previously unselected package opensc-pkcs11:amd64. Preparing to unpack .../opensc-pkcs11_0.23.0-0.3_amd64.deb ... Unpacking opensc-pkcs11:amd64 (0.23.0-0.3) ... Selecting previously unselected package opensc. Preparing to unpack .../opensc_0.23.0-0.3_amd64.deb ... Unpacking opensc (0.23.0-0.3) ... Setting up libpkcs11-helper1:amd64 (1.29.0-1) ... Setting up opensc-pkcs11:amd64 (0.23.0-0.3) ... Setting up easy-rsa (3.1.0-1) ... Setting up opensc (0.23.0-0.3) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for bamfdaemon (0.5.6+repack-1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for libc-bin (2.36-9) ... E: Failed to fetch http://deb.debian.org/debian/pool/main/o/openvpn/openvpn_2.6.3-1_amd64.deb 404 Not Found [IP: 199.232.58.132 80] miracledinner@miracledinner-b550aoruselitev2:~$ | @MiracleDinner: What is the output of the following commands ? Code: Select allscript log.txt sudo apt update sudo apt install openvpn apt-cache policy openvpn exit The commands and their ouputs will be stored in the file named log.txt |
Hello, I created a "ifcfg-eth1" file under the "/etc/network/interfaces.d/" directory with the following contents: Code: Select allauto eth1 iface eth1 inet static address IP netmask IP gateway IP But, I can't enable and disable my NIC: Code: Select all$ sudo ifdown eth1 ifdown: interface eth1 not configured $ $ sudo ifup eth1 RTNETLINK answers: File exists ifup: failed to bring up eth1 Why? Thank you. | "IP" is not a recognised IP address. Use actual, available, IP addresses instead. |
I have read all the posts regarding problems with Broadcom 4312 drivers but I have a new problem. On an old Lenovo I can run Broadcom wifi on Mint LMDE with no problem. On Bookworm I use a Netgear dongle to download the Broadcom drivers, install them and reboot. Both wifi interfaces are displayed in the Network Manager but the Network switch is off and greyed out so I cannot switch it on. If I remove the Broadcom drivers then the Netgear interface works. I have checked the blacklist files and there is no hardware switch for wifi on Lenovo. I also re-installed using the sta-dkms file as described in the Debian wiki. After reboot the broadcom interface does not show up and Netgear works OK. Any suggestions pease? | That first device is hard blocked. Which means it's switched off by hardware. You could try: Code: Select allrfkill unblock all You do need to post the results of the commands from Aki which should show the driver status. And use code tags for terminal text output please.. |
Most of my systems are based on LUKS-encrypted LVM, using the automatic partitioning scheme that was in the installer from the Jessie_ - Official Snapshot amd64 kde-CD Binary-1 20141883. and I've updated them every time there was a new stable release. Four upgrades went smoothly without any significant issue, but on my primary local file server the new Bookworm linux-image-6.1.0-9-amd64 kernel drops me into busybox, though my last Bullseye kernel (linux-image-5.10.0-23-amd64) boots normally to Bookworm. Sorry, I have two monitors, vertical and horizontal, and only the vertical one lights up until later in the boot process, so the picture doesn't capture too much of the dialog, but from what I can glean the new kernel is not properly initiating my LVM which is at /dev/mapper/hostname--vg-root. The screen message says: Code: Select allGave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) -Check rootdelay= (did the system wait long enough>) -Missing modules (cat /proc/modules; ls /dev) I believe the syslog had something like this: Code: Select allBegin: Mounting root file system ... Begin: Running /scripts/local-top ... Volume group "liva-vg" not found Cannot process volume group liva-vg Volume group "liva-vg" not found Cannot process volume group liva-vg Couldn't find device with uuid Eyx2dv-R4Qo-6oEL-UyVf-vY87-BSJ0-CrcGZi. Couldn't find device with uuid Eyx2dv-R4Qo-6oEL-UyVf-vY87-BSJ0-CrcGZi. Refusing activation of partial LV liva-vg/freespace. Use '--activationmode partial' to override. See 'systemctl status lvm2-pvscan@8:67.service' for details. My booted system (with the Bullseye kernel) does not show anything when catting that line. Unit lvm2-pvscan@8:67.servic.service could not be found. I also got a line like this: 2023-06-13T16:49:55.822032-07:00 ubu udisksd[869]: Failed to load the 'mdraid' libblockdev plugin The /var/log/bootlog file has a lot of entries like this: 0;1;31mFAILED[0m] Failed to start [0;1;39mLVM event activation on device 254:0 Can anyone belt me with a clue stick? Edit: I booted back to the new kernel and played around with busybox, but didn't see any way to see the log output and save it to a file, particularly cranking my neck 90 degrees to read off of my vertical monitor. Nothing in kern.log or kern.log.1 caught my eye in the fully booted system using the Bullseye kernel. Ditto dmesg. Time to walk the pooch I'm dog sitting for a neighbor before I get mauled, but I'll check in later. | You can boot with a previous kernel, so run Code: Select all# update-initramfs -u -k all |
So I've been giving a neglected system some love. After upgrading from stretch to buster a few months ago, I noticed that my Dual onboard R8168 started to intermittently losing its link on the primary network interface. For some reason only eth0 is affected, and eth1 is not. I then found out that this might be caused by the default R8169-driver in the kernel and that I should give r8168-dkms a try. Installing this did indeed fix the problem (buster uses version 8.046.00-1). (Note that the R8169-driver for all kernels of stretch did not have this issue). Then yesterday, I upgraded from buster to bullseye. After a few struggles with package dependencies, broken packages and version updates that had breaking changes in their configs, that's all working properly. However, the problem of eth0 intermittently losing link (3 seconds, then goes back up automatically) suddenly returned. The link-down happens in between 13s up to 1h40m periods (sampled in the past 23 hours), and every time the link goes back up again after 3s. Other than the fact that bullseye uses kernel 5.10 and r8168-dkms version 8.048.03-3 (and I can't switch back to 8.046.00-1 as that requires kernel 4.19.0) there have been no significant changes with regard to networking, so I'm at a loss what could cause this (and at an even greater loss as to how to fix it). Any help would be greatly appreciated. Edit to include output from lspci and inxi: Code: Select all02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller Flags: bus master, fast devsel, latency 0, IRQ 24 I/O ports at e000 [size=256] Memory at dfe04000 (64-bit, prefetchable) [size=4K] Memory at dfe00000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 02-00-00-00-68-4c-e0-00 Kernel driver in use: r8168 Kernel modules: r8168 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller Flags: bus master, fast devsel, latency 0, IRQ 25 I/O ports at d000 [size=256] Memory at dfd04000 (64-bit, prefetchable) [size=4K] Memory at dfd00000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 03-00-00-00-68-4c-e0-00 Kernel driver in use: r8168 Kernel modules: r8168 Code: Select allSystem: Kernel: 5.10.0-23-686-pae i686 bits: 32 Console: tty 0 Distro: Debian GNU/Linux 11 (bullseye) Machine: Type: Desktop Mobo: N/A model: N/A serial: N/A BIOS: American Megatrends v: 4.6.4 date: 03/27/2012 CPU: Info: Dual Core Intel Atom D2550 [MT MCP] speed: 1862 MHz Graphics: Device-1: Intel Atom Processor D2xxx/N2xxx Integrated Graphics driver: gma500 v: N/A Display: server: No display server data found. Headless machine? tty: 237x62 Message: Unable to show advanced data. Required tool glxinfo missing. Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8168 IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter> IF-ID-1: vlan34 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 223.57 GiB used: 144.7 GiB (64.7%) Info: Processes: 135 Uptime: 1d 3h 30m Memory: 3.87 GiB used: 564.1 MiB (14.2%) Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.01 Edit2: Solved | Hello, Welcome to the forum. In your previous post, you referred both to the r8168 and r8169 kernel module. Which one does your network adapter use ? It could be useful to report the output of the following commands (the inxi program must be installed) to verify your network adapter identifcation: Code: Select alllspci -vd ::0200 inxi -bnz Have you followed the Debian Bullseye (11) release notes [1] about upgrading from previous release ? Have you completed the upgrade process ? --- [1] https://www.debian.org/releases/bullseye/releasenotes |
Hello, I want to setup Tor as a proxy server and a remote computer connect to my system and use Tor. I opened "/etc/tor/torrc" file and added the following lines to it: Code: Select allSocksListenAddress (Server's internal IP address) SocksPolicy accept * Then, restarted the Tor service: Code: Select all● tor.service - Anonymizing overlay network for TCP (multi-instance-master) Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2022-12-14 09:47:38 +0330; 5min ago Process: 9759 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 9759 (code=exited, status=0/SUCCESS) Dec 14 09:47:38 Xen-aka-X3n systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)... Dec 14 09:47:38 Xen-aka-X3n systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master). After it, I opened port 9050 with the following command: Code: Select all$ sudo iptables -A INPUT -p tcp --dport 9050 -j ACCEPT On the client, I set proxy in the Internet browser, but I got the following error: Off Topic The proxy server is refusing connections Why? How to solve it? Thank you. | Hello, hack3rcon wrote: 2022-12-14 06:27 On the client, I set proxy in the Internet browser but I got the following error: Code: Select allThe proxy server is refusing connections How do you set proxy in the Internet browser ? |
On a Debian 12 system (upgraded from Debian 11) i try to run Solaar, but I get the following error: Code: Select allsolaar Traceback (most recent call last): File "/usr/local/bin/solaar", line 4, in <module> __import__('pkg_resources').run_script('solaar==1.1.9', 'solaar') ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3248, in <module> @_call_aside ^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3223, in _call_aside f(*args, **kwargs) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3261, in _initialize_master_working_set working_set = WorkingSet._build_master() ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 617, in _build_master ws.require(__requires__) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 956, in require needed = self.resolve(parse_requirements(requirements)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 815, in resolve dist = self._resolve_dist( ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 856, in _resolve_dist raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'solaar==1.1.9' distribution was not found and is required by the application A search on te internet hints that appears to be a pythin error, but I upgraded severa systems from 11 to 12 and Solaar was still working. I re-installed python3-setuptools, as suggested in the searches on the internet, but I still get the error. Unfortunately, there are not many resources for this error. | undesign wrote: 2023-06-20 17:06 It works now, so it can be closed. Happy you got sorted. I suspect it was caused by a conflict between Debian version (you removed) and the custom version previously installed. I installed the Debian version of solaar in my Debian Bookworm and worked like a charm. :wink: You can mark the thread as "Solved" manually adding the tag "[Solved]" to the subject of the first message. |
I upgraded the following MacBook Pro from Debian 11 to Debian 12: Code: Select allSystem: Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Console: pty pts/1 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Laptop System: Apple product: MacBookPro11,1 v: 1.0 serial: <filter> Mobo: Apple model: Mac-189A3D4F975D5FFC v: MacBookPro11,1 serial: <filter> UEFI: Apple v: 149.0.0.0.0 date: 09/17/2018 Battery: ID-1: BAT0 charge: 6.2 Wh (10.4%) condition: 59.7/71.5 Wh (83.4%) volts: 10.7 min: 11.3 model: DP bq20z451 status: discharging Memory: RAM: total: 7.67 GiB used: 2.73 GiB (35.6%) Array-1: capacity: 8 GiB slots: 2 EC: None max-module-size: 4 GiB note: est. Device-1: DIMM0 type: DDR3 size: 4 GiB speed: 1600 MT/s Device-2: DIMM0 type: DDR3 size: 4 GiB speed: 1600 MT/s CPU: Info: dual core model: Intel Core i5-4278U bits: 64 type: MT MCP arch: Haswell rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 800 min/max: 800/3100 cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 20801 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Apple driver: i915 v: kernel arch: Gen-7.5 bus-ID: 00:02.0 Display: server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 tty: 140x22 resolution: 2560x1600 API: OpenGL Message: GL data unavailable in console for root. Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Apple driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 Device-3: Broadcom 720p FaceTime HD Camera driver: facetimehd v: kernel bus-ID: 02:00.0 API: ALSA v: k6.1.0-9-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: n/a (root, process) Network: Device-1: Broadcom BCM4360 802.11ac Wireless Network Adapter vendor: Apple driver: wl v: kernel bus-ID: 03:00.0 IF: wlp3s0 state: up mac: <filter> Bluetooth: Device-1: Apple Bluetooth Host Controller type: USB driver: btusb v: 0.8 bus-ID: 1-3.3:6 Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 Drives: Local Storage: total: 1.13 TiB used: 467.99 GiB (40.3%) ID-1: /dev/sda vendor: Apple model: SSD SM0256F size: 233.76 GiB temp: 39 C ID-2: /dev/sdb type: USB vendor: Apple model: SD Card Reader size: 928.25 GiB Message: No optical or floppy data found. Partition: ID-1: / size: 223.88 GiB used: 10.74 GiB (4.8%) fs: btrfs dev: /dev/dm-2 mapped: vg-root label: N/A uuid: N/A ID-2: /boot size: 920.7 MiB used: 142.9 MiB (15.5%) fs: ext4 dev: /dev/sda2 label: N/A uuid: 2a68c5da-8ff7-47e0-bac7-2014bb371f6a ID-3: /boot/efi size: 569.9 MiB used: 11.6 MiB (2.0%) fs: vfat dev: /dev/sda1 label: N/A uuid: F613-0AC4 Swap: ID-1: swap-1 type: partition size: 8.38 GiB used: 0 KiB (0.0%) dev: /dev/dm-1 mapped: vg-swap label: N/A uuid: 18fc2b63-9067-4f17-8797-cf47d9ea395e Sensors: System Temperatures: cpu: 43.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 263 Uptime: 1h 6m Init: systemd target: graphical (5) Compilers: gcc: 12.2.0 Packages: 2704 Shell: Bash v: 5.2.15 inxi: 3.3.26 Prior to this, everything worked flawlessly. I even installed a kernel 6.1 (from backport) to make sure that the facetimehd module will compile successfully and the webcam will still work. It did, therefore I upgraded to Debian 12. Now, the webcam doesn't work anymore and this is all what's displayed in the logs: Code: Select allJun 19 21:27:14 macbook2014 /usr/libexec/gdm-x-session[1107]: (II) modeset(0): EDID vendor "APP", prod id 40984 Jun 19 21:27:14 macbook2014 /usr/libexec/gdm-x-session[1107]: (II) modeset(0): Printing DDC gathered Modelines: Jun 19 21:27:14 macbook2014 /usr/libexec/gdm-x-session[1107]: (II) modeset(0): Modeline "2560x1600"x0.0 268.50 2560 2608 2640 2720 1600 1603 1609 1646 +hsync -vsync (98.7 kHz eP) Jun 19 21:27:15 macbook2014 pipewire[1091]: pw.link: (44.0 -> 135.0) init -> error (ports are in error) Jun 19 21:27:15 macbook2014 wireplumber[1093]: <WpSiStandardLink:0x564031da3a20> 1 of 1 PipeWire links failed to activate Indeed, the pipewire is the cuprit for this, because it appears that interferes with the video. Cheese only displays: "There was an error playing video from the webcam". If I kill one pipewire process, then the camera shows one frame, then freezes. Apparently, there are no config files for pipewire on Debian 12. How can be set an exception, so that pipewire will no try to link with video from webcam? | undesign wrote: 2023-06-19 19:51 [..] I even installed a kernel 6.1 (from backport) to make sure that the facetimehd module will compile successfully and the webcam will still work. It did, therefore I upgraded to Debian 12. [..] Could you specify from which site you downloaded the facetimehd kernel module source ? |
When using a phone as hotspot Wi-Fi one computer can't connect. That pc can connect to another phone (always using hotspot Wi-Fi). And another pc can connect to both phones. What is wrong on the problematic pc? | Maybe it's in a bad mood. Seriously, there is no way to even guess what's going on from the information you have supplied. |
Hello all, I just built a new PC around the MSI MPG X570S EDGE MAX WIFI motherboard. It has an Intel WiFi 6 AX210 chipset. I'm running Debian 11 Bullseye ( Kernel: 5.10.0-23-amd64 ). Specifically Debian 11 LTS (stability is important for me). From the Ubuntu forums, this chipset and my kernel have a disagreement, covered in a bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=212371#c13 I've attempted the solution, to no avail. Help me Obi-WAN Ken-wifi, you're my only hope ^_^ | Hello, This wireless network interface has been reported as problematic many times. The Debian Bug Tracking System tracked this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977299. The upgrade to a more recent kernel then 5.10 version (with a working firmware) from Debian bullseye-backports is an option. The upgrade to Debian Bookworm (Debian 12) is another option according to the aforementioned bug report. |
After an upgrade from version 11 to version 12 automount doesn't work anymore: - there is no message (of any kind) in system logs - lsusb doesn't find the device - same for usb-devices Other details: The LED from the external HDD is on, so the drive is powered If I attach an USB mouse, this works. | Hi, More clues are required. Please, search in the system journal. You can use the command (as root): Code: Select alljournalctl -b You can send it as attachment to a follow-up message or use the https://forums.debian.net/app.php/pastebin/ service, if you want. |
Hey all, I installed Debian 11 with Gnome and everything is perfect except I'm not getting any notification sounds from Transmission. In other distros, I get a sound alert when a torrent finishes downloading. After Debian 12 was released a few days ago, I thought maybe this issue was not present in the new version so I installed Debian 12 but still no notification sounds in Transmission. So now I'm thinking there may be additional packages that I need to install to enable the sound notification feature? Any help is greatly appreciated, thank you! | Hello, What packages have you installed for transmission ? You can check with: Code: Select allapt -i list "transmission*" This is the configuration panel: |
Hullo! I am currently running a minimal Bookworm with no DE on a fujitsu (ca 2012) board with a usb sound card (focusrite scarlet 2i2) which i use for audio input and output. I mostly use the following applications for sound: Ardour and Puredata under Openbox; cmus for playback of files. The board itself has some kind of build in sound device and my graphics card also seems to be able to process sound via hdmi. I am attempting to default all audio input and output to usb-audio. This is the problem: Without any config of ALSA, Ardour and Puredata process output and input thorugh usb without problem; but cmus is silent, i discover this after using the other to programs for a while since i only playback files on the computer in the context of my own music production. At the point of discovering this i still ran Bullseye. Attempting to configure ALSA through the different filepaths given in documentation i find that the system lacks any such files. I try my best to implement the solutions given to set up the cards directly anyway but i fail to find any useful info on how these files should be manually set up. Having planned to migrate to Bookworm anyways i backup and make a new clean install. I find that the system still completely lacks the directories and files in ALSAs config path; i reread all documentation, the debian wiki claims that "there should already be a lot of files in /etc/alsa/conf.d" but there is no alsa directory in etc. Without the files i find it impossible to instruct ALSA to treat my soundcard correctly. So i ask is there some specific apt package of config files i shd install? Is there any guide to manually setting up said files (i am not afraid of a little scripting)? if that is of any help cat /proc/asound/cards returns: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7130000 irq 31 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 17 2 [USB ]: USB-Audio - Scarlett 2i2 USB Focusrite Scarlett 2i2 USB at usb-0000:00:14.0-6, high speed Note: i have a ~/.asoundrc set to use card 2; attempted manual setup of config file to assign usb-audio to index 0 yielded no result; with the user-specific rc file ALSA gets the wrong settings and cant use the card; since there are no config files i cannot give it correct instructions; i find very little useful documentation abt this kind of issue. | @lobra2 Nice work sorting it! Please mark topic solved so it may help other users. You can do so by editing your first post and adding prefix [Solved] from the drop-down menu. |
Hi everyone, I am running a headless server with UEFI and have the OS running on a thumb drive. My installation procedure involves setting up a VM on a my main PC and installing debian 12 onto the thumb drive with the netinstall iso. After that, I reboot the thumb drive in the VM and do the following as root: Code: Select all/usr/sbin/grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB --removable This allows the USB thumb drive to be booted on the headless server ( I cannot got to the UEFI menu to point it to grub due to it being headless). Once booted the folder structure looks like this: Code: Select allroot@homeserver:/boot/efi/EFI# ls -la total 16 drwx------ 4 root root 4096 Jun 25 14:01 . drwx------ 3 root root 4096 Jan 1 1970 .. drwx------ 2 root root 4096 Jun 25 14:01 BOOT drwx------ 2 root root 4096 Jun 25 13:55 debian root@homeserver:/boot/efi/EFI# ls -la BOOT/ total 5880 drwx------ 2 root root 4096 Jun 25 14:01 . drwx------ 4 root root 4096 Jun 25 14:01 .. -rwx------ 1 root root 108 Jun 25 14:01 BOOTX64.CSV -rwx------ 1 root root 948768 Jun 25 14:01 BOOTX64.EFI -rwx------ 1 root root 126 Jun 25 14:01 grub.cfg -rwx------ 1 root root 4199872 Jun 25 14:01 grubx64.efi -rwx------ 1 root root 849616 Jun 25 14:01 mmx64.efi root@homeserver:/boot/efi/EFI# ls -la debian/ total 5968 drwx------ 2 root root 4096 Jun 25 13:55 . drwx------ 4 root root 4096 Jun 25 14:01 .. -rwx------ 1 root root 108 Jun 25 13:55 BOOTX64.CSV -rwx------ 1 root root 87328 Jun 25 13:55 fbx64.efi -rwx------ 1 root root 126 Jun 25 13:55 grub.cfg -rwx------ 1 root root 4199872 Jun 25 13:55 grubx64.efi -rwx------ 1 root root 849616 Jun 25 13:55 mmx64.efi -rwx------ 1 root root 948768 Jun 25 13:55 shimx64.efi My questions: There are now two different grub entities in /boot/efi/EFI , which one will be edited, when I modify grub with grub-update? Which one will be updated, when I get a new grub version via apt? Is there a config file that keeps track of of the "dominant"/"main" grub install? kind regards, | It's probably best to use Code: Select all# dpkg-reconfigure grub-efi-amd64 Then select the "force installation to EFI removable loader location" option. EDIT: removed noise. |
Hi there, Today I found out that kernel 6.4 is available from experimental repo, so I immediately installed it hoping to finally being able to use Debian kernel and not compiling my own one to be able to use realtek SDIO wifi modules on my ARM boards. After spending some time I find out that rtw88 SDIO drivers that are added to kernel in version 6.4 are missing from Debian version of 6.4, even USB version of rtw88 which were added in kernel 6.3 are missing too. Here is all rtw88 modules (/lib/modules/6.4.0-0-arm64/kernel/drivers/net/wireless/realtek/rtw88) in 6.4rc7 : Code: Select allrtw88_8723d.ko rtw88_8821c.ko rtw88_8822b.ko rtw88_8822c.ko rtw88_core.ko rtw88_8723de.ko rtw88_8821ce.ko rtw88_8822be.ko rtw88_8822ce.ko rtw88_pci.ko And all of USB & SDIO variants are missing (all models in list above are PCI devices). Just created this topic to know if this is a Debian policy to for some reason do no include those devices inside Debian kernel or an old config is still being used to compile newer Debian kernels ? | symbian wrote: 2023-06-26 08:09 Just used IRC and problem solved : https://salsa.debian.org/kernel-team/li ... 5cc186a88f Glad you got sorted and thank you so much for updating the thread. It could be useful to other viewers to mark the thread as "Solved" adding the tag [Solved] at the beginning of the subject of the first message, adding a reference to kernel version and involved CPU architecture, for example: [Solved] Why rtw88 driver is not matching mainline kernel 6.4rc7 for arm64 ? Thanks :-) |
I am building a small cluster of diskless servers, that will boot Debian 12 via PXE. Initially this worked fine, the prototype system booted up and I could log in etc. However, after making a few changes (mostly installing software packages), the kernel dies in a panic, apparently because /root is mounted on a different filesystem - but how is that possible? Unfortunately I haven't found reliable instructions for how to make changes to the initramfs, otherwise I would start looking closer at what is going on in the scripts. I have read every line in the following without finding an obvious error - what have I done wrong? Code: Select all[ 0.000000] Linux version 6.1.0-9-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) [ 0.000000] Command line: BOOT_IMAGE=/debian12/boot/vmlinuz-6.1.0-9-amd64 console=tty0 console=ttyS0 ip=dhcp root=/dev/nfs ro nfsroot=192.168.50.9:/image/debian12,vers=3,nolock panic=0 ipv6.disable=1 rootwait [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [ 0.000000] signal: max sigframe size: 1776 [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000de1b6fff] usable [ 0.000000] BIOS-e820: [mem 0x00000000de1b7000-0x00000000de1fffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000de200000-0x00000000deceefff] usable [ 0.000000] BIOS-e820: [mem 0x00000000decef000-0x00000000dedeefff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000dedef000-0x00000000deeeefff] type 20 [ 0.000000] BIOS-e820: [mem 0x00000000deeef000-0x00000000def6efff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000def6f000-0x00000000def7efff] ACPI data [ 0.000000] BIOS-e820: [mem 0x00000000def7f000-0x00000000deffefff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000defff000-0x00000000df36afff] usable [ 0.000000] BIOS-e820: [mem 0x00000000df36b000-0x00000000dff6afff] type 20 [ 0.000000] BIOS-e820: [mem 0x00000000dff6b000-0x00000000dffeefff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000dffef000-0x00000000dffeffff] type 20 [ 0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000021fffffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] efi: EFI v2.70 by EDK II [ 0.000000] efi: ACPI=0xdef7e000 ACPI 2.0=0xdef7e014 SMBIOS=0xdeffd000 [ 0.000000] secureboot: Secure boot disabled [ 0.000000] SMBIOS 2.5 present. [ 0.000000] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 0.000000] Hypervisor detected: KVM [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000002] kvm-clock: using sched offset of 52329851899 cycles [ 0.000003] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [ 0.000006] tsc: Detected 2803.198 MHz processor [ 0.000464] last_pfn = 0x220000 max_arch_pfn = 0x400000000 [ 0.000470] Disabled [ 0.000471] x86/PAT: MTRRs disabled, skipping PAT initialization too. [ 0.000472] CPU MTRRs all blank - virtualized system. [ 0.000474] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC [ 0.000480] last_pfn = 0xdf36b max_arch_pfn = 0x400000000 [ 0.000533] found SMP MP-table at [mem 0x0009fff0-0x0009ffff] [ 0.000954] RAMDISK: [mem 0x359f5000-0x36cf1fff] [ 0.000958] ACPI: Early table checksum verification disabled [ 0.000961] ACPI: RSDP 0x00000000DEF7E014 000024 (v02 VBOX ) [ 0.000965] ACPI: XSDT 0x00000000DEF7D0E8 000044 (v01 VBOX VBOXFACP 00000001 01000013) [ 0.000969] ACPI: FACP 0x00000000DEF79000 0000F4 (v04 VBOX VBOXFACP 00000001 ASL 00000061) [ 0.000974] ACPI: DSDT 0x00000000DEF7A000 002353 (v02 VBOX VBOXBIOS 00000002 INTL 20200925) [ 0.000977] ACPI: FACS 0x00000000DEFFE000 000040 [ 0.000979] ACPI: APIC 0x00000000DEF78000 000054 (v02 VBOX VBOXAPIC 00000001 ASL 00000061) [ 0.000982] ACPI: SSDT 0x00000000DEF77000 00036C (v01 VBOX VBOXCPUT 00000002 INTL 20200925) [ 0.000985] ACPI: BGRT 0x00000000DEF76000 000038 (v01 INTEL EDK2 00000002 01000013) [ 0.000987] ACPI: Reserving FACP table memory at [mem 0xdef79000-0xdef790f3] [ 0.000988] ACPI: Reserving DSDT table memory at [mem 0xdef7a000-0xdef7c352] [ 0.000989] ACPI: Reserving FACS table memory at [mem 0xdeffe000-0xdeffe03f] [ 0.000989] ACPI: Reserving APIC table memory at [mem 0xdef78000-0xdef78053] [ 0.000990] ACPI: Reserving SSDT table memory at [mem 0xdef77000-0xdef7736b] [ 0.000990] ACPI: Reserving BGRT table memory at [mem 0xdef76000-0xdef76037] [ 0.001095] No NUMA configuration found [ 0.001095] Faking a node at [mem 0x0000000000000000-0x000000021fffffff] [ 0.001101] NODE_DATA(0) allocated [mem 0x21ffd5000-0x21fffffff] [ 0.001497] Zone ranges: [ 0.001498] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.001500] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] [ 0.001501] Normal [mem 0x0000000100000000-0x000000021fffffff] [ 0.001502] Device empty [ 0.001502] Movable zone start for each node [ 0.001503] Early memory node ranges [ 0.001503] node 0: [mem 0x0000000000001000-0x000000000009ffff] [ 0.001504] node 0: [mem 0x0000000000100000-0x00000000de1b6fff] [ 0.001505] node 0: [mem 0x00000000de200000-0x00000000deceefff] [ 0.001506] node 0: [mem 0x00000000defff000-0x00000000df36afff] [ 0.001506] node 0: [mem 0x0000000100000000-0x000000021fffffff] [ 0.001507] Initmem setup node 0 [mem 0x0000000000001000-0x000000021fffffff] [ 0.001801] On node 0, zone DMA: 1 pages in unavailable ranges [ 0.001821] On node 0, zone DMA: 96 pages in unavailable ranges [ 0.014594] On node 0, zone DMA32: 73 pages in unavailable ranges [ 0.014608] On node 0, zone DMA32: 784 pages in unavailable ranges [ 0.015213] On node 0, zone Normal: 3221 pages in unavailable ranges [ 0.015423] ACPI: PM-Timer IO Port: 0xb008 [ 0.015462] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23 [ 0.015465] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.015466] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.015470] ACPI: Using ACPI (MADT) for SMP configuration information [ 0.015492] smpboot: Allowing 1 CPUs, 0 hotplug CPUs [ 0.015510] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.015512] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff] [ 0.015513] PM: hibernation: Registered nosave memory: [mem 0xddb8b000-0xddba5fff] [ 0.015514] PM: hibernation: Registered nosave memory: [mem 0xde1b7000-0xde1fffff] [ 0.015514] PM: hibernation: Registered nosave memory: [mem 0xdecef000-0xdedeefff] [ 0.015515] PM: hibernation: Registered nosave memory: [mem 0xdedef000-0xdeeeefff] [ 0.015515] PM: hibernation: Registered nosave memory: [mem 0xdeeef000-0xdef6efff] [ 0.015516] PM: hibernation: Registered nosave memory: [mem 0xdef6f000-0xdef7efff] [ 0.015516] PM: hibernation: Registered nosave memory: [mem 0xdef7f000-0xdeffefff] [ 0.015517] PM: hibernation: Registered nosave memory: [mem 0xdf36b000-0xdff6afff] [ 0.015517] PM: hibernation: Registered nosave memory: [mem 0xdff6b000-0xdffeefff] [ 0.015518] PM: hibernation: Registered nosave memory: [mem 0xdffef000-0xdffeffff] [ 0.015518] PM: hibernation: Registered nosave memory: [mem 0xdfff0000-0xffbfffff] [ 0.015519] PM: hibernation: Registered nosave memory: [mem 0xffc00000-0xffffffff] [ 0.015520] [mem 0xdfff0000-0xffbfffff] available for PCI devices [ 0.015521] Booting paravirtualized kernel on KVM [ 0.015523] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns [ 0.018881] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1 [ 0.019245] percpu: Embedded 61 pages/cpu s212992 r8192 d28672 u2097152 [ 0.019270] kvm-guest: PV spinlocks disabled, single CPU [ 0.019277] Fallback order for Node 0: 0 [ 0.019279] Built 1 zonelists, mobility grouping on. Total pages: 2060113 [ 0.019280] Policy zone: Normal [ 0.019281] Kernel command line: BOOT_IMAGE=/debian12/boot/vmlinuz-6.1.0-9-amd64 console=tty0 console=ttyS0 ip=dhcp root=/dev/nfs ro nfsroot=192.168.50.9:/image/debian12,vers=3,nolock panic=0 ipv6.disable=1 rootwait [ 0.019336] Unknown kernel command line parameters "BOOT_IMAGE=/debian12/boot/vmlinuz-6.1.0-9-amd64 ip=dhcp nfsroot=192.168.50.9:/image/debian12,vers=3,nolock", will be passed to user space. [ 0.019389] random: crng init done [ 0.020809] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.021513] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.021547] mem auto-init: stack:all(zero), heap alloc:on, heap free:off [ 0.021552] software IO TLB: area num 1. [ 0.047195] Memory: 3679676K/8371908K available (14342K kernel code, 2324K rwdata, 8728K rodata, 2772K init, 17436K bss, 302392K reserved, 0K cma-reserved) [ 0.047274] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.047296] Kernel/User page tables isolation: enabled [ 0.047318] ftrace: allocating 39983 entries in 157 pages [ 0.052242] ftrace: allocated 157 pages with 5 groups [ 0.052758] Dynamic Preempt: voluntary [ 0.053059] rcu: Preemptible hierarchical RCU implementation. [ 0.053060] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=1. [ 0.053061] Trampoline variant of Tasks RCU enabled. [ 0.053061] Rude variant of Tasks RCU enabled. [ 0.053062] Tracing variant of Tasks RCU enabled. [ 0.053062] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.053063] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ 0.055711] NR_IRQS: 524544, nr_irqs: 256, preallocated irqs: 16 [ 0.055870] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.055967] Console: colour dummy device 80x25 [ 0.056094] printk: console [tty0] enabled [ 0.108900] printk: console [ttyS0] enabled [ 0.109166] ACPI: Core revision 20220331 [ 0.109472] APIC: Switch to symmetric I/O mode setup [ 0.109924] x2apic enabled [ 0.110233] Switched APIC routing to physical x2apic. [ 0.111274] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.111651] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x28680e0a5c3, max_idle_ns: 440795346756 ns [ 0.112278] Calibrating delay loop (skipped) preset value.. 5606.39 BogoMIPS (lpj=11212792) [ 0.112773] pid_max: default: 32768 minimum: 301 [ 0.116933] LSM: Security Framework initializing [ 0.117252] landlock: Up and running. [ 0.117474] Yama: disabled by default; enable with sysctl kernel.yama.* [ 0.117886] AppArmor: AppArmor initialized [ 0.118138] TOMOYO Linux initialized [ 0.118357] LSM support for eBPF active [ 0.118926] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.119412] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.120154] process: using mwait in idle threads [ 0.120283] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0 [ 0.120602] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0 [ 0.120959] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 0.121642] Spectre V2 : Mitigation: Retpolines [ 0.122007] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 0.122654] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT [ 0.123182] Speculative Store Bypass: Vulnerable [ 0.123548] MDS: Mitigation: Clear CPU buffers [ 0.137198] Freeing SMP alternatives memory: 36K [ 0.246333] smpboot: CPU0: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (family: 0x6, model: 0x8c, stepping: 0x1) [ 0.247287] cblist_init_generic: Setting adjustable number of callback queues. [ 0.247797] cblist_init_generic: Setting shift to 0 and lim to 1. [ 0.248178] cblist_init_generic: Setting shift to 0 and lim to 1. [ 0.248274] cblist_init_generic: Setting shift to 0 and lim to 1. [ 0.248274] Performance Events: unsupported p6 CPU model 140 no PMU driver, software events only. [ 0.248274] rcu: Hierarchical SRCU implementation. [ 0.248274] rcu: Max phase no-delay instances is 1000. [ 0.248380] NMI watchdog: Perf NMI watchdog permanently disabled [ 0.248780] smp: Bringing up secondary CPUs ... [ 0.249055] smp: Brought up 1 node, 1 CPU [ 0.249298] smpboot: Max logical packages: 1 [ 0.249556] smpboot: Total of 1 processors activated (5606.39 BogoMIPS) [ 0.267530] node 0 deferred pages initialised in 16ms [ 0.268196] devtmpfs: initialized [ 0.268317] x86/mm: Memory block size: 128MB [ 0.269096] ACPI: PM: Registering ACPI NVS region [mem 0xdef7f000-0xdeffefff] (524288 bytes) [ 0.269656] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.270238] futex hash table entries: 256 (order: 2, 16384 bytes, linear) [ 0.270672] pinctrl core: initialized pinctrl subsystem [ 0.271445] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.271933] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations [ 0.272378] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.273176] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.273676] audit: initializing netlink subsys (disabled) [ 0.274091] thermal_sys: Registered thermal governor 'fair_share' [ 0.274092] thermal_sys: Registered thermal governor 'bang_bang' [ 0.274450] thermal_sys: Registered thermal governor 'step_wise' [ 0.274801] thermal_sys: Registered thermal governor 'user_space' [ 0.275154] thermal_sys: Registered thermal governor 'power_allocator' [ 0.275528] cpuidle: using governor ladder [ 0.276284] audit: type=2000 audit(1687873702.187:1): state=initialized audit_enabled=0 res=1 [ 0.276781] cpuidle: using governor menu [ 0.277047] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.277486] PCI: Using configuration type 1 for base access [ 0.278444] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible. [ 0.298162] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages [ 0.298598] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page [ 0.299165] ACPI: Added _OSI(Module Device) [ 0.299415] ACPI: Added _OSI(Processor Device) [ 0.299677] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.299960] ACPI: Added _OSI(Processor Aggregator Device) [ 0.301051] ACPI: 2 ACPI AML tables successfully acquired and loaded [ 0.302109] ACPI: Interpreter enabled [ 0.302364] ACPI: PM: (supports S0 S5) [ 0.302588] ACPI: Using IOAPIC for interrupt routing [ 0.302968] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.303503] PCI: Using E820 reservations for host bridge windows [ 0.303910] ACPI: Enabled 2 GPEs in block 00 to 07 [ 0.306535] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.306931] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3] [ 0.307387] acpi PNP0A03:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI] [ 0.308138] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge. [ 0.308441] PCI host bridge to bus 0000:00 [ 0.308684] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.309081] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.309479] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.309916] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfdffffff window] [ 0.310355] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.310760] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000 [ 0.311332] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100 [ 0.312531] pci 0000:00:01.1: [8086:7111] type 00 class 0x01018a [ 0.313047] pci 0000:00:01.1: reg 0x20: [io 0xc1a0-0xc1af] [ 0.313432] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7] [ 0.313863] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io 0x03f6] [ 0.314282] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177] [ 0.314730] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io 0x0376] [ 0.315200] pci 0000:00:02.0: [15ad:0405] type 00 class 0x030000 [ 0.316530] pci 0000:00:02.0: reg 0x10: [io 0xc190-0xc19f] [ 0.320527] pci 0000:00:02.0: reg 0x14: [mem 0xe0000000-0xe3ffffff pref] [ 0.324531] pci 0000:00:02.0: reg 0x18: [mem 0xe4400000-0xe45fffff] [ 0.340566] pci 0000:00:02.0: BAR 1: assigned to efifb [ 0.340936] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] [ 0.341628] pci 0000:00:03.0: [1af4:1000] type 00 class 0x000000 [ 0.344343] pci 0000:00:03.0: reg 0x10: [io 0xc160-0xc17f] [ 0.352324] pci 0000:00:03.0: reg 0x18: [mem 0xe4606000-0xe4607fff] [ 0.364678] pci 0000:00:04.0: [80ee:cafe] type 00 class 0x088000 [ 0.368317] pci 0000:00:04.0: reg 0x10: [io 0xc140-0xc15f] [ 0.372317] pci 0000:00:04.0: reg 0x14: [mem 0xe4000000-0xe43fffff] [ 0.376326] pci 0000:00:04.0: reg 0x18: [mem 0xe4600000-0xe4603fff pref] [ 0.392304] pci 0000:00:05.0: [8086:2415] type 00 class 0x040100 [ 0.392773] pci 0000:00:05.0: reg 0x10: [io 0xc000-0xc0ff] [ 0.393140] pci 0000:00:05.0: reg 0x14: [io 0xc100-0xc13f] [ 0.393689] pci 0000:00:06.0: [106b:003f] type 00 class 0x0c0310 [ 0.396344] pci 0000:00:06.0: reg 0x10: [mem 0xe4609000-0xe4609fff] [ 0.416503] pci 0000:00:07.0: [8086:7113] type 00 class 0x068000 [ 0.417128] pci 0000:00:07.0: quirk: [io 0xb000-0xb03f] claimed by PIIX4 ACPI [ 0.417570] pci 0000:00:07.0: quirk: [io 0x4100-0x410f] claimed by PIIX4 SMB [ 0.418113] pci 0000:00:0b.0: [8086:265c] type 00 class 0x0c0320 [ 0.420334] pci 0000:00:0b.0: reg 0x10: [mem 0xe4608000-0xe4608fff] [ 0.440563] pci 0000:00:0d.0: [8086:2829] type 00 class 0x010601 [ 0.444344] pci 0000:00:0d.0: reg 0x10: [io 0xc1b8-0xc1bf] [ 0.448333] pci 0000:00:0d.0: reg 0x14: [io 0xc1c4-0xc1c7] [ 0.452331] pci 0000:00:0d.0: reg 0x18: [io 0xc1b0-0xc1b7] [ 0.456331] pci 0000:00:0d.0: reg 0x1c: [io 0xc1c0-0xc1c3] [ 0.460330] pci 0000:00:0d.0: reg 0x20: [io 0xc180-0xc18f] [ 0.464330] pci 0000:00:0d.0: reg 0x24: [mem 0xe4604000-0xe4605fff] [ 0.469144] ACPI: PCI: Interrupt link LNKA configured for IRQ 10 [ 0.469652] ACPI: PCI: Interrupt link LNKB configured for IRQ 10 [ 0.470056] ACPI: PCI: Interrupt link LNKC configured for IRQ 11 [ 0.470460] ACPI: PCI: Interrupt link LNKD configured for IRQ 11 [ 0.470999] iommu: Default domain type: Translated [ 0.471298] iommu: DMA domain TLB invalidation policy: lazy mode [ 0.472335] EDAC MC: Ver: 3.0.0 [ 0.472677] Registered efivars operations [ 0.473121] NetLabel: Initializing [ 0.473334] NetLabel: domain hash size = 128 [ 0.473599] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.473961] NetLabel: unlabeled traffic allowed by default [ 0.474303] PCI: Using ACPI for IRQ routing [ 0.474692] pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.475056] pci 0000:00:02.0: vgaarb: bridge control possible [ 0.475404] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.476275] vgaarb: loaded [ 0.476600] clocksource: Switched to clocksource kvm-clock [ 0.484682] VFS: Disk quotas dquot_6.6.0 [ 0.484997] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.485501] AppArmor: AppArmor Filesystem Enabled [ 0.485806] pnp: PnP ACPI init [ 0.486402] pnp: PnP ACPI: found 3 devices [ 0.491872] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns [ 0.492600] NET: Registered PF_INET protocol family [ 0.493253] IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.495506] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear) [ 0.496075] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.496594] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear) [ 0.497465] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear) [ 0.498056] TCP: Hash tables configured (established 65536 bind 65536) [ 0.498485] MPTCP token hash table entries: 8192 (order: 5, 196608 bytes, linear) [ 0.498946] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 0.499356] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 0.499808] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.500157] NET: Registered PF_XDP protocol family [ 0.500485] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] [ 0.500851] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] [ 0.501214] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] [ 0.501616] pci_bus 0000:00: resource 7 [mem 0xe0000000-0xfdffffff window] [ 0.502042] pci 0000:00:00.0: Limiting direct PCI/PCI transfers [ 0.503417] PCI: CLS 0 bytes, default 64 [ 0.503708] Trying to unpack rootfs image as initramfs... [ 0.508452] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 0.508842] software IO TLB: mapped [mem 0x00000000d7fbe000-0x00000000dbfbe000] (64MB) [ 0.509338] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x28680e0a5c3, max_idle_ns: 440795346756 ns [ 0.509928] clocksource: Switched to clocksource tsc [ 0.510249] platform rtc_cmos: registered platform RTC device (no PNP device found) [ 0.512512] Initialise system trusted keyrings [ 0.512787] Key type blacklist registered [ 0.516463] workingset: timestamp_bits=36 max_order=21 bucket_order=0 [ 0.517629] zbud: loaded [ 0.517939] integrity: Platform Keyring initialized [ 0.518229] integrity: Machine keyring initialized [ 0.518512] Key type asymmetric registered [ 0.518755] Asymmetric key parser 'x509' registered [ 1.704651] Freeing initrd memory: 19444K [ 1.710372] alg: self-tests for CTR-KDF (hmac(sha256)) passed [ 1.710800] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) [ 1.711286] io scheduler mq-deadline registered [ 1.712100] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 1.712707] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.713194] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 1.714044] Linux agpgart interface v0.103 [ 1.714366] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug. [ 1.714960] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 [ 1.715763] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.716081] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.716481] mousedev: PS/2 mouse device common for all mice [ 1.716945] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [ 1.718252] rtc_cmos rtc_cmos: registered as rtc0 [ 1.718656] rtc_cmos rtc_cmos: setting system clock to 2023-06-27T13:47:30 UTC (1687873650) [ 1.719362] rtc_cmos rtc_cmos: alarms up to one day, 114 bytes nvram [ 1.719842] intel_pstate: CPU model not supported [ 1.720155] ledtrig-cpu: registered to indicate activity on CPUs [ 1.720606] efifb: probing for efifb [ 1.720828] efifb: framebuffer at 0xe0000000, using 1920k, total 1920k [ 1.721217] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 1.721569] efifb: scrolling: redraw [ 1.721784] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 1.722997] Console: switching to colour frame buffer device 100x37 [ 1.723615] fb0: EFI VGA frame buffer device [ 1.731430] IPv6: Loaded, but administratively disabled, reboot required to enable [ 1.731923] mip6: Mobile IPv6 [ 1.732105] mip6: mip6_init: can't add xfrm type(destopt) [ 1.732446] NET: Registered PF_PACKET protocol family [ 1.732781] mpls_gso: MPLS GSO support [ 1.733086] IPI shorthand broadcast: enabled [ 1.733377] sched_clock: Marking stable (1676094022, 56340408)->(1735297504, -2863074) [ 1.733972] registered taskstats version 1 [ 1.734229] Loading compiled-in X.509 certificates [ 1.745644] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [ 1.746317] Loaded X.509 cert 'Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f' [ 1.747874] zswap: loaded using pool lzo/zbud [ 1.748391] Key type .fscrypt registered [ 1.748792] Key type fscrypt-provisioning registered [ 1.751801] Key type encrypted registered [ 1.752240] AppArmor: AppArmor sha1 policy hashing enabled [ 1.752790] ima: No TPM chip found, activating TPM-bypass! [ 1.753280] ima: Allocated hash algorithm: sha256 [ 1.753719] ima: No architecture policies found [ 1.754149] evm: Initialising EVM extended attributes: [ 1.754606] evm: security.selinux [ 1.754948] evm: security.SMACK64 (disabled) [ 1.755347] evm: security.SMACK64EXEC (disabled) [ 1.755765] evm: security.SMACK64TRANSMUTE (disabled) [ 1.756216] evm: security.SMACK64MMAP (disabled) [ 1.756647] evm: security.apparmor [ 1.756981] evm: security.ima [ 1.757286] evm: security.capability [ 1.757623] evm: HMAC attrs: 0x1 [ 1.820082] Freeing unused decrypted memory: 2036K [ 1.821302] Freeing unused kernel image (initmem) memory: 2772K [ 1.821696] Write protecting the kernel read-only data: 26624k [ 1.822400] Freeing unused kernel image (text/rodata gap) memory: 2040K [ 1.822992] Freeing unused kernel image (rodata/data gap) memory: 1512K [ 1.860332] x86/mm: Checked W+X mappings: passed, no W+X pages found. [ 1.861389] x86/mm: Checking user space page tables [ 1.897363] x86/mm: Checked W+X mappings: passed, no W+X pages found. [ 1.898406] Run /init as init process Loading, please wait... Starting systemd-udevd version 252.6-1 [ 1.953573] ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 1.956421] ACPI: battery: Slot [BAT0] (battery present) [ 1.971920] ACPI: bus type USB registered [ 1.973412] piix4_smbus 0000:00:07.0: SMBus Host Controller at 0x4100, revision 0 [ 1.977847] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input2 [ 2.013349] virtio_net virtio0 enp0s3: renamed from eth0 [ 2.014515] usbcore: registered new interface driver usbfs [ 2.014945] usbcore: registered new interface driver hub [ 2.015344] usbcore: registered new device driver usb [ 2.019092] ehci-pci 0000:00:0b.0: EHCI Host Controller [ 2.020070] ehci-pci 0000:00:0b.0: new USB bus registered, assigned bus number 1 [ 2.023231] ehci-pci 0000:00:0b.0: irq 19, io mem 0xe4608000 [ 2.036412] ehci-pci 0000:00:0b.0: USB 2.0 started, EHCI 1.00 [ 2.037434] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 2.037879] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.038326] usb usb1: Product: EHCI Host Controller [ 2.038679] usb usb1: Manufacturer: Linux 6.1.0-9-amd64 ehci_hcd [ 2.039089] usb usb1: SerialNumber: 0000:00:0b.0 [ 2.039542] hub 1-0:1.0: USB hub found [ 2.039852] hub 1-0:1.0: 12 ports detected [ 2.041207] ohci-pci 0000:00:06.0: OHCI PCI host controller [ 2.041549] ohci-pci 0000:00:06.0: new USB bus registered, assigned bus number 2 [ 2.042068] ohci-pci 0000:00:06.0: irq 22, io mem 0xe4609000 [ 2.101445] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01 [ 2.104979] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.106651] usb usb2: Product: OHCI PCI host controller [ 2.107931] usb usb2: Manufacturer: Linux 6.1.0-9-amd64 ohci_hcd [ 2.109466] usb usb2: SerialNumber: 0000:00:06.0 [ 2.111212] hub 2-0:1.0: USB hub found [ 2.111577] hub 2-0:1.0: 12 ports detected Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done. Begin: Running /scripts/nfs-premount ... done. Begin: Waiting up to 180 secs for any network device to become available ... done. IP-Config: enp0s3 hardware address 08:00:27:ae:a4:19 mtu 1500 DHCP [ 2.208560] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3 [ 2.500435] usb 2-1: new full-speed USB device number 2 using ohci-pci [ 2.901944] usb 2-1: New USB device found, idVendor=80ee, idProduct=0021, bcdDevice= 1.00 [ 2.903087] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 2.903560] usb 2-1: Product: USB Tablet [ 2.903901] usb 2-1: Manufacturer: VirtualBox [ 2.919989] hid: raw HID events driver (C) Jiri Kosina [ 2.930373] usbcore: registered new interface driver usbhid [ 2.930722] usbhid: USB HID core driver [ 2.932133] input: VirtualBox USB Tablet as /devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/0003:80EE:0021.0001/input/input4 [ 2.933381] hid-generic 0003:80EE:0021.0001: input,hidraw0: USB HID v1.10 Mouse [VirtualBox USB Tablet] on usb-0000:00:06.0-1/input0 IP-Config: no response after 2 secs - giving up IP-Config: enp0s3 hardware address 08:00:27:ae:a4:19 mtu 1500 DHCP IP-Config: enp0s3 complete (dhcp from 192.168.50.9): address: 192.168.50.93 broadcast: 192.168.50.255 netmask: 255.255.255.0 gateway: 192.168.50.1 dns0 : 192.168.50.9 dns1 : 0.0.0.0 domain : comind.io rootserver: 192.168.50.9 rootpath: filename : grubx64.efi [ 3.265470] FS-Cache: Loaded [ 3.294240] RPC: Registered named UNIX socket transport module. [ 3.295260] RPC: Registered udp transport module. [ 3.295607] RPC: Registered tcp transport module. [ 3.295989] RPC: Registered tcp NFSv4.1 backchannel transport module. done. Begin: Running /scripts/nfs-bottom ... done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: Invalid cross-device link mount: mounting /dev on /root/dev failed: Invalid cross-device link done. mount: mounting /sys on /root/sys failed: Invalid cross-device link mount: mounting /proc on /root/proc failed: Invalid cross-device link /init: line 331: can't open /root/dev/console: Invalid cross-device link [ 3.471814] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 3.475441] CPU: 0 PID: 1 Comm: init Not tainted 6.1.0-9-amd64 #1 Debian 6.1.27-1 [ 3.477195] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 3.478180] Call Trace: [ 3.478472] <TASK> [ 3.478732] dump_stack_lvl+0x44/0x5c [ 3.479078] panic+0x118/0x2ed [ 3.479385] do_exit.cold+0x15/0x15 [ 3.479717] ? fpregs_assert_state_consistent+0x22/0x50 [ 3.480130] ? exit_to_user_mode_prepare+0x40/0x1d0 [ 3.480530] do_group_exit+0x2d/0x80 [ 3.480859] __x64_sys_exit_group+0x14/0x20 [ 3.481201] do_syscall_64+0x5b/0xc0 [ 3.481526] ? fpregs_assert_state_consistent+0x22/0x50 [ 3.481931] ? exit_to_user_mode_prepare+0x40/0x1d0 [ 3.482320] ? syscall_exit_to_user_mode+0x17/0x40 [ 3.482707] ? do_syscall_64+0x67/0xc0 [ 3.483037] ? fpregs_assert_state_consistent+0x22/0x50 [ 3.483446] ? exit_to_user_mode_prepare+0x40/0x1d0 [ 3.483834] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 3.484228] RIP: 0033:0x7f54a88a5209 [ 3.484556] Code: 00 4c 8b 05 f9 db 0f 00 be e7 00 00 00 ba 3c 00 00 00 eb 12 0f 1f 44 00 00 89 d0 0f 05 48 3d 00 f0 ff ff 77 1c f4 89 f0 0f 05 <48> 3d 00 f0 ff ff 76 e7 f7 d8 64 41 89 00 eb df 0f 1f 80 00 00 00 [ 3.485897] RSP: 002b:00007ffdb9af02f8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 [ 3.486385] RAX: ffffffffffffffda RBX: 00007ffdb9af1f04 RCX: 00007f54a88a5209 [ 3.486889] RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 [ 3.487394] RBP: 0000000000000001 R08: ffffffffffffff80 R09: 0000557f007e1200 [ 3.487886] R10: a89baab0b693edfd R11: 0000000000000202 R12: 0000000000000000 [ 3.488392] R13: 00007ffdb9af06d0 R14: 0000000000000000 R15: 00007f54a89f8020 [ 3.488888] </TASK> [ 3.489159] Kernel Offset: 0x8a00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 3.489936] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]--- | Hello, fargris wrote: 2023-06-27 15:21 I am building a small cluster of diskless servers, that will boot Debian 12 via PXE. Initially this worked fine, the prototype system booted up and I could log in etc. What are the manual or the instructions you followed to set up the prototype ? |
Internet was working fine for a couple of days after upgrading smoothly to Bookworm. Now, I can ping IPs such as 1.1.1.1 and 8.8.8.8 without issue but attempting to ping, for example, google.com or trying to use a web browser instantly fails. It seems that the issue is a broken symlink cause by a systemd update, but I have not found a clear way to fix it. Any help is appreciated. Thanks! | Can you do the folling in a terminal please and give us the results? Code: Select allls -l /etc/resolv.conf cat /etc/resolv.conf |
Hello all, I have to use IPv6 to access my debian 10 server using SSH. Here is the current output of iptables-save, which works still well in IPv4 Code: Select all# Generated by iptables-save v1.6.0 on Wed Apr 1 15:00:13 2020 *filter :INPUT DROP [125:9610] :FORWARD DROP [0:0] :OUTPUT ACCEPT [511:77841] -A INPUT -i lo -j ACCEPT -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 22 -j ACCEPT COMMIT # Completed on Wed Apr 1 15:00:13 2020 I try to do something similar with ip6tables, just by copying them. Here is the output of ip6tables-save Code: Select all# Generated by xtables-save v1.8.2 on Mon Mar 27 21:11:49 2023 *filter :INPUT DROP [125:9610] :FORWARD DROP [0:0] :OUTPUT ACCEPT [511:77841] -A INPUT -i lo -j ACCEPT -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 22 -j ACCEPT COMMIT # Completed on Mon Mar 27 21:11:49 2023 When I restore the ip6tables configuration with ip6tables-restore - new incoming ssh connections are not possible - already active ssh connections work for ~10 secconds, then are freezed, until I run iptables -P INPUT ACCEPT Obviously, ESTABLISHED connections are not accepted in IPv6. Do you folks have any idea why ? Thanks | Well, I've finally found the solution. ICMPv6 has to be accepted in the INPUT chain. This works as intended : Code: Select all# Generated by xtables-save v1.8.2 on Mon Mar 27 22:23:13 2023 *filter :INPUT DROP [394:33816] :FORWARD DROP [0:0] :OUTPUT ACCEPT [1121:205310] -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 22 -j ACCEPT COMMIT # Completed on Mon Mar 27 22:23:13 2023 See also https://serverfault.com/questions/66759 ... of-packets and https://serverfault.com/questions/41032 ... p-for-ipv6 |
Hello, 6.0 Kernel (amd64 from Bullseye backports) has entered into EOL state (by kernel.org), so no longer supported. Is it worth to give a try and install 6.1 from testing/unstable repo? I've read there are essential improvements in 6.1 (memory management etc). Is there any experience/knowledge about compatibility problems (I'm using compiled Samba ADDC)? Or should I better waiting for Bookworm release? Just a humble question to spare some time, not because I'm too lazy . Thanks in advance, Leslie | There's a 6.1 kernel in bullseye-backports already. It's unsigned so won't work with Secure Boot, but I'd guess a signed one would be available shortly. https://packages.debian.org/bullseye-ba ... 4-unsigned |
Hey there; I was performing routine port check: Code: Select allNetid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process udp UNCONN 0 0 0.0.0.0:51820 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:631 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* udp UNCONN 0 0 0.0.0.0:40175 0.0.0.0:* udp UNCONN 0 0 [::]:51820 [::]:* udp UNCONN 0 0 [::]:60038 [::]:* udp UNCONN 0 0 [::]:5353 [::]:* tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:* Code: Select allActive Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:51232 0.0.0.0:* udp 0 0 0.0.0.0:51820 0.0.0.0:* udp 0 0 0.0.0.0:631 0.0.0.0:* udp 0 0 0.0.0.0:5353 0.0.0.0:* udp 0 0 0.0.0.0:40175 0.0.0.0:* udp6 0 0 :::51820 :::* udp6 0 0 :::60038 :::* udp6 0 0 :::5353 :::* I tried to identify (using google) the app o daemon associate with some ports, but others it's imposible to said what applications is behind. it is possible to find out the application or process that opens those ports? I'm using a firewall to denied incoming connections. | Hello, sakurita wrote: 2023-03-16 17:46 it is possible to find out the application or process that opens those ports? You can use the following command from net-tools package: Code: Select allnetstat -tcup |
Hello, I have a freshly installed Debian on my Server and now i ran into some issues. - The Server ist attached to a Network Switch, which is connected to my Laptop and my Router. Thanks to DHCP i have an internet connection on interface eno1. But now I want to add another network interface on the Server with a static ip, to make a local network with my laptop and my server while keeping the server connected to the internet via the switch+Router with its configured eno1 network interface. When i just add another interface e.g. eno2 in /etc/network/interfaces like this: auto eno2 iface eno2 inet static address 192.168.2.1 netmask 255.255.255.0 it just gives me an error after restarting networking.service that the interface eno2 is unknown. How can i add multiple network interfaces separated from each other on the debian system? ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- other question would be: How can i assign a static ipv6 adress to my server, so it is reachable from the internet? Hope somebody can help me, thank you! | karottenkopf wrote: 2023-01-27 10:58 I want to add another network interface on the Server with a static ip Do you want to configure a second existing physical network interface (if the server has two ethernet ports), or add a static IP address to eno1, or create IEEE802.1q tagged VLAN interfaces on eno1 (assuming the switch supports IEEE802.1q) ? karottenkopf wrote: 2023-01-27 10:58 How can i assign a static ipv6 adress to my server Code: Select alliface eno1 inet6 static address xxx:xxx/nn gateway xxx:xxx For details, see man interfaces. |
Need guru help to solve this. Newish to linux and really can't grasp the way users and groups work, or why the script in fstab will add a SMB drive, but does not mount the drive. Using a Pi400 with the Raspberry Debian OS. I have a NAS with SMB shared folders that I access from the Pi. After boot, I manually run a bash script ( using a shortcut on the desktop ) that executes : Code: Select allsudo mount.cifs //192.168.x.xxx/GailOnlinBackup /home/gail/NASdrive -o credentials=/home/gail/.smbcreds,noperm This works perfectly. Connects to the NAS, mounts the folder and adds a desktop link / icon for the SMB Folder. I can open the folder and access the files. Now I want to have the mount run at boot ( instead of having to start and execute with the desktop icon ) used Terminal, changed to the etc folder, and then Code: Select allsudo nano fstab line added to fstab file : Code: Select all192.168.x.xxx/GailOnlinBackup /home/gail/NASdrive cifs vers=3.0,credentials=/home/gail/.smbcreds This is where I get stuck. On reboot, the NASdrive appears in the list of drives in the File Manager, but if I try and select the drive, I can't see the files in the folder - Permission Denied. The error it throws is : mount:cifs Permission Denied also tried changing the fstab code to this, but same result : Code: Select all//192.168.x.xxx/GailOnlinBackup /home/gail/NASdrive cifs vers=3.0,credentials=/home/gail/.smbcreds,iocharset=utf8,gid=0,uid=0,file_mode=0777,dir_mode=0777 0 0 Only if I use Terminal and run : Code: Select allsudo mount -a then I can access the folders and see the files So it appears that the line in fstab connects and lists the SMB shared folder, but does not mount it until I run sudo mount -a Static hostname: raspberrypi Icon name: computer Machine ID: xx Boot ID: xx Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.19-v8+ Architecture: arm64 | update : partially solved. After a long search, I can across info that indicates the fstab on the pi is run before the network connection is established, so I guess the drive is added, but not mounted / populated as there is no network connection at the time the fstab file executes. Changed the fstab line to : Code: Select all//192.168.x.xxx/GailOnlinBackup/ /home/gail/NASdrive cifs _netdev,uid=gail,gid=gail,credentials=/home/gail/.smbcreds,x-systemd.automount 0 0 Now it connects and mounts the drive. Only issue is that it adds 2 icons to the desktop - 1 appears to be a Drive icon, and the other a Cloud Folder icon. Selecting either icon opens the File Manager at the Cloud Folder location ( /home/gail/NASdrive ) Is there a way to have only 1 icon added to the desktop by the fstab script ? |
In terminal, I can use the following to copy files to a mounted smb folder on a NAS : Code: Select allsudo cp ./.mozilla/firefox/s0mwxsxv.default-esr/*.* /home/gail/NASdrive/FirefoxProfileBackup/ But, as soon as I add this to a script file ( 'FoxBackup.sh' ), and try run with either : FoxBackup.sh or sudo FoxBackup.sh it says :Code: Select all sudo: FoxBackup.sh: command not found What am I missing that needs to be changed when running the script from a file ? | Assuming the script is in your CWD, try './FoxBackup.sh' Note the preceding path, you need to include path to call any executable not in the search directories defined in $PATH (/bin/, /usr/bin/, /usr/local/bin/ etc.). You will also need to set the executable permission bit on that script (chmod +x), or call the appropriate interpreter explicitly, e.g. 'sh ./FoxBackup.sh'. |
So whenever I log into my system, I have an issue with wifi, and it centers around my /etc/resolv.conf file. It reads as such: # Generated by NetworkManager nameserver 127.0.0.1 options edns0 trust-ad However, when I edit that file and replace "edns0" with "wlan0" and save it, wifi works. However, every time I restart my system, "wlan0" is replaced by "edns0". How do I keep my system from changing "wlan0" back to "edns0"? Also, I am developing a custom Debian Sid distro using Cubic. Everything works, however I want to ensure that my /etc/resolv.conf file writes "options wlan0 trust-ad" instead of "options edns0 trust-ad". How do I go about fixing this? If I can get this issue fixed, then I should be able to release the distro. I develop the Zoonity Desktop project, and I am just about finished with ZoonityLite based on Debian Sid. (I am moving away from the Ubuntu base.) | If this is for a 'default' in the 'distro' that is intended to always work the same on every install then a concern is whether "edns0" is a stable first state, and it's not. beardogg0524 wrote: 2022-12-28 17:37 How do I keep my system from changing "wlan0" back to "edns0"? As a particular install solution you can create a link file in /etc/systemd/network/ to rename the device in various ways. I think wlan0 is a kernel name, if so you may be able to use NamePolicy=onboard kernel |
Hi Everyone, I am forwarding my syslog from my Synology nas to my debian 11.x server , but I have figured out that the message sent from the NAS is stored in both syslog and messages log file. /var/log/syslog -> <14>Apr 14 13:36:14 nas Connection: User [david] from [HOMEPC(192.168.71.70)] via [CIFS(SMB3)] accessed shared folder [Backup]. /var/log/messages -> <14>Apr 14 13:36:14 nas Connection: User [david] from [HOMEPC(192.168.71.70)] via [CIFS(SMB3)] accessed shared folder [Backup]. /var/log/syslog -> <14>Apr 14 13:16:32 nas System Test message from Synology Syslog Client from (51.154.21.243) /var/log/messages -> <14>Apr 14 13:16:32 nas System Test message from Synology Syslog Client from (51.154.21.243) Is this a standard/normal way receiving and storing logs, or is there ways to limit in which log file it is stored. The main issue is that I am crunching logs via LogScale from Crowdstrike (https://www.crowdstrike.com/products/ob ... -logscale/) , and the logs appears twice (in both log file). Thanks, David | Hello, How do you forward system logs ? What are configurations you set up ? |
Hello, these are the information about the wifi card in my laptop HP ProBook 455 Code: Select alllspci | grep Ethernet 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) I installed the firmware and the correct driver (I hope!) by: Code: Select allsudo apt install firmware-realtek sudo apt install r8168-dkms and everything went fine (apparently) The following is my actual situation as per Code: Select allsudo lspci -v and here it is a relevant (I hope) extract of the standard output of the previous command Code: Select all01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 9 I/O ports at 3000 [size=256] Memory at fb604000 (64-bit, non-prefetchable) [size=4K] Memory at fb600000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-ff-9f-78-3b-b1-a8 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8168 Kernel modules: r8168 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 Subsystem: Hewlett-Packard Company Device 88e3 Flags: fast devsel, IRQ 255, IOMMU group 10 I/O ports at 2000 [disabled] [size=256] Memory at fb500000 (64-bit, non-prefetchable) [disabled] [size=1M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-88-52-01 Capabilities: [158] Latency Tolerance Reporting Capabilities: [160] L1 PM Substates The problem is that I can't see listed a menu 'wifi' in the gnome interface and neither it seems working the wifi, whilst on the other hand the ethernet cable connection is working fine (I can get perfectly through the net) Any suggestion for sorting out the problem? I'm currently running Debian 5.10.162-1 (2023-01-21) Sorry but I'm completely new to this kind of issues thanks | lspci | grep Ethernet ? What is the output of: lspci |grep Network? |
Hi, this is my first time using Debian. I'm a new linux user that enjoy a lot Debian philosophy, but has only basic knowledge. I ask you kindly to give me detailed orientations if possible. My problem: Sometimes, my notebook get stuck and won't boot. Last time i waited 10 minutes and had to reboot. It doesn't happen all the time. I would say 3 out of 10 boots. I don't know how to provide proper information, but i tried to take a pic of my screen [https://imgur.com/a/wl8hUYZ] during the problem and added some commands outputs here... lspci Code: Select alljoao@debian:~$ lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Processor Host Bridge/DRAM Registers [Coffee Lake H] (rev 07) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10) 00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) 00:1d.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #14 (rev f0) 00:1d.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 (rev f0) 00:1e.0 Communication controller: Intel Corporation Cannon Lake PCH Serial IO UART Host Controller (rev 10) 00:1f.0 ISA bridge: Intel Corporation HM470 Chipset LPC/eSPI Controller (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1) 06:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5763 (rev 01) 07:00.0 Non-Volatile memory controller: ADATA Technology Co., Ltd. Device 33f8 (rev 03) 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25) 09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) And i also tried a journalctl -b -1 -p3 to list the last boot problem and it is always related to this : Code: Select allroot@debian:~# journalctl -b -1 -p3 -- Journal begins at Wed 2023-02-22 04:17:17 -03, ends at Tue 2023-03-07 20:00:51 -03. -- mar 07 19:32:56 debian kernel: integrity: Problem loading X.509 certificate -65 mar 07 19:32:56 debian kernel: integrity: Problem loading X.509 certificate -65 mar 07 19:32:56 debian kernel: mar 07 19:32:56 debian kernel: iwlwifi 0000:09:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) mar 07 19:32:56 debian kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware mar 07 19:32:59 debian bluetoothd[828]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. mar 07 19:32:59 debian bluetoothd[828]: sap-server: Operation not permitted (1) mar 07 19:32:59 debian bluetoothd[828]: Failed to set mode: Blocked through rfkill (0x12) mar 07 19:34:56 debian systemd[1]: Failed to start Helper to synchronize boot up for ifupdown. mar 07 19:35:57 debian systemd-udevd[359]: wlan0: Worker [383] processing SEQNUM=3676 killed mar 07 19:36:53 debian kernel: INFO: task kworker/u16:2:53 blocked for more than 120 seconds. mar 07 19:36:53 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:36:53 debian kernel: INFO: task kworker/3:2:192 blocked for more than 120 seconds. mar 07 19:36:53 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:36:53 debian kernel: INFO: task systemd-udevd:383 blocked for more than 120 seconds. mar 07 19:36:53 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:36:53 debian kernel: INFO: task NetworkManager:706 blocked for more than 120 seconds. mar 07 19:36:53 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:36:53 debian kernel: INFO: task modprobe:766 blocked for more than 120 seconds. mar 07 19:36:53 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:38:54 debian kernel: INFO: task kworker/u16:2:53 blocked for more than 241 seconds. mar 07 19:38:54 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:38:54 debian kernel: INFO: task kworker/3:1:78 blocked for more than 120 seconds. mar 07 19:38:54 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:38:54 debian kernel: INFO: task kworker/3:2:192 blocked for more than 241 seconds. mar 07 19:38:54 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:38:54 debian kernel: INFO: task systemd-udevd:383 blocked for more than 241 seconds. mar 07 19:38:54 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:38:54 debian kernel: INFO: task NetworkManager:706 blocked for more than 241 seconds. mar 07 19:38:54 debian kernel: Tainted: P OE 5.10.0-21-amd64 #1 Debian 5.10.162-1 mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mar 07 19:43:18 debian kernel: watchdog: watchdog0: watchdog did not stop! | You probably need firmware, at least intel-microcode and firmware-iwlwifi for starters. The easy way (when it works) is to install isenkram and run Code: Select allisenkram-autoinstall-firmware It sometimes doesn't detect all required firmware so let us know how it goes. |
I have mariadb installed and can successfully start it using the traditional mysql_safe route. In attempting to make it start automatically on boot up systemctl gave the message "sudo systemctl status mariadb.service" and, indeed, the systemd directory does not have the file or any likely variant of name. Can anyone tell me what needs to go into such a file or perhaps post a copy of it; I would expect to be able to do such things as correct any paths that might differ in my environment. | Hello, Michael Farthing wrote: 2023-04-27 14:22 In attempting to make it start automatically on boot up systemctl gave the message Code: Select allsudo systemctl status mariadb.service and, indeed, the systemd directory does not have the file or any likely variant of name. What is the complete output of the previous command ? That's quite strange that a service file disappears. Are you sure they are missing ? You can check with the command: Code: Select allls -la /lib/systemd/system/maria* Michael Farthing wrote: 2023-04-27 14:22 Thanks, but yes I had read that. The difficulty is that it is concerned mainly with optional tweaks and assumes there is an existing file that is being modified. What is your Debian version ? You can check with: Code: Select allcat /etc/debian_version How did you installed mariadb server package ? Is was installed by apt ? You can check with: Code: Select allapt policy "mariadb-server*" Michael Farthing wrote: 2023-04-27 14:22 My problem is that I have lost the entire file. What's your init system ? Are you using systemd or other init system ? You can check with: Code: Select allls -la /sbin/init Michael Farthing wrote: 2023-04-27 14:22 There is also a reference to a supplied script which is supposed to create the systemd configuration file from the mysqld_safe, but that also has failed to work Can you supply the full output of the script from the link supplied by @kent_dorfman766 ? Anyway, you can get *.service files extracting them from the binary package (for Debian Bullseye), with the following commands: Code: Select allmkdir temporary-mariadb-server cd temporary-mariadb-server apt download mariadb-server-10.5 dpkg --extract mariadb-server-10.5*.deb ./ The *.service files will be in ./temporary-mariadb-server/lib/systemd/system/ |
Here is the output from xrandr on my machine Code: Select allScreen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 698mm x 392mm 1920x1080 60.00*+ 59.94 50.00 60.05 60.00 50.04 1680x1050 59.95 1600x900 60.00 1440x900 59.89 1440x576 50.00 1440x480 59.94 1400x1050 59.98 1280x1024 75.02 60.02 1280x960 60.00 1280x720 60.00 59.94 50.00 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 56.25 720x576 50.00 720x480 59.94 640x480 75.00 72.81 59.94 59.93 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) If I use "xrandr --output HDMI-0 --primary", it works for that session. However the next time I login, HDMI-0 is no longer the primary monitor (Note, HDMI-0 is the only monitor connected), so the system has no primary monitor at all. I would like HDMI-0 to be set as the primary monitor every time I log in. I have tried: adding a file to /etc/X11/Xsession.d called 60custom_xrandr-settings containing only the line "xrandr --output HDMI-0 --primary" adding the above line to ~/.xsessionrc Neither of these have worked. | You could try launching a script (or simply the command itself) via XFCE4 Session and Startup. It should work since I have a similar command in it. I don't quite well remember how I exactly did it, but if I'm right this should create a file in ~/.config/autostart/ Code: Select all$> cat ~/.config/autostart/DualMonitorsSwitch-nofun.desktop [Desktop Entry] Encoding=UTF-8 Version=0.9.4 Type=Application Name=DualMonitorsSwitch-nofun Comment=switches on/off secondary monitor according to last session state Exec=/home/nofun/.nofun/xfce4-DualMonitorsSwitch/DualMonitorsSwitch lastState OnlyShowIn=XFCE; StartupNotify=false Terminal=false Hidden=false Notice the OnlyShowIn=XFCE; line. Since there is no such field in XFCE4 Session and Startup, I believe that I manually added it to this file. For completeness, here is the script involved: Code: Select all#!/usr/bin/env bash ### DualMonitorsSwitch - 2017 - switches on/off secondary monitor ### on/off : on demand switch (see ~/.local/bin/gimp) ### lastState : suitable to automagically recover last session's state ### * : inverts state. Suitable for one-single-button manual switch DESKENTRY="/home/nofun/.config/xfce4/panel/launcher-34/15047360296.desktop" STATE="/home/nofun/.nofun/xfce4-DualMonitorsSwitch/State" [[ $(xrandr --current | grep -A1 "HDMI-2 connected 1280x1024" |tail -n1 |grep "\*+") ]] && CURRENT="on" || CURRENT="off" f_off () { xrandr --output HDMI-2 --off NEWDESKENTRY="$(sed 's/^Icon=.*$/Icon=\/home\/nofun\/.nofun\/xfce4-DualMonitorsSwitch\/dualMonitorOff.png/' "$DESKENTRY")" echo "$NEWDESKENTRY" > "$DESKENTRY"; echo "off" > "$STATE" } f_on () { xrandr --output HDMI-2 --right-of HDMI-3 --auto NEWDESKENTRY="$(sed 's/^Icon=.*$/Icon=\/home\/nofun\/.nofun\/xfce4-DualMonitorsSwitch\/dualMonitorOn.png/' $DESKENTRY)" echo "$NEWDESKENTRY" > "$DESKENTRY"; echo "on" > "$STATE" } case "$1" in off) [[ "$CURRENT" = "on" ]] && f_off;; on) [[ "$CURRENT" = "off" ]] && f_on;; lastState) LASTSTATE="$(cat $STATE)" [[ "$LASTSTATE" = "off" ]] && { sleep 1; f_off; } [[ "$LASTSTATE" = "on" ]] && { sleep 1; f_on; };; *) [[ "$CURRENT" = "on" ]] && f_off || f_on;; esac |
Hallo!I am running Debian 11.7 64 bit I wanted to create a cron job to run a script that opens a specific TXT file that reminds me to perform a task everyday at a specific time lets say 2.15 PM daily. I have created a script called linuxtd.sh that opens a certain textfile called dr.txt and in that dr.txt there is a sentence that reminds me to perform a certain task everyday at 2.15 PM. The linuxtd.sh file is as below Code: Select all#!/bin/bash gedit /data/scripts/dr.txt If I run the linuxtd.sh file from terminal,the dr.txt file opens from gedit and I can see the sentence that reminds me to perform a specific task. Now I wanted the linuxtd.sh to run as a cronjob daily at 2.15 PM to open the dr.txt from gedit to remind me to perform a task. I have edited the crontab as below Code: Select all15 14 * * * /data/scripts/linuxtd.sh I assumed with this configuration the cronjob would succesfully run at 2.15 PM and the dr.txt file would open from gedit but unfortunately the dr.txt file isnt opening at 2.15 PM.Initially I assumed that the cronjob wasnt running but having run the command below I can see the cronjob did run but never opened the dr.txt file Code: Select all# grep "linuxtd.sh" /var/log/syslog Apr 30 14:15:01 joey-xxx CRON[21801]: (root) CMD (/data/scripts/linuxtd.sh) How can I successfully configure the cronjob to open the dr.txt file. Please assist.Thanks in advance | the first thing I would try is replace gedit with /fullpath/gedit I always use commands with full path in scripts The second thing is add a logfile and write commands from within the script to the logfile. So I can see exactly where it goes wrong. |
As in title, I removed the pinctrl_elkhartlake kernel module with Code: Select allmodprobe -r pinctrl_elkhartlake (in hindsight I should have probably blacklisted), as it was interfering with the ability to use the OS. In any case, for testing purposes I wish to reinsert this mod into the kernel. How do I do it? Running Code: Select allmodprobe pinctrl_elkhartlake does not seem to do anything. | Hello, You can check if it is loaded by the kernel using the command lsmod [1]: Code: Select alllsmod | grep pinctrl_elkhartlake If it is loaded, it appear an output like: Code: Select allpinctrl_elkhartlake 28672 0 --- [1] https://manpages.debian.org/bullseye/kmod/lsmod.8.en.html |
Greetings, I'm running Debian 11 x64 on a HP laptop I performed an update yesterday sudo apt update && sudo apt upgrade -y The process failed about half way through... Investigation revealed that while I could connect to my wifi, I had no internet connection A quick search on youtube for "debian wifi connects but no internet" led me to a few video's all stating to edit /etc/resolv.conf like this # Generated by NetworkManager # nameserver ::1 nameserver 8.8.8.8 nameserver 8.8.4.4 It looked like this originally # Generated by NetworkManager nameserver ::1 When I went online today, the problem is back, and was fixed with the same solution as yesterday. Wondering if anyone can throw some light onto what is going on ? | NetworkManager will overwrite /etc/resolv.conf every time it starts. You should not edit resolv.conf manually but rather set DNS in NetworkManager settings. See:- https://wiki.debian.org/NetworkConfigur ... orkManager I recall grappling with this some time ago, and I don't even use NM. I ended up setting the DNS servers in my router rather than in Linux, that way it also uses that DNS for any other connected devices as well. Much simpler. |
$ sudo inxi -Sazy Code: Select allSystem: Kernel: 5.10.0-20-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/vmlinuz-5.10.0-20-amd64 root=redacted ro quiet redacted Console: tty 1 wm: kwin_x11 DM: SDDM Distro: Debian GNU/Linux 11 (bullseye) apt update;apt upgrade ended up installing 5.10.0-23-amd64 (full output here) But new kernel was not added to grub: grep -i linux /boot/grub/grub.cfg since it shows 5.10.0-20-amd64 not 5.10.0-23-amd64 same happened with *22 kernel some time ago, so which commands to try please? | Hello, Are you sure that linux-image-5.10.0-23-amd64 is installed ? You can verify with the command: Code: Select allapt list linux-image-5.10.0-23-amd64 |
Hello everyone, I just bought a new laptop and I installed Debian on it instead of Windows 11. Unfortunately, I'm having trouble getting the wifi to work. I'm a big linux beginner and this doesn't help... If someone could give me a little help, I would appreciate it. So, here are the details of the situation : The laptop in question is this model : Honor Magicbook 16 - AMD Ryzen 5 5600H (spec : https://www.hihonor.com/global/laptops/ ... k-16/spec/ ) In order to identify my network card, I typed the following line in the terminal: Code: Select alllspci -nn | grep Network Return : Code: Select all02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) By doing some research on the Internet (like here: https://en.techinfodepot.shoutwiki.com/ ... m_QCNFA765 ), I found that this reference was the following model: "QCNFA765 Wireless Network Adapter". Unless I am mistaken - it seems that the correct driver for this hardware is "ath11k". Using the Synaptic Package Manager (from the GUI), I installed the "firmware-atheros" package (version 20210315-3) (is "ath11k" in there? I have no idea!) ... but I don't have the impression that it worked... I can't find a button or something that looks like a wifi activation from my desktop. I found this page on the internet - https://wireless.wiki.kernel.org/en/use ... stallation - that seems to talk about my situation, but I don't have the skills to figure out exactly what I need to do. (When I tried to do the first step "Clone Kernel", my terminal answered somethink like "bash: git: command not found" ......) Does anyone know what I need to do to get the wifi on my laptop? (Many thanks.) | First hit from a search for "debian 17cb:1103" has a probable solution - https://access.redhat.com/discussions/6953291 Copying the firmware from https://github.com/kvalo/ath11k-firmwar ... 6855/hw2.0 and https://github.com/kvalo/ath11k-firmwar ... ONZ_LITE-1 to /lib/firmware/ath11k/WCN6855/hw2.0 and then rebooting the system fixes the wifi problem. I do need to use the linux kernel 5.17 from ELRepo kernel-ml repository. Not sure if both those files are needed but won't hurt, and they should go under /usr/lib/firmware/ rather than /lib/firmware/ as suggested. Also you will need to add backports to your sources and install a more recent kernel than the stock Bullseye one (5.17 is mentioned so any higher version than that). https://wiki.debian.org/Backports This problem occurs usually because the hardware is newer than the Debian release and thus not supported out of the box. That page you linked at kernel.org has instructions to compile a kernel. You don't need that, just a newer kernel which already has the driver. |
Hello, Tired of finding a solution, I turned to the radical solution. Installation of Debian 11 on the media server. Now everything is ok. Debian 11 OS client laptop. Samba server OS Ubuntu 20.04. Very fast connection with samba client in the LAN network. Fast navigation through directories, fast display of files in directories, very good transfer speed. Via wireless very slow connection, very slow navigation through directories, very low transfer speed. Wired mount -a, umount -a under a second. On boot shared the directories are mounted Wireless mount -a , umount -a over 15 seconds On boot shared the directories are not mounted On the laptop (inxi -Fx): Network: Device-1: Intel Ethernet I219-V vendor: Hewlett-Packard driver: e1000e v: kernel port: efa0 bus ID: 00:1f.6 IF: enp0s31f6 state: down mac: 80:ce:62:9e:66:d6 Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: efa0 bus ID: 02:00.0 IF: wlp2s0 state: up mac: e4:70:b8:21:c5:e1 IF-ID-1: wwan0 state: down mac: ce:d8:61:52:c0:0d On the server (inxi -Fx): Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: AOPEN driver: r8169 v: kernel port: e000 bus ID: 01:00.0 IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: 00:01:80:86:a1:14 Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: AOPEN driver: r8169 v: kernel port: d000 bus ID: 02:00.0 The difference is very disturbing. Please help ! | Hello, It could be a WiFi connection issue, obviously. Can you describe how the client connects to the server when WiFi is used ? What network interface is used on the server (supposing the WiFi adapter is used on the client) ? Is a router / switch used ? Are there any rx/tx errors with the involved network interfaces ? You can check with: Code: Select allip -s -s link Are there any messages in the system log about the involved network adapters ? |
os: debian 11 kde plasma qemu-system: 1.5.2 Virtual Machine Manager: 3.2. 0 I want to make a directory on my host accessible from within a guest. And I want to do this in the virtual machine manager (VMM). I googled this and it should be possible but the solutions I found do not work for me See: Code: Select allhttps://troglobit.com/2013/07/05/file-system-pass-through-in-kvm-slash-qemu-slash-libvirt/I This is what I have done: In the VMM I go to the hardware details. Then I choose 'Add new Hardware" and add a new "filesystem" Then I choose a directory on my host and give it a name Screenshot.png (26.21 KiB) Viewed 11069 times I am not able to change the type When I start the vm I cannot see the drive/directory. | This is one of those moving targets with multiple past solutions and partial new methods. look at 'man qemu-nbd' still coming are 'qemu-storage-daemon' and 'libblkio' where a qcow2 image is usable on the host without a vm, and usable as a 'virtio_blk' with fuse for nbd or.... somewhere in the mix is using 'virtiofs' which may be what the dialog posted is trying to create in the guest xml; Code: Select all<domain> ... <devices> ... <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs'/> <source dir='/path'/> <target dir='mount_tag'/> </filesystem> ... </devices> </domain> peer wrote: 2023-02-13 13:09 When I start the vm I cannot see the drive/directory. Then within the guest Code: Select all'mount -t virtiofs mount_tag /mnt But systemd-mount would be preferred, maybe combined with an automount unit... There is host config in that process I think... anyway, I have no concise answer on which way to go. My stab at it over the last few years has been thwarted by 'moving target'. It is tempting to have a host directory with shared common guest access however I rule that out as unreasonably insecure currently. I already use qcow2 as my preferred format even though full usefulness is yet to arrive. It is an extra step but allows isolation of potential 'paths to host'. In my way a qcow2 image is used as the 'shared directory'. It can be local or remote to the host. It can offer the image to the guest as a nbd device, virtiofs, emulated drive as in my case a virtual usb. This area of use is expanding in capabilities and will get smoother, so my personal target. Overall clumsy at the moment, it is passively done for the guest as if I plugged in a usb drive, then the important part is unplugged. Then there is no persistent connection or fixed dependency in guest xml configuration. To make a virt-usb; Code: Select allvirsh attach-disk domain path/to/qcow2 sdx --targetbus usb --subdriver qcow2 A caveat in my methods is the use in any vm and not just linux kernels 5.4+. Soon the libblkio driver will take over management of qcows and be able to manage multi-path use, so r/w for host and any guest simultaneously while disconnecting the guest method from importance. So a virtual usb, a virtiofs, virtio net device, etc will all coherently access host storage through this new layer, and it's not quite here yet... I apologize for completely over-complicating the subject! |
Hello, after the last update (on sat 17, the list of updated package is given bellow) the integrated audio card does not work any more. I'm on Debian 11, the Motherboard is a Gigabyte GA-P55A-UD3 with an i5/750 2.67 GHz, I made a comparison between the output of the command Code: Select allsudo dmesg for this version (Debian 11) and the previous one (Debian 10) still bootable on an other HDD in my computer with no problem on sound, and find no noticeable differences for the lines concerned. any idea is welcome! PS: Info on the audio device: Code: Select all$ sudo lspci -k | grep -A 4 Audio 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Se[ 7.818116] snd_hda_codec_realtek hdaudioC0D2: autoconfig for ALC888: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line ries Chipset High Definition Audio (rev 06) Subsystem: Gigabyte Technology Co., Ltd 5 Series/3400 Series Chipset High Definition Audio Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) Kernel driver in use: pcieport Info on kernel modules: Code: Select all$ sudo lsmod |grep snd snd_hrtimer 16384 1 snd_seq 94208 1 snd_seq_device 16384 1 snd_seq snd_hda_codec_realtek 163840 1 snd_hda_codec_generic 98304 1 snd_hda_codec_realtek ledtrig_audio 16384 1 snd_hda_codec_generic snd_hda_intel 57344 3 snd_intel_dspcfg 28672 1 snd_hda_intel soundwire_intel 45056 1 snd_intel_dspcfg snd_soc_core 319488 1 soundwire_intel snd_compress 32768 1 snd_soc_core snd_hda_codec 176128 3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 110592 4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hwdep 16384 1 snd_hda_codec snd_pcm 143360 7 snd_hda_intel,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_hda_core snd_timer 49152 4 snd_seq,snd_hrtimer,snd_pcm snd 110592 16 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm soundcore 16384 1 snd Packages updated (history from apper) Installed: base-files, base-files, nftables, libnftables1, libtasn1-6, libtasn1-6, nano, chromium, chromium-common, chromium-sandbox, distro-info-data, firefox-esr-l10n-en-gb, firefox-esr-l10n-fr, firefox-esr, grub2-common, grub-pc, grub-pc-bin, grub-common, libbluray2, mariadb-common, libmariadb3, libpq5, speech-dispatcher-espeak-ng, speech-dispatcher, speech-dispatcher-audio-plugins, libspeechd2, libtinyxml2.6.2v5, libvncclient1, linux-compiler-gcc-10-x86, linux-headers-5.10.0-20-common, linux-kbuild-5.10, linux-headers-5.10.0-20-amd64, linux-headers-amd64, linux-image-5.10.0-20-amd64, linux-image-amd64, linux-libc-dev, mariadb-client-core-10.5, mariadb-server-core-10.5, nvidia-detect, python3-speechd, thunderbird-l10n-fr, thunderbird, speech-dispatcher-audio-plugins, linux-compiler-gcc-10-x86, libnftables1, nftables, nvidia-detect, python3-speechd, distro-info-data, libpq5, linux-libc-dev, chromium-sandbox, mariadb-common, grub-common, libvncclient1, libspeechd2, linux-headers-5.10.0-20-common, libmariadb3, libtinyxml2.6.2v5, nano, linux-image-5.10.0-20-amd64, linux-kbuild-5.10, chromium-common, thunderbird, chromium, libbluray2, firefox-esr, firefox-esr-l10n-en-gb, mariadb-server-core-10.5, thunderbird-l10n-fr, grub2-common, linux-image-amd64, grub-pc-bin, speech-dispatcher, grub-pc, linux-headers-5.10.0-20-amd64, mariadb-client-core-10.5, speech-dispatcher-espeak-ng, firefox-esr-l10n-fr, linux-headers-amd64 | Also check pavucontrol and alsamixer to make sure volumes are turned up and not muted. |
Hello everyone. I recently bought an HP 15-ef2126wm laptop (Ryzen 5 5500 with radeon graphics, 8gb RAM, 256 SSD). It comes with a wi-fi + Bluetooth module, a Realtek RTL8821CE-M. I've been trying to set up Debian for a couple of days now, in an endless loop of searching for the wifi controller firmware packages to install from a USB, and now trying to simply use a live non-free image (with gnome desktop in particular). The problem is that nothing has worked for me so far, and the laptop won't even hold the wired internet connection (I'm using an ethernet to USB-C adapter). However, bluetooth DOES work, as I have just tested out with a pair of wireless headphones. I've been searching endlessly for a solution to this, but I can't seem to find one. It's my first time using Debian, since I've always used Ubuntu and Mint, but wanted to try and step up the challenge. I knew the wi-fi drivers, and generally the non-free packages were going to be a hassle, but didn't expect this amount of resistance. Is there something I'm missing? Is this a general Realtek problem? (I've seen many intel wi-fi related packages around, but not many realtek ones). How can I know if the package for this module even exists?!? EDIT: I can attest the hardware works, since I ran a live Ubuntu 20.04 LTS image and was able to use eveything normally. (And I say everything because yes, gpu drivers are next on the list, to at least give the fans a rest and lower the screen's brightness) | A quick web search for "debian Realtek RTL8821CE-M" found this thread in which the issue was solved by installing a newer kernel from Backports. - viewtopic.php?t=151517 See the wiki for how to enable and install from backports - https://wiki.debian.org/Backports Probably the driver is not included in the original Bullseye kernel. Likely also needs the firmware-realtek package but that may be present already in the non-free live image. Hopefully the "-M" version uses the same driver as the non-M version. |
I would like to be able to suspend my system from commandline/scripts. "systemctl suspend" works fine, but can be run only as root: Code: Select alluser@host:~$ systemctl suspend User root is logged in on tty1. Please retry operation after closing inhibitors and logging out other users. Alternatively, ignore inhibitors and users with 'systemctl suspend -i'. user@host:~$ systemctl suspend -i Failed to suspend system via logind: Access denied Failed to start suspend.target: Access denied See system logs and 'systemctl status suspend.target' for details. /* I have no clue why it says "User root is logged in on tty1". I logged root out of tty1 before. /* I know that it can be done by creating executable from code likeCode: Select all#include <stdlib.h> int main(void) { int exit_code; const char command[] = "systemctl suspend"; exit_code = system(command); return exit_code; }with setuid root, but I've heard that it's a bad practice due to security reasons. Web search shown only scripts using sudo. So-called "power managers" achieve suspending & shutting down w/o root password in some way, but I'm not so advanced to dive into source code of one. Running Debian Bullseye on an Lenovo laptop. No "full" desktop environment - just i3 WM + lightdm. What's the elegant way of doing it? Is privilege escalation neccessary? | dashek wrote: 2023-03-08 09:55 Nope. Ran those as a normal user: if you run 'systemctl' as user and no args do you get the unit table? Try adding the user to group 'adm' ...if that's not it maybe need a polkit rule. |
Long time Xubuntu user discovered Debian installation is somewhat more challenging than Xubuntu. Linux h270m 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye XFCE I have some issues: Applications > System 1. Logs - Opens with message, "Unable to read system logs". Sent from pipewire, "Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name " 2. Print Settings - Can not configure printers; must "sudo system-config-printer" from terminal to add and configure printers 3. Software - Cannot add software; message reads, "Unable to install guvcview: you do not have permission to install software" 4. Synaptic Package Manager - Will not even start; must run "sudo synaptic" from terminal 5. Thunar - Can not mount other internal disks; message "Failed to mount 243 GB Volume" Not authorized to perform operation. I do not mind providing a password to open protected applications, but the five listed applications do not even request root password. During installation, I provided a password for root as well as username. Since then, I have added username to /etc/sudoers file. please advise, | 1. Ignore that. I get it too and it is inconsequential. 2. I don't know, don't have a printer 3. Give exact details of how you are trying to install software 4. Running from graphical menu should initiate a Polkit authentication box for a password. Does this not happen? 5. Give exact details of how you are trying to mount the disk If sudo works to launch synaptic, at least it must be set up correctly. |
When my computer starts, after the BIOS is done (at least I think it is), the display will show the text "Welcome to Grub" for over 30 seconds, before moving on to the actual grub menu. I have no idea why it takes so long. I don't know what the system is doing during that time. I don't even know where to look to find out. Does anyone have an idea? | /etc/defaults/grub |
Hi guys, First of all, thanks for reading! So let's go to the problem, I have installed a Debian 10 on my brand new pc with the Motherboard Asus Prime H510M-K, what looks have been an big mistake. Until now I haven't had success to connect to my pc using the Intel® I219-V which is the one on the board. I have been used one via USB. Until now i have tried a lot of things, even rebuild the driver, without success. So follow some data that I think it would be useful. Code: Select allroot@ironman:~# sudo dmesg | grep -e eth -e e1000 [ 0.007438] ACPI: Reserving DMAR table memory at [mem 0x9a3e1000-0x9a3e1087] [ 6.904106] ax88179_178a 2-1:1.0 eth0: register 'ax88179_178a' at usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:70:84:57 [ 6.957045] ax88179_178a 2-1:1.0 enx000ec6708457: renamed from eth0 Code: Select allroot@ironman:~# lspci -nn | grep -i Ethernet 00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:15fa] (rev 11) Code: Select allroot@ironman:~# lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b53] (rev 03) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9bc8] (rev 03) 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:43ed] (rev 11) 00:14.2 RAM memory [0500]: Intel Corporation Device [8086:43ef] (rev 11) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:43e8] (rev 11) 00:16.0 Communication controller [0780]: Intel Corporation Device [8086:43e0] (rev 11) 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] (rev 11) 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:43bc] (rev 11) 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:4388] (rev 11) 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:f0c8] (rev 11) 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:43a3] (rev 11) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:43a4] (rev 11) 00:1f.6 Ethernet controller [0200]: Intel Corporation Device [8086:15fa] (rev 11) Code: Select allroot@ironman:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enx000ec6708457: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:0e:c6:70:84:57 brd ff:ff:ff:ff:ff:ff inet 192.168.0.198/24 brd 192.168.0.255 scope global dynamic enx000ec6708457 valid_lft 85843sec preferred_lft 85843sec inet6 fe80::20e:c6ff:fe70:8457/64 scope link valid_lft forever preferred_lft forever If anyone can give me a direction, would be amazing | Is Code: Select allfirmware-misc-nonfree installed? https://unix.stackexchange.com/questio ... t-detected The kernels in Debian 11 or 11 backports probably have better support to be honest. 10 is a bit long in the tooth for newer hardware. |
I have some nftables that roughly look like this; Code: Select all#!/usr/bin/nft -f define wg_iface = "wg0" define local_nics = { "eth0", "wlan0" } # ... table ip nat { chain prerouting { type nat hook prerouting priority 0; iifname $wg_iface tcp dport 80 ip daddr 10.10.0.150 dnat to 10.0.1.150 iifname $wg_iface tcp dport 80 ip daddr 10.10.0.151 dnat to 10.0.1.151 iifname $wg_iface tcp dport 80 ip daddr 10.10.0.152 dnat to 10.0.1.152 iifname $wg_iface tcp dport 80 ip daddr 10.10.0.153 dnat to 10.0.1.153 iifname $wg_iface tcp dport 80 ip daddr 10.10.0.154 dnat to 10.0.1.154 iifname $wg_iface tcp dport 80 ip daddr 10.10.0.155 dnat to 10.0.1.155 } chain postrouting { type nat hook postrouting priority srcnat; policy accept; oifname $local_nics masquerade } } Can I simplify the copy/pasted lines by use of a map? It accepts this: Code: Select alldefine ip_map = { \ 10.10.0.150 : 10.0.1.150, \ 10.10.0.151 : 10.0.1.151, \ 10.10.0.152 : 10.0.1.152, \ 10.10.0.153 : 10.0.1.153, \ 10.10.0.154 : 10.0.1.154, \ 10.10.0.155 : 10.0.1.155, \ } So it seems possible. But how do I actually use it? What is the correct syntax for the below? Code: Select all ip daddr {} dnat to {} map $ip_map | Does it work ? |
Hello everyone, I am having some difficulties setting up VPN for work. We use forticlient for VPN so I need to set it up. Connecting using openfortivpn is possible. It creates the tunnel and I am given IP address 170.30.10.2. And it creates new interface Code: Select all4: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1354 qdisc pfifo_fast state UNKNOWN group default qlen 3 link/ppp inet 170.30.10.2. peer 190.0.1.1/32 scope global ppp0 valid_lft forever preferred_lft forever At this point I should connect to my work machine using RDP with address MACHINEXXX.DOMAIN.COM. Now while I do get connection it seems my network traffic is still using main wifi interface. My problem here is that I am unable to see my work machine on such address. Actually I don't know much about networking at all, so just getting there was something for me. To set up openfortivpn I had to change some settings for it such as seclevel-1 = 1 and min-tls = 1.0. Code: Select allsudo openfortivpn --min-tls=1.0 --seclevel-1 Unknowing how to proceed tried to set it up with NetworkManager but there I don't know how to set seclevel-1 = 1 and min-tls = 1.0 in its config file under /etc/NetworkManager/system-connections. Looking around for manual if it uses different naming for configuration got me nowhere. Those two options just get overwritten when I try to connect. Right now config file is Code: Select all[connection] id=Company name uuid=3e42387a-fffff-4423-9804-75829a134fff type=vpn permissions=user:user3:; [vpn] gateway=193.133.133.133:10000 otp-flags=0 password-flags=2 user=company_user service-type=org.freedesktop.NetworkManager.fortisslvpn [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto [proxy] So my question here would be, if anyone knows, how to add those two options (seclevel-1 = 1 and min-tls = 1.0) for NetworkManager config file for openfortivpn. Or other way how would I forwards traffic through VPN connection. I don't know much about networking so anything would be helpful to me, Thanks in advance. | Hello, I suppose you are probably using the NetworkManager with NetworkManager-fortisslvpn [1]. This module requires the openfortivpn client installed. Here [2] is the manual page for openfortivpn where you can find the description of the two options: --min-tls=<version> Use minimum TLS version instead of system default. Valid values are 1.0, 1.1, 1.2, 1.3. --seclevel-1 If --cipher-list is not specified, add @SECLEVEL=1 to the list of ciphers. This lowers limits on dh key. --- [1] https://gitlab.gnome.org/GNOME/NetworkM ... ortisslvpn [2] https://manpages.debian.org/bullseye/op ... .1.en.html |
Hello, I'm using Wireguard to setup a VPN automatically when server starts. However, I get this error in relevant service log: Mar 13 15:37:51 osmc systemd[1]: Starting WireGuard via wg-quick(8) for ivpn/sui... Mar 13 15:37:51 osmc wg-quick[2618]: [#] ip link add ivpn-sui type wireguard Mar 13 15:37:51 osmc wg-quick[2618]: [#] wg setconf ivpn-sui /dev/fd/63 Mar 13 15:37:51 osmc wg-quick[2717]: Name or service not known: `ch1.wg.ivpn.net:2049' Mar 13 15:37:51 osmc wg-quick[2717]: Configuration parsing error Mar 13 15:37:51 osmc wg-quick[2618]: [#] ip link delete dev ivpn-sui Mar 13 15:37:52 osmc systemd[1]: wg-quick@ivpn-sui.service: Main process exited, code=exited, status=1/FAILURE Mar 13 15:37:52 osmc systemd[1]: wg-quick@ivpn-sui.service: Failed with result 'exit-code'. Mar 13 15:37:52 osmc systemd[1]: Failed to start WireGuard via wg-quick(8) for ivpn/sui. This means name resolution fails when wg-quick starts to enable the VPN. There's no issue with relevant configuration file /etc/wireguard/ivpn-sui.conf because I can start the service manually (once boot has completed) w/o issues. Can you please advise how to fix this issue? THX | cmonty14 wrote: 2023-03-13 14:49 [..] This means name resolution fails when wg-quick starts to enable the VPN. There's no issue with relevant configuration file /etc/wireguard/ivpn-sui.conf because I can start the service manually (once boot has completed) w/o issues. Perhaps you are trying to start the VPN when DNS service or the network configuration itself is not already active. |
Since the update to kernel 5.10.0-19 last year; and since then my computer is refusing to boot in the GUI. The problem I have found is that the amdgpu module is simply not loading. However: My GPU is detected if go in Advanced options and boot the old version of the kernel: 5.10.0-18. I have seen this bug, https://bugs.debian.org/cgi-bin/bugrepo ... ug=1022025, which is similar to my issue; however I have an Intel CPU, and the patches proposed do not work. I have tested up to 5.10.0-21 and it still does not work. I have inspected kernel.log and found that the 'drm' module simply isn't loading and the 'amdgpu' module either. I'm attaching a complete diff (see attachments section)- perhaps this can help. Below is a short version of the diff. What would be the cause of the issue? Any ideas? kernel.log: Booting 5.10.0-18 - All normal - working Code: Select all[ 0.000000] Linux version 5.10.0-18-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.140-1 (2022-09-02) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-18-amd64 root=UUID=395b803e-2132-4576-9c8d-de572c6b74c5 ro quiet [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' ..... [ 4.131268] sr 0:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray [ 4.131274] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 4.183746] usb 3-1.1: new full-speed USB device number 3 using ehci-pci [ 4.254689] [drm] amdgpu kernel modesetting enabled. [ 4.254913] CRAT table not found [ 4.254917] Virtual CRAT table created for CPU [ 4.254953] amdgpu: Topology: Add CPU node [ 4.255089] checking generic (e0000000 1f0000) vs hw (e0000000 10000000) [ 4.255091] fb0: switching to amdgpudrmfb from EFI VGA [ 4.255184] Console: switching to colour dummy device 80x25 [ 4.255238] amdgpu 0000:03:00.0: vgaarb: deactivate vga console [ 4.255383] [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1043:0x04C2 0xEF). [ 4.255386] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [ 4.255397] [drm] register mmio base: 0xF7E00000 [ 4.255398] [drm] register mmio size: 262144 [ 4.255402] [drm] PCIE atomic ops is not supported [ 4.255407] [drm] add ip block number 0 <vi_common> [ 4.255409] [drm] add ip block number 1 <gmc_v8_0> [ 4.255410] [drm] add ip block number 2 <tonga_ih> [ 4.255411] [drm] add ip block number 3 <gfx_v8_0> [ 4.255412] [drm] add ip block number 4 <sdma_v3_0> [ 4.255413] [drm] add ip block number 5 <powerplay> [ 4.255415] [drm] add ip block number 6 <dm> [ 4.255416] [drm] add ip block number 7 <uvd_v6_0> [ 4.255417] [drm] add ip block number 8 <vce_v3_0> [ 4.255420] kfd kfd: skipped device 1002:67df, PCI rejects atomics [ 4.255687] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from ROM BAR [ 4.255690] amdgpu: ATOM BIOS: 115-C940PI0-100 [ 4.255710] [drm] UVD is enabled in VM mode [ 4.255711] [drm] UVD ENC is enabled in VM mode [ 4.255713] [drm] VCE enabled in VM mode [ 4.255754] [drm] vm size is 256 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [ 4.255815] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_mc.bin [ 4.255823] amdgpu 0000:03:00.0: amdgpu: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used) [ 4.255826] amdgpu 0000:03:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF [ 4.255833] [drm] Detected VRAM RAM=4096M, BAR=256M [ 4.255834] [drm] RAM width 256bits GDDR5 [ 4.255995] [TTM] Zone kernel: Available graphics memory: 41213726 KiB [ 4.255997] [TTM] Zone dma32: Available graphics memory: 2097152 KiB [ 4.255999] [TTM] Initializing pool allocator [ 4.256004] [TTM] Initializing DMA pool allocator [ 4.256470] [drm] amdgpu: 4096M of VRAM memory ready [ 4.256474] [drm] amdgpu: 4096M of GTT memory ready. [ 4.256477] [drm] GART: num cpu pages 65536, num gpu pages 65536 [ 4.257340] [drm] PCIE GART of 256M enabled (table at 0x000000F4001D5000). [ 4.257501] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_pfp_2.bin [ 4.257527] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_me_2.bin [ 4.257557] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_ce_2.bin [ 4.257560] [drm] Chained IB support enabled! [ 4.257586] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_rlc.bin [ 4.257700] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec_2.bin [ 4.257815] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec2_2.bin [ 4.259515] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma.bin [ 4.259544] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma1.bin [ 4.259697] amdgpu: hwmgr_sw_init smu backed is polaris10_smu [ 4.259920] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_uvd.bin [ 4.259925] [drm] Found UVD firmware Version: 1.130 Family ID: 16 [ 4.260821] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_vce.bin [ 4.260826] [drm] Found VCE firmware Version: 53.26 Binary ID: 3 [ 4.262239] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris10_k_smc.bin [ 4.298090] usb 3-1.1: New USB device found, idVendor=062a, idProduct=4102, bcdDevice= 1.03 [ 4.298096] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.298099] usb 3-1.1: Product: 2.4G Wireless Mouse [ 4.298101] usb 3-1.1: Manufacturer: MOSART Semi. kernel.log: Booting 5.10.0-21 - AMDGPU not recognized - will not boot to GUI Code: Select all[ 0.000000] microcode: microcode updated early to revision 0x71a, date = 2020-03-24 [ 0.000000] Linux version 5.10.0-21-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.162-1 (2023-01-21) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64 root=UUID=395b803e-2132-4576-9c8d-de572c6b74c5 ro quiet .... --- > no mention of amdgpu/drm/etc. [ 4.224077] tsc: Refined TSC clocksource calibration: 1995.190 MHz [ 4.224092] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x3984dcddca4, max_idle_ns: 881590726873 ns [ 4.224200] clocksource: Switched to clocksource tsc [ 4.276161] sr 0:0:0:0: Attached scsi CD-ROM sr0 [ 4.480075] usb 4-1.1: new full-speed USB device number 3 using ehci-pci ... | You may need to file your own bug report for this against your specific hardware as fixes for previous issues have not worked for you. |
As per docs to solve screen tearing issue I followed these steps Add this line to the end of /etc/modprobe.d/nvidia.conf: Code: Select alloptions nvidia-drm modeset=1 2. Regenerate your initramfs image by running: Code: Select all# update-initramfs -u 3. The modesetting driver for an Intel GPU loads a module called glamor, which conflicts with the NVIDIA GLX implementation. To disable glamor uncomment this line in /etc/X11/xorg.conf: Code: Select allOption "AccelMethod" "none" and after reboot Code: Select allsudo cat /sys/module/nvidia_drm/parameters/modeset outputs 'N' Here is more info Code: Select all>> sudo cat /etc/modprobe.d/nvidia-blacklists-nouveau.conf blacklist nouveau #options nouveau modeset=0 Code: Select all>> sudo cat /etc/modprobe.d/nvidia.conf options nvidia-drm modeset=1 options nvidia NVreg_PreserveVideoMemoryAllocations=1 Code: Select all>> sudo cat /etc/X11/xorg.conf Section "ServerLayout" Identifier "layout" Screen 0 "nvidia" Inactive "intel" EndSection Section "Device" Identifier "nvidia" Driver "nvidia" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "nvidia" Device "nvidia" Option "AllowEmptyInitialConfiguration" EndSection Section "Device" Identifier "intel" Driver "modesetting" BusID "PCI:0:2:0" Option "AccelMethod" "none" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection Code: Select all>> sudo cat /etc/default/grub # 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="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Code: Select all>> sudo cat /usr/share/sddm/scripts/Xsetup #!/bin/sh xrandr --setprovideroutputsource "modesetting" NVIDIA-0 xrandr --auto --- Moderator edit by aki (2023/03/25): added code tags for better readability. | Hello, Welcome to the forum. It looks like your previous post is a solution about the topic in the subject. It could be useful to other viewer to give more context about the used Debian release and the hardware of you computer (manufacturer and model). To do it, you can use the following command: Code: Select allinxi -SMCIxxz Can you send the output of previous command in a follow-up message ? Thank you ! :-) |
I recently installed Debian 11 Bullseye with Mate` I have several other computers including W10, W11, and RPOS (raspberry pie Debian). I can connect to my rpi's from W10 and W11. I have an account for RealVNC, downloaded and installed both the client and server. The client works fine, I can connect to to my rpi's. When I attempt to connect to my Debian box from W10 I get "Timed out waiting for a response from the computer" I did some googling, I installed telnet on one of my rpi's and telnet: could not resolve 192.168.1.108:5900/telnet: Name or service not known The next step in the trouble shooting is to open up port 5900 I attempted to open the port and got "Bad argument '5900' I typed iptables -h or -help and get "bash: iptables: command not found" Before I assume that iptables is not installed... is there a firewall installed by default when Debian installs? I did some reading and apparently getting REALVNC to work can be a difficult thing. | SamuelMac wrote: 2023-03-26 21:38I attempted to open the port and got "Bad argument '5900' Sounds like bad command-line syntax to me, but you don't say what the command you used was. vOv Exact command and response please, in code tags. SamuelMac wrote: 2023-03-26 21:38Before I assume that iptables is not installed... is there a firewall installed by default when Debian installs? IIRC debian switched to nftables a while back. As far as I know there are no rules enabled by default, so it shouldn't interfere with your vnc server. |
Hi, i have just received my brand new Lenovo P14s AMD Gen 3 and installed Debian Bullseye with non-free firmware. So far, everything works fine with the exception of the Wireless Lan. Regarding to Lenbovo it is a Qualcomm NFA-725A Wi-Fi 6E card, lspci sdays : Qualcomm Device 1103 I have tried the firmware-Atheros 21xxx as well as 23xxxxxx, but can't see any success. uname -r says 5.10.0-23-amd. Any suggestions how to get this to work ? Thank you in advance for any help | Looks like that device needs at least kernel 5.15: https://www.phoronix.com/review/rembrandt-linux-boot To upgrade the kernel version either install the linux-image-amd64 metapackage from the bullseye-backports repository: https://backports.debian.org/Instructions/ Or use the Liquorix kernel: https://liquorix.net/ The Liquorix version will be kept more up to date than the backported kernel. You could try Debian bookworm but that is still in development so there may more bugs than would be expected for a stable release. |
I have a dual boot system with Buster amd64 installed on an SSD and an HDD. I just upgraded the HDD to Bullseye. Now I am experiencing a strange networking issue. If I select Bullseye as the boot option it starts up and the network connection is fine. However, if I then restart the computer (select restart from the xfce menu) and at grub now select the SSD when I arrive at the desktop the network icon just spins around and around. I have tried to restart the network. I have tried stopping and then starting the network. The only thing that works is to shutdown and turn off the UPS. I can then select the SSD in grub and the network connection will be made. I am assuming that there is something in the Bullseye configuration that is causing the problem. Any suggestions or guidance as to where to look would be appreciated. | I have possibly the same Ethernet controller and have 5 Linuxes (including 3x Buster and a week-old Bullseye) and Windows 10 all installed on a 1TB SSD. Booting any of these brings up the network almost instantly. Check journalctl for any clues but from the info you have posted I have no idea why yours misbehaves. |
There is something I am doing wrong, but I couldn't find helpfull tips anywhere (perhaps I'm just stupid). This is in my /etc/auto.master: Code: Select all/media/removable /etc/auto.removable This is my /etc/auto.removable: Code: Select alltoshiba-ext -fstype=auto UUID="8EF9-F8C0" The partition is type "HPFS/NTFS/exFAT" (fdisk -l) mount -l: Code: Select all/etc/auto.removable on /media/removable type autofs (rw,relatime,fd=6,pgrp=2744,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=33019) /media/removable is empty Could someone help me out? Thanks in advance | Ok I am just stupid indeed. /media/removable is empty I thought this would be wrong, but I only have to try to access /media/removable/toshiba-ext without the directory beeing created yet and then autofs creates and mounts it automatically. |
Debian 11 server install did not mounted my partitions ( noted only now ! ) ? I have 4 nvme`s in raid card with bifurcated bios and i have server ssd for sql usage ... i run lsblk and i have this: Code: Select allNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 447.1G 0 disk ├─sda1 8:1 0 372.5G 0 part └─sda2 8:2 0 74.6G 0 part sdb 8:16 0 3.6T 0 disk └─sdb1 8:17 0 3.6T 0 part /media/evo/My Passport nvme0n1 259:0 0 465.8G 0 disk └─nvme0n1p1 259:1 0 465.8G 0 part nvme1n1 259:2 0 465.8G 0 disk └─nvme1n1p1 259:3 0 465.8G 0 part nvme2n1 259:4 0 465.8G 0 disk └─nvme2n1p1 259:6 0 465.8G 0 part nvme3n1 259:5 0 465.8G 0 disk ├─nvme3n1p1 259:7 0 476M 0 part /boot ├─nvme3n1p2 259:8 0 143M 0 part /boot/efi ├─nvme3n1p3 259:9 0 59.6G 0 part [SWAP] └─nvme3n1p4 259:10 0 405.6G 0 part / Which turns out - 3 of 4 nvmes was not mounted and my sda too. 1 nvme should be /home and other 2`s just plain work and files sda1 - should be /custom mount point sda2 - should be /var/www I did recall partitioning and setting up mount point but turns out - my drives left unmounted. checked fstab - indeed only / , /boot, /efi and swap partitions ... How do i mount them. Most important part is i need to mount my sda1 and 2 as its server ssd for my sql and web work. EDIT: sda1 - XFS partition, sda2 - ext4 partition, nvme1 - ext4, nvme2 - i believe is xfs as well, nvme0 - xfs ( maybe - but def not ext4 ) i was experimenting with partition types. And i was using LVM as one of the nvme partitions supposed to be /home partition. EDIT2: hmmm, no LVM either . Basically install used 1 disk out of 5. Thank You. | I'm hesitant to answer this because the answer can blow into a full debate over disk management, but here goes. There are several ways to manage disk partitions under linux. Old school you simply add the partitions to the /etc/fstab file, which is generally what I prefer. But now systemd (svchost for linux) wants to control disk mounts as units (which I tend to avoid if possible), so you have a choice and you can mix and match those methodologies. IMHO, one of the significant updates in the linux ecosystem was the ability to mount partitions by UUID, which solved the problem of device reenumeration when you add/delete a disk. At boot the /dev/disks will populate with the UUIDs of all available partitions and you can reference a partition in /etc/fstab using UUID= syntax instead of refering to the partition by its /dev entry name. It also supports mounting by filesystem label as LABEL= lsblk -o +uuid will show all known UUIDs for partitions This is my workstation fstab, as an example # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdd1 during installation UUID=a21a2f61-39e8-4050-9f74-e32569aa40b4 / ext4 errors=remount-ro 0 1 # /6TB was on /dev/md127 during installation UUID=2f8727e4-4a2a-4df7-ad25-7f2eca84d532 /6TB ext4 defaults 0 2 /dev/md0 /var ext4 defaults 0 2 # TCLPS LABEL=TCLPS /mounts/tclps ext4 defaults 0 2 # backups LABEL=backups /mounts/backups ext4 defaults 0 2 # /tmp ramdisk tmpfs /tmp tmpfs defaults,nodev,nosuid,size=10G 0 0 #tmpfs /ramwork tmpfs defaults,size=10G 0 0 # swapfile /6TB/swapfile none swap defaults 0 0 UUID=5a6dfacd-03ab-4bba-9e20-2da2d06d23e6 /usr/src ext4 defaults 0 2 ------------------------------------- Another option I prefer instead of systemd is autofs, which automatically mounts partitions when they are referenced, and unmounts them after a configurable idle timeout. This works pretty well for local filesystems, but I've had issues with unsolicited mounts when applied to NFS or SMB shares. web and manpage research of autofs/automountd is left as an exercise for the OP. |
Hi, my first post. Generally I try to solve my PC-related problems on my own, but I've lost my patience with this one. I try to set unattended-upgrades on my mom's PC. As title says- they never fetch any, although for sure they are after recent Debian's point release (could this be the problem?) Guess you'd like to see: 1) Unattended-upgrades log- I attach today's, any day is the same story: Code: Select all2022-12-29 20:34:42,522 INFO Starting unattended upgrades script 2022-12-29 20:34:42,538 INFO Allowed origins are: origin=Debian,codename={distro_codename}-updates, origin=Debian,codename={distro_codename},label=Debian, origin=Debian,codename={distro_codename},label=Debian-Security, origin=Debian,codename={distro_codename}-security,label=Debian-Security 2022-12-29 20:34:42,545 INFO Initial blacklist: 2022-12-29 20:34:42,546 INFO Initial whitelist (not strict): 2022-12-29 20:34:49,077 INFO No packages found that can be upgraded unattended and no pending auto-removals 2) /etc/apt/apt.conf.d/50unattended-upgrades file: Code: Select all// Unattended-Upgrade::Origins-Pattern controls which packages are // upgraded. // // Lines below have the format "keyword=value,...". A // package will be upgraded only if the values in its metadata match // all the supplied keywords in a line. (In other words, omitted // keywords are wild cards.) The keywords originate from the Release // file, but several aliases are accepted. The accepted keywords are: // a,archive,suite (eg, "stable") // c,component (eg, "main", "contrib", "non-free") // l,label (eg, "Debian", "Debian-Security") // o,origin (eg, "Debian", "Unofficial Multimedia Packages") // n,codename (eg, "jessie", "jessie-updates") // site (eg, "http.debian.net") // The available values on the system are printed by the command // "apt-cache policy", and can be debugged by running // "unattended-upgrades -d" and looking at the log file. // // Within lines unattended-upgrades allows 2 macros whose values are // derived from /etc/debian_version: // ${distro_id} Installed origin. // ${distro_codename} Installed codename (eg, "buster") Unattended-Upgrade::Origins-Pattern { // Codename based matching: // This will follow the migration of a release through different // archives (e.g. from testing to stable and later oldstable). // Software will be the latest available for the named release, // but the Debian release itself will not be automatically upgraded. "origin=Debian,codename={distro_codename}-updates"; // "origin=Debian,codename=${distro_codename}-proposed-updates"; "origin=Debian,codename={distro_codename},label=Debian"; "origin=Debian,codename={distro_codename},label=Debian-Security"; "origin=Debian,codename={distro_codename}-security,label=Debian-Security"; // Archive or Suite based matching: // Note that this will silently match a different release after // migration to the specified archive (e.g. testing becomes the // new stable). // "o=Debian,a=stable"; // "o=Debian,a=stable-updates"; // "o=Debian,a=proposed-updates"; // "o=Debian Backports,a=${distro_codename}-backports,l=Debian Backports"; }; // Python regular expressions, matching packages to exclude from upgrading Unattended-Upgrade::Package-Blacklist { // The following matches all packages starting with linux- // "linux-"; // Use $ to explicitely define the end of a package name. Without // the $, "libc6" would match all of them. // "libc6$"; // "libc6-dev$"; // "libc6-i686$"; // Special characters need escaping // "libstdc\+\+6$"; // The following matches packages like xen-system-amd64, xen-utils-4.1, // xenstore-utils and libxenstore3.0 // "(lib)?xen(store)?"; // For more information about Python regular expressions, see // https://docs.python.org/3/howto/regex.html }; // This option allows you to control if on a unclean dpkg exit // unattended-upgrades will automatically run // dpkg --force-confold --configure -a // The default is true, to ensure updates keep getting installed //Unattended-Upgrade::AutoFixInterruptedDpkg "true"; // Split the upgrade into the smallest possible chunks so that // they can be interrupted with SIGTERM. This makes the upgrade // a bit slower but it has the benefit that shutdown while a upgrade // is running is possible (with a small delay) Unattended-Upgrade::MinimalSteps "true"; // Install all updates when the machine is shutting down // instead of doing it in the background while the machine is running. // This will (obviously) make shutdown slower. // Unattended-upgrades increases logind's InhibitDelayMaxSec to 30s. // This allows more time for unattended-upgrades to shut down gracefully // or even install a few packages in InstallOnShutdown mode, but is still a // big step back from the 30 minutes allowed for InstallOnShutdown previously. // Users enabling InstallOnShutdown mode are advised to increase // InhibitDelayMaxSec even further, possibly to 30 minutes. //Unattended-Upgrade::InstallOnShutdown "false"; // Send email to this address for problems or packages upgrades // If empty or unset then no email is sent, make sure that you // have a working mail setup on your system. A package that provides // 'mailx' must be installed. E.g. "user@example.com" //Unattended-Upgrade::Mail ""; // Set this value to one of: // "always", "only-on-error" or "on-change" // If this is not set, then any legacy MailOnlyOnError (boolean) value // is used to chose between "only-on-error" and "on-change" //Unattended-Upgrade::MailReport "on-change"; // Remove unused automatically installed kernel-related packages // (kernel images, kernel headers and kernel version locked tools). Unattended-Upgrade::Remove-Unused-Kernel-Packages "true"; // Do automatic removal of newly unused dependencies after the upgrade Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; // Do automatic removal of unused packages after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies "true"; // Automatically reboot *WITHOUT CONFIRMATION* if // the file /var/run/reboot-required is found after the upgrade //Unattended-Upgrade::Automatic-Reboot "false"; // Automatically reboot even if there are users currently logged in // when Unattended-Upgrade::Automatic-Reboot is set to true //Unattended-Upgrade::Automatic-Reboot-WithUsers "true"; // If automatic reboot is enabled and needed, reboot at the specific // time instead of immediately // Default: "now" //Unattended-Upgrade::Automatic-Reboot-Time "02:00"; // Use apt bandwidth limit feature, this example limits the download // speed to 70kb/sec //Acquire::http::Dl-Limit "70"; // Enable logging to syslog. Default is False // Unattended-Upgrade::SyslogEnable "false"; // Specify syslog facility. Default is daemon // Unattended-Upgrade::SyslogFacility "daemon"; // Download and install upgrades only on AC power // (i.e. skip or gracefully stop updates on battery) Unattended-Upgrade::OnlyOnACPower "true"; // Download and install upgrades only on non-metered connection // (i.e. skip or gracefully stop updates on a metered connection) Unattended-Upgrade::Skip-Updates-On-Metered-Connections "true"; // Verbose logging // Unattended-Upgrade::Verbose "false"; // Print debugging information both in unattended-upgrades and // in unattended-upgrade-shutdown // Unattended-Upgrade::Debug "false"; // Allow package downgrade if Pin-Priority exceeds 1000 // Unattended-Upgrade::Allow-downgrade "false"; // When APT fails to mark a package to be upgraded or installed try adjusting // candidates of related packages to help APT's resolver in finding a solution // where the package can be upgraded or installed. // This is a workaround until APT's resolver is fixed to always find a // solution if it exists. (See Debian bug #711128.) // The fallback is enabled by default, except on Debian's sid release because // uninstallable packages are frequent there. // Disabling the fallback speeds up unattended-upgrades when there are // uninstallable packages at the expense of rarely keeping back packages which // could be upgraded or installed. // Unattended-Upgrade::Allow-APT-Mark-Fallback "true"; 3) /etc/apt/apt.conf.d/20auto-upgrades file: Code: Select allAPT::Periodic::Update-Package-Lists "1"; APT::Periodic::Unattended-Upgrade "1"; I tried to perform unattended-upgrade with --dry-run flag. I noticed that it sees packages to upgrade, but only after issuing "sudo apt update". I thought that I've found solution on AskUbuntu: https://askubuntu.com/questions/1336631 ... get-update But it didn't help: Code: Select allsudo systemctl status apt-daily.timer ● apt-daily.timer - Daily apt download activities Loaded: loaded (/lib/systemd/system/apt-daily.timer; enabled; vendor preset: enabled) Active: active (waiting) since Thu 2022-12-29 21:42:18 CET; 53min ago Trigger: Fri 2022-12-30 05:05:38 CET; 6h left Triggers: ● apt-daily.service gru 29 21:42:18 lenovo-yoga300 systemd[1]: Started Daily apt download activities. Any ideas? Thanks in advance! | Code: Select allUnattended-Upgrade::OnlyOnACPower "true"; Is it a laptop that's only charged when it's off? Unlikely, I know. Code: Select allUnattended-Upgrade::Skip-Updates-On-Metered-Connections "true"; Is it a metered connection? |
Hi, I have tried to Debian stable an unstable on second M2 drive after some tries I found that Debian did not found some usb ports and none of my four onboard network interfaces, with help of a usb2ethernet adapater and a "working" usb port for usb stick and mouse/keyboard, I tried the Mint LMDE5 live iso ( no working ethernet there either... ), Latest Fedora live iso works and OpenSUSE is also working and Arch on my main disk. Three of the four main distros work wihtout any changes whatsoever, what do I need to do in Debain to use it ( how do I get Debian to load the drivers ? ) root@debian-threadripper:/home/janne/Desktop# journalctl -b Dec 20 18:28:32 debian-threadripper kernel: Linux version 6.0.0-6-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-9.1) 12.2.0> Dec 20 18:28:32 debian-threadripper kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6-amd64 root=UUID=817750c1-2a9b-4ca6-935f-ad5a9d3d> Dec 20 18:28:32 debian-threadripper kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' .............. Dec 20 18:28:32 debian-threadripper kernel: igb: Intel(R) Gigabit Ethernet Network Driver Dec 20 18:28:32 debian-threadripper kernel: igb: Copyright (c) 2007-2014 Intel Corporation. Dec 20 18:28:32 debian-threadripper kernel: igb: probe of 0000:c4:00.0 failed with error -5 Dec 20 18:28:32 debian-threadripper kernel: igb: probe of 0000:c5:00.0 failed with error -5 Dec 20 18:28:32 debian-threadripper kernel: xhci_hcd 0000:c6:00.1: init 0000:c6:00.1 fail, -16 Dec 20 18:28:32 debian-threadripper kernel: xhci_hcd: probe of 0000:c6:00.1 failed with error -16 Dec 20 18:28:32 debian-threadripper kernel: xhci_hcd 0000:c6:00.3: init 0000:c6:00.3 fail, -16 Dec 20 18:28:32 debian-threadripper kernel: xhci_hcd: probe of 0000:c6:00.3 failed with error -16 ............... Dec 20 18:28:32 debian-threadripper kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver Dec 20 18:28:32 debian-threadripper kernel: ixgbe: Copyright (c) 1999-2016 Intel Corporation. Dec 20 18:28:32 debian-threadripper kernel: ixgbe: probe of 0000:c9:00.0 failed with error -5 Dec 20 18:28:32 debian-threadripper kernel: ixgbe: probe of 0000:c9:00.1 failed with error -5 //========================================================================================== janne@debian-threadripper:~/Desktop$ lsusb Bus 002 Device 002: ID 17ef:7205 Lenovo Thinkpad LAN Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub janne@debian-threadripper:~/Desktop$ //=========================================================================================== [janne@threadripper Desktop]$ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0414:a002 Giga-Byte Technology Co., Ltd USB Audio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 17ef:7205 Lenovo Thinkpad LAN Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [janne@threadripper Desktop]$ | Find exact device IDs and check if the required firmware is in the Debian repository. Firmware is/was quite out of date. viewtopic.php?p=759413&hilit=Gigabit+Et ... er#p759413 |
On my laptop (Thinkpad P15s) with Debian 11 (desktop is Plasma) sound doesn't work properly. When NOT connected to the docking station (Lenovo USB-C Mini Dock) I have no sound (neither speakers nor when I connect headphones via the 3.5mm jack). When connected to the docking station, headphones work if I plug them into the headphone jack of the docking station. This thread seems to deal with a similar problem, so I tried to follow the same diagnostic steps:viewtopic.php?t=151319&sid=8fa3dd9f0fe9 ... 436fa0034b I know nex to nothing about sound on Debian (or Linux in general), so I didn't install any packages / change config files like suggested in the other thread. I would be very happy if someone could help me get this to work. The goal is that: - The headphone jack of my laptop always works - The headphone jack of te docking station works when the laptop is plugged in - The speaker works unless something is plugged into the headphone jack of the laptop 1. The output of amixer Code: Select all$ amixer Simple mixer control 'Master',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 65536 Mono: Front Left: Playback 37120 [57%] [on] Front Right: Playback 36464 [56%] [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch cswitch-joined Capture channels: Front Left - Front Right Limits: Capture 0 - 65536 Front Left: Capture 65536 [100%] [on] Front Right: Capture 65536 [100%] [on] 2.The output of pacmd list-sinks Code: Select all$ pacmd list-sinks 4 sink(s) available. index: 1 name: <alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_5__sink> driver: <module-alsa-card.c> flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9037 volume: front-left: 29988 / 46% / -20.37 dB, front-right: 29988 / 46% / -20.37 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 0.00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 2 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0.00 ms; range is 0.50 .. 341.00 ms card: 1 <alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic> module: 7 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "" alsa.id = "HDMI3 (*)" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "5" alsa.card = "0" alsa.card_name = "sof-hda-dsp" alsa.long_card_name = "sof-hda-dsp" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-0000:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "a0c8" device.product.name = "Tiger Lake-LP Smart Sound Technology Audio Controller" device.string = "hw:sofhdadsp,5" device.buffering.buffer_size = "65472" device.buffering.fragment_size = "16320" device.access_mode = "mmap+timer" device.profile.name = "HiFi: hw:sofhdadsp,5: sink" device.profile.description = "HDMI3 Output" alsa.mixer_device = "hw:sofhdadsp" device.description = "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI3 Output" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: [Out] HDMI3: HDMI3 Output (priority 700, latency offset 0 usec, available: no) properties: active port: <[Out] HDMI3> index: 2 name: <alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_4__sink> driver: <module-alsa-card.c> flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9036 volume: front-left: 45544 / 69% / -9.48 dB, front-right: 45544 / 69% / -9.48 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 0.00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 3 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0.00 ms; range is 0.50 .. 341.00 ms card: 1 <alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic> module: 7 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "" alsa.id = "HDMI2 (*)" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "4" alsa.card = "0" alsa.card_name = "sof-hda-dsp" alsa.long_card_name = "sof-hda-dsp" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-0000:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "a0c8" device.product.name = "Tiger Lake-LP Smart Sound Technology Audio Controller" device.string = "hw:sofhdadsp,4" device.buffering.buffer_size = "65472" device.buffering.fragment_size = "16320" device.access_mode = "mmap+timer" device.profile.name = "HiFi: hw:sofhdadsp,4: sink" device.profile.description = "HDMI2 Output" alsa.mixer_device = "hw:sofhdadsp" device.description = "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI2 Output" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: [Out] HDMI2: HDMI2 Output (priority 600, latency offset 0 usec, available: no) properties: active port: <[Out] HDMI2> index: 3 name: <alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink> driver: <module-alsa-card.c> flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9035 volume: front-left: 68812 / 105% / 1.27 dB, front-right: 65125 / 99% / -0.16 dB balance -0.05 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 0.00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 4 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0.00 ms; range is 0.50 .. 341.00 ms card: 1 <alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic> module: 7 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "" alsa.id = "HDMI1 (*)" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "3" alsa.card = "0" alsa.card_name = "sof-hda-dsp" alsa.long_card_name = "sof-hda-dsp" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-0000:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "a0c8" device.product.name = "Tiger Lake-LP Smart Sound Technology Audio Controller" device.string = "hw:sofhdadsp,3" device.buffering.buffer_size = "65472" device.buffering.fragment_size = "16320" device.access_mode = "mmap+timer" device.profile.name = "HiFi: hw:sofhdadsp,3: sink" device.profile.description = "HDMI1 Output" alsa.mixer_device = "hw:sofhdadsp" device.description = "Tiger Lake-LP Smart Sound Technology Audio Controller HDMI1 Output" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: [Out] HDMI1: HDMI1 Output (priority 500, latency offset 0 usec, available: no) properties: active port: <[Out] HDMI1> * index: 4 name: <alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink> driver: <module-alsa-card.c> flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: RUNNING suspend cause: (none) priority: 9032 volume: front-left: 35389 / 54% / -16.06 dB, front-right: 35389 / 54% / -16.06 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 22.61 ms max request: 4 KiB max rewind: 4 KiB monitor source: 5 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 1 linked by: 1 configured latency: 23.22 ms; range is 0.50 .. 341.00 ms card: 1 <alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic> module: 7 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "" alsa.id = "HDA Analog (*)" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "sof-hda-dsp" alsa.long_card_name = "sof-hda-dsp" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-0000:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "a0c8" device.product.name = "Tiger Lake-LP Smart Sound Technology Audio Controller" device.string = "hw:sofhdadsp" device.buffering.buffer_size = "65472" device.buffering.fragment_size = "16320" device.access_mode = "mmap+timer" device.profile.name = "HiFi: hw:sofhdadsp: sink" device.profile.description = "Speaker + Headphones" alsa.mixer_device = "hw:sofhdadsp" device.description = "Tiger Lake-LP Smart Sound Technology Audio Controller Speaker + Headphones" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: [Out] Speaker: Speaker (priority 100, latency offset 0 usec, available: unknown) properties: [Out] Headphones: Headphones (priority 200, latency offset 0 usec, available: no) properties: active port: <[Out] Speaker> 3. When running alsamixer and then hitting F6 I see two options: "- (default)" and "0 sof-hda-dsp" 4. This is the output of $ lspci | grep -i audio: Code: Select all$ lspci | grep -i audio 00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20) 5. This is the output of lsmod | grep '^snd' | column -t: Code: Select all$ lsmod | glsmod | grep '^snd' | column -t snd_soc_skl_hda_dsp 28672 5 snd_soc_hdac_hdmi 45056 1 snd_soc_skl_hda_dsp snd_soc_dmic 16384 1 snd_hda_codec_hdmi 73728 1 snd_hda_codec_realtek 163840 1 snd_hda_codec_generic 98304 1 snd_hda_codec_realtek snd_sof_pci 24576 0 snd_sof_intel_byt 24576 1 snd_sof_pci snd_sof_intel_ipc 20480 1 snd_sof_intel_byt snd_sof_intel_hda_common 102400 1 snd_sof_pci snd_sof_xtensa_dsp 16384 2 snd_sof_intel_hda_common,snd_sof_intel_byt snd_sof 139264 4 snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_sof_intel_ipc snd_sof_intel_hda 20480 1 snd_sof_intel_hda_common snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match 45056 2 snd_sof_pci,snd_sof_intel_hda_common snd_soc_acpi 16384 3 snd_soc_acpi_intel_match,snd_sof_intel_hda_common,snd_sof_intel_byt snd_hda_intel 57344 0 snd_intel_dspcfg 28672 3 snd_hda_intel,snd_sof_pci,snd_sof_intel_hda_common snd_soc_core 319488 7 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_dmic,snd_soc_skl_hda_dsp snd_compress 32768 1 snd_soc_core snd_hda_codec 176128 6 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl_hda_dsp snd_hda_core 110592 11 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda,snd_soc_skl_hda_dsp snd_usb_audio 319488 0 snd_usbmidi_lib 45056 1 snd_usb_audio snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec snd_rawmidi 45056 1 snd_usbmidi_lib snd_seq_device 16384 1 snd_rawmidi snd_pcm 143360 11 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_hda_core snd_timer 49152 1 snd_pcm snd 110592 27 snd_hda_codec_generic,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_soc_hdac_hdmi,snd_compress,thinkpad_acpi,snd_soc_core,snd_pcm,snd_soc_skl_hda_dsp,snd_rawmidi 6. This is the output of aplay -l: Code: Select all$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 7. This is the output of dmesg | grep 'snd\|firmware\|audio': Code: Select all$ sudo dmesg | dmesg | grep 'snd\|firmware\|audio' [ 1.692313] i915 0000:00:02.0: firmware: direct-loading firmware i915/tgl_dmc_ver2_08.bin [ 1.692894] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_08.bin (v2.8) [ 1.799755] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/nvdec/scrubber.bin [ 1.799770] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/acr/bl.bin [ 1.799785] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/acr/ucode_ahesasc.bin [ 1.799795] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/acr/bl.bin [ 1.799804] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/acr/ucode_asb.bin [ 1.799813] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/acr/unload_bl.bin [ 1.799821] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/acr/ucode_unload.bin [ 1.799824] nouveau 0000:01:00.0: pmu: firmware unavailable [ 1.799946] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/fecs_bl.bin [ 1.799957] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/fecs_inst.bin [ 1.799964] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/fecs_data.bin [ 1.799970] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/fecs_sig.bin [ 1.799982] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/gpccs_bl.bin [ 1.799990] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/gpccs_inst.bin [ 1.799996] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/gpccs_data.bin [ 1.800001] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/gpccs_sig.bin [ 1.800009] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/sw_nonctx.bin [ 1.800017] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/sw_ctx.bin [ 1.800025] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/sw_bundle_init.bin [ 1.800036] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/gr/sw_method_init.bin [ 1.800052] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/sec2/sig.bin [ 1.800071] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/sec2/image.bin [ 1.800083] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/tu117/sec2/desc.bin [ 2.929307] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x12, buttons: 3/3 [ 43.700314] platform regulatory.0: firmware: direct-loading firmware regulatory.db [ 43.700550] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [ 43.719491] iwlwifi 0000:00:14.3: firmware: direct-loading firmware iwlwifi-QuZ-a0-hr-b0-59.ucode [ 43.719727] iwlwifi 0000:00:14.3: loaded firmware version 59.601f3a66.0 QuZ-a0-hr-b0-59.ucode op_mode iwlmvm [ 43.719737] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 43.719784] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 43.966494] usbcore: registered new interface driver snd-usb-audio [ 44.143002] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 44.145094] bluetooth hci0: firmware: direct-loading firmware intel/ibt-19-0-4.sfi [ 44.145096] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi [ 44.179415] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 44.179511] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 44.267626] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 44.267641] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 44.267897] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 44.271557] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 44.280678] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 44.374324] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 44.374326] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 44.374328] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 [ 44.377849] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-tgl.ri [ 44.377855] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 6 size 0x20 [ 44.377856] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 [ 44.377857] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 [ 44.377858] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel [ 44.377861] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 3 size 0x30 [ 44.377862] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 5 size 0x20 [ 44.465037] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 [ 44.465038] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 [ 44.465039] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel [ 44.501097] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-hda-generic-2ch.tplg [ 44.501116] sof-audio-pci 0000:00:1f.3: Topology: ABI 3:18:1 Kernel ABI 3:17:0 [ 44.501117] sof-audio-pci 0000:00:1f.3: warn: topology ABI is more recent than kernel [ 44.527774] sof-audio-pci 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 44.580163] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC257: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 44.580164] snd_hda_codec_realtek ehdaudio0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 44.580165] snd_hda_codec_realtek ehdaudio0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 44.580166] snd_hda_codec_realtek ehdaudio0D0: mono: mono_out=0x0 [ 44.580166] snd_hda_codec_realtek ehdaudio0D0: inputs: [ 44.580167] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 [ 44.641085] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten [ 44.641090] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten [ 54.568948] Bluetooth: hci0: Failed to send firmware data (-110) 8. The file `/etc/modprobe.d/alsa.conf ` does not exist on my machine. 9. I have two speaker icons in my task bar. The tooltip of the first says Speaker/Headphones (depending on whether headphones are plugged in), the second says "Playback Devices - Tiger Lake-LP Smart Sound Technology Audio Controller Speaker + Headphones" | Do you have Code: Select allfirmware-sof-signed ? If not, install it and reboot. There is a bug affecting * Lake devices and kernel 5.10.0-20-amd64. Check you kernel with Code: Select all$ uname -a If you have the affected kernel, this may explain your sound problems, so from the Grub menu, boot from the previous kernel (hit the down arrow when the Grub menu appears and select Advanced options for Debian GNU/Linux). |
On my laptop (Thinkpad P15s) with Debian 11, Sleep / Suspend to RAM doesn't work properly. This is what happens when I try to put the laptop to sleep and then wake it up: When I select sleep from the shutdown menu, the screen turns black almost immediately. When I press the power button, then screen turns on almost immediately and shows the desktop or the last active window before the machine went to sleep. After half a second, a black shutdown/bootup screen appears (the same one that I see when I boot the machine) and displays a long list of what I think are kernel messages? The machine then shuts down. As an example, these are the last 4 messages: Code: Select all[ OK ] Reached target Shutdown. [ OK ] Reached target Final Sleep. [ OK ] Finished Power-Off. [ OK ] Reached target Power-Off. I suspect these messages are useful for debugging the problem, but I can't copy them. Could someone point me in the right direction of where to find these (if you think they are important) or have any idea what could cause the problem? General information about my machine: My current kernel version is 5.10.0-19-amd64, but the problem also occurred with 5.10.0-20-amd64. My desktop environment is Plasma. | Hello, What are the KDE/Plasma settings for suspend to ram and hybernate ? They should be in the power management section. System logs are in systemd's journal. The logs since the last kernel boot (before suspension or hibernation) can be extracted with the following command as root user: Code: Select alljournalctl -b 0 --no-pager > systemd.log |
I have an Nvidia Quadro P600 that I'd like to use for transcoding in various Docker containers. I don't know if I should stay with the nouveau kernel driver or swith to the latest Nvidia driver ??? | kent_dorfman766 wrote: 2023-01-20 04:14 I know that under qemu VM that I commonly use, direct gpu/cuda access is impossible (at least was last time I investigated). It should work fine? Direct gpu for sure, cuda I don't use. I've got one running now. I do know in a vm this gpu will accelerate the software QXL gpu, that's a neat trick. Code: Select all$ lspci -nnkd 10de: 04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) Subsystem: Hewlett-Packard Company GK107GL [Quadro K600] [103c:094b] Kernel driver in use: vfio-pci Kernel modules: nouveau 04:00.1 Audio device [0403]: NVIDIA Corporation GK107 HDMI Audio Controller [10de:0e1b] (rev a1) Subsystem: Hewlett-Packard Company GK107 HDMI Audio Controller [103c:094b] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel I'd be curious how well it encodes, if worth it. I just use cpu's, and bet their quieter. |
I've been having this problem recently on my debian bullseye installation where in some instances, the grub rescue menu would show up instead of the usual grub. I have used multiple tutorials: https://www.linuxfoundation.org/blog/bl ... 2-on-linux, https://phoenixnap.com/kb/grub-rescue and https://youtu.be/r7meKJsjqfY to try fixing the issue but none seem to work as important commands like the insmod and setting root/loading the kernel all seem to fail(shown in the screenshots). The bizarre thing about this issue is also the fact that it doesn't always happens, perhaps it happens maybe 4 out of 10 times I boot up my system and after failing to solve it through the tutorial methods, I've found that simply restarting my computer once the rescue screen shows up seems to have a chance of making it go away and to load the correct grub. For context, my computer is a dual boot system with windows and now debian on 2 separate hard drives(the one debian resides in is hd0) with an efi partition on each. When I used manjaro a while ago, I installed it the same way as I installed debian and yet only debian seems to have this issue. I am at my wit's end on any solutions as I cannot find any problems similar to mine online and I do not want to give up on debian yet as I am loving it, but it makes me very nervous that my system could suddenly not just boot while I need it for an emergency. I hope I do not have to go back to manjaro/arch again.**inxi + neofetch information screenshots and my grub rescue attempt shown below** | adrit123 wrote: 2023-01-03 19:41 the grub rescue menu would show up instead of the usual grub What do you mean by "grub rescue menu" ? What happens exactly ? The screenshot does not show any grub rescue shell nor menu, only the normal grub shell. |
Hi! I've never used Debian before, but I have an old harddrive with Debian on it, I'm not sure what the version is, but it is upto 10-15 years old. When booting in single-user-mode with GRUB, I am told that it uses Linux 2.6.32-5-686 and the GNU/GRUB version is 1.98+20100804-12+squeeze. Unforuntately I do not know what the password is, and I am trying to reset it. I have tried entering single user mode in GRUB and resetting the password with `passwd` but I simply get "bash: passwd command not found". I have also tried editing `/etc/shadow` and removing the password for the account, however, the account still requires a login. I am not sure what else to do, any help would be appreciated! If it is usefull, commands such as mkpasswd, chpasswd, adduser, useradd and usermod also throw errors. Also, when I enter bash in single user mode, I get: bash: cannot set terminal process group (-1): Inappropraite ioctl for device bash: no job control in this shell | Hello, You can edit the grub configuration at boot adding the "init=/bin/bash" parameter to the "linux" line. Starting the computer with this configuration, the computer will start a bash shell with full access to the root disk containing the operating system (if not encrypted). Then, you can use the passwd command. |
I have been trying to balance tasks across my CPUs so that the CPU0 memory channel doesnt run so hot. To that end I added ExecStart=taskset 0xf0 /usr/bin/lightdm to the unit file so that the greeter and any of its children should be tied to the cores of CPU1. I then view the results in htop where htop displays processes, but also threads within each process. It looks mostly correct but the tree display shows a couple of lightdm Xorg threads with the wrong core bindings as 0 and 2 instead of 4-7, like they should be. I added the screen dump attachment. Any thoughts on why a couple of the threads are bound to the wrong cores? | If we are talking a single numa group, frankly I don't think manual user space clock and affinity tools will have any useful effect. If you want to tone it down, shut off the threads. If I'm reading this right 4-7 are threads. when there is more physical space between things, then numactl comes into play and can help control power/thermal factors. Within one 'die' the cpu itself will make better choices. It can and does move execution around due to thermal/power limits. Anymore we don't know better! This has been the case for most cpu's in the last decade. |
Hi, Not sure what the issue is but I will try to explain it as best I can. I noticed long load times when using Firefox (102.11.0esr (64 bit)) compared to my Windows10 virtual machine using Firefox 113.0.2 (64-bit) that is bridged to the same Ethernet controller. An example is loading www.dnsleaktest.com and doing the standard test takes 120 sec or 2 min. loading the same web page and test from inside Debian with a Windows10 VM in Virtualbox takes 7 sec., so all the hardware is the same. I have noticed slow loading on most web pages. I then booted my computer on a Linux Mint live USB and noticed the same behavior and then spun up Pop! OS in a VM again the same. I then thought OK Browser issue so I launched Konqueror and it comes up with a different issue "The server failed the authenticity check (89ec995b-696d-47a7-b480-4a882b39bed7.test.dnsleaktest.com). The error is: Server's certificate does not match the URL. Do you want to ignore this error?". I have been trying to figure this out for a few hours that is why I was running the DNS leak check. I also ran a few trace routes interesting enough the trace routes on the Debian machine would get lots of time outs and never reach the destination even with 64 hops while the Windows 10 VM would reach the destination in around 15 hops destination was google.com. the results of the DNS Leak test confirmed that I was using the correct DNS. Any guidance is appreciated to include maybe better verbiage to search the archives. Dual boot with rEFInd SSD to NVME Processor Dual Intel(R) Xeon(R) CPU E5-2670 @ 2.60GHz Memory 98899MB (3681MB used) Machine Type HP z620 Operating System Debian GNU/Linux 11 (bullseye) Cinnamon Desktop Video Card AMD Radeon RX 580 2048SP (POLARIS10, DRM 3.40.0, 5.10.0-23-amd64, LLVM 11.0.1) Ethernet controller Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) | I suspect a driver or firmware issue. Check if driver is loaded, open a terminal and run: Code: Select alllspci -knn | grep -i -A 3 net Check if firmware is installed: Code: Select allapt list -i firmware-realtek Post the output of these commands inside code tags. |
Hello everybody, I am stacked with a network problem since a few days ago. Everything was working just fine when I rebooted my laptop. During the rebooting process it stacked saying “a stop job is running” mentioning something about “watchdog” (sorry, I don’t remember exactly and I don’t have any screenshot of that). The point is that I was in rush, and I forced the shut down by pressing the power button. When I restarted the laptop, both wifi and ethernet connections were connected (looking at network settings) but I have no internet access. Looking for solutions on internet many suggested to check the DNS configurations. Actually when I checked the /etc/resolv.conf the nameserver was badly configured: Code: Select all# Generated by NetworkManager nameserver ::1 I changed it to 8:8:8:8 but, once restarted the system, it went back to the wrong conf (::1). I managed to avoid this behavior on reboot by doing the following after editing the resolv.conf: Code: Select allsudo chattr +i /etc/resolv.conf After this, the file stayed with the correct configuration: Code: Select all# Generated by NetworkManager nameserver 8:8:8:8 nameserver 8:8:4:4 However, internet is not working. I can ping other devices in my network. Code: Select allguido@guido-debian:~$ ping 138.4.46.22 PING 138.4.46.22 (138.4.46.22) 56(84) bytes of data. 64 bytes from 138.4.46.22: icmp_seq=1 ttl=128 time=2.00 ms 64 bytes from 138.4.46.22: icmp_seq=2 ttl=128 time=1.77 ms I can ping 8:8:8:8 Code: Select allguido@guido-debian:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=112 time=2.59 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=112 time=1.62 ms I cannot ping google.com or facebook.com Code: Select allguido@guido-debian:~$ ping google.com ping: google.com: Name or service not known guido@guido-debian:~$ ping facebook.com ping: facebook.com: Name or service not known IP configuration are ok as far as I can say (I use DHCP for IP address). All the previous happens regardless I am using wifi or ethernet connection. I have dual boot with Windows 10, everything works smoothly on windows. I don’t know what to do, I red several threads about this on internet but either they didn’t solve my problem or they were too advanced and hardware specific (I am newby, it is difficult for me to adapt complex solutions). Another thing I noticed is that I had a VPN configured to connect to my working network. It disappeared from network setting. I recently installed ProtonVPN and now the only VPN on my network setting is ProtonVPN. I could not say if the work VPN disappeared when the internet issue began or when I installed ProtonVPN. However I tried to uninstall ProtonVPN. Nothing change, and I can still see ProtonVPN in my network setting even if I cannot see it in installed packages/programs. Any help or suggestion is appreciated. Debian 10 buster, Kernel 4.19.0-22-amd64. Thanks in advance… Guido | Hello, According to your previous post, the computer seems non able to resolve canonical names in IP addresses. Perhaps the VPN configuration is still active and interfere with normal network operations. I suggest you to follow a structured troubleshooting approach, documenting the commands (with their output) you use to replicate and analyse the issue. If you wish, you could also see here [1]. In the meanwhile, It could useful to take a look at the general hardware information of your computer (in anonymous form) with the command (the inxi program must be installed): Code: Select allinxi -Fxxxz It could be useful to check system logs: Code: Select alljournalctl -b0 --no-pager > log.txt The previous command will generate a log file named log.txt that can be compressed and added as attachment to a follow-up message. --- [1] https://www.redhat.com/sysadmin/beginne ... ting-linux |
I upgraded (yes it is an upgrade, not and update!) from Bullseye to Bookworm last night. It went very smoothly, no issues at all. After most major dist-upgrades, typically I'll have to mess with cups-pdf to work "my way". Two of those things being, 1) pre-fixing the job ID, 2) Change the output directory from the default {HOME}/PDF/ to {HOME}/Documents/cups-pdf. I had been able accomplish this by editing edit /etc/cups/cups.conf and changing the label option from 0 to 1, and modify the output path. It appears now that due to apparmor, cups.conf and apparmor profile both need to be edited. From the Bookworm package page https://packages.debian.org/bookworm/pr ... r-cups-pdf Documents are written to a configurable directory (by default to ~/PDF) or can be further manipulated by a post-processing command. Note that AppArmor prevents outputting PDF documents to non-default directories so </etc/apparmor.d/usr.sbin.cupsd> must also be edited, whenever the above default get changed in </etc/cups/cups-pdf.conf>. /etc/apparmor.d/usr.sbin.cupsd doesn't exist, do I need to create it? The statement "must also be edited" implies it is created during apt-get install of the package. However, usr.sbin.cupsd.dpkg-dist does exist. The last section of this file has # allow read and write on almost anything in @{HOME} (lenient, but # private-files-strict is in effect), to support customized "Out" # setting in cups-pdf.conf (Debian#940578) #include <abstractions/private-files-strict> @{HOME}/[^.]*/{,**/} rw, @{HOME}/[^.]*/** rw, Which my understanding is that no modification to usr.sbin.cupsd.dpkg-dist is necessary. So I'm a bit confused what needs editing in order to accomplish my two "tweaks" to customize the output path and filename format. Rich | ramack wrote: 2023-06-12 03:35/etc/apparmor.d/usr.sbin.cupsd doesn't exist It should Code: Select all$> apt-file search "/etc/apparmor.d/usr.sbin.cupsd" cups-daemon: /etc/apparmor.d/usr.sbin.cupsd ramack wrote: 2023-06-12 03:35However, usr.sbin.cupsd.dpkg-dist does exist. From 5.2.3. Checksums, List of Configuration Files, et al. dpkg behaves as intelligently as possible: if the standard configuration file has not changed between the two versions, it does nothing. If, however, the file has changed, it will try to update this file. Two cases are possible: either the administrator has not touched this configuration file, in which case dpkg automatically installs the new version; or the file has been modified, in which case dpkg asks the administrator which version they wish to use (the old one with modifications, or the new one provided with the package). To assist in making this decision, dpkg offers to display a “diff” that shows the difference between the two versions. If the user chooses to retain the old version, the new one will be stored in the same location in a file with the .dpkg-dist suffix. If the user chooses the new version, the old one is retained in a file with the .dpkg-old suffix. You probably said no when asked whether to use the maintainer new file. You can safely Code: Select all#> mv -i /etc/apparmor.d/usr.sbin.cupsd.dpkg-dist /etc/apparmor.d/usr.sbin.cupsd |
I upgraded Debian 11 to 12. My DNS has stopped working. Commands host and dig have started print these errors: Code: Select all;; communications error to ::1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached Connection seems to be OK, because pinging to 8.8.8.8. and 1.1.1.1 is OK. Please, where is the problem and how can I to solve it? Update: I have probably found a clue to the source of the error. File /etc/resolv.conf is link to ../run/systemd/resolve/stub-resolv.conf, which does not exist. | There are several recent topics about this, maybe the answer lies there:- search.php?keywords=resolv.conf |
I have searched for this a lot, and all of the recommendations are for the opposite result I want. I have a headless, remote PC, booting into the GUI desktop. The other person who logs in is incapable of learning the CLI necessary, so the GUI is has to be running. It is connected to an FM radio transmitter on top of a mountain to supply the transmitter with analog audio from an internet stream. When booting, the ethernet port only comes online about 25sec after the GUI finishes loading. The autostart streaming app doesn't handle this at all, and quits. I have put a ping loop in a shell script to delay until the network is ready, but I would prefer to have systemd control things and not continue until network is established (static IP). systemd-networkd service is enabled as is NetworkManager, both by default. I have tried every combination of -wait-online of both that I can think of, but there is never any change. GUI comes up, 30sec wait, connected. All the questions I have read about this are complaining about long boot times. I would prefer that over finagling shell scripts for all the apps I need to start. Any suggestions for how I should proceed? | Please mark the thread as "Solved" adding the tag [Solved] to the subject of the first post, e.g.: [Software][Solved] -wait-online |
Hello, I followed this guide https://www.linuxbabe.com/debian/connec ... supplicant to configure the WiFi connection on 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) without DE. Until I disconnect the Ethernet cable, I have wifi and Ethernet connection. I can SSH to the machine via both interfaces IP's. As soon as I disconnect the cable, the WiFi connection is lost too. If I run "ip a" on the actual machine, it says that the wifi interface is up and running and I have wireless connection, along with properly assigned IP address. But there is no connection to outside of the machine, no ping, nothing... As soon as I connect the cable, wireless connection is working again. What I'm doing wrong? | Good you worked it out. iwd does seem to be an improvement from my limited experience using it once months ago. Please mark this thread [SOLVED] by editing your first post. This info may be useful for others. |
Hi, For space reasons I have rearranged disks and partitions in my PC running Debian 11 x86-64. For the sake of simplicity I'll just say my root partition (LVM) is on /dev/mapper/vg1-lvroot on top of a mdadm RAID 1 array and my /boot/efi FAT32 partition is right on top of another RAID 1 segment but no LVM involved this time. I cannot for the life of me make the GRUB bootloader to start, being forced to use a Super GRUB2 Rescue disk to boot. The error spitted by GRUB is something like it cannot find lvmid/<LVM_ID> which indeed has nothing to do with the true ID of the real LV. I have ran update-grub && grub-install /dev/sda && grub-install /dev/sdb && update-initramfs -u -k all (even -c -k all), both from the running system and from some live distro (booting in UEFI mode and doing the mount -o bind stuff) to no avail. The only place where I have found <LVM_ID> is in some *.vg files in /etc/lvm/archive but it seems there is no trace of this LVM ID anywhere else (none at least in /boot/grub/grub.cfg). Somewhere down the wild I read there were (is?) some bug preventing LVM to be properly updated in GRUB when changes were on the run and they also proposed a workaround doing some minor change to the LVM groups / volumes (as changing a volume group's name then updating/installing GRUB then reverting the change) but that didn't succeed for me. I must admit I'm not much familiarized with all that EFI jazz and I'm not even quite sure my system was really running in UEFI mode before the changes (BIOS settings were in UEFI compatibility mode though, but as long as I remember the efi directory was empty by then). FYI my mobo is a Gigabyte B450M DS3H: https://download.gigabyte.com/FileList/ ... a6b519794a I beg for some guidance on this matter. Cheers, Antonio | avelach wrote: 2022-11-11 12:42 I have rearranged disks and partitions in my PC What did you change ? First, you must determine whether GRUB boots in EFI or BIOS/legacy mode. Do you get a "grub>" or "grub rescue>" prompt ? At the GRUB prompt, type "set" and report the value of the following variables : cmdpath, grub_cpu, grub_platform, prefix, root. Type "ls" and report the device list. If LVM volumes are listed, you should be able to set the proper value for $prefix. Code: Select allset prefix=(lvm/<vg>-<root_lv>)/boot/grub if /boot is in the root LV or Code: Select allset prefix=(lvm/<vg>-<boot_lv>)/grub if /boot is in a separate LV, then Code: Select allinsmod normal normal When in the Debian system (not in a live system), report the output of the following commands: Code: Select alldpkg --get-selections "grub*" ls /boot/grub grub-probe -t drive /boot |
for beginners users: 1. open terminal: sudo nano /etc/default/grub 2. go to: GRUB_CMDLINE_LINUX=" " and add to: GRUB_CMDLINE_LINUX="init_on_alloc=0" 3. save and exit 4. sudo update-grub 5. reboot pc I tested with Linux debian 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux | herreradimas wrote: 2021-08-17 18:12 The new Debian Bullseye by default is using kernel 5.10.0-8-amd64 but this have inconsistent for resume system this broken and does not more response for interface GUI.[..] Thank you all teams Debian and I hope the next release kernel 5 have fixed this details for suspended and resume. :) Hello, Thanks for your report. A bug report has been opened for suspend to ram / suspend to disk issues in Debian 11 with a NVIDIA G96CM [GeForce 9600M GT] graphic card (see [1]): please update the bug report with data from your installation and way of failure, if you can. What is the graphic card installed in your computer ? it would be helpful if you could provide more information using the following command (with the program inxi installed) : Code: Select allinxi -Gxxx [1] https://bugs.debian.org/cgi-bin/bugrepo ... bug=989705 |
Running Debian Bullseye, kernel 5.10.0-19 (10-21-2022) on 8-core 16GB. Not using pulseaudio, not using pipewire. Installed ASUS-BT500 (USB) bluetooth adapter, downloaded and installed Linux drivers from the ASUS website. Command lsusb shows hardware present; lsmod shows driver rtk_btusb loaded. System/Settings/Blueman discovers and pairs the Bose Quiet Connect 35 II, but for a connection option Blueman only offers "Connect to serial port" or "Don't connect". The upshot is that the headphones pair but can't connect. Not sure whether it's important, but again I'm using neither pulseaudio nor pipewire. I've built and installed the USB version of the driver. Log shows no abnormality that I can discern. | I think you should have to install pulseaudio-module-bluetooth to get the headphone to work. |
I am running bullseye $ uname -r 5.19.0-0.deb11.2-amd64 This problem is on the hardware platform and not a VM. This is the message I am seeing over and over again every 5 seconds in syslog: Code: Select allNov 17 13:20:38 blackbox brltty[1698]: /lib/brltty/libbrlttyxa2.so: cannot open shared object file: No such file or directory Nov 17 13:20:38 blackbox brltty[1698]: cannot load screen driver: /lib/brltty/libbrlttyxa2.so Nov 17 13:20:38 blackbox brltty[1698]: screen driver not loadable: a2 I thought that maybe a newer file would fix this but I seem to be running the latest library. Code: Select all$ sudo apt install -t bullseye-backports libglib2.0-0 Reading package lists... Done Building dependency tree... Done Reading state information... Done libglib2.0-0 is already the newest version (2.66.8-1). 0 upgraded, 0 newly installed, 0 to remove and 162 not upgraded. What is happening? it feels like bullseye is simply broken. I suspect this message started appearing when I tried installing -- via apt-get -- gnome-screensaver, which says it can't run because of a session file that is missing. But I am not sure. Just in case the screensaver is related, here is that message: Code: Select all** (gnome-screensaver:5370): WARNING **: 13:52:36.852: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files | Also Code: Select allapt update && apt list --upgradable |
first of all I already search around about 1 day and can not find a useful solution, so I hope ask in forum would fix it XD SYSTEM: debian bookwarm, which is the latest testing version of debian now DESKTOP: KDE my content with crontab -e Code: Select all@reboot cfw @reboot python -m http.server 9191 --directory ~/Rules --bind 0.0.0.0 cfw is a symbollink I create in /usr/bin/cfw, if I run cfw in terminal by hand, it works perfectlly along with terminal session alive, but in cron it just not working the second cron job start a python server, it works perfectlly so I dont know where is the problem, please help me fix it, appreciated ! ADDITION INFO: cfw is ClashForWindows linux release, github link | You are trying to run a GUI (X) program, from a non-interactive session (cron), which is furthermore running as root instead of your user. If you want to autostart a program when your user logs in X, there are many ways, including the use of ~/.config/autostart, which most DEs honor. |
Hello, I recently installed Debian 11 (kernel Linux 5.10.0-19-amd64) and I am experiencing some problems with the WiFi module. After the installation, the WiFi option was not showing up, so I manually downloaded the drivers from https://github.com/lwfinger/rtw89 and installed them. The WiFi was then working but terribly slow compared to e.g. the phone. I read somewhere that the problem might be due to conflicting drivers. I tried to blacklist the one that I do not need but not only I couldn't figure out which are the ones that I need, but it also seems that the blacklist command does not work: I tried to blacklist all the available drivers and the WiFi was still working after reboot. I attach some screenshots to give more details: Can someone please help me? I am not very expert with Linux systems | Try - Install firmware-realtek from non-free repo. Install the most recent kernel from bullseye-backports |
Hello, Before this conversation starts, I just want to inform the reader that I'm using Debian Bullseye. I have been using Tor for many applications including the Debian SourcesList as found on here https://wiki.debian.org/SourcesList for a number of years now, I'm heavily dependent it's functionality. Now, I have been using Tor to do all my updates and upgrades for a long time without any problems till recently. I started getting the failed the fetch errors on a regular basis that I cannot make go away. Taking a closer look at this, I noticed that the links are still in version 2 onion. In July of 2021, version 2 addresses were discontinued as mentioned here https://support.torproject.org/onionser ... precation/. I would like to go back to using Tor in my sources list. My first guess to fixing these "failed to fetch" errors is by reconfiguring the list with version 3 onion links. Only problem is, I can't find any information anywhere as to where or what the version 3 addresses are. The only thing I have to go on is the Debian Wiki. Is there anyone that could please assist me with this problem? Thanks | Have you tried another mirror? They're listed here: https://onion.debian.org/ |
Hello everyone, I’m getting the following error when trying to utilize snap on Debian 11 / bullseye Code: Select allroot@puppeteer:~# snap install core error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-mountpoint-180662911: unknown filesystem type 'squashfs'. I read through all the forum posts/stackover I could and nothing helped. Here is all the info I could gather. I would appreciate any help you could provided. I restarted the machine between and after every step. Code: Select allroot@puppeteer:~# snap --version snap 2.49-1+deb11u1 snapd 2.49-1+deb11u1 series 16 debian 11 kernel 5.10.0-19-amd64 root@puppeteer:/tmp# snap download hello-world Fetching snap "hello-world" Fetching assertions for "hello-world" Install the snap with: snap ack hello-world_29.assert snap install hello-world_29.snap root@puppeteer:/tmp# mkdir snap-test root@puppeteer:/tmp# mount hello-world*.snap snap-test mount: /tmp/snap-test: unknown filesystem type 'squashfs'. root@puppeteer:~# sestatus -bash: sestatus: command not found root@puppeteer:~# apt install libsquashfuse0 squashfuse fuse Reading package lists... Done Building dependency tree... Done Reading state information... Done fuse is already the newest version (2.9.9-5). libsquashfuse0 is already the newest version (0.1.103-3). squashfuse is already the newest version (0.1.103-3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@puppeteer:/tmp# grep squashfs /proc/filesystems root@puppeteer:/tmp# root@puppeteer:/tmp# journalctl -u snapd @ https://sourceb.in/YlNydVLb9m When I run the following commands squashfs is not in them Code: Select alllsmod cat /proc/filesystems Unfortunately when I run "modprobe squashfs" this command changes nothing in the above commands. System Info @ Code: Select allroot@puppeteer:~# cat /proc/version Linux version 5.10.0-19-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-2 (2022-10-21) root@puppeteer:~# cat /etc/*-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye I would appreciate any help | Does "modprobe squashfs" return an error ? If not, squashfs should be present in /proc/modules and /proc/filesystems unless an "install squashfs" directive is present in /etc/modprobe.d/*.conf. Any related messages in the kernel logs ? |
I tried to use this site locally with apache2: https://github.com/pippim/pippim.github.io. If I change index.md to index.html it loads but very bad. How can I use it locally? | You can run it locally using what gihub pages use jekyll: 1 Clone the repo. 2 Create a Gemfile with this line: "gem "github-pages", group: :jekyll_plugins". 3 Run "bundle install". 4 Run your Jekyll site locally "bundle exec jekyll serve". 5 Connet to http://localhost:4000 instead of http://127.0.0.1:4000/. |
Hello! I have recently installed Debian 12 with LXDE and LXQT on the one of my old machines. I have installed it using Debian live DVD. During the installation process the wi-fi network was found and laptop connected. I logged into LXDE, the internet is working out of the box, if i remember correctly, all seems fine. I checked the Connman settings, it was complex, but still fine. Then i logged into LXQT, there i had to manually connect to wi-fi with Connman. OK. It works. But. After restart i can't see any network connections, though wi-fi is working. Connman shows me that wi-fi is powered and on, green. But when i switch to wireless services option all is empty. I can't change the wi-fi connection. It doesn't see any. This situation is seen both in LXDE and LXQT At first i thought that the problem is in Connman, i have installed "network-manager" and tried to use nmtui. Result is the same - No connections. I gave a try to network-manager-gnome - same. I can see in tray under the "Wi-fi networks" that "device not managed" I must mention here that before i had here Debian 11 XFCE and i had no such problems there. OK, lets go full CLI. Code: Select allroot@debian:~# iwlist wlan0 scan wlan0 Interface doesn't support scanning. Hm. Code: Select allroot@debian:~# ping -c 3 google.com PING google.com (173.194.222.139) 56(84) bytes of data. 64 bytes from lo-in-f139.1e100.net (173.194.222.139): icmp_seq=1 ttl=106 time=21.0 ms .............etc --- google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 21.014/21.780/22.993/0.867 ms ip addr show Code: Select allroot@debian:~# ip addr show 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: eno1: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether ec:9a:74:3e:a8:8a brd ff:ff:ff:ff:ff:ff altname enp2s0 3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9c:b7:0d:62:9e:98 brd ff:ff:ff:ff:ff:ff altname wlp1s0 inet 192.168.1.70/24 brd 192.168.1.255 scope global dynamic wlo1 valid_lft 79158sec preferred_lft 79158sec inet6 fe80::9eb7:dff:fe62:9e98/64 scope link valid_lft forever preferred_lft forever I am not qualified to say what it means, unfortunately. And my Network hardware from INXI Code: Select all Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k Will be glad to hear any ideas. | Hello, There's a bug report about it [1], even if the OP reports that he/she cannot configure the wifi at all. How do you have configured the wireless network ? Did you use the /etc/network/interfaces file ? --- [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948865 |
I'm in a world of hurt. A thunderstorm zapped the onboard Ethernet port on my Buster Linux server. I plugged a NIC into an open slot, then commanded ip to bring it up, but I got a message saying the firmware was missing. After searching the Web, I found the firmware file firmware-bnx2x_20190114+really20220913-0+deb10u1_all.deb, which I burned to a DVD. I can mount the DVD and see the file (everything I do is CLI logged in as root). But I haven't discovered how to install it. One web page advises to use apt-cdrom to install the firmware, but another says, "You have to install the .deb and the dependencies, with dpkg. As long as you have all the dependencies, you should be able to install them with dpkg." Sure enough, apt-cdrom doesn't find any useful files on the DVD. I tried dpkg -i /mountpoint/firmware-bnx2x_20190114+really20220913-0+deb10u1_all.deb. It seemed to run OK, but when I used ip to bring up he link, I got the same "no firmware" message. What dependencies are required, and where can I find them? I'll need to burn another DVD with all the needed files. Can anyone point me in the right direction to install the firmware file for my NIC? Thank you! | arzgi wrote: 2023-06-30 18:03 Just use apt. As root or with sudo Code: Select allapt install some.deb Actually it is Code: Select allapt install ./some.deb from a terminal opened in the directory containing the .deb . Without the "./" it will look in the repositories and fail. And that is assuming that is the correct firmware for your device. To inform us what is your actual device, post the output of Code: Select alllspci |grep -i net |
hi, there help me please to understand the situation about iw which is both present and absent from debian 12 newly installed on my PC Code: Select allbash: iw: command not found da@debian:~/rtl8192eu-linux-driver$ sudo apt install iw Reading package lists... Done Building dependency tree... Done Reading state information... Done iw is already the newest version (5.19-1). iw set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. da@debian:~/rtl8192eu-linux-driver$ iw bash: iw: command not found da@debian:~/rtl8192eu-linux-driver$ sudo iw list da@debian thank you for your kind attention | Hello, The iw command is in the path of the superuser (user root): Code: Select all$ ls /sbin/iw -la -rwxr-xr-x 1 root root 290072 13 Jul 2022 /sbin/iw To acquire user root privileges, you can use the Code: Select allsudo or the Code: Select allsu -l commands. Otherwise, you can execute it specifying the complete path if an unprivileged command is required (to query wlp3s0 wireless interface, e.g.): Code: Select all$ /sbin/iw dev wlp3s0 info |
Kernel is not upgrading to latest version with following warnings: Setting up linux-image-6.1.0-10-amd64 (6.1.37-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-10-amd64. dkms: autoinstall for kernel: 6.1.0-10-amd64. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64 W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module amdgpu raspi-firmware: missing /boot/firmware, did you forget to mount it? run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1 run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure): installed linux-image-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); however: Package linux-image-6.1.0-10-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-6.1.0-10-amd64 linux-image-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) If anyone knows the location of the missing firmware, I can install manually. | The amdgpu lines are harmless warnings. Your real problem is raspi-firmware. |
I have a combo laptop (detachable keyboard) and from power saving / SSD wear reasons, I want to disable certain NVME power states. Power states available: Code: Select allsmartctl -a /dev/nvme1 Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 2.60W - - 0 0 0 0 0 0 1 + 2.60W - - 1 1 1 1 0 0 2 + 1.70W - - 2 2 2 2 0 0 3 - 0.0250W - - 3 3 3 3 5000 9000 4 - 0.0025W - - 4 4 4 4 5000 44000 (this is confirmed by nvme id-ctrl /dev/nvme1 command) current powerstate: Code: Select allnvme get-feature /dev/nvme1 -f 2 -H get-feature:0x02 (Power Management), Current value:0x00000004 Workload Hint (WH): 0 - No Workload Power State (PS): 4 ...meaning the SSD is idle. If I start to write something, then the power state will change / decrease. This is because Autonomous Power State Transition is on: Code: Select allnvme get-feature /dev/nvme1 -f 0x0c -H get-feature:0x0c (Autonomous Power State Transition), Current value:0x00000001 Autonomous Power State Transition Enable (APSTE): Enabled If I disable automatic power state in kernel (nvme_core.default_ps_max_latency_us=0) and then set power state: Code: Select allnvme set-feature /dev/nvme1 -f 2 -v 3 then the power state will NOT change (it will remain stuck on 3), meaning the SSD will get warm because the power state will remain the same (1.7W in this case). If I set a manual value (/sys/module/nvme_core/parameters/nvme_core.default_ps_max_latency_us), this means all power states with a latency greater than the one I specified will not be used. This is actually the contrary of what I want to obtain. I should use APST, but disable certain power states (0 and 1 in my case), but I didn't found how I can do that. Archlinux documentation states that this is possible, but doesn't say how. Please help. | Hello, Can be this [1] useful ? --- [1] https://nvmexpress.org/resource/technology-power-features/ |
Hello, I would like to ask a question on how to troubleshoot booting. I am admin for a small server that mainly runs file sharing (over fuse-ssh), gitlab-ce and mail for a small work group. Main hardware is from supermicro (X11SCL-IF), 4 hard drives in a Raid array for file storage, and a SSD to run the os. Os has been Debian, for the last 15years or so, works flawlessly for this purpose so far . The machine runs well, with the exception of the m.2 nvme drive. I first used a Kingston m.2 SSD, which started to generate a lot of read / write errors after one or two months. Brought it back to the store, they could not find anything wrong with the drive, but offered a Samsung replacement So ran the Samsung m.2 SSD, which also started to generate errors. Switched to a Western Digital SSD. The idea behind this is that there may be something odd with the nvme hardware, so switching to sata would help. And it seems it did, system is running fine for several months, no issue... no read/write errors... however. During updates, I find it still boots in a very old kernel. After a short search it seems like something odd is going on. The system is still (partially) booting from the m.2 disk, to remedy this I tried the following: - checked bios settings -> set to 'dual' meaning both uefi/mbr boot. ( tried setting this to 'legacy/mbr' did not make a difference). -> check that sata ssd is the first boot option, it is. - checked grub -> did 'grub-mkconfig", "update-grub" and "grub-install /dev/sde" -> reboot, this did not help the situation. - reinstall grub bootloader from usb on /dev/sde using rescue mode. -> reboot, this did not help the situation either. - check for mbr using "file -s /dev/sde" -> "/dev/sde: Dos/mbr boot sector" (? dos no grub ?) - check for mbr using "file -s /dev/sde1" -> "/dev/sde1: Dos/mbr boot sector ... " (? same question as above ...) - check for mbr using "file -s /dev/sde5" -> "/dev/sde5: Linux rev 1.0 ... " (? no boot sector ?) - check for boot flag using fdisk /dev/sde: - boot flag on /dev/sde5 ( where I think it should be ). -> ?? This is puzzling to me, "file" shows boot sectors where "fdisk" does not show boot flags and the other way around. I am assuming there is a difference between a mbr and a bootable flag... - check for mbr using "file -s /dev/nvme0n1" -> "/dev/nvme0n1: Dos/mbr boot sector" (? dos no grub ?) I cannot see what is wrong, unless the 'dos/mbr boot sector' flag is wrong. But that would be odd, there has been no dos or windows installed on this system. I have come up with two theories... I would like to ask help in testing them... What may be a factor is that I have moved the system from one drive to another using 'dd' (i.e. clone). That way, I thought, the system should be transferred nicely, but things like drive UUID's are also the same. I wonder if that might have something to do with it, how I could check? and if so fix? The other idea is that for some reason, the MBR on /dev/sde is not pointing to /dev/sde5/boot/. Or for some reason not running the grub on the sde drive. But is there a way to check what is in the MBR? can you check what is happening? I am hesitant to just reinstall everything as that typically takes a significant amount of time and testing. And I am pretty sure I am not the only one with this problem, how to switch hardware on the drive the system runs on? So I request help, any hints very much appreciated! Boris | PanToffel wrote: 2023-05-17 09:29I am assuming there is a difference between a mbr and a bootable flag. Indeed. The "boot" partition flag is a value within a boot record, hinting the BIOS and/or bootloader which boot record to use. PanToffel wrote: 2023-05-17 09:29unless the 'dos/mbr boot sector' flag is wrong. But that would be odd, there has been no dos or windows installed on this system. "dos/mbr" is a reference to the partition table and boot sector format on the disk. The "DOS compatible PC" and all the baggage that goes with it long predates GNU/Linux. Whether it was actual DOS that wrote the partiton table is irrelevant, if you're booting in "legacy" mode, that's how the BIOS will look for an OS to boot. PanToffel wrote: 2023-05-17 09:29things like drive UUID's are also the same. I wonder if that might have something to do with itQuite possibly. Probably, even. Unless you have configured things otherwise, both grub and initrd/fstab will be using UUIDs... Potentially leading to entertainingly random combinations of kernel image/initrd, boot and root partitions on startup. PanToffel wrote: 2023-05-17 09:29how I could check? Compare output of blkid [device of interest] to contents of fstab, grub.cfg, and output of mount. PanToffel wrote: 2023-05-17 09:29and if so fix? For filesystem UUIDs, something like: 'tune2fs -U [new UUID or "random"] [partition]' (for ext4), or equivalent if you are running some other filesystem. See relevant command manual page. For (GPT) partition UUIDs, look in fdisk's "expert" menu. Or just, ya know, pull or nuke the disk you're not using. |
Hi, folks I have Debian 8 installed, using: * gdm3 as the default display manager (set up in "/etc/X11/default-display-manager"); * LXDE as the default desktop environment. I did "dpkg-reconfigure locales" and I selected three languages: "en_US.UTF-8", "it_IT.UTF-8", "sv_SE.UTF-8" (the predefined one is "it_IT.UTF-8"). Now I wish to create two more users each with a different language (both for X and console applications). I did a lot of googling without success; I tried modifying ~/.profile or ~/.dmrc (adding "export LANG=...") but they didn't work. I was able to change only the system-wide language, not the one of a single user. I got the conclusion that It's not possible to have multiple users each with a different language. Is it true? Thanks to all. *** UPDATE: I made another try: In another installation (Debian 8, with GNOME and LXDE) I created two users: antonio, ida The former has only one hidden file in its home-dir: ".bashrc" with "LANG=it_IT.UTF-8" as the last line (no "export $LANG" added). The latter ("ida") has only two hidden files in its home-dir: 1. ".bashrc" clean, with no "LANG=it_IT.UTF-8" line 2. ".dmrc" containing two lines: [Desktop] Language=sv_SE.utf8 I put "/usr/sbin/gdm3" in "/etc/X11/default-display-manager" After reboot both users are OK: each of them displays its own language: antonio has all menus and programs in italian ida has all menus and programs in swedish It looks curious to me ; I don't know why, but that's it. Someome else can confirm it? Thanks to all *** UPDATE 2 I was able to create 4 users with 4 languages (SE, IT, FR, ES). Then I deleted all directory and files (including "~/.bashrc" and "~/.dmrc") of one user, rebooted the PC, and NOTHING changed! So, where is stored the user's language? Not in his home; there is a list elsewere? *** UPDATE 3 I don't know why (I wait someone explaining me), but now I can tell others how to do: 0. Use "lightdm" (not "gdm3") as the display manager (see "/etc/X11/default-display-manager") To install it: su -c "apt-get install lightdm" 1. su -c "dpkg-reconfigure locales" (select the desired locales: en_US.UTF-8, it_IT.UTF-8, sv_SE.UTF-8, etc; set "default locale for the system environment=None") 2. su -c "adduser emil" ("emil" is the name of a swedish user) 3. Logout 4. Select "Swedish" as default language (see at the top-right corner of the screen) 5. Write user name (emil) and password to login 6. After login, language is english (but file "~/.dmrc" is created with the correct language). 7. Reboot PC. 8. After reboot, login again as "emil": now language is Swedish Now you can change the display manager to gdm3 if you prefer. To change applications language: su -c "apt-get install task-swedish task-swedish-desktop" Hope it helps *** UPDATE 4 I found the file containing the user's language: it's the same containing the link to its icon: /var/lib/AccountsService/users/UserName (needs "apt-get install accountsservice"). Editing that file is much simpler as I described earlier | Did you modify ~/.profile with non-root user? How about ~/.bashrc ? Code: Select allexport LANG=it_IT.UTF-8 http://www.shellhacks.com/en/HowTo-Chan ... t-in-Linux Modifying ~/.bashrc works correctly on one of my debian sid. Did you log out and log in? Modification takes effect after re-logging in. |
On my first pc (debian 11 kde plasma ) is did a frugal install of Parted Magic.. I copied the pqmagic folder to /boot and added the following line to /etc/grub.d/40_custom: Code: Select allmenuentry "Parted Magic" { set root=(hd0,1) linux /boot/pmagic/bzImage root=/dev/sda directory=boot edd=on vga=normal initrd /boot/pmagic/initrd.img /boot/pmagic/fu.img /boot/pmagic/m.img } (see: https://partedmagic.com/frugal-install/) After sudo update-grub Parted Magic was visible in the grub menu and could be started On my second pc I also wanted the frugal install of Parted Magic so I did exactly the same: copy pqmagic folder, edit the file 40_custom and updated grub. But Parted magic did not show in the grub menu. So grub does not see Parted Magic On both systems the system is installed on partition /dev/sda1. I think the line 'set root=(hd0,1)' could be the problem but I cannot figure out what is wrong. | peer wrote: 2022-09-14 07:30 I tried your suggestions. But it still does not work. Perhaps I am doing something completely wrong. How would we know ? This statement does not provide any useful information. Please describe in detail what you did and what happened. AFAIK the presence of a menu entry does not depend on its contents. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.